 Great. So next up, we have Alexander Schradt from MSG System and he will be speaking about docs as code and I see the primary. Alex will explain the workshop and I'm just going to remind you that if you have any questions, please go to the Q&A section and we will read out about them later. So Alexander, I give you all the power here. Thanks for the introduction. Yeah, my name is Alexander or just Alex and I'll be the host for today's workshop. And it's all going to be about ASCII docs as code and let's dive right into it. I'll ask you to use the chat to interact here with me. I hear that maybe you heard about ASCII doc before or you have plans with ASCII doc. So now it's a good time to go to the chat and maybe paste or write a short note what you, if you've used ASCII doc before, the plans you might, you have about using ASCII doc in your project. So I'm very, very interested to hear that. So please go to the chat and just post a short statement here. Let's see who wants to share it and I will then read it to the group. David says, okay, so you have some experience. Let's talk to us code in the portal network, okay. Shandra Lecker writes that they use ASCII doc in the current project. So you have already some experience. That's great. But today you're going to be writing ASCII doc in a small web editor and maybe learn things about ASCII doc that you didn't know before and maybe experience that with a small team. So let's dive into the slides and say, well, ASCII doc, why do you, how do you write your docs? Well, sometimes you use an office suite. It's nice to print them or share them by making them around. But it's nothing that really works together with source control. Very good. And wikis are then also very, very difficult to share. They're also difficult to print if that's still needed. And while they're good at collaboration, they kind of are difficult to version documentation together with their software that you're writing in the git repository. So that's probably, that's usually problems wikis with a real continuous integration and continuous delivery setup that works both for text and documentation. And for your code, you want to have a documentation that you can search delivered by your continuous integration pipeline. You want to have code snippets in your documentation, like using real code that's tested by unit tests. You want to document your APIs, but you don't want to duplicate them when you write documentation. And ASCII doc can help you doing that. And while there are two things around in here that are not to be confused, and I always try to be exact here, if I don't make mistakes, please point them out to me. So ASCII doc is the language. So like the text that you write in the documentation, that's the, and ASCII doc is one of the tool changer that you can use to create HTML and PDFs from that. So ASCII doc is all about fiction as writing and using plain text. It has a feature rich syntax for technical documentation. It's been around for more than 15 years. And in 2020, standardization process started at the Eclipse Foundation. ASCII doc is then the tool train to create HTML and PDF from ASCII doc files. So it's all open source. It's written in Ruby, but also runs on Java Ruby and JavaScript runtimes and can be integrated in the build, like Maven, for example, or an NPM build, you choose it. And there's ASCII doc you write it in your IDE. So I'm also the maintainer, the current maintainer of the IntelliJ ASCII doc plugin. So when you write your content, you're actually not leaving your IDE. You stay focused. You don't switch any apps. And you collaborate with others using version control. That's what developers do. And also for technical writing, it helps a lot to version the content that you're writing. And while this plugin provides also support for Antora, so there's a full site builder for ASCII doc content. And about Antora, there will be a talk later today that I will also present and where you might pick up some other or deeper insights on how you built a documentation site for your users using ASCII doc and Antora. So there's IDE support in Eclipse and IntelliJ and Atom, which is to code and brackets and many others. And they provide you a live preview. If you type on the left, on the left side, usually in the editor and on the right, you will have a preview. And there are also, if you just want to have a preview and there are plugins for different browsers that help you there, all standalone editors like ASCII doc effects. Yeah, and let's dive into what I've brought you today. So you will dive into ASCII doc and learn together with others how to write ASCII doc. So I've brought you some, I would say, cutters or little writing challenges. There's a web editor that will have a scratch list on the left, a source code in the middle and a preview on the right. So it works just like an IDE, but it works in your browser and you don't have to install anything on your local PC. You can use your local IDE if you like, but you don't have to. Right. So I will show you in your live how this editor works. And I will also already post a link here to the chat for a Google Docs document that will provide lots of links that you will later need during the workshop. There's another link in the chat that will open a Google Docs document that should be read only for you. There's lots of links in there. So I'll show you the editor. So the editor. Oh, well, this is now the live view here. Let's close this here, give me a little bit more space. So I can type in here hello world on the left and it will give me a preview here on the right. If I start writing something in ASCII doc, make it maybe bold. That is the formatting for bold. It will show it in bold on the right. And this is a live preview. And the good thing is you can share this URL with others. And all the people who work in this one editor share the same document and can work collaboratively in a group exercise in these. So what I would, and we have one of these, well, cutters I call them. I presented to you as, for example, a formatting cutter. So the cutters itself was written in ASCII doc. So here on the left. And it's also between these equal signs. There's, you will see, I would say, the instructions. You also see links here. And it might look a bit confusing first. But then you then you can see a pre-rendered content here on the right and you can click on the link here. So you want, if you want to learn more about text formatting and punctuation, you click on this link and a new tab will open in your browser and tell you everything about formatting and punctuation that you can use to solve this. And down here, and you see another user already entered this. Does it cause up another user? And then you can type along with that other user to work on this exercise and say, okay, let's do some bold text. Let's make it bold. And this works. Well, as long as I scroll down here and you can then as a team find out how these different things work. Everybody can have their own kind of space here. Right. If you choose not to, well, I recommend to do this in this web editor to collect collaborative with others. And to do that really collaboratively, I would like you to share maybe voice, maybe your camera as well using Zoom breakout rooms. And I then therefore ask you, there's also a link in this Google Docs document for Zoom that you can enter. And if you then go to this document here, you will have the Zoom breakout rooms. I'm going to enter here, but I think I probably misconfigured them that I need to assign you to the different breakout rooms. You can't do that on your own. Then you, when you're in one of these rooms, you open this link, for example, the one for formatting, the one for images, and then start typing and while solving the little puzzles, I present it there for you. So while everybody is then entering Zoom, I would suppose, are there any questions that you want to discuss with me or that you have? You can put them in the chat or we then all meet in Zoom. And for those who want to do the group, want to do the cutters in their local IDEs without collaboration, you can follow the link down here. This will take you to GitHub. And on GitHub, you will find all the cutters with the text here, and you will then go to raw view. And then you can copy out this raw view to your IDE. Right. So I will then write into the chat. So leave a note for everybody who will join a bit later. Please click on link. And then join Zoom and pick group exercises. So the group exercises will be, as I said, will be about formatting text, images and diagrams, how to use lists to structure content, how to use source code, how to do structuring with sections, and how to use tables and ask a dog. And the idea behind these exercises, so you learn something today, how to do these, but you will also learn how to use the documentation of ask a dog. And with that knowledge, you will be an efficient, or you will train your muscle memory in terms of where to find things in the documentation and how to help yourself after today's workshop. I think we will give ourselves time until like 10 past the hour. So that will give you a good 20 minutes to work on one of these assignments that you choose. And then we will all meet again in Hopin. And for a Q&A session, and I'm happy to answer maybe questions that arise from today, or we will look at the group exercises, maybe look at some of the solutions that people are prepared there. And then later on, maybe show how that works in an IDE. Good. Let's move all over to Zoom and see how that works. So can I help? Yeah, right. You can click on the very left here where the user is and change your name if you want to click on this name here. And then Alman now changed their name. And if you mark some text, you will see also the person who marked the text or changed something. Right. That no works. It's good. So I hear someone is still having problems. So Alex, I'm not sure if you are listening to me, but maybe if you share the audio you're hearing Hopin, everyone could listen because there are new people and this will be recorded.