Google Summer of Code Part 3: Goodbye Summer, Hello Future

Summer’s officially over, but we’re taking one last longing look at it in part 3 of our Google Summer of Code blog series. Fittingly enough, this week we’re featuring Avijit, a GSOC participant who helped work on making the creator dashboard that much more user-friendly.

As you may already know, Oppia is a community of learners and teachers looking to help anyone learn anything in an effective and enjoyable way. Being a community based on education, it’s absolutely important that the quality of content is not compromised at any cost. With quality content being the primary focus of their work; creators play a pivotal role in the learning pipeline. The learning experience can be better enhanced with improvements to the “explorations” (lessons) created. To accomplish this, the creator must be made aware of the current state of his/her exploration(s), and how they can improve them. And that’s where I came in- improving the creator’s dashboard.

Revamping the existing “Creator Dashboard” consisted of implementing a dashboard with the following goals:

  1. Allow creators to see common statistics like total plays, average rating, common student misconceptions, and student-submitted feedback for the lessons they own — and to make it easy for creators to take action on this information.
  2. Prioritize the explorations in the dashboard which need action, decided by different parameters such as number of new feedback instances and number of unresolved answers.


Screenshot 2016-08-27 19.52.13.png


Screenshot 2016-08-27 20.01.21.png

The new dashboard page allows creators to choose how they view their explorations in either the default view, as shown above (card view), or in a tabular format (list view). Users can switch to the list view to see a more informative version of the dashboard.

The statistics shown in the top white row are values calculated across all the explorations of the user. In the default card view, explorations may be clicked on to open a dropdown tab which provides statistics for that exploration. However, if the exploration is private then the user will be taken directly to the editor. The explorations can be sorted using the select dropdown and even by clicking on the table headers in the list view.

Sharing the content created also just became easier; there are options in the dashboard to share explorations on popular social media platforms like Google+, Facebook, and Twitter.

Lastly, to provide an equally appealing experience for the users browsing the dashboard on a mobile device, care was taken to ensure the new dashboard is similarly functional to be almost as well equipped as the desktop version. Here’s how it looks on smaller screens:

Screenshot 2016-08-27 20.08.37.png

I would like to thank Google for enabling students to participate in open source development through GSoC, the whole of Oppia community for accepting my project proposal and letting me embark on this fantastic adventure, and most importantly, my mentors — Sean Lip, Xinyu Wu, Allan Zhou for being there to help me and Rachel Chen for ideas and design mocks for the dashboard.

I learned a lot during my 3 months of GSoC. I did the best that I could to help the community. And though I can say that most of my work is concluded, there’s still a pull-request in git-hub left unmerged, a few ongoing pull-requests involving work unrelated to GSoC, and some more code I’ve promised to write. And I’m happily looking forward to all of it as my summer of code comes to an end.

Thanks to Avijit’s great work this summer, we’ve seen quite a change come through the Oppia interface. We’ve got some exciting things coming soon such as an Hour of Code event, and a blog post featuring Sourav, who helped organize a Hacktober bug-bash to help Oppia find a few bugs and help us make things better for you. Stay Tuned!

-Oppia Team

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.