Skip to content

Commit 96ec76a

Browse files
author
Sacha Greif
committed
add strings
1 parent ff68248 commit 96ec76a

File tree

3 files changed

+45
-4
lines changed

3 files changed

+45
-4
lines changed

devs2025.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ translations:
6161
t: |
6262
15% of women participation might feel small, but it's at least considerably higher than [other surveys](https://2024.stateofjs.com/en-US/demographics/#gender), which tend to hover around 6%.
6363
64-
And while the data reveals a gender income gap, it could be due to a difference in median experience, since that gap is not present when looking at comparable experience levels.
64+
And while the data reveals a gender income gap, further research would be needed to conclude whether this is due to gender discrimination, or other correlated factors such as differences in experience levels.
6565
6666
- key: user_info.race_ethnicity.takeaway.devs2025
6767
t: |
@@ -187,9 +187,9 @@ translations:
187187
# t: |
188188
# xxx
189189

190-
# - key: technology.programming_languages.takeaway.devs2025
191-
# t: |
192-
# xxx
190+
- key: technology.programming_languages.takeaway.devs2025
191+
t: |
192+
While it might be tempting to learn Clojure, Elm, Ruby, or Scala given the income premium these languages seem to carry, it's important to also acknowledge that these language tend to be practiced by more experienced devs, which could account for the difference.
193193
194194
- key: technology.productivity_apps.takeaway.devs2025
195195
t: |

html2025.yml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,14 @@ locale: en-US
22
translations:
33
- key: foo
44
t: bar
5+
6+
- key: faq.survey_design_html2025
7+
t: How was this survey designed?
8+
- key: faq.survey_design_html2025.description
9+
t: >
10+
This survey was designed as the results of an [open design process](https://github.com/Devographics/surveys/issues/253) involving browser vendors and the web development community.
11+
12+
- key: faq.results_released_html2025
13+
t: When will the results be released?
14+
- key: faq.results_released_html2025.description
15+
t: The survey will run from July 15 to August 15, 2025, and the survey results will be released around September 15, 2025.

state_of_html.yml

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1056,3 +1056,33 @@ translations:
10561056
aliasFor: sections.accessibility.title
10571057
- key: features.mobile_web_apps
10581058
aliasFor: sections.mobile_web_apps.title
1059+
1060+
###########################################################################
1061+
# FAQ
1062+
###########################################################################
1063+
1064+
- key: faq.how_long_will_survey_take_html
1065+
t: How long will answering the survey take?
1066+
- key: faq.how_long_will_survey_take_html.description
1067+
t: >
1068+
Depending on how many questions you answer (all questions can be skipped),
1069+
filling out the survey should take around 10-15 minutes.
1070+
1071+
- key: faq.who_should_take_survey_html
1072+
t: Who should take this survey?
1073+
- key: faq.who_should_take_survey_html.description
1074+
t: >
1075+
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!
1076+
1077+
- key: faq.data_used_html
1078+
t: How will this data be used?
1079+
- key: faq.data_used_html.description
1080+
t: >
1081+
All data collected will be released openly for any developer or company to consult.
1082+
Browser vendors also [use this data](https://web.dev/blog/interop-2024) to prioritize focus areas and inform their roadmaps.
1083+
1084+
- key: faq.survey_goals_html
1085+
t: What are the survey's goals?
1086+
- key: faq.survey_goals_html.description
1087+
t: >
1088+
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.

0 commit comments

Comments
 (0)