surveys.yml

locale: en-US
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: No surveys to preview
  - 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.

  - key: general.numeric_input.unit.years
    t: years
  - key: general.numeric_input.unit.years_old
    t: years old
  - key: general.numeric_input.unit.hours
    t: hours

  ###########################################################################
  # 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: 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 this survey?
  - key: faq.team.description
    t: This survey is run by [Devographics](http://devographics.com) together with a collective of 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

  - 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:"

  - key: user_info.gender.snowball_sampling
    t: >
      ### Help us share this survey with more women!


      We are hoping to increase women participation this year, and one approach we're trying (known as “[snowball sampling](https://github.com/Devographics/surveys/issues/258)”) is asking women respondents such as yourself to share the link to this survey with other women developers.


      If you're able to help with this, here is a special share link you can use so we can track the success of this initiative:

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

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

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

  ###########################################################################
  # 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 in the corner 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: Reading List

  - key: readinglist.description
    t: >
      Save items here using the "+" button, and you'll get a list of links to learn more about them at the end of the survey.

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

  # JS 2023

  - key: general.js2023.survey_intro
    t: >
      JavaScript started its life as a browser language, and then went to on conquer the server with Node.js. 


      And it 2023, it seems like the ecosystem as a whole might finally be ready to try and bridge that gap. Between features like React Server Components, frameworks like Solid and Qwik, or meta-frameworks like Next.js and Sveltekit, providing a better way of serving code and data to clients has become JavaScript's next big goal. 


      Or should we say TypeScript? At this point it's become hard to disentangle the two, so let's not even try. 


      Instead, take the survey and help us figure out what's new, what's old, and what async/awaits us in the years to come!

  - key: faq.data_used_js2023
    t: How will this data be used?
  - key: faq.data_used_js2023.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_js2023
    t: What are the survey's goals?
  - key: faq.survey_goals_js2023.description
    t: >
      The survey's goals are to measure awareness and popularity of JavaScript features and libraries in order to anticipate future trends.

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

  - key: faq.how_long_will_survey_take_js2023
    t: How long will answering the survey take?
  - key: faq.how_long_will_survey_take_js2023.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_js2023
    t: Where can I learn more?
  - key: faq.learn_more_js2023.description
    t: You can learn more about this survey in [our announcement post](https://dev.to/sachagreif/the-state-of-js-2023-survey-is-now-open-2hah).

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

  - key: faq.results_released_js2023
    t: When will the results be released?
  - key: faq.results_released_js2023.description
    t: The survey will run from November 22 to December 12, and the survey results will be released shortly after that.