GitLab Create Editor Group, 15 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.8 Kickoff - Create:Editor

Description

Monthly kickoff video for the Editor group discussing upcoming work slated for GitLab 13.8.

See our planning issue for more detail: https://gitlab.com/gitlab-org/create-stage/-/issues/12740

A

Hi everyone, my name- is eric schroeder and I'm the product manager for the editor group, which is part of the create stage of the devops lifecycle here at git lab- and I want to talk to you today about what we have planned for 13.8 I'll link to the planning issue in the video description has a link to our release board has all the issues that we are working on this release and I'd love to have you contribute your questions and feedback in those issues directly, but I want to highlight a few right now in across our category, so I'll start with web ide to understand this one a little bit.

A

I need to talk a little about the underlying editors across gitlab, so the web ide is based on monaco and when you're editing code in snippets, though uh or in the single file, editor we're using something that we've started to call editor light, which is an abstraction around monaco.

A

So technically, they're still the same, the underlying editor, but there's there's some extensibility and and some some work we've done around editor light to to make it just work a little better for us and we are um looking to uh understand the complexity and effort it would take to replace the implementation of monaco that is in the web, ide with editor lite, and that would leave us with a much more consistent code.

A

Editing experience across gitlab, as well as allowing the web ide to take advantage of the the modularity and extensibility of the web of the editor light framework itself. So we're not looking to actually ship this in 13 8, but we are doing the research and hopefully talking more about this in the milestones to come, switching gears to snippets real quick. I just want to highlight some back-end work, we're doing to allow moving the snippet data from which is stored in a separate repository um from one shard, one giddily shard to another.

A

um Now it doesn't come over with the the projects and other um data, so we need to do the work to move it and allow load, balancing and and generally moving the repository data.

A

We're also going to do a little work on the usability for snippets. So, in particular, when you upload a binary file, for example, an image as a snippet, it can be viewed, but it can't be edited.

A

Unfortunately, when we block the editing, we also block editing the the title, and so we've got an approach here where um we can have an edit view that allows you to still edit the title but um prevents you from trying to edit the binary it's just a little bit of a refinement, meaning that you can and keep your multi-file snippets um organized and and named appropriately, without necessarily us having to enable binary file. It um there's a little carryover work related to the wiki.

A

uh There's a few issues on this design, consistency, uh effort that we had that carry over from 137.. I talked about it last time, but uh we'll be wrapping up that work in 13.8 and the goal here is really just to make the the wiki editor much more consistent with the the current ux and ui patterns across gitlab and last I'll talk about settings and navigation.

A

We've been working on providing a much more consistent experience around disabling features in the gitlab settings and we've been focused on the the project settings so, for example, turning off things like the analytics tab or the and we're working on the operations tab. And here the the purpose of turning it off is not only just to to make sure that you're not exposing functionality that you don't want to for your project, but it also helps keep a tidy or left nav, and so we're going to be extending this pattern.

A

A little bit into the group level with the analytics feature as well in 13.8 and last related to settings and navigation, is um we've completed some technical discovery around um searching within a settings page, and we have a proof of concept that we'll be working on it'll likely be shipped behind a feature flag before we roll it out to all the the settings pages, but in 13.8 we're going to be working on making the the larger settings pages searchable within the context of it, and so there's a little um proof of concept.

A

uh Snippet already defined, and that's in the issue we'll be applying that to one of the core views in the project settings and then we'll be repeating that pattern in 13.9 and hopefully shipping it across all of them defaulted to on and 13.9.

A

So that's all I wanted to cover for today. I guess again take a look at our planning issue and let me know if you have any questions or feedback thanks a lot and I'll talk to you in a month.