Rock U - Content Management - Advanced HTML Block

Transcribed Video Content

Okay. So we've looked at some of the basic settings of the HTML block. Now, let's look at some of more advanced settings. Okay. So let's go ahead and actually bring up the fly out for the block. And this time, let's look at the the properties, the block properties. And as you'll see that this block has a ton of block properties. And we're just gonna walk through some of these and, unpack what you can do with them. The first one is the enabled Lava commands. And if you look at into the, Lava area of, these videos, you'll see a lot more on these commands. And these commands are very very very powerful, but with great power comes great responsibility. And so for security reasons, you have to enable each of these commands that you want to actually use. So if you wanted to use, say for instance, some of the entity commands, you'd have to actually enable that on this block. Otherwise, they wouldn't be available. It will give you a nice warning that says, hey, this entity command is not enabled, which will remind you to come in here and actually set that. The next setting is this whether you wanna start in the Code Editor or the Wetzuig. And so the default is Code Editor, but you can actually change that. You don't wanna do use the Code Editor, you wanna use the Wetzuig. These next two, settings determine where to go to look for the the documents and the images when you use that image picker. So in this case, we're just using content, but in this in this maybe the use case for this one, might wanna say, no, I actually wanna look for, under intranet. And so you're not gonna let the person see the content folder, they're gonna start at the intranet level and they won't be able to go up any higher. I'm able to just paste that down here for the the image root two. Now, the next setting kind of relates to these two says user specific folders. And what that will do is actually create folders underneath these directories for each specific logged in person, each editor. So that keeps everybody's content kind of together and they can't see each other's content. This is great if you're using it maybe where you have a lot of, ley leaders and you don't want them to see the other files that are in there, you want them to see their own files. Okay. Moving down. Cache duration. So what this says is it can take a little bit of time to read this information out of the database. The cache duration is actually gonna say, hey, don't read it out of the database. Just keep a copy in memory and that'll be a lot faster. So this is the time in seconds that the content should be cached before it goes back to the database and looks again. Okay. So that's a ways of improving the, speed of your website. Now, one little tip here. If your content, in our case, we have personalized content, right, using the Lava, it has our our nickname. If it's if you're using personalized, Lava, you don't want to have a cache. Right? Because the first person who loads it, it'll have their name in it and then the next person who loads it, it'll have that first person's name in it. That's not what we want. Okay. So I'm gonna change that castration down to zero. Okay. So now we get into some context. So there's three different contacts contacts on this block. There's the context parameter, the context name, and then down here there's another context for the entity type. And let's talk about each in detail. Okay. So let's just say context parameter. Parameters referring to a parameter in the address. Okay. So say, my page might be loaded in several different ways based on a group. So I might say, hey, the if you see a group parameter, maybe a group ID parameter in the URL, I want the content to be specific to this group ID. Okay. So let's go ahead and actually just save this. Okay. So my content went away because I don't really have a group ID. So let's add a group ID. Group ID equals, let's say, 233. Okay. So I don't because you can see I don't have any content here. So let's add some content for when this is group two to 33. So let's say group number 233. Okay. Well, now I got content that's specific only to when this is up in the address. Okay. So let's make it 234. Okay. Don't have content for that one, so we'll add this content here. I'm gonna say group ID 234. Actually, let's make it kind of the same. There we go. Okay. Now again, if I go back to 233, I see the content for 233. If I go back to 234, so you get the gist. The content you that shows up in here is specific to whatever's in this URL. Okay. Let's go back to our settings. Okay. So we see how that works with the context parameter. How about context name? So this is very similar but instead of using a query string parameter, we're basically just gonna give it a name. Okay. So let's take this out and give it the context name of maybe test. And save it. We'll lose our content. I'm just gonna reload the page just to make sure everything gets reloaded right. And now I'm gonna add content here. So let's see. This is test content. Okay. So everything kinda looks the same. Right? Now, what this says is I don't really care what page you're on, always pull the content that has that test as the context name. And that allows me to go to other pages here and maybe on this block here I say, hey, I want the content here to be the same exact content that was on the other page. So if I give it the context name of test, I should see the same content. Okay. So this allows me to link content, the same content across different pages. And if I update it here, so let's prove that. Let's update this content. I'm gonna say two. And then go back to my first page, you'll see it says two. Okay. So that content is now linked. So that's pretty powerful. Let's go back to our settings. Okay. Now, the next setting here is enable versioning. And so what I can do with this is I can keep copies of the HTML that I'm editing. So I'm gonna turn that on. And while I'm doing that, I'm also gonna look at this approval. So what I can do here is say, hey, whatever changes are made to this content, I need to have approvals on that. So I'm gonna say go ahead and say yes and save. Okay. Reload my page. I'm gonna edit this content again. This is test content. Okay. So now I'm gonna change this again to this is new test content. And you can see here this is version one. I'm gonna go ahead and save this. Okay. Now I'm gonna edit it again. Now you can see this is actually version two. So let's do it again. So this is new new test content. Okay. Let's do it one more time. Okay. Now when I'm saving this, can actually check down here and say, hey, don't save this as a new version. Maybe I just made a minor tweak and I don't want to save that revision. I can go ahead and do that if I want. So I'm gonna go ahead and check that and say yes. Okay. So one more time. Let's just go in and this time let's click on history so we can see all those histories. Okay. So as you can see, we actually have some other ones as we're going through making changes before we enabled the history. Those are in here too. So if I want to revert to one of these, I can. I can go back and say, what, I really want version two, so I'm gonna select that. And now I have version two, and I can go ahead and save this and get that content back. Also note too that you have this display from and to. So what I can do is I can say, hey, what? I really want this change, but I want this change only to be, active between these this this date range. And so maybe I want to go up there and add maybe a special message for say, a Christmas message. And I don't have to I don't want to have to remember to come back and take it back off. So what I can do is I can enable versioning, so I have all those versions. I can make it to and from, and then that message after the it expires, it'll go back to the next one in the version, that does not have a date range attached to it or has a valid date range attached to it. This is a a great way to really kind of fire and forget. You don't have to put reminders on your calendar to go back and change things. You can just set it up correctly the first time and then just kind of walk away. Okay. So we talked about, approvals. So let's look at the security on this block. So I get the block security, I'll see my typical view, edit and administrate. And again, this is important so you can control who can actually edit this content. But you'll see that there's another verb here, security verb called approve. And here is where I'll define who actually has permissions to approve this content. Now, because I do have access to approve this, I get to see at the top here this little bar and it's already defaulted to approve. It's , hey, you're allowed to approve it so I'm not gonna make you approve it because you already have rights to. But if I didn't have rights to approve it, that wouldn't be shown. And instead, when I made my change, it wouldn't immediately show up on the page. It would be set as a version and someone would have to approve that version before it's actually displayed. And let me show you where you would do that approval. Okay. So under tools, there's a page here called HTML content approval. And this would actually show me any, items out there that needed to be approved. Okay. So in this case, I I was already had approval rights so I didn't have to, go here. But if I would didn't if that person didn't have rights, it would show up here and someone who had access could then see and then do the approval. So hopefully that's a deeper dive into the HTML content block and I hope that, kind of helps, show you all the different power available to this block.