GitLab Digital Experience, 18 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Retro Video - Nov 18, 2021

Description

Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Digital Experience Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit#

A

Hey everyone uh welcome to the digital experience teams, retro uh we're just going to go over what went well and what we can improve on. uh First up, barker.

B

All right, um mateo had a great proposal to change our view: template team system to increase the maintainability and mateo. Can you talk about that? A little bit.

C

Yes, the proposal is to change the templates, to not describe the components inside of them, but to use the the content files to describe the order and which components are supposed to go in inside a page, and I took the team's feedback on on this and I will begin the implementation for it.

B

I think it's a great idea, good opportunity to really make our templating system a lot more.

A

Efficient, so yeah there's just one thing I just thought about. I think I added a comment on that thread, because we also have to remember that going forward we're not probably going to be the ones updating the yaml files. So we should. I don't know if we do like, I don't know, pipeline checks or something just to make sure that they don't break the components or anything just something to consider going forward.

B

Yeah we'll have to iterate on the implementation.

A

Yeah, but no it's amazing, it's a step in the right direction. That's for sure.

B

Yeah um second thing um I had was uh new team members, great job, getting onboarded and making contributions to our buyer experience, repo and our dub dub repo starting to learn the landscape.

B

How we work um really good job, it's it's, not it's not easy stuff. So I'm really proud of the new team.

C

D

Hey, uh I do have two points. um Thank you very much, lauren and tina for all the feedback that you gave me on the armor for these solution pages and also another good point is. This- is the first page of many pages that we are going to do as a team, so I'm looking forward for for what's next, that's it and the next.

C

One is it's mine um yeah. I just wanted to say that the first task, the migration- was a very fun task. uh You know when, when you enter a new team, there's always that worrying that maybe the task will be something super complex, more complicated, but it was really really fun doing it so so yeah I was. I was happy.

A

Awesome all right, I guess we're moving on to things- to improve on um javi's, not here and laura, is not here um parker. I think he wanted to talk about this one earlier.

B

um Yeah so javi honestly didn't know, contribute was happening until like the meeting we were planning for our sprint cycle. um I can second that it's like. Oh, we do oh shoot. I don't have two days to work on stuff, um laura seconded that and said: there's definitely some improvement to be made about how that communication is placed out um yeah.

B

um I am. We should start using our names in the doc set of initials, because that way we know who we are um I'm next, uh so we plan for our iteration cycle async before the meeting on monday. So it's like you get fired up monday morning. You plan the work you're gonna do for that iteration.

B

So if we have large projects that have hard deadlines, um place them in the sprint planning dock friday or like super early monday morning, so that the team can absorb the ask and plan for it, um it doesn't feel good having your entire sprint plan blown up during the sprint plan meeting um john.

D

um I haven't found any documentation or I don't know if, if there is one for these luck tools that the team uses like clockwise or the ptos or the end of the week check-ins. So I would like to have to know if there is any documentation or or something.

A

um I'll probably have to get it for you, but I also, I think, I've just been picking it up over time.

A

uh Laura just showed me that there's a roots slack app, I think it's called roots or pto roots or something, and then in there that's how you do your pto uh clockwise a lot of us strongly dislike it and I think it may be going away and also, I think there you have to be added to uh geekbot, so we'll add down the action items just to add everybody to keep bought for the mid-sprint check-in.

A

um I think that should be it but I'll post, a follow-up in the uh the channel or on the third. Thank you nathan. No, it works uh action items is the next one. I think laura.

A

Oh no need to verbalize, so I'm not going to parker.

B

It's me again: ah hey matteo john. I know you had so much fun migrating those pages over and working with next, um but for the next iteration we need to pivot to working on the google analytics implementation.

B

So if you could work on getting read up on that epic, some of those um issues, that would be great um because we do have a hard deadline for all of that. um I think it's like december 1st or something.

A

B

All right and then we'll go back to working on the fun stuff.

A

Yeah, maybe we shouldn't have talked about google analytics.

B

A

uh Yeah, I think that's it for this meeting um this retro and we'll see you again at the next retro in two weeks.