Sacha Greif
Sacha Greif
**(Updated August 17, 2021)** We are getting ready to hold the **2021 edition** of the annual [State of CSS survey](https://stateofcss.com/) (see the [2020 edition here](https://2020.stateofcss.com/)). Please use this issue thread...
Here is the YAML file containing the outline of the 2020 State of CSS survey: https://github.com/StateOfJS/StateOfJS-Vulcan/blob/2020/packages/stateofjs/lib/surveys/yml/css2020outline.yml It's currently more or less a copy of the [2019 version of the survey](https://2019.stateofcss.com/)...
Ideally all homepages (State of JS and State of CSS) would be managed through the same codebase, using an env variable to switch between site variants.
Just like the survey and survey results, it would be great if the homepage supported multiple languages.
Currently the data (surveys, translators, etc.) is all hardcoded. It would be better to pull it in at build time from the existing [State of JS API](https://api.stateofjs.com/graphql).
It would be nice to migrate this codebase to [Astro](https://astro.build/) instead of Gatsby, since it's a way simpler setup.
One of the main goals for this next round of the State of JS survey is to learn more not just about JS language features usage (destructuring, proxies, etc.) but...
See #113 to discuss APIs, otherwise use this thread for other feedback.
First let me say this library has been super helpful, it does one thing well and was very easy to add to my charts. The only thing I've noticed is...