 Okay, so front-end update. So I'm gonna go through a list of some awesome things we've done. Some of this will be repeats from, because the back end and the front end are obviously working together. And if anybody has any questions, we can take those questions at the end. So here's just a couple of the awesome things we've done. We're now using system fonts, which means that we're using the natural fonts that come with your operating system, instead of loading external fonts, which take up space. We have saved a lot of extra kilobytes. And I personally think it looks fantastic. We also have manual actions on the pipeline graph. And so you can, you know, act on the pipeline graph itself. We have Docker templates that you can choose from in a dropdown. And we have direct links from the pipeline list to bills. So these are just some of the things we worked on in the last release. This is a huge one. The build log, we improved the scrolling experience. So now you can actually use the build logs quite easily. It's a much better user experience. And we obviously have the shorter line lengths for issues and merge requests. And that makes the issues and merge requests much more readable and visually more appealing. We had this awesome community contribution that took some work, but we got it in. Thanks to the help of Sean and Dawa, we were able to get this in. It's a really cool feature that provides KTEC support. So you can see that you write some formulas in latex and it actually renders it. So here's some of the problems that we have solved or things that are work in progress that have solutions and things that we're currently solving. So right now we have real-time data being used in multiple places. It has not been deployed yet anywhere except as the notification that comes in on the merge request page, but we do have real-time data solved as a problem, which is a fairly complicated problem. You can see here, this is a work in progress for the issue page where the title is being updated and then somebody viewing that page will get that update in real-time. Accessibility is something that we are also currently working on, it's a huge issue, but for people who are using screen readers, we have as just three of the many things that we've done, we have updated the tab index, so that when somebody is tabbing two different fields, they will get the right thing highlighted and we're using more semantic HTML to make sure that screen readers will read these properly and we're working on testing things on actual screen readers so that we know that when they're using the screen reader, they're getting what we thought they were going to get. We have some JavaScript bloat, which we're currently working on removing different libraries. We have a lot of jQuery libraries that just don't need to be in there or they're being used very little, and so we're removing those as well. CSS bloat, thanks to Annabelle, Annabelle took the entire last release and went into our CSS and organized it because our previous method was just to write or the method that a lot of people were using is to just write CSS and plop it on. With the rest of the CSS, Annabelle organized a lot of the stuff and she's still working on that as well, which will make our development time much quicker because most likely people don't need to write CSS anymore because the components have already been built, so this will save us a lot of time. So there's a couple of problems that we need to solve that we are looking to solve. One of them is pages with lots of data. So this is a performance specific to the front end. This looks like a completely fake graph, but it's real and it shows us that on one particular merge request and the linked merge request is not the merge request pictured here, that's a merge request that is solving some of the problems listed here by Fatih. But you can see that there is something close to like 35,000 nodes, individual elements on the page and over 4,000 listeners, obviously with event delegation and different techniques, we can solve a lot of these problems. So the roadmap for the front end, we have a lot of real-time things coming up, so real-time issue updates and merge request approvers. We're working on implementing Webpack, which will allow the front end to have a similar thing to the back end where the front end code, the libraries that we use can be loaded, they don't have to be included with the GitLab library itself. We're improving accessibility and we're also improving our CSS. This is part of our roadmap going forward, at least for this release.