 All right. It is the top of the hour. So, welcome everyone to the UX functional update. Just going to jump right in. So, first we'll go over the UX improvements that are being made in 9.5. To start, we have trial and license purchase. So, as part of making EE the default download in GitLab, we needed to allow for the activation of a trial and the ability to purchase full licenses from inside of GitLab. So, when a GitLab EE instance does not have a license and this will include any previous license or trial license, there will be a link to activate a trial. Trial activation page consists of a basic form. All trial licenses will be sent out a 10,000 seat license. Submitting the form will automatically activate a trial and create sales leads and display confirmation to the user that the trial is activated. So, continuing on that, when the trial license has seven days remaining, there will be a message above the header to remind users of this. The message should only be shown to admin users since they are the only ones that have the ability to actually purchase. If the trial expires, there will be a message to show the status of trial license expiration above the header. In the trial period, the primary button on the license page will be a buy license button. In the details table, it will show free trial remains X amount of days to indicate that this is a trial license and remind them of when the license will expire. So, lastly, this is a big one. As part of making EE the default download on GitLab, we will promote EE features when there is no license for that particular feature. This is a meta issue to organize all of the areas of promotion. So, one of those is promoted. Oh, sorry. I thought someone had a question. So, this will first one here is to promote service desk. The banner will appear if the license plan is GitLab EES since service desk is for GitLab EE premium. For regular EE on-prem sites, users who never start the GitLab EE trial will see the banner from the issue linked here. GitLab.com users will also see the banner from that issue. Another one is to promote issue boards. So, an additional board will appear which tells users how they can improve the issue boards with the EE addition. And we have some further improvements we're actually working on right now to remove that other excess board. We'll probably be talking about that one in our next functional group update. So, another great thing that we're bringing to everyone is the new project templates. So, getting started with GitLab can be daunting. Learning all that GitLab has to offer is even more so. So, for these reasons, it's helpful to be able to quickly create a new project from the template that has several important things already configured, such as CI, CD, review, apps, etc. With GitLab 95, we're introducing this ability and a set of templates supporting some of the most common environments, Ruby on Rails, Node Express, and Java Spring. Navigation is an ongoing improvement. So, we're going to be moving on to the next stage, and that is to make the sidebar collapsible and add icons. This is something that we had planned for in the beginning, and it was reinforced by the feedback. That was pretty much unanimous that everyone wanted it to be collapsible. In order to allow for the collapsing and expanding, we're adding one more row anchored to the bottom. We have also added icons to the first level items in the sidebar to assist with recognition when the sidebar is collapsed. Another feature that we're adding is to add the flyout dropdown to the contextual navigation. So, when you're hovering over a section with second level items, a flyout dropdown menu will appear to offer quick access to those second level sections. When the sidebars expanded, all sections show the flyout on however, except for the active section. The active section already shows all of the sub-elements, so there would be no purpose to that flyout. When a section has no sub-sections, the flyout also doesn't show up for obvious reasons. To avoid navigation tongs, we're supporting fast mouse navigation and improved accuracy, and this is highlighted in that red area in the middle image to kind of show the area that you'll have to be in to have the flyout remain open. Another big issue that we're going to be bringing out in 9.5 is the repo file view as VS Code Editor. Browsing and editing files using GitLab's current repo browser is a bit cumbersome, slow, maybe not the most intuitive thing. To solve this issue, we've added a way to browse and edit files that nearly any user will be instantly familiar with. Users will be able to navigate a familiar file tree structure, edit and commit files in one easy-to-use interface. This feature is going to roll out in 9.5 as an experimental feature very much as the navigation did, so we can test it and gather feedback. We'll be creating an issue specifically to gather feedback today similar to the way we did things for the navigation. So next we're going to talk about work in progress and unscheduled UX-ready issues. Pedro is going to help me out here and present this section. Thanks Sarah. Hi everyone. So the first up we're going to look into what we're currently doing, great things the UX team and also what is already done and that can be implemented either by community contributions or internally with the company. So to give you an overview of what we're doing or what we've done already, there's a total of 113 open issues in CE and EE where UX work is complete and that don't have a really milestone assigned to them yet. So there's a lot of things that have already been done and we're just going to show you now some of the the issues that either we're doing already currently or that we are that are already done. Next. So one of them is the view the to-do button that we're going real time in everything in lab. So one of them is to show in real time how marking to do as done or adding that to do will affect your to-do counter in the header and we're experimenting now with some animations and feedback to the user. The other one is in EE you can already use the approval features which is very useful but now we're making so that you can continue approving or disapproving no matter if the the limit has been reached for the approvals. So reviewers can come back and signal their input without having any effects but this encourages continued considerable collaboration and simplifies business rules throughout organization. The other thing is one of the most requested features is the ability to customize the branch name when you're using the create branch button in an issue. So when you're going to create a new branch or create a merge request and a branch at the same time the default name is shown and you can change it to something else to suit your organization's flow and way of doing things. A small one but yet very important is to display the member role per project. Our user testing revealed that users have trouble knowing their project's membership if their owner master developer or so on and they weren't able to quickly tell which projects there were a member of when they were exploring all the projects in their GitLab instance. So we're proposing to add a project membership label to all project lists and to also change the current group membership indication to follow the design that we have for the project lists. A big revamp is in in the works for the integration settings page that needed some some love for some time now and so as part of simplifying the settings we are improving the visibility of this particular page and now webhooks are going to become just another integration and are no longer treated separately. All active integrations are shown first allowing users to easily edit, delete or deactivate them. Integrations are now just called integrations not project services anymore and we're adding the logos or symbols associated with each integration so it gives more color to the page and makes it easier for users to scan and locate the integration or service that they want to activate and there's a separate section for that where you see all of the logos for all of the brands. Another small one but still important is the ability to resize the comment boxes. We recently removed the resize option when you were commenting and adding a new comments or editing an existing comment. We removed that because of performance issue and when but when you edit the comments the form does not auto resize and there's no way to resize it. So we're going to but when you edit the comments the form does not auto resize and there's no way to resize the box yourself so this is a frustrating experience because you're limited to a small frame and the contents within a comment can get quite long as we all know so the form should auto resize when editing an issue to allow the user to see the full message when editing. In terms of security it's also one of our concerns is improving the perception and also the use security practices when you're dealing and using with GitLab and this issue about improving the confirmation before removing an account came from a suggestion from a Hacker One reporter and improves the confirmation process before removing an account by asking for the password or username of the account depending on whether the account is authenticated externally to GitLab and so it's something that we really would like to get in to so that we can give the reporter some some credit and this is it for the UX ready issues back to you Sarah. Awesome thanks Pedro. So I wanted to talk quickly about UX process. UX process is something that is not necessarily very visible to the entire company so I wanted to kind of talk about the way that we work and the improvements that we're making in our workflow so that we can work faster work smarter and get even more done in a release cycle. So we've created UX is a big plan in the design repo a perceived lack of UI consistency within GitLab is one of the most common negative points referred to by the wider community so we've created this big plan in order to make sure that we're working steadily towards both cleaning up and establishing GitLab's unique personality and voice so the meta issue gathers together all the building blocks of a solid UX foundation and there are many sub issues most of which are already in progress or even near completion so this is very close to really coming together. So here on on this one slide we have a color palette that's something that Pedro has worked quite a bit on making sure that we have a harmonious color palette uniquely GitLab icons actually yep okay want to make sure I didn't have individual slides uniquely GitLab icons so we've been using font awesome for quite a while and we wanted to really take those icons and and ramp them up by using our own unique illustrative style so once in place the new icons will help to distinguish our unique GitLab personality and vertical rhythm so establishing a vertical rhythm means that we're keeping vertical spaces between elements on a page consistent with each other we do this by selecting a baseline number which will act as a common denominator to create all of our spacing this creates repetition throughout the UI and repetition breeds familiarity right now we have a lot of different spacing I know that front-end has created an issue to help clean this up as well they noticed that there were a lot of different margins and paddings being used and this will help address those issues but getting this repetition and this set spacing makes reading easier your eyes will glide along the familiar spacing a lot a lot better things will just seem to fit together Pedro again has been doing some excellent work on this researching and putting together a vertical rhythm for for our UI and this will be across the board so this is just an example of what we currently have and then the proposed vertical rhythm and how that will affect the overall look and feel for each page so you can have a look at that issue and see how that's all put together and on the colors I did just miss one thing part of this color palette was also tweaking it to make sure that it meets the web content accessibility guidelines so very very important another huge undertaking for getting our polish polish inconsistency at GitLab is adding our UX design pattern library to craft so Tori has bravely taken on this enormous task and is currently putting on the finishing touches this library is shared by the design team and it can be updated for all of us as changes occur so this allows our designs to remain consistent and up to date across all files without adding the burden of someone having to actually go in and update a set of master files makes us a lot faster and a lot more accurate and then some more small but important improvements UI polish UX debt the labels meaning and usage they were being used for a very a variety of different issues so we had a discussion to properly differentiate and use them so there was no confusion so these labels allow us to have a better overview of the different type of UX work and the relationship between UX and other teams but especially with the front-end team then the GitLab design repository has been converted to use GitLab or Git LFS excuse me that helps us to work a lot faster it doesn't take so long to download and upload Dimitri took this on as a very welcomed improvement and with the help of Marin we now have this in process and organization of work in progress files and contribution guidelines so part of our workflow in the design repository was a bit outdated so the team came together to standardize and update the way files and folders are organized this consistency helps us on board new team members pick up someone else's work if they're out of office and facilitate contributions from pretty much anyone so a lot of work going on any questions I haven't had a chance to look at the chat so let me just jump in I think it's okay so far okay so far yeah it looks like things very well okay I lost some of my notes there for a minute I was like well where'd they go all right well the last slide as always we want to give some shout outs we've had a lot of help from a lot of people in the past release especially with the navigation and in this release with more navigation changes so we just wanted to give a shout out to everybody but particularly these people for their different contributions I won't go through and read them all you can check out the slide and check out the work that they helped us with if there's no questions I will let everyone go perfect well thanks everybody I really appreciate it see you in the team call