GitLab Digital Experience, 12 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Iteration Planning - April 12, 2021

Description

Sprint Planning Doc: https://docs.google.com/document/d/1uFw2snKuBlt2VirP5mjMvCr66HD7hOAB6QrXaElBZQE/edit?usp=sharing
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, everyone uh welcome to the digital experience. Team uh iteration planning, meeting yeah sami, is dancing it's a good time. It's monday uh april 12th already uh so we'll be going over what we plan on accomplishing for the next two weeks. uh So I believe that brandon is up first.

B

Yeah, so we have a pricing, a b test uh that has been kind of in the design process for updating copy, and you know a few other things that management asks for. So I think um you know once that kind of copy and design is finalized or getting in a good spot, we'll be ready for engineering that.

B

So that's, probably what I'll be working on uh for a chunk of this sprint uh and then also we had some uh localization issues for the um germany uh landing page uh german language, landing page for german market uh and then also um I've been kind of working over how we can uh tree out how we can refine our triage process um so kind of doing a proof of concept for that for some upcoming projects, and that's where my work will be focused. This sprint I think up next is lauren.

C

All right, so I'm gonna finish up an event copy block in slippers. That's started almost done. um I'm gonna help assist tyler in assembling the event. Template in slippers help out support and review.

C

We have an issue for improper header structure, so our h1 or h2 tags, and I think the blog template and the topic template. So I'm just going to patch that up real quick, I'm going to continue working on linking a merge request to a review app using the deploy preview links in netlify cms.

C

I'm going to start a working group to separate the handbook from the marketing site. I discovered danielle mentioned working groups was like this is a perfect use case for working groups. So let me get that started and then I'm gonna wrap up our okr for um webpack iteration. So we have a couple outstanding ones there and I'm just going to look for easy wins and if there aren't any I'm going to move them over to the next iteration epic and close that one out and we'll head over to tina.

D

Thanks lauren um I'll be working towards completing an okr that um I'm working on for the prospects for the free trial um that includes creating a user journey and doing a little bit of pathway analysis.

D

I've also reserved three points of time to support mr reviews for both commit and slippers integration for this sprint, so that I can focus on a little bit on that um next is send me.

E

Thank you, and this spring I'm going to be working on the on our homepage. Compliance uh on our homepage taught by is requesting that we showcase some companies that we are comparison as part of our security. So I'm allocating two points for that. Then. The second thing is: I'm just going to be correcting the title or one of our pages. That is not correct.

E

Then I'm going to be fixing some broken images that is affecting our seo, because when google is linking to a page that has broken links, it could actually negatively impact our seo ranking. Then the next thing I'm going to be doing is on slippers, I'm going to build in the block cards, components that has the image version. We already have the blog card, but we have the ones.

E

We've got the image version and the resources cut to the one, with the image version then, depending on, if we have our final assets for the pending highlighted partners page, the page has been pending for over experiment because we have not yet got all the final assets required to finish up. If I can get that, then I'll move it into the sprint and finish on that project and that's it from from me. The next person is tyler.

F

Hey, I don't have jury duty, it's very exciting to me, um so uh I'm gonna finish up the event blocks. um I was talking to sonme and tina about this earlier today. um I like it's basically done I just like. I really need to clean it up. I like got it done end of friday and I was like cool. This is bad, so I'm gonna go clean that up today um before I actually submit it for a review.

F

uh Then I'm gonna, um like lauren, said uh we're gonna work on assembling the event template in slippers, um so we're gonna pull stuff together in storybook um and then once lauren, and I have kind of like wrapped that up and that's got some dependencies on other blocks uh coming through, but um we can start moving on to the middleman integration side of things, uh and I am gonna take on just like the uh components that I like built out in this prior phase.

F

So video blocks in middleman and lfi cms speaker blocks and benefits blocks so um yeah and then up next is laura.

A

uh Yeah, uh so I will also be finishing up some of the event template work. uh I have carryover of the countdown block. That'll count down the days until the event uh so I'll be building that out. um I anticipate a few minor fixes for partner block.

A

I think tina's going to be taking a look at that, but there will probably be a few little tweaks improvements, so I left a point open for that uh and then I have some slippers grid improvements and now that we're kind of using a version of the grid, uh the tyler built out in the past iteration um having a more global component that we have access to for that, uh and then I picked up three of the smaller kind of stylistic um issues that came up with the blog, so the confetti z index, covering some of the elements on the page, some hover states and uh the newsletter styles.

A

So I grabbed those if there are higher priority issues I might swap them out, but for now that's uh that's what I'm committing to, and I think next up is javi.

G

Hello, um can you hear me I'm just doing a test piece just because yeah I'm working on this iteration on getting a layout to work with the slippers, header and footer, and the reason why I have that set up like on the very top is because I was hoping that I could get these components to a usable enough state, so that, like I, can continue to iterate on the style um but get to the point where I can start pulling that all of that over to www and then continue to iterate on the style like without having to be blocked by that.

G

So that's kind of why I have it ordered that way. I want to work on the footer mbc2, there's some like accessibility, things that I've caught that are problematic with that. So I want to catch uh navigation, I'm calling it mvc 1.5, because I don't want to like break the naming convention- maybe 1.1 I don't know, but I'm working towards that.

G

I want to finally get to the sop component generator that has been in the backlog and been called out already three meetings in a row. So this is third time's. A charm, um finally, I have this request from an external party on the landing page for the dev setup survey.

G

um I in the dock I put question my question about question mark just because we're blocked by content, um because it's like I want to know, what's going to be on the page for me to develop it, so um that would be very helpful um for getting that page out. So I think that should be fine. I might have like yeah. I I have to inquire on that further, especially now, as the day has come around, and I see that, like the due date is set for a certain day, and it's like.

G

Is this like a hard date like? Is there other things that you need for me like? What can I do to help like make? This request happen? So enough of me up next is jess.

A

League savvy, uh so the main project I'm working on this week is the next iteration of the free trial page uh and then I've also got a couple little tasks going on. So one is. We have like the final mock-ups for the highlighted partner page from the template we created before so I'll, just be uh kind of working on that a little bit and then um there's also a content.

A

A copy change for the pricing tiers on the pricing page and I'll just again be offering a little bit of design guidance on that, and if I have extra time I did some bonus research last week for the home page in the devops page. um If I have time I'll actually put some sort of readout together um and that's it for me- and next is steven.

H

uh Yeah, my main focus is still my okr, which continues to get bigger and bigger and so involved. In my 10-point estimation is creating some content, wireframes and some user journeys with some real content and and then from that possible suggestions for our content team around and how we're actually servicing that content. So we have different ways of doing it at the minute, with blog with webcast videos and so on so um yeah. That's me as well, and I think, on the last one.

A

Yeah, I think that's it. It looks like we do have a sprint name that I forgot to mention at the beginning. uh Lauren put the idea of uh let's build a boat, a metaphor for a really great uh transition, which is apt all right thanks. Everyone and we'll see you next time.