surveys.yml

locale: ko-KR
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: Global
  - 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: Pick up to {limit} items.

  - 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: No browser implementation yet

  - key: general.skip_question
    t: Skip

  - key: general.unskip_question
    t: Answer Question

  - key: general.skip_question.description
    t: Skip question and mark it as completed

  - key: general.unskip_question.description
    t: Unskip question and answer it

  - key: years.less_than_one_year
    t: Less than one year

  - key: years.years
    t: years

  - key: likert.option.0
    t: Very Unhappy
  - key: likert.option.1
    t: Unhappy
  - key: likert.option.2
    t: Neutral
  - key: likert.option.3
    t: Happy
  - key: likert.option.4
    t: Very Happy

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

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

  - key: error.duplicate_response
    t: Sorry, you already have a session in progress for this survey.

  - key: error.report_issue
    t: Report issue

  - key: success.data_saved
    t: Data Saved
  - key: success.data_saved.description
    t: Your data has been saved.

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

  - key: accounts.create_account
    t: Continue with 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.upgrade_account.action
    t: Upgrade your account
  - key: accounts.upgrade_account.description
    t: Upgrading your account with an email address will let you access your survey response after you end your session.

  - 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 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.
    # 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: 예, 모든 데이터는 공개적으로 공개되지만 개인 정보(이메일, 사용자 아이디, 사용자 이름 등)가 제거된 후에만 공개됩니다.
  - 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: 이 설문 조사는 [Devographics](http://devographics.com/)가 Contributor(기여자), 번역가, 그리고 자원봉사자들과 함께 주최합니다.

  ###########################################################################
  # 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

  - 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}% 완료"

  - key: response.details
    t: "{startedAt} 시작, {completion}% 완료."

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

  - key: readinglist.prompt
    t: >
      You picked “{option}”. If you'd like to learn more about this feature at the end of the survey, you can click the "+" icon above to add it to your **reading list**.

  - key: readinglist.add_to_list
    t: Add to Your Reading List

  - key: readinglist.remove_from_list
    t: Remove from Reading List

  - key: readinglist.added_to_list
    t: Added “{label}” to your reading list.

  - key: readinglist.title
    t: 읽을 거리

  - key: readinglist.description
    t: >
      "+" 버튼을 사용해 아이템을 이 곳에 저장하면 설문이 끝난 후에 관련된 링크 목록을 받을 수 있습니다.

  - key: readinglist.empty
    t: >
      You don't have any items in your reading list.
      Try going back to the survey and adding features or libraries you'd like
      to learn more about using the "+" button.

  - key: readinglist.results
    t: >
      Here are some resources to learn more about the items in your reading list:

  - key: readinglist.homepage_link
    t: Homepage

  - key: readinglist.receive_copy
    t: >
      Enter your email to get a copy of your reading list straight in your inbox:
  - key: readinglist.send_by_email
    t: Send
  - key: readinglist.email_sent
    t: Thanks! Your reading list is on its way to your inbox.

  ###########################################################################
  # 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: |
      React가 처음 등장할 당시, 웹 개발 분야에 큰 변화가 올 것이 확실했습니다.

      어쨌든 React는 Facebook을 개발할 때 사용되었고, "JSX"라는 조금 이상한 개념의 도입에도 불구하고 개발자들은 빠르게 React를 도입했습니다. 무엇보다 인상깊은 것은 함수 컴포넌트와 Hooks 같은 주요 변화가 일어났음에도 커뮤니티가 이를 버티고 따라갔다는 것입니다.

      하지만 이제 10년이 흘렀고, 최근에 소개된 React 서버 컴포넌트는 아마 React의 등장 이후 생기는 가장 큰 변화가 될 것으로 보입니다.

      이번에도 커뮤니티는 이 변화를 따라갈 수 있을까요? 아니면 개발자들이 Svelte, Solid나 다른 기술로 넘어가게 될까요?

      사상 최초의 State of React 설문조사를 통해 함께 알아봅시다!

  ###########################################################################
  # 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.

  # JS 2023 
  - key: general.js2023.survey_intro
    t: >
      JavaScript는 브라우저 언어로 시작해서 Node.js와 함께 서버 언어로 까지 나아가고 있습니다.

      그리고 2023년에는 이 전체 생태계가 브라우저와 서버간의 차이를 줄이려는 시도를 할 준비가 된 것 같습니다. 
      React Server Components와 같은 기능, Solid와 Qwik와 같은 프레임워크, 그리고 Next.js와 Sveltekit 같은 메타 프레임워크를 통해, 클라이언트들에게 코드와 데이터를 더 좋은 방식으로 제공하는 것이 JavaScript의 새로운 큰 목표가 되었습니다.
      
      아니면 TypeScript라고 해야 할까요? 이제는 두 언어를 구분하기 어려워졌으니, 구분하지 않는 것이 좋을 것 같습니다.

      대신, 설문조사에 참여해서 무엇이 새롭고, 무엇이 오래되었으며, 그리고 앞으로 몇 년간 어떤 async/awaits가 우리를 기다리고 있는지 알려주시기 바랍니다!

  - key: faq.how_long_will_survey_take_js2023
    t: 설문 조사에 응답하는데 얼마나 시간이 걸릴까요?
  - key: faq.how_long_will_survey_take_js2023.description
    t: 응답하시는 질문의 수에 따라 다르겠지만(모든 질문은 선택 사항입니다), 설문 조사는 대략 15~20분 정도 소요될 것 같습니다.

  - key: faq.who_should_take_survey_js2023
    t: 이 설문 조사는 누가 참여해야 하나요?
  - key: faq.who_should_take_survey_js2023.description
    t: 이 설문 조사는 직업으로, 학습 목적으로, 또는 취미로 JavaScript(혹은 Typescript)를 정기적이거나 가끔 사용하는 모든 사람을 대상으로한 공개 설문입니다!

  - key: faq.survey_goals_js2023
    t: 설문 조사의 목표는 무엇인가요?
  - key: faq.survey_goals_js2023.description
    t: 이 설문 조사의 목표는 JavaScript 기능과 라이브러리의 인지도와 인기를 측정하여 미래의 트렌드를 예측하는 것입니다.
  
  - key: faq.data_used_js2023
    t: 이 데이터는 어떻게 사용되나요?
  - key: faq.data_used_js2023.description
    t: 수집된 모든 데이터는 누구나 참고할 수 있도록 공개적으로 발표될 것입니다. 개발자나 회사들은 이것을 이용해서 중점적으로 다뤄야할 분야를 결정하거나 로드맵을 수립하는데 사용할 수 있습니다.

  - key: faq.results_released_js2023
    t: 결과는 언제 발표되나요?
  - key: faq.results_released_js2023.description
    t: 설문 조사는 11월 22일부터 12월 12일까지 진행되며, 그 이후 곧바로 결과가 발표될 예정입니다.

  - key: faq.team
    t: 이 설문 조사는 누가 주최하나요?
  - key: faq.team.description
    t: 이 설문 조사는 [Devographics](http://devographics.com/)가 Contributor(기여자), 번역가, 그리고 자원봉사자들과 함께 주최합니다.

  - key: faq.survey_design_js2023
    t: 이 설문 조사는 어떻게 설계되었나요?
  - key: faq.survey_design_js2023.description
    t: 이 설문 조사는 커뮤니티의 의견을 수렴하여 [공개 피드백 스레드](https://github.com/Devographics/surveys/issues/224)를 통해 설계되었습니다.

  - key: faq.learn_more_js2023
    t: 더 자세한 정보는 어디서 얻을 수 있나요?
  - key: faq.learn_more_js2023.description
    t: 이 설문 조사에 대한 자세한 정보는 [저희 공지 게시물](https://dev.to/sachagreif/the-state-of-js-2023-survey-is-now-open-2hah)에서 확인하실 수 있습니다.
  

  # 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: 데이터는 어떻게 사용될 예정인가요?
  - key: faq.data_used_react2023.description
    t: >
      수집된 모든 데이터는 누구나 확인할 수 있도록 공개될 것입니다.
      개발자나 기업은 이 데이터를 바탕으로 우선순위나 로드맵을 계획할 때 사용할 수도 있습니다.

  - key: faq.survey_goals_react2023
    t: 설문의 목표는 무엇인가요?
  - key: faq.survey_goals_react2023.description
    t: 리액트 API 및 리액트 생태계의 라이브러리에 대한 인식과 인기를 측정하는 것입니다.

  - key: faq.who_should_take_survey_react2023
    t: 이 설문의 대상은 누구인가요?
  - key: faq.who_should_take_survey_react2023.description
    t: >
      리액트를 사용하는 모든 사람이 대상입니다. 가끔 사용하던지, 많이 사용하던지, 직장에서 사용하던지, 교에서 사용하던지, 재미로 사용던지 상관없이 누구나 참여 가능합니다!

  - key: faq.how_long_will_survey_take_react2023
    t: 설문조사는 얼마나 걸리나요?
  - key: faq.how_long_will_survey_take_react2023.description
    t: >
      질문에 얼마나 답변하느냐에 따라(모든 질문은 선택 사항입니다),
      보통 15-20분이 소요될 것으로 예상됩니다.

  - key: faq.learn_more_react2023
    t: 관련 정보는 어디에서 더 찾아 볼 수 있나요?
  - key: faq.learn_more_react2023.description
    t: 자세한 내용은 [해당 공식 문서](https://dev.to/sachagreif/announcing-the-first-ever-state-of-react-survey-3k6b)에서 더 확인할 수 있습니다.

  - key: faq.survey_design_react2023
    t: 이 설문은 어떻게 설계되었나요?
  - key: faq.survey_design_react2023.description
    t: 이 설문은 커뮤니티의 [공개 피드백](https://github.com/Devographics/surveys/issues/85)을 통해 설계되었습니다.

  - key: faq.results_released_react2023
    t: 결과는 언제 발표되나요?
  - key: faq.results_released_react2023.description
    t: 이 설문은 10월 27일부터 11월 15일까지 진행되며, 결과는 그 이후 빠른 시일 내에 발표될 예정입니다.