GitLab Growth, 24 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Reviewing the Initial CI Setup Exeperience

Description

Thao walks Mike and Tim through the different experiences for getting set up with CI.

A

B

Right so we're here today.

A

Too, I'm so sorry todd michael um we're here today to to check out the ci kind of initial experience and setup uh for gitlab.com user, so that within retention we can look for potential opportunities for experimentation around that experience so that we can drive higher throughput, more adoption and therefore better retention, renewal rates. uh You know nine months after so I'm going to go ahead and share my screen and then how it's going to direct me through getting the setup on my own account.

C

So, instead of starting we'll start with the simplest use case, um which is when a user creates a new project or already has a project and want to start using gitlab ci- and I say by simplest, the more complex one would be if they already uh they wanted to use an external repository, let's say they're wanting to integrate their github repo with with a gitlab ci. But in the simplest scenario the user has a project or is creating a project in gitlab and they want to get started. um Yes, so you're creating a blank project.

C

They want to get started with ci. um There's a couple so now that they have their project created. What you're displaying there michael, they would go to the setup ci um uh it's in yes, yeah right there. You click on that and for a brand new project, and um so there's a couple things they can do here. The simplest thing is the user actually applying a template because there's different personas, um you know a more advanced author may either paste in or start authoring right here or they can.

C

If you click on the drop down for apply template, they can choose from existing ones that will, depending on what the application is that'll just insert for them. um uh You can choose either yeah, so the ruby one's a little uh more detailed, but it works. It basically gives them everything they need if their application is using ruby and the commit message is already inserted for them. This puts this in their project. Repository and all they have to click is commit changes button at the bottom.

A

So just to pause here for a second. So when I come here it's you know, it's initially.

B

A

What if I was someone who's just like interested in getting this up and I'm not a ci expert, I've never really used it.

A

Where what would I go to or like what resources do we have that? We may want to potentially surface here or um I'm just trying to figure like for me not being super familiar with yeah. I come here and I'm.

B

A

Of like, oh no, I'm I'm now lost it's just a blank page. It's asking me to type. I see the template drop down, but I I may not even know what those templates are. So I'm just wondering if there's even some initial things we could think about on this screen um like are there? Is there a documentation we may want to point to, or anything like that? That's like could help me understand what ci can do for me like I've. I've shown some interest in it.

A

I've clicked the setup button, but is there additional kind of coaching I can get here.

C

Yeah, so probably the first thing is to send them to the um the introduction or the getting started.

C

uh Let me let me copy it here, I'll drop it into the so maybe on this page it would be nice if we linked his to maybe that documentation page, which is just talking about um after the brief intro about getting started. It talks about creating a gitlab, ci yaml file. I guess I was assuming that the user would have already read through this or they go to create their project and click on create cicd file, but you're right it. That might not be the case.

C

A

And I'm probably not the you know the core use case, because someone doing this probably is more familiar with it than I am it's just one of those things that if I was exploring- um and maybe you know not as familiar it would be nice to have do, do you happen to know? Do we have any kind of tracking on like entrances to this page versus set like the setup success rate of this phone.

C

uh No, but recently last week I was talking um to james the pm for for verified testing, and he referred me to a document where the tech writers are tracking, all page hits in the documentation, and so I realized I could start monitoring the page hits to to all of the ci relevant documentation page and then try to figure out some kind of correlation between that and um adoption of ci.

C

I haven't gotten that far yet on building out the connections there, because we were talking about how I would go about creating a funnel, um for you know my performance indicator so.

A

Yeah yeah that would be really cool to see here as well like if there was a let's say, 10 of people who get here, set it up or 80 like that, we would. We would approach those two things very differently.

C

Yes, I the the thing that stalled me out was: how do I connect the visits to this page and know that's the same user that belongs to a project that has a gitlab cieno file, set up right um because it's it's it's not it's.

C

The at the closest I can get to identifying the user on those page hits is page, uh there's a it uses, google analytics and there is source as a field that captures where the user is coming from when they land on that page and the pageview is being tracked, and so you made me think that one thing that we may be able to track is: if we link to that documentation, page from where you're at when they're creating their yaml file.

C

That would be the source we could try and then and then we would go okay, for this page hit the source was, they were on the um the configure. Your ci uh create your your your yaml file, and then we could see was that was the yaml file from that project? Did it trigger a pipeline to know that it was you know, even even if the pipeline was not successful, we could say okay, that kind of connect them somehow that way, but right now yeah we aren't linking to that documentation.

C

um One thing that you, um I probably should give you a heads up about, is very recently um jason yvorska and I were talking about how we want to change, how we want to steer users towards the the web id the the the for where they want to edit their gitlab ci yaml file, and so this this editor here will probably slowly play less of a role when the user is is starting off in creating their cicd pipeline and they'll get directed to the web id because we're going to have more guidance to the user on how to create their file and how to both author, the syntax, as well as helpful tips and tricks there.

A

Does the web ide offer you more flexibility to do that? Is that why.

C

um There's there's more right now: they've already built out more um uh warnings and helpful tips and tricks when you're kind of when you're authoring incorrectly, for example, um let me find yeah so.

A

It's already baked in there, and so the idea is just point: people there, instead of the just the regular editor here.

C

Yeah this this plane, editor, which, which is pretty stripped down uh and this plane editor.

A

C

Thank you, uh this plane, editor is, is uh pretty bare bone and I think, there's a lot of assumption of expertise in using this, and that's why you don't get a lot of guidance on here. Let me let me find the issue that I'm thinking of that uh there's an epic.

B

B

Okay, oh that's not! It.

A

While you're um looking for that, should I go ahead and commit these changes and see what's next yeah yeah.

C

I'll show I'll find that later um and okay, so a couple things that happened, you'll see uh at the top. Under your name, this gitlab ci configuration is valid, and so from that editor it does get run through our ci linter to check that. Obviously, it's valid also because it's from a template- and we know the template- has all the correct syntax, but now so that now the user has a ci configuration and if you.

C

Did you just open, read me to the right at a separate time.

A

I did yeah, I don't really.

C

Learn learn more sorry.

A

Yeah, uh do you want me to go to that page or.

C

uh No, but that was that was interesting, that you did that I think most usually would see that and want to go to this page and see what there is to learn.

A

Yeah and my thing was, I clicked it and it didn't open a new tab, and so I wanted to this is one of the things with gitlab. That kind of is hit.

A

C

um So once they're they're here I would, I would guess, I'm just guessing what a new user would do is they would go back to their project and see that they have this in the roots uh uh in the yep? Oh, that is.

C

Is it ci experience yeah, so you'll see it right there in your your first and only file um is that so that is one route that a user would go through to to set up their cicd configuration is to use a template, um and then they would choose the template based on the type of application they were creating.

A

So I see a failure here so, like my my again, not not familiar um user experience here would be. um Oh no. I did something wrong like I applied the template, but I didn't something I did was wrong. So what I said like as a user I'd, probably click on this, and then I see a bunch of x's and I'm wondering.

C

uh Okay, so it's looking for um so it's looking for application um code files, that's not in your project yet, and so it's failing these jobs that are built in so we chose the ruby template, so it expects certain files in the in your repository for a ruby built application. So that's why.

A

I got it yeah, so most users wouldn't have that experience because they probably have some code.

C

Right right, right, um right, the they would choose the template. That applies to the the application files that that that would use that pipeline yep.

A

So maybe before we go for like super high level, what are kind of the prerequisites that you need um in order to get the value out of cs so like before? I were to go into this experience. You probably want you to have uploaded your your repo and got your files all like. What, in your mind, are the things like the you know: three steps, five steps whatever it is, that should be done prior to going into that experience, so that you get value out of it.

C

Right, um I'm looking through the documentation, because I think we actually call out the specific prereqs that you'd want to have in place to set up c ci configurations.

C

We recently updated our documentation.

C

C

Where I should be grabbing.

B

That okay and create a file name hold on a second.

A

While you do that, I'm going to pull up a document that is helping me think through the framework for this, and so I think it will help help. You understand why I'm asking to set up things, because it's a big part of activation, just kind of stepping back from the aha moment, so that you can determine all right. What are the things we need to have them do before they can experience that aha yeah. So here it is so we're trying to get you to this habit moment.

A

um Which is using ci getting value out of it, and you know kind of more likely now to retain, and in order to do that, you've got to get to the aha moment, which is like that first time they experience the value the first time the pipeline passes, or it fails and catches an error that has, you know, saved them time and energy and before that is the setup moment, which kind of what we're doing now.

A

But it seems that there's actually a few other prerequisites before the ci setup moment that are also part of that setup. um So that's why I'm trying to just understand all of these things so that we can think holistically about that experience.

C

Yeah um yeah, so so yeah. So even before, that's as part of that setup moment, or even before that the assumption is, you have code that you want to build test and deploy, or maybe just build and test.

C

So maybe that's the first thing is they have in their project files for the code that they would want to build and test and then once they have that, um because when you create a project, um for example, go create a new project and we'll back up, because I think we skipped through something too quickly.

C

C

Okay, um can you click on create from a template um to the right? We're not gonna, do it, but I'm just I can't remember gotcha, so even from even before a blank project.

C

If, if the users want to even take a greater shortcut, they would even choose a project template, but I don't know how basic you want to go or, for example, go down to like 10 from the top pages pages, um get gatsby uh yeah that one, if you, if you preview that template um it'll show you not only it will have the code like sample code files that you would need for that. It also should does it include. It also has the example, a ci yml file.

A

C

Probably the very very simplest thing that a user would not simplest, but um the quickest way for them to set up a project with all of the necessary code files and a built-in ci cd yaml file or ci file that that pertains to that type of code. Build and testing yeah.

A

So is it fair to say that if you're creating a project from a template, you have ci built in already so you're.

B

A

Of that kind of.

B

A

Curve we saw so that's interesting because it could be. There could be something that's actually related to this more so than actually ci itself potentially. Do you know what I mean it could just.

C

Be that right if we wanted to get started? Yes, if we want to make it really easy for users, we really invest, and you saw there were a lot of possible project templates. If you go back to the the drop.

A

C

That uh and we're just in the preview here, um there's 24 built-in templates there uh and um a lot of these towards the top or the more commonly needed ones, and so it's almost like a turnkey single button use this template. It puts everything in there the code files you need, as well as the ci gitlab ci yaml file, and then from there you just modif.

C

The idea is you start from a template, but you modify it to what you need, but everything all the pieces are there and your pipeline would be green because it has everything it needs.

A

I wonder why we don't default to templates.

C

Oh, I didn't think of that.

A

You know, because I wonder how many people actually go to this. um Maybe that's something we could look at tim tracking, wise.

C

A

If this is getting you like 60 of the way there versus zero or five percent of the way like it seems like a good thing to default people into so actually I'm gonna take this. If you don't mind, this page is plain html one, because that's that's a language. I actually understand, and I could uh probably get this a little more.

C

If you yeah go ahead and use template yep, it creates the uh well, you have to name it and then it creates a project for you, and it has everything you need and you'll see that the pipeline will not have that failed red x that you saw earlier.

A

So is this basically doing an import of that preview project.

C

Yeah, not the one we've previewed, but for this one I think we've reviewed the gaspi one, but yeah.

A

C

Yeah- and this is a very basic one- you see there's only um very few files. There.

A

Yeah, it's probably just an index yeah.

C

And then, if you, if you go into the, if you click to go into the ci yaml file,.

C

Yeah um you'll see it's a very simple yaml file for this pages. It just has the one stage to deploy it, because there's no there's nothing complex that you're building and testing right, yep.

A

Okay, so maybe the templates might be something to look at the project variation.

C

um But yeah, actually that come to think of it. I, uh when I think about ci alone, I think about the easiest thing for them is to do auto devops, but for a user, that's just creating everything from the beginning. The project template which already has the ci yama file built into it, is probably even even simpler to get them started.

A

Yeah yeah, it's probably I mean it's something. We still need to research a lot and turn like how much of a use case is that someone like me doing this? It's probably a lot smaller than someone who actually understands it and knows what they're doing so. It might not be the right thing to optimize for, but you can probably also assume that the folks who know what they're doing they're gonna they're gonna figure it out and get it done regardless.

B

A

Probably just go to blank and build it off from scratch or import one and.

B

A

It good to go: where is the opportunity is probably the people that are more on the fence, that kind of understand it or a little intimidated by it, but want to check.

B

It out and if we.

A

Can optimize for removing the anxiety and friction and for those customers or those.

B

A

That might be where we actually see the biggest game.

C

Yeah, in which case investing in more and more templates, that could account for a greater percentage of all the possible use cases out. There would give them. You know a single button, click to get going.

A

Yeah yeah, especially um you know more of a long term play but like students, people just getting into development if we make it like. Oh, it's super easy to use, git lab versus github, or you know github and ci or whatever circle ci. um Then we just we get them immediately when they're, young and they're just getting started, and then hopefully they they stick with gitlab over any competitor or they prefer gitlab.

C

Yeah, you may may realize something too when they're looking at the project templates. Maybe we have something at the I mean if we're, if we're going to try to default to that tab, also, maybe have something that is a dummy template that really kind of walks through the anatomy of what's in a project template and what's already built in there for you these all these templates here are uh assuming that you know exactly the type of application you're building, whether it's using spring or it's an android app, and you go straight to that. Template yeah.

A

Yeah I mean even like a blurb here this prime real estate. Here um you know, project templates, get you set up with ci and everything you need to get going right away; click here for more information or learn how to contribute to our built-in. You know something like that.

C

You don't think that's already covered to the left there in the left panel.

A

I don't think it says anything about templates.

A

I scanned it, I didn't.

B

A

That's true, but I don't think.

B

There's anything.

A

Mentioned about, I think, that's the same, regardless of the tab. You're on.

C

A

So it's something that's something to think about again. I this is just me like spitballing, without having done enough research, so I could be way wrong on this, but.

C

No, it's it's good because you haven't seen this before and I look at it all the time, and so I think, there's a lot of assumption on um what the experience is, because I'm because I forget to look at it with fresh eyes.

A

C

A

It's good to get that that opinion once in a while, but I I'm probably off somewhat here for sure when.

C

You when you look at the the tabs the way it goes from blank project to more complex to the right of ci cd for external repo.

C

It's supposed to be from least complex, like a blank project to something more complex, but it doesn't necessarily mean blank project. Is the most user friendly for setting up? It actually has expects more expertise to use than going straight to to creating a project from a template that has everything you need.

A

Yeah yeah, it's a good point and I think it really does depend on the distribution of our user base. How many are those experts and could just go from scratch? It's also. You know people making projects that aren't for um well, potentially that aren't so much for actually building and deploying, but they could be an internal project for issue tracking or something like that. They're, not actually, shipping.

C

A

I need to dig in to the usage there a little more, I think, to understand what that typical is the typical yeah.

C

Yeah, but even for someone who's really experienced, um I just know engineers will tell me it's it's sometimes faster not to reinvent the wheel and just to go straight to something that has all of the basic styles that I need set up instead of adding them individually on my own to a blank project and then editing all of the ones that are already there based on the template.

A

Yeah yeah, so it's nice to have that boilerplate yeah.

C

And so maybe create from templates should be the, if not the first tab, the tab that you default to when you go to this view,.

B

C

Yeah I mean we keep this order of um uh most blank canvas tab, tab to the far left where there is now and then more complex but defaulting to create from template.

A

Yeah, I mean, I think we want to get ux's input on that. I'm not sure I don't know what, if it's kind of weird to default into the second one versus the first, if we would want to switch them.

D

A

But yeah that's I mean that's probably the most nbc ways just to somehow have that tab select without any other structural change to the page.

A

All right so, let's say that uh you know I've got that set up.

D

Sorry mike I had one quick question I didn't know, I was muted apologies. I was talking away there, I'm wondering why is everyone ignoring me um on that create um project page I get a different screen to to mike, so I've got four boxes. um Is there an it is? Is there a particular difference between where I end the entry point um when I create a new project? I'm not sure if I'm wondering if I could just quickly share my screen mic.

A

Yeah I'll stop sharing for.

D

Sure, thank you.

D

A

Interesting, I have get lab next to naval, but I doubt that I bet you do too.

D

I believe I do, although it's not showing up.

D

But I have this page and I'm trying to wonder what the difference is between the the two and the reason I'll show you how I got to here so.

A

Oh, that's your is that your no that's not! You can say that.

D

So I've just got a private group.

B

D

I go into a new project and it takes me to this page rather than the tabbed approach. um Is this just the just the starting of the process? So if I clicked on blank ah so that I don't have a tab approach at all, is.

B

This a test thing.

A

I'm gonna try to add.

A

If you switch get lab next on, does it change at all.

D

uh I keep on forgetting how do I.

A

I can turn it off more easily. Actually, it's sorry.

D

How do I you know I've totally forgotten how to turn it on?

D

How do you turn it on.

A

uh I forget too, once.

B

A

On it has the next thing there and you can just get.

B

D

What's the url, is it just next.gitlab.com.

A

Yep, that's exactly it.

D

Okay, let me switch it back. No.

A

I'm still getting the same thing when I'm not on next, so I don't know. That's weird.

B

A

You in a private project versus a public project or a group.

C

I went I went to um create a new project as well and I get the same view that michael gets.

C

Let me go back. Let me see so I'm in. Let me compare to what michael has and then. Oh that's interesting, stay there for a moment like uh stay there for another team, we're both. So I can go.

A

What was your entry for? That.

B

D

A private private group.

B

C

Okay, let me go sorry. Let me go to a private group of mine, then just to make sure that I'm doing the same thing. I.

A

Think my mind will also private okay.

D

Yeah, I thought that's why I asked because I um I thought your group was also private mate.

C

Yeah, no, I get the same experience that michael got so.

D

C

But you know what here's the difference you're, when I go to create a new project in your url. uh It has new question mark, but then it has the namespace id if go to the top of your url and remove everything from the question mark to the right.

D

D

It looks like this must be a test.

C

D

C

Interesting that it randomly takes you, but I.

A

Wonder who's running it too.

D

Yeah someone's running a test in the.

C

Command line uh interesting, I haven't seen that what you're, what you're experiencing.

D

Or it's um it's something that's been released on the feature flag um with maybe percentage wires of traffic.

C

Yeah, can you take a screenshot of what.

D

You have there.

C

And just go to the questions um uh slack channel and ask: is this: is this the result of a testing that's done and then I'll um I'll uh ping me on it as well, so that I can add my screenshot of what I see what I get to create a project.

D

Sorry, for that.

A

Diversion okay, so I'm sorry I was just kind of bouncing around and then, if I go back to that project, the recent projects never works now.

A

Sorry, I don't think it's the projects within the group view. Oh they're just listed right here.

A

Some of our nav trips me up again.

A

The many layers uh all right, so if I did that, so I'm set up it's my html project. I've got the email so from now on, it would just be like whenever I commit any code, it just automatically runs through those pipelines and that's it.

C

You're good to go right: yeah! Yes, you can, um in the left, nav go to ci cd and go to the pipelines page and just click run pipeline.

C

Go ahead and run pipeline.

C

Okay, sorry, you know.

A

I could try one of the like the ruby project too.

C

Well, it's it's running now, right.

C

Okay, so yeah, so this is because the user is using a template that has all of the required just bare bone code for an html project.

A

If I was coming from github and circle ci, or something like that, what would that typical process is like.

C

Actually, go back to click uh on new project.

C

You'll see that in the information to the left, it'll say to use third paragraph to use only ci cd features for an external repository like github to ci cd for external repo. So it's the far right tab in the main window, cicd for external repo and then the user would be guided through um right. Now we support github and then a specific url to the repo, and so they would click on one of those buttons and and either.

C

If let's say it's, github, there's instructions on how to put in the details uh of that repository to connect it to the their ci cd pipeline in gitlab. Interesting yeah are using.

A

That or we ever.

B

A

um Like get them to use gitlab for everything else as well.

C

um So so for those folks that have as heavily invested in get home, this is the way that they can start using. Git lab is just connected to a for use, get lab for ci.

C

In fact, there was, uh and there is a good number of users that are set up that way. There was actually a community contribution in 13.3 I was. I was looking at it in the release post that their their changes were merged in, but um we didn't, we don't write up every community contribution, but the relevance of that uh is um they wrote.

C

They wrote a addition to when you're, using external repository being able to call out the name of that repository, in addition to all the other attributes that we we specify. So I know it is important to to those users to have.

B

C

Integration working between github and gitlab.

A

Yeah interesting well, let's say I was doing a full migration or let's say that I was using like uh circle ci or just a different ci tool outside to get lavendail like I'm gonna combine all this into get loud. I like get lab for the repo and everything, but I want to condense all the tools. I'm using reduce the complexity in my tool chain.

A

What they would, then that is um was that the previous would they do an import? Well, no, that would be the entire project. So would they set the project up first and then go into the ci setup, like you showed me before, and then like paste in their code kind of thing,.

B

C

Not every so not everything from circle. Ci is going to translate to the syntax that we support, forget labs, yayamo file.

C

I I just put in the zoom chat there: the documentation that we have to guide users migrating from circle ci, because they we call out first of all, what the differences are, and so, if you scroll down to circle ci example with workflows it, it shows the that in ci, crisco circle, ci and how that same thing would be authored in gitlab, ci cd, so that they can see the difference. um It's I don't think it's a it's a clear copy paste for them. It's it's. They would kind of have to rework.

C

When I say syntax, we use different keywords than they do, and so it's just guiding them on what they would have to to change um and basically re-author.

A

Where is that section, I'm not don't jump.

C

Let me let me share my screen. um Oh oh.

B

C

So um so the link I gave you should land you here and then it's showing right here. This is the circle ci example um and then how that same thing would look with stages in gitlab, ci cd.

C

um So, like our syntax, just the convention of how we set things up in gitlab ci, we call out the stages at the top and you'll notice that you don't need to do that in circle ci and then we within each job, we reiterate which stage this job belongs to the first two job aligned to stage build and then the third job is for the stage test. um They don't necessarily do that in theirs. So it's it's. You see how copying pasting this in to the gitlab ci uh yaml file is not gonna work correctly.

A

Got it okay yeah this is super helpful, yeah gitlab one looks a little more um condensed or efficient. If you want to use got, it is, do you know, is there any discussion like industry-wide about trying to standardize on that, like any other kind of language.

B

C

I mean for the end user. That would probably be uh just uh something they would be happy for, but it comes down to. We think ours is more logical and obviously our competitors think their way of creating a pipeline is more logical. So I don't know yeah.

B

It would be a tricky thing to do.

C

Yes, it it's it's the same thing of we would like all phone chargers to have the same uh adaption point right I mean and not to have to use adapters, but getting there is is another.

C

Is who's going to win out who, wherever.

A

Right, well, it's a kind of competitive uh mode. You know you don't want to make it too easy to just take the pick up and leave if you're a circle or anything else. So.

B

A

Especially if you're only ci yeah, so I can understand that as well.

C

But that that example there it clearly shows that um even circle ci, even though the way they set up their configure their jobs in their pipeline is pretty close a lot similar than what you would see in a jenkins job compared to get lab. But even so you see there's differences that um they just don't.

C

We couldn't build a translator that automatically shifts it all into the way. We would write a.

B

A

B

C

Almost that time, but did I answer the questions that um you had for this session? Should we have ongoing? I don't know what is helpful to you. Yeah.

A

No, this has been super helpful for me. Thank you so much um I don't know if we need another session just yet. I think what will end up happening is tim and I will dig in more and more and then we'll probably get a list of additional questions and maybe then we'll reach back out and regroup. We're also going to try to keep an eye on and monitor all the research that's kicking off with lori and others around this.

A

So um it's good timing for us that these larger projects are kicking off, so we can kind of feed back on them. But no, my goal for today was really just try to understand it from a customer and new user perspective, and you definitely got me all the way there on that. So I really appreciate it and um well, I think, for now, we've got some homework to do and we'll definitely circle back with questions when we when we come across them. But this this has got me everything I needed to to start that process.

A

I don't know if there's anything that you are curious about learning more or you have questions while we have foul on the line for a few more minutes, no.

D

That was um the only question I had uh was just in regards to the that crazy project page and I'm sure we'll get to the bottom of it soon. So from me, um no questions. Thank you. So much, though,.

C

Yeah um one thing I wanted to mention I just put in the zoom chat a link to the epic. I mentioned that we're trying to move away from that that very simple yaml file editor that you first get when you create a project to steering them towards using the web ide, because there's already things that the create team is building into the web id that guides the user in authoring.

C

um So so it's a heads up.

A

If I pull up a yaml file like a gitlab ciel file and I go to the web id, I should see some additional functionality in there.

C

Well, if you, if you pull up the yammer file and you click edit, it will instead of taking you to the editor that we were just looking at um when you create a project. It'll. Take you to the web ide editor, since that's going to be the future, where we're going to steer all of the editing of the ci yaml file,.

A

But if I go to the web ide with one today right now, I can see what those those changes are.

C

um Not yet not yet um the the issues that are the issues that are in this epic is to start introducing that making that possible in the web, ide and, and then the very last issue in that list, for example of that epic make web id the preferred experience for editing. That's the one that's going to achieve it! It's it's our current milestone, oh yeah,.

A

Well, I will definitely keep an eye on this awesome. Well, thank you so much pal. This has been a huge help, really appreciate it and uh we'll talk soon.

C

Okay, take care.

A