This project tracks organize developer signals (interest, needs, wants, frustrations) around web platform features. The work is done within the W3C WebDX Community Group.
Signals is defined broadly to allow for any available data about web developers to be considered, and typically fall into one of these categories:
- Survey results, for example from State of CSS or MDN short surveys
- Developer interviews, such as those done for the MDN Browser Compatibility Report 2020
- Browser bugs, including upvote/star counts
- Reactions on GitHub issues relating to web platform features
- Blogs, podcasts, or social media
To the extent possible, signals will be organized around web-features.
This project is only about organizing signals, not about conducting or coordinating research. For that, see the WebDX research workstream.
A discussion on organizing developer signals around features led to the creation of this project, see that discussion for more background.
This work is exploratory and will be shaped by what we learn through experimentation. If you'd like to contribute, please file issues or send pull requests, and consider joining the W3C WebDX Community Group!
All participants are expected to follow the project's Code of Conduct.