The WordPress Developer Survey #265
Replies: 5 comments
This comment was marked as spam.
This comment was marked as spam.
-
Next steps:
|
Beta Was this translation helpful? Give feedback.
-
What is the purpose of this survey? What is the survey trying to gather/learn/understand?The purpose of this survey is to understand the current state of the WordPress extender community (a.k.a. WordPress developers). These are the users of WordPress who build on top of WordPress every day, customizing WordPress core, plugins, and themes and building custom themes and plugins, either for their employers or for their customers. The survey would be modeled after the Stack Overflow Developer Survey What would a reader of the survey results gain from reading the results?The WordPress project currently has three major platforms to speak directly to developers:
Contributors to these platforms can use the results of this yearly survey to make better-informed decisions about new content that needs to be added (or perhaps updated) on these platforms to better serve the needs of the WordPress developer community. Community members who read the results of this survey could use them to gauge where they fit into the extender community and learn about new and interesting tools, online learning resources, and developer communities to consider joining. It would also help promote WordPress developer-related content outside of the developer blog. What questions/topics would be included in the survey? What questions would not be included?While not an extensive list, examples of topics could include things like:
Additional questions about the specific developer platforms could include things like:
|
Beta Was this translation helpful? Give feedback.
-
@jonathanbossenger Thank you so much for additional thoughts on the Developer survey. During last month's meeting, there was also a concern that a survey like this would need some cross-team collaboration and buy-in from project leadership as running of the survey would also require additional resources, for translation and analysis. An example the question: "What development tools do you use daily?" "Are you a solo developer or working in a team? Freelance or employed?" The question: "What developer conferences do you go to?" seems a promising one. |
Beta Was this translation helpful? Give feedback.
-
After various discussions, it looks like surveys are less and less beneficial, so I'm marking this as closed so we can consider other ways to source this information. |
Beta Was this translation helpful? Give feedback.
-
About a year ago I published a small survey of WordPress development tools on my personal blog: https://jonathanbossenger.com/2023/07/the-state-of-wordpress-developer-tools-survey-results/
I was thinking that this is something we could expand on, and use to survey all WordPress developers each year. This would help give us insights on various things like developer tooling, WordPress API experience, and knowledge of planned developer features.
This could be similar to the Stack Overflow Developer Survey, but with a very specific focus on WordPress developers.
My suggestion is that we publish a post each year around June/July to survey all WordPress developers, and then report on the results around August/September of that year.
Beta Was this translation helpful? Give feedback.
All reactions