GitLab Digital Experience, 28 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Iteration Planning - Mar 28, 2022

Description

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

A

And the home page: oh sorry, it's the uh free trial and talk to an expert. You know like we used to have, I think, buttons or something for them, but now they look a lot cleaner and then there's also a part to talk to sales and talk to experts so I'll be pulling that in as well. um Next up we have laura.

B

uh Yeah um so also working on the homepage, a few components here, so the hero cta section at the top, um the solutions page section which goes through each of the solutions, in kind of like a slider manner, uh the customer logos, which is pretty similar to what we currently have and then the resources section which is like that video uh section towards the bottom of the page. So I'll work on on those uh next is mateo.

C

Yes, I will continue working on the on the pricing page now the v2 components I have the header component, the new tiers component and the new pricing, and next one is tyler.

D

uh Yeah, so I think we have some follow-up and wrap-up on customer case studies landing page uh megan will probably be actually doing that um I'm around to consult and follow up on things that I've said in there um and then I've got the getting started and support pages.

D

um I do not know any of the details about those things, um so I guess like michael, I haven't even like gotten to like hop in there yet to like see what's written down, but like are those designs kind of done or are we still blocked on these.

E

uh Yeah uh the getting started page should be um good to go soon by the end of today, at least yeah for sure.

D

Excellent um and then, who knows things about the support page.

F

Yeah um also like it could be started, but just want to do like a one pass with the jam. 3 ui first.

D

Where should we go like I'm looking at these issues and like nathan's like this is just a placeholder issue like? Where is a place to go for all of the designs? Is there like a link or an epic or a document where I can like pull in the links and say this? Is what I'll be working against.

F

Yeah I mean there are.

D

F

Issues for each one, are you looking for something else.

D

No I'm looking for the issues. I just don't know: where is there an epic where they're housed or.

F

Yeah, so each one should have so like support and resources, I think, is one like kind of sub-epic and then.

F

Yeah exactly exactly so, we just need to make sure that we're putting all of our related issues in the same epics, um so yeah. If you go there, there should, in theory at least be a support issue. If not, I will make sure it's linked later.

D

Is that that ux support page refresh.

F

Yeah, I think that's cool cool.

D

Excellent, thank you and answer my questions.

D

uh Next up is lauren.

G

G

So cool um I'm gonna be working on the category leadership, template um and I'm just gonna build the protect and modern applications page as part of building that template just give it a shot, get it in the refresh branch, also building the solutions, page template by technology and then getting a placeholder for the aws one.

G

And then there was a data layer update that um we need to do for contact sales, public sector and self-managed trials to make sure we're shipping the right data to google analytics and pass it over to hobby.

H

Thanks laura uh lauren, oh my gosh having two laura yeah. It messes me up all the time, I'm working on the template for the individual feature page uh and then I'm building out one of the one of the templates out into its specific features. Just getting one of the pages built out to see if this template is being actually, you know what's actually working, that's it for me. Next, miguel.

I

Yeah I'll be working on the templates for the solutions pages by industry and by department, and also I will be working on a couple of pages with those simple templates and uh finishing the stage stages of devops lifecycle, which just needs a revision, and that will be my iteration and I'll pass it over to john.

J

Thank you, um I'm for this iteration, I'm going to finish the landing page for the features uh page b1. Also, I'm going to work on the template for the version 2 of the feature space and also I'm going to work on a couple of uh solutions. Child pages passing over to megan.

K

Hey um wrapping up the customer case, studies page as tyler mentioned that should be wrapped up pretty quick in this sprint and then tackling the. Why gitlab page, I'm guessing I'll have some capacity later on to um look into one of those open issues that nathan shared. So next is jess.

F

So um a lot of what I'll be doing at the beginning this week is kind of doing that run through of the jam three brand over these pages, so over the home page, the pricing page and the support page to start uh and then once that's done I'll turn my attention over to resources see what's needed over there, um potentially a template tbd.

F

If that gets done, I will then do the footer a full footer and a minimal footer and I'll also be helping out tina wherever she needs and she's taking a little time off. So uh along the category leadership line and.

L

Speaking of tina you're up next, that's me thanks. um I have a short iteration this uh I'm off, I think thursday, or no friday until next thursday. It's bad timing. I realize that, but I'm moving um so unavoidable, um so I'll be wrapping up this week, the solutions uh ui, so I've been kind of taking what gem 3 has been doing, putting them um onto some of these templates. I believe gem 3 is providing designs um also on thursday, so um we'll have to take a look at applying whatever designs they provide onto those.

L

So this will be very iterative, um also um going to hand over category leadership to jess, um just because I won't be able to do it. I don't know if she'll have bandwidth either. So maybe our squad should talk about a plan for category leadership. I was thinking since those topic pages already exist.

L

Maybe we don't skin them, but that'll be a conversation that we can have and then we can focus on features and solutions, but that's just that just popped into my head right now. um That's it uh carries next.

E

um Yeah, I guess I'm just working on the iterations for the get started checklist and the y git lab page and including any sort of gem 3 changes that we'll have for those pages um yeah. If tina. If you need any help, I can definitely help you um the next week. Probably that's that's it for me. uh Dennis.

M

um For me, I'm hoping to finalize the data studio dashboard. I have a meeting out with michael and filzo later today, um also some net new tracking items for stakeholders like capturing namespace with every purchase.

M

um I also created a new view on ga for the self-service team, so I just need to clean that up um and then tracking ctas on the blog post um yeah. That's it for me back to nathan, question mark.

A

Yeah, uh I think we're good on screen sharing this or I can leave it open. If we want to talk about anything in specific, but I guess as tyler mentioned earlier, is there anything we want? We need from jm3 or any questions.

N

Do you want me to give you a quick little rundown of where we're at and what our next two weeks look like.

A

Yeah yeah that'd be great cool.

N

um So we of course have the homepage and pricing designs, um but we need to add motion and content to them. So we have two of our team members working on motion and content for those pages and then our two other team members um who are all in this call um tackling the ui for the next two pages, which are features and solutions.

N

So over the next two weeks. That's what we're working on and our thursday syncs will be sharing kind of an update of where we're at and then the following week is when we're going to going to be officially delivering both.

A

And solution pages are those the landing pages.

N

It is everything and that.

A

N

The wires or the version of the wires that we we got from tina, okay, also, if you're ever curious about like what we're doing or what's going on, we have that running masters agenda masters attack, whatever we call it and all of the details are in there all the time, everything's in one place, organized there. So take a look and if you have any questions or don't feel like reading it all, because it's a lot just hit me up on stock and I'll fill in the gaps. If any.

A

Yeah, I imagine we're going to be pretty active in that slack group this week because, as we start implementing the designs, I think maybe how things interact, even though we've kind of gone through the walkthrough, I'm sure there's going to be questions same with gradients and stuff. I think we have access to the sigma file, so we can grab the variables from that.

A

N

Should let me know if you don't, but also do we want some sort of channel specifically for dev, just if there's like quick things that we need to address, dev, wise or pixel, pushing or whatever it may be, or how do you guys typically work at kit lab just one.

G

D

G

Fewer channels.

D

um uh If possible I mean, hopefully, the development work is like pretty uh encapsulated, uh based on our conversations last week, so um like channel for like questions and like chatting and stuff and like sort of like informal communication.

D

But if there's um like more like nitty gritty like in the weed stuff, I would hope we could do that uh with either issues in our project or issues in the in the code base that uh jam three is putting together and, like sort of um you know, capture that, uh in whatever like in the appropriate tools, rather than slack, because something to keep in mind like our slack um channels, get wiped every 90 days. So, like slack, is not a place to put permanent information.

N

No way yeah yeah.

D

Like we don't like get gitlab does not use, like slack, is not a source of truth at git labs, so they we specifically like all conversations, are deleted every like 90 days so, like that's.

N

D

Place to store stuff that should be permanent.

N

Good to know yeah we we do have access to um all of your platforms too, so we can use that and then tyler. I know we owe you some more information from a tech standpoint. um Suk was going to put together some sort of plan and then we're going to send it your way. He is working on that as well.

D

Did not even know that that's exciting.

N

Thank you. Well, that's happening too cool cool. um Did you all have any other questions for us gym three.

G

I have a one um kind of just like an awareness for the group. A lot of our issues are placeholder. They don't have all the info in them. So if you get one, take crack fill it out put the links in there like this is the page. This is the figma file. This is the content issue.

G

um We're all gonna have to work together to fill those out and that'll help create that single source of truth, which is the issue. That's what we work from.

L

Does everyone have access to the squad document, so you know who to address your questions to they should be in the epics. But if they're, not here's just like a link to it and just I think that's it.

N

I don't know if we should have access to it, but I just requested anyway, just in case yeah.

G

On that spreadsheet that tina linked um so cool, you should bookmark that.

N

I just requested access for both.

B

Any last thoughts before I stop the recording we don't have to like leave, but nothing else, opinions, feelings. Okay, all right! Let me stop that.