Hello, I would like to provide you with some insight and information about the proof of concept that will allow us to run web id on the editor lite without further ado. Let me just jump straight into the editor into the web id and, let's see how it works now, so we are in a project and let's open any file, let's say authors for example, so it's still the same web id.

It does have syntax highlighting and things, but you could already notice one slight difference. The updated web id now has the loading state. Let me reload this page gang once for you to take a look at that.

You saw this little spinner right, but when we switch the files, we not only show the spinner, but we also blur the already open file before we get the content for the new file, and here we go.

This is one uh more like user experience change to the web id after moving to edit the light simply because the data light already comes with the loading state, bundled so it was just a matter of setting and removing the data set attribute.

Now. Does it actually work? Does it do the things as it is it's supposed to? Let's make some changes to this test empty. It doesn't look like it has a lot of sense. So, let's remove this thing right now. Now we have it marked as changed. We have the commit button available. Let's go there and here we go, the div does work as well. It does show the changes.

uh Wonderful, let's discard the changes. Well, this work.

It does work, but it doesn't reload you to the edit. This is not related to this proof of concept. This is how the current web id works, because we have javascript error fired up there, and I think I have created the issue for that as well. But let's get back to the testimony. Okay, it got uh restored, it was restored right, we don't need so we remove it once again and we try to let's check yeah.

It is still marked, has changed so let's actually commit this file and see whether we can create a merge request out of this file right so creating your branch starting emerging quest. Let's do that.

Error loading last commit error. Message doesn't come from this proof of concept; it is in the current web id as well so nothing new here. So let's take a look. Whether our change is actually propagated to this merge request. We open the only change in this merge request and, yes, we do have this change here.

Now, let's go back here and submit the merge request. Now we are going to test whether we can get to web id from the merch request to review our changes without any problem. Let's click this opening web id button and we are getting straight to the web id to the review tab with our single file.

That has been changed in this merge request and it does show the things properly with that, I think we can claim that the proof of concept has been done.

There is a merge request, open it here, so merge request, number 51212.

That invites you to the discussion of the things and if you go to the commits tab, it will give you all the things that have been changed. I was pretty uh pretty careful with.

Squashing related changes to one commit so that we could split this proof of concept into several merge requests with uh two three commits per merge request for proper implementation, because here we are lacking some tests. Some tests need to be updated and so on and so on. But I welcome you to discuss the things and please please, please do ask the questions participate in the discussions and, let's make it happen, let's make our webidee beat driven by editor light. Thank you.