 Again, I come from pretty much the same background as Steph. I don't have a lot of background in coding, so I decided to take a project which is kind of related to what I usually do within the PL. As Steph has already pointed out, there are a lot of problems when it comes to documentation, especially the documentation around Filecoin and the loader implementation of the Filecoin. To quickly go through some points, it's really hard to find what you're looking for, especially in terms of a new storage provider or even somebody who just want to try out loader implementation. That's a bit tricky. People usually end up just asking on Slack, hey, how do I do this, where do I find that? So many problems. That should not be happening in the first place. That was the main aim of the project, that people should directly just go and look at the docs and they should be able to understand pretty much all of it. Another problem is a lot of documentation, which is currently in there, does assume a certain technical expertise on the part of the user, like you should know how to build it, in which situation building it is better than directly downloading an artifact and using it and so on and so forth. And of course, one of the biggest pain point is there's literally no troubleshooting section, like a dedicated troubleshooting section, which tracks known issues and their known solutions, or maybe an article about how you can debug a particular kind of problem. Of course, there is no way for such a large community, right? We have such a large community who are storage providers, retrieval providers and all of those people, they have so much knowledge and so much experience, but currently we are not able to utilize it very effectively. A lot of those conversations just directly go on Slack and that's not an effective way. OK, so what's the solution, right? So the first problem that I saw was the documentation itself is like literally just one big documentation with so many sections and so many pages. It's hard to figure out what to look at. So the first thing we did was literally break the website and five, six big chance one would be Lotus, which would just handle the Lotus part of things. So you can be a client, you could be running a Lotus light node, you could be running a Lotus full node, whatever you want to do, just focus on this section. Anything Lotus goes there. If you're an SP, you just focus on this section. It's going to have all the links to the other section that you're supposed to know about. It's going to be properly collated with the other section. So you don't have to start jumping from section to section directly. Then of course, a very dedicated section for developers. Currently, it was a bit of a mess. Some of the local network issues have been sorted and the documentation has been updated going forward. This section would get more pages, especially about API examples and how to use simple code to try to debug, you know, if you're trying to build an app on top of Lotus. And of course, a new section for tutorials, right? A lot of people, especially in launchpad phase, you know, a tons of problem when trying to start the Lotus node or connect to API chain love and so on and so forth. So right now I'm writing tutorials on how to run a minor, how to add you know, worker nodes, how to set up a Lotus. So these would be like, you know, you just follow this guide and it's going to be done at the end of it. You don't need to know other stuff. Then a dedicated section for knowledge base, right? This is where we are going to collect everything. This is what it is going to look like, you know, going forward and the left side pane would now be dedicated to basically it would contain an umbrella sections to, you know, bundle the pages together by their relevancy. And of course, apart from that, the knowledge base is, as I said, it's very important. So we're going to take all those file coin discussions on Slack and create knowledge articles and solutions articles based on those. And we are also going to encourage the community to, you know, basically contribute to this part of the section so they can start putting on their knowledge there. And lastly, the blog sections. So blog section is mostly about, you know, show and tell people different minors, what they're running, how they do it, how what are their scripts that they have written to automate stuff, how they're monitoring their minors and all of that. Currently, it is all very distributed. Some of it is inside the Lotus repo. Some of it is on the file coin blog section. And it's a little hard to try to find all of this, you know, information out there. So I just want to put it all in the same place. You just go to this website and you're done with the Lotus part. So this is what it would typically look like. And this is just a very first draft. We are still working through the PR there were some issues. So this is what it's going to look like. And as you can see, like the storage provider section has now been broken into four different categories. First getting started. Now it will have all the economics of the file coin, hardware requirement, mining architecture, what should you know before you actually start thinking about being a storage provider? Right. Then you go to the how to set it up. What are the different configuration that you should know about? And you can adjust. Then you have daily operations, which would contain all the pages which are about doing, you know, typical operations when you are a storage provider. And then, of course, a dedicated session, a scene focus, which doesn't have a lot of information, but it's going to get more pages in the future. What are the advantages of going with this approach? Right. So the first one is, of course, making it easier for people to actually find everything. And the second big one would be when we add the knowledge base section, right? People can directly just put their error code in the search bar. And if there is a solution that exists already, we're going to have it. Otherwise, when they find the solution, they can contribute that solution back to the website. And this way, we'll have a good feedback mechanism and a very big collection of knowledge articles out there. And of course, as I said, the blog section would be about show and tell and anything which is, you know, not your typical technical part of it, just how we do things. So that's going to be there. And I've also enabled flexible typing. Basically, if you create an article, you can tag what part of Lotus does it deal with or what subsystem the problem could be in. So it is truly flexible. You can, I mean, of course, we will be reviewing the PR when you add a new article out there. So just to make sure that, you know, it's not some weird name out there, but basically people are free to target how accurate they want to tag it. So there are no predefined tags by PL anymore. So that's a good thing. And of course, the search function works in blogs as well. So it's possible that something that you're trying to do or trying to find might already be written out there. And you can quickly search for it. This is just, I quickly took some snapshots of how it looks like screenshots. This is what the knowledge base is. And as you can see on the left pane, our types are, if it is a solution to a very exact problem or the other type would be articles, these would be long articles, how to articles, long debugging articles and all of that. Areas would be the tags, whatever tag you want to put it in. Right. It could be that, okay, this is related to base OS issue. It could be related to a Linux issue, so on and so forth. And on the other screenshot, you can see, I simply put the error code soft FD limit. You get this error code when you first start Lotus. A lot of people get it. So you just put it there and it is pointing you to the solution on how to fix it. So no need to search through the whole documentation. Okay. So what's the current status? So, yeah, I, all the changes that I wanted to get done, I have put them in a PR and, but unfortunately, I think I might have broken some CSS things while training around because I made a lot of changes to the website. And so right now, doc steam is helping me sort through all of that. So they closed my PR and have started pulling one by one, all the comments on their PR and they're making sure that CSS is working exactly how it is supposed to be. And hopefully this will be merged in next one or two weeks and you'll be able to see the new structure out there. What's next? I'm pretty much going on the same line as what Steph has been trying to do. And I'm going to, you know, work with him more closely now to get it done properly. And of course, you know, I have seen a lot of challenges that we as cadets faced when we started, you know, trying to work with Filecoin and especially the Lotus implementation. So there are total three projects that came out of all of this first is, of course, we are auditing the documents completely end to end all the Lotus documentation each and every single page, each and every single line would be audited and if it requires a change, it would be, you know, changed as per, you know, to make sure that it is more easily readable and the content is understood or if there is anything missing there, that would be added as well. Apart from that, as I said, I'm planning to add more detailed tutorials on how to do things so people don't have to go and look at different parts of the documentation to get a simple task like, you know, getting a notice note started. The next problem again, Steph has already pointed it out. We have some problem with artifact builds. I have identified a few things and already let the Lotus team know and we are going to talk to infra people because infra team actually handles the CircleCI for us. And I have taken a look at that particular build code. There are definitely some challenges there. So we're going to audit that as well and try to fix that CI CD pipeline so we don't have all of that. And I'll work with Steph to get all of this properly, you know, so it can all be monitored and automated as much as possible. So any failures out there can be easily pointed out and fixed. So thank you so much, everybody who has actually helped me in one way or another to find this project and point out all the problems that are there, because ultimately that is what led to this project. And hopefully it will improve, you know, the user experience down the line. And thank you so much for every helping me make this work. And shout out to everybody, you know, all the candidates and every mentor and of course, Lindsay, wow, you gave us so many points. So this was a really nice card. So thank you so much. Thank you, everybody.