


<p>So, content needs to be tagged with main to actually have that work. If people are creating sites or layouts with column blocks and each column doesn&#8217;t have any tag, but one is a sidebar that&#8217;s a reusable block, or it&#8217;s a template part, it will read through that every single time on every page, if it&#8217;s not tagged non-content, or a sidebar, or side, or something like that, or the main content is not tagged. Now, you couldn&#8217;t do that with a classic theme from a user interface, but you can do it actually with a group block that has these HTML elements that you can designate your content being either a main or a side. But the most important part is that you wrap whatever sidebar you have into a group block and then select those HTML elements. They&#8217;re also not very prominent, they&#8217;re in the advanced section.</p>



<p>So, I just wanted to, those who are creating themes through the site editor or helping others to create templates, to be aware of these accessibility ramifications, or to make it known what people who are not visually impaired can see, that that&#8217;s repeated content, but the screen readers that help those that are impaired to go through the internet websites need a little help from the content creators or from the template creators. So, I&#8217;m sure there will be some more information about that, I just wanted you to be aware, and thank you for the listener to pick up on that and point that out. Accessibility is such an important part of web design and web building, that we need to make sure that if we use just the interfaces that we have those tools in place.</p>



<p><em>Anne McCarthy</em>: I couldn&#8217;t agree more. Thanks for going through that too, it&#8217;s always good to learn about this stuff and to make sure that the default implementation ideally, can be done well. And this is where folks can create patterns into the parts to have this set up automatically in their themes with the right stuff in place. So I also encourage blocking authors to think about that.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And I think it&#8217;s sometimes really hard on the user documentation to point out the higher ramification. If you just point out this little piece on the sidebar that is a new interface, what is the bigger objective for that?&nbsp;</p>



<h3 class="wp-block-heading"><strong>Announcements</strong></h3>



<p>So, I&#8217;m really glad that the listener sent me that email and let me know about that, that&#8217;s a good question. So, Anne, you just published a post on the news site, speaking of changes for wordpress.org and it&#8217;s titled, Synced Patterns: the Evolution of Reusable Blocks. On the Podcast, we talked a little bit about the upcoming changes, so what is this post all about?</p>



<p><em>Anne McCarthy</em>: Yeah, so this builds on work that&#8217;s done in 6.3, to bring the creation of patterns to the experience, and that&#8217;s part of that you can sync or unsync patterns, which basically consolidates the concept of reusable block into the new concept of synced patterns. So this post is just trying to flag the change for people because reusable blocks is a known concept in the WordPress community, and retiring such a known concept deserves a lot of attention. And as part of this, there will be documentation updated, I am keeping an eye on that there, but this is just one of many efforts, including nudges in the interface to help communicate this change to folks. So, just see this as part of a larger effort to make sure that we&#8217;re bringing folks along as things evolve. I&#8217;m personally really excited because I think compared to the concept of reusable blocks, which sounds almost more technical than it should be, I think patterns is a much more approachable concept for folks to get behind and to use.</p>



<p>So, I&#8217;m really excited and I hope it helps surface this more for folks, whenever they&#8217;re working with WordPress. But yeah, it&#8217;s pretty exciting. So, unseen patterns are essentially what you know and love as patterns today, you can put them in your post or page or template and customize it as you&#8217;d like, it&#8217;s not synced across the entire system. Sync patterns are just exactly how our usable blocks worked. They&#8217;re synced across things, you can have a way to convert to blocks if you want to edit it individually and turn it into an unsynced pattern. But yeah, there&#8217;ll be a whole interface to manage all your patterns, if you&#8217;re using a block theme, if you&#8217;re using a classic theme, we basically just reuse what&#8217;s in place for the reusable block screen. So, honestly, it&#8217;s a lot of just interface changes for, if you&#8217;re using a classic theme and for a block theme it unlocks a lot of functionality in terms of being able to manage all your patterns across themes and plugins and all sorts of stuff.</p>



<p>So, yeah, it&#8217;s a huge, huge step forward and a big change, so hopefully this helps get you prepared, and if you have questions or things that you want answered, yeah, I&#8217;m @annezazu, Let me know what we&#8217;re not thinking about because I&#8217;m sure there&#8217;s a lot.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, and I had some conversations before in the last two months, once I saw that this change is going to come, and I was really excited that finally we have the feature to grade your own patterns in your own site. I think there were quite a few plugins out there that had very high installs and it&#8217;s now coming to core. I think the design team and the developers did a great job in just changing the name but leave everything else in place, for those who use reusable block or created reusable block, everything will be familiar, just the names are going to change. The concept itself is not necessarily retired, it&#8217;s just going to build into the pattern metaphor more. Because really, the only difference between a pattern and a reusable block was the synchronization over the instances. Yeah, definitely.</p>



<p>Yeah, so we talked about it here at the podcast before and it brings us a leap forward, it also opens up the doors to additional changes. Because what I hear also, and you probably hear it even more, is what&#8217;s missing is that if you have a pattern and that&#8217;s used around the website, but all of a sudden you want to change styles, you&#8217;re not catching every pattern because you need to open up that, switch it out, you have to work around that. And so, partial synced patterns are now possible because we have an interface now, and it&#8217;s certainly further down the roadmap to find a way for the canvas to remember this was an unsynced pattern, but it can be partially synced. Because that is certainly missing in between where you don&#8217;t want to update content but you want to update the styling here, and the content stays the same that it was there.</p>



<p>So, it&#8217;s all a little bit&#8230; But bringing it all together is reducing the cognitive load on things and have it all in one metaphor rather than have different ways on doing things. And you&#8217;ll find it just the same way you found it before. The icons are the same and the color is the same and the list views&#8230; I think you&#8217;ll find that the switch over to the new thing from reusable block to sync pattern is relatively&#8230; I wanted to say harmless, but smooth. Painless is, I think, the one that I was looking for.</p>



<p><em>Anne McCarthy</em>: Yes.</p>



<h3 class="wp-block-heading"><strong>What’s Released &#8211; WordPress 6.3</strong></h3>



<p><em>Birgit Pauli-Haack</em>: So, that brings us to our section on what&#8217;s released. WordPress 6.3 is coming fast, Release Candidate 2 is out, has been out since the beginning of the week, and is ready for testing. The final release is scheduled for August 8th, and that&#8217;s less than two weeks to go. So, what&#8217;s the latest information about 6.3? Is everything on track? The dev notes have been out, your post is out about the sync patterns, you also published a post about the accessibility improvements and there have been a ton of dev notes also for the performance improvements. Is there anything else that has been new or what are the features that you are most excited about?</p>



<p><em>Anne McCarthy</em>: Oh man, that&#8217;s a great question.</p>



<p><em>Birgit Pauli-Haack</em>: Can you pick?</p>



<p><em>Anne McCarthy</em>: Yeah, can I pick? I will say, actually, I&#8217;m very excited&#8230; I did a YouTube video on this. There&#8217;s some hidden features and one of them, that&#8217;s not really hidden, but I think it can be taken for granted, it&#8217;s really the block theme previews. That has been something, that people have been unable to preview a block theme. So to even try to explore a required setting up a test site required, or just fully activating it without knowing how it might impact your site, and the ability to preview&#8230; And the preview uses the site editor, so you&#8217;re both getting a sense of what the theme will do, how it might impact your site, what bells and whistles it has, and it allows you to actually dive into the site editor itself and get a feel for it. And I&#8217;m just completely excited about that.</p>



<p>I think that will be a huge thing with adoption that will be the unsung hero of this release in my mind. It&#8217;s been something that&#8217;s been a pain point for a long time and a lot of work went in to make it smooth, and yeah, it&#8217;s something I&#8217;m very excited to play around with and to see how it impacts things and helps folks step into that world. The only other thing&#8230; Thank you for calling out the accessibility improvements as well, so much work has gone into that with a lot of these features and more work remains to be done. But I&#8217;m in particular excited about some of the improvements to List View, which I know Alex Stein spent a lot of time doing, and so I want to call that out in particular as something that I&#8217;m quite excited about. I think the only other thing on my mind relates to, right now, there is some conversation around footnotes and how footnotes are being stored, and there&#8217;s some interesting dialogue there.</p>



<p>I think we&#8217;ll end up seeing fixes get in place for it, but it&#8217;s just neat how these tiny blocks that are packed full of power are continuing to be iterated on at this point and getting bug fixes. So thank you to everyone who&#8217;s testing, because a lot of that has come from testing and feedback. And I know it might seem like, oh, we&#8217;re in the RC, things are smooth sailing, but you never know. We&#8217;ve had to remove stuff, we had to remove something in 6.2, so we still have time for the final release and we want it to be as polished and bug-free as possible.</p>



<p>So it&#8217;s a very high impact time to be testing WordPress 6.3. This is actually my favorite time, because if you find something now, it&#8217;s also not great, but if you find something now, you prevent it for millions of people, so I think it&#8217;s a really exciting and important time. But there&#8217;s nothing, I&#8217;m trying to think of anything else in my mind that&#8217;s super&#8230; Beyond all this pattern stuff and all the other stuff that we&#8217;ve been talking about, but the blocking previews really does stand out to me personally, as something as I&#8217;m particularly excited about.</p>



<p><em>Birgit Pauli-Haack</em>: I really like how the style book is happening around the site editor, that you can really see all the&#8230; Even if you change something on the style variation and then propagate it, you see how it changes all the blocks, or if it doesn&#8217;t change the blocks. So, is the theme preview actually also using the style book? If you go into a preview and then you see the site editor, can you access the style book to see how the…</p>



<p><em>Anne McCarthy</em>: Yes.</p>



<p><em>Birgit Pauli-Haack</em>: Yes. Yeah, that&#8217;s what I thought.</p>



<p><em>Anne McCarthy</em>: Yes, you can. Yeah, the entire site editor is using the preview, it&#8217;s amazing. The main thing that&#8217;s missing right now that some folks have brought up is the ability to schedule and save this draft, those different things. So that is work that needs to be done, that got brought up in the product demo, that needs to be done still, but we&#8217;ll get there. I think that&#8217;s part of the fun about iterating on this stuff, is like, yeah, yeah, totally, that is part of the roadmap, that&#8217;s something we&#8217;ll get to.</p>



<p><em>Birgit Pauli-Haack</em>: I still remember the excitement, when the customers got that feature to schedule updates.</p>



<p><em>Anne McCarthy</em>: Really?</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, where people got ready for Christmas changes or for special sales on their website and then they could put it in the customizer and schedule it and then go on vacation or whatever.</p>



<p><em>Anne McCarthy</em>: Which is very cool.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, which is really cool. And it wasn&#8217;t so long ago, so that&#8217;s why people are still, come from that excitement and find it missing. But yeah, getting the previous in is really big. Yeah, absolutely.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: So…</p>



<p><em>Anne McCarthy</em>: Now, also…</p>



<p><em>Birgit Pauli-Haack</em>: Mm-hmm, go ahead.</p>



<p><em>Anne McCarthy</em>: Revisions is the only other one that just came to mind, as we&#8217;re talking about revisions and saving and all that sort of stuff. The visual nature of the star revisions is so cool. Template and template part revisions didn&#8217;t make it for 6.3, but I&#8217;m hoping to see that in 6.4, and I think when that completion happens, I&#8217;m curious to see what kind of confusion might come up around if you have multiple different&#8230; I&#8217;ve already noticed that, some calls for testing, where people are like, oh, I made a change to the title of this, whatever, and then try to roll back with star revisions, and it&#8217;s like, oh no, you actually need do that with template revisions. So, having an intelligent system that works and makes sense, you know where to roll back, but there&#8217;s been so much good feedback about how visual and easy and beautiful the star revisions are. So, that&#8217;s another hidden feature that I like to talk about.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, that&#8217;s great. The hidden features of 6.3, with Anne McCarthy. Yeah.</p>



<p><em>Anne McCarthy</em>: Could be here for two hours if I do that.</p>



<p><em>Birgit Pauli-Haack</em>: Well, we have an open-ended thing here. Sooner or later I need to go to bed though. So, Anne and I, we are nine hours apart. So, Anne just got up and I&#8217;m at the end of the day, so.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Gutenberg 16.3</strong></h3>



<p>So, Gutenberg 16.3, last time I looked it was about 180 PRs…</p>



<p><em>Anne McCarthy</em>: Ooh.</p>



<h3 class="wp-block-heading"><strong>Enhancements</strong></h3>



<p><em>Birgit Pauli-Haack</em>: &#8230;it&#8217;s one of the larger Gutenberg releases from 54 contributors. Two of them were first timers, and I think it was a lot of polishing and bug fixes, but there were also a few enhancements that made it into 6.3, and some of them don&#8217;t, probably, but let&#8217;s talk about them. So, the first one that I see was that you can have more intuitive archive titles for your query title block, there&#8217;s quite a few changes around that. Those don&#8217;t make it into 6.3 though, but it&#8217;s because it&#8217;s the first time it&#8217;s in there I think. So you can change the titles of your archive pages, remove the archive type, and what else is in there?&nbsp;</p>



<p><em>Anne McCarthy</em>: I think this is hugely helpful because this is definitely something where we&#8217;ve gotten feedback from folks, where it was too generic before, it just showed archive title or whatever. It would not say specifically what you&#8217;re looking at, and when you&#8217;re creating a new template and you&#8217;re a first time user you might delete it, because you don&#8217;t know what it is. So knowing what it powers, knowing what it does, it&#8217;s a huge step up and I&#8217;m quite excited about this.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, yeah. And then the whole change the title of your archive pages is such an improvement towards the classic experience, because you always needed a developer to remove something or to change the title and now you can do it by yourself and you can create any kind of different templates with a query block, or the post template block. Yeah. So, yeah, next up is the add, renaming, duplication, and deletion option to patterns. That&#8217;s certainly coming into 6.3, patterns now have a dropdown menu, you can assess the three dots and then allow you to rename, duplicate and delete patterns easily. It wasn&#8217;t easy to do that before, especially the removal of patterns from your my patterns kind of thing. Yeah, it was a little bit convoluted because it wasn&#8217;t through the editor, now you can do it all through the editor. Yeah.</p>



<p><em>Anne McCarthy</em>: I&#8217;ll also note, one of the reasons why this is also so important to get in and why it was backported in my opinion, is that when you are setting&#8230; You create a pattern and you set the sync status, so synced or unsynced, you cannot change that status after the fact. So, let&#8217;s say you make a mistake, you create an unsync and you&#8217;re like, wait, actually, I want this to be synced. Before you&#8217;d have to go in and copy/paste, this whole convoluted process, now, with the duplication you can duplicate, and when you duplicate you can basically decide the sync status. So that&#8217;s one of the things that came up, was we wanted a way to make it easy to give people control without having the option to change the sync status back and forth because that will create some muddiness.</p>



<p>Let&#8217;s say you synced a pattern and then you randomly unsynced it two months later, imagine how that might create some chaos across your site. So, to limit that, we just basically said you cannot change the sync status after it&#8217;s created, but we&#8217;ll add in options to make it easy to manage those things. And things like, renaming and deleting are also just important basics to have, so yeah, I&#8217;m glad to see this in, and I think not being able to set the sync status might cause some confusion, so I&#8217;m curious how that lands with 6.3 and how we can integrate it for 6.4.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Yeah, I had some questions that were around that before, but the duplication feature, yeah, one click duplication, it&#8217;s pretty much, your work is not wasted, you just can replicate it and move forward with that. Yeah. The next piece is enable focus mode editing patterns. It was available for template parts before the focus modals, but now it&#8217;s also available for patterns, and it is then also backport it to 6.3&#8230; I&#8217;m just going to double check.</p>



<p><em>Anne McCarthy</em>: I&#8217;m nearly positive, yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, me too, but…</p>



<p><em>Anne McCarthy</em>: Potentially not. Let&#8217;s see if it works.</p>



<p><em>Birgit Pauli-Haack</em>: Potentially not, yeah.</p>



<p><em>Anne McCarthy</em>: Maybe we should consider it. It might be because a new feature, but I&#8217;m like&#8230; We&#8217;re both on the corridor triage team here, it&#8217;s like, thoughts on backporting.</p>



<p><em>Birgit Pauli-Haack</em>: Maybe we should put it on the 6.3 editor task.</p>



<p><em>Anne McCarthy</em>: Yeah. Yeah, let&#8217;s drop it into the triage session we&#8217;re doing today. Nice, I love it.</p>



<p><em>Birgit Pauli-Haack</em>: All right, and the next part is that&#8230; Well, it&#8217;s the copy, to make sure that reusable is removed from menus and all that, for the reusable block. The next part is the sticky header and pagination for pattern page. That is really cool.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah.</p>



<p><em>Anne McCarthy</em>: Yeah. I love seeing that. And that basically takes the patterns section of the block editor and ensures that when you&#8217;re scrolling down, unless you have a ton of patterns, that top heading that you can filter with will still appear, and it&#8217;s a quality of life improvement and definitely something that, if you have lots of patterns, which a lot of sites do with block themes, it&#8217;s pretty critical to be able to switch between and see what you&#8217;re actually seeing. So, I was pretty excited to see that in there.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And I like the filter part, that you can just show me the synced patterns, just show me the unsynced patterns, so that&#8217;s really cool. The next one is, I wanted to mention it because that&#8217;s one of the changes, so the links that go to manage reusable blocks and manage patterns go to different places now. So, they go now to this site editor, where all the other interfaces are, to interact with patterns synced and unsynced patterns. There is that place, the WP admin looking place, still there, but now you can use all the site editor for the editing part. So, I think we will have that quite a bit in the next few releases, that we have a new managed thing, and then we can go back to the old thing, just because it might not be feature parity or so. I think that&#8217;s the first place where we can train ourselves with that.</p>



<p>So, I like the site editor very much, but I&#8217;m still often going back to the WP admin and see a few things there. Yeah. Yeah, we talked about the sync status separation on the filter control already, but that&#8217;s coming also to 6.3, and it was backported to Beta 4. The components have been updated to support defined IDs for the text control component, that means that you can target them with CSS and also with JavaScript, and directly with the IDs, and identify…</p>



<p><em>Anne McCarthy</em>: Very cool.</p>



<p><em>Birgit Pauli-Haack</em>: &#8230;particular instances of the text control component, which is really important for a lot of extensibility usage there. There were some changes for the Interactivity API, and that&#8217;s only on the Gutenberg plugin. That, of course, every time we have a new thing in WordPress, we need to think about turning it off. What is necessary to turn things off? And so, the same with Interactivity API, it has been merged into 16.2, but not for 6.3, not for the WordPress, it&#8217;s coming in 6.4. But even with the Gutenberg plugin enabled, some people still want to turn off the Interactivity API because it interferes with their extensions.</p>



<p>So, there&#8217;s now a filter to do this, and there&#8217;s also a runtime support to the WP style directive, so you can, on the fly, change the style for some of the Interactivity API entities. So, that&#8217;s these two things of Interactivity API. I&#8217;m sure there will be, very soon, a little bit more, a higher level, but also a more strategic announcement or strategic documentation about the Interactivity API. I know a few of our coworkers are working on that, to get this out, but with all the documentation it&#8217;s always a little bit behind the features there. So, go into the PRs to learn more about it.</p>



<p><em>Anne McCarthy</em>: Yeah, I&#8217;ll note too on that front. I got some really good feedback from someone saying, &#8220;Hey, this project&#8217;s been hard to keep on top of.&#8221; And so that was feedback that&#8217;s been brought back to the folks working on that. So, I think, last I can remember, from a conversation, my brain&#8217;s a bit mushy in the last couple of weeks, but I think they&#8217;re going to try and experiment with using discussion issues as a way to keep track of things, which is a bit of a departure from using overview or tracking issue labels in GitHub, but I think it&#8217;s going to be interesting and we can learn from that. But it is, as you said, anytime you add something, we need to think about removing it, and I know the Interactivity API is likely slated for 6.4, so it&#8217;s definitely something you can keep on top of and this was a great thing to call out. I could see folks skimming over this and not realizing how important it is. So, it&#8217;s a good one to keep in mind.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. In WordCamp Europe, I talked with quite a few people&#8230; Well, there were 2000 people there and I probably talked to 200 or so. So, I couldn&#8217;t talk to everybody. But there were quite a few people who were a little bit hesitant with a block editor because they&#8217;re PHP developers, and JavaScript is not really their thing, and they were really excited about the Interactivity API and the bigger emphasis on the dynamic blocks rather than the static JavaScript block. Because they can use the render that they did in shortcuts and then in widgets or something like that, all the render code, they can now use for blocks and then put the Interactivity API just in the directives in there to, to make it replicate some of the features that they had before. Which seems to be easier than the JavaScript, jumping all in on the JavaScript side. Yeah.</p>



<p>So, well, from the block library section, there&#8217;s one component, the range control, that now has an additional attribute for the default size of 40 pixels. I think it does a few other sizes, but you can now use it if you use it in your own plugin settings pages or your own sidebar items, you can have a different size as a default size managed there. So that&#8217;s pretty cool.</p>



<p><em>Anne McCarthy</em>: My understanding of that one was that it was updating the component to use the 40 pixel size and the design, but I could be wrong about that. I know Rich was working on that. So, I think it&#8217;s less having a default set and more having consistency across the settings. It&#8217;s a design quality of life. Because right now I think that settings page has been shifted around, but yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, that&#8217;s what I get from the PR too, but it&#8217;s an additional attribute or a different component for the range control, because they need to keep it backwards compatible. So, what goes for the core range controls, the previous attributes and range control sizes are still in there, so it&#8217;s practically an enhancement there. But the core view is the new default, 40 pixel thing there.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s what I understood. But I might be wrong, I&#8217;ve been wrong before, so.</p>



<p><em>Anne McCarthy</em>: Same. Same. Been looking at too much stuff anyway.</p>



<h3 class="wp-block-heading"><strong>New API</strong></h3>



<p><em>Birgit Pauli-Haack</em>: Yeah, sometimes you make it up as you go along, right? So, the next item is about the nested inner blocks. There&#8217;s a new API, or at least stabilizing existing API for default block, direct insert, and get direct insert block selectors, that were previously experimental, and it was hard to build on top of them. And one of the panelists that were on our past live Q&amp;A, Seth Rubenstein, stabilized those, as a first time contributor, stabilize those APIs. So he can also work on a separate PR, that he shared some code from their Pew Research work on quizzes with the core developers, with core. So, that&#8217;s really good that community developers also stabilize some of the APIs so they can continue on their quest of making the plug editor more versatile.</p>



<p><em>Anne McCarthy</em>: Yeah, I love seeing this, and Seth has been awesome to be driving stuff forward, with really practical use cases, and I think it&#8217;s a great example of using and extending Gutenberg and the core editor, and then also contributing back in a way that furthers it and is in line with the goals of this project. So, I think it&#8217;s really exciting and cool to see this moving along.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And they want to make some of the quiz code available as plugins, but you&#8217;re not supposed to put in plugins in the repo when you have experimental APIs in there. So yeah, that&#8217;s where this work also comes in, so it&#8217;s really important to make this all work in stable conditions.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Bug Fixes</strong></h3>



<p>The next part is for patterns and alternative grid layout to improve keyboard accessibility. That&#8217;s one of the accessibility improvements that you were talking about before.</p>



<p><em>Anne McCarthy</em>: Yeah, as we&#8217;ve talked about just generally adding new features, accessibility does need to keep up and we need to have it accessible for all folks. And so, this just makes a change to using a standard UL, with keyboard tab indexes, to try and improve keyboard accessibility in particular. And I&#8217;m nearly positive&#8230; Scroll down. Yeah, I was going to say, AFercia who is, that&#8217;s the GitHub username, he is sponsored by Yoast, did a great job reviewing this, and to the point that Alex Stein was like, &#8220;This looks good to me.&#8221; And so, it&#8217;s another great example of showing the back and forth between the teams, but I also would love to get to the point where this is done by default and not caught later. So, it&#8217;s great to see the collaboration and to see this being done. And I know the accessibility team is always looking for more help, so it&#8217;s just great to see the back and forth and it is back forwarded to the release.</p>



<p><em>Birgit Pauli-Haack</em>: To 6.3, yeah. Yeah. Yeah, I&#8217;m really glad to see Andrea coming back to the accessibility team. He did take a break from working on the accessibility team, but I think he found quite a few contributors now really digging into Gutenberg. So he felt a little lonely about three or four years ago, before the pandemic definitely, and so I&#8217;m glad he&#8217;s contributing back again on the team. And sponsored by Yoast, just to mention that once in a while. Great. The next part, yeah, so there is a fix to apply text color selection to link color if link color isn&#8217;t active. That has been a long-standing issue with the block editor, that people who changed the text color on the paragraph didn&#8217;t get the same color also for the link color and needed to change that separately.</p>



<p>And some people, because it&#8217;s not a default control on the paragraph, just didn&#8217;t know about the link color and how to change it, and it really wanted to not make the changes and couldn&#8217;t dream up the new design. So, I&#8217;m really glad that that is now by default. Well, of course if you want to change the link color you can, but if you just change the text color in a paragraph, it automatically also changes the link color.</p>



<p><em>Anne McCarthy</em>: And I want to call out, that that was part of an effort on a project board, which is a bit in the weeds, but the UX and Polish project board is a board within the Gutenberg project that is specifically for just super actionable issues, that are typically, quality of life, as the name suggest with Polish. And then user experience, so how can we make it just super intuitive? So, I just want to point that out, is the more you can write really targeted contained requests that are like, this is just a pain in the butt, I run through this a couple of times a week or something like that, it&#8217;s a great consideration for the UX and Polish board.</p>



<p>I think there&#8217;s been maybe 80 items completed as a part of the UX and Polish board, which is kind of wild. And it&#8217;s something that I know a lot of folks keep an eye on, and it&#8217;s a great, if you&#8217;re a new developer and you want to get started, it&#8217;s also a great place to go and look at ways you can improve the project. So, I was excited to see that done as well.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Does it make sense to share the link to the project board in our show notes?</p>



<p><em>Anne McCarthy</em>: Yeah, let&#8217;s do it.</p>



<p><em>Birgit Pauli-Haack</em>: &#8230; so all the developers can grab things on what they&#8217;re interested in, and see the progress on it? Or even just test some of the PRs that are available and see if they are doing what they&#8217;re supposed to do.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Performance</strong></h3>



<p>Yeah. So, the next thing is add client-side pagination to the panel list, client-side means in your browser, so you don&#8217;t go back to the server to get the next pages of patterns. I think that&#8217;s definitely a quality of life improvement. And this also has been ported back.</p>



<p><em>Anne McCarthy</em>: This is the fun time with Gutenberg releases, where it&#8217;s like, what&#8217;s backported?</p>



<p><em>Birgit Pauli-Haack</em>: Yeah.</p>



<p><em>Anne McCarthy</em>: What&#8217;s not? It was cherry-picked for everyone.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, it&#8217;s synced with the core WordPress. Yeah, it doesn&#8217;t work. What&#8217;s backported? Yeah. What else? Do you want to talk about the work that&#8217;s done with the TinyMCE compatibility and the classic editor? Or the classic block in bigger projects?</p>



<p><em>Anne McCarthy</em>: Yeah. So, one of the things that&#8217;s fun about Gutenberg is there&#8217;s actually experiments you can turn on and off. And so right now, from what I&#8217;m seeing, is there&#8217;s an experiment for TinyMCE removal, basically to help with compatibility with the classic editor plugin, and other plugins that disable the block editor. So, previously an experiment was introduced to help with TinyMCE removal, and so they&#8217;re just trying to polish this to make sure that there aren&#8217;t any regressions or just weird edge cases, and make sure that it&#8217;s using the same filter for classic editor plugin is using.</p>



<p>So, it&#8217;s not for a lot of folks who are, Gutenberg change log, who are Gutenberg forward, but I think it is important to consider when we think about broader adoption and folks still using the classic editor, work and thought is still put in there. I know sometimes that feedback bubbles up, but there are efforts underway to ensure that people who do want to disable it, it still works. But yeah, I would encourage folks to also just use blocks. But yeah, I would call this a maintenance task, something that is really to just plug in interoperability and make sure things still work as expected. And so, it&#8217;s something that might be not as glamorous and shiny, but it&#8217;s still important work to do as part of the wider WordPress ecosystem.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And definitely, because there is this backwards compatibility promise for WordPress, and not only for the classic editor, but also for the classic theme. So, keeping that in mind, when you move forward in a different direction that people are still using the current stuff quite extensively and successfully, so they&#8217;re not impaired by any changes that are done. But sometimes these things are strategic and need to have a broader attention span on it and just not that one single feature. Excellent. So, I&#8217;m really glad that there is somebody on it. Yeah.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Documentation</strong></h3>



<p>The next thing is mostly just to say that the documentation has been updated for the layout architecture after some of the APIs were stabilized. So, they are now showing up in the documentation and they&#8217;re not labeled as private or as experimental. So, that is definitely also a good thing, because a lot of people are a little bit hesitant to use experimental APIs or features.</p>



<p>So, every time you can stabilize them and update the documentation so people know about it, is a good thing, it&#8217;s a good day. What else do we find? Oh yeah, there is an interactive template for talking about the Interactivity API.&nbsp;</p>



<h3 class="wp-block-heading"><strong>Tools</strong></h3>



<p>So, we have this scaffolding tool called Create Block, which speeds up your block development quite a bit when you start out with a new one or with putting additional blocks into a plugin. And now, there is also a template to use the Interactivity API on the next block that you are trying to build, that you&#8217;re working on, so you don&#8217;t have to include all the Interactivity stuff, for lack of a better technical term. And hook it up to all your other files, so there&#8217;s a template there. And it&#8217;s available now with a command line command, so that is certainly something for those people that want to dive into the Interactivity API.&nbsp;</p>



<p><em>Anne McCarthy</em>: And when we make stuff like that easier, it&#8217;s so exciting, so great to call out.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. Yeah, I think the great block scaffolding tool actually has not gotten enough exposure into the developers, because it was so late when it came out, people tried to build blocks and then gave up quite a bit. But now, every course, every tutorial that comes out of WordPress education or for the developer block uses a great block scaffolding. We hope to get more people building blocks.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. So, I think we are through with the change log, that&#8217;s what we wanted to point out for 16.3.&nbsp;</p>



<h3 class="wp-block-heading"><strong>What’s in Active Development or Discussed</strong></h3>



<p>So, in active development, I think everybody, we talked about, just briefly about the phase three collaboration phase and all the posts that are there, we didn&#8217;t talk too much about it because WordPress 6.3 is such a big thing in front of us, the collaboration, we don&#8217;t know yet what&#8217;s going to be, but everyone&#8217;s excited, I think about the admin changes as well as the media library. And then, of course, the real time collaboration and the async collaboration, there&#8217;s a lot to come out. So, what are the next steps that we are going to see when people say, okay, some of us are still working on the Polish and UI changes for the site editor, and some of us are going to start and move over to the collaboration?</p>



<p><em>Anne McCarthy</em>: Yeah, I will say, I don&#8217;t anticipate to see any sort of real time collaboration added into 6.4. I think it&#8217;s such a short release cycle, so I just want to put that out there. I&#8217;m not seeing headwinds about that or momentum in that direction. But I do think that&#8217;ll give us lots of time to experiment, and I know Riad posted on Make Core about the realtime architecture, which is totally worth reading. And there&#8217;s also a GitHub issue, of course, it is a GitHub issue. But right now, the feedback that I&#8217;ve gotten and questions that I&#8217;ve gotten, since I run basically the phase two outreach program, the full site outreach program is, it&#8217;s, what outreach are we doing? What&#8217;s going to happen with that? Are you going to run one for that? There&#8217;s a lot of questions bubbling up, of what&#8217;s next.</p>



<p>And right now, I will say, the focus remains on 6.3, but I would expect to see a lot of experimentation, a lot of stuff starting up. I have done some outreach to plugin authors, I&#8217;ve done related functionality like that. I&#8217;ve started talking to folks in a larger to medium to small publishing space and agencies and all that sort of stuff. But I encourage folks to stay tuned and as soon as something is ready, I planned, and I&#8217;m sure you planned, to shout it from the rooftops, try and get folks involved and figure out exactly how best to organize stuff. Because I think that is a big question is, these are such related but yet disparate initiatives, and I don&#8217;t think there&#8217;s necessarily an overarching, here is the next thing we&#8217;re doing. I think some folks, some individual contributors, are just kind of trying to explore and pave the path for now and see what we can learn, ahead of a more collective push, once 6.3 is out the door.</p>



<p>But yeah, I expect things to be more experimental in the Gutenberg plugin, by the time 6.4 is released. And then 6.5 is when I am more anxious about what are we going to have in place and how can people help test. And so, right now, I encourage folks to comment on the post that Matias wrote, share your feedback, share your experiences. Are you a writer? Are you a journalist who&#8217;s had to work in collaborative situations? Talk about it, write your comments, what do you want to see? What do you like about other tools that have those kinds of features in place? What workflows does your team have?</p>



<p>Yeah, I think there&#8217;s a plugin author who commented recently on a workflows post, after we had exchanged some emails, who works on a calendar. So, you have a calendar post coming up and you have workflows related to that. And he took the time to very kindly share his feedback. So, anything you can do there is super helpful, whether it&#8217;s your plugin or you&#8217;re a writer or you&#8217;re an organizational leader who has to manage this kind of stuff.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, that&#8217;s going to be real interesting. So, any feedback is really helpful in that. I just wanted to go back to what you said, okay, there&#8217;s not going to be a whole lot in 6.4 for phase three. I know there&#8217;s also quite a few things that are residual from phase two, contributors are aiming to get the funds API and the fund library into core, together with the typography management system. We talked about the Interactivity API, there&#8217;s certainly some front fund hydration kind of tools. We&#8217;re still waiting for the table of content block to be stabilized, and the time to read block, is something that is definitely on the list. And I&#8217;m really excited to see what&#8217;s coming as a default theme for 2024. And of course, all the publishing that goes into phase two interfaces and workflows for the site editor. Yeah, the default theme. Yeah.</p>



<p><em>Anne McCarthy</em>: There&#8217;s so much already slated for 6.4.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And then your central…</p>



<p><em>Anne McCarthy</em>: Provisions and templates and template parts, yeah, we could rattle off a bunch of stuff, let&#8217;s leave it.</p>



<p><em>Birgit Pauli-Haack</em>: And we already know there&#8217;s stuff in there, so Beta 1 is September 26th, that&#8217;s just eight weeks away. And that&#8217;s kind of interesting to see how short of a cycle we are going to have, but we won&#8217;t hit US big holidays, like Thanksgiving, it will be out before Thanksgiving, it will be out before Christmas, and nobody goes into a Christmas year-end sale with a changed WordPress. So, I think it&#8217;s a good thing for the community, but it&#8217;s going to be hard to make it a splashy new feature kind of thing, when you only have eight weeks to develop. And it&#8217;s-</p>



<p><em>Anne McCarthy</em>: It&#8217;s tight.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. But then Josepha started a wishlist post. We got quite a few comments there, and it&#8217;s still open until August 15th. She also made clear that it&#8217;s a wishlist, it&#8217;s not everything that&#8217;s going to be on there. It&#8217;s going to come into 6.4, but I think the jury is still out which part will be. If there is already a track ticket or a Gutenberg PR or issue, the chances might be going in, but a global, yeah, this is my wishlist kind of thing, it probably won&#8217;t get that attention. So, August 15th, that&#8217;s just before the community summit and WordCamp US. We will hopefully have, after WordCamp US, have a roadmap post, like you did for 6.3. Are you planning to doing something like that?</p>



<p><em>Anne McCarthy</em>: Yes, I am. It is on my to-do list, I think for the week after, maybe August 14th or something like that, to start compiling stuff and figuring out what we can write up. Because yeah, that is an important thing to get out, especially with a shorter release cycle.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. And it&#8217;s going to be interesting to see, it&#8217;s the underrepresented gender lead release. The last one was 5.6 and now we are 6.4, two years later, three years later. So, there are some awesome people on the release team, so I&#8217;m really looking forward to working with you and so many other, 40 on the direct release team or on the cohort, so it&#8217;s a great group of women/non-binary people working on the release.&nbsp;</p>



<p>So, we are at the end of the show, Anne, it was wonderful to talk to you and you sharing all your knowledge&#8230; Not all your knowledge, we would be here another 10 hours.&nbsp;</p>



<p><em>Anne McCarthy</em>: The highlights.</p>



<p><em>Birgit Pauli-Haack</em>: The highlights of the most immediate thoughts in the show. It was wonderful to have you, is there anything that you want our listeners to be aware of beyond what we talked about today, that we didn&#8217;t touch upon yet?</p>



<p><em>Anne McCarthy</em>: Oh, gosh. No, I don&#8217;t think so. I think the only thing that I&#8217;m noodling on is the next call for testing for the outreach program, and how we can get some feedback and get it going for 6.4, and just how 6.3 lands. So, stay tuned for that, if you&#8217;re not part of the FSE Outreach Program, it is still kicking, it&#8217;s still going over three years on.&nbsp;</p>



<p><em>Birgit Pauli-Haack</em>: That&#8217;s wonderful.</p>



<p><em>Anne McCarthy</em>: Yeah.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah. I really love that, how that turned out. And together, more people involved in testing themes, and no code and code people as well. So, is there a chance that you&#8217;re going to remove the experiment on that particular channel too?</p>



<p><em>Anne McCarthy</em>: Oh, gosh. I know, it&#8217;s so funny, I think it&#8217;s called FSE Outreach Experiment. Yeah, which is funny, because it&#8217;s like, how long can the experiment go for? We&#8217;re on very scientific terms right now, but yeah, no, we should remove it. I think I just referenced it everywhere, as FSE Outreach Experiment, so I&#8217;ve been nervous about getting rid of it.</p>



<p><em>Birgit Pauli-Haack</em>: Oh, okay. Yeah, I can see it.</p>



<p><em>Anne McCarthy</em>: And FSE is also an old term&#8230; It&#8217;s just kind of a weird snapshot in time. But yeah, we&#8217;ll see.</p>



<p><em>Birgit Pauli-Haack</em>: All right, well, it was wonderful to have you. If people want to get in touch with you, would be through the channel FSE Outreach Experiments?</p>



<p><em>Anne McCarthy</em>: Yeah, that&#8217;s probably the easiest. I&#8217;m @annezazu on Make Slack, and then I have a site, <a href="https://nomad.blog/">Nomad.blog</a>. I&#8217;m on LinkedIn, but otherwise, not really typically on any social media. So not on X, or whatever they&#8217;re calling it, the kids are calling it these days. I don&#8217;t know how you even refer to that anymore.</p>



<p><em>Birgit Pauli-Haack</em>: Yeah, it&#8217;s now a Boomers network, right? All right, well, thank you so much for being here, and we are going on holiday, the next recording will be August 25th and we will have Ellen Bauer.</p>



<p><em>Anne McCarthy</em>: Oh, amazing.</p>



<p><em>Birgit Pauli-Haack</em>: &#8230;lead for design, or co-lead, on the design release team for 6.4. And we&#8217;re going to talk about their work on block themes, and of course the next two Gutenberg releases, Gutenberg 16.4 and 16.5. So, stay tuned for the next one. And there&#8217;s always, dear listeners, the show notes will be published on gutenbergtimes.com/podcast, and if you have questions as suggestions or news you want us to cover, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. That&#8217;s <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a>. And that&#8217;s it for me, I wish everybody a great summer, and I will be back end of August. Take care.</p>



<p><em>Anne McCarthy</em>: Amazing. Thank you for having me.</p>



<p><em>Birgit Pauli-Haack</em>: All right, bye-bye.</p>



<p><em>Anne McCarthy</em>: Bye.</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:"Sat, 29 Jul 2023 20:28:20 +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:18:"Birgit Pauli-Haack";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:33;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:76:"Gutenberg Times: Patterns, Block Styles and Slotfills—Weekend Edition #263";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:35:"https://gutenbergtimes.com/?p=25029";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:83:"https://gutenbergtimes.com/patterns-block-styles-and-slotfills-weekend-edition-263/";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:14894:"<p>Howdy, </p>



<p>One more week, and I will start my Summer vacation. It&#8217;ll be a mixture between, pursuing neglected passing projects, giving family support, birthday celebrations and home improvement projects. My husband and I will join my in-laws  (MIL + SIL) on a river-cruise on the Danube and visit new places and revisit familiar places. </p>



<p>The last touches on the WordPress 6.3 release are happening. If you haven&#8217;t yet, check out all the information that&#8217;s out there, and you find in the last two weekend editions. </p>



<p>Yours, 💕<br /><em>Birgit</em></p>






<div class="wp-block-group has-light-background-background-color has-background is-layout-flow wp-block-group-is-layout-flow"><div class="wp-block-group__inner-container">
<p><strong>Table of Contents</strong></p>



<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#0-word-press-release-information">Developing Gutenberg and WordPress</a><ul><li><a href="https://gutenbergtimes.com/feed/#1-word-press-6-3">WordPress 6.3</a></li><li><a href="https://gutenbergtimes.com/feed/#1-gutenberg-16-3">Gutenberg 16.3 </a></li></ul></li><li><a href="https://gutenbergtimes.com/feed/#0-p">Plugins, Themes, and Tools for #nocode site builders and owners</a></li><li><a href="https://gutenbergtimes.com/feed/#2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</a></li><li><a href="https://gutenbergtimes.com/feed/#3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor. </a></li></ul></div>
</div></div>




<h2 class="wp-block-heading" id="0-word-press-release-information">Developing Gutenberg and WordPress</h2>



<h3 class="wp-block-heading" id="1-word-press-6-3">WordPress 6.3</h3>



<p>On the WordPress News site, <strong>Anne McCarthy</strong> published <a href="https://wordpress.org/news/2023/07/synced-patterns-the-evolution-of-reusable-blocks/"><strong>Synced Patterns: The Evolution of Reusable Blocks</strong></a>. You&#8217;ll learn everything there is to know about how the term &#8220;Synced patterns&#8221; is replacing the term &#8220;Reusable blocks&#8221;, and how this brings a unified creation experience for new pattern to your WordPress site with the new version. </p>



<p>Many users have been applying reusable blocks to CTA, bios and compliance copy on their sites. Those will stay intact. Nothing changes here. The same mechanism you used to create reusable blocks, is also used to create synced patterns. It&#8217;s now also expanded to create standard patterns. A feature many site owners and designers have been waiting for. McCarthy and I also talked about this during our podcast recording. </p>



<img />



<hr class="wp-block-separator has-text-color has-accent-color has-alpha-channel-opacity has-accent-background-color has-background is-style-wide gt-separator" />



<p><strong>Matt Medeiros,</strong> publisher of WPMinute, asked in his latest episode: <br /><a href="https://thewpminute.com/will-wordpress-6-3-be-the-best-ever/"><strong>Will WordPress 6.3 be the best ever?</strong></a> &#8220;There are a lot of exciting features coming to WordPress 6.3 which will set the tone for the next few years of our favorite CMS.&#8221; he wrote. </p>



<hr class="wp-block-separator has-text-color has-accent-color has-alpha-channel-opacity has-accent-background-color has-background is-style-wide gt-separator" />



<p><strong>Jonathan Bossenger </strong>provides a recording of his <a href="https://wordpress.tv/2023/07/28/testing-wordpress-6-3-developer-edition/"><strong>Testing WordPress 6.3 – Developer Edition</strong></a> session. You&#8217;ll learn how to install the <a href="https://wordpress.org/plugins/wordpress-beta-tester/"><em>WordPress Beta Tester plugin</em></a>, convert a local installation to 6.3 RC  for testing. Then use this setup to test it against a theme that is in active development, and then revert it back to WordPress 6.2.2. With WordPress 6.3 due on August 8, 2023, now would be a great time to help test the release candidate, as well as confirm that your plugins and themes are ready for the 6.3 release.</p>



<h3 class="wp-block-heading" id="1-gutenberg-16-3">Gutenberg 16.3 </h3>



<p><strong><a href="https://twitter.com/michaelburridge">Michael Burridge</a></strong> led the latest Gutenberg release. It was mainly a maintenance release and comprised of a myriad of bug fixes for features slated for WordPress 6.3. Burridge highlighted in his release post <strong><a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/">What’s new in Gutenberg 16.3? (26 July)</a>&nbsp;</strong></p>



<ul>
<li><a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/#focus-mode-editing-for-patterns">‘Focus mode’ editing for patterns</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/#sticky-header-bar-on-patterns-page">Sticky header bar on Patterns page</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/#rename-duplicate-and-delete-patterns">Rename, duplicate, and delete patterns</a></li>
</ul>



<img />



<hr class="wp-block-separator has-text-color has-accent-color has-alpha-channel-opacity has-accent-background-color has-background is-style-wide gt-separator" />



<div class="wp-block-group has-light-background-background-color has-background is-layout-constrained wp-block-group-is-layout-constrained"><div class="wp-block-group__inner-container">
<div class="wp-block-group has-light-background-background-color has-background is-layout-flow wp-block-group-is-layout-flow"><div class="wp-block-group__inner-container">
<p class="is-style-no-vertical-margin"><strong>🎙️ </strong> Latest episode: <a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-87/">Gutenberg Changelog #87 – Patterns, Gutenberg 16.3 and WordPress 6.3.</a> with Anne McCarthy as special guest, hosted by Birgit Pauli-Haack</p>
</div></div>
</div></div>



<p><strong>Anne McCarthy</strong> and I talked about this release and, of course, also about WordPress 6.3 while recording the <strong>Gutenberg Changelog 87</strong>. It&#8217;s always a great joy to listen to Anne and take a deep dive into the Site editor with her. The episode is still at the editor, but will be available via your favorite podcast app over the weekend. My favorite Podcast app is <a href="https://pocketcasts.com/">Pocket Casts</a> and I have been a paying subscriber for many years.</p>



<img />



<hr class="wp-block-separator has-alpha-channel-opacity" />



<p><strong>Sarah Gooding</strong> reported on the release as well in her article: <a href="https://wptavern.com/gutenberg-16-3-adds-new-tools-for-patterns"><strong>Gutenberg 16.3 Adds New Tools for Patterns</strong></a>. &#8220;Most notably, custom user patterns now have a dropdown menu for renaming, duplicating and deleting them. Patterns and template parts that come with themes will only have the “duplicate” option available since they cannot be deleted or renamed.&#8221; she wrote. </p>




<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2022&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly.  <a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/"><em>The index 2020 is here</em></a></p>




<h2 class="wp-block-heading" id="0-p">Plugins, Themes, and Tools for #nocode site builders and owners</h2>



<p><strong>Jamie Marsland </strong>released a new video with a <a href="https://www.youtube.com/watch?v=ckq0Wfu2xvs"><strong>tons of WordPress News that you probably missed</strong></a> with a demo of the <a href="https://gutenbergtimes.com/introducing-the-breadcrumbs-wordpress-block-plugin/">Justin Tadlock&#8217;s Breadcrumbs Block</a>, the time to read block, and vertical text feature, and finally short appearances from Mike McAlister and Kevin Geary, with strong opinions on block themes specifically and Gutenberg as a whole. </p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p>When users are new to WordPress, taxonomy is one of the concepts, that is harder to explain. <strong>Sarah Snow</strong> published a tutorial: <a href="https://learn.wordpress.org/tutorial/categories-vs-tags-whats-the-difference/"><strong>Categories vs. Tags: What’s the difference?</strong></a> on the Learn.WordPress site. She shows you how to use them and that they are good for SEO juice and enhances content discovery for your readers. And  never have posts &#8220;uncategorized&#8221; again. </p>



<h2 class="wp-block-heading" id="2-word-press-6-0-1-and-6-1-scheduled">Theme Development for Full Site Editing and Blocks</h2>



<p>Last week, <strong>Justin Tadlock</strong> published <a href="https://developer.wordpress.org/news/2023/07/beyond-block-styles-part-1-using-the-wordpress-scripts-package-with-themes/">part 1</a> of his Beyond Block Styles series. In part 2 he walks you through how to build custom styles for the core Separator Block.  <a href="https://developer.wordpress.org/news/2023/07/beyond-block-styles-part-2-building-a-custom-style-for-the-separator-block/"><strong>Beyond block styles, part 2: building a custom style for the Separator block</strong></a>. It&#8217;s a deep dive into the inner workings of creating block styles for core blocks. You would need to have a certain set-up in place to follow along, and Tadlock takes you by the hand on <a href="https://developer.wordpress.org/news/2023/07/beyond-block-styles-part-1-using-the-wordpress-scripts-package-with-themes/">using the WordPress scripts package with themes</a>. I can hardly wait for the third part. I probably see first drafts next week. </p>



<img />



<p class="has-light-background-background-color has-background">Oh, and while I have you: Are you a developer with a topic idea that you would like to share with the community? How about publishing it <strong>WordPress Developer Blog?</strong> Read the&nbsp;<a href="https://developer.wordpress.org/news/tips-and-guidelines-for-writers/">tips and guidelines</a>&nbsp;and find out&nbsp;<a href="https://developer.wordpress.org/news/how-to-contribute/">how you can contribute</a>. Our next monthly meeting will be on August 3rd, 2023 at 13:00 UTC in the WP Slack <a href="https://wordpress.slack.com/archives/C03RL47B3S8">#core-dev-blog</a> channel. Or just DM me on Slack @bph and we&#8217;ll set up a talk. </p>



<p>If you are a novice to working with NodeJS or npm, <strong>Jonathan Bossenger </strong>has a tutorial for you on Learn.WordPress: <a href="https://learn.wordpress.org/tutorial/installing-node-js-and-npm-for-local-wordpress-development/"><strong>Installing Node.js and npm for local WordPress development</strong></a>. </p>



<h2 class="wp-block-heading" id="3-building-themes-for-fse-and-word-press">Building Blocks and Tools for the Block editor. </h2>



<p>In his live coding session on twitch, <strong>Ryan Welcher</strong> covered &#8211;  it seems &#8211; his most favorite topic: <strong><a href="https://www.twitch.tv/videos/1883051136">Using custom SlotFill to extend a codebase</a>,</strong> using is ever evolving Advanced Query Loop plugin and adding more settings to the plugin&#8217;s sidebar. </p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />



<p><strong>Michael Burridge</strong> and <strong>Justin Tadlock </strong>presented at this month&#8217;s <a href="https://wordpress.tv/2023/07/26/wordpress-developer-hours-styling-blocks-july-2023/"><strong>Developer Hours about Styling Blocks.</strong></a> The recording is available on WordPress TV. The panel talked about CSS custom properties (also known as CSS variables). You learn how to leverage them in custom blocks to give users more control over the styling and presentation of their sites.</p>




<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s master branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>



<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge" /></p>




<p class="has-text-align-right has-small-font-size"><em>Questions? Suggestions? Ideas? Don&#8217;t hesitate to send <a href="mailto:pauli@gutenbergtimes.com">them via email</a> or send me a message on WordPress Slack or Twitter @bph</em>. </p>



<p class="has-text-align-right has-small-font-size">For questions to be answered on the <a href="http://gutenbergtimes.com/podcast">Gutenberg Changelog</a>, send them to <a href="mailto:changelog@gutenbergtimes.com">changelog@gutenbergtimes.com</a></p>



<hr class="wp-block-separator has-alpha-channel-opacity is-style-wide" />




<p>Featured Image: <a href="https://creativecommons.org/share-your-work/public-domain/cc0/">CCO</a>&nbsp;licensed&nbsp;<a href="https://wordpress.org/photos/photo/382642d6b2/">photo</a>&nbsp;by&nbsp;<a href="https://wordpress.org/photos/author/lanche86/">lanche86</a>&nbsp;from the&nbsp;<a href="https://wordpress.org/photos/">WordPress Photo Directory</a>.</p>



<hr class="wp-block-separator has-css-opacity is-style-wide" />



<p class="has-text-align-left"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>



<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email"><br />Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button type="submit" class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>



<hr class="wp-block-separator has-css-opacity is-style-wide" />";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:"Sat, 29 Jul 2023 09:34:30 +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:18:"Birgit Pauli-Haack";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:34;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:92:"WPTavern: Ninja Forms Version 3.6.26 Patches Multiple High Severity Security Vulnerabilities";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:30:"https://wptavern.com/?p=147292";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:103:"https://wptavern.com/ninja-forms-version-3-6-26-patches-multiple-high-severity-security-vulnerabilities";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:1893:"<p>If you use the <a href="https://wordpress.org/plugins/ninja-forms">Ninja Forms</a> plugin and your sites aren&#8217;t set to get automatic plugin updates, add a round of updates to your weekend plans. Patchstack is <a href="https://patchstack.com/articles/multiple-high-severity-vulnerabilities-in-ninja-forms-plugin/">reporting multiple high severity security vulnerabilities</a> in the plugin, including the following:</p>



<ul>
<li>a POST-based reflected XSS (7.6 CVSS 3.1 score)</li>



<li>a broken access control on form submissions export feature that allows Subscriber and Contributor role users to export all of the Ninja Forms submissions on a WordPress site (7.6 CVSS 3.1 score)</li>
</ul>



<p>Patchstack researchers discovered the vulnerabilities on June 22, 2023, and Ninja Forms patched them on July 4, 2023. The security advisory was publicly released on July 27, 2023. </p>



<p>The plugin&#8217;s changelog for version 3.6.26 transparently identifies the security fixes included in the release:</p>



<blockquote class="wp-block-quote">
<p><em>Security Enhancements:</em><br />* Prevent unauthorized download of submission<br />* Prevent scripts in dashboard field labels; responsibly reported by Sayandeep Dutta<br />* Prevent front-facing label scripts; responsibly reported by Jonathon Zamora &amp; WordPress.org<br />* Prevent excess extra data through automated form submission<br />* Prevent override access where not permitted</p>
</blockquote>



<p>Ninja Forms is used on more than 800,000 WordPress sites. The majority of the plugin&#8217;s users are on version 3.6.x (73.6%) but WordPress.org doesn&#8217;t offer a more detailed breakdown of minor versions, so it&#8217;s not clear how many are still vulnerable. Ninja Forms users are recommended to patch their sites immediately. At this time, the vulnerabilities are not known to have been exploited.</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:"Fri, 28 Jul 2023 22:11:38 +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:13:"Sarah Gooding";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:35;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:48:"WPTavern: WordPress Launches Slack/Matrix Bridge";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:30:"https://wptavern.com/?p=147271";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:59:"https://wptavern.com/wordpress-launches-slack-matrix-bridge";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:3419:"<p>WordPress meta contributors have just logged an important milestone in their efforts to <a href="https://wptavern.com/wordpress-project-to-evaluate-replacing-slack-with-matrix-open-source-chat">explore replacing Slack communication with Matrix</a>, an open source federated chat system. The team hosted a meeting on the Meta Slack channel and the corresponding #meta:community.wordpress.org Matrix room simultaneously, enabled by the project&#8217;s <a href="https://make.wordpress.org/meta/2023/07/20/matrix-chat-summary-july-20-2023/">new Slack/Matrix bridge</a>.</p>



<p>The bridge allows users to follow the chat and participate from either Matrix or Slack, with messages showing up in real-time. It&#8217;s a tool that will make the transition easier as the WordPress project moves towards replacing Slack. The team is still in the process of importing the history for channels but the bridges are already in place for all public Slack channels/Matrix rooms. </p>



<p>DM&#8217;s do not work over the bridge, although they work between Matrix users. The bridge doesn&#8217;t have access to anything that is private, and the historic data import into Matrix will only apply to public Slack channels. DMs and private channel history will not be ported over.</p>



<div class="wp-block-spacer"></div>



<img width="1213" height="996" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/07/make-meta-chatrix.png" alt="" class="wp-image-147278" />Meta contributor meeting inside Chatrix instance with room switcher disabled 



<p>The Matrix team has created a Gutenberg block that embeds a Matrix client called <a href="https://wordpress.org/plugins/chatrix/">Chatrix</a>, which can be added to any WordPress page/post or P2 blog, as shown in the screenshot above. This example can be accessed at <a href="https://make.wordpress.org/meta/chat/">https://make.wordpress.org/meta/chat/</a>. WordPress.org users can sign in with SSO inside the block and authorize their accounts to connect:</p>



<img width="465" height="500" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/07/Screen-Shot-2023-07-28-at-3.03.35-PM-465x500.png" alt="" class="wp-image-147279" />



<p>Now that the Matrix server is live at <a rel="noreferrer noopener" href="https://community.wordpress.org/" target="_blank">community.wordpress.org</a>, WordPress users who want to attend team meetings or join rooms via Matrix can now do so using their choice of Matrix clients that support SSO. Logging in uses the same credentials as the WordPress.org account.</p>



<p>&#8220;Compared to Slack this means a vastly simplified onboarding process,&#8221; Automattic-sponsored contributor Alex Kirk said. &#8220;Instead of waiting for an e-mail arriving at a special e-mail address, you set the server in your Matrix client to <code>community.wordpress.org</code> and click &#8216;Login with WordPress.org&#8217; (the name of that button might vary by client).&#8221;</p>



<p>As the channels&#8217; history gets migrated over, Kirk said WordPress users will be automatically invited to rooms on Matrix that they have already joined from the Slack side. The team is planning to make more wide-scale public announcements after the Slack/Matrix bridge has demonstrated that it is running stable.</p>



<p><a target="_blank" rel="noreferrer noopener" href="https://app.slack.com/services/B05A8FX9LBD"></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:"Fri, 28 Jul 2023 21:31:35 +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:13:"Sarah Gooding";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:36;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:25:"Matt: Ottawa Can Bring It";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:22:"https://ma.tt/?p=92586";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:42:"https://ma.tt/2023/07/ottawa-can-bring-it/";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:470:"<p>Ottawa reminds me a lot of Houston. A city that is a microcosm of Canada&#8217;s diversity and vibrance.</p>



<p>When you visit Ottawa, I&#8217;d recommend checking out <a href="https://aiana.ca/">Aiana Restaurant Collective</a> (powered by WordPress, natch!) and <a href="https://www.stolengoodscocktailbar.com/">Stolen Goods Cocktail Bar</a> to see craftspeople operating at the top of their game. <a href="https://dineriviera.com/">Riviera</a> was also nice.</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:"Fri, 28 Jul 2023 02:52:40 +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:4:"Matt";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:37;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:89:"WPTavern: ClassicPress Community Considers Re-forking WooCommerce for Classic Commerce v2";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:30:"https://wptavern.com/?p=147238";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:100:"https://wptavern.com/classicpress-community-considers-re-forking-woocommerce-for-classic-commerce-v2";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:4802:"<p><a href="https://www.classicpress.net/">ClassicPress</a>, the fork that has been keeping WordPress 4.9 on life support for those who don&#8217;t want to use the block editor, will soon be moving into version 2.0 after the community <a href="https://wptavern.com/classicpress-community-votes-to-re-fork-wordpress">voted to re-fork a newer version of WordPress</a> (6.x) to keep moving forward. <a href="https://www.classicpress.net/classicpress-v1-6-0-is-out/">Version 1.6.0</a> was released a few weeks ago as the last minor release before version 2.0.</p>



<p>ClassicPress contributors are <a href="https://forums.classicpress.net/t/classiccommerce-v2/4860">discussing the future of Classic Commerce</a>, which is a <a href="https://classiccommerce.cc/">fork of WooCommerce 3.5.3</a> created to provide a reliable e-commerce solution for ClassicPress users. The community is now bracing for the inevitable compatibility issues introduced by version 2.0 that will require a massive undertaking to resolve. </p>



<p>In a forum thread seeking community input, @shimmy, an IT solutions business owner with an interest in supporting a long term e-commerce solution, proposed the following options for Classic Commerce&#8217;s future: </p>



<ul>
<li>Re-Fork Woo-Current</li>



<li>Re-Fork Woo-Previous</li>



<li>Fork a different eCommerce solution</li>



<li>Migrate CCv1 to current</li>



<li>Complete Rewrite</li>
</ul>



<p>&#8220;We can talk about re-forking, using something that works or asking ourselves: are we ready to really fork and support it on our own developing it in a way it works in ClassicPress or do we fork it and continue to patch it every time it doesn’t work because blocks or just keep it frozen?&#8221; Elisabetta Carrara said.</p>



<p>After some discussion multiple participants in the conversation were in agreement that forking the latest version of WooCommerce to make it work with ClassicPress is not a viable option.</p>



<p>ClassicPress director Viktor Nagornyy suggested exploring a refork similar to the method used for ClassicPress 2.0.</p>



<p>&#8220;With CP v2.0, we didn’t take WP v6.2 and rip out blocks, FSE, and React,&#8221; he said. &#8220;<a href="https://forums.classicpress.net/u/mattyrob">@MattyRob</a> merged <code>develop</code> branch with CP v1, and worked his way through all the files to resolve merge conflicts. That was a lot of work, and he did a great job. WooCommerce and Classic Commerce are plugins, so I assume they have fewer files than WP/CP core.</p>



<p>&#8220;This type of &#8216;merge-fork&#8217; could be a viable option for CC to save time and effort.&#8221; </p>



<p>@shimmy, who would be leading this effort, said he is leaning toward this approach.</p>



<p>&#8220;I think this provides a more natural upgrade path and to some degree backwards compatibility,&#8221; he said. &#8220;At some point in the course of merge-fork WC plugins will no longer be compatible with CC; which is fine because I think that CC should have it’s own plugin &#8216;bazaar.&#8217; This ensures compatibility with CC; if you need a feature then it should be a filtered result with what you already have in place.&#8221;</p>



<p>Nagornyy also encouraged a nascent plugin ecosystem to grow up around these forks to provide additional features. Although the WooCommerce plugin ecosystem has thousands of options for extending stores, they are not guaranteed to be compatible with forks built on older versions of WordPress and WooCommerce.</p>



<p>&#8220;While the core CC is free, I encourage plugin developers to consider developing paid plugins for CC to ensure they get paid for their time and effort,&#8221;  Nagornyy said. &#8220;It only strengthens CP and CC knowing premium, supported plugins are available. For e-commerce, the two profitable (and critically important) categories of plugins are payment gateways and shipping integrations.&#8221;</p>



<p>With the major <a href="https://wptavern.com/wordpress-plans-ambitious-admin-ui-revamp-with-design-system-galvanizing-broad-support-from-the-developer-community">changes coming to the WordPress admin in Phase 3</a> of the Gutenberg project, maintaining these forks will continue to be an uphill slog, as fewer plugins from the wider ecosystem will remain compatible with ClassicPress. </p>



<p>Maintaining payment gateways and shipping integrations for compatibility with these forks is also going to be challenging, as this discussion indicates that the community doesn&#8217;t have many experienced e-commerce developers who are eager to step up and donate their time to this project.  If Classic Commerce cannot deliver on the ambitious &#8216;merge-fork&#8217; option, users may need to look towards integrating external e-commerce solutions. </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:"Thu, 27 Jul 2023 22:16:18 +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:13:"Sarah Gooding";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:38;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:"Post Status: WordPress 6.3 RC2 • Synced Patterns • Internationalization • Gutenberg Phase 3";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://poststatus.com/?p=150017";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:96:"https://poststatus.com/wordpress-6-3-rc2-synced-patterns-internationalization-gutenberg-phase-3/";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:25140:"<h2 class="wp-block-heading" id="h-this-week-at-wordpress-org-april-3-2023">This Week at WordPress.org (July 25, 2023)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">We&#8217;re under two weeks away from WordPress 6.3 release. Have you started testing? <br /><br />Big changes are envisioned for the Media Library, Admin Dashboard, and more. You have an opportunity NOW to share ideas. What considerations do we need to account for? Read the Phase 3 post from Matías and share your feedback in the comments. <br /><br />No longer will you find Reusable Blocks. In WordPress 6.3, you&#8217;ll now find Synched Patterns. Read on to learn why the name has been changed. </p></div>


<div class="wp-block-spacer"></div>



<div class="wp-block-kadence-infobox kt-info-box_94d1bd-77"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kb-svg-icon-wrap kb-svg-icon-fe_gitMerge kt-info-svg-icon"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title"> WP 6.3, Reusable Blocks, Phase 3, i18N</h2><p class="kt-blocks-info-box-text"><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f680.png" alt="🚀" class="wp-smiley" /> <a href="https://wordpress.org/news/2023/07/wordpress-6-3-release-candidate-2/">WordPress 6.3 Release Candidate 2</a><br /><br />3&#x20e3; <a href="https://make.wordpress.org/core/tag/phase-3/">Gutenberg Phase 3</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f310.png" alt="🌐" class="wp-smiley" /> <a href="https://make.wordpress.org/core/2023/07/24/i18n-performance-analysis/">I18N Performance Analysis</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f501.png" alt="🔁" class="wp-smiley" /> <a href="https://wordpress.org/news/2023/07/synced-patterns-the-evolution-of-reusable-blocks/">Synced Patterns: The Evolution of Reusable Blocks</a></p></div></div></div>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_b57166-6e"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<h2 class="wp-block-heading" id="h-news"><a href="https://wordpress.org/news">News</a></h2>



<ul>
<li><a href="https://wordpress.org/news/2023/07/synced-patterns-the-evolution-of-reusable-blocks/">Synced Patterns: The Evolution of Reusable Blocks</a></li>



<li><a href="https://wordpress.org/news/2023/07/wordpress-6-3-release-candidate-2/">WordPress 6.3 Release Candidate 2</a></li>



<li><a href="https://wordpress.org/news/2023/07/wordpress-6-3-live-product-demo-highlights-recording/">WordPress 6.3 Live Product Demo – Highlights &amp; Recording</a></li>
</ul>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_8f6276-eb"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<div class="wp-block-columns is-layout-flex wp-container-22">
<div class="wp-block-column is-layout-flow">
<h2 class="wp-block-heading">WordPress 6.3</h2>



<ul>
<li><a href="https://make.wordpress.org/polyglots/2023/07/18/wordpress-6-3-ready-to-be-translated/">WordPress 6.3 ready to be translated</a></li>



<li><a href="https://wordpress.org/news/2023/07/wordpress-6-3-release-candidate-2/">WordPress 6.3 Release Candidate 2</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/19/wordpress-6-3-accessibility-improvements/">WordPress 6.3 Accessibility Improvements</a></li>



<li><a href="https://wordpress.org/news/2023/07/wordpress-6-3-release-candidate-1/">WordPress 6.3 Release Candidate 1</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/19/wordpress-6-2-release-candidate-phase-2/">WordPress 6.3 Release Candidate Phase</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/13/improvements-to-the-metadata-api-in-wordpress-6-3/">Improvements to the metadata API in WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/06/30/6-3-release-parties-schedule-and-hosts/">6.3 Release Parties Schedule and hosts</a></li>



<li><a href="https://wordpress.org/news/2023/06/wordpress-6-3-beta-2/">WordPress 6.3 Beta 2</a></li>



<li><a href="https://make.wordpress.org/design/2023/05/25/wordpress-6-3-design-kickoff/">WordPress 6.3 design kickoff</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/25/bug-scrub-schedule-for-6-3/">Bug Scrub Schedule for WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/18/wordpress-6-3-planning-roundup/">WordPress 6.3 Planning Roundup</a></li>



<li><a href="https://make.wordpress.org/core/2023/05/18/roadmap-to-6-3/">Roadmap to 6.3</a></li>
</ul>



<h2 class="wp-block-heading">WordPress 6.4</h2>



<ul>
<li><a href="https://make.wordpress.org/core/2023/07/18/wordpress-6-4-whats-on-your-wishlist/">WordPress 6.4: What’s on your wishlist?</a></li>



<li><a href="https://make.wordpress.org/core/2023/06/05/wordpress-6-4-development-cycle/">WordPress 6.4 Development Cycle</a></li>
</ul>
</div>



<div class="wp-block-column is-layout-flow">
<h3 class="wp-block-heading">WordPress 6.3 Field Guide and Dev-Notes</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/07/18/wordpress-6-3-field-guide/">WordPress 6.3 Field Guide</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/17/introducing-the-block-selectors-api/">Introducing the Block Selectors API</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/17/introducing-the-wordpress-command-palette-api/">Introducing the WordPress Command Palette API</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/14/layout-updates-in-the-editor-for-wordpress-6-3/">Layout updates in the editor for WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/17/social-icons-block-applied-colors-now-dynamically-update-based-on-theme-json-and-global-styles/">Social Icons block: Applied colors now dynamically update based on theme.json and Global Styles</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/18/miscellaneous-editor-changes-in-wordpress-6-3/">Miscellaneous Editor changes in WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/18/bundled-themes-dropping-internet-explorer-scripts-and-styles/">Bundled themes dropping Internet Explorer scripts and styles</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/17/improvements-to-the-cache-api-in-wordpress-6-3/">Improvements to the Cache API in WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/14/configuring-development-mode-in-6-3/">Configuring development mode in 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/14/i18n-improvements-in-6-3/">I18N Improvements in 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/13/image-performance-enhancements-in-wordpress-6-3/">Image performance enhancements in WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/13/improvements-to-the-metadata-api-in-wordpress-6-3/">Improvements to the metadata API in WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/14/wp_query-used-internally-in-get_pages/">WP_Query used internally in get_pages()</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/14/registering-scripts-with-async-and-defer-attributes-in-wordpress-6-3/">Registering scripts with `async` and `defer` attributes in WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/11/new-in-6-3-rollback-for-failed-manual-plugin-and-theme-updates/">New in 6.3: Rollback for failed manual plugin and theme updates</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/14/improved-caching-for-database-queries-in-wp_user_query/">Improved Caching for Database Queries in WP_User_Query</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/18/miscellaneous-developer-changes-in-wordpress-6-3/">Miscellaneous developer changes in WordPress 6.3</a></li>
</ul>
</div>
</div>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<div class="wp-block-columns is-layout-flex wp-container-27">
<div class="wp-block-column is-layout-flow">
<div class="wp-block-columns is-layout-flex wp-container-25">
<div class="wp-block-column is-layout-flow">
<h2 class="wp-block-heading" id="h-community"><a href="https://make.wordpress.org/community">Community</a></h2>



<ul>
<li><a href="https://make.wordpress.org/community/2023/07/13/recap-of-the-diverse-speaker-training-group-wpdiversity-amer-emea-on-july-12-2023/">Recap of the Diverse Speaker Training group (#WPDiversity) AMER/EMEA on July 12, 2023</a></li>



<li><a href="https://make.wordpress.org/community/2023/07/13/new-handbook-page-for-wordcamp-organizers-wordcamp-speaker-selection-for-content-and-diversity/">New handbook page for WordCamp Organizers: WordCamp Speaker Selection (for content AND diversity)</a></li>



<li><a href="https://make.wordpress.org/community/2023/07/12/summary-of-the-q2-community-team-role-updates/">Summary of the Q2 Community Team Role Updates</a></li>
</ul>



<h2 class="wp-block-heading" id="h-core"><a href="https://make.wordpress.org/core">Core</a> </h2>



<ul>
<li><a href="https://make.wordpress.org/core/2023/07/25/a-week-in-core-july-24-2023/">A Week in Core – July 24, 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/">What’s new in Gutenberg 16.3? (26 July)</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/24/i18n-performance-analysis/">I18N Performance Analysis</a></li>
</ul>



<h3 class="wp-block-heading">Phase 3 Ideations</h3>



<ul>
<li><a target="_blank" href="https://make.wordpress.org/core/2023/07/03/real-time-collaboration/" rel="noreferrer noopener">Real-Time Collaboration</a></li>



<li><a target="_blank" href="https://make.wordpress.org/core/2023/07/04/workflows/" rel="noreferrer noopener">Workflows</a></li>



<li><a target="_blank" href="https://make.wordpress.org/core/2023/07/05/revisions/" rel="noreferrer noopener">Revisions</a></li>



<li><a target="_blank" href="https://make.wordpress.org/core/2023/07/07/media-library/" rel="noreferrer noopener">Media Library</a></li>



<li><a target="_blank" href="https://make.wordpress.org/core/2023/07/10/block-library/" rel="noreferrer noopener">Block Library</a></li>



<li><a target="_blank" href="https://make.wordpress.org/core/2023/07/12/admin-design/" rel="noreferrer noopener">Admin Design</a></li>
</ul>



<h3 class="wp-block-heading" id="h-developer-blog"><a href="https://developer.wordpress.org/news/">Developer Blog</a></h3>



<ul>
<li><a href="https://developer.wordpress.org/news/2023/07/beyond-block-styles-part-1-using-the-wordpress-scripts-package-with-themes/">Beyond block styles, part 1: using the WordPress scripts package with themes</a></li>



<li><a href="https://developer.wordpress.org/news/2023/07/make-your-sites-typography-make-a-statement/">Make your site’s typography make a statement</a></li>



<li><a href="https://developer.wordpress.org/news/2023/07/whats-new-for-developers-july-2023/">What’s new for developers? (July 2023)</a></li>



<li><a href="https://developer.wordpress.org/news/2023/07/how-to-modify-theme-json-data-using-server-side-filters/">How to modify theme.json data using server-side filters</a></li>
</ul>



<h3 class="wp-block-heading" id="h-meetings">Meetings</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2023/07/26/core-editor-chat-summary-26th-july-2023/">Core Editor chat summary: 26th July 2023</a></li>



<li><a href="https://make.wordpress.org/core/2023/07/25/dev-chat-agenda-july-26-2023/">Dev Chat agenda, July 26, 2023</a></li>
</ul>



<h2 class="wp-block-heading"><a href="https://make.wordpress.org/docs">Docs</a></h2>



<ul>
<li><a href="https://make.wordpress.org/docs/2023/07/24/online-monthly-docs-team-contributor-day-july-25-2023/">Online monthly Docs Team Contributor Day July 25, 2023</a></li>



<li><a href="https://make.wordpress.org/docs/2023/07/18/call-for-volunteers-to-help-with-6-3-end-user-documentation/">Call for volunteers to help with 6.3 end-user documentation</a></li>



<li><a href="https://make.wordpress.org/updates/2023/07/24/documentation-team-update-july-24-2023/">Documentation Team Update – July 24, 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-hosting"><a href="https://make.wordpress.org/hosting">Hosting</a></h2>



<ul>
<li><a href="https://make.wordpress.org/hosting/2023/07/26/hosting-team-meeting-agenda-2023-07-26/">Hosting Team meeting agenda 2023-07-26</a></li>



<li><a href="https://make.wordpress.org/hosting/2023/07/26/wordpress-hosting-survey/">WordPress Hosting Survey</a></li>
</ul>



<h2 class="wp-block-heading"><a href="https://make.wordpress.org/meta">Meta</a></h2>



<ul>
<li><a href="https://make.wordpress.org/meta/2023/07/20/matrix-chat-summary-july-20-2023/">Matrix chat Summary – July 20, 2023</a></li>



<li><a href="https://make.wordpress.org/meta/2023/06/20/make-team-dashboards/">Make Team Dashboards</a></li>



<li><a href="https://make.wordpress.org/meta/2023/06/15/triaging-open-issues-on-trac-for-make-teams/">Triaging open issues on Trac for Make Teams</a></li>



<li><a href="https://make.wordpress.org/meta/2023/06/11/linking-to-supporting-orgs/">Linking to Supporting Orgs</a></li>
</ul>



<h2 class="wp-block-heading" id="h-mobile"><a href="https://make.wordpress.org/mobile">Mobile</a></h2>



<ul>
<li><a href="https://make.wordpress.org/updates/2023/07/26/mobile-team-update-july-25th/">Mobile Team Update – July 25th</a></li>
</ul>



<h2 class="wp-block-heading" id="h-openverse"><a href="https://make.wordpress.org/openverse">Openverse</a></h2>



<ul>
<li><a href="https://make.wordpress.org/openverse/2023/07/25/community-meeting-recap-2023-07-25/">Community Meeting Recap (2023-07-25)</a></li>



<li><a href="https://make.wordpress.org/openverse/2023/07/24/last-week-openverse-2023-07-17-2023-07-24/">A week in Openverse: 2023-07-17 – 2023-07-24</a></li>
</ul>



<h2 class="wp-block-heading" id="h-performance"><a href="https://make.wordpress.org/performance/">Performance</a></h2>



<ul>
<li><a href="https://make.wordpress.org/core/2023/07/25/performance-chat-summary-25-july-2023/">Performance Chat Summary: 25 July 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-plugins"><a href="https://make.wordpress.org/plugins">Plugins</a></h2>



<ul>
<li><a href="https://make.wordpress.org/plugins/2023/07/24/tackling-team-challenges-together/">Tackling team challenges together</a></li>



<li><a href="https://make.wordpress.org/plugins/2023/06/29/plugin-review-team-update-the-next-phase-begins/">Plugin Review Team Update: The next phase begins</a></li>



<li><a href="https://make.wordpress.org/updates/2023/07/24/plugin-review-team-24-jul-2023/">Plugin Review Team: 24 Jul 2023</a></li>
</ul>
</div>



<div class="wp-block-column is-layout-flow">
<h2 class="wp-block-heading" id="h-polyglots"><a href="https://make.wordpress.org/polyglots">Polyglots</a></h2>



<ul>
<li><a href="https://make.wordpress.org/polyglots/2023/07/26/agenda-weekly-polyglots-chat-july-26-2023-0700-utc/">Agenda: Weekly Polyglots Chat – July 26, 2023 (07:00 UTC)</a></li>



<li><a href="https://make.wordpress.org/polyglots/2023/07/18/wordpress-6-3-ready-to-be-translated/">WordPress 6.3 ready to be translated</a></li>
</ul>



<h2 class="wp-block-heading" id="h-project">Project</h2>



<ul>
<li><a href="https://make.wordpress.org/project/2023/07/13/proposal-for-establishing-a-make-diversity-equity-inclusion-and-belonging-deib-team-within-the-wordpress-community/">Proposal for Establishing a Make Diversity, Equity, Inclusion, and Belonging (“DEIB”) Team within the WordPress Community</a></li>
</ul>



<h2 class="wp-block-heading">Support</h2>



<ul>
<li><a href="https://make.wordpress.org/support/2023/07/wp-contributor-mentorship-program-support-team-onboarding-meeting/">WP Contributor Mentorship Program: Support Team Onboarding Meeting</a></li>



<li><a href="https://make.wordpress.org/support/2023/07/agenda-for-july-27th-support-meeting-2/">Agenda for July 27th Support Meeting</a></li>
</ul>



<h2 class="wp-block-heading"><a href="https://make.wordpress.org/sustainability">Sustainability</a></h2>



<ul>
<li><a href="https://make.wordpress.org/sustainability/2023/07/27/sustainability-chat-agenda-july-28-2023/">Sustainability Chat Agenda, July 28, 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-test"><a href="https://make.wordpress.org/test">Test</a></h2>



<ul>
<li><a href="https://make.wordpress.org/test/2023/06/27/help-test-wordpress-6-3/">Help Test WordPress 6.3</a></li>



<li><a href="https://make.wordpress.org/updates/2023/07/24/test-team-update-24-july-2023/">Test Team Update: 24 July 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-theme"><a href="https://make.wordpress.org/theme">Theme</a></h2>



<ul>
<li><a href="https://make.wordpress.org/themes/2023/07/26/themes-team-meeting-notes-july-25-2023/">Themes Team Meeting Notes – July 25, 2023</a></li>



<li><a href="https://make.wordpress.org/updates/2023/07/25/themes-team-update-july-25-2023/">Themes team update July 25, 2023</a></li>
</ul>



<h2 class="wp-block-heading" id="h-training"><a href="https://make.wordpress.org/training">Training</a></h2>



<ul>
<li><a href="https://make.wordpress.org/training/2023/07/26/training-team-meeting-recap-25th-july-2023/">Training Team Meeting Recap – 25th July 2023</a></li>



<li><a href="https://make.wordpress.org/training/2023/07/25/call-for-volunteers-to-help-with-6-3-learn-wordpress-updates/">Call for Volunteers to help with 6.3 Learn WordPress updates</a></li>
</ul>



<h3 class="wp-block-heading" id="h-tutorials"><a href="https://learn.wordpress.org/tutorials">Tutorials</a></h3>



<ul>
<li><a href="https://learn.wordpress.org/tutorial/improving-website-performance-with-caching/">Improving website performance with caching</a></li>



<li><a href="https://learn.wordpress.org/tutorial/installing-node-js-and-npm-for-local-wordpress-development/">Installing Node.js and npm for local WordPress development</a></li>
</ul>



<h3 class="wp-block-heading" id="h-online-workshops">Online Workshops</h3>



<ul>
<li><a href="https://learn.wordpress.org/?meeting=apac-exploring-some-of-the-new-6-3-wordpress-features">APAC: Exploring some of the new 6.3 WordPress features</a></li>



<li><a href="https://learn.wordpress.org/?meeting=exploring-some-of-the-new-6-3-wordpress-features">Exploring some of the new 6.3 WordPress features</a></li>



<li><a href="https://learn.wordpress.org/?meeting=onboarding-to-test-team">Onboarding to Test Team</a></li>



<li><a href="https://learn.wordpress.org/?meeting=testing-wordpress-6-3-developer-edition">Testing WordPress 6.3 – Developer edition</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-to-validate-content-feedback-for-the-wordpress-training-team-3">How to validate content feedback for the WordPress Training Team</a></li>



<li><a href="https://learn.wordpress.org/?meeting=how-to-validate-content-feedback-for-the-wordpress-training-team-2">How to validate content feedback for the WordPress Training Team</a></li>



<li><a href="https://learn.wordpress.org/?meeting=mentorship-program-introduction-to-the-wordpress-open-source-project">Mentorship Program: Introduction to the WordPress Open Source Project</a></li>



<li><a href="https://learn.wordpress.org/?meeting=what-is-the-domain-name-system-4">What is the Domain Name System?</a></li>



<li><a href="https://learn.wordpress.org/?meeting=what-is-the-domain-name-system-3">What is the Domain Name System?</a></li>
</ul>



<h3 class="wp-block-heading" id="h-courses"><a href="https://learn.wordpress.org/courses">Courses</a></h3>



<ul>
<li><a href="https://learn.wordpress.org/course/developing-with-the-wordpress-rest-api/">Introduction to developing with the WordPress REST API</a></li>
</ul>



<h2 class="wp-block-heading"><a href="https://make.wordpress.org/tv">WordPress TV</a></h2>



<ul>
<li><a href="https://make.wordpress.org/tv/2023/06/15/enhancing-slide-management-for-video-publications/">Enhancing Slide Management for Video Publications</a></li>
</ul>



<h2 class="wp-block-heading">WordCamp Central</h2>



<ul>
<li><a href="https://central.wordcamp.org/news/2023/07/wordcamp-malaysia-2023-is-looking-for-speakers-and-sponsors/">WordCamp Malaysia 2023 is Looking for Speakers and Sponsors</a></li>



<li><a href="https://central.wordcamp.org/news/2023/07/wordcamp-masaka-2023-celebrating-inclusion-diversity-and-innovation-with-wordpress-in-ugandas-pearl-of-africa/">WordCamp Masaka 2023: Celebrating Inclusion, Diversity, and Innovation with WordPress in Uganda’s Pearl of Africa!</a></li>
</ul>



<h2 class="wp-block-heading" id="h-wptv">WPTV</h2>



<ul>
<li><a href="https://wordpress.tv/category/year/2022/">Latest WordPress TV videos</a></li>
</ul>
</div>
</div>
</div>
</div>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 class="wp-block-heading" id="h-related-news">Related News:</h2>



<ul>
<li><a href="https://blog.jquery.com/2023/05/11/jquery-3-7-0-released-staying-in-order/">jQuery 3.7.0</a></li>



<li><a href="https://nodejs.org/en/blog/release/v20.2.0">Node v20.2.0 released</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-07-06-1">PHP 8.3.0 Alpha 3 available for testing</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-05-11-1"></a><a href="https://www.php.net/archive/2023.php#2023-07-06-2">PHP 8.2.8 Released!</a></li>



<li><a href="https://www.php.net/archive/2023.php#2023-07-06-3">PHP 8.1.21 Released!</a></li>



<li><a href="https://github.com/PHPMailer/PHPMailer/releases/tag/v6.8.0">PHPMailer 6.8.0</a></li>



<li><a href="https://262.ecma-international.org/">TC39</a></li>



<li><a href="http://github.com/composer/composer/releases/tag/2.5.8">Composer 2.5.8</a></li>
</ul>



<p class="has-theme-palette-7-background-color has-background">Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status&#8217; <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It&#8217;s also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



<div class="wp-block-spacer"></div>



<div class="wp-block-media-text alignwide is-stacked-on-mobile has-background"><a href="https://poststatus.com/"><img src="https://poststatus.com/wp-content/uploads/2021/09/vertical-post-status-logo-250.png" alt="Post Status" class="wp-image-85823 size-full" /></a><div class="wp-block-media-text__content">
<p class="has-text-align-left has-normal-font-size" id="h-get-ready-for-remote-work">You — and <a href="https://poststatus.com/#Agency">your whole team</a> can <a href="https://poststatus.com/#choose-membership">Join Post Status</a> too!</p>



<p class="has-text-align-left has-small-font-size"><strong>Build your network. Learn with others. Find your next job — or your next hire.</strong> Read the <strong>Post Status</strong> <a href="https://poststatus.com/newsletter/">newsletter</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2709.png" alt="✉" class="wp-smiley" /> Listen to <a href="https://poststatus.com/podcasts/">podcasts</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /> Follow <a href="https://twitter.com/post_status/">@Post_Status</a> <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /> and <a href="https://www.linkedin.com/company/post-status-llc/">LinkedIn</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4bc.png" alt="💼" class="wp-smiley" /></p>
</div></div>



<div class="wp-block-spacer"></div>
<p>This article was published at Post Status — the community for WordPress professionals.</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:"Thu, 27 Jul 2023 22:03:25 +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:18:"Courtney Robertson";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:39;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:69:"WordPress.org blog: Synced Patterns: The Evolution of Reusable Blocks";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:35:"https://wordpress.org/news/?p=15541";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:84:"https://wordpress.org/news/2023/07/synced-patterns-the-evolution-of-reusable-blocks/";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:4355:"<p>Synced patterns are replacing Reusable blocks, offering a unified creation experience for new pattern functionality coming to WordPress 6.3. Patterns, first introduced in WordPress 5.5, are a collection of blocks that make it simple to add complex layouts and designs to any WordPress site without starting from scratch. With WordPress 6.3, set to be released on August 8th, you will be able to arrange blocks in unlimited ways and save them as patterns for use throughout your site, directly within the editing experience. You can also specify whether to sync your patterns, so that one change applies to all parts of your site, or to keep them unsynced, so you can customize each instance.</p>



<div class="wp-block-embed__wrapper">

</div>



<h2 class="wp-block-heading">Create your own patterns</h2>



<p>The ability to create your own patterns, on top of using the ones bundled into each WordPress release, opens up a world of possibilities. Need to repeat the same contact information across your site and keep it up to date? Create a synced pattern with all the details, and say goodbye to repeating yourself, with the ability to quickly insert the synced pattern wherever you need it. If you find yourself creating various banners for your site and want them to have the same layout with unique content, creating an unsynced pattern speeds up your workflow and ensures a level of consistency in approach. While themes and plugins have been able to offer patterns to users and <a href="https://developer.wordpress.org/block-editor/how-to-guides/curating-the-editor-experience/#utilizing-patterns">curate the experience</a>, this update allows agencies and site builders to do the same for their clients, directly in the site building process.</p>



<h2 class="wp-block-heading">Dig into the details</h2>



<p>Any previously made Reusable blocks will continue to function as they do now, just under the new Synced pattern name. To help adjust to these changes, a few contextual notices will be placed throughout the interface. Specifically, the menu item in the creation flow will show as “Create pattern/reusable block” until the prompt describing the switch is dismissed in one of the various locations, including the naming and syncing modal:&nbsp;</p>



<div class="wp-block-embed__wrapper">

</div>



<p>For folks using block themes, all patterns will be listed alongside template parts in the Site Editor &gt; Patterns section, where you can enter a focused editing mode to make changes. For Classic themes, the prior reusable block management page will now house patterns in a list, similar to the Posts &gt; All Posts view.</p>



<img width="1024" height="590" src="https://i0.wp.com/wordpress.org/news/files/2023/07/Site-Editor-_-All-Patterns-View.png?resize=1024%2C590&ssl=1" alt="Patterns section of the WordPress Site Editor with My Patterns selected" class="wp-image-15569" />



<p>For a complete overview of patterns on your site, all patterns provided by themes and plugins will be shown in this section but without the option to edit directly.</p>



<h2 class="wp-block-heading">Go further</h2>



<p>With the ability to create your own patterns baked into the creation experience, remember that you can copy the patterns available in the <a href="https://wordpress.org/patterns/">Pattern Directory</a> and <a href="https://wordpress.org/patterns/about/">contribute back</a>, an excellent way to democratize design for every WordPress user and the web.</p>



<p><em>For more exciting features coming to patterns in WordPress 6.3, </em><a href="https://make.wordpress.org/core/2023/07/13/core-editor-improvement-advancing-the-power-of-patterns/"><em>read on in the Advancing the Power of Patterns post</em></a><em>. Thank you to the contributors who collaborated on this post: </em><a href="https://profiles.wordpress.org/cbringmann/"><em>Chloé Bringmann</em></a><em>, </em><a href="https://profiles.wordpress.org/jpantani/"><em>Jonathan Pantani</em></a><em>, </em><a href="https://profiles.wordpress.org/chanthaboune/"><em>Josepha</em></a><em>, </em><a href="https://profiles.wordpress.org/kristastevens/"><em>Krista Stevens</em></a><em>, </em><a href="https://profiles.wordpress.org/eidolonnight/"><em>Nicholas Garofalo</em></a><em>, <a href="https://profiles.wordpress.org/provenself/">Peter Rubin</a></em>.</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:"Thu, 27 Jul 2023 14:45: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:8:"annezazu";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:40;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:84:"Do The Woo Community: Building Your Agency Stack with Judd Dunagan and Carlos Caneja";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=75733";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:83:"https://dothewoo.io/building-your-agency-stack-with-judd-dunagan-and-carlos-caneja/";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:445:"<p>Judd from Bright Vessel and Carlos from Britecode share insights and experience in building their WooCommerce Agency stack.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/building-your-agency-stack-with-judd-dunagan-and-carlos-caneja/">Building Your Agency Stack with Judd Dunagan and Carlos Caneja</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</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:"Thu, 27 Jul 2023 08:44: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: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:"";}}}}}i:41;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:52:"WPTavern: Gutenberg 16.3 Adds New Tools for Patterns";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:30:"https://wptavern.com/?p=147209";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:63:"https://wptavern.com/gutenberg-16-3-adds-new-tools-for-patterns";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:2393:"<p><a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/">Gutenberg 16.3</a> was released today as a maintenance release but includes several new tools that make pattern management smoother and easier for users. Most notably, custom user patterns now have a dropdown menu for renaming, duplicating and deleting them. Patterns and template parts that come with themes will only have the &#8220;duplicate&#8221; option available since they cannot be deleted or renamed. </p>



<div class="wp-block-spacer"></div>



video credit: <a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/">Gutenberg 16.3 release post</a>



<p>Gutenberg 16.3 adds a sticky header bar on the Patterns page. It also brings the &#8220;focus mode&#8221; to patterns, which is already available for template parts in the Site Editor but not available when editing patterns. Users may not notice but it provides more a consistent editing interface.</p>



<p>Those who have been keenly following the evolution of the Patterns page will notice that the &#8220;Theme patterns&#8221; heading has been <a href="https://github.com/WordPress/gutenberg/pull/52570">removed</a> and the pattern categories rearranged. Theme and plugin patterns now appear above template parts.</p>



<div class="wp-block-spacer"></div>



<img width="1270" height="1158" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/07/Screen-Shot-2023-07-26-at-10.16.04-PM.png" alt="" class="wp-image-147218" />image credit: <a href="https://github.com/WordPress/gutenberg/pull/52570">Gutenberg PR #52570</a>



<p>The icon for synced patterns isn&#8217;t self evident and some users may need more context. <a href="https://github.com/WordPress/gutenberg/pull/52458">A new tooltip</a> identifies synced patterns as those for which edits will apply anywhere the pattern is used.</p>



<p>Gutenberg 16.3 includes more than two dozen pattern interface-related fixes, among other editor bug fixes. If you are using and managing patterns frequently, having the Gutenberg plugin installed will enable a better experience with this interface until these updates make their way into core WordPress. Check out the <a href="https://make.wordpress.org/core/2023/07/26/whats-new-in-gutenberg-16-3-26-july/">release post</a> for a full list of all the changes and fixes in 16.3.</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:"Thu, 27 Jul 2023 02:49:22 +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:13:"Sarah Gooding";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:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:65:"WPTavern: WordPress 6.3 RC2 Released, Watch the Live Product Demo";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:30:"https://wptavern.com/?p=147173";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:75:"https://wptavern.com/wordpress-6-3-rc2-released-watch-the-live-product-demo";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:4287:"<p><a href="https://wordpress.org/news/2023/07/wordpress-6-3-release-candidate-2/">WordPress 6.3 RC2</a> has been released and is ready for community testing. Since RC1 landed a week ago, 15 changes have come in from the <a href="https://github.com/WordPress/gutenberg/commits/wp/6.3">Editor</a> and <a href="https://core.trac.wordpress.org/query?status=accepted&status=closed&changetime=07%2F18%2F2023..07%2F25%2F2023&milestone=6.3&col=id&col=milestone&col=owner&col=type&col=priority&order=id">Trac</a>, including bug fixes for footnotes, internationalization fixes, a missing command for opening the distraction free in the Site Editor, and a few other issues. </p>



<p>This release also brings in <a href="https://core.trac.wordpress.org/ticket/58067">work completing the About page</a> and adds a &#8220;Get Involved&#8221; section, closing a 10-year old <a href="https://core.trac.wordpress.org/ticket/23348">ticket</a> that suggested adding a &#8220;Contribute&#8221; tab to the About page.</p>



<div class="wp-block-spacer"></div>



<img width="1367" height="2560" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/07/screencapture-ppopotamus-zaje-instawp-xyz-wp-admin-contribute-php-2023-07-26-13_58_57-scaled.jpg" alt="" class="wp-image-147183" />



<p>The new Get Involved page features both code-based and no-code contribution opportunities with a link to WordPress&#8217; contributor teams.</p>



<p>The video of the <a href="https://wordpress.org/news/2023/07/wordpress-6-3-live-product-demo-highlights-recording/">WordPress 6.3 Live Product Demo</a> has been published so anyone who was not able to attend can get a preview of what is coming in the next release. Automattic-sponsored contributors <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a> and <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a> hosted the demo, showing users how to use the new command palette to zip around the editor and manage settings views. They also guide viewers through browsing and editing pages within the Site Editor, managing synced patterns (formerly called Reusable Blocks), and showcased various new blocks and design tools.</p>



<div class="wp-block-embed__wrapper">

</div>



<p>Check out the <a href="https://wordpress.org/news/2023/07/wordpress-6-3-live-product-demo-highlights-recording/">highlights post</a> for all the links to features referenced in the demo and the Q&amp;A portion of the broadcast.</p>



<p>For those interested in performance improvements coming in 6.3, an upcoming <a href="https://make.wordpress.org/core/2023/06/29/hallway-hangout-performance-improvements-for-wordpress-6-3/">hallway hangout</a> is happening tomorrow <strong><strong><a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230727T1500"><abbr title="2023-07-27T15:00:00+00:00">Thursday, July 27, 2023 at 11:00 AM EDT</abbr></a>. </strong></strong>Participants can check the <a href="https://wordpress.slack.com/archives/C02KGN5K076">#core-performance</a> Slack channel for the Zoom link before the event. Team leads will cover highlights from the 170+ performance improvements included in 6.3 and will discuss future improvements for 6.4. </p>



<p>WordPress&#8217; Training team is <a href="https://make.wordpress.org/training/2023/07/25/call-for-volunteers-to-help-with-6-3-learn-wordpress-updates/">calling for volunteers</a> to help with updating and revising existing Learn WordPress resources ahead of the 6.3 release. The team has created a <a href="https://github.com/WordPress/Learn/labels/6.3">board</a> on their GitHub repository which highlights high priority tasks. </p>



<p>WordPress 6.3 RC3 is expected to be released on August 1, and the general release is scheduled for August 8, less than two weeks away. There is still time to find and report some bugs. One easy way is to install the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin on a local testing site or use a quick throwaway site from services like InstaWP or TasteWP. <a href="https://core.trac.wordpress.org/newticket">Bugs can be reported on Trac</a> or via the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta section</a> of the support forums.</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, 26 Jul 2023 19:19:54 +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:13:"Sarah Gooding";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:43;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:79:"WPTavern: #85 – Giulia Laco on the Importance of Typography for Your Websites";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:48:"https://wptavern.com/?post_type=podcast&p=147116";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:93:"https://wptavern.com/podcast/85-giulia-laco-on-the-importance-of-typography-for-your-websites";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:51871:"Transcript<div>
<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.</p>



<p>Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case the importance of typography for your websites.</p>



<p>If you&#8217;d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to WPTavern.com forward slash feed forward slash podcast. And you can copy that URL into most podcast players.</p>



<p>If you have a topic that you&#8217;d like us to feature on the podcast, I&#8217;m keen to hear from you, and hopefully get you or your idea featured on the show. Head to WPTavern.com forward slash contact forward slash Jukebox, and use the form there.</p>



<p>So on the podcast today, we have Giulia Laco. Giulia is a web designer and developer who has been working on the web since the mid 1990s. Her primary interests are web typography and font design. In addition to project development, she&#8217;s a consultant and a trainer, mostly working with CSS, web fonts and web typography.</p>



<p>This is the last of our podcasts from WordCamp Europe, 2023. I spoke to Giulia in Athens because she had just finished her presentation entitled &#8220;typographic readability in theme design and development&#8221;.</p>



<p>In this session, she explored how designers can assist with the readability of websites through careful consideration of the fonts they choose and why they choose them.</p>



<p>It turns out there&#8217;s quite a lot to consider. And if you&#8217;ve not given this topic much thought in the past, you&#8217;ll perhaps learn something new. I certainly did.</p>



<p>We begin the podcast talking through how, at the start of the web, we were making do with a limited range of tools to help us make typographic choices. There were no web fonts available, but that started to change around 2010. Now we have access to hundreds of fonts and need to be mindful that some fonts can pose readability challenges for some users of your website.</p>



<p>Giulia talks about the fact that the manner in which we read has changed since the dawn of the internet. Many people now mostly consume small passages of text, which need to be considered in a different way to longer writing.</p>



<p>Concentrating upon the letters in the Latin alphabet, we talk about the ways in which readers typically break up words into smaller units, and the fact that the way letters are shaped can make them easier to parse. There&#8217;s some technical language here, ligatures X-height, apertures, and more. Which tell us about the shaping and spacing of letters. Giulia explains the current state of research into how these characteristics of fonts can affect readability.</p>



<p>We talk about whether or not there are fonts which are more readable than others. Is there a collection of fonts, which you can use and be confident that you&#8217;re going to make it easy for all users of your websites?</p>



<p>Giulia talks about how designs need to consider the spaces into which the text is put. Most people have a proclivity for the order in which they view a page. And knowing about this path across the page can help your readers access the text.</p>



<p>The width of the text is also important. You want people to be able to read from side to side without having to move their head. How does this work across different device sizes and what can be said about text, which runs right to left, or top to bottom?</p>



<p>We round off the conversation with Giulia telling us where we can find out more, as well as some of the thought leaders in this space.</p>



<p>It&#8217;s a fascinating conversation about a subject that often gets overlooked. Web designers, this episode is for you.</p>



<p>If you&#8217;re interested in finding out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you&#8217;ll find all the other episodes as well.</p>



<p>And so without further delay, I bring you Giulia Laco.</p>



<p>I am joined on the podcast by Giulia Laco. Hello Giulia.</p>



<p>[00:04:43] <strong>Giulia Laco:</strong> Hello.</p>



<p>[00:04:43] <strong>Nathan Wrigley:</strong> It&#8217;s very nice to have you on. Giulia is joining me at WordCamp EU in Athens. It&#8217;s the last conversation that I&#8217;m recording, so very nice to have you on. You are going to be talking to us today about something that I genuinely didn&#8217;t know about.</p>



<p>This was a really interesting topic to research from my point of view. You&#8217;re going to be talking to us a little bit about typography. That&#8217;s based upon a workshop that you did yesterday. How did it go?</p>



<p>[00:05:12] <strong>Giulia Laco:</strong> I&#8217;m happy about that. I&#8217;m happy to hear that you are interested in typography as well.</p>



<p>[00:05:17] <strong>Nathan Wrigley:</strong> Was it well attended? Did you get your information across? Did people engage with the topic?</p>



<p>[00:05:22] <strong>Giulia Laco:</strong> I think so. I divided people in two groups, developers and designers. So to let them think about typography with the mentality of the others. So that was the point I was trying to have.</p>



<p>[00:05:35] <strong>Nathan Wrigley:</strong> Well, the reason I wanted to talk to you was because when I was looking through the list of presentations and workshops, yours was really different, a topic that I genuinely hadn&#8217;t thought about in the way that you&#8217;ve made me think about it.</p>



<p>Because whenever I think about typography, I am really just thinking about whether I like a font. So if I go to a website, I just make a quick judgment. Do I like that font? Do I not like that font? But there&#8217;s a lot more to it than that, which we&#8217;re going to get into. But can you just tell us why you&#8217;re interested in this? Do you have a history with working with type? Why are you so fascinated by typography?</p>



<p>[00:06:17] <strong>Giulia Laco:</strong> Okay, well, maybe it&#8217;s because I&#8217;ve started making websites at the very beginning of the internet era. It was around, mid nineties. And we didn&#8217;t have the possibility to use web fonts of any kind on the web. We did what we could with very few tools. Whereas later on in 2009 or 10, we had this great possibility of using web fonts, and I started to get engaged with, with the typography. And that was the time when I was starting typography for the first time actually.</p>



<p>[00:06:52] <strong>Nathan Wrigley:</strong> Are you interested in typography away from the internet? Are you interested in the way that type is presented in books and on paper?</p>



<p>[00:07:00] <strong>Giulia Laco:</strong> Yes, everywhere. On menus as well.</p>



<p>[00:07:03] <strong>Nathan Wrigley:</strong> Yeah, because when you actually turn your attention to typography, which is what I did after we booked this interview. Text is everywhere, and it&#8217;s really, really different wherever you look. So we are sitting in a room. There&#8217;s almost no text, but there&#8217;s a little bit of text behind you. It has a particular font.</p>



<p>[00:07:22] <strong>Giulia Laco:</strong> Montserrat.</p>



<p>[00:07:23] <strong>Nathan Wrigley:</strong> Montserrat probably, yeah. I&#8217;m looking at my computer. It has a font on it. I&#8217;ve just been downstairs, looked at a menu. It had three or four fonts on it. Wherever you look, there is text, and usually the typography has been thought about.</p>



<p>But you were talking about typography from the point of view of how can be done better. How can be a problem for some people, and that I didn&#8217;t really realize. I knew that people would perhaps struggle to read text because it was too small, or there was a background color, which clashed with the color of the text. But I didn&#8217;t realize that the font itself could be a problem. So tell us how it can be a problem. How can some people struggle to read one font but not another?</p>



<p>[00:08:08] <strong>Giulia Laco:</strong> Well, it&#8217;s a big question, because, there&#8217;s a lot of research about that, recent research on readability. Because very few people read a lot nowadays in each country. So a lot of countries are worried about that.</p>



<p>So there are movements to let people read better by making some tools. And big companies like Adobe, Google are on this concern. They&#8217;re concerned about that. So they&#8217;re trying to study that subject. The Readability Consortium, a consortium from between these big companies and universities in America.</p>



<p>And it&#8217;s working interdisciplinary. So with psychologists, typographers, graphic designers. And started to focus on what makes text legible. And what they are, as far as I know, they&#8217;re saying is that it&#8217;s different for everybody. So you test it.</p>



<p>And so that&#8217;s why you need to make tools that help people adjust their texts when they read for long form reading, of course. Not for just a menu or, very few words you are going to read. And they&#8217;re trying to do those tools. And maybe it&#8217;s difficult for a user to know what they need.</p>



<p>[00:09:30] <strong>Nathan Wrigley:</strong> Right.</p>



<p>[00:09:30] <strong>Giulia Laco:</strong> So, they are working also with AI. Trying to have some patterns and, have some themes, let&#8217;s say. So that can adapt to very different kind of people. But they&#8217;re trying to reach that patterns by research, not by guessing. So that&#8217;s very intereting.</p>



<p>[00:09:50] <strong>Nathan Wrigley:</strong> Yeah, really interesting. I mean, again, when I was researching this, it suddenly occurred to me that, I have children, they&#8217;re grown up largely now. But I remember when they came home from school, at the beginning, their homework was in child-friendly fonts. Let&#8217;s put it that way. Often it was something along the lines of comic sans something like that. And it didn&#8217;t occur to me at all at the time, I just thought, oh, well it&#8217;s a child-friendly font. It&#8217;s kind of round and it&#8217;s got, you know, there&#8217;s no hard edges.</p>



<p>I just thought it&#8217;s just a pleasant thing to look at. But now that I&#8217;m thinking about it, it was probably an easier font for the child to begin to learn to read with. Because all of the letters were clear. There was no confusion between one letter and the other. You know, you couldn&#8217;t mistake the L for the I, for example. And I did wonder, you were saying that there&#8217;s less people reading than ever. If the typography is a, quotes, difficult font, it may be more difficult to begin learning to read. I don&#8217;t know if that&#8217;s something that you were trying to say there.</p>



<p>[00:10:59] <strong>Giulia Laco:</strong> Well actually, when a child start reading has a very tough task. And helping that process is important. I remember seeing books in upper case letters only, it was meant to be simpler. But they started only to recognize only one kind of letters. In the Latin alphabet, we have upper case and lower case, and they&#8217;re very different because of their history.</p>



<p>Uppercase letters comes from the engraved Latin letters. Whereas the small, lowercase, comes from calligraphy. So they&#8217;re very different origins,. And it&#8217;s not the same to learn lowercase a and a lowercase a. Recognizing them as the same letter, the same sound.</p>



<p>And with sound is also difficult, especially in English, you have so much problem with sounds and letters.</p>



<p>[00:11:57] <strong>Nathan Wrigley:</strong> Yeah. I think we have 44 sounds, but only 26 letters.</p>



<p>[00:12:02] <strong>Giulia Laco:</strong> And the combination. When you use a letter and a sound, other languages are much more simpler on that respect.</p>



<p>[00:12:09] <strong>Nathan Wrigley:</strong> Yeah again, remarkable. I&#8217;d never really given any thought to how different uppercase and lowercase are. But they don&#8217;t bear, in some cases they&#8217;re quite similar.</p>



<p>[00:12:17] <strong>Giulia Laco:</strong> Yes.</p>



<p>[00:12:18] <strong>Nathan Wrigley:</strong> So an l and a capital L, broadly the same. But something like an a, the capital letter A and the lowercase letter. They&#8217;re just utterly different, aren&#8217;t they? They&#8217;re really, really remarkably different. Oh, that&#8217;s fascinating. I hadn&#8217;t given any thought. So what makes text legible to a lot of people, or not legible to a lot of people? Are there any kind of guidelines around that?</p>



<p>[00:12:41] <strong>Giulia Laco:</strong> Okay, I will distinguish between legibility and readability. Because, you have this distinction in English and it&#8217;s great. We don&#8217;t have it in Italian. I guess the legibility comes from lighting as we have for legibilita in Italian. And it&#8217;s something that has to do with decoding. So that&#8217;s something that has to do with the typeface.</p>



<p>Whereas readability is something you want to read, you like to read something, you want to read. And not you&#8217;re just trying to decode things. So that&#8217;s a big difference, when you start to understand why a text is readable or not. I would say that trying to take a legible font means to have a font with certain characteristics.</p>



<p>For example, it&#8217;s let&#8217;s say proved that a font with a higher X-height is more legible. I&#8217;m talking about running text, the body text for long reading experience. So X-height is basically the medium height of the lower case letters, based on the letter x, that&#8217;s why X-height, you see.</p>



<p>And so for example, I don&#8217;t Helvetica has a higher X-height than Times New Roman, for example, if you compare it. And having a higher X-height is a typeface, be more readable.</p>



<p>And another very important thing is with apertures. Apertures, how can I say, the white space inside the part of the letters that are open. Take a lowercase e in the lower part of the letter. You have this room. If it&#8217;s more closed, it&#8217;s less legible because it can be taken for an o for example, you see. So Helvetica, for example, is very well used, but it&#8217;s not legible as a body copy. Helvetica is wonderful for display type for titles, but not so well for body text.</p>



<p>[00:14:42] <strong>Nathan Wrigley:</strong> So you are saying, so this X-height? So is typically the height of the letter x. So if I put an x next to the letter h, for example, it&#8217;s the height of the rounded bit of the letter h? </p>



<p>[00:15:55] <strong>Giulia Laco:</strong> Yes, exactly.</p>



<p>[00:14:57] <strong>Nathan Wrigley:</strong> Or it would be the height of the letter a? Or the rounded bit of the letter p? The more tall that bit is, the more legible it is for most people to read. I had no idea.</p>



<p>[00:15:09] <strong>Giulia Laco:</strong> Well, it&#8217;s just one thing because, not only that, because it&#8217;s also how you set type. For example, if you have a large X-height, typeface and you set it with a very small space between the lines, the line height, the leading, they say in typography. You don&#8217;t take advantage of that highness, you see.</p>



<p>[00:15:32] <strong>Nathan Wrigley:</strong> Okay. So if letters are squashed. If one line of letters is compressed, so line height.</p>



<p>[00:15:37] <strong>Giulia Laco:</strong> Mm-hmm.</p>



<p>[00:15:37] <strong>Nathan Wrigley:</strong> Is compressed up against another line of letters beneath it, that makes it more difficult to read because there&#8217;s just no room for the letters to breathe, There&#8217;s no gap. They&#8217;re all just squished together. Okay?</p>



<p>[00:15:48] <strong>Giulia Laco:</strong> But you have to pay attention not to put too much line height. Otherwise you lose the next line when you jump from one line to the other, it&#8217;s too far and you can&#8217;t find it.</p>



<p>[00:15:59] <strong>Nathan Wrigley:</strong> So this is the eyes ability to go from the end of one line and track, and immediately find the beginning the next line.</p>



<p>[00:16:46] <strong>Giulia Laco:</strong> Yes exactlly.</p>



<p>[00:16:47] <strong>Nathan Wrigley:</strong> I confess I have experienced that problem before, and I hadn&#8217;t noticed, until just now, that that was because of that. I&#8217;ve definitely had books that I&#8217;ve been reading where I&#8217;ve struggled to begin the next line, and sometimes repeated the line that I was supposed to be on. Or I&#8217;ve skipped a line and missed a line out and only halfway through thought, actually that doesn&#8217;t make any sense. Let me go back. I had no idea. But also you are saying that the amount of, what did you call it, the space?</p>



<p>[00:16:30] <strong>Giulia Laco:</strong> Oh, typographers call it leading because it&#8217;s comes from lead, lead, lead, I don&#8217;t know, of the metal types. With metal types they used to put some space between the lines with some lead. So the lead bars.</p>



<p>[00:16:45] <strong>Nathan Wrigley:</strong> Oh, okay. So they spaced them out with a physical object.</p>



<p>[00:16:30] <strong>Giulia Laco:</strong> Yes, exactly.</p>



<p>[00:16:45] <strong>Nathan Wrigley:</strong> And it was a bar of lead, and the wider the bar of lead, the more space. This is fascinating. But you also mentioned in the letter e for example, the lowercase e, forgive me if I misunderstood. So the bottom half of the letter e, there&#8217;s a gap, a little gap, and the amount of gap, if the gap is bigger.</p>



<p>[00:17:07] <strong>Giulia Laco:</strong> That&#8217;s the aperture, yes.</p>



<p>[00:17:08] <strong>Nathan Wrigley:</strong> The bigger the gap is, the more you are likely to be able to read it, typically?</p>



<p>[00:17:13] <strong>Giulia Laco:</strong> Yes, because you&#8217;re likely to distinguish it from an o.</p>



<p>[00:17:16] <strong>Nathan Wrigley:</strong> Of course.</p>



<p>[00:17:17] <strong>Giulia Laco:</strong> You decode it easiest.</p>



<p>[00:17:19] <strong>Nathan Wrigley:</strong> You keep mentioning Helvetica. Is that a font which has lots of problems? Is that why you mention it, because it&#8217;s full of things you can identify?</p>



<p>[00:17:26] <strong>Giulia Laco:</strong> It&#8217;s very well known. That&#8217;s why I&#8217;m mentioning. And very much used. But it&#8217;s better to use it as a display type.</p>



<p>[00:17:34] <strong>Nathan Wrigley:</strong> The only thing that I&#8217;ve ever had a problem reading, was the thing that I&#8217;ve just described where I have skipped a line or gone back and reread the other line. But I&#8217;m imagining that you&#8217;ve done this talk because there are problems which people experience, which I fortunately, don&#8217;t appear to have a problem with. What trips people up? If you were somebody that, I don&#8217;t know how to say this correctly. If you are somebody who struggles to read, what are the trip wires, if you know what I mean?</p>



<p>What are the things in a font could be wrong that make you unable to read it? So you mentioned that the line height, you mentioned the X-height. Is there more to it than that?</p>



<p>[00:18:14] <strong>Giulia Laco:</strong> Well, there might be a lot. One thing that I can think of are ambiguous forms of letters. Let&#8217;s take lowercase letters, p and q or b and d. So for these four letters in a sans serif font, for example, are usually with the same shape, just flipped or rotated. That&#8217;s said to be a problem with people that experience dyslexia. But it&#8217;s actually opinionated because we don&#8217;t know exactly how it works. Actually for everybody can be a problem to distinguish between similar shapes.</p>



<p>For example, as you said before, a child who is starting to read, or to write as well, may experience the same problem. No matter if it&#8217;s, if there&#8217;s a problem of dyslexia or not. So if you are going to avoid these kind of things, you can pick a font, a serif font that generally has different letters, different forms. The four letters I mentioned, typically with small serfis in different parts of the letters so they can be distinguished, for sure.</p>



<p>[00:19:27] <strong>Nathan Wrigley:</strong> Can you, I know it&#8217;s probably obvious to most people, but will you just tell people what a serif font is and what it isn&#8217;t? You know, if you&#8217;ve got a non serif font or serif font, what&#8217;s the difference?</p>



<p>[00:19:39] <strong>Giulia Laco:</strong> Let&#8217;s take the example of Helvetica and Times New Roman. So maybe it&#8217;s easier for people to visualize the difference. Helvetica has straight lines, nothing at the termination of the strokes. Whereas Times New Roman has some small shapes that derive from the calligraphic or the, in that case, for the upper case, the engraving, the instrument that we use to engrave. And so they had this little [feet?] let&#8217;s say so, that distinguish the kind of font.</p>



<p>And the font has a different mood, very different mood. And a lot of other characteristics. There are, well, history of typography is based on that more or less.</p>



<p>[00:20:24] <strong>Nathan Wrigley:</strong> It always feels to me as if a font, a serif font, which has these, I think you use the word where the letter terminates. I&#8217;ve never really</p>



<p>[00:20:31] <strong>Giulia Laco:</strong> thought about that. They always look as if they&#8217;re more, I don&#8217;t know, maybe in a legal document or something like that. They have this feeling of something more powerful or more important or something. It&#8217;s quirky that, isn&#8217;t it?</p>



<p>I&#8217;m looking at a Google Doc where I&#8217;ve written my show notes and, I don&#8217;t see any that. I can&#8217;t tell you that either of those fonts are a serif font or a non serif font. I find them both equally easy to read. It doesn&#8217;t trip me up at all. But typically, is there a problem for some people with a serif font or a non serif font? Is there one, to catch everybody would it be better to not deploy a serif font or is there just no difference in people&#8217;s ability to cope with either?</p>



<p>Each font is maybe very different. Most people at the first level, when they start talking about topography, they started to see this difference. But that&#8217;s not the main point. Maybe the main point in readability is the rhythm of letters. The rhythm where the white space and the black space, meaning when you have black text on white. They alternate each other.</p>



<p>Try to figure out this word, minimum. You&#8217;ll have a lot of rhythm. Minimum in, written in lower case letters. You see? So, the rhythm is very, very different. And maybe that&#8217;s important in typography, in reading. And is very important for people who struggle with reading, because you don&#8217;t interrupt the rhythm. The rhythm helps reading.</p>



<p>[00:22:03] <strong>Nathan Wrigley:</strong> It just sort of bounces along, doesn&#8217;t it? If you look at the word minimum, it genuinely has a, it&#8217;s almost like a little wave pattern going up and down, isn&#8217;t it? That&#8217;s fascinating. So what did you call it? Your ability to read it. There was a word you just said. Rhythm, rhythm. So words can have rhythm, and the more rhythm there is, the easier it is to read. So if a font provides rhythm, that&#8217;s a good thing.</p>



<p>[00:22:24] <strong>Giulia Laco:</strong> I think so. But it depends also on the purpose. Long reading. I think that&#8217;s important. Otherwise it&#8217;s different. It&#8217;s totally different. I mean concepts with display types because they have a different purpose, you know, text and function. The titles have different purpose. They have to catch the attention. Whereas the long, the body text has to be read, so needs a different kind of attention.</p>



<p>[00:22:53] <strong>Nathan Wrigley:</strong> Right. And are there any guidelines which kind of fonts catch the attention more, and which kind of fonts work better with the body content? You know, where you&#8217;re reading long paragraphs and so on? Does it matter or is there one kind of font that you would recommend in each case?</p>



<p>[00:23:08] <strong>Giulia Laco:</strong> Generally, when you buy a font, you&#8217;ll have a font that is meant for body text and some other for display type. So if you rely on what the designer, the type designer, has done, you are safe. Otherwise you have to. try. But also if you go on a repository like Google fonts for example, you have this distinction among display types and other kind of types. So it&#8217;s quite a common mistake at the beginning to take display type and use it as a body text. And that&#8217;s a typographic crime.</p>



<p>[00:23:47] <strong>Nathan Wrigley:</strong> I like it. Typographic crime. That&#8217;s great. We&#8217;re all of us using our devices more and more. It&#8217;s funny that you said that reading is becoming less and less, because it feels like we have text in front of us all the time now. So we&#8217;re constantly staring at our mobile phones, and our computers. But when I was a child, if I wasn&#8217;t holding book, I probably wasn&#8217;t reading.</p>



<p>I mean, maybe there was a poster somewhere or something, but I&#8217;m surprised that reading is, there&#8217;s less desire to read, because it feels like every day I&#8217;m reading more or less constantly, you know, I&#8217;m scanning Twitter or Facebook or whatever.</p>



<p>[00:24:26] <strong>Giulia Laco:</strong> It&#8217;s a new kind of reading, Because we had long form reading for books. Then we have glanceable reading for, I don&#8217;t know, street signs. Or maybe a manual in a website. And then we have this, they call it interlude reading. You read when you&#8217;ve time, you&#8217;re doing, you don&#8217;t have a lot of attention, you scroll. And then you have also that the way we read on the web is very different from what we read, elsewhere.</p>



<p>For example, we have this shape, F shaped reading. When we, in a website, eye tracking has shown it quite a lot. You start from the top left where the logo generally is. Then you go on the right, then you go on the left, but a bit bottom, and then a bit, you are just drawing an F more or less, when you read.</p>



<p>[00:25:17] <strong>Nathan Wrigley:</strong> So that&#8217;s what the eye typically does when it lands on a webpage.</p>



<p>[00:25:20] <strong>Giulia Laco:</strong> Yes.</p>



<p>[00:25:20] <strong>Nathan Wrigley:</strong> What was that? Top left, top right.</p>



<p>[00:25:23] <strong>Giulia Laco:</strong> Bottom.</p>



<p>[00:25:23] <strong>Nathan Wrigley:</strong> Bottom.</p>



<p>[00:25:24] <strong>Giulia Laco:</strong> A bit in the middle, right. And then bottom again.</p>



<p>[00:25:27] <strong>Nathan Wrigley:</strong> So it makes an, if you were to draw on top of that screen, it coincidentally looks a bit like a capital F.</p>



<p>[00:25:32] <strong>Giulia Laco:</strong> Yes, exactly.</p>



<p>[00:25:33] <strong>Nathan Wrigley:</strong> That&#8217;s fascinating.</p>



<p>[00:25:34] <strong>Giulia Laco:</strong> Capital F reading.</p>



<p>[00:25:36] <strong>Nathan Wrigley:</strong> Capital F reading. Presumably that&#8217;s on a desktop. On this, I&#8217;m not doing that am I? I&#8217;m holding up my phone. If I&#8217;m looking at a webpage, presumably it&#8217;s a different experience. It&#8217;s just left to right, left to right, left to right.</p>



<p>[00:25:49] <strong>Giulia Laco:</strong> Also because you are hiding some part of the text with your thumbs. Are you right-handed? Left-handed? It depends what you do. And it change a lot. For example, in the UX design, we generally change some patterns with smartphones because we put some menus at the bottom because the area near the thumb, for example.</p>



<p>So, if it changes where you put your fingers, your changes also where you put your eyes. Focusing in which part of the screen.</p>



<p>[00:26:20] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s interesting. My experience of the internet is that usually the menu on a mobile device comes at top right. There&#8217;s usually some icon.</p>



<p>[00:26:28] <strong>Giulia Laco:</strong> But that&#8217;s for convention.</p>



<p>[00:26:29] <strong>Nathan Wrigley:</strong> But what you&#8217;ve just described is much more sensible, having the menu the bottom because.</p>



<p>[00:26:33] <strong>Giulia Laco:</strong> I hope it will change soon.</p>



<p>[00:26:34] <strong>Nathan Wrigley:</strong> Because my thumb can just go right to it. It&#8217;s just there. Yeah, that&#8217;s fascinating. It does matter what device you&#8217;re on. But are you using the same? I know that you&#8217;ve said that you reposition things like the menu or what have you, but are you using the same font on a desktop as you would be on a mobile device? Is it broadly the same? You don&#8217;t need to worry about the view port of a mobile device in terms of the CSS for setting the font. It&#8217;s just the same desktop, mobile, tablet, same fonts.</p>



<p>[00:27:03] <strong>Giulia Laco:</strong> From the readability point of view, I would say yes. And it&#8217;s for branding. I guess it&#8217;s better to have different environments recognizable. Whereas you have to pay attention to licensing. If you buy a font, for example, you put it on an app, you might need a different license. If you&#8217;re using open type, open source phones, you are not going to have a problem. But if you buy, if you rent, web fonts, yeah, you might have some problem or you have to check if you can put that web front on an app. You might need a different license.</p>



<p>[00:27:39] <strong>Nathan Wrigley:</strong> Yeah, I hadn&#8217;t really thought about that. It&#8217;s always quite common in the circle of friends that I have, comic sans is a font, which most of my friends ridicule. They think it&#8217;s a childish font. Nobody would put it on a professional website. Are there some fonts like that, which you would just always avoid? Not because they look childish, but because they are largely unreadable.</p>



<p>[00:28:00] <strong>Giulia Laco:</strong> There might be some, for example, well comic sans has a very big history of love and hate, basically of hate actually. But remember the case and presentation of the Higgs Boson?</p>



<p>[00:28:16] <strong>Nathan Wrigley:</strong> Yes. Was that done in comic sans?</p>



<p>[00:28:18] <strong>Giulia Laco:</strong> Yes. There was a Twitter storm. Okay, you couldn&#8217;t use that informal font on a formal presentation, and that raised the topic actually. You have to use the font that is proper to the situation. It&#8217;s like clothing. The clothes you wear, it&#8217;s like the font you use. It depends on the situation.</p>



<p>But I can understand the feeling that people have when they choose comic sans. And maybe I can suggest something similar, but a bit more proper, or a bit more interesting in that context.</p>



<p>There&#8217;s one font. I am on Google fonts repository. That&#8217;s called Amantic Small Caps, and it&#8217;s a small caps, so it&#8217;s a more, it&#8217;s not lowercase. But it&#8217;s, I think has a similar mood and I would dare it&#8217;s quite a new comic sans in the mood. I mean, it has the same mood, in my opinion. I say in my opinion, it&#8217;s also because it&#8217;s in my culture, it&#8217;s very culture dependent. Because it&#8217;s based on what you saw, what you associate to those fonts for example.</p>



<p>[00:29:28] <strong>Nathan Wrigley:</strong> Yeah, it&#8217;s really interesting when I travel to the US. The US have a really different set of fonts which they use, especially on government documents, than we have in the UK. And wherever I look, so I don&#8217;t know, I buy some sun cream or something like that. The font choice is utterly different from how it would typically look in the UK. And it&#8217;s kind of curious, that it&#8217;s so obvious to me that that&#8217;s an American box. And yet it&#8217;s merely a font that tells me that. But I can see it all the time.</p>



<p>But what you&#8217;re saying though is you&#8217;ve got to use your intuition. There&#8217;s no rule for this is a good font, that&#8217;s a bad font. It&#8217;s really where are you putting it and your own personal preference. There are no fonts which are out of the question because they&#8217;re just literally unreadable by a subset of the people, no, you look like you&#8217;re about to say something.</p>



<p>[00:30:18] <strong>Giulia Laco:</strong> Well, there might be some fonts that are really illegible, but there are some really nice experiment by a very talented type designers, David Jonathan Ross. He tried to push the boundaries of readability, making good fonts, but making how long you can go to draw a very new kind of letter and still have it readable. So that&#8217;s interesting to see. But made by people who know what they do.</p>



<p>Whereas if you start, if you look at the, I don&#8217;t know, fonts that you can have on a lot of websites, just experiments by people who start. But if you, look at experiments by very good designers, oh, you know what they do.</p>



<p>[00:31:06] <strong>Nathan Wrigley:</strong> You make client websites still. Do you get into this conversation quite a lot with your clients? Is typography something that you bang the drum of?</p>



<p>[00:31:14] <strong>Giulia Laco:</strong> I try to listen as for everything else, to the client and understand what they need. And then I&#8217;ll try to suggest what I think is proper. It&#8217;s like also for the colour of a website for example. I ask and I give an advice maybe.</p>



<p>[00:31:30] <strong>Nathan Wrigley:</strong> Are there any kind of hard and faster rules for where you, really, it would be unwise to put typography. In our show notes, I was talking about things like is it a bad idea to put, I don&#8217;t know, fonts into images.</p>



<p>So you&#8217;re overlaying fonts on images. In other words, is it better always to have fonts on a plain background rather than on, let&#8217;s say you&#8217;ve got a mountain scene or something and you want to write something, you put it onto the image. Is it better to keep the text away from the images? That was just one thought.</p>



<p>[00:32:02] <strong>Giulia Laco:</strong> That&#8217;s definitely better. But you have to distinguish between titles and body copy. A title might be, how can I say? It would be okay anyway. It&#8217;s only a word. You might have some tricks, for example, reducing the contest of the underground image. As long as you stick with accessibility guidelines, you&#8217;re safe for that regard.</p>



<p>There are very good starting point for readability. I mean, I generally say that it&#8217;s better to start from accessibility and there are a lot of accessibility guidelines that help with the text. And then you go on and if you have some tools, like a very powerful web font, you can do more. And then you go with type setting and start type setting.</p>



<p>Well, for example, you have to stop the line length. That&#8217;s very, very important. You don&#8217;t have to let your user go through all the screen, a very huge screen to go to the other line, to the second line.</p>



<p>[00:33:04] <strong>Nathan Wrigley:</strong> Is there any guidance about how wide the text line should be? So maybe that&#8217;s a, I don&#8217;t know, you said using a number pixels is not always the best idea. But is there a character limit, or a word limit typically where the eye can cope with scanning from left to right and then beginning again. Because I&#8217;m staring at a Google Doc at the moment and it&#8217;s kind of interesting that the Google Doc looks like a piece of paper.</p>



<p>And they&#8217;ve obviously deliberately taken it in. The Google doc could consume the whole width of my monitor, but it doesn&#8217;t. They&#8217;ve confined it to what looks like a piece of paper, and I presume that&#8217;s a convention, just so that my eye doesn&#8217;t have to go far left, far right, far left, far right. I could keep my nose pointed at the document and just let my eye do the work, whereas if it went from left to right, I would be moving my neck all the time as well. So is there a guidance of how wide text should be?</p>



<p>[00:33:56] <strong>Giulia Laco:</strong> Typographers, for a long time, had recommended a line length of between 45 and 65 characters per line. It depends for Latin alphabets. The Web Accessibility Guidelines says, I think at the level Triple A. They say that they need 80 characters maximum per line for Latin, I think 40 for languages with ideograms. So they say something about that.</p>



<p>And it&#8217;s very interesting to see that there&#8217;s a correlation between this line length and the way we read. The way we read is basically with eye and brain because, it&#8217;s a really complex process. But when we read with the eye, we just focus on few letters at the time, maybe six, seven characters. Then we jump to another area of fixation. And so you can do some math. A very good typographer Bruno Maag made that math.</p>



<p>And he discovered that calculating the number of characters you see in each fixation has a relationship with what typographers said for years, for decades, for centuries actually. So they arrived at the same conclusions. So let&#8217;s say 55, 65 characters per line is a good measure.</p>



<p>[00:35:18] <strong>Nathan Wrigley:</strong> Yeah.</p>



<p>[00:35:18] <strong>Giulia Laco:</strong> On the other hand, all these factors are correlated. And especially font size, line height, and line length. Some typographers says that it&#8217;s like a triangle of these three elements have to be on balance. So if you change one, you have to change the others. Adapt the others.</p>



<p>[00:35:40] <strong>Nathan Wrigley:</strong> So we&#8217;ve just been talking about the left to rightness, the line length. Is there anything about the length of the paragraphs that you use as well? I mean, I&#8217;m just used to reading books and obviously they&#8217;re confined by the width. The line length is taken account of. But I&#8217;m conscious that everything&#8217;s broken up into paragraphs and those chunks of meaning have often got little gaps between them. I&#8217;m imagining in many cases, paragraphs could go on for pages, but it&#8217;s better to break it up and it helps the brain to associate that this is a body of meaning and here&#8217;s another body of meaning and so on.</p>



<p>[00:36:10] <strong>Giulia Laco:</strong> Yes. I think absolutely. The basic of our work as web designers actually. So it&#8217;s different from what we do on paper, because on screens we have to catch the attention. And so we need to make things very easy for the reader. That&#8217;s the purpose. Maybe it&#8217;s not always the case that that&#8217;s the purpose, but on web design generally, that&#8217;s the purpose.</p>



<p>So it&#8217;s better to split a paragraph in a few small chunks, let&#8217;s say so, and give different, styling and introduce hierarchy as well. So that helps a lot in reading.</p>



<p>[00:36:48] <strong>Nathan Wrigley:</strong> So headings and paragraphs and other headings and so on. You mentioned in the show notes that when you did your workshop, were going to give some helpful CSS to break up the text. Can you just tell us what that was? What helpful CSS did you have?</p>



<p>[00:37:02] <strong>Giulia Laco:</strong> Basically, I would say that&#8217;s very important not to use an absolute unit when you set the font size. Where font size is what is more relevant in readability? Because if it&#8217;s too small, you can&#8217;t read at all. If it&#8217;s too big, also so you can&#8217;t read it well. So font size is very important and after the responsive web design, we&#8217;ve had the responsive web typography. It didn&#8217;t come at the same time. Because with responsive web design, we started to make things different for different devices. But we didn&#8217;t touch the font size.</p>



<p>[00:37:40] <strong>Nathan Wrigley:</strong> Right, it was just the same. Yeah.</p>



<p>[00:37:42] <strong>Giulia Laco:</strong> But it was really important to change the font size. At the beginning I thought that it was important to make smaller font size on smartphones. Because you had a very smaller screen, but that was not the reason I realized later on.</p>



<p>And the reason is the distance of reading. So when you read something that is near, you don&#8217;t need a big font size. You generally keep an iPhone at 20, 30 centimeters of distance from your eye. Whereas if you read to a computer you are 70 centimeter, 80, 1 meter, I don&#8217;t know. If you read to a screen in a room, for example, yeah, it&#8217;s very, very different.</p>



<p>For example, yesterday I had this at the workshop. I had this CSS Codepen. I realized I had some minimum and maximum font size in my slider. It was perfect for desktop reading. As soon as I was in the room, I said, oh no, I have to change, and I changed it to a different values because of that.</p>



<p>[00:38:48] <strong>Nathan Wrigley:</strong> So, the presentation looked good on your computer, but as soon as it went on the big screen.</p>



<p>[00:38:52] <strong>Giulia Laco:</strong> Okay, the presentation was okay because I knew it in advance. I mean, it was a presentation, but it was in the playground, I realized, yes. And because I had all those values, I was guessing what was reasonable values. But I didn&#8217;t test it before on such a big room.</p>



<p>[00:39:10] <strong>Nathan Wrigley:</strong> So I&#8217;m guessing that at some point soon we&#8217;ll be able to make a link to WordPress TV. It occurs to me that the whole time we&#8217;ve been talking about typography, but we&#8217;ve probably been concentrating on English. Although it&#8217;s a common language, it&#8217;s by no means what everybody reads.</p>



<p>So we&#8217;re going from top to bottom, left to right. But other parts of the world, let&#8217;s say people that read Arabic or Hebrew or Korean or Japanese or Chinese, whatever it is. They&#8217;re going in completely different directions, left to right, bottom to top and so on.</p>



<p>Do they have similar concerns with their characters? Or is it just uniquely the Latin set of characters which has these problems?</p>



<p>[00:39:54] <strong>Giulia Laco:</strong> I&#8217;m sure they have. Also maybe different problems. I&#8217;ll distinguish between Arabic to the other languages you mentioned, like Japanese, Chinese, and Korean, for example. They have ideograms. With Arabic it&#8217;s quite a calligraphic origin of the way of writing. And they make a lot of use of ligatures. It means it changes the shape of letters according to their combination.</p>



<p>We have ligatures in Latin as well. For example, if you think of f and i, small lowercase letters f and y. Sometimes you have one glyph that put the dot of the i inside the f. And that&#8217;s coded inside the file, the font file.</p>



<p>So in Arabic they have a lot of ligatures. And lately I&#8217;ve discovered that they also use color for accent. And Google fonts has some new fonts with this characteristic. Color fonts. Do you know color fonts?</p>



<p>[00:40:54] <strong>Nathan Wrigley:</strong> No.</p>



<p>[00:40:54] <strong>Giulia Laco:</strong> They&#8217;re very, very new. They&#8217;re coming.</p>



<p>[00:40:57] <strong>Nathan Wrigley:</strong> How do you deploy color to. What? You&#8217;re going to have to explain that.</p>



<p>[00:41:00] <strong>Giulia Laco:</strong> Well, they have color coded inside the typeface. It&#8217;s a new format we can use. And, it&#8217;s linked to CSS. It&#8217;s not so much ready, but it&#8217;s coming. It&#8217;s a new technology after variable fonts.</p>



<p>[00:41:17] <strong>Nathan Wrigley:</strong> So certain aspects, certain portions of the letter receive different colors?</p>



<p>[00:41:22] <strong>Giulia Laco:</strong> Yes.</p>



<p>[00:41:23] <strong>Nathan Wrigley:</strong> And it provides, I have to just ask why? Why would you want to have a different portion of the letter in a different color?</p>



<p>[00:41:30] <strong>Giulia Laco:</strong> Apart from Arabic, why not?</p>



<p>[00:41:31] <strong>Nathan Wrigley:</strong> Oh, so it is, it&#8217;s just style. It&#8217;s not from the point of view of readability or legibility?</p>



<p>[00:41:37] <strong>Giulia Laco:</strong> No. New frontiers of typography.</p>



<p>[00:41:39] <strong>Nathan Wrigley:</strong> Oh, that is interesting.</p>



<p>[00:41:40] <strong>Giulia Laco:</strong> But that was one point, but for Arabic might be for readability purpose. That&#8217;s why I mentioned it.</p>



<p>[00:41:46] <strong>Nathan Wrigley:</strong> Honestly, this is such a fascinating subject. Unfortunately, we&#8217;re running out of time. Where would we go if we&#8217;ve been inspired by the talk that you&#8217;ve given today to me? Have you got any tips or places, websites to go to? If people are curious, where would you send them?</p>



<p>[00:42:03] <strong>Giulia Laco:</strong> Okay. There are plenty of places and topography has been receiving quite an attention lately on the web. I&#8217;m always talking about on the web. But you can start with books from the tradition of typography. There are, I don&#8217;t know, from the sacred book of yypography, Robert Bringhurst, The Elements of Typographic Style. That&#8217;s a really nice starting point. Well, it&#8217;s not only a starting point.</p>



<p>Erik Spiekermann&#8217;s, Stop Stealing Sheep and Find Out How Type Works. It&#8217;s very funny name. It has a history. I won&#8217;t spoiler it.</p>



<p>Or I really, really liked the book by Richard Rutter, that is more on the web. It&#8217;s called Web Typography. It&#8217;s a manual on that.</p>



<p>Or otherwise you can follow Jason Parmental that has been making a lot of experiments. It depends which part are you interested in.</p>



<p>[00:42:59] <strong>Nathan Wrigley:</strong> You&#8217;ve given three or four things there. There&#8217;s probably something to get teeth into. And what about you? Where would we find you if people have listened to this and quite fancy having a chat with you about all this. Where do you hang out online?</p>



<p>[00:43:09] <strong>Giulia Laco:</strong> Quite everyone. Maybe on LinkedIn, maybe you can reach me there so it&#8217;s better.</p>



<p>[00:43:14] <strong>Nathan Wrigley:</strong> I will find your LinkedIn profile and I will link to that in the show notes. So let&#8217;s wrap it up there. Giulia, thank you so much for chatting to me today. Honestly, a real eye-opener. I&#8217;ve enjoyed that a lot.</p>



<p>[00:43:24] <strong>Giulia Laco:</strong> Thank you. Me too.</p>
</div>



<p>On the podcast today we have <a href="https://www.linkedin.com/in/giulialaco/">Giulia Laco</a>.</p>



<p>Giulia is a web designer and developer who has been working on the web since the mid 1990s. Her primary interests are web typography &amp; font design. In addition to project development, she is a consultant and a trainer, mostly working with CSS, web fonts and web typography.</p>



<p>This is the last of our podcasts from WordCamp Europe 2023. I spoke to Giulia in Athens because she had just finished her presentation entitled “Typographic readability in theme design &amp; development”.</p>



<p>In this session she explored how designers can assist with the readability of websites through careful consideration of the fonts they choose, and why they choose them.</p>



<p>It turns out there’s quite a lot to consider, and if you’ve not given this topic much thought in the past, you’ll perhaps learn something new.</p>



<p>We begin the podcast talking through how, at the start of the web, we were making do with a limited range of tools to help us make typographic choices. There were no web fonts available, but that started to change around 2010. Now we have access to hundreds of fonts and need to be mindful that some fonts can pose readability challenges for some users of your website.</p>



<p>Giulia talks about the fact that the manner in which we read has changed since the dawn of the internet. Many people now mostly consume small passages of text, which need to be considered in a different way to longer writing.</p>



<p>Concentrating upon the letters in the Latin alphabet, we talk about the ways in which readers typically break up words into smaller units, and the fact that the way letters are shaped can make them easier to parse. There’s some technical language here, ligatures, X-height, apertures, and more, which tell us about the shaping and spacing of letters. Giulia explains the current state of research into how these characteristics of fonts can affect readability.</p>



<p>We talk about whether or not there are fonts which are more readable than others. Is there a collection of fonts which you can use and be confident that you’re going to make it easy for all users of your websites?</p>



<p>Giulia talks about how designs need to consider the spaces into which text is put. Most people have a proclivity for the order in which they view a page, and knowing about this path across the page can help your readers access the text. The width of the text is also important; you want people to be able to read from side to side without having to move their head. How does this work across different device sizes, and what can be said about text which runs from right to left, or top to bottom?</p>



<p>We round off the conversation with Giulia telling us where we can find out more, as well as some of the thought leaders in this space.</p>



<p>It’s a fascinating conversation about a subject that often gets overlooked. Website designers, this episode is for you.</p>



<h2 class="wp-block-heading">Useful links.</h2>



<p>Giulia&#8217;s WordCamp Europe 2023 Session &#8220;<a href="https://europe.wordcamp.org/2023/session/typographic-readability-in-theme-design-development/">Typographic readability in theme design &amp; development</a>&#8220;</p>



<p><a href="https://thereadabilityconsortium.org/">The Readability Consortium</a></p>



<p><a href="https://fonts.google.com/specimen/Amatic+SC">Amantic Small Caps font</a></p>



<p><a href="https://djr.com/">David Jonathan Ross&#8217; website</a></p>



<p><a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Accessibility Guidelines website</a></p>



<p><a href="https://en.wikipedia.org/wiki/Bruno_Maag">Bruno Maag Wikipedia page</a></p>



<p><a href="https://fonts.google.com/">Google fonts</a></p>



<p><a href="https://archive.org/details/elementsoftypogr0000brin">Robert Bringhurst&#8217;s The Elements of Typographic Style</a></p>



<p><a href="https://www.oreilly.com/library/view/stop-stealing-sheep/9780133441147/">Erik Spiekermann&#8217;s Stop Stealing Sheep and Find Out How Type Works</a></p>



<p><a href="https://book.webtypography.net/">Richard Rutter&#8217;s Web Typography</a></p>



<p><a href="https://rwt.io/">Jason Parmental&#8217;s website</a></p>



<p><a href="https://www.linkedin.com/in/giulialaco/">Giulia&#8217;s LinkedIn page</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:"Wed, 26 Jul 2023 14: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:44;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:53:"WordPress.org blog: WordPress 6.3 Release Candidate 2";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:35:"https://wordpress.org/news/?p=15460";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:69:"https://wordpress.org/news/2023/07/wordpress-6-3-release-candidate-2/";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:7320:"<p>WordPress 6.3 RC2 is ready for download and testing.</p>



<p><strong>This version of the WordPress software is under development.</strong> <strong>Please do not install, or run, or test this version on production or mission-critical websites.</strong> Instead, you should evaluate RC2 on a test server and site.&nbsp;</p>



<p>While release candidates are considered ready for final release, additional testing and use by the community can only make it better.</p>



<p>WordPress 6.3 is scheduled for release on August 8, 2023 – just two weeks from today.</p>



<p>Get an overview of the <a href="https://make.wordpress.org/core/6-3/">6.3 release cycle</a>, check the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/6-3/">6.3-related posts</a>, review <a href="https://wordpress.org/news/2023/06/wordpress-6-3-beta-2/">new features in WordPress 6.3</a>, or <a href="https://wordpress.org/news/2023/07/wordpress-6-3-live-product-demo-highlights-recording/">watch a recorded demo</a>.</p>



<p>Developers and extenders should review the <a href="https://make.wordpress.org/core/2023/07/18/wordpress-6-3-field-guide/">comprehensive WordPress 6.3 Field Guide</a> for detailed technical notes regarding new features and improvements.&nbsp;&nbsp;</p>



<h2 class="wp-block-heading">RC2 Highlights</h2>



<p>Since the RC1 release on July 18, 2023, there have been approximately 15 issues resolved in <a href="https://github.com/WordPress/gutenberg/commits/wp/6.3">Editor</a> and <a href="https://core.trac.wordpress.org/query?status=accepted&status=closed&changetime=07%2F18%2F2023..07%2F25%2F2023&milestone=6.3&col=id&col=milestone&col=owner&col=type&col=priority&order=id">Trac</a>.</p>



<p>Notable updates for this release include:</p>



<ul>
<li>Footnotes will be reverted or restored with post revisions (<a href="https://github.com/WordPress/gutenberg/pull/52686">#52686</a>).</li>



<li>Distraction free adds a missing command in the site editor (<a href="https://github.com/WordPress/gutenberg/pull/52868">#52868</a>).</li>



<li>Global styles revisions will display text if no revisions are found (<a href="https://github.com/WordPress/gutenberg/pull/52865">#52865</a>).</li>



<li>The About Page has been completed (<a href="https://core.trac.wordpress.org/ticket/58067">#58067</a>).</li>



<li>The About Page now includes a “Get Involved” section (<a href="https://core.trac.wordpress.org/ticket/23348">#23348</a>).</li>



<li>The dark mode option has been restored in the block editor iframe for Twenty Twenty-One (<a href="https://core.trac.wordpress.org/ticket/58835">#58835</a>).</li>



<li>Max height value was fixed in the image scaling in the Edit Media screen (<a href="https://core.trac.wordpress.org/ticket/50523">#50523</a>).</li>



<li>Additionally, some issues regarding internationalization were addressed (<a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58879" target="_blank">#58879</a>, <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58067" target="_blank">#58067</a> and <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/ticket/58864" target="_blank">#58864</a>).</li>
</ul>



<h2 class="wp-block-heading">Test features in WordPress 6.3</h2>



<p>Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether you have experience or not. While testing the upgrade process is essential, trying out new features is too.&nbsp;</p>



<ul>
<li>Encountered an issue? Please report it to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta area</a> in the support forums. If you are comfortable writing a reproducible bug report, you can <a href="https://core.trac.wordpress.org/newticket">file one on WordPress Trac</a>. You can also check your issue against a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</li>



<li>New to testing? This <a href="https://make.wordpress.org/test/2023/06/27/help-test-wordpress-6-3/">detailed guide</a> is a great place to start if you’ve never tested a beta/RC release.</li>



<li>Want to know more about testing releases in general? Follow along with the <a href="https://make.wordpress.org/test/">testing initiatives in Make Core</a> and join the <a href="https://wordpress.slack.com/messages/core-test/">#core-test channel</a> in <a href="https://wordpress.slack.com/">Making WordPress Slack</a>.</li>
</ul>



<h2 class="wp-block-heading">Vulnerability bounty doubles during the Beta/RC phases</h2>



<p>The monetary reward for reporting new, unreleased security vulnerabilities is doubled between the Beta 1 release and the final release candidate (RC). Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the <a href="https://hackerone.com/wordpress">HackerOne page</a> and in the <a href="https://wordpress.org/about/security/">security white paper</a>.</p>



<h2 class="wp-block-heading">Get WordPress 6.3 RC2</h2>



<p>You can test WordPress 6.3 RC2 in three ways:</p>



<ul>
<li><strong>Option 1:</strong> Install and activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).</li>



<li><strong>Option 2: </strong>Direct download the <a href="https://wordpress.org/wordpress-6.3-RC2.zip">RC2 version (zip)</a>.</li>



<li><strong>Option 3:</strong> Use the following WP-CLI command:<br /><code>wp core update --version=6.3-RC2</code></li>
</ul>



<h2 class="wp-block-heading">Thanks to WordPress plugin and theme developers</h2>



<p>Do you build plugins and themes? Your products play an integral role in extending the functionality and value of WordPress for users of all types worldwide.&nbsp;</p>



<p>Hopefully, you have already tested your themes and plugins with WordPress 6.3 betas by now. With RC2, you will want to continue your testing and update the “<em>Tested up to”</em> version in your plugin’s readme file to 6.3.&nbsp;</p>



<p>If you find compatibility problems, please post detailed information to the <a href="https://wordpress.org/support/forum/alphabeta/">support forums</a>.</p>



<h2 class="wp-block-heading">Help translate WordPress</h2>



<p>Do you speak a language other than English? ¿Español? Français? Português? Русский? 日本? <a href="https://translate.wordpress.org/projects/wp/dev">Help translate WordPress into more than 100 languages.</a></p>



<h2 class="wp-block-heading">Haiku for RC2</h2>



<p>Time is nearly here<br />WordPress shines thanks to you all<br />Let’s get testing, dear</p>



<p><em>Thank you to the contributors who collaborated on this post: <a href="https://profiles.wordpress.org/priethor/">@Priethor</a></em>,<em> <a href="https://profiles.wordpress.org/audrasjb/">@AudrasJb</a>, <a href="https://profiles.wordpress.org/davidbaumwald/">@DavidBaumwald</a>, <a href="https://profiles.wordpress.org/dansoschin/">@DanSoschin</a>, <a href="https://profiles.wordpress.org/jpantani/">@JPantani</a></em> and <em><a href="https://profiles.wordpress.org/meher/">@Meher</a></em>.</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, 25 Jul 2023 16:43:13 +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:10:"Meher Bala";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:45;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:77:"WordCamp Central: WordCamp Malaysia 2023 is Looking for Speakers and Sponsors";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:39:"https://central.wordcamp.org/?p=3240139";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:102:"https://central.wordcamp.org/news/2023/07/wordcamp-malaysia-2023-is-looking-for-speakers-and-sponsors/";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:2991:"<img src="https://malaysia.wordcamp.org/2023/files/2023/06/WCMY-2023-Feature-Image-fb.png" alt="" />



<p>WordCamp Malaysia 2023 is set to take place on 8-9 September 2023 at the Cheras North International Convention Centre (CNICC) in Kuala Lumpur, Malaysia. The first ever WordCamp Malaysia promises to be an unforgettable gathering, offering a platform for knowledge sharing, networking, and community building.</p>



<img src="https://i0.wp.com/malaysia.wordcamp.org/2023/files/2023/06/CNICC-Cheras-North-International-Convention-Centre-edited.jpg?resize=680%2C382&ssl=1" alt="" class="wp-image-1017" />



<p>Situated near the city center, CNICC provides convenient access to major transportation hubs, allowing attendees to make the most of their time in Kuala Lumpur. With a plethora of nearby amenities and attractions, visitors can immerse themselves in the city’s rich cultural experiences, explore its iconic landmarks, indulge in its diverse culinary scene, and even venture into the nearby natural parks.</p>



<img src="https://i0.wp.com/malaysia.wordcamp.org/2023/files/2023/06/IMG_0612.jpg?resize=1024%2C683&ssl=1" alt="" class="wp-image-990" />



<p>The organizing team behind WordCamp Malaysia 2023 is actively seeking speakers who can share their valuable insights, expertise, experiences, and inspiring stories with the WordPress community. If you have a passion for WordPress and a desire to contribute to its growth, this is your chance to shine. Interested individuals can&nbsp;<a href="https://malaysia.wordcamp.org/2023/call-for-speakers/">submit speaker proposals now</a>. Don’t miss the opportunity to be part of this prestigious event and make an impact on the WordPress community in Malaysia.</p>



<img src="https://i0.wp.com/malaysia.wordcamp.org/2023/files/2023/06/HRX00555.jpg?resize=1024%2C683&ssl=1" alt="" class="wp-image-989" />



<p>In addition to speakers, WordCamp Malaysia 2023 is also actively seeking sponsors to showcase and elevate their brands and products to the WordPress community in Malaysia. This is an exceptional opportunity for businesses and organizations to gain exposure, connect with a highly engaged audience, and demonstrate their commitment to supporting the WordPress ecosystem. To explore the various sponsorship packages available and learn more about the benefits of becoming a sponsor, interested parties can visit&nbsp;<a href="https://malaysia.wordcamp.org/2023/call-for-sponsors/">the call for sponsors page</a>.</p>



<p>To stay updated and learn more about WordCamp Malaysia 2023, visit the official website at&nbsp;<a href="https://malaysia.wordcamp.org/2023/">https://malaysia.wordcamp.org/2023/</a>&nbsp;. The website will serve as your go-to resource for event details, schedules, ticketing information, speaker profiles, and other important announcements.</p>



<p>Don’t miss your chance to be part of WordCamp Malaysia 2023. Submit your speaker proposal or explore sponsorship opportunities today!</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, 25 Jul 2023 12:53:17 +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:10:"Sam Suresh";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:46;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:134:"WordCamp Central: WordCamp Masaka 2023: Celebrating Inclusion, Diversity, and Innovation with WordPress in Uganda’s Pearl of Africa!";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:39:"https://central.wordcamp.org/?p=3166793";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:152:"https://central.wordcamp.org/news/2023/07/wordcamp-masaka-2023-celebrating-inclusion-diversity-and-innovation-with-wordpress-in-ugandas-pearl-of-africa/";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:3351:"<p><a href="https://masaka.wordcamp.org/2023/">WordCamp Masaka 2023</a> is the inaugural WordCamp event in Uganda&#8217;s Greater Masaka region. It will be held on <strong>October 6 and 7, 2023</strong>, at <a href="https://equsat.ac.ug/">Equator University of Science and Technology</a> in Masaka City, Uganda. The event is dedicated to celebrating inclusion, diversity and fostering innovation within Uganda&#8217;s WordPress community.</p>



<p>WordCamp Masaka 2023 will offer a wide range of engaging workshops, informative talks, and student WordPress project showcases designed to cater to attendees of different skill levels. The workshops will provide hands-on learning experiences and practical knowledge to help both beginners and advanced users enhance their WordPress skills. The informative talks will cover a diverse range of topics, providing valuable insights and inspiring discussions. The student WordPress project showcases will offer a platform for attendees to share their WordPress projects, regardless of their skill level, and gain inspiration from the creativity within the community.</p>



<p>In addition to the diverse range of activities, WordCamp Masaka 2023 will include a contributor session dedicated to translating WordPress from English to Luganda. This session will actively engage participants of all skill levels in the translation process, fostering collaboration and empowering Luganda (the most spoken language in Uganda) speakers to access WordPress in their native language.</p>



<h2 class="wp-block-heading">Get Involved</h2>



<ul>
<li><a href="https://masaka.wordcamp.org/2023/tickets/">Purchase Attendee Tickets</a>: Secure your tickets to join the WordPress community in celebrating this inaugural event in the Greater Masaka region, Uganda. Tickets are available for purchase, offering a unique opportunity to engage with like-minded individuals and expand your WordPress knowledge.</li>



<li><a href="https://masaka.wordcamp.org/2023/call-for-sponsors/">Call for Sponsors</a>: Support the first-ever WordCamp Masaka and gain visibility for your company. Explore available sponsorship options to contribute to the success of this event and demonstrate your commitment to the WordPress community.</li>



<li><a href="https://masaka.wordcamp.org/2023/call-for-speakers/">Call for Speakers</a>: Share your expertise, experiences, and insights by applying to be a speaker at WordCamp Masaka 2023. The call for speaker applications welcomes submissions, allowing you to contribute to a diverse range of topics during the event.</li>



<li><a href="https://masaka.wordcamp.org/2023/call-for-volunteers/">Call for volunteers</a>: Apply to be a volunteer and actively participate in the organization of WordCamp Masaka 2023. Volunteering offers a unique opportunity to contribute behind the scenes and play an integral role in the success of this inaugural event.</li>
</ul>



<p>The full list of speakers, session descriptions, and schedule will be published in early September 2023. Be sure to follow us on <a href="https://twitter.com/WordPressMasaka">Twitter</a> and <a href="https://www.facebook.com/WordCampMasaka">Facebook</a> to get the latest updates.</p>



<p>Please don&#8217;t forget to post about this event on your social media handles using the hashtag <strong>#WCMasaka</strong>. </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, 25 Jul 2023 08:50:19 +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:15:"Ssebuwufu Moses";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:47;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";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:47:"WPTavern: Learn How to Use WordPress Playground";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:30:"https://wptavern.com/?p=147137";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:58:"https://wptavern.com/learn-how-to-use-wordpress-playground";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:3358:"<p>WordPress Playground, an experimental project that uses WebAssembly (WASM) to <a href="https://wptavern.com/new-prototype-runs-wordpress-in-the-browser-with-no-php-server">run WordPress in the browser</a>, was <a href="https://twitter.com/dbchhbr/status/1679949344315936769">number 1 on Hacker News</a> recently and was also <a href="https://techcrunch.com/2023/07/18/wordpress-playground-lets-you-run-wordpress-entirely-in-your-browser/">featured on TechCrunch</a>. Word is getting around about how easy it is to fire up a sandbox environment in just a few seconds for testing plugins and themes and even different versions of WordPress and PHP.</p>



<p>Visiting <a rel="noreferrer noopener" href="https://playground.wordpress.net/" target="_blank"><code>playground.wordpress.net</code></a> instantly creates a real WordPress instance with admin access and everything without having to install PHP, MySQL, or Apache. Instead, it runs inside the browser using a SQLite database.</p>



<p>The Playground isn&#8217;t just for developers. It also makes it easy for users who would not ordinarily maintain a local development environment to quickly test plugins or themes they find on WordPress.org, or to just explore new WordPress features in a safe place where you can&#8217;t break anything.</p>



<p>If you have found it difficult to wrap your head around WordPress Playground, Learn WordPress has published a timely new tutorial called <a href="https://learn.wordpress.org/tutorial/how-to-start-using-wordpress-playground/">How to start using WordPress Playground</a>. In this 10-minute video, WordPress Playground creator Adam Zieliński offers a quick demonstration of how to install plugins and themes and customize a site, and how to export design work from a customized theme. He also covers how to download the entire site and import it into a new WordPress instance, and guides users through basic compatibility testing of a theme, by switching the WordPress version on the playground site.</p>



<div class="wp-block-spacer"></div>



<img width="1878" height="1048" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/07/Screen-Shot-2023-07-24-at-6.01.57-PM.png" alt="" class="wp-image-147142" />Learn WordPress Tutorial: <a href="https://learn.wordpress.org/tutorial/how-to-start-using-wordpress-playground/">How to start using WordPress Playground</a>



<p>Developers who want try some more complicated things with this tool can check out the <a href="https://wordpress.github.io/wordpress-playground/docs/apis-overview">Playground API</a> and learn <a href="https://developer.wordpress.org/playground/">how to integrate it with an app</a> in five minutes. It&#8217;s also useful for <a rel="noreferrer noopener" href="https://wordpress.github.io/wordpress-playground/docs/build-your-first-app#preview-pull-requests-from-your-repository" target="_blank">previewing pull requests from a repository</a> or setting up a local WordPress development environment using the <a rel="noreferrer noopener" href="https://marketplace.visualstudio.com/items?itemName=WordPressPlayground.wordpress-playground" target="_blank">VisualStudio Code plugin</a> or <a rel="noreferrer noopener" href="https://github.com/WordPress/playground-tools/tree/trunk/packages/wp-now" target="_blank">a CLI tool called <code>wp-now</code></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:"Mon, 24 Jul 2023 22:09:30 +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:13:"Sarah Gooding";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:"
	
	
	
	
	
	
";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:74:"WPTavern: Mojeek Search Engine Adds WordPress’ Openverse to Image Search";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:30:"https://wptavern.com/?p=147123";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:82:"https://wptavern.com/mojeek-search-engine-adds-wordpress-openverse-to-image-search";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:2259:"<img width="2292" height="1320" src="https://149611589.v2.pressablecdn.com/wp-content/uploads/2023/07/Screen-Shot-2023-07-24-at-1.21.17-PM.png" alt="" class="wp-image-147125" />



<p><a href="https://www.mojeek.com/">Mojeek</a>, a UK-based privacy-oriented search engine, has <a href="https://blog.mojeek.com/2023/07/expanding-mojeeks-image-search-with-openverse.html">added Openverse to its image search</a>. For more than 15 years, Mojeek has provided independent, unbiased search without tracking or building profiles on users. It is one of just a handful of genuine search engines that uses its own technology and algorithms, unlike the metasearch engines that syndicate Bing, Google, and Yandex. In October 2022, Mojeek passed a major milestone of having <a href="https://blog.mojeek.com/2022/10/mojeek-now-six-billion-pages.html">indexed more than 6 billion pages</a>. </p>



<p>The search engine had previously provided Pixabay as the default for its image search with the option to use Bing as an alternative.</p>



<p>&#8220;We have always wanted to eventually get rid of Bing,&#8221; Mojeek Head of Marketing Joshua Long said. &#8220;Due to both Microsoft&#8217;s API pricing decisions, and informed comments by people using Mojeek to search the web, we recently took that step.&#8221;</p>



<p>Openverse&#8217;s openly-licensed media was a natural fit for the independent search engine. In 2021, Creative Commons Search was <a href="https://wptavern.com/creative-commons-search-is-now-openverse">rebranded to Openverse</a> when it came under the umbrella of the WordPress open source project. With more than 700 million Creative Commons licensed and public domain image and audio files, Openverse exceeds Pixabay&#8217;s 4 million+ royalty-free and stock images, greatly expanding users&#8217; abilities to search deeper on more topics.</p>



<p>Although Pixabay is still Mojeek&#8217;s default image search provider, users can change their <a href="https://www.mojeek.com/preferences">preferences</a>, which are set using a local cookie and contain no personal data.</p>



<p>&#8220;This addition is a testament to the utility that Openverse brings, as well as the ease and extensibility when it comes to using its API,&#8221; Long said.</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:"Mon, 24 Jul 2023 20:30:07 +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:13:"Sarah Gooding";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:"
	
	
	
	
	
	
";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:115:"Do The Woo Community: A Deep Dive into Sales Tax for Agencies and Freelancers with Kate Bacholzky and Roger Walker";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=75724";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:66:"https://dothewoo.io/deep-dive-into-sales-tax-agencies-freelancers/";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:464:"<p>Kate Bacholzky from Avalara and Roger Walker from americaneagle.com take you deep into sales tax for yourself and your clients.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/deep-dive-into-sales-tax-agencies-freelancers/">A Deep Dive into Sales Tax for Agencies and Freelancers with Kate Bacholzky and Roger Walker</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</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:"Mon, 24 Jul 2023 09:08: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: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:"*data";a:18:{s:12:"content-type";s:23:"text/xml; charset=utf-8";s:4:"vary";s:46:"Sec-Fetch-Dest, Sec-Fetch-Mode, Sec-Fetch-Site";s:12:"feedburnerv2";s:0:"";s:13:"last-modified";s:29:"Fri, 11 Aug 2023 03:24:12 GMT";s:13:"cache-control";s:46:"no-cache, no-store, max-age=0, must-revalidate";s:6:"pragma";s:8:"no-cache";s:7:"expires";s:29:"Mon, 01 Jan 1990 00:00:00 GMT";s:4:"date";s:29:"Fri, 11 Aug 2023 03:28:09 GMT";s:9:"accept-ch";s:191:"Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Full-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Model, Sec-CH-UA-WoW64, Sec-CH-UA-Form-Factor, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version";s:23:"content-security-policy";s:243:"script-src 'report-sample' 'nonce-Jrl8okST2vgzwKvQOMI68Q' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/RaichuFeedServer/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /_/RaichuFeedServer/cspreport";s:28:"cross-origin-resource-policy";s:9:"same-site";s:18:"permissions-policy";s:173:"ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-form-factor=*, ch-ua-platform=*, ch-ua-platform-version=*";s:26:"cross-origin-opener-policy";s:11:"same-origin";s:16:"content-encoding";s:4:"gzip";s:6:"server";s:3:"ESF";s:16:"x-xss-protection";s:1:"0";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:22:"x-content-type-options";s:7:"nosniff";}}s:5:"build";s:14:"20220126053730";}