MoodleNet/Front-end dev workshop: Difference between revisions
From MoodleDocs
Doug Belshaw (talk | contribs) No edit summary |
Doug Belshaw (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
There is a [https://gitlab.com/moodlenet/clients/react/boards GitLab board] to track issues from both this workshop and forthcoming front-end development work. | There is a [https://gitlab.com/moodlenet/clients/react/boards GitLab board] to track issues from both this workshop and forthcoming front-end development work. | ||
* [ | ----- | ||
During the workshop itself, we managed to: | |||
* Prioritise the above work, using a 'must', 'should', and 'could' approach | |||
* [https://gitlab.com/moodlenet/clients/react/issues/17 List the assumptions] we came into the workshop with and whether they're actually correct | |||
* [https://gitlab.com/moodlenet/clients/react/issues/6 Agree on the front-end toolkit] we're going to use and make decisions on components | |||
* Make some UI decisions, [https://gitlab.com/moodlenet/clients/react/issues/7 building on UX Milestones 1 and 2] | |||
* 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] | |||
Revision as of 10:53, 24 September 2018
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:
- Prioritise the above work, using a 'must', 'should', and 'could' approach
- List the assumptions we came into the workshop with and whether they're actually correct
- Agree on the front-end toolkit we're going to use and make decisions on components
- Make some UI decisions, building on UX Milestones 1 and 2
- Decide on resource allocation
- Figure out what the 'containers' would look like from a basic design point of view
