We have started work on improving the navigation around Moodle as part of the Moodle 4.0 UX improvements. The main goal is to reduce the cognitive load for new users in our system. We want to users to be able to intuitively find the location they are looking for.
We ask for your feedback on our proposal. We have the outline of our project located at Moodle 4.0 navigation improvements, as well as an epic in the tracker which has even more detail. Please feel free to add comments and suggestions at any of these locations.
(I know, it's a wiki. I could edit it myself, but I did not want to start 'messing around' with 'your' page.)
Admin->Courses->Manage courses and catagories. Then editing the settings for whichever course would seem the logical place to set enrollment methods.
Looking at the course navigation (because I think that is most important) I am not sure this is right. Just my opinion, I don't have a very strong one because we use a custom theme and would not use navigation like this in any case (and I haven't worked out if underlying changes have problems for us).
Overview Settings Participants Grades Reports Question bank More
- The actual course
- Use the course shortname (e.g. CS101) instead of the misleading 'Overview'.
- Change formatting so it's clear that the course is much more important than the other options.
@Sam Marshall: That seems to be an older screenshot. Overview has been replaced with "Course". I'll look into getting that image replaced.
@Luiggi Sansonetti: That is an older forum discussion. This forum here would be better.
These improvments seems very clean and nice.
Do you also plan to create some user tours to explain how things (now / in future) work, like it was done some versions ago? I think it would be useful (but to do later in the whole process).
- About half of the top of the screen on mobile. Far from being the most importat thing that much screen space could be used for
- It is inconsitent: These days, every system that you log into (including Moodle) has the user menu top right. That is good consistency. Don't break it.
As a penant who one did a course in requirements analysis, I feel impelled to point out that your user stories are not worded well. E.g. the first one;
"As a learner, I want to easily find the menu item, so that I can move between courses and activities."
The user story should be what the user wants to do:
"As a learner, I want to easily move between courses and activities."
How to achieve that is your business as UX designer, but things like 'menu item' are part of the solution, not part of the requirement. (Also, not a very specific requirement, which could usefully be improved.)
When we get to
"As a learner, I can want to view my grades for a forum activity, so that I can discover if my participation is satisfactory."
that just makes me want to cry. So many dangerously wrong assumptions about learning and pedagogy, crammed into one sentence 😥