New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User experience and facilitation of data entry #123

loleg opened this Issue Aug 27, 2018 · 0 comments


None yet
1 participant
Copy link

loleg commented Aug 27, 2018

The easiest way to use Dribdat right now is to avoid using it at all: has a (admittedly rather fiddly) script which allows participants to update their projects in a Slack channel. Nevertheless, people tend to (mostly uncomplainingly) use the same plain old form to work on their projects that we've had from the beginning. This could be dramatically improved with not too much effort: for instance:

  • by putting into a wizard and better explaining the steps
  • simplifying the vocabulary
  • allowing edits directly on the page
  • have a tutorial or video explanation of the process
  • forking projects #92

Though less of a priority, the event forms could be improved in the same fashion. For instance, users like to customize the CSS of their site, but they may not know how to host a CSS file on GitHub (which is recommended in the form) and instead add code directly to the very clunky interface. The event form has many fields, and is disconnected from the process of creating challenges (further discussed in #93).

The goal of this issue is to analyse the problem and propose a strategy to revise or replace the UX of the interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment