 So just a bit of a background for anyone who's new to this project. In the 4.0 release, the ability to indent text and activities and resources was removed for various reasons and it ended up having a really big impact on course creators and their ability to create a visual hierarchy for the content of their courses. So we knew this was a problem. Our community members were being very vocal about how this had impacted them and many of them were just calling for us to bring indentation back, saying that they didn't or didn't want to or couldn't upgrade to newer versions of Moodle without indentation. So we didn't want to limit this discussion to whether or not we were going to bring indentation back. So our approach was to try to understand the underlying needs of course creators when they're structuring their courses and try to find the best solution to meet those needs. Next slide, Marie. So like I said, this is going to be pretty high level, but we wanted to just touch on two things that we thought helped contribute to the success of this project. One was the process that we followed for discovery all the way through to design and going into development. And the next was just the collaboration that we had both internally and with our community. So first the process, the process that we followed maps back to the development loop that's outlined in our product heartbeat, which is the photo or the image on the right. So I just wanted to drop that image in here because I think it just helps to illustrate the process that we followed. So in the understand phase, that's where we conducted discovery research. We had in-depth interviews with members of our community to learn about their course creation process and some of their core needs. In the explore phase, we conducted a co-design workshop just to generate ideas and design concepts with our community. And then Sabina has taken the research and the outcomes of that workshop. She's created some initial design solutions, design concepts, and has been having weekly rounds of feedback with the community to help refine those designs. For the act phase, after the research was conducted, the product team was able to align on both a short-term and long-term strategic plan. And then by the end of this project, because design reviews are still happening, there will be finalized and agreed upon designs for the first phase. And then the long-term solution will follow a similar design process. Next slide. Thanks. And so collaboration. I won't go through all of these cells. I won't read the entire table, but you can see there was involvement from research, design, the entire rest of the product team and our community. And if you look at the colors, hopefully you can sort of kind of tell that as a researcher, my involvement was heavier kind of earlier on during the discovery phases. And then Sabina and the rest of the product team became increasingly more involved as we moved from discovery into design and development. And of course, we had a really passionate core group of community members that were providing feedback at each phase and were being updated along the way. So this project has been a really collaborative experience the whole way through, which I think allowed everyone to take part in the research and learn from the research as we were learning. And it also meant that we were having conversations, like really important conversations early and frequently about user needs, potential solutions and what was actually possible to implement. So there were fewer misunderstandings and probably more alignment overall. So design workshop in a very structured way. So we started by, well, first of all, I have to say that we conducted the session during two hours with five participants that most of them were having initial interviews in the discovery phase with us. We had a couple of them that didn't have any contact with them before. But it was a very pilot group of different users coming from different organizations. And we started with an introduction of the how my work and doing just a little exercise to get them started with my room using the notes. We, of course, introduce ourselves and explain a little bit why we were here, giving some context about the project for those people who didn't have those initial interviews with us. And we explained basically the agenda of the workshop. This was a very kind of practical workshop. So we wanted the participants to get their hands on and draw different ideas and concepts. And before we started with the exercise, we did a run of introduction just to get familiarized with all the other participants that were on the call and also with the people from HQ. We explained in some rules. We wanted to make this workshop in a fun and dynamic way. And we started with the quick warm up exercise just to break the ice and get people not afraid of throwing. We were asking them to draw an alien spaceship, and we wanted to call out the differences that were coming up, depending on who draw the idea or the concept, just to make them understand that this exercise will bring a lot of different and diverse ideas and concepts to the table. So after that, we started the ideation round. We break the ideation into phases. So first, the participants had five minutes for creating and drawing their ideal course hierarchy. And after those five minutes, we asked them to have another second round in a very similar way, but drawing something completely different from their original design. Just trying to make them think out of the box in a creative way and to try to look at the problem from completely different perspectives. And after that, we run through all the participants ideas in a quick presentation from all of them, of the two concepts. We were kind of having conversations, letting them, the other participants ask questions. And what we wanted basically is to start creating a conversation between them, between many different users coming up from different organizations. And basically, the conversation got started very fluently in the presentation rounds. So we have here all the participants' drawings with some notes that we were taking out from the presentation and the comments. And at the end of this presentation, we let them finish to have a discussion and to basically talk about all the ideas that they were showing, that they were, sorry, they saw during the presentations. And just basically talking about how the different ideas from other participants have changed the way in which they were seeing the solution for this project. And it was a very, very interesting discussion. And at the end, we wanted to run out a retro exercise just to get the participants' feedback and to see whether they liked this exercise, these activities, what they thought we could be improving and what were the wonders about this session. And to wrap up the session, we explained them the next steps, asking them to sign up into the weekly sessions that we conducted. And also asking them to join the mood exchange staff. So far, we've received a response and feedback from all the participants. And they really enjoyed this involvement of the community in our work process. And they were asking for having this kind of exercise more often and also in a big picture level. So, yeah, that was kind of the exercise that we conduct. I'm going to stop sharing and go back to the slides. Yes, so after these workshops, Sitara and I worked on the analysis of the takeaways, the outcomes of the workshop and the exercise. And also, along with the results of the initial interviews that we conducted, we took some main concepts, main ideas that were the most important for those participants for these projects. So the users want the ability to visually group elements related within a course with expandable and accessible sections and subsections. We observed levels of Brooklyn or Hierarchy are enough for us to show the big picture of an entire course in a very quickly expandable way. So users don't want things hidden away, they want to see everything at a glance. And so in a course here, we also related to this. So the scroll of death was something that came up into the conversation a lot. To reduce this, prove this kind of identity. Yep. Okay, thank you. So after the analysis of the outcomes of the discovery phase, we had a technical discussion with the team to scope the project and we decided to break this project into the storm or temporary solution and the long term. And just because of the magnitude of this project, it was very big. We decided to bring the invitation back in an improved way with three levels of Hierarchy rather than infinite levels that we used to have before. And also improving the text and media activities to be reflected in the course index and some other changes. So that will be the temporary solution that will have in place for the next release while we work on the long term. And all these workshop and discovery outcomes that we collect through the initial phases will be reflected on the long term solution. So if you want to move to the next slide, Marie. So yeah, for the long term, I've got a demo that I'm not going to be doing just because I'm going to be running out of time. But the link for the prototype is there. You can see that other projects and other issues are involved in this Hierarchy project that we have for the course date. And if you move to the next slide, Marie, I've got also there the some wireframes from the long term solution that we are conducting the design reviews in a weekly basis. So these wireframes are a very low fidelity level in a very early stage of the design process. We're still getting feedback and iterating in a quickly way based on the participant feedback. And you've got them the link to the prototypes as well with all the different alternatives that I'm working on. And these concepts and ideas will be evolving through the time with all the feedback that we are collecting. So the good thing about this is that we are working closely with the community. The community is, well, the participants of this project are very aware of all the change and ideas that we are proposing. And this is something positive for getting positive feedback at the end in the release of a project.