 Hey everyone, I'm super excited to see you all here at popcorn Europe and this is the main character of your story, the cloud native way of technical writing. Hey, I am Karuna and I am studying data science previously worked as a coach at major late hacking and I have also been a technical writer at a single API and I recently started contributing to a bunch of documentation. A fun fact about me, I have tried 15 Linux distribution. So since this is the stock is called as a be the main character. So let me tell you a story. Before that we all might have seen or connected with a lot of CNCF contributors who code, right? Well, is that the only way? Nope, they can contribute in a number of ways and technical writing is one of them. So let me introduce you to two characters here. We have sq and tag. So sq is wondering how can they contribute? Because contributing to CNCF is kind of difficult sometimes and there is tag. So tag has been contributing to CNCF since a long time. Procoder does everything well. Now we all can relate to sq at some point of time where we were new struggling, figuring out things or just blaming the system. Why is it so difficult to contribute to CNCF? Or why is every single issue taken? Or why is the code based so large that we can't understand now? How can I be the main character coming to the main question? Now, let's see. Let's build upon sq skills. What sq needs to do to be the main character find folks who are already contributing and ask them. How did they start or learn from their journey and sq will find a lot of beginner contributors just like them. Also, you can join the meetings of CNCF to know more about the people getting involved there also trying out the new technology now trying out can be a fun and exciting way to learn new things. You might discover features or bugs. Yeah, they might know it's like it's not existing but when you try out, you will know. Oh, there is a bug now. You raise the issue to improve it. There you go. Your first contribution to CNCF now next is explain it in the simplest way simplest possible way to know how well you understood explain it to someone who doesn't know about it and then try ask them if they understood it. If yes, that is a great sign that you have understood it really well. Next steps learn concepts of Kubernetes or CNCF. They both have Kubernetes Clushery and CNCF. You can learn from this from them. They have amazing documentation right now too. So you can learn from them and build upon your skills. Next is start blogging now once you're trying once you're trying out tools explaining to someone who doesn't know about it. It's time to share it with the world. Start building upon your writing skills, start blogging and try to explain it convey your words, how you speak by doing technical writing. Now are you feeling confident? Start by contributing to CNCF Clushery. That's the first step. You can contribute to CNCF Clushery as it is really big enough friendly. Don't give up if you don't find opportunities right away. Don't feel like oh, there are no opportunities for technical writing. Why did I come into the string? Well, there are a few. Let me share it with you. A layer file writing program. So that is a complete program dedicated to technical writing where you can submit tutorials and you can submit blogs. You can submit articles videos about how can others use their tools. Contribute to documentations of organizations like Fluent, ATCD plus they all welcome your contributions. And there are also a lot of CNCF projects participating in Google Season of Talk. So you can check out those projects and you can apply it to the next season of Google Summer of Season of Talk. So lesson at the end one can be a main character. We all know that cloud native technologies are really really complex. Many projects heavily rely on technical writers and documentation and open source. Usually does not have assigned technical writers and if the community does not step forward to contribute to the documentation, the documentation to remove will remain as it is with no improvement. People, particular students or someone who's really getting started with CNCF right now will have a fresh perspective and will be able to contribute to improvements. Docs are as important as code. Let's not forget that. Now, what's next part after this talk? Scan this QR code for resources. I have collected all of the opportunities for you to get started or showcase your technical writing and please leave your valuable feedback or if you have any questions and thank you for listening. Have a great day.