Update: Check out this overview video showing the changes we’ve made!
Yesterday, we made our first major update to the version of MoodleNet currently undergoing initial testing. Not only did this update alter the look and feel of the interface, but it also added some useful new functionality and fixed some bugs reported by users via Changemap.
- Gravatars to represent users
- Community overviews
- List of members in communities
- Collections display number of resources they contain
- Collections indicate number of followers
- Button styles and positions improved (e.g. for ‘Create a community’)
- Increased character limit in text fields
- Moved language selector to menu and removed flags
- Added full-width images in communities
- Sidebar has a darker colour
- Improved metadata import when adding resources
- Users can only add resources & edit collections in communities they’ve joined
- ‘All collections’ page fixed
- Switching languages and then back to British English no longer causes an error
- Word wrapping on community descriptions
Next week, we’re aiming to add collection-level discussions, featured collections, and basic user profiles.
For those interested in our product management processes, we’ve also switched to Moodle Tracker (Jira) for stories and epics while sticking with GitLab for issues. Check out bit.ly/MN-epics
We’re a week into the initial testing of MoodleNet and are already getting some fantastic feedback from testers!
While there’s a long way still to go before we can open registrations, things are really starting to come together in terms of the user interface (UI) for MoodleNet.
The above screenshot was taken today. Even in this very initial version, the feedback we have had from testers has been mostly positive. Our anonymous survey to ask for their first impressions included responses such as “nice interface”, “attractive” and “clean and clear”.
Our designer and front end developer, Ivan Minutillo, isn’t content to rest on his laurels, however. The above screenshot is taken from our staging server and shows an iteration of the UI that we will make available to users over the next few days.
As you can see, there are many improvements, including:
- Image width
- Placement of ‘Create a community’ button
- ‘Overview’ tab in communities
- Indication of community members
- Dark sidebar
- Use of gravatars
Ivan hasn’t stopped there, either, though! Although the above mockup isn’t coded yet, this is the direction we are currently thinking of heading with MoodleNet. As you can see, the sidebar now includes ‘MoodleNet’ at the top, there is search functionality (which we will be doing across federated instances) and the whole experience feels much more refined.
Whether or not you’re part of the initial testing process, we’d love your feedback on this! Do you like what you see?
Last week, we put out a call for initial testers of MoodleNet in English and Spanish. We’ve been delighted with the response, and have now closed the sign-up process until the next round.
When developing a new product or service, it’s important to test, test, and test again – which is exactly what we’ve done with MoodleNet so far. The concept of a resource-centric social network came out of talking to a wide range of experts and educators. That led to a design sprint that included user testing of the resulting prototype. We tested the sign-up process to MoodleNet, solicited feedback on our code of conduct, tested out community calls and office hours, how we work as a team, done some internal testing, and will be very soon running a privacy and security testing programme.
The most important test so far, however, starts next week. That’s the time when we’ll be putting MoodleNet in front of users for the first time. We’re testing the value proposition: “Do educators want to join communities to curate collections of resources?” This doesn’t mention federation. There’s no mention of mobile devices, fancy user interfaces, or machine learning. We’ve tried to create a very simple approach to test this basic value proposition.
It may turn out that users agree with this value proposition. They may think that, yes, joining communities to curate collections of resources is something they want to do. Alternatively, they may indicate that they prefer a different approach. Either way, this test is of vital importance; it makes no sense to continue along this particular path without a mandate from real-world users!
For those interested, but who aren’t part of the initial testing, here’s how it will proceed:
- Successful applicants will have their email address whitelisted and be invited to sign up to a Moodle HQ-run instance of MoodleNet
- Feedback from users during the testing process will be collected in two ways: via Changemap and through weekly surveys
- New features will be rolled out during the testing process, as detailed on this milestone
If you missed the sign-up process this time around, or weren’t available for the first testing period, then don’t worry! You will have an opportunity to put your name forward again in a few weeks’ time.
We’ve a few short updates that don’t necessarily warrant a post in their own right, but which are nevertheless important to communicate as MoodleNet develops.
1. Draft community guidelines
Thanks to those who took the time to comment on this. We perhaps took a wrong turn in calling the whole thing a ‘contributor covenant’ and have separated this out into contribution guidelines and a code of conduct.
2. Updated sign-up process
After reflecting on user feedback about the sign-up process, we’ve changed our approach. The latest workflow can be seen below, based on sketches we’ve already shared:
Not showing up? Click here!
Users can now get more quickly into MoodleNet, and have a choice as to when to update their profile (including Emoji ID).
3. Draft testing plan
Our plan for the initial testing of MoodleNet existed in various GitLab issues and wiki pages. We’ve pulled them together into a single wiki page giving an overview of the draft testing plan. While we’ve still a way to go to ensure we’ve got everything in place, hopefully it’s possible to see the plan emerging up to integration with Moodle 3.7!
Finally, we’ve got two pieces of exciting news to announce next week, one relating to our team and one to external recognition of our work so far!
Image by Christopher Burns via Unsplash
Last week, the MoodleNet team were in Barcelona at Moodle Spain HQ. Much of the work week involved the kind of discussion and implementation that can be difficult to write about, as it mainly involved hooking up the backend and front-end code.
Kayleigh and Sam from Outlandish joined us in the office on Thursday and Friday, which meant that we had an opportunity to reflect on the results of some testing they did with users about the sign-up process for MoodleNet. Their findings are below (or click here).
Based on user feedback, which is always different from what you expect, we’ve decided to take a different approach to the sign-up process. It became clear that there are users who want to get straight in and start using platforms straight away. These are the kind of users who will complete their profile later.
On the other hand, there are users that want to complete their profiles straight away, so that they have a full ‘presence’ on the platform and others can find out more about them.
Our proposed workflow, which will have a knock-on effect on other elements of the user interface, is below (or click here).
What are your thoughts on this? Note that we’re planning to implement a (skippable) user tour for first-time users of MoodleNet. We’ll also be writing a post soon that explains ‘Emoji ID’ and why it’s more than just a cute thing to have on your profile!
Image by José Alejandro Cuffia used under the terms of an open license
Update: sign-ups for this are now closed, and Outlandish will be in touch with those who registered their interest!
Over the next couple of weeks we’re going to be doing some online user testing of MoodleNet’s sign-up process. It will be run by Outlandish, with whome we’ve been working on front-end development and UX.
We’re aiming is to remove any barriers to adoption for the beta testing in January. So we need feedback on everything from “that button should be on the left” to “what on earth is that emoji ID thing?!”
It’s not remunerated, but you’d be front of the queue for a MoodleNet beta account (of which there’ll only be 100, initially) next year!
If that sounds like the kind of thing in which you’d be interested, here’s what to do:
- Introduce yourself here
- Check your availability for the following dates (GMT): Weds 14th (PM), Mon 19th (PM), Tues 20th November
- Fill in
Thanks in advance! We’re looking forward to making MoodleNet as awesome as possible!
Privacy notice: if you volunteer for testing, your details will be added to a spreadsheet, stored on Moodle HQ’s Google Drive. We’ll keep your information until the end of the testing process and share your details with Outlandish, who are overseeing the testing process. Before testing, you’ll be required to give your consent to ensure GDPR compliance.