Title: survey – Make WordPress Core --- # Tag Archives: survey [ ](https://profiles.wordpress.org/mapk/) [Mark Uraine](https://profiles.wordpress.org/mapk/) 5:04 pm _on_ April 7, 2017 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), survey    # 󠀁[Editor Experience Survey Results](https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/)󠁿 The Editor Experience Survey results are in! There were a total of **2,563 responses** which were gathered anonymously through PollDaddy. There was a big focus on asking multiple choice questions to keep the survey manageable. I tried to provide images where relevant and ask actionable questions as I could. Thanks to: [@iseulde](https://profiles.wordpress.org/iseulde/), [@karmatosed](https://profiles.wordpress.org/karmatosed/), [@melchoyce](https://profiles.wordpress.org/melchoyce/), [@joen](https://profiles.wordpress.org/joen/),@ designsimply, @azaozz, [@chanthaboune](https://profiles.wordpress.org/chanthaboune/), [@samuelsidler](https://profiles.wordpress.org/samuelsidler/), [@codebykat](https://profiles.wordpress.org/codebykat/) and many more for helping me organize this survey. Let’s jump in. ### How do you use WordPress? This question was pulled from the annual WordPress survey which helped reveal the backgrounds of the respondents. I was hoping for a more diverse group from a variety of backgrounds using WordPress, but this sampling should provide decent insight. Keep in mind that respondents were allowed to answer more than one. Developers clearly dominated the survey. Because of this, I wanted to break this stat down a bit more. This chart displays each categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. outside of “Developer”. The blue represents the amount of respondents that selected that category, but did not select “Developer”. The red represents the amount of respondents that chose “Developer” plus that category. The total respondents that selected “As a Developer” in this survey was 1,703 out of 2,563 total responses. [[ ### How often do you use the Editor? This questions was written in an effort to make sure the results were from respondents that _used_ the Editor. As can be seen, 89% use the Editor weekly or more. [[ ### Do you use the markup text Editor? Is the Text Editor an important part of people’s workflow while using WordPress? It was interesting to see that over 85% of respondents use the Text Editor _sometimes_ or more. [[ > “Only one wish: please don’t remove the plain text/mark-up editor.”   > “I’m a huge fan of the text editor. I like the ability to use raw htmlHTML HyperText > Markup Language. The semantic scripting language primarily used for outputting > content in web browsers. when necessary.”   > “Would really appreciate syntax highlighting in text view.”   ### Do you use the markup buttons? While a vast majority of respondents use the Text Editor, almost half never use the markup buttons. [[ ### Do you use the distraction free writing mode? The distraction-free writing mode seems to be often overlooked or just ignored in the respondent’s flow when using the Editor. Could it be that the button to initiate the distraction-free writing mode is a _distraction_ itself? [[ > “I love the distraction-free writing option but wish it offered a wider column > for editing purposes and easy size-adjusting for easier reading/editing.”   > “I like distraction free mode when I remember it’s there. Would be cool if choosing > to edit a post/page from the front end invoked something like distraction free > mode as a modal overlaying the page, allowing for quick editing and committing.”   > “[Would like] better Distraction Free (not just hiding surrounding menus, but > expanding the actual text area)”   > “I like the distraction free mode a lot. It makes it easier to write directly > in the editor in a clutter-free way.”   > “‘Distraction free’ is depressing due to the large gray area and limited writing > space for desktop.”   > “Distractions free mode is an utter joke.”   > “Would like to see a full screen version. Distraction free just removes the menus, > full screen would allow the menus on top and bottom but still give the complete > screen width.”   > “I wish the distraction free mode was how it used to be with bigger fonts and > centered.”   ### Installing plugins that added features to the Editor Exploring these questions might help reveal which features respondents are looking for in the Editor itself. The majority answered that they had installed plugins to add features. The most common features are graphed below. [[ [[ ### Current Editor ease-of-use and organization On a scale of 1 to 5 (5 being Very Easy or Very Organized), the majority of respondents found the current Editor’s ease-of-use and organization to be sufficient or better. [](https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/ease-of-use/#main) [](https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/editor-orgaization/#main) ### Editor AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) 105 respondents use a screen reader. 94 of those people feel the screen reader experience is sufficient or better. Other assistive technologies used by the respondents include: On-screen keyboards, alternative input devices like wands & sticks, voice recognition programs, screen enlargers, text to speech synthesizers, and braille embossers. [](https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/screen-reader/#main) [](https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/screen-reader-experience/#main) [](https://make.wordpress.org/core/2017/04/07/editor-experience-survey-results/assisstive-tech/#main)   Some quotes from the survey question about accessibility issues with the Editor: > “You need to add more notifications for screen reader when somethings change on > the page.”   > “I reached and pressed the Publish button and forgot that there are metaMeta Meta > is a term that refers to the inside workings of a group. For us, this is the team > that works on internal WordPress sites like WordCamp Central and Make WordPress. > boxes after that. So then I had to fill up the category and tags then shift + > tab to go back to Update the post.” ### Is there anything in the Editor you never use? I was hoping to discern some of the less used items in the Editor. This question is not intended to provide for support for eliminating any elements within the Editor, but rather to help with visual hierarchy in the new Editor. By far, the main element never used was the “Text color” dropdown, followed closely by the “Special character” button, the “Insert Read More tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)” button, and the “Distraction-free writing mode” button. [[ ### Is there anything else about the Editor you’d like to share? The last question yielded 37 answers. I’ve pulled a few interesting ones below.   > “Please make the editor to seems as an a4 paper it is best for authors :)”   > “Add a no follow option in the link editor.”   > “I’d like to see the bullet points/numbers to go along with the text if I increased > or decreased indentation.”   > “Would be way better if you could edit directly on the site instead of having > to open the dashboard and find the content somewhere there.”   > “Better implementation of shortcodes would be a real benefit.”   > “I would like that to see an easier way to bring the cite tag to the editor to > use with blockquote.”   > “Wish there was better support for content columns.”   > “I would love much better WordPress support for writing in various apps and then > posting to WordPress. […] In particular I’d like to see it in a lot more text > editors / note taking apps, […]. Writing in a web page in a browser is never going > to be comfortable, or at least never as comfortable as a “native” experience, > so I recommend focusing on letting people use the native experiences with which > they’re most comfortable.”   ### Conclusion The Editor Team is working hard on redesigning the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor experience to be something WordPress users could enjoy using daily. If you feel anything important was not represented in this survey, please comment below. If you have any feedback regarding the results or future work on the Editor, please feel free to comment as well. I look forward to the improved Editor experience in Core!       [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#survey](https://make.wordpress.org/core/tag/survey/) [ ](https://profiles.wordpress.org/mapk/) [Mark Uraine](https://profiles.wordpress.org/mapk/) 8:13 pm _on_ March 15, 2017 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [design ( 27 )](https://make.wordpress.org/core/tag/design/), survey    # 󠀁[Editor Experience Survey](https://make.wordpress.org/core/2017/03/15/editor-experience-survey/)󠁿 As you’re well aware, a project is underway with the focus on [redesigning the editing experience](https://make.wordpress.org/design/2017/01/11/what-makes-a-great-editor/) in the wp-adminadmin (and super admin). As the project moves forward, a better understanding of how WordPress users actually feel about the editing experience is needed. Please take a few minutes to fill out this survey and help influence the future of your favorite CMS, WordPress. **Survey Link:** [http://wordpressdotorg.polldaddy.com/s/editor-survey](http://wordpressdotorg.polldaddy.com/s/editor-survey) +make.wordpress.org/design   [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#design](https://make.wordpress.org/core/tag/design/), [#survey](https://make.wordpress.org/core/tag/survey/) [ ](https://profiles.wordpress.org/shaunandrews/) [shaunandrews](https://profiles.wordpress.org/shaunandrews/) 3:32 pm _on_ August 14, 2013 Tags: [3.8 ( 31 )](https://make.wordpress.org/core/tag/3-8/), survey, [widgets ( 26 )](https://make.wordpress.org/core/tag/widgets/)    # 󠀁[Howdy everyone There’s been a lot of discussion…](https://make.wordpress.org/core/2013/08/14/howdy-everyone-theres-been-a-lot-of-discussion/)󠁿 Howdy everyone! There’s been a lot of discussion over the last week or two around widgets for 3.8. Inspired by [@lessbloat](https://profiles.wordpress.org/lessbloat/), I’ve made a short survey with a few basic questions about widgets and how you use them. It you could, please take a few minutes to share your thoughts: [Take the Widgets Survey](http://shaunwp.polldaddy.com/s/working-with-widgets) Thanks! [#3-8](https://make.wordpress.org/core/tag/3-8/), [#survey](https://make.wordpress.org/core/tag/survey/), [#widgets](https://make.wordpress.org/core/tag/widgets/) [ ](https://profiles.wordpress.org/lessbloat/) [Dave Martin (lessbloat)](https://profiles.wordpress.org/lessbloat/) 1:09 pm _on_ August 13, 2013 Tags: [3.8 ( 31 )](https://make.wordpress.org/core/tag/3-8/), [dashboard ( 5 )](https://make.wordpress.org/core/tag/dashboard/), survey    # 󠀁[I’m doing some quick research into the wp…](https://make.wordpress.org/core/2013/08/13/im-doing-some-quick-research-into-the-wp/)󠁿 I’m doing some quick research into the wp-adminadmin (and super admin) dashboard( which I plan to look at for 3.8). I’d like to learn more about how you use the dashboard, and how you think it could be better. Please take a few moments and fill out this 5 question survey: [Take the survey](http://wp-survey.polldaddy.com/s/wp-dashboard-questionnaire) Thanks so much for your help! [#3-8](https://make.wordpress.org/core/tag/3-8/), [#dashboard](https://make.wordpress.org/core/tag/dashboard/), [#survey](https://make.wordpress.org/core/tag/survey/) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 5:55 pm _on_ April 26, 2012 Tags: [collaboration ( 4 )](https://make.wordpress.org/core/tag/collaboration/), survey, [team reps ( 21 )](https://make.wordpress.org/core/tag/team-reps/)    # 󠀁[Team Reps](https://make.wordpress.org/core/2012/04/26/team-reps/)󠁿 A few weeks ago I put up a survey for each of the contributor teams, with the goal of identifying a rep (or reps) for each contributing group. In most cases I lined up a primary rep and a backup. For core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org) it was a little different, because we have sub-groups within our group (which is also about 5 times larger than the next biggest contributor group, the theme reviewers). In the survey for core contributors, I asked how many reps you thought coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. should get to ensure that each core contrib constituency would be represented. Choices ranged from 2 to 4, in varying configurations. There was no overwhelming winner for this question. There were many votes for 4, 3, and 2, though some configurations had more votes than others. I removed the votes from people who have not actually contributed to core, but it was still a pretty even split. That said, across each of the configurations, the same people tending to be chosen for the 1 and 2 spots. **Based on the votes, I propose that the core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. group be made up of Mark Jaquith, Andrew Nacin, Aaron Campbell, and Helen Hou-Sandi, with their backups being Ryan Boren, Daryl Koopersmith, Cristi Burca (scribu), and Mike Schroder (DH-Shredder) respectively.** The primary responsibility of being a rep will be participating in a monthly chat with other contributor group reps starting in May, and communicating things between that group and this one. Backup reps can attend the chat if they wish but are not obligated to do so, unless the primary rep says they can’t make it. Since the core team will have multiple reps, we can work out details later like who’ll post what where and how to get feedback from the people they’re meant to represent. Thanks to everyone who participated! [#collaboration](https://make.wordpress.org/core/tag/collaboration/), [#survey](https://make.wordpress.org/core/tag/survey/), [#team-reps](https://make.wordpress.org/core/tag/team-reps/) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 7:45 pm _on_ April 5, 2012 Tags: [contributors ( 7 )](https://make.wordpress.org/core/tag/contributors/), survey    # 󠀁[Organizing Our Contributor Groups](https://make.wordpress.org/core/2012/04/05/organizing-our-contributor-groups/)󠁿 Hi there, core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org)( and those who follow them). One of the things I’ve been meaning to do in the contributor community for the last 3-4 years is organize it so that when we say “contributor” it doesn’t just mean coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. code and the different contributing groups can all be on the same page. You may have seen some surveys sent/posted to the forums/docs/theme review teams etc. Your turn! In order to create a closer relationship between all the contributor groups, ensure our policies and agendas don’t conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered _stale_, and will require a _refresh_ of the changes before it can be applied, or the conflicts will need to be _resolved_., recognize outstanding contributors, and just generally level up, we need some organization. To wit: * I’d like to identify who the active contributors are in each group. * I’d like to appoint someone from each group (based on votes from the active group participants) as a group liaison to the rest of the WP project and any cross- team initiatives to improve communication. * I’d like to set up a central P2P2 A [free theme for WordPress](http://p2theme.com/), known for front-end posting, used by WordPress for development updates and project management. See our [main development blog](https://make.wordpress.org/core/) and [other workgroup blogs](https://make.wordpress.org/). for communicating project- wide things so that no contributor group ever has to hear important announcements after the fact and we can discuss any issues that come up that could use the help/attention of people from other groups (including core). * I’d like to try and set up a monthly IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are **#wordpress** and **#wordpress-dev**, on irc.freenode.net. chat and/or Google hangout for the liaisons to have some real-time communication. * I’d like to organize an annual contributor summit. Similar to the core team meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. concept, but more inclusive. The core code contributor team is the most in the know right now, but I’d like to make things a little more equal. Even within core, sometimes I hear people saying they wish they had more of a voice. The way the survey is set up, first you’ll pick how many reps you think core needs to have in the game (just one for core, or a couple, with each representing a different level of experience/seniority to make sure more issues/concerns are heard?), then you’ll vote on who you think the rep( s) should be. Note that inclusion in the survey does not mean that person has agreed to be a rep… I just pulled from our credits list and teams page for 3.4. Once the votes are in, I’ll contact people to see if they’re up for it. The survey is at http://wordpressdotorg.polldaddy.com/s/core-contributors and is password protected to help reduce spam responses: core2012 If you could fill it in before the weekend is over (or right now… it’s only a few multiple choice questions), that would be great. Thanks! [#contributors](https://make.wordpress.org/core/tag/contributors/), [#survey](https://make.wordpress.org/core/tag/survey/) [ ](https://profiles.wordpress.org/jenmylo/) [Jen](https://profiles.wordpress.org/jenmylo/) 8:06 am _on_ June 21, 2011 Tags: survey    # 󠀁[I’m doing a talk at Open Source bridge…](https://make.wordpress.org/core/2011/06/21/im-doing-a-talk-at-open-source-bridge/)󠁿 I’m doing a talk at Open SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. bridge tomorrow/ today on encouraging younger contributors. Can any/all contributors do me a favor and [fill in this tiny little anonymous survey](https://polldaddy.com/s/D66515582B909640) so we can get an idea of the average age of our current contributors, and how old people were when they got bitten by the open source bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Thanks much! [#survey](https://make.wordpress.org/core/tag/survey/)