Sacha Greif

Here's the first draft of the outline, currently it's basically just a copy of last year's outline: https://github.com/StateOfJS/StateOfJS-Vulcan/blob/master/packages/stateofjs/lib/surveys/yml/js2020outline.yml Do let me know what to add/remove this year! The main issue...

Other thoughts: - Add a new Graphics & Animation section for things like D3, three.js, etc.? - Should Build Tools have their own full section? - Add a new Utilities...

@justinfagnani those would be great to know about, but I think that might be going a bit too much into detail for us… And some of them can probably be...

Oh also there is no strict criteria for inclusion in the survey for libraries or frameworks, it's a mix of: - What got the most write-in votes in past surveys....

@lindsaykwardell in this case the main criteria would probably be freeform answers from past years, and since the Ladybug Podcast came in third (https://2019.stateofjs.com/resources/#podcasts_others) we can definitely include it :)

@lindsaykwardell you could check that the info in [this file](https://github.com/StateOfJS/state-of-js-graphql-results-api/blob/master/src/data/entities.yml#L1151) (which we use to get metadata about the items that appear in the survey) is correct, and then add the...

@lindsaykwardell Also I really wanted to say thanks for actually taking the time to make a proactive move to improve things, instead of just complaining on Twitter :)

@laurakalbag thanks so much for your feedback! > I think it’s important to consider whether you are asking these questions for demographic information, or for information about how people use...

> (I assume) what you want to know is how disability affects how somebody experiences the web, so the questions should focus on that. (WebAIM’s surveys cover this to some...

> cringe. What a phenomenally bad take. It was probably poorly worded, so let me elaborate. Obviously our goal is never to go out of our way to offend people,...