Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

MoodleNet/Front-end dev workshop: Difference between revisions

From MoodleDocs
No edit summary
No edit summary
Line 29: Line 29:
* Decide on [https://gitlab.com/moodlenet/clients/react/issues/12 resource allocation]
* Decide on [https://gitlab.com/moodlenet/clients/react/issues/12 resource allocation]
* Figure out what the 'containers' would look like from a [https://gitlab.com/moodlenet/clients/react/issues/16 basic design point of view]
* Figure out what the 'containers' would look like from a [https://gitlab.com/moodlenet/clients/react/issues/16 basic design point of view]
* Start thinking about [https://gitlab.com/moodlenet/clients/react/issues/14 pre-MVP user testing]

Revision as of 10:54, 24 September 2018

<< Back to MoodleNet index


Doug and Mayel from the MoodleNet team spent three days (Weds 19th to Fri 21st September 2018) with Outlandish. This was follow-up work to the Design Sprint we did back in May 2018, and to UX Milestones 1 and 2.

We had an ambitious agenda for the workshop, aiming to:

  • Allow Sam, the front-end developer Outlandish have assigned to this project, to get up to speed with MoodleNet
  • Help define and scope front-end deliverables
  • Decide on the layout/look/feel of both the desktop and mobile web versions of MoodleNet
  • Create a draft style guide (in code)
  • Develop a basic app (skeleton repo in GitLab)
  • Filed GitLab issues for (at least 1+ month of) post-workshop front-end development
  • Agree on the toolkit (incl. libraries) we’re going to use

There is a GitLab board to track issues from both this workshop and forthcoming front-end development work.


During the workshop itself, we managed to: