Introducing ArchiveWP ![rw-book-cover](https://img.youtube.com/vi/TorK3VUVF30/maxresdefault.jpg) ## Metadata - Author: [[YouTube]] - Full Title: Introducing ArchiveWP - Category: #articles - Document Tags: [[accessibility]] [[content]] [[wordpress]] - Summary: Introducing ArchiveWP - URL: https://www.youtube.com/watch?v=TorK3VUVF30 All right, we're live. >> Hey. >> Hey. How's it going, William? >> Yeah, going pretty good. >> Awesome. Let's see if uh everything's working as it should. It looks like we're live on X. And let me check YouTube. Yeah, looks like things are working. All right, we had a couple we had a couple weeks there where uh we had some hiccups with with the live stream, but we seem to have ironed out those problems. So, cool. All right, so today's a big day, William. >> It is. Brand new thing. >> Brand new thing. So, we'll give people a little bit of time to join. Um, so we've been cooking up something new, a new plugin, right? We can and uh we've been pushing on it pretty hard for the last month. October was a pretty huge push month for that. And uh so, how you feeling about it? >> Yeah, I'm pretty happy with what we ended up at. was it's quite a lot nicer than the initial expectation that I had. I thought it would be a quick a quick build then we'd move on but that did not end up being the case. >> Yeah, I think so. I think from a product creation kind of uh you know uh evaluation of what we went through it definitely at first you know you come up with an idea and and you think it's simple and and the reality of making something that is that goes to market that could be used by anybody is is quite different. >> Yes. >> So >> simple is not easy. Simple is not easy. Let's Simple is not Let's break that down. Simp. That sounds like a shirt. Simple is not easy. >> I'm pretty sure I saw in a shirt somewhere. >> Yeah, that's pretty good. I like that. Cool. Um, so I'm just making sure everything's working. Giving people a little bit of time to join. And it looks like we have some some of our own people here from our own team, which is good. So they can watch us and make sure we say the right things or not. >> Okay, when we accidentally leak license keys, >> we leak license keys. Yeah. I mean, that's all the rage these days with AI, right? >> Yeah. I feel left out. I haven't once got a notification that I've leaked an API key. fat. >> That's right. Yeah, it's fun fun times. So, well, we we we uh kind of came up with this idea for a new product. It was uh it was from uh you know, a client need, right? And a lot of times that's kind of how these products are born, right? That's how accessibility checker was born was uh from client needs and from our own uh need to understand accessibility and how it works and to have tools within WordPress to help us audit websites and see what the accessibility is and and this this new plugin that we're going to unveil here in a few minutes is is kind of the same. It was something we built for a client. Uh >> oh, >> we lost connection. >> Oh, you're back. >> I'm back. Oh, look at that. Reream leaked my unveil. I dropped. That was weird. >> You're gone for just a second. >> Okay, I'm back. But we're good. We're stable. Steve's not going to disappear again. William's going to have to do the whole thing if it if I do. >> Cool. You better send me that demo link. >> I've got one. >> Yeah. Yeah. Cool. All right. Let's see. Well, we should we get started? >> Yeah. >> All right. Let me make sure. Cool. I'm stable. Good. Yeah, that's really weird. All right, cool. Well, let's do it. So, uh this is the this is the accessibility checker uh change log live stream. Um but today we're not talking about accessibility checker at all. We're talking about a whole new plugin. Um so I just want to welcome everybody here and oh we got a thumbs up uh from Amber Hines that the connection is good. So thanks for that Amber. Um so today we are talking about a brand new plugin and this plugin is called archive WP. So archive WP is a plugin that helps you organize and manage legacy content. uh that helps you keep legacy content online for reference or recordkeeping in a clearly designed searchable archive. So what exactly does it do? So uh it it allows you to quickly build and build a searchable archive. It makes a a dynamically searchable archive page. It comes with three blocks and three short codes. And it comes with two block patterns to help you make the the layout. And it it comes with an archive page generator. So, we didn't think it was enough to just create a few blocks and say, "Here you go, assemble these how you want." But we also created a tool to help you generate that page. And also comes with a short code generator page. So even if you're even if you're using classic editor, you can uh generate an archive uh content page uh with one one click of a button. So it also has a migration feature so you can ar archive posts in a few clicks. Uh there is termle migration controls. So if you don't want to migrate all of your terms over to the archive content, you can choose which ones you do want to move. or if you or if you don't want to migrate any of them at all. Uh we we automatically implement 301 redirects so you can maintain your SEO on your archived content so there's no change to the search engines. And if you make a mistake or if you would like to u refresh some archived content and make it uh you know new content again you there is a restore feature that you can use to send that post back to its original custom post type and restore its taxonomies taxonomy terms. And it also adds an archive disclaimer in uh several places such as on the archive and on the single to help uh delineate this as archived content. So this sounds kind of simple on the face of it but but why would we why did we create this and why do we have a need for this? Well, through our own audits and remediations, uh there are exceptions uh for certain kinds of content uh to where you can categorize it as archived content and then it's no long then you no longer have to u remediate all of that the accessibility of that archived content. so long as it meets the criteria of whatever accessibility um laws or specs that you're you're following. Uh it saves time and money on audits and remediation. So like if you have tons of historic public information that needs to stay public, but you can't necessarily afford nor have the time to um remediate the accessibility of all that. you can categorize it as archived content. Cool. So, that's kind of the rundown, but let's uh let's dive into it and take a look at it and see what exactly it does. Because on the surface, like I said, it's kind of a simple idea, but the plug-in itself goes very indepth in helping you uh create these pages and giving you the design, layout, and controls to make this look however you see fit. All right. So, you ready to jump into a demo, William? >> Yep. Let's take a quick look, see what we can do. >> Cool. So, I will drive and you feel free to jump in whenever whenever you want. Um, so let's let's take a look at the front end first. So, I've rolled up a InstaWP uh install of it. So, I'll go to pages. So, this already has the plug-in installed and set up. So, I'll go to the archived content page. All right, cool. So, this is the archived content. Um, this consists of three block editor blocks. The disclaimer block, which you can see here, which has a default disclaimer message that is displayed, but you can modify that. You have the filters over on the left and we have the loop over on the right. So this is dynamic content. So if I were to search by these are migrated terms from from when it was migrated, it pulls them over into this this archived content custom taxonomy. So I can just you know I can search by that and you can see that the com the content dynamically loads and with the changes I can clear these filters. So this is a typical dynamic uh u filter here and it is accessible. We do announce to screen readers the the changes. You can actually visually see the what is going to be read read out to screen readers when these dynamic changes are made. You can filter by the original custom post type. So if I only want to see posts that were migrated over from uh the post post type, I can filter by those. Um or like a notice, I can filter that. And uh the loop has a brings along pageionation. And as you can see, it's it's created in an effort to make these blocks adhere the theme as as closely as possible as we can without us making many opinionated design decisions around that. We wanted to inherit the the theme that's being used. Uh >> yeah. Do you want to talk a bit about the pain of how different themes style different form elements? Quite sometimes I would say quite ad hoc. >> Yeah. Yeah. I I mean I don't really want to talk about that but I can. So, so in creating these blocks, you know, we could have been very opinionated on the the way this layout and design looked and um in some instance we kind of wanted to, but actually what we did was we backtracked quite a bit. So, this was actually implemented uh the first iteration of this plugin was implemented on a client website where a lot of the styles and stuff were kind of just manually uh written to match the theme. But in this case, we want want it to inherit. We want the submit button. We want it to inherit your button styles. And the clear filters button, which is actually uh uh which actually should be a button for, you know, accessibility. This is dynamic content. This should be a button. It's not a link. But I want it to look like a link, but I can't style it like a link because I would have to make an assumption of what your your your links look like. So in that instance, I actually do want to make it a link. I want to give it a roll of button so that from an accessibility standpoint, it's se access accessible, but from a design standpoint, it adheres your theme. Um there's a lot of font issues that can arise when you're when you're dealing with u with trying to adhere styles from an existing theme such as you know do they use rims or m appropriately. Um, uh, we did a lot of testing on 2020 themes and you get back to which one was it, William? 20. >> The actual 2020 has the the awkward RAM count. >> Yeah. So, I think the the base font size is 10. Is that correct? >> Yep. >> Yeah. Yeah. So, it's the base size is 10. So, if I do a rim of like 875, right? thinking in my head thinking that's going to come down from like 18 or 16, right? Like but in that theme it's actually 10. So like my my styles could end up a lot smaller than the rest of the styles on the page. So you could you could use an M in that instance to try to adhere where where it exists rather than the global uh default font size. So, we had to kind of massage that a bit and make some decisions on how how best to do that. I know um looking at the page here like the the published and the archive dates would end up really small on the 2020 theme. So, so I mean I could talk about that all day, William. And um because it was it was quite the undertaking. So, I didn't have to fix this because we chose not to do it. But in some of the themes that I was testing, they had some very opinionated choices on what those check boxes should look like. Specifically, a lot of people trying to enlarge them a lot, >> which you know is >> maybe good for their design choices, but >> did not fit here for us. >> Yeah, totally. So this is just our demo site there. You know, it's worth noting that there are some accessibility issues on this s this site by default because it's to demo um the uh archive WP and the accessibility checker. So that's just worth noting. So what you see here on on our loop um we are actually outputting u the publish date and the archive date to signify when this post was originally published and to signify when it was migrated over to be archived content. And that's just to help you know with compliance of of for content that can be excluded from uh remediation. And we do have our disclaimer at the top uh stating that this is archived content. Uh did I miss anything, William? >> Nope. I think that that covers the the general loop how the fers work. You didn't show off that you can search. >> Yeah. Yeah. Let's do a keyword like >> like if I just want to look up July, I'll type July in the keyword search and hit submit. And so now you can see I have all all posts uh that are tagged with July as a keyword search. So so your typical basic filters um and I it's worth noting that you can define how many uh terms are shown and then you can toggle those uh you can show more or show less to kind of keep this clean. Um there is there when archiving content from you know multiple custom post types the the archived content uh category taxonomy can can get quite large if you're just migrating in tons of terms. >> Yes. So on one of my test sites I had over 200 200 terms migrated over. >> So when you hit show more it just drops all the way to the bottom of the page. But at the time we didn't have that show more link and the entire length of the page was dictated by the number of categories, not the number of posts. >> Yeah. Yeah. So if you've ever used something like FacetW, this stuff will be very familiar to you. So let's jump over and look at a single page. So this is a single page. And what we've done is we've we've we're hooking in and we're adding the disclaimer to the the single page too uh because that's a requirement uh when you're making uh exclusionary content in an archive u for accessibility reasons. Um but other than that we don't do too much for the single. Um there are there there is a template correct William a block template is that for the single am I missing >> so there is a block template for archives um so if you were to reach so I don't think this theme shows it but if you were to reach some of the categories for the archive content this message would appear on those categories as well. Yeah. On the taxonomy term pages. Yeah. Yeah. So, >> so what we're doing is we're trying to flag anytime that there is archived uh content and show this disclaimer. And the only difference on the the the single or the term pages is that we actually do flag the date uh that that post was archived. Um cool. So, that's a little bit of the front end. Uh let's take a look at the back end. So let's run through settings. So in the back end you you'll notice that uh there's this archive content uh custom post type and then if you go to settings archive WP is listed under settings. Uh William William you want to run through through some of these settings? >> Yeah. So, let me just pull them up on my side because your screen is too small on that. >> Sure, no problem. >> I mean, the first one here is pretty clear. This is all of the custom post types that are available on this website. Um, and or or rather this is all of the public custom post types that someone could could pick from. And as you can see in you know this test site we have four out of the 10 in total which are on this website. Um so we have posts pages documents and notices as custom post types set up for archiving. Um the next setting down is the the taxonomy settings. So we by default will copy taxonomy terms to archive content when you archive that content. Um however that might not be something that you want and if you do not want it you can just come here disable that none of your custom categories custom taxonomy terms of any kinds will be migrated. Um next set down for the archive category visibility. So, if you do not want to allow the category terms to be found on like in the search or on your website in general, you can actually turn those terms off that, you know, prevent them from being indexed, prevent people from accessing them. Um, as far as the the archive post template goes, so this was a rather complex piece of this plug-in. So we by default will use your single.php template and in the you know comes from your theme we will display it the same way we the other you know posts will by default. Um, however, you might want it to look how it looked originally. And if that's the case, you can toggle this to use the original post template, and it will do its best to try and find the original post template for the original post type that the content was, which will, you know, hopefully in most situations make it look exactly how it looked originally. Um, in the the demo site we have here today, single post look the same across almost all of the custom post types, but that isn't the case on most people's websites. Some people have a custom post type because they want it specifically to look different. >> And if that's the case, you can change this here. >> Yeah. And a big a big piece of this is like say you're migrating from a certain custom post type that has custom fields. Um, yes. And and your custom fields, you know, out output custom content on the front end. >> And if if it then starts to pull from your single from your single post template that doesn't have uh, you know, it's not hooked into and those custom fields output are not on that single, they won't see that. Now, the met the meta still exists on the post. So uh using the original uh post template for that post uh will help uh pull in those custom fields again so you can retain that that information. >> Yeah. And I will call out that this supports classic theme templates. So if you have a specific, you know, news.php for your single news posts, it will support that just fine. It does also support blockbased custom templates. However, I will also call it the blockbased custom templates in most cases will override PHPback templates. So if you've created a custom template on the content originally in the back end, chances are it will by default use that custom template that is selected on the post type originally. So no need to change that setting here to do that. Yeah. Um, >> next setting down much easier the redirects setting. So you either allow all your posts to be redirected or you do not. You have the option here. So in cases where we archive the content generally the URL is going to change is going to be like namespaced under the archive-content URL on your website. you you know that is an expected part of building a discrete section for all of this content. Um however the original URL we do generally want to redirect so someone visits the original URL we want them to land on the new URL in the archive content section. So that's what this end does here. I will say that this setting is customizable on a per post basis. You don't need to just, you know, all or nothing. You can modify this on each individual post. And the final setting we have here is the disclaimer text. So this is the default disclaimer text has a link to your contact us page. Asks people if they want to, you know, access this content that is archived, they should contact you to to get an accessible version. You can change this. You might want to link to your accessibility policy. You might want to, you know, open up a live chat. You might want to send people to various different places. You can change that default content and that will reflect across all of the single archive content pieces. It will reflect on the the main search page, it will reflect on all of the archives. >> Yeah. >> So, it will you update this default here, it will reflect everywhere. >> Yeah. Cool. And uh looks like we have Jeff joining us and he says uh he says uh sorry I tuned in late. What pro what problem is this plug-in solving? Uh so um the problem is that uh this plugin helps you organize and manage legacy content. So in a nutshell uh uh certain accessibility uh laws or requirements help you to uh allow you to choose content to exclude from accessibility uh remediation and and uh Amber has posted a very good explanation as well. So thanks for joining us, Jeff. So that is the the settings and uh we do have a first time configurator in here. Um so it's like an onboarding wizard. We'll touch on that here in in a little bit probably um towards the end. And there are some s uh system settings here to just delete data when the plugin is deleted. uh your license key can be added here and then just some support uh documentation links. So in line with uh in line with some settings there are some settings at the term level. So we've talked about u being able to migrate over terms when you're archiving content. Um you can actually you know choose to do that uh at the taxonomy level which is which is I mean a global for all taxonomies or you can do it at the u the term level as well. So if I go to post categories you see that there is a toggle a custom uh admin column here for archive migration uh with a toggle. So you can go in here and you can toggle on or off which terms you want to be migrated. So if you've toggled all these off, none of these terms will migrate when moving over to the archived content custom post type. Um, and you can do that for tags as well. So you can see we don't have any tags selected to be moved over in these settings. Um, cool. So, let's take a look at how this actually works. How do you how do you archive content? So, uh, if I go to post and open up a post, you notice you'll notice now that you have a new sidebar and we've integrated with the block editor sidebars rather than doing like a classic metab box, but um, this actually works in the classic editor as well. There's a fallback to the classic uh, metab box. So, you can still get these settings and uh, these can be unpinned. These sidebars can be unpinned. Uh, so sometimes it can get kind of lost if it's been unpinned and you have to go to the little uh uh three dots menu and then go down and and repin it or reopen it. Um, but we've also added this little helper uh sidebar area uh where you can, you know, with one click jump over and and toggle open the sidebar. So on a post that has not been archived, we give a little description. Uh the details are uh uh move this post to legacy content archive. Archived content is kept for reference only. It is not updated and may be excluded from accessibility scans and reports. So we we put out a little warning here too about what's going to happen when you migrate this. So currently taxonomy terms will be copied to the archive categories when this post is archived. You can disable term migration globally in the archive WP settings which William just went over. And what I just went over is is the next part to exclude specific terms from migration. Edit them in the categories tags. And this will show all taxonomies um related to this post format screens and uncheck include and archive migration. So we're trying to help you with every step of these migrations. Um giving you context of what's going to happen so you don't archive and then are surprised. Wait, why did it do that? Or it didn't pull over my terms. Why didn't it pull over my terms? And and now I have to restore it and then do it again. Um, so if this is what you want, this sounds good, you can go ahead and archive the post. So there's a button that says archive post. If I click that, I'm now presented with an alert that says, are you sure you want to archive this post? So since archiving is kind of uh can can be a little bit a little bit scary that you're moving you're doing something to your post like what what is it actually doing? and and maybe here in a second William can kind of touch base on what it actually is doing behind the scenes, but um we want to give you a confirmation. We want to give you an out if you accidentally click that button. So, I actually do want to archive this. So, I'll hit okay. So, it says post archive successfully. And then it refreshes. And now you'll notice we're if you look at the sidebar, we're no longer in post. We're in archive content. So that post has been moved over to the archived content post and you can see that the the categories that were selected have now been moved over to the archive categories and selected. Uh William, do you want to kind of touch on what is actually kind of happening behind the scenes when you migrate? >> Yeah. So when you click that migrate button in the background, what it is doing is first off it is it's collecting all of the terms that are currently assigned to the post. It's also gathering some other data like the current post type, um, publish date, just gen some generic information about this post. Once it has collected all the information, it saves the majority of that information inside post meta. It then proceeds to disconnect the old taxonomies and does uh a post type flip. It changes the post type over. And finally, it clears the old accessibility checker issues out of the page, which would no longer be applicable because the content of the page template has likely changed. And that won't be the case all the time, but it it's quite likely the case in most of the tests that I've done. However, once this page actually refreshes, the scan will run. it will kick off immediately and it will produce fresh accessibility checker issues. >> Yeah. And I will I I will put a caveat in there that that's if you have accessibility checker turned on on archived content. I think our recommend I I think our recommendation is that you you don't have accessibility checker enabled for archive content because the whole purpose around moving this is is because it's content that can be excluded from accessibility audits. >> That's fair. And that is not how I have my local site set up, but that is likely how most people will have their sites configured. Um, I will call out that if you have a term disabled, that term does still get saved in the metadata of the post. However, it is not assigned in the the categories you see here in the sidebar. Um, so I guess that, you know, maybe I'm jumping ahead, but that is for >> restoration. Yeah, let's let's pull up. So when when you are on the archived content custom post type after it's been migrated, you have the the archive WP sidebar here as well. We do show you a little shortcut as well here, but the information presented is is a little different. Um so like William said, we we are flipping the post type that this post is is attached to. we are dropping the taxonomy terms and from a technical standpoint we had a lot of internal back and forth on whether or not it was a good idea to actually remove those or to leave them dangling. And uh this is a this was a really nerdy software engineering kind of conversation we had on, you know, is it ethical to leave them dangling? It it should we clean them up? Should we remove them? We actually sided on not leaving them dangling and and actually storing an array of all the the original terms that were on that custom post type. So if you restore it that all those terms actually get restored, not just the ones that were migrate, not just the ones that were selected to be migrated. So in the on the archive content in the sidebar here we have a little bit more information. So we have archive details. So we have an archive date. We timestamp the moment that it's archived. We have the original post type which in this case is post. And we have the original taxonomies which in this case it was just one uh it was a category taxonomy and the term was press release. And then we also have the original URL. And this just is to kind of help you keep track of where it originally was to maybe test if a redirect is actually working like it should. And um and then you see we have some redirect settings. William, do you want to explain how we're handling redirects with archived content? >> Yeah. So the default option for redirects is that we will enable redirects. The redirects will automatically apply as soon as you archive a content. um you can disable them at the global level. However, if you have a individual page that you just no longer want to redirect, you can disable it at the post level. So, you can toggle that that checkbox right there. You can disable redirects for this individual post only. This does not affect the global setting. This takes precedence over the global setting. So, you can do this both ways. If you have redirects disabled globally, you can enable it for a single post and if you have them enabled globally, you can disable it. >> Yep. And and I think that is it is smart like it does know what your setting is and it will present a different message. Let me >> Yes. >> Jump back over to settings and I'm going to disable archive redirects in the settings. Hit save changes and then I'm going to jump back over to my post and archive post and look at the sidebar. So in the redirect settings now there's a there's a notice that says redirects are disabled. So they're dis redirects are disabled globally um and with a little bit of link to over to the settings to enable those if you would like. I'll jump back to the settings and reenable redirects and refresh the page. And you can see in the archive sidebar that I I have the toggle again to disable redirect. So if a so if a redirect's enabled like it is now, William, if I click on the original URL, this will redirect. Correct. >> Correct. Should >> Okay. So I actually clicked on a link to the original post which act has a different perma link than than the archive post and you can see that it it redirected to archived content slash the post name now. So the redirect is working properly. Now, what may be a little fuzzy or a little confusing when dealing with redirects if you actually disable them is is you might still see a redirect. Uh because WordPress out of the box does try to match. Is correct? >> It does. And the first thing it tries to match against is the slug, which in the case of migrating the post, the slug has not changed. And as such, WordPress itself will try and find the correct place to send users rather than present them with a 404. Um, however, the redirect code is different. It will probably do a 302 if it's a 404 find, whereas we are doing a 301 specifically. >> Yeah. Uh so Jeff said uh are there any SEO things people need to consider before archiving content? Um >> so yes and in fact that is exactly where this redirect idea comes from in talking to the SEO people i.e. Gemini Google Google's AI they suggested providing these links when I was discussing it with them um because you know to preserve SEO. So we don't want to break these links. We actually do want the original links to still reach the same content. Um hopefully retaining all of its existing link juice for SEO reasons. Um however, if people do choose to disable these redirects, there is some implications of lost content that an SEO might want to consider. So I would suggest that we don't left on. However, someone more well-versed in SEO might disagree and they, you know, they have the option to pick and choose as they see best for each piece of content. Yeah. And I mean this is still opposed and while we recommend that you don't uh modify this content after archiving it and we we do have a feature that we we will probably int implement after uh the initial uh version one release that will block publishing or at the very least it will warn that publishing archive content. uh uh may may not make it considered archived content. It may it's not a violation, but it's like, you know, if this is archive, if this is truly archived content and you're you're putting it here, so you don't have to make it accessible, then modifying it kind of nullifies that it's archived content. Um but I mean to to the the redirect piece, right? So, this is a post and that is editable and you can modify this slug and we actually want to retain the the redirect even if you do modify the archive content slug. Um, William, since this can be done with like a plug-in like redirection, why did we build it into the plugin? >> I mean, this can be done with a plug-in like redirection. However, redirection is not going to natively know that you have changed this content and the URL has changed because this as far as a plugin like redirection or you know the redirects that exist maybe in Yost SEO plugin, it isn't going to think this has changed because the slug has not changed which is generally how these these other plugins detect whether content has been you know need to redirect. Um, however, also, you know, we you we don't want you to have to have another plugin to manage that, >> right? >> Like we can do that. We have all the data here. We know the operation when it happens. We can set up this redirect. And also, if you restore this post, we can remove that redirect that like there's no way a redirect plugin is going to be able to understand. >> Yeah. Yeah. both both operations. >> Yeah, totally. And so what we've tried to adopt with this plugin is that we want you to be able to achieve these things with just clicks or we want it to just do it automatically. So with redirection, you have to, you know, you have to import these all. You probably have to export the URLs and get the new ones, match them up, import it with a spreadsheet, and you know, do it all manually. And if one changes, you have to manually go back over there and and reconcile the change where here it's just kind of doing it in real time. Um I do want to get to the blocks because that's the fun stuff. But um uh >> I mean I mean it'll be fun for users, but I will say that it was not super fun for us to build. >> So I do think this comment that Amber uh put in the chat is worth reading. Uh this is this is a uh probably a more layman way of of saying what the plugin does, but uh mostly I I think of this plugin as a dumping ground of all all the content you think your client should just delete, but they are afraid to delete. Um it's a good way to put it. >> Yeah, I I do think there's legitimate reasons on a lot of websites that they want to keep their legacy content. You know, there might be like one one site I was considering when we were building this was like, you know, my local council's website, and they're going to want to keep records of prior years regulations forever. >> Yeah. >> You know, they're they're going to always want to keep them, but they're not going to want to update them. And in fact, they're explicitly going to not ever update them because they're last year's regulations. And I think this is going to be a perfect solution for that kind of content. You know, content that updates every year or maybe laws that have changes, you know, you're going to want to retain the original as is. Well, you provide the new updated version. >> Yeah, totally. I mean like you know you know city council meeting minutes things like that things that they are required to publish and and keep out there and and it could go back sever several years and could be quite the uh uh accessibility remediation nightmare to to go through all that content. So, we've we've showed how to uh well, actually, before I do this, let me let me not get ahead of myself. Uh on an archive post. So, I've archived this uh by mistake. I don't really want this to be archived content. I've made a big mistake now. Now, how do I get it? Is there a way to like revert and get it back? >> Yep. So, basically the same process but in opposite. You find the sidebar, you find the button. >> So when I hit restore post, I do get another alert saying, are you sure you want to do this? Just to make sure. And you hit okay. And then you can see the post flips back to the post uh post type and it restores the categories. Even even if I didn't migrate the categories, it will attempt to restore them. The only the only instance where it won't successfully restore it is one is if the taxonomy is gone or um but if the term is gone, it'll it'll restore the term. Correct, William? >> It it will. If the term has been removed, it will recreate this term. Um the yeah, the only situation where it can is if the tags on literally no longer exists. Um you might be able to show some restored tags though cuz all of our tags were disabled. >> This post might not have tags. if this post has tags. >> No, it doesn't. No. So, but so it will restore those back to the original um terms that they were. So, your post is back where it was and essentially we're not really changing much of anything when we migrate except for the custom post type and then dumping of the taxonomy terms. Um we could have >> so everything is entirely reversible which is the nice thing. We store all the data required to just completely revert the change. >> Right. Right. Cool. So that's how you migrate and that's how you restore a single post. But man, I have lots of posts to to migrate. Can I do this in bulk? And the answer is yes. So we've uh into the bulk editor. So if you're on post on the post edit page where you can see all your post in the admin you can select which ones you would like to archive you can uh select bulk actions and you can choose archive and then you can hit apply and then six posts have been success successfully archived and those have all moved over to the archived content now and you can do the same when you're selecting terms as well. I don't know if I went over this. When you're choosing which terms to migrate, you can use the bulk action features there as well. Like if I wanted to, you know, turn all these uh on, I could go up here and I can hit include in and archive migration or exclude an archive migration. So, if I hit um include and then hit apply, the page will refresh and you can see they're all included. Now, there is one little caveat with this that really drives me nuts, and it's it's the uncatategorized U default term. Uh, you cannot apply bulk actions to. And this is a WordPress core thing, and there is nothing we can we can do about that. We probably could hook in and automatically flip it, but we kind of stuck with the way the UI works inside of WordPress, not to do something kind of out of the box. But if I go back and I hit exclude, I selected all of them and you can see they're they're all excluded. So, just another way that the archive WP plugin is is trying to come alongside and help you do this archiving uh with just a one or two clicks of a button. So that's how you that's how you archive. That's how you migrate. That's how you choose your your terms. But let's get to the fun stuff. Blocks and short codes. So we did make this uh backwards compatible for uh um people not using the block editor. So, I'm going to go to pages. And then if I go to the archive content page, which this is the page we've chosen uh for this theme to be our archived content page, um we don't actually use an archive so that we can uh fully utilize the block editor. So, William, you want to walk through some of these blocks? >> Yep. So, on this page, we have three blocks. All three of the blocks that we offer. Um I will say that this is a pattern that we offer out of the box. So if you wanted you know no sidebar we do offer a pattern for that as well. So we provide two patterns. Both patterns that we provide include all three of these blocks. >> Yeah. So, what I've pulled up uh I've pulled up the uh patterns uh sidebar and I've searched for archive WP and you can see we have an archive WP sidebar left and an archive WP single column. And while I have this open, you can actually see below you can see the blocks, but I'll go to the I'll go to the blocks tab and and do the search as well. But you can see that we have the three archive WP blocks available here as well. So >> cool. So the disclaimer block, William, this was kind of one you worked on quite a bit. You want to explain how this >> was the easiest of all of them. This is literally just a text field and we have one setting which is to use the default message which is what is set in the global sends. However, it's possible that you want this message here to differ to the message that appears on the single posts. In which case, you can toggle that off on the sidebar. And now, this field becomes entirely editable. You can edit any of this content, provide your content entirely. So, the placeholder content is the default. And if you were to save this post right now, that would be the content that still gets output. Um, however, if you, you know, want custom message, this is how you do that. >> Cool. And this pulls this pulls from the settings, the default message from the settings. >> So, if you change the message in the global settings, that message will change here with exception to the fact if you toggle off that saying in the sidebar for the default message and customize it. If you customize the message, your customized message will always be what gets used here, >> right? Cool. All right. So, we made a design choice on this block, which I originally, like I said, we're trying to not be opinionated about design. Um, but we thought the disclaimer needed to be kind of wrapped in something because it kind of gets lost in the other content if it's not. Um, but I wanted to implement this in a way that didn't like uh that was still unopinionated in some fashion. And uh what we've done is the disclaimer blocks all have a class called archivewp disclaimer on them. And the class is actually what holds the styles. They're not they're not like if I go to the styles tab of the archive wp disclaimer block, you can choose a text color. You can choose a background color like you would on any block. Um, but I didn't want to set that by default because again I'm trying to be unopinionated. Um, so what we did is we actually implemented a class. So when the block is added, a class is also added to it. And if you don't want those default styles on here, you could grab that class and restyle it or you could remove it. And then you have just a blank you have a blank uh block that you can go in and and you know well that let's do something that contrasts. You can change the colors of and you can um Yeah, we don't have padding on this. We should add padding. >> We should. >> Yeah, we're at a ticket. >> We're at a ticket for that. This the plugin isn't released yet. So, um, but you can still use these default styles or clear them out. Um, cool. So, the next block is the filters block. Uh, so this block is for the filters. And the reason why the filters and the loop block are two separate blocks is because again, we want you to be able to take these blocks and lay them out however you see fit. You can use a a group block and create their columns to whatever width that you desire. And you can add these blocks separately. And um but but they are meant to be used together. So in most cases, you want to use them u together unless you don't want any filters at all on your archive. Um so let's look at some of the settings on the the filter block. We're running a beta version of the plugin. Um, so there is a couple tweaks that we are making still before we go live. Um, so we have filter options. So I can choose not to show the the search field and you can see the search field disappears when I toggle that off. And I can choose not to show the the category filters. And then we have implemented a a third one to uh not show the content type filters. Uh so that will be in the initial release. So you can fully customize what what gets shown here. Like say you don't want the filters and you just want the search box, you you can have just that. And then we have a collapse on mobile which uh will take the filters and collapse them with just like a like a hamburger like a a menu to o open them and they will expand on mobile so that you don't have these huge long filter list output before you're uh like if you're William and you have you know 200 >> hundreds >> hundreds of terms you can have that collapsed by default on mobile. Um and then you can set the visibility uh limit as well. So the visibility limit can be set to six. So like we showed on the front end where the show more and the the show less will it will collapse uh based on that number. Um and then um I think that's the filter settings. So let's take a look at the loop. So, the loop has a lot of lot of settings here because like I said, we want you to have full control over the layout and design here. We don't want to lock you into a design that doesn't match your website. So, you can choose how many posts per page. Um, so if I just want one post per page, you can see now I only have one post. If I want two, I can go up to two post per page. Um, let's say I want 10. And then you can choose to show the pageionation or not show the pageionation. Uh because there may be, you know, this may be an archive that doesn't have a ton in it. Say maybe it's 50 posts and you you want to have 50 posts per page and so you don't really need the pageionation. You can toggle the pageionation off and it disappears. And then you have like your content settings. So within the loop on each individual article, you can uh choose to show or hide the featured image and it just collapses down. Um you can choose to show or hide the excerpt. Um you can uh if the e excerpt is on, you can choose how many words it outputs. So like say I only want 10 words. So it collapses down to 10 words. Um I want to read more button. So you can toggle on a read more button and and uh so people can click on that to read more. Um and then there's some metadata settings. So we could if we want to show categories. So these are the archived content categories. So we can we can hide those if we don't want to show those. We can show the publish date or not show the publish date. And we can show or hide the archive date as well. So if you if you only want to show the archive date, you can just show the archive date. And I do believe that the meta output for these is filterable. If you're a developer and you do want to go a little further, maybe you want to remove archived off of here. That is filterable. We haven't surfaced um all those settings into the block because we're you know we're trying to make this as streamlined as possible right now. But those are um well while you mention that I do want to call out that we provide short codes for all of these items and if someone want some of the short codes have attributes that might not be exposed here in the sidebar. So if someone wants to customize the display of this and they're not a developer, they may be able to customize it via the short code as opposed to writing custom code. >> Yeah. So the short code actually will accept all parameters, not just parameters that we've surfaced in the blocks. And we do have this all documented out in our our documentation. Cool. So that's the blocks. Um that's the the patterns and um let's see what else. Um so the first time configuration I think that's something we should probably go through before we wrap this up. William? >> Yes. >> What I'm going to do though is I'm going to pull up my local and and show that. Um Okay, cool. So, when you first install ArchiveW, you're going to get redirected to the the onboarding wizard, the first time configuration. The first step is going going to be to activate your license key. And um in this instance, we've already done that. Um and then the next step would be to choose your page. Uh now the plug-in doesn't use this setting uh to to really make any other logical choices but this is just for the configurator to know which page to implement uh the the page on. So uh I want to choose an existing page. Um so you by default you can create an archive content page and it'll actually just create a page called archive content. But I'm gonna use an existing page. Actually, I don't think I have one called archive. Let's just use that. So, I'll continue. >> So, the next step uh step three is to select a layout. So, the the I can choose from those patterns. So, these are the patterns that we have for um uh block patterns that we've defined. So we have a left and then we have a single column. So if I I think I already have left on here but so like if I choose single column and this is a new page so I'm I don't have to override the content. So if you're if you've chosen an existing page and it has content on it, this will actually override that content. So we've created a a checkbox for for you to actually check that you do want to override that content. If you don't want to override that content, then you need to either pull the the patterns or the blocks over manually on your page. So, I'm going to choose a single column and I'm going to hit apply selection. >> I'll also call it >> I must already have this page. >> Yeah, you do. So in the previous choice um it will detect whether you have the block editor completely deactivated and if you do have the block editor completely deactivated it will still generate those patterns but it will generate them purely with shortcuts as opposed to blocks >> right and we'll demo that here in a second. So, I do already have this page. I was mistaken and the plug-in actually caught me and said, "Hey, dude. The this page already has content on it. Are you sure you want to override it? If you want to override it, check the override existing content uh checkbox." So, I do have uh content here. So, I'm running just your basic I think I'm on 2025 um 2024. I don't know what theme I'm on, but um you can see I have just a basic theme and it's already been applied and it is the single column. So what I'll do so you can see the change is I'll choose the the sidebar left and then I will override and then okay so block pattern applied to your archive page. So if I go to this page and I refresh look at that I've got a whole new page with one click of a button. Um, it's it's applied uh all those that pattern layout for me. And now I have a fully functional archive page with literally the two clicks of a button. I didn't have to go in and add a group block and throw the uh filters block into one side and throw the loop block into the other side and select all my settings. U no, the the configurator actually just did it all for me. And now I'm up and running. I'm ready to just start archiving content. You can see I already have on this page. Um so as you go through the the the first time configuration we will prompt you to choose the custom post types and um the taxonomies whether or not you want to you know uh preserve taxonomies and whether or not you want to enable uh category archive pages and I'll just hit continue to go to the next step display settings. Um, I can choose whether or not to use the default single uh page template or use the original uh custom post types uh single page and the redirect behavior enable automatic redirects from the original URL to this archive. So I can choose to I do want these to redirect and then the disclaimer. I can set the disclaimer just like William showed and I can hit save and finish. And I come to the final step, step seven here. And I just get a little summary of, you know, a link to my archive page, my layout that I'm using, um, the arch archable custom post types, the taxonomy preservation, the template, uh, preference, and whether redirects are enabled, and a a preview of my disclaimer. So, what we've tried to do is we've tried to just take all this stuff, you you install it, you get redirected here, you click you click through a few steps, and you're ready to archive content, and uh your pages, your archive is set up. It's got a layout, it's it's got design, it's all good to go. What I do want to show though is, you know, what if I don't have the block editor, right? I I still want to use this. How this how does this implement the short codes? Because a short code is just a short code. So, we have three short codes that just match the blocks. They do. They have all the same parameters. Actually, they have a little bit more parameters available to you than the blocks do. But, um well, how do you get a layout from that? Right? Because they're separate. Wouldn't you just need one short code that has a layout all built in? Well, actually, what we do is we just insert the short codes into the page with some custom HTML to go along with it. So, I'm going to go back to choose a page in the first time configurator uh configuration and then I will choose an existing page. I'll choose archive content short codes. So, this is a page that I have the classic editor plugin enabled on, I believe. So, um we will find out. Yeah. So now it says, "Your current theme appears to disable the block editor for pages. Archive WP can output the chosen layout using short codes with inline styles in instead." So the plug-in has detected that the page that I chose is a classic theme page. So now it's going to uh it's going to present me with the short codes. Uh, so if I choose the archive column, archive WP sidebar left layout and I want to override content because I already have this page. Um, and then I'm presented with a couple more settings here. How should the layout be applied? Uh, select whether to insert short codebased markup or attempt to apply a block pattern anyway. Well, we don't want to attempt to apply a block pattern anyway. We want to actually use the short codes. >> Yeah, I I will call out here that if you do attempt to apply the block pattern, so sometimes that will be fine. Actually, if you install the classic editor plugin, you usually can switch freely between them and if sites are configured that way, this is this is the option for them. Right, this is detected. This is a classic page currently, but they might still want to apply the block styles and they they can do that if if someone wants to. I don't think that's a common configuration where people can freely swap between block editor and classic, but the default might be classic. Yep, totally cool. So, let's go ahead and apply short code layout applied to your archive page. So, let me let me find this page. If I go down to summary, I can I can hit view page. So, archive content short codes. So, it's it's applied the short code to the page. Now, I'm I'm running 2025 and um you know, it has a very small >> it has a very small uh content area. So, I could I could use the single column layout to make this look better or I could uh you know change my my template here with a with a wider content area, but this is just the default content area for uh demo purposes. But what does this look like if I edit the page and I so you can see I'm in the classic editor here and I and um and if I go to code you can see this is the code we've implemented the wrapper the all the div wrappers around the short codes that you would need to give this a a left column layout. So you don't have to do anything. It's ready to go. It's got inline styles. Use this flex. It should it should wrap fine. And you're you're ready to go. And uh you can add your attributes to these short codes to modify it how you see fit. >> Well, speaking of being ready to go, what if someone wanted to get this plug-in? >> Where where can they get it and when? >> Yeah. So, when will it be a available? We got a drum roll. We need sound effects, William. This needs to be more dramatic. There you go. So, archive WP will be available for purchase tomorrow. And um so you can check in at equalizedigital.com/archchivewp and you will be able to purchase at that time. We are finishing up the final touches on the plugin and getting everything ready to go. Today that's only half the story though. What kind of plugin is this? Is this can I get this on WordPress.org? Can I do I have to Is it premium? What's the deal? So, it's a little different than accessibility checker where accessibility checker has a very fullfeatured free plugin and and the reason why accessibility checker has that is just because of our whole methodology around accessibility and extending it to to uh uh making accessibility checker accessible to everybody with no um you know no price uh price guards there. But uh the archive WP plugin will be a premium only plugin and the pricing for it. Let me pull down to this unpublished page that Amber Hind has been working so hard on. So, you would be able to buy it uh for one site for $59 a year, five sites for $159 a year, 25 sites for $2.99 a year, and unlimited websites for $3.99 a year. So, um the plug-in is the same throughout those tiers, and you just get more site licenses. Cool. Anything else to add, William, on your side? >> I mean, I will say that if someone wants to buy an unlimited license, please be kind and don't activate 2,000 websites at at the same time. You can activate 2,000 websites, but you know, leave a little gap between >> Yeah. Yeah. Yeah. Yeah. We can we can stage those. Uh, no. Um, so, archive WP um is our new plugin. We're very proud of it. We have been working extremely extremely hard on it. Uh William and me and Amber and the rest of the team have been putting together you know uh sales and marketing and development efforts towards this and we're very excited. The accessibility checker is is five years old and we thought it's time to to bring in a new plugin to that kind of complements accessibility checker and helps u people further make their websites more accessible. So um look for the release tomorrow and um we're glad that you guys joined us today and uh we we were happy to show archive WP to you. We if uh we have these live streams every two weeks uh feel free to join us and feel free to uh follow us on social and find us at accessibility or at equalizedigital.com. Catch you all next time. See you., Introducing ArchiveWP, YouTube, 01ka272ns74dv39ygx6n8jmwg9.