surveys.yml

locale: ja-JP
translations:
  ###########################################################################
  # General
  ###########################################################################

  - key: general.title
    t: Devographics Surveys
  - key: general.description
    t: The State of JavaScript, State of CSS, State of HTML, and other developer surveys.

  - key: general.no_preview_surveys
    t: 表示できるアンケートはありません
  - key: general.global_nav
    t: グローバル
  - key: general.survey_status_preview
    t: Preview
  - key: general.survey_status_open
    t: Open
  - key: general.survey_status_closed
    t: Closed
  - key: general.survey_status_hidden
    t: Hidden

  - key: general.pick_up_to
    t: 最大{limit}つ選択してください。

  - key: general.privacy_policy
    t: Privacy Policy
  - key: general.privacy_policy.description
    t: >
      ### 1. Data Collection

      In addition to the data collected through a survey's questions, we collect your device, browser, OS, browser version, and referrer.

      Note that all questions are entirely optional, and we never link any identifiable information (such as email addresses) to your survey answers.

      ### 2. Email Collection

      We may optionally collect your email to:


      1. Generate a magic log-in link, after which we discard your email and only keep a one-way hash in our user database.

      2. Contact you once survey results are available, as well as when we launch future editions of a survey and for infrequent announcements. You can unsubscribe from our mailing list at any time, and your email is discarded from our records once it is sent to our email newsletter provider.

      3. Send you a recap list of features or tools you want to learn more about. We will discard your address once the email has been sent out through our transactional email provider.


      When we do collect your email address, it is never linked to your responses for a survey, or to your user account.

      ### 3. Cookies

      We set a log-in cookie, and our hosting provider (Vercel) may also sets its own cookie. We do not set any other cookie or use client-side analytics or ads.

      ### 4. Data Use

      We process the data and then use it to publish reports. We also make the entire dataset publicly available.

      ### 5. Data/Account Deletion

      You can email us at [hello@stateofjs.com](mailto:hello@stateofjs.com) if you'd like us to delete all or part of your data.

  ###########################################################################
  # Other UI Strings
  ###########################################################################

  - key: textlist.placeholder
    t: Item {index}…

  - key: feature.unimplemented
    t: どのブラウザも未実装

  - key: general.skip_question
    t: スキップ

  - key: general.unskip_question
    t: 回答する

  - key: general.skip_question.description
    t: 質問をスキップして完了する

  - key: general.unskip_question.description
    t: 質問をスキップ解除して回答する

  - key: years.less_than_one_year
    t: 1年未満

  - key: years.years
    t: 年

  - key: likert.option.0
    t: とても不満
  - key: likert.option.1
    t: 不満
  - key: likert.option.2
    t: どちらでもない
  - key: likert.option.3
    t: 満足
  - key: likert.option.4
    t: とても満足

  - key: general.numeric_input.invalid_input
    t: Please make sure you enter a valid number.

  - key: general.numeric_input.unit.years
    t: 年
  - key: general.numeric_input.unit.years_old
    t: 歳
  - key: general.numeric_input.unit.hours
    t: 時間

  ###########################################################################
  # Errors & Messages
  ###########################################################################

  - key: error.duplicate_response
    t: ごめんなさい、このアンケートに関してすでに進行中のセッションがあるようです。

  - key: error.report_issue
    t: Report issue

  - key: success.data_saved
    t: Data Saved
  - key: success.data_saved.description
    t: 保存されました。

  ###########################################################################
  # Accounts
  ###########################################################################

  - key: accounts.create_account
    t: アカウントを使って回答する
  - key: accounts.create_account.description
    t: アカウントがあれば自分の回答データを見返すことができ、調査結果が公開されたタイミングで通知を受け取ることができます。
  - key: accounts.create_account.note
    t: すでにアカウントをお持ちの方には、ログインのためのメールでマジックリンクを送信します。
  - key: accounts.create_account.action
    t: アカウントを使って回答する
  - key: accounts.your_email
    t: Your Email

  - key: accounts.upgrade_account.action
    t: アカウントをアップグレードする
  - key: accounts.upgrade_account.description
    t: セッションが終了した後も自分の回答にアクセスしたい場合はメールアドレスを使用してアカウントをアップグレードしてください。

  - key: accounts.continue_as_guest
    t: ゲストとして回答する
  - key: accounts.continue_as_guest.description
    t: 匿名で回答することもできますが、セッションが終了したあとは自分の回答データを見返すことはできません。
  - key: accounts.continue_as_guest.action
    t: ゲストとして回答する

  - 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.
    # Open known mail provider directly in browser with the right search params
  - key: accounts.magic_link.browser
    t: <a href="{link}">Click to open your inbox.</a>

  ###########################################################################
  # FAQ
  ###########################################################################

  - key: general.faq
    t: FAQ
  - key: faq.create_account
    t: アカウントを作る必要はありますか？
  - key: faq.create_account.description
    t: 重複回答を避けるため、またあなたの回答データを保存するため、そして結果が公開されたときにあなたに伝えられるよう、アカウントの作成をお願いしています。
  - key: faq.anonymous_survey
    t: 匿名での回答はできますか？
  - key: faq.anonymous_survey.description
    t: はい。偽のメールアドレス（something@example.com）や、個人を特定しないメールアドレスを利用すれば可能です。アドレスが分かってさえいれば、回答を保持できます。
  - key: faq.questions_required
    t: 全部の質問に答えないといけませんか？
  - key: faq.questions_required.description
    t: すべての回答は任意になっているので、飛ばすこともできます。
  - key: faq.data_published
    t: 私のデータは公開されますか？
  - key: faq.data_published.description
    t: はい。基本的にすべてのデータが公開されますが、個人を特定可能な情報（メールアドレス、ユーザー名、IDなど）は省かれます。
  - key: faq.survey_design
    t: 設問はどうやって作られましたか？
  - key: faq.survey_design.description
    t: アンケートの設問はコミュニティからフィードバックや、エキスパートのレビューを経て作られています。[詳細はこちら](https://dev.to/sachagreif/how-the-state-of-js-css-surveys-are-run-4lnb)
  - key: faq.results_released
    t: 結果はいつ公開されますか？
  - key: faq.results_released.description
    t: 基本的にはアンケート期間終了後、数週間で公開しています。
  - key: faq.survey_deadline
    t: 回答期限はいつまでですか？
  - key: faq.survey_deadline.description
    t: このアンケートは {date} まで実施しています。
  - key: faq.team
    t: このアンケートは誰が行っていますか？
  - key: faq.team.description
    t: アンケートは[私](http://sachagreif.com)を中心に、コントリビュータや翻訳者、ボランティアの協力のもと行っています。

  ###########################################################################
  # Form Controls
  ###########################################################################

  - key: bracket.vs
    t: VS
  - key: bracket.start_over
    t: 最初からやり直す
  - key: bracket.winner
    t: 勝者：
  - key: bracket.round
    t: ラウンド
  - key: bracket.empty_bracket
    t: 結果待ち（前のラウンドを完了してください）
  - key: bracket.result
    t: 結果
  - key: bracket.cancel
    t: キャンセル

  - key: experience.leave_comment
    t: Leave a Comment (optional)
  - key: experience.leave_comment_short
    t: Leave a Comment
  - key: experience.tell_us_more
    t: "You answered “{response}”. Tell us more about your choice:"
  - key: experience.tell_us_more_generic
    t: "Tell us more about your answer:"
  - key: experience.tell_us_more_no_value
    t: "You didn't pick any response. Tell us why:"

  ###########################################################################
  # Response
  ###########################################################################

  - key: response.completion
    t: "{completion}% completed"

  - key: response.details
    t: Started on {startedAt}, {completion}% completed.

  ###########################################################################
  # Reading List
  ###########################################################################

  - key: readinglist.prompt
    t: >
      あなたは “{option}” を選びました。"+"ボタンをクリックしてリーディングリストに追加すれば、アンケート終了後にこの機能についてもっと詳しく知ることができます。

  - key: readinglist.add_to_list
    t: リーディングリストに追加する

  - key: readinglist.remove_from_list
    t: リーディングリストから削除する

  - key: readinglist.added_to_list
    t: “{label}” をリーディングリストに追加しました。

  - key: readinglist.title
    t: リーディングリスト

  - key: readinglist.description
    t: >
      "+"ボタンをクリックしてリーディングリストに追加すれば、アンケート終了後にリンクの一覧が表示されます。

  - key: readinglist.empty
    t: >
      リーディングリストには項目がありません。アンケートに戻り、詳しく知りたい機能やライブラリの"+"ボタンをクリックして、リーディングリストに追加してみてください。

  - key: readinglist.results
    t: >
      以下のリンクから、あなたがリーディングリストに追加した項目についてさらに学ぶことができます：

  - key: readinglist.homepage_link
    t: ホームページ

  - key: readinglist.receive_copy
    t: >
      リーディングリストをメールで受け取るためには、メールアドレスを入力してください：
  - key: readinglist.send_by_email
    t: 送信
  - key: readinglist.email_sent
    t: ありがとう！あなたのリーディングリストは、あなたのメールボックスに送られています。

  ###########################################################################
  # Score & Knowledge Ranks
  ###########################################################################

  - key: knowledge_rank.your_rank
    t: "Your Rank:"
  - key: knowledge_rank.rank1
    t: Novice
  - key: knowledge_rank.rank2
    t: Apprentice
  - key: knowledge_rank.rank3
    t: Intermediate
  - key: knowledge_rank.rank4
    t: Expert
  - key: knowledge_rank.rank5
    t: Scholar
  - key: knowledge_rank.rank6
    t: Elite

  ###########################################################################
  # Survey-Specific Intros
  ###########################################################################

  - key: general.js2020.survey_intro
    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.

  - key: general.css2021.survey_intro
    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!

  - key: general.js2021.survey_intro
    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!

  - key: general.graphql2022.survey_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.css2022.survey_intro
    t: |
      CSS keeps progressing at an unprecedented rate. Luckily this year we got help from someone at the forefront of all these changes: [Lea Verou](https://lea.verou.me/) took the lead on selecting this year's questions, with a special focus on highlighting new and upcoming CSS features.

      What's more, the survey results will also help browser vendors prioritize their roadmaps and work towards better compatibility between browsers.

      With all this out of the way, let's see how CSS evolved in 2022!

  - key: general.js2022.survey_intro
    t: |
      For the first time in a while, it feels like the status quo of the JavaScript ecosystem is being questioned.

      Faster bundling with Vite, island architecture with Astro, resumability with Qwik… New entrants are challenging the old guard, and the result is a lot more excitement, but also
      a lot more uncertainty.

      So once more, let's try and figure out together where JavaScript is going, in 2022 and beyond.

  - key: general.css2023.survey_intro
    t: |
      To help you keep up with `:has()`, `@container`, and all the other new CSS features, we're introducing a new feature of our own this year: the **Reading List**.

      As you take the survey, you'll be able to bookmark any feature you want and learn more about it after you submit your answers.

      This year [Chen Hui Jing](https://chenhuijing.com/) took the lead of the survey design process, building on the work done by [Lea Verou](https://lea.verou.me/) last year. And as usual, your feedback here will play a key role in helping browser vendors prioritize their roadmaps and work towards better compatibility between browsers.

      With all this out of the way, let's see how CSS has evolved so far in 2023!

  # Intro for actual survey page
  - key: general.html2023.survey_intro
    t: |
      While web developers tend to focus on JavaScript and CSS, none of what we do would be possible without HTML acting as the foundation.

      It has long seemed like HTML wasn't evolving, but things may be changing.
      New elements like `<selectlist>` are on the horizon, cool new features like popovers,
      and a swath of related browser APIs (Web Components, PWAs, etc.).

      This year, [Lea Verou](https://lea.verou.me/) took on the formidable task of leading the design of this brand new survey, from content to UX and beyond.

      Building on the success of [State of JS](http://stateofjs.com/) and [State of CSS](https://stateofcss.com/), we introduce **State of HTML**;
      the last missing piece that completes the trilogy, so we can track the evolution of the web platform as a whole.

      Benefits to you:
      - Survey results are **used by browsers** and standards groups **for roadmap prioritization**.
      Your responses can help get features you care about implemented, browser incompatibilities being prioritized, and gaps in the platform being addressed.
      - Learn about new and upcoming features; add features to your reading list and get a list of resources at the end!
      - Get a personalized knowledge score and see how you compare to other respondents

      The survey will be open for 3 weeks, but responses entered **within the first 9 days (until October 1st)** will have a much higher impact on the Web,
      as preliminary data will be used for certain prioritization efforts that have deadlines before then.

  - key: general.react2023.survey_intro
    t: |
      As soon as React was first introduced, it was clear that it would become a big deal for the web. 

      It was used to build Facebook after all, and despite this weird "JSX" thing, developers quickly adopted it. And what's even more impressive, the community stuck on through major changes such as function components and hooks. 

      But it's now 10 years later and the newly-introduced React Server Components promise to be the biggest change since… well, since React itself!

      Will the community follow along one more time? Or will developers jump ship to Svelte, Solid, or something else?

      Let's find out together with the first ever State of React survey!

  # JS 2023

  - key: general.js2023.survey_intro_not_used
    t: |
      Between Astro, Vite, and Remix, 2022 kicked off a wave of JavaScript change that kept on growing in 2023 with Bun, Svelte 5, Tauri, and many others. 

      But the –relatively speaking– old guard hasn't been standing still either, with Next.js and React leading the way with innovations such as Server Components and Server Actions. 

      So after yet another busy year, it's now time to take stock, and see where things stand in the JavaScript ecosystem.

  ###########################################################################
  # Survey-Specific FAQs
  ###########################################################################

  # CSS

  - key: faq.data_used_css
    t: How will this data be used?
  - key: faq.data_used_css.description
    t: >
      All data collected will be released openly for any developer or company to consult.
      Browser vendors also [use this data](https://web.dev/interop-2023/) to prioritize focus areas and inform their roadmaps.

  - key: faq.who_should_take_survey_css
    t: Who should take this survey?
  - key: faq.who_should_take_survey_css.description
    t: >
      This is an open survey for anybody who writes CSS, whether regularly
      or occasionally, as part of their job, as a student, or just for fun!

  - key: faq.survey_goals_css
    t: What is the survey's goal?
  - key: faq.survey_goals_css.description
    t: >
      The survey's goal is to track the evolution of upcoming features and libraries,
      and help developers decide which new technologies to focus on.

  # CSS 2022

  - key: faq.learn_more_css2022
    t: Where can I learn more?
  - key: faq.learn_more_css2022.description
    t: You can learn more about [last year's survey here](https://2021.stateofcss.com/en-US/about/).

  - key: faq.survey_design_css2022
    t: How was this survey designed?
  - key: faq.survey_design_css2022.description
    t: This year, thanks to a grant from Google's [UI Fund](https://web.dev/ui-fund/), [Lea Verou](https://lea.verou.me/) was able to take the lead and managed the [open survey design process](https://github.com/orgs/Devographics/projects/1/views/1) on GitHub.

  - key: faq.results_released_css2022
    t: When will the results be released?
  - key: faq.results_released_css2022.description
    t: The survey will run until the end of October 2022, and the survey results will be released in early November.

  - key: faq.data_used_css2022
    t: How will this data be used?
  - key: faq.data_used_css2022.description
    t: All data collected will be released publicly. It will then become a resources both for developers, who consult it to inform their technological choices, and browser vendors, who use it to prioritize focus areas and inform their roadmaps.

  # CSS 2023

  - key: faq.how_long_will_survey_take_css2023
    t: How long will answering the survey take?
  - key: faq.how_long_will_survey_take_css2023.description
    t: >
      Depending on how many questions you answer (all questions can be skipped),
      filling out the survey should take around 10-15 minutes.

  - key: faq.learn_more_css2023
    t: Where can I learn more?
  - key: faq.learn_more_css2023.description
    t: You can learn more about this survey in [our announcement post](https://dev.to/sachagreif/the-2023-state-of-css-survey-is-now-open-18bk).

  - key: faq.survey_design_css2023
    t: How was this survey designed?
  - key: faq.survey_design_css2023.description
    t: >
      This year, thanks to a grant from Google's [UI Fund](https://web.dev/ui-fund/),
      [Chen Hui Jing](https://chenhuijing.com/) was able to help manage the survey's [open design process](https://github.com/Devographics/surveys/issues/84).

  - key: faq.results_released_css2023
    t: When will the results be released?
  - key: faq.results_released_css2023.description
    t: The survey will run until July 15, 2023, and the survey results will be released in the following weeks.

  # JS 2022

  - key: faq.learn_more_js2022
    t: Where can I learn more?
  - key: faq.learn_more_js2022.description
    t: You can learn more about [last year's survey here](https://2021.stateofjs.com/en-US/about/).

  # - key: faq.survey_design_js2022
  #   t: How was this survey designed?
  # - key: faq.survey_design_css2022.description
  #   t: This year, thanks to a grant from Google's [UI Fund](https://web.dev/ui-fund/), [Lea Verou](https://lea.verou.me/) was able to take the lead and managed the [open survey design process](https://github.com/orgs/Devographics/projects/1/views/1) on GitHub.

  - key: faq.results_released_js2022
    t: When will the results be released?
  - key: faq.results_released_js2022.description
    t: The survey will run until December 15, 2022, and the survey results will be released shortly afterwards.

  - key: faq.data_used_js2022
    t: How will this data be used?
  - key: faq.data_used_js2022.description
    t: All data collected will be released publicly. It will then become a resources both for developers, who consult it to inform their technological choices, and browser vendors, who use it to prioritize focus areas and inform their roadmaps.

  # HTML 2023

  - key: faq.data_used_html2023
    t: How will this data be used?
  - key: faq.data_used_html2023.description
    t: >
      All data collected will be released openly for any developer or company to consult.
      Browser vendors also [use this data](https://web.dev/interop-2023/) to prioritize focus areas and inform their roadmaps.

  - key: faq.survey_goals_html2023
    t: What are the survey's goals?
  - key: faq.survey_goals_html2023.description
    t: >
      The survey's goals are to measure awareness of new HTML features and browser APIs, and help developers keep track of how their usage is evolving.

  - key: faq.who_should_take_survey_html2023
    t: Who should take this survey?
  - key: faq.who_should_take_survey_html2023.description
    t: >
      This is an open survey for anybody who makes websites or web apps, whether regularly or occasionally, as part of their job, as a student, or just for fun!

  - key: faq.how_long_will_survey_take_html2023
    t: How long will answering the survey take?
  - key: faq.how_long_will_survey_take_html2023.description
    t: >
      Depending on how many questions you answer (all questions are optional),
      filling out the survey should take around 15-20 minutes.

  - key: faq.learn_more_html2023
    t: Where can I learn more?
  - key: faq.learn_more_html2023.description
    t: You can learn more about this survey in [our announcement post](https://lea.verou.me/blog/2023/design-state-of-html/).

  - key: faq.survey_design_html2023
    t: How was this survey designed?
  - key: faq.survey_design_html2023.description
    t: >
      The survey was designed by [Lea Verou](https://lea.verou.me), with input from browser vendors as well as groups such as the [WebDX Community Group](https://www.w3.org/community/webdx/).

  - key: faq.results_released_html2023
    t: When will the results be released?
  - key: faq.results_released_html2023.description
    t: The survey will run from September 19 to October 16, and the survey results will be released shortly after that.

  # React 2023

  - key: faq.data_used_react2023
    t: How will this data be used?
  - key: faq.data_used_react2023.description
    t: >
      All data collected will be released openly for anybody to consult. Developers or companies may use it to prioritize focus areas and inform their roadmaps.

  - key: faq.survey_goals_react2023
    t: What are the survey's goals?
  - key: faq.survey_goals_react2023.description
    t: >
      The survey's goals are to measure awareness and popularity of React APIs, as well as libraries in the React ecosystem.

  - key: faq.who_should_take_survey_react2023
    t: Who should take this survey?
  - key: faq.who_should_take_survey_react2023.description
    t: >
      This is an open survey for anybody who uses React, whether regularly or occasionally, as part of their job, as a student, or just for fun!

  - key: faq.how_long_will_survey_take_react2023
    t: How long will answering the survey take?
  - key: faq.how_long_will_survey_take_react2023.description
    t: >
      Depending on how many questions you answer (all questions are optional),
      filling out the survey should take around 15-20 minutes.

  - key: faq.learn_more_react2023
    t: Where can I learn more?
  - key: faq.learn_more_react2023.description
    t: You can learn more about this survey in [our announcement post](https://dev.to/sachagreif/announcing-the-first-ever-state-of-react-survey-3k6b).

  - key: faq.survey_design_react2023
    t: How was this survey designed?
  - key: faq.survey_design_react2023.description
    t: >
      The survey was designed with input from the community through an [open feedback thread](https://github.com/Devographics/surveys/issues/85).

  - key: faq.results_released_react2023
    t: When will the results be released?
  - key: faq.results_released_react2023.description
    t: The survey will run from October 27 to November 15, and the survey results will be released shortly after that.

  # JS 2023

  - key: general.js2023.survey_intro
    t: >
      JavaScriptはブラウザで動く言語として生まれ、その後Node.jsを使ってサーバでも活躍するようになりました。 


      2023年は、エコシステム全体がそのギャップを橋渡しするための準備を整えたようにみえます。React Server Componentsのような機能や、Solid、Qwikといったフレームワーク、またNext.jsやSveltekitといったメタフレームワークでは、クライアントに対してコードとデータをより良い手段で提供することが、JavaScriptの次なる大きな目標となっています。


      あるいはTypeScriptと言うべきでしょうか？この時点では、これら二つを切り離すのは難しくなってきています。


      何が新しいか、古いか、そして今後の数年で何が私たちを待ち受けているのかを知るためにアンケートにご参加ください！

  - key: faq.data_used_js2023
    t: 回答したデータはどのように使用されますか？
  - key: faq.data_used_js2023.description
    t: >
      集めたデータはすべて公開され、誰でも参照できるようになります。開発者や企業は、これを参考にして重点分野の優先順位付けをしたり、ロードマップを立てるために役立てることができます。

  - key: faq.survey_goals_js2023
    t: この調査の目的は何ですか？
  - key: faq.survey_goals_js2023.description
    t: >
      この調査の目的はJavaScriptの機能やライブラリの認知度や人気を測定し、今後のトレンドを予測することです。

  - key: faq.who_should_take_survey_js2023
    t: このアンケートの対象者は誰ですか？
  - key: faq.who_should_take_survey_js2023.description
    t: >
      このアンケートはJavaScript（または TypeScript）を、仕事として、学生として、あるいは単なる趣味として使っている人なら誰でも参加できるオープンなアンケートです！

  - key: faq.how_long_will_survey_take_js2023
    t: このアンケートの回答にはどのくらいの時間がかかりますか？
  - key: faq.how_long_will_survey_take_js2023.description
    t: >
      回答する質問の数によりますが、アンケートの所要時間は15〜20分程度です。（すべての質問は任意です）

  - key: faq.learn_more_js2023
    t: 調査についてもっと詳しく知りたいです！
  - key: faq.learn_more_js2023.description
    t: この調査についての詳細は「[The State of JS 2023 Survey is Now Open](https://dev.to/sachagreif/the-state-of-js-2023-survey-is-now-open-2hah)」をご覧ください！

  - key: faq.survey_design_js2023
    t: この調査の内容はどのように設計されていますか？
  - key: faq.survey_design_js2023.description
    t: この調査は「[State of JS 2023 Feedback](https://github.com/Devographics/surveys/issues/224)」を通して、コミュニティからの意見をもとに組み立てられました。

  - key: faq.results_released_js2023
    t: 結果はいつ公開されますか？
  - key: faq.results_released_js2023.description
    t: 調査期間は11月22日から12月12日までで、調査結果はその後まもなく公開される予定です。