ite broad. You need to be using WordPress in a unique and innovative way, representing a notable organisation, government entity, or corporation as a official blog or website.</p>\n\n\n\n<p>The key piece here before I say the last one is that, you need to be doing one or more of the following. So one or more of these, and or you need to be using modern WordPress. So for example, a small little restaurant might have a really cool, interesting design. They&#8217;re not a notable organisation or corporation, but they&#8217;re using it in a unique and innovative way. Maybe they&#8217;re using a block theme to do so. So you don&#8217;t have to apply it to all of these, but these are kind of the broad criteria around that.</p>\n\n\n\n<p>So when it comes to being things like accessibility, and responsiveness or whatever. These are things where there is no criteria right now around a site passing a certain level of accessibility, or a certain lighthouse score. And it&#8217;s not to say that those criteria couldn&#8217;t exist, but they would need to be decided on collectively as a community. Identified what those are, and then that criteria can be implemented to the sites in the Showcase.</p>\n\n\n\n<p>That process is highly opinionated, not highly opinionated, but it requires a lot of group consensus. And that is partially why the whole submission process and, you know, the content moderation was not part of the redesign. Because that requires an, at least personally, that requires its own consideration, its own thought processes, its own discussion with the community. And hopefully that could happen relatively soon as well.</p>\n\n\n\n<p>[00:15:38] <strong>Nathan Wrigley:</strong> It seems like a not particularly onerous submission process, in that case. So long as you hit two out of the three of the criteria that you mentioned, you&#8217;re eligible. And then we must wait for the community to decide which go in, and add to the pool that we can currently see.</p>\n\n\n\n<p>Doing a quick refresh, there&#8217;s always one website which dominates, if you like, it&#8217;s in the, you know, the hero section. And there&#8217;s one website which get featured. But every time I click refresh, broadly speaking, I get what seems to be something random. Although having refreshed probably 50 times or so now, it would appear that the ones which get into the header, there&#8217;s a few that seem to be earmarked.</p>\n\n\n\n<p>There&#8217;s maybe five or six that I&#8217;ve seen so far. I&#8217;m seeing the New York Times. I&#8217;m seeing Meta. I&#8217;m seeing a variety of others that come up. Is there some other criteria there to get right to the top, if you like, of that page?</p>\n\n\n\n<p>[00:16:26] <strong>Nick Diego:</strong> There is not. Behind the scenes, they&#8217;re basically a sticky post. And so there&#8217;s a server cache that refreshes, I believe it&#8217;s every 120 minutes, or every 60 minutes. And once that refreshes you&#8217;ll see a new page. The sites that were up there were selected as part of just the redesign aesthetic process just to have something there.</p>\n\n\n\n<p>But the mechanism around those six sites can completely change. So if the community decides some brand new site really should be part of that six, then it can be. Should be considered kind of a default just to get the site launched. But I kind of put who those six are, kind of falls into that content moderation bucket, and it really can be anything that the community wants. Obviously that&#8217;s within the Showcase.</p>\n\n\n\n<p>[00:17:09] <strong>Nathan Wrigley:</strong> When you click through to any of the particular websites in question, it looks like one of the submission things is A, give us the name. B, give us some imagery, or presumably you scrape that imagery somehow. But then it&#8217;s categorised by country, by the word category in this case, I&#8217;m looking at one which is categorised as business.</p>\n\n\n\n<p>Then there&#8217;s flavor, which is quite an interesting term. Publish date, and then there&#8217;s a bunch of tags, which obviously refer to the industry that you&#8217;re in. So I&#8217;m looking at art, hospitality and so on. But there&#8217;s probably some more there.</p>\n\n\n\n<p>You get a link, which seems to go directly, I don&#8217;t know what kind of a link that is, but maybe it&#8217;s just a regular old link, going directly to the property itself. And then you get some descriptive text, where you get to establish what this business is, and how the website has been put together.</p>\n\n\n\n<p>But it doesn&#8217;t seem on the whole, this isn&#8217;t really a promotional tool for agency X. This is not a technique for an agency that&#8217;s big in the WordPress space, we know all the names. For them to push something and say, look what we did. There&#8217;s no link to them anywhere as far as I can see.</p>\n\n\n\n<p>[00:18:08] <strong>Nick Diego:</strong> Correct. And this is something that, again, we tried to stay out of because it really falls into kind of content moderation again. But ideally, the Showcase should be a very exciting, place to Showcase your best work.</p>\n\n\n\n<p>So it would be amazing if, you know, some of the largest agencies, even small agencies, submitted their work to the Showcase for review. Because we know that there&#8217;s a hundred sites in this Showcase, right? We know that there&#8217;s millions of sites out there. Probably many that are better than the ones that are in the Showcase, right? And so having folks submit their work will be awesome.</p>\n\n\n\n<p>Now, you&#8217;re right. It is not a tool to show off the agencies or promote the agencies. That being said, when you submit a site, you include a description about the site and how it was built. And it would be kind of nice, you know, in the future of these kind of became little mini case studies. Hey, you know, we built this nasa.gov, and we&#8217;re using Multisite.</p>\n\n\n\n<p>And it&#8217;s fine to highlight the agency dimension who built it, that&#8217;s okay. But it&#8217;s really about showcasing the work, and showcasing what can be built with WordPress. An agency can kind of inadvertently promote their work by being on Showcase, but that&#8217;s not the intended purpose. And I don&#8217;t know if we want to jump right into it, but I do want to share some thoughts around the taxonomies because you mentioned you have category and flavor.</p>\n\n\n\n<p>[00:19:27] <strong>Nathan Wrigley:</strong> Categories and flavors. Flavor, by the way, you have three options that I can see at the moment. You have WordPress, WordPress enterprise, you might want to pick that one apart for the audience, and WordPress Multisite. They&#8217;re the options that you&#8217;ve got. So yeah, throw all the taxonomy stuff at us. That&#8217;s good.</p>\n\n\n\n<p>[00:19:41] <strong>Nick Diego:</strong> So the taxonomy stuff is an area of the site that needs a future iteration. A lot of it was just pulled over from the old site to make sure that, you know, we kind of had feature parity as we moved over.</p>\n\n\n\n<p>Flavor is an interesting one. And I think this is where we can really, maybe flex in the future. You could imagine a flavor being block theme, or hybrid theme. You know, maybe it&#8217;s different flavors of how the sites are built. WordPress is just like the catch all, just like normal WordPress. Presumably everything is WordPress.</p>\n\n\n\n<p>But in enterprise, again, kind of a nebulous thing around sites that, and there&#8217;s only a handful of them that are listed as enterprise, where in doing this and reviewing the sites, we knew that this was a massive site that was enterprise grade, quote unquote, like NASA. With, you know, 60,000 pages. Really massive sites. And then Multisites, obviously for folks that are using Multisite.</p>\n\n\n\n<p>Flavor, the current setup for the, you know, the taxonomy needs some work. We left it because it could be reused in a really interesting way in the future. And if folks have ideas around how this taxonomy can be used and additional terms to add, by all means, let us know.</p>\n\n\n\n<p>Category is, and this goes back to thinking about some of the competitors of WordPress. Where we have Squarespace and Wix and so on. If you go to their Showcases, they have some very simple categories. You know, these are like five or six, that kind of bucket the sites. So it&#8217;s a little bit easier to navigate.</p>\n\n\n\n<p>Right now, the category just looks like a normal taxonomy. But one of the ideas, perhaps in a future iteration is like, when you land on the Showcase, maybe there&#8217;s, visually you have some, you know, nice little buttons or something to say like business and portfolio. To try and help users navigate around the site a little bit better.</p>\n\n\n\n<p>For this iteration of the Showcase, we left it very simple. It&#8217;s just another taxonomy term. But it leaves the door open for a new, updated design in the future that kind of leverages those categories a bit more. Makes the site a little bit more navigable for users, especially who are coming there for the first time.</p>\n\n\n\n<p>And then your site tags are, it&#8217;s supposed to be like a fun expression where, we could have a thousand tags. It&#8217;s just a way to provide additional context about what a site is like. So tags are free form. Ideally we&#8217;ll have hundreds of them, that really help provide a little bit of fun to the sites and explain a little bit more.</p>\n\n\n\n<p>[00:21:57] <strong>Nathan Wrigley:</strong> I think the categories will be really useful for novice people coming to WordPress, because it really does break out what WordPress is capable of, as much as anything else. So currently, at the time that I&#8217;m looking at the screen, the options are business. I would imagine a lot of people would immediately grasp what that is, but community. Oh, okay, WordPress can do that kind of thing. Can it? Okay.</p>\n\n\n\n<p>Creative publication, obviously capturing people who are creating blogs or newspapers or whatever that might mean. But also store, you know, okay WordPress can handle that as well, can it? And whilst it&#8217;s obvious to you and I that those things are well within the purview of what WordPress can do, it may not be to other people.</p>\n\n\n\n<p>So, yeah I think they&#8217;ll be really, really useful. And you can stack them on top of each other. So you can filter two or three things at the same time. And it strikes me that that will be, yeah, incredibly useful.</p>\n\n\n\n<p>Now you threw out there, dare we say it on a WordPress podcast. You threw out there the name Squarespace, I don&#8217;t know if you mentioned Wix. But we know who the commercial competitors are. And you also said, if you look at their Showcases. So I haven&#8217;t looked at their Showcases, but I&#8217;m guessing that there must have been, in order for this redesign to happen, there must have been a moment in time where the WordPress Showcase, perhaps fell behind in terms of the appeal, or the design or what have you.</p>\n\n\n\n<p>Did the WordPress Showcase, in times gone by, a few months ago let&#8217;s say, did it not live up to what it does now?</p>\n\n\n\n<p>[00:23:18] <strong>Nick Diego:</strong> I want to be very clear and not disparage anybody that was involved in the original Showcase. It served its purpose, but it felt as old as it was. You know, I don&#8217;t know when that original site was launched, but it felt many years old, and it was.</p>\n\n\n\n<p>And so when, I mean, WordPress.org is not a commercial entity. But at the same time, we are trying to grow the user base of WordPress. And other proprietary platforms, like Squarespace and Wix are also trying to grow their user base. And part of that is showing off what those platforms can do. And that was, that&#8217;s the point of the Showcase, to kind of show what WordPress can do.</p>\n\n\n\n<p>And I think it was very fair to say that the previous aesthetic of the Showcase did not showcase WordPress in the best light, especially compared to some of these other tools that people can use.</p>\n\n\n\n<p>And what we&#8217;re thinking about here is really not, you know, not an agency that already knows WordPress, not people who already know WordPress. But those folks who are just want a website, just want a presence online. And so if you were to compare the old Showcase, and something like Squarespace and Wix, it was a very stark difference there. And it was very clear which direction a user might go if they knew nothing else other than, this looks pretty, I want this.</p>\n\n\n\n<p>And so yes, there was a lot of consideration around what others were doing when the Showcase was designed. And it&#8217;s not necessarily to compete with these other platforms, but it&#8217;s just to really showcase WordPress in a modern way that allows WordPress to kind of, allows us to be excited about directing people to the Showcase, other than perhaps cringing that it was a little bit out of date, and not reflective of the best that WordPress can be.</p>\n\n\n\n<p>[00:24:51] <strong>Nathan Wrigley:</strong> It strikes me that this has lots of layers of use as well. Because, not only could you go to this website, obviously there&#8217;s a hundred at the moment, but that number is going to be in flux. Let&#8217;s imagine that there&#8217;s more in the future. Not only could you go there and just get bucket loads of inspiration, because really, genuinely there&#8217;s not one that looks anything like the other. They really are truly different in nature. And I guess that&#8217;s part of the Showcase, is to maintain that originality, as you said.</p>\n\n\n\n<p>So you can go there to get inspiration. But also, it was always a part of the arsenal, I thought of a freelancer, and an agency when trying to persuade clients that WordPress was a credible choice. It was always really great to, not only show the designs, but also to name the names.</p>\n\n\n\n<p>So, you know, The White House, NASA, you just list it. Well, these people are using WordPress, and immediately credibility just falls out of your mouth. I just wondered if there was any bit of this which was designed for that? You know, to help the community to be able to sell WordPress to their clients.</p>\n\n\n\n<p>[00:25:54] <strong>Nick Diego:</strong> Absolutely. I think that WordPress has, in some circles, a negative connotation. You know, it&#8217;s just a blogging software. People decry security issues, which we know is not necessarily founded. And, you know, these are things where being able to send some customer or client somewhere and say, hey, do you know Noma? One of the most famous restaurants in the world? They&#8217;re using WordPress.</p>\n\n\n\n<p>Hey, do you know the Ray Charles Museum? You&#8217;ve heard of Ray Charles. They&#8217;re using WordPress, so on and so forth. Rolling Stone is using WordPress. And I really think that that, not that we need to prop up the credibility of WordPress, but I think that having something like this really helps with that. And, you know, establishing that credibility, and also showcasing what WordPress can do.</p>\n\n\n\n<p>[00:26:33] <strong>Nathan Wrigley:</strong> This could be completely wrong. Apologies if this comes out and you think, no, no, no, that really wasn&#8217;t the intention. The ones that I&#8217;m looking at, I&#8217;ve got a screen full of, and it probably is by some sort of random query of the database. I&#8217;ve got a screen full of things where everything is in English.</p>\n\n\n\n<p>I doubt that that&#8217;s the case because now that I&#8217;ve gone onto the second page, I can see there&#8217;s one or two where English as the first language is not there. So is that just a coincidence? It&#8217;s not like there&#8217;s a proclivity here to showcase English things. Any language is possible. It&#8217;s the design that&#8217;s the point, not the language.</p>\n\n\n\n<p>[00:27:05] <strong>Nick Diego:</strong> I think that may have been unfortunate happenstance because there was a really strong effort to make sure that there&#8217;s a diversity of sites across other languages. Actually, we do have one on the homepage, the Denmark Museum of Design. The featured name is Design Museum Denmark, but then all the navigation is in Danish, I believe.</p>\n\n\n\n<p>So that was definitely a huge effort as well. Because WordPress is not just the United States, and the state of the word that&#8217;s coming up is taking place in Madrid to kind of show off all the amazing contributors that we have in Spain. You know, so this is really a global Showcase, and it really should reflect that.</p>\n\n\n\n<p>So perhaps we need to add a few more items to the homepage that are from different areas, but absolutely not. We really want to have a broad spectrum of sites across the world.</p>\n\n\n\n<p>[00:27:51] <strong>Nathan Wrigley:</strong> So, WordPress is doing a really good job here, we can see that. WordPress is also doing a really good job in the amount of materials that are being created in order to learn how to use WordPress. And I know this isn&#8217;t directly within your wheelhouse, but i&#8217;m kind of interested where this would go.</p>\n\n\n\n<p>I wonder if in the future it would be kind of interesting to match up some of these designs with learn material. So, you see them on YouTube all the time. Somebody dissects a site, and then quickly rebuilds it in WordPress, with blocks or whatever it may be. This just seems to be enormously popular.</p>\n\n\n\n<p>You know, people love to consume that kind of content because they learn. They&#8217;ve got a template that they can work towards, and they can see how it&#8217;s scaffolded and built on the screen. So I&#8217;m not holding you to anything, but I do wonder if the Showcase might lean in that direction to help people, not just see what&#8217;s beautiful, but also, this is how it was built as well. That would be kind of nice.</p>\n\n\n\n<p>[00:28:42] <strong>Nick Diego:</strong> Absolutely. And I think that there is some work, and I don&#8217;t want to, again, put words in anybody&#8217;s mouth, but there is some work around. So we have an enterprise section. wordpress.org/enterprise. And I know that there&#8217;s some work being done exploring how to create more case studies.</p>\n\n\n\n<p>So if you look at a site, take NASA for example, massive site. And I go, how do you even build that sort of thing? Wouldn&#8217;t it be cool if there was a case study that said, hey, this is what we did. Hey, we had 50 custom blocks, you know, we did this X, Y, and Z. Being able to show what went behind each Showcase entry, in some sort of case study, would be really, really, really cool.</p>\n\n\n\n<p>So I love that idea. And I think that there&#8217;s some exploration around how we can do that. Because it&#8217;s not only enough to show the site that was built, but how it was built. Maybe even in broad terms, would be incredibly helpful for folks to help kind of recreate that sort of thing.</p>\n\n\n\n<p>[00:29:30] <strong>Nathan Wrigley:</strong> Get the excitement going, but also getting people learning how to build it. You may have already answered this question, towards the beginning of the show. I don&#8217;t think you said that all of these, or even many of them, are based upon block themes. Let&#8217;s just firstly clear that up. There&#8217;s no proclivity here of, well, it must be done with, in air quotes, modern WordPress block based themes, no?</p>\n\n\n\n<p>[00:29:51] <strong>Nick Diego:</strong> Nope. There&#8217;s a lot of sites in here that are not. There are some that are, and I think that as we move forward, it would be cool to have maybe a flavor that could clearly call out, okay, this is a full on block theme. Because I think that we do kind of lack some examples of real world examples of block themes.</p>\n\n\n\n<p>But to go to the broader effort, so Showcase is just one piece of this wordpress.org redesign. We want wordpress.org to be fully block based. You know, because it&#8217;s a massive site. There&#8217;s a lot of different pieces of it. There&#8217;s a showcase, there&#8217;s plugins repo and themes repo. Having that all block based really showcases the power of blocks. So we&#8217;re not even close to that yet.</p>\n\n\n\n<p>But the cool thing is, is that the Showcase is entirely block based. So if you want to build a site like the Showcase, you can with blocks.</p>\n\n\n\n<p>[00:30:34] <strong>Nathan Wrigley:</strong> I&#8217;m going to get you to, somewhat unexpectedly, change the hat that you&#8217;re wearing, because I want to just ask you about blocks actually, and block based themes in particular, if that&#8217;s okay? So it wasn&#8217;t exactly why I got you on the call, but I hope I can smuggle the odd question in.</p>\n\n\n\n<p>How is that enterprise going? Because, I&#8217;m specifically talking now about block based themes. We&#8217;ve had these around for a little while now, and it would appear at least on the face of it, that the stats, if you just took the raw stats, the pendulum doesn&#8217;t seem to have swung in the direction of adoption for block based themes, perhaps as much as one would have imagined or hoped, whichever word you prefer there.</p>\n\n\n\n<p>What&#8217;s your opinion of that? Do you think people are just sticking with what they&#8217;re familiar with? They&#8217;re waiting for the right moment. Or do you think this is a permanent thing that WordPress is going to face going into the future? Where we&#8217;ve got this, well, you have to make a decision right at the outset. Are we going to go with a classic theme? Are we going to go with a block theme?</p>\n\n\n\n<p>And that decision will never get resolved. There&#8217;ll always be the option for those two things. Or you have some sort of intuition that, perhaps in the future, block based themes will start to consume that pendulum swing?</p>\n\n\n\n<p>[00:31:39] <strong>Nick Diego:</strong> I think that there will always be a choice between the two. But I think that, actually the development of the Showcase site and the other sites that we&#8217;re doing for wordpress.org, is a very interesting exploration. Because you&#8217;re talking about applying a block theme to a massively trafficed site.</p>\n\n\n\n<p>So one of the other projects that we&#8217;re working on right now is overhauling the developer resources section. So this takes into account the block editor handbook, the themes handbook, a lot of handbooks. You know, it&#8217;s hundreds and hundreds of pages.</p>\n\n\n\n<p>Exploring how to build a block theme that supports that sort of thing, can be challenging. And so, I think that there is a certain level of tension around transitioning from an architecture that you already know, to something like a block theme, where you&#8217;re going to have to implement things in different ways. Learning how to do that at scale can be challenging.</p>\n\n\n\n<p>A good example is that, every page, or almost every page in wordpress.org, actually needs to stay in version control so it can be translated. So when you&#8217;re editing things in the block editor, if you&#8217;re just on your personal site, when you save something to the site editor, that change is saved in the database.</p>\n\n\n\n<p>We can&#8217;t do that in wordpress.org. All those changes need to be synced back to the actual template files that power the theme. This is getting very in the weeds I know, but it&#8217;s just one of these things you have to kind of account for when building a block theme, on a site of this scale.</p>\n\n\n\n<p>Once you figure that out, once you figure out a process for it, it&#8217;s not that big of a deal. It&#8217;s not that bad. But figuring that out can be a little challenging. For anybody that&#8217;s interested in this sort of thing, all the theme files for Showcase and rest of .org. It&#8217;s all open source. It&#8217;s all available to the public in the WordPress repository on GitHub. So if you want to know, how do they do this block that does the big banner image on the homepage? It&#8217;s a custom block, and it&#8217;s available in the GitHub repo for you to check out.</p>\n\n\n\n<p>So I&#8217;m hopeful that as we go through these things and we can actually, you know, show how some of these implementations are done, that might help get others over that hump of transitioning. But there&#8217;s no doubt in my mind that it&#8217;s going to take some time, especially for large sites like this.</p>\n\n\n\n<p>But I know, from somebody who, I didn&#8217;t do the development work, but I did a lot of, you know, editing and, you know, we&#8217;re doing more work now and other sites. Being able to go into a block editor page and scaffold out a design in blocks is so much easier. Like it is so much better.</p>\n\n\n\n<p>And it also requires much less development, because you can scaffold out a page and how you want it to look. You can move blocks around. And once you&#8217;re done, then you can pass it off the development team. They push it into a theme template, and you&#8217;re good to go. So it really cuts down on the development time, once you have the entire architecture set up.</p>\n\n\n\n<p>And it also really empowers, which was kind of the promise of the block editor and site editor, empowers the content creator, or the designer, to build most of it themselves. And we&#8217;re starting to see that with this .org project. We&#8217;re getting to a point where a lot of the ground work is done, a lot of infrastructure is done. And now we can start really moving quickly because it&#8217;s just designing in the editor, which is great.</p>\n\n\n\n<p>[00:34:32] <strong>Nathan Wrigley:</strong> I think by pure coincidence, a bit of serendipity, it&#8217;s the 7th of November, and it&#8217;s a big day for WordPress because 6.4 has landed. I don&#8217;t know if you&#8217;ve got to get off the call go quickly triage things or anything like that.</p>\n\n\n\n<p>It does appear, from my perspective anyway, I keep a pretty close weather eye on what&#8217;s happening in the project. It does seem that version by version, minor release by minor release, the promise of what blocks can do and block themes can do, is becoming more and more compelling. I do understand, you know, if your agency is embedded in a workflow which just is going to be so difficult to untangle, I can understand why that inertia might be there.</p>\n\n\n\n<p>If you had point somebody, Nick, in the direction of a resource, a good website. I mean, we can probably give it, take it as given that you&#8217;d point them in the direction of learn.wordpress.org and various other properties like that. I wondered if you had any good advice as to where to go, to learn about block based themes.</p>\n\n\n\n<p>[00:35:24] <strong>Nick Diego:</strong> Yeah. So, learn.wordpress.org is fantastic. I&#8217;ll also give a little self plug from me and my team. I have a small team with a few others and we&#8217;re on the developer relations team, and if you&#8217;re interested in more developer oriented content, the learn team does a great job with user content and some developer content, but our focus is all developer content.</p>\n\n\n\n<p>And so once a month or once or twice a month, we do a developer hours, which is a live series. And it&#8217;s always a very specific topic. The last one we just did was theme oriented. We had Jessica and Maggie who helped build the new 2024 theme, and they went through how that theme was built. Code examples and, you know, how the whole thing was built.</p>\n\n\n\n<p>And so every month we have these sessions that are very developer oriented, whether it&#8217;s building custom blocks, whether it&#8217;s building block themes. And that&#8217;s where, if you&#8217;re a developer and you really want to learn how to build this stuff, as opposed to using a block theme, that&#8217;s great for learn. I highly recommend that.</p>\n\n\n\n<p>I also want to say again, another shout out. We&#8217;re doing a lot of work to overhaul the block editor handbook document, basically the documentation on how to build blocks, and work with the editor. Justin Tadlock, who used to write for WP Tavern, he&#8217;s been undertaking a massive project to overhaul the themes handbook.</p>\n\n\n\n<p>And so with these two efforts, it&#8217;s going to take into 2024 to kind of complete them. But the idea is that both the block editor handbook and the themes handbook will be much more robust, especially when it comes to building with blocks, whether it&#8217;s a block theme or building custom blocks.</p>\n\n\n\n<p>And we hope that better documentation leads to better projects that people can build. Because right now there&#8217;s some, definitely some holes in both of those pieces of documentation which we hope to fix.</p>\n\n\n\n<p>And we&#8217;re also going to get a brand new design very soon for that developer resources section, which will make navigating the documentation much nicer.</p>\n\n\n\n<p>[00:37:17] <strong>Nathan Wrigley:</strong> And lest anybody forget, this is all free. It&#8217;s entirely free, ready for you to utilize.</p>\n\n\n\n<p>Nick, thank you so much for chatting to us about the Showcase. My hope is that people listening to this will be able to, A, make use of it, you know, perhaps to pitch their own work, but also perhaps submit their own site so that the number there 100, will continue to rise and we can all benefit from the wonderful things that have been produced.</p>\n\n\n\n<p>Where might people find you if they want to communicate with you directly?</p>\n\n\n\n<p>[00:37:46] <strong>Nick Diego:</strong> Absolutely. So anybody is welcome to reach out in the WordPress Slack channel, @ndiego, and also on Twitter, X, whatever we&#8217;re calling days @nickmdiego. But happy to answer any questions about block development, block theme development.</p>\n\n\n\n<p>[00:38:00] <strong>Nathan Wrigley:</strong> Nick Diego, thank you so much for chatting to me about the Showcase. I really appreciate it.</p>\n\n\n\n<p>[00:38:05] <strong>Nick Diego:</strong> Thank you so much for having me back.</p>\n</div>\n\n\n\n<p>On the podcast today we have <a href=\"https://twitter.com/nickmdiego\">Nick Diego</a>.</p>\n\n\n\n<p>Nick is a sponsored full-time contributor at Automattic. His official position is a developer relations advocate, which allows him to focus on creating developer orientated content. Apart from his regular responsibilities, Nick is also involved in a separate project called the <a href=\"https://wordpress.org/showcase/\">WordPress Showcase</a>, and this is the focus of the podcast today.</p>\n\n\n\n<p>The WordPress showcase is a curated collection of websites built with WordPress. Its purpose is to inspire, and show the breadth of what WordPress can achieve. Currently the showcase features around a hundred sites, including large enterprises like the New York Times and NASA. It aims to challenge misconceptions about WordPress, and highlight the platforms scale and reach.</p>\n\n\n\n<p>The design of the showcase is contemporary and visually impactful. It shows that whatever proprietary platforms can do, WordPress can also do.</p>\n\n\n\n<p>During the podcast we talk about the intricacies of the Showcase project. We discuss the selection criteria for featured sites, including the possibility of case studies to show the process behind their creation.</p>\n\n\n\n<p>We also explore the importance of block themes within the Showcase, and the ongoing efforts to make wordpress.org fully block-based.</p>\n\n\n\n<p>We also get into the future iterations of taxonomies and navigation on the site to enhance its functionality. Nick suggests that the categories in the showcase will serve as a valuable resource for novice users, trying to understand the capabilities of WordPress.</p>\n\n\n\n<p>The redesigned showcase aims to highlight WordPress in a modern way, inspire web design, and convince clients that WordPress is a credible choice. Everything that you see on the website is open source, meaning that you can download all the theme files for the showcase site to see how it was all put together.</p>\n\n\n\n<p>If you&#8217;re curious about block development, or how you might convince clients that WordPress is a credible CMS, this podcast is for you.</p>\n\n\n\n<h2 class=\"wp-block-heading\">Useful links</h2>\n\n\n\n<p><a href=\"https://wordpress.org/showcase/\">WordPress Showcase</a></p>\n\n\n\n<p><a href=\"https://wordpress.org/enterprise/\">WordPress Enterprise</a></p>\n\n\n\n<p><a href=\"https://developer.wordpress.org/block-editor/\">The block editor handbook</a></p>\n\n\n\n<p><a href=\"https://developer.wordpress.org/themes/\">The theme handbook</a></p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/\">Learn WordPress</a></p>\n\n\n\n<p><a href=\"https://wordpress.tv/2023/11/02/developer-hours-exploring-the-twenty-twenty-four-theme/\">Recent Developer Hours</a></p>\n\n\n\n<p><a href=\"https://twitter.com/nickmdiego\">Nick&#8217;s Twitter</a></p>\n\n\n\n<p>You can reach out to Nick in the WordPress Slack channel: @ndiego</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 22 Nov 2023 15:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"BuddyPress: BP Classic 1.2.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=331958\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://buddypress.org/2023/11/bp-classic-1-2-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2568:\"<p>Dear end users &amp; site owners,</p>\n\n\n\n<p>Never heard about BP Classic? You should read the <a href=\"https://buddypress.org/2023/07/bp-classic-1-0-0/\">Add-on’s first version announcement post</a>. Please note <a href=\"https://downloads.wordpress.org/plugin/bp-classic.1.2.0.zip\">version 1.2.0</a> is now available for upgrade/download.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2 class=\"wp-block-heading\">What about 1.2.0 changes?</h2>\n\n\n\n<p>3 issues have been fixed:</p>\n\n\n\n<ul>\n<li>Avoid a type mismatch issue during the migration process (See <a href=\"https://github.com/buddypress/bp-classic/issues/27\">#27</a>).</li>\n\n\n\n<li>Only check once BuddyPress current config &amp; version are ok (See <a href=\"https://github.com/buddypress/bp-classic/issues/28\">#28</a>).</li>\n\n\n\n<li>Make sure the migration script is run on Multisite (See <a href=\"https://github.com/buddypress/bp-classic/issues/31\">#31</a>).</li>\n</ul>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2 class=\"wp-block-heading\">Many thanks to the contributors who helped BP Classic be ready for the next BP major release (12.0.0)</h2>\n\n\n\n<p><a href=\"https://buddypress.org/members/imath/\">@imath</a>&nbsp;<a href=\"https://buddypress.org/members/emaralive/\">@emaralive</a></p>\n\n\n\n<p>NB: BuddyPress&nbsp;<strong>12.0.0</strong>&nbsp;is still under development (final release is scheduled to December 6). You can contribute to BP Classic to check it makes sure the third party plugins &#8211; not ready yet for the BP Rewrites API (to be introduced in 12.0.0) &#8211; you are using will behave as expected thanks to this backwards compatibility add-on. To do so simply test it &amp; your BP plugins with the <a href=\"https://buddypress.org/2023/11/buddypress-12-0-0-beta4/\">BP 12.0.0-beta4 pre-release</a> and report issues adding a reply to <a href=\"https://buddypress.org/support/topic/lets-prepare-the-buddypress-12-0-0-next-major-release/\">this topic</a>.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2 class=\"wp-block-heading\">Please upgrade!</h2>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-layout-2 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\"></div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"wp-embedded-content\"><a href=\"https://wordpress.org/plugins/bp-classic/\">BP Classic</a></blockquote>\n</div>\n</div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\"></div>\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Nov 2023 21:01:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"Do The Woo Community: Now is the Time for Passkeys in WordPress, All the Time with Timothy Jacobs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://dothewoo.io/?p=78528\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"https://dothewoo.io/now-is-the-time-for-passkeys-in-wordpress-all-the-time-with-timothy-jacobs/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:584:\"<p>On Emerging Tech, Timothy Jacobs of SolidWP explores passkeys, a security tech for WordPress. Eliminating passwords, it uses biometric data, ensuring user safety and resisting phishing. Adopted by major firms, passkeys promise enhanced WordPress security.</p>\n<p>&gt;&gt; The post <a href=\"https://dothewoo.io/now-is-the-time-for-passkeys-in-wordpress-all-the-time-with-timothy-jacobs/\">Now is the Time for Passkeys in WordPress, All the Time with Timothy Jacobs</a> appeared first on <a href=\"https://dothewoo.io\">Do the Woo - a WooCommerce and WordPress Builder Podcast</a>	.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Nov 2023 08:39:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:48:\"WpOrg\\Requests\\Utility\\CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Sat, 23 Dec 2023 14:15:56 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:13:\"last-modified\";s:29:\"Sat, 23 Dec 2023 14:00:30 GMT\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:16:\"content-encoding\";s:2:\"br\";s:7:\"alt-svc\";s:19:\"h3=\":443\"; ma=86400\";s:4:\"x-nc\";s:9:\"HIT ord 2\";}}s:5:\"build\";s:14:\"20231223135206\";}','no'),(141,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1703384158','no'),(142,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1703340958','no'),(143,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1703384159','no'),(144,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','<div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2023/12/state-of-the-word-2023-recap/\'>State of the Word 2023 Recap</a></li><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2023/12/episode-68-toward-a-more-interconnected-web/\'>WP Briefing: Episode 68: Toward a More Interconnected Web</a></li></ul></div><div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://dothewoo.io/goodbye-2023-and-hello-2024/\'>Do The Woo Community: Goodbye 2023 and Hello 2024</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/podcast/104-thomas-fanchin-on-community-engagement-in-wprdpress-sponsorship\'>WPTavern: #104 – Thomas Fanchin on Community Engagement in WordPress Sponsorship</a></li><li><a class=\'rsswidget\' href=\'https://dothewoo.io/a-post-state-of-the-word-chat-with-rocio-valdivia-pooja-derashri-jose-ramon/\'>Do The Woo Community: A Post State of the Word Chat with Rocio Valdivia, Pooja Derashri &amp; José Ramón</a></li></ul></div>','no'),(145,'theme_mods_twentytwentyfour','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(146,'_site_transient_timeout_theme_roots','1703411206','no'),(147,'_site_transient_theme_roots','a:3:{s:16:\"twentytwentyfour\";s:7:\"/themes\";s:17:\"twentytwentythree\";s:7:\"/themes\";s:15:\"twentytwentytwo\";s:7:\"/themes\";}','no');

--
-- Table structure for table `wp_postmeta`
--

CREATE TABLE `wp_postmeta` (
  `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `post_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext DEFAULT NULL,
  PRIMARY KEY (`meta_id`),
  KEY `post_id` (`post_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_postmeta`
--

INSERT INTO `wp_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default');

--
-- Table structure for table `wp_posts`
--

CREATE TABLE `wp_posts` (
  `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `post_author` bigint(20) unsigned NOT NULL DEFAULT 0,
  `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_content` longtext NOT NULL,
  `post_title` text NOT NULL,
  `post_excerpt` text NOT NULL,
  `post_status` varchar(20) NOT NULL DEFAULT 'publish',
  `comment_status` varchar(20) NOT NULL DEFAULT 'open',
  `ping_status` varchar(20) NOT NULL DEFAULT 'open',
  `post_password` varchar(255) NOT NULL DEFAULT '',
  `post_name` varchar(200) NOT NULL DEFAULT '',
  `to_ping` text NOT NULL,
  `pinged` text NOT NULL,
  `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `post_content_filtered` longtext NOT NULL,
  `post_parent` bigint(20) unsigned NOT NULL DEFAULT 0,
  `guid` varchar(255) NOT NULL DEFAULT '',
  `menu_order` int(11) NOT NULL DEFAULT 0,
  `post_type` varchar(20) NOT NULL DEFAULT 'post',
  `post_mime_type` varchar(100) NOT NULL DEFAULT '',
  `comment_count` bigint(20) NOT NULL DEFAULT 0,
  PRIMARY KEY (`ID`),
  KEY `post_name` (`post_name`(191)),
  KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`),
  KEY `post_parent` (`post_parent`),
  KEY `post_author` (`post_author`)
) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_posts`
--

INSERT INTO `wp_posts` VALUES (1,1,'2023-12-23 14:11:43','2023-12-23 14:11:43','<!-- wp:paragraph -->\n<p>Welcome to WordPress. This is your first post. Edit or delete it, then start writing!</p>\n<!-- /wp:paragraph -->','Hello world!','','publish','open','open','','hello-world','','','2023-12-23 14:11:43','2023-12-23 14:11:43','',0,'http://localhost:8000/?p=1',0,'post','',1),(2,1,'2023-12-23 14:11:43','2023-12-23 14:11:43','<!-- wp:paragraph -->\n<p>This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like pi&#241;a coladas. (And gettin\' caught in the rain.)</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>...or something like this:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>As a new WordPress user, you should go to <a href=\"http://localhost:8000/wp-admin/\">your dashboard</a> to delete this page and create new pages for your content. Have fun!</p>\n<!-- /wp:paragraph -->','Sample Page','','publish','closed','open','','sample-page','','','2023-12-23 14:11:43','2023-12-23 14:11:43','',0,'http://localhost:8000/?page_id=2',0,'page','',0),(3,1,'2023-12-23 14:11:43','2023-12-23 14:11:43','<!-- wp:heading --><h2>Who we are</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>Our website address is: http://localhost:8000.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Comments</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor&#8217;s IP address and browser user agent string to help spam detection.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Media</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Cookies</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select &quot;Remember Me&quot;, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Embedded content from other websites</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Who we share your data with</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>If you request a password reset, your IP address will be included in the reset email.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>How long we retain your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What rights you have over your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Where your data is sent</h2><!-- /wp:heading --><!-- wp:paragraph --><p><strong class=\"privacy-policy-tutorial\">Suggested text: </strong>Visitor comments may be checked through an automated spam detection service.</p><!-- /wp:paragraph -->','Privacy Policy','','draft','closed','open','','privacy-policy','','','2023-12-23 14:11:43','2023-12-23 14:11:43','',0,'http://localhost:8000/?page_id=3',0,'page','',0),(4,1,'2023-12-23 14:15:43','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2023-12-23 14:15:43','0000-00-00 00:00:00','',0,'http://localhost:8000/?p=4',0,'post','',0),(5,1,'2023-12-23 14:15:46','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2023-12-23 14:15:46','0000-00-00 00:00:00','',0,'http://localhost:8000/?p=5',0,'post','',0),(6,1,'2023-12-23 14:16:49','2023-12-23 14:16:49','<!-- wp:page-list /-->','Navigation','','publish','closed','closed','','navigation','','','2023-12-23 14:16:49','2023-12-23 14:16:49','',0,'http://localhost:8000/?p=6',0,'wp_navigation','',0);

--
-- Table structure for table `wp_term_relationships`
--

CREATE TABLE `wp_term_relationships` (
  `object_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `term_order` int(11) NOT NULL DEFAULT 0,
  PRIMARY KEY (`object_id`,`term_taxonomy_id`),
  KEY `term_taxonomy_id` (`term_taxonomy_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_term_relationships`
--

INSERT INTO `wp_term_relationships` VALUES (1,1,0);

--
-- Table structure for table `wp_term_taxonomy`
--

CREATE TABLE `wp_term_taxonomy` (
  `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `term_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `taxonomy` varchar(32) NOT NULL DEFAULT '',
  `description` longtext NOT NULL,
  `parent` bigint(20) unsigned NOT NULL DEFAULT 0,
  `count` bigint(20) NOT NULL DEFAULT 0,
  PRIMARY KEY (`term_taxonomy_id`),
  UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
  KEY `taxonomy` (`taxonomy`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_term_taxonomy`
--

INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1);

--
-- Table structure for table `wp_termmeta`
--

CREATE TABLE `wp_termmeta` (
  `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `term_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext DEFAULT NULL,
  PRIMARY KEY (`meta_id`),
  KEY `term_id` (`term_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_termmeta`
--


--
-- Table structure for table `wp_terms`
--

CREATE TABLE `wp_terms` (
  `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(200) NOT NULL DEFAULT '',
  `slug` varchar(200) NOT NULL DEFAULT '',
  `term_group` bigint(10) NOT NULL DEFAULT 0,
  PRIMARY KEY (`term_id`),
  KEY `slug` (`slug`(191)),
  KEY `name` (`name`(191))
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_terms`
--

INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0);

--
-- Table structure for table `wp_usermeta`
--

CREATE TABLE `wp_usermeta` (
  `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `user_id` bigint(20) unsigned NOT NULL DEFAULT 0,
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext DEFAULT NULL,
  PRIMARY KEY (`umeta_id`),
  KEY `user_id` (`user_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_usermeta`
--

INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','gillesah'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','1'),(16,1,'session_tokens','a:3:{s:64:\"17eee600c7d791babe5c7abf669cf582383f5148be7f0c00a07a8f689ff64659\";a:4:{s:10:\"expiration\";i:1703513724;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:101:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36\";s:5:\"login\";i:1703340924;}s:64:\"60870a8323f17287ea198beaac809e643ee6cc7c551adc4957ec18b993926fc3\";a:4:{s:10:\"expiration\";i:1703513739;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:101:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36\";s:5:\"login\";i:1703340939;}s:64:\"46346f365652d89954b1e4de1360ed72985d0c38681ca2504bced6785002f358\";a:4:{s:10:\"expiration\";i:1703582202;s:2:\"ip\";s:10:\"172.18.0.1\";s:2:\"ua\";s:101:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36\";s:5:\"login\";i:1703409402;}}'),(17,1,'wp_dashboard_quick_press_last_post_id','5'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.18.0.0\";}');

--
-- Table structure for table `wp_users`
--

CREATE TABLE `wp_users` (
  `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `user_login` varchar(60) NOT NULL DEFAULT '',
  `user_pass` varchar(255) NOT NULL DEFAULT '',
  `user_nicename` varchar(50) NOT NULL DEFAULT '',
  `user_email` varchar(100) NOT NULL DEFAULT '',
  `user_url` varchar(100) NOT NULL DEFAULT '',
  `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `user_activation_key` varchar(255) NOT NULL DEFAULT '',
  `user_status` int(11) NOT NULL DEFAULT 0,
  `display_name` varchar(250) NOT NULL DEFAULT '',
  PRIMARY KEY (`ID`),
  KEY `user_login_key` (`user_login`),
  KEY `user_nicename` (`user_nicename`),
  KEY `user_email` (`user_email`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_users`
--

INSERT INTO `wp_users` VALUES (1,'gillesah','$P$BAsDdE54n3q7BJ0LmVuNcUFZrJcveX1','gillesah','helleugilles@gmail.com','http://localhost:8000','2023-12-23 14:11:27','',0,'gillesah');


