 Well, as Carlos mentioned, the whole thing was working like a lot in the back end. And well, I'm just showing here some visible changes and also thanks a lot. And this work was from Sabia and the rest of the UX team. So I'm just the messenger here. I prepared this presentation in the demo in the left side. We have a 4.3 site. And in the right side, there is a site with the main brands and a couple of commits on top. Some of them are already integrated and the rest will be there also soon. So we can see here now the main differences that, for example, now instead of having the activity cars, we are moving to the section car, so this will be helpful for the future hierarchy. And we can also see the new icons here. So they are super cool. And yeah, this is the view without the editing mode. And the main differences here in this part of the project is if you enable the edit mode, there are more differences. So you are aware that you are in editing mode. So for example, if I can go editing in both sides, here you can see that the separators are different. So there's no differences about the functionality. So if I go here in the previous version to other activities, just the same as the new one. So no differences about functionality, but there are in the UI main things. So these plus icons are now, because there are no cars now, there are separators with that icon working as before. And this button is replaced with this smaller one. And also this button to add topics between, sorry, yeah, well, to add topics between section between them is it was replaced also with a separator here between sections that is super nice. And but well, it mentioned that at the bottom of the course, you will have this big button to add sections. The functionality, as we said before, is nothing new. So it's working as before. So you can add sections and it will work exactly as before. Cool thing is, for example, now if you collapse all sections, you will be able also to add sections in between. So that's a nice addition. And well, also mentioned that if you go through GVOTE, it would work like perfectly, so it's fine. And last thing to show, if you go to a section, you can, this is nothing new. But you can go to the section page and it will work the same. So you can add modules between sections, between activities and at the end of the session. And bulk actions will also work the same. You can move things around as before. So nothing new about functionality, but yeah, there was an amazing job for the UX team. And that's it. I'm Ferrand Retio, the technical architect from Educational Solutions. And I work mostly with MOPIS team. And in this case, MOPIS team has a weird project that will end up having two releases on its back. So it usually happens with this kind of project that we implement many small things that are quite abstract. And it's easy to lose the North Star that guides the project. So now it's time to show a bit what it's all about, all the changes that we are presenting on the previous Spring demos. So this is an instance that has everything that it's on going now and even the alpha version of the mod sub plugin, I sub subsection, which is the final feature we want to incorporate in model. So this is the new course aspect. So with the new icons, the new cards, et cetera. The first thing that it's noticeable is that the focus point of the course page, it's not it's moved from the activity card itself to the section. So we are giving more importance to section than to activities and that it's not random. It's not casual. It came from the UX perspective analysis and it's consistent with the future subsections. So all the icons are moved and everything. So it happens the same with the edit mode, where all the stuff has been reshaped to be less intrusive for the user or more obvious in some cases, like the disappearing things now are more obvious where we'll go and the activity mode user, it's more more whitish and more clean in general. So everything looks cleaner because we are preparing the model for having subsection. So what is a subsection in the end? Subsection will be a new kind of activity that can be tested right now because it's public in GitHub, but it's not meant to be used yet because there are many aspects of model that are not prepared to have subsection. So that will be the all the issues from the next release will be to prepare the idle to make it work as a real subsection. But in this case, we have a course with some sections on it. And there are a couple of activities that are from the icon. You cannot recognize is this one and the other is this one. Those are subsections. So this is an instance with a special plugin called mod subsection in it. When, as I can see, there's only four sections in this course and I go inside. This will go straight to the new section page we created in 4.4. It was not casual as the rest of the thing. So the idea is to let core have always a section page on its own. So we don't depend on showing all the course. This is something that it's on model since forever that to show a section, you need to show a course page. And now it's not anymore. This is a special page that it's only for section display. And we have all the logic embed here. And then the subsection itself can the activity itself because this section depends on an activity. It can replace all the action menus using the activity one. So it's not editing the section per se, but it's editing the activity. And all the, and those activities here are not displayed in the course index because the course index is not yet ready for subsections. But the course page is not listing all the delegated sections, which means that sections that are inside the subsection. So it's not represented here, but they are on the course in the end, but in delegated sections. And we accomplish quite a few things in this release. For example, we start wondering what happens if I drag things directly into a subsection. So this is working. We can go in and out of the subsection. But we also prevent looping because this is a subsection and this is another subsection. And we don't want the user to create loops and complex structures. We only want one level of subsection. So if I try to drag a subsection directly on its own content, it's not doing anything. If I drop it, it won't do anything. And the same happened with any other subsections. So we add extra controls to the drag and drop to have more fine grain on what we want to accomplish there. And there are many things going under the curtain on that project, like synchronizing the section names with the activity names and all this stuff. We also find out that the users don't use the self-numbering section. So now everything is more named as section. So we stopped using the Word topics for sections and we create new sections as a new section. So that does a huge and probably an expected change for many of you. And this is all about this release. We have many, many changes going on. And the next version, the 4.5, should be the one that will bring subsections as it is designed from the UX team. But we want to show you how it is right now. So we have a plugin that can be used, but it has many things that are still not adapted, but it's working more or less. So that's me.