GitLab Digital Experience, 24 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Release Video - Feb 24, 2022

Description

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

A

Hi everyone uh welcome to the digital experience team. This is our iteration uh release. Video we'll be demoing. What we released for the past two week period uh today is thursday february 24th and first up according to our boards, is lauren barker.

B

All right share my screen. um Oh don't leave the meeting shoot. Okay, I can do this.

B

Share share: okay: there we go um so this iteration, I finally shipped all the visible stuff super exciting. So that's now in the product um that required two extra, mrs one for charts and one for omnibus, so that was cool to ship those. I still don't quite know what they do. But I did it um also added the add to cart event to the gtm data layer, for the usage tab that shipped with 14.8 as well.

B

um This retired js dependency scanning job just snuck in and it was causing a bunch of pipeline failures. So I I just removed it from our www repo closed out. This topic template layout changes issue here and I actually opened um a another follow-up issue down here for adding the faq schema to our topics and solution pages. That's going to take an extra plug-in and some um some more work.

B

So there's a follow-up issue there for that, but was able to to close that one out and um since I had some bandwidth I took a look at this: implement the um linkedin event, specific tracking, using the insight tag and as I looked into it, realized that needs to be implemented via google tag manager, so loot dennis in and he will be working on that.

B

So that's all I've got um next up is tyler.

C

Oh yes, um so screen sharing here we are stuff that I did. um Big ticket item was um adding the form submission event to uh they're, using a combined group and project form now for the onboarding flow. um So I had to like redo a bunch of google tag manager, stuff that we're doing. um There is also a um a follow-up to it for more events uh which the work for this is done. It's just it's in review um and I've.

C

Actually it's gone through one round of reviews, and so now I'm in the second review um so like I expect that I you know this, is it's basically done uh as far as I'm concerned, um I expect that to basically just ship and merge and and get out there, you know in the next 24 hours um did some work around some requirements for making sure that our all of the google tag manager, stuff we've done- is uh totally like in the clear legally speaking- and it absolutely is, um I think we were just like we had.

C

We basically asked questions that we asked before we started this work and we just like re-asked those questions and just to like triple check, and the answer was like yep you're good um and then I I just closed this issue out, because this already works. um The deploy script for the product, the production deploy script, has a cleanup script that runs and works to remove deleted pages. uh If anyone uh does encounter a scenario where their deleted page is not being deleted, let me know it's also.

C

It doesn't run every time, so it is on a timer. So there are some interstitial states where you may end up for a period of a couple hours like not seeing a page removed. So that could be the issue um and then other stuff.

C

We did in review apps, uh so works with laura on uh stopping the cookie banner from appearing in review apps, which I think is mostly an issue for people who live in countries where their countries take their privacy seriously, because it was never an issue for me, uh but I know canadians were probably having problems there. um So what happens now in the review? Apps there's two different solutions uh for both for middleman and for next and middleman. We can like very easily just not ever render one trust.

C

uh So that's what we're doing there and then in next. I have a little callback thing uh set up that, like checks to see a particular environment variable and then, if we're in the review app, it will close. It'll it'll render one trust and then auto close it. So you may see a flash of one trust, but you shouldn't have to like manually click a thing for it: um it'll just go away so um yeah. I think that's it for me and uh who's up next in the order.

C

uh Nathan is not here today, so laura it is you.

A

Thank you and yeah. Thank you for the the cookie banner thing. It's already been such a blessing. uh I will share not you, oh no. I should have planned this a little bit better.

A

You, okay, I didn't really want to give you my whole desktop, but here it is. Okay, so you'll see my kind of sad looking closed column. uh I worked on all three of these they're all uh code complete and in review, and so I will show them. First up is the install page. um So this sorry, my little zoom thingy is in the way. I know you guys can't see it, but okay, uh so this is the install page huge.

A

uh It has the kind of side nav stuff going on uh these top ones have their own like install instructions which pop open and can be closed. uh Some of them have, you know, highlight on them for if they're important, there's a little tooltip action and we have- I had a lot of fun, building out this little little guy. So that's going to be hopefully up soon.

A

I have some back and forth going on with nathan about um some a hacky bit, so I might have to do a small refactor, but that should be out soon uh and then also in review is the home page. uh So this is uh should look pretty familiar.

A

The only new part is, I think, tina showed this last iteration is a small update to the compliance section, so I snuck that in here as well, but everything else should be kind of what we're used to seeing on the homepage. So that is me- and I think next is javi.

D

Yeah, okay, sweet! Thank you, laura uh hi everybody. uh Let me show my screen. Am I looking at the right thing. You know, I think we're looking at the wrong one wait hold up yeah we're gonna, get really good at this, as we keep doing this more and more so uh this iteration, I worked on trying to integrate lunch darkly onto our repository, which was a lot.

C

D

um So I'm just gonna do a little demo, real, quick and I'm going to end up, recording a video and then updating our documentation. How this ends up working.

D

But if I turn this feature flag on and I save it- I reload the page watch it break like when I'm jumping uh it should uh it should work and it didn't, but it should so that's something uh we had figured out uh something that's kind of nice about the way that we're doing it is uh like in the templating, it's more explicit when we're actually using uh an experiment which I think will be nicer for all of us when we're doing stuff, uh and then I worked on trying to integrate uh gitlab es lint into our repository.

D

I didn't get much headway in this, since I was focusing mostly on trying to integrate lunch darkly and there's a lot of tests for things that are still failing. I think there's further questions for us to ask regarding what rules we actually want to enforce, uh but we can talk about that in the actual thread itself uh and then up next I have megan yeah thanks all right.

E

I need to share that one yep all right in this iteration um I added mermaid charts to the buyer. Experience repository um there's nowhere in these pages that we actually need to implement them. Quite yet, but the plug-in is there there's more information how to use it uh in the plugins markdown file, and there is a component you can integrate, um that's ready to go or you can just import the library directly into the page or component.

E

You want to work on um you're right that little zoom thing is in the way um next uh was adding shadows into slippers um specifically into the card component, but in slippers now we have variables for um are many box shadow variations and for the card component now there's you can specify it whether you want a primary or secondary shadow, and each one has four variations in that. So primary is not as dark, but secondary. Four is is very, very dark, so that is in prod.

E

Now next was adding the microservices topics page, I think we're all wrapped up on those. um There was a regression, not this one. um This I updated some header tags uh and a lot of pages, and you can look at this. Mr um a lot of pages had like either no h1 tag or they had an h3 tag with h2 tags supposedly in it. So a lot of things I swapped around and made that more semantic.

E

Today there was a quick update, there's a new remote playbook that launched today. So on the all remote page, swapped out that image there was a few regressions. I updated this iteration one of them was with the addition of the all remote page. um If you went to company culture uh it was trying to render from next, so it was rendering like the free trial, cta component and like nothing else, so I added that to the route ignore file. So now it's rendering correctly from the dub dub da repo uh another aggression.

E

I think jess had caught this one. uh There's some text alignment issues. So that's all sorted out um this one I caught. I think this is from an update of the slippers button, but this is not what it should look like. This is what it should look like, and it now looks like that again. um I think this specifically hit our topics pages.

E

um Another aggression. There were some borders around images that were not supposed to have borders, so that is fixed. And lastly, um there were some images that wrapped in like an anchor tag, they were not showing up. So that's fixed now this just hitting these two solutions pages. So a lot of regressions. um That's all next, I think, is jess.

F

A

Okay, so um I worked on get what I call the content gathering for ia refresh, so we're doing this information architecture refresh um basically went through about 800 urls one by one, just trying to figure out what we should keep. What should move into the new buyer repo, what should be deleted?

A

What should be redirected, um we're still discussing about like what should be deleted and redirected, but pretty confidently decided that these it's somewhere between 80 and 90 um pages, should be moved or, if they're not already moved into our buyer repo, or they might also be in that new page. So a lot of them exist already. Some are net new for the net new pages um went ahead and made content issues for all of them.

A

There's like 25 of them, so lots of pages to be worked on with our content team and what else is on my board and then this was just an issue that got promoted to an epic. So the other thing working on is now that we know what pages we're going to be in our buyer, repo um working on the navigation layout. um This is still work in progress.

A

It's still in doing, but just a little sneak peek of what we're kind of trying to go for it's a little bit more complex in our current um navigation. So a few more drop downs and whatnot, but work in progress, and I think tina's up next.

G

Okay, all right, um so I had uh you a request for an update on the customer stories page. um This is the page that we have now um so we've brought it up to date by applying uh slippers to it. So this is a new header with uh maybe it's rotating things doesn't work very well, because this is a figma, but you get the idea um which would change the content up here and the data points.

G

um What else do we have here? We've got also some filtering options to help customers and users find case studies that are relevant to them. uh We're calling them customer stories now pardon me and that's it um a second mock up for that also, which just shows the filtering option a little bit higher.

G

uh I was also the dri for the slippers maintenance. This iteration it was a short one, so I really only had time to work on the cards, so the biggest update here is that now we have a single card in figma with different options um I'm clicking over here, uh whereas before we had a card for every single one of these options for resources for blogs. um So I want to thank jess for teaching me how to do this also, so I didn't do this by myself by the way.

G

uh What else do I want to show uh yeah this kind of uh dropped on our laps yesterday, uh just a design refresh of the homepage for scope, but I'm just adding the new brand and maybe just doing some neat things there. It's not an estate to look at since we started on that yesterday.

G

So that's it! That's it for me, carrie I'll, pass it over to carrie.

H

Hi, um so this is my first time participating in this. um I I am working on some uh competitive research uh for our. Why gitlab page- uh and I can show you the google doc, just give me a second, because I wasn't prepared.

H

And I could share this too. um Let's see.

F

Let me share this page.

H

Okay yeah, so I've just been kind of looking at um some competitors um sites and seeing how they do their own. Why pages um I've kind of left some notes on the side? To um give my opinion on what I like and what I don't like about them? um Hopefully we can take things that we find um we all like and and can put them in to ry pages, but yeah. That's that's! Basically it so far.

H

I'm going to stop sharing.

H

Oh yes, I did onboarding too.

H

um Okay, sorry, I don't know what who is next, which.

G

One is next: okay, on my board.

I

Yeah, I think, uh since john is not here, I will be next um so sharing my screen right now,.

I

Okay, um so let me get rid of the zoom thingy, okay, so here's my port, um there's one at the bottom. The update all remote landing page was pretty much complete at the beginning of the sprint. It was just uh some small feedback that needed to be addressed, um so that was done this one. On top of that, the add the 1025 breakpoint was so the breakpoints we were using were generic.

I

They were good for a variety of devices, multiple devices and it was causing an issue where some devices that had this specific resolution uh were breaking pretty much uh for some components. uh So added this one to the two slippers for for those resolutions to work. Fine um also did an update on the on page navigation.

I

So I will show that so this one over here is the top anchor navigation.

I

So it now uh has that updated styling and also when on mobile resolution, it becomes a drop down which can be used to navigate to the sections. This drop down. Pretty much applies to all in page navigation now um also updated the these styles for the the single level navigation here and created the multi-level navigation for nested links.

I

I also fixed an issue with the buttons the button component from the slippers repo. It was displaying uh much smaller than intended. This one was just a small fix and also migrated all the button components. This is uh not using the button component that we had created in the buyer's experience repo anymore, but using the one from from slippers, so updated the components that we're using it and that's it for me. uh Next one is miguel.

J

uh Yep, thank you. Mateo. I'm gonna share my screen.

J

Yep, so um this iteration, um I fixed some issues. We were having uh with the partners pages and there was like uh changes in typography and swap, and the cta and some minor changes.

J

And, for example, uh we also eliminated the the line that was behind those cards and um we centered some text here and yeah. It was like a simple uh issue and then I worked uh with the migration of the analyst page. uh This is like uh almost done. It needs some feedback from dina and but it's already on the other side here we implement the revamped menu that mateo did and we also have like this combination of the fnq with uh some some copy and this other component.

J

That's that was created for this page and in the contacts uh I missed the filter buttons here in the future reports I'm still working on them. I probably will do it in mpc2 and next iteration, um but yeah. That's it from this issue and.

J

Also, I did the mistake of jumping straight into an nmr without creating um an issue, so it doesn't reflect here, but we did a two-line change in the video carousel component because it was a css uh property that was repeated, so it was, he was having kind of a strange behavior and next time I will create the issue, so it gets reflected and also I worked on this uh there's some changes to be done. There are some. um There are some uh instances where the uh anchoring tags have uh nested components or images and icons.

J

So if we apply the slippers link, styles and component just like that, it messes up with the the ui, so I have to look for those regressions and and yeah. That's it, and next is daniel.

K

K

Oh sorry, I don't think.

K

F

K

Me to restart, um but um uh well I basically work on uh ux situation. uh uh There are like uh several uh only one big one has several issues there, uh all of them related with the ux it's around 11. um uh I made the same. uh I didn't create uh specific uses, so it is not reflected in the board, but we have the big one. um One of them is um uh I I remove all the timing, tags and in all solutions.

K

uh So we have two columns now for for uh and also uh another one, uh it's uh related with um the default image. uh What we were using for for uh some heroes, it's in place now, with uh only the specs and vital hero, because we don't. We don't have a button right now to create a certain image for them.

K

Right now- and I also was working on uh stages of devops life- um I wanted to show you that it is basically done, but I'm still trying to figure out why I'm still having a persistent uh regression with that hero and also working on some.

K

Responsive inconsistencies with the stigma, because I think that's all.

A

I think that's everyone, um if you want daniel, do you want to send me the link and I can share the screen right, real, quick or do you just want to, I guess we're running low on time, but um yeah? Okay, maybe that's fine, okay! Well, thank you! Everyone and we will see you next time.