So let's start off just by making a new publication. So we'll click on the folder, select create content, click publication, and call it 'super duper'. So it's gonna be a big publication. Let's open it. So I could drag SaaS application into here, and I could, for example, drag 'getting started' into here. I now have two separate publications. But if I publish, they'd have two categories, two top levels, one SaaS application, one getting started with Paligo, and it's just bringing all the content in together. So it's very simple. So I gave two cases before, multiple products with their own... each with their own publication. You just take all of those and drag them in, all the separate modules, and drag them in. One, that's a side comment that you can set in the layout editor. Let's say that the case that we had before, but but I just wanna split up chapters one to five in one sub publication, and chapters six to ten in a second publication. And I want chapters one to five and six to ten. And I don't want to see a top level. I don't wanna see, for example, SaaS application. I just wanna see chapters one to five and six to ten in the second one. There's an option in the layout editor where we can say ignore the top level of a sub publication and just bring in everything that's inside that publication instead. That would allow us to do chapters one to ten, and nobody would know who actually stored them in two separate publications. This could be very useful for you as you're building your strategy, gives you the flexibility to keep everything in one large publication or split up according to the different types of use cases as we've discussed. Now here's something maybe not everybody knows, so it's good we're doing this. You can actually reuse part of a publication in another publication. Let me show you what I mean. So I'll open 'Super Duper', which I didn't save, so it's now empty. Let's say I just want to use the introduction together with the video 'about us' that happens to be inside another publication. I don't want to reuse everything. So if I just drag this over, it's just dragging the topic like anything else. But if I shift and drag on the icon, notice it actually brings in the structure. So even if I were to change what's inside of here, but I've got another topic, it'll always match what's in the original publication. So let's say this is we just use the word chapter for for an example. So it'll always bring in the introduction chapter into this 'super duper' publication. Even if I change the introduction structure, it'll be changed here as well. So I don't always need to use the whole publication. I can reuse part of the publication. Remember, to shift clicks, you see that icon, so it's reusing the actual structure itself. Now we're moving on to something else. Let's say you've got some reusable content. Maybe it's a copyright notice. Maybe it's a procedure you want to use in different places or a table. But it's not a whole topic like we've seen before with a title at the top and everything else underneath. Snippet or chunk of reusable content, maybe we'd call it, and some products actually do call them snippets, informal topics. So reusable content, but it's not stand alone. You can't drag it into a publication. That has to go inside something else. Let's take a look. So back in Paligo, first thing I'm gonna do then is create a new informal topic. So let's go to the topics folder, create content. This time, it's called an informal topic. Table, we want to reuse. And there's got a slightly different icon. Let's click and open it. So you'll notice here it doesn't have a section at the top like it had with topics. We have a sidebar. A sidebar is really just a container of anything we want to include. It could also be just be a sidebar by itself inside a topic as well for whatever reason, but a informal topic is a sidebar. I don't want the paragraph, so let's get rid of the paragraph. And we could put a title if we want to as well. You know, let's put a title in, but we don't need to. We'll call it an example table. And I want to put a table underneath, and we did this in the authoring recording. So insert table like this. New title, two by two. I'll just quickly put some information here. Okay. There's my example table, and I'll save. Say I want to reuse it somewhere. So let's go to video 'about us', and I wanna say put it here underneath the video. So I just reinsert the component like we did with the regular topic. Insert component. And, well, let's go down. We are already in recordings. In the informal topic. And there we have an example table. And if we do a preview, HTML5. There's our video, there's our table, and there's the content that was underneath. Really quite good. Right? Let me just show something maybe extra extra clever here. Maybe the same way, if you remember, we made this section, this mini section into an accordion. Do the same thing for an informal topic. Let's just do that quickly. Go back into our informal topic. Go to the sidebar, go to the attribute, we'll call it 'role', and we will type in 'accordion', do a save, go back into video 'about us', and do a preview. As you can see now, the informal topic with the title we gave it is now an accordion. Now I want to show you a really snazzy or cool use of an informal topic. So a few years ago, I actually did a webinar in 2018. You'll actually see it on YouTube. Have a look and find it. And let's have a look at this. This is actually a regular sidebar, a regular informal topic with a procedure with a special role, and so I'll explain in the help, called reuse range, nothing to do with x. And what this basically says, this accord this this attributes is I can use it inside another procedure to update that procedure accordingly. If I didn't put this in, it's like putting a totally new procedure and you have to put it in the right place. So let me show you. If I go into reusing a range of steps here, and I could put maybe this list in the middle between one and two, and I'm gonna put it at the beginning, at the top procedure level. If we put it here, for example, it wouldn't make sense. It's coming in like it's regular steps in the procedure. And if I go insert component, and this time I'll do a search. And if I click on the informal topic we were looking at a second ago, you can see now it's updated the list one, two, three, four. And if I preview, then you can try this yourselves later. It will just show it for the customer as if it's a normal list of one, two, three, four. It's really quite useful. Let's say you have, you know, a procedure, but very common, say, start to it. Log in to the system, click on the dashboard, click the view icon. So you could actually create that as an informal topic and reuse that in larger steps. Just makes life quicker and more efficient for you. Let me show you some one other thing regarding informal topics. Let's call this advanced. But for those of you who are migrating your content, this might be useful to you. So if I go to, for an informal topic, or any topic informal topic, open structure, actually I'm actually able to switch. So component default means a topic. This is now an informal topic. If I wanted to, I could change it to a topic or vice versa. So just be careful with this and experiment before you do anything too dramatic. But if you've imported content and maybe you wanted to make things either in a formal topic or a topic or vice versa, this is quite a useful piece of functionality you might not know about. You might never use it or it could be particularly useful. Admonition reuse. Admonitions maybe is a term that people aren't so familiar with, like a note, warning, danger. So you might have those types of notes or dangers that you want to reuse in different parts of your content. I'd say it's a physical product. So you might want to say ensure it's disconnected from the mains before you open the back, and you might put that in multiple times. Let's take another look to see how admonitions are used inside Paligo. So here we are, introduction. And maybe the first thing we can do is actually create a new component. Create components. And we have here all these different types of admonitions: dangers, warnings, caution, notice, notes, important, tip. Maybe tip's not quite an admonition, but goes in the group of admonitions. So I wanna create a tip. So I get a tip, and we'll call it 'great'. It's a 'great idea', and let's even open it directly in the editor. So if I click on okay, there we have our tip. It's got a title. If you don't use a title, just it'll be by default called tip. A great idea is to read before you go to rest. Okay? Keeps the mind supple and ready for the next day. So I've saved that. I can go back now into my introduction. Say I just wanna put it here. I'd go 'insert component', and there it is. Great idea. The icon is the same for all the adminitions, but we know it's an admonition. And there you go. And you could put it anywhere inside a table, inside a bulleted list. It doesn't matter. So that's an easy way to do that. We could also create admonitions, which I think we did in the authoring session as well. We could create one here, and let's, for example, call it a note. Note read. Is this reusable currently anywhere else? No. It's not. What I could do, like we did with the section, we can go to note, convert to reusable component, and we'll just call it reading. Reuse the component at the same place, and now I've made this note into a reusable component, so it could be used in any other document, and I've put it here. And I'll just save so we have our content. And just to reiterate, if I actually go to reading now and go to edit open structure, it actually tells you where it's being reused. It's being reused in the component, a topic called introduction. I always know what's going on with my with my content.