GitLab Digital Experience, 20 Apr 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Retro - April 20, 2023

Description

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

A

Hi everyone welcome to digital experience. uh This is our iteration retro meeting today's Thursday April 20th we'll go over some of the things that went well and some of the things for improvement uh over the last two week period. First, up for things that went well is Barker.

B

Yeah I I just want to say, like super good job, Laura and John, we figured out a release process for our localized nav.

B

um It's adding lots of new functionality to our site and we're going to have a separate branch that we're going to start stacking all of our changes into um so just really good job figuring out what that process is going to be and doing it in git lab. So it's transparent and it's documented right. There.

C

Plus one plus one to all of that plus 100 to all of that I think it looks so good um for anyone. That's not in the search now support team like definitely go. Look at the release, video or pop through some of the links there. um If you want to see all the great work there learn.

B

uh Yeah and the second one is um just props to to John that language selector is so cool and it works. So we're gonna be able to to build lots of great stuff from there um and Laura's already done that by building off on the localized nav. So I'll pass it over to her.

A

Yeah uh I met with John and he pretty much had this thing built and had already figured out all the conditions for which language should be shown at which time uh and I just had to like take that piece of code and translate the nav with it made my job very easy. So thank you John. It looks so good uh Justin.

D

Shout out to Trevor and Margaret um the developer survey page looks amazing. Even without some animation still looks, amazing, hopefully get those in. We have three more releases.

C

D

This um developer survey each quarter so definitely add them in make it uh very sparkly and I. Don't know if Margaret that was years um shout out to Megan or helping with the pipeline stuff.

D

B

A shout out to for helping out uh with the pipeline and just getting.

A

uh The delivery page out.

D

And then another um event, one one think Mateo and Trevor again for the commit not commit World Tour events page. um It was supposed to launch this week. There was a delay on the events team totally fine, but we were ready. We were good to go so makes us makes you feel happy that we were all ready to lunch thing super early in the morning, but launch next week.

E

Yeah, the first one up for things to improve on um and I put this up before. I realized Parker made an issue. um This is just related to the the memory leak stuff related to the survey page um Barker liked the issue there. So please go take a look if you're not familiar um if you're experiencing issues with Mr builds, um I think Laura found a way around it for now until we can find the root cause, but um yeah I just wanted to bring that up. If anyone wanted to take on that.

B

Yeah, let's use that issue to link all of our work into there and get it all documented and then get it fixed. That would be cool.

B

um I had number two yo: do you want your work to show up in the change? Log use those semantic commits, or else it won't be there. So I've been seeing a ton of Mrs go through and I'm having to add them.

B

um Also squashing your commits down to one would super help with that they make you do that in the GDK Miracle found that one out, so that's just kind of standard, good coding practices um so just FYI there.

F

um We can set our repo sorry to like automatically swash commits, so you don't have to click the box and maybe that's just something we should do anyway.

B

Yeah we could do that and then I think would that just take your last commit and make that the message. So, if your your last commit is semantic I think it's the very first one. ah That would be something to figure out. Let's make that an action item.

B

G

Thank you um well I'm, putting this for that game for the for our assets, because right now, uh every time I do a pull, I, see new images. So every time we do a new page or every time we add a new feature, always a new asset uh comes around, so the project is growing a lot. We have a lot of images, a lot of assets.

G

We have been patching out um the assets, removing duplicated images and stuff, but I believe the the main problem is still there and I believe that having a bucket or a server or any solution that gitlab may give to us will be very good for the project in building times in in a location, space and everything. Maybe uh if we remove all those images and move them to a server, our project will be faster to um to build and maybe will be more performant uh when uh moving into production.

G

So I I just wanted to put again in the spot um this topic, because, as our localization will have different assets for each language, it will grow a lot. So maybe, if we prevent that before happening, uh would be really awesome, uh that's it! For me, that's what he is suggesting.

D

Take it back on that just a little bit um CMS might have to resolve some of that. If, if all, if CMS does have like a cloud, damn that we can put off our images to that would help to resolve that yeah.

C

D

I think we're bumping up into certain elements and we're also because of how next webpack does things. We are also cash busting, which is every single time, so it actually reduces I mean it causes every user to like re-download all the images that are going to Cache them on their computer. It does obviously hit our performance scores every single time. We hit a build, something like that. We could think about too, like do those need to stay within, like the next build processor that I live outside of that and we're just calling to those.

C

D

Be another way for performance that we could help with.

D

um This next one is kind of from Dennis. um Just wanted a shout out to make sure that we were adding forms to our page that we keep that push in mind, so it can be tracked in the data. Later correctly.

D

That's pretty much. It was um related to the developer survey, just something that we can keep in mind. You just want me to like call it out, and it's retro.

B

We we had a couple Pages push this iteration for localization that have forms on them sales and free trial and then also some forms on the newly migrated company pages. So if you did that, can you go and check that those Marketo forms have um that push? That would be great.

H

For the company ones, uh I don't see like uh uh thing to pass it in the documentation. I mean there's no company Pages there. So maybe we should ask Dennis what we need to push.

B

Yeah we should do that.

B

um Let's do an action item, one to ensure localized Marketo forms are pushing the right data and then we can just do the company pages in that one also and kind of just pass it over to Dennis to look into.

D

About last, one and Laura has some good points coming up with it. um We've seen this before, um but whenever users with a third party people and it's harder when it's links are in emails and.

F

D

Press release system there's no way to pull those back up to them. So when someone links to any page, even our Pages, like the platform page that has that features component.

F

D

um Query parameters that then, like you know, deep link to a specific uh stage of process. We don't have a trailing slash. It breaks the JavaScript on the site, so something we need to one make sure that, like we're, checking and testing, if we see something like that going out into if there is a way to look into this, it's something that we've looked into before.

D

It was never really a good redirect regex thing, but maybe there's a better solution now that we can think about. But that's some of the uh might be something we can dive into it's corner to see. If there's a better way to handle that, and still make sure like the biggest thing is that we can still we don't strip the UTM. We don't just like make sure we regex it add that drag slash, and then you came back in before the page loads with all the analytics track with it.

D

A

Yeah I was just writing that I'll look into seeing if there's some rejects that we can do to do exactly what you just said at a slash in at the end of the URL and then append the UTM parameters. But yeah I, don't know how easy that'll be, um maybe Lauren still typing in there.

B

This is just the off the cuff thought, but is that trailing slash standard for websites? I know it's needed for SEO.

A

That's why I added the trailing slash it true, um let's cause Hannah I, think Hannah said to add it.

B

D

Really it's a weird bug too, because the page works like next routes work without the trailing slash and the UTM code, but yet JavaScript won't run whether there's some bug within the code itself. That is not allowing the JavaScript to run or if it's something else, that's like blocking it like. That's, where we're running into like the big ratio like do that, like maybe there's there's.

H

D

Two two ways to think about this: do we fix the bug, so you don't need the drilling slash if there's it doesn't and it won't break anything or forget a way to like append that to.

F

D

B

Just put John's comment in there bought the trailing slash for the site map.