GitLab Digital Experience, 1 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Sprint Recap 2021-07-01

Description

Sprint Release Video agenda: https://docs.google.com/document/d/1I9Th3Q-AakOkE_-pmNtEzwwMDSqYKF5Je2etGdPTovk/edit

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

Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/

A

Hello, welcome to the digital experience, uh iteration release video. uh This iteration is ending on july 1st of 2021, which is today, uh and so we can just hop right into the things that are getting released. uh Barker you want to start off and I will do some screen sharing here. I'm not sharing my screen. I will do some screen sharing now.

B

There we go um so we released a new content type in netlify cms, all of our beautiful case studies are in there and there's a ton of them. Look at them all, so you can go in and edit them. You can add a new one um and they are there. um They take a little wild load.

B

um Oh there, you go and yeah. um We also added events in there, and um so now you can build um a event landing page in the cms and it's there you'll see it, um which is cool.

B

um There is handbook documentation for this, for the events also- um and I highly recommend you read that if you do want to use that event landing page right now, it's only turned on for local development builds, but we can switch it on for production, so just reach out to us and we'll turn it on and there's some some extra notes about some things.

B

In there um moving on, we launched a new red hat partner, page design and now all of our featured partners have this new slippers, landing page design and all the content stored in a data file and our um global partner marketing team is getting in there and editing the content using git lab super cool and we updated the devops lifecycle image on the solutions page. This one keeps popping up for some reason.

B

If you scroll down yeah that little circle image, um sometimes it pops up on the website and it's wrong so updated it to the right version and um a little bit of my sprint was um dealing. We had a incident four nine six, nine, uh some slippers, caching issues, but um I think we got that handled so over to tyler.

A

Yeah uh so uh big push here was: oh, that's the mr um for the get lab 14 release. We updated the homepage, hero section, uh super exciting and then uh built out a landing page for it as well.

A

We were able to do this super fast, based on all the slippers work that had already gone into a pre-existing page that I can't recall which one it was, but we were able to move really quickly on this and it was great- and I also had a lot of time, eaten up by our cdn issues as well um other than that. uh The other thing I was able to get out the door, though, was um we upgraded? uh Well, we didn't.

A

We had a community contribution to upgrade our middleman version to 4.4.0, which is awesome, because that version adds support for ruby3 and before this change we were on a like specific commit hash in our dependencies, and we are now back on like a semantic version, which just gives us a little bit like easier, uh tooling around like dependency management stuff. So uh thanks again to community contributors uh really excited to bump that up and next I think it is nathan.

C

uh Yeah so the first one uh brandon used to do all the experiments, so there's a big learning curve how to set up experiments. uh I set one up: it's ready to go, but I'm gonna wait because I'm off tomorrow and then monday's also a holiday. So I think I'm gonna. Do it tuesday just to make sure, because it's a pricing page, I don't want to mess around so tuesday. We'll launch that uh and then there's a couple issues that arose this week: uh marketo forums uh over the site they weren't submitting properly.

C

um So I found a problem in there fixed it. um There was another issue uh with the teams page uh that was taken up. It's okay, you have to click through these. That was, uh the footer was taken up like half of the the page that showed all of our faces on that team page. um Then there was another one with the pricing mobile uh thanks, jess just found it and we were quickly to fix it. But the carousel was broken. Oh well, um and then we put a new homepage banner.

C

So right now it's gartner it's going to run until the 6th of july and then the commit uh banner is going to go up on the 6th.

C

um What next we have uh yeah anchors for the epic or sorry, this one yeah, this one's a bit uh a bit tricky so I'll, try and walk you through it. So if you scroll down- um and you choose, there's three filters- so change the event, type or location type, and then, if you were to reload that page, it adds the query params into the into the url. So now you can filter before arriving on the page.

C

So now you can hit a link on a different page, come here and have the filters already pre-selected, which is pretty sweet. This can also be used on different pages. If we have drop downs that we want to apply later on.

C

Thank you tyler and then the next one is faq anchors.

C

So this is a review app, and so, if you click the one, if you scroll up a bit uh and you click on the 400 ci cd minutes per month- there's a one there so now, instead of opening up another page, it'll open up the faq header and it'll scroll to the associated the appropriate section, uh there's a bug right now, where you should be able to do it through a hash in the url which I'm gonna fix uh right now, it's not working, but I'm gonna get that done.

C

Hopefully today and I think that's it for me heavy. I think you're next.

D

I think I might be next. Oh sorry, I uh was going off of memory. Jess is up okay, it's the other jay. um So I worked on the designs um for the home page landing and landing page that tyler already showed, so we don't need to reshow them and I'm also working on this install page mvc2.

D

um It's kind of smaller iterations there's a lot of things we could do on this page, so we're kind of breaking it out into mvcs. um Just a couple. Small updates changing the layout, so you've got that side menu. You can kind of scroll exactly where you need to be calling out things that are popular or recommended some other small things like that um yeah and then who's next tina. That's.

E

Me um I wrapped the usability testing sessions that I ran on the gitlab versus skit hub infographics. um I posted a highlights reel and some key observations and recommendations for future improvements in the issue. um Some some of the observations are just validating some things that we just kind of notice and is that users kind of don't understand the values that are being presented.

E

So I anticipate that future iterations of this page we're going to have to look at either how the scoring methodology is is being used or how we can kind of further explain what that is, and so on and so forth.

E

So um all of that is there on the issue uh and the other item I worked on is I rescued the solutions uh template to align with delivering specifically the public sector page for so for mvc, one where I'm gonna be focusing on just using existing blocks, which means removing the case studies section, um which is different than the case studies that uh barker was talking about at the top of this meeting um and we'll be leaving the content content contact section at the bottom.

E

As is I coordinated with the public sector team, and they are supportive of this iteration uh stephen you're. Next.

F

Yeah uh added the confetti elements to our figma library, and there was an issue for that and they're in there now shareable. uh Well, uh the features design is complete for desktop. The mobile version is currently in work and work in progress. So there's the issue there and and they've linked the content issue which is uh oh, did I skip one yeah?

F

Sorry, there's an issue open for a content audit and then so for the features page, so that's assigned to myself a brie and she's, pretty small on the right now, but uh is at least open, and it's linked to our uh parent issue, which is the features page itself uh added a new type style as well to our library. So that's shareable too, because it's being used by justin tina on some of the other cards and stuff like that.

F

So it's reusable component, so that's added in two and it needs to be correctly named once we align with engineering, I believe so just a little bit, maybe some small thinkers and next up is javi.

G

I'm muted hello, um we released a new navigation to the main site. um This is a lot of work and yeah. I don't know what what else to say. I think you all can see what's happening.

G

I don't know I've looked at this for far too long that I'm just like this is this is the thing that's live and it works oh and then tapping for people who have screen readers and for people who are visually impaired and whatnot. There's a lot of considerations that uh we put into it.

G

So we're really excited to have this uh live, uh and so people can go around and mess and play with it and whatnot so- um and this is our first iteration so obviously with time, um we'll nail down some of the details, both so in implementation, but also in the design uh itself, uh so we tinker out like bugs and also just what'll help drive some of our metrics.

G

um I also made a small change with the safari home page, um essentially that navigation, the logo itself would be cut out in safari, so that's fixed. I spent a lot of my rest of the remainder of the iteration, just pretty much cleaning up a ton of slippers related stuff. The only thing that I'm going to show right here um is something I found out about.

G

Storybook, that's pretty neat is that we can nest um like types um within each other, so that helps like create kind of like that sort of um you know more uniform structure, so it's easier to consume.

G

I should be pushing another commit that will update the titles for some of these, and also some of like deleting some of the extra files, because we have like multiple story files per component and we only really need one per each subdirectory. So a lot of like code deletion and uh making sure that our workflow stays efficient and our code stays as dry as possible um change left hook to exclude deleted files with prettier before that wouldn't work.

G

So when writing a commit and deleting a file, the pre-commit hook would yell at you for doing something that doesn't exist um and that doesn't do that anymore.

G

Added a prettier ignore to yarn lock because we don't want the yarn lock file to be messed with by prettier, um consolidates slippers components into hierarchy that matches sigma. Essentially, this is kind of a code like developer experience change so that, like it's easier to find the relevant story relative to the view component, um because before they were nested in completely different locations, now they're all um I believe they all should be now um in the correct spot. So that'll help engineers uh with that and then finally change storybook structure. To oh, I added that.

G

That's a total duplicate, my bad, um but yeah. That's the last thing uh on the agenda for me and I think I'm the last person so yeah excellent.

A

Thank you. Anyone else before I stop sharing and recording hearing none. I will go ahead and stop the recording thanks for being here with us, uh and we will see and I'll see everyone in retro and folks will see us there. So have a good one.