diff --git a/state_of_js.yml b/state_of_js.yml
index ad3b215746a..c04294e35b4 100644
--- a/state_of_js.yml
+++ b/state_of_js.yml
@@ -246,6 +246,21 @@ translations:
   - key: options.top_js_pain_points.date_management.description
     aliasFor: options.js_pain_points.date_management.description
 
+  - key: options.top_js_pain_points.performance
+    t: Performance
+  - key: options.top_js_pain_points.performance.description
+    t: Writing performant and efficient JavaScript code
+
+  - key: options.top_js_pain_points.build_tools
+    t: Build Tools
+  - key: options.top_js_pain_points.build_tools.description
+    t: Managing tooling to bundle your code
+
+  - key: options.top_js_pain_points.typing
+    t: Typing
+  - key: options.top_js_pain_points.typing.description
+    t: Managing and maintaining types
+
   - key: options.top_js_pain_points.build_tools
     t: Build Tools
   - key: options.top_js_pain_points.typing
diff --git a/surveys.yml b/surveys.yml
index 8a1a57b5a43..b93b9b3c8a6 100644
--- a/surveys.yml
+++ b/surveys.yml
@@ -600,3 +600,51 @@ translations:
 
   - 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, join us to 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-1cmh).
+
+  - 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.