Now that we've worked really hard in this session, All the different types of reuse. What do we need to do? We need to finally publish our content. Let's see how we can publish and we're able to choose which variables and which profiling we want to use and also save them. So we don't have to recreate that logic again. We can just publish them again later or even call from the API or bulk publish, but let's get that ready so we can publish our content out with the settings that we need. We've worked on our content, created variables, defined our profiling, filtering, conditions? Let's see the fruits of our labors. Let's see what the content looks like as a result of our efforts. So what we'll do, we'll go to our publication, as we know already. We'll click the three dots and go to publish. This shows me the different options I have for publishing. So at the top I have my different types of channels, my different outputs, I can use. And firstly, let's create a PDF, create some PDF, and underneath in this list, drop-down list of all the layouts that I've created will which we'll explain in a different session, one that I've created to call the sample PDF automobile. We'll choose that. If we have different languages, we'd select them here, profiling attributes. So we want to go for, let's create this one for beginners, and the version will be version three. And, obviously, the output format is going to be for a PDF. That should all make sense after the work we did previously. For variables, let's go down to the group that we created called recordings, and we'll select product A. And okay. Now if we had some integrations with, for example, GitHub or Bitbucket, Netlify, GitLab, FTP, Amazon S3. As your repos, you could also automatically push the content there. So CICD, the continuous development, can be an integral part of your Paligo workflow as well. Now rather than just clicking publish, which I can do here, I wanna save the settings so I don't need to essentially reproduce the logic at another point. So I go to save settings. And some sort of brief description that will remind me. So whatever code or syntax that you use. Just keep it consistent so you everybody in your system, everybody using Paligo can understand what you've done and click okay. So next time, I just need to go to save settings. Click on the icon or multiple icons if they're there and publish, and the content is now being published. At the same time, let's do the same thing for HTML5 output. So I'll go to publish. HTML5. And I'll just choose one which is very similar to the default output. Just one or two small changes. The profiling attributes, So we're going to say for this one, the audience will be experts, and the output will obviously be HTML5. And we'll make the version, version two and click okay. Let's save this one. I'll just call it H5. For speed purposes now. So I can go to save settings, click on the icon and publish that out as well. Paligo has created zip files for me. And whether using Windows or a Mac, You just want to expand the zip file. So PDF open that file. For an HTML file, you'll open the first index HTML file that you see. So let's have a look at what we've done. Here we have the PDF that we created. We can see a logo. We can see a nice picture on the front page with a title. We've got some metadata. We've got the subtitle at the bottom. The second page contains them. Additional information, this is all optional copyright notes, whatever you wanna put in. We have a working table of contents. We can see with the links, work as well. You can see the mouse over. You can create headers and footers, left right, middle images, text, dynamic text, title name, chapter name, all these types of things are very simple to do. We can see here's our welcome page. We have the variable in there: product A, and you can see beginners exist. No experts, version two doesn't exist, and we see just the PDF, not the HTML. So it's Word with all the filters and variables that we use, isn't that really exciting to see? And the rest of our content. Now let's have a look at HTML5. And here's our HTML5 output, a really professional looking output. We have categories or top levels here on the top. We have a search button, and the search works of I just type with our out of the box, searches you immediately get content, search content as you type. If I click on to 'welcome to product day', you also have the variable 'product day'. This time I wanted version two in there, it says HTML rather than PDF. As a side, comment, all of the branding and the colors can be changed via normal CSS, even drop some JavaScript if you wanna do some clever things like adding widgets, or, moving things around or adding headers and footers, all sorts of options on that, but you just need, let's say, solid CSS skills that you maybe have or somebody from your team, or you can also speak to us. I'm a quick look as we go through this this content. See, all the content we created is here, and it's all configurable as well. And the images open up as light boxes, large pictures as well. So you got a quick professional output, really without any effort that you've put in there. Let me show you just a couple of examples of customers: what they have done with the Paligo outputs. This is an output I've just downloaded directly from the web from native instruments. For those of you in the music industry, you'll know this company pretty well. And just a quick browse through, you'll see it's a very professional, very tight branded PDF for their company. And really, this isn't a lot of work at all in what we call the layout editor to create this output. They've decided to put numbering on some of the sections. And not all the levels of sections, again, easily configurable whatever you'd like to do. Let's also have a look at HTML5. Couple of options. So if we look at volume, a lot of interesting things happening on this HTML5 output. First of all, I believe this is HubSpot. They put a chat in. They didn't need to come to Paligo for a customization. They just dropped in the JavaScript widget that makes that work. They happen to use Freshdesk for support, a little widget again, that opens a pop up box so they can add the information for the support ticket. As we scroll down, you'll see they have accordions drop-downs where you, can see additional content, and they've put animated GIFs in here. It really does look great at this output. And they've got a customized footer, large footer at the bottom, which they added via a little bit of JavaScript. And was this helpful, which is also built in where you could even send content back to whatever email you provide so your customers can give you comments on the content or whatever's related to it. Let's look at an additional example from Moogsoft. They have their regular content, but for those of you who have multiple versions of your products out on the market. Therefore, you have multiple versions of your content. It's very simple to create this drop down. She can easily move between the different versions. So not only are you able to manage versions inside Paligo, which is another video that we've released for you to to watch. We also have versioning outside for your customers using HTML5 output simply and out the box. Let's just take one quick look at one of their pieces of content. There we have a nice picture. We have links or the links work. I think that gives you all an idea. We've succeeded. We've reused content, and we've published it, and we had very professional output. As a result. Okay. I actually don't know if I'd called chunking fun, but just give me the flexibility of language do that. We're gonna have a look at a chunking. What chunking actually allows you to do is take one angle of chunking is I could actually have a publication with lots of levels but say, you know what, I don't want to have all those levels in the output. I wanna put the children as part of a parent so to speak, which can be really useful flexibility of how you build your your structure and your publication. Chunking. Here we go. Let's build a scenario before I actually show you chunking just so it's easier to understand. So let's take our application here. I just want to add a few extra topics and let me just take them from the tutorial folder. Let's take this one. On this one. Let me open up. Let's put this one underneath and underneath Okay. And I'll save. So if we look at this, if we're publishing to HTML because chunking is not so relevant, for a PDF. You'd expect under publishing, including publishing to have four topics. Publishing would be a topic. We're using content via topic. Then images would be a topic and lists would be a topic. So we expect to have four topics. What about, and if you remember we did insert components and reuse structure, maybe I don't want images and lists to be their own individual independent topics. I just want there to be sub topics and inside the reusing content topic. In other words, when I have a web page, it'll have reusing content with two subsections, one images, and one lists. That's what chunking is gonna do. Chunking basically says chunk stuff, chunk the children inside the parent. Let's we've got a big hierarchy, so we're going to put the stuff underneath inside a larger one. It's the same as doing insert component that we've done before, we've done previously together. So how would I do that? Cause right now, it's going to produce four separate topics. So I'll go into reusing content. I'll click on the edit button. And it's really quite easy. Technically, it's very easy. Just need to understand. I go to the top section, attributes, and you can all have a guess. There's one called x info chunk, and I set it as yes. When I set that as yes, It means everything underneath is going to be part of reusing content. So you won't see it here and if if even if I do a preview, you won't see it here either because if you just shows you this topic, it's not showing you the publication. When we actually publish, then you'll see. I'm gonna show you very quickly how to do that. First, we'll save this. In a future session, I'm gonna show you all about layouts. But I'm just gonna very quickly open a new layout so I can just show you what we've done here. Creating a layout and as I say I'll explain this in another session, I'm gonna open a layout that I've created for HTML5. I'm gonna choose a document as a preview. So we're gonna go to recordings, what we've been working on here. Open our publication. It's essentially, rather than downloading, it's doing a preview of my whole HTML5. It opens up as if it's on a small machine. So I'm gonna click on full screen. If I go to publishing, if I click on reusing content, it's got images, and it's got lists. Just click on that. So those two topics that we created over here are now part of that one topic. That's what chunking is. In the layout editor, there are options for chunking. You can set levels. So again, maybe you'll understand this a bit more later, but if we're here, I'll show you. If we go to token chunking for the HTML5, well, first of all, I can actually set what level my table of contents should be. That actually means this on the left, how many levels did I want? I could have a publication with five or six levels. So I really just want to show three levels in the right table of content in my navigation on the left. That's what that does. It doesn't remove content. It doesn't show in the navigation. But this is the chunk section depth. So, for example, if I set the number as three, if I by default have say four or five levels, they will always be brought into that third level topic. You'd never have a fourth or fifth level. What we did before is we manually said, okay, put everything inside. Here, we can't go below three. If we wanted to, then what you would do on one of the children, let's say in our case, we'd set it as this is actually two, but let's say imagine it was, but let's put lists here for a second, something like that. And our our limit is three. So I'd actually go into lists. I'd go to the top here. And I'd go chunk, and I'd tell it. No. That way, even though it's meant to be chunked, And I don't want to be chunked and lists would be its own topic. There's also help articles on this, but this kinda just gives you an idea. It's an alternative way in order to organize your content. And I give you just my personal opinion. I actually like doing it all in the publication. Rather than doing it as insert component or doing it, if you remember, we can go to any topic and do edit structure, open structure from there. Because I see everything here. And if I have a whole bunch of topics, I can move them around much easier, full visibility, not just of the publication, but also of the order of every topic. It's an individual thing. There's no right and there's no wrong, but that's how I would do it. And I think it's very helpful. Another reason you might want to do that, there's a limit that some of you might have found that we have a piece. We have a piece of advice, you shouldn't put more than ten sections or components into a single topic. It's just not good practice to do so. So that is a way to avoid that problem because I could put, for example, ten topics here underneath me using content. Put twelve topics here. That restriction is not relevant here. So I could do it by chunking to get the same effect and not to have the restriction of ten sections in one topic.