WordPress has launched its 2023 annual survey, which is open to the entire community, including users, site builders, plugin and theme authors, and contributors.
The 2022 survey collected responses from roughly 3,400 people, including approximately 800 contributors, a decline in submissions from previous years. The 2022 survey introduced the Likert scale, a rating scale that quantitatively assesses opinions, attitudes, or behaviors. The total number of questions were reduced, with socio-economic questions mostly removed.
WordPress is still evolving the survey format to get a better understanding of the community’s sentiments and values.
“This year, like last year, the survey has undergone some improvements to the flow and question set,” Automattic-sponsored contributor Dan Soschin said. “A new platform is also being piloted, offering an updated interface, enhanced multi-lingual support, expanded analysis and visualization tools for the results, and more. The new platform also has built-in accessibility and privacy controls, ensuring the survey meets the diverse needs of the WordPress community.”
The 2023 survey takes approximately 5-10 minutes to complete. It collects information on some basic demographics, various community involvements, preferred WordPress editor, how and why you are using WordPress, and more. Several questions allow the community to weigh in on the most frustrating aspects of WordPress, areas that need more attention, and whether or not the current WordPress roadmap reflects respondents’ needs and desires for the future of the project.
In addition to English, the survey is available in nine widely-used languages, which participants can select from a drop-down menu at the top of the page. All the data collected in the survey will be anonymized and WordPress does not associate IP addresses or email addresses with the results.
The survey was frustrating and synptomatic of what is wrong with WordPress atm.
I’ve worked at the bottom end of market research and the rate things on a scale questions are useless. They depend hugely on the framing of the question, previous questions or the interviewer (if there is one). And in many cases they miss the real problems entirely
In this case I’d have liked to express disatisfaction with the current development priorities in core. It’s mad the features being developed for Gutenberg that most don’t want and the huge number of apis and bugs not being addressed
There was nowhere to express this opinion directly in the survey. And I know many others think similarly