GitLab Digital Experience, 19 Jan 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Slippers Sprint Planning 2021-01-19

Description

Sprint planning agenda: https://docs.google.com/document/d/1DFs47irmcL513pP5v-SPzjFypK7SDCR_dYSwSI7R3og/edit?usp=sharing

Related epics, issues, and merge requests :

Homepage MVC 3.03: https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/809

Apply new design language to the install page: https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/814

New Webpage Request: Remote survey (title TBD): https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/695

Test Slippers(DS) on a about.gitlab page: https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/741

Publish Slippers to npm: https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/740

Add Blocks to Storybook: https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/232

A

Hello and uh yeah, okay, hello, and welcome to the marketing design system uh working groups uh in the digital digital experience team on the marketing side of things. This is our sprint planning meeting for sprint six and we're going to go over what we hope to accomplish this release cycle.

A

Personally, I'm working on a project related to the pricing page that I can't just yet announce. um However, it's part of a company-wide initiative: that's uh going to be going, live soon um and that'll be where my focus is for the next week or so uh week, and a half maybe uh or for the rest of this release cycle. I suppose um so that's it for me, um I think I can go over.

A

uh Sunmi said uh that he might be iterating on um some homepage stuff, in addition to some cms stuff. But let me just go over this here. We have an issue um that references kind of more of the um updates we want to do to the home page, and uh so a few things are left.

A

um You know this news section see what's new um restyling of the blog card and uh stuff like that, so um getting close to the final product, for um you know what we have already planned for the home page and we'll continue to iterate from there and that's uh should be coming out. Hopefully this release cycle, uh let's see who's up next.

B

I think it's me, um I will be uh working with javi to get some updates um to the slippers design system, uh adding in a new block, hopefully, which will be my first time touching the slippers design system. So that's very exciting and other than that.

B

I have a kind of dated page, uh the install page um to add some design system updates to it, update some of the look and feel of the page, um as well as a request uh for a new web page um by the uh the greater team, uh and next, I think, is tyler.

C

Yeah, um so for this sprint I'm gonna, be I'm gonna help out javi with a small thing on the slippers storybook, some conditional class names just a little bit of troubleshooting, in the view components.

C

But more broadly, I think one of our objectives here is going to be getting like integrating slippers into the about.getlab.com website or at least having the infrastructure there, so that we can do that. So that's going to be my big focus and that's really two components which is packaging up the slippers design system and then importing it into about.getlab.com and then from there we'll be able to put some processes in place. But when we start like building out these blocks, they'll be that much easier to drop into the existing.

D

Website um next, I'm going to be making sure that we have an epic to define some of the new uh block, slash components that we're going to be adding to storybook and be able to assign those out to different people.

D

um We're going to be working on some of the feedback mechanisms and code by looking into existing issues, mrs and about.getlab, and I think what that will end up looking like is just kind of trying to see what people end up trying to do by looking at like what exists in the repository already to see the existing behaviors.

D

I don't know if there's ever been such a conscious effort. I think sometimes we forget like when things are open source, that people do things and contribute in ways so trying to see if we can find any insights there.

D

Another thing that I want to work on is making sure that we end up progress on the static site, generator discussion and I'll be sending a calendar invite to the team when we're looking free and I'll pass it off to jess.

B

Thanks albe, um I'm going to be working on a few user research uh exercises, so the first one is doing a card sort for our various product features to make sure we can group them in ways that make sense to our users and then a second test to do tree testing on our website navigation, to make sure people understand where they can find things when they're looking uh through a navigation. um Those are both dependent on usertesting.com they're, currently having a few technical difficulties.

B

So if they can't get those going, then I will maybe pull in a few ux tickets, some smaller things that need to be done. But my aim is to do research this week.

E

On my side, I'll begin to add some documentation for some of our elements and components within figma itself and as well as some refinements to our figma files. So it's working correctly with different content and responsiveness and so yeah there's a lot of documentation to get in there. So that's! My aim is to make a start on that.

D

We forgot the most important part. uh Our sprint name is the longest road out is the shortest road home. So yeah, I don't know what that means, but we're getting work done.

A

Cool all right uh thanks, everyone and uh yeah sounds sounds good, sounds like a good sprint and I hope we'll have something to show you all soon.

D