![\"WordPress](\"https://i0.wp.com/wordpress.org/news/files/2023/07/Live-Product-Demo.png?resize=1024%2C576&ssl=1\")
Want to learn more about WordPress 6.3, planned for release on August 8, 2023? Join the WordPress community for a first look at 6.3 in action during a live product demonstration.
\n\n\n\n6.3 release squad members, Anne McCarthy and Rich Tabor, will team up with moderator, Nathan Wrigley, to guide attendees through the anticipated highlights of the upcoming release. This event will follow a similar format to the live demo for 6.2.
\n\n\n\nAttendees will see recent improvements to the Site Editor, Patterns, Command Palette, and more. Following the demo, there will be a Q&A session, and you may submit questions in advance via Slack.
\n\n\n\nThursday, July 20, 2023 at 16:00 UTC
Zoom Link | Save this link and use it on July 20 to join the event.
The event will be recorded, archived for on-demand viewing on WordPress.tv, and shared in a recap post shortly afterward.
\n\n\n\nTo learn more about WordPress 6.3, please visit the following resources:
\n\n\n\nProps to our panelists and moderator, and to @jpantani, @meher, @eidolonnight, and @dansoschin for helping prepare this announcement and supporting event logistics.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15354\";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:1;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 6.3 Beta 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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2023/07/wordpress-6-3-beta-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Jul 2023 17:10:55 +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:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";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:1;a:5:{s:4:\"data\";s:8:\"Releases\";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:2;a:5:{s:4:\"data\";s:3:\"6.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:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";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:4;a:5:{s:4:\"data\";s:8:\"releases\";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=15340\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:289:\"WordPress 6.3 Beta 3 is now ready for download and testing!\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version on production or mission-critical websites. Instead, it is recommended that you test Beta 3 on a test server and site.\";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:11:\"Dan Soschin\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5926:\"\nWordPress 6.3 Beta 3 is ready for download and testing!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version on production or mission-critical websites. Instead, it is recommended you evaluate Beta 3 on a test server and site.
\n\n\n\nGet an overview of the 6.3 release cycle, and check the Make WordPress Core blog for 6.3-related posts in the coming weeks for further details. Also, save the date for a live product demo tentatively scheduled for Thursday, July 20, 2023 at 16:00 UTC (link TBD). This will be a great opportunity to join the WordPress community to celebrate the accomplishments of 6.3 and this final chapter of Phase 2.
\n\n\n\nThanks to the many WordPress beta testers, this release contains approximately 34 (Site Editor) and 40+ (Trac) updates since the Beta 2 release. Nice work, team!
\n\n\n\nTesters should note that the “Patterns Library” is now simply called Patterns in the UI. Additionally, pattern details now include a sync status and a lock icon is added for theme patterns.
\n\n\n\nBrowse the technical details for issues addressed since Beta 2 using these queries:
\n\n\n\nTesting 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.
\n\n\n\nWhile testing the upgrade process is essential, trying out new features is too. Review the many new features in WordPress 6.3 and focus your testing efforts on those areas in particular.
\n\n\n\nBetween the Beta 1 release and the final release candidate (RC), the monetary reward for reporting new, unreleased security vulnerabilities is double. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nYou can test WordPress 6.3 Beta 3 in three ways:
\n\n\n\nwp core update --version=6.3-beta3The current target for the final release is August 8, 2023, which is about five weeks away. Your help testing this version ensures everything in this release is the best.
\n\n\n\nBeta three, a peek
Summer here and winter there
A fourth in one week
Thank you to the contributors who collaborated on this post: @DanSoschin, @Meher, @JPantani, @eidolonnight, @davidbaumwald, @priethor, and @DanSoschin for the Haiku.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15340\";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:2;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"WP Briefing: Episode 59: A Polyglot’s WordPress\";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:68:\"https://wordpress.org/news/2023/07/episode-59-a-polyglots-wordpress/\";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, 03 Jul 2023 13: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";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:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";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:53:\"https://wordpress.org/news/?post_type=podcast&p=15281\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:227:\"Join WordPress Executive Director Josepha Haden Chomphosy in the 59th episode of the WordPress Briefing. Today she invites guest speaker Alex Kirk to discuss Polyglots’ work to continue to help bring translation to WordPress.\";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:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2023/06/WP-Briefing-059.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s: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:\"Brett McSherry\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:30284:\"\nJoin WordPress Executive Director Josepha Haden Chomphosy in the 59th episode of the WordPress Briefing. Today she invites guest speaker Alex Kirk to discuss Polyglots’ work to continue to help bring translation to WordPress.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHost: Josepha Haden Chomphosy
Guests: Alex Kirk
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry and Nicholas Garofalo
Song: Fearless First by Kevin MacLeod
( Intro music )
\n\n\n\n[Josepha Haden Chomphosy 00:00:10]
\n\n\n\nHello everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\n( Intro music )
\n\n\n\n[Josepha Haden Chomphosy 00:00:39]
\n\n\n\nI have with me Alex Kirk, who is a longtime WordPress contributor and who has been instrumental in recent innovations in the Polyglots’ work. Phase four of the Gutenberg project is native multilingual support, and so I see this work that is being done as instrumental, not only for our global community but in support of what’s to come in that specific roadmap.
\n\n\n\n[Josepha Haden Chomphosy 00:00:59]
\n\n\n\nSo without further ado, Alex Kirk, welcome to the WordPress Briefing.
\n\n\n\n[Alex Kirk 00:01:03]
\n\n\n\nHello, how are you doing?
\n\n\n\n[Josepha Haden Chomphosy 00:01:05]
\n\n\n\nI’m good. I’m good. Can you, let’s, because I bet that not a lot of people know who you are, can you first start by just telling me a bit about your work with WordPress, and then let us know what GlotPress is, for those of us who don’t know yet?
\n\n\n\n[Alex Kirk 00:01:19]
\n\n\n\nAll right. So, Automattic sponsors me to work in the WordPress project on the Meta team and on the Polyglots team. So I spent time on improving or helping improve the software that powers the translation on WordPress.org. But I also work on the meta team on things like Matrix and evaluating if it would be a good fit for WordPress to switch to Matrix for their chat system.
\n\n\n\n[Josepha Haden Chomphosy 00:01:46]
\n\n\n\nSo a lot of really big projects that you work on, all of that kind of stuff that has no easy solutions anymore, is where you are right now. Huh?
\n\n\n\n[Alex Kirk 00:01:56]
\n\n\n\nYeah, there’s no clear path, but it’s our mission to find it. So that’s part of what makes things interesting.
\n\n\n\n[Josepha Haden Chomphosy 00:02:05]
\n\n\n\nCool. So for folks who don’t know too much about the Polyglots team or generally translating WordPress, the software, can you let us know a bit about what GlotPress is?
\n\n\n\n[Alex Kirk 00:02:16]
\n\n\n\nRight. So the translation system that powers WordPress.org is called GlotPress. It used to be a standalone software that was developed a couple of years ago, and it was transformed into a WordPress plugin at some point, and now powers the translation that happens on WordPress.org. So we translate WordPress core there from English to other languages, plugins, themes, block patterns, and it all happens through this software called GlotPress. There are a couple GlotPress installations around the world, but I think the WordPress.org one is one of the bigger ones.
\n\n\n\n[Josepha Haden Chomphosy 00:02:55]
\n\n\n\nProbably, WordPress.org is pretty, pretty massive. Also, I think it’s great that you said that GlotPress was created a couple of years ago, like that, that indicates to me that you’re working on a really different timescale than a lot of folks are in WordPress.
\n\n\n\n[Josepha Haden Chomphosy 00:03:10]
\n\n\n\nSo Alex, tell me a little bit about what it takes to ship translated WordPress software. So, I mean, for people who don’t need translated WordPress, like obviously we don’t have a good idea of what it takes to make sure that WordPress is available in so many languages. So what goes into the work of making sure that that happens?
\n\n\n\n[Alex Kirk 00:03:32]
\n\n\n\nAll right, so typically the WordPress software and plugins and themes are primarily created in English. And for it to be available in other languages, it needs to be translated. And for that to be able to happen, the programmers need to make the software translatable. Basically, they’re providing each English string for the translation software to be available to be transformed, so to speak, into another language and to what it’s being transformed to. This is what the translators do. So they go into the GlotPress software and see the list of texts that need to be translated and translate it to their language that they speak. Typically there is a process around this.
\n\n\n\n[Alex Kirk 00:03:32]
\n\n\n\nSo, we’ve got people who have lots of experience in translation. And specifically in translating WordPress or WordPress plugins. And they’re kind of the, the people who help ensure good quality of translation. So anybody who’s working the WordPress project, so basically who has a WordPress.org account, can come in and address the translation. And that translation enters the system, so to speak, in a waiting state. And then somebody who we promoted to be a Translation Editor will come along and take a look at your translation and will approve it or will give you suggestions how to do the translation in a better way, or come up with maybe even a better translation.
\n\n\n\n[Alex Kirk 00:05:03]
\n\n\n\nYou know, when you have like a small thing that’s just not right, like a missing full stop or something like that. They might just add it for you. And well, as soon as the plugin or software is translated to a certain level of translations those translations will be shipped out to the WordPress installs.
\n\n\n\n[Alex Kirk 00:05:20]
\n\n\n\nSo, for example, for a plugin, you would reach 90% of translated strings. Those translations will then be basically packed up into zip file, a language pack and delivered to each WordPress so that you can have the translations available there.
\n\n\n\n[Josepha Haden Chomphosy 00:05:35]
\n\n\n\nAnd is 90% the threshold for plugins only, or is that also the threshold for like themes and the CMS itself?
\n\n\n\n[Alex Kirk 00:05:34]
\n\n\n\nWell. We strive for 100%, I would say.
\n\n\n\n[Josepha Haden Chomphosy 00:05:47]
\n\n\n\nGood. ( laughs )
\n\n\n\n[Alex Kirk 00:05:48]
\n\n\n\nAnd, 90% more of a motivational point. To be actually honest, I’m not sure if the threshold is 90% for every project or even if it’s actually 90%. It’s different between different GlotPress installations and it’s basically something that is made as a setting that can be changed. There’s, it’s an arbitrary number. Typically you’d actually want to make sure that the most important strings are translated first. So the ones like, if you look at the whole picture, software usually consists of many parts, many of whom are not encountered by people on a regular basis. For example, error messages that could be like obscure error messages, and you could argue that those might be not as important. Or even sometimes you could even say like, do they need to be translated? Because if you encounter an error message and you search the internet, wouldn’t you probably want everybody to search for the English one to find the solution? But that set-aside, it’s important to have like the headline of the plugin or like the most important strings translated, and typically translating those most important strings will take you to a pretty high percentage so that we can then say it’s good enough to be shipped.
\n\n\n\n[Josepha Haden Chomphosy 00:07:02]
\n\n\n\nGotcha. I see, I see. Okay. Well, we talked a bit earlier about GlotPress’s timeline. It has been around for a bit, I know. But with that kind of in mind, have there been any notable changes to GlotPress recently?
\n\n\n\n[Alex Kirk 00:07:19]
\n\n\n\nYeah, so I think for GlotPress there’s been a bit of an up and down over time in terms of engagement and progress on the software. But in, in the recent year, I think we’ve added a couple of things that have been very helpful for translators. So one of them was adding the commenting functionality, so yeah.
\n\n\n\n[Josepha Haden Chomphosy 00:07:35]
\n\n\n\nSuper helpful. Shocked it wasn’t there before. Sorry, translators. Sorry, all of our polyglots.
\n\n\n\n[Alex Kirk 00:07:40]
\n\n\n\nWell, it can be like there was when GlotPress was created there, there is like the, a big part of GlotPress are these states, like the waiting state when you enter translation, and then there’s approved state, which basically a translation we say it’s set to current, and there’s all sorts of process around it. So if the software is updated or translation might get fuzzy. But also like, if somebody submits a translation that doesn’t fully conform to what’s the translation editors, or like what the standards of the translation community have been set to, then you would have to need to reject it.
\n\n\n\n[Alex Kirk 00:08:16]
\n\n\n\nAnd that has been something that we felt wasn’t a very good and enticing way of telling people like, we appreciate your work. It wasn’t just quite right, but it’s more of a rejection. So this is how we came up with this like, let’s give people the option to say what was wrong and give them a chance to try again without making them feel rejected.
\n\n\n\n[Josepha Haden Chomphosy 00:08:38]
\n\n\n\nYeah. Sort of a “No, but…” as opposed to a, just refusal to receive it.
\n\n\n\n[Alex Kirk 00:08:45]
\n\n\n\nAnd other things that we’ve worked on is, like, with the recent search of AI, like getting help from AI on translation and also on reviews. So, there’s some interesting things that you can do with AI in that regard; that one important aspect of translations, it’s also that we’ve got glossaries for each language where people, basically the translation community, identifies certain words they want to translate them the same way every time. And with the AI, you can basically add to the prompt, like, please translate those words to those translations when you give me a translation for that. And as it can change over time, you can always adapt this to the prompt, and that has been proven quite helpful.
\n\n\n\n[Josepha Haden Chomphosy 00:09:25]
\n\n\n\nThat is great. That’s one of those things I know that AI has been like a really popular thing to talk about. And AI, specifically for translations, I think has caused some concern that maybe we’ll just like translate it all and hope that computers get it right when we know pretty certainly that computers don’t always get the translations right. But that’s not what you’re talking about, right? What you’re suggesting is that AI would suggest what could be translated and what it could be translated to, and then human beings have to confirm that that’s correct, right?
\n\n\n\n[Alex Kirk 00:09:59]
\n\n\n\nThat’s exactly it. So basically, we give suggestions to the translators, and then they can modify a translation before they press save. It’s more of a, like supporting them in getting the translations, like looking up words more quickly and all of that.
\n\n\n\n[Josepha Haden Chomphosy 00:10:16]
\n\n\n\nThat’s wonderful. So is that the major sort of next step that is coming for GlotPress, or are there other things that we should keep an eye out for in that software?
\n\n\n\n[Alex Kirk 00:10:27]
\n\n\n\nSo one direction that we’ve been taking GlotPress is basically making use of the fact that GlotPress is WordPress plugin now. And you know, typically, you would just use a GlotPress install. So on WordPress.Org, there’s like GlotPress installed, there’s translation projects created, something that we call “translation sets”. So for languages, you want to translate it to, it’s all pre-configured, and if you would install GlotPress to plugin on your own WordPress, it would be empty and not very useful. So what we’ve added is a way for you to basically be able to translate the plugins and themes that you’ve got installed in your WordPress into the language that you’re interested in.
\n\n\n\n[Alex Kirk 00:11:07]
\n\n\n\nSo you might have a non-English website that you want to use certain plugins with, and they might not be fully translated at this point, so obviously, you could go to WordPress.org and help translate them, and that’s the way to, that’s preferred. But you could also now go install GlotPress on your own website and translate there. And then you have the translations there right when you enter them. And you can then contribute those translations back to WordPress.org.
\n\n\n\n[Josepha Haden Chomphosy 00:11:35]
\n\n\n\nSo that’s with local GlotPress?
\n\n\n\n[Alex Kirk 00:11:37]
\n\n\n\nThat’s something that we call local GlotPress. And you know, since we then have all these translations in the local database, it means we can do even more with those translations. So typically, language packs would be delivered to WordPress, but with local GlotPress, you’ve got like all the GlotPress software there.
\n\n\n\n[Alex Kirk 00:11:56]
\n\n\n\nSo we can do things like inline translation. So, on your own WordPress and wp-admin, for example, we can highlight all the strings that can be translated, and those strings just have to right-click them and enter your translation, and that way, you can basically go about and translate the whole ui, seeing your progress, as you’re making, basically turning the screen from red to green.
\n\n\n\n[Josepha Haden Chomphosy 00:12:20]
\n\n\n\nYeah. Yeah. So that’s something now that you can do in your local WordPress installation.
\n\n\n\n[Alex Kirk 00:12:26]
\n\n\n\nBasically, it’s completely independent of WordPress.org. We would ask you to contribute the translations back when you have them, but being independent also allows you to translate like premium plugins, which could not be hosted on WordPress.org or doing something like that we call like hyper-local translation. So, for example, I speak Austrian German natively, but even inside Austria, we’ve got different dialects or like special words that we use. And if I wanted to create a website that’s targeted at the Viennese market, for example, I might want to use those specific terms. And this is something I would have to argue for those translations to be accepted on WordPress.org because it’s a, it’s like a very targeted market. But if I have a local GlotPress, I can do those translations there.
\n\n\n\n[Josepha Haden Chomphosy 00:13:11]
\n\n\n\nThat seems awfully beneficial, especially as dialects. I’ve been having these conversations. I have, in my extended family, many children, and they are all learning languages and one of them has been having kind of thoughts about, like, dialects and how dialects are almost another language. And if so, like how do you know what everybody’s saying when you’re speaking all the same thing, but it’s kind of a little bit it sounds a little bit different.
\n\n\n\n[Josepha Haden Chomphosy 00:13:37]
\n\n\n\nThat’s certainly a thing in the US, the distinct dialects across our country. And so I imagine that that’s gonna be a really beneficial sort of implementation for countries that have a lot of different regional variations and certainly smaller countries that have technically the same language as somebody else, but a lot of regional differences, regional specific things.
\n\n\n\n[Josepha Haden Chomphosy 00:14:01]
\n\n\n\nIs that the same or different as the live translations, Translate Live, that we talked about at the WordCamp Europe a couple weeks back?
\n\n\n\n[Alex Kirk 00:14:12]
\n\n\n\nRight. So, Translate Live is kind of the next step after local GlotPress. It’s like this happy marriage between the WordPress Playground and local GlotPress. So the WordPress Playground is also something that has come up a lot. It’s basically a way for you to run WordPress inside a browser window, so in JavaScript. And at first, it seems like mildly interesting, I would say. But when you combine it with other things like local GlotPress, it can lead to really interesting opportunities. So with inline translation, for example, on WordPress.org, you would typically find for every plugin, the UI would look the same. You would have a table of strings, and all that makes you realize you’re translating this certain plugin is that in the header of the page, it says this name of the plugin, but other than that, it can look really all the same.
\n\n\n\n[Alex Kirk 00:15:07]
\n\n\n\nAnd now, with WordPress Playground, you can put up a WordPress and run this plugin inside that Playground. And now, if you add local GlotPress to the picture, you can also do the inline translation of that plugin inside the WordPress Playground. So you’ve got inline translation. We add the glossary so they do make sure that you translate things the same way that they’re expected, and you don’t have to install the plugin.
\n\n\n\n[Alex Kirk 00:15:33]
\n\n\n\nAnd still, you can see what the translations will look like. You can see the strings next to each other, and what I think is most important, you will start with the strings that you see first, which are the most important ones. When you’re in the table view, those strings might be somewhere buried in the middle, and yeah, it’s really hard to see progress if you start with kind of obscure error messages, for example, versus just starting with the things that you see first.
\n\n\n\n[Josepha Haden Chomphosy 00:16:02]
\n\n\n\nYeah. So, moving translations away from table-based translations where you kind of have to know what you’re looking for. So the Translate Live, along with local GlotPress, along with WP Playground, is going to make it so that it’s easier to see visually what needs to be translated, where, what’s most valuable to translate for your mid users and your end users, basically.
\n\n\n\nYeah?
\n\n\n\n[Alex Kirk 00:16:30]
\n\n\n\nThat, and also like for plug-in authors, it can be really good to see, you know, you can switch the languages in the Playground to another language, and you can quickly see like what’s the state of the translation in this language or in that language. And even things like, you know, Arabic as an RTL language rights to left language. The sidebar will change to the right, and you can also just switch language and see like, what’s my plugin like in this environment. I mean, this is not technically something that’s related to local GlotPress, but in this translation live ui, it’s very easy to change languages and see your plugin in another language.
\n\n\n\n[Josepha Haden Chomphosy 00:17:06]
\n\n\n\nI mean, it’s not specifically related to, to Translations Live, but also, I think that if we’re saying that WordPress not necessarily is going to lead the way with translations and native multilingual support in our CMS because, of course, it’s still a little bit far out on our roadmap. We certainly have an opportunity to have the best implementation of that.
\n\n\n\n[Josepha Haden Chomphosy 00:17:27]
\n\n\n\nAnd even if like that specific use case that you’re talking about isn’t related directly to what it is that you are working on for Polyglots and inside GlotPress and all of that, I do see that having more streamlined, more easy to see and access opportunities to like test the way that our software looks across varying environments, especially those that change it substantially from what we typically work in day-to-day for any individual developer or any individual WordPress site implementer.
\n\n\n\n[Josepha Haden Chomphosy 00:18:00]
\n\n\n\nLike, I think that that is a big step forward for all of us and certainly for anyone who is having to use WordPress as not a native English speaker. And so you say it’s not related, but it still is a big, a big benefit for WordPress overall, I think, to have this kind of work happening so that we can have those benefits to the folks who are using our software.
\n\n\n\n[Josepha Haden Chomphosy 00:18:22]
\n\n\n\nSo there were a couple of different things that you mentioned over the course of our conversation. We’re gonna put some links to the show notes for all of those. But one thing that you mentioned that just kind of went by, and we never really had an opportunity to talk about it. You talked about the, I think it was GTEs, Global Translation Editors, the folks that are like approved as final approvers of translations. If there is someone who’s listening to this podcast who wants to become a GTE someday, where would they go to do that?
\n\n\n\n[Alex Kirk 00:18:54]
\n\n\n\nSo the path to GTE is a PTE. ( laughs )
\n\n\n\n[Alex Kirk 00:18:59]
\n\n\n\nSo, we’ve got different levels of translation editors. Basically, you start, you could say you start off as a translator, and this is how you can kind of show that you can do good translations or that you’re very firm in your language. And this might make you be noticed in the community.
\n\n\n\n[Alex Kirk 00:19:16]
\n\n\n\nSo we’re always looking for people who like to help with translations. And you might be then promoted to be a Project Translation Editor. Basically, it means that for a single language in a project, you’ll be able to approve translations. So, you’ll be the one who says, like, this translation is a good one and this conforms to the to the rules that we have stated as a translation community.
\n\n\n\n[Alex Kirk 00:19:42]
\n\n\n\nAnd further down the path then is the GTE, where you basically are allowed to approve translations across any project on translate.WordPress.org in your language. And that’s, usually you’ll be in, in that position with other GTEs.
\n\n\n\n[Alex Kirk 00:20:04]
\n\n\n\nSo there is, like, in each community, there is like, we’re people based. We talk about what might be a good translation. We talk to each other, try to find rules that maybe prevent common mistranslations, or set the standards for how we want the software to be translated. And this is something where you get a voice as a translator, but as a GTE, you get into a position where you can actually make the changes or find consensus on how the software should be translated in your language.
\n\n\n\n[Josepha Haden Chomphosy 00:20:35]
\n\n\n\nAnd if folks are not familiar where the Polyglots team works and meets, where would they find you all?
\n\n\n\n[Alex Kirk 00:20:41]
\n\n\n\nAt make.WordPress.org/polyglots.
\n\n\n\n[Josepha Haden Chomphosy 00:20:45]
\n\n\n\nPerfect. Alex, this has been such a fascinating conversation. Thank you so much for joining me today.
\n\n\n\n[Alex Kirk 00:20:50]
\n\n\n\nThank you very much.
\n\n\n\n( Intermission music )
\n\n\n\n[Josepha Haden Chomphosy 00:20:59]
\n\n\n\nSo that brings us now to our small list of big things. First, WP Campus 2023 is taking place July 12th through the 14th. That’s a nonprofit three-day conference with topics that focus on the growth of higher education, accessibility, WordPress, and anyone who works in higher education.
\n\n\n\n[Josepha Haden Chomphosy 00:21:17]
\n\n\n\nIt’s a hybrid event. There is an in-person component on the beautiful campus of Tulane University in New Orleans, Louisiana. I’ll add information about that in our show notes for anyone who would like to join in person or online.
\n\n\n\n[Josepha Haden Chomphosy 00:21:32]
\n\n\n\nThe second thing is that the mentorship program pilot that I have been talking about a little bit over the last few months has been formally launched.
\n\n\n\n[Josepha Haden Chomphosy 00:21:39]
\n\n\n\nIf you are interested in contributing more to the project but not sure where to begin, take a look at this comprehensive onboarding experience. It’s cohort-based. It has some personalized one-to-one mentorship. There are guided courses, live workshops, all of that. So read more about it in our show notes and sign up for one-on-one team mentorship.
\n\n\n\n[Josepha Haden Chomphosy 00:21:59]
\n\n\n\nAnd then, finally, Matt mentioned at WordCamp Europe an idea that he had been thinking of for some time a Make team dashboard that would sort of help define team metrics and help identify for individual contributors what should indicate team health and where they can find the most impactful projects to work on.
\n\n\n\n[Josepha Haden Chomphosy 00:22:20]
\n\n\n\nA post has since been published on make.WordPress.org/meta calling for additional feedback on that idea, so that we have an understanding of what this could be, how the dashboard can kind of come to be. And so stop by and add your thoughts there in the comments.
\n\n\n\n[Josepha Haden Chomphosy 00:22:38]
\n\n\n\nAnd that, my friends, is your small list of big things.
\n\n\n\n[Josepha Haden Chomphosy 00:22:42]
\n\n\n\nThanks for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\n\n\n( Outro music )
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15281\";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:3;a:6:{s:4:\"data\";s:72:\"\n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"People of WordPress: Allison Dye\";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:67:\"https://wordpress.org/news/2023/06/people-of-wordpress-allison-dye/\";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, 30 Jun 2023 21:23:11 +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:8:\"category\";a:6:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";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:1;a:5:{s:4:\"data\";s:8:\"Features\";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:2;a:5:{s:4:\"data\";s:7:\"General\";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:3;a:5:{s:4:\"data\";s:10:\"Interviews\";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:4;a:5:{s:4:\"data\";s:9:\"HeroPress\";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:5;a:5:{s:4:\"data\";s:19:\"People of WordPress\";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=15287\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:121:\"The People of WordPress goes to the US to feature Allison Dye, who uses the software in her work and disability-advocacy.\";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:11:\"Abha Thakor\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:14661:\"\nA way to escape chronic pain and give a sense of independence, is what using WordPress means for Italian-American Allison Dye. Now as a project manager and social media content manager living in North Carolina, USA, she uses the software in her work and in disability-advocacy.
\n\n\n\nThe People of WordPress series shares inspiring stories of how people’s lives can change for the better through WordPress and its global community of contributors.
\n\n\n\n![\"Allison](\"https://i0.wp.com/wordpress.org/news/files/2023/06/fi-allison-dye.jpg?resize=1024%2C537&ssl=1\")
Allison was first introduced to WordPress when she was 13 years old. Her parents gave her own WordPress website to use, play, test, and try whatever she wanted with it. Her health issues had started when she was eight years old, and being able to express who she was and learn new skills provided an escape she needed.
\n\n\n\nAllison said: “While the technical aspects of my new WordPress website intrigued me, I was more interested in the space it made for me to write. All throughout my childhood I had struggled with chronic pain, fatigue, and other unexplained symptoms. Having a private world I could call my own, I was able to write my story.”
\n\n\n\n\n\n\n\n\n“There is something truly amazing about having a place to tell your story.”
\nAllison Dye
Her family faced many doctors, nurse, specialists and hospital visits, but could not get an answer to the difficulties faced by Allison. She said: “I felt like my life and world were out of control. But logging onto my little website and typing away on the computer keys gave me a sense of control. I couldn’t always do things that other kids had the energy to do. But I could get lost in writing for hours. I couldn’t control my life story, but I could write about it.”
\n\n\n\nShe felt it was like writing letters to her future self and would act as a reminder of how strong she had become. Even now when Allison writes on her website, she feels it is writing letters to her past self, expressing reassurance and pride. The practice of writing online continues to help her reflect on how she coped and made it through the difficulties.
\n\n\n\nAllison hoped her early experiences with hospitals and being unwell was just part of being a child, and that in adulthood she would be healthy. She longed for this time.
\n\n\n\nGrowing up did not bring her this dream of a healthier life and an end to chronic pain. In fact, her condition worsened as she went through her teens and at 18 she finally received a diagnosis of Multiple Sclerosis.
\n\n\n\n![\"Allison](\"https://i0.wp.com/wordpress.org/news/files/2023/06/allison-2.jpg?resize=768%2C1024&ssl=1\")
This changed what had been conventional job choices, as she was not able to handle a 9 to 5 work schedule. She could not drive herself to work on some days and relied on her mother to help with transport. She knew that she would have to find another way to work and she was determined to find it.
\n\n\n\nShe began writing music and book reviews online, and then moved onto writing blog posts. As they were published she started to receive payment and a sense of power over her life. She said: “WordPress felt familiar, typing on the computer keys felt comfortable, and sharing my words with the world felt surreal.”
\n\n\n\nAllison’s sense of ownership of the software became part of her strength. “I think I believed WordPress was mine somehow. I was learning that WordPress is something that belongs to everyone in some way. And I loved it.”
\n\n\n\nThe confidence using the platform gave Allison led her to find more about what it could do and meet other people who used it. She said: “The thing I love about WordPress is that it’s not just for developers or bloggers or SEO experts. I began to meet more people in the community and was delighted to find people like me, who didn’t know the technical stuff, but were a part of WordPress.”
\n\n\n\nThis global community orbiting around the software gave her an opportunity to meet social media managers, designers, and people from many different areas. She found that ‘there was a place for everyone’. The guiding strength and fascination Allison found and still finds today is in that community. Allison said: “The community felt as important as the rest of everything that makes WordPress what it is. It felt like it was about people and relationships as well as codes and databases.”
\n\n\n\nIn 2020, she was hired by a WordPress company. She said: “I like being a part of a WordPress company, and I love that I contribute to a team that helps people with their websites. I understand the importance of having a space that’s yours. Whether it’s a business or personal site, having a website gives you the power of telling your own story.”
\n\n\n\nWordPress gave Allison a freedom and an independence. She did not have to work a 9 to 5 job, rely on others to drive her on bad days with her MS, nor worry about days when she wanted to stay in her sweatshirts rather than go into an office to work. She said: “I have a 100% remote job which I can do despite the plot twists in my story, thanks to WordPress and the people in it.”
\n\n\n\nWordPress took Allison into the world of project management for a small agency, and this experience was to help guide her path, skills and confidence into the future. She went on to work in content management in WordPress, building pages for awareness campaigns for non profit organizations and small businesses as a contractor. She helps people update their websites, add and edit content, perform basic updates and help them to learn how to use their sites.
\n\n\n\n\n\n\n\n\n“I tell all my clients to use WordPress because there is really no other solution that can scale as easily for growing organizations and small businesses. I love how WordPress allows them to tell their stories, share their passion, and have a place to call their own on the internet.”
\nAllison Dye
As a fluent English and Italian speaker, Allison is able to support clients in different countries from where she lives. “I love that with WordPress I’m able to support clients remotely. This is thanks to all of the many WordPress contributors, developers, project managers, content writers, and many, many volunteers that work tirelessly to enable people around the world to use WordPress.”
\n\n\n\nAllison also became a certified as an English As A Second Language (ESL) teacher. “My affinity for words and languages allows me to teach passionately and creatively. I’m Italian-American and am fluent in English and Italian. Teaching English allows me to share my passion for communication with others.”
\n\n\n\n![\"Allie](\"https://i0.wp.com/wordpress.org/news/files/2023/06/WPCoffeeTalk-Allie-Dye.png?resize=1024%2C562&ssl=1\")
Allison attributes mentors and supporters in the WordPress community for helping her appreciate she really is part of it. Allison recalled: “It felt unreal. I wasn’t a dev, I don’t know how to code, and yet I got to be a part of it all? I felt like I was a fake. But Kimberly continues to remind me that I’m real, I get to be here, I get to stay, I have a place.”
\n\n\n\nShe was later encouraged to contribute by a WordPress community member to the Big Orange Heart, which aims to support and promote positive well-being and mental health within remote working communities. She said she felt ‘honored typing my words, pieces of my story, and sharing them with a community of people’.
\n\n\n\nShe also joined the WordCamp US 2021 online organizing team.
\n\n\n\nAllison enjoys the fact that in the WordPress community, ‘everyone here is constantly working to be better and do better’.
\n\n\n\n![\"\"](\"https://i0.wp.com/wordpress.org/news/files/2023/06/allison-1.jpg?resize=675%2C900&ssl=1\")
Allison was later diagnosed with two additional neurological conditions: Functional Neurological Disorder and Migraine. She said: “If it were not for WordPress I would really be unable to work. But WordPress and its community continue to be a part of my life and I am grateful to everyone who’s helped me along my way. I don’t know where I would even be without it.”
\n\n\n\nShe strives to raise awareness of dynamic disabilities and invisible illnesses like her own through podcasts and social media. She feels that her WordPress friends have helped her both in her professional life and in her wish to be an advocate for others with disabilities too.
Allison hopes reading of her experience will help others who are worried about not progressing in a WordPress career due to health concerns.
\n\n\n\n\n“I hope that it will remind anyone reading this that WordPress is a space for everyone. Healthy or not, developer or not, blogger or not — WordPress belongs to you too.”
\nAllison Dye
Help share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Allie Dye (@allisondye) for sharing about her adventures in WordPress.
\n\n\n\nProps to Abha Thakor (@webcommsat) and the late Surendra Thakor (@sthakor) for interviews and writing the feature, Meher Bala (@meher) for work on images, and to Meher, Maja Loncan (@mloncar) and Chloe Bringmann (@cbringmann) for reviews.
\n\n\n\nThe People of WordPress series thanks Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support.
\n\n\n\n![\"HeroPress](\"https://i0.wp.com/wordpress.org/news/files/2020/03/heropress_logo_180.png?resize=180%2C135&ssl=1\"){kind=logo}
This People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress
\nWordPress 6.3 Beta 2 is ready for download and testing. This is the first release of the 6.3 cycle, as there was no Beta 1 due to technical issues with packaging the release. Rather than further delaying a beta release, the release squad has decided to package and ship Beta 2.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, the release squad recommends you evaluate Beta 2 on a test server and site.
\n\n\n\nWordPress 6.3 demonstrates incredible progress toward achieving the goals outlined in the WordPress roadmap and is the final major release of Phase 2. Phase 2 has focused mainly on the Site Editor, enabling site creators to build websites, design compelling layouts, and manage content without toggling between multiple configuration areas or editing code.
\n\n\n\nLearn more about Gutenberg updates debuting since WordPress 6.2 by reviewing prior editions of What’s New in Gutenberg posts for 15.2, 15.3, 15.4, 15.5, 15.6, 15.7, 15.8, 15.9, 16.0, and 16.1.
\n\n\n\nWordPress is the result of contributions by users, developers, and extenders across the globe. As this community seeks new features, the platform will continue to evolve, including the site editing features and beyond. Get an overview of the 6.3 release cycle, and check the Make WordPress Core blog for 6.3-related posts in the coming weeks for further details.
\n\n\n\nThis latest WordPress release includes many updates spanning all platform areas, emphasizing the editing experience and polishing usability. This release contains more than 500 new features and enhancements and 400+ bug fixes.
\n\n\n\nFollowing the incredible performance improvements introduced in 6.2, the release includes more than 170 performance-related updates, including adding defer and async support to the WP Scripts API and fetchpriority support for images. Optimizations were made to block template resolution, image lazy-loading, and the emoji loader, all of which benefit LCP performance. Support for PHP versions 8.0, 8.1, and 8.2 has been improved.
\n\n\n\nThe Site Editor expands to include navigating and editing pages, styles, templates, and content. The unified site editing experience will include a distraction-free mode, enhanced navigation, and an improved loading experience. Additionally, you can use the Site Editor to preview a block theme and adjust your site before activating the new theme. This release includes style revisions so you can toggle between and preview different saved styles. Rounding out the changes, 6.3 ushers in a new Command Palette, enabling users to context switch and perform actions quickly across different sections of the site editing experience.
\n\n\n\nNew blocks for details and footnotes debut in this release, along with updates for better handling of image aspect ratios and improved fallback states. Spacer blocks now include presets, and the cover block gets updates for managing text colors and layout support.
\n\n\n\n![\"\"](\"https://i0.wp.com/wordpress.org/news/files/2023/06/Spacing-Presets.png?ssl=1\")
Reusable blocks have been renamed to synced patterns. This change reflects the unification of reusable blocks and traditional block patterns (unsynced patterns) within the Editor. A new option allows you to assign patterns to templates, adding the ability to have starter patterns to speed up the creation process. Site creators can now easily create, save, and manage custom synced and unsynced patterns, as well as browse a directory of curated patterns. Additionally, the duotone filter and captions can now be edited in the Styles interface.
\n\n\n\n![\"\"](\"https://i0.wp.com/wordpress.org/news/files/2023/06/Styling-Captions.png?ssl=1\")
Some key usability highlights include toolbar updates, updated template descriptions, enhanced list view drag-and-drop, improved padding and margin controls, and a new area for managing patterns (including reusable blocks, now called synced patterns.) Link control receives some updates, rounding out high-level usability enhancements in 6.3.
\n\n\n\n![\"\"](\"https://i0.wp.com/wordpress.org/news/files/2023/06/Add-and-modify-descriptions-for-templates.png?ssl=1\")
WordPress remains steadfast in making the site-building experience accessible to everyone. 6.3 incorporates over 50 accessibility improvements across the platform. Improved labeling, optimized tab and arrow-key navigation, revised heading hierarchy, and new controls in the admin image editor allow those using screen readers, keyboard navigation, and other assistive technology to navigate more easily. The login form, installation steps, and list tables (for sorting and selection) have all been updated. Additional accessibility tickets are viewable in the WordPress Trac.
\n\n\n\nThis release includes auto-rollback for failed manual updates of themes and plugins.
\n\n\n\nPlease note that the features in this list may change before the final release.
\n\n\n\nTesting 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.
\n\n\n\nWhile testing the upgrade process is essential, testing new features is too. Review the many new features listed above and focus your testing efforts on those areas in particular.
\n\n\n\nIf you encounter an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs.
\n\n\n\nNew to testing? This detailed guide is a great place to start if you’ve never tested a beta release.
\n\n\n\nWant to know more about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on the Making WordPress Slack.
\n\n\n\nBetween the Beta 2 release and the final release candidate (RC) for each new WordPress version, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
\n\n\n\nYou can test WordPress 6.3 Beta 2 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the Beta 2 version (zip).
\n\n\n\nOption 3: Use the following WP-CLI command:
\n\n\n\nwp core update --version=6.3-beta2
The current target for the final release is August 8, 2023, which is about six weeks away. Your help testing this version ensures everything in this release is the best.
\n\n\n\nA chapter closes
Excitement yet much newness
Phase 2 finale
Thank you to the following contributors for collaborating on this post: @DanSoschin, @Meher, @JPantani, @CBringmann, @AudrasJB, @annezazu, @ndiego, @davidbaumwald, @desrosj, @priethor, @flixos90, @wildworks, and @JPantani for authoring the haiku.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15193\";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:5;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"WP Briefing: Episode 58: A New Wave for WordPress Events\";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:78:\"https://wordpress.org/news/2023/06/episode-58-a-new-wave-for-wordpress-events/\";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, 19 Jun 2023 13: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";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:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";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:53:\"https://wordpress.org/news/?post_type=podcast&p=15179\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:145:\"Hear special guest host Chloé Bringmann and special guest Angela Jin in the WordPress Briefing as they discuss the next generation of WordCamps.\";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:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:59:\"https://wordpress.org/news/files/2023/06/WPBriefing-058.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s: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:\"Brett McSherry\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:15637:\"\nJoin WordPress guest host, Chief of Staff and Head of Operations, Chloé Bringmann, and special guest Head of Programs and Contributor Experience, Angela Jin, in the 58th episode of the WordPress Briefing as they discuss the next generation of WordCamps.
\n\n\n\n(Intro music)
\n\n\n\n[Chloé Bringmann 00:00:10]
\n\n\n\nHello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your guest host Chloé Bringmann. And here we go.
\n\n\n\n(Intro music)
\n\n\n\n[Chloé Bringmann 00:00:40]
\n\n\n\nSo I have the privilege of guest hosting this episode of the WordPress Briefing. And today I have with me a very special guest. The Head of Programs and Contributor Experience, Angela Jin. Welcome. Before we dive into all the questions, can you tell me and our listeners a little bit about your role in the WordPress community?
\n\n\n\n[Angela Jin 00:01:01]
\n\n\n\nYeah, happy to, and thank you so much for having me. I’m very excited to be here. I am the Head of Programs and Contributor Experience, and I provide oversight and guidance for our WordPress programs, such as our events programs, training, and Five for the Future, with an eye toward ensuring their sustainability and growth. I’m very fortunate to work with our contributors across many teams around the world. In addition to troubleshooting and helping folks figure out how to move forward, I also spend a good amount of time exploring with others what could be in our programs.
\n\n\n\n[Chloé Bringmann 00:01:41]
\n\n\n\nWe just got back from WordCamp Europe in Athens, Greece. It was such an energizing event for me, but I’m curious about what your impressions were of the past week.
\n\n\n\n[Angela Jin 00:01:52]
\n\n\n\nYeah, it was fantastic. I’m always really inspired by what a group of like-minded people can achieve together. There’s a lot of passion for this particular WordCamp, and it made for a really wonderful WordPress experience. Full of lots of great connections and memories; I have a million follow-ups and probably even more thoughts to reflect on. So it’s great. There were a lot of new WordPressers there. So it was lovely to meet them. And I’m really excited to see how many exciting new projects and ideas that we have in the space.
\n\n\n\n[Chloé Bringmann 00:02:27]
\n\n\n\nSame, you said it perfectly. Josepha also mentioned in the flagship’s keynote, the proposal for the next generation of WordCamps. I’m curious about what the main ideas and goals, as discussed thus far, are of that proposal.
\n\n\n\n[Angela Jin 00:02:42]
\n\n\n\nFor sure. So WordCamps have been fundamental for the WordPress community for a very long time. And while they have continued to grow larger and reach more places around the world, it’s also undeniable that the way that people meet has changed since 2006.
\n\n\n\n[Angela Jin 00:03:01]
\n\n\n\nAnd so, just as WordPress itself iterates we’re looking at iterating on WordCamps so that they move from fundamental to indispensable for the WordPressers of today and tomorrow. So event attendees today are looking to learn essential skills, make connections that lead to neat opportunities, and more.
\n\n\n\n[Angela Jin 00:03:23]
\n\n\n\nSo to that end, we put forth an updated purpose for our events, which is that WordPress events spark innovation and adoption by way of accessible training and networking for users, builders, designers, and extenders. We celebrate community by accelerating 21st-century skills, professional opportunities, and partnerships for WordPressers of today and tomorrow.
\n\n\n\n[Angela Jin 00:03:47]
\n\n\n\nSo the goal here is to create events that are more clearly defined – who these are for what you will gain from attending. We are looking to see events that take a deeper dive into content, or topics and provide more advanced content. And let’s try out some different formats and see how that shapes our event experience. And so it is a big shift. And change is always hard.
\n\n\n\n[Angela Jin 00:04:13]
\n\n\n\nHowever, the feedback that I’ve gotten so far, and certainly at WordCamp Europe, is that this is a very welcome evolution. And the Community team has already received over 60 proposals. So I’m very excited about that. In fact, a WordPress Community Day in Rome has already been announced and is focused on providing meet-up organizing and community management skills. So that’s pretty cool.
\n\n\n\n[Chloé Bringmann 00:04:37]
\n\n\n\nWow, that’s incredible. I love that we’ve gotten 60 suggestions already and that we already have an event in place. That’s fantastic. In that blog post, too, it’s mentioned that WordCamps should prioritize inclusivity and diversity. How can organizers ensure these values are upheld in the next generation of WordCamps and beyond events? Into our day-to-day project involvement?
\n\n\n\n[Angela Jin 00:05:04]
\n\n\n\nExcellent question. So while WordCamps themselves are changing, some of our core values, like prioritizing inclusivity and diversity, are non-negotiable. For the whole project, we have a diversity, equity, and inclusion statement, and a Code of Conduct that lays out how we expect our community to engage with each other in this space.
\n\n\n\n[Angela Jin 00:05:27]
\n\n\n\nAnd on top of that, our programs do focus on providing resources and training like how to create a diverse speaker roster. And we have diverse speaker training workshops on how to organize a diverse and inclusive WordPress event. And we also have a great list of third-party resources as well. And so, with so many events, we create a lot of opportunities to grow as a visible contributor, whether it is a speaker, a volunteer, or an organizer.
\n\n\n\n[Angela Jin 00:05:56]
\n\n\n\nAnd so with the next generation of events, we could more intentionally create these spaces for groups that historically have been underrepresented. Even long before my post went live, the BlackPress meetup group, for example, wanted to create an event that connected with historically black colleges and universities. And an event like that that really invites a specific group to learn all about WordPress would be a really great experience and a wonderful way to celebrate that community and a great connection to the broader community so that we can intentionally get to the diversity that we want to see.
\n\n\n\n[Angela Jin 00:06:38]
\n\n\n\nAnd I also want to add that the people who are underrepresented in our community are more likely to need financial sponsorship. And so even though we do keep our ticket prices low so that our events are more easily accessible, the cost of travel continues to increase, not to mention the time and energy required to participate in these events. So an excellent way that companies can help is to sponsor somebody’s time and somebody’s contributions, which we’re always trying to encourage through the Five for the Future program.
\n\n\n\n[Chloé Bringmann 00:07:11]
\n\n\n\nBeautiful. So, with that in mind, how do you foresee the next generation of WordCamps impacting the WordPress community, that larger ecosystem? So, what changes do you hope to see regarding community engagement, learning opportunities, and best practices?
\n\n\n\n[Angela Jin 00:07:31]
\n\n\n\nI foresee us evolving our tried and true event format into a dynamic wealth of community-led opportunities. I know that online events were pretty exhausting during the worst of the pandemic, but there is a ton of unexplored opportunities there. And community research is also showing that online is a great way to create more inclusive and diverse events.
\n\n\n\n[Angela Jin 00:07:58]
\n\n\n\nThe Training team, with their learn WordPress online workshops, have really led the way with our online events. And there are so many more people that we can reach there.
\n\n\n\n[Angela Jin 00:08:08]
\n\n\n\nAnd so in addition to providing more advanced content, I also hope to see content around broader tech and business trends that influence WordPress, and conversely, how WordPress can shape those trends as well. And with all of that, I really hope that we can bring in more community members that otherwise wouldn’t be interested in what we currently offer, especially a younger generation that will help us drive the next generation of WordPress, the open source project.
\n\n\n\n[Chloé Bringmann 00:08:39]
\n\n\n\nVery excited to hear all of this, and I bet our listeners are too. I’m curious how they and community members can provide feedback or get involved with this next generation of WordCamps.
\n\n\n\n[Angela Jin 00:08:50]
\n\n\n\nI’m going to encourage everyone, please come chat with the Community team and comment on the current posts. We really welcome your feedback to help us get our events to this next iteration of what they will become. There are two posts, in particular, one is to suggest ideas of event formats and topics that you would like to see. And the second is if you are an organizer, we’re inviting you to hear some recommendations for improved tooling that would be helpful for your event site. And we’ll include links to those posts in the show notes.
\n\n\n\n[Chloé Bringmann 00:09:26]
\n\n\n\nOne final question for you, Angela. Any thoughts as we prepare for WordCamp US and the Community Summit, which will be in National Harbor, Maryland, in August?
\n\n\n\n[Angela Jin 00:09:37]
\n\n\n\nFor the Community Summit in particular, if you want to attend and you haven’t already applied, please please do make sure to apply as soon as possible. And encourage somebody else who you think should attend to apply as well.
\n\n\n\n[Angela Jin 00:09:53]
\n\n\n\nAnd if financial constraints are a blocker, we are aiming to help with the cost of hotel and or flight. And so one way to help support the diversity and inclusion of this event, and really to the whole project, is to also contribute to the Community Summit travel fund. You can find information about all of that on the Community Summit site.
\n\n\n\n[Angela Jin 00:10:15]
\n\n\n\nAnd next, if you have a topic in mind that you think needs to be discussed at the Community Summit, please please also share that information with us as well. And last but not least, I am, I am so excited. I’m not going to spoil anything. But I have been working with the WordCamp US organizing team and looking at some of what they have planned and some of the content. It’s going to be a truly incredible event, so don’t miss out.
\n\n\n\n[Chloé Bringmann 00:010:41]
\n\n\n\nOh, wonderful. Thank you so much for joining me, Angela. And I can’t wait to see you and the WordPress community in August in person.
\n\n\n\n[Chloé Bringmann 00:010:58]
\n\n\n\nWhich brings us now to our small list of big things. First up is the proposal and establishment of a new WordPress contributor team, the Sustainability team. Coming into WordCamp Europe, a proposal was put forward to create a team that would embed sustainable practices and processes in the ecosystem to ensure the Project’s longevity, both socially, economically, and as well environmentally. At WordCamp Europe, this proposal was confirmed, and the Sustainability team is now officially the 22nd contributor team that WordPressers can support with their contributions. Head on over to their making WordPress Slack channel, #sustainability, and join the conversation.
\n\n\n\n[Chloé Bringmann 00:011:39]
\n\n\n\nSecond, I would like to call your attention to the 6.4 development cycle post that was published on June 5th. 6.4 will be the third major release of 2023 and supports our diversity, equity, and inclusion efforts by being led by those contributors that identify as underrepresented gender. This release will also be the first to kick off phase three of the Gutenberg roadmap, which is collaborative editing and workflows. I’ve included a link to the post in our show notes and encourage anyone who is interested in being part of this momentous release to join us in making this both impactful and meaningful.
\n\n\n\n[Chloé Bringmann 00:012:16]
\n\n\n\nFinally, WordCamp US, as discussed, will be upon us before we know it starting on August 24th at National Harbor, Maryland. While tickets may be sold out, volunteers are still very much needed to make the flagship event run smoothly. So stop by us.wordcamp.org, raise your hand, and join us in August for engagement, inspiration, and learning. And that, my friends, is your small list of big things. I’m your guest host Chloé Bringmann and thank you for tuning in today for the WordPress Briefing.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15179\";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:6;a:6:{s:4:\"data\";s:66:\"\n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"Twenty Years of WordPress at WCEU\";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/06/twenty-years-of-wordpress-at-wceu/\";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, 10 Jun 2023 22:21:51 +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:8:\"category\";a:4:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";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:1;a:5:{s:4:\"data\";s:7:\"General\";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:2;a:5:{s:4:\"data\";s:8:\"WordCamp\";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:3;a:5:{s:4:\"data\";s:4:\"WCEU\";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=15167\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:373:\"Inspiring the global community The atmosphere was electric at WordCamp Europe (WCEU) 2023 in Athens, Greece, as WordPress celebrated its 20th anniversary and the opportunity to gather in person for inspiration and engagement. More than 2,500 individuals from 94 countries came together in person or through the live stream to participate in a remarkable three-day […]\";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:16:\"Jonathan Pantani\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6426:\"\nThe atmosphere was electric at WordCamp Europe (WCEU) 2023 in Athens, Greece, as WordPress celebrated its 20th anniversary and the opportunity to gather in person for inspiration and engagement. More than 2,500 individuals from 94 countries came together in person or through the live stream to participate in a remarkable three-day event (plus Contributor Day) filled with talks, networking, and learning opportunities. The event concluded on June 10 with a captivating keynote address by WordPress co-founder Matt Mullenweg, Executive Director Josepha Haden Chomphosy, and Gutenberg Product Architect Matías Ventura, who highlighted the advancements and upcoming milestones of the WordPress Project.
\n\n\n\nOne significant update shared during the keynote was the successful reactivation of WordCamps. This time last year, we organized eight in-person WordCamps, and by the end of 2022, the number had risen to 23. Thanks to the enthusiasm and involvement of the WordPress community, we are already on track to organize 25 WordCamps in the first half of this year alone.
\n\n\n\nJosepha also emphasized the importance of the upcoming Community Summit on August 22-23. This in-person gathering brings contributors together across the WordPress open source project, fostering cross-project discussions vital for future growth and sustainability. For more information, visit the official Community Summit website.
\n\n\n\n![\"Total](\"https://i0.wp.com/wordpress.org/news/files/2023/06/Five-for-the-Future-WCEU-1.png?resize=585%2C365&ssl=1\")
Discussing the Five for the Future (5ftF) program, Josepha highlighted the impressive growth in active contributors and company pledges over the past year. She also underscored the expansion of the WordPress ecosystem, citing examples like Openverse, which now provides access to nearly 800 million images and audio files, all easily accessible in the Site Editor.
\n\n\n\nAnother exciting addition to the WordPress repertoire is WP Playground. This new feature allows users to build WordPress applications instantly in the browser without needing a PHP server. This tool provides a swift and seamless experience, reducing the installation time from five minutes to a near-instantaneous 500 milliseconds. The application of WP Playground may seem like magic, but its practical application promises tangible and revolutionary benefits for WordPress users.
\n\n\n\nMatías Ventura then took the stage to share updates on Gutenberg. Through a visually stunning video built entirely with blocks, he showcased the six-year development journey and the transition from words to blocks to a final design. The upcoming WordPress version 6.3 will mark the completion of the first two phases of Gutenberg, consolidating all these features into a cohesive and user-friendly experience. He also highlighted the introduction of features such as the Wayfinder tool, Style Book, and the ability to save patterns, further empowering users to own their web presence and voice.
\n\n\n\nFollowing the keynote presentation, the WordPress leadership engaged in a lively Q&A session with the audience, further illustrating the continuous evolution within the WordPress Project. This session highlighted how the WordPress community innovates, iterates, and continually improves to create a better platform for today and tomorrow.
\n\n\n\nJoin the global community and be part of the WordPress journey toward a brighter future!
\n\n\n\nSpecial thanks to @cbringmann and @eidolonnight for review and collaboration.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15167\";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:7;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"The Month in WordPress – May 2023\";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:67:\"https://wordpress.org/news/2023/06/the-month-in-wordpress-may-2023/\";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, 06 Jun 2023 10:15:56 +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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";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:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";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=15100\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:350:\"May has been a month of celebrating WordPress and the open source community that makes it possible. In honor of the project’s 20th anniversary, WordPress Executive Director Josepha Haden Chomphosy reflected on this journey and the opportunity to build a better future for those who come after: The more our community invests in itself and […]\";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:\"Reyes Martínez\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:16972:\"\nMay has been a month of celebrating WordPress and the open source community that makes it possible. In honor of the project’s 20th anniversary, WordPress Executive Director Josepha Haden Chomphosy reflected on this journey and the opportunity to build a better future for those who come after:
\n\n\n\n\n\n\n\n\nThe more our community invests in itself and supports one another, the stronger WordPress and the open source software movement become.
\nJosepha Haden Chomphosy in Celebrating 20 Years of WordPress.
Read on for highlights of this milestone and the latest updates in the WordPress space.
\n\n\n\n\n\n\n\nMay 27, 2023, marked the 20th anniversary of WordPress’ first release. Since its inception by Matt Mullenweg and Mike Little in 2003, the project has transformed the digital publishing landscape and enabled millions of people to craft their stories.
\n\n\n\nWordPress enthusiasts from all over the world gathered at more than 130 events to celebrate this important milestone. WP20’s commemorative book, Building Blocks: The Evolution of WordPress, was published in tandem and documents some of the most significant moments and changes of the last decade of the project.
\n\n\n\n![\"3D](\"https://i0.wp.com/wordpress.org/news/files/2023/06/wp20-celebrate-desktop-1.png?resize=1024%2C576&ssl=1\")
The anniversary date may have passed, but the festivities and fun aren’t over. You can still join a meetup, sign the #WP20 From Blogs to Blocks campaign birthday card, or participate in #WP20 social celebrations.
\n\n\n\n\n\n\n\n\n\n\n\n\nJoin Josepha Haden Chomphosy in Episode 55 of WP Briefing as she looks back at the 20 years of WordPress and how the community made WordPress what it is today.
\n
Work on WordPress 6.3 officially kicked off with the announcement of its development cycle and release squad. Set for release on August 8, 2023, this version will be the second major update of WordPress in 2023 and will mark the end of Phase 2 of the project’s development roadmap.
\n\n\n\nWordPress 6.3 aims to bring a cohesive site editing experience by introducing expanded functionality, richer interfaces, and a dedicated focus on refinement.
\n\n\n\n\n\n\n\n\n\n\n\n\nCheck out the 6.3 roadmap post for a tentative preview of anticipated features.
\n
WordPress 6.2.2 became available for download on May 20, 2023. This release was a quick response to resolve a regression introduced in 6.2.1, specifically with shortcode support in block templates, and to further patch a vulnerability already addressed in the previous version.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Three new versions of Gutenberg have shipped in the last month:
\n\n\n\n\n\n\n\n\n\n\n\n\nThe latest Core Editor Improvement post highlights features such as revisions and the ability to preview block themes, and how they enable a smoother site editing experience.
\n
\n\n\n\n\n\n\n\n\nWhat is WordPress Playground, and why it matters? WP Briefing Episode 56 discusses the benefits and potential of this tool with special guests Rich Tabor and Adam Zielinski.
\n
\n\n\n\n\n\n\n\n\nWhich next generation of WordPress events would you like to see? Share your ideas and start exploring new event formats this year.
\n
![\"🇪🇸\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ea-1f1f8.png\")
WordCamp Cartagena, Spain on June 10-11, 2023![\"🇺🇸\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f1fa-1f1f8.png\")
WordCamp Montclair, NJ, USA on June 24, 2023\n\n\n\n\n\n\n\n\nJoin WordPress project leadership on June 10 at WordCamp Europe 2023 to hear about the latest developments and what’s next for WordPress. Check out the schedule for details.
\n
Have a story we should include in the next issue of The Month in WordPress? Fill out this quick form to let us know.
\n\n\n\nThe following folks contributed to this Month in WordPress: @rmartinezduque, @nahidsharifkomol, @chaion07, @devinmaeztri, @bsanevans, @ninianepress.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15100\";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:8;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"WP Briefing: Episode 57: The Power of WordPress Mentorship\";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:80:\"https://wordpress.org/news/2023/06/episode-57-the-power-of-wordpress-mentorship/\";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, 05 Jun 2023 13: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:7:\"Podcast\";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:1;a:5:{s:4:\"data\";s:11:\"wp-briefing\";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:53:\"https://wordpress.org/news/?post_type=podcast&p=15089\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:215:\"Join WordPress Executive Director Josepha Haden Chomphosy in the 57th episode of the WordPress Briefing as she discusses the Contributor Mentorship Program to help increase the success of new contributors over time.\";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:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2023/06/WP-Briefing-057.mp3\";s:6:\"length\";s:1:\"0\";s:4:\"type\";s: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:\"Brett McSherry\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7743:\"\nJoin WordPress Executive Director Josepha Haden Chomphosy in the 57th episode of the WordPress Briefing as she discusses the Contributor Mentorship Program to help increase the success of new contributors over time.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nEditor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry
Song: Fearless First by Kevin MacLeod
[Josepha Haden Chomphosy 00:00:00]
\n\n\n\n(Intro music)
\n\n\n\nHello everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks.
\n\n\n\nI’m your host, Joseph Hayden Chomphosy. Here we go!
\n\n\n\n(Intro music)
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nOver the course of this year, there has been a lot of research and examination of the contributor funnel in the WordPress community. That research confirms some assumptions about what most contributor stories have in common: the hurdles, the general paths taken, and the way that problem-solving was done. Then in February of this year, Hari Shanker published a proposal for a mentorship program for WordPress.
\n\n\n\nAnd now we’ve got a pilot program that’s been defined and is waiting for your feedback. If you’ve not read the post about the contributor mentorship program, for one do it. But if you would rather hear a synopsis from me, don’t worry, I’m about to give you a 10-cent tour.
\n\n\n\n[Josepha Haden Chomphosy 00:01:22]
\n\n\n\nFirst up, who is doing this? This pilot program has been outlined by a community working group. We often have working groups in WordPress, and they almost always have specific projects around events or programs, or code updates. Since this working group is focused on a project-wide program, there is project-wide representation in it. All the names are at the bottom of the post, which you can find in our show notes. But it’s got folks who contribute with code or contribute with time or contribute with design folks who are self-sponsored or corporately sponsored, just a nice mix of people. The program as a whole, though, is being stewarded by Hari Shankar, a longtime supporter of and contributor to WordPress.
\n\n\n\n[Josepha Haden Chomphosy 00:02:06]
\n\n\n\nSo next, what is this for? There are a few goals for the program. But the overarching goal is to increase the success of new contributors over time. We can all agree that if we were to have 1000s of new contributors every day, but they couldn’t find their way to impactful contributions or meaningful connections quickly, then we would have done them a disservice. And they probably won’t continue to be part of the community without a bit more effort.
\n\n\n\nThe when and the where are essentially “right now and right here,” so that brings us finally to Why. Why are we doing this mentorship program? Apart from to help people who want to contribute have an easier path to success – which frankly is enough of a reason anyway – the why is wrapped up in our overall philosophies in the project. If we believe that good ideas can come from anywhere and that contributions of any size matter. And that open source is an idea that can change our generation and that we are democratizing publishing, then bringing new people brings new ideas, and beginner contributions can grow over time. We can maintain this idea, this concept of open source, into the next generation and to future generations. And always keep our sights on the open web. To learn more about this and other project-wide initiatives, swing by make.wordpress.org/project or check the links in today’s show notes on wordpress.org/news/podcast.
\n\n\n\n[Josepha Haden Chomphosy 00:03:53]
\n\n\n\nWhich brings us now to our small list of big things.
\n\n\n\n[Josepha Haden Chomphosy 00:03:56]
\n\n\n\nFirst on the list is WordCamp Europe. That’s coming up at the end of the week on June 8 through 10th in Athens, Greece. There will be a major update from Matt and friends, so even if you aren’t there in person, keep an eye out for those recordings. But for those who are there and you’re curious about the mentorship program or anything else to do with WordPress and contributing to the project, you can come find me or Angela Jin, Hari will also be there, Chloé will be there, Héctor will be there, lots of people, and we want to hear your thoughts and answer your questions.
\n\n\n\n[Josepha Haden Chomphosy 00:04:27]
\n\n\n\nSecond is a call for brainpower! A call for your brainstorms! On the subject of the next generation, we’ve got a discussion going on about the next generation of WordCamps. We’ve been discussing what new types and varieties might be available, and that might make sense for people as we get back to in-person events. So if you’ve got a kind of WordCamp that you’ve been desperately wanting to try, now’s the time to let folks know about it.
\n\n\n\n[Josepha Haden Chomphosy 00:04:54]
\n\n\n\nAnd the final thing is the second volume of The WordPress history book called Building Blocks: The Evolution of WordPress is now available for download in several formats as well as on GitHub. Stop buy, give it a read, and relive some of the highlights of the past ten years of the WordPress project.
\n\n\n\n[Josepha Haden Chomphosy 00:05:12]
\n\n\n\nAnd that, my friends, is your smallest of big things. Thanks for tuning in today for the WordPress Briefing. I’m your host Josepha Haden Chomposy, and I’ll see you again in a couple of weeks.
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"15089\";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:9;a:6:{s:4:\"data\";s:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"People of WordPress: Stefano Cassone\";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:71:\"https://wordpress.org/news/2023/05/people-of-wordpress-stefano-cassone/\";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, 31 May 2023 20:48:58 +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:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";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:1;a:5:{s:4:\"data\";s:8:\"Features\";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:2;a:5:{s:4:\"data\";s:10:\"Interviews\";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:3;a:5:{s:4:\"data\";s:9:\"HeroPress\";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:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";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=15030\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}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:125:\"The People of WordPress feature series goes to Italy to interview web designer, photographer and translator Stefano Cassone. \";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:11:\"Abha Thakor\";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:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:15999:\"\nWith WordCamp Europe 2023 in June, we feature Stefano Cassone, a web designer, photographer and volunteer translator, who believes his life has been transformed through WordPress and its community.
\n\n\n\nThe People of WordPress series shares inspiring stories of how people’s lives can change for the better through WordPress and its global community of contributors.
\n\n\n\n![\"Stefano](\"https://i0.wp.com/wordpress.org/news/files/2023/05/stefano-featured-img.jpg?resize=1024%2C535&ssl=1\")
Stefano has always been fascinated by the internet. His initial learning in the 1990s was through joining friends at a local pub where they could explore how websites were structured and learn to use chat software.
\n\n\n\nThis led to Stefano creating websites for fun in 1998, and his first paid job was for the shop where he bought comics. He turned to content management systems (CMS) to speed up the creation process for sites, but found he needed more documentation to really understand their capabilities. Then he read a magazine article about WordPress, a CMS which was being used to make incredible blog sites, and was supported by an international community and documentation. Over time, Stefano started using that documentation to work on websites in Italian.
\n\n\n\nStefano describes himself as an introvert. He found that WordPress helped him to work from home, to develop his skills and the quality of what he could produce, as well as build his self-confidence.
\n\n\n\nA catalyst for the turning point in his life and career was the discovery of an area for events on the WordPress dashboard. On this page, he found a forthcoming local meetup in Rome.
\n\n\n\nIn November 2017, Stefano took the step to go along to this event, led by a curiosity of what he might discover and intrigued by how a software could be supported by a vast community. The topic at the event was on WP-CLI, a command line interface for WordPress. He recalled that he felt outside his comfort zone as he did not regard himself as a developer and at that point, had only used the software for simple jobs. He wondered whether using the software as his only CMS was going to be a long term option and if these meetups were suitable for him.
\n\n\n\nAt the meetup, people were talking about a forthcoming event, called WordCamp Rome. Through his research, he saw that there was a lot of enthusiasm for this event. This intrigued him and he wondered if it would show him that he could have a career using the software after all.
\n\n\n\nUnfamiliar with WordCamps, Stefano found it difficult at first to know what he could go to and how to get involved, but he persevered and attended the event.
\n\n\n\n\n\n\n\n\n“The WordCamp was a great discovery: talks at all levels from basic to those for developers, advanced and very advanced. I was immediately struck by the enthusiasm of the volunteers. It was an environment where I felt very comfortable, so much so, that I asked myself how I could participate in some WordCamps.”
\nStefano Cassone
From this event, Stefano was encouraged by those he met to consider applying as a volunteer for a future WordCamp.
\n\n\n\nThere was also much talk at the event about ‘Slack’. It was new to Stefano, but with help from those attending, he signed up for the messaging tool Slack, used by the WordPress community. He was still unsure how he could contribute, and if he would be welcome.
\n\n\n\n![\"Italian](\"https://i0.wp.com/wordpress.org/news/files/2023/05/stefano-wc-italia-2022.jpg?resize=800%2C600&ssl=1\")
Stefano took the plunge and was excited to find there was a team called Polyglots. In this team, people from across the world translate the WordPress software into many different languages. He started with translating a theme he was using in his work. Little by little he became more interested in plugins and attended meetings with other translators. He offered his skills to translate into Italian themes and plugins in general and as his experience grew, he took on the volunteer role of a General Translation Editor. He also took care of the translation into Italian of the WordPress Core. More recently he has joined the group of translators for the HelpHub, which is part of the WordPress documentation system.
\n\n\n\nHe said: “Participating in the WordPress Slack has helped me enormously: I’ve met a lot of people who I now call friends. Moreover, by translating, I learned a lot about how themes and plugins work.
\n\n\n\n“It’s a great way to contribute to WordPress, especially for someone like me who is not a developer. Translating also allows me to fully understand how WordPress works.”
\n\n\n\n\n\n\n\n\n“I always say that translating themes, plugins, and the Core software is the best way to learn WordPress, better than any course or book.”
\nStefano Cassone
![\"Stefano](\"https://i0.wp.com/wordpress.org/news/files/2023/05/stefano-at-WC-2019.jpg?resize=667%2C500&ssl=1\")
Stefano’s growing commitment to the open source WordPress project was further boosted through his volunteering. He was a volunteer at WordCamp Rome 2018 and participated there in his first Contributor Day where he had the opportunity to translate the software with others.
\n\n\n\nHe was also able to bring his own hobbies and skills to help the project grow and reach others. One example was his passion for photography, and he volunteered as a photographer for many other events in Italy organized by the WordPress community. He said: “This commitment to the community also allows me to have fun: being a photographer means having the opportunity to walk around the halls and capture moments of the life of a WordCamp.” The more WordCamps he attended, the more he wanted to be part of and keep contributing to the wider WordPress community.
\n\n\n\n![\"Stefano](\"https://i0.wp.com/wordpress.org/news/files/2023/05/stefano-at-the-support-table-contributor-day.jpg?resize=1024%2C683&ssl=1\")
When Stefano was asked to become an organizer for the WordPress meetup in Rome in October 2019, he knew he wanted to be part of reaching and supporting more people in his area. He faced challenges with finding venues, but a greater issue was to come: the Covid-19 pandemic.
\n\n\n\nSpurred on by the Italian WordPress community as a whole, he was determined that the meetup was still needed. The regular event was transformed into an online meeting. He was able to gain help from people he had met as a volunteer to share their expertise with meetup attendees.
\n\n\n\nThe community in Italy also worked together to put on WordCamp Italia online. It brought together the organizers of previous meetups and WordCamps, and new contributors too. Stefano volunteered in both online editions of this camp, including being part of the social and communication team. He found it to not only be a fun experience but also one that helped him grow professionally and learn from so many others.
\n\n\n\nHe went onto help restart the Rome WordPress meetup in-person meetings in May 2022, was an organizer for the third WordCamp Italy, and has been volunteering for camps in 2023.
\n\n\n\n![\"Stefano](\"https://i0.wp.com/wordpress.org/news/files/2023/05/stefano-at-a-wc.jpg?resize=533%2C800&ssl=1\")
“Persona and professional growth and friendship” are some of the things they have brought Stefano. Contributing boosted his confidence and willingness to try new opportunities in his work.
\n\n\n\nHe said: “The best thing I got out of joining the WordPress community was the chance to collaborate with some people on a working basis and, I have to say, that was incredible. Being with many of them you have an incredible opportunity to grow in knowledge, you just have to be ready to learn. With WordPress you never stop learning.”
\n\n\n\nHis top recommendation is: “Join your local meetup or think about organizing one, it will introduce you to an amazing world. Don’t be afraid to meet people at WordCamps and Contributor Days, because you will learn more there than in dozens of courses. Talk to people at those events and don’t worry. The WordPress community is inclusive so you’ll always feel welcome, and you will see enthusiasm like you’ve never seen at other IT events. Sign-up and get involved.”
\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Stefano Cassone (@deadpool76) for sharing about his adventures in WordPress.
\n\n\n\nThank you to Abha Thakor (@webcommsat), the late Surendra Thakor (@sthakor) and Meher Bala (@meher) for interviews, writing the feature and collaborating on images, to Chloe Bringmann (@cbringmann), Mark Smallman (@marks99), Nalini Thakor (@nalininonstopnewsuk), Mary Baum (@marybaum), and Maja Loncar (@majaloncar) for help with reviews.
\n\n\n\nThe People of WordPress series thanks Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support.
\n\n\n\nThis People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress
\nWelcome to a world-class fitness experience. Our team specializes in providing personalized training sessions, group workout classes, and Do-It-Yourself access to a multitude of fitness equipment. We will help you achieve the healthy physique that is best suited to your personal goals and lifestyle. Through dedication, professionalism, and an encouraging atmosphere you can and will achieve the body that you’ve been dreaming about.
\r\n\r\n![\"9hi8ujmsdza\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_9HI8UJMSdZA-imhwpb-16lt57g6yolmmw5.jpg\")
![\"b2-fbvrfx0o\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_b2-fBVrfx0o-imhwpb-zba1rzvazi2u1sy.jpg\")
If you want to experience the benefits of a customized workout program that focuses on your core areas, then try one of our personalized training classes. You’ll be hooked in five minutes!
\r\n\r\n![\"xv7k95vofa\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_Xv7k95vOFA-imhwpb-5blo5ds381thf3b.jpg\")
Sometimes we all need a little motivation to make it to the gym every week. These group workout classes will get you pumped (literally) for the gym!
\r\n\r\n![\"78t99kbcp_4\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_78T99kbcp_4-imhwpb-zbik273bhi2omad.jpg\")
Achieving a better physique is about more than simply shedding the pounds and improving muscle tones. Our yoga and health wellness classes will help you to focus on both your mental and physical well-being.
\r\n\r\n![\"yadcgbslhce\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_YadCgbsLHcE-imhwpb-kjakgkqww4nb5j2.jpg\")
The fitness-center is the best that I’ve ever seen. After a great workout I can head to the steam showers to give my muscles the relaxation that they need.
\r\n\r\n![\"s_nxt6gx-2a\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_s_NxT6Gx-2A-imhwpb-jifkmjomsrquohk.jpg\")
I was nervous about getting ready for my wedding day. I wanted to lose weight and was yo-yo dieting. The yoga classes really helped me find my Zen and lose the weight.
\r\n\r\n![\"4yx0oj7gf8o\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_4YX0oj7gf8o-imhwpb-ut5s3lmwf6dg2wc.jpg\")
My husband and I actually like coming to the gym… together! And it’s all thanks to the group fitness classes.
\r\n\r\n![\"8tn3fldtqbu\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/tmp_8tN3flDTQBU-imhwpb-kxmpsoge3h4672l.jpg\")
The staff is incredibly friendly. The trainers are amazing. Thanks for giving me the body I’ve always wanted.
\r\n\r\n![](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/coiWR0gT8Cw-1-imhwpb-91r89phud3kxfaw.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/a02c3692-c04b2dff-undrey150400263-200x200.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/14693b8d-a53981b4-yurok150900007-200x200.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/4ba64942-c3890b-bluefox150300073-200x200.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/aHR0cHM6Ly9zb3VyY2UudW5zcGxhc2guY29tLy1yV2p5ZE5oQVR3LzYwMHg0NTA_3D-imhwpb-qi6hj44g334fjqc.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/aHR0cHM6Ly9zb3VyY2UudW5zcGxhc2guY29tL19QZFpkVzdmaURjLzYwMHg0NTA_3D-imhwpb-24tawnme8snkr6i.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/aHR0cHM6Ly9zb3VyY2UudW5zcGxhc2guY29tL3ZHUTQ5bDlJNEVFLzYwMHg0NTA_3D-imhwpb-ceho1ljgk9lzazx.jpg\")
![\"\"](\"http://test.connectreleaseheal.com/wp-content/uploads/2018/05/aHR0cHM6Ly9zb3VyY2UudW5zcGxhc2guY29tL052VjgtcUZVVjRJLzYwMHgzMDA_3D-imhwpb-by6i1wxava2jjv6.jpg\")
admin@test.connectreleaseheal.com
\n\n777-765-4321
\n\n1234 Your St, City, STATE, 12345
\n\n\nPremium extension for the Total Upkeep plugin.<\\/p>\\n\",\"installation\":\"
Release date: April 29th, 2021<\\/p>\\n\\n
Release date: March 11th, 2021<\\/p>\\n\\n
Release date: February 16th, 2021<\\/p>\\n\\n
Release date: December 8th, 2020<\\/p>\\n\\n
Release date: December 2nd, 2020<\\/p>\\n\\n
Release date: October 15th, 2020<\\/p>\\n\\n
Release date: October 13th, 2020<\\/p>\\n\\n
Release date: August 12th, 2020<\\/p>\\n\\n
Release date: July 7th, 2020<\\/p>\\n\\n
Release date: July 7th, 2020<\\/p>\\n\\n
Release date: May 19th, 2020<\\/p>\\n\\n
Release date: February 19th, 2020<\\/p>\\n\\n
Release date: February 18th, 2020<\\/p>\\n\\n
Release date: December 13th, 2019<\\/p>\\n\\n
Release data: November 21th, 2019<\\/p>\\n\\n
Release date: October 1st, 2019<\\/p>\\n\\n
Release date: October 1st, 2019<\\/p>\\n\\n
Release date: May 21th, 2019<\\/p>\\n\\n
Release date: May 14th, 2019<\\/p>\\n\\n
Release date: Feb 14th, 2019<\\/p>\\n\\n
Release date: Dec 5th, 2018<\\/p>\\n\\n
Release date: Nov 20th, 2018<\\/p>\\n\\n
Release Date: October 25th, 2018<\\/p>\\n\\n
Release Date: April 11th, 2017<\\/p>\\n\\n
BoldGrid Backup Premium has been renamed to Total Upkeep Premium. Different name with the same great features.<\\/p>\\n\"}\";s:7:\"siteurl\";s:25:\"https://www.boldgrid.com/\";s:13:\"compatibility\";s:45643:\"{\"5.7\":{\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.6.3\":{\"1.5.9\":[100,95]},\"5.6.2\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.6.1\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.6\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.5.4\":{\"1.5.9\":[100,95]},\"5.5.3\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.5.2\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.5.1\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.5\":{\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.4.5\":{\"1.5.9\":[100,95]},\"5.4.4\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.4.3\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.4.2\":{\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.4.1\":{\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.4\":{\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3.7\":{\"1.5.9\":[100,95]},\"5.3.6\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3.5\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3.4\":{\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3.3\":{\"1.4.0-rc.2\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3.2\":{\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3.1\":{\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.3\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.9\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.8\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.7\":{\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.6\":{\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.5\":{\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.4\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.3\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.2\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2.10\":{\"1.5.9\":[100,95]},\"5.2.1\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.2\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.8\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.7\":{\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.6\":{\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.5\":{\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.4\":{\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.3\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.2\":{\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1.1\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.1\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.9\":{\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.8\":{\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.7\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.6\":{\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.5\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.4\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.3\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.2\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.10\":{\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0.1\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"5.0\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.9\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.8\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.7\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.6\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.5\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.4\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.3\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.2\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.14\":{\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.13\":{\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.12\":{\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.11\":{\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.10\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9.1\":{\"1.0.0\":[100,12],\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.9\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.9\":{\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.8\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.7\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.6\":{\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.5\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.4\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.3\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.2\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.10\":{\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8.1\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.8\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.9\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.8\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.7\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.6\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.5\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.4\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.3\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.2\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.12\":{\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.11\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.10\":{\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7.1\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.7\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.9\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.8\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.7\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.6\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.5\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.4\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.3\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.2\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.12\":{\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.11\":{\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.10\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6.1\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]},\"4.6\":{\"1.0.0-alpha.1\":[100,95],\"1.0.0-alpha.2\":[100,95],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.1.0-rc.1\":[100,95],\"1.1.0\":[100,95],\"1.1.1\":[100,95],\"1.1.2\":[100,95],\"1.2.0-rc.1\":[100,95],\"1.2.0\":[100,95],\"1.2.1\":[100,95],\"1.3.0\":[100,95],\"1.3.1\":[100,95],\"1.3.2\":[100,95],\"1.3.3\":[100,95],\"1.4.0-rc.1\":[100,95],\"1.4.0-rc.2\":[100,95],\"1.4.0\":[100,95],\"1.5.0-rc.1\":[100,95],\"1.5.0-rc.2\":[100,95],\"1.5.0-rc.3\":[100,95],\"1.5.0\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3-rc.1\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6\":[100,95],\"1.5.8\":[100,95],\"1.5.9\":[100,95]}}\";s:6:\"rating\";i:100;s:11:\"num_ratings\";i:100000;s:4:\"tags\";s:143:\"{\"backup\":\"Backup\",\"cloud backup\":\"Cloud backup\",\"database backup\":\"Database backup\",\"restore\":\"Restore\",\"wordpress backup\":\"Wordpress backup\"}\";s:7:\"banners\";s:125:\"{\"low\":\"//repo.boldgrid.com/assets/banner-backup-772x250.png\",\"high\":\"//repo.boldgrid.com/assets/banner-backup-1544x500.png\"}\";}}s:7:\"updated\";i:1689009407;}','no'),(1415628,'_site_transient_boldgrid_plugins_filtered','a:7:{s:39:\"boldgrid-easy-seo/boldgrid-easy-seo.php\";a:13:{s:4:\"Name\";s:17:\"BoldGrid Easy SEO\";s:9:\"PluginURI\";s:38:\"https://www.boldgrid.com/boldgrid-seo/\";s:7:\"Version\";s:6:\"1.6.10\";s:11:\"Description\";s:82:\"Easily manage your website\'s search engine optimization with Easy SEO by BoldGrid!\";s:6:\"Author\";s:31:\"BoldGrid The Post and Page Builder is an intuitive drag and drop editor plugin and the easiest way to create and edit pages for any theme. Whether you are new to WordPress or consider yourself a pro, BoldGrid solutions will make your WordPress life better. Stop dealing with site-breaking shortcodes and theme restricted editors. You are going to love just how fast and easily you can create beautiful websites now.<\\/p>\\n\\n Try out the BoldGrid Demo<\\/a> on Cloud WordPress to see for yourself!<\\/p>\\n\\n [youtube https:\\/\\/youtu.be\\/QoIb7OhV9ys?rel=0]<\\/p>\\n\\n Additional Features when used with other BoldGrid plugins:<\\/p>\\n\\n Visit our website to learn more about additional BoldGrid plugins<\\/a> to further improve your WordPress experience!<\\/p>\\n\\n \\\"It\'s really the perfect starting point for just about any web project, allowing users to get their site up and running in very short time. \\\" - Digital.com<\\/p>\\n\\n \\\"BoldGrid is a great extension to WordPress that will make my job a lot easier and faster while creating custom layouts and pages.\\\" - Webhostingmedia.net<\\/p>\\n\\n \\\"Well, I have seen many site builders but this is the only one that provides so many features.\\\" - Woblogger.com<\\/p>\\n\\n The Post and Page Builder by BoldGrid is designed to work with almost any WordPress theme. Add it to your existing website today, or try a BoldGrid theme for your new website. Alternatively, consider upgrading and using the powerful BoldGrid framework theme (available in Premium subscription) as an excellent time saver for agencies and developers.<\\/p>\\n\\n Create layouts and pages faster and easier than ever with Blocks by BoldGrid. Blocks are pre-built page sections consisting of various layouts of rows and columns prepopulated with content that can be edited visually or with HTML and CSS. Blocks utilize a wide variety of content that can be completely customized to fit your needs such as icons, buttons, free and premium images, font packs, and more.<\\/p>\\n\\n The Post and Page Builder by BoldGrid is designed to create pages that load fast. BoldGrid ditches shortcodes in favor of clean markup that can be served quickly. That also means BoldGrid code is easy to assess and customize.<\\/p>\\n\\n Great for making \\\"under construction\\\" or \\\"coming soon\\\" pages. You can create a simple page within minutes by using free professionally designed WordPress Blocks.<\\/p>\\n\\n Our drag and drop system is built on the Bootstrap Grid. You can drag columns, rows, and containers around your pages to make quick updates to pages. Advanced CSS controls allow you to make pixel perfect designs.<\\/p>\\n\\n Choose your brand\'s colors and we\'ll help your design stay unified. Our unique color palette system is built with SASS and allows you to change all the colors on your site. You don\'t have to choose from a few presets anymore!<\\/p>\\n\",\"installation\":\" You will find a \'Post and Page Builder\' menu in your WordPress admin panel and find most features within the\\nWordPress Editor.<\\/p>\\n\",\"changelog\":\" Release date: March 15, 2023<\\/p>\\n\\n Release date: March 14, 2023<\\/p>\\n\\n Release date: April 26, 2022<\\/p>\\n\\n Release date: December 8th, 2020<\\/p>\\n\\n Release date: November 11th, 2019<\\/p>\\n\\n Release date: October 30th, 2019<\\/p>\\n\\n Release date: December 5th, 2018<\\/p>\\n\\n Release Date: December 4th, 2018<\\/p>\\n\\n Release Date: October 16th, 2018<\\/p>\\n\\n BoldGrid Inspirations is an inspiration-driven plugin to assist with creating a fresh new website, or to customize an existing website. The first phase is Inspiration; the guided tool creates your base website. If you already have a website, then you can skip this step. The second phase is Customization; tools to transform your website into your vision. Upload the entire boldgrid-inspirations folder to the /wp-content/plugins/ directory. Activate the plugin through the Plugins menu in WordPress. You will find the Inspirations menu in your WordPress Dashboard / admin panel. Release date: March 23rd, 2023 Release date: September 20th, 2022 Release date: September 7th, 2022 Release date: August 8th, 2022 Release date: July 8th, 2022 Release date: July 7th, 2022 Release date: January 25th, 2022 Release date: October 18th, 2021 Release date: June 10th, 2021 Release date: April 14th, 2021 Release date: February 16th, 2021 Release date: January 25th, 2021 Release date: December 8th, 2020 Release date: October 23rd, 2020 Release date: October 17th, 2020 Release date: September 22nd, 2020 Release date: August 11th, 2020 Release date: June 15th, 2020 Release date: May 29th, 2020 Release date: May 18th, 2020 Release date: March 12th, 2020 Release date: December 17th, 2019 Release date: November 22st, 2019 Release date: October 15th, 2019 Release date: September 17th, 2019 Release date: September 5th, 2019 Release date: August 29th, 2019 Release date: August 16, 2019 Release date: August 1st, 2019 Release date: July 25th, 2019 Release date: July 2nd, 2019 Release date: May 21st, 2019 Release date: Apr 23nd, 2019 Release date: Apr 19th, 2019 Release date: Apr 16th, 2019 Release date: Jan 29th, 2019 Release date: Dec 5th, 2018 Release date: Dec 4th, 2018 Release date: Nov 26th, 2018 Release date: Nov 20th, 2018 Version 1.3 has been released with a redesigned Inspiration phase. For more information on this change and others, please visit our blog at https://www.boldgrid.com/boldgrid-1-3-released/ . Users should upgrade to version 1.0.2 to ensure proper BoldGrid theme updates. BoldGrid Gallery is a standalone plugin used for slideshows and galleries. Upload the entire boldgrid-gallery folder to the /wp-content/plugins/ directory. Activate the plugin through the Plugins menu in WordPress. If you have an existing WordPress focused podcast, consider introducing it to our audience at Do the Woo. >> The post Bring Your Podcast to Do the Woo appeared first on Do the Woo - a WooCommerce Builder Community . WordCamp Dhaka 2023 has been cancelled and the official announcement has been published on the event website. There were no tickets or sponsorship packages sold, therefore there are no tickets or sponsorships to be refunded. To ensure the success of future WordCamps, we encourage the Dhaka community to participate in collaboration and contribute to creating a more diverse, inclusive and open community. Any members of the community, regardless their gender, company affiliations, and background, can apply and collaborate as co-organizers. Here are the basics of our Meetup Program and the application to become a Meetup organizer. The Community Team believes that the Dhaka WordPress Community can build a stronger community with opportunities for everyone interested in WordPress. If you have any questions, you can reach out to us by sending an email to support@wordcamp.org. Thank you, WordPress Community Team WordPress 6.3 is scheduled to be released one month from today on August 8, 2023. The live product demo date and time has now been set for Thursday, July 20, at at 16:00 UTC. Participants can join live via this Zoom link. Automattic-sponsored Gutenberg contributors Anne McCarthy and Rich Tabor will be hosting the event, moderated by Nathan Wrigley. They will highlight upcoming changes and take questions from participants during a Q&A session at the end. WordPress 6.3 is set to introduce an exciting array of new features – the Command Palette, content editing and distraction-free mode in the Site Editor, pattern creation, and much more. There have also been significant changes to pattern management UI as late as Beta 3. The live product demo is a good opportunity to get up to speed with a guided tour of everything new that will be landing in 6.3. The event will be recorded and those who cannot attend live can catch it later when it is published on WordPress.tv. Howdy, Wow. This weekend edition holds a lot of date/times of upcoming online events for all WordPress users, developers, designers, site builders, and content creators. The most important might be the the WordPress 6.3 Product Demo on July 20th, (16:00 UTC) roughly 14 days before the final release, filled to the brink with new and enhanced features. Watching the Product Demo gets you up to speed quickly. Yes, there will be a recording, too. Don’t forget to consult the workshop schedule of the training team on the Learn WordPress site. Have a wonderful weekend! Mine will be dominated by unpacking boxes and eating delicious food and chatting with long-distance friends. Be well. Yours, 💕 Next Live Q & A: Design Systems and Theme.json on July 21, 2023 David Bowman and and Alec Geatches from WordPress VIP will show off how they keep design systems developed in Figma and themes in WordPress in synch and their workflows streamlined. Joni Halabi, senior developer from Georgetown University will join me as co-host. Joen Asmussen published for the WordPress design team the Design Share: Jun 19–Jun 30, recounting all the great UI and UX work the design team contributed during the past two weeks. Reminder: Anne McCarthy and Emily Clark will co-host a Hallway Hangout to discussion WordPress 6.3 performance improvements on July 27, 2023, at 15:00 UTC to discuss WordPress 6.3 performance improvements led by performance reps Emily Clark and Felix Arntz and also look ahead to WordPress 6.4. Anne McCarthy and Rich Tabor will present at the WordPress 6.3 Live Product Demo on July 20th, 2023 at 16:00 UTC (12 pm EDT / 18:00 CEST). “Join the WordPress community for a first look at 6.3 in action during a live product demonstration.” Attendees will learn about recent improvements to the Site Editor, Patterns, Command Palette, and Navigation. There will be a Q&A session, and you may submit questions in advance via the #walkthrough channel on WordPress Make Slack. Sarah Gooding reports on WordPress 6.3 Beta 3 Released, Introduces UI Changes to Pattern Management. “A last-minute PR has renamed Library to Patterns in the Site Editor and was cherry-picked to get it included in Beta 3.” she wrote, and then continues with the reasons. Only tangentially related to the Block editor, I still want you to have this overall change on your radar: In his post on the Make Blog, John Blackburn informed the WordPress community that the project is Dropping support for PHP 5 . “The minimum supported version was last adjusted in WordPress 5.2 in 2019, and since then, usage of PHP 5.6 has dropped to 3.9% of monitored WordPress installations as of July 2023,” Sarah Gooding also has the skinny for you in WordPress 6.3 to Drop Support for PHP 5 🎙️ New episode: Gutenberg Changelog #85 – Gutenberg 16.1, WordPress 6.3 with special guest, Tammie Lister and host Birgit Pauli-Haack Following his March 2023 Gutenberg Phase 3 post, Matias Ventura, architect on the Gutenberg project, published a series of posts to go deeper on all the aspects of the next phase and outline the requirements. There might be more posts coming and, of course, I’ll keep you in the loop. Sarah Gooding summarized it all in WordPress Unveils Plans for Real-Time Collaboration with Major Improvements to Revisions and the Media Library In his post, What Collaborative Features Will Bring to WordPress, Eric Karkovack explored a few scenarios that demonstrate how new collaborative features can streamline working together in a team responsible for publishing content on a larger site. “Keeping up with Gutenberg – Index 2022” Nick Diego announced a new season of his “Builder Basics” series. The next event is scheduled for July 17th 7pm UTC ( 3 pm EDT) Goodbye Reusable Blocks—Hello Synced Patterns (and more). He’ll review the updates coming in WordPress 6.3 for reusable blocks and explore the improved editing flows for patterns and template parts. In another event, Bud Kraus will demystify the Navigation Block for you on July 11 at 19:00 UTC / 3 pm EDT. You will learn how to set your site’s navigation using only blocks and not the classic menu system. Bijay Yadav, long-time contributor to the open-source WordPress project, published his first theme in the Theme directory. Geum is block themes allowing the user to take full advantage of the new site editor to customize their site. Jamie Marsland posted a tutorial on How to Choose the perfect WordPress Block Theme. He started out summarizing the advantages of a block theme over a classic theme, and listed all the considerations to take into account when comparing block themes from the repository or other theme directories. He also mentioned his favorites: Basti by Ana Segota, Ollie WP by Mike McAlister and Spectra One by the Astra team. Anne McCarthy published the Summary of feedback from the latest FSE Program Momery Makeover Summary. “Since this call for testing took place during the early stages of an iterative process, several aspects of the feedback provided have already been swiftly addressed, thanks to ongoing development for WordPress 6.3. The relatively limited amount of bugs received and feedback aligning with feature development reflects a level of solidness in the direction of recent improvements.” she wrote. On WPTavern, Sarah Gooding reviewed the latest block theme for blogging – Hey, built by Automattic in here article Hey: An Elegantly Simple WordPress Block Theme for Blogging. In his article for the Torque Magazine, How to Modify WordPress Block Themes (JSON Beginner’s Guide), Nick Schäferhoff explored ways on how you can customize a block theme’s theme.json file for those of us, who are used to tinker around via functions.php and style.css. Jonathan Bossenger published his series for live streams on Developing Sendig a Block theme on YouTube. The goal is to create a theme following the designs by Emily Rapport. (See Weekend Edition 253 for details). You can take Wes Theron‘s tutorial on Designing with row and stack blocks on Learn WordPress. “Using the Group block is one of the cornerstones of mastering the block editor. When you select a Group block, you have the variations of the Group block, the standard group, rows, and stacks. In this video tutorial, you learn how you can use rows and stacks to achieve various designs. Ronald Huereca published a tutorial on Adding Commands to the WordPress Command Palette can be accomplished, ahead of the official WordPress 6.3 Dev Notes. He explained what the Command Palette is, what it can be used for, and step-by-step how you can add your custom commands to it via a plugin. A new post on the WordPress Developer Blog covers how to modify theme.json data using server-side filters. Discover, with Nick Diego as your guide, the possibilities of theme.json server-side filters. Learn how to modify color palettes dynamically or restrict block controls based on user permissions. The recording of this week’s Live Q & A is now available on YouTube: Leveraging Gutenberg’s architecture to take plugin development to new levels. Learn how Gutenberg components and scripts can be used outside the block editor to revamp a plugin’s code base in this Case Study of GiveWP 3.0 with Jason Adams, Director of Development, Jon Waldstein, Lead Developer of GiveWP and co-host Lena Morita, JavaScript Developer on the Components team. The list of resources is available in the description of the video. Ryan Welcher announced the topics for the next Twitch streams: Recordings of previous streams can be viewed on his YouTube Channel. Need a plugin .zip from Gutenberg’s master branch? Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph. For questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com Featured Image: Victoria Pickering “Old Type”, found on Openverse.org Don’t want to miss the next Weekend Edition? In a series of four posts, Gutenberg lead architect Matías Ventura has outlined the project’s phase 3 plans for Real-Time Collaboration, Workflows, Revisions, and the Media Library. WordPress 6.3 is set to be the final major release of Phase 2, which focused on Customization. Phase 3 will shift focus from the editors and move into other parts of the admin in an effort to bring seamless collaboration to WordPress. “The primary aim of real-time collaboration is to build functionality into the block editors so that concurrent collaboration, shared edits, and online presence of peers are possible,” Ventura said. “Supporting these workflows is not just about concurrency, though, but also about lifting restrictions that have been present in WordPress for a long time, such as locking a post when two people try to edit at the same time.” The technical challenges here are in making this available to all WordPress users, even those on the most economical hosting environments. Ventura shared a quick preview of what that might look like, along with the scope of the tasks that would be part of this effort. In the Workflows document, Ventura details collaborative features that will be part of this phase, including allowing users to add comments, suggest edits, and tag other users for peer review. These enhancements would apply to both content creation and design changes on block themes. There are some interesting projects listed within the scope of this section, including a publishing checklist, sharing draft links with permission controls, and exploring hook points for version control systems to take over internal revision systems if desired. Users can expect that Revisions will also be getting some major improvements as part of the Collaboration phase of the project. “As part of improving the overall experience, we should also go beyond document level history and explore how the interface could let users browse through single block changes and offer the ability to restore them individually rather than requiring full post restores,” Ventura said. “For global styles, we should evolve the revisions panel to allow comparing two revisions side by side. For synced patterns, we could allow browsing edit history with side by side and overlay comparison tools.” Long-awaited improvements to WordPress’ Media Library are also considered part of this phase. “The main goals are to expand the media management capabilities, unify the block edit and single media interfaces, and improve upon the major media flows,” Ventura said. He highlighted a few major areas that may get some enhancements, such as categorization and tagging, better handling of attached media, and design improvements to the library view. Other Media Library projects may include a revamp of the image editing interface, which remains somewhat unintuitive at this time. Ventura proposes these tools, such as cropping and thumbnail browsing, be updated to align more with the current block editor tools. Contributors may also be exploring contribution to the commons from WordPress, along with improvements to attribution. “As we look into expanding the presence and touch points of Openverse, it’d be interesting to see how contributions to the commons could work directly from a user’s WordPress install,” Ventura said. “Another area to look at is improving handling and presentation of other media types (audio, video, files) and their connection with blocks and the block APIs. We should resurface work on a native Playlist block, ideally powered by the Interactivity API.” Reactions to the outlined vision and scope for the Collaboration phase have so far been positive, as users and contributors are eager to see a strong focus come to some of the other parts of WordPress that have not had much attention for years. The newer real-time collaboration features that will take WordPress beyond the days of locking posts while another person is editing, have the potential to speed up content creation and editing for groups working on the same website. “Very much looking forward to this phase. I think it will really enable larger teams to work on posts much easier,” WordPress developer Rich Holman commented. “I’ve mentioned this before but the ability to continue working on a published draft without the front-end updating seems important especially with more editors working on something, especially if doing more experimental edits.” For more details on the features being considered for this phase, check out the Phase 3 overview post, along with Ventura’s more recent write-ups on how contributors will improve and expand WordPress’ collaboration architecture with updates to Real-Time Collaboration, Workflows, Revisions, and the Media Library. On Saturday, September 30, 2023, Rochester will again (for the sixth time) host the region’s WordCamp for bloggers and web designers of all skill levels. Registration opens at 8:00am. Sessions begin at 9 a.m. and continue to 5 p.m. This year’s WordCamp will be held at the Rochester School of the Arts, 45 Prince Street, Rochester, NY 146017. Tickets are required in advance. The $25 ticket cost covers WordCamp Rochester swag, morning coffee, lunch, and the evenings’s after-party food. Participants are strongly encouraged to bring their laptop or tablet computers. Ticket purchase and program details are available at www.rochester.wordcamp.org/2023. The capacity for this event is about 120 people, so getting tickets early is advised. WordCamps are held worldwide, locally run and purposely provided at a low cost for accessibility to all. WordCamp Rochester is dedicated to WordPress, blogging and web facility. WordCamps are sponsored by WordPress, the open-source, free platform for individuals, groups and businesses to build their own blogs and websites. WordPress.org began in 2003. Its administrators call it the “largest self-hosted blogging tool in the world, used on millions of sites and seen by tens of millions of people every day.” Similar to previous years, Rochester’s 2023 WordCamp will divide its workshops along two tracks, with sessions for every ability and level of use. Speakers will include WordPress users from Rochester, Buffalo, and beyond, with experience ranging from user/blogger to advanced developer. Want to learn more about WordPress 6.3, planned for release on August 8, 2023? Join the WordPress community for a first look at 6.3 in action during a live product demonstration. 6.3 release squad members, Anne McCarthy and Rich Tabor, will team up with moderator, Nathan Wrigley, to guide attendees through the anticipated highlights of the upcoming release. This event will follow a similar format to the live demo for 6.2. Attendees will see recent improvements to the Site Editor, Patterns, Command Palette, and more. Following the demo, there will be a Q&A session, and you may submit questions in advance via Slack. Thursday, July 20, 2023 at 16:00 UTC The event will be recorded, archived for on-demand viewing on WordPress.tv, and shared in a recap post shortly afterward. To learn more about WordPress 6.3, please visit the following resources: Props to our panelists and moderator, and to @jpantani, @meher, @eidolonnight, and @dansoschin for helping prepare this announcement and supporting event logistics. WordCamp San José 2023 will take place on November 4-5, 2023 at Fidélitas University. That means we are currently looking for speakers who want to take the stage and share their knowledge, and sponsors who can help make this event unforgettable. Costa Rica is known as a country that stands out for its natural beauty, commitment to environmental sustainability, and quality of life, so we are looking for a great and diverse group of speakers to reflect our local community. Both new and experienced WordCamp speakers are welcome. If you would like to propose multiple topics, please submit the form multiple times, once for each topic. Apply at https://sanjose.wordcamp.org/2023/llamado-a-ponentes/ If you have just started a business, or moving an existing one into this unique open source community, there is a lot to learn. >> The post Navigating the WooCommerce and WordPress Community appeared first on Do the Woo - a WooCommerce Builder Community . Hey is a block theme designed by Automattic for users on WordPress.com and also released for free in the WordPress.org Themes Directory. It’s the kind of simple theme that enables you to quickly get started writing online, without having to configure a bunch of design elements. The homepage features a profile image (Site Logo), site title, and recent posts with dates. Single posts display with the feature image at the top of the post, although this template can easily be edited if this is an undesirable feature. Previous and Next post navigation appears under the post. Users can add menu items to display at the top, but clicking the site logo brings the visitor back home in the absence of a navigation menu. The Hey theme comes in two different styles – the default and a serif variation. Colors can be adjusted to create a more vibrant palette for the site design. One major drawback to this theme, which may not be immediately evident by looking at the demo, is that if users want to display more than the three most recent posts, they will need to add the pagination block inside the query loop block. It will also need to be styled to match the theme better. The query loop can be edited to show more posts on the homepage. Although Hey is a simple personal blog theme, it also comes packaged with templates for WooCommerce compatibility. This is likely for the benefit of WordPress.com users who may want to quickly fire up a store. Self-hosted users who want to sell products with WooCommerce will be able to easily display things like the mini-cart, customer account block, product archive, product search results, and more. Overall, Hey is an elegantly simple block theme with a clean design and plentiful white space. It’s suitable for the person who wants an almost blank slate to get started, or just a theme that enables writing without any distraction for the reader. Check out the live demo on WordPress.com and download Hey from WordPress.org. In this Woo DevChat we talk with Mathias from Oliver POS about his journey in building a point of sales for WooCommerce. >> The post Building a WooCommerce Point of Sales with Mathias Nielsen appeared first on Do the Woo - a WooCommerce Builder Community . WordPress is officially dropping support for PHP 5 in the upcoming 6.3 release, which is expected on August 8. WordPress’ minimum supported version has sat at PHP 5.6.20 since 2019, but will be updated to 7.0.0 in the next release. The recommended PHP version will stay the same at 7.4+. “The minimum supported version was last adjusted in WordPress 5.2 in 2019, and since then usage of PHP 5.6 has dropped to 3.9% of monitored WordPress installations as of July 2023,” WordPress core developer John Blackbourn said. “There’s no concrete usage percentage that a PHP version must fall below before support in WordPress is dropped, but historically the project maintainers have used 5% as the baseline. Now that usage of PHP 5.6 is well below that at 3.9% and dropping by around 0.1% every few weeks, plans to increase the minimum supported PHP version can move forward.” Blackbourn also emphasized that WordPress’ support for PHP 8.0, 8.1, and 8.2 is “very good” and contributors may soon act on a proposal for the criteria that would enable them to remove the “beta” support label on new PHP versions. Nearly 26% of WordPress users are already running sites on PHP 8.0+. Prior to this minimum required version boost, some hosts had even taken matters into their own hands in urging users to get on newer versions of PHP. Dreamhost charges additional fees for sites that require extended support for PHP 7.4 and older. IONOS and Strato have similar policies. The decision to bump the minimum supported version is happening after a lengthy seven-month long discussion, which surprisingly drew a little resistance. Although sites that remain on PHP 5.6 cannot upgrade beyond WordPress 6.2, they will still receive security updates, as the project currently backports them to versions 4.1+. The bump to 7.0.0 for the minimum supported version will have many benefits for the WordPress ecosystem of themes and plugins, will significantly reduce memory usage for upgraded websites, and provide better security and improvements to core tooling. “There are no plans to bump the minimum supported PHP version on a schedule,” Blackbourn said. “The core team will continue to monitor usage of PHP versions and work with the hosting team to encourage users and hosting companies to upgrade their versions of PHP as swiftly as possible. The 5% usage baseline will continue to be used for the foreseeable future.” WordPress contributors are onto another round of testing, as 6.3 Beta 3 was released this week. RC 1 is expected on July 18, and a live product demo is anticipated to be broadcast on Thursday, July 20, 2023 at 16:00 UTC. These demos have become a more regular part of the release process and allow viewers to familiarize themselves with important new features and updates coming in the release. Beta 3 includes approximately 34 updates to the Site Editor since the previous beta release, and more than 40 updates coming from Trac. A last-minute PR has renamed Library to Patterns in the Site Editor and was cherry-picked to get it included in Beta 3. Automattic-sponsored Gutenberg contributor Aaron Robertshaw cited three reasons for the renaming: This video from the PR gives a quick overview of the changes testers should see in the Patterns UI as of Beta 3: Beta 3 introduces a new lock icon to designate theme patterns as unable to be edited or modified. It also adds a sync status details section within the pattern sidebar navigation screen. There are a significant number of new things being introduced after Beta 1, which seems usual. Major features like the pattern creation and the Patterns section made their debut in Gutenberg 16.1 but had very little testing before being rolled into the upcoming WordPress 6.3 release. This is likely why UI changes are being introduced after Beta 1 has already shipped. Check out the Beta 3 release post for more information on how to test. A Beta 4 is anticipated the week of July 11, followed by RC 1 on July 18. The general release is scheduled for August 8, 2023. [00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcastwhich is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, how and why you need to be thinking sustainably when building websites. If you’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. If you have a topic that you’d like us to feature on the podcast, I’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. So on the podcast today, we have Louise Towler. She joined me at the recent WordCamp Europe in Athens to talk about websites and making them more sustainable. Louise is the founder of Indigo Tree, a UK based agency with deep expertise in WordPress websites. She gave a presentation at WordCamp Europe entitled, Digital sustainability: The benefits for business and the environment, in which she emphasized the impact websites can have on our planet. Her aim was to deliver practical tips for users and developers to help them make informed decisions. This presentation is the focus of today’s podcast, and we cover quite a lot of ground. Louise highlights the significant role which electricity plays in powering data centers and transmitting data to end devices. Even if data centers use renewable energy, there is still a need to address overall electricity consumption. She points out that the internet is the fourth largest polluter globally, surpassing the airline industry. We discussed how the continuous and widespread use of the internet has made it difficult to reduce its own impact, while still emphasizing the importance of the steps that we can take to make the internet more energy efficient. She suggests ways that we can all make a difference right away. Educating clients about the consequences of certain design choices, such as using large videos or auto-play features that require substantial data to load. Optimizing videos, images, and other website elements, which makes it possible to reduce data consumption and improve performance. The conversation then explores other suggestions, such as using modern image formats, using images as placeholders for videos, self hosted fonts, and considering the carbon footprint of email communications. Louise acknowledges the challenges of discussing environmental concerns with clients, whilst also explaining that we have to come up with ways to make clients understand that these decisions are beneficial to them as well. After all, an optimized website is one that is looked upon favorably by search engines. Whilst clients ultimately are the decision makers, informing them about the consequences of their choices can help them be more informed. Moving onto WordPress, we talk about the responsibility theme authors play. It’s a crucial role, helping users make sustainable choices. Her agency builds custom themes for clients which allows them to have full control over design decisions. We get into the subject of how legislation is certainly coming, and so getting in early and understanding the implications of such legislation will help your endeavors in the future. Towards the end of the podcast, we chat about some of the tools which you can use to assess the impact that your websites have, including a tool which Louise and her team have been working on for the last few years. If you’re interested in how your sites can become more sustainable, this podcast is for you. If you want to find out more, you can find all of the links in the show notes by heading to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well. And so without further delay, I bring you Louise Towler. I am joined on the podcast today by Louise Towler. Hi Louise. [00:04:54] Louise Towler: Thank you for inviting me. Hello. [00:04:56] Nathan Wrigley: We’re going to talk today about, well possibly the most important topic ever, which is the environment and your website compared to the environment. Prior to that Louise, will you just tell us a little bit about you, so that we have some context. Who are you? What’s your relationship with WordPress and so on? [00:05:13] Louise Towler: Okay. I am the founder of Indigo Tree. We’re a small but beautiful WordPress agency based about 30 minutes on the train north of London in the UK. There’s 15 of us in total at the moment. We have an engineering team, a project management team, and a support team, and we build WordPress websites. I started building websites, well my first webpage that I built was built Christmas Day, the year 2000, because my husband was daft enough to buy me a book on html. So he cooked the turkey and I built myself a little webpage. I started freelancing about 20 years ago, and then one of my freelancing clients said to me, we’ve heard there’s this thing called WordPress. Would you mind building our website in WordPress? And I was like, okay, I’ll give it a go. And went off and Googled and found out how to do it, and the rest is history. [00:06:09] Nathan Wrigley: Nice. You did a talk today entitled The Benefits for Business and the Environment. Just give us a bit of a background about your thoughts on the environment. What I mean by that, is this something that you are concerned about in your normal life? Does the environment figure heavily in your daily life? [00:06:27] Louise Towler: It does. It’s really difficult to tread lightly on the planet. It’s very hard to do things in a sustainable way, but I think I’m very conscious of it. So I buy a few clothes, but I wear them a lot rather than throw them away, and the fast fashion thing. I use recycled paper. I try to do things in a good way. Turn off lights. Think about my travel. But it is genuinely hard. But then I have children and they’re going to live a lot longer than me, and global warming is going to affect them a lot more than it’s going to affect me. But 2050 is not that far away. And we are in trouble, as we can see by the mad world weather that’s happening at the moment. [00:07:16] Nathan Wrigley: You work in the website building industry, as do I. Which feels in my daily interaction with my computer, it feels like the cleanest thing ever. I have a shiny laptop. I have a shiny phone. None of them put smoke out of the back when I switched them on. You know, if I worked in the automotive industry, it would be obvious what my footprint was. But I switch on my computer, there’s no connection between that and the environment. And yet it’s pretty bad. [00:07:49] Louise Towler: Yeah. [00:07:50] Nathan Wrigley: We browse the internet. We’re probably asking Google and all the other rivals, trivial things all the time. So make the connection for us. What is the environmental impact? What are the things which are happening between me switching on my computer and browsing WordPress websites? What are the things that are going on? What’s the technology, the bits and pieces that we need to be thinking about? [00:08:13] Louise Towler: Well, if the internet was a country, it would be the fourth largest polluter. Compared to airlines, you know, that are 1.6%, it’s massive. It is just massive. And it’s fundamentally about electricity. Because it’s electricity that powers the data centers, whether or not they’re running on renewable energy, the fact is they still need electricity. You’ve got the transmission, the wires between the data centers and the end devices, and then you’ve got the power to power your device. If you’re on a phone, you are recharging it. If you’re on a laptop, you are plugging it in, and that’s all using electricity. And not all of that electricity is renewable and the electricity that comes through the wires, you don’t have any control about what proportion of that is renewable. On a hot, windy day in the UK, a vast proportion of that electricity is from renewable energy, from solar and wind turbines. But on a dark, gloomy day with no wind, a massive proportion of that is fossil fuel powered electricity. [00:09:27] Nathan Wrigley: It feels like we’re completely addicted to the internet. I use the car that I have, a bit. But I use the internet more or less continually. You know, I’ve got my phone, it’s constantly charged up. The merest thought in my head can easily lead me to whip out the phone, do some banal scrolling of Facebook or whatever it may be. And that feels like that’s crept up on us. We’re all using it all the time. You said what was it, 4%? [00:09:57] Louise Towler: It’s the fourth largest polluter. [00:09:59] Nathan Wrigley: Fourth largest polluter. Can you compare that to another industry? You mentioned airlines. Does the internet as a whole, so every website, all the online services that we can use and so on, does that pollute more than the airline industry? Because the airline industry is the poster child of pollution, isn’t it? [00:10:15] Louise Towler: I believe it does. I mean, the problem is finding out, and even measuring it is really hard. So all the estimates are that it is just massive, and it’s getting worse. With AI, the stat that I’ve read is that to do a search in ChatGPT takes four times as much energy as to do a search in Google. And to build that AI model takes a massive amount of processing power to suck in all the data and build out that model that then does predict the next word that’s going to come out in the chat box. And so it’s not getting better. When you are talking about carbon footprints and getting to net zero, you’ve not just got to change the energy mix so that you’re running off renewable energy. You need to actually reduce demand. In the UK there’s a carbon reduction in task force. Their target is by 2030, they will have reduced demand by 15% for electricity in comparison to 2021. You have to reduce the demand as well. [00:11:25] Nathan Wrigley: Right. [00:11:26] Louise Towler: And the connection to IT and websites is that if you transmit less data, you are, there’s not a direct correlation always, but you are essentially using less electricity to transmit that data. [00:11:37] Nathan Wrigley: So the easiest way to mitigate your use of the internet is just to stop using it. But that’s completely unrealistic now? [00:11:44] Louise Towler: Well, a company with zero carbon footprint is probably a company that’s not in business. You can’t not use the internet. What you have to do, we have to try and make sure the internet uses less electricity to do what it does. [00:11:59] Nathan Wrigley: Okay, so given that we’re not going to be switching our computers off, we’re not going back to the internet stone age, if you like. We’ve got to figure out ways to reduce the amount of carbon that we put out. So we’ve got to become responsible citizens because we’re using the internet. But also, we’re in a slightly unique position, you, I, and the people listening to this podcast, because we’re sitting behind the websites that are causing the pollution. And that’s, I guess, where the rest of this conversation is going to go. What are the things that we can do to make our websites for our clients, for ourselves, pollute a little bit less? [00:12:38] Louise Towler: Think about the data and educate your client. So in the first instance, if your client wants that amazing stock video on the banner of their homepage, that auto plays in the background and looks absolutely fab. But actually the amount of data that you are then having to load on the homepage to deliver that video is massive. Well explain to them the consequences of that decision. It’ll probably mean the homepage is a little bit slower, which won’t be as good for Core Web Vitals and for search. So whether or not they care about the planet, they should be caring about the performance of their website. And the fact is it will use more data and that’s not good for people or the planet. If I’m on a fixed price data plan, because I’m on a low income and my children’s school has a massive video on the homepage of their school website with lots of happy kids running around the playground. And every time I visit that website, I’m using up my scarce resources of data, auto playing that video, that’s not very respectful to me when I’m trying to go about my daily life. So there’s lots of levels you can talk to your clients about why it’s good to do things. So it’s things like optimizing videos, optimizing images. If you’re familiar with Core Web Vitals and trying to speed up websites, these are nothing new. But you know, design your website with two fonts rather than five. Think about when you embed videos on the page. The block editor, it’s really easy to embed a video from YouTube or Vimeo, but use a plugin and put a facade in front of it so that when you actually load the page it loads an image. If it’s below the fold, you can lazy load the image. If people don’t scroll down, the image doesn’t load, and it’s only when they click on that image that the video plays and actually downloads that extra data. So you are being really respectful to your visitors as well as to the planet by consciously thinking about these things. And it doesn’t cost anymore if you plan it in from the beginning. Talking to your clients and planning it, most clients are really happy to have that conversation because in the end, performance and speed should increase conversions and profit. [00:14:56] Nathan Wrigley: Actually, that’s a really good point. You mentioned, just as we were beginning, that you run an agency. [00:15:00] Louise Towler: Yeah. [00:15:01] Nathan Wrigley: Do you have this conversation with your clients? [00:15:03] Louise Towler: I talk about performance and speed. [00:15:08] Nathan Wrigley: Yeah, so how does that go down? [00:15:09] Louise Towler: Fine. [00:15:10] Nathan Wrigley: Have you ever had somebody push back and say, no, we need the video? Or is it generally a conversation of look, okay you could have the video, but here’s the reason why I think for the planet, you shouldn’t have the video. How does that conversation normally go? [00:15:19] Louise Towler: We advise them. It’s like with banners, with sliders, we advise them. I emailed something to a client last week saying, here’s the Google stats. About 8% will see banner number two. Do you really think banner number three, as one of your key important messages being viewed by 4% of your home paved visitors, you’re better off putting that content on the page. It is the client’s choice in the end, but I will educate them so they’re conscious of the choice that they’re making. Rather than not aware and then complain that nobody clicks through from banner number three. And I’m like, well, we did tell you. But there’s some things I don’t give clients a choice on, like accessibility. They don’t get a choice about having an accessible website because you don’t want to give people a choice where you don’t want them to make a poor decision. [00:16:04] Nathan Wrigley: And in terms of your agency, do you advertise your environmental credentials? [00:16:09] Louise Towler: We don’t really talk about it at the moment, but we will be dipping our toe in the water and talking more and more about it over the next few months, because we’ve been doing some interesting stuff in the background. [00:16:20] Nathan Wrigley: You mentioned that an autoplay video, that seems like the most extreme example. You know, you go to a website, suddenly you’ve downloaded without your realizing it, I don’t know, 10 megabytes of data that you really didn’t need. Just run through the components of a typical webpage. So what have we got? We’ve got text, we’ve got images, we’ve got video, we’ve got, audio like this. What are quick wins? What’s the order, if you like, that you should go through when in your head you’re trying to make a page more environmentally friendly? [00:16:49] Louise Towler: I would start with images because a website typically has more images than videos. And if you’re doing something with images like you are, I don’t know, using a CDN, or you’ve installed the performance plugin and you are delivering things as WebP, then one plugin and one solution might work across all images on your website. So I would definitely think about images in terms of making sure you deliver the right sized image for the device as well. So make sure that in your theme, you’ve got that function which saves it all out at the various different break points. [00:17:22] Nathan Wrigley: If you’re on a, mobile website, the image that’s loaded should be the same size as the device that you’re looking at. Not a great big image that’s been squished down, okay. [00:17:30] Louise Towler: Exactly. And that can be a bit tricky because sometimes on mobile sites for example, we’ll have a nice banner image, but we’ll make it cropped and square. Whereas on a desktop site you might have it that letter box shape. And actually it won’t really work on a mobile. It’s too sort of narrow and thin. So you sometimes need to be a bit careful about, especially with the block editor, do you need to have different versions of images unless the cropping is right in the middle. Doesn’t work very well with the block editor to just auto crop. It’s about thinking about it. So I definitely start with images. Little things like making sure you are using SVGs where it’s appropriate. If you’ve got an animated gif, turn it into a video. I then look at the videos. Just make sure you’ve got facades or posters on videos and try and persuade your client not to have that large banner video. I would then look at fonts and make sure all your fonts are self-hosted. Which is a good thing anyway because certainly from a GDPR perspective, if you are using Google fonts in Europe, then there’s been some case law around, it’s leaking data to Google about who’s using those fonts and you don’t want to be doing that. But that again will speed it up because you can cache the fonts and things like that. And subset the fonts. So I think you can do things where if you are only, if you’ve got a font set that’s in multiple languages, but actually your website’s just in English, only use the bit of the font that you need for the language that you are working in. And then I would definitely think about things, other things on the website, like email. If you’ve got a transactional site and you are sending out lots of confirmation of shipping emails. Do you need a really big logo in the email? Can it be a tiny logo or even just text on a colored background and make those emails have a lower carbon footprint as well. [00:19:18] Nathan Wrigley: How does WordPress out of the box do with helping you get to some of these targets? [00:19:26] Louise Towler: It’s not helpful. [00:19:28] Nathan Wrigley: So I was going to say, I imagine that most people listening to this podcast have an understanding of everything that you just said, but the typical user of WordPress is not somebody that’s listening this podcast. Used by millions of people who probably see the media library throwing the biggest image they’ve got, and that’s it. [00:19:43] Louise Towler: I think you’ve got to be a responsible theme author. As an agency, we build our own custom themes for each client. So we’re not constrained in any way at the design stage. But if you’re choosing either a free theme or a paid for theme, you can be quite wise about it. So if you are you’re building a brochure site for a client, you don’t need to choose a theme with every possible e-commerce, form plugin, event plugin, all that extra code. If you’re not using font awesome icons, then don’t let the theme pull in the complete font awesome icon set. Just download a little SVG. So try and think about the theme that you choose. It can be a bit of a pain to actually turn off on some of those very flexible all singing, all dancing dancing themes, the options when you just want something really simple. There are some plugins that can help. So for example, we often use a plugin called Perf Matters, which is really good for performance. And one of the things I particularly like about that plugin is, so if we are working with a client where they might have an inquiry form or a landing page with an inquiry form on it. You install a plugin, we use Gravity Forms. Really brilliant plugin. Love it. But of course you get that plugin code in the head of every page, just in case the form’s required. Well turn it off. You can use Perf Matters and go in, and go I only want the Gravity Form code to be embedded on these three pages, on the site that have forms on. Doesn’t need to be downloaded for any other pages. The same with something like Google Maps, the API for Google Maps. Often you’ll put it in so that you can have a nice map on your contact page. Well actually, number one, could you replace that map with an image, and then just link out to Google Maps? How many people are actually going to be scrolling in and out on the page? Think about it from the user’s perspective, but then actually just have that Google Maps API code in the contact page. Don’t have it anywhere else on your website. It’s just not needed. But you see it a lot where all the plugins inject all their stuff into the head on every single page just in case. So go through and turn things off. [00:22:02] Nathan Wrigley: You mentioned earlier that obviously this is something you’re trying to embed in your company. You also mentioned that you don’t have the conversation about accessibility. It’s just the way it is. [00:22:10] Louise Towler: Well, we talk about it. The only time we really push back is where clients have got brand colors, which aren’t AA accessible, and then we discuss with them whether we can change them. [00:22:21] Nathan Wrigley: But are you going to in the future be having more conversations like this? [00:22:26] Louise Towler: Yes. [00:22:27] Nathan Wrigley:And if so, how forceful are you going to be with your clients if they push back? Say, no, no, no, no. There’s a delicate line here, isn’t there? You want to do the best for your client and the best for your client may be a bitter pill for them to swallow. [00:22:39] Louise Towler: There may be a really good a brand reason, depending on the client, as to why they have to use a particular font. But I would be going to the client and saying, I’m going to tell you why it’s not a good idea. In the end, it is your choice. It is your website. You own the site once you’ve paid me for us to build it. So it is yours to do what you want with. But do it consciously, knowing the consequences of the decision that you are making. So I will always tell them, in the end it is their choice. But with things like brand and fonts and that, well you know, the consequences of pulling in an Adobe font is 6 to 800 milliseconds of a page load. That can be the difference between a first and second spot on google. So sometimes you can argue it really strongly from a commercial reason, and they will listen and go, right, let’s go back to our brand designer and get them to find some web fonts or some Google fonts that we can use. And elsewhere, yes, you’ll use that fancy type kit or whatever font, but let’s use something for the web that actually will work and not impact on the performance of the site. Because if they’re a commercial client, they’re going to care about the performance. We need to make them look good to their boss. [00:23:59] Nathan Wrigley: Given exactly what you just said, is there some accreditation that websites can expose to the world to say, we made an effort here? I’m trying to think of an example, but there are badges that you can get in all manner of industries to say, okay, we went through this training. We made the effort here, and so we have a badge to prove that we made an effort. Is there something that people can do on the internet to say, look, our website is consuming 50%, 30%, whatever, less energy than it might have done. We made an effort. Here’s our badge to prove it. [00:24:32] Louise Towler: I’m not aware of a badge, but there are lots of people doing lots of things out there. So there might be. I think it’s really hard because what might be a good score for a e-commerce site, might be of a poor score for a different type of site. And I think that in the end, yes, you can measure against other people, but actually you have to have that intrinsic motivation for just wanting to do it. It’s not about collecting badges. Does it matter if your site is AA accessible and you have a badge on your site? Or does it matter that you basically have enabled 40% of the population with disabilities or temporary impairments to actually access your goods and services, and you’ll increase your profits as a result? [00:25:15] Nathan Wrigley: So that was the website piece. You know, can you expose this credential to visitors? What about you as an agency? Can you expose your credentials to your clients? Is there anything there? [00:25:26] Louise Towler: Well, we’re working, and it is a very much a work in progress, towards something called B Corp, which is an accreditation thing that you can get for being, if you like, a good citizen to the planet. It covers environmental. It also covers governance, and more things to help with inclusivity and diversity. And we are rewriting our staff handbook, and we’re measuring our carbon footprint as part of that, as an agency. But we’re also doing other things as well. Making sure that we do things in a way that’s consciously responsible, and there’s got to be a business for good. We want to be a good citizen for the planet. And I think that’s quite a high standard. And there’s, I think about a thousand companies in the UK who have that. And we are not there yet, but it’s something that I think we can aspire to be. [00:26:12] Nathan Wrigley: Do you have any sense that this message that you are preaching here is beginning to catch on? You are definitely in the vanguard. Most people are not talking about this. If we go downstairs, we’re not really picking up on that message yet. But do you sense some kind of change? Are you communicating with people on a more regular basis about this? Clearly you are interested in it, but are you talking into the void or are people beginning to listen? [00:26:37] Louise Towler: There’s a lot of people in communities where the communities are talking about this a lot. I think what’s really nice is I was given the opportunity to speak at a conference, and this conference, to the entire WebPress community had a session about digital sustainability. I personally think that every conference that anyone puts on should have at least one speaker, or channel, or workshop, or something talking about sustainability in the industry, or sector that the conference is in. Because it is looming. The legislation is coming. The governments are legislating now, and at the moment in the UK it’s only very, very large businesses who have to do reporting. But if you are a large business wanting a government contract with a value of more than 5 million pounds, which you know, even small consultants and agencies can go for big contracts. You have to have your scope one, scope two, and some scope three emissions and a carbon reduction plan will be coming. By 2028 The National Health Service in the UK will require every product or service that is supplied to it to have a carbon footprint. So you need to be starting now because for some things that’s going to be really hard to do and it’s going to take a while to do. So start now with the little things, the quick wins. Start measuring where you are, because your carbon reduction plan has to say how you’re going to reduce. And then you have to show that you are making those reductions. So start measuring now, so that all the things you start doing now can be part of that reduction that you make and you can report on. [00:28:18] Nathan Wrigley: So you are describing things in the UK. In the UK in the future, you are literally going to be unable to get certain types of website client work if you cannot prove that you’ve done the due diligence. [00:28:31] Louise Towler: Yeah. [00:28:31] Nathan Wrigley: Okay, that’s really interesting. But still a way off. We’re still five years out from that portcullis closing? [00:28:37] Louise Towler: Yeah. But if you are a large business, very large business, you already have to do mandatory reporting. The government is slowly going to bring that down. It wouldn’t surprise me in the slightest if by 2030, as well as putting in my annual tax return, on my submission of my company accounts to Companies House, I have to do a carbon accounting report. Every small business. The EU, 23 million organizations there are in the EU at the moment, by 2028, all of them are going to be expected to put in some sort of carbon report on what they’re doing. The legislation is coming. But even quicker than that, procurement is starting to change. So I think it was the back end of 2021, Tesco sent out a letter to all of their suppliers saying, we want you to do these four things. You need to have a carbon reduction plan. You need to move to green energy. Otherwise you can’t be part of a supplier to Tesco. Doesn’t matter whether or not you are a large business or a small business, they sent it out as part of their procurement. So the government legislation is coming, but larger businesses are doing it quicker because they’re using procurement as a tool to do that. And then on top of that, for some organizations now it’s affecting their access to finance. So if I’m a pension fund or I want to invest in a large enterprise or a business, why would I invest in you, if you are not sustainable in 5, 10, 15 years time? They are now beginning to ask for those carbon reduction plans, sustainability report. What are you doing for your ESG as a condition of investment? [00:30:22] Nathan Wrigley: So the window of opportunity for ignoring this is fast closing? [00:30:25] Louise Towler: And why not get ahead of it? Why not be that agency that can help your clients with these challenges? [00:30:32] Nathan Wrigley: Although you described that there’s no badge necessarily for this. It really does feel that for the right client this is a conversation which will win you work. If you can prove that you are going to do this work now, like you said, who’s going to say no to a more green website? Would you like your website to be much more environmentally friendly than it could have been? Well, no, actually we’d like it to pollute more, please. That’s just not a conversation you’re going to get into. [00:30:56] Louise Towler: Exactly. Exactly. [00:30:58] Nathan Wrigley: That’s interesting. So the only piece that I can see in this conference where anything is mentioned about the environment is hosting. And even that, it’s probably I don’t know, one in fifty, one in a hundred who have that badge. Talk to us about that side. So obviously we build websites, we’ve got a computer, we know that it’s stored somewhere, but tell us about hosting, and what people are doing. [00:31:22] Louise Towler: Actually some of the hosting companies here are very green, but you have to consider the political climate. So if you are a hosting company based in Texas, in the US. And you are being told that you have to support big oil because that’s what runs Texas. You don’t talk about the fact that you are running your hosting data centers on green energy. So it’s not that they’re not. It’s just that they’re not, it’s not necessarily part of their marketing message at this point, because the political climate isn’t necessarily conducive to that. [00:31:55] Nathan Wrigley: So you are saying that the hosting industry broadly are doing a fairly good job of this? [00:32:00] Louise Towler: Well, some of them are, yeah. I know for a fact a lot of the Google Cloud hosting is green and a lot of the big, they’re using Google data centers. [00:32:09] Nathan Wrigley: That feels like one of the most grounded things that you can do. If you’re having a website, you can actually go out and look for green hosting. [00:32:16] Louise Towler: And the Green Software Foundation has a little URL. It’s a little tool. You can literally go and put in your domain name and it will tell you whether it’s running on a green hosting. [00:32:25] Nathan Wrigley: What is the Green Software Foundation? [00:32:27] Louise Towler: It’s a sort of organization that is talking about green software, green web, green all sorts of things. They’re doing some really interesting stuff. They work a lot with very large organizations. I think to be a member you have, like have to pay up 10,000 pounds or something. It’s like out of my league to be a member, but it doesn’t mean I can’t see what they’re doing and listen to what they’re doing. They’ve also got a really interesting free course that you can do on sustainable software development. And it gives you all the background and all the things you should be considering when you’re building software and websites basically, and the things that you can do to make them run better in a greener way. [00:33:09] Nathan Wrigley: If I wanted to make my website more SEOable, I’ve got a whole suite of tools available to me. And many of them will give me some sort of data saying, okay, this page is, you’ve done a good job here. Like a traffic light or something you, you know what I’m saying? [00:33:25] Louise Towler: Yep. [00:33:26] Nathan Wrigley: Are there tools similar to that, that we can use in WordPress? Maybe it’s some kind of extension to a browser where we can see what our browsing is doing on the internet. In other words, is there a plugin, something which will show us a dashboard saying, okay this page, based upon the hosting that you’ve told us you’re using is consuming or creating this much carbon debt. [00:33:51] Louise Towler: There’s individual tools at the moment that I am aware of. You can put in a URL and it will say, oh yes, your page is this many grams of CO2. Actually what we’ve done is something. We’ve been doing a thing. I did that thing of having a side project to the agency, and we’ve been building something for the past couple of years, and we’re about to launch a piece of software. It’s an extension to WordPress, which will actually, in the dashboard, show you a daily carbon footprint of your website based on daily visits and page views. [00:34:24] Nathan Wrigley: How is that working then? So presumably the daily page bit is fairly straightforward. This website has been consumed 25,000 times, we can make the connection there. But presumably it must be figuring out, okay, that page had a video on it. This one had nothing but text, and it’s based upon upon some hosting. [00:34:40] Louise Towler: So we’re basically measuring the page, a measure of the data or page weight for each page. And then we’re looking at the visitors to the pages as well. [00:34:50] Nathan Wrigley: And are you giving like a score out at the end? [00:34:52] Louise Towler: We’re not giving a score at the moment, but eventually when the software’s launched and there’s lots of people using it, we will be able to say, oh, actually, in comparison to other people using our software, you are in the top quarter, or bottom quartile or you are in the middle. So we can give some feedback. But more importantly, if you look at it and you use things like traffic, then you can start to see where you should be optimizing. [00:35:17] Nathan Wrigley: Okay. And is this tool going to give you helpful advice on how to optimize it? [00:35:22] Louise Towler: Yes, we’re building out a knowledge base as well. [00:35:23] Nathan Wrigley: I was going to say, it’s all very well saying this page is doing really badly, but, you know, tough luck. [00:35:27] Louise Towler: Yeah. [00:35:28] Nathan Wrigley: So, where will it point me? What are the sort of metrics that you’re going to be helping me with? [00:35:31] Louise Towler: We’ll be helping with all the basics. It’s actually about empowering the content editors. Because as website theme builders and as website developers and designers, we can build the most amazing AA accessible website that’s really lightweight and fast. And then a year later we could audit it and find, oh, content editors added, you know, 30 images and they didn’t realize they had to add alt text to each one. And they can have loaded that really large video and not realized that it needed a poster attribute to make sure that the page didn’t take a long time to load. So what we are trying to do is give that feedback to editors in the browser when they’re editing the site, in the backend of the admin. Because that continuous measurement, if they see a little spike, or they see that suddenly something’s changed, they can go in and fix it. Rather than end up just doing an annual check, or checking every so often and ending up with a list of defects to fix, basically. So the whole point is, it’s about designing out people making those unconscious mistakes in the first place. And making sure the website continues to be at the standard it should be at and potentially improves over time. [00:36:44] Nathan Wrigley: So slightly off piste a little bit. That’s lovely. I mean I would hope to be able to see that kind of data and it would be really useful to me as a website builder. What about by just general browsing the internet? Do you know if there’s any tool which can tell me, right at the end of today Nathan, you’ve been a poor citizen. Some kind of, I don’t know, a browser extension or something which tells me. [00:37:05] Louise Towler: I don’t know that. Nobody’s ever asked me that question, so I will have to take that away Nathan and I will have to come back to you, because I genuinely don’t know the answer to that. [00:37:13] Nathan Wrigley: I think that would be quite a useful thing to know. At the end of the year, Nathan, your internet use is the equivalent of a 20,000 mile flight or something that would be. [00:37:22] Louise Towler: You must be online a lot. [00:37:23] Nathan Wrigley: I really am. Yeah. Okay, when are you hoping to get this tool out? [00:37:28] Louise Towler: We are doing a soft launch, early adopter, by invitation to Indigo Tree clients mid-July. [00:37:33] Nathan Wrigley: Okay. So really soon. [00:37:35] Louise Towler: Yeah. And then from then on we’ll be building out new features and basically getting it to the point where we can launch it to people as a SaaS product. [00:37:45] Nathan Wrigley: So going to go beyond WordPress at some point? [00:37:47] Louise Towler: Couldn’t possibly say, but yes. [00:37:49] Nathan Wrigley: Maybe. Maybe, yeah. [00:37:50] Louise Towler: Well, it depends on the roadmap and it depends what interest we get. And for me it’s not just about the commercial side of, we to build something that’s obviously profitable and successful. It’s actually where can we make the biggest impact? How can we, with what we are doing, make sure that we get the biggest carbon reduction overall. And the great thing about when you’re measuring stuff is we can actually report on global stats that are sort of, you know, a thousand clients and cumulatively this month they have reduced their carbon footprint by this amount. You know, so it is going to be an interesting journey to see how we get on and where the biggest impact can be whilst being commercial as well. [00:38:26] Nathan Wrigley: Yeah. It really does sound interesting. Okay, so we’re going to have to wrap it up. We’re probably at the edge of the amount of time that we’ve got. Where would we go if we are curious about the things that you’ve talked about? So maybe that’s a link to your, the product that you’ve just mentioned. Maybe it’s just a more general set of resources. What are the two or three top places that you would send people? [00:38:45] Louise Towler: I’d definitely have a look at the Green Software Foundation. I would also go to, there’s a Slack channel in the WordPress. I think they’re just about to create a team in Core for sustainability. So I’d be going and talking to them. And then I would be keeping an eye on people like Wholegrain Digital. Tom and Vineeta talk about things a lot. Tom’s got a really great newsletter that you can subscribe to. So there’s lots of people talking about it, but I think it’s about figuring out where it fits with your particular clients. And some of our clients are very values based and will immediately go for this. Some people just need that more commercial argument as well. [00:39:26] Nathan Wrigley: Well, Louise, thank you for telling us all about your efforts regarding sustainability and the environment. It is a genuinely fascinating subject, and my prediction is that this conversation is only going to get louder and louder. [00:39:39] Louise Towler: I hope so. [00:39:39] Nathan Wrigley: As the years go on. Yeah, thank you for talking to me. [00:39:41] Louise Towler: You’re welcome. Thank you. On the podcast today we have Louise Towler. She joined me at the recent WordCamp Europe in Athens to talk about websites and making them more sustainable. Louise is the founder of Indigo Tree, a UK based agency with deep expertise in WordPress websites. She gave a presentation at WordCamp Europe entitled, Digital sustainability: The benefits for business and the environment in which she emphasised the impact websites can have on our planet. Her aim was to deliver practical tips for users and developers to help them make informed decisions. This presentation is the focus of today’s podcast, and we cover quite a lot of ground. Louise highlights the significant role which electricity plays in powering data centres and transmitting data to end devices. Even if data centres use renewable energy, there is still a need to address overall electricity consumption. She points out that the internet is the fourth largest polluter globally, surpassing the airline industry. We discuss how the continuous and widespread use of the internet has made it difficult to reduce its own impact, whilst still emphasising the importance of the steps we can take to make the internet more energy-efficient. She suggests ways that we can all make a difference right away; educating clients about the consequences of certain design choices, such as using large videos or autoplay features that require substantial data to load. Optimising videos, images, and other website elements, which makes it possible to reduce data consumption and improve performance. The conversation then explores other suggestions such as using modern image formats, using images as placeholders for videos, self-hosted fonts, and considering the carbon footprint of email communications. Louise acknowledges the challenges of discussing environmental concerns with clients whilst also explaining that we have to come up with ways to make clients understand that these decisions are beneficial to them as well. After all, an optimised website is one that is looked upon favourably by search engines. Whilst clients ultimately are the decision makers, informing them about the consequences of their choices can help them be more informed. Moving onto WordPress, we talk about the responsibility theme authors play. It’s a crucial role, helping users make sustainable choices. Her agency builds custom themes for clients, which allows them to have full control over design decisions. We get into the subject of how legislation is certainly coming, and so getting in early and understanding the implications of such legislation will help your own endeavours in the future. Towards the end of the podcast we chat about some of the tools which you can use to assess the impact that your websites have, including a tool which Louise and her team have been working on for the last few years. If you’re interested in how your sites can become more sustainable, this podcast is for you. Green Software Foundation website Clients consider they have learned a lot through GPT or by Googling it. They assume they know what will work best for them. >> The post What the Client Thinks They Know appeared first on Do the Woo - a WooCommerce Builder Community . Listen in on our Woo AgencyChat where Shadi and Jimmy talk about the journey of productizing your services. >> The post Productizing Your Agency Services with Shadi Manna and Jimmy Rosén appeared first on Do the Woo - a WooCommerce Builder Community . WordCamp Dhaka (Bangladesh) 2023 has been cancelled by The WordPress Community Team due to concerns of corporate influence on the community decision-making process. The camp was scheduled for August 5, and organizers had already secured a venue and progressed on moving the camp forward. The Community Team published a statement on the event’s website, which cited the interference of corporate interests: The WordPress Community Team’s primary goal is to support and nurture the WordPress community by enabling organizers to create amazing events that celebrate WordPress, its community, and globally shared values. The Community team cannot support the event if a WordCamp is not aligned with these values. WordPress events benefit the WordPress community as a whole, not specific businesses or individuals. The Community Team expects that WordCamps decisions should be guided by the community’s collective wisdom and not influenced by any one company’s interests. When companies attempt to exert influence on the planning process, the Community Team must step in to mediate. In this instance, we have decided to cancel WordCamp Dhaka 2023. The Community Team urged the Dhaka community to focus on collaborative organization, companies uplifting the community, and greater diversity in participation. In an equally vague incident report on WordPress.org, which doesn’t even identify the WordCamp that was cancelled, Community Team contributor Sam Suresh called it “an unfortunate but necessary decision.” He summarized the team’s reasons for the decision: The decision to cancel the event was not a result of inadequate planning or insufficient effort on the part of the organizing team. Instead, there were observable actions from local community members to influence decisions that would benefit specific individuals or companies. When this influence did not immediately lead to their desired results, the individuals aimed to undermine the organizing process and event success. While the Community Team took steps to mediate, the inappropriate behavior and actions we saw necessitated the cancelation. This is a rare and extreme decision and underscores the severity of the situation. Suresh said the issues applied to the local meetup group as well, and that all co-organizers and event organizers were removed from their roles and required to repeat their orientation to gain access again. A community deputy and a mentor were also removed from their roles in the project and the companies involved in the infractions were banned from sponsoring WordPress events for a year. “In times of challenges like these, it is important to remember that anyone can organize WordPress events regardless of who they work for and that WordPress community events are for the benefit of everyone, not any one business or individual,” Suresh said. “As a community, we will not tolerate harassment or influencing unacceptable behaviors.” Shortly after publishing, several community members commented with objections to the level of secrecy around the issues at hand and the people and companies involved. The Community Team’s nebulous posts on the matter seem to have further scandalized the situation, instead of offering clarity and transparency. “This post definitely abides by the ongoing policy of not letting the community know who is being censured by the Community Services team, even in cases of egregious action,” WordPress marketing and meta contributor Sé Reed commented. “I’ve seen multiple cases of people filing harassment reports and various Code of Conduct violations, and that person/people have had various consequences, including being removed from organizing teams. However, those people then cite various reasons for leaving the team, often outright lying. But because of the secrecy around these cases, no one says otherwise and those people can and often do continue to operate in the community without any repercussions beyond secretly losing their ‘official’ role(s).” Reed highlighted the damaging effects of the secrecy surrounding these incidents, most notably that explaining the situation often falls to those who filed the report, as the Community Team abdicates any further responsibility after validating the report. “This action is damaging to the community as a whole, as we do not have a full picture of who we are working with and we continue to unknowingly support and empower people who have not honored their community commitments,” Reed said. Not all participants in the discussion were in favor of The Community Team identifying the individuals involved, but in this situation they demand to know the companies that were banned from sponsoring WordPress events. “I’m on the fence about knowing peoples’ names here, but I think people definitely need to know the companies involved; actively trying to sabotage a WordPress WordCamp is a serious breach of trust for the community,” WebDevStudios Director of Engineering Mitch Cantor said. “Especially when they may turn around and then make money from that said community they tried to sabotage.” Dealing with these types of sensitive situations is not an enviable task, but the community, for whom these decisions are designed to serve, is calling for a greater level of transparency regarding those who act in ways that are not aligned with WordPress’ globally shared values. “One way or the other, protecting folks who have violated the Community Code of Conduct is a policy that very clearly needs to be revisited,” Reed said. WordPress 6.3 Beta 3 is ready for download and testing! This version of the WordPress software is under development. Please do not install, run, or test this version on production or mission-critical websites. Instead, it is recommended you evaluate Beta 3 on a test server and site. Get an overview of the 6.3 release cycle, and check the Make WordPress Core blog for 6.3-related posts in the coming weeks for further details. Also, save the date for a live product demo tentatively scheduled for Thursday, July 20, 2023 at 16:00 UTC (link TBD). This will be a great opportunity to join the WordPress community to celebrate the accomplishments of 6.3 and this final chapter of Phase 2. Thanks to the many WordPress beta testers, this release contains approximately 34 (Site Editor) and 40+ (Trac) updates since the Beta 2 release. Nice work, team! Testers should note that the “Patterns Library” is now simply called Patterns in the UI. Additionally, pattern details now include a sync status and a lock icon is added for theme patterns. Browse the technical details for issues addressed since Beta 2 using these queries: 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. Review the many new features in WordPress 6.3 and focus your testing efforts on those areas in particular. Between the Beta 1 release and the final release candidate (RC), the monetary reward for reporting new, unreleased security vulnerabilities is double. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper. You can test WordPress 6.3 Beta 3 in three ways: The current target for the final release is August 8, 2023, which is about five weeks away. Your help testing this version ensures everything in this release is the best. Beta three, a peek Thank you to the contributors who collaborated on this post: @DanSoschin, @Meher, @JPantani, @eidolonnight, @davidbaumwald, @priethor, and @DanSoschin for the Haiku. Authors of the Ultimate Member plugin have released version 2.6.7 with a patch for a privilege escalation vulnerability. Last week WPScan reported that Ultimate Member had still not fully patched the vulnerability after multiple inadequate attempts. There was evidence that it was being actively exploited in the wild. Working through the complexities of this security issue, WPScan researcher Marc Montpas opened a ticket on WordPress trac, identifying an issue with the meta key field in the usermeta table using accent insensitive collations: Looking at the latest string of vulnerability issues that came up related to the Ultimate Member plugin I discovered that the usermeta table has an accent insensitive collation for the Imagine the attack surface this brings. In fact, don’t imagine, just look at the recent attacks in the wild. This particular issue made it more difficult to fully patch the vulnerability in question. Ultimate Member released version 2.6.7 on July 1, 2023, which whitelists for metakeys the plugin stores while sending forms. The plugin’s security advisory details a few other changes that may affect third-party developers: 2.6.7 also separates form settings data and submitted data and operates them in 2 different variables. [It] includes some significant changes to how forms submissions are handled. This may cause 3rd-party modifications to stop working. For Third-party developers, please update your customizations to support the new changes in the latest version Ultimate Member recommends users review and delete any unknown administrator accounts, reset all user passwords including the admin, enable SSL and backups, and send any advisories to site members and/or customers about the incident. The plugin’s developers are working on releasing a feature inside the plugin that will enable the website admin to reset passwords for all users, but it is still being finalized: The reason for this is a site using our plugin may have been hacked or injected with malware that sniffs login inputs, because this vulnerability issue is prone to these attacks, we recommend to reset passwords after updating with a security patch. This is to ensure the best protection for your website user’s passwords. All Ultimate Member users should update to the latest available version, 2.6.7, which has the patch for the vulnerability. The plugin’s developers are awaiting more feedback from WPScan and are evaluating all their extensions to ensure they are secure. Join WordPress Executive Director Josepha Haden Chomphosy in the 59th episode of the WordPress Briefing. Today she invites guest speaker Alex Kirk to discuss Polyglots’ work to continue to help bring translation to WordPress. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Host: Josepha Haden Chomphosy ( Intro music ) [Josepha Haden Chomphosy 00:00:10] Hello everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go. ( Intro music ) [Josepha Haden Chomphosy 00:00:39] I have with me Alex Kirk, who is a longtime WordPress contributor and who has been instrumental in recent innovations in the Polyglots’ work. Phase four of the Gutenberg project is native multilingual support, and so I see this work that is being done as instrumental, not only for our global community but in support of what’s to come in that specific roadmap. [Josepha Haden Chomphosy 00:00:59] So without further ado, Alex Kirk, welcome to the WordPress Briefing. [Alex Kirk 00:01:03] Hello, how are you doing? [Josepha Haden Chomphosy 00:01:05] I’m good. I’m good. Can you, let’s, because I bet that not a lot of people know who you are, can you first start by just telling me a bit about your work with WordPress, and then let us know what GlotPress is, for those of us who don’t know yet? [Alex Kirk 00:01:19] All right. So, Automattic sponsors me to work in the WordPress project on the Meta team and on the Polyglots team. So I spent time on improving or helping improve the software that powers the translation on WordPress.org. But I also work on the meta team on things like Matrix and evaluating if it would be a good fit for WordPress to switch to Matrix for their chat system. [Josepha Haden Chomphosy 00:01:46] So a lot of really big projects that you work on, all of that kind of stuff that has no easy solutions anymore, is where you are right now. Huh? [Alex Kirk 00:01:56] Yeah, there’s no clear path, but it’s our mission to find it. So that’s part of what makes things interesting. [Josepha Haden Chomphosy 00:02:05] Cool. So for folks who don’t know too much about the Polyglots team or generally translating WordPress, the software, can you let us know a bit about what GlotPress is? [Alex Kirk 00:02:16] Right. So the translation system that powers WordPress.org is called GlotPress. It used to be a standalone software that was developed a couple of years ago, and it was transformed into a WordPress plugin at some point, and now powers the translation that happens on WordPress.org. So we translate WordPress core there from English to other languages, plugins, themes, block patterns, and it all happens through this software called GlotPress. There are a couple GlotPress installations around the world, but I think the WordPress.org one is one of the bigger ones. [Josepha Haden Chomphosy 00:02:55] Probably, WordPress.org is pretty, pretty massive. Also, I think it’s great that you said that GlotPress was created a couple of years ago, like that, that indicates to me that you’re working on a really different timescale than a lot of folks are in WordPress. [Josepha Haden Chomphosy 00:03:10] So Alex, tell me a little bit about what it takes to ship translated WordPress software. So, I mean, for people who don’t need translated WordPress, like obviously we don’t have a good idea of what it takes to make sure that WordPress is available in so many languages. So what goes into the work of making sure that that happens? [Alex Kirk 00:03:32] All right, so typically the WordPress software and plugins and themes are primarily created in English. And for it to be available in other languages, it needs to be translated. And for that to be able to happen, the programmers need to make the software translatable. Basically, they’re providing each English string for the translation software to be available to be transformed, so to speak, into another language and to what it’s being transformed to. This is what the translators do. So they go into the GlotPress software and see the list of texts that need to be translated and translate it to their language that they speak. Typically there is a process around this. [Alex Kirk 00:03:32] So, we’ve got people who have lots of experience in translation. And specifically in translating WordPress or WordPress plugins. And they’re kind of the, the people who help ensure good quality of translation. So anybody who’s working the WordPress project, so basically who has a WordPress.org account, can come in and address the translation. And that translation enters the system, so to speak, in a waiting state. And then somebody who we promoted to be a Translation Editor will come along and take a look at your translation and will approve it or will give you suggestions how to do the translation in a better way, or come up with maybe even a better translation. [Alex Kirk 00:05:03] You know, when you have like a small thing that’s just not right, like a missing full stop or something like that. They might just add it for you. And well, as soon as the plugin or software is translated to a certain level of translations those translations will be shipped out to the WordPress installs. [Alex Kirk 00:05:20] So, for example, for a plugin, you would reach 90% of translated strings. Those translations will then be basically packed up into zip file, a language pack and delivered to each WordPress so that you can have the translations available there. [Josepha Haden Chomphosy 00:05:35] And is 90% the threshold for plugins only, or is that also the threshold for like themes and the CMS itself? [Alex Kirk 00:05:34] Well. We strive for 100%, I would say. [Josepha Haden Chomphosy 00:05:47] Good. ( laughs ) [Alex Kirk 00:05:48] And, 90% more of a motivational point. To be actually honest, I’m not sure if the threshold is 90% for every project or even if it’s actually 90%. It’s different between different GlotPress installations and it’s basically something that is made as a setting that can be changed. There’s, it’s an arbitrary number. Typically you’d actually want to make sure that the most important strings are translated first. So the ones like, if you look at the whole picture, software usually consists of many parts, many of whom are not encountered by people on a regular basis. For example, error messages that could be like obscure error messages, and you could argue that those might be not as important. Or even sometimes you could even say like, do they need to be translated? Because if you encounter an error message and you search the internet, wouldn’t you probably want everybody to search for the English one to find the solution? But that set-aside, it’s important to have like the headline of the plugin or like the most important strings translated, and typically translating those most important strings will take you to a pretty high percentage so that we can then say it’s good enough to be shipped. [Josepha Haden Chomphosy 00:07:02] Gotcha. I see, I see. Okay. Well, we talked a bit earlier about GlotPress’s timeline. It has been around for a bit, I know. But with that kind of in mind, have there been any notable changes to GlotPress recently? [Alex Kirk 00:07:19] Yeah, so I think for GlotPress there’s been a bit of an up and down over time in terms of engagement and progress on the software. But in, in the recent year, I think we’ve added a couple of things that have been very helpful for translators. So one of them was adding the commenting functionality, so yeah. [Josepha Haden Chomphosy 00:07:35] Super helpful. Shocked it wasn’t there before. Sorry, translators. Sorry, all of our polyglots. [Alex Kirk 00:07:40] Well, it can be like there was when GlotPress was created there, there is like the, a big part of GlotPress are these states, like the waiting state when you enter translation, and then there’s approved state, which basically a translation we say it’s set to current, and there’s all sorts of process around it. So if the software is updated or translation might get fuzzy. But also like, if somebody submits a translation that doesn’t fully conform to what’s the translation editors, or like what the standards of the translation community have been set to, then you would have to need to reject it. [Alex Kirk 00:08:16] And that has been something that we felt wasn’t a very good and enticing way of telling people like, we appreciate your work. It wasn’t just quite right, but it’s more of a rejection. So this is how we came up with this like, let’s give people the option to say what was wrong and give them a chance to try again without making them feel rejected. [Josepha Haden Chomphosy 00:08:38] Yeah. Sort of a “No, but…” as opposed to a, just refusal to receive it. [Alex Kirk 00:08:45] And other things that we’ve worked on is, like, with the recent search of AI, like getting help from AI on translation and also on reviews. So, there’s some interesting things that you can do with AI in that regard; that one important aspect of translations, it’s also that we’ve got glossaries for each language where people, basically the translation community, identifies certain words they want to translate them the same way every time. And with the AI, you can basically add to the prompt, like, please translate those words to those translations when you give me a translation for that. And as it can change over time, you can always adapt this to the prompt, and that has been proven quite helpful. [Josepha Haden Chomphosy 00:09:25] That is great. That’s one of those things I know that AI has been like a really popular thing to talk about. And AI, specifically for translations, I think has caused some concern that maybe we’ll just like translate it all and hope that computers get it right when we know pretty certainly that computers don’t always get the translations right. But that’s not what you’re talking about, right? What you’re suggesting is that AI would suggest what could be translated and what it could be translated to, and then human beings have to confirm that that’s correct, right? [Alex Kirk 00:09:59] That’s exactly it. So basically, we give suggestions to the translators, and then they can modify a translation before they press save. It’s more of a, like supporting them in getting the translations, like looking up words more quickly and all of that. [Josepha Haden Chomphosy 00:10:16] That’s wonderful. So is that the major sort of next step that is coming for GlotPress, or are there other things that we should keep an eye out for in that software? [Alex Kirk 00:10:27] So one direction that we’ve been taking GlotPress is basically making use of the fact that GlotPress is WordPress plugin now. And you know, typically, you would just use a GlotPress install. So on WordPress.Org, there’s like GlotPress installed, there’s translation projects created, something that we call “translation sets”. So for languages, you want to translate it to, it’s all pre-configured, and if you would install GlotPress to plugin on your own WordPress, it would be empty and not very useful. So what we’ve added is a way for you to basically be able to translate the plugins and themes that you’ve got installed in your WordPress into the language that you’re interested in. [Alex Kirk 00:11:07] So you might have a non-English website that you want to use certain plugins with, and they might not be fully translated at this point, so obviously, you could go to WordPress.org and help translate them, and that’s the way to, that’s preferred. But you could also now go install GlotPress on your own website and translate there. And then you have the translations there right when you enter them. And you can then contribute those translations back to WordPress.org. [Josepha Haden Chomphosy 00:11:35] So that’s with local GlotPress? [Alex Kirk 00:11:37] That’s something that we call local GlotPress. And you know, since we then have all these translations in the local database, it means we can do even more with those translations. So typically, language packs would be delivered to WordPress, but with local GlotPress, you’ve got like all the GlotPress software there. [Alex Kirk 00:11:56] So we can do things like inline translation. So, on your own WordPress and wp-admin, for example, we can highlight all the strings that can be translated, and those strings just have to right-click them and enter your translation, and that way, you can basically go about and translate the whole ui, seeing your progress, as you’re making, basically turning the screen from red to green. [Josepha Haden Chomphosy 00:12:20] Yeah. Yeah. So that’s something now that you can do in your local WordPress installation. [Alex Kirk 00:12:26] Basically, it’s completely independent of WordPress.org. We would ask you to contribute the translations back when you have them, but being independent also allows you to translate like premium plugins, which could not be hosted on WordPress.org or doing something like that we call like hyper-local translation. So, for example, I speak Austrian German natively, but even inside Austria, we’ve got different dialects or like special words that we use. And if I wanted to create a website that’s targeted at the Viennese market, for example, I might want to use those specific terms. And this is something I would have to argue for those translations to be accepted on WordPress.org because it’s a, it’s like a very targeted market. But if I have a local GlotPress, I can do those translations there. [Josepha Haden Chomphosy 00:13:11] That seems awfully beneficial, especially as dialects. I’ve been having these conversations. I have, in my extended family, many children, and they are all learning languages and one of them has been having kind of thoughts about, like, dialects and how dialects are almost another language. And if so, like how do you know what everybody’s saying when you’re speaking all the same thing, but it’s kind of a little bit it sounds a little bit different. [Josepha Haden Chomphosy 00:13:37] That’s certainly a thing in the US, the distinct dialects across our country. And so I imagine that that’s gonna be a really beneficial sort of implementation for countries that have a lot of different regional variations and certainly smaller countries that have technically the same language as somebody else, but a lot of regional differences, regional specific things. [Josepha Haden Chomphosy 00:14:01] Is that the same or different as the live translations, Translate Live, that we talked about at the WordCamp Europe a couple weeks back? [Alex Kirk 00:14:12] Right. So, Translate Live is kind of the next step after local GlotPress. It’s like this happy marriage between the WordPress Playground and local GlotPress. So the WordPress Playground is also something that has come up a lot. It’s basically a way for you to run WordPress inside a browser window, so in JavaScript. And at first, it seems like mildly interesting, I would say. But when you combine it with other things like local GlotPress, it can lead to really interesting opportunities. So with inline translation, for example, on WordPress.org, you would typically find for every plugin, the UI would look the same. You would have a table of strings, and all that makes you realize you’re translating this certain plugin is that in the header of the page, it says this name of the plugin, but other than that, it can look really all the same. [Alex Kirk 00:15:07] And now, with WordPress Playground, you can put up a WordPress and run this plugin inside that Playground. And now, if you add local GlotPress to the picture, you can also do the inline translation of that plugin inside the WordPress Playground. So you’ve got inline translation. We add the glossary so they do make sure that you translate things the same way that they’re expected, and you don’t have to install the plugin. [Alex Kirk 00:15:33] And still, you can see what the translations will look like. You can see the strings next to each other, and what I think is most important, you will start with the strings that you see first, which are the most important ones. When you’re in the table view, those strings might be somewhere buried in the middle, and yeah, it’s really hard to see progress if you start with kind of obscure error messages, for example, versus just starting with the things that you see first. [Josepha Haden Chomphosy 00:16:02] Yeah. So, moving translations away from table-based translations where you kind of have to know what you’re looking for. So the Translate Live, along with local GlotPress, along with WP Playground, is going to make it so that it’s easier to see visually what needs to be translated, where, what’s most valuable to translate for your mid users and your end users, basically. Yeah? [Alex Kirk 00:16:30] That, and also like for plug-in authors, it can be really good to see, you know, you can switch the languages in the Playground to another language, and you can quickly see like what’s the state of the translation in this language or in that language. And even things like, you know, Arabic as an RTL language rights to left language. The sidebar will change to the right, and you can also just switch language and see like, what’s my plugin like in this environment. I mean, this is not technically something that’s related to local GlotPress, but in this translation live ui, it’s very easy to change languages and see your plugin in another language. [Josepha Haden Chomphosy 00:17:06] I mean, it’s not specifically related to, to Translations Live, but also, I think that if we’re saying that WordPress not necessarily is going to lead the way with translations and native multilingual support in our CMS because, of course, it’s still a little bit far out on our roadmap. We certainly have an opportunity to have the best implementation of that. [Josepha Haden Chomphosy 00:17:27] And even if like that specific use case that you’re talking about isn’t related directly to what it is that you are working on for Polyglots and inside GlotPress and all of that, I do see that having more streamlined, more easy to see and access opportunities to like test the way that our software looks across varying environments, especially those that change it substantially from what we typically work in day-to-day for any individual developer or any individual WordPress site implementer. [Josepha Haden Chomphosy 00:18:00] Like, I think that that is a big step forward for all of us and certainly for anyone who is having to use WordPress as not a native English speaker. And so you say it’s not related, but it still is a big, a big benefit for WordPress overall, I think, to have this kind of work happening so that we can have those benefits to the folks who are using our software. [Josepha Haden Chomphosy 00:18:22] So there were a couple of different things that you mentioned over the course of our conversation. We’re gonna put some links to the show notes for all of those. But one thing that you mentioned that just kind of went by, and we never really had an opportunity to talk about it. You talked about the, I think it was GTEs, Global Translation Editors, the folks that are like approved as final approvers of translations. If there is someone who’s listening to this podcast who wants to become a GTE someday, where would they go to do that? [Alex Kirk 00:18:54] So the path to GTE is a PTE. ( laughs ) [Alex Kirk 00:18:59] So, we’ve got different levels of translation editors. Basically, you start, you could say you start off as a translator, and this is how you can kind of show that you can do good translations or that you’re very firm in your language. And this might make you be noticed in the community. [Alex Kirk 00:19:16] So we’re always looking for people who like to help with translations. And you might be then promoted to be a Project Translation Editor. Basically, it means that for a single language in a project, you’ll be able to approve translations. So, you’ll be the one who says, like, this translation is a good one and this conforms to the to the rules that we have stated as a translation community. [Alex Kirk 00:19:42] And further down the path then is the GTE, where you basically are allowed to approve translations across any project on translate.WordPress.org in your language. And that’s, usually you’ll be in, in that position with other GTEs. [Alex Kirk 00:20:04] So there is, like, in each community, there is like, we’re people based. We talk about what might be a good translation. We talk to each other, try to find rules that maybe prevent common mistranslations, or set the standards for how we want the software to be translated. And this is something where you get a voice as a translator, but as a GTE, you get into a position where you can actually make the changes or find consensus on how the software should be translated in your language. [Josepha Haden Chomphosy 00:20:35] And if folks are not familiar where the Polyglots team works and meets, where would they find you all? [Alex Kirk 00:20:41] At make.WordPress.org/polyglots. [Josepha Haden Chomphosy 00:20:45] Perfect. Alex, this has been such a fascinating conversation. Thank you so much for joining me today. [Alex Kirk 00:20:50] Thank you very much. ( Intermission music ) [Josepha Haden Chomphosy 00:20:59] So that brings us now to our small list of big things. First, WP Campus 2023 is taking place July 12th through the 14th. That’s a nonprofit three-day conference with topics that focus on the growth of higher education, accessibility, WordPress, and anyone who works in higher education. [Josepha Haden Chomphosy 00:21:17] It’s a hybrid event. There is an in-person component on the beautiful campus of Tulane University in New Orleans, Louisiana. I’ll add information about that in our show notes for anyone who would like to join in person or online. [Josepha Haden Chomphosy 00:21:32] The second thing is that the mentorship program pilot that I have been talking about a little bit over the last few months has been formally launched. [Josepha Haden Chomphosy 00:21:39] If you are interested in contributing more to the project but not sure where to begin, take a look at this comprehensive onboarding experience. It’s cohort-based. It has some personalized one-to-one mentorship. There are guided courses, live workshops, all of that. So read more about it in our show notes and sign up for one-on-one team mentorship. [Josepha Haden Chomphosy 00:21:59] And then, finally, Matt mentioned at WordCamp Europe an idea that he had been thinking of for some time a Make team dashboard that would sort of help define team metrics and help identify for individual contributors what should indicate team health and where they can find the most impactful projects to work on. [Josepha Haden Chomphosy 00:22:20] A post has since been published on make.WordPress.org/meta calling for additional feedback on that idea, so that we have an understanding of what this could be, how the dashboard can kind of come to be. And so stop by and add your thoughts there in the comments. [Josepha Haden Chomphosy 00:22:38] And that, my friends, is your small list of big things. [Josepha Haden Chomphosy 00:22:42] Thanks for tuning in today for the WordPress Briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks. ( Outro music ) There are many ways to be a guest or host on the podcast. Or maybe you have an idea you would like to pitch. >> The post Opportunities on Do the Woo appeared first on Do the Woo - a WooCommerce Builder Community . Howdy, I am sending this while traveling back from WordCamp Leipzig, where I had great conversations with people from the German WordPress community. I published a few photos on Twitter: here, here, here, and on LinkedIN. Language switching is as difficult as context switching. WordPress 6.3 Beta 1 is released, as well as Gutenberg 16.1. More below. Yours, 💕 If you haven’t yet, it’s time to reseaver your seat! for next week’s Gutenberg Live Q & A on July 6th, 2023, at 17:00 UTC Leveraging Gutenberg’s architecture to take plugin development to new levels. Learn how Gutenberg components and scripts can be used outside the block editor to revamp a plugin’s code base in this Case Study of GiveWP 3.0 with Jason Adams, Director of Development, Jon Waldstein, Lead Developer of GiveWP and co-host Lena Morita, JavaScript Developer on the Components team. On Tuesday, WordPress 6.3 Beta 2 was released, after Beta 1 wasn’t quite finished the day before. The release team is also preparing a Walk-through for later this month, to introduced many of the new features coming to a WordPress instance near you on August 8, 2023. Please, help test WordPress 6.3, and report issue you encounter. Gutenberg 16.1 was released led by Isabel Brison and Ramon Dodd. In their release post, What’s new in Gutenberg 16.1? (29 June), they highlight the following functionality: It was great fun to catch up with Tammie Lister as my guest on the Gutenberg Changelog. I hope you also have fun listening to us discussing the milelong Changelog for this Gutenberg release. The episode and the show notes are already available. The transcript is still in the works. 🎙️ New episode: Gutenberg Changelog #85 – Gutenberg 16.1, WordPress 6.3 with special guest, Tammie Lister and host Birgit Pauli-Haack Sarah Gooding also reported on the Gutenberg 16.1 in her article: Gutenberg 16.1 Introduces Pattern Creation and Library, Adds Distraction Free Mode to Site Editor, highlighting additional functionality found in this mamooth release. In his latest video, Unlocking the Power of Navigation in WORDPRESS 6.3: What YOU Need to Know, Dave Smith, JavaScript developer at Automattic and core contributor, walked us through the updates to the Navigation handling in the Site Editor. It helped me wrap my head around all the different aspects of creating mulitple menus, style them and add them to templates and template parts in the site editor. Anne McCarthy and Emily Clark will co-host a Hallway Hangout to discussion WordPress 6.3 performance improvement on July 27, 2023 at 15:00 UTC to discuss WordPress 6.3 performance improvements led by performance reps Emily Clark and Felix Arnzt and also look ahead to WordPress 6.4. Mike McAlister advocates for Don’t call it Gutenberg anymore (unless you actually mean to). “it’s time to drop the Gutenberg vocabulary from our day to day usage, unless we’re actually talking about the Gutenberg project or development plugin.” he wrote. In the post he gives a quick overview of the history of Gutenberg development and how the block editor made it into the WordPress. Rich Tabor published a new Pattern in the directory on WordPress.org: Two Column, Matted Gallery Images. “I really want to keep pushing whats possible with all this new design tooling in WordPress.” Tabor tweeted. With WordPress 6.3 you will have a way to create patterns for your site via the site editor. It used the same interface that allows you to create reusable blocks, now called “synched patterns”. In his, Benjamín Pérez Sout at Yotako,vannounces the new plugin release that allows users to Edit your Figma & Adobe XD designs as WordPress Gutenberg blocks. The toolset of Yotaku provides some amazing synergies between AI and various design tools to Gutenberg Blocks. Ryan Welcher continued his series Creating a block theme for developers with Part 4 and Part 5 on Twitch. If you want to catch up on Parts 1 through 3, they are available on Welcher’s YouTube Channel “Keeping up with Gutenberg – Index 2022” The recording of this week’s Developer Hours: Exploring Editor Extensibility is now online with Michael Burridge, Nick Diego, and Ryan Welcher giving demos on various ways developer can already extend blocks and the editor experience. They also shared lots of resources and examples. Igor Benic explained in his blog post How to Programmatically add a block in the WordPress Block Editor. “When working with custom blocks or custom solutions to enhance the WordPress Block Editor, you might need to have a way to add blocks programmatically to the editor.” he wrote and showed how to use – Working with Blocks also means getting data via the Rest API. The team of Learn WordPress just published the new course on Introduction to developing with the WordPress REST API. “This course presents a developer-oriented introduction to using and developing with the WP REST API. If you want to learn to use the WP REST API to power your next site build, plugin, or theme, or you just want to understand how it works, then this course is for you.” they wrote. Need a plugin .zip from Gutenberg’s master branch? Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph. For questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com Featured Image: Train Station at Leipzig, Germany. Photo by Birgit Pauli-Haack Don’t want to miss the next Weekend Edition? Tammie Lister and Birgit Pauli-Haack discuss Gutenberg 16.1 and WordPress 6.3 and what’s coming to 6.3 Add a summary/excerpt here Show Notes Podcast With Tammie Lister: How Gutenberg Evolves and the Future of WordPress with Emma Young at Hostinger Creating Gutenberg – Live Q & A w/ leads Tammie Lister, Joen Asmussen and Matias Ventura July 6th, 2023 – 17:00 UTC Leveraging Gutenberg’s architecture to take plugin development to new levels July 21, 2023-17:00 UTC Live Q & A with designers and developers for WordPress VIP. They created a bridge between Figma Design themes and the theme.json file for classic and block themes What’s new in Gutenberg 16.1? (29 June) Gutenberg 16.1 Introduces Pattern Creation and Library, Adds Distraction Free Mode to Site Editor Proposal: The Interactivity API – A better developer experience in building interactive blocks WordPress.TV: Developer Hours: Introduction to the Interactivity API Stay in Touch Transcript Birgit Pauli-Haack: So hello and welcome to our 85th episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about Gutenberg 6.1, WordPress 6.3 and that’s pretty much it. We have a full program alone with that. I’m your host, Birgit Pauli-Haack, curator at the Gutenberg Times and full-time core contributor for WordPress open source project sponsored by Automattic. And I’m so happy that Tammie Lister joins me today. She’s one of the Gutenberg design leads of phase one and design lead of WordPress 6.3 release squad and will be the editor tech co-lead on the all underrepresented gender squad for 6.4. In her day job Tammie works at the global agency Inpsyde from Germany as a developer. Good afternoon, Tammie. So happy to see you again. Thank you so much for making the time to be on the show. How are you? Tammie Lister: I am great. Thank you so much for having me. Birgit Pauli-Haack: Oh, it’s so wonderful. And for our longtime listeners, you are no stranger. You’ve been on the Gutenberg Live Q&A few years ago, and you were part of the last year’s developer hours, and it’s actually the first time that you’re on the podcast. How did that happen? For those of you listening for the first time, tell me a little bit about your WordPress work and what you’re doing now. Tammie Lister: So my WordPress journey has been a long one and an awesome one. Like a lot of people, I started out by blogging and poking around themes and then I worked for a long time on the problems with themes, went via core through BuddyPress and then for a long time I worked as creating themes and working through that. And that’s where I started really my contribution journey through the theme review team and a little bit in core. And then Gutenberg, I guess it was my adventure by Gutenberg. The seed of Gutenberg is rooted in a lot of people from the theming background. It’s one of those not so hidden facts about Gutenberg, that a lot of people who worked on it had that background as well. And I’ve been really lucky since I worked on that project, to have quite an adventure working in various roles from design. And at the moment, I’m really lucky to be balancing back my developer skills. I’ve always done both, but at the moment I’m really focusing on how can I raise back up those skills, and I’m really lucky to be doing that in an agency role. So I am now getting to work with this amazing thing that we’ve created in the editor and getting to implement it within the agency at a development level so that I’m having all sorts of fun now. Birgit Pauli-Haack: Yeah, I can imagine that. That’s awesome. Well, thank you so much and yes, so you will have opinions about the extensibility of Gutenberg, which is one of the top… Tammie Lister: Only a few. Birgit Pauli-Haack: That will come or that has been in the background or in the other current of all the new features, where’s the extensibility or how can we extend this? So before we dive into the recent releases, I want to tell you dear listeners all about the two live Q&As that are coming up in July. So next week, we have on July 6, 2023 at 17:00 UTC and I’m not going to convert this to any other time right now. Time zones are the bane of my existence at the moment. So we have the topic, leveraging Gutenberg’s architecture to take plugin development to new levels, and we learn about how Gutenberg components and scripts can be used outside the block editor to revamp a plugins code base. So this is a case study of GiveWP 3.0, how that’s come about and we will have a guest, Jason Adams, who’s the director of development and Jon Waldstein, who’s the lead developer on the show. And my co-host will be Lena Morita who is a JavaScript developer on the components team. So she has some really geeky questions for the two and she’s quite excited about it, and I’m really looking forward to it because I find it fascinating when developers discover all the ways to use existing components and script to build on top of Gutenberg. And it saves so much development time and it opens up new synergies between the core and the added functionality in a plugin. So if you’re interested to dive in, the next one, two weeks later on July 21st, also at 17:00 UTC, we will hold the next live Q&A with designers and developers of WordPress VIP, and they created a bridge plugin between Figma design themes and the theme JSON file for the classic and block themes. And it’s a fascinating way to keep faithful to the existing design systems and start spinning up new sites that mirror that design system without a whole lot of friction in between us. My co-host will be Joni Halabe from the web team at Georgetown University, also a very interesting live Q&A. I’m really happy that we’re putting it together. The last one, you have to just subscribe to the newsletter so you get early access to it, newsletter at the Gutenberg Times and should you listen to this episode, I know a lot of people binge listen to it. If you listen to this episode after July 22nd, check out the Gutenberg Times YouTube channel for the recordings of that. We always record them, we have them transcribed, we have a post on the Gutenberg Times with the resources shared and all that. So even if you miss it, but the live Q&A is really interesting because all of a sudden from the demos that are there, there comes these very quick questions from the audience and I really like having that a live show. So that’s that. We are coming to the what’s released section and we come to what happened last night. So today, we are recording it on Thursday, June 28th and this morning in I think 1:30, WordPress 6.3 beta two was released. And were you up at that time? Tammie Lister: No, I got up as far as about just hitting 11:00 UK time at night and I could see it wasn’t going to be the 11:00, so I left the amazing people that were doing and I’d kept going that far, and I bowed out and got some sleep because it was the second night running. Birgit Pauli-Haack: Yeah, there was a second shift coming in from Australia. Tammie Lister: Which is amazing. That’s part of the global project. We all get to open doors and close doors after each other, leave post-it notes virtually up for each other. There was a lot of that going on for the past two days and I think that’s the important thing. It’s been two days we’ve been working to get this out. Birgit Pauli-Haack: Yeah, the make blog has one was the delay for one day and then also the explanation why it’s now called beta two instead of beta one. Tammie Lister: Systems are hard. Birgit Pauli-Haack: Systems are hard, releases are hard. I have switched my role for this release from doing for three releases, dev notes wrangling to actually be editor triage, co-lead with four other people. And this has been quite an interesting experience because all of a sudden, I’m looking behind the scenes and how timely a lot of PRs are to getting into the beta. And then it’s not only that there’s in the plugin, but you also need to sync the core data, the PHP code with the Gutenberg code and that is another big adventure for the tech leads. And you get to do this, when is it? In September before beta 6.4. Tammie Lister: Yeah. And I think you never know the unknowns until you know them and then you document, and then you try and that’s the important part of this amazing journey that is these big projects. You can predict most things but it’s always going to be the thing that you don’t predict. Honestly, we are doing incredible. Everyone is doing incredible. We just have to remember humans’ need to sleep sometimes and I think that is the beauty we learn. One of the amazing things we do now, which we didn’t do before is we have the use of the time zones. We use that. We have multiple leads. I think back even a few years ago, we didn’t have that for these roles and by having that, we can take advantage of time zones and lives and different people, but just documenting and writing, I think there’s going to be some like, “Okay, so that could happen.” Okay, now we document this, now we learn this and that’s great. There’s stuff I now want to learn about. My curious brain is like, “Okay, well this went wrong. Okay, so how do we learn?” And that’s great because our documentation gets better. That’s generally what happens in between releases where people debrief and then take everything that happened in a release and then the next release gets better each time. We rise on the past release each time. Birgit Pauli-Haack: Right, yeah. As you know, this big project, nobody really knows everything. So the collaborative effort is… Tammie Lister: And if they claim to, I really think they need to go for a little walk in the countryside and think about themselves because nobody does and that’s amazing. You’ve just got to be very humble and just go, “Okay, on we go.” I just wanted to say shout out to everyone that was working so hard the past 48 hours and then some. You saw some beautiful handovers of patches, people just teleporting in on their phones and doing things and just some amazing open source hearts. You saw a lot of that going on. Birgit Pauli-Haack: And I saw a lot of also the humbleness stuff. I don’t know, does somebody else is able to help me? Tammie Lister: I don’t know, but I might know someone who does in their mental Rolodex going through a list of people, and that’s amazing to do. It’s not like I might know, I’m going to struggle with it for a while and then I’m not going to come up with a good solution. That does not help anybody. Birgit Pauli-Haack: No, no, no. At that moment, you need somebody who knows. But it’s also… Tammie Lister: It would help otherwise you make it worse. It’s like the I will fix this and make it worse. Nobody needs that at 10:00 at night. Birgit Pauli-Haack: Yeah. Not on a software that’s used by millions of people. Tammie Lister: But a beta is a beta. And I think that’s the amazing thing we all have to… Now, let’s test it now let’s poke it and do things and nothing is ever going to be bug free. We always want that, but we do our best every time. I am so excited about how big this changelog is. Birgit Pauli-Haack: Yeah, we’re getting to that. But I just wanted to do a shout-out for Brian Alexander who’s heading the test team. He has put together some amazing instructions on how you can make really impactful contributions to this open source project and we will share the link in the show notes. So when you go to the test make.webpress.org/test, that’s the first post that will come up is help test WordPress 6.3. There are quite a few features coming in and they all need testing and they all need hitting the real life scenarios. Have plugins that use some of that, themes, just poke it from all the ends and it’s really necessary. And like every beta, it’s beta, but the bugs that we find now in the beta two, three and four, we don’t have to fix later when the release is done. So yes. What also was released was Gutenberg 16.1 and that’s when 255 PRs merged with this release by 69 contributors and it’s just amazing what all went in there. It’s also understandable because if it went for the last minute, nothing really gets done in life, I found. And everybody wanted to get their work merged, so it will be in the next WordPress release and with the beta this week, it’s the last plugin release for enhancements and new features to come in. After that, it’s all bug fixing. So that made it for a mile long changelog. And Tammie and I will do our best to pick the stars amongst the 255, the bright shining stars and the highlights for you and talk them through. So do you want to hit us off with the first thing or do you have any other comments to add? Tammie Lister: Wow, the amount. I guess the first one would be the navigation menu sidebar, the renaming, duplication, and deleting of navigation menus from browse mode sidebar. Navigation menu sidebar, the maturity of that in general, it feels such a long adventure the navigation menu has come on and I think that’s also maybe this point is why there was so much as well. It’s not the final-final release, it’s like Photoshop when you name a final-final 01 file or something, but it’s a closure and I think having a navigation block, having things changed, all these things, it’s a closure for a lot of these features. So I think navigation, it feels like quite a closure on some of these things as well. Birgit Pauli-Haack: And it now made real sense. I think it really needed to gruel it and often and throw out concepts and get new ones there. So there’s navigation and then there is the sidebar menu in the site editor that also has a navigation piece to it. Tammie Lister: But bringing that functionality means that you then… There’s this weird separation, but it allows that to feel more cohesive and native. That’s the best words I can think of it. I think navigation’s going to take a little while to get a lot of people using because navigation’s over here and all these kinds of things. It’s that maturity of that feature and the dependability of that feature and the work there. I’ve definitely started feeling that it feels more robust to use with these changes. Birgit Pauli-Haack: Yeah. Tammie Lister: It’s pretty exciting. Birgit Pauli-Haack: And I finally feel the same way. I was always a little hesitant to touch the navigation because I knew it wasn’t finished. So I didn’t want… Tammie Lister: You sneeze near it, it’ll fall over, bless it. And I say that having worked on it myself, but it’s just a really hard problem. Turns out navigation… Linking alone is a hard problem, but navigation is linking plus plus plus. It’s a really difficult problem. If you just write code, it felt easier. But if soon as you add any interface, it’s really difficult. Birgit Pauli-Haack: And it’s also such a prominent piece of a website that you build, that it really needs to… Tammie Lister: And people are very bonded to a particular way of using navigation in WordPress as well. So we’ve got to retrain that mindset. Birgit Pauli-Haack: Yeah, that definitely is true. And so we have the navigation and the sidebar and the site editor as a navigation menu where you can do certain things and from that menu, from that sidebar, you already can rename, duplicate menus, or delete them. You cannot create them. That’s what you do when you create, you add a navigation block to a template part to the header or to the footer and then on the right hand sidebar on the white sidebar, that’s where you assemble your menu or the many menus. Tammie Lister: I like that consciousness of creating them somewhere else. There there’s so many opinions on separation and workflows. I feel like… This is a complete personal opinion, but making navigation too easy, I think that you end up with too many navigation everywhere. That’s always been one of our problems, that you end up with people drowning in menus. So I think that there’s a balance that there’s a maturity of navigation. I think that’s where the overlap of this. Birgit Pauli-Haack: Yeah, definitely. And I like that in the site editor left side navigation, you just touch on the overall website, but you always go into the canvas to actually make changes. Tammie Lister: The best words I can use is assembly there. I don’t know if that’s a good word, but it feels like assembly there, functionality doing here. And then that’s what it feels like. The different mental models that I’m moving in between when I’m doing things and I’m for that, different areas having very distinct different mental models when I’m doing it. Birgit Pauli-Haack: And I like that too because I can’t have two different thoughts in my head at the same time and be productive. Tammie Lister: Life’s too short. Birgit Pauli-Haack: Yeah. So that’s why I like the next item, that the footnotes block is now coming to text blocks and that’s really something that we have all been waiting for a long time. And I know that Ella van Durpe has also tried multiple ways to get this done and I think she has such great ideas that she all pursued them all. And in the GitHub, you can have the history of all the footnotes, but I think this version is really hitting it out of the park. It works well. You put the cursor where you need the footnote, you get it from the menu from the inside menu bar menu dropdown on the block toolbar, and then you say footnote, and then it gets you right into the place where the content of the footnote, you can add that and it does the numbering itself. So if you say, “Oh, I put a footnote in the middle of a paragraph, but also I need another one on top of it,” it recounts them so automatically. So that’s a really good feature. And it has color controls, but it also follows whatever your paragraph or your link color is. I just see that when you change the background of a paragraph, you get what you always get with links is if you change the text, you also need to change the link color. But that is something that’s the nature of the beast and there is no automation for that. But I’m really happy that this block comes and it will be in 6.3. Tammie Lister: Footnotes has an adventure for many years. I think footnotes is one of those, to me, it’s a sign of maturity for an editor. Quite a few see it as extra functionality or features. But it really is something that if you are in a particular field or you are particularly using, that you will not use an editor unless it has the footnotes functionality. It’s whether you choose to use or not. There’s no doubt whether you would want, you wouldn’t even have a plugin. It would be base functionality. So I think I am very glad to see it. Also, it’s a really strong indicator of things like collaboration. It sets that. It may not feel like it, but it is. It sets those using that canvas in a little bit of a different way as well. So I’m really pleased to see it. Birgit Pauli-Haack: Yeah. Tammie Lister: And that experimenting outside to then bring in, I think is a real good way forward to start seeing the interface as well. Birgit Pauli-Haack: Yeah, definitely. Definitely. And then you could actually move the footnotes block where all the footnotes are to the end of things or put them a little bit further. So it’s also quite versatile. Tammie Lister: That’s really important depending on what article you’re writing as well. I do not claim to know any different medical whatever articles, but I’m sure that there are certain rules and regulations around where things go and depending on articles and what order things go. So having that functionality that you can determine yourself is better for everybody. Birgit Pauli-Haack: Yeah, absolutely. Absolutely, yeah. Tammie Lister: The next big one. Birgit Pauli-Haack: Yep, go ahead. Tammie Lister: I feel like there’s a whole episode here on patterns and I guess the big one here is the naming and language to me is… Again, we talk about maturity, well renaming reusable blocks, rename to my patterns and add option to also add a non-synced pattern. This is big, it’s a small big thing I guess because it’s a big thing, but it’s not a massive feature, is it? But it also is a massive feature. Reusable blocks are quite limited but really quite bonded for some people. So I think that we got to respect that. But patterns to me are what everyone always wanted with reasonable blocks. When everyone describes what they want from a reusable block, it’s a mature functional pattern that has all the things that patterns are getting like syncing, all these things. And that’s what patterns are getting now. So I don’t know what you feel, but that to me it’s just maturity of patterns, you have blocks, patterns, template parts, templates. It makes sense. Birgit Pauli-Haack: Oh yeah, yeah. They’re pretty much cut from the same cloth and all had different names and also different models. So you had to get here for template parts, you need to go there for a reusable block and you had a pattern here, but they all had different updates kind of thing. So if you update a reusable block, it updates on all instances. A pattern doesn’t have any updates, so every time you put them into a canvas, they are all disintegrating. They don’t know about itself anymore. But what I like is that you now can create your own patterns and that is something that a lot of people were missing, that you were dependent on the pattern directory or you were dependent on the theme to provide your patterns or some third-party directory where you can copy paste it over, but you are not able to say, “Oh, this is a marvelous pattern. Can I store that on my site?” And now you can. And it’s the same interface or same workflow that you are accustomed to when you create a reusable block and there’s only one change there… Well, one attribute, it’s called sync this over all the instances, yes or no, it’s a toggle switch. So if you switch it on, you get a reusable block that if you change it, it changes all the instances. And if you switch it not on, it’s a pattern which does not update. But this is also, and you say, “Okay, but I want, when I change the style of my pattern, I want it to be replicated over all the instances.” It’s coming. This is the first step. This is the first step to unify the wording, unify the interface. And then also, you don’t have this duplicate mental model anymore. You find them and you can edit them at the same spaces. It’s called my custom patterns. That’s how you find them in the pattern list. And then in the block when you highlight them, there is manage your patterns. So it’s a great step and it’s one that we have been really all waiting for. Tammie Lister: And putting my agency hat on, really trying to explain all this language. People, they work in design systems, they work in simple language and been able to sell this easier by simpler language that it behaves more like a design system as they expect. This all is that. You don’t have to then build a system on top because then the system will be easily done within, you don’t then have to bring the system. So I am very excited about this. It is the start. It is something that I would’ve liked a couple of years ago, but we had so much to do. We’ll get there. And I think that is the thing of there’s so much changing to do. Patterns are really getting strong. When they first came out, it felt like, “Oh, you can do patterns.” But they are so powerful. People get patterns way more than blocks as well. If you explain a block, people are like, “You don’t need to make blocks.” And I think we’re going to see less blocks people making and more patterns with this because patterns are just more useful then. Birgit Pauli-Haack: That’s what I have been seeing as well is also that people say, “Okay, I don’t have to create a custom block just because I want a group of blocks in my site.” Tammie Lister: As much as I love block variations, I love all these things that you can do because blocks were amazing. I’d like to see less because then it means that patterns are doing what they’re meant to do because that’s what humans see. The interface that we’re having for pattern browsing and all that, we’re getting onto the management stuff that’s also part of this, that is just better as a human. Those human interfaces, once humans are using that, that’s way better than the tiny little pickers that we have for blocks. Birgit Pauli-Haack: Yeah. But I wanted to go back to what you said, while I would love to have it two years ago, but I think sometimes waiting helps you really to see the big picture, the whole picture. So two years ago, we didn’t have template parts, yeah? Tammie Lister: Yes. Birgit Pauli-Haack: Or we didn’t know yet how they’re going to fit in into the block themes and in pattern, we’re just at the beginning, but we didn’t know how to lock them. How to lock certain pieces of it. Tammie Lister: When I say that, that’s just eagerness and that’s also… Birgit Pauli-Haack: Yes, impatience. I see it, I want it. Tammie Lister: Way too many people in the agency just want it tomorrow because honestly, those are the people who are trying to solve it with design systems who are trying to work around the problem today. Absolutely, these toys are amazing. And that then means these bigger systems can start using. They don’t have to build on top or around. They can build a lot more natively and the more native you can build, the easier upgrades, the easier components, everything. And it’s just a better experience for everybody. Birgit Pauli-Haack: Right, right. Or you see the power now and you say, “Oh, wouldn’t it be great? And then you have to wait. Tammie Lister: If no one ever has to go through a load of patterns and I’ve actually had to do this, go through someone makes a change in patterns, but this was quite a while ago. If you use patterns and then you had to make a change in patterns at scale, that was hard to do before. Not having to do that, that’s going to be amazing. So getting all the amazing benefits of all these things, but having the amazing benefits of things like reusable blocks, but with these visual benefits that humans have. Yeah, it’s amazing. We have all the toys. Birgit Pauli-Haack: And there’s one more toy coming, which is now you can get a preview of block themes in your site. We all remember the customizer where you install a theme on your website and then you use the customizer and you were able to preview your site with the theme. And that hasn’t happened yet, but now it’s here for block themes as well. You see where you have all your themes, you see a live preview button and that gets you into a similar interface as the site editor. And then you can navigate your site with the theme that is installed but not activated yet. So you can see how your blocks behave, you see how your posts behave, and in advance you don’t have this what Helen Hou-Sandí always calls the save and pray feature there. Tammie Lister: What you see might maybe what you get, but possibly not. Birgit Pauli-Haack: Probably different, yes. And it’s amazing to see this in block themes. You also see all the style variations and how they would change your website and it’s really amazing. And it’s in 16.1 and it will come to 6.3 soon. Tammie Lister: And moving on to the site editor, the distraction free. We’ve had distraction free, so it’s like ta-da. But having that with the site editor, been able to create and just go get away. I remember… Age, that Dreamweaver full screen mode. And you now got that. The day where you could suddenly do visual in Dreamweaver, we’ve now got that in WordPress. Wow. It’s incredible to think that we can do that and you’ve got that without some of the ickiness. Bless it. Without tables. But we’ve now got that and that means that you can really focus on what you’re creating. And sometimes like if you’re doing some of these three-column query or whatever when you’re trying to do, you do not need those side panels and everything in the way. So distraction free is really, really nice to be able to do that and create. We talked earlier about modes when you’re doing things that really helps you with that creation mode, there’s a reason why when you are writing, you have those zen modes and that really works for people. Or you have that get away from my desktop all the apps. I don’t know what you feel, but I think this is just a small improvement to life. Birgit Pauli-Haack: Absolutely. Tammie Lister: Quality of life improvement. Birgit Pauli-Haack: Absolutely. And it’s a good one, when you can do an almost one-to-one preview of your site for that particular page, it opens up so much or it takes away so much worry. It’s really a better life there. Tammie Lister: Know what you’re getting rather than guessing what you’re getting. Birgit Pauli-Haack: And test this, please test this so much. Tammie Lister: Yeah. And again, that’s the part of this. A lot of these things, they’re going in and they’ve been tested by the people that are creating them and they’re amazing humans, but they are not the people that are going to be poking it. It’s now up to people that are listening to this, the people that are going to be testing, who are the people that should be poking it and using it. And I think that is exactly what this is about. Birgit Pauli-Haack: Absolutely, absolutely. And what is now coming back to the site editor is editing templates as well as content. At the beginning of when the site editor was introduced, it was already there, but people got confused. Am I editing a page? Or they were not confused. They didn’t have that concept of a template part like this is just the template that drives all the pages and they made changes, and then were surprised that the changes were duplicated on all the pages. So it was taken out of the editor, and now it comes back with some guidance for the content creator of, “Okay, you can edit that now and when you’re in the template, you get all this whole title kind of thing.” It names the things that are in there. And when you’re on a page, it gives you the page title exactly how you put it in and then you can edit it. But when you go into the places where the template is, it tells you this is a template piece, do you want to edit now? And then gets you out of the editing mode into a template editing mode. And I think that the guardrails there really help with the mental image as well. This is a template, I don’t want to screw that up. I just want this on my page. I want that content done. And you can do it in the site editor. Do you have to go back to the WP admin? Once in a while when you create pages, yes, yeah. But sometimes you want to edit things and you want to see it with… that’s the good part in this section now when you have the edit the page content as well as the template, is you see the page and it’s all in its context. How will it show up on the site? There is no, “Oh, okay. There is something on the sidebar that’s interfering with my page.” And it’s the same thing that we talked about before where as long as you see the full context of your page, all the worry goes away. Tammie Lister: I love what you said as well about having something in and then taking it away. I think that’s really, really important because sometimes when something’s completely new, it doesn’t work because it’s new, it’s not because it’s a bad idea and this is showing, it just needed to be delivered in a certain way. And I think not everything, but quite a few things that have been added a little bit recently are that. They are re-adding a slightly different variation once we’ve got things together. So sometimes you’ve got to find the combination of the puzzle to put these pieces in or the order to put them in. And this is exactly one of those, it needed to come in a certain order. Birgit Pauli-Haack: Yeah. And I had some interesting conversations at WordCamp Europe. I had a lot of conversations at WordCamp Europe, but some of them were really interesting because I think if you’re not a developer, it’s really hard to understand that you have a vision for what people want to do. But unless you start programming and putting it in, you don’t know yet how it’s going, how it’s going to work. So let’s put it with the features in and then see what other people think about it and then reiterate on it. Tammie Lister: It’s part of the freedom of creating in the open and part of what we’ve learned with this whole project is by creating in a plugin, we get to experiment. I want to use the word play because experiment sometimes feels a little bit harsh, it feels serious, but we get to play and see if this goes here, what did someone feel about it? This goes here. Testing things was really, really hard to do in core and it has been really, really hard. But by having it in this and been able to backtrack quicker, and that has been something that has happened time and time again of, “Oops, nope, let’s try this.” Or, “Okay, well this idea didn’t work this time.” We’ve still got it in the code base. It’s just back now. We haven’t completely lost it. In core, ideas go and get lost because it’s a big space, sadly. So having that flexibility, I think we are doing it a lot more as a project and having that healthier macro experimentation. But it’s seeing those mature ideas come. I love seeing things that was talked about, like you said footnotes, but things that were said years and years ago and it’s like, “Yay, they finally shipped.” Birgit Pauli-Haack: Yeah. And it’s not because they couldn’t ship it earlier. It’s also you didn’t know yet how other pieces that needed to fit. Tammie Lister: It’s like baking a cake. It needs to be the right time and the right ingredients need to be available, and the right people to taste the cake. I don’t know, that metaphor went really weird, but right? Birgit Pauli-Haack: Well, only chocolate lovers love chocolate cake, right? Tammie Lister: Yeah. And sometimes you are not delivering chocolate cake, you are delivering a Victorian sponge and to the wrong crowd. I don’t know. Birgit Pauli-Haack: Those metaphors are really… Tammie Lister: It’s not working. Backtrack, what’s the next thing? Birgit Pauli-Haack: Let’s try it again. We all have experiences, but it’s not in WordPress. So creating something really, really new in WordPress with a lot of backwards compatibility promises, it’s really hard. Tammie Lister: I always describe it as the difference between moving a little rowing boat to moving an ocean liner. One of them big Disney cruises or these giant things and then moving a little rowing boat. It is really easy, right? Birgit Pauli-Haack: Yeah. Tammie Lister: It’s not the same. Birgit Pauli-Haack: Yeah, yeah. But this editing piece, I think it’s really so much better now and I think it meets the vision now. So what’s also in the site editor bar is some template details. You might have already seen that, but now it also respects the settings and there is some language going on as well. Some language changes. You see the home template details, but that only tells you, okay, how many blog posts are on it? So it’s the blog home and not only just the homepage. So if you switch it to a static page, you will see that in the pages and not in the template pages. But it’s really good to have those template details in the site editor on the sidebar, it gives you a little bit more context. Tammie Lister: With components, I guess one of them to call out is the button has a size prop, which is a small little thing, but it’s maturity of the burn block, how many sites have burned every one of them? And having something like that is really big. It’s going back to one of my favorite topics of design systems. If we are building off core as a basis, you need to have these foundational things as part of it. So I’m really excited to see. Anytime I see that or any of the blocks getting different attributes, I am giddy with excitement about all those things. Basically because it means I can then use them. Birgit Pauli-Haack: You can use them, you can create styles with them. You can have different variations on the buttons and you don’t have to create a new block for the buttons. Tammie Lister: Yes. Birgit Pauli-Haack: Yeah. Another block that got some nice features, an additional feature in there is the list block. It now has a different numbering type for the ordered list. So you could have alphabetical numbering or numbered numbering or Roman lit numbering and then capitals and then small cases. So now you have quite some options in there. I really like that. It’s catching up with other documentation or writing tools where you have that. But yeah, it’s good to have it in there. Tammie Lister: And image block has as aspect ratio control. For some reason, I wanted to say radio control. That was exciting. I think that’s a whole different thing. Birgit Pauli-Haack: Multimedia, an image has radio. Tammie Lister: Which again is maturity, right? You mentioned parity with tools. It is, right? We need to have the best of these tools so that people use them natively. So that’s really what a lot of this is maturity of these tools, I think. Birgit Pauli-Haack: Yeah. And that was particularly important because you want your patterns when you switch out the images, you have them in a certain aspect ratio and when you switch them out and somebody puts in another image, you want it in the same aspect ratio and not blow up the whole pattern. Tammie Lister: Could ruin a party, that really can. Birgit Pauli-Haack: Yeah. I’m scrolling past it, but there is just stop to say that the interactivity API will not be in 6.3. It has been merged for the Gutenberg plugin, but it will only be available… they’re aiming for 6.4, which is not so far away, actually. September is the next beta. So it’s really going forward. There were some questions in the community about the interactivity API. A lot of people are very excited about it. Tammie Lister: We’re going to have some really nice toys for Christmas. Birgit Pauli-Haack: And November 8th is I think the release of 6.4. So let’s get those toys wrapped up for Christmas. Tammie Lister: That’s actually going to be some really interesting testing, I think. Some difference in testing because yes, we’ve done, but how you test some of that stuff is going to be a little bit different, I think. Birgit Pauli-Haack: Yeah. And we need a lot more examples. Tammie Lister: That’s where I’m going. How do you push some of that stuff? Birgit Pauli-Haack: Yeah. And definitely there’s some documentation. I think they started with the documentation now. There were quite a few insights already in the make blog on core. I think two of them, and I can certainly add them to the show notes. So people who are all interested in that and want to help with the rollout, definitely can get a headstart on it, but not in 6.3. Tammie Lister: The next one, I’m going past so much, this is such a long list. It’s amazing. It is in the design tool section and that’s a sticky position. That’s not a phrase. Try re-enabling non-root sticky position. So actually, I think any improvements to things like this is really nice. The fact that we have this shows maturity of design tools. So I think that’s part of calling this out. Design tools as a whole are a concept that is still relatively new to us, but design tools means again, that people are going to build using it. And so I’m really excited anytime that any of our refinement happens to any of our design tools. Birgit Pauli-Haack: And I think in 6.2, the sticky position was already introduced for the header and the footer, but it was not for the sidebar because somehow it was really, really hard. Tammie Lister: Sticky is hard. Sticky is hard to stick. Birgit Pauli-Haack: You never get it to stick. And it needed to be a root wrapper or root block to make it sticky. You couldn’t do it in a column block where you have a sidebar and make that sticky. Tammie Lister: Because CSS. Birgit Pauli-Haack: Because of CSS, yes. Yeah. So there is another attempt to make this work and needs definitely testing. Tammie Lister: Yes, I was about to say that if anything needs testing, any time you see something listed in design tools, I would point anyone who is building themes or building anything to please test around those things because these are what really you will be building with. Having native sticky positions is much better than having to call on libraries or add things. And again, it means that people who want to build and create in the editor themselves have that capability to create some incredible, powerful, beautiful designs without having lack of access to them. It all sets us up to what amazing things could be done with the default themes, and that’s super exciting, what Christmas is going to bring there with all these tools. Birgit Pauli-Haack: So the next one is actually for media and we need to set this up a bit. So when you copy paste something from Google or from another website and there’s images in there, when you paste them into your canvas, the image will always go back to the original. So when the original site goes away, especially when you migrate from one domain to the other, the image goes away. And now there was a little button on every image where you could say and if it was allowed from the source site, that you could add that image to your library with a button. But of course when you have 15 images, it’s a little harder to do that. So now in the pre-publish screen, there is a section that suggests that you upload the external images and gives you a button and you can do it all at once. You also can click on the images and see how they show up in the post or in the page. So I think that’s a great addition to… Tammie Lister: Just what people expect. Again, and I do not belittle it by saying that. It’s more just, it just raises it up. It’s what people expect, it’s what people want. So it’s amazing. Birgit Pauli-Haack: It really raises the quality of the tools that you use, that it actually helps you also with the little things. Images are important. Tammie Lister: Quality of life. Really, the release is quality of life and completion, which is a beautiful summer thing. Birgit Pauli-Haack: And refinement. Tammie Lister: Yeah. So I think we’re going to talk maybe a little bit later about the command section, but we’re into commands. Birgit Pauli-Haack: We’re good? Tammie Lister: Going down the list, there’s two things about the commands and that is add commands to templates, template parts and styles, and to related commands as well. I don’t know if you want to talk about commands right now or later? Birgit Pauli-Haack: We could. So we have a name now for it. Tammie Lister: We do. Birgit Pauli-Haack: In the development, it was always called the command center, but now it’s command palette and it tries to convey that’s the tool when you hit control K in the site editor, it gives you quick access to various commands, context-sensitive. And so you can say go to library or go to templates or go to template parts or delete template parts. All this you can do, and it’s also extensible. So you can create commands for your plugins, you can create commands for your themes as well. But the API is very, very new. So there are commands and with this release, there are commands with template, template parts, styles, how to manage the custom patterns, which custom patterns are the former reusable blocks. Sync patterns. So now you can say to your command palette, manage patterns or you also get UI commands for your post editor. So where you can say, add new post or something like that. So it’s not the center of it because it’s not a mission control palette or something like that. Or dashboard, it’s just you have a thought that you wanted… Tammie Lister: It’s your friendly helper there and there. And I think what these are doing is giving you examples. As you said, this is the start and it’s new. So by having these there, and this is just to start again, I think it’s worth of saying these are an example that someone could look at and be like, “Oh, that’s how you write one,” as well. So I am super curious to do that myself and be like, “Oh, okay, that’s how you write one. Okay.” And I am really excited to see what people create with this. Now we have decided the name, I was going to call it Bob, but it didn’t catch on. Birgit Pauli-Haack: I always call him Fred. Tammie Lister: I call everyone Bob. No idea. Everyone picks a name that they call things repetitively, I think. And now that it has a name, which is amazing. And I think one of the good things is its translatable. And I think that was key in all of it. Personally, as long as it’s translatable, as long as we agree to something, we get it in, things can change. But let’s get it in and iterate. So these are great examples to then copy, rehash, and learn from. So I think 6.4, we’ll probably see more. And then I imagine there’s going to be a flowy of plugins, some nice little iterations and people exploring what it means to have these things as well. So it’s going to be very exciting to see what people create. Birgit Pauli-Haack: Yeah, I’m really happy about that. I would’ve never thought that my website tool would have these quick commands that I can just call up and then do stuff. Tammie Lister: So the way that I think of it is a combination of… Because initially, I was Alfred was where my mind went because it’s searchy, I think of it now like Alfred. And if this, then that, and those two things combined is where I go because it is that, but it’s also workflow. So it’s that but in WordPress for me, and I am very excited about extending that and then where people take it, because people always take it in a way that you would never expect it to go. So I think the next year or so, we’re going to see some really exciting things come from that. Birgit Pauli-Haack: Yeah, I totally agree with that. Tammie Lister: New toys. Birgit Pauli-Haack: New toys for everybody when the biggest toy is probably creating those commands and find, “Yeah, oh I can do this. It’s not that hard.” Tammie Lister: And then even vigilant spaces to be able to create those commands ourselves. That becoming easier and easier I think is something that will happen over time as well. Birgit Pauli-Haack: Yeah, I totally get it. I want to get into programming so much and lock myself away for two weeks and do all this. Tammie Lister: You don’t have to lock yourself away for it, but that’s all right. Birgit Pauli-Haack: Yeah. So I’m scrolling and scrolling and scrolling. I don’t see anything anymore. Tammie Lister: So much. And I think that’s the thing. If we are going through the bug fixes and the enhancements and there’s just so much, I like the repetitive word flaky because when I see the fix flaky, that means that all the things which flaky is a bug report for, it kind of works and it kind of didn’t. I love that we’re down to that end of polishing, is my reflection on that. So I think that is really, really exciting that there’s so much polishing here. Birgit Pauli-Haack: Yeah, and I think that was actually the outlook for 6.3, that most of the features get in and then we’re almost already… Tammie Lister: This is a giant section of those, which I love. Birgit Pauli-Haack: Are we done? I think we’re done. Oh yeah. Tammie Lister: Yeah. Birgit Pauli-Haack: There are a lot of documentation fixes. Code quality fixes, code quality in block library, code quality in site editor. No, this is cool. Yes. Tooling. Yeah, the whole testing thing was kind of, whoa. Tammie Lister: Yeah. Birgit Pauli-Haack: That’s what you were talking about. Tammie Lister: And I think that’s the thing that’s there. It’s probably testing coming in for command as well, but it’s all maturity of that. As I’m scrolling down, I’m seeing improving, improving, improving, improving. Birgit Pauli-Haack: Yeah. No, I think we made it. Yay. Tammie Lister: Yay. Birgit Pauli-Haack: Yeah. So we want to bring it back to the WordPress 6.3 beta and talk a little bit about what this means plus tickets for 6.3. Tammie Lister: I think one of the big things to think about is yes, there are things in now, but things that are in are going to have to respond to feedback. So whilst you might think, “Oh, that burden is perfectly placed,” I am really paraphrasing here, “That burden might not be perfectly placed.” So during beaters, you might see that burden moves because that burden needs to be in a better place. And there are a couple of tickets out there at the moment, which one of them particularly has things could be done in a better way. That’s where I’m going with this. So we are going to see that. We are going to see, “Oh dear, this breaks this under this circumstance when we actually tested it under this load or we tested it under this situation.” Because you can test under all the situations you think, but you don’t have that until you are real world testing or you’re testing. And as the betas get towards the higher numbers, we’re on two now. So we’re probably going to go at least four I would say, I don’t know. Birgit Pauli-Haack: I agree, I agree. Tammie Lister: I want to be optimistic. But realism kicks in here a little bit. You’re going to see fixes. So people need to bug report. People need to test or poke it, prod it, and use it. If you find something, see something, report something is the biggest thing because if you see something at release candidate, it’s a little bit late. It’s like shouting after the sheep have left the field. But if you say something now, it can be fixed. So if something doesn’t work with the plugin that is the only reason your client’s site works, now’s the reason to say basically. Birgit Pauli-Haack: Yeah, definitely. And there will be. So I also wanted to caution some of the more eager WordPress news people or that want to grab screenshots and that kind of thing. There might be changes there. Tammie Lister: Going back to my button moving. Birgit Pauli-Haack: For instance, one change is from 6.0 to beta or to 16.2, so plugin releases 6.0 to 6.2, which will probably have some of the things that will get into 6.3 WordPress. But there was one menu item in the site editor on the bottom that was called library. And that has been renamed to patterns because that’s what’s in there. It’s the reusable block that are patterns now, template parts that are patterns now, and your custom patterns that are patterns now. And one was thinking about the library part for a long time because also there will be a fonts library, something like that. But then there were quite a few smart people who said, “Well, if I’m looking for fonts, I won’t go to library. I go to my styles and that’s a separate place.” So while we were using it, it was rethought what would make it a better idea or better metaphor for that. And pattern is something that’s WordPress branded and that a lot of people are really responding to. So library was not, it removes cognitive load when you have to think about, “I need to think of library.” When you see patterns, that’s where you want to go. So that’s just one example. There might be others. So when you do a screenshot for your video, make sure you have the latest beta or the latest… Tammie Lister: Really, screenshots is release candidate as much as it feels late, it’s not. There’s several weeks and that’s when you’ll find a lot of documentation takes it as well. I’ll working on the about page and we’re going to be doing the graphics around there as much as possible. But honestly, the final-final 01 PSD graphics… I don’t have to deal with PSDs, that’s when you take them because things rightly about translation. This language though, I think so many of these language refinements happening, whether you agree with it or not, because language is so subjective and everyone has feelings about Bob or Fred, what things should be called, is a sign of maturity of the product, is that we’re working our own language system and we’re saying these things are called this because it makes sense in our ecosystem. So I welcome that we’re finally clarifying some language and not just confusing everybody because it’s always been very confusing. We’re finally settling on some terms and we are then documenting what they are called because one of the problems we’ve always done is called something and then not written it down. So actually doing that is really helpful. Birgit Pauli-Haack: Yeah. Release candidate is scheduled for the 27th of July, so it’s another four weeks to go. So caution. Tammie Lister: So you got to let the dust settle, you got to let stuff go. If everything is amazing and unicorns walk and everything, then nothing will change, but something’s going to change because humans in software. Birgit Pauli-Haack: Yeah, it’s going to change. And computers, right? Computers are involved, all bets are off, right? Tammie Lister: Yeah. And that’s okay, right? Birgit Pauli-Haack: Yeah. Tammie Lister: That’s totally okay. Just if you’re going on holiday, maybe have a friend do your screenshot for your blog post. Birgit Pauli-Haack: All right. So before we all come to an end, just a reminder, the two live Q&As on July 6th and July 21st. Hit the registration button so we can all see you also on the live show and with some great demos. Before we end this show, do you have anything that you want to… How can people get in touch with you, Tammie? Tammie Lister: I’m karma Toast on all the things and I’m still around core, I’m around everywhere and I would love to speak to people. I will be at WordCamp U.S. as well if someone else is going. So I’d love to say hi, but reaching out, I’m always welcome. Birgit Pauli-Haack: Awesome, awesome. Thank you so much for being on the show. And as always, dear listeners, the show notes will be published on gutenbergtimes.com/podcast. This is episode 85, and if you have questions or suggestions or news you want us to cover, send them to changelog@gutenbergtimes.com. That’s changelog@gutenbergtimes.com. So thank you so much Tammie. It has been a great pleasure geeking out with you over Gutenberg. Tammie Lister: It’s been a pleasure. It’s always great talking to you. Thank you so much for having me. Birgit Pauli-Haack: Thank you so much, and you all have a good weekend and a good week and I’ll see you all or hear you all in the next two weeks. Take care, bye-bye. A new era has begun for WordPress.org’s Plugin Review Team. Mika Epstein, who has served for the past decade, is stepping down, but not before launching a new crew of volunteers. The team is responsible for approving newly submitted plugins, maintaining the Plugin Reviewer Handbook, as well as investigating any reported security issues and guideline violations. Historically, the Plugin Review team has had very little turnover, but a new crop of six sponsored volunteers will be contributing an estimated 50+ hours per week. The new members include David Pérez, Evan Herman, Francisco Torres, Luke Carbis, Marta Torre, and Paco Marchante. Their efforts are already in demand as they work to tackle a large backlog of plugins. “Given the nature of the work the team does, joining this team is a little different than some of the others: each new member will go through a vetting process by current team members before being selected,” Epstein said. “Some of the things the team is looking for are: a solid track record as a plugin developer; the ability to communicate clearly, kindly and constructively – both with other developers and users; interest in improving tools and processes; and excellent collaborative and conflict-management skills.” Epstein is encouraging more volunteers to apply, if they have at least five hours per week to devote to the team, as they could still use more help. Prospective team members can submit an application, which will be evaluated by current team members. Applicants will be required to send examples of plugins they have coded to demonstrate their experience, provide references, and detail some of their contributions to the project. Release season is upon us as we approach WordPress 6.3’s August 8th release. Your help is needed testing the latest changes. β WordPress 6.3 Beta 2 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. You — and your whole team can Join Post Status too! Build your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. This article was published at Post Status — the community for WordPress professionals. A way to escape chronic pain and give a sense of independence, is what using WordPress means for Italian-American Allison Dye. Now as a project manager and social media content manager living in North Carolina, USA, she uses the software in her work and in disability-advocacy. The People of WordPress series shares inspiring stories of how people’s lives can change for the better through WordPress and its global community of contributors. Allison was first introduced to WordPress when she was 13 years old. Her parents gave her own WordPress website to use, play, test, and try whatever she wanted with it. Her health issues had started when she was eight years old, and being able to express who she was and learn new skills provided an escape she needed. Allison said: “While the technical aspects of my new WordPress website intrigued me, I was more interested in the space it made for me to write. All throughout my childhood I had struggled with chronic pain, fatigue, and other unexplained symptoms. Having a private world I could call my own, I was able to write my story.” “There is something truly amazing about having a place to tell your story.” Her family faced many doctors, nurse, specialists and hospital visits, but could not get an answer to the difficulties faced by Allison. She said: “I felt like my life and world were out of control. But logging onto my little website and typing away on the computer keys gave me a sense of control. I couldn’t always do things that other kids had the energy to do. But I could get lost in writing for hours. I couldn’t control my life story, but I could write about it.” She felt it was like writing letters to her future self and would act as a reminder of how strong she had become. Even now when Allison writes on her website, she feels it is writing letters to her past self, expressing reassurance and pride. The practice of writing online continues to help her reflect on how she coped and made it through the difficulties. Allison hoped her early experiences with hospitals and being unwell was just part of being a child, and that in adulthood she would be healthy. She longed for this time. Growing up did not bring her this dream of a healthier life and an end to chronic pain. In fact, her condition worsened as she went through her teens and at 18 she finally received a diagnosis of Multiple Sclerosis. This changed what had been conventional job choices, as she was not able to handle a 9 to 5 work schedule. She could not drive herself to work on some days and relied on her mother to help with transport. She knew that she would have to find another way to work and she was determined to find it. She began writing music and book reviews online, and then moved onto writing blog posts. As they were published she started to receive payment and a sense of power over her life. She said: “WordPress felt familiar, typing on the computer keys felt comfortable, and sharing my words with the world felt surreal.” Allison’s sense of ownership of the software became part of her strength. “I think I believed WordPress was mine somehow. I was learning that WordPress is something that belongs to everyone in some way. And I loved it.” The confidence using the platform gave Allison led her to find more about what it could do and meet other people who used it. She said: “The thing I love about WordPress is that it’s not just for developers or bloggers or SEO experts. I began to meet more people in the community and was delighted to find people like me, who didn’t know the technical stuff, but were a part of WordPress.” This global community orbiting around the software gave her an opportunity to meet social media managers, designers, and people from many different areas. She found that ‘there was a place for everyone’. The guiding strength and fascination Allison found and still finds today is in that community. Allison said: “The community felt as important as the rest of everything that makes WordPress what it is. It felt like it was about people and relationships as well as codes and databases.” In 2020, she was hired by a WordPress company. She said: “I like being a part of a WordPress company, and I love that I contribute to a team that helps people with their websites. I understand the importance of having a space that’s yours. Whether it’s a business or personal site, having a website gives you the power of telling your own story.” WordPress gave Allison a freedom and an independence. She did not have to work a 9 to 5 job, rely on others to drive her on bad days with her MS, nor worry about days when she wanted to stay in her sweatshirts rather than go into an office to work. She said: “I have a 100% remote job which I can do despite the plot twists in my story, thanks to WordPress and the people in it.” WordPress took Allison into the world of project management for a small agency, and this experience was to help guide her path, skills and confidence into the future. She went on to work in content management in WordPress, building pages for awareness campaigns for non profit organizations and small businesses as a contractor. She helps people update their websites, add and edit content, perform basic updates and help them to learn how to use their sites. “I tell all my clients to use WordPress because there is really no other solution that can scale as easily for growing organizations and small businesses. I love how WordPress allows them to tell their stories, share their passion, and have a place to call their own on the internet.” As a fluent English and Italian speaker, Allison is able to support clients in different countries from where she lives. “I love that with WordPress I’m able to support clients remotely. This is thanks to all of the many WordPress contributors, developers, project managers, content writers, and many, many volunteers that work tirelessly to enable people around the world to use WordPress.” Allison also became a certified as an English As A Second Language (ESL) teacher. “My affinity for words and languages allows me to teach passionately and creatively. I’m Italian-American and am fluent in English and Italian. Teaching English allows me to share my passion for communication with others.” Allison attributes mentors and supporters in the WordPress community for helping her appreciate she really is part of it. Allison recalled: “It felt unreal. I wasn’t a dev, I don’t know how to code, and yet I got to be a part of it all? I felt like I was a fake. But Kimberly continues to remind me that I’m real, I get to be here, I get to stay, I have a place.” She was later encouraged to contribute by a WordPress community member to the Big Orange Heart, which aims to support and promote positive well-being and mental health within remote working communities. She said she felt ‘honored typing my words, pieces of my story, and sharing them with a community of people’. She also joined the WordCamp US 2021 online organizing team. Allison enjoys the fact that in the WordPress community, ‘everyone here is constantly working to be better and do better’. Allison was later diagnosed with two additional neurological conditions: Functional Neurological Disorder and Migraine. She said: “If it were not for WordPress I would really be unable to work. But WordPress and its community continue to be a part of my life and I am grateful to everyone who’s helped me along my way. I don’t know where I would even be without it.” She strives to raise awareness of dynamic disabilities and invisible illnesses like her own through podcasts and social media. She feels that her WordPress friends have helped her both in her professional life and in her wish to be an advocate for others with disabilities too. “I hope that it will remind anyone reading this that WordPress is a space for everyone. Healthy or not, developer or not, blogger or not — WordPress belongs to you too.” Help share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series. Thanks to Allie Dye (@allisondye) for sharing about her adventures in WordPress. Props to Abha Thakor (@webcommsat) and the late Surendra Thakor (@sthakor) for interviews and writing the feature, Meher Bala (@meher) for work on images, and to Meher, Maja Loncan (@mloncar) and Chloe Bringmann (@cbringmann) for reviews. The People of WordPress series thanks Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support. This People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress The WP Feature Notifications project has launched a community survey to get feedback on the current system of notices in the WordPress admin. The project aims to create a better way to manage and deliver notifications in the admin, and the survey is intended to further refine this work. A few months ago, the project released version 0.2.0 of the feature plugin in which contributors implemented a more robust JavaScript-based system for standardizing how notifications appear in the admin. This is a proof of concept plugin that uses demo data only. They are working towards an MVP for 0.3.0, which will remove the demo content and provide a functional notification system. Contributors have also put together an updated design based on the idea of working within WordPress’ existing design system. “The team has recently made some solid progress on things like database storage and REST API endpoints,” WordPress core contributor Joe Bailey-Roberts said. “However this is slightly paused for now so we can revise things if necessary, based on the survey results. We also have an updated design for the admin notices UI that we’ll shortly be showcasing, which came out of the WCEU Contributor Day.” Anyone who uses WordPress is welcome to take the survey – it’s for developers and users alike. It takes just a few minutes and may help shape the direction of the WP Feature Notifications project in the future. The first-ever Finnish WordCamp gathered a few hundred fellow WordPress enthusiasts to Tampere back in 2015. This September, on 14.-15., our community will return to the city where everything started. Content has been planned with all skill levels, employment types and interests in mind. We do not discriminate, and WordPress users, developers, designers, people working in agencies or as a freelancer and other enthusiasts are all welcome, regardless of the experience level. We are more than thrilled about the upcoming lineup of talks and speakers. The best and most exciting part is that many of the topics do come outside of the WordPress world! WordCamp Finland will truly have educational, insightful and thought-provoking talks for everyone. Here’s a sneak peak of some of the topics: WordCamp Finland 2023 sessions will take place in Tampere on Friday 15. September. Most of the sessions will be held in English, although there are a handful of sessions held in Finnish as well. The day before, on Thursday 14. September, a contributing evening will take place starting at 16:00. The contributing evening will feature workshops where you can contribute and learn about various WordPress-related topics in a hands-on setting. No coding skills required! During the whole event, there will also be ample time for networking and meeting other WordPress enthusiasts. Getting to meet and learn from other WordPress users face-to-face is one of the main reasons people attend WordCamps. In addition to learning from each other, attendees often make new friends and find employees/employers from the WordCamp crowd. Secure your tickets now and ensure you’ll get to experience all of the insightful talks and activities with a welcoming community! The full list of speakers, session descriptions and schedule will be published in early August, so make sure to follow us on Twitter, Facebook and Linkedin to get the latest updates. Naturally the WordPress Finland Slack has #events-wcfi channel and discussion is ongoing on WPWoofi Facebook group. Gutenberg 16.1 was released this week, debuting of the Pattern Library, which coincides with reusable blocks getting renamed to synced patterns. Users can now create and manage their own patterns that will also show up in the block inserter. Custom patterns are saved to the new Library alongside custom template parts. This release also adds a new Distraction Free mode to the Site Editor, which removes all controls and menus, functioning in a similar way to the mode added to the content editor in October 2022. The mode can be accessed under the more menu of the Site Editor. Automattic-sponsored engineer Andrei Draganescu submitted the PR for the feature and cited three reasons why the Site Editor could benefit from a Distraction Free mode: Draganescu published a video of the Distraction Free mode working in concert with the new Command Palette: Another new feature in this release is automated footnotes.* Users can add them by highlighting the text and selecting Footnote from the formatting menu. This will automatically insert the note and create a Footnote block at the bottom of the content. (This block can be moved.) Footnotes can be added inside paragraph, heading, and list blocks, and are saved as post meta. The Footnote block doesn’t seem to be accessible in the block inserter. It is automatically created and inserted with the first footnote. A few other notable features in this release include the following: Gutenberg 16.1 is included in the upcoming WordPress 6.3 release, but if you want to take advantage of these features before August, you will need to be using the plugin or test 6.3 Beta 2. Check out the release post for the full changelog that includes all the latest enhancements, bug fixes, and performance and accessibility improvements. WPScan is reporting a hacking campaign actively exploiting an unpatched vulnerability in the Ultimate Member plugin, which allows unauthenticated attackers to create new user accounts with administrative privileges and take over the site. The vulnerability has been assigned a CVSSv3.1 (Common Vulnerability Scoring System) score of 9.8 (Critical). Automattic’s WP.cloud and Pressable.com hosting platforms picked up on a trend in compromised sites where each had rogue new administrators popping up. After further investigation they found a discussion on the WordPress.org support forums about a potential Privilege Escalation vulnerability in the plugin, as well as indications that it was already being actively exploited. Ultimate Member, which is active on more than 200,000 WordPress sites, patched the plugin, but WPScan reports that it wasn’t sufficient. “In response to the vulnerability report, the creators of the plugin promptly released a new version, 2.6.4, intending to fix the problem,” WPScan security researcher Marc Montpas said. “However, upon investigating this update, we found numerous methods to circumvent the proposed patch, implying the issue is still fully exploitable. “Adding to the urgency of the situation, a look at our monitoring systems also confirmed attacks using this vulnerability were indeed happening in the wild.” WPScan has identified more than a dozen IP addresses from which exploits are originating, common usernames for malicious accounts, and other indicators of compromise, such as malicious plugins, themes, and code. Check the security advisory if you believe you have been compromised. Version 2.6.6 is the latest release from the Ultimate Member plugin but it is still believed to be vulnerable. WPScan recommends users disable the plugin until it has been adequately patched. This year’s Kim Parsell Memorial Scholarship recipient is Yumi Nishioka (mimi). mimi is a passionate WordPress contributor who embodies the values that Kim would have appreciated. mimi is a Web/UI Designer and Developer based in Tokyo, and has been a WordPress contributor since 2018. She was lead organizer of WordCamp Tokyo 2019. That year she also began hosting a personal study group on the Gutenberg Project, which meets twice a month. Then in 2021, she started co-organizing monthly small study sessions about Design and WordPress. While there have been numerous contributions I’m proud of, one that stands out is my commitment to the core code. Although it was a small code change, the experience of being actively involved in the open-source software that I use daily was incredibly rewarding. The WordPress Foundation created this memorial scholarship in 2015, to honor the memory of longtime WordPress contributor Kim Parsell and ensure that Kim’s values would continue to be infused into the WordPress community. This scholarship provides travel to WordCamp US for a woman who contributes to the WordPress open source project, and who would not otherwise be able to attend WordCamp US. More information on the scholarship, including past recipients, is available here. In this episode, nothing goes untouched. A lot of great reflection on WordCamp EU 2023 in Athens. >> The post Reflecting Back on WordCamp Europe 2023 appeared first on Do the Woo - a WooCommerce Builder Community . WordPress 6.3 hit a major milestone today with the release of Beta 2. The release leads opted to skip Beta 1, which was delayed yesterday after some technical issues with packaging the release, and have moved straight on to Beta 2. As WordPress 6.3 is set to be the last major release of the Gutenberg project’s Phase 2 focus on customization, it ties up many loose ends related to the Site Editor and usability in general. It rolls in the ten most recent releases of the Gutenberg plugin – versions 15.2 through 16.1. Major interface enhancements in this release, as outlined by the comprehensive 6.3 testing guide, include the following: Patterns are also getting a big boost in this release, as reusable blocks have been renamed to “synced patterns.” Pattern creation is now available to users and a new pattern library will be located inside the editor for saving and managing both synced and unsynced patterns. Theme authors now have the capability to register custom patterns to templates, so they appear in the start modal to speed up page building. WordPress 6.3 will introduce three new blocks, including details, time-to-read, and footnotes, along with many improvements to existing blocks. This release comes with significant performance updates, most notably the addition of defer and async support to the WP Scripts API and fetchpriority support for images. Support for PHP versions 8.0+ has been improved, along with block template resolution, image lazy loading, and the emoji loader. In the rare event that the manual update of a theme or plugin fails, auto-rollback is available as of WordPress 6.3. Beta 2 testers are encouraged to file bug reports on WordPress Trac. During beta testing until the last RC, the WordPress project will also be doubling its monetary reward for any new, unreleased security issues that are uncovered. The vulnerabilities must be found in new code in order to qualify for the doubled reward. Check out the Beta 2 release post for more information on new features, accessibility improvements, and instructions on how to test. WordPress 6.3 is scheduled for release on August 8, 2023. WordCamp Asia has announced its dates for 2024. The flagship event is now officially scheduled for March 7-9, in Taipei, Taiwan. Organizers have secured the Taipei International Convention Center (TICC) venue to host the event, which is located in the business district not far from Taipei 101, formerly known as the Taipei World Financial Center, a skyscraper that is the city’s most visible landmark. TICC has a capacity of more than 3,000 people. “The local community is massive and I’ve been told that WordCamp Taiwan (this October) alone would boast of at least 500 attendees,” organizer John Ang said after visiting Taipei with his team to sign the venue. “While we were on the same trip, we were lucky to be able to celebrate the 20th Anniversary of WordPress with the Taiwanese community. “There’s also active work bringing in government support and other open source communities across the region (e.g. Hong Kong) to WordCamp Asia next year.” WordCamp Asia attendees can expect 3-5 tracks of sessions featuring diverse presentations across a range of topics for beginners and seasoned WordPress professionals alike. The venue also offers ample common areas for networking. More details on the event and calls for speakers and sponsors should be coming soon. Those who are hopeful to attend can subscribe to updates on the event’s website or follow @WordCampAsia on Twitter. WordPress 6.3 Beta 2 is ready for download and testing. This is the first release of the 6.3 cycle, as there was no Beta 1 due to technical issues with packaging the release. Rather than further delaying a beta release, the release squad has decided to package and ship Beta 2. This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, the release squad recommends you evaluate Beta 2 on a test server and site. WordPress 6.3 demonstrates incredible progress toward achieving the goals outlined in the WordPress roadmap and is the final major release of Phase 2. Phase 2 has focused mainly on the Site Editor, enabling site creators to build websites, design compelling layouts, and manage content without toggling between multiple configuration areas or editing code. Learn more about Gutenberg updates debuting since WordPress 6.2 by reviewing prior editions of What’s New in Gutenberg posts for 15.2, 15.3, 15.4, 15.5, 15.6, 15.7, 15.8, 15.9, 16.0, and 16.1. WordPress is the result of contributions by users, developers, and extenders across the globe. As this community seeks new features, the platform will continue to evolve, including the site editing features and beyond. Get an overview of the 6.3 release cycle, and check the Make WordPress Core blog for 6.3-related posts in the coming weeks for further details. This latest WordPress release includes many updates spanning all platform areas, emphasizing the editing experience and polishing usability. This release contains more than 500 new features and enhancements and 400+ bug fixes. Following the incredible performance improvements introduced in 6.2, the release includes more than 170 performance-related updates, including adding defer and async support to the WP Scripts API and fetchpriority support for images. Optimizations were made to block template resolution, image lazy-loading, and the emoji loader, all of which benefit LCP performance. Support for PHP versions 8.0, 8.1, and 8.2 has been improved. The Site Editor expands to include navigating and editing pages, styles, templates, and content. The unified site editing experience will include a distraction-free mode, enhanced navigation, and an improved loading experience. Additionally, you can use the Site Editor to preview a block theme and adjust your site before activating the new theme. This release includes style revisions so you can toggle between and preview different saved styles. Rounding out the changes, 6.3 ushers in a new Command Palette, enabling users to context switch and perform actions quickly across different sections of the site editing experience. New blocks for details and footnotes debut in this release, along with updates for better handling of image aspect ratios and improved fallback states. Spacer blocks now include presets, and the cover block gets updates for managing text colors and layout support. Reusable blocks have been renamed to synced patterns. This change reflects the unification of reusable blocks and traditional block patterns (unsynced patterns) within the Editor. A new option allows you to assign patterns to templates, adding the ability to have starter patterns to speed up the creation process. Site creators can now easily create, save, and manage custom synced and unsynced patterns, as well as browse a directory of curated patterns. Additionally, the duotone filter and captions can now be edited in the Styles interface. Some key usability highlights include toolbar updates, updated template descriptions, enhanced list view drag-and-drop, improved padding and margin controls, and a new area for managing patterns (including reusable blocks, now called synced patterns.) Link control receives some updates, rounding out high-level usability enhancements in 6.3. WordPress remains steadfast in making the site-building experience accessible to everyone. 6.3 incorporates over 50 accessibility improvements across the platform. Improved labeling, optimized tab and arrow-key navigation, revised heading hierarchy, and new controls in the admin image editor allow those using screen readers, keyboard navigation, and other assistive technology to navigate more easily. The login form, installation steps, and list tables (for sorting and selection) have all been updated. Additional accessibility tickets are viewable in the WordPress Trac. This release includes auto-rollback for failed manual updates of themes and plugins. Please note that the features in this list may change before the final release. 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, testing new features is too. Review the many new features listed above and focus your testing efforts on those areas in particular. If you encounter an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. You can also check your issue against a list of known bugs. New to testing? This detailed guide is a great place to start if you’ve never tested a beta release. Want to know more about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on the Making WordPress Slack. Between the Beta 2 release and the final release candidate (RC) for each new WordPress version, the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper. You can test WordPress 6.3 Beta 2 in three ways: Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream). Option 2: Direct download the Beta 2 version (zip). Option 3: Use the following WP-CLI command: The current target for the final release is August 8, 2023, which is about six weeks away. Your help testing this version ensures everything in this release is the best. A chapter closes Thank you to the following contributors for collaborating on this post: @DanSoschin, @Meher, @JPantani, @CBringmann, @AudrasJB, @annezazu, @ndiego, @davidbaumwald, @desrosj, @priethor, @flixos90, @wildworks, and @JPantani for authoring the haiku. [00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. 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 how AI and WordPress can work together. If you’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. If you have a topic that you’d like us to feature on the podcast, I’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. So on the podcast today, we have James Dominy. James is a computer scientist with a master’s degree in bioinformatics. He lives in Ireland working at the WP engine Limerick office. This is the second podcast recorded at WordCamp Europe, 2023 in Athens. James gave a talk at the event about the influence of AI on the WordPress community and how it’s going to disrupt so many of the roles which WordPressers currently occupy. We talk about the recent rise of ChatGPT, and the fact that it’s made AI available to almost anyone. In less than 12 months, many of us have gone from never touching AI technologies to using them on a daily basis to speed up some aspect of our work. The discussion moves on to the rate at which AI systems might evolve, and whether or not they’re truly intelligent or just a suite of technologies which masquerade is intelligent. Are they merely good at predicting the next word or phrase in any given sentence? Is there a scenario in which we can expect our machines to stop simply regurgitating texts and images based upon what they’ve consumed; a future in which they can set their own agendas and learn based upon their own goals? This gets into the subject of whether or not AI is in any meaningful way innately intelligent, or just good at making us think that it is, and whether or not the famous Turing test is a worthwhile measure of the abilities of an AI. James’ his background in biochemistry comes in handy as we turn our attention to whether or not there’s something unique about the brains that we all possess. Or if intelligence is merely a matter of the amount of compute power that an AI can consume. It’s more or less certain that given time machines will be more capable than they are now. So when if ever does the intelligence Rubicon get crossed? The current AI systems can be broadly classified as Large Language Models or LLMs for short, and James explains what these are and how they work. How can they create a sentence word by word if they don’t have an understanding of where each sentence is going to end up? James explains that LLMs are a little more complex than just handling one word at a time, always moving backwards and forwards within their predictions to ensure that they’re creating content which makes sense, even if it’s not always factually accurate. We then move on from the conceptual understanding of AI to more concrete ways it can be implemented. What ways can WordPress users implement AI right now? And what innovations might we reasonably expect to be available in the future? Will we be able to get AI to make intelligent decisions about our websites SEO or design, and therefore be able to focus our time on other more pressing matters? It’s a fascinating conversation, whether or not you’ve used AI tools in the past. If you’re interested in finding out more, you can find all the links in the show notes by heading to WPTavern.com forward slash podcast. Where you’ll find all the other episodes as well. And so without further delay, I bring you James Dominy. I am joined on the podcast today by James Dominy. How are you doing James? [00:04:51] James Dominy: I’m well, thanks. Hi Nathan. How are you doing? [00:04:53] Nathan Wrigley: Yeah, good, thanks. We’re at WordCamp Europe. We’re upstairs somewhere. I’m not entirely sure where we are in all honesty. The principle idea of today’s conversation with James is he’s done a presentation at WordCamp Europe all about AI. Now, I literally can’t think of a topic which is getting more interest at the moment. It seems the general press is talking about AI all the time. [00:05:17] James Dominy: Yeah. [00:05:17] Nathan Wrigley: It’s consuming absolutely everything. So it’s the perfect time to have this conversation. What was your talk about today? What did you actually talk about in front of those people? [00:05:24] James Dominy: Right. So my talk was about the influence of AI on the WordPress community. The WordPress community involving, in my mind, roughly three groups. You’ve got your freelancer, single content generator, blogger. You have someone who does the same job but in a business as in an agency or a marketing or a brand context. And then on the other side, you’ve got software developers who are developing plugins or working on the actual WordPress Core. And AI is going to be changing the way all of those people work. Mostly I focused on the first and the third groups. I don’t know enough about the business aspects to really talk about the agency and the marketing side of things. I personally, I’m a software developer, so I suppose I really skewed towards that in the end. But, my wife has been a WordPresser for 15, 20 years, which is how I ended up doing this. And a lot of the things that she’s been using ChatGPT quite actively recently. And she’s been chatting to me after work going, you know, I was trying to use ChatGPT to do X Y Z. And I thought, well, you know, that’s interesting. I know some bit about machine learning and the way these things work. I’ve read some stuff on the internals and I have opinions. [00:06:33] Nathan Wrigley: Perfect. [00:06:34] James Dominy: So that’s how I got here. [00:06:35] Nathan Wrigley: Yeah. Well, that’s perfect. Thank you. It seems like at the moment the word ChatGPT could be easily interchanged with AI . Everybody is using that as the pseudonym for AI and it’s not really, is it? It really is a much bigger subject. But that is, it feels at the moment, the most useful implementation in the WordPress space. You know, you lock it into the block editor in some way shape and you create some content in that way. [00:07:00] James Dominy: And I mean, I am absolutely guilty of that. I think the number of times I’ve said ChatGPT, I mean AI generative systems, or something during my workshop this morning is well beyond count. it is likely to fall victim of a trademark thing at some point. Like Google desperately tries to claim that Google is a trademark and shouldn’t be used as a generic term for search. I expect the same thing will happen with ChatGPT at some point. [00:07:25] Nathan Wrigley: This is going to sound a little bit, well, maybe snarky is the wrong word, but I hope you don’t take it this way, but it feels to me that the pace of change in AI is so remarkably rapid. I mean, like nothing I can think of. So, is there a way that we can even know what AI could look like in a year’s time, two years’ time, five years’ time? So in other words, if we speculate on what it could be to WordPress, is that a serious enterprise? Is it serious endeavor? Or are we just hoping that we get the right guess? Because I don’t know what it’s going to be like. [00:07:59] James Dominy: I think if we rephrase the question a bit, we might get a better answer. So AIs are human design systems. And there is a thing called the alignment problem where there is an element of design to AIs, and we give it a direction, but it doesn’t always go the direction we want and I think that is the unanswerable part of this question. Yes, there are going to be emergent surprises from the capabilities of AIs. But for the most part, AIs are developed with a specific goal in mind. Large language models were developed, okay I’m taking a wild educated guess here perhaps, but they were developed with the idea of producing text that sounded like a human. And I mean, we’ve had the Turing test for nearly a hundred years, more than a hundred years? 21, yeah, more than a hundred years now. So I mean, that’s been a goal for a hundred years. Everyone says that AI has advanced rapidly and it has, but the core mathematical principles that are involved, those haven’t advanced. I don’t want to take away from the people who’ve done the work here. There has been work that’s been put into it, but I think what’s really given us the quantum leap here is the amount of computational power that we can throw at the problem. And as long as that is increasing exponentially, I think we can expect that the models themselves will get exponentially better at roughly the same rate as the amount of hardware we throw at it. [00:09:28] Nathan Wrigley: So we can stare into the future and imagine that it’s going to get exponentially, logarithmically it’s going to, it’s just going to get better and better and better. But we can’t predict the ways that it might output that betterness. Who knows what kind of interface there’ll be, or. [00:09:41] James Dominy: Yeah. I think better’s a very evasive term perhaps, on my part. I think there are specific ways that it is going to get better. For example, we are going to see less confused AIs, because they are able to process more tokens. They have deeper models. Deeper statistical trees for outputs. They’re able to take more context in and apply it to whatever comes out. So in that sense we’re going to see a better output from an AI. Is it going to ever be able to innovate? Ooh, that’s a deep philosophical question, and I mean we can get into that, but I don’t know that we have time. [00:10:20] Nathan Wrigley: I think I would like to get into that. [00:10:22] James Dominy: Okay. [00:10:22] Nathan Wrigley: Because when we begin talking about AI, I think the word which sticks is intelligence. The artificial bit gets quickly forgotten and we imagine that there is some kind of intelligence behind this, because we ask it a fairly straightforward, or even indeed quite complicated question. And we get something which appears to pass the Turing test. Just for those people who are listening, the Turing test is a fairly blunt measure of whether you are talking to something which is a human or not human, masquerading as a human. And if something is deemed to have passed the Turing test, it’s indistinguishable from a human. And so, I have an intuition that really what we’re getting back, it’s not intelligent in any meaningful sense of the word. It’s kind of like a regurgitation machine. It’s sucking in information and then it’s just giving us a best approximation of what it thinks we want to hear. But it’s not truly intelligent. If you asked it something utterly tangential, that it had no capacity, it had no data storage on, it would be unable to cope with that, right? [00:11:22] James Dominy: I think yes. If you can clearly delineate the idea of, we have no data on this, which is very difficult considering the amounts of information that, you know, give something access to Wikipedia and that AI generative system might well be able to produce an opinion on practically anything these days. But if it hasn’t read the latest paper on advanced quantum mechanic theory, it’s not going to know it. That text isn’t going to be there. Could it reproduce that paper? That’s a subtely different question, because then it comes down to, well, when a human produces that paper, what are they really doing? They’re synthesizing their knowledge from a bunch of different things that they’ve learned, and they’re producing text in a language, in a grammar, that they have learned in a very similar way, that statistically speaking this sentence follows this grammatical form. Because I have learned that as a child through hearing it several thousand times from the people around me and my parents. What’s different? A more practical example here, I was having this discussion earlier today, and someone said yes, but they’re not truly intelligent. But if you consider it, even now, we can ask Chat GPT something, and I’m going to be abstract cause I don’t have a concrete example here, I’m sorry. But we can say to ChatGPT, I want you to produce a poem in the style of Shakespeare, a sonnet or something. But I want you to use a plot from Goethe. Okay, fine. Now it can do that. It can give you a response. I’m not sure that it’ll be a good response. I haven’t tried that particular one. But in that context, if you are asking a human to do that, and we automatically make the assumption of other human beings that they understand. And, sorry, I’m making air quotes here. That they understand, in quotes, who Goethe is. That that is a person and a character. That Goethe has a particular style and a proclivity for a certain pattern in his plots. And that those are all, to use a computer science term, symbolic representations. Abstract concepts. So is ChatGPT actually understanding those abstract concepts? Does it understand that Goethe is a person? Educated guests here, probably not. But it does understand that Goethe refers to a certain, can draw a line in all the stuff that it has learned and know this is Goethe. It has a concept of what it thinks Goethe is. Then from there it can say, and he has done work on the following things, and these are plots. And so it kind of understands. There’s another line there about what a plot is, which is a very abstract concept. Does that mean it’s intelligent? Does that mean it understands? I don’t know. That’s my answer because I did biochemistry at university, and there’s also the question there, and it’s exactly the same question. It’s at what point do the biological machines, the biochemical machines, your actual proteins and things that are obviously on their own, unintelligent, and yet when they act in concerts, they produce a cell, and a living being. Where does that boundary exist? Is it gray? Is it a hard line? And the same for me is true of the intelligence question here. Intelligence is a, it’s an aglomeration of lots of small, well-defined things that when they start interacting, become more than the sum of their parts. Does it come down to the Turing test? I mean, the fact that people on support, little support popups on the web, have to ask, are you a human every now and then. It immediately says, we have AIs that have passed the Turing test long ago. But here in this case, like the extended Turing test is the thing actually intelligent? I don’t know. I genuinely don’t know the answer there. In some sense, yes, because it’s doing almost the same thing as we are, just in a different, with different delineations and different abstractions, but the process is probably the same. [00:15:33] Nathan Wrigley: Given that you’ve got a background in, forgive me, did you say biochemistry? [00:15:37] James Dominy: Yeah, biochemistry and computer science, bioinfomatics. [00:15:39] Nathan Wrigley: Yeah, do you have an intuition as to whether the substrate of the brain has some unique capacity that can lock intelligence into it? In other words, is there a point at which a computer cannot leap the hurdle? There’s something special about the brain, the way the brain is created? This piece of wetwear in our head. [00:16:00] James Dominy: Unpopular opinion, I think it comes down to brute force count. We’ve got trillions of cells. Large language models, I don’t know what the numbers are for GPT4, but we’re not at trillions yet. Maybe when we get there, I don’t know where the tipping point is, you know. Maybe when we get to tens of billions, or whatever number it happens to be, is the point where this thing actually becomes intelligent. And we would be unable to distinguish them from a human, other than the fact that we’re looking at a screen that, that we know it’s running on the chip in front of us. But if it’s over the internet and it’s on a machine running, or whether we’re talking to a person in the support center. Or we are at the McDonald’s kiosk of 2050 and being asked whether we want fries with that. If we can’t see the person who’s asking the question, if we’re at the drive-through, we can’t see the person. Do we care? [00:16:54] Nathan Wrigley: Interesting. You mentioned a couple of times large language models, often abbreviated just to LLM. My understanding at least, forgive me I’m, I really genuinely am no expert about this. This is the underpinning of how it works. I’m going to explain it in crude terms, and then I’m hoping you’ll step in and pad it out and make it more accurate. [00:17:12] James Dominy: I should caveat anything that I say here with I also am not an expert on these, but I will do what I can. [00:17:17] Nathan Wrigley: So a large language model, my understanding is that things like ChatGPT are built on top of this, and essentially it is vacuuming up the internet. Text, images, whatever data you can throw at it. And it’s consuming that, storing that. And then at the point where you ask it something, so write a sonnet in the style of Goethe, written by Shakespeare. It’s then making a best approximation, and it’s going through a process of, okay, what should the first word be? Right, we’ve decided on that. Now, let’s figure out the second word, and the third word and the fourth word. Until finally it ends in a full stop and it’s done. And that’s the process it’s going through. Which seems highly unintelligent. But then again, that’s what I’m doing now. I’m probably selecting in some way what the next word is and what the next word is. But yeah, explain to us how these large language models work. [00:18:03] James Dominy: I think that’s a pretty fair summation. I think the important bit that needs to be filled in there is that what we perceive and use as customers of AI systems in general is a layer of several different models. There is a lot of pre-processing that goes into our prompts and post-processing in terms of what comes out. But fundamentally the large language model is, yes, it’s strings of text generally. There are different systems that the AI images, image systems, are a different form of maths. Most of them, at least the ones that I know of, are mostly based on something called Stable Diffusion. We can chat about that separately, but large language models tend to be trained on a large pile of text where they develop statistical inferences for the likelihood of some sequence of words following some other sequence of words. So as you say, like, if I know that a pile of words were written by Goethe, then I can sub select that aspect of my trained data. And I’m personifying an AI here already. The AI can circumscribe, isolate a portion of its training set, and say, okay I will use this subset of my training, and use the statistical values for what words follow what other words that Goethe wrote. And then you will get something in the style of Goethe out. [00:19:29] Nathan Wrigley: It’s kind of astonishing that that works at all. That one word follows another in something which comes out as a sentence because, I don’t know if you’ve ever tried that experiment on your phone where you begin the predictive text. On my phone there’s there’s usually three words above the little typewriter, and it tries to say what the next word is based upon the previous word. [00:19:49] James Dominy: It’s not called auto corrupt for nothing. [00:19:50] Nathan Wrigley: Yeah, so you just click them at the end of that process, you have fantastic gibberish. It’s usually quite entertaining, and yet this system is able to, in some way just hijack that whole process and make it so that by the end the whole thing makes sense in isolation. It is Goethe. It looks like Shakespeare, sounds like Shakespeare, could easily be Shakespeare. How is it predicting into the future such that by the end, the whole thing makes sense? Is there more processing going on than, okay, just the next word. Is it reading backwards? [00:20:22] James Dominy: Yes absolutely. Again, not an expert on LLMs, but there is this thing called a Markov Model. Which is a much more linear chain. It’s used often for bioinformatics, for genome and predicting the most likely next amino acid or nucleic acid in a genomic or a proteomic sequence. And so Markov Models are very simple. They have a depth and that is how much history they remember of what they’ve seen. So you point a Markov Model at the beginning of the sequence of letters of nucleic, the ACGT’s. And then you want to say, okay, I’ve managed to sequence this off my organism. I’ve got a hundred bases and I want to know what the most likely one after that is, because that’s where it got cut off. You give it a hundred, maybe you have a buffer of 10. So it remembers the last ten. It sort of slides this window of visibility over the whole sequence and mathematically starts working out, you know, what comes after an A? Okay, 30% of the time it’s a C. 50% of the time it’s a G. And by the end of it, it can with reasonable accuracy to some value of how much information you’ve given it, predict okay, in this particular portion of 10 that I’ve seen, the next one should be T. And they get better as you give them more and more information. As you give them a bigger and bigger window. As you let them consume more and more memory whilst they’re doing their job, their accuracy increases. I imagine the same is true of large language models, because they do. They don’t just predict the next word, they operate on phrases, on whole sentences. At some point, maybe they already do, but I imagine they operate on whole paragraphs. And again, it depends on what you’re trying to produce. Like if you’re trying to produce a legal contract that’s got a fairly prescribed grammar and form to it. And you know, then like statistically you’re going to produce the same paragraph over and over again because you want the same effect out of contracts you do all the time. [00:22:22] Nathan Wrigley: You described this slider. That really got to the nub of it. I genuinely didn’t realize that it wasn’t doing any more than just predicting the next word. And because that’s the way I thought about it, I thought it was literally astonishing that it could throw together a sentence based upon just the next word, if it didn’t know what two words previously it had written. It’s back to my predictive text, which produces pure gobbledygook. But it still, occasionally, it goes down a blind alley, doesn’t it? Because although that is, presumably 99 times out of a hundred that will lead to a cogent sentence, which is readable. Occasionally it does this thing, which I think has got the name hallucinate, where it just gets slightly derailed and goes off in a different direction. And so produces something which is, I don’t know, inaccurate, just nonsense. [00:23:06] James Dominy: Yes. Well known for being confidently wrong for sure. I’ve experienced something similar, and I find that it is especially the case where you switch contexts. Like when you are asking it to do more than one thing at a time, and you make a change to the first thing that you expect to carry over into the context of the second task, and it just doesn’t. It gets confused. And then the two things, this is especially true in coding, where you ask it to produce one piece of code and a function here, and another piece of code and a function on the other side. And you expect them, those two functions to interoperate correctly. Which means that you have to get the convention, the interface between those two things, the same on both sides. But if you say, actually, I want this to be called Bob, that doesn’t necessarily translate. Again, I suppose this is my intuition. There are a lot of ways that that failure can happen. The most obvious one is that you’re doing too much and it’s run out of tokens. Tokens are sort of an abstraction. Sorry I used that word a lot. Computer scientist. Tokens are, they’re not strictly speaking individual words, but they are a rough approximation of a unit of knowledge, context. I don’t know what the right word here. They chose token, right? So, if you use the API for ChatGPT, one of the things that you pass is how many tokens is the call allowed to use? Because you are charged by tokens. And if you say only 30 tokens, you get worse answers than if you give it an allowance of a hundred tokens. Meaning that you might have given it a problem that exceeds the window that I was describing earlier. That sort of backtrack of context that it’s allowed to use. Or you give it to two contexts and together they just go over and then it’s confused because it doesn’t know which, again, I say this as a semi-educated guess. We as humans don’t have a good definition of what context means in this conversation. How do we expect a computer system to? [00:25:05] Nathan Wrigley: Just as you’ve been talking, in my head, I’ve come up with this analogy of what I now think AI represents to me, and it represents essentially a very, very clever baby. There’s this child crawling around on the ground, I really do mean an infant who you fully forgive for knocking everything over and, tipping things over, damaging things and what have you. And yet this child can speak. So on the one hand, it can talk to you, but it’s just making utterly horrific mistakes because it’s a baby and you forgive it for that. So I don’t know how that sits, but that’s what’s it landed in my head. [00:25:40] James Dominy: I wouldn’t say that AI is in its infancy anymore, but it’s probably in its toddler year, and maybe we need to watch out when it turns two. [00:25:47] Nathan Wrigley: So we’ve, done the sort of high level what is AI and all of that. That’s fascinating. But given that this is a WordPress event and it’s a WordPress podcast, let’s bind some of this stuff to the product itself. So WordPress largely is a content creation platform. You open it up, you make a post, you make a page, and typically into that goes text, sometimes images, sometimes video, possibly some other file formats. But let’s stick with the model of text and images. Why do we want, or how could we put AI into WordPress? What are the things that might be desirable in a WordPress site that AI could assist us with? [00:26:21] James Dominy: I am totally going to be stealing some ideas from the AI content creation things that have happened this morning. I mean, there’s the obvious answer. I need to generate a thousand words for my editor by 4:00 PM today. Hey, ChatGPT, can you generate a thousand words on topic, blah? I think there are a lot of other places. I’d be super surprised if this hasn’t actually happened already. But, hey ChatGPT, write me an article that gets me to the top five Google ranking. The other obvious place for me as a software developer is using it to develop code. Humans are inventive. We’re going to see a lot of uses for AI that we never thought of. That’s not a bad thing at all. The more ways that we can use AI, I think the better. Yes, there are questions about the dangers, and I’m sure that’s a question coming up later on, so I won’t dive into them now, but in the WordPress community, there’s content creation, but there’s also content moderation, where AI can probably help a lot. Analyze this piece of text to me and tell me is it spam? Does it contain harmful or hateful content? Again, it’s a case of you get what you give. There’s that story about Microsoft, I think it was Microsoft, and the chatbot that turned into a horrible Nazi racist within about two hours, having been trained on Twitter data. We need to be careful about that, certainly. I’m struggling to think of things beyond the obvious. [00:27:47] Nathan Wrigley: Well, I think probably it is going to be the obvious, isn’t it? Largely, people are popping in text and so having something which will allow you within the interface, whether you are in a page builder or whether you’re using the Gutenberg editor, the ability to interrupt that flow and say, okay, I’ve written enough now, ChatGPT, take over. Give me the next 300 words please. Or just read what I’ve written and can you just finish this? I’m almost there. [00:28:11] James Dominy: Yeah, we are doing it already, even if it’s a sort of fairly primitive flow now where we write some stuff in our block editor, copy it up, pop it in ChatGPT or Bard or whatever, and say, hey, this is too formal. Or this is not formal enough. And it’s really great at that. Make this sound more businessy. And it understands the word businessy. The tool integration, it’s obvious in a lot of ways, but I think there are going to be a lot of non-obvious integrations. Like, oh wow, I wish I thought of that, and, you know, made my millions off that product. I mean, Jetpack is doing it already, you know. I am able to actively engage with ChatGPT whilst I’m editing my blog post. Fantastic. Another thing that I’ve just thought of is oh, I run a WooCommerce site and I want to use, not necessarily ChatGPT, but some other AI system to analyze product sales and use that to promote, to change the listing on my product site, so that I can sell more product. That’s going to happen. [00:29:09] Nathan Wrigley: Yeah, given that it’s incredibly good at consuming data. [00:29:13] James Dominy: Yeah, or even generating it on the fly. Generate 300 different descriptions of this product and randomize them. Put them out there and see which one sells best. We are doing that manually already. It’s AB testing at a larger scale. [00:29:28] Nathan Wrigley: Yeah. You can imagine a situation where the AI runs the split test, but it’s divided over 300 variations. And it decides for itself which is the winner. [00:29:39] James Dominy: On a day-to-day basis. [00:29:40] Nathan Wrigley: On an hourly basis. Implements the winner and then begins the whole process over and over again. I also wonder if in WordPress there is going to be AI to help lay out things. So at the moment we have the block editor. It enables you to create fairly complex layouts. We also have page builders, which allow us to do the same thing. So it alludes to what I was speaking about a moment ago. Talking, so literally talking, as well as typing in. I would like a homepage. I would like that homepage to show off my plumbing business, and here’s my telephone number. I’d like to have a picture of me, or somebody doing some plumbing, some additional content down there. You get the picture? [00:30:17] James Dominy: Yeah, absolutely. [00:30:18] Nathan Wrigley: A few little prompts, and rather than spitting out text or an image, whole layouts come out. And we can pick from 300 different layouts. I’ll go for that one, but now make the buttons red. The AI takes over the design process in a way. [00:30:32] James Dominy: Yeah. I’m going to confess here that I’m absolutely stealing this opinion from the AI panel earlier. I think the danger for WordPress specifically there, is that that level of automation for us with human engagement and, you know, developing something through conversation with an AI, might actually skip WordPress entirely. Why must the AI choose WordPress to do this? Maybe if we as a WordPress community invest in making WordPress AI integrated, then yeah, absolutely. Then hopefully we’re first to market with that in a way. And then it will generate stuff in WordPress. But there’s no, there’s no reason for it to maybe choose a Wix page as a better solution for you as a plumber, who doesn’t update things very often. You just want a static, you know. Chances are it’ll just say, here is some HTML it does the job for you, it’s pretty. I made some images for you as well. And, all you need to do is run the sequence of commands to, SSH it up to provider of your choice. Or I have selected this provider because I know how much they all charge and this is the cheapest. Or you’ve asked for the fastest, whatever. [00:31:41] Nathan Wrigley: Oh, interesting, okay. So it’s not just bound inside the WordPress interface. Literally, put this in the cheapest place as of today. And then if it changes in the next 24 hours, just move it over there and change the DNS for me and. [00:31:53] James Dominy: One day. For sure. Yeah. [00:31:54] Nathan Wrigley: Okay. So that very nicely ties into the harms. [00:31:58] James Dominy: There it is. [00:31:58] Nathan Wrigley: What we’ve just laid out is potentially quite harmful to a lot of the jobs that people do inside of WordPress. We’ve just described a workflow in which many of the things that we would charge clients for, which we could potentially get AI to do. Whether that’s a voice interface or a visual interface or a type, we’re typing in. So that is concerning, if we are giving AI the option to put us out of work. And I know at the moment, this is the hot topic. I’m pretty sure that there’s some fairly large organizations who have begun this process already. They’ve taken some staff who are doing jobs which can be swapped out for AI, and they’ve shed those staff. And whilst we’re in the beginning phase of that, it seems like we can swallow so much of people getting laid off. The problem, potentially is, if we keep laying people off over and over and over again and we give everything over to the AI, we suddenly are in a position where, well, there’s no humans in this whole process anymore. Does any of that give you pause for thought? [00:32:53] James Dominy: Yeah, it certainly does. I think we should temper our expectations of the capabilities of AI. So there’s a technical term called a terminal goal. The delineation between specific artificial intelligences and machine learning, in that world, and the concept of the general artificial intelligences, which is what everyone thinks of when they think of the I in artificial intelligence, is an AI that is capable of forming its own terminal goals. Its own, don’t get me wrong, like we have AIs that are capable of forming what are called intermediate nodes. If you tell an AI of a particular type to go and do a particular thing, then it is capable of forming intermediate steps. In order to do the thing you’ve told me, I need to first do this, which requires me to do that. And, you know, it forms a chain of goals, but none of those goals are emergent from the AI. They are towards a goal we have given the AI externally. That ability to form a goal internally is the concept of a terminal goal. And we don’t have, large language models don’t have terminal goals. Large language models, stable diffusion, all of the different algorithms that are hot topics today, are all couched within the idea of solving a problem given to them as an input. Which means there’s always going to need to be a human. At least with what we’ve got now. No matter how good these models get, how much brain power we give them. And this maybe is going against what I said earlier of like, I think it’s probably a quantity thing. Maybe there’s a tipping point. Maybe there’s a tipping point where the intermediate goal that it forms is indistinguishable from a terminal goal in a human brain. But for the moment, I think there always needs to be a human there to give the AI the task to solve. Open AI isn’t just running servers randomly just doing stuff. It spends its computational time answering users prompts and questions. [00:34:48] Nathan Wrigley: So if we pursue artificial intelligence research, and the end goal is to create an AGI, then presumably at some point we’ve got something which is indistinguishable from a human because it can set its own goals. [00:35:02] James Dominy: The cyberpunk dystopia, right? [00:35:03] Nathan Wrigley: But we’re not there yet. This is a ways off, my understanding at least anyway. But in the more short term, let’s bind it to the loss of jobs. [00:35:11] James Dominy: In my workshop this morning, I think the primary point that I wanted to get across is, if you are currently in the WordPress community, employed and or making an income out of WordPress. ChatGPT, Bard, generative AI, large language models are a tool that you should be learning to use. They’re not going to replace you. Maybe that’s less true on the content generation side, because large language models are particularly good at that. But there’s a flip side to that because on the software development side, programming languages have very strict grammars, which means the statistical model is particularly good at producing output for programming languages. It’s not good at handling the large amounts of complexity that can exist in large pieces of code. But equally so, I mean, if you ask it to give you a hundred items of things to do in Athens, whilst I’m totally, totally, working hard at a conference, uh, then you are probably going to get repeats. You might run into the confusion problem, the hallucination issue at some point there, where just a hundred is too much. Nobody has ever written an article of a hundred things to do in Athens in a day. I don’t know, I haven’t tried that. I’m guessing that there are going to be limitations. So some jobs are more in threat than others, but I think that if you’re already in the industry, or in the community and working with it, go with it and, absorb the tools into your day-to-day flow. It’s going to make you better at what you do. Faster at what you do. Hopefully able to make more money. Hopefully able to communicate with more people, translations et cetera. Make your blog multilingual. There are a lot of things that you can use it for that aren’t immediately coming after your job. The problem for me, and this again is the point that I was trying to get across in the workshop, the problem is the next generation. The people who are getting into WordPress today and tomorrow, and in six months time. Who are coming into a world where AI is already in such usage that it’s solving the simple problems. And the same as true, my editor wants 200 words or whatever on fun things to do in Athens overnight. Okay, great. ChatGPT can do that for the editor. Why does he need a junior content writer anymore? But the problem is, I mean, we’ve already said, sometimes it’s spectacularly wrong. Does that editor always have the time to actually vet the output? Probably not. And so the job of that junior is going to transform into, they need to be a subeditor. They need to be a content moderator almost, rather than a content generator. But that’s a skill that only comes from having written the content yourself. We learn by making mistakes, and if we are not making those mistakes because AI is generating the stuff, and either not making mistakes or making mistakes that we haven’t made before ourselves, and thus don’t recognize his mistakes. So my fear of the job losses aspect of AI is not that it’s going to wipe out people who are working already. It’s going to make that barrier to entry for the next generation, it’s knocking the bottom rung out of the ladder. And unless we change the ways that we teach people as they are entering the community, the WordPress community, the industry, and all the industries which AI is going to affect, the basics, and we focus on it. You know, it’s a catch 22. We have to teach people to do stuff without AI, so they can learn the basics. But at the same time, they also have to learn how to use AI so they can do the basics in the modern world. And I mean, we get back to that old debate like, why am I learning trigonometry in school? Because maybe someday it actually helps you do your job. Admittedly, so far, not so much. But I will say this. History, I did history in school. That has surprisingly turned out to be one of the most useful subjects I ever did, just because it taught me how to write. Which I didn’t learn in English class. Go figure. [00:39:17] Nathan Wrigley: It sounds like you are quite sanguine for now. If you are in the space and listening to this podcast now, everything is fine right now. [00:39:26] James Dominy: Yeah. [00:39:27] Nathan Wrigley: Maybe less sanguine for the future. Given that, do you think that AI more broadly needs to be corralled. There need to be guardrails put in place. There needs to be legislation. I don’t know how any of that works, but manufacturers of AI being put under the auspices of, well it would have to be governments, I guess. But some kind of system of checks and balances to make sure that it’s not, I don’t know, deliberately producing fakes. Or that the fakes are getting, the hallucinations are getting minimized. That it’s not doing things that aren’t in humanity’s best interests. [00:39:59] James Dominy: Absolutely. Yes. Although I’m not sure how we could do a good job of it, to be fair. The whole concept of, we want AIs to operate in humanity’s best interests. Who decides? The alignment problem crops up here where, it’s well known that we can train an AI to do something we think that it’s going to do, and it seems to be doing that thing until suddenly it doesn’t. And we just get some weird output. And then when we go digging, we realize actually it was trying to solve an entirely different problem to what we thought we were training it on, that just happened to have a huge amount of overlap with the thing that we did. But when we get to those edge cases, it goes off in what we think is a wildly wrong direction. But it is solving the problem that it was trained to solve. We just didn’t know we were training it to solve that problem. As far as regulation goes. Yes, I think regulation, it’s coming. I really want to say nobody could be stupid enough to put weapons in the hands of an AI. The human race has proved me wrong several thousand times already in history. Yeesh, I personally think that that’s an incredibly stupid idea. But then the problem becomes what’s a weapon? Because a weapon these days can be something as subtle as enough ability to control trading, high frequency trading. Accidentally crash a stock market. It’s already happened. Accidentally, and again, I’m air quoting the accidentally here, accidentally crash your competitor’s stock, or another nation’s stock market. AI is there, is being used as a validly useful tool to participate in the economy, but the economy can be used as a weapon. Putting AI in control of the water infrastructure in arid countries. Optimization, it can do those jobs a lot better. It can see almost instantaneously when there’s a pressure drop. So there’s a leak in this section of the pipe. Somebody needs to go fix it. And also it can just shut off the water to an entire section of the city because, I don’t know, it feels like it. Because for some reason it is optimizing for a different goal than we actually think we gave it. The trick is we can say, we can input into ChatGPT, I want you to provide water to the entire city in a fair and equitable way. That doesn’t mean that’s what it’s going to do. We just think that that’s what it’s going to do. We hope. [00:42:26] Nathan Wrigley: I think we kind of come back to where we started. If we had a crystal ball, and we could stare five, two years, three years, 10 years into the future. That feels like it would be a really great thing to have at the moment. There’s obviously going to be benefits. It’s going to make work certainly more productive. It’s going to make us be able to produce more things. But as you’ve just talked over the last 20 minutes or so, there’s also points of concern and things to be ironed out in the near term. [00:42:52] James Dominy: Absolutely, yeah. [00:42:53] Nathan Wrigley: We’re fast running out of time, so I think we’ll wrap it up if that’s all right? A quick one James, if somebody is interested, you’ve planted the seed of interest about AI and they want to get in touch with you and natter about this some more, where would they do that? [00:43:06] James Dominy: The best way is probably email. I am not a social person in the social media sense. I don’t have Twitter. I don’t do any of that. So I’m probably terrible for this when I think about it. My email is, J for Juliet, G for golf, my surname D O M for mother, I, N for November, Y for yankee at gmail.com. Please don’t spam. Please don’t get AI to spam me. [00:43:30] Nathan Wrigley: Yeah, yeah. James Dominy, thank you so much for joining us today. [00:43:34] James Dominy: Thank you for the opportunity. It’s been great fun, and I’ve really enjoyed being able to kind of deep dive into a lot of the stuff I just had to gloss over in the workshop. Thank you. On the podcast today we have James Dominy. James is a computer scientist with a masters degree in bioinformatics. He lives in Ireland, working at the WPEngine Limerick office. This is the second podcast recorded at WordCamp Europe 2023 in Athens. James gave a talk at the event about the influence of AI on the WordPress community, and how it’s going to disrupt so many of the roles which WordPressers currently occupy. We talk about the recent rise of ChatGPT and the fact that it’s made AI available to almost anyone. In less than twelve months many of us have gone from never touching AI technologies to using them on a daily basis to speed up some aspect of our work. The discussion moves on to the rate at which AI systems might evolve, and whether or not they’re truly intelligent, or just a suite of technologies which masquerade as intelligent. Are they merely good at predicting the next word or phrase in any given sentence? Is there a scenario in which we can expect our machines to stop simply regurgitating text and images based upon what they’ve consumed; a future in which they can set their own agendas and learn based upon their own goals? This gets into the subject of whether or not AI is in any meaningful way innately intelligent, or just good at making us think that it is, and whether or not the famous Turing test is a worthwhile measure of the abilities of an AI. James’ background in biochemistry comes in handy as we turn our attention to whether or not there’s something unique about the brains we all possess, or if intelligence is merely a matter of the amount of compute power that an AI can consume. It’s more or less certain that given time, machines will be more capable than they are now, so when, if ever, does the intelligence Rubicon get crossed? The current AI systems can be broadly classified as Large Language Models, or LLMs for short, and James explains what these are and how they work. How can they create a sentence word by word if they don’t have an understanding of where each sentence is going to end up? James explains that LLMs are a little more complex than just handling one word at a time, always moving backwards and forwards within their predictions to ensure that they’re creating content which makes sense, even if it’s not always factually accurate. We then move on from the conceptual understanding of AI to more concrete ways it can be implemented. What ways can WordPress users implement AI right now, and what innovations might we reasonably expect to be available in the future? Will we be able to get AI to make intelligent decisions about our website’s SEO or design, and therefore be able to focus our time on other, more pressing, matters? It’s a fascinating conversation whether or not you’ve used AI tools in the past. Implementing a CAPTCHA or reCAPTCHA system is a highly effective way to protect your WordPress website or ecommerce business from spam and bots, which is crucial for ensuring online security. All that sounds great, but the effort involved in solving a CAPTCHA often results in reduced conversions. According to Moz, including a CAPTCHA could result in a loss of 3.2% of conversions. Yikes! That’s why today, we’ll explain the problem with the traditional CAPTCHA setup, offer a stand-out alternative, and provide steps to add CAPTCHA and reCAPTCHA to your WordPress site, if that’s still the route you feel most comfortable with. After following this guide, your website will be safer and more secure for your visitors. Let’s get started! While CAPTCHA systems have been widely adopted for their ability to prevent spam and bot activity, they do come with a number of drawbacks. Make sure you’re aware of these downsides before you use a WordPress CAPTCHA plugin. Traditional CAPTCHA systems often rely on distorted images of text, making it difficult for users with visual impairments to solve them. This can lead to accessibility issues and discourage visitors from interacting with your site. CAPTCHAs can be frustrating and time-consuming to solve, particularly when the distorted text is difficult to read. This annoyance can cause people to leave your site without completing their intended action, such as submitting a form or making a purchase. Sometimes, visitors may even have to solve multiple CAPTCHAs — a real test of endurance. CAPTCHA systems can sometimes incorrectly identify real human users as bots, preventing them from accessing your site or submitting forms. This can lead to a loss of leads, customers, or subscribers. As bots become more advanced, they’re increasingly able to bypass traditional CAPTCHA systems, rendering them less effective at preventing spam and malicious activity on your site. Implementing CAPTCHA systems can negatively impact your site’s user experience, particularly when the CAPTCHAs are overly complex or difficult to solve. This can lead to lower visitor satisfaction and, ultimately, decreased engagement and conversions. As mentioned above, the frustrating experience of solving CAPTCHAs can lead to users abandoning your site before completing their intended actions. This can result in lower conversion rates for your business. Implementing CAPTCHA systems can also contribute to slower page load times, as they often require additional resources and scripts to load. This can negatively impact your site’s performance and search engine rankings. Given these challenges, it’s important to find a solution that’s both effective at preventing spam and bots, while also providing a positive user experience. That’s where Akismet comes in to save the day. Akismet addresses the shortcomings of traditional CAPTCHA systems by employing advanced algorithms and a continuously-updated database of spam signatures. It can effectively identify and block spam and malicious activity without any user input and without annoying barriers for site visitors. The result is enhanced accessibility, a superior user experience, and fewer false positives. Even the most sophisticated bots can be identified and blocked by Akismet due to its advanced spam detection technology and constantly-updated database. By staying ahead of emerging threats, Akismet ensures your online presence remains secure and your valuable content and data are safeguarded. Given the challenges associated with traditional CAPTCHA solutions, Akismet presents several benefits that make it a compelling and superior alternative for WordPress site owners. Akismet doesn’t require users to solve puzzles or enter codes, ensuring a more pleasant and frustration-free browsing experience. It operates seamlessly in the background, allowing visitors to focus on your content and offerings without any distractions or interruptions. Akismet can be used by people with vision impairments because it doesn’t use visual puzzles to block spam and bots. This approach makes sure that your website is user-friendly and welcoming to a diverse audience, creating a positive online environment for everyone. Akismet uses advanced algorithms and a vast database of spam signatures to minimize false positives. This means that genuine users can access and interact with your site without being mistakenly identified as bots. This accurate spam detection helps build a trustworthy online presence and improve user experiences. Akismet is highly effective at identifying and blocking spam and malicious activity, including sophisticated bots that can bypass traditional CAPTCHA systems. Its constantly-updated database and advanced spam detection technology ensure your website remains secure and protected from emerging threats. Akismet runs in the background and won’t slow down your website by using extra data or running unnecessary scripts. This means your website will stay fast and responsive for your visitors, which can help improve your search engine rankings and create a great browsing experience. If this sounds like a solid prospect, you’ll be delighted to hear that we’re discussing how to install and set up Akismet on WordPress next. Incorporating Akismet into WordPress comment and contact forms is a breeze, and you can accomplish it in just a few steps. However, the procedure might differ slightly depending on the contact form or plugin you’re using. Let’s explore how it’s done! Akismet can be used for free to get rid of spam comments and harmful form submissions on your non-commercial site. Websites run for commercial purposes can choose from several affordable premium options. First, install and activate the plugin. To do this, log in to your WordPress dashboard, go to the Plugins tab, click Add New, and search for it. The plugin is usually included in the top “Featured” list. To install the plugin, click on Install Now and then Activate. After activation, go to Settings and select Akismet Anti-Spam. Under Settings, locate the API key field. You can get the key by going to the Akismet website and creating an account. Once you finish the signup process on the website, log in to your new account then locate My Account and choose Add Subscription. You can select your desired plan next. The Personal plan is free for individual website use if your site is considered “non-commercial.” After registering, you’ll receive an API key in the My Account section. Copy this key and then navigate to the WordPress dashboard’s Settings → Akismet Anti-Spam screen. Next, paste the key into the API Key field. Click on Save Changes to finish. Akismet will automatically filter comment spam and put it in a queue for review on the dashboard. But if you want it to work on your contact form(s), you’ll need to complete another step. By default, WordPress does not have a contact form feature. Therefore, you’ll need to use plugins to include contact forms on their sites. The method to add these forms will vary based on the plugin being used. Some popular contact form plugins, including Jetpack, already have Akismet support built-in. Other plugins necessitate setting up Akismet add-ons to incorporate spam protection into their forms. Gravity Forms is the most popular example of this. Still other WordPress plugins like Contact Form 7 require a code snippet to add Akismet support. Thankfully, it’s easy to configure Akismet on your contact forms, no matter which method you choose. Akismet is very much a set-it-and-forget-it type of tool. Just install, activate, and you’re basically done. But it also allows you to control how to handle contact form spam a bit more precisely. The plugin is configured, by default, to send flagged comments to a holding queue located in the Comments section of the WordPress dashboard so that you can review them later. You can also set up Akismet to delete spam entirely. If this sounds appealing, just go to Settings → Akismet Anti-Spam and locate the Settings. Scroll down to the section called Strictness. Akismet is good at identifying which messages are spam and which ones are legitimate, which means you can delete the spam messages from your contact form without worry. However, if you want to keep all messages, you can select the option to Always put spam in the Spam folder for review. Remember that Akismet stores spam comments for 15 days before they’re deleted. So, if you go for this option, review your queue regularly. Although we suggest using Akismet due to its ease-of-use and success in blocking spam and bots, we realize that certain users may still want to learn how to add CAPTCHA to WordPress. This section will provide clear instructions on how to integrate both CAPTCHA and reCAPTCHA into a WordPress contact form. Although most well-known contact form plugins include CAPTCHA functionality, you can also manually incorporate CAPTCHA into any form element on WordPress that’s being misused. This not only includes contact forms, but also comment forms, user registration pages, login pages, and opt-in forms. For the purposes of this tutorial, we’re using the Friendly CAPTCHA for WordPress plugins, though there are other options available. Go to your WordPress dashboard then to Plugins → Add New and search for the plugin by name. Once you locate it, click Install → Activate. To input your Site key and Secret key, locate Friendly Captcha in the dashboard, then click Settings. Then go to the Friendly Captcha website and create an account. Pick a plan, then copy your site key. Go back to your WordPress installation and paste in the Site key in the appropriate field. Then go back to your account on the website and generate an API key by typing in a name for it then clicking Create API Key. For this tutorial, please select the comment form box to enable forms and keep all other settings at their default values to configure the remaining options based on your preferences. Once you’re done making changes, click Save Changes, then visit a live blog post to verify the comment form is working as intended. Google reCAPTCHA adds an extra layer of protection to your contact forms, using a two-step verification process. This tool can help stop bots and spammers, as they’ll need to pass the reCAPTCHA test. You can use a WordPress CAPTCHA plugin to get the job done. Here’s how you can incorporate it into your WordPress contact form: First, install and activate the Simple Google reCAPTCHA plugin. Just search for it by name under Plugins → Add New. Then click Install → Activate. After activation, navigate to Settings → Google reCAPTCHA to configure the plugin settings. The plugin will prompt you to enter Google reCAPTCHA keys. You can obtain these keys for free from the official reCAPTCHA website by clicking the register your domain link at the top of the page. The register your domain link directs you to the Google reCAPTCHA website, where you can register your site to work with reCAPTCHA. Sign in with your Google account, and you’ll see the Register a new site page. Enter the necessary basic information to register your site. In the Label field, input your website name or any name of your choice to help you identify your site later. Next, choose the reCAPTCHA V2 radio button to reveal two new options. To add the reCAPTCHA checkbox to your site, select the first option, I’m not a robot checkbox. In the Domains text box, add the domain name of your website. You can also add multiple domains or subdomains by clicking the plus + icon, enabling you to use the same API keys across different websites. Google will automatically add your email address under Owners. You can also add another email if desired. Then accept the terms of service. Select the Send alerts to owners checkbox to allow Google to send emails if they detect any misconfigurations or suspicious activity. After completing the form, click Submit to register your site. Google reCAPTCHA will display a success message, along with the site key and secret key. Use these API Keys in your website’s plugin settings. Navigate to Settings → Google reCAPTCHA from your WordPress dashboard. On the Settings page, paste the site key and secret key. The plugin will incorporate reCAPTCHA verification into the WordPress comment form, registration form, reset password form, new password form, and login form. You can disable reCAPTCHA on the login form by selecting the appropriate checkbox. Remember to click Save Changes to store the API keys and activate reCAPTCHA. You have now successfully added reCAPTCHA to your WordPress comment form. Check the comment section of your blog posts to ensure it’s working correctly. So now you know how to add CAPTCHA or reCAPTCHA to your WordPress contact forms. Although these options can reduce spam and bot activity, we suggest using Akismet instead because it is easy to use, more accessible, and effective against advanced bots. Regardless of the solution you choose, however, keeping your WordPress site secure from spam and malicious activity is crucial for maintaining a positive user experience, safeguarding your online presence, and protecting your reputation. Still curious about CAPTCHA, reCAPTCHA, and how to safeguard the contact forms on your website? Let’s take a look at some answers to the most commonly asked questions on the subject. CAPTCHA, which stands for “Completely Automated Public Turing test to tell Computers and Humans Apart”, is a security measure used on websites to prevent automated bots from submitting forms, leaving comments, or performing other actions that should only be done by human users. CAPTCHAs typically require users to solve visual puzzles — such as identifying distorted text or selecting specific images — to prove that they’re not bots. reCAPTCHA is a more advanced version of CAPTCHA developed by Google. It improves upon traditional CAPTCHA systems by incorporating machine learning and advanced risk analysis techniques to better differentiate between human users and bots. reCAPTCHA is designed to be more user-friendly, with some versions requiring people only to click a checkbox. Akismet is a powerful anti-spam solution for WordPress websites, developed by Automattic, the company behind WordPress.com. It uses advanced algorithms and a continuously-updated database of spam signatures to identify and block spam comments and form submissions, without requiring user input or creating accessibility barriers. Akismet operates in the background (kind of like an invisible CAPTCHA, in a sense), providing a seamless and user-friendly browsing experience. While each solution has its own advantages, Akismet is generally considered more user-friendly and accessible compared to CAPTCHA and reCAPTCHA. It doesn’t require users to solve puzzles or enter codes, making it easier for those with visual impairments and providing a smoother browsing experience overall. Akismet is also highly effective at blocking spam and bots, even as they evolve and become more sophisticated. Yes, Akismet integrates with many popular WordPress contact form plugins, including Contact Form 7. By connecting Akismet to your contact form plugin, you can effectively protect your forms from spam submissions without the need for CAPTCHA or reCAPTCHA. Akismet is trusted by over 100 million websites worldwide, including well-known enterprise brands such as Microsoft, ConvertKit, and Bluehost. Its widespread adoption and use by major companies serve as strong social proof for its effectiveness in preventing spam and ensuring a secure, user-friendly online experience. Should you choose Akismet for your contact and registration forms, you’ll be in good company, joining millions of other websites that have successfully protected their online presence from spam and malicious activity. To keep your WordPress site free from spam and bots while ensuring a good user experience and accessibility, you should use Akismet. It offers an effective way to combat spam that doesn’t disrupt your site visitors’ browsing experience. If you add Akismet to your WordPress site, it will use complex calculations and a big collection of spam markers to keep your site safe from unwanted content. In addition, it integrates smoothly with well-known tools for contact forms, making sure that everyone can use your website securely and without hassle. While CAPTCHA and reCAPTCHA may still be preferred by some, Akismet stands out as a user-friendly, effective, and accessible alternative for securing your WordPress contact forms against spam and bots. And by choosing Akismet, you’re investing in the success of your online presence and ensuring a pleasant experience for your visitors, which is definitely worth prioritizing. Last week Gutenberg contributors were engaged in a spirited debate regarding a proposal to rename the new Command Center to Wayfinder. The feature, designed to be an extensible quick search and command execution tool, will land in WordPress 6.3. The majority of participants in the discussion were strongly against calling it Wayfinder, as the term doesn’t translate well, nor does it make the feature’s benefits easy to understand. Wayfinder was proposed as a unique name that “has the potential to evoke a sense of curiosity, exploration, and discovery.” There were several attempts to wrap up the discussion with notes on alternatives even when it was apparent that the general consensus was unequivocally not in favor of the term Wayfinder. Automattic-sponsored Gutenberg contributor Anne McCarthy commented on the issue with the decision, which she said was reached after consulting project leadership and reading through the comments: Let’s move forward with Command Palette. Reasoning: easier to translate, consistent across other tooling outside of WordPress, matches current functionality, eases discoverability/understanding of value, and leans generic which matches the concerns raised here. Ultimately, we can always discuss renaming if the feature reaches a point of evolution outside of this initial name. As raised above, that would be more worth risking a unique name for than something that exists in other products and that ultimately we want people to quickly understand/find value in. Plus if we hold off on that name for the future, it can create a nice marketing push for something truly unique when/if the time comes. If folks have additional specific concerns around this naming, please speak up sooner rather than later. McCarthy also requested other contributors ensure the re-naming is updated throughout the interface for the upcoming release. This was an important decision that needed to be made ahead of WordPress 6.3 Beta 1, which was supposed to be released today but was delayed to Wednesday, June 28, due to an unrelated issue. The Command Palette will likely be introduced in blog posts, the 6.3 About page, and countless third-party resources so the proposal urgently needed a conclusion. It’s also to the team’s credit that they didn’t force a fancy marketing name and instead landed on the side of the majority of contributors who were in favor of using clear language. The API for the Command Palette is now public and ready for developers to create their own custom commands. Using a term that is easy to understand and translate will engender more global community buy-in, as 52% of WordPress users run the software in a language other than English. WordCamp Europe 2023 in Athens attracted more than 2,500 attendees from 94 countries, made possible by 112 organizers and 250 volunteers. The event is now looking forward to 2024, which will be hosted by the Italian WordPress community in Torino, Italy, June 13-15. This modern city is located at the foot of the Alps in northwestern Italy and has more than 2,000 years of history to explore. WCEU 2024 is calling for organizers who will serve on one of a dozen teams that have been operating for the past few years, including attendee services, budget, design, sales and sponsors, communications, and more. Those selected to organize will begin planning WCEU in September 2023 and will work with a distributed team on a weekly basis until June 2024. During the 2023 event’s speaker announcements, the WCEU organizing team was criticized for the second year in a row regarding its commitment to diversity. The previous year organizers were called out for the lack of diversity on the organizing team and this year the complaint was a lack of diversity in the speaker selection. WCEU 2023 organizers published a transparent account of the various selection processes used for organizers, speakers, media partners, and others involved in the event. The article states that organizers are shortlisted based on their skills, with an effort “to keep gender parity high whilst also selecting people from all available European WordPress communities.” It also states that applicants’ experience and enthusiasm are chief among selection factors but organizers also reach out to encourage underrepresented groups to apply: During the selection process we don’t have anything that resembles a “positive discrimination” policy, whereby we choose people based on their race, color, background, gender, sexual identity, or any other attribute; we solely chose people based on their stated experience and enthusiasm to be part of the team… Acknowledging that diversity within the Organizing team is important, we reach out to community groups and members before and during the application process, encouraging people to apply where we have historically seen underrepresentation. The article concludes with a statement of willingness to modify this selection process if the organization is not able to achieve a diverse lineup: WordCamp Europe is an iterative event; each year learns from the last and 2024 will be no different. We cannot take for granted that achieving diversity one year guarantees it the next. As a flagship WordCamp event we may need to positively discriminate to achieve gender parity, or fair representation of communities. The call for 2024 organizers does not identify any changes that have been made to the selection process. Prospective organizers will need to fill out the application form highlighting their skills, experience, and desired role. There has always been some confusion and overlap between reusable blocks and patterns. The difference was that reusable blocks can be created and edited in the block editor and then reused in other places – inserted into posts or pages. Block patterns, once inserted, can be edited and are not synced. They give users the ability to apply the same layout to different posts and pages. Reusable blocks have now been renamed to patterns, with the option to be synced, which offers the same functionality as the former reusable blocks where all instances can be updated at once. Non-synced patterns are just regular patterns – those that can be edited independently of other other instances that have been inserted. These updates are coming in Gutenberg 16.1 and will be included in the upcoming WordPress 6.3 release. WordPress contributor Aki Hamano posted a diagram to Twitter regarding the renaming, which was confirmed as an accurate representation of the changes. “Clients already find the pattern and reusable block concept very difficult to grasp,” WordPress developer Mark Howells-Mead commented on the pull request for the renaming. “This change will make things much harder for regular users to comprehend.” Gutenberg contributor Paal Joachim Romdahl commented that it would be helpful to have more time to test this in a few versions of the Gutenberg plugin, as WordPress 6.3 beta 1 is expected this week. Learning materials and documentation will need to be updated with very little notice. Gutenberg contributor Daniel Richards encouraged contributors to see the change as part of “the great unification,” an effort towards consolidating the many different block types into a single concept and streamlining the content and site editors. “In the future it might also be possible for template parts to be considered ‘synced patterns’, and at that point things become much more streamlined and there are far fewer concepts for users to grasp,” Gutenberg contributor Daniel Richards said. “So the hope is that this is a first step on the path to making things easier for users, rather than more difficult. But I do realize that for existing users it’s quite a shift.” As part of this effort, WordPress 6.3 will also introduce pattern creation in the block editor using the same interface that it previously used for reusable blocks. Pattern creation necessitates having a place for users to view and manage their patterns. WordPress 6.3 will also include a first pass at a Pattern Library inside the Site Editor, which will include both patterns and template parts. Gutenberg designers shared a preview of what this would look like a couple weeks ago: In May, contributors began a discussion about the concept of partially synced patterns, which Daniel Richards summarized: Today, when you insert a pattern, the blocks from that pattern are completely decoupled and standalone. There’s no way to tell that those blocks originated from a pattern, especially since they can be edited to no longer resemble the source pattern. Partially synced mode is different. When a pattern that’s partially synced is inserted, it retains a reference to the source pattern. The blocks within the pattern are locked so that they cannot be removed or reordered and new blocks cannot be inserted (this is called When the source pattern is updated, all instances of blocks that reference the source pattern are updated too (much like a reusable block), but the This concept will not make it into the upcoming version of WordPress, as contributors are still discussing one of many complex implementations, but it offers a glimpse of what might be more granular control coming to patterns in the future. Partially synced patterns would bring distinct benefits to many CMS and content design use cases where clients may be editing content. “I am a site developer for an agency, and am actively making sites for clients using Gutenberg every day,” Eric Michel said. “Probably our biggest pain point right now is that the editor does not handle types of content that are mostly standardized with small content customizations per post – things like contact directories, majors at a university, products in a catalog. “For us, the absolute dream scenario is what you are proposing, except with the inclusion of the ability to alter the primary template and have all of the pages that use that template automatically change as well.” The discussion on making partially synced patterns possible continues in search of an implementation that will ensure users don’t modify the patterns in ways that destroy the ability to display the retained content. WordPress 6.3 will ship with synced and non-synced pattern options, and partially synced patterns may land further down the road in a future release. Howdy, It’s been a more quiet week. Many people have been working hard to get the latest features into the next Gutenberg release, so they can also be merged with WordPress 6.3. If you want to start testing, the Gutenberg 16.1 RC is available here. The changelog is massive. Next week, Tammie Lister will be going over this with me when we record the next Gutenberg Changelog. On Friday, I’ll hope on a train to Leipzig and give a presentation to the attendees of the back-to-the-roots, no frills WordCamp. Added thrill for me: it’s my first time presenting in German about technology. Oy. Next week is also WordPress 6.3 Beta 1 release. Get ready for testing and filing bug reports! The best way to learn what will be in 6.3 is by using the beta version and heed the Testing Call #24: Momery Makeover. Testing a new version pre-release, is an open-source contribution with the highest impact. If you are keen to learn how to do it, please let me know and I do a short tutorial zoom with you. This weekend edition seems rather short, too Yours, 💕 Join us for the next Gutenberg Live Q & A July 6th, 2023, at 17:00 UTC Leveraging Gutenberg’s architecture to take plugin development to new levels. Learn how Gutenberg components and scripts can be used outside the block editor to revamp a plugin’s code base in this Case Study of GiveWP 3.0 with Jason Adams, Director of Development, Jon Waldstein, Lead Developer of GiveWP and co-host Lena Morita, JavaScript Developer on the Components team. 🎙️ New episode: Gutenberg Changelog #85 – Gutenberg 16.1, WordPress 6.3 with special guest, Tammie Lister and host Birgit Pauli-Haack In his latest Design Share: Jun 5–Jun 16, Joen Assmussen shares the work of the WordPress Design team on the Jamie Marsland shared in his latest video, WordPress Block Theme Secret Hacks You Didn’t Know Existed, five secret features of Block Themes, you might not know about. Marsland also offers a Block Theme course: Mastering Site Editing and WordPress Block Themes, so you can get a head start. Wes Theron also shares his secrets, too in the tutorial Using the block editor: Tips and shortcuts for efficiency on Learn WordPress. He has eight tips and shortcuts for you to work faster and more efficiently in the block editor. In this video on WordPress TV, Kathryn Presner and Sarah Snow showed their students how to Create a four-page WordPress website: Explore Plugins + Contact Forms. Watch this workshop to learn about plugins–how to find them, how to vet them, what can go wrong–in WordPress in 2023. Another new feature is coming to WordPress 6.3, the Command Center. Be aware that’s only the working title and contributors discuss renaming it. Sarah Gooding reports on the discussion WordPress Contributors Discuss Renaming Command Center Tool. Creating patterns using the block editor has been one of the most requested features since Patterns have been available and since the release of the Pattern directory on WordPress.org in Summer of 2021. It’s now coming to the editor in WordPress 6.3 version. It uses the same workflow as creating reusable blocks. To remind you: create a collection of blocks, group them, and use the 3-dot menu “Create reusable Block” except it now says “Create custom pattern”. Turns out Patterns and Reusable blocks are cut almost from the same cloth. The only difference is that the change to a reusable block synchs over all the instances the block has been used, hence the new name “synched pattern”. There is now a toggle switch to “Keep all pattern instances in sync” or not. This is the first iteration: the name change and the creation workflow. To re-use the pattern, you find them in different places, though. Synched patterns are listed in the list of Blocks in the Inserter and available via slash “/” command. Unsynched patterns are in a new Pattern category = Custom Patterns in the Patterns Tab in the big blue button inserter. There are many users, and I might be one of them, who find patterns, should also be at least partially sync-able. That feature is planned to come to the block editor after WordPress 6.3 is released. It will take a few more thoughts on how to separate the various pieces. You might want to synch the design but not the words, or styles but not the images. The headings but not the links. And immediately you see that this can be quite complicated. So, it might take some more time. You can read up on the genesis of this new feature in the PR Reusable blocks: Rename to ‘Patterns’ and add option to also add a non-synced Pattern. (51144) Ganesh Dahal, also writer at CSS-Tricks, published his first article on the WordPress Developer Blog about The Style Book: a one-stop shop for styling block themes. The Style Book is the new one-stop Global Style feature of the Site Editor that allows you to add all global or per-block design elements with a live preview window. This also lets users create a new set of variations that they can modify with a single click. Wrestling with a huge theme.json might deter people from creating block themes. Petter Walbø Johnsgård developed the npm package @theme-json/create that helps you with that. It allows you to create a logical directory structures to separate out various parts of the theme.json. It makes it easier to maintain and quickly navigate to the necessary area you wish to modify. This way you can standardize variables and reference them in our theme.json, and makes it them much more maintainable when designers decide to make changes. (Thank you to Marius Jensen for the tip). “Keeping up with Gutenberg – Index 2022” In his post for the Torque Magazine, How to Add Widget Areas to WordPress (Block & Classic Themes), Nick Schäfferhoff took a look at different ways to add widgets to your WordPress theme. You learn how to use widgetized areas and create new ones in classic themes, as well as how to make widgets show up in your block themes. It might be the post you have been waiting for. In his post on How to Navigate the Block Editor Handbook, Michael Burridge leads the way with Compass and Maps so to speak. “The Block Editor Handbook is intimidating even for seasoned developers. If you are new to block development, you’re likely to feel completely overwhelmed. This guide will help you find your way around the Block Editor Handbook. It suggests a learning path that will help you become an expert in no time.” he wrote in the excerpt Brian Coords published a tutorial about Custom Lists in WordPress with Register Block Style. He explains how to work with Block styles without a build process. It’s a great way to learn to customize the blocks without any JavaScript and very little php. Earlier this year, Justin Tadlock wrote about Creating custom block styles in WordPress themes, that could be another great tutorial for you. Need a plugin .zip from Gutenberg’s master branch? Questions? Suggestions? Ideas? Don’t hesitate to send them via email or send me a message on WordPress Slack or Twitter @bph. For questions to be answered on the Gutenberg Changelog, send them to changelog@gutenbergtimes.com Featured Image: Skyline of Athens, view of the Acropolis from the roof of the Museum for contemporary art by Birgit Pauli-Haack Don’t want to miss the next Weekend Edition? Really Simple SSL, a popular plugin used on more than five million sites for installing SSL certificates, handling website migrations, mixed content, redirects, and security headers, has added a new feature in its most recent major update. Version 7.0.0 introduces vulnerability detection as part of a partnership with WP Vulnerability, an open source, free API created by Javier Casares with contributions from other open source, freely available databases. Once enabled, it notifies users if a vulnerability is found and suggests actions. “Really Simple SSL mirrors the free database with its own instance to secure stability and deliverability, but of course provides the origin database with an API to enrich, or improve its current data,” Really Simple Plugins developer Aert Hulsebos said. The new vulnerability detection feature is not enabled by default, so users will need to enable it in the settings. A modal will pop up where users can configure their notifications and run the first scan. When emailed about a vulnerability users can manually respond with an action or set the plugin to automatically force an update (when available) after 24 hours of no response. There are other automated actions the plugin can take based on how users configure the Measures section of the settings. For the past several years Really Simple SSL has been providing SSL certificate configuration and installation via Let’s Encrypt as a first pass at securing WordPress sites. To finance this for the free users, the plugin also has a Pro version that handles Security Headers, such as Content Security Policies, which are highly complex for most and not easily configured. “We figured that with our reach we could impact security on the web as a whole, by adding features in order of impact on security,” Hulsebos said. “So vulnerabilities, after hardening features specific to WordPress, was next. “The nature of our partnership with Javier and WP Vulnerability is sponsoring the efforts of WP Vulnerability and appointing a security consultant ourselves to this open-source effort to improve, and moderate the open-source database daily. WP Vulnerability does not compensate us, nor does it have a stake in Really Simple SSL. Vulnerability detection is available for everyone and always will be.” Because Really Simple SSL started as a lightweight SSL plugin, Hulsebos said they have taken a modular approach to minimize impact on users who only want or need certain features. Following the launch of the new vulnerability detection feature, the plugin’s authors plan to add login security with 2FA to better secure authentication on WordPress sites. Last but not least! This is the final episode of our post series about the new direction we plan to take regarding the BuddyPress project. If you’re just discovering this series, we advise you to read about the 4 first episodes of it. This post is finally focusing on the feedback you shared with us here & there about the BuddyPress community & BuddyPress contribution. A new theme for this community website is a must-have, I agree. Although our current theme does a good job, it has remained unchanged for years. We had begun to work on this but in a way that wasn’t in line with my conviction on this topic. That’s absolutely fine with me as long as we ship! It didn’t happen unfortunately, we didn’t manage to attract enough contributor energy. So I’m back with my conviction: we should build the Block Theme I told you about in episodes 3 & 4 with the secondary goal of using it for BuddyPress’ network sites! In my opinion, we’d kill two birds with one stone Ideally, all BuddyPress code should be available on our Trac environment. It’s fine to use GitHub as it’s using Git which is more intuitive than SVN, but at some point (eg: when the feature is stable), the code should be mirrored on Trac. We need a central place where people can open tickets, contribute to any parts of our project and be sure to be rewarded with our lovely contributors badge. Although I believe optional components (or any new Add-ons) should live in their own repository on the WordPress.org plugins directory, I also think they should primarily live into our Trac when it’s about contributing to their code. This way it will be easier for us to maintain all Add-ons making sure they behave nicely with each other when they are all activated. The confusions about where to contribute to the BP REST API experience convinced me that maintaining it on Trac once a stable version has been released (or included into Core for this API) is the right move to make (not to mention the fact I need to explore many different places to credit all contributors to a major BuddyPress release). Contributors shouldn’t be confused about where to contribute to BuddyPress, there’s only one Documentation is very important and, let’s face it, we’re not good at it The first 4 to 5 months of 2022, we’ve tried to organize contributors meetings to update the codex. The results were not at the level of our expectations: I believe we need a Documentation leader We have recently decided to include a docs subdirectory to our main BuddyPress repository. This is where documentation (and its history) will primarily live from now on! This move reflects the fact we acknowledge documentation is as important as code. And we’ll reward documentation contributors just like code contributors with props & a BuddyPress contributor badge on their WordPress.org profile (as shown above). Our support forums is another strategic area we absolutely need to be better on. Some figures about it are very impressive, eg: there are 127,716 posts inside the How-to & Troubleshooting category. Do we still need all these posts? I’m sure we don’t: some posts are probably about very old versions of BuddyPress and can be misleading nowadays. We should archive what’s no more up to date, have a specific tag for resolved questions, get rid of duplicates, etc. There again, I believe we need a Support leader to tackle all manner of improvements and manage a team of support contributors. Last but not least: how do we collaborate about plugin features or fixes? I believe it’s what’s at the root of the 3 last key feedbacks. I can understand some frustrations you shared because I’m feeling the same regularly when it comes to contributing to WordPress code. As a contributor it’s difficult to be pushed back for reasons we do not agree on or that we don’t understand, to see a ticket postponed indefinitely or even worst to be ignored. I personally try to always write a few words in my ticket replies to say « hi, thanks for your feedback » or explain why I’m not sure we should do what you’re suggesting because I value your contribution & I know it’s important for you. We can agree or disagree, we can change our minds, we can take bad decisions, the most important is to act at some point with BuddyPress community interests in mind. We can always act again to revert some mistaken changes. We all learn from our mistakes and I’d rather make a lot of mistakes than stay still. Here’s my advice if you strongly believe we should fix an issue or add a new feature: have it built and share it with us as patches or pull requests. Most of the time doing is half deciding! Yes we currently have a « low number of contributors » and yes I believe BuddyPress deserves more love Oh, one more thing: let’s meet during a BuddyCamp, a BuddyPress online meeting or at least do talk about BuddyPress during as much as possible contributor days or WordCamps! If you need help with your contribution table or with your slides, don’t be shy or afraid: ask us about it here! First: many thanks to @dcavins for his review Many thanks for your feedbacks, it’s a great first step, what about contributing to your ideas with us as a next step? David McCan, Derin Tolu, basicD, Tom Watts, Sander van Dragt, Mr David Hoy, Tara, Jann, Vicent Nemeyimana, Bryant, muhittinsahilli, johnjamesjacoby, ok2net, espellcaste, riversdale1844, djpaul, dimensionmedia, sunsetcowboy, egyptimhotep, staion, shahriar83, unsalkorkmaz, osmor1, giannis4, gomle, fanvid, fawp, coolhunt & imath. If you haven’t visited the WordPress Pattern Directory lately, it may look very different from when it launched two years ago. At first there was an emphasis on getting the community to contribute to the resource but the directory has now passed more than 1,500 patterns. Contributors are making changes to provide a more curated experience ahead of the inclusion of a new Pattern Directory Explorer that is still in progress. A recent update to the Pattern Directory alters the homepage and category pages to show curated patterns by default, a change that has been a bit confusing for some when returning to the directory. The curated patterns are those by WordPress.org – the core bundled patterns. Community-contributed patterns are available as a filter in the dropdown of the directory’s menu. There are only 46 core patterns, so some category pages tend to look a little sparse and far less colorful than when community patterns are selected. At the moment, having curated patterns display by default does not offer the best experience for users coming to browse, as Pootlepress founder Jamie Marsland pointed out on Twitter. Automattic-sponsored contributor Rich Tabor responded that there is still more work to be done on providing a better curated experience in the Pattern Directory. “This change also prepares to support the Pattern Explorer in the editor,” Automattic-sponsored contributor Kelly Choyce-Dwan said in the announcement. “It’s still in progress, but it will be possible to search through community-submitted patterns directly from the editor.” Choyce-Dwan referenced an effort that is currently underway to bring a new flyout to the patterns tab of the inserter inside WordPress, making the modal a place where users can more easily explore and access patterns from the directory. There are also related discussions on how themes could create pattern bundles, enabling the possibility of users filtering by theme. In this discussion, Automattic-sponsored contributor Anne McCarthy suggested these pattern bundles could be automatically submitted to the directory upon the theme’s approval, which would make it effortless for theme authors to contribute them. Updates to the Pattern Directory’s filtering are part of the redesign work on WordPress.org and more discussions are happening on the Pattern Directory GitHub repository. WordPress.com has been known to experiment with its pricing from time to time, and the platform announced another major change today. Users on the Free plan are now able to use monetization features without upgrading. In the past, WordPress.com users who wanted to earn money on their websites by collecting donations, creating a newsletter, or selling items or subscriptions, had to be on one of the paid plans. These monetization features are now available to all users on all tiers. The fee structure varies, based on the user’s plan. Transaction fees are the highest for Free users at 10%, but it gives creators the opportunity to see if they can make money without it costing anything upfront. Commerce plan users ($70/month or $45/month billed annually) don’t pay any transaction fees. Stripe also collects 2.9% + US$0.30 for each payment made to a Stripe account in the US. Self-hosted WordPress users already have many free plugin options to monetize theirs sites but with that comes the requirement of knowing how to maintain and update their own sites. WordPress.com’s offering is targeted at creators who just want to get started making money online. The company is inching closer to being a one-stop shop for websites, especially as it makes a play for former Google Domains customers who are looking for somewhere to host domains after theirs were sold to Squarespace. It’s important to note that creating a full-featured online store is still restricted to Business and Commerce plans. Using Pay with PayPal to accept credit and debit card payments via PayPal is also only available via an upgraded plan. WordPress.com’s pricing page has not yet been updated to reflect monetization features as being free – i.e. the Personal plan still lists paid subscribers and premium content gating as an upgrade. It’s possible the team hasn’t edited that page yet or this may be another pricing experiment. Expanding the availability of monetization features is likely to be received as a positive change, since users are not losing any features that were previously free. Instead, they have the opportunity to see if they can monetize and then adjust their plans based on their comfort level with the transaction fees extracted. Up until yesterday, the Gravatar (Globally Recognized Avatar) blog lay dormant for nine years, the last post chronicling how the team set out to create a Gravatar app that somehow “morphed into a Selfies app.” Communication went silent after that, although the Twitter account posted occasionally. The service has pivoted to become “a personal digital business card” where users can link to various apps and websites that help to establish their identities online. Gravatar announced this week that it has launched new payment features for profiles. Users have the option to add links for PayPal, Venmo, and Patreon. The Gravatar team is looking at adding Cash App and more providers in the future. On mobile, profiles appear with new “Send Money” and “Share Profile” buttons. Each profile has its own unique QR code that can be copied and shared. The payment accounts show up as links that visitors can click through. Users can also display links to cryptocurrency wallet addresses, including Bitcoin (BTC), Litecoin (LTC), Dogecoin (DOGE), Ethereum (ETH), XRP, and Cardano (ADA). Profiles can be customized with a background image, photo gallery, social links, and links to verified services. Automattic reported that the company does not receive a cut of any payments passed through Gravatar links, nor does it have financial partnerships with any of the payment providers. The company also has no visibility into the transactions that happen through Gravatar payment links. During the past nine years, the small Gravatar team has been improving how profile pages look, adding services that can be verified, working to improve the hashing and security of data, and maintaining the infrastructure required to store and serve so many images and profiles. “We aren’t currently working on a Gravatar app, but it is something we are considering,” an Automattic representative told the Tavern. After the Selfies app was retired, some of the code went into Jetpack and is now part of the app. Jetpack users can manage their Gravatar profile information and avatar photo inside the app. Woo AgencyChat Live with Jimmy Rosén and Shadi Manna June 22, 2023 Transcript Shadi: Here we are, the agency chat interview with Bob. Thanks for inviting us. My name is Shadi Manna from Progressus.io and... Jimmy: And I\'m Jimmy Rosen from Angry Creative. Shadi: Where should we get started, Jimmy? Jimmy: I don\'t know. How … Woo AgencyChat Live with Jimmy Rosén and Shadi Manna Read More » >> The post Woo AgencyChat Live with Jimmy Rosén and Shadi Manna appeared first on Do the Woo - a WooCommerce Builder Community . Corey Maass and Cory Miller continue the development of their new WordPress plugin, Crop.Express. In this episode, they discuss the importance of finding personal fulfillment, embracing the journey, and enjoying the process of pursuing hobbies and personal projects. They encourage everyone to reevaluate their definition of success and find meaning in the act of creation while also cherishing the connections and collaborations that come along the way. Top Takeaways: The Post Status Draft podcast is geared toward WordPress professionals, with interviews, news, and deep analysis. C&C 18 [00:00:00] Corey Maass: And don’t forget to record this time. Yeah, no. [00:00:23] Cory Miller: Excellent. All right everybody. Welcome back to Corey and Cordy launching a pro WordPress product live session 18. And we’ve had, we were just kind of in prep for this real quick, just talking about a little of the things that’s been going on in our lives. It’s always fun to talk real life with a great person like Corey. So, um, this time we’re just gonna kind of talk about catching up. We’ve been out kind of the last two, maybe three weeks I wanna say. Yep. And, um, I have been on, uh, uh, last week I was at CLOUDFEST in Austin for post status. Then we extended and went on a Epic Clark w Griswold type. Um, Road trip. Got to see Carlsbad Caverns. Um, and, and they were closed. Yes. No, dead ants on the roof of the minivan. When we did render vans, I had to go Griswold South. Um, but I know you’ve had things going on too, so, um, that’s a little snippet for me just trying to kinda get things a little bit better sane for me work-wise. And, um, I think that’s in preparation for the. Real conversation here, but um, you wanna Yeah. Updates on what you’ve been [00:01:36] Corey Maass: up to. Yeah. And on my end, so it’s, I’ve, so I’ve got, you know, one, one main client and, uh, I have a monthly. They, they ask me to stay within a window of, of how much I work and what, uh, what I actually like about that is I tend to work a little less the beginning of the month. Um, and then, uh, which lets me work on side projects or lets me work on the house or whatever. Uh, Um, and then towards the end of the month, you know, the days get longer to make sure I hit my quota, um, and maximize my budget. But, um, so at the beginning of the month I wound up helping my dad drive from South Carolina up to Maine, um, which is a really fun road trip with dad. But, you know, and of course the, the client website goes down when I’m the farthest from my computer. Uh, you know, sitting at a restaurant in, uh, Fredericksburg, Virginia, if you ever have the opportunity, it’s a beautiful little place to stop. Um, but anyway, and then you can probably hear from my voice. I think last week I begged off because I was sick as a dog. Um, And it’s funny, it actually, you’re like, oh, it’s been I think two, three weeks and I’m like, it feels like it’s been months. Cuz I spent at least, uh, a few days last week. Literally just in bed in a NyQuil haze, you know? So it felt like weeks went by and, um, you know, and then you come out of that and you’ve gotta scramble to make up work and, um, get caught up on life. And, um, and then for me time, um, Always means house projects. So we’ve built another, uh, 11 times eight. So 88 feet of fencing. No. And then we turn a corner, so about 120 feet of fencing, stockade, fencing, cuz we’re getting a new foster dog. Um, and uh, so setting up a room for him and anyway, yeah, it just gets crazy. And, uh, and so I think you and I touched. Space briefly last week and, and said, okay, so, you know, that’s fine. We missed a week or two. Let’s, let’s start, um, moving forward. I was like, all right, you know, I’m still working on a review of, uh, the product. I’ll get you a new version for post status. I don’t think you heard from me until nine minutes ago. Uh, that never happened. So, yeah. You know, but it’s like, and I hate to. It, it’s easy to fall into like, well, it’s not out yet, so it, you know, there are no expectations other than our own. Yeah. Which is true. Um, you know, but it’s also like, I mean, this is, this is part of why we do this, right? Like, yeah. We’re, we’re at least part of our, our aspirations is, is freedom, uh, to make our own choices, to manage our own hours, to work on what we wanna work on. Um, which also means, I mean, family comes first and health comes first, and Yeah. You know, and, and paying clients come first when you’re at this stage. So, you know, these are just things we have to juggle and, and keep trying to make progress. I mean, it says everything to me that. You and I at least are like, okay, let’s keep talking once a week. Where are we at? You know? And, and cuz I have other people who I’ve worked with who many, many other people who, who ghost or who just wanna stop. There’s, there’s inherently so much shame in all of it that the moment they miss a day or a deadline or don’t hit the mark in some fashion, don’t want to talk about it. You know, I have friends who we’ve been talking about, Collaborating for years talking about like music or art or whatever. And, and now we, we, we’ve gone months where we’ll talk every week or every month, you know, how are you, how are the kids, da, da da. And we literally won’t, we won’t talk about the subject now because there’s, you know, because we didn’t, one of us didn’t move forward with it. There’s shame associated with it, so, you know. Definitely none of it’s that important, you know? [00:05:56] Cory Miller: Yeah, exactly. Like we started with really good intentions and openness. Um, what it occurs to me is just kinda your references back to music and bands and stuff is like, I’ve not, I, I played an instrument when I was in like middle school, but I’ve not been in a band, but it’s occurs to me. It’s like, it seems like that you’re, mm-hmm. Stru, you know, struggling to kinda get something going. And then there’s seasons of life that happened. Um, this, this stage of my life and my career, I really see more of the seasonal aspects of life. Yeah. Better than I ever have. And you go. You know, just things you don’t, you can’t anticipate, or if you tried to, you’d have another set of problems. And, um, it’s just like you said, like we’ve got other priorities, but, uh, it’s important for us to keep talking. I, I think too, when I think about entrepreneurship, I think there’s like part real hard work just doing things, trying to do it consistently, getting things out there, getting the next thing, and then there’s this bigger part. Which is, maybe somebody would’ve called it luck, you know? But it is like magic. You know? You stay around doing something. Maybe bands operate like this, I don’t know, but like you, you got enough interest, you know something’s there, you just haven’t figured it out yet. And then a magical moment, and I say magic cuz it’s like oftentimes in my career, specifically my professional career as an entrepreneur couldn’t have planned those things, man. They just happened, you know? Um, however, I might have tried to take credit for them. They just happened and it’s like the reading I’ve been and work I’ve been doing too personally is like creativity. You don’t control creativity. Those really magical moments we’re talking about, they kind of blossom out. And there was somebody I was just like, well, Anna, who runs feeder bars, Lindsay and her have been friends for a decade, you know? Anna tried so many things over the years, so many things, and then Vita Bars was the spark, the magic that made it happen. Mm-hmm. Now, now she’s full-time with it and she’s got employees and all that kind of stuff. So like all that time it’s kinda like learning the piano. People go, oh, you’re at the piano. You’re doing this beautiful thing at the wedding, or whatever it is. They don’t think about all those years spent. Right. You know, in the practice of it, and it’s kinda like that moment too. It’s like, I’m dribbing for a second, but do enough things to get to a moment that, that you probably didn’t plan. I think most of us, at least the entrepreneurs I know would say. Yep. That’s about it. Absolutely. Yeah. However, we like to think we control it and plan it. We don’t. [00:08:59] Corey Maass: And there’s, there’s time. Sometimes you, you, you ha you just have to let time go by. It’s like, in music, it’s one of the hardest things I’ve, I’ve had to learn. It’s like for years I made music and put out music, made music, and put out music. And then I actually started writing music that people were like, oh, this is a summertime song. It’s the end of the summer. We’re not gonna put it out now. That’d be dumb. So we’re gonna sit on it and you, and it’s like in actual pop music, you can find out that there, there were pop songs, but huge, huge hits. And in our minds, you know, you’re picturing, you know, Taylor Swift yesterday was in the, in the recording studio and then today you’re hearing the song cuz that’s cuz music can be live. Um, and in this day and age, sometimes that’s true and it’s a truer than it used to be. It used to be that, you know, a band would go into a studio and produce an album and it would take months and yada yada, you know. But a lot of the times thing, tunes or tracks or albums are actually held back. To try to be released strategically. It’s like big movies that sit on shelves for, you know, years potentially, because they’re like, this is a Christmas day blockbuster, we’re not gonna release, you know, or a summertime when all the kids are outta school type of movie. You know, we’re not gonna release it on the second day of school on a Tuesday. That’s dumb, you know? Um, but we don’t, we don’t really think about that, but, There’s sometimes there’s strategic reasons and sometimes like this where it’s like, I’m a lot better about it than I used to be, especially since, um, years ago now. So for a while I tried to make music an actual career or second career, um, and it really broke my heart. And so I stepped away from it for a while, and then when I was getting back into it, this is where having an amazing spouse is worth everything. Lindsay and I sat down, my Lindsay spelled with an A, sat down and, and she’s like, okay, so you, you know, you wanna get back into music. Great. Like, how do we, how does it not break your heart again? And one of the things that, that. Came outta that conversation was me being able to articulate like, okay, I’m not taking it as seriously this time, it’s a hobby. Mm-hmm. And, and so suddenly a lot of things changed. One, you know, I couldn’t just go out and, and buy new instruments or, you know, throw money at it the way I used to. Sure. But it also meant that like I could work on, like, I have found that I make a lot of. Music in the fall and then tend to not make any music, but it, but a lot of that music that I finish, I can like leak out again, a track a month or I can wait until summertime and put it out or whatever. And so it’s like I’ve got these big waves rather than it just being, you know, picturing this straight line of productivity. Um, and I think it, that kind of goes for this, this stuff too, like, This stuff. Uh, entrepreneurship side hustles. They’re, they’re side hustles. And for a long time I, I was like, I want this to be a day job. Still would love it. I’d still love my own product to be my primary focus. Then it’s a job that’s very different, right from, um, side, side hustles, um, ideas, putting out little apps, little ideas, um, little products. I mean, um, so. And so it’s, it’s picking things up, putting things down, um, and, and these days being okay with, again, letting some time go by or occasionally changing priorities even for a, a little while. Um, cuz there was a time when. I remember one time in particular that I was like, I was in between paying client gigs and came up with an idea [00:13:00] for an app and was like, okay, I’ve gotta crank this out and then it’s also gotta make money. And it was like the dumbest little idea. I won’t even share it, I’m embarrassed. Um, but it was like, it was an app that nobody wanted, you know? It solved a problem that nobody had. It was just an idea. But I remember like, Going, this is the first time where I, I, it has to make money. And I was like, it’s never gonna make money. Like, and I’m, so, I’m putting myself in danger here. That’s dumb. You know? Um, and that’s not to say that there aren’t entrepreneurial journeys. With VC capital or, you know, we’ve gotta double down and, and make this our full-time gig and all that stuff. But it’s like, at least for me, I find often that I’m, if I’m making decisions from a position of desperation, of, of need. That I’m not gonna make the best decision, you know, cuz my priorities, I can’t have any, I can’t have proper perspective on it. So, stepping back for a few weeks, honestly, what I look forward to is going back into my code, realizing that I did everything wrong and cleaning it up and then it’s a better product. And, and you know, are we the worst off for having missed a few weeks? Maybe. Who can say nothing’s obvious? Um, you know, but again, you know, just trying to keep moving forward with it. [00:14:19] Cory Miller: I think it’s like when we’re thinking about bands and hit music or products and entrepreneurs think about, you know, with or, and Anna and yours. My experience in this is like, If there’s enough of a fire to keep it going. Mm-hmm. You know, just enough. It doesn’t have to be a bonfire. There’ll be times of that for sure, but, but then mostly it’s probably just. Sometimes a little candle, sometimes just a little mini campfire. But if there’s enough in fuel in there that there’s something here. I think time is on your, like you said, as time goes by, time is on your side because yeah, it’s only a matter of time where th where things kinda move and shift and the, the market, the world where you’re like that. Some of the classic stories, the person I’m thinking of, I think it’s a product company and how it came out. It’s just a recent example, but the classic ones were in Founders at Work where you almost stumbled into, backed into what became the hit thing. But you couldn’t have kind of planned that. Right. Um, where you were just keeping on a path enough, knew something was here, didn’t thought you had a beat on it a couple of times, and then just really it was just. The fire was stoked long enough where something did really hit and it became this, it, it became its own thing, I guess. Yeah. Lot of the, and I’m not, go ahead. A lot of the entrepreneurial stories I hear, they aren’t like the VC route. We saw a big market and we went after and we got a big money. Uh, that’s a, that’s an outlier I think, um, for the, Millions of us, the rest of us, I think it’s mostly backing into something, staying around long enough to find the opportunity that really fits. [00:16:09] Corey Maass: Yeah. Chipping away at it, having, having fun with it, working around real life needs, family, money, mortgages, healthcare, you know, that kind of stuff. And it’s like, and that’s kind of the difference. Like I, I have friends who I. Are, have always wanted to do something. And I’m like, so outside of their job and, and so I’m like, so do something, you know, talking art, music, entrepreneurship, whatever. And it’s like you just, you, you, you have it in you or you don’t is one aspect and then the timing is right. Where it’s like you have that drive and you look around and you’re like, okay, right now I’ve got a couple hours a day where I’ve got. Whatever commitment you need, you know, to work at it. And so, um, and I think you and I also, I mean this is, this is the warm and fuzzy moment, but it’s like you and I also I think, have looked for an opportunity to work together for a long time. So it’s like we will continue to be friends and, you know, hopeful partners in something kind of always, you know. Yep. Um, I do have to say that. We have to keep the fire burning at least long enough to, so that I get to rock the swag at WordCamp us. That’s true. These are the, these are the real important things. [00:17:40] Cory Miller: Um, yeah, a absolutely. I know. Um, no, and I think that’s the other part on, down to this is, you know, at the base I enjoy our conversations. It it, it’s this hot, crazy hobby we might have of. Seeing what’s out there, seen, seeing something following the path down it. And, uh, I still believe in the product. Yeah. Um, but it’s funny, it’s like I believe in the product, but I also believe in the path that might lead to something else. Yeah. Because, I mean, well, we’re on our second iteration of a product. Like, not even same product, there’s similarities. Mm-hmm. But like, we went down this path to here and I think it just adds to the ongoing conversation that we’re having is something’s gonna happen. Yeah. And then there’s a flat, simple, practical byproduct. All of this is that we’re having a conversation live and sharing our philosophies, sharing our thoughts, sharing our actions, um, all these things that has another byproduct that could lead us in another direction altogether, which is good. Yeah. Yeah. You just say from a professional opportunity standpoint, [00:18:53] Corey Maass: right, exactly. I mean, it’s the part, being part of the same network overlapping concentric circles. Um, And, uh, and kinda seeing what comes out of it. Cuz the other, I think the other thing I’m, I’m thinking in from the perspective of somebody who’s listening, who’s like, right, you, you know, you are both established. You have, you know, other income streams or you’ve got your networks, you’ve, you know, and, and you’re also putting a product out there. Like, I still see people on entrepreneurial forums that are like, you know, somebody’s gonna steal my idea. And, and we have gone the other direction and, and obviously we’re not the first, but, um, of, you know, just brazenly putting it out there and taking our sweet time. Let’s be honest. Like if we were other people, if we had venture capital, if we, you know, Didn’t have, you know, responsibilities and mortgages and things like we’d eat ramen and we’d have cranked this thing out years, uh, months ago. And, um, and there’s absolutely the chance that somebody listens and goes, oh, that’s a great idea. And, and comes in and, and, Steals it and releases it before we do. Um, you know, but it’s still, like you just said, it’s all part of the journey. We’re going to put our own twist on it. We’re going to put our own experience on it and, uh, and continue to iterate on the project, the product too. So when the product does come out, like it’s very much ours. And it might overlap with other people’s, but frankly it already will. Like, that’s the nature of. Pretty much any product. There’s no, there’s, there’s really, you know, almost nothing that hasn’t been invented. Um, and I also, another, uh, thread I saw recently again on, um, I think it was Reddit, one of the entrepreneurial ride along, or, or one of those subreddits, um, That people were concerned about not having an idea. And everybody else was like, just you, you don’t, you know, okay, don’t, don’t steal an idea and reproduce it. Like that’s boring. But you know, if you can build the better mousetrap, if you can build the better to-do list, if you can build the better time tracking app, uh, you know, whatever, do it. Like, that’s how most. Competition starts as, as these pretty subtle little differences. Um, and then you listen to your users, you listen to your own gut, and you end up di I feel like you end up diverging more and more and more. Um, you know, and or you’ve got, you’ve got a network that, that you can tap into that existing client or existing products can’t or whatever. So, um, You know, it’s all, I guess I, these days I view it, I view it as kind of as a game, which is more flippant than it probably sounds, but it’s like you’re wheeling and dealing, but there’s times when you win and there’s times when you lose. God. I’m being very metaphorical here, but, um, you know, but it’s the, the. I view it as an ebb and flow, which is, uh, again, I think for me the, the way that I had to phrase it a while ago was like, this is a hobby. And, uh, and so it’s, it’s meant to be fun. Um, and that isn’t to say that everything we do has to be fun cuz, and, and, or that I don’t take it seriously, but, um, but it gives you, I think, a little more perspective. You don’t have, I don’t, I don’t have board members that I have to, or, you know, or stockholders that I have to appease. Um, And I don’t have, uh, you know, I don’t have to burn the, the, the candle at both ends, um, to make ends meet if there’s a bug. And I’ve got users that are depending on me, that happens with my apps or my plugins once in a while, but it’s honestly like once in a while. That’s fun. I don’t wanna do it all the time, but it’s like, oh, I’ve gotta do a little hackathon and, and you know, figure this out until 2:00 AM cuz a bunch of people are depending on me. That’s fun too, you know? So, [00:22:45] Cory Miller: Yeah. It occurs to me it’s really a low pressure and stress for us, which is what we both need. Right. Um, having a little bit more, I mean, I guess that’s the definition of a hobby, right? You know, enjoyment without the stress and pressure. Yeah. When it switches from hobby. Oftentimes it counts with stress and pressure. Yeah. [00:23:08] Corey Maass: Well, and and it’s interesting cuz like I, I worked at startups, you know, it’s like I’ve done, I’ve done a lot of work in WordPress, um, and there’s been a lot of overlap. But I also, for a long time specifically was working for and with and at startups, um, of different natures. Um, and some of it was WordPress work and some of it was not. But there, there, and I was in New York City for a long, long time, um, so-called Silicon Alley. Um, during the WeWork stuff, I think I’ve mentioned that before. You can actually see me in the WeWork movie and, um, and all that. And I was surrounded by people who were hustling all the hustlers and, and all that stuff. And it’s like, Most people were chipping away. I mean, almost like, like almost anything. It’s a, everything’s a bell curve, right? So most of the people on the bell curve were just chipping away, you know, and they weren’t burning themselves out, but they weren’t also only working a day a week or something. And you had people who were working very, very hard. And you did have people who were there just for the lifestyle and honestly spent all day just playing ping pong. Um, and were there for the beer kegs, you know? Um, But working at different startups, like I’ve worked at startups where it was all hustle, hustle, hustle, and we’ve gotta put in long hours. And, um, and I, I found that I got out of those pretty quickly in part because I would, would burn out. Um, and I think it would be different if I had been in charge. Um, but like the one main startup where I was CTO was. Um, I think there’s a cultural difference here. Um, but it was in Nashville. It wasn’t in New York. So there’s, um, there two things were different. We were not in the hustle bustle of New York City. Nashville’s a little more easygoing. Um, but also we were generally all, you know, in our thirties and older, we weren’t all a type. Hustler entrepreneurs. Um, and then, uh, stereotypically, uh, down south you’ve got family values are, uh, or at least the family itself is prioritized higher. And so we, there, we absolutely put in some long days, but for the most part it was. A priority of the founder and subsequently everybody else on the team that, you know, you wouldn’t, if it could be done tomorrow, if it was five or six o’clock, then fine. Do it tomorrow. You know, keep chipping away, make good progress. But, um, you know, but you didn’t, we didn’t have to burn ourselves out. Uh, we weren’t gonna really get anywhere by burning ourselves out. And, and we did just fine till we ran outta money, which happens with startups. Um, you know, but it, but it doesn’t, it doesn’t always have to be that crazy atmosphere. Yeah. I, I [00:26:02] Cory Miller: can’t help but think there’s a shift going on globally too, with work. [00:26:07] Corey Maass: Um, what, sorry, what, what was it like at, like, ithe or, you know, some of the, the bigger places you’ve worked? [00:26:13] Cory Miller: The biggest place I have been be beyond like liquid web would be, um, I was at a seminary and I think there was 150, 200 people employed by the seminary. Maybe that it’s too much. No, I actually, there’s a hundred, 150, um, that, that was just a very academic setting, so it was money, always money. So, Um, I loved it cause it was a learning stuff, but as far as like in the past, um, you know, I worked at newspapers, so it was always deadline. I think it was more startup, you know? Yeah. Very much startup. Except every day we were launching a new product. [00:26:58] Corey Maass: That’s, that’s insane. [00:27:00] Cory Miller: Which I think is why I probably liked entrepreneurship is just the deadlines and product is, it was so fulfilling to come. At the end of the day. But as far as values and stuff goes, I think I learned more in my leadership from what the not to do what I didn’t like, the obsession with whatever the goal was at the expense of people and just realistically, like what are we expecting people to do? You know, I could, my truck. Get it all, get it up to 150 miles per hour and get into the red line, then it’s eventually gonna break. And I don’t think you can do that. We try to do that with people. Um, but I took a lot of those lessons leadership wise. I had, um, probably some things I go, I’m not gonna do that ever. My last job before I started iThemes, um, I worked for a really amazing pastor. The one that kind of refreshed my optimism that. There could be one who at the time, the way I understood the Bible was be just a shepherd. You know? Um, he was really awesome. I really, I, I took his archive as a leader into, into I themes or eventually when we grew on our team. But you’re right, the first, first couple years, um, it was just fun and new. It was creating stuff. With hopes and dreams and thoughts and ideas and, uh, it was messy. Um, it was messy, but we got to do some cool stuff. We did like create an office that eventually grew to about 5,000 square feet and got to, like, my dad actually drove up. From about two hours from where he lives from us and came and helped me, helped us demolish some of the walls that were up at this place. Cause we wanted more of that bigger open thing and we went to IKEA and get all the tables. And I think about all that initial time, very romantically, very affectionately, because it was just, we didn’t all know. We didn’t know what we were doing. I sure as hell didn’t know what I was doing, but it was fun creating something that. What would our expression look like? And so I would say for the first three years it was just kinda hanging on and having fun with, yeah, doing some real stuff. Um, there was electricity in the air and uh, with a whole set of problems that developed out of that. And then I think when we hit about a million in revenue, I couldn’t manage the team by myself. Um, we were up to at least 10 people by that time and. I think things got more serious and probably professional, um, in the sense of, okay, you know, we, we had health insurance probably I think our first year. As soon as we hired the first couple employees we needed to get health insurance type of thing. And uh, but I think that year something was different is like, we’ve got something here. Yeah. Lining in the bottle. Let’s figure out how to protect it, grow it. Maintain it. And um, and so we needed some of the structure in there. Um, my value as leader though, was always, like, I did a talk early on. I was like, I wanted to build a tree house. I wanted to have a tree house, and I wanted to invite all these cool people to play with me in the tree house. That’s what it was the first couple years. And, and some really good stuff came out of that. Um, you know, we didn’t fall out of the tree house and break her arm. Um, mostly, and then it was, it was shifting of like, holy crap, like look at this thing, we gotta figure out that. And then, but when it really serious was toward the end when it was like, oh, there was more children of our employees than there were employees, and that was responsibility barrier. And then it’s like, house gets a little serious, you know? Yeah. [00:31:07] Corey Maass: That’s interesting. Um, [00:31:11] Cory Miller: so yeah, I’m. I look back at that time very fondly and nostalgically. Um, cuz I remember it was toward the end of the year. No, it was after the first of the year. And I got invited to be in, uh, entrepreneurs organization and said, well, you need a million in sales. And I remember going to our accountant like in January and going, okay, where do we hit? And we were like, $70 over a million or something. And I thought we did it, but here’s how weird it was. More treehouse thing is like, That money didn’t flow directly to me. That was, I wasn’t swimming in the lap of luxury or anything. It was like that childhood c childish feeling of I get the high score on Gallagher. Oh wow. We did it. We did it. You know, and, uh, [00:32:00] but what’s, what’s crazy related to the whole entrepreneur journey is I think that was probably, I. Those circumstances and timing and backing into that was just ideal, obviously. But I go, it wasn’t all luck, right? It was both. It was all luck, all hard work. You know? It was both. Um, cuz I’ve since then tried to recreate the magic experiment, you know? Yeah. It was cool. My partner came in, I think it was our first year, we had our first office, and I would buy these, sorry, I’m these plastic tables from Sam’s Club. Mm-hmm. Basically picnic tables, you know. Yeah. And I was like, these are our desks. I held onto that for the longest time until we got our next office. And Matt was like my co he was like, Time to time to probably upgrade from the white desk. And I was like, no, I don’t want to. I did eventually. Um, but I think that was part of that magic right time, right place, right? People were partners, right. WordPress. Um, but it, I that those conditions were really conducive to creativity and magic and pulling. People were pull. Pulled in to that, like Christine was one, um, I think it was our second or third team member, man, changed the change, solidified the entire direction of the company and. Um, huge, uh, different people like Dusti Bolton, Matt Danner, and Kristen Rutten, and different people that poured into our orbit. I go, wow, this is cool. So like when you talk about band, I go, that’s what my band was. Mm-hmm. Because it’s just like, we just made really good music for a long time. Yep. Uh, but how do I recreate that? That’s been the obsession for the last five years. Uh, until I just go, that was done. That was there. Yeah. That was album. I laid, we laid, excuse me. And it’s on to new music, right? [00:34:03] Corey Maass: Yeah. Or yeah, arriving at a different thing, different voices. You can’t just recreate the same thing. Music’s always the perfect metaphor in, in entrepreneurship, ownership and programming. And I think there’s a reason why so many of us are into music or are musicians or whatever. Um, but yeah, and I think that’s, That’s what a lot of, like, I, I was really into all the entrepreneur stories for a long time and I’m glad I listened to a bunch of the podcasts and, you know, and whatnot. But you can’t recreate somebody else’s story can be inspired [00:34:44] Cory Miller: by for sure. [00:34:46] Corey Maass: Oh hundred percent. A hundred percent. And, and, and some of it is good advice or, you know, in certain situations you’re like, oh, you know, I remember this thing. It’s like, like reading a playbook, but you still have to know what plays to apply or whatever. [00:35:01] Cory Miller: I, so when I le met Lindsay and in like 2010, which was that year, we hit a million, um, we started this thing that, um, was called Startup Sofa. [00:35:13] Corey Maass: I’m sorry, I’m laughing because you know, you’re, She’s clearly in it for the money. Um, you know, yes. That year, you know, you were walking around being like, uh, my company just turned a million. You know what? Beautiful women want, want, want me now? She, she, [00:35:30] Cory Miller: she remembers. She goes, no, you know, we were dating when. You hit your first six figure month. And I was like, Uhhuh, I realized everything got better with you. It did. Um, that’s the other way [00:35:44] Corey Maass: she sees it. The she sees it the other way around. Yeah. [00:35:47] Cory Miller: And it. And honestly, candidly, it did, everything did get better when you just had some like, like while we’re doing this together, not apart, right? It’s right. It’s just better together. I’ve said that with post status. All the other things, it’s like, God, as much as I want to think I’m a solo act, I’m really not. Well, I’m much better as a collaborator. Um, oh, so we started, I started this thing called Startup Sofa, um, and tried to share all these things I had learned. I was laughing, telling her that, and I said, I was two years into this thing and thought I was, I could share, I do believe there’s a point where if you’re like one step, two step ahead of someone, sure it’s very helpful. It’s very good stuff. Like this is where I’ve got, uh, but I started laughing. I go, cuz now I try to share less. I really actively try to not give advice as best I can until I go, okay, now it’s time for advice. I just share experiences cuz I go right. Everybody I hear doing that and you’re like, how long have you been doing this? All right. Have you been doing it exactly the way they have? Do you know their dna N do you know their company? Do you know the mix? Do you know the environment? The answer is no. Very few bands lose their cover singer and have can just plug in another person and know, I think Queen is one of them, but you’re like, it’s very hard to, the magic is that band, those people that time to [00:37:12] Corey Maass: do that. Yeah. Yeah. And I mean, you can’t, and time is is the other, is the other thing. It’s like you can’t, you know, I’m, I’m stuck in that a little bit with music. It’s like I am, I am getting better and better at making a genre that basically died 10 years ago. I do it cuz I love it. And again, I’m, I’m, there are moments where I’m like, uh, these other genres are more popular. I would get more airplay if I switch genres again cuz I switched genres. Like I rode a lot, the wave of, a lot of genres for a lot of years and I was sincere about it. I wasn’t, cuz I, I’ve never made music thinking that it was really going to get popular or what have you. Um, But now I make the music that I love the most and nothing else has come along that I love more. Um, but, so if you’re the perfect band, but you’re making seventies rock, uh, you might have a hard time if it sounds too much. Just like seventies rock, you know? Okay. That’s [00:38:15] Cory Miller: so good because then I go, there’s this other part to the whole magic is that you want magic to happen. Probably some baseline passion, desire, interest for you. Seventies rock music, right? And I go, well, as time goes by, everything works in cycles. We know it might be dead 10 years ago, but it could be alive 10 years from now. And you’re like, oh, it’s those people that I admire very much, Corey, that have their interests and desires and passions and don’t. Stop. Mm-hmm. There’s some little fire of that in what we’re talking about while we keep showing up on [00:39:00] Wednesdays. But I really admire it because I go, those are the people that, that something is gonna happen. It’s probably gonna be better than what they imagined. Not what they imagined, but better. And, uh, I go to like seventies music. You said it just so organically. It’s something I, I like probably not gonna stop and then I go, well, if you stay around for another 20 years, Doing that, something’s gonna happen of that. Right, [00:39:25] Corey Maass: right. I mean, that’s been proven over and over again and it doesn’t happen for everybody. And I’m, I have, you know, there’s, there’s two thi, two things, only two, there are at least two. One, one is persistence, um, doing what you love. And, but again, this is where, and for me it had to be. Calling it a hobby, you have to make your peace with it. I think that’s the bigger, uh, the wider way to describe it is like there are people who are session musicians, you know, there are people who are, um, who will try to ride each wave to make the next, you know, hit song based on what trends are now. Um, there are people who would just grind. Um, Derek Sives talks a lot about this. Yeah. Um, love his work. And, um, you know, and, and, uh, and he’s a good example. And other people, uh, who are like, okay, well I’m going to, I’m gonna do other things to, you know, to pay the bills, but, uh, my passion lies over here. And, uh, because it’s my passion, it will, I will always keep chipping away at it kind of thing. Um, but I think, so that’s, that’s sort of one line. And then there’s another line, which is time and perspective and, um, Because you talk about good things will happen to them eventually. Right? And so it’s like I, for me, part of that I think can be the lowering of expectations, uh, which sounds so old and cynical and beaten down, but it’s like I get more out of. Smaller things musically, like again, I’m, I’m, I’m getting older and older. The likelihood that even if I got a song that blew up, am I gonna tour on that at age 46? I also, I generally make music that that’s popular in England and so am I going to tour in England at age 46 and I can barely stay awake past 10:00 PM Am I, am I really gonna go DJ gigs at three in the morning? No. You know, uh, and so managing, managing expectations and it’s like I’ve, but I, and being content with, uh, a little bit of airplay here and there, or the people who, uh, I’ve now been friends with for. You know, decades coming to me and saying like, this is the best song you’ve ever written. I’m like, that’s enough. Like, I don’t, you know, yes, I would still love, you know, uh, endless BBC airplay or something, but the li the likelihood is less. And so it’s the, uh, staying consistent for me. Staying consistent, plugging away, doing what I wanna do, but then also being more and more content with, again, smaller wins. Um, cuz it’s like there’s, yeah. You know, it’s hard not to like, um, I am reacting to what you just said of like going, there’s a lot of entrepreneur advice that, that the entrepreneurs that I was following, like for years I wanted to go to, um, Rob Walling and, and Mike, they do startups for the rest of us. Um, and they do a conference, MicroCon. Yeah. For years I wanted to go to MicroComp and, and then it, and, and I went to businesses, software, and some of these that were, I. Like only a few of the talks were relevant to the very, very bootstrapping I was doing. Um, and now even MicroComp, I mean, and years ago they split into two tracks. I don’t know where they are anymore, but the last time I looked, and this is no criticism of them, it’s just like I never. I never was able to go up, up, up with all the other people that were going up, up, up. And so then they were all, you know, you, you were, you mentioned being a couple of rungs ahead of me. They were ladders ahead of me. And so it stopped being, um, pertinent. Um, and I also took my foot off the gas and, and aimed a little smaller. And again, qualifying more the more side hustles and, and you know, uh, and stuff like that. And so it’s like, I struggle, I go back and forth, right? Pride at the end of my life, I, I would love to have owned a gajillion dollar company, or more importantly to me, honestly, would be to have a gajillion user product. Um, cuz it’s just more fun, frankly, and, and presume that money would come out of it and stuff like that. But it’s like, what are my, what are my actual goals? Like, why at 46 do I code extracurr? I, I, it’s a hobby. I love it. Okay, but what, what are the goals? You know, are there still goals? Am I still trying to earn millions of dollars? Like what is, it’s like I always, I always talk about, um, I don’t know, I, I don’t actually know anybody who makes canoes, but I always talk about, Uh, the, or I love the idea of a person who, cuz I think I, it’s the most frivolous thing I can think of. Um, and that’s that, and I don’t mean that negatively, but as a hobby, like in your garage, taking up most of your a, a car bay. So one of your cars probably has to be parked in the, in the driveway so that you can make a canoe. I guarantee you don’t need a canoe. And, and the world doesn’t need another canoe. There are canoes that you could go buy, probably get one for free because everybody buys a canoe and then never ends up using it. That’s, at least that was me, my family growing up. Um, but anyway, it’s like that to me is the epitome of a hobby. It’s pure love. Absolutely nothing in the world needs or requires or even probably encourages you to build a canoe, but you want to, so you’re gonna do it. Um, and that’s, and then I look at, at what I’m doing and it’s like, okay, well the, if, you know, the end goal of a canoe is that you can put it in the water and paddle it around, right? It’s like, so the end goal for me, for building a product is users as people, users it. And I’m like, look, I, I brought value or joy or productivity or, you know, something that it’s validating. Um, You know, but, but in the grand scheme of things, like there was a time when I was like, you know, the goal is to make a gajillion dollars. Um, now it’s like I’ve, I’ve gotten, I’ve gotten smaller and smaller and smaller. Now it’s to make a good product that people use. Mm-hmm. And it’s like, is that because I have failed so many times that my expectations have gone down, down, down, or. Is that still I’ve, I’ve, for myself, I have distilled it down to, that’s the first real spark, and then you kind of grow a, ideally grow a fire from there, right? If you’ve got people using something, then you’ve got something, presumably, and then that’s where you, you know, uh, You are, you are the fuel, and I’m the f I’m the spark or whatever, you know, that’s where you and I collaborate because fire takes three things. Um, and so you, you can’t, you probably can’t do it yourself or you don’t want to. Um, and, or, you know, the idea of cool people working together to build something bigger and bigger and bigger. And so part of the joy is like, I was texting my, talking about the, the startup in Nashville. I was texting with the ceo. Yes. This weekend, you know, and I haven’t, and that was at least 10 years ago. So it’s like friendships that last, or fond memories or, or war stories or, you know, I don’t know. It’s hard to, I’m, I’m totally rambling, but it’s hard to quantify now, harder to quantify now for me, like. Why on earth I do this, but I do it and it brings me joy and maybe that’s all I need. [00:47:30] Cory Miller: Yeah. We’ve talked a lot about hobbies and historically I’ve been like, I don’t have hobbies. I have work, I don’t have a home life. Um, and work was always my hobby. I mean, I would say even before I, I could, I had so much fun. It was like a hobby, I guess. Mm-hmm. Um, and most of the business was fun and I didn’t. Have time and want to have time for other hobbies. Like it had to be productive. When you said hobby, it’s like when you’re talking about the canoe, I go, there’s a reason the person has makes space in the garage and the significant other probably goes, we don’t have any garage cause the canoe. But I go, that energy, that passion needs to take up space in your life somehow. And I go, so I haven’t had those. I do have two motorcycle, um, two motorcycles and the girls that don’t work. Um, but like what takes up space? I guess I was thinking what takes up space and this is it, this is part of this. So like we talked about it and your, your thoughts and hobbies have helped me so much more as go, I still think about it as. For some reason, I, it’s hard for me to do something just for the value of doing it. The joy of doing it. Yeah. Um, I do have joy in doing things that build. I just want the practical something to the end. But I go, you know, this has, this, this time should take, uh, space in my life because I enjoy it. Right for that only value. That’s something that did not exist probably a year ago, five years ago. 10 years ago. In my, in my mind, in my heart, because I was like, well, it’s just extra. It does take up just like the canoe in the garage takes up space, that other things could be there, but I go. No, enjoy talking to you. Enjoy having these conversations. Enjoy tinkering with these products. This is our little mm-hmm. Garage hobby. You know, my version because I don’t physical things, you know, you build fences and stuff. Um, I, I don’t really do a lot of that. Don’t feel like I have always the ability and patience to do it, but I was like, hobby that builds, I, that’s my version of hobby is something, even when I could say I. My reading hobby, my hiking hobby, for me, it still builds. I’d need that part. It’s just, it connects somewhere back. Um, like I can say we’re gonna my daughter and sent her home. Of course summer, we’ll go to the swimming pool. The value of that is rest and recuperation and enjoying time with them. That checks by something that builds. Sure. Thing, but I don’t know. As you were talking, I was like, no, it’s this time should take up this space. It has taken up, what, the last six months I think we’re our 18th session. [00:50:40] Corey Maass: Yeah. I, yeah. I love, I love that you say it that way, like I think the hard part is, again, settling it in your own mind and then explaining it to other people. Yeah. And, and I know that we’ve struggled a little bit, um, where to my wife, it looks like I’m working all the time and I’m like, yeah. And sometimes I am. And sometimes it’s work, but it’s not earning me any money. And sometimes it’s fun and it’s not earning me any money. And it’s, you know, and it’s like there are four, the four quadrants of earns money or doesn’t, and it’s fun or it isn’t, but, um, and it’s client work or it’s not. And, and I know that like my folks struggle with this too. My dad, my folks are retired, but my dad still writes papers, um, using research that he did during his career as a forester. Um, And it just brings him joy. And my mom’s like, get off the damn computer, where, you know, go play golf. We’re retired. That’s not the retirement she wants. It’s the retirement he wants, you know? Um, and so it’s the hard, sometimes it’s hard to explain or show to other people, like, this is okay, this is what I wanna do. It’s like, as long as you’re getting enough exercise in vitamin D, you know, uh, but it’s, you know, cuz it’s, And it’s funny cuz people will look at gaming, you know, it’s like, oh, well you’re, you’re 10, 12 hours a day in front of the TV going zap, zap, zap or whatever. You know? We’ll go, okay, that’s fi that’s fine. That’s a hobby. It’s like, It may or may not be the healthiest me sitting here typing, building something, and I’m not judging one against the other, obviously, but it’s the, like, it’s hard to, it’s, it, it’s not as easy to demonstrate that it’s the same sort of thing of like, no, this is fun. You know? [00:52:35] Cory Miller: Oh yeah. I, you know, self-care is all in the rage and I’m glad it is, but I go, it’s such an abstract concept for me. But because I’m, I try to be pretty practical with things, but I go, you know, that time and space is valuable to me. And you put the other part, is it seen as valued by others? And that’s another conversation. But I go, what I’m trying to do is like, I don’t have those things. Maybe I don’t consciously have those things a take up space that I go, this is me, this is for me. Right. It’s for others but me and this whole concept of taking, so I says, what the heck does that talk about? It means for me personally, being in a line, not worrying about everybody else, necessarily worrying about me too. I’m okay to be in this space. Um, there’s a great person on Instagram talking about, or Instagram talking about Enneagram, and I’m an Enneagram nine, which is peacemaker Art Tap. And the one thing they said, take up space. And I said, I think I’m starting to get that now from canoe in the garage to standing in line. And you know what? I’m in this part and I’m gonna take this particular space, you know, for myself. Yeah. And I think that goes back to hobbies is now of course communication with sniff and others and all that stuff. But I go, it’s one added element I think our conversations have been so enriching for me is just go, it’s okay. This time our async time takes up space and what I increasingly see is limited time. Yeah. And energy. But I go, I wanted to take up space. I wanted to take up that space. And you know, that’s the amber that I think keeps me coming to this. Uh, and then, you know, you never know. You just never know. Yep. Like we’re not losing our house families, all this stuff, like you said earlier. Yep. So good reflection on a Wednesday. [00:54:48] Corey Maass: So, uh, I think both of us have limited availability for a while, but as we’ve said so I’m the only thing that is tugging at my sleeve. Given, given the reflection that we’ve just done, like I’m, I would be okay if time went by. Um, but the, the little bit that’s, that’s nagging at me is that we’re, we are really close. Like I have something working. Um, and so I think that that’s gonna keep, that’s gonna drive me soon to, again, start putting in a few hours here and there, um, to try to get something. Out the door, um, for you to use. For me to use and mm-hmm. Um, and you know, as quick as we can get it on the website. And, and so it’s on, it’s for sale. Like, and there it is. People can try it. And, and you know, um, we were [00:55:55] Cory Miller: talking about our, don’t think feature damages post says that are gonna, we got this new theme in staging. We’re gonna be launching before work camps. I’ll say July 1st, and realizing thumbnails on the feature, damage on the archive pages, uh, how we’re gonna do the feature damages in the post gonna need to change as an awareness thing from the post edit client side. I go, this is gonna be good, you know, we’ll keep iterating on this. Um, with when, when you’re able to get the new update. Is, um, I think there’d be a lot of good feedback there, um, to how does that look on that home? How does that look on the inside page? That I think is that cornerstone to value for, yeah. So I like to say, I think it’s good timing when you get the new update, put it on staging, start trying it out. We’ll have another round of feedback. [00:56:52] Corey Maass: Yeah, exactly. Exactly. So yeah, baby steps or big steps sometimes, you know. Yeah. But. Keep moving forward. Sounds good. [00:57:04] Cory Miller: All right. Thanks my friend. [00:57:05] Corey Maass: Yeah, great talking as ever. You too. [00:57:08] Cory Miller: Talk to you next week. Bye. This article was published at Post Status — the community for WordPress professionals. Have you updated your free Gravatar profile page recently? We are excited to announce the launch of new payment features on Gravatar profiles! Now, you can add verified payment links for PayPal, Venmo, and Patreon and share your cryptocurrency wallet addresses (Bitcoin, Dogecoin, Ethereum, and more). When someone looks at your profile on their phone, they’ll see a new button at the top to Send Money. A new Share Profile button also displays your unique QR code and a simple way to copy your link, allowing you to share your profile with others quickly. Millions of people view Gravatar profiles every month. Keep your profile up-to-date and manage your online identity by adding verified links to the services you use, such as Instagram, Tumblr, GitHub, Mastodon, and more. Adding multiple payment options to your profile builds trust that those paying you know they have the correct account. Gravatar is your personal digital business card. And now a one-stop place for those that need to send you payments. Version 5.2 of the Akismet plugin for WordPress is now available. The plugin has been given a fresh coat of paint, and you will notice a nicer appearance when configuring Akismet or viewing your stats. This update also improves compatibility with PHP 8.1 and above. Note that the minimum required version of WordPress is now v5.8, and installing Akismet requires PHP v5.6 or above. We also no longer provide support for Internet Explorer 11, matching WordPress’ own behavior. To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory. BoldGrid Inspirations is an inspiration-driven plugin to assist with creating a fresh new website, or to customize an existing website.<\\/p>\\n\\n The first phase is Inspiration; the guided tool creates your base website. If you already have a website, then you can skip this step.<\\/p>\\n\\n The second phase is Customization; tools to transform your website into your vision.<\\/p>\\n\",\"installation\":\" Upload the entire boldgrid-inspirations folder to the \\/wp-content\\/plugins\\/ directory.<\\/p><\\/li>\\n Activate the plugin through the Plugins menu in WordPress.<\\/p><\\/li>\\n You will find the Inspirations menu in your WordPress Dashboard \\/ admin panel.<\\/p><\\/li>\\n<\\/ol>\\n\",\"changelog\":\" Release date: March 23rd, 2023<\\/p>\\n\\n Release date: September 20th, 2022<\\/p>\\n\\n Release date: September 7th, 2022<\\/p>\\n\\n Release date: August 8th, 2022<\\/p>\\n\\n Release date: July 8th, 2022<\\/p>\\n\\n Release date: July 7th, 2022<\\/p>\\n\\n Release date: January 25th, 2022<\\/p>\\n\\n Release date: October 18th, 2021<\\/p>\\n\\n Release date: June 10th, 2021<\\/p>\\n\\n Release date: April 14th, 2021<\\/p>\\n\\n Release date: February 16th, 2021<\\/p>\\n\\n Release date: January 25th, 2021<\\/p>\\n\\n Release date: December 8th, 2020<\\/p>\\n\\n Release date: October 23rd, 2020<\\/p>\\n\\n Release date: October 17th, 2020<\\/p>\\n\\n Release date: September 22nd, 2020<\\/p>\\n\\n Release date: August 11th, 2020<\\/p>\\n\\n Release date: June 15th, 2020<\\/p>\\n\\n Release date: May 29th, 2020<\\/p>\\n\\n Release date: May 18th, 2020<\\/p>\\n\\n Release date: March 12th, 2020<\\/p>\\n\\n Release date: December 17th, 2019<\\/p>\\n\\n Release date: November 22st, 2019<\\/p>\\n\\n Release date: October 15th, 2019<\\/p>\\n\\n Release date: September 17th, 2019<\\/p>\\n\\n Release date: September 5th, 2019<\\/p>\\n\\n Release date: August 29th, 2019<\\/p>\\n\\n Release date: August 16, 2019<\\/p>\\n\\n Release date: August 1st, 2019<\\/p>\\n\\n Release date: July 25th, 2019<\\/p>\\n\\n Release date: July 2nd, 2019<\\/p>\\n\\n Release date: May 21st, 2019<\\/p>\\n\\n Release date: Apr 23nd, 2019<\\/p>\\n\\n Release date: Apr 19th, 2019<\\/p>\\n\\n Release date: Apr 16th, 2019<\\/p>\\n\\n Release date: Jan 29th, 2019<\\/p>\\n\\n Release date: Dec 5th, 2018<\\/p>\\n\\n Release date: Dec 4th, 2018<\\/p>\\n\\n Release date: Nov 26th, 2018<\\/p>\\n\\n Release date: Nov 20th, 2018<\\/p>\\n\\nWhat is the Post and Page Builder by BoldGrid?<\\/h4>\\n\\n
Features<\\/h4>\\n\\n
\\n
\\n
People Love BoldGrid<\\/h4>\\n\\n
A Post and Page Builder That Works With Your Theme and Plugins<\\/h4>\\n\\n
A Post and Page Builder Stuffed With Pre-Designed Templates & Blocks<\\/h4>\\n\\n
A Post and Page Builder That Is Faster Than The Rest<\\/h4>\\n\\n
Coming Soon \\/ Maintenance Page<\\/h4>\\n\\n
Bootstrap WYSIWYG Post & Page Builder for WordPress<\\/h4>\\n\\n
Create Custom Color Palette<\\/h4>\\n\\n
Minimum Requirements<\\/h4>\\n\\n
\\n
Manually<\\/h4>\\n\\n
\\n
1.1.1<\\/h4>\\n\\n
\\n
1.1.0<\\/h4>\\n\\n
\\n
1.0.6<\\/h4>\\n\\n
\\n
1.0.5<\\/h4>\\n\\n
\\n
1.0.4<\\/h4>\\n\\n
\\n
1.0.3<\\/h4>\\n\\n
\\n
1.0.2<\\/h4>\\n\\n
\\n
1.0.1<\\/h4>\\n\\n
\\n
1.0.0<\\/h4>\\n\\n
\\n
\n
\n\";s:9:\"changelog\";s:43724:\"2.7.5
\n\n
\n2.7.4
\n\n
\n2.7.3
\n\n
\n2.7.2
\n\n
\n2.7.1
\n\n
\n2.7.0
\n\n
\n2.6.5
\n\n
\n2.6.4
\n\n
\n2.6.3
\n\n
\n2.6.2
\n\n
\n2.6.1
\n\n
\n2.6.0
\n\n
\n2.5.2
\n\n
\n2.5.1
\n\n
\n2.5.0
\n\n
\n2.4.4
\n\n
\n2.4.3
\n\n
\n2.4.2
\n\n
\n2.4.1
\n\n
\n2.4.0
\n\n
\n2.3.1
\n\n
\n2.3.0
\n\n
\n2.2.2
\n\n
\n2.2.1
\n\n
\n2.2.0
\n\n
\n2.1.1
\n\n
\n2.1.0
\n\n
\n2.0.7
\n\n
\n2.0.6
\n\n
\n2.0.5
\n\n
\n2.0.4
\n\n
\n2.0.3
\n\n
\n2.0.2
\n\n
\n2.0.1
\n\n
\n2.0.0
\n\n
\n1.6.5
\n\n
\n1.6.4
\n\n
\n1.6.3
\n\n
\n1.6.2
\n\n
\n1.6.1
\n\n
\n1.6.0
\n\n
\n1.5.8
\n\n
\n1.5.7
\n\n
\n1.5.6
\n\n
\n1.5.5
\n\n
\n1.5.4
\n\n
\n1.5.3
\n\n
\n1.5.2
\n\n
\n1.5.1
\n\n
\n1.5
\n\n
\n1.4.11
\n\n
\n1.4.10
\n\n
\n1.4.9
\n\n
\n1.4.8
\n\n
\n1.4.7
\n\n
\n1.4.6
\n\n
\n1.4.5
\n\n
\n1.4.4
\n\n
\n1.4.3
\n\n
\n1.4.2
\n\n
\n1.4.1
\n\n
\n1.4.0.1
\n\n
\n1.4
\n\n
\n1.3.9
\n\n
\n1.3.8
\n\n
\n1.3.7
\n\n
\n1.3.6
\n\n
\n1.3.5
\n\n
\n1.3.4
\n\n
\n1.3.3
\n\n
\n1.3.2
\n\n
\n1.3.1
\n\n
\n1.3
\n\n
\n1.2.13
\n\n
\n1.2.12
\n\n
\n1.2.11
\n\n
\n1.2.10
\n\n
\n1.2.9
\n\n
\n1.2.8
\n\n
\n1.2.7
\n\n
\n1.2.6
\n\n
\n1.2.5
\n\n
\n1.2.4
\n\n
\n1.2.3
\n\n
\n1.2.2
\n\n
\n1.2.1
\n\n
\n1.2
\n\n
\n1.1.8
\n\n
\n1.1.7
\n\n
\n1.1.6
\n\n
\n1.1.5
\n\n
\n1.1.4
\n\n
\n1.1.3
\n\n
\n1.1.2.3
\n\n
\n1.1.2.2
\n\n
\n1.1.2.1
\n\n
\n1.1.2
\n\n
\n1.1.1.1
\n\n
\n1.1.1
\n\n
\n1.1
\n\n
\n1.0.12.1
\n\n
\n1.0.12
\n\n
\n1.0.11
\n\n
\n1.0.10
\n\n
\n1.0.9.2
\n\n
\n1.0.9.1
\n\n
\n1.0.9
\n\n
\n1.0.8.1
\n\n
\n1.0.8
\n\n
\n1.0.7
\n\n
\n1.0.7
\n\n
\n1.0.6
\n\n
\n1.0.5
\n\n
\n1.0.4
\n\n
\n1.0.3
\n\n
\n1.0.2
\n\n
\n1.0.1
\n\n
\n1.0
\n\n
\n\";s:14:\"upgrade_notice\";s:311:\"1.3
\n1.0.2
\n\n
\n\";s:9:\"changelog\";s:3079:\"1.5.1
\n\n
\n1.5
\n\n
\n1.4.3
\n\n
\n1.4.2
\n\n
\n1.4.1
\n\n
\n1.4
\n\n
\n1.3.1
\n\n
\n1.3
\n\n
\n1.2.3
\n\n
\n1.2.2
\n\n
\n1.2.1
\n\n
\n1.2
\n\n
\n1.1.2
\n\n
\n1.1.1
\n\n
\n1.1.0.1
\n\n
\n1.1
\n\n
\n1.0.4
\n\n
\n1.0.3
\n\n
\n1.0.2
\n\n
\n1.0.1
\n\n
\n1.0
\n\n
\n\";s:14:\"upgrade_notice\";s:1:\"\n\";}s:7:\"siteurl\";s:24:\"http://www.boldgrid.com/\";s:13:\"compatibility\";s:2163:\"{\"5.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95]},\"4.8.1\":{\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.3\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.2\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.1\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.3\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.2\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.1\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.9\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.8\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.7\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.3\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.2\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.1\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.9\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.8\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.7\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.10\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.3.1\":{\"0.4\":[100,12],\"1.0\":[100,12],\"1.0.1\":[100,12],\"1.0.2\":[100,12],\"1.0.3\":[100,12],\"1.0.4\":[100,12],\"1.1.0.1\":[100,12],\"1.1.1\":[100,12],\"1.1.2\":[100,12],\"1.2\":[100,12],\"1.2.1\":[100,12],\"1.2.2\":[100,12],\"1.2.3\":[100,12],\"1.3\":[100,12],\"1.3.1\":[100,12],\"1.3.2\":[100,12],\"1.4\":[100,12],\"1.4.1\":[100,12],\"1.4.2\":[100,12],\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]}}\";s:6:\"rating\";i:100;s:11:\"num_ratings\";i:100000;s:4:\"tags\";a:4:{s:7:\"gallery\";s:7:\"Gallery\";s:6:\"slider\";s:6:\"Slider\";s:9:\"slideshow\";s:9:\"Slideshow\";s:7:\"masonry\";s:7:\"Masonry\";}s:7:\"banners\";a:2:{s:3:\"low\";s:53:\"//repo.boldgrid.com/assets/banner-gallery-772x250.png\";s:4:\"high\";s:54:\"//repo.boldgrid.com/assets/banner-gallery-1544x500.png\";}s:11:\"new_version\";s:5:\"1.5.1\";s:4:\"name\";s:16:\"BoldGrid Gallery\";s:4:\"slug\";s:16:\"boldgrid-gallery\";s:17:\"short_description\";s:74:\"BoldGrid Gallery is a standalone plugin used for slideshows and galleries.\";s:12:\"last_updated\";s:19:\"2020-07-27 20:25:23\";s:6:\"author\";s:68:\"BoldGrid.com \";s:5:\"icons\";a:3:{s:2:\"1x\";s:66:\"https://repo.boldgrid.com/assets/icon-boldgrid-gallery-128x128.png\";s:2:\"2x\";s:66:\"https://repo.boldgrid.com/assets/icon-boldgrid-gallery-256x256.png\";s:3:\"svg\";s:66:\"https://repo.boldgrid.com/assets/icon-boldgrid-gallery-128x128.svg\";}s:5:\"added\";s:10:\"2015-03-19\";s:3:\"url\";s:24:\"http://www.boldgrid.com/\";s:15:\"active_installs\";b:1;s:13:\"download_link\";s:148:\"https://api.boldgrid.com/api/open/getAsset?key=01af702773fa877ba366b40ba2c2d03c&id=1118061&installed_plugin_version=1.5.1&installed_wp_version=5.7.9\";}}','no'),(1415663,'can_compress_scripts','1','no'),(1415676,'adminhash','a:2:{s:4:\"hash\";s:32:\"302d87e736494e305764eddffbb036f2\";s:8:\"newemail\";s:27:\"lora@connectreleaseheal.com\";}','yes'),(1415661,'_site_transient_timeout_available_translations','1689021562','no'),(1415811,'boldgrid_reseller','a:11:{s:19:\"reseller_identifier\";s:3:\"IMH\";s:14:\"reseller_title\";s:16:\"InMotion Hosting\";s:17:\"reseller_logo_url\";s:78:\"./wp-content/plugins/boldgrid-inspirations/assets/images/wordpressinmotion.png\";s:20:\"reseller_website_url\";s:32:\"https://www.inmotionhosting.com/\";s:20:\"reseller_support_url\";s:52:\"http://www.inmotionhosting.com/support/edu/boldgrid/\";s:16:\"reseller_amp_url\";s:55:\"https://secure1.inmotionhosting.com/amp/boldgrid/manage\";s:14:\"reseller_email\";s:27:\"support@inmotionhosting.com\";s:14:\"reseller_phone\";s:14:\"1-888-321-4678\";s:16:\"reseller_css_url\";s:71:\"/wp-content/plugins/boldgrid-inspirations/assets/css/boldgrid-login.css\";s:17:\"reseller_coin_url\";s:55:\"https://secure1.inmotionhosting.com/amp/boldgrid/manage\";s:20:\"reseller_brand_login\";b:1;}','no'),(1415689,'_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1689054042','no'),(1415690,'_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1689010842','no'),(1415691,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1689054042','no'),(1415692,'_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"WordPress Planet\";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:28:\"http://planet.wordpress.org/\";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:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"en\";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:47:\"WordPress Planet - http://planet.wordpress.org/\";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:\"item\";a:50:{i:0;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"Do The Woo Community: Bring Your Podcast to Do the Woo\";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=75527\";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:53:\"https://dothewoo.io/bring-your-podcast-to-do-the-woo/\";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:367:\"
Birgit\n\n\n\n\n\n\n\n\n\n\n
Developing Gutenberg and WordPress
\n\n\n\n\n
\n\n\n\n\n\n\n\n
WordPress 6.3
\n\n\n\n
\n\n\n\n
\n\n\n\n\n
\n\n\n\n\n\n\n\n\nGutenberg Phase 3: Collaboration starts
\n\n\n\n\n
\n\n\n\nScreenshot shared on the post about Workflows\n\n\n\n
\n\n\n\n
\n\n\n\n
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. The index 2020 is herePlugins, Themes, and Tools for #nocode site builders and owners
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\nTheme Development for Full Site Editing and Blocks
\n\n\n\n
\n\n\n\n\n\n\n\n
\n\n\n\nBuilding Blocks and Tools for the Block editor.
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n\n
\n\n\n\n
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
\n\n\n\n\n
\n\n\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 08 Jul 2023 09:45:29 +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:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:120:\"WPTavern: WordPress Unveils Plans for Real-Time Collaboration with Major Improvements to Revisions and the Media Library\";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=146631\";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:131:\"https://wptavern.com/wordpress-unveils-plans-for-real-time-collaboration-with-major-improvements-to-revisions-and-the-media-library\";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:6352:\"\n\n\n\n
image credit: Workflows – Matías Ventura\n\n\n\n
\n\n\n\n
\n\n\n\nDate, Time, and Location
\n\n\n\n
Zoom Link | Save this link and use it on July 20 to join the event.About WordPress 6.3
\n\n\n\n\n
\n\n\n\n\n\n\n\n![\"\"](\"https://i0.wp.com/sanjose.wordcamp.org/2023/files/2023/06/Wapuu.png?resize=266%2C300&ssl=1\")
![\"🔊\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f50a.png\")
Our deadline for submitting proposals is midnight EST on August 26, 2023.
WordCamp San Jose is also looking for sponsors who can help with expenses. We are the largest WordCamp in Latin America. Be part of the fun and help us by bringing a great experience in terms of food, networking opportunities, and some fun contests!![\"🚀\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f680.png\")
Call for Sponsors: https://sanjose.wordcamp.org/2023/call-for-sponsors/![\"🎟\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f39f.png\")
Buy your ticket here: https://sanjose.wordcamp.org/2023/tickets/\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n
\n\n\n\nimage credit: Gutenberg PR #51990\n\n\n\n
\n\n\n\n\nUseful links.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n
\n\n\n\nBeta 3 highlights
\n\n\n\n\n
\n\n\n\nTest the new features in WordPress 6.3
\n\n\n\n\n
\n\n\n\nVulnerability bounty doubles during the Beta/RC phases
\n\n\n\nGet WordPress 6.3 Beta 3
\n\n\n\n\n
\n\n\n\nwp core update --version=6.3-beta3A Beta 3 Haiku for You
\n\n\n\n
Summer here and winter there
A fourth in one week\n
\n\n\n\nmeta_key field. This results in queries for wp_cãpăbilitiës to return the actual wp_capabilities row! See update_metadata() function in wp-includes/meta.php\n
\n\n\n\n\n
\n\n\n\nCredits
\n\n\n\n
Guests: Alex Kirk
Editor: Dustin Hartzler
Logo: Javier Arce
Production: Brett McSherry and Nicholas Garofalo
Song: Fearless First by Kevin MacLeodShow Notes
\n\n\n\n\n
\n\n\n\nTranscript
\n\n\n\n\n\n\n\n
Birgit\n\n\n\n\n\n\n\n\n\n\n
Developing Gutenberg and WordPress
\n\n\n\nWordPress 6.3
\n\n\n\nGutenberg 16.1
\n\n\n\n\n
\n\n\n\n
\n\n\n\nTo book cases, two developers having fun and a podcast episode \n\n\n\n
\n\n\n\n\n
\n\n\n\n
\n\n\n\nPlugins, Themes, and Tools for #nocode site builders and owners
\n\n\n\n
\n\n\n\n\n\n\n\n
Theme Development for Full Site Editing and Blocks
\n\n\n\n
\n\n\n\n
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. The index 2020 is hereBuilding Blocks and Tools for the Block editor.
\n\n\n\n
\n\n\n\nwp.blocks.createBlock – wp.data.dispatch(\'core/block-editor\').insertBlocks to accomplish the task.
\n\n\n\n
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
\n\n\n\n\n
\n\n\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 02 Jul 2023 06:30: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: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:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"Gutenberg Times: Gutenberg Changelog #85 – Gutenberg 16.1, WordPress 6.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:53:\"https://gutenbergtimes.com/?post_type=podcast&p=24618\";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:87:\"https://gutenbergtimes.com/podcast/gutenberg-changelog-85-gutenberg-16-1-wordpress-6-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:63883:\"\n
\n\n\n\nUpcoming Live Q & As
\n\n\n\nWordPress 6.3
\n\n\n\n\n\n\n\n\n\n\n\nGutenberg 16.1
\n\n\n\nInteractivity API
\n\n\n\n\n\n\n\n\n\n
\nAnnouncements
\n\n\n\nWhat’s Released – WordPress 6.3
\n\n\n\nGutenberg 16.1
\n\n\n\nWordPress 6.3 Beta
\n\n\n\nThis Week at WordPress.org (June 26, 2023)
\n\n\n\n\n\n\n\n\n\n
Do you run or attend WordPress events and notice only one type of person is attending? What can you do to be a good ally to foster, promote, and support diversity and an inclusive space? Sign up now for the July 20th WPDiversity workshop.
Stop by the Plugin team to wish Mika a happy retirement as she hands over the work to the 6 new Plugin Review teammembers.
Applications to be mentored as a contributor in the inaugural Mentorship Program have now closed. The team is selecting both mentors and mentees at this time and will kick off the first cohort on July 12.
\n\n\n\nWP6.3b2 • Test • WPDiversity • Mentorship • Plugin Team Next Steps
![\"🧑🏽💻\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f9d1-1f3fd-200d-1f4bb.png\")
Help Test WordPress 6.3![\"🧕🏿\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f9d5-1f3ff.png\")
Attention WordPress event organizers: This important workshop on July 20, 2023 is for you!![\"🔌\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f50c.png\")
Plugin Review Team Update: The next phase begins![\"🧑🏻🏫\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f9d1-1f3fb-200d-1f3eb.png\")
Launch your WordPress Contributor Journey through the Mentorship Program Pilot\n\n\n\nNews
\n\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWordPress 6.3
\n\n\n\n\n
\n\n\n\nWordPress 6.4
\n\n\n\n\n\n\n\nAccessibility
\n\n\n\n\n\n\n\nCommunity
\n\n\n\n\n
\n\n\n\nCore
\n\n\n\n\n
\n\n\n\nDeveloper Blog
\n\n\n\n\n
\n\n\n\nMeetings
\n\n\n\n\n\n\n\nDesign
\n\n\n\n\n\n\n\nDocs
\n\n\n\n\n
\n\n\n\nHosting
\n\n\n\n\n\n\n\nMeta
\n\n\n\n\n
\n\n\n\nMobile
\n\n\n\n\n\n\n\nOpenverse
\n\n\n\n\n
\n\n\n\nPerformance
\n\n\n\n\n\n\nPlugins
\n\n\n\n\n\n\n\nPolyglots
\n\n\n\n\n\n\n\nProject
\n\n\n\n\n\n\n\nSupport
\n\n\n\n\n\n\n\nSustainability
\n\n\n\n\n\n\n\nTest
\n\n\n\n\n\n\n\nTheme
\n\n\n\n\n\n\n\nTraining
\n\n\n\n\n
\n\n\n\nTutorials
\n\n\n\n\n
\n\n\n\nOnline Workshops
\n\n\n\n\n
\n\n\n\nCourses
\n\n\n\n\n\n\n\nWPTV
\n\n\n\n\n
\n\n\n\nRelated News:
\n\n\n\n\n
\n\n\n\n
Are you interested in giving back and contributing your time and skills to WordPress.org? ![\"🙏\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png\")
Start Here ›
Get our weekly WordPress community news digest — Post Status’ Week in Review — covering the WP/Woo news plus significant writing and podcasts. It’s also available in our newsletter. ![\"💌\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f48c.png\")
\n\n\n\n\n![\"Post](\"https://poststatus.com/wp-content/uploads/2021/09/vertical-post-status-logo-250.png\"){kind=logo}
\n![\"✉\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/2709.png\")
Listen to podcasts. ![\"🎙\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f399.png\")
Follow @Post_Status ![\"🐦\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f426.png\")
and LinkedIn. ![\"💼\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f4bc.png\")
\n\n\n\nMy first encounter with WordPress
\n\n\n\n\n
\n\n\n\nWordPress in the real world
\n\n\n\nAllison enjoying time with nature and trees\n\n\n\nFinding work with WordPress
\n\n\n\n\n
\n\n\n\nWelcomed into the WordPress community
\n\n\n\nAllie interviewed for a podcast on her use of WordPress\n\n\n\nFacing the future with strength from her friends and colleagues in WordPress
\n\n\n\n\n\n\n\n
Allison hopes reading of her experience will help others who are worried about not progressing in a WordPress career due to health concerns.\n
\n\n\n\nShare the stories
\n\n\n\nContributors
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 30 Jun 2023 21:23:11 +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:11:\"Abha Thakor\";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:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: WP Feature Notifications Contributors Seek Feedback on Admin Notices with Community Survey\";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=146339\";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:111:\"https://wptavern.com/wp-feature-notifications-contributors-seek-feedback-on-admin-notices-with-community-survey\";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:2075:\"\n\n\n\n\n
\n
\n\n\n\n\n\n\n\n
\n
\n\n\n\n
\n\n\n![\"↩\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/21a9.png\")
︎\n\n\n\n
\n
\n\n\n\n\n
\n\n\n\n\n
\n\n\n\nphoto credit: Preparations have started for WordCamp Asia 2024\n\n\n\n
A first look at 6.3
\n\n\n\nPerformance
\n\n\n\nSite Editor
\n\n\n\nBlocks
\n\n\n\nThe new height control for the Spacer block\n\n\n\nPatterns and Design
\n\n\n\nStyle your captions in the new Styles interface\n\n\n\nUsability
\n\n\n\nAdd and modify descriptions for templates\n\n\n\nAccessibility
\n\n\n\nOther notes
\n\n\n\nTesting makes WordPress stronger!
\n\n\n\nVulnerability bounty doubles during Beta 2
\n\n\n\nGet WordPress 6.3 Beta 2
\n\n\n\nwp core update --version=6.3-beta2The first haiku for 6.3
\n\n\n\n
Excitement yet much newness
Phase 2 finale\n\n\n\n\nUseful links.
\n\n\n\n\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 28 Jun 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:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"Akismet: How to Add CAPTCHA and reCAPTCHA to WordPress\";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:27:\"http://akismet.com/?p=70973\";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:43:\"https://akismet.com/blog/wordpress-captcha/\";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:25456:\"The problem with traditional CAPTCHA solutions
\n\n\n\n1. They’re challenging for those with visual impairments
\n\n\n\n![\"example](\"https://akismet455732288.files.wordpress.com/2023/06/image12.png\")
\n\n\n\n2. They create a frustrating experience
\n\n\n\n3. They can generate false positives
\n\n\n\n4. They’re easily bypassed by sophisticated bots
\n\n\n\n5. They can create a negative user experience
\n\n\n\n6. They can lead to lower conversion rates
\n\n\n\n7. They can cause higher page load times
\n\n\n\nHow does Akismet address these issues?
\n\n\n\nThe benefits of using Akismet over CAPTCHA
\n\n\n\n1. Greater user-friendliness
\n\n\n\n2. Improved accessibility for all users
\n\n\n\n3. Greater accuracy in spam detection
\n\n\n\n4. Robust effectiveness against malicious activity
\n\n\n\n5. Optimized performance and load times
\n\n\n\nHow to add Akismet to WordPress
\n\n\n\nStep 1: Install the Akismet plugin
\n\n\n\n![\"finding](\"https://akismet455732288.files.wordpress.com/2023/06/image6.png\")
\n\n\n\n![\"Aksimet](\"https://akismet455732288.files.wordpress.com/2023/06/image7.png\")
\n\n\n\n![\"Akismet](\"https://akismet455732288.files.wordpress.com/2023/06/image1.png\")
\n\n\n\nStep 2: Add Akismet to your contact form
\n\n\n\nStep 3: Set up the anti-spam settings in Akismet
\n\n\n\n![\"Strictness](\"https://akismet455732288.files.wordpress.com/2023/06/image10.png\")
\n\n\n\nStill want to use CAPTCHA?
\n\n\n\n1. How to add CAPTCHA to a WordPress contact form
\n\n\n\nStep 1: Install and activate the Friendly CAPTCHA for WordPress plugin
\n\n\n\n![\"Friendly](\"https://akismet455732288.files.wordpress.com/2023/06/image8-1.png\")
\n\n\n\nStep 2: Add the site key and secret key
\n\n\n\n![\"creating](\"https://akismet455732288.files.wordpress.com/2023/06/image5.png\")
\n\n\n\n![\"creating](\"https://akismet455732288.files.wordpress.com/2023/06/image13.png\")
\n\n\n\nStep 3: Finish configuring settings
\n\n\n\nStep 4: Save and view
\n\n\n\n2. How to add reCAPTCHA to a WordPress contact form
\n\n\n\nStep 1: Install and activate a WordPress reCAPTCHA plugin
\n\n\n\n![\"the](\"https://akismet455732288.files.wordpress.com/2023/06/image11.png\")
\n\n\n\nStep 2: Configure the plugin settings
\n\n\n\n![\"warning](\"https://akismet455732288.files.wordpress.com/2023/06/image2.png\")
\n\n\n\nStep 3: Obtain reCAPTCHA API keys by registering your website
\n\n\n\n![\"registering](\"https://akismet455732288.files.wordpress.com/2023/06/image14.png\")
\n\n\n\nStep 4: Add a new site
\n\n\n\n![\"options](\"https://akismet455732288.files.wordpress.com/2023/06/image9-1.png\")
\n\n\n\nStep 5: Add domain and email to your reCAPTCHA site
\n\n\n\nStep 6: Submit and register your WordPress site
\n\n\n\n![\"creating](\"https://akismet455732288.files.wordpress.com/2023/06/image4.png\")
\n\n\n\nFrequently asked questions about CAPTCHA and reCAPTCHA
\n\n\n\nWhat is CAPTCHA?
\n\n\n\nWhat is reCAPTCHA?
\n\n\n\n![\"I\'m](\"https://akismet455732288.files.wordpress.com/2023/06/image3.png\")
\n\n\n\nWhat is Akismet?
\n\n\n\nIs Akismet better than CAPTCHA and reCAPTCHA?
\n\n\n\nDoes Akismet integrate with contact form plugins like Contact Form 7?
\n\n\n\nWhat are real-world examples of sites using Akismet?
\n\n\n\nAkismet: Non-intrusive spam protection for WordPress
\n\n\n\n\n
\n\n\n\n\n
\n\n\n\n\n
\n\n\n\n![\"\"](\"https://i0.wp.com/make.wordpress.org/design/files/2023/06/patterns.gif?resize=776%2C540&ssl=1\")
image credit: WordPress Design Share June 5-16\n\n\n\nThe Potential of Partially Synced Patterns
\n\n\n\n\n
\n\n\n\ncontentOnly locking). Only specific parts of the pattern considered ‘content’ can be edited (denoted by adding __experimentalRole: \'content\' to a block’s definition).content values the user entered are retained. The best way to think of this is that the user can update the design of a pattern, but doesn’t lose content that exists in templates and posts.
Birgit\n\n\n\n\n\n\n
\n\n\n\n\nDeveloping Gutenberg and WordPress
\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n\n\n\n
Plugins, Themes, and Tools for #nocode site builders and owners
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\nReusable blocks are now called Patterns
\n\n\n\n\n\n\n\n
Theme Development for Full Site Editing and Blocks
\n\n\n\n
\n\n\n\n
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. The index 2020 is here
\n\n\n\nBuilding Blocks and Tools for the Block editor
\n\n\n\n
\n\n\n\n
\n\n\n\n\n
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
\n\n\n\n\n
\n\n\n\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 24 Jun 2023 06:07: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: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:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"WPTavern: Really Simple SSL Plugin Adds Free Vulnerability Detection\";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=146129\";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:79:\"https://wptavern.com/really-simple-ssl-plugin-adds-free-vulnerability-detection\";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:2999:\"\n\n\n\n
\n\n\n\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nKey feedbacks about BuddyPress community
\n\n\n\n\n
\n\n\n\n![\"🥌\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f94c.png\")
.![\"☝\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/261d.png\")
URL to know: https://buddypress.trac.wordpress.org/.![\"📕\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f4d5.png\")
. The codex is not updated as frequently as it used to be, the « wiki » model where everyone can contribute to docs is no more efficient.\n
\n\n\n\n![\"👨🏫\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f468-200d-1f3eb.png\")
to organize this part, lead a documentation team and carry on the work we started on splitting resources between two targets (end-users and developers) :\n
\n\n\n\na Plugin an Add-on handbook, a Theme handbook and BuddyPress code reference.\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2023/06/contributor-badges.png\")
![\"❤\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/2764.png\")
. Again you are all welcome to express yourselves on code, documentation, support, events, etc. Don’t hesitate to contribute even if you just started BuddyPressing, we’ll always help you and believe my experience, you’ll learn a lot. I had no ideas about PHP Object Oriented programming, PHPUnit, Continuous Integration, React, SASS etc.. I’ve learnt all this contributing to BuddyPress.Props
\n\n\n\n![\"🤗\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f917.png\")
!![\"😍\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f60d.png\")
.\n\n\n\n
\n\n\n\nWordPress.com Plan Payment Fees WordPress.com Commerce 0% WordPress.com Business 2% WordPress.com Premium 4% WordPress.com Personal 8% WordPress.com Free 10% \n\n\n\n
\n\n\n\n
Gravatar is used by Slack, Atlassian (owner of Jira and Trello), GitHub, Stack Overflow, and Disqus, serving millions of requests per day. Another new major user is OpenAI, which displays users’ Gravatar images when chatting with ChatGPT. The service is also integrated with every WordPress install, and an Automattic representative confirmed there are no plans to change this.\n
\n\n\n\n
\n\n\n\n![\"🔗\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f517.png\")
Mentioned in the show:\n
\n\n\n\n
\n\n\n\n You can follow Post Status and our guests on Twitter:\n
\n\n\n\n![\"📝\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f4dd.png\")
Browse our archives, and don’t forget to subscribe via iTunes, Google Podcasts, YouTube, Stitcher, Simplecast, or RSS. ![\"🎧\"](\"https://s.w.org/images/core/emoji/14.0.0/72x72/1f3a7.png\")
Transcript
\n\n\n\nSession 18 Corey & Cory Launch a WordPress Product Live
\n\n\n\n\n\n\n\n
![\"\"](\"https://akismet455732288.files.wordpress.com/2023/06/screenshot-2023-06-19-at-15.40.36-1.png?w=1024\")
\n\n\n\n\\n
2.7.5<\\/h4>\\n\\n
\\n
2.7.4<\\/h4>\\n\\n
\\n
2.7.3<\\/h4>\\n\\n
\\n
2.7.2<\\/h4>\\n\\n
\\n
2.7.1<\\/h4>\\n\\n
\\n
2.7.0<\\/h4>\\n\\n
\\n
2.6.5<\\/h4>\\n\\n
\\n
2.6.4<\\/h4>\\n\\n
\\n
2.6.3<\\/h4>\\n\\n
\\n
2.6.2<\\/h4>\\n\\n
\\n
2.6.1<\\/h4>\\n\\n
\\n
2.6.0<\\/h4>\\n\\n
\\n
2.5.2<\\/h4>\\n\\n
\\n
2.5.1<\\/h4>\\n\\n
\\n
2.5.0<\\/h4>\\n\\n
\\n
2.4.4<\\/h4>\\n\\n
\\n
2.4.3<\\/h4>\\n\\n
\\n
2.4.2<\\/h4>\\n\\n
\\n
2.4.1<\\/h4>\\n\\n
\\n
2.4.0<\\/h4>\\n\\n
\\n
2.3.1<\\/h4>\\n\\n
\\n
2.3.0<\\/h4>\\n\\n
\\n
2.2.2<\\/h4>\\n\\n
\\n
2.2.1<\\/h4>\\n\\n
\\n
2.2.0<\\/h4>\\n\\n
\\n
2.1.1<\\/h4>\\n\\n
\\n
2.1.0<\\/h4>\\n\\n
\\n
2.0.7<\\/h4>\\n\\n
\\n
2.0.6<\\/h4>\\n\\n
\\n
2.0.5<\\/h4>\\n\\n
\\n
2.0.4<\\/h4>\\n\\n
\\n
2.0.3<\\/h4>\\n\\n
\\n
2.0.2<\\/h4>\\n\\n
\\n
2.0.1<\\/h4>\\n\\n
\\n
2.0.0<\\/h4>\\n\\n
\\n
1.6.5<\\/h4>\\n\\n
\\n
1.6.4<\\/h4>\\n\\n
\\n
1.6.3<\\/h4>\\n\\n
\\n
1.6.2<\\/h4>\\n\\n
\\n
1.6.1<\\/h4>\\n\\n
\\n
1.6.0<\\/h4>\\n\\n
\\n
1.5.8<\\/h4>\\n\\n
\\n
1.5.7<\\/h4>\\n\\n
\\n
1.5.6<\\/h4>\\n\\n
\\n
1.5.5<\\/h4>\\n\\n
\\n
1.5.4<\\/h4>\\n\\n
\\n
1.5.3<\\/h4>\\n\\n
![\"GitHub](\"https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge\")