 Hello, everyone. I'm Andrew Lyons. I'm the technical architect for Moodle LMS. So we're currently working on removing the legacy TinyMCE plugin that's available in MDL77308, which is up for review. We've also got some changes to make TinyMCE the default editor for new installs. So that will be in 75915 and we will make that the default editor for existing installs from Moodle 4.3 onwards. I will be giving a demo in just a moment. We have also had a meeting with TinyMCE themselves to discuss premium integrations. One of the things that I've also been working on is improving out the way that we do settings and the demo. So for those, I'll give a second foot to share. There we go. So at the moment we have a lot of different ways and this is part of the TinyMCE. You work a lot of different ways of doing settings in Moodle. So each of these tabs in my browser is a different settings page showing essentially the same thing. Different columns, different column orders, different titles from the same columns. For example, we have hide and show. Sometimes we have order. Sometimes we have different links. So essentially as part of the TinyMCE work, we're trying to add the ability to control which plugins are enabled or disabled. So to that effect, I have been working on standardising the way in which we show these pages. So again, we have the activities page which looks like a tool but is now using the same code, the same underlying code, the same table, reducing a whole load of code duplication but also reducing the differences between each instance. We still have places where there are custom columns or where columns are not relevant. For example, some plugins cannot be enabled or disabled and some cannot have their order changed. The other thing which this change brings about is JavaScript-based editing. So every time we want to change a plugin, we can do so and it will reload just this one page and just the table inside it that also applies for the order of plugins and it also applies to things like custom features like the block, has the ability to lock individual things and we can find that elsewhere. So the end goal on this change is to reduce the code duplication, reduce the number of places that we are doing very similar things in the user interface but doing it very differently and that will give us a more consistent user interface and generally make this a bit nicer to use and also give us a slightly more modern UI. This does not currently have drag and drop but it would be relatively simple once we've implemented this to add, drag and drop to this interface which would again make it a bit more useful and a bit more usable and make our users happier hopefully and that's TinyMCE.