 Okay, so today it's June 17th and it's the sixth meeting of a building Jenkins.io with alternative terms. So let's go through the action items from last week. So first off, have you updated the script to fix links and tour? Yeah, I have created a new script to for to creating the navigation that in total uses. Yeah, how about images? Yeah, I haven't started the images yet because I was I completed the tutorials and the solutions on the solutions page. I have some questions because when you go to the solutions page, it show it shows embedded articles on the right side of the page. Okay, so like, how, how does that work. And what I did, I created a sidebar on the top of the page on the start of the page with the embedded articles. I wanted to know how does that embedded articles can work. So maybe we can make incorporated into and over. Yeah, maybe we can, but do you have like an example we can see. Yeah, if you, if you go to Jenkins.io solutions, a bit bucket. Yeah, on the solutions page. Yeah. Okay. Anyone of them. Bit bucket. This, this, the thing that is on the side on some other pages, it is embedded articles on some pages, it is just this. Okay, so. Oh, okay. So you're wondering like how to do it when the two options to choose from. Yeah. Okay. So I think maybe this way. So this one's a plugins list. Okay. Yeah. This is where this, if we go to, if we go back, just click on it. It's easy. It's the same. Let me check it. It's like the class is plugins. Which was different. Embedded embedded. I guess it was embedded. Jenkins embedded articles. Yeah, it doesn't have a class. So we can, you can try to write a script. You can try to look for a class. If. So. Yeah, no dispute. I was going to say that I don't know that. So it's. If you're detecting inconsistencies between the pages on Jenkins.io already. Then I think that gives us reason to say, okay, maybe we should just declare that we'll be consistent. And do something, do something that we think makes sense. So embedded articles, should it be embedded articles, whereas on Jenkins with GitHub, it says GitHub article. Okay, embedded. So the Jenkins with GitHub page has articles as well. But you say the bit bucket page says plugins, not articles. Yeah. It seems like we ought to choose one of those two that there's a style that there's a, there's a thing that should be done. So for Android, it shows articles. And if we look at Java, it shows plugins. So it's like, I'm not sure which, which one is the winning, but. Okay, articles for continuous delivery. Yeah, we have, we have on Jenkins with GitHub, we have both of them articles and plugins section. Ah, right. Okay, I see. So there are and Ruby likewise has both articles and plugins. So like one of two times. So either like like in this page. So either we have like no class Jenkins love GitHub articles, or like this one plugins list. Yeah. Well, one way to to fix this as to if we're allowed to add a class to this, like articles items here. And we can like, shift through them by class. Yeah, but like how on the on the in the dog file, I couldn't and I couldn't like understand and make it out how, how this is generated from where are we getting this. Do you have. Can we see the script you have for feelings so I can tell we can. If you if you scroll down and just like open open this page on GitHub, you'll see. Okay. And put this right here. Yeah. Like, in this, if you don't have anything related to how that works. I think it is something with layout solutions because when all the pages with layout solutions we have this, the layout matter and ostrich uses something with layout. Yeah, so there is a there's a content under slash underscore data slash solutions that seems to be YAML files that are used in the that a YAML file that's so content slash underscore data. Okay, slash solutions. And here it seems that the contents of that right hand side are defined in these YAML files. So it's got articles. So when I look at embedded. Yeah, articles and plugins for some of them. And others know articles. It looks like this is manually maintained though not. Yeah, not by any automation. If it is manually maintained we I can just add it in the page itself. Yeah. Yeah, because these are just links I'll create a sidebar I'll create a sidebar that will create a distinction for this for the heading. Yeah, at the end of the page or at the start of the page. Okay, so, so here the. Yeah, I mean the. So Chris the, the, let's see there was one that you just touched on that had videos in it it was. GitHub. No. Thank you. I was in bed. No. No. So under Android and Docker, there are there are video links. And those I think are placed across the top of the page. Yeah. Android. Oh, yeah, we have more. Yeah, so it's got videos and this one is Docker is that the page. Yep. So if articles plugins and videos. Yeah, the videos are on the top of the page. Right. Okay, there they are I see them. Yeah. There's certainly more videos that each of those solution pages would would benefit on the current documentation from having those. Is it feasible for you to do that style of a layout because for me I'm less concerned the solution pages tend to be a marketing or a pointer to other things I'm not sure I need we need to worry about them being versioned. Yeah, I can I can update the UI to for to match this type of layout. See, so like this way. Okay, so let's move. Yeah. Yeah, I have been opening tickets on Trello. Okay. I will go through it next. Yes. How about they get a page or we have to get it. So we're using one.com. We need to do this. This one I can cause it out. It's not needed. So branches. Yes. Next week. Yes, I think I've done it. Yeah. Let's see. I've raised a pass submitted a PR for tutorials. Okay. Yeah, I saw it. Okay. I'll look at it tonight. I'll go with them. So let me check. Okay, so, so we have. We've done this way. So it's going to go with you so we're searching assets. So is this on the code review as well. I don't know I haven't created that one. Like, it is, we don't have to do something with assets folder. So I, I couldn't delete it. Oh, I don't think we can do this, but I'll make it into not something else. So up there existing links. I have updated the existing links and user docs and half developer docs. I need to like, I need to check in. So I'm not, I'm not automating it on the complete folders. So this one's done. Yeah. Okay, good. So at images or correct links to images. Yeah, it I'll, I'll complete it by Tuesday. I'll complete it by Tuesday. Tuesday. Anything else. It's not, not, not very clear. This is yeah. So how about this one? Yeah, I added I added both of these today. Okay. Oh, is it doing like, it is doing and this isn't to do. Yeah, I like doing. Yeah, I'll start, I'll start doing it. Okay, let's get them. So we'll get there. Okay. So let's, let's go to. So how about us go to the new tutorial, the new tutorials you have done. So do want to share a screen and just walk us through. Yeah. I have to show the tutorials right. Yes, please. It is, it is still in PR phase. So like when I thought of you, we could see it from. Yeah, I noticed this to like, can we, is there, are you working on like getting rid of the errors? What are the errors here? Are you working on getting rid of all these. These errors. Yep. These are the, these are the image link error, which is not working. Yeah. Okay, so you're working on this way. Yeah, I am still, I'm still figuring it out. Okay. Because like, I was searching if I was searching probably what Mark said in the last meeting if he could place all the images and one directly for each for user documentation and then reference that. And it would like, so I was, I was searching that on the, in a Torah. Okay. How does and Torah support images and pages it certainly must it just assumes that the images are in the same directory with the source file. It assumes it assumes that the, you are, you are following the given structure that and Torah provides with images in one folder that is named images. Okay. So I'm searching if we can like, in, if we have to, I think we will have, we can change something in in Torah. The configuration file to so that and Torah looks somewhere else for images. Why not just follow their pattern. You're already having to make changes, aren't you you're already having to do automated, automated transformations from existing source to final why not just use their pattern and okay we'll put the files in that in the directory they recommend so you don't have to do research on on their configuration. Yeah, because, because for, because on the user documentation and developer documentation the images are bit scattered. Yeah, the images are scattered all over the place so I was thinking if I can, I can just download the images from GitHub and to have in a directory and reference that directly so that and Torah searches for that. And I'll just delete all the necessary ones, which could be faster but if I but I'm still not I'm not getting a breakthrough so if that I would start, I would start just putting them manually. If it won't work. I think you can do it automatically. So why is great for you. Automatically automatically I'll have. Yeah, if I, if I could create a script with all the links of the images with the name and then automate it. I'll try it. I'll try it. I guess possible. This is a file. And it's currently in Torah is searching for the tutorial tutorial on the main branch. Okay. Oh, do you want me to merge it now. Yeah, yeah, if you can. Yeah. Okay. Okay, so it's on the main bar now. I'll have to. Is it working. It's still not fetching the files that I have first. Um, did you pull. No, and Dora and Dora haven't for fetch it. That's good. I'll try to, I'll try so it's because I, I've been working with locally so I just fetched it from the file system so I'll try to do that. Um, did you want to come on again? Yeah. Because I don't see the fashion. Um, wait, wait, wait, wait, wait, wait, wait. Okay. Okay. Well, we are. Okay. It's working. Chris, you have much the wrong PR. Yeah, it's that's why it's not working. You have much, you have much extension direct to you and I have to much the ad tutorials section. Yeah, that's why it was not working. Oh yeah. Okay. Is it working now. It's not. I'll have to check it's not showing the next page. Yeah. Maybe to open a ticket for. Oh, I, yeah, I haven't updated that. I haven't updated the number by that's right. When we have now on the site then we see when then we see all the updates to the next page one and also also I have a question about this include partial feedback for the HTML. Yeah. Yeah, like it's added it's added on the page so but as I proposed on the guitar channel, maybe we could like have it. Yeah, I kind of like the way looked before because like right now if you make it sticky like this. So we cannot really see what's what's like on the side of before. I was, let me just show you what I was like. Yeah, I was thinking of the feedback putter somewhere here with like you with option to like and dislike the page. And if you want to suggest something you can, you can, I can update the UI to incorporate that. I saw that in many sites in Kubernetes sites site and some more sites that that's why. Yeah, we can try it. We can try it. Well, so, so the Jenkins.io site has was this page helpful on the end of the page on the photo. Right. So I was thinking if we can like add a couch base or as it um yeah something like this is this page helpful and for feedback like we can like shift it to where because I was thinking I was thinking we can we can modernize our photo while while making sure it matches on all the sites. Yeah. Okay, but but since the feedback footer is on the page we can like we can move it. Okay. Also, I was also I was I wanted to like get an opinion on edit this page button like somewhere like here because we have so much we have so much white space here. This edit edit this page can be somewhere here and under that we can have the feedback for the feedback. Either way. How about you Mark. Yeah, no problem putting it there in the top right over there. Yeah, so the place I'm use right now it's in the footer and and hard to find right improve this page. So putting it, I like it in the top right hand corner where you've got it it doesn't feel like it uses a lot of space there but if you put it in that in the content section. Yeah, we can put it under the content section or above the content section. Put it under just because I think contents is more useful to the reader. Then, then you've got subsections. We can keep it right like as it is right now on the right top and sorry. Yeah, we can do that but I just wanted to get your guys opinion. Because I saw some other sites and having having it here and I this one is to to play and we can. I can add an icon before that and put it somewhere here. I prefer above the content section because on pages like on likes pipeline pages are so long that the content will push it down. And since it won't take much space it will just it will be just somewhere here. I can put I can put all improve the page and report up before the problem with this page here. And under that we can have contents. Since we since the user won't have to scroll that much if he's just targeting the content to access the page. You can just like navigate like this. I wanted to know your guys opinion after that I will start working on it. I can add an icon. Where they've moved it. Mark what do you think should we move out of this page. I don't object. I like edit this page at the top right, but I think it's a valid thing to note that it's not just edit this page right it's also give feedback and other things and so it won't fit in a single line anymore as soon as we have more than one item. So putting it under contents feels really good to me I would not put it above contents because contents is much more frequently used by the reader of the page then is the I want to contribute more. Okay, yeah, sure. Let's do that. So, so I'll implement it. So, so that show that. Okay. Let me add an action items, which is to add to move. Added this page to below contents. Anything else you would like to show us. I know the all of this, I could have told you the solution page but I haven't posted yet. So, so this, this week I'll have to update the solutions are you I lay out to incorporate the videos and the images, I need to get any to get done with the images part. And third would be feedback. So, fix the feedback. Some pages are not redirecting. And I'll check how into the redirects to the different pages. So fix the direction. Anything else we'd like to ask. Yeah, I wanted to ask about the data table API so that we discussed. I couldn't invest, I couldn't figure it out myself. Okay, show us. Oh, yeah. I haven't got time to look at it yet maybe I should do it tomorrow. Okay. Yeah, I'm still stuck on that. Okay, so that's the link for this. Yeah, I answered it and I can just see the head and the headings of the paper. Anything else we should need to discuss before we go. Yeah, the 599 stuff. Yeah, we should like to answer this question. Sorry. And what was the question for give my not not tracking the question. It's since this page is since this page highly depends on the JavaScript and like, like it is not completely it's not completely static. So I was thinking if you could build it with Gatsby. So replacing this page. Replacing this page is nowhere on my list of things that you need to do. If you've got to replace it, then absolutely Gatsby is fine. We just can't lose the functionality. Yeah. So the, I was thinking if we can build it a bit Gatsby. Thanks. And I, and again, I don't object, but I feel like Vandi, you've already got an awful lot of work on your plate. You've, you've got more, more, more work than, than I worry can be done in the time we have, but if, if doing this in Gatsby will help. I certainly don't object. Yeah. Yeah. I suppose do it in Gatsby. Yeah. Again, no objection for me. What we can't lose is the functionality. Right. If, if we lose the ability to search for pipeline steps, then we have, we have removed what we did last year in Google summer of code. Yes, I, I, I'll search about it. Maybe if we, if we can like, um, since the, since the, since the page currently it gets filled with, uh, um, yeah. Uh, HTML. Like I, I, I search for a strict documentation, but I couldn't found it. I, so I don't understand. I don't completely understand how this works. But yeah. I, I, I, I'll try. It's jQuery. I'll search about it. Then I'll come back to it with the portions. Okay. Yeah. Yeah, well, and, and if we need to, we could certainly ask V Hanthora last year's G soc student who implemented this, if, if we need more guidance, V Han, I'm sure is willing to join us and, and have a discussion. But again, my worry is. This thing, this thing is much less important than the version documentation. Right. Getting docs dot Jenkins.io to be able to show. Documentation for Jenkins 2.401.1 is much more valuable than whether or not we touched, we changed this page. Yeah, we can, yeah, we can use it as it is. Yeah. Yeah, that was what I wanted to ask. Okay. So it's not a priority, but we can do it later. Okay. Yeah. Okay. Yeah. So I don't forget about. Yeah. Okay. From my side. Yeah. Okay. So what, what do you plan to do next week? Next week. By next week, I would. Yeah. By next week, I'll. I'll be present in front of you with the presentation for July 6. And I would, I would complete whatever that is left in extensions. And the images, like, yeah, the images. Then we would have completely functional docs, docs, version docs for user and developer. Okay. So what do you track of, like, what, what other changes, like workflow rise. Or updating the docs. You know, like we, like we discussed, I would just look into the comments and the files that were changed. So I don't have to, like, check all the files. I'm not, I'm not, I'm not tracking them right now. Okay. Yeah. So I think it's important to get the scrims. To fix the images and the lines. Yeah. Yeah. Yeah. Okay. So we'll meet again next week sometime. Yeah. Okay. Cool. So I think it's, I don't think I have anything else to say. How about you? Thank you. Nothing else from me. Okay. So it's good. So good progress. So that's to meet again next week. Yeah. Okay.