This repository was archived by the owner on Dec 9, 2024. It is now read-only.
forked from Devographics/locale-en-US
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsurveys.yml
244 lines (199 loc) · 11.6 KB
/
surveys.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
locale: en-US
translations:
###########################################################################
# General
###########################################################################
- 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
###########################################################################
# Errors
###########################################################################
- key: error.duplicate_response
t: Sorry, you already have a session in progress for this survey.
###########################################################################
# 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 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
###########################################################################
- 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 ([email protected]) 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 mandatory?
- 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: The data will be made public in a form of readable charts and graphs. We will not publish any identifiable information.
- key: faq.survey_design
t: How was this survey designed?
- key: faq.survey_design.description
t: The survey was designed based on our expertise and the community feedback gathered on [this GitHub discussion](https://github.com/software-mansion/state-of-react-native/discussions/6).
- key: faq.results_released
t: When will the results be made available?
- key: faq.results_released.description
t: The results are going to be 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 [Software Mansion](http://swmansion.com). We are a software development company based in Poland, with a strong focus on React Native app development and multimedia streaming.
- key: faq.swm_devographics
t: This survey looks very familiar!
- key: faq.swm_devographics.description
t: It's because it's using the same infrastructure as [State of JavaScript](https://stateofjs.com) and [State of CSS](https://stateofcss.com) surveys made by [Devographics](https://devographics.com).
###########################################################################
# 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 picked “{response}”. Tell us more about your choice:"
- 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.
- key: response.view_results
t: View Results
###########################################################################
# 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.
###########################################################################
# Survey-Specific FAQs
###########################################################################
# 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.
# 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.