GitLab Digital Experience, 3 Nov 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Retro - Nov 3, 2022

Description

Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/digital-experience/

A

Foreign welcome to digital experience team. This is our retro video, where we go over things that went well, and things do improve on from this last two week, iteration today is Thursday November 3rd uh first up for things that went well is Nathan.

B

I was not ready for that. um Well, usually I'm the late one to the Ducks I'm doing it last minute. Procrastinator um yeah, despite I, feel like it's been a little chaotic like the last couple weeks with all these urgent requests, but I must say we're delivering and like I I, don't know how we're doing it, but we're doing it and so like a huge pat on the back to everyone for I.

B

Don't know how we're doing this, but but getting everything out and together Gathering all the requirements and push into production like we're, hitting all the deadlines which is which is unbelievable, uh but yeah. That's all Jess you're up next.

C

Yeah kind of tagging on to that a little bit, I just wanted to shout out Megan for doing some really awesome work. The last Sprint um there's been a few instances because of all the chaotic quick turnarounds where, like we didn't, have the full ux UI done, and so she built things without mobile or without or like from a screenshot um and just like crushed it, like barely had any notes at all so awesome, job, Megan and Pastor or Lauren. Sorry,.

D

uh Shout out Laura Miguel John 2.0 nav, that was a doozy we've been like Rapid Fire for the last 24 hours, because you know you ship it to npm and then you bring it down and then it there's these weird Phantom bugs and like you, can't drill down and yeah so good job.

D

We got that through and there will be a quick iteration, I'm sure um and then big page releases about gitlab and the analyst pages are live so Laura miracle and Carrie um great job getting those ones out the door and then glm tracking get lab link management um is going to be added to our free trial button. So it's a hundred percent tracking from website over to the product that lets. You know what page they clicked on, that free trial button huge. We don't get any cookie loss or anything.

D

So if that works and the data looks good, we could Implement that elsewhere, um so good job Miguel getting that in and then we've got a real change. Log coming like a real one, that's gonna automatically tell us what went in.

D

um So that's in the works, it's kind of like awesome FYI for the group that that's gonna happen soon late. Then.

B

That's cool is it. Is that a change look for nav or for everything.

D

uh Buyer experience and.

B

Then we'll get a.

D

Change log for nav also but Bruce.

B

uh Yeah, just congrats I, don't know how this one's left got all the rug but Laura and Lauren on uh Lauren you're. Officially, a manager and Laura senior super exciting so congrats to both of you, nice dab, Laura.

D

Dream Team super.

B

Excited we'll have to celebrate in Palm Springs, so oh.

D

Man got plans um shout out to Megan she's, pretty much just been running the major league hacking fellow program and doing an amazing job at it. So yeah just awesome, I literally couldn't do it without Megan. So awesome.

D

um I'm next things to improve on in this whole nav release figured out that we can't debug um the navigation locally in the dub repo. That is a problem. So how do we fix that um Nathan? So you got some yeah.

B

Some not good news uh yeah, you can't really debug a node module like the only way is in node modules but you're looking at like minified code and that's not fun, but it is a way um I guess. The best solution is, let's get out of www. So I don't know if we can somehow Fast Track that but uh yeah John. Do you want to I think you have another idea.

E

Yeah right now, in order to debug um the person navigation in buyer's experience, we are using ER link.

E

um It says, to deploy sorry release new versions into a VM, so I believe that could work also for I'm, not really sure, because I I don't work so, but if that's possible, that would be a a good solution.

F

I I would say that uh it would be possible with the young Link um I I I I've tried it in the past and we did that repo and I've done it with jarlink, but yeah um just gotta make sure it works.

A

Yeah, something is broken with the import where the entire package just doesn't even get brought in, like it errors out. um That's that's the issue. Yeah typically yarn like should work, but there's something wrong with the actual import. It can't find. Buyer experience navigation, um but we just didn't have time to debug this particular issue.

A

um So we'll look into that as uh this next iteration.

D

Let's get an issue created for that yeah um because that that presented us with some challenges, as we are releasing this major version um and then the next thing is um the nav items got to be in the Dom for SEO and also just makes it easier to like figure out things and debug it and like drill down into class names.

D

um So we're going to work on that next John. Do you want to speak to how we're going to do that? Maybe.

E

um Yeah I will probably do a drop down from scratch, because in this situation, I used a library called floating view, but I didn't find a way to hide in the dome uh these. um These links, because the library didn't allow me so I will refactor the navigation, remove this library and do it from scratch so um that that is a good thing, because we can have custom um behaviors in the in the in the navigation and right now we are limited for the library.

E

I choose this Library um thinking it was in my it satisfied our requirements, but it did not so sorry for that.

E

um Next one is Jessica.

C

Yeah, just a friendly reminder to make sure you're, always using um slippers textiles in the code whenever possible should be almost always um just because like if we update the typography and slippers, uh we want the all those changes to be pushed through every page where they exist, so um just double check that that's happening. We're seeing it both in like really old pages and like new Mrs, so just want to make sure everyone's um got that on their mind um and Laura I think you have a good point. Chad.

A

Yeah I think for the most part we try to use the slippers typography component, um if, like the only time in recent memory, I can think of not using. It is. If there's like a block of code that says, like you know, gitlab's Mission and somewhere in there is like a link like a little text link um we use markdown to render that and then we have to kind of style it manually ourselves. So it doesn't pick up the slippers, typography Styles um I could be wrong if we're not doing that anymore.

A

uh But that's the last time I remember not using slippers. Typography, um oh and I, see Lauren is uh typing.

D

Away um yeah, this came up in the the mlh office hours we had um about the slip typography component. It was like well we're we're getting different typography on the site and our thinking was it was because of markdown.

D

We can't put a ton of mark down in the slip typography component, so then we're like rendering our own styles um so we're gonna try to build a typography component that does accept markdown, um and that has to do with next and the content, module and there's a plug-in. We can add to slippers that enables next it's more of like a spike. We're going to look into it.

D

D

G

Yeah, uh so this is a recurrent one but content. We got content for some pages that needed to go out like 30 minutes before our release, meeting Nathan and I and yeah. The last few hours have been a little crazy trying to get that in time. So so that could be improved.

B

And I want to add on to that actually um I know things get hectic and that, like you slack and we communicate, maybe informally or I, don't know if that's the right word, but issues need to be updated and unfortunately like something slipped through the cracks, because uh we weren't assigned these issues and the content wasn't added to the issues. So we didn't know that we were supposed to do the issues, um even though I did see I think the slack message like early in the week it just slip behind me.

B

You know I'm used to seeing like the to-do list and all things to do but um yeah if we can try and keep to our process and issues.

C

Issues, issues.

B

Dennis I think here up next, oh.

H

B

As you're typing.

H

Yeah, when there's new element just be sure to add the data GA attribute, um which is it's for tracking and so yeah or just tag me in an issue, if you're not sure like what should go on that element, I think I'm, the last one. So.

E

Yeah I added that comment. um So we have that new um item in the checklist for the merge.

H

Requesting plates.

E

In order to remember that, we need to add these attributes in the links, because we need to put it no links, and sometimes we only forgot. But we need to put back in.

H

Yeah there is a a section on the issue template, but it doesn't specify data. So maybe I can revise that to include the data portion.

H

um So, okay yeah, that's.

A

H

H

um Back to whoever started this meeting, Laura.

A

uh Cool uh if there are no other thoughts, um I guess that's it. Thank you. Everyone, and we will see you next time.