GitLab Digital Experience, 1 Aug 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: DEX Engineering Iteration Planning

Description

FY24-Q3: 2023-08-01 - 2023-10-31
Iteration: Aug 14, 2023 - Aug 27, 2023
Week 3 of the FY24-Q3

A

How's it going. This is the whole digital experience, engineering team and we are uh kicking off this iteration. It is Monday August 14th go ahead and share our mascot porcupine high five yeah. So we're gonna be a team high five and work through some good stuff. So I'll go ahead and uh pass it over to Nathan Kick It Off.

B

Thanks a lot uh for this iteration I'm, mostly going to be supporting uh the contentful integration, so I'm working with contentful a lot and we have a bunch of training sessions this week. So it should be fun, but in the background I'm going to try and get some of our uh our packages, maybe using Vite and some icons getting ready for the CMS but yeah, mostly in the background. And then we have a big list of stuff to do in the open board.

B

It doesn't have to all get done this iteration, but it's good to pull from so yeah I'll pull in uh when I have some bandwidth, um Megan.

C

Yeah, um like Nathan a few contentful training sessions this week, um as for issues of carry over from last iteration on um some Discovery work for how the CMS might look like working with the navigation and in tandem, if we can have maybe like some performance improvements to the navigation package, um so I have like a a doc in progress on um on some ideas and I'd like to pass that around to the Dex engineers at some point, this iteration for some feedback.

C

Maybe what I have isn't the right solution and someone on the team has some better ideas: I'd love to get our brains together on that um next I have an issue to update, looks like pricing content. Sync I think that's related to some of our uh the pricing translated pages, um an issue for our semantic change. Log commits looks like there's some like duplications on there and um I know. The problem is I'm. Gonna um just add some documentation on how we can avoid that.

C

um That is the problem uh and then, lastly, a spike on um how we can maybe work with our internationalized content in tandem with our CMS and how that might work.

C

um If we have an English uh content in the CMS and the translated stuff isn't yet, how does that look like so I've been working on that Spike and then pulling in any other issues in our open board, but uh javi's not here, but Lauren will speak for him.

A

Yeah so javi's um still doing some follow-up on our GA attributes uh in the navigation for translation um and some more follow-up for functional bugs. So every time we get a page translated, it goes back to the um translated team and then they send over big old spreadsheet, with like a bunch of bugs they've found and we fix them. So it's great.

A

We have another set of eyes on the marketing site, doing QA and he's also working with Megan on um the discovery of CMS and the navigation and how it's built the architecture and he will also be running our nav release for this iteration Laura is out I'll, go ahead and read for her as well.

A

um She's doing the solutions get Ops page, refresh a platform, page iteration, um a website component audit. So looking at all the components we've got in be and seeing if we can uh make that more efficient and preparing the data structures for the be and CMS, and that's something Megan, Nathan and Laura all working on together and then also setting up our blog repo to send a little alert to our slack Channel Dex alerts and be like hey, go check out.

A

The pipeline it broke, which is really good, let's just catch stuff um Miracle, is also out she's, working on adding CI variables and artifact upload script, and that's for the blog. Also. We set up a whole new repository and we're just getting the deployment ready, and then we have a bug with the marketing site, cookie the miracle cookie, where it still says, you're logged in, even though you've left this site, um and so we gotta, we gotta patch, that up and then she'll be uh building a Lex test on our free trial form.

A

So we have a free trial form and the product we've reskinned, and now we're going to build an A B test using git Labs functionality to test between those versions. Good stuff, okay, pass it over to John.

D

Thank you um well for this iteration I'm, just catching up about contentful, because I was out, while everyone was implementing contentful so um for this stretch, I'm going to work on translating the solutions. Kubernetes page uh also I'm, going to implement contentful module into buyers periods following what Mateo did in the blog project and finally, an easy one I'm going to work on the library previewer for contentfuls, uh so that would be it for my iteration I hope uh everything is fine with contemploy and my learning with contentful.

D

um That's it for me. Next one is Mateo.

E

Thank you again, uh so I will continue working to the blog, uh creating a couple new components: uh the CDA component and the code component to be used in the template. Page um I also picked a couple of issues from Parts experience, repo, which is changing the URL for the CI CD page, adding a video to the dedicated page um and yeah. That's it.

E

I will also be configuring, the contentful gitlab pipeline, so that uh for the blog, so that, when anything changes in the blog content, the pipeline should run and from previous iteration I still have the template page in review that when it's, it's really just just being reviewed and yeah, that's it for me. Next one is Miguel.

F

Thank you. um I have a couple of issues carried over from that situation. uh The first one is the uh Solutions analytics and insights page, which uh I'm working currently and uh also I'm with you know, feedback for the um uh for some Microsoft Office updates in the email template and after that, I will be prioritizing um contentful contentful issues and the working sessions. We have this iteration and with that possible to migrate.

G

Yep, uh so for the situation I'm going to continue work on the home page redesign, we just got access to the translations, so I'm, just gonna update that in wait for our final final assets to be in I'm, also going to be working on updating the Roy calculator efficiency, tab, design and um I have small updates for some of our devs. A cop City, uh Virtual, City, Pages.

G

Sorry and I picked up one of our CMS issues for the page content type, so I'm gonna also be working on that I think that's it for my iteration I'm gonna hand over to TV.

H

uh So for my integration, I still have to investigate a few solution, links that are not being localized because last week we localized a lot of our solution pages but for some reason a specific components still is not localizing. The link from one page to another I have to investigate that, and I will also update the switch type synonyms to provide results for our common top queries. And my last one is our so contents type for Content. So we still are studying some solutions and investigating them.

H

uh I think that's it for me, I'm, not sure. If we're going to start the new test for our devsecops page, yet so yeah, let's see I will test you just.

I

Thank you. Yes, we have a everyone said training this week for contentful, there's more training next week for the contentful. They have one ramped up, so it'll be kind of a slow burn into CMS and contentful, but once everyone's on the same page, we can hit.

B

The ground, rolling and.

I

Really dive into uh and.

B

Choose iterations that.

I

uh Nathan has successfully set up for everyone. um Thank you. Everyone Lauren.

A

All right see you later.

E

A