 So today is the fourth meeting after GSOC, building Jenkins.io with alternative tools project. And first off, today we're going to discuss about the strategy to tackle the project as discussed in a good chat, let's see. So it's like, I did reply eventually to everyone, which may be a little bit different from what we had discussed before. That's why I want to confirm the strategy. That's one thing I want to discuss. Also, we would like to check on problems. So what do you have to show this week? Well, I have good news. I have reported the user documentation completely. Wait, I can show that. I guess right now. Yeah, sure. So wait. Okay, thank you. Just a minute. Yeah. Yeah, share screen. Okay. Can you guys see this? Very well. Yeah. I was, I'm facing some problems with system administration paid because like they, it has reverse proxy configurations and the like links are not working. The page is not changing other than that. Everything is working fine. Like, I think in some pages where we have work in progress and Nora is not reading them correctly. So what should I do? I don't, I don't, I don't know how this work in progress equals to true things work. If I remove this, if I remove this, the page will be just an empty page without that. Without what we, what we see on Jenkins.io on pages that are actually in work in progress. Yeah. Cause like we have a work in progress. It shows a button. Yeah. Managing like managing Jenkins and. Yeah. Here we have, I guess it was. Script console. No, it is not work in progress. Wait, let me see which one is the work in progress page. Okay. So is this indicating to us? You may not be, oh, there we go. I don't know how this system does like, I don't know how, how this thing is here. I think, but I'm not sure cause like, let me check. So I think I, we can, we can do is to. For in toilet. Let me search for it. Cause sorry. This is, this is just, I can, I can, like we can place this with like, I can just write it here. Like somewhere here. I can write the warning, the warning tag. I guess it's the warning. It's the warning admonition block in Antora. Correct. Yeah. So I can, we can use that on, like I can copy paste that on every page. I don't want to do a copy page. So I want to like use a config for it. So it was like, we can, we can make a component. And we can, we could, yeah, that, that might, we can create a partial in Antora. Oh, that, that works to you. Yeah. And then we can include that partial on all the work in progress pages. Yeah. So does Antora have a concept of that variable that's, that's defined in that ASCII doc file? Or no, it's only, it does not. Okay. Thank you. No, it does not. Okay, but can we define something similar? Like when it's hard to turn on like a flag, we show like the work in progress page. So the, because Antora does not actually read all this layout section, it does it, the, the minimum, the standard page structure is just says your title and start like writing whatever you want. Yeah, but can we, can we customize like if we go back to Antora page? Does it say we can customize the icon? Or is it just a page? Yeah, we can, we can custom, we can customize this admonition block. Okay. But it, it will then, yeah, I can, I can do that. I can do that. We can, we can create, no, wait, I can, I can try updating the UI project and add a warning for work in progress, which will show that on pages where like we have actual warnings on, we'll have, we'll have something like this because I have like updated how the, here, the UI, which I am creating, it, it show, it will have warning here and yellow color. Okay. But how does, how does this work compared to the fact for the work in progress? The question? Yeah. Yeah. So I can, I can like create like I can update, I can update the admonition block, keeping the previous one too and one for the working progress one. Okay. Or we can, we can, we can, let's check that. Have you ever kept a record of all the like the other ones besides work in progress that we need to account for? I haven't like, I see, I saw some work in, I've saw some work in progress files and I just pushed my changes. So I just, I just saw that it was not working like five minutes ago. So, but I think, I think using a partial would be much easier to like add. I think for, for, for work in progress, it's easy to use a partial to like, yeah. Yeah. We can just add a partial. Okay. Yeah, sure. Anything else you want to report on? No, I, I, I will, I will like, put the tutorials and resources tomorrow. And after that, I'll have to like, correct the links on all the pages. So I'm thinking about writing a script. So I'll start working on the script. Yes. After the day after tomorrow. Yeah, sure. Yeah, sure. But I'm just wondering if you, we can use the trouble. I just created. So if do you still like to it? I didn't quite catch you Chris. Trello. Trello. Yeah. I joined, I joined it. Can, can you create some tickets for it so we can track where progress because like we, you're not opening PRs on your like way. Trello. Yep. Yep. I joined it with my phone. I have to see. Yeah. Yeah. Okay. Like I do I have to try creating a card? Yep. Thanks. Oh yeah. Cause I quit some for you, but. Yeah. I saw the existing ones. Update the existing links to Intura. How Intura reads links. And includes. Yeah. Yeah. I can. Okay. Yeah, sure. That's good. That's one thing existing links. Let me add an actual item on the dogs too. So we have that. Let me see. So this one too. At. Square. Okay. Anything else you want to report on? No, this is all I have done after the after Thursday. But can we go through what you have done so far? Like what, what, what did you, what have you, like how much it's loved to do. In comparison to what we have on Jenkins.io. In comparison to Jenkins.io. First I'll have to like support tutorials and resources. Then. Then how Mark pointed out that special page where we in the pipeline. Like we, where we can like search for things. I do the special pages are the ones which I'll work on later. But I'm constantly checking if anything is wrong with them or not. So like I can, I can research while working while working on other things. Okay. Sure. You show us what you have currently with Antora. Yeah. With Antora, I currently have Jenkins main home page. I still have to put all the images because they are not in the same folder. So like I'll have to search for I'll download the complete project and like put them in the right places. So I think it will, that will be like time taking. So it would be done by next Saturday. Where next by next Saturday we'll have complete user docs and developer docs. I guess. If everything goes well. Yeah. I'm, you may have already explained it to others, but it would help me if, if you could help me understand what's, so what's the difference between the images in the, in the current site, the Jenkins.io repository. And where we're going in Antora and Torah assumes some different things about the location of the pictures or. Yes. Tell us more about it. I'll show you how they organize the files. Images. Okay. I'll just show it from here. In Antora, I have these modules and these modules has the, have these assets where we can add attachments and images. So like each with all the pages in a module will first read the images from the images folder, the assets folder from the images. So I'll have to put them in the images folder in each module. Currently on our site, we have images on like, we have images on different, in a different folder. Some images are some, some images are on a different folder for documentation and developer documentation and user documentation. Wait, I'll. I think it's on the content. So is that one? Yeah. The images, the images folder. Yeah. I'll have to download all of this. And in this, I blue, like, like I have created the blue ocean, blue ocean part. Blue ocean section, blue ocean section. All the images for blue ocean will be here, will be in here. So I'll download this and put them in the correct, incorrect, correct files. Do you mean like currently within toys by module, right? Yeah. The image folder goes with the module. Yeah, I'll have to follow that structure only. Okay. So, so there and Torah doesn't have a way to augment or extend the search path for images like we use with Ostrich and ASCII doc today. If it has a, then I'll have to like, I'll have to put the part, part of each image, part of each image there. If I show you how, how we like add images in Ostrich content. I think it's content doc, right? It's content doc book. Where, where, where was I, I was in creating pipelines, creating pipelines. Yeah. So up at the top, there is that, that very top of the top of the, what do you call it at the top of the file. There's the images. It's directory, images directory. Yeah. And that's not a concept that and Torah has. Yeah, it does not have, I'll have to like put the complete path. If, like, if I just put all the images in one place and then reference them from there, then I'll have to write the complete path. Okay. Which will be equally like, which will be equally time wasting, I guess you can say. Okay. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. And Torah really doesn't have a concept of look in another location for images. It wants them in exactly the location it's defined. Make sense. Okay. Thank you. Yeah. I don't know a question though. It was like, um, how do we keep track of the current documentation and any changes to it before our project is finalized? Because like, um, I might have, I might have been updated by contributors. Yeah. I, because it is a common problem by like till September, many of the files will be like updated by the contributor. So I was thinking about checking, checking the commits. Checking the comments on all that, like checking the comments. Or like, we can like manage a spreadsheet for that. Yeah, that would be good. Like if, if any of the documentation files are updated, we can like update that there that I'll have. So later I'll just update the updated for one last time. So everything will be up to date. So, so. We can't just, I would have initially thought, oh, manage this as a fork of the repository and use get commands to do the moves so that get would help us do that. I assume your current working repository is not actually a fork of Jenkins.io, is it? No, it is a complete new project. Right. And that's a lot tidier. So, so I think some other means rather than using get to track the changes probably is what we'll have to do. Okay. Yeah, but, but if you, if you like, if we look in for think for the future, when we'll, when I'll start working on the blogs, the blogs have much more amount of images. And the same problem like the same problem problem would be there. Yeah. Well, but, but the blog images are the blog content in general is much less likely to change than this documentation on creating a pipeline or on a tutorial. So because blogs tend to be written once and never modified. Yeah. Okay. Thanks for the clarification. Yeah. We'll have to, we'll have to like track this, these changes somewhere. So like, I can update them later before like, we actually host docs.enter.io, docs.genkins.io. And are you currently watching the Waipo show on GitHub? Nope. I'm, I'm currently like, I, I, I sometimes glance over the issues, but like, like not actually reading what they are about. Okay. Yeah. The reason you found a way to keep track of all the changes. Other than or, or like I said, we can just look at the comments, the more, the more I can, the more recent comments, the files, which will have more recent comments, I'll update them nonetheless. Yeah. Yeah. Okay. That's from my site. I want, I wanted, I wanted your guys and put on the like the look of the site. I'm very impressed. I am really thrilled. I, I like that. I forget, maybe it was even you who did all the work to get us so that the left hand navigation was static was held steady on the current site. And I like this layout even better. This looks great to me. I think you've done a brilliant job there with the, and I, I hope it came for with low, with low, relatively low effort thanks to Antora. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. So the creating dash plie pipelines. I assume those will get a title that's not just the title of the file. Yes, yes, yes. Like I said, I just pushed these changes and I was testing them out. Right. Then I saw like, oh, it's time for the meeting. Yeah. I'll, I'll update all this and send a record. I send a video recording screen recording of how the complete user documentation will look. Like tutorials and solutions. Very good. Yeah, Chris. That's from my site. Okay. So let me stop sharing. Okay. So let me share my screen for the document. So currently I have three action items. So one is to complete the script. Yeah. I kind of think that the first is overlapping of the second. It's to complete a user developer docs. Bye next Saturday. Yeah. Bye. So also for an item to open tickets on trial. Anything you can think of, I should add to it. No, I think it's like, it sums it up. Okay. So why, why are you pushing a code to you? When you're you like, you just, um, it's a way we can keep track of like incremental changes or like, um, What you would, are you working by branches now or not really? No, I'm just pushing to the main right now. Okay. So maybe after you're done with the developer dog. Is it okay for you to work on a branch and stuff like the main. Okay. Chris is, is your concern wanting. Vandy, you're using a public repository, right? So the rest of us could certainly open your repository, build it and look at it ourselves or, or is the build process more complicated than that? No, it's not. Um, the way I want, I want them to host like a version. V a, let's say like in a pages first. If we can do so. I want to go by branches. Yeah, so I'll set, I'll set up GitHub pages for that. So like we can like show the community as well. Okay. Existing. Is it main branch? Yeah. Okay. Okay. And we should afterwards, um, once you have a product to show, we should, um, start another email. Yeah. Yeah. Uh, anything, anything else from you guys for Jeff, you mean? No, for a moment. I like his work. I'm impressed about his page. Yeah. Me too. How about you? Not for myself. Yeah. It's very clean. Also like, yeah. So branches, we'll be making a branches. So I'm going to create a PR, right? Uh, the changes you're doing. Yeah. I think so I can like bring you guys for a review. I should use branches. Oh, yeah. Yeah. Okay. Sounds good. So, um, let's make him next Saturday. Same time. Yeah. Okay. Any, any other questions you have for us? And before you go. No, everything is fine. Okay. I have one last question. Yeah. So, uh, will the, uh, will the poor request be sent to the. Uh, get her. Yeah. Yeah. Okay. Thanks. Okay. I got a question for you though. Like, could you send the final length test again? Cause like, I think you sent out three before, but I think only two are currently in use. Uh, I didn't quite get that you Chris. So, uh, yes, you have sent out three. Yeah. Yeah. I think only two are in use by you. Yeah. Yeah. Jenkins UI is not used. You, I'm not using Jenkins UI. Uh, I'm only using Jenkins, uh, docs and Jenkins UI project. Okay. Could you send those again? Yeah, I can. Yeah. Yeah. Yeah. I'll send the links to the, uh, Gitter. Okay. Thanks. Okay. Thank you. Thanks everyone.