GitLab Digital Experience, 25 Aug 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: DEX Conversion | Sprint Release Video Sync Aug, 25 2022

Description

https://about.gitlab.com/handbook/marketing/digital-experience/#groups-metrics--team-members

A

Hey everyone: here's our sprint release video for the digital experience; conversion team for august, the 25th um I'm gonna hand this off to jess to get going and go from there.

B

Thanks, I'm going to share my screen really quickly.

B

um The first thing I want to point out this sprint is finally got around to finishing this, like campus versus education, page uh user research- and I put together this readout that I would love people to take a look at just kind of breaking down really quickly. It's only like eight pages, and some of them are just title pages.

B

um You know things that are happening on these pages. That could use an update, and it's just one part of a bigger.

B

Look at those two pages and what we might be able to do with them in the future um and then also um there were a couple updates to the commit page new sections. Things like that photos that needed updating, um added informational frames around the pricing page, which I can also show maybe yep.

B

I think this is going to be an a b test in the future.

B

Just use a little great for small business or great for enterprise, just kind of calling out each tier um and then.

B

Lastly, um there were some updates to the hero section of the install page, uh mostly just like type in links, and that's it for me for the sprint and I'll pass it to tyler.

A

Yeah um super simple for me: um I just my time was eaten up entirely by fixing the google tag manager in the sign up flow um we've had they added a new like company information page to that flow which did not have the um google tag manager, stuff uh and then I've just been like shepherding the merger. It's been.

A

It's been for external reasons from other team, like the merge request process in the product, like basically um broke a whole bunch of times for other things and like I got to experience all of them um and then like troubleshoot, that alongside the people who were also troubleshooting that so that's.

B

A

Most of my sprint um and then uh spent some time like uh merge, request review uh like uh chatting with people getting other folks up, just be like working with javi and getting up to speed on data layer, changes that are on the on the list as well. So that's uh that's it for me.

B

Yeah um in this iteration, a bunch of commit updates um still wrapping them up, but they should be all pushed by today, end of the day, um a few broken links I fixed on the pricing premium and the feature comparison pages, uh the y premium and ultimate pages. We updated their h1 tag and page title to do better seo wise and then one thing I was excited about was the marketo form fallback state.

B

um Previously, I think a few weeks ago marketa was down and our forms like just they weren't there, but it still said, like all fields required and fill up. This form stuff like that. So now, if there is an error that comes from marketo, uh we'll show like a message to the user. Saying like hey, there's something wrong here, so I think we just uh cleaned up that experience much better.

B

uh Next is only.

C

Yes, okay, this spring had I had less issues and merged, but um there they were more complex. So with more problems. First, they we have. I update the h1 class.

C

The tag was correct, but the the class needed to be changed. Another one was the peel booth iteration. It comes from a boolean parameter to a string options. There are no three options: three styles and the problem with this is right. Now I have to I I'm helping to get release the components, because the comments um was wearing a bunch of updates from the slippers repo, but I forget to install it, so the delivery can export and right now the components can't cannot be used in the viewers experience repo.

C

So right now, I'm doing the publish release and upgrading process by myself. I'm not sure. If the I need some approval, it's just publish the components that are made, but this is the the troll right now and I also update a hero section in the install page we detect uh update and we detect uh some type type uh com. The type elements, some elements in the type component and maybe we'll need a issue to fix.

C

Some letter spacing, and maybe it will be, a future issue- we updated links, analytics and implement the new site, navigation and also the problem was I detect and resolve some style problems because a complex, no complex but a special and background style for for a shirt, but it reynolds is resolved, um that's it and we and I insert uh the I code iteration proposal that will be will be fixed and do it in the next iteration. So I think that's it next is dennis, but dennis is not here.

C

A

um Yeah, I think that's it for this spirit, release.