In episode 133 of the Gutenberg Changelog Podcast, Birgit Pauli-Haack hosts Faith Ruth Imokol, a Ugandan web developer and longtime Gutenberg advocate, to discuss the Gutenberg 23.6 release and the upcoming WordPress 7.1 update. The episode opens with insights into the WordPress community in Uganda, highlighting their active WordCamp scene and educational initiatives such as the Campus Connect program, which introduces WordPress to students across the country.<\/p>\n
Faith Imokol shares her experience on a recent WordCamp Kampala panel about AI in web development, noting divided perspectives: while some Ugandans are excited about AI\u2019s possibilities, others are concerned about job security and adaptation. She describes her personal transition into using AI as a collaborative development tool, driven by the need for faster production due to heightened competition.<\/p>\n
Discussion moves to WordPress 7.1, covering new features such as customizable viewports via theme.json, expanded notes and commenting capabilities, enhanced SVG icon registration, and improvements to blocks like playlists and tabs. Both speakers are enthusiastic about the collaborative features and the evolving editorial workflow, particularly the granular notes system for streamlined feedback.<\/p>\n
The episode emphasizes community feedback\u2019s role in shaping new releases and encourages listeners to help test upcoming WordPress versions to ensure quality and translatability. The episode closes with practical tips and excitement for ongoing educational outreach and future Gutenberg advancements.<\/p>\n
Show Notes<\/a> \/ Transcript<\/a><\/p>\n Show Notes<\/strong><\/p>\n Upcoming Events <\/p>\n Past 2026 Events<\/p>\n More Developer Notes for WordPress 7.1 <\/p>\n What\u2019s new of Gutenberg 23.6<\/a><\/p>\n The post editor is going full iframe: what block developers need to know before WordPress 7.1<\/a><\/p>\n Video w\/ Ryan Welcher: iframed post editor canvas<\/a><\/strong><\/p>\n Stay in Touch<\/p>\n Transcript<\/strong><\/p>\n Birgit Pauli-Haack:<\/em> Welcome to our 133rd episode of the Gutenberg Changelog Podcast. In today\u2019s episode, we will talk about Gutenberg 23.6 release and some WordPress 7.1. And that should be enough for today. I\u2019m your host, Birgit Pauli Haag, curator at the Gutenberg Times and full-time core contributor to the WordPress Open Source Project sponsored by Automattic. And today I\u2019m very excited that Faith Ruth Imokol joins me. She\u2019s a web developer from Uganda, WordCamp organizer there and speaker, and a Gutenberg advocate since 2018, as long as the Gutenberg Times. And I\u2019m glad she agreed to come on the show and talk through with this release and tell us more about the WordPress community in Uganda. Welcome to the show, Faith. How are you today?<\/p>\n Faith Imokol<\/em>: Thank you very much, Birgit, for having me. I am okay. I\u2019m very fine. Thank you, listeners, for having me as well. I\u2019m excited.<\/p>\n Birgit Pauli-Haack<\/em>: Me too. Me too. It\u2019s such wonderful to have you on the show. So, WordCamp community in Uganda is really busy this year, and it probably was last year as well because there\u2019s a lot of experience there in doing WordCamps. So you, you were in WordCamp Kampala this year.<\/p>\n Faith Imokol<\/em>: Yes.<\/p>\n Birgit Pauli-Haack:<\/em> And you were on a panel session titled AI and the Future of Web Development: The Good, the Bad, and the Ugly. So what were your takeaways? How are the people in Uganda kind of looking at AI and the future of the web?<\/p>\n Faith Imokol:<\/em> Oh, well, the opinions on the future of AI in Uganda and how people view it are quite divided. Many are very hopeful, but some are also a little worried about what is going to become of them, especially when it comes to their jobs with AI. There\u2019s a lot of talk on AI taking over. There\u2019s a lot of talk on, okay, what do we need to do? Do we still need to continue with the way that we\u2019ve been working or should we transition into full AI mode working with AIs? So there\u2019s a lot of speculation around AI. And during the panel session, very many people had very many questions around that. They wanted reassurances on, especially when it comes to their jobs. Do we still have our jobs as developers? Can we still maintain the work that we are doing right now? Can we still continue using the tools that we are working with right now, or should we leave them and just take on AI and start working with AI. So it was a panel that was there to encourage people, to also highlight and offer corrections on some of the misinformation that was going, that has been spreading and going around in the community, especially in the WordPress community. Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: So how, you don\u2019t have to go into details, but how are you approaching AI for your work?<\/p>\n Faith Imokol<\/em>: Personally, I could say that I\u2019ve been forced in some way to use AI \u2019cause I\u2019m using it more as a pair working along with it in my development. And I\u2019ve been forced to use it. Initially, I was a little hesitant. I like to do my own discoveries. I like to go through my own work and do my own troubleshooting. But with the AI coming in, it forced some of the teams that I was working in to have to increase the rate at which they produce and release applications. Why? Because the competition has now stiffened. If you\u2019re not using AI to work faster, someone else is going to produce what you\u2019re doing and they\u2019re going to release it, and then you\u2019re going to be left behind. So I kind of, at some extent, have had to take a back seat on doing my own personal investigations and leaving those to my own personal time. But when it comes to work, it\u2019s something that I\u2019ve fully incorporated into my day-to-day working. Yeah, still, I still apply my own knowledge as well. I don\u2019t leave everything to AI to do it.<\/p>\n Birgit Pauli-Haack<\/em>: That\u2019s certainly quite prudent, yeah, to see how AI can really go wrong and you don\u2019t know which tangent they go on. Yeah. And I have found, well, I\u2019m using AI maybe a year now for a lot of different things and I have found that there\u2019s no taste. Yeah. It has no feelings, of course. Yeah. And it has no empathy for anything. Yeah. So, human judgment is even more needed for anything that is released that was done by AI. And I think it becomes more and more clear the longer we practice with it. First, it\u2019s a fantastic tool. Yeah, it kind of gets you to certain things faster, but it also is very verbose in code, in reviews, in analysis, and you really need to kind of slow it down and figure out what\u2019s really important. And that it can\u2019t do. It doesn\u2019t know what\u2019s important, what\u2019s not important. Everything is the same.<\/p>\n Faith Imokol<\/em>: I kind of think it\u2019s like a very smart child who thinks they know everything, but they\u2019ve not lived through the experience of what an adult knows.<\/p>\n Birgit Pauli-Haack:<\/em> So they still need guidance. That\u2019s a good analogy. Yeah. It\u2019s like a young person who just graduated high school and knows everything.<\/p>\n Faith Imokol<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, I was that when I graduated from high school. I knew everything. But back to the Uganda community, the next WordCamp is in Jinja. Is that how you pronounce it? From the 19th to the 20th of September. It\u2019s in the Civil Service College in Jinja. Just, just in case you dear listeners are in the region and you wanna go to a WordCamp in Uganda. But there\u2019s also running from now to December several WordPress Campus Connect events with 25 schools, each one with at least 100 participants, 25 schools, colleges, or universities. And the program will bring practical, as it aims to, practical WordPress learning sessions to selected schools across Central and Eastern Uganda. And students will be introduced to the basics of WordPress, how websites are built, how to create and publish content and how they can use WordPress for school projects, personal portfolios, blogs, business ideas, and future technology careers. So these are the Campus Connect from the WordPress Education Program that started, I think, in the end of \u201924 and has now run through \u201925 and half of \u201926. So, and Uganda is really taking to it and getting a lot of students involved with WordPress.<\/p>\n Faith Imokol<\/em>: Yeah, we\u2019re working hard to see that the future, the next generation that comes into the workforce is not too ill-equipped like the way we were. So these programs that we\u2019re starting as the WordPress community are out to help the next, the coming, the young generations that are coming in, for them to know, to know the different skills that they can take on and to know that there are different tools that they can also learn that can help them. So it\u2019s really a very amazing initiative that was started by Mr. Dumba and Moses.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Yeah. And they are still completely involved and totally immersed in that field. Yeah. Stephen Dumba also organized a website project competition for elementary schools, high schools, and colleges. And they had, I think, 20 teams in total there. And then each team had to create a website for a community project that is local and was very important to the community and how to communicate those problems and solutions. And that was also in June. Then there was WordCamp Osaka, Campus Connect in Osaka, and then Campus Connect in Kakumiro, if I pronounce all that right.<\/p>\n Faith Imokol<\/em>: Yes. Yeah, you\u2019re trying.<\/p>\n Birgit Pauli-Haack<\/em>: I\u2019m trying. Yeah, I\u2019m not succeeding. Okay.<\/p>\n Faith Imokol<\/em>: Your pronunciations are very good.<\/p>\n Birgit Pauli-Haack<\/em>: Okay. Yeah. Yeah. So I\u2019m really excited about what\u2019s happening on the African continent in the various communities. Uganda is one. I think another very active one is Kenya. And there was one in Rwanda. I don\u2019t know how active they are now. But yeah, I\u2019m really excited about that. <\/p>\n So we have a few announcements. 7.1 is coming Today is July 30th. So in about 3 weeks, we will have a final release of 7.1. August 19th is the release date. And it will be released on the last day of WordCamp US. The Source of Truth, that\u2019s the book about things, yeah, that is published on the Gutenberg Times. This time it\u2019s about 39 minutes to read and 7,000 words. It\u2019s really an ebook or something like that. The table of contents, it\u2019s very detailed. So you can jump into the sections that you want. Okay. That you need. And the developer notes are coming out for those who need more technical details. And there was one from the client-side media processing, the text shadow support for global styles. <\/p>\n The media library infinite scroll is coming back and is enabled by default, but there is a filter to disable it for those who need it disabled. And then there are now editable blocks inside custom HTML blocks. That\u2019s a very interesting construction. So if you\u2019re interested in that, we share, of course, the developer links in the show notes. There are some editor component updates that are interesting for those who are using those for development in admin as well as in block editor. And then a lot of people have been waiting for that part, registering and rendering SVG icons and icon collections. The developer note is out and it will come to 7.1. And then there\u2019s also a mid-width block support and background gradient block support. So there are some things for the global styles that are only available through the theme.json. There is no UI yet for it because it just needs to simmer a bit and kind of brew a bit before developers are thinking about the UI. Is there anything that excites you from 7.1 from, from these developer notes yet?<\/p>\n Faith Imokol<\/em>: Yeah, well, I really, really, really enjoy the new features that are coming in, especially the one thing that I\u2019ve really been excited about is the collaboration tools. So I\u2019m really looking forward to working more with those and seeing how they will help people collaborate on different WordPress projects.<\/p>\n Birgit Pauli-Haack<\/em>: Yes. Yeah, yeah, yeah. Unfortunately, the real-time collaboration has been punted again. Or it was clear that it would not come to 7.1 because it has these underlying server technical approaches that depending on where the site is hosted, it needs to have a different approach. Or in enterprise, yeah, it\u2019s a different approach and all that. And they haven\u2019t narrowed down what the default value could be. But what I really like are the e-syncer. So it\u2019s very rare that I\u2019m sitting there and somebody else is sitting on their computer and we\u2019re on the post or on the site at the same time. Mostly it\u2019s because, yeah, I work remotely in Europe time zone with a lot of people in the United States that\u2019s 6 hours behind. It\u2019s more asynchronous. And I think the notes section is really getting some great love there that came in 6.9 and 7.0 and now has additional features. Yeah, I really like that.<\/p>\n Faith Imokol<\/em>: Yeah. I see it growing. I see it growing into something much bigger. So I\u2019m looking forward to whatever is coming ahead.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, yeah, I could actually see that. But the current publishing flow at the official developer blog is that the writers do a draft in Google Docs, and then 2 reviewers come in and help edit that or streamline it or shorten it or whatever, comment on it. And then the writer has to make all the changes after those feedbacks and then take the whole Google Doc and put it into a blog. So with the notes feature, we can cut out the Google section part because we can now comment on the, on writing on the blocks. Yeah, we can mention people and we can resolve issues from the notes. So it\u2019s coming really close to streamlining that, our process. All right. <\/p>\n What\u2019s released? WordPress 7.1 Beta 4 came out. That\u2019s the last release before the release candidate next week on August 5th. August 5th is also the deadline for the rest of the dev notes, the developer notes for that, and the Field Guide will come around that as well. And that\u2019s also the time where string freeze happens. Release candidate is still 14 days away. The translators need to get into it. So string freeze means there are no new strings that come in that need to be translated. Because the WordPress ecosystem has a huge army of translators. And by the time the release comes out, it will be translated into about 70 languages, almost 100% from the new release. And that\u2019s huge. But we need to give those translators a time on the polyglots teams to actually get it all in. And this is not a small release, although it wasn\u2019t a long pipeline there. Yeah. <\/p>\n And if you want to test it, this is now the time to go to the Make\/Test team and follow the Help Test WordPress 7.1. It\u2019s also linked from the release post from the news section because it gives you an opportunity to not only dive into the new features, but it also gives you instructions and a video and you learn quite a bit about it. And if you find things that are not right, you surface that. And that is not only surfaced for yourself, but it\u2019s also surfaced for millions of other people who are going to get this new version. And if you are fast enough and the problems are small enough, they might get the fixes in before the final release. So if you wanna help and contribute quite impactful, help test WordPress 7.1. It\u2019s my call for action for this show. Did you get a chance to dive into some of the features yet?<\/p>\n Faith Imokol:<\/em> Yes, I did. I did try testing them as well locally. And yeah, it\u2019s really impressive. The work that is being put into this is very, very impressive.<\/p>\n Birgit Pauli-Haack<\/em>: All right. So this brings us to the Gutenberg plugin release 23.6. And 23.6 is also the last feature release for 7.1. So everything that made it into the 23.6, almost all of it will come to 7.1. Everything that\u2019s enhancements in the next release will not make it because we are past the beta site. But all the bug fixes that you find in your testing and you report them as issues or on the support forums have a chance to get in. Yeah. So let\u2019s start with that. <\/p>\n The first item that I want to point out is that you can now set the viewport for tablet and mobile values in theme.json. What does that mean? So the Gutenberg plugin editor had hardcoded viewports for what\u2019s considered desktop, what\u2019s considered tablet, and what\u2019s considered mobile. And everybody had to work around those if you had a different idea about those viewports.<\/p>\n Faith Imokol:<\/em> Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: But now you can just set the setting in your theme.json for your theme and then everything will fall into place.<\/p>\n Faith Imokol<\/em>: I think this gives us much more flexibility because initially with the default viewpoints that are set by WordPress, all sites end up having the same, could I say breakpoints?<\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol:<\/em> I think personally I prefer to, I refer to them as breakpoints. for different screens that is in mobile responsiveness. And this is going to allow us to be able to customize this to our own liking so that our themes can be uniform with, uh, can have settings that have been preset by us than having the default ones that WordPress has added. And I think as I was going through the changelog, I came through the discussion because the viewports allow you to set the tablet and the mobile view. And there was a discussion of what could happen if someone set the tab view to have a smaller, should I say, breakpoint than the mobile screen. What could happen by that? And it was quite interesting that at that point we reverted back to the defaults.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol:<\/em> Yeah. So it\u2019s a good thing to have in the background, as I don\u2019t think everyone will abide by the rules, but As you\u2019re working with this and anyone who gets to work with this, I think you have to keep that in mind that you, you\u2019re setting different breakpoints for different devices and tablets are larger than mobile devices.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. Yeah. That\u2019s the assumption that tablets are larger than mobile devices. So if someone puts a mobile breakpoint in that\u2019s bigger than the tablet, that can probably just be a mistake or something like that. Yeah. So having a fallback to not ruin the whole site just because of a wrong value in the theme.json is probably a good measure, yes.<\/p>\n Faith Imokol<\/em>: I\u2019m thinking we now have these new Samsung phones that have come out, the flip phones. Does it become a tablet? I\u2019m still trying to understand.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, it\u2019s a good question. So I saw a discussion, an issue that you can\u2014 that on Gutenberg to think through the consequences if you have more than 3 breakpoints. Yeah. Can we have multiple sizes? I mean, at one point it really becomes a usability issue. How would an editor or a user, keep in mind that, yes, I saw plugins that have 6 breakpoints and it\u2019s really hard to control those because you never know where you have all the changes made. Yeah, and come back to it when you, when you start out, it\u2019s probably easier to kind of think through it. But once you have a site and you need to make some changes, it\u2019s very hard to figure out where all those changes have to be made. So it doesn\u2019t become better with more breakpoints. I think that was a point why the Gutenberg developers started out with really honing in on the intrinsic designs, that there\u2019s actually a seamless adaption to the screen sizes. And that\u2019s where the Samsung folding phone probably will come in.<\/p>\n Faith Imokol:<\/em> Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: That you\u2019re not fixed on a breakpoint to just say, okay, yeah, it takes the space it has. Yeah. And rather do content queries rather than media queries. Yeah.<\/p>\n Faith Imokol:<\/em> I hope we see how, what else will be added to this, cuz I think more is going to come up and shall have more settings being added to this.<\/p>\n Birgit Pauli-Haack<\/em>: For sure. Yeah.<\/p>\n Faith Imokol<\/em>: So, uh, notes, this is, features that I\u2019m really excited about. It shows you how powerful Gutenberg has gotten. Being able to add notes. So the upcoming features, one of the features that we have will be auto-completing mentions. This is you\u2019ll be able to tag an individual, a user, onto the post, and when you tag them, the prompt will be able to\u2014 will allow you to select from\u2014 it will pop up a list of the available users and you\u2019ll be able to select the ones that you want to tag. And when they are tagged on the front end, you\u2019ll be able to see that they are highlighted, that the tag name is\u2014 their display name is highlighted. So this is a feature that I\u2019m really, really impressed by and hope to see how far it grows more because I\u2019m seeing all the different possibilities that it can be used in, things like notifications. And I think this is one of the features that is being incorporated for the collaboration right. Later, even as we\u2019re collaborating, because you can tag someone within the notes, but now you\u2019re also doing inline, you know, you\u2019re able to tag people within, within the context of the content that you\u2019re creating. Yeah. So this is something that I\u2019m really impressed by and looking forward to see how far that can be taken.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. And now what a lot of people were waiting for, that you can actually highlight partial text and have those notes in the sidebar about a certain portion of a text and not just a whole paragraph block. And now you can also have multiple notes per block as well. So if you have here, the paragraph is, I don\u2019t know, 10 lines long and you have something you want to note about the first line or the first 6 words or so, and then in the middle is something, and you could have notes for each one of them that then show up in the section. So it makes it much easier to streamline the conversation and to be really granular in what the notes are about or the comments are about. Yeah. And it now has a resolved divider. And so when you check a note that is resolved, it pushes it further down and has a little divider in the sidebar. So yeah, it really comes well together, this note section. Yeah. It really starts growing up.<\/p>\n Faith Imokol:<\/em> Yeah, I\u2019m seeing lots and lots of ways that this is going to, because I\u2019m thinking with the resolver, adding the resolved divider, I\u2019m seeing this going into something like project management and we\u2019re able to add even more other statuses possibly besides just the resolved divider. Very impressive.<\/p>\n Birgit Pauli-Haack<\/em>: I can see some plugin opportunities there to kind of collect all those and have a separate kind of setup for a whole editorial workflow where the main editor just kind of looks through what are the posts and what are the comments. And you can see, okay, or you come in as an editor and see, oh, I need to go through all the comments where I\u2019m tagged. Yeah. So these kinds of things, I think that would be an interesting feature set to add to it. Not sure that core is actually gonna aim for it. So that might be plugin territory because, territory, because it\u2019s a very finite use case for that.<\/p>\n Faith Imokol:<\/em> Yes.<\/p>\n Birgit Pauli-Haack<\/em>: The next item is by default, the admin bar is now shown for post and site editor as well. Once you\u2019re logged in, you see a black bar on your website on top of it with some links where you can jump in different places, and that is coming to 7.1 as well. And now that admin bar has been streamlined and kind of combines the site editor navigation as well with the admin bar. And it\u2019s really, it\u2019s a nice feeling. It kind of feels now a little bit more consistent, and you can access the things that you could access before. Yeah, you have your site icon. You also have the big W, and that was in there before, but the header of the site editor is now smaller or the block editor. And it\u2019s all coming together quite nicely.<\/p>\n Faith Imokol<\/em>: Yes. Coming in version 7.1, we are having, I could say there\u2019s a kind of more a mix of both dynamic and static content blocks, block content, where we are going to be able to have what WordPress offers. I don\u2019t know if this is the right way to present this, but currently WordPress offers you a way of providing or creating content that is you\u2019re either working with blocks or you\u2019re working with your default static HTML. And this new feature of adding inner content is going to allow us to be able to add dynamic content within static content. So you\u2019ll be able to work with your HTML and still add editable content within your static content. that is your normal HTML, but within it you have an editable, let me say, paragraph block within there. So the other content remains static, but within it you have your inner content. And we\u2019ve been provided a new feature called inner content that we can use to set this up.<\/p>\n Birgit Pauli-Haack<\/em>: Mm-hmm.<\/p>\n Faith Imokol<\/em>: That is, if you\u2019re working with if you\u2019re creating your own code, you\u2019ll be able to add this inner content feature and we\u2019ll be able to allow you to create static content that has HTML blocks within it.<\/p>\n Birgit Pauli-Haack:<\/em> Yeah. No, very well described. Yeah, I can see how that is really helpful, especially for patterns that you have editable sections and you say static, I say hardcoded. Yeah, don\u2019t touch things as an editor. You\u2019re right. This comes to 7.1 as well. And there are developer notes out. So it will be in the show notes so you can see the technical implementations for that in 7.1.<\/p>\n Faith Imokol<\/em>: Yeah, it\u2019s, it\u2019s, it\u2019s, it\u2019s quite a powerful tool, I think, because it\u2019s\u2014 I see it becoming also\u2014 it\u2019s some\u2014 one of those features that I feel can be added onto in different ways because you\u2019re now not just building something that is strict, but you can modify it to appeal to different scenarios and different use cases. As current cases, either you have one block that is doing one particular thing, but now here you\u2019re able to work with blocks and also normal HTML. So it gives, as a developer, I feel it gives me some power. I\u2019m not just leaving everything to the blocks to be doing everything, but it gives me some power to be able to add different content styles. Yes.<\/p>\n Birgit Pauli-Haack<\/em>: Nice.<\/p>\n Faith Imokol:<\/em> Yeah. Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: The next one is part of the Icons API. Now 23.6 Gutenberg plugin now has PHP methods To render inline SVG icons from the registry. So that can also be used in PHP-only blocks or in other templates and all that. So that also comes in 7.1, is a new API for registering icons in WordPress, SVG icons and icons collections that came in with 23.6.<\/p>\n Faith Imokol:<\/em> I can take the next one.<\/p>\n Birgit Pauli-Haack<\/em>: Mm-hmm.<\/p>\n Faith Imokol:<\/em> Coming in 7.1. So we had some issues with the backgrounds in some of the blocks, that is the accordion, the post content block, the quotes block, the verse block. And in this, there were issues with the way the images were being handled, that is in the CSS, in the blocks, in the block CSS, which ended up blocking the gradient. It ended up breaking the gradient. So kind of could say that there was a conflict. In how the background images and the gradients were being handled. So it was causing a bug with our gradients. So this has been fixed in how the background images and the gradients are handled. And so you\u2019ll not be able to see conflicts when you apply a gradient onto any of your blocks, especially the blocks that we have stated, that is the block quotes accordion, the pull quotes, the verses and post content blocks.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. And actually, this fix also gives you a totally new feature. Now you can overlay the gradient onto the background image, and that gives a whole new way of designing things. And if you look at some of the PRs that are coming through and with a screen share there, it\u2019s actually quite nice that the image kind of feels a little bit more lively when there\u2019s a gradient on top of them. So it\u2019s really good. <\/p>\n Yeah, the latest post block received layout and block spacing support. The latest post block was historically just a re-rendering as a block from the widget section of WordPress prior to that, and hasn\u2019t gotten a whole lot of love after that because the query block is kind of also a latest block kind of thing. But it now has layout and block spacing support so you can fit it in other places quite nicely. Speaking of the query block, it now has an option to exclude the current post from the query block, from the list of blocks, so to speak. So this gives a better feel for your single post template where you can say, okay, so this is the post with the post content, but then underneath you can add a list of blocks from either the same category or for the same taxonomy and exclude the current block. Up until now, it would always also render the current block if it had the same taxonomy. So I think that\u2019s a feature that a lot of people actually were waiting for. It sounds so minuscule. Yeah, but it\u2019s actually pretty powerful.<\/p>\n Faith Imokol<\/em>: So we have a new feature that has been added to the cover block. And this will allow users to restrict the kind of videos that they want to be added to their cover blocks. Initially, currently what we have is that WordPress has a variety of different video providers that you can embed into your cover block, but this will allow you to restrict. So if you only want to display only YouTube videos, you can add a restriction that we only need YouTube videos being uploaded in our cover block. While you can switch this up to any that you want, as opposed to just allowing it to have any video embedded provider adding the videos. So this is one of those features. I think it gives us more control over what you want. Could I say, when it comes to different service providers, they provide a whole different interface and layout for how their videos play out, and this will allow something like uniformity. <\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol<\/em>: Because I think it can be a little strange when you have your website on\u2014 some videos are playing like YouTube content and then it switches into another format and it\u2019s maybe Vimeo and it all looks so different. I see this creating a better display, a better feel, but it also gives you more control on what kind of content is acceptable.<\/p>\n Birgit Pauli-Haack<\/em>: Absolutely. So from the history, this comes after 7.0 allowed to actually use a video URL as a background for a cover. And after that was installed, there was quite some feedback from the community, especially the agency community and the enterprise level where they say, okay, I don\u2019t want people just have video embeds from outside of, especially those that are in restricted industries, they\u2019re regulated industries, they cannot just have willy-nilly URLs playing on their website. So they needed a way to restrict the video providers or even restrict that feature altogether. So this is a reaction of all the community feedback that came in to provide that.<\/p>\n Faith Imokol<\/em>: Yeah.<\/p>\n Birgit Pauli-Haack<\/em>: Speaking of video, the new client-side processing now also has a way to convert the GIF, an uploaded animated GIF. We know them from the \u201990s, right? But some of the Screen recording features also do animated GIFs. And when they have one problem. It\u2019s nice for smaller things, yeah, for 1 second or something like that. But if you have a longer GIF, you cannot control it. You cannot stop it. You cannot do anything. So some people want to convert that to a video. And now that feature is coming to 7.1, but it\u2019s also made opt-in. So people have to say, okay, I wanna do this. And then it shows up in the block transform dropdown from a block toolbar. And then you can automatically have the GIFs converted to a video. It really depends on the video and the frame size and a lot of other things to get this right. But it\u2019s a really nice feature.<\/p>\n Faith Imokol<\/em>: Yeah, it\u2019s a very nice feature in that I think now we have still, one has the ability to choose what they want, if they want to maintain the image GIF or to have it as a video. Whereby if it was a video, it could be lightweight and loads much faster than when it\u2019s a normal GIF. GIFs tend to be quite heavy.<\/p>\n Birgit Pauli-Haack<\/em>: Yes.<\/p>\n Faith Imokol:<\/em> On websites. Yeah. Just a funny scenario. I went on a website that had\u2014 was literally littered with GIFs everywhere. And I\u2019m just imagining having to work with that.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol<\/em>: How resource intensive that can be and how the performance of the website. So I think this resolves a problem that was there previously that they had tried to resolve previously. That is by allowing the conversion of the GIF into a video. So now one can choose, they can either maintain using the GIF or they can choose to go with the video.<\/p>\n Birgit Pauli-Haack:<\/em> Yeah.<\/p>\n Faith Imokol:<\/em> We had 2 blocks that were initially still, should I say, in production. That is the playlist block and the tab block. And these are coming out in version 7.1. The playlist block will allow you to add a playlist. If you\u2019ve worked with any podcasting and different\u2014 if you\u2019re doing any music playlists on your website, this block will allow you to be able to add a list of music that you want and you\u2019re able to play it as well in one after the other. So it\u2019s a very powerful block coming out in version 7.1. And I\u2019m also talking about the tab\u2014 the tabs block. This will allow you to be able to organize content into tabs on your website. So it will allow you to group, literally to group different content onto your website. It\u2019s also a very, very powerful block that I think will make a whole sense on how different content can be added onto our site. So maybe you can add on to that.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah, there were right from the beginning when Gutenberg came out, there were quite a few block collections that had tabs blocks in there. So finally it comes into core. I have a question for a developer. I don\u2019t know how you feel about that, but doesn\u2019t it seem that the details block, the accordion block, and the tabs block, they all kind of have the same metaphor kind of thing? Yeah, kind of. Yeah, you check something and something opens, and then you have a collection of check something and the tabs are there, or accordions kind of I mean, they behave a little bit differently, but aren\u2019t they just a variation of the same idea?<\/p>\n Faith Imokol<\/em>: I think it\u2019s kind of a similar idea, especially when you see how accordions work. But they\u2014 I think it comes down to what kind of display is someone looking forward to. They may all be doing the same kind of similar thing, but someone wants their content to work differently. The tabs block, I think, gives us kind of more\u2014 I find it to be superior, should I say superior, to the accordion block in the sense that it allows you to actually group content that you\u2019re displaying. <\/p>\n So an accordion can be used for things\u2014 I could say the most common example that I\u2019ve seen where they\u2019re mostly applied is something like FAQs, right, where you group questions and answers. But now looking at a tab, imagine you have something like a WooCommerce site and you have all this different content that is in line with that product. You have the details, then you have the, uh, should I say specifications, then you have the pricing. So all these things can be grouped into different tabs and it can allow someone to navigate through them while providing more concrete details within them. You can do the same with accordions. But I find that this provides a better way of navigating, you know, of navigating through content. Accordions, if the content is quite a lot, they may become, I think, kind of very bulky and they create a lot. You have a lot within one thing while tabs allow you to break down that thing. And I think also, I don\u2019t know right now, I don\u2019t know how far this this feature is, but I think tabs can also allow you to also add different other blocks, should allow you to add different blocks within it. So you can do a lot more within, within it.<\/p>\n Birgit Pauli-Haack<\/em>: So, and I feel it\u2019s a little bit of a\u2014 the metaphor that tabs do is kind of more like in an office setting where you have files, folders, and then files in them that are kind of\u2014 you pull them out of the register and then you have the writers on top that are your tabs and then you can\u2014 that metaphor is kind of in a website now. And I think people can navigate that better than figuring out how an accordion works.<\/p>\n Faith Imokol<\/em>: Yes.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah. I think you\u2019re right there. Yeah. Well, that was actually kind of a tricky question because that question should go to the WC3 body that does the standards for HTML because that\u2019s what these 3 blocks do, details, accordion, and tabs. They put the HTML that\u2019s available into a block setting and then offer that as a tool to design pages and lay out the pages. So the question is actually for the WC3 standards body. Why did you come up with these different standards there and HTML tags for that? <\/p>\n So I think, yeah, we have a few, 2 more updates on the visual revisions page. There is now a label for autosaves. Because the revisions historically only saved what you did, what was there when you hit the save button. And now it also adds the autosaves as separate line items to the revisions timeline. It might get a little crowded now, but you can collapse them quite a bit. And so when you leave a post that was autosaved and then come back to it again, you get a notification on top of the screen that says there is a newer version in autosave. And when you clicked on the link there, you were going back to the old revisions screen, and that has been solved too. So now this screen also goes to the new block-based visual revision screen.<\/p>\n Faith Imokol:<\/em> I think this is one of the things\u2014 revisions is one of the things that I\u2019m actually impressed by and excited about. I don\u2019t know how many times I just could come back to my site trying to look through my content and going through the revisions, I\u2019ll just give up and be like, you know, no need to go back. But I think this helps us to be able to track and actually know where in time we ended, what changed, and also being able to go through what the different revisions are. <\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol<\/em>: And it\u2019s quite also funny that the person who reported this was a first-time contributor.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol<\/em>: The person who caught this. Yes.<\/p>\n Birgit Pauli-Haack<\/em>: Yeah.<\/p>\n Faith Imokol<\/em>: So with the new settings that we have for the viewpoints, this is a buildup on what we had, we had talked about previously. That is being able to remember what we have, we now have a new feature that allows us to add our own custom viewpoints. in our theme that is in the theme.json.<\/p>\n Birgit Pauli-Haack<\/em>: With the new states being for either the viewport states or the pseudo states, which is kind of hover and action on that and active, what didn\u2019t work was that when you changed the color, you didn\u2019t get a notification that your color choices didn\u2019t adhere to the contrast for accessible websites. So, and normally when you change the color for the background and for the text, you get a little warning that this is not contrast-rich. You better check your color settings. This feature wasn\u2019t working for the viewports for the mobile or tablet or for the pseudo-states. So when you change the styling for those states, you didn\u2019t get the warning. So, and that has been rectified with 23.6 Gutenberg. And it is actually a nice, I would say bug fix, but it\u2019s an enhancement because it was something that wasn\u2019t there before. And I think the next one, we already talked about the inner blocks and the custom HTML block. I think we\u2019re gonna skip through that.<\/p>\n Faith Imokol<\/em>: <\/p>\n This is just, I think, adding up to what we had previously.<\/p>\n\n
Special Guest: Faith Ruth Imokol<\/h2>\n
\n
WordPress Events in Uganda <\/h2>\n
\n
\n
WordPress 7.1 <\/h2>\n
\n
\n
\n
Announcements<\/h3>\n
What\u2019s Released -WordPress 7.1<\/h3>\n
Gutenberg 23.6<\/h3>\n
Features<\/h3>\n
Enhancements<\/h3>\n