Notice: The WebPlatform project, supported by various stewards between 2012 and 2015, has been discontinued. This site is now available on github.

Berlin 2-2013

Survey results from the Berlin Doc Sprint February 8 & 9, 2013

The results of the survey of doc sprint participants show our community is deeply involved in the development of the Web Platform and equally committed to making the documentation and excellent for everyone in the community.

We received a total of 34 responses to our survey. That’s 63% of the 54 doc sprint attendees.

Doc sprint scoring and questions

score 1.png

score 2.png

score 3.png

dsq 1.png

Other sources of hearing about the doc sprint

  • Annouced by AJM at Firefox OS Appday
  • Friends
  • Google Developers Group Meetup

dsq 2.png

Usability scoring and questions

use 1.png

use 2.png

use 3.png

Which aspects of the site do we need to improve to make contributing easier and how should we improve them?

  • Please improve input boxes and stuff like this
  • The editing of content is really hard. The Templates are not really explained and you need to search for answers. Example pages with all templates would help alot!
  • Stability or Bug Fixing. When Saving a CSS property page, some of the contents is not saved unless in prior one clicked "preview". The time it takes to make even small edits is far too long. Also textfields of templates are far too small to get all the content in conveniently
  • clearer documentation
  • don’t restrict edits or mark them as non-editable
  • make priorization (= need of review) online
  • improve editing by changing syntax to Markdown or HTML
  • The site needs more speed and there are a lot of little bugs and showstoppers that slow you down a bit. It is also not clear what to do with imported but unfinished content, and how to contact authors of content with disputable quality (e.g. a11y parts)
  • It would be nice for beginners if small tasks were grouped by task somewhere and listed on a small list just to give an idea how to participate. It doesn’t need to give every possibility.
  • A lot of things have already been said during the doc sprints and filed as bugs
  • search gives me the same page several times, if the word exists several times - that wierd.
  • I cant add answers to the q/a section. Dont know why, everytime the page says i am not logged in. Pipe issue is an issue.
  • The MediaWiki bugs regarding examples and such (where sometimes code was rendered and sometimes not) were a bit annoying.
  • Workflow, versioning, reviewing.
    • Although flags are useful, maybe find a way to explain a bit more what needs to be changed or improved, and how.
    • When we are done with editing, maybe a special state "needs review", before removing old (addressed?) flags.
    • A “being-worked” state to prevent conflicts ?
  • Switch from mediawiki syntax to smth. devs are used to know (markdown)
  • Make the search function outputting useful content.
  • Solve the session timeout issue, introduce a Markdown editor, implement a mediawiki extension that converts characters into html entities. It would be awesome to have the form organized into steps, so one can fill them out one at the time quickly and easily.
  • Get rid of Mediawiki. Seriously.
  • Define clear and useful structures and rules for the entries
  • Don’t sort the content based on the browser’s code implementation, but think about users. A web developer doesn’t care if context.font belongs to canvas.2dcontext, he or she will search for a `working with fonts` section
  • In other words: the content pages are aready nice and useful, the structure to get to these pages is horrible (atm)
  • Bug fixing (Session bug et al), finally, and as thoroughly as possible. This is the perfect showstopper to turn away anybody that has had interest (and these people might not come back that early).

Community questions

com 2.png

dsq 3.png

In your own words about working with the community

  • Define User Experience as an evaluable process and spread the concept of UX into the world of web development.
  • I think there is real need for a good documentation! I’m so tired of looking and reading that takes longer than coding and enjoying the work. Also, if I think about the editors of the future which could get semantic information about the language you’re coding (think of autocompletion tuned up), is really exciting, isn’t it?

com 3.png

You and your work

you a.png

Other occupations

  • University Teacher and Mobile Developer
  • uhm, almost everything :)

you b.png

you 2.png

you 3.png

you 4.png

you 5.png

What else would you like to say?

  • I appreciate all the good work that you’ve done so far and I’m looking forward to contribute.
  • For such an event the internet connection has to be faster and stable.
  • Thanks for organizing DocSprints!!! :)
  • Thanks for the nice event.
  • … I told everything one by one. Thanks for the event and the oportunity to parcipate.
  • I really like the cause and reasoning behind I find that I do have some trouble with things like attribution (W3C isn’t mentioned, for instance, even though I do get a lot of information from their spec-pages) and trying to write the information in my own words.
  • involving experience - more music during the breaks
  • I would love, love, love to see a JSON API, where TextEditors and Web IDEs could get meta information from in order to provide good autocompletion and quick lookup helpers and snippet inserters. And hints. Just imagine your CSS editor isn’t only providing a drop down for “fixed” or “absolute” but also telling you the difference without leaving the editor. That would be so totally awesome!

About the survey

Like a lot of what we do here at WPD, this survey was a learning experience. Due to operator error, the results of the survey could not be shared publicly without forcing everyone through Google+. That is why we’ve had to resort to screen shots from the survey results pasted into this article. The results have not been altered or otherwise affected. Next time we’ll fix it so that the survey results are publicly available to all with no log-ins required. We’ll also fine-tune the questions and methodology. Thanks to everyone who helped with the survey and everyone who responded!