Each year, members of the WordPress community (users, site builders, extenders, and contributors) provide valuable feedback through an annual survey. Key takeaways and trends that emerge from this survey often find their way into the annual State of the Word address, are shared in the public project blogs, and can influence the direction and strategy for the WordPress project.
\n\n\n\nSimply put: this survey helps those who build WordPress understand more about how the software is used, and by whom. The survey also helps leaders in the WordPress open source project learn more about our contributors’ experiences.
\n\n\n\nTo ensure that your WordPress experience is represented in the 2022 survey results, take the 2022 annual survey now.
\n\n\n\n\n\n\n\nYou may also take the survey in French, German, Italian, Japanese, Russian, or Spanish, thanks to the efforts of WordPress polyglot contributors. These are the most frequently installed languages based on the number of WordPress downloads.
\n\n\n\nThe survey will be open through the end of 2022, and then WordPress plans to publish the results sometime in 2023. This year, the survey questions have been refreshed for more effortless survey flow, completion, and analysis. Some questions have been removed, while a few new ones are now present, reflecting the present and future of WordPress. If you’re looking for the analysis of the 2021 survey results, those will also be shared in early 2023.
\n\n\n\nHelp spread the word about the survey by sharing it with your network, through Slack, or within your social media accounts. The more people who complete the survey and share their experience with WordPress, the more the project as a whole will benefit in the future.
\n\n\n\nData security and privacy are paramount to the WordPress project and community. With this in mind, all data will be anonymized: no email addresses nor IP addresses will be associated with published results. To learn more about WordPress.org’s privacy practices, view the privacy policy.
\n\n\n\nThank you to the following WordPress contributors for assisting with the annual survey project, including question creation, strategy, survey build-out, and translation:
\n\n\n\ndansoschin, _dorsvenabili, angelasjin, arkangel, audrasjb, atachibana, bjmcsherry, chanthaboune, eidolonnight, fernandot, fierevere, fxbenard, jdy68, jpantani, laurlittle, nao, nielslange, peiraisotta, piermario, rmartinezduque, santanainniss.
\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:"14062";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: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:34:"People of WordPress: Huanyi Chuang";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/2022/11/people-of-wordpress-huanyi-chuang/";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, 30 Nov 2022 20:09: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: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=13562";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:144:"The latest People of WordPress story features Huanyi Chuang, from #Taiwan, on his journey to become a digital marketer and front end developer. ";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:11499:"\nThis month we feature Huanyi (Eric) Chuang, a front end developer from Taiwan, who helps connect local groups to WordPress and the worldwide open source community. He is part of the team helping to make the first WordCamp Asia a success in 2023.
\n\n\n\nThe People of WordPress series shares some of the inspiring stories of how people’s lives can change for the better through WordPress and its global network of contributors.
\n\n\n\nHuanyi’s first footsteps in WordPress began in 2017 when he worked for a firm that built blogs and developed ad content for clients.
\n\n\n\nAfter building a few sites using the platform, he discovered child themes and through them opened up a world of possibilities for his clients. To this day, he uses child themes to deliver truly custom designs and functionality for clients.
\n\n\n\nLater in his career, Huanyi moved into digital marketing, integrating sites with massive ad platforms like Google and Facebook. This led him to learn to work with tracking code and JavaScript. He also began his learning journey in HTML, CSS, and PHP, to be able to improve his development skills and customize child themes.
\n\n\n\n
When Huanyi had a problem with a client’s site, he looked to WordPress meetups near where he lived in Taipei to help find the solutions.
\n\n\n\n\n\n\n\n\n“When I encountered an issue with the custom archive pages, a local meetup announcement showed up on my WordPress dashboard.”
\nHuanyi Chuang
At the meetup, he met more experienced WordPress users and developers there, who answered his questions and helped him learn.
\n\n\n\n“When I encountered an issue with the custom archive pages, a local meetup announcement showed up on my WordPress dashboard. That was my original connection with the local community,” Huanyi said.
\n\n\n\nThe WordPress community gave Huanyi a chance to connect with people, feed his curiosity about the software, and join a circle of people he could share this interest.
\n\n\n\nAt first, he thought meetups were an opportunity to source new clients, and he took his business cards to every event. However, he soon found that these events offered him the opportunity to make friends and share knowledge.
\n\n\n\nFrom then on, Huanyi started focusing more on what he could give to these events and networks, making new friends, and listening to people. This led him to share as a meetup speaker his own commercial website management experience.
\n\n\n\nIt was going to his first meetup and then getting involved with WordCamps that changed Huanyi’s whole relationship with WordPress.
\n\n\n\n
In 2018, he took the step to help as an organizer, having joined the Taoyuan Meetup in Taiwan. He played several parts across the organizing team, and the welcoming feeling he got in every situation encouraged him to get more involved.
\n\n\n\nHe recalls meeting new friends from different fields and other countries, which gave him a great sense of achievement and strengthened his passion for participating in the community.
\n\n\n\nWhen the team started this meetup, numbers were much lower than in the group in the city of Taipei, but they were not disheartened and gradually grew the local WordPress community.
\n\n\n\nThey created a pattern of ‘multiple organizers,’ which spread the workload and grew friendships.
\n\n\n\n\n\n\n\n\n“Being connected to and from meetups is the most valuable part of the community. Having these friends makes me gather more information. We share information and benefit from others’ information, and thus we gain more trust in each other. With such credibility, we share more deeply and build deeper relations.”
\nHuanyi Chuang
Before the pandemic, the meetup met every month and grew to become the second largest meetup in Taiwan. Huanyi also contributed to the WordPress community as an organizer of WordCamp Taipei 2018 in the speaker team and lead organizer of WordCamp Taiwan 2021.
\n\n\n\nAccording to Huanyi, you will always have something to take home with you. It might be new information or experiences. It might be plugins or theme ideas. But most of all, it is the chance to meet fascinating people and make new friends.
\n\n\n\n\n\n\n\n\nHuanyi’s message to other contributors:
\n
“Keep participating, and you will find more you can achieve than you expect.”
He added that long-term participation will ‘let you feel the humanity behind the project’.
\n\n\n\n
Huanyi believes WordPress has the power to break down the barriers between designers, project managers, developers, marketers, writers, and publishers. In Taiwan, he said WordPress is ‘a common protocol’ that lets people from all of these disciplines work and communicate together more easily than they ever have before.
\n\n\n\nThat is why he works on and encourages others to localize plugins today. He believes localization of the software is the foundation for the extension of the WordPress community as it enables people to ‘Flex their Freedom’ in a language they speak!
\n\n\n\nHe has helped to organize online events around previous WordPress Translation Day events.
\n\n\n\nHuanyi said: “I think it’s important to localize WordPress because its very concept of ‘open source’ means that people can access it freely. In another way, free from the monopoly of knowledge and speech. To achieve it, it’s important that people can access it with their own language.
\n\n\n\n“Localization is the foundation of the extension of WordPress community because it helps people using different languages to access the project and lowers the hurdle to understand how things work.”
\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\nThank you to @no249a002 for sharing his adventures in WordPress.
\n\n\n\nThank you to Abha Thakor (@webcommsat), Mary Baum (@marybaum), Meher Bala (@meher), Chloe Bringmann (@cbringmann), Surendra Thakor (@sthakor), Adeeb Malik (@adeebmalik) for research, interviews, and contributing to this feature article.
\n\n\n\nThe People of WordPress series thanks Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support.
\n\n\n\n
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
\nIn the forty-fourth episode of the WordPress Briefing, our host Josepha Haden Chomphosy highlights the role of major and minor releases in the WordPress open source project.
\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: Santana Inniss
Song: Fearless First by Kevin MacLeod
[Josepha Haden Chomphosy 00:00:00]
\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, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[Josepha Haden Chomphosy 00:00:27]
\n\n\n\nAt the top of November, a new major release for WordPress shipped. That was WordPress 6.1. I know I talked about it basically nonstop. Then two weeks later, there was a new minor release for WordPress. It was WordPress 6.1.1, which I did not talk about at all. Way back in episode four of this podcast, I dug into the overall release cycle and what someone could expect from a high-level logistics aspect.
\n\n\n\n[Josepha Haden Chomphosy 00:01:05]
\n\n\n\nAnd today we’re gonna take a quick look at minor releases in particular. Just as a general heads up, I always want to lean into sports metaphors when I’m talking about releases, and I think it’s because of the words major and minor. And so, I’ve done my level best to not include that in any of my explanations today.
\n\n\n\nBut I do have one, I do have one that’s a sports thing. So just if you don’t like sports, know that it’s just one little bit and we’ll try to be carefully quick around it together. All right, so minor releases. You may have noticed that I don’t mention minor releases nearly as often as I mention major releases. And yet, most of the time, when we have a major release of WordPress, there’s a minor release that gets started almost immediately after.
\n\n\n\nSo first major versus minor. Major releases in WordPress happen roughly three times a year, give or take a release. Inside a major release, you will find that we include features, so– brand new abilities, enhancements, which you can generally call improvements to existing abilities, and also any bug fix that we can find, big or small, we’ll take ’em all.
\n\n\n\n[Josepha Haden Chomphosy 00:02:16]
\n\n\n\nSo minor releases in WordPress happen about four or five times a year on average. Minor releases include patches for issues introduced in the major release and any bug fix that doesn’t add or change functionality.
\n\n\n\nIf you’re with me so far, you probably have noted that there’s basically always at least one minor release per major release. And you might have also noted that I said minors include patches for issues we introduced in a major.
\n\n\n\nNow, if I were hearing this with fresh ears, the first thing I would wonder is, okay, so if you start working on the minor right after you release the major to deal with issues you know you introduced in the major– why just not ship the major while there are bugs in it? Great question. I’m glad you asked. So there are a few things worth knowing here.
\n\n\n\n[Josepha Haden Chomphosy 00:03:09]
\n\n\n\nFirstly, there is this concept of “ship and iterate,” which is present in both agile and open source. The idea is that we ship software as soon as we have confidence that what is in the release is non-breaking and represents our best guests at a better experience for our users.
\n\n\n\nOnce that is out there, we use feedback on the initial release to quickly iterate and ship another release. That way, we don’t hold back any good features. And since we already planned the immediate minor, any major issues that show up can be fixed in as little as two weeks. Secondly, there is the concept that with many eyes, all bugs are shallow, which is primarily present in open source.
\n\n\n\nThe idea here is that with enough people looking at a problem, that problem doesn’t stand a chance. So when a release is shipped in a workable state but with interactions that could use some refinement, the fastest way to find those refinements is to take it to the community of WordPress users and developers and invite them to co-create this CMS with us.
\n\n\n\n[Josepha Haden Chomphosy 00:04:10]
\n\n\n\nWhich touches on my final thought. The concept of the user as co-creator.
\n\n\n\nIf we think about the development and evolution of our software as a team effort, then we can think of the people who use our software as what’s called the “Twelfth Man” That’s in quotes, and I will, I’ll leave a link to that in the show notes as well.
\n\n\n\nIn sports, this refers to the fans. And if you’ve ever been to a live sporting event or played in any, you will know that the cheering and jeering from fans turns into this distinct motivating entity all its own. As a whole team or individual member, you know what you have to do. You know what you need to do in a game, but there’s something about that chaotic, loud roar of feedback that just brings life to what you’re doing, and that’s how I see our community of users.
\n\n\n\n[Josepha Haden Chomphosy 00:05:02]
\n\n\n\nSo at the end of the day, the answer to the question of ‘why so many releases’ and the follow-up question of ‘why tolerate stable imperfection’ is largely the same. To get features into the hands of our users quickly so that we can always be breathing life into this CMS we care so much about.
\n\n\n\nI hope that answers your questions about our release cadence, and if you didn’t come into this podcast having any questions about release cadences at all, I hope this new information brings a little extra light to the complexity of working in open source.
\n\n\n\n[Josepha Haden Chomphosy 00:05:32]
\n\n\n\nThat brings us now to our small list of big things.
\n\n\n\nBig thing number one is that the State of the Word has been announced and is scheduled for December 15th. It’s a little earlier in the day than in past iterations, so I hope we get a new crew of listeners tuning in at the same time. I’ll leave a link to that in the show notes, or you can pop over to wordpress.org/news to see the announcement for yourself.
\n\n\n\n[Josepha Haden Chomphosy 00:06:00]
\n\n\n\nBig thing number two is that team rep nominations are open on most teams right now. So if organization and people wrangling are high on your list of ways you can give back to WordPress, head on over to the team you contribute to and see how you raise your hand for that.
\n\n\n\nThen big thing number three is that big-picture goals, hopes, and timelines are being gathered, and I will ship those shortly after the start of the new year.
\n\n\n\nIt will give us all an idea of where we want to focus our attention to ensure that WordPress continues to grow toward the future. You can keep an eye out for that on make.wordpress.org/project.
\n\n\n\nAnd that, my friends, is your small list of big things. 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.
\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:"13996";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: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:39:"The Month in WordPress – October 2022";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/2022/11/the-month-in-wordpress-october-2022/";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, 22 Nov 2022 11: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: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=13988";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:224:"With the end of the year fast approaching, the WordPress project has not slowed down. Read on to learn more about the latest major release, WordPress 6.1, and the State of the Word 2022 live event, among other exciting news.";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:"rmartinezduque";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:13933:"\nWith the end of the year fast approaching, the WordPress project has not slowed down. Read on to learn more about the latest major release, WordPress 6.1, and the State of the Word 2022 live event, among other exciting news. It’s time to catch up on all things WordPress!
\n\n\n\nThe third and last major release of 2022, WordPress 6.1 “Misha,” shipped on November 1, 2022. Named after jazz pianist Mikhail “Misha” Alperin, this release comes packed with many improvements that refine the site-building experience introduced earlier this year in WordPress 5.9 and 6.0, as well as accessibility and performance upgrades.
\n\n\n\nWordPress 6.1 is also bundled with a new default block theme, Twenty Twenty-Three (TT3), that features 10 style variations designed by WordPress community members. These intentionally unique designs ensure that you can change the visual details of your site with ease—and within a single theme.
\n\n\n\nLearn more about what’s in 6.1:
\n\n\n\n\n\n\n\nFollowing WordPress 6.1 “Misha”, a 6.1.1 maintenance release landed on November 15, 2022. This minor release includes about 50 bug fixes.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n
State of the Word 2022, the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 15, 2022. The event will take place in person in New York City and live-streamed via various WordPress.org social media platforms.
\n\n\n\nYou can also host or join a State of the Word watch party to enjoy the event with your WordPress friends.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Two new versions of Gutenberg have shipped in the last month:
\n\n\n\n\n\n\n\n\n\n\n\n\nExplore some of the latest enhancements to the writing experience in this Core Editor Improvement post.
\n
\n\n\n\n\n\n\n\n\nEnjoy a spooky Halloween Mad Libs story completed by community contributors in Episode 42 of WP Briefing.
\n
\n\n\n\n\n\n\n\n\nWere you involved in WordPress 6.1? Share your thoughts on the release process by December 15, 2022.
\n
WordCamp São Paulo, Brazil on November 26, 2022
WordCamp Kolkata, West Bengal, India on December 17-18, 2022\n\n\n\n\n\n\n\n\nBoost your speaking confidence in WordPress events. Register for the How to Own Your Expertise & Start Speaking at WordPress Events online workshop happening December 7, 2022.
\n
Have a story that 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 edition of The Month in WordPress: @rmartinezduque, @webcommsat, @santanainniss, @dansoschin, @eidolonnight.
\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:"13988";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:63:"\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:22:"State of the Word 2022";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/news/2022/11/state-of-the-word-2022/";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, 21 Nov 2022 17:14:43 +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:3:{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:4:"sotw";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:17:"state of the word";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=13971";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:223:"Join the WordPress project leaders for State of the Word 2022 in New York City on December 15, 2022. Also live-streamed on social media, you will hear about the WordPress project, open source, and more in this annual event.";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:7:"Josepha";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:9853:"\nHello, WordPress!
\n\n\n\nMark your calendars; it’s almost time for State of the Word 2022!
\n\n\n\nState of the Word is the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg. Every year, the event shares reflections on the project’s progress and the future of open source. Expect this and more in this year’s edition.
\n\n\n\nThis year’s event will take place in person in New York City and live-streamed via various WordPress.org social media platforms.
\n\n\n\nJoin Matt as he provides a retrospective of 2022, the latest WordPress releases, Site Editor advancements, and a return to in-person events around the globe, among other topics.
\n\n\n\nWhat: State of the Word 2022
\n\n\n\nWhen: December 15, 2022, 1–2:30 P.M. EST (18–19:30 UTC)
\n\n\n\nHow: If you’re watching from the comfort of your home or local watch party, the live stream will be embedded in this post and available through the WordPress YouTube channel.
\n\n\n\nWould you like to join the in-person audience? Request a seat by completing this survey.
\n\n\n\nState of the Word will include a Q&A session. If you want to participate, you can either send your question ahead of time to ask-matt@wordcamp.org or ask during the event in the live stream chat on YouTube.
\n\n\n\nGiven the volume of questions that are usually submitted, please note that it may not be possible to answer all of them in the live Q&A. A follow-up post will be published after the State of the Word to answer those not covered at the event.
\n\n\n\nFirst time attending State of the Word? Check out previous years’ recordings on WordPress.tv to get a sense of the event.
\n\n\n\nSee you in person or online on December 15!
\n\n\n\nCan’t make it to New York? No problem, organize or join a watch party in your community in person or online. Like last year, the Community team has resources available to help! Check out this handbook page, which includes event templates, information on requesting a Zoom account, and how to get some swag.
\n\n\n\nGather together to look back on how WordPress has grown in 2022 and what is ahead for 2023. Stay up-to-date as a group on the latest happenings in the WordPress world and collaborate together on any questions you might have for Matt!
\n\n\n\nBelow you can find a list of State of the Word watch parties that will be updated regularly as the event approaches. If you don’t see a watch party in your region, check this page on Meetup.com to see if your local WordPress group is organizing one.
\n\n\n\n
Seattle WordPress Meetup – WordPress Developer Meetup: State of the Word/General Discussion
Port-au-Prince WordPress Meetup Group – State of the Word Watch Party (Online)
WordPress Meetups Genève (Geneva) – State of the Word “Watch Party” et plus/and more (FR/EN) WordPress
WordPress Ancona Meetup – State of the Word Watch Party + Auguri di Natale + Proposte 2023
WordPress Sofia Meetup – “State of the Word 2022” watch party!
Granada WordPress Meetup – ¡Veamos el State of the Word 2022! Kochi WordPress Meetup – State of the Word Watch Party (In-person)
WordPress Meetup Tegal – Nonton bareng “State of the Word 2022”
Tokyo WordPress Meetup – State of the Word から来年の WordPress を考えよう！+ 忘年会 WPGR – Grand Rapids WordPress Meetup – State of the Word Watch Party (In-person)If you are planning a watch party for State of the Word and have questions, please email support@wordcamp.org. A member of the WordPress community team will assist you in the best way possible.
\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:"13971";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: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:35:"WordPress 6.1.1 Maintenance Release";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/2022/11/wordpress-6-1-1-maintenance-release/";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, 15 Nov 2022 19:51:45 +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: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:1;a:5:{s:4:"data";s:3:"6.1";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:5:"6.1.1";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:14:"minor-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: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=13918";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:244:"WordPress 6.1.1 is now available for download. This maintenance release features several updates since the release of WordPress 6.1 on 01 November 2022. You can review a summary of the key changes in this release by visiting WordPress.org/news.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Jeffrey Paul";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:9850:"\nThis minor release features 29 bug fixes in Core and 21 bug fixes for the block editor. WordPress 6.1.1 is a short-cycle maintenance release. You can review a summary of the key updates in this release by reading the RC1 announcement.
\n\n\n\nThe next major release will be version 6.2 planned for 2023.
\n\n\n\nIf you have sites that support automatic background updates, the update process will begin automatically.
\n\n\n\nYou can download WordPress 6.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.
\n\n\n\nFor more information, check out the version 6.1.1 HelpHub documentation page.
\n\n\n\nThe WordPress 6.1.1 release was led by Jonathan Desrosiers, George Mamadashvili, and Jeffrey Paul.
\n\n\n\nWordPress 6.1.1 would not have been possible without the contributions of more than 105 people. Their asynchronous coordination to deliver several enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\n10upsimon, Aaron Jorbin, Aaron Robertshaw, Adam Silverstein, Aki Hamano, alexstine, Andrei Draganescu, Andrew Ozz, Andrew Serong, Andre, Andy Fragen, Ari Stathopoulos, azurseisme, Ben Dwyer, Bernie Reiter, Bethany Chobanian Lang, Birgit Pauli-Haack, bjorn2404, Carlos Bravo, Carolina Nymark, Clayton Collie, codesdnc, Colin Stewart, Daniel Richards, David Baumwald, David Smith, David Vongries, Dilip Bheda, Dion Hulse, Dominik Schilling, Ella, Eugene M, Felix Arntz, fpodhorsky, franzaurus, gamecreature, Gary Pendergast, George Mamadashvili, gisgeo, glendaviesnz, Innovext, ironprogrammer, Isabel Brison, James, Jan Thiel, Javier Carazo, Jb Audras, jchambo, jeffpaul, joelmadigan, Joen A., John Blackbourn, John Watkins, Jonathan Desrosiers, Jonny Harris, jsh4, Juliette Reinders Folmer, K. Adam White, kacper3355, Kai Hao, Konstantin Obenland, konyoldeath, larsmqller, Lena Morita, Leo Milo, lozula, Marco Ciampini, Marin Atanasov, Marius L. J., Matt Keys, Michal Czaplinski, Miguel Axcar, Miguel Fonseca, Mukesh Panchal, mw108, Namith Jawahar, Nick Diego, Nik Tsekouras, Nithin SreeRaj, nuvoPoint, oakesjosh, ockham, Oliver Juhas, Pascal Birchler, Paul Biron, Peter Wilson, petitphp, pkolenbr, pypwalters, ramonopoly, Riad Benguella, rjasdfiii, Robert Anderson, rodricus, Ryan Kienstra, Sarah Norris, Sergey Biryukov, stentibbing, Stephen Bernhardt, Subrata Sarkar, Sybre Waaijer, Timi Wahalahti, Timothy Jacobs, Tonya Mork, Torsten Landsiedel, and vtad.
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core and #6-1-release-leads channels. Need help? Check out the Core Contributor Handbook.
\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:"13918";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: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:102:"WP Briefing: Episode 43: Openverse & Photo Directory– What Are They, and How Are They Different?";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:113:"https://wordpress.org/news/2022/11/episode-43-openverse-photo-directory-what-are-they-and-how-are-they-different/";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, 14 Nov 2022 12: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=13890";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:151:"Join Josepha as she explores the differences between Openverse & Photo Directory, two resources for openly licensed media in the WordPress project.";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:62:"https://wordpress.org/news/files/2022/11/WP-Briefing-043-1.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:"Santana Inniss";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:8965:"\nIn the forty-third episode of the WordPress Briefing, Josepha Haden Chomphosy explores two resources for openly licensed media in the WordPress project– Openverse and Photo Directory– and how they differ from one another!
\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: Santana Inniss
Song: Fearless First by Kevin MacLeod
Photo Directory Make Page
Submit a Photo to the Photo Directory
Openverse Make Page
Openverse Call for Contributions: Block Editor Integration
Download WordPress 6.1
Docs Team Contributor Day Recap Post
Hallway Hangout Block Themes (Video)
[Josepha Haden Chomphosy 00:00:00]
\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, Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:27]
\n\n\n\nAbout 18 months ago, the Openverse project became part of the WordPress open source project, and at roughly the same time, we also welcomed the Photo Directory.
\n\n\n\nSince that time, we’ve seen growth in teams supporting both of these initiatives. But if you’re not involved in the day-to-day, it can be hard to know how those two things fit together or if they fit together at all.
\n\n\n\n[Josepha Haden Chomphosy 00:01:00]
\n\n\n\nToday, let’s take a brief tour of those two projects and why they came to be.
\n\n\n\nIn my timeline, work on the Photo Directory started before the work on Openverse, so that’s where we’ll start.
\n\n\n\nFor as long as I can remember, the WordPress community has raised the need for WordPress-first ways to have and host GPL-compatible photos for use in themes, site builds, and marketing efforts as a whole. As recently as 2016, that was still coming up as a question at various flagship events and among the career photographers that contribute their time to WordPress.
\n\n\n\nSo in 2017 and 2018, as attention started to turn toward rebuilding the CMS using blocks, it dropped down the list of priority items. But it never really went away as a thing that people were hoping we could do for the project as a whole. So in 2019, it was becoming clear that having open source-first tools of all varieties for people whose businesses were built on our software would help broaden the availability of the open source freedoms we believe in.
\n\n\n\n[Josepha Haden Chomphosy 00:02:00]
\n\n\n\nThis began the work on the Photo Directory with the intention of providing a GPL-friendly, community-driven repository of images. It has since launched, and we have photos in it now. We have a whole team around it. It’s wonderful. But that is how that all kind of came to be.
\n\n\n\nOpenverse, on the other hand, was launched as CC Search in 2019 with the laudable mandate to increase the discoverability and accessibility of open access media.
\n\n\n\nLate in 2020, while work on the Photo Directory was underway, Matt shared with me that the team was looking for a new project home. When I first met with them, they shared an overview of the product, which they shorthanded as an open source search engine that searches openly licensed images. We were working on a repo of openly licensed images, so clearly, this was all written in the stars. And so you might be asking yourself at this point, great, how does it work together?
\n\n\n\nI think for most of us, the timeline there kind of covers the question of what is the difference between these two things.
\n\n\n\n[Josepha Haden Chomphosy 00:03:00]
\n\n\n\nBut because I never know which of you will want to strike up a conversation about open source on an elevator, I’ve also got the elevator pitch version.
\n\n\n\nOpenverse is an open source search engine that searches, indexes, and aggregates copy left media from across the web using sources such as WordPress’s Photo Directory, Flickr’s CC Tagged Media, and Wikimedia, to name just a few.
\n\n\n\nAnother key difference between the Photo Directory and Openverse is that in order to contribute to the Photo Directory, now that it’s all built, that’s mostly done by submitting photos or reviewing photos. So you don’t really need to be a developer to join in.
\n\n\n\nOpenverse is not only a developer-centric contribution opportunity, but it also uses a different tech stack than WordPress as a whole. So it’s a good place for folks to go if they’re looking to broaden their horizons.
\n\n\n\nSo that’s your elevator pitch of what Openverse is and how it uses the Photo Directory.
\n\n\n\n[Josepha Haden Chomphosy 00:04:00]
\n\n\n\nYou have a couple of ways that you can get involved with these two projects. For the Photo Directory, as I mentioned at the start, you can always contribute photos, and they could always use more photo contributions.
\n\n\n\nI’ll include a link to the submission guidelines in the show notes below, and as I mentioned, it is a no-code way to give back to the WordPress project. So no code, development environments, and testing skills are required. The Photo Directory team also could always use more contributors to help with the moderating of photo submissions.
\n\n\n\nAnd so I’ll link to their making WordPress page in the show notes as well so that you can get started there.
\n\n\n\nAnd as I mentioned before, Openverse is an aggregator, so it doesn’t host any media itself, but it is always accepting suggestions for new GPL-compatible media providers. I’ll link the area where you can leave suggestions in the show notes as well.
\n\n\n\nAnd if you are more code inclined, there’s an open issue for adding Openverse browsing to the block editor right now.
\n\n\n\n[Josepha Haden Chomphosy 00:05:00]
\n\n\n\nSo I’ll link that issue in the show notes in case you thought to yourself, gosh, that sounds like my most favorite thing to do. That is where you can go.
\n\n\n\n[Josepha Haden Chomphosy 00:05:12]
\n\n\n\nThis leads us now to our small list of big things.
\n\n\n\nIn case you missed it, WordPress 6.1 is now available. It launched on November 1st. Late, late, late in the day, and so it was easy to miss if you’re used to seeing it at a particular time. We were about six hours later than usual. But if you go to wordpress.org/download, you can get your own copy there.
\n\n\n\nThe second thing on our small list of big things is that the Docs team had a contributor day. It was excellent. There’s a recap post up. I will include that in the show notes.
\n\n\n\nAnd then the final thing is that there was a recent hallway hangout that talked about the site editor and block themes.
\n\n\n\n[Josepha Haden Chomphosy 00:06:00]
\n\n\n\nThe video for that is also published. I will also share that in our show notes.
\n\n\n\nAnd that, my friends, is your small list of big things. Thank you 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";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:"13890";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:70:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"Introducing Twenty Twenty-Three";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/2022/11/introducing-twenty-twenty-three/";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, 08 Nov 2022 15:42:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:5:{i:0;a:5:{s:4:"data";s:6:"Design";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:"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:2;a:5:{s:4:"data";s:3:"6.1";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:3:"tt3";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:"twenty twenty-three";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=13892";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:376:"This post was written in collaboration with Lauren Stein (@laurlittle) and Anne McCarthy @annezazu). Twenty Twenty-Three is here, alongside WordPress 6.1! The new default theme offers a clean, blank canvas bundled with a collection of style variations. Style variations are predefined design options that give you the opportunity to alter the appearance of your 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: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:72:"https://wordpress.org/news/files/2022/11/Introducing-TT3_V4_captions.mp4";s:6:"length";s:8:"90767180";s:4:"type";s:9:"video/mp4";}}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:"Beatriz Fialho";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:2438:"\nThis post was written in collaboration with Lauren Stein (@laurlittle) and Anne McCarthy @annezazu).
\n\n\n\nTwenty Twenty-Three is here, alongside WordPress 6.1! The new default theme offers a clean, blank canvas bundled with a collection of style variations.
\n\n\n\nStyle variations are predefined design options that give you the opportunity to alter the appearance of your site without having to change your theme. This means that you can keep your template structure but change the visual details of your site with ease.
\n\n\n\nFor a truly diverse collection, Twenty Twenty-Three’s featured style variations were submitted by members of the WordPress community, resulting in 38 submissions from 19 people in 8 different countries. From those submissions, a curated collection of ten was chosen and bundled with the new theme.
\n\n\n\nThis approach to style variations ushers in the next generation of block themes, able to harness the potential of the platform’s latest design capabilities and tools directly in the Site Editor. Since style variations don’t require any code experience, you’re encouraged to tweak and/or create your own.
\n\n\n\nThank you to everyone who contributed. 
Useful links:
Download Twenty Twenty-Three
Twenty Twenty-Three Documentation
Twenty Twenty-Three Project Kick Off
Twenty Twenty-Three Selected Style Variations
Say hello to WordPress 6.1, “Misha,” inspired by the life and work of jazz pianist Mikhail “Misha” Alperin. Ukrainian-born Misha introduced the work of jazz ensembles globally and is celebrated as a founding member of the Moscow Art Trio.
“Misha” further refines the site-building experience. Inside WordPress 6.1 you’ll interact with enhancements that continue to make site creation more intuitive while pushing your creative boundaries further than ever. Don’t forget to enjoy some of Misha’s jazz piano as you take in all WordPress 6.1 has to offer.
The third major release of 2022 is here. Download it now! As of the time of this release, WordPress powers 43% of websites worldwide.
\n\n\n\nSite owners and administrators should upgrade today to take full advantage of the many stability, performance, and usability enhancements. Furthermore, WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.
\n\n\n\n\n\n\n\n\n\n\n\n\nThis release includes features that many in the WordPress Community have been most excited about since the start of this project. Additional enhancements and improvements to the editor give site owners more control and easier customization while offering a more cohesive experience to users. A lot of writing-focused improvements are included in the release, because if you’re giving voices to the voiceless you’ve got to focus on folks writing the copy.
\n\n\n\nSome of my favorite enhancements are the refined ability to select partial paragraphs in a block; settings to keep list view open by default; and the keyboard shortcut to add internal links expanded to all blocks.
\nJosepha Haden Chomphosy, Executive Director
After introducing foundational elements for block themes and style variations in releases 5.9 and 6.0, WordPress site builders welcome a new default theme, Twenty Twenty-Three, that is powered by 10 different styles and tagged as “Accessibility Ready.” These intentionally unique styles ensure users can apply a different look and feel to their site with a single click—all within a single theme.
\n\n\n\n
New and more refined templates now give site builders more control over the creation of their sites. In this suite of new templates, find a custom template for posts & pages in the Site Editor. Create and edit template parts like headers and footers more quickly with a new search-and-replace tool and easily view your new site.
\n\n\n\n
Thoughtful upgrades to the controls for design elements and blocks make laying out and building your new site a more consistent, complete, and intuitive experience.
\n\n\n\n
New fallback options in the navigation block mean you can edit the menu that’s open; no searching needed. Plus, the controls for choosing and working on menus have their own place in the block settings. The mobile menu system also gets an upgrade with new features, including different icon options, to make the menu yours.
\n\n\n\n
View and manage post and page settings with a better-organized display improving the use of features like template picker and scheduler.
\n\n\n\n
When locking blocks, a new toggle lets you apply your lock settings to all the blocks in a containing block like the group, cover, and column blocks.
\n\n\n\n
Various blocks have improved placeholders that reflect customization options to help you design your site and its content. For example, the Image block placeholder displays custom borders and duotone filters even before selecting an image.
\n\n\n\nThe List and Quote blocks now support inner blocks, allowing for more flexible and rich compositions like adding headings inside your Quote blocks.
\n\n\n\nFor developers working with block themes and/or theme.json, fluid typography lets you define font sizes that adapt for easy reading in any screen size.
In WordPress 6.0, site builders could add suggested patterns so that when creating a new page, you did not have to start blank. In 6.1, site builders can continue to opt-in to this feature for not only pages but for any post type.
\n\n\n\nThe Themes Directory has a filter for block themes, and a pattern preview gives a better sense of what the theme might look like while exploring different themes and patterns.
\n\n\n\nSite Editor settings are now persistent for each user. This means your settings will now be consistent across browsers and devices.
\n\n\n\nThe CSS rules for margin, padding, typography, colors, and borders within the styles engine are now all in one place, reducing time spent on layout-specific tasks and helps to generate semantic class names.
\n\n\n\nUpdates include styling elements like buttons, citations, and links globally; controlling hover, active, and focus states for links using theme.json (not available to control in the interface yet); and customizing outline support for blocks and elements, among other features.
\n\n\n\nThe default content dimensions provided by themes can now be overridden in the Styles Sidebar, giving site builders better control over full-width content. Developers have fine-grained control over these controls.
\n\n\n\nBlock template parts can now be defined in classic themes by adding the appropriate HTML files `parts` directory at the root of the theme.
\n\n\n\nNew filters let Query Block variations support custom queries for more powerful variations and advanced hierarchical post types filtering options.
\n\n\n\nLeverage filters in the Styles sidebar to control settings at all four levels of your site—core, theme, user, or block, from less to more specific.
\n\n\n\nSave time and avoid hard-coding values into a theme with preset margin and padding values for multiple blocks.
\n\n\n\nThanks to content-only editing settings, layouts can be locked within container blocks. In a content-only block, its children are invisible to the List View and entirely uneditable. So you control the layout while your writers can focus on the content. Combine it with block-locking options for even more advanced control over your blocks.
\n\n\n\nAccessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.1 includes nearly 60 updates specifically focused on enhancing the accessibility of the platform. Read these updates to learn more about the continual initiatives aimed at improving accessibility.
\n\n\n\nWordPress 6.1 resolves more than 25 tickets dedicated to enhancing performance with improvements for every type of site. A full breakdown can be found in the Performance Field Guide.
\n\n\n\nSee WordPress 6.1 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.1.
\n\n\n\nExplore learn.wordpress.org for brief how-to videos and lots more on new features in WordPress. Or join a live interactive online workshop on a specific WordPress topic.
\n\n\n\nDevelopers can explore the WordPress 6.1 Field Guide, complete with detailed developer notes to help you build with and extend WordPress. Read the WordPress 6.1 Release Notes for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.
\n\n\n\nThe group listed below tirelessly supported the release, from conception to ship date, and beyond:
\n\n\n\nRelease Lead: Matt Mullenweg
Release Coordinators: Héctor Prieto and Jonathan Desrosiers
Core Tech Co-Leads: Mike Schroder, David Baumwald, and Jeff Paul
Editor Tech Co-Leads: Michal Czaplinski, Bernie Reiter, and Carlos Bravo
Core Triage Co-Leads: JB Audras and Ahmed Chaion
Editor Triage Co-Leads: Nick Diego and Anne McCarthy
Documentation Co-Leads: Birgit Pauli-Haack, Milana Cap, and Femy Praseeth
Marketing & Communications Co-Leads: Jonathan Pantani and Dan Soschin
Test Lead: Brian Alexander
Design Lead: Rich Tabor
Default Theme Co-Leads: Beatriz Fialho & Sarah Norris
\n\n\n\n\n\n\n\n\nThank you to all the contributors who dedicated time and energy to bring the best WordPress experience to everyone.
\nJosepha Haden Chomphosy
10upsimon · 1naveengiri · Aaron D. Campbell · Aaron Jorbin · Aaron Robertshaw · Abha Thakor · Abu Hurayra · Adam Bosco · Adam Pickering · Adam Silverstein · Adam Wiltgen · Adam Zielinski · Addie · Adil Öztaşer · aduth · Aezaz Shekh · afrid1719 · Ahmed Chaion · Ahmed Saeed · Akash Mia · Aki Hamano · Akram ul haq · Akshit Sethi · Alain Schlesser · alamgircsebd · AlanP57 · alansyue · Albert Juhé Lluveras · Alberuni Azad. · Alejandro J. Sanchez P. · Aleksej · Alex Concha · Alex Lende · Alex Mills · Alexis Coulombe · alexstine · allancole · allisonplus · Alvaro Gómez · amirkamizi · Amjad Ali · Anantajit JG · Andrea Fercia · Andreas · Andrei Draganescu · Andrei Surdu · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Wilder · AndrewNZ · Andrey "Rarst" Savchenko · Andrija Naglic · André · Andy Fragen · Andy Keith · Aniket Patel · anitanenova · Ankit K Gupta · Anna Bansaghi · Anne McCarthy · Ante Laca · Anthony Burchell · Anton Vlasenko · apedog · apokalyptik · AR Rasel · arcangelini · archon810 · Ari Stathopoulos · Ariel Chinn · Arjun Singh · Arnab Mondal · Arslan Kalwar · Artur Grabowski · Arunas Liuiza · Aspexi · Aurooba Ahmed · Austin Matzko · Ayesh Karunaratne · azurseisme · BaneD · barneydavey · Bartosz Bobnis · Beatriz Fialho · Ben Dwyer · Ben Greeley · Benachi · Benjamin Grolleau · Benoit Chantre · Bernhard Reiter · Bernie Reiter · Bethany Chobanian Lang · Bhavik Kalpesh · Bhrugesh Bavishi · bing · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · bjorn2404 · Bob · bobbingwide · bonger · Boone Gorges · Brad Jorsch · Brandon Kraft · Brian Alexander · Brian Gardner · Bruno Cantuaria · Bruno Ribaric · burgiuk · Burhan Nasir · bwbama · cadlec · cagsmith · Carlos Bravo · Carlos Garcia Prim · Carolina Nymark · cavalierlife · cdbessig · Chad Chadbourne · Chandra M · Channing Ritter · Chetan Prajapati · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Budd · Chris Hardie · Chris Zarate · chriscct7 · chrisguitarguy · Christian-W. Budde · Christina Voudouris · Christoph Daum · Christopher Finke · Chuck Reynolds · chynnabenton · ckanderson22 · Clayton Collie · CodePoet · codesdnc · codewhy · Colin Stewart · colonelphantom · Cory Birdsong · Courtney Robertson · craigfrancis · crazycoders · Crisoforo Gaspar · Cupid Chakma · Curdin Krummenacher · cyrillbolliger · Daijiro Miyazawa · dainemawer · Daisy Olsen · Dale du Preez · Damon Cook · damonganto · Dan Farrow · Dan Soschin · Daniel Bachhuber · Daniel Iser · Daniel Richards · Daniel Schutzsmith · Daniele Scasciafratte · darerodz · Daria · Darin Kotter · Darko G. · darkskipper · Darren Coutts · Dat Hoang · datainterlock · Dave Hilditch · dave1010 · David Anderson · David Baumwald · David Biňovec · David C · David Calhoun · David E. Smith · David Goring · David Gwyer · David Herrera · David Rozando · David Smith · David Vongries · daxelrod · daymobrew · Dean Sas · Deepak Vijayan · Denis de Bernardy · Denis Žoljom · denishua · Dennis Claassen · Dennis Snell · derekblank · Derrick Hammer · Dharmesh Patel · dhl · Diane Co · Dilip Bheda · dingdang · Dion Hulse · Dipak Parmar · divyeshgodhani · Dominik Schilling · donmhico · Doug Wollison · Dougal Campbell · Drew Jaynes · Drivingralle · drzraf · Dwain Maralack · Dzikri Aziz · Dōvy Paukstys · eclev91 · Edwin Cromley · eedee · Ehtisham S. · Eliezer Peña · Ella van Durpe · Emily Clarke · Emmanuel Hesry · Enrico Battocchi · Erick Hitter · Erik · Erik Betshammar · Estela Rueda · Eugene M · Eugene.Manuilov · eugene.manuilov · Evan Herman · Evan Mattson · Evan Mullins · Fabian Kägy · Faisal Alvi · Faison · Felipe Elia · Felix Arntz · Fellyph Cintra · Femy Praseeth · Florian Brinkmann · fpodhorsky · Francisco · franzaurus · Fuad Ragib · furi3r · gabri3lmarques · Gabriel de Tassigny · Gabriel Rose · gamecreature · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · garymatthews919 · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · gigitux · giox069 · gisgeo · giuseppemazzapica · Glen Davies · goldenapples · Grégory Viguier · graham73may · Grant M. Kinney · Greg Niedzielski · Greg Ziółkowski · gRegor Morrill · gunterer · Gustavo Bordoni · gvgvgvijayan · h2ham (Hiromu Hasegawa) · hakanca · hakre · Hans-Christiaan Braun · Hardik Thakkar · Harit Panchal · harshvaishnav · Hasanuzzaman · Hauwa Abashiya · Helen Hou-Sandi · Henrique Iamarino · Henry Wright · here · Herre Groen · Hilay Trivedi · hiren sanja · hiyascout · Howdy_McGee · hugodevos · huubl · hztyfoon · Héctor Prieto · Ian Belanger · Ian Dunn · iansvo · iCaspar · Ignacio Cruz Moreno · Igor · igrigorik · ilovecats7 · ilunabar · imadarshakshat · Innovext · ipajen · Ipstenu (Mika Epstein) · irecinius · Isabel Brison · Iulia Cazan · ivanjeronimo · iviweb · J.D. Grimes · Jacob Schweitzer · Jakaria Istauk · James · James Koster · jamesckemp · jamieburchell · Jan Thiel · Jarret · Jason Johnston · Jasper Kinoti · Javier Arce · Javier Carazo · Javier Casares · Jay Trees · jchambo · Jean-Baptiste Audras · jeawhanlee · Jeff Ong · Jeff Paul · Jeff Uberstine · Jeremy Felt · Jeremy Herve · JeroenReumkens · Jessica Lyschik · jhart35 · jhnstn · jigar bhanushali · jnz31 · Joe Dolson · Joe Hoyle · Joe McGill · joelhardi · joelmadigan · Joen Asmussen · John Blackbourn · John James Jacoby · John Regan · John Watkins · johnmark8080 · Jon Brown · Jon Surrell · Jonathan Bossenger · Jonathan Desrosiers · Jonathan Pantani · jonmackintosh · Jonny Harris · jonny-s · Jono Alderson · Joost de Valk · Jorge Costa · Jos Velasco · Joseph Grainger · Josepha Dambul · Josepha Haden · Josh Habdas · Joshua Abenazer · Joy · jrbeilke · jsh4 · jsnajdr · Juhi Saxena · Julie Moynat · Juliette Reinders Folmer · Julio Potier · just0nequestion · Justin Ahinon · Justin Sainton · Justin Tadlock · Justin Welenofsky · jyolsna · K. Adam White · kacper3355 · KafleG · Kai Hao · Kajal Gohel · Kalpesh Akabari · Kapil Paul · Kari Anderson · karlgroves · Karlijn Bok · Kaspars · Kathryn Presner · kbrownkd · Keanan Koppenhaver · Kelly Choyce-Dwan · Kelly Hoffman · Kevin Behrens · Kevin Hagerty · Khoi Pro · Khokan Sardar · killua99 · Kishan Jasani · kitchin · Kjell Reigstad · kkmuffme · klewis · Knut Sparhell · Koen Van den Wijngaert · Konrad.K · Konstantin Kovshenin · Konstantin Obenland · konyoldeath · Kris Kelvin · KrishaWeb · Krupal Panchal · Kunal Madhak · Kurt Payne · kwillmorth · Kyle B. Johnson · Kyle Nel · larsmqller · laurelfulford · Lauren Stein · laurent22777 · lazam786 · Lee Willis · leemon · Lena Morita · Leo Milo · leogermani · Linkon Miyan · Linnea Huxford · lonnylot · Lovekesh Kumar · Lovro Hrust · lozula · Lucas Bustamante · lucilastancato · luigipulcini · Luis Felipe Zaguini · luisherranz · Luiz Araújo · Lukas Niebler · Luke Cavanagh · M S Newaz · Maarten · Maciej · maciejmackowiak · Madhu Dollu · Madhu Dollu · Maggie Cabrera · Mahrokh · maksimkuzmin · malthert · manfcarlo · Manish Songirkar · Manzoor Wani · Manzur Ahammed · Marc · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marek Dědič · Marianna · Marie Comet · Marin Atanasov · Mario Santos · Marius L. J. · Mark Biek · Mark Howells-Mead · Mark Jaquith · Mark Parnell · Marko Heijnen · Markus · Markus Kosmal · Martijn van der Klis · Martin Stehle · martin.krcho · Mary Baum · Mashu · masteradhoc · Matías Emanuel Surdi · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Keys · Matt Mullenweg · Matt Wondra · Matthew Boynes · Matthew Eppelsheimer · Matthias Pabst · Matthias Reinholz · mattyrob · Mauriac AZOUA · Maxime J. · Maxime Meganck · Mayank Majeji · maythamalsudany · Mayuge · mcliwanow · Md Rakib Hossain · Md. Russel Hussain · mdrago · Mehedi Foysal · Meher Bala · Mehul Kaklotar · Mel Choyce-Dwan · meloniq · Merkys Maliukevičius · meysam norouzi · Micha Krapp · Michael Bourne · Michael Burridge · Michal Czaplinski · Miguel Axcar · Miguel Fonseca · Mihai Dumitrascu · Mike Crantea · Mike Glendinning · Mike Hansen · Mike Jolley (a11n) · Mike Schroder · mikemanzo · Milana Cap · Milind More · mimi · Minal Diwan · miya · Mladen · Mohammad Jangda · MohammadJafar Khajeh · Mohit Dadhich · Monique Dubbelman · moto hachi · mreishus · mrobit · msolution · mtias · Muhammad Arslan · Mukesh Panchal · Muntasir Mahmud · Mustaque Ahmed · mvraghavan · mw108 · mweichert · n8finch · Nahid Hasan · Nalini Thakor · Namith Jawahar · Naresh Bheda · Nate Allen · Nathan · Nathan Johnson · navigatrum · neffff · nendeb · Neycho Kalaydzhiev · Nicholas Garofalo · Nick Diego · Nick Halsey · Nico · nidhidhandhukiya · Nik Tsekouras · nikkigagency · Niloy · Ninos · Nithin John · Nithin SreeRaj · nlpro · Noah Allen · noplanman · nouarah · NumidWasNotAvailable · nunomorgadinho · Nurul Umbhiya · nuvoPoint · nvartolomei · oakesjosh · Obayed Mamur · obliviousharmony · ockham · oguzkocer · Olga Gleckler · Oliver Stapelfeldt · OllieJones · oneearth27 · Onni Hakala · opr18 · ovidiul · p_enrique · Paal Joachim Romdahl · Pablo Postigo · PabloHoney · palmiak · Paolo L. Scala · Paragon Initiative Enterprises · Parham Ghaffarian · Pascal Birchler · Patrick Groot · Paul Bearne · Paul Biron · Paul Kevan · Paul Ryan · Paulo Cruz · Paulo Trentin · Pavan Patil · pavelschoffer · pbking · Pedro Mendonça · Peter Westwood · Peter Wilson · petitphp · Petter Walbø Johnsgård · Phil Johnston · Phill · Pierre Sylvestre · Pieterjan Deneys · Piotrek Boniu · Pippin Williamson · pkolenbr · Pooja Derashri · Pooja N Muchandikar · Praful Patel · Pratiksha · presscustomizr · Presskopp · presstoke · Priyo Mukul · prokium · pypwalters · Q · Rachel Baker · Rachel Peter · raduiason · Rafi Ahmed · Rahi Prajapati · Rajan Panchal · Rajesh Raval · ralucastn · Ramanan · Ramon Ahnert · Ramon Corrales · ramon fincken · Ramon James · Randhir Jha · Ravikumar Patel · rcanepa · rebasaurus · Rehan Ali · Remy Perona · Renatho (a11n) · renegeuze · Reuhno · rflw · Riad Benguella · Rich Tabor · Rinat · Rinky Chowdhury · Rishi Shah · rjasdfiii · rkaiser0324 · Robert Anderson · Robert Chapin · robertght · Robin · robmiller · rodricus · rodrigosevero · Rolf Allard van Hagen · Rolf Siebers · rollybueno · Romain Herault · romulodl · ross_ritchey · Roy · Russell Aaron · Ryan Boren · Ryan Kienstra · Ryan McCue · Ryan Murphy · Ryan Welcher · Sébastien SERRE · Sérgio Gomes · Sören Wrede · Sabbir Ahmed · Sajjad Hossain Sagor · Sakri Koskimies · Sami Keijonen · Sampat Viral · Samuel Wood (Otto) · Sandip Mondal - a11n · Sandra Sanz · Sarah Norris · sarahricker · Sathiyamoorthy V · Saumya Majumder · Saurabh Sharma · Scott Fennell · Scott Kingsley Clark · Scott Lesovic · Scott Taylor · scribu · Sean Fisher · Sebastian Pisula · seieric · Sergey Biryukov · Sergio Scabuzzo · seriouslysenpai · Seth Alling · shangidah afroz · Shannon Little · Sharjeel Khan · Shoaib Ali · Shraboni · Shreyas Ikhar · shuvo586 · siddharth ravikumar · Siddharth Thevaril · Siobhan · sirzooro · Slava Abakumov · Slobodan Manic · Smit Rathod · sobatkras · Stanislav Khromov · SteelWagstaff · Stefano · Stefano Minoia · Stefanos Togoulidis · stentibbing · Stephen Bernhardt · Stephen Edgar · Stephen Page · Sterling Hamilton · Steven Lin · steveo2000 · studiolxv · Subrata Sarkar · Sumit Bagthariya · Sumit Singh · Sumit Singh · Sumon Sarker · SunilPrajapati · sunyatasattva · Sybre Waaijer · Synchro · system909 · Tahmid ul Karim · Takashi Kitajima · Tammie Lister · Tanbir Ahmod · Tanvirul Haque · Taras Dashkevych · targz · Taylor Lovett · tazotodua · tbember · Teddy Patriarca · Tellyworth · Terence Eden · tharsheblows · thejaydip · Thierry Muller · Thijs · Thomas Griffin · Thorsten Schraut · threadi · Tiffany Bridge · Till Krüss · Timi Wahalahti · Timothy Jacobs · Titus Moore · TobiasBg · tobifjellner (Tor-Bjorn Fjellner) · Tom de Visser · Tom J Nowell · Tom Janssen · Tom Rhodes · Tomasz Tunik · tomepajk · Tomoki Shimomura · Toni Viemerö · tony.localword · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · transl8or · Travis Smith · Tremi Dkhar · TrevorPolischuk · Trinadin · Tung Du · turtlepod · Ugyen Dorji · Ulrich · Umesh Gupta · upadalavipul · utsavmadaan823 · Vagelis · varma · vasartam · vdankbaar · Velochicdunord · Vicente Canales · vikasprogrammer · Virginie Garnier · Vishal Kakadiya · vortfu · vtad · webbeetle · WebMan Design | Oliver Juhas · Weston Ruter · whaze · Whissi · William Earnhardt · williampatton · withinboredom · woji29911 · Yahil Madakiya · Yan Knudtskov · Yann · Yoav Farhi · Yohann Billard · Yui · yuu · zaerl · Zebulan Stanphill · Zenaul Islam · ziposc · Česlav Przywara · 沈唁
WordPress 6.1 would not have been possible without the contributions of more than 800 people in over 60 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\nBy release day, 71 locales had translated 90-percent or more of WordPress 6.1 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in over 200 languages.
\n\n\n\nMany thanks to all of the community volunteers who contribute to the support forums by answering questions from WordPress users around the world.
\n\n\n\nIf contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to Make WordPress and explore the product roadmap on the core development blog.
\n\n\n\nWordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.
\n\n\n\nWordPress believes in democratizing publishing and the freedoms that come with open source. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.
\n\n\n\nLearn more about WordPress and how you can join our community to help shape the future of the world’s most popular website platform.
\n\n\n\nAnother release,
Mark it down as completed.
Breathe, relax, and cheers!
This announcement was updated on Tue Nov 8 at 9:00 p.m. UTC to clarify some features in 6.1.
\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:"13798";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: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:44:"People of WordPress: Raghavendra Satish Peri";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://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/";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, 31 Oct 2022 19: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: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=13705";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:138:"The latest People of WordPress story features Raghavendra Satish Peri, a digital entrepreneur in web accessibility and digital marketing. ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Meher Bala";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:15167:"\nThis month, in the run up to WordPress Accessibility Day, we feature Raghavendra Satish Peri, a blogger turned digital entrepreneur based in India, who specializes in web accessibility and digital marketing.
\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 network of contributors.
\n\n\n\n
Raghavendra Satish Peri says WordPress is more than a way to succeed online. It’s a community that has always answered his questions and helped him learn, and has enabled his voice to be heard across the world.
\n\n\n\nThese are motivating benefits for Raghavendra, who has a vision impairment that introduces challenges to many of the things he wants to do. The WordPress community has helped him make some of his dreams come true. After chatting with others at WordPress events, about his wish to go trekking and running, he found he was later contacted by people in the community went with him to do just that.
\n\n\n\n
He also found WordPress events a way to raise the importance of accessibility issues, share tips, and connect local communities so they can collaborate on items both within and outside WordPress.
\n\n\n\nA key asset for Raghavendra has been the support of his family as he coped with his progressive blindness. His sister took charge of teaching him important social and life skills, so he could navigate his country’s rigorous education system.
\n\n\n\nThose were the early days of technology everywhere, and nobody much was thinking about using it in education and day-to-day life.
\n\n\n\nWhen Raghavendra got his first computer, in 2004, it was a revelation. His sister taught him to use the internet efficiently, and he taught himself a few basics of programming. Soon he was spending 10 to 12 hours a day exploring the online world and learning about the web.
\n\n\n\nIn 2006, he learned basic web design and began to sell website templates. His growing interest in search engines and content led him to WordPress. As the years progressed, his eyesight deteriorated. He had to relearn his skills and acquire new ones to compensate. When he could no longer see the computer screen, he learnt to use screen readers.
\n\n\n\nAt that point there was a gap: he had the same business skills, but he couldn’t apply them as effectively until he got comfortable with using screen readers.
\n\n\n\n
To help achieve that, Raghavendra moved to Bengalaru, where he got a full education in screen-reader technology and took a job as a consultant in digital accessibility.
\n\n\n\nHe recalls learning from that time that, in his words: “Some things are important, but one needs to let them go so that more important things can take the new space.”
\n\n\n\nDuring his stay in Bengaluru, he stumbled on the idea of blogging and audiobooks. On his 23rd birthday, he had two firsts: registering a domain and publishing a blog post. At first he wrote about things happening in his daily life, which initially got low responses. But when he started attending blogging and tech meetups, he received encouragement from fellow bloggers who complimented him on his writing style.
\n\n\n\nUsing WordPress to publish his story, Raghavendra found a love for writing and this made him want to learn and understand WordPress much better.
\n\n\n\n\n\n\n\n\n“Writing freed my mind and soul from the pain and sorrow; it takes a person into a Zen state where one can understand their soul once they see their own thoughts on paper.”
\nRaghavendra Satish Peri
There were still some ongoing challenges arising from his difficulties with seeing. For example, Raghavendra found coding was made more complicated. But he took it slowly, and he improved steadily.
\n\n\n\nHe started as many WordPressers do, installing themes and plugins, and making minor changes to the code. Ultimately, he moved all of his sites to WordPress, and as he learned more about WordPress, he could help his friends and family more with their projects.
\n\n\n\nAfter just a few years, Raghavendra had the skills and the confidence to build just about anything in WordPress, progressing from simple to complex websites.
\n\n\n\nToday Raghavendra is a successful entrepreneur. He sees his life as full of promise. WordPress still helps him grow every day, professionally and personally.
\n\n\n\n\n\n\n\n\n“There is always hope for tomorrow! Do not look for the light at the end of the tunnel, embrace the darkness, listen to the quietness, and feel the airflow. You will know that light is ahead even before you see it.”
\nRaghavendra Satish Peri
Another thing Raghavendra has in common with many WordPressers is his enthusiasm and involvement in the community. As he has learnt more about the software, he felt he needed to be involved with improving accessibility too. He started to help organize local meetups and conferences and encourages others to give time and skills to contribute too.
\n\n\n\n
He follows software development closely, especially where WordPress meets accessibility.
\n\n\n\nIn 2020, on learning about a global WordPress Accessibility event, he applied and became a speaker. His topic was Gutenberg Accessibility, A Screen Reader User’s Perspective. His interest continued as a result of this event, and he wanted to be part of growing its audience and impact, initially through joining its dedicated channel on Slack. Eventually, he joined the organizing team for future events.
\n\n\n\nHelping run WordPress events brought together all of Raghavendra’s existing skills. It taught him a lot about what it takes to make an event truly inclusive, from captions and sign language to media players and more.
\n\n\n\nAs his involvement has grown, Raghavendra has found it has become easier to source and use resources that make events and presentations more accessible. But knows there’s always more that can be learnt in this area, and encourages others to use understanding from events like the Accessibility Days in their conferences.
\n\n\n\nJoin the global WordPress Accessibility Day 2022 online on November 2-3, 2022. It’s free to register!
\n\n\n\n
In 2021, Raghavendra underwent his most challenging event to date, when he had a kidney transplant. To motivate himself, he started a website that focuses on accessibility and inclusive design. This prompted him to start an accessibility community to help fill the gaps in accessibility knowledge. Today, it is one of India’s largest online accessibility communities, educating developers and designers and training people with disabilities to build a career in accessibility testing.
\n\n\n\n
Raghavendra is also a keen user of the WordPress Gutenberg editor and builds all his websites using it. Though content creation and editing can still pose him difficulties, he finds the front end of the Gutenberg blocks very accessible. He believes in participating in the software to make it a better experience for all.
\n\n\n\n\n\n\n\n\n“I decided to live my life to the fullest and make my mark on the world. This thought keeps me motivated.”
\nRaghavendra Satish Peri
After a successful transplant, he lives a disciplined life with a few restrictions. He continues to enjoy working in-depth in disability, accessibility, and inclusion spaces. Raghavendra hopes others will join with him and the thousands of other people who collaborate to make a difference.
\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\nThank you to Raghavendra Satish Peri (@tarkham) for sharing his experiences for this latest edition.
\n\n\n\nThanks to Meher Bala (@meher), Abha Thakor (@webcommsat) and Surendra Thakor (@sthakor) for interviews and writing this feature, to Mary Baum (@marybaum), Chloe Bringmann (@cbringmann), and Larissa Murillo (@lmurillom) for 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
\nVersion 5.0.2 of the Akismet plugin for WordPress is now available. This update contains the following improvements:
\n\n\n\nTo 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.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Dec 2022 17:20:06 +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:17:"Christopher Finke";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: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:76:"WordPress.org blog: Share Your Experience: The 2022 WordPress Survey is Open";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=14062";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:57:"https://wordpress.org/news/2022/12/2022-wordpress-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:4507:"Each year, members of the WordPress community (users, site builders, extenders, and contributors) provide valuable feedback through an annual survey. Key takeaways and trends that emerge from this survey often find their way into the annual State of the Word address, are shared in the public project blogs, and can influence the direction and strategy for the WordPress project.
\n\n\n\nSimply put: this survey helps those who build WordPress understand more about how the software is used, and by whom. The survey also helps leaders in the WordPress open source project learn more about our contributors’ experiences.
\n\n\n\nTo ensure that your WordPress experience is represented in the 2022 survey results, take the 2022 annual survey now.
\n\n\n\n\n\n\n\nYou may also take the survey in French, German, Italian, Japanese, Russian, or Spanish, thanks to the efforts of WordPress polyglot contributors. These are the most frequently installed languages based on the number of WordPress downloads.
\n\n\n\nThe survey will be open through the end of 2022, and then WordPress plans to publish the results sometime in 2023. This year, the survey questions have been refreshed for more effortless survey flow, completion, and analysis. Some questions have been removed, while a few new ones are now present, reflecting the present and future of WordPress. If you’re looking for the analysis of the 2021 survey results, those will also be shared in early 2023.
\n\n\n\nHelp spread the word about the survey by sharing it with your network, through Slack, or within your social media accounts. The more people who complete the survey and share their experience with WordPress, the more the project as a whole will benefit in the future.
\n\n\n\nData security and privacy are paramount to the WordPress project and community. With this in mind, all data will be anonymized: no email addresses nor IP addresses will be associated with published results. To learn more about WordPress.org’s privacy practices, view the privacy policy.
\n\n\n\nThank you to the following WordPress contributors for assisting with the annual survey project, including question creation, strategy, survey build-out, and translation:
\n\n\n\ndansoschin, _dorsvenabili, angelasjin, arkangel, audrasjb, atachibana, bjmcsherry, chanthaboune, eidolonnight, fernandot, fierevere, fxbenard, jdy68, jpantani, laurlittle, nao, nielslange, peiraisotta, piermario, rmartinezduque, santanainniss.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Dec 2022 16:00:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Chloe Bringmann";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: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:55:"Do The Woo Community: Episode 300: The Hosts, My Heroes";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=73766";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:52:"https://dothewoo.io/episode-300-the-hosts-my-heroes/";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:355:"There was no better way to celebrate episode 300 of the podcast than to celebrate our hosts.
\n>> The post Episode 300: The Hosts, My Heroes appeared first on Do the Woo - a WooCommerce Builder 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:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Dec 2022 11:14:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;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:99:"WPTavern: ElasticPress 4.4.0 Adds New Status Report Page and Instant Results Template Customization";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=139973";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:110:"https://wptavern.com/elasticpress-4-4-0-adds-new-status-report-page-and-instant-results-template-customization";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:2708:"10up has released version 4.4.0 of ElasticPress, its enhanced search plugin that speeds up searching while reducing the load on WordPress sites. The plugin is based on Elasticsearch and is used by customers of the ElasticPress.io service (a SaaS solution), as well as those who are hosting their own Elasticsearch instance.
\n\n\n\nThis update adds a new “Status Report” page in the dashboard with information that can be helpful for troubleshooting ElasticPress and synced content. The UI uses Gutenberg components for the collapsible sections. Version 4.4.0 introduces a new query logger functionality that stores failed queries (up to 5 in the last 24 hours) and displays an admin notice if failed queries are detected. The failed queries are displayed on the new Status Report page.
\n\n\n\nAnother highlight of this release is the ability to customize the template for Instant Results. It gives developers a JavaScript hook for replacing the component used to render search results in Instant Results. The Instant Results feature was introduced in March with limited customization capabilities. It added a new search modal over the page content that inherits the site’s styles. Developers could adjust the appearance and expose facets, but this new update gives them control over the whole template.
\n\n\n\nAnother small but useful update in this release is the ability to exclude a specific post from Search. This helps site owners further customize the search experience to deliver only the intended results.
\n\n\n\nDevelopers who are using the plugin should take note of the announcement included in this release regarding the migration of the Users feature to the ElasticPress Labs plugin, which houses more experimental features:
\n\n\n\n\n\n\n\n\nNote that starting from the ElasticPress 5.0.0 release the
\nUsersfeature will be moved to the ElasticPress Labs plugin. TheTermsandCommentsfeatures will remain in ElasticPress but will be available only if enabled via code.
Check out the full list of updates and bug fixes on GitHub in the changelog for 4.4.0.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Dec 2022 05:22:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:67:"WPTavern: WordPress Versions 3.7-4.0 No Longer Get Security Updates";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=139956";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://wptavern.com/wordpress-versions-3-7-4-0-no-longer-get-security-updates";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:1338:"In September, WordPress’ Security Team announced it would be dropping support for versions 3.7 through 4.0 by December 1, 2022. Yesterday the final releases for these versions (3.7.41, 3.8.41, 3.9.40, and 4.0.38) were made available to the very small percentage of users who are running ancient versions of WordPress.
\n\n\n\nAs part of the final releases, the upgrade notification now informs users that they are on a version that is no longer receiving security updates. This affects fewer than 1% of total installs. The vast majority of WordPress sites are running 4.1 or later and will continue receiving security updates.
\n\n\n\nWherever possible, WordPress users should be running 6.1.1 on PHP 8 or later. (Although PHP 7.4 is the minimum version required to use WordPress, PHP 7.4 reached end of life two days ago and will no longer be receiving security updates. Version 8.0 will reach EOL in 11 months.)
\n\n\n\nNow that the Security Team is no longer obligated to backport security updates to very old versions, it frees up their time to better support newer versions 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 30 Nov 2022 20:53:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;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:"WordPress.org blog: People of WordPress: Huanyi Chuang";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=13562";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/2022/11/people-of-wordpress-huanyi-chuang/";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:9814:"This month we feature Huanyi (Eric) Chuang, a front end developer from Taiwan, who helps connect local groups to WordPress and the worldwide open source community. He is part of the team helping to make the first WordCamp Asia a success in 2023.
\n\n\n\nThe People of WordPress series shares some of the inspiring stories of how people’s lives can change for the better through WordPress and its global network of contributors.
\n\n\n\n\n\n\n\nHuanyi’s first footsteps in WordPress began in 2017 when he worked for a firm that built blogs and developed ad content for clients.
\n\n\n\nAfter building a few sites using the platform, he discovered child themes and through them opened up a world of possibilities for his clients. To this day, he uses child themes to deliver truly custom designs and functionality for clients.
\n\n\n\nLater in his career, Huanyi moved into digital marketing, integrating sites with massive ad platforms like Google and Facebook. This led him to learn to work with tracking code and JavaScript. He also began his learning journey in HTML, CSS, and PHP, to be able to improve his development skills and customize child themes.
\n\n\n\nHuanyi pictured in Australia during one of his travels meeting a koala bear.\n\n\n\nWhen Huanyi had a problem with a client’s site, he looked to WordPress meetups near where he lived in Taipei to help find the solutions.
\n\n\n\n\n\n\n\n\n“When I encountered an issue with the custom archive pages, a local meetup announcement showed up on my WordPress dashboard.”
\nHuanyi Chuang
At the meetup, he met more experienced WordPress users and developers there, who answered his questions and helped him learn.
\n\n\n\n“When I encountered an issue with the custom archive pages, a local meetup announcement showed up on my WordPress dashboard. That was my original connection with the local community,” Huanyi said.
\n\n\n\nThe WordPress community gave Huanyi a chance to connect with people, feed his curiosity about the software, and join a circle of people he could share this interest.
\n\n\n\nAt first, he thought meetups were an opportunity to source new clients, and he took his business cards to every event. However, he soon found that these events offered him the opportunity to make friends and share knowledge.
\n\n\n\nFrom then on, Huanyi started focusing more on what he could give to these events and networks, making new friends, and listening to people. This led him to share as a meetup speaker his own commercial website management experience.
\n\n\n\nIt was going to his first meetup and then getting involved with WordCamps that changed Huanyi’s whole relationship with WordPress.
\n\n\n\n\n\n\n\nIn 2018, he took the step to help as an organizer, having joined the Taoyuan Meetup in Taiwan. He played several parts across the organizing team, and the welcoming feeling he got in every situation encouraged him to get more involved.
\n\n\n\nHe recalls meeting new friends from different fields and other countries, which gave him a great sense of achievement and strengthened his passion for participating in the community.
\n\n\n\nWhen the team started this meetup, numbers were much lower than in the group in the city of Taipei, but they were not disheartened and gradually grew the local WordPress community.
\n\n\n\nThey created a pattern of ‘multiple organizers,’ which spread the workload and grew friendships.
\n\n\n\n\n\n\n\n\n“Being connected to and from meetups is the most valuable part of the community. Having these friends makes me gather more information. We share information and benefit from others’ information, and thus we gain more trust in each other. With such credibility, we share more deeply and build deeper relations.”
\nHuanyi Chuang
Before the pandemic, the meetup met every month and grew to become the second largest meetup in Taiwan. Huanyi also contributed to the WordPress community as an organizer of WordCamp Taipei 2018 in the speaker team and lead organizer of WordCamp Taiwan 2021.
\n\n\n\nAccording to Huanyi, you will always have something to take home with you. It might be new information or experiences. It might be plugins or theme ideas. But most of all, it is the chance to meet fascinating people and make new friends.
\n\n\n\n\n\n\n\n\nHuanyi’s message to other contributors:
\n
“Keep participating, and you will find more you can achieve than you expect.”
He added that long-term participation will ‘let you feel the humanity behind the project’.
\n\n\n\n\n\n\n\nHuanyi believes WordPress has the power to break down the barriers between designers, project managers, developers, marketers, writers, and publishers. In Taiwan, he said WordPress is ‘a common protocol’ that lets people from all of these disciplines work and communicate together more easily than they ever have before.
\n\n\n\nThat is why he works on and encourages others to localize plugins today. He believes localization of the software is the foundation for the extension of the WordPress community as it enables people to ‘Flex their Freedom’ in a language they speak!
\n\n\n\nHe has helped to organize online events around previous WordPress Translation Day events.
\n\n\n\nHuanyi said: “I think it’s important to localize WordPress because its very concept of ‘open source’ means that people can access it freely. In another way, free from the monopoly of knowledge and speech. To achieve it, it’s important that people can access it with their own language.
\n\n\n\n“Localization is the foundation of the extension of WordPress community because it helps people using different languages to access the project and lowers the hurdle to understand how things work.”
\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\nThank you to @no249a002 for sharing his adventures in WordPress.
\n\n\n\nThank you to Abha Thakor (@webcommsat), Mary Baum (@marybaum), Meher Bala (@meher), Chloe Bringmann (@cbringmann), Surendra Thakor (@sthakor), Adeeb Malik (@adeebmalik) for research, interviews, and contributing to this feature article.
\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
\nShould code comments switch to // ? Meetup.com stops using an accessibility overlay. Final releases for WordPress 3.7 – 4.0 are now available. Tune in soon for State of the Word 2023, happening December 15 via livestream from New York City.
Share Your Experience: The 2022 WordPress Survey is Open
State of the Word 2022
Meetup.com Accessibility Overlay Update
Now Available: WordPress 3.7-4.0 Final Releases
Proposal: Amend the Inline Documentation Standards for multi-line comments
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.
Are you interested in giving back and contributing your time and skills to WordPress.org? 
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. 
You — and your whole team can Join Post Status too!
\n\n\n\nBuild your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. 
Listen to podcasts. Follow @Post_Status 
and LinkedIn. 
This article was published at Post Status — the community for WordPress professionals.
";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, 30 Nov 2022 19:15:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;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:71:"WPTavern: #53 – Matt Medeiros on the State of the WordPress Landscape";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=139905";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:85:"https://wptavern.com/podcast/53-matt-medeiros-on-the-state-of-the-wordpress-landscape";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:55637:"Transcript[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, the thoughts on the past present and future of WordPress.
\n\n\n\nIf 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.
\n\n\n\nSo on the podcast today, we have Matt Medeiros. Matt is the driving force behind many WordPress initiatives. That could be the creation of plugins, WordPress news, media, as well as podcasts about all manner of WordPress specific subjects. He likes to juggle multiple projects at once.
\n\n\n\nCurrently he’s the director of podcaster to success at Castos, which is a podcast hosting company with a WordPress plugin. He’s on the podcast today to give us his take on the past, present and future of WordPress.
\n\n\n\nMany millions of people like to work with the WordPress software, they create websites, plugins, and themes, and extend what the CMS can do. Others, such as Matt like to ponder the broader purpose and direction of the software and the community around it. The Matt Report and The WP Minute have enabled us to hear about what the community is doing, what it wants and where its points of friction are. He’s talked to hundreds of people about what WordPress was, is, and might be. And so he’s in a unique position to pontificate about what WordPress, beyond the software, is.
\n\n\n\nWe start with mats backstory. How he found WordPress and why he started to use it. We talk about how he’s dipped in and out of the community over the years. More excited at times, less so at others.
\n\n\n\nThe conversation moves on to some of the trends that Matt has noticed. He identifies how the software and the wider community have altered over time. We talk about how The WP Minute got started, and how he’s building up a community of like-minded people to consume as well as to create the content that they’re putting out.
\n\n\n\nTowards the end, we get into the governance of WordPress and the future of the project more generally. There are certainly things that Matt likes, but there are some wrinkles which get aired as well.
\n\n\n\nWe finish up by talking about podcasts and Matt’s work with Castos and how they are trying to make it easier to get your voice out there, especially with their WordPress integration.
\n\n\n\nIt’s a lovely chat with a thoughtful and far sighted member of the community.
\n\n\n\nIf you’re interested in finding out more. You can find all of the links in the show notes by heading over to WP tavern.com forward slash podcast. Where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Matt Medeiros.
\n\n\n\nI am joined on the podcast today by Matt Medeiros. Hello, Matt.
\n\n\n\n[00:04:10] Matt Medeiros: Nathan, thanks for having me.
\n\n\n\n[00:04:12] Nathan Wrigley: You are so welcome. If you’ve been in the WordPress space for, I’m going to say a decade or more, it’s very likely that you’ve heard about Matt Medeiros, but just in case you haven’t, I’m going to let Matt do a little bit of an intro to give us his backstory about WordPress, the WordPress space, the projects he’s been involved in. So, Matt, off you go.
\n\n\n\n[00:04:33] Matt Medeiros: Well, my newsletter list says otherwise. So, there’s still plenty of people who need to know me. So Matt Medeiros. I’ve been doing WordPress stuff, 10, 15 years. I don’t know how long it’s been. Started a podcast called Matt Report back when I started a digital agency. That’s how I built the digital agency. Ran Matt Report for many, many, many, many years still out there, and now have pivoted this focus on thewpminute.com, which is five minutes of WordPress news every week.
\n\n\n\nSo I’ve been in the WordPress space, agency stuff, plugin stuff, theme stuff, podcasting stuff, YouTube stuff. And now I am the director of podcaster success at castos.com, which is a podcast hosting company, which also has a WordPress plugin. And also the parent company of wordpress.com, Automattic, has invested in Castos a little over a year ago at this point. So it’s podcasting and WordPress.
\n\n\n\n[00:05:24] Nathan Wrigley: We’ll definitely get into that. I confess I had forgotten that fact. Cast your mind back. Let’s say it’s 12 years ago, something like that. What was the thing that made it WordPress as opposed to something else all those years ago? Could have been Drupal, could have been Joomla, could have been Expression Engine. Why WordPress?
\n\n\n\n[00:05:40] Matt Medeiros: In fact, it was Drupal, to begin with. That was my first foray into really taking an open source CMS seriously, besides PHP-Nuke, which I had played with, before Drupal. But Drupal came into my professional career as I was head of web services for an ISP, internet service provider.
\n\n\n\nWe used to do things like dial up, ISDN, if you can remember those. T1 lines. And we purchased another ISP that had a web development arm and it was a Drupal shop. And this is around Drupal four and five, around those versions. And the head of design or the head designer at the time, he was like, hey Matt, because we were taking over and other people were leaving and I was going to steer the ship.
\n\n\n\nHe’s like, I want to get away from Drupal. It is so hard to design on top of. Now you got to remember this is, I don’t know, 15 years ago, something like that. And he said, there’s this thing called WordPress. I can really design on top of that. I can do really well with it. I want to try it out. And that was the first theme we bought was the theme called Standard, which was a collaboration way back in the day between John Saddington, Tom McFarlin, and Eric Dye, I believe was his last name.
\n\n\n\nThat was the first theme I ever purchased, in a professional setting. We use that to build themes and do that with our customers. And, and that was the entrance into WordPress. And once I broke off from that company, I just took all that knowledge and started my digital agency with that. And it was domino effect, ever since in the WordPress space.
\n\n\n\n[00:07:08] Nathan Wrigley: You’ve really had a, like a broad, rich, encounter with WordPress though, because for me at least, anyway, it was WordPress websites and then more recently got into podcasting and those are basically the two things that I’ve done. But, as we’ll probably find out during the course of the show, you’ve really dotted around.
\n\n\n\nOne of the things that I want to raise right at the beginning, and I don’t know what your thoughts on this are. It’s a bit of an abstract thought. If we were to rewind the clock, say 20 years ago. Both of us have obviously decided at some point, I think the internet is quite an interesting and fun thing. But I genuinely had no idea, it could have been a flash in the pan. Maybe it would’ve represented a tiny sliver of what people were doing. Shops, brick and mortar shops would still be thriving. Websites would’ve been really tangential, hardly anybody might have visited them.
\n\n\n\nThere was no conception that the phone would become a conduit. That you would carry something around in your back pocket. That computers would be basically portable. None of that was a thought, and yet both of us staked more or less everything on it, which with a bit of hindsight was probably the best decision we ever made.
\n\n\n\nNow, you can talk to computers that sit in a tiny box in your kitchen and it will give you coherent answers to everything. Do you feel like you’re a very privileged person to have stepped into the broader internet and all that that offers?
\n\n\n\n[00:08:28] Matt Medeiros: My genesis around getting into this space, if you want to go even deeper into the rabbit hole of who Matt Medeiros is, is my family ran a string of car dealerships for about 45 years in my local, my local area. We weren’t like this big massive conglomerate auto dealership. We just had two, family owned and operated.
\n\n\n\nIt was the technology that was moving, fast paced in that world. Consumer internet being born, websites, you know, this all sounds pretty trivial, but back then it was like, oh wow, we can post a car on the internet and somebody can look at it and email us, or most likely call us back then and buy it? Speaking of the privilege that, like being in that space, having a family that ran this dealership, but because I was the youngest one and I was into it. I was the one that put all the technology together, from General Motors, right?
\n\n\n\nThey were literally talking to an 17, 18 year old at the time, as the head of the internet department. Because I was the only one who got it, who understood it. My dad did, but you know, I sort of led the charge on that. And, I remember being in college and, you know, when you look at WordPress and open source, one of my, uh, capstone courses was to build something with, I forget what the terms were, but they said build it with multiple packages. And back then I was learning like Linux and Novell and, and Windows NT.
\n\n\n\nAnd I remember building PHP-Nuke with a bulletin board with, a blog roll. And I was building a car site, and I was like, wouldn’t it be awesome if somebody could go to this website and book an oil change for their car by filling out this form. And then if you had questions about repairing your car, you could come to this thing called a bulletin board, and have like this little community.
\n\n\n\nWhat I was doing back then was doing everything that social, that we all take for granted these days with the advancement of technology. And I was like wiring it together with little open source packages. So yeah, roundabout way of getting to, yeah, I feel pretty lucky to fall into that space at an early age.
\n\n\n\n[00:10:30] Nathan Wrigley: I feel that you and I hit a time when you could flip from just having any kind of job into working on the internet, because the barrier to entry in terms of knowledge was so low. You basically had to learn HTML and then along came CSS, it was straightforward.
\n\n\n\nI think the promise now is much more difficult. I can’t really imagine what it must be like for somebody at the age of 17 or 18. The things that they must need to learn in order to become employable. Speaking of the internet, you mentioned social media and what have you. I wonder what your thoughts are on that.
\n\n\n\nI know that we’re straying away a little bit from WordPress, but it does touch on GPL and it does touch on the broader purpose of the internet. What are your feelings about how the internet has evolved over the last, let’s say seven, eight years? Things like Facebook, social media, and the associated benefits and harms that go with it.
\n\n\n\n[00:11:25] Matt Medeiros: I don’t think humans were ready to be wired up emotionally, to the level that we’re at these days. Spanning across many, many contexts, right? From your everyday life of sharing pictures of what you’re eating, what your kids are doing, to more serious things like health, wellness, mental health.
\n\n\n\nCouple weeks ago suddenly lost my father-in-law and like the grieving factor of online. And you really start to sit back and say like, what, what is this? Like why? Is this value, all of us connected like this? Are we really together in this? Or is it just this digital connection that sort of literally just disappears as the feed refreshes?
\n\n\n\nAnd it really starts to have you question all of these things. Now there’s definitely many, many benefits. I mean, friends, that I’ve made through social, the businesses that I’ve built, and continue to build. There’s definitely a plus factor, but there’s a huge negative and, and things that I don’t think human beings are really ready for.
\n\n\n\nAnd I look at it in two different ways. One, I have three very young sons, three boys, under the ages of six. And I’m just like mentally preparing on how to onboard them to the internet, how I will do that. But I also see things from the broader perspective, is you and I are content creators. We’re just playing in the WordPress world mostly and softwares and stuff like that.
\n\n\n\nBut I see people who are whatever, they’re into fashion, they’re into tech, they’re into video games, and there’s a burnout factor. There’s a, I must continue to create all of this content to please these people who really don’t care about me, factor. And then there’s those who really become hits, they do really well. And they’re not ready for that fame and that spotlight, because they’re one person with a million YouTube subscribers in their home office.
\n\n\n\nAnd they’re not ready for what that’s like, to have all of these humans watching them and asking them for things. And it’s just, it’s not a mindset that I think we’re all really ready for, without some education. But we’re so early that, 50 years from now, it’s, it’s probably not going to be a thing, because we’re, we’re still cresting the analog to the digital. Like you said, the young folks, how are they going to get jobs?
\n\n\n\nI think the, the issue is, is they lose the fundamentals of building technology. When I was learning how to build a website, I was learning how to build a computer. So I knew that there was a CPU and memory and a hard disc, and these things were storing this content and yada, all that fun stuff. Now, with the introduction of whatever, let’s say, easy web website builders and you just talk to AI and it codes a website for you. There are going to be this swath of people who just don’t know where all of this stuff lives and how it’s all connected. So, that was a deep rabbit hole that I just went down, and I hope we tumbled around it.
\n\n\n\n[00:14:14] Nathan Wrigley: Yeah, really interesting. You mentioned your three children and I think that’s really fascinating for me. I have children as well, and one of the things that I struggle with. On the one hand, I’m really a proponent of technology. I love it. There’s almost nothing about it that I don’t love.
\n\n\n\nAnd yet at the same time, I’ve noticed that my children have been born into an era in which technology could be literally welded to your hand and, you know, there’s no escape from it. And so the notifications can come in at all times of day, and night. Stress there on night, so it disrupts things. Like it disrupts the normal cycle of interpersonal relations in a room because, there’s a bing bong on a phone and suddenly you’re distracted.
\n\n\n\nAnd the reason for being in the room with other people is somewhat shattered. And then, you hear about people who leave their phones by their bedsides and the phone goes off in the middle of the night and it disrupts their sleep, and all of these impacts. And whilst I am boldly a proponent of the internet, there are aspects of it which trouble me. And I think your wise point there, right at the end was that we’re young to this. We’re 20 years in, maybe a little bit more, but let’s say roughly 20 years in. And so we don’t really know where this is going.
\n\n\n\nIt’s kind of like steering a ship. I’m imagining somebody in 1492, Christopher Columbus or somebody on a ship, you know, they’ve set sail. They know they’ve got a destination, but they don’t know how long it’s going to be or when they’re going to get there. This feels to me like the internet. And I do wonder if some of these things that we may regard as bad habits at the moment will get washed away and replaced, hopefully with more beneficial things. I’m optimistic about that.
\n\n\n\n[00:15:52] Matt Medeiros: Yeah, I agree.
\n\n\n\n[00:15:53] Nathan Wrigley: Let’s just turn to the WordPress space, generally speaking. So you’ve been in it for a long time. Certainly much longer than I have. And you’ve been somebody that’s been observing the WordPress space. Not just using the software, but considering it, considering the impact of it, considering the business that can be made around it, and looking at the plugins and the themes and all of that, and having a critical eye on it.
\n\n\n\nThis is a very broad question, but I’m going to ask it anyway. What have you noticed as the main changes over time? Young people to the community, you’ve been in the community using WordPress for a couple of years. They won’t know that there’s been any changes. The software’s just the software, but there’s been a lot. What do you think the main things have been for you?
\n\n\n\n[00:16:29] Matt Medeiros: Yeah, I’m, I’m going to try to summarize this as quickly as possible that we can break off into different paths that I think are, are relevant. But there was certainly a long span of the same folks doing the same WordCamp talks, I’m not saying this in a bad way, but there was, I don’t know, a 10 year cohort of WordPress that I felt, we were all jiving and doing the same thing, showing up to the WordCamps, and everyone knew each other.
\n\n\n\nThe real pivotal milestone, for better or worse, was the introduction of Gutenberg, and the software and how it was introduced and all that stuff. Those pages in the history books have already been written. I think it was at that point where a certain segment of the community was one, they were like, I don’t want this in WordPress, so I’m done. There was another segment where, we don’t know how to code around this, and I don’t want this coding overhead. And then there was a third, in my view, where a lot of people used it.
\n\n\n\nExcuse might be the wrong word, but it was certainly a time where, man, you’re 10 or whatever it was, 10 or 12 years into software. That’s a lifetime of using the same shiny tool. And there’s just this natural thing, I think, of all of us who are like technologists or like 10, 12 years in, ah, I just got to try something else. And that was a moment, two thirds of these people are leaving because of these reasons. I guess I’ll leave too, and go find another shiny object.
\n\n\n\nAnd that’s where I guess the no code market really stepped in. Not saying because of WordPress, but it was certainly a right time, right place, kind of thing where those tools were getting shinier and better, and it was a great moment for them to somebody else to be like, ah, Webflow, ah, Wix, Squarespace, Shopify, Coda, Notion, all these things that we’re just like piecing together like we did with WordPress 10 years ago. Now we can do this again here with these shiny, faster free tools.
\n\n\n\nSo that’s the way that I see it. That change in the community over the milestone of Gutenberg, and up until now there’s a lot of fresh faces in here, which is great. But there’s less of this, I don’t know, warm blanket around all of us these days, that used to be there, for a good 10 year cohort.
\n\n\n\nOne of the reasons why I started The Matt Report at the time was, one, it’s because I wasn’t a developer and I didn’t know anyone. I didn’t know how to talk to developers, so I said, well, I’ll just interview them and, and promote them so that they can get jobs and maybe I’ll learn more people.
\n\n\n\nBut two, when I was at one of my first WordCamps, perfect example, there was, you know, one of the core contributors of WordPress and he would walk by and people like, Oh, I really want to talk to him. I’m afraid to talk to him. So there was like this celebrity status kind of thing.
\n\n\n\nAnd that’s when it hit me like, oh, people really care about these other people in the community. Let me go and find them and interview them, and prop them up so other people can meet them instead of being, you know, shy or worried to talk about them at a WordCamp. So I think the biggest change, for me anyway, has been the community in the involvement of everyone.
\n\n\n\n[00:19:24] Nathan Wrigley: Did I get a sense, I could be wrong. Forgive me if I got this sense and my spidey sense was tingling in the wrong direction. But, I kind of got a feeling about three or four years ago that you, you kinda fell out of love a little bit with WordPress and were seeking paths new. But then you’ve drifted back in, drift is the wrong word, you’ve come back in with great aplomb, you know, you’re back in making all the content and what have you. Is that true? Did you find yourself in that miasma, thinking I don’t really know whether I belong anymore?
\n\n\n\n[00:19:55] Matt Medeiros: Picture us in the, in my therapist office, and you’re sitting across from me with your pen and notepad. There’s a lot of things that go into that feeling. You’re not totally wrong. But, as you know as a content creator, you continue to create all the content. And quite literally, I burned out on the YouTube stuff because it was just a hard slog on the Plugin Tut channel. But then it was, how do I really grow this? How do I grow this podcast and, bring in other, other voices? Because the same thing I just mentioned about this 10 year cohort, all the same people.
\n\n\n\nI could feel those effects on the content that I was doing. That’s when I started to introduce the no code, maybe the more business aspect, SaaS developers, stuff like that, and bringing that into the fold. It certainly, my love for WordPress, it actually goes much deeper than the software. I think that WordPress itself is, speaking of like jobs and education. This is a tool that can empower individuals, local organizations, states, towns, to put people into a workforce.
\n\n\n\nAnd WordPress is, I think, a great learning tool. A great building tool to do all that stuff, aside from the fun web stuff that we can do with it. So you’re not too far off, but there was sort of a reshaping of how do I introduce new voices? Because I could feel probably just like you, the social media, the engagement of everyone sort of just getting burned out from the same old thing in WordPress, and that was probably me shifting the way I do content at the time.
\n\n\n\n[00:21:32] Nathan Wrigley: So shifting more recently, your content creation, it’s not entirely this, but you’ve moved to a new moniker. You’ve got The WP Minute. Just give us a bit of an insight into what the intention was there and how it’s going.
\n\n\n\n[00:21:46] Matt Medeiros: We can thank our mutual friend Davinder Singh Kainth for getting me into this, uh, yet another content rabbit hole. But I also thank him very much for pushing me in this direction. I had an idea that I pitched to him one day and I was like, hey, probably just like your spidey sense went off. I’ve gotten really busy with the Castos day job, three young boys. It’s like, how the heck can I even do long form content anymore?
\n\n\n\nSo I wanted to do short form content and I approached Davinder and I said, hey, what I’d really like to do is a spoken version of your, of your newsletter. Fast forward, to make a long story short, he just said, how about you just start your own and I’ll just support you and I said, I don’t really want to do my own, I just want to, just want to piggyback off of somebody else. And that’s how we, we got into The WP Minute. So it’s your favorite five minutes of WordPress news, every Wednesday. But it’s really grown, to, uh, a small but mighty community. Just introduced Erik Karkovack, who is a top WP Tavern commenter, as the head editor or the editor of The WP Minute.
\n\n\n\nSo he’s working for me, air quotes, full time as the editor of putting together all the news, curating the news. And then I read the news, every Wednesday, and it’s just a short five minutes, so you’re busy, you’re a busy WordPress professional, you don’t have the time. We get all the top headlines for you and summarize it for you. And we have a fun community. So if you’re into the news, I, I certainly recommend The WP Minute.
\n\n\n\n[00:23:10] Nathan Wrigley: How do you decide what stays in and what’s goes out? I face this problem. I have to decide which podcast episode I’m going to make, but it’s much more straightforward because the stuff that I’m producing content on, probably won’t matter whether it’s next week or the week after, it’s less critical. But for you, you’ve really got one shot and you’ve got to presumably try and get all the good bits in in five minutes. That’s hard, because in the WordPress community, as you know, I can talk about it for at least an hour and a half every week. How do you decide what stays in and what gets cut onto the floor?
\n\n\n\n[00:23:41] Matt Medeiros: Yeah, so I look at the WP Minute as probably the best thing that I’m ever going to create for WordPress, right? So Matt Report, all the plugins, themes, services, consultations I’ve done, I feel like the WP Minute is the best thing that I’m going to contribute to this community. As far as I can see, and I look at it as community driven journalism without, self-promotion on this point.
\n\n\n\nThe idea is if you really want to have a hand in the news, you could join the membership and be part of this, and you join the membership to support it, because it costs money. And I try to be as transparent as possible of, there’s hosting, there’s podcast hosting, there’s paying Eric, there’s paying Raquel, there’s paying Pat to run this team.
\n\n\n\nAnd the idea is if you want to get the stories out, you join us for short money to support the whole cause. And what I call the members, they call them producers. So you, the community member, can help produce the show. And as you know, Nathan, you get people knocking on your door to promote their product, promote their thing, and it’s like, hey, great, put your money where your mouth is and if you want your news to be heard, submit it to, what we call the link squad at The WP Minute. It’s a member curation. So you have the editorial team, myself, Eric, Pat, Raquel, and then you have the members who contribute the news. We all watch the news.
\n\n\n\nYou know, I got some Slack bots wired up. We get all the hot topics pumped right into the Slack channel so we can all collaborate on it. But then everyone sort of gets to have a vote. So people who put in their links, if their link makes it to the news, then they all get a credit thank you, both in the newsletter and the podcast. Now the idea is it’s supposed to be a five minute show. So if there’s a ton of news and somebody has voted for their top 10 slider plugins for October, chances are that one’s not going to make it. But we’ve had some times where we’ll cut a story from make.wordpress.org.
\n\n\n\nHey, we’ve got WordPress 6.1 release candidate one is ready. Please test it. Those are things that we always include to raise awareness, but if there’s acquisition news, community news, Tumblr News, like things that are really big and impactful, those things might drop because those things happen a lot more. So that’s not the most educated answer of how we select the news, but it is a community effort, and then within the confines of, hey look, this is also short form, so we try to keep it to five to seven minutes every week. People have said to me, why isn’t it called The WP Minutes?
\n\n\n\n[00:26:07] Nathan Wrigley: You’ve been doing this like you said, for such a long time, and so you’ve been inspecting the community and what have you. You’ve got this media channel now, WP Minute, I know you’re doing a bunch of other stuff, and we’ll get onto that.
\n\n\n\nHave you noticed over the last 10, 12, 8, whatever number of years. Have you noticed that the audience has changed? The desire of the content for the audience has changed? Because, when I started listening to WordPress content, really the only stuff I could find was how tos. It was, here I am, I know stuff about code. I’m going to tell you about code. Whereas now, if you look around, I feel that you can get news on almost everything.
\n\n\n\nYou know, you’ve got news about accessibility. You’ve got news about governance. You’ve got news about the plugins. You’ve got news about the themes, full site editing. The list could go on and on. And it seems almost like we’ve really properly got a little ecosystem where you don’t need to code, you could just be a community member talking about the community. So any thoughts on that?
\n\n\n\n[00:27:05] Matt Medeiros: Yeah, I have a lot of thoughts on that. I talk about this topic a lot, I really just put all my cards out on the table and I could be totally wrong and it wouldn’t, certainly wouldn’t be the first time. But I think that the audience size, and again, this goes back to your spidey sense from before. I think that the audience size for the type of content that you and I put out is maximum, if you had the whole globe of human beings in front of you, the whole earth is probably about 8,000 people, out of whatever, 8, 9 billion people.
\n\n\n\nI think that’s our cap for WordPress news, the inside baseball or how, how the community is put together, the ins and outs of the project, right. I think that the cap is 8,000 people. Now, the cap for how to put together a WooCommerce store, vastly different, right? those are the ones that, I mean, that’s hundreds of thousands, if not, uh, I don’t know, millions of people, who would want that kind of content? So I think yes, it has changed. I think the one constant is content that is still developer centric, is still the king of WordPress content, because there’s just far more WordPress developers who care about how to put sites together, than it is about the business side of WordPress and, maybe the community side, right?
\n\n\n\nSo I think that it has certainly shifted, although maybe even has gotten even tighter into the development space with the introduction of Gutenberg, full sight editing and just the general changes of WordPress.
\n\n\n\nSo, I know that if you told me 10 years ago, could you have made a business out of, whatever I, Matt Report and The WP Minute, I probably would’ve said no, I’m just trying to like grow brand awareness, which I was. I think I’ve successfully turned it, air quote, successfully turned it, into a media business, but it’s still very, very small. Very appreciative to like the sponsors over the years, and I have done really well compared to the larger podcasting industry, But, the audience I think for the stuff that, at least that I do, not trying to put you in the same bucket as me, is pretty small. It’s just people going in and out, all the time.
\n\n\n\n[00:29:12] Nathan Wrigley: Given that we’ve both hitched our cart to the WordPress space, what are your thoughts about the future? Because I personally feel at least anyway, that the future is quite bright. I’m fairly optimistic about the progress around full sight editing and the block editor. I can well understand why people have become dissuaded with the desire to use WordPress into the future, I can understand that. But I feel that there’s light at the end of that tunnel, albeit, I don’t know how many days, weeks, months, or years it’s going to be before the train finally emerges out of the tunnel. But for me, it’s important because I do podcasting. I do content in the WordPress space. I would like to think that WordPress has a bright and glowing future. Maybe you share that optimism or maybe not.
\n\n\n\n[00:30:02] Matt Medeiros: Yeah, I feel like I’m a realist in the fact that Automattic will take over wordpress.org, and it’ll just be more of a prominent upsell to either Jetpack or wordpress.com. And there is nothing wrong with that in my eyes, okay. So let’s just set that aside for a moment. I’ve recently, so hold that thought.
\n\n\n\nI’ve recently been using Ghost, another open source CMS and, I’m using their paid version because like the folks who would make that decision to not have to maintain WordPress, get a hosting account, do plugins and themes. I said, hey, for this little side, side, side project that I’m working on, I’m just going to pay ghosts 30 bucks a month.
\n\n\n\nAnd I want to be carefree like everyone else who picks these no code tools. This is what they’re all saying. This is why they’re all moving there. And I’ll tell you, yes, Ghost is good in the lane that Ghost runs in. But just the other day I was like, ah, I need to add a landing page, or I need to edit the footer.
\n\n\n\nAnd I go to the help docs and it’s like, install your code editor. Set up a local repo., like run docker containers, and I’m like, I don’t want this. Where’s my full sight editing? Where’s my Beaver Builder? Where’s my Elementor? I just want to edit this one thing. Why can’t I do it? There is a luxury in WordPress that I think a lot of, a user interface luxury. Uh, a no code luxury. Call it what you want, that when I just want to click something and edit, for all the faults that you hear people complain about speed and performance. Man, put this up against the Ghosts, the Webflows, the Wix’s.
\n\n\n\nI was looking at card.co, the other, I think it’s card.co. It’s like a super simplified like page building, five page portfolio site and I wanted to upload multiple photos. This was for again, the passing of my father-in-law and I wanted to put a little memorial site up, and I had hundreds of photos that I wanted to upload and I had to upload one at a time. And I said, no, I just want you drag a bunch of photos like I do in WordPress into a media gallery and display it. And these other tools just, they just don’t do it as easy as WordPress.
\n\n\n\nSo, like you, I’m, I’m an optimist on using WordPress. It’s the learning curve and the maintenance. But I think that’s a world we’re all slowly moving to where, that will all continue to get simplified by Automattic, by web hosts. Full sight editing. Oh boy. I’m really struggling with that big time. Gutenberg, yes, there are still some things I really struggle with, but there are some other great tools as alternatives that I use. And that’s the patchwork that I’m doing now.
\n\n\n\n[00:32:38] Nathan Wrigley: The grass is always greener. There’s always that, I’m going to try that other CMS and see how it goes. And I’ve done the same, I’ve always ended up back with WordPress. It always seems like a, a comfortable pair of shoes. Terrible analogy, but there you go.
\n\n\n\n[00:32:52] Matt Medeiros: WordPress, a comfortable pair of shoes.
\n\n\n\n[00:32:54] Nathan Wrigley: Let’s get into the awkward business of Automattic and your thoughts around that. And you mentioned a moment ago that you thought that wordpress.org was moving inexorably towards being dominated by Automattic. What makes you say that, and does it trouble you? You went to great pains to say that it didn’t trouble you, but maybe on some level it does?.
\n\n\n\n[00:33:14] Matt Medeiros: I think that the biggest factor here is communication, right? It’s communication from WordPress leadership. It’s communication from Jetpack and Automattic. These are signs that are quite obvious. So, I forget six months ago or something like that, I interviewed the uh, president or CEO of wordpress.com, talking about their new price points because they had done new price points.
\n\n\n\nAnd the obvious gorilla in the room to me is, what are we doing with WooCommerce? We collectively as Automattic, like, when are you really going to compete with Shopify? And you know, he is, oh, you can compete with Shopify right now. You can just sign up for a WordPress.com. Yeah, but it’s nothing, it’s nothing like going to Shopify to start an e-commerce store. Nothing is guiding you as a merchant, as a store seller, as an entrepreneur.
\n\n\n\nSo these are obvious things that I can see, that everyone can see are the obvious paths to monetization to Automattic. And I think, one, we all step back and say, What would WordPress look like without Automattic? What would that world look like? Who would it be? Would it be Salesforce? Would it be Oracle? Would it be Microsoft? Do you want them in the lead of this software?
\n\n\n\nI think that the best steward for all of this stuff, .org included, is Automattic. The challenge is, communication, direction. And do we all really get a seat at the table, question mark? And I fight for that seat at the table from my point of view, which is the website builder, the entrepreneur, the user, not a developer, certainly not a developer. But from my perspective, these are the things that I fight for. And I fight for WordPress to be open source because I think it is, in a world where we all go closed source, like I said before, this is things that could impact local economies.
\n\n\n\nThis is a tool that could get somebody who’s really struggling in life, to get a job in technology because you know how to make a WordPress post. These are the building blocks of the fundamentals of the internet, in my eyes. So, to me it’s, hey, go Automattic. Tax us, air quotes, tax us. I know this is interesting, me being in New England and you being in England to me, for me to say tax us. But that’s fine with me. I used to say the same thing when I used to sell themes. Why is this process so difficult? Why don’t we have the data? Why isn’t dot org just a marketplace?
\n\n\n\nI am fine getting a 30% tax. If I can sell my goods in a place that’s trusted, secure, that we’re true partners with. And it just hasn’t happened because I feel that all roads lead to, we’ll monetize WordPress, this is Automattic speaking. We’ll monetize WordPress through Jetpack, wordpress.org, and then we’ll eventually upsell, hey, if you don’t want to host it yourself, come to .com, or Pressable. And I don’t see anything wrong with that. It’s just everyone, I think needs to sort of just face the fact and build their business, their plugin business around that.
\n\n\n\nWhat I don’t like is overstepping and, and the hidden paths to upsell without anyone saying anything, ala Jetpack. I still think Jetpack is good for the right user. In fact, I used it on that memorial site because it’s a fantastic tool for quick and easy. But I think it’s also going to dominate other SEO plug-ins, other contact form plugins, the blue collar digital workforce that I try to advocate for a lot in the content that I put out.
\n\n\n\n[00:36:35] Nathan Wrigley: What do you think about the governance of the project? So at the moment, we have the model, which is often called the benevolent dictator for life, and it kind of trickles down from there. Would you like there to be forays into altering that model? Are you happy with the fact that there is one person governing for life, or would you like to see little bits of that chipped away, chunks of the project, which are governed by the community more?
\n\n\n\n[00:37:00] Matt Medeiros: I really appreciate the three conversations that Matt and I have had on my podcast. I think it’s been three. I don’t think that there is, when I have a problem with my MacBook, I don’t call up Tim Cook, and say hey man, come on my podcast, let’s talk about this Apple ecosystem you’ve got here, speaking of a 30% tax. It’s great for us as a community to have a single person that is semi approachable to have conversations with you. To be at WordCamps and have this, literally armed lengths away, to have a conversation with. Having said all of that, yes, I would like change. As I’ve told Matt, he does an insane amount of stuff.
\n\n\n\nAutomattic, wordpress.org, Tumblr, and Automattic is like 25 different products. One of them my favorite, which is Simple Note App, Jetpack, and all the other stuff that he does in life. How can he do it all? And I think that is a real issue. We look at the last couple of weeks ish, he’s actually talked more openly about where he wants to go with Tumblr than I feel he has with WordPress dot org, and how can you balance that?
\n\n\n\nI think it’s a super challenge. I think, he thinks he can do it and he is doing it, but I think there should be some level of change. And Josepha again gracious to have her on the podcast once. How much can she possibly load on her back to do all of the work that she does? So, yes, I mean, I don’t have the answer for it.
\n\n\n\nI don’t think it’s easy. I think a lot of people think that it’s easier said than done. But there should be something, some kind of governance model change, which I know people have pushed for in the past. I just don’t see how, how Matt can steer so many ships at once.
\n\n\n\n[00:38:46] Nathan Wrigley: Speaking of steering a lot of ships. You’ve not only got The WP Minute and various other bits and pieces. You’ve also got a real interest in how podcasts are made, not just because you’re making podcasts and you go through that whole editing process and interviewing guests, much like we’re doing right now. But you’ve also taken a great interest in the technology behind how podcasts work. Actually just occurs to me, many people might not even know that there is a whole industry behind podcasting, but there is, and Castos is one of them. How long have you been now with Castos and what do you do over there?
\n\n\n\n[00:39:19] Matt Medeiros: Yeah, so two and a half years, something like that. Director of Podcaster success. I try to make podcasters coming in to Castos successful with their podcast, however they might define success, Again, joining Caso because one, I’m a podcaster, two, they have a fantastic WordPress plugin.
\n\n\n\nThere’s a commitment to open source, on the WordPress side, there’s a commitment to open RSS. These are two worlds that collide greatly with me, and I’m a huge proponent, of course on open source and open distribution. You know, the perfect example is what’s the difference? Well, the, difference is a Spotify where you have to have the Spotify app to listen to a particular show, and open RSS means you can subscribe and distribute anywhere that accepts RSS.
\n\n\n\nThe world of podcasting, it’s funny, it continues to grow and there continues to be this excitement around it, but it continues to be more in more corporate interest. There is a tiny, tiny, tiny open source team that’s sort of leading the charge for, I’ll dumb it down, but RSS standards.
\n\n\n\nIt’s called Podcasting 2.0, and you can go to the podcastindex.org, and they run their own index, which is different than Apple, right? So Apple has their index, but you have to, you know, register and do all this stuff with Apple. Podcastindex.org is an open, so think of it as almost like wordpress.org, if you will.
\n\n\n\nAnd they’re really leading the charge of enhancing the RSS feed. Doing things, more things in the RSS feed, like micro payment support, transcripts, chapters, live feed item tags, chat, cross platform chat. So they’re introducing a lot of this data and information that can help podcasters, and their challenges, similar to WordPress. They have to get other podcast hosts and other podcast apps to support these name spaces so that it’s for the greater good of the whole podcast economy or, or industry, right?
\n\n\n\nSo, you know, I’m a huge proponent of that. Again, to talk about like the approach of Matt, Matt Mullenweg to pull it back. I know, well, Matt’s from Texas, one of the head guys at Podcast Index is from Texas, Adam Curry, and I sent an email to Matt and Adam and I said, hey, you guys should talk to each other. You both know each other, you’re both into open source, open distribution. You all should have a conversation.
\n\n\n\nAnd they, and they had a conversation and that Matt tied together the Pocket Cast team to them, and they had some great conversations. So, yeah, open source, open collaboration, it’s a great thing and I hope to keep waving that flag for podcasting.
\n\n\n\n[00:41:52] Nathan Wrigley: That’s really interesting. I wonder if we are on the cusp of something akin to RSS with things like Mastodon, based upon Activity Hub, which is very like RSS. So essentially it’s an open platform where you can attach your social media stuff. I don’t know if you’ve come across this exodus from Twitter over the last couple of weeks.
\n\n\n\nBut there seemed to be a lot of people who, over the last few weeks have made up their mind that they would like something a bit more open. They would like to be able to get the content and post the content that they wish without the constraints of being logged in to some proprietary system. And in many of the comments that I’ve seen in people’s flight from Twitter, they keep talking about podcasts and how podcasting, 20 years ago, I believe it was Dave Winer who came up with the spec for RSS for podcasts, I could be wrong about that.
\n\n\n\nBut just how, with the benefit of hindsight, the whole RSS open nature of podcasts, so take Spotify and all those other things out of the equation. The fact that my podcast, your podcast, is available completely for free. You don’t need any sort of system, particularly, you just need to subscribe to a podcast feed, which is held on the website. Just how breathtakingly clever that was with a bit of hindsight.
\n\n\n\n[00:43:03] Matt Medeiros: Yeah, yeah. Adam Curry as well helped, lead that charge. And he’s, he’s the one that’s sort of leading up the podcast index stuff, and podcasting 2.0 stuff. Yeah, it is great. A lot of the technology is, it’s very easy to implement, right? It’s all part of the RSS feed.
\n\n\n\nAnd, you know, the challenge is, is sharing that data. So, it’s a, I don’t know if platform war is the right phrase for it, but you know, if you have your podcast on Spotify, Spotify can give you more analytics. They can do things in app that are for the better of the, of the listener. But don’t forget that it will be for the better of Spotify first, because they’re going to be the ones that run the ads and take a larger chunk of the profits or what have you.
\n\n\n\nWhereas open RSS, we’re all fending for ourself, and as the more collaboration and the more people who support the innovations, the better we’ll all be. But that’s the challenge. To get everyone on the, on the same page. It’s, it’s actually no, a lot of similarities to WordPress.
\n\n\n\n[00:44:01] Nathan Wrigley: You mentioned a moment ago that you feel that podcasting is still growing? I, I honestly have no insight into that whatsoever, but it does feel much more of a mainstream thing this year than it was last year and the year before that and so on. Is that in fact the case? Is there still a case to be made, is there data to back up that, yeah, podcasts really are still growing, and if your business or your interest, your hobby is something that you want to plunge into a podcast, it’s probably worth your time and effort.
\n\n\n\n[00:44:27] Matt Medeiros: You have to kind of look at it, obviously I’ll call myself an insider to the podcasting space, but there is a lot more money and a lot more interest coming in from what I’ll call the corporate level. And the corporate level translates into Wondery’s, Amazon. Amazon owns Wondery, which is probably the premier podcast production company creating fiction, true crime, entertainment podcasts. And that’s all backed by advertisement. That can be openly distributed, but because Amazon owns it, if you listen to it on Amazon’s music app, then you get it without the ads. But if you listen to it on Apple Podcasts, you get it with the ads, right?
\n\n\n\nSo there’s this big interest in advertising, and celebrities and movies and movie industry and all that stuff. Then there’s the flip side, there’s you and me. The guys that make probably a few thousand dollars a year, instead of a few million dollars a year, like the big boys.
\n\n\n\nIf you go to podcastindex.org, I’m looking at it right now. There’s 4 million podcasts in the index. I think Apple says around two and a half million. But there is a stat right below that, that within the last three days there’s been 109,000 updates to podcasts. And in the last 90 days, 483,000 have been updated.
\n\n\n\nSo of the 4 million, yes, there’s a bunch that have probably either just ended, you know, it’s just a series of content that people have done. Pod faded where they have given up. The true earmark to that is 483,000 in the last 90 days. So people get scared of the 4 million mark. Like, oh my God. How is my podcast going to live within 4 million? But when you look at the data of 500,000 active within the last 90 days, you still have a shot, and yes, the answer is it’s still growing for the hobbyists, like you and I.
\n\n\n\n[00:46:14] Nathan Wrigley: It’s really amazing. I feel so privileged in a way that I made the decision to get into it a little bit early when things were probably less competitive than they are now. That I’ve just kept banging on with it week week after week. It’s, yeah, it’s pretty amazing. Uh, I realize that we’ve used up a lot more of your time than I should have done, I apologize. So I’m just going to round off with one very simple question. You’ve been in the community many, many years. Let’s imagine five years, 10 years into the future. Do you reckon you’ll still be
\n\n\n\n[00:46:40] Matt Medeiros: here?
\n\n\n\nYeah, a hundred percent. I’ll be using WordPress, as far as I can see, again. One, because I love it as a publishing tool. Two because I believe in it as a tool for somebody to learn and educate themselves and, and find a new opportunity, whether that’s coding, designing or writing. This is a tool that can impact economies. Three, I love, I just love the idea of, of open source on the web and really believe in that wholeheartedly. So yeah, I see myself sticking around.
\n\n\n\n[00:47:09] Nathan Wrigley: Matt Medeiros, thank you for joining us on the podcast today.
\n\n\n\n[00:47:12] Matt Medeiros: Thanks, Nathan.
\nOn the podcast today we have Matt Medeiros.
\n\n\n\nMatt is the driving force behind many WordPress initiatives. That could be the creation of plugins, WordPress news media, as well as podcasts about all manner of WordPress specific subjects. He likes to juggle multiple projects at once.
\n\n\n\nCurrently he’s the Director of Podcaster Success at Castos, which is a podcast hosting company with a WordPress plugin.
\n\n\n\nHe’s on the podcast today to give his take on the past, present and future of WordPress.
\n\n\n\nMany millions of people like to work with the WordPress software. They create websites, plugins and themes which extend what the CMS can do. Others, such as Matt, like to ponder the broader purpose and direction of the software and the community around it.
\n\n\n\nThe Matt Report and The WP Minute have enabled us to hear about what the community is doing, what it wants and where its points of friction are. He’s talked to hundreds of people about what WordPress was, is, and might be, and so is in a unique position to pontificate about what WordPress, beyond the software, is.
\n\n\n\nWe start with Matt’s backstory. How he found WordPress and why he started to use it. We talk about how he’s dipped in and out of the community over the years; more excited at times, less so at others.
\n\n\n\nThe conversation moves on to some of the trends that Matt has noticed. He identifies how the software and the wider community have altered over time.
\n\n\n\nWe talk about how The WP Minute got started and how he’s building up a community of like-minded people to consume as well as to create the content that they’re putting out.
\n\n\n\nTowards the end, we get into the governance of WordPress and the future of the project more generally. There are certainly things that Matt likes, but there are some wrinkles which get aired as well.
\n\n\n\nWe finish up talking about podcasts and Matt’s work with Castos and how they are trying to make it easier to get your voice out there, especially with their WordPress integration.
\n\n\n\nIt’s a lovely chat with a thoughtful and far sighted member of the community.
\n\n\n\nGutenberg 14.6 was released last week with a long list of small but impactful refinements to core blocks and the full-site editing experience. One of the most practical enhancements included in this update is the new list view for editing the Navigation block.
\n\n\n\nGutenberg contributor Fabian Kägy published a quick video that helps to visualize the changes:
\n\n\n\n\n\n\n\nThe list view makes it easy for users to reorder navigation items using a drag-and-drop UI. The Navigation block in the content area instantly previews items that are moved in the block inspector.
\n\n\n\nAs part of a larger effort to make it easier to edit Navigation Links off the canvas, this release also adds a new URL field to the Navigation Link inspector controls. Now user can edit the URL from the inspector controls as well as from the main link control.
\n\n\n\nVersion 14.6 also adds a variation picker to the Group block placeholder. When users insert a new Group block, it will now allow them to select from among different variations to set the layout for the block. This makes it significantly easier for users to get started when using a Group block, instead of having to fiddle around to manually assign the desired layout.
\n\n\n\nOne of the most creative features introduced in this release is the new “Randomize colors” feature that will automatically generate color palettes on the fly. It utilizes hue rotations based on the Cubehelix color scheme.
\n\n\n\n“Hue rotation consists in rotating the hue wheel — such as the one you
might see in a color picker — by a determined amount of degrees, each turn
generating a new color,” Gutenberg contributor Vicente Canales said in the PR for the feature. He also noted that this new feature surfaces “the need for themes to explicitly support style randomization, as well as the need to incorporate a way to define a color’s role within a palette as a way of avoiding getting, for example, palettes where background and foreground don’t contrast, rendering text illegible.”
While randomizing color palettes is a fun feature for users, some theme and plugin developers do not see the need for it to land in core Gutenberg and eventually WordPress.
\n\n\n\n“Yes, it’s fun, but from a theme designer’s perspective I don’t see an urgent use since the theme designer can provide numerous style variations,” block and theme developer Ellen Bauer commented on the PR. “For the user this provides the same kind of ‘fun feel’, but theme designers would provide an experience that actually works.
\n\n\n\n“There is so much potential in styles, but not much is published yet. So as a theme builder I feel style export/imports, the option to separate font styles from color styles are much more basic features I would love to have first.”
\n\n\n\nNewsletter Glue co-founder Lesley Sim agreed that it’s a fun idea but that anyone using a theme will probably rely on the theme’s style variations.
\n\n\n\n“And that will probably feel like a randomizer to them already,” Sim said. “At least, that’s how I personally view style variations.
\n\n\n\n“I’d much rather focus on basic features first too, rather than fun ones. Let plugin and theme developers build the fun.”
\n\n\n\nOther notable features in Gutenberg 14.6 include the following:
\n\n\n\nThis update’s performance benchmarks for the site editor and post editor are significantly improved for three out of four metrics over the last release. Check out the release post for a more detailed look at every PR included 14.6.
\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, 30 Nov 2022 03:12:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;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:59:"Do The Woo Community: Cooking Up Some Code with Kim Coleman";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=73751";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"https://dothewoo.io/cooking-up-some-code-with-kim-coleman/";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:408:"Kim talks about looking at code as words, learning PHP, her journey as a WordPress developer, and choosing her lifestyle and her career.
\n>> The post Cooking Up Some Code with Kim Coleman appeared first on Do the Woo - a WooCommerce Builder 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:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 29 Nov 2022 11:25:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;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:98:"WPTavern: Meetup.com Removes Accessibility Overlay In Response to WordPress Community’s Concerns";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=139886";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:106:"https://wptavern.com/meetup-com-removes-accessibility-overlay-in-response-to-wordpress-communitys-concerns";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:4753:"Meetup.com has removed its accessibility overlay, a recent addition to the company’s website that raised concerns with the WordPress community and the broader community of accessibility professionals. The overly was powered by EqualWeb, a product which claims to provide automated compliance with accessibility standards but doesn’t address inaccessibility at the root of the problem.
\n\n\n\nWordPress Community Team leaders requested a meeting with the company and were able to persuade them to take the overlay down and focus on direct improvements to the Meetup.com platform. WordPress community organizer Angela Jin reported that their director of engineering and other team members were “very receptive to our feedback.”
\n\n\n\n“EqualWeb’s widget does scan for accessibility issues, and the original plan was for EqualWeb’s team (real people!) to provide progressive fixes to the overlay,” Jin said. “Meetup’s hope was to provide, over time, a fully accessible overlay.”
\n\n\n\nDuring the meeting, WordPress’ Community Team representatives contended that overlays create a poor user experience for people who use assistive technology while also ignoring key WCAG issues. This is why there are growing legal and privacy concerns associated with the overlays, which do not deliver on the promise of providing equal and open access to platforms.
\n\n\n\nAfter reporting on the issue earlier this month, one reader asked if the overlays actually work to address the issues and, if so, what is motivating the complaint.
\n\n\n\n“They don’t work,” WordPress accessibility contributor Joe Dolson said. “To the degree that they do work, they mostly offer functionality that is already duplicated by the user’s own technology.”
\n\n\n\nDolson examined Meetup.com’s overlay and highlighted a few of its major shortcomings:
\n\n\n\n\n\n\n\n\nThis particular overlay also commits the cardinal sin of labeling tools by disability, rather than according to what they do. For example, if you turn on the “Visually Impaired” mode, that’s actually a high contrast mode; which is only relevant if your visual impairment benefits from high contrast. This kind of presumptive labeling is ineffective at best (because it makes it difficult to find what tool might actually help you, should you need it), and offensive at worst.
\n\n\n\nBut the reality is that overlay tools are a misdirection of resources: if a user needs high contrast, large fonts, or other tools, they need those on all websites, and they need a solution that’s their tool, in their control, with their settings – and the majority of users already have that in their assistive technology.”
\n
As part of revising its accessibility roadmap, Meetup.com is requesting feedback from WordPress community members with experience using its platforms across devices with accessibility features enabled. Those who have 50 minutes in the coming weeks can request to speak with Meetup representatives regarding which features should be prioritized. People can also leave feedback in the comments.
\n\n\n\nMeetup.com’s decision to remove the overlay was well-received by accessibility advocates who hope to see more changes to the platform’s source code based on community feedback in the next few weeks. Beyond these changes, some community members are also recommending Meetup.com add people with disabilities to their team to get more first-hand information without having to publicly walk back an implementation like this.
\n\n\n\n“Although I applaud Meetup for removing the Overlay, they are going at this backwards,” WordPress user @bryan202 said in the comments. “They should have an independent company who employs persons with disabilities to audit their platform and inform them of the issues. If Meetup wants feedback on the specific issues this choice of overlay caused, then they should be willing to pay for that market feedback.
\n\n\n\n“As a disabled person we are constantly called upon to give feedback for free. We deserve to be respected for our time, efforts and feedback. Meetup needs to expand their technical team to include persons with disabilities so they have an inside look since their current team is missing this essential component.”
";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, 29 Nov 2022 03:18:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;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:93:"WordPress.org blog: WP Briefing: Episode 44: Minors, Majors, and Why We Have So Many 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:53:"https://wordpress.org/news/?post_type=podcast&p=13996";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:93:"https://wordpress.org/news/2022/11/episode-44-minors-majors-and-why-we-have-so-many-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8340:"In the forty-fourth episode of the WordPress Briefing, our host Josepha Haden Chomphosy highlights the role of major and minor releases in the WordPress open source project.
\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: Santana Inniss
Song: Fearless First by Kevin MacLeod
[Josepha Haden Chomphosy 00:00:00]
\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, Josepha Haden Chomphosy. Here we go.
\n\n\n\n[Josepha Haden Chomphosy 00:00:27]
\n\n\n\nAt the top of November, a new major release for WordPress shipped. That was WordPress 6.1. I know I talked about it basically nonstop. Then two weeks later, there was a new minor release for WordPress. It was WordPress 6.1.1, which I did not talk about at all. Way back in episode four of this podcast, I dug into the overall release cycle and what someone could expect from a high-level logistics aspect.
\n\n\n\n[Josepha Haden Chomphosy 00:01:05]
\n\n\n\nAnd today we’re gonna take a quick look at minor releases in particular. Just as a general heads up, I always want to lean into sports metaphors when I’m talking about releases, and I think it’s because of the words major and minor. And so, I’ve done my level best to not include that in any of my explanations today.
\n\n\n\nBut I do have one, I do have one that’s a sports thing. So just if you don’t like sports, know that it’s just one little bit and we’ll try to be carefully quick around it together. All right, so minor releases. You may have noticed that I don’t mention minor releases nearly as often as I mention major releases. And yet, most of the time, when we have a major release of WordPress, there’s a minor release that gets started almost immediately after.
\n\n\n\nSo first major versus minor. Major releases in WordPress happen roughly three times a year, give or take a release. Inside a major release, you will find that we include features, so– brand new abilities, enhancements, which you can generally call improvements to existing abilities, and also any bug fix that we can find, big or small, we’ll take ’em all.
\n\n\n\n[Josepha Haden Chomphosy 00:02:16]
\n\n\n\nSo minor releases in WordPress happen about four or five times a year on average. Minor releases include patches for issues introduced in the major release and any bug fix that doesn’t add or change functionality.
\n\n\n\nIf you’re with me so far, you probably have noted that there’s basically always at least one minor release per major release. And you might have also noted that I said minors include patches for issues we introduced in a major.
\n\n\n\nNow, if I were hearing this with fresh ears, the first thing I would wonder is, okay, so if you start working on the minor right after you release the major to deal with issues you know you introduced in the major– why just not ship the major while there are bugs in it? Great question. I’m glad you asked. So there are a few things worth knowing here.
\n\n\n\n[Josepha Haden Chomphosy 00:03:09]
\n\n\n\nFirstly, there is this concept of “ship and iterate,” which is present in both agile and open source. The idea is that we ship software as soon as we have confidence that what is in the release is non-breaking and represents our best guests at a better experience for our users.
\n\n\n\nOnce that is out there, we use feedback on the initial release to quickly iterate and ship another release. That way, we don’t hold back any good features. And since we already planned the immediate minor, any major issues that show up can be fixed in as little as two weeks. Secondly, there is the concept that with many eyes, all bugs are shallow, which is primarily present in open source.
\n\n\n\nThe idea here is that with enough people looking at a problem, that problem doesn’t stand a chance. So when a release is shipped in a workable state but with interactions that could use some refinement, the fastest way to find those refinements is to take it to the community of WordPress users and developers and invite them to co-create this CMS with us.
\n\n\n\n[Josepha Haden Chomphosy 00:04:10]
\n\n\n\nWhich touches on my final thought. The concept of the user as co-creator.
\n\n\n\nIf we think about the development and evolution of our software as a team effort, then we can think of the people who use our software as what’s called the “Twelfth Man” That’s in quotes, and I will, I’ll leave a link to that in the show notes as well.
\n\n\n\nIn sports, this refers to the fans. And if you’ve ever been to a live sporting event or played in any, you will know that the cheering and jeering from fans turns into this distinct motivating entity all its own. As a whole team or individual member, you know what you have to do. You know what you need to do in a game, but there’s something about that chaotic, loud roar of feedback that just brings life to what you’re doing, and that’s how I see our community of users.
\n\n\n\n[Josepha Haden Chomphosy 00:05:02]
\n\n\n\nSo at the end of the day, the answer to the question of ‘why so many releases’ and the follow-up question of ‘why tolerate stable imperfection’ is largely the same. To get features into the hands of our users quickly so that we can always be breathing life into this CMS we care so much about.
\n\n\n\nI hope that answers your questions about our release cadence, and if you didn’t come into this podcast having any questions about release cadences at all, I hope this new information brings a little extra light to the complexity of working in open source.
\n\n\n\n[Josepha Haden Chomphosy 00:05:32]
\n\n\n\nThat brings us now to our small list of big things.
\n\n\n\nBig thing number one is that the State of the Word has been announced and is scheduled for December 15th. It’s a little earlier in the day than in past iterations, so I hope we get a new crew of listeners tuning in at the same time. I’ll leave a link to that in the show notes, or you can pop over to wordpress.org/news to see the announcement for yourself.
\n\n\n\n[Josepha Haden Chomphosy 00:06:00]
\n\n\n\nBig thing number two is that team rep nominations are open on most teams right now. So if organization and people wrangling are high on your list of ways you can give back to WordPress, head on over to the team you contribute to and see how you raise your hand for that.
\n\n\n\nThen big thing number three is that big-picture goals, hopes, and timelines are being gathered, and I will ship those shortly after the start of the new year.
\n\n\n\nIt will give us all an idea of where we want to focus our attention to ensure that WordPress continues to grow toward the future. You can keep an eye out for that on make.wordpress.org/project.
\n\n\n\nAnd that, my friends, is your small list of big things. 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.
";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, 28 Nov 2022 12: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:"Santana Inniss";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:12;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:142:"Gutenberg Times: Gutenberg Changelog #76 – The new developer blog’s public beta, Gutenberg 14.5 and 14.6, and what’s coming up in 6.2. ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://gutenbergtimes.com/?post_type=podcast&p=22833";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:145:"https://gutenbergtimes.com/podcast/gutenberg-changelog-76-the-new-developer-blogs-public-beta-gutenberg-14-5-and-14-6-and-whats-coming-up-in-6-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:74613:"Ryan Welcher and Birgit Pauli-Haack discuss the new developer blog’s public beta, Gutenberg 14.5 and 14.6, and what’s in the works for the block editor.
\n\n\n\n\n\n\n\nShow Notes
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nBirgit Pauli-Haack: Hello and welcome to our 76th episode of the Gutenberg Changelog podcast. In today’s episode, we will talk about the new Developer Blog Public Beta, Gutenberg 14.5, 14.6 and what’s in the work on for the Block Editor. I’m Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate. And I’m thrilled that my friend, Ryan Welcher, core contributor, livestream on Twitch and developer advocate joined me today. Again, yeah, you’ve been on the show before. Good afternoon, Ryan. How are you?
\n\n\n\nRyan Welcher: I’m good, Birgit. Thanks for having me again. I’m always excited to hang out with you and talk Gutenberg release notes and all this stuff. Yeah. I’m excited.
\n\n\n\nBirgit Pauli-Haack: We do to have you here. So yesterday, you had your weekly Twitch stream again. And you had a break of three weeks and you came back and so what was it about?
\n\n\n\nRyan Welcher: Well, for the past two weeks… well, the first week back I spent trying to relearn how to use computers and the internet because it was three weeks off. I didn’t have a clue what I was doing. So the last couple of weeks, I’ve been focusing on Query Loop Block variations. So this week or yesterday, I actually started building a plugin that introduced controls to the Query Loop Block to be able to do more complicated and more advanced queries. And so I’ll probably be doing that for the next couple of streams and then hopefully releasing that into the wild for developers or anyone to use really. So yeah.
\n\n\n\nBirgit Pauli-Haack: Oh, that’s cool. Yeah.
\n\n\n\nRyan Welcher: Yeah. You can check me out at RyanWelchercodes is my handle on Twitch. Every Thursday at 10:30 Eastern.
\n\n\n\nBirgit Pauli-Haack: And if you missed any of Ryan’s Twitch streams, they go silent on Twitch. But Ryan always makes the additional effort to put them up on your YouTube channel. That’s the same username, youtube.com/ryanwelchercodes.
\n\n\n\nRyan Welcher: That’s right, yep.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I always have to follow up because it’s really great stuff that you put out there and I learn so much about it.
\n\n\n\nRyan Welcher: Oh, thank you.
\n\n\n\nBirgit Pauli-Haack: Not only how to do it well, but also to how to get to doing it well and see what you’re struggle with. And I’m really good-
\n\n\n\nRyan Welcher: Yeah. 80% of my stream is me spelling things horribly and typoing like crazy and then not knowing why something’s broken. So, yeah, I have some viewers that are regulars that help me out all the time. Shout out to Kevin, he knows who he is. Cool.
\n\n\n\nBirgit Pauli-Haack: Awesome. Awesome. And we have a good show for you dear listeners today. And for the American listeners, it’s all happy Thanksgiving. And also I hope you have a great time on Black Friday and then serve on Monday. So I will be, over the weekend, at a cricket game tournament in Sarasota. And so we are doing this recording today and then I’m off to my weekend.
\n\n\n\nSo we have a couple announcements that came in from project and one of we are all involved, you and I. That’s the WordPress Developer Blog is in public beta. And so it came out of discussion or year-long complaints or many years is that staying on top of the new features that are coming to WordPress. Open source is really one of the main barriers for developers to get started on the Block Editor, the site editor and doing stuff with it.
\n\n\n\nAnd the Core Block where most of the information is released has a very heavy emphasis for meeting nodes of the various core teams. And also it only highlights the new features that came with a major release. But for the Gutenberg plugin or what’s in the works on the PHP site, there is not a central place. It’s difficult for developers who are not contributors to get anything out of those make blogs as a relevant information. So the content will or focuses on the updates for developers, extenders who create plugins and themes and those who work with WordPress at an agency or as freelancers. And you were one of them working at an agency, also a free freelancer. So I really appreciate your continuing input on what is needed for agencies on the new features and how does it work there also.
\n\n\n\nSo it’s really good that we have now a place where that information can be shared. And it’s in beta, so there are not a whole lot of posts there, but that’s definitely going to change next year. We have three posts there. One is Ryan’s post on how to extend the WordPress wire slot fill system. What is that about, Ryan?
\n\n\n\nRyan Welcher: So a slot fill system is an extension paradigm that was introduced with the Block Editor with WordPress 5.0. And it’s a way of extending UIs, let’s put it that way. So you can inject your own elements into certain areas inside of the Block Editor and inside the site editor now. And, yeah, the article there is sort of preliminary. Sort of deep but not too deep. Deep enough to get started. And it’s based on a couple of talks that I’ve given in the past. So if you’re looking to extend the UI for the site editor or for the Block Editor, I’d go and take a look at that.
\n\n\n\nBut, yeah, it’s kind of code heavy, but it’s one of the reasons why the Developer Blog, I think, is going to be so important because normally I would write this on my own personal blog. And now we have a central place where we can share this information, it’s sort of official, and people know where to go and they don’t have to know who I am or what my web address is or any of that stuff to be able to get the information that I’m trying to share.
\n\n\n\nBirgit Pauli-Haack: Yeah, that’s a very good point. Yeah, there’s a lot of information out there that’s decentralized and bringing them all in or bring the writers in. Daisy Olsen has a post and she demystifies the home and post templates for the WordPress theme development. It’s not necessarily focused on block themes, that’s pretty much… it shows you for classic themes as well as for block themes. And then Justin Tadlock has a post where he helps theme developers think about block theme development from a pattern first mindset to avoid redundancy in code and also to have some simplicity more in the theme development. And I think that all three of them are really excellent hosts there. So I’m so excited about this and I know a lot of people are to kind of see what comes out of that. Yeah, so check it out.
\n\n\n\nThere’s also a page there that gives you a little bit more history about that and also a page that says how you can contribute if you want to be a writer or if you want to be a reviewer or you want to just kind of add your ideas to it, go there. And it’s mainly managed through GitHub so you get even an additional kind of insight in how GitHub works, even if you’re not so code centric and had always shied away. But believe me, it’s always a good place to be as a WordPress contributor.
\n\n\n\nRyan Welcher: I just want to kind of reiterate what you’re saying about how anyone can write for the Developer Blog. It’s not gated in the sense of… there is a process and ideas and content may not be accepted, but that’s based on topic, not based on who’s contributing it. So I think it’s really important to understand that it’s not just for certain folks and it’s not just for contributors or whoever, it’s for whoever really wants to. And as long as you sort of adhere to the process, there’s no reason why I could say anybody wouldn’t be able to add content to the Developer Blog. It’s truly open source.
\n\n\n\nBirgit Pauli-Haack: And can also be reused because it’s going to be in public domain. So that’s the GPL part of it. Yeah. Another announcement came down the pipe, which is that core committer and Peter Wilson, and he’s also member of the security team, announced that WordPress will drop support for WordPress 3.7 and 4.0 on December 1st. And you might ask, “What? They’re still supporting that? I thought it was only the last two WordPress versions.” That is true. Officially, WordPress only supports the last two major versions, but the security team had always also applied security updates to previous versions from 3.7 to 6.03. They all got the same security updates. And that is to end.
\n\n\n\nSo 3.7, 3.8, 3.9 and 4.0, they get one more update that will announce that there won’t be any future updates in the WP admin. So if you have these old versions in the stable of your clients, make sure that you upgrade to the later versions. I looked at the WordPress stats for that. So there is a stat online that gives you how many people are on which version on WordPress. And all four versions come together at 0.5% of WordPress installations. So, yeah, it’s a good decision. They wanted to do it last year but somehow it didn’t make it. Now it’s this year. So I just wanted to let everybody know the 3.7 to 4.0.
\n\n\n\nRyan Welcher: It just amazes me that WordPress versions that far back still work. People are still able to run it and I just think that’s fantastic. You should update. If you’re running 3.7, you should update. There’s a lot of functionality that you’re missing out on, but it’s amazing that it still works.
\n\n\n\nBirgit Pauli-Haack: I wanted to look up when 3.7 was actually released and I think it was 2010 or something like that, but I can verify that. Maybe not. Yeah.
\n\n\n\nRyan Welcher: March 14th, 2017? That makes sense?
\n\n\n\nBirgit Pauli-Haack: Oh, yeah. Could be. Could be. Yeah. Yeah. We are only at 3.0 or something.
\n\n\n\nRyan Welcher: Sorry, I was looking at the wrong place. October 24th, 2013, version 3.7.
\n\n\n\nBirgit Pauli-Haack: Okay, thank you.
\n\n\n\nRyan Welcher: Was named for Count Basie. Interesting.
\n\n\n\nBirgit Pauli-Haack: 2013. So that is a nine year old version, and nothing on your computer should be nine years old. And not on the survey either or be just accessible by the public on the internet. Yeah, for sure. Update.
\n\n\n\nSo we’ll come to sections what’s released? And since the last show on October 30th recorded, we had two WordPress releases. One was a major release 6.1 and we talked about it. Yay. We talked about it quite a few times here and I definitely will share again the field guide link in the show notes. And then there was another release on November 15th for the 6.1.1. And it’s about roughly 50 bug fixes that didn’t make it in at 6.1 or came out after 6.1 was released. So that was a major effort from the release team 14 days after a major release to come up with a point release to get all the bug fixes in the hands of the WordPress users.
\n\n\n\nSo there’s also a release from WooCommerce Blocks 9.0. Just for those who don’t know, WooCommerce Blocks is the bleeding edge plugin from WooCommerce similar to the Gutenberg plugin relates to the WordPress software. So using it, you can test all the future features coming to WooCommerce and help improve them before they’re actually released in WooCommerce. And the 9.0 the release came out this week. Actually today, and it’s November 25th, 2022. So they updated the options to customize products with an attribute template from the site editor, which sounds really cool. And then they improved the performance of product blocks by removing some fragments that were in there. And then they also cleared out some validation errors that were visible. A nice quality of life enhancement is that the placeholder for blocks who has placeholders… so the cover block, the image block, the gallery block, they all have placeholders that they take on the main store color coming from the theme JSON file. That’s kind of really nice. It’s, of course, an experimentation, but that is certainly something that any theme developer might want to look at how they implement that.
\n\n\n\nRyan Welcher: Yeah, that’s really neat. I’d love to take a look and see. I’ve always been intrigued because I do a lot of block development, especially on my streams, and I’m always intrigued by how much can I interface? If I had a block that just didn’t matter where it was installed, if it could take on certain aspects of theme.JSON, I think that would be super neat. I mean I think some of that stuff just trickles down by default, but I’d be interested to take a deeper look at that.
\n\n\n\nBirgit Pauli-Haack: Yeah. In Gutenberg, there was also a feature where you can access the theme JSON through some hooks and filters in 6.1, but I’m not sure how robust that is.
\n\n\n\nRyan Welcher: You can filter it as and add new things to it, but I’d be interested to see how it works. And I just haven’t put in the research so I don’t know. But I mean I’d be interested to see if there’s a data store on the JavaScript side where we could retrieve that stuff because you can get Block Editor information. I just have to do the research.
\n\n\n\nBirgit Pauli-Haack: That will be for the, what did you say? The next couple of Twitch streams are still Query Block and then the third one from now.
\n\n\n\nRyan Welcher: Yeah. It’s a great idea integrating… thinking about JSON into your blocks, using values from there to do things in a block, that’d be fun.
\n\n\n\nBirgit Pauli-Haack: Yeah. I think that makes whatever block in you have kind of very versatile and kind of migrates from theme to theme. But I also think that you probably need some standards as the naming convention on how you kind of primary, secondary, tertiary kind of colors. So I think as long as we don’t have them, it can be hit and miss. Yeah.
\n\n\n\nRyan Welcher: Yeah. I mean as soon as it’s up to somebody naming something, that’s like what? The second hardest thing to do in computer and software development is naming things.
\n\n\n\nBirgit Pauli-Haack: What’s the hardest thing?
\n\n\n\nRyan Welcher: Recursion I think.
\n\n\n\nBirgit Pauli-Haack: Okay.
\n\n\n\nRyan Welcher: I can’t remember who said that. Somebody smarter than me anyway.
\n\n\n\nBirgit Pauli-Haack: Yeah. And, yeah, Gutenberg 4.5 was released on November 9th and we have a few enhancements there. It was not a very heavy release because everybody still came off of the November 1st 6.1 release and I’m still moving some stuff around.
\n\n\n\nThere were some enhancement for Create Block for instance and I’m sure… you were, I think, involved in that to update to use the APIs. Yeah.
\n\n\n\nRyan Welcher: Yep. So the Create Block package is near and dear to my heart. And this one actually allowed us to create… so backing up, when you use the Create Block package, you can also create external templates. And so those templates will define how your plugin is structured and how your block is structured. And part of that templating system, there’s a series of default values that you can pass. And so what this commit did was it allowed you to use the Render property because in 6.1, the block API introduced Render as a block.JSON property where you can pass the path to a file and that file will be used for dynamic blocks. It’s a PHP file.
\n\n\n\nAnd so what that did, that allows you to do away with having to call Render call back and defining a function when you’re registering a block. So it’s made block registration a lot easier, but we needed to update the Create Block package to be able to work with that system. As a template author, you can define what the name of that file is, where it lives and all those sort of things. So that’s what that did. That’s a long way of explaining it. Just caught one thing up to the other thing.
\n\n\n\nBirgit Pauli-Haack: Yeah, it was cool. That’s cool. Thank you so much. And we all need kind of a little bit more explanation about these things that are just one headline from… that’s what we are doing here at the podcast. So in the Style Engine, that’s kind of the engine that’s behind… that’s the black box behind the theme JSON file that kind of tries to manage all the user inputs, the block JSON attributes, the styles from the theme and the default style from the Block Editor. And nowadays, support the dimensions minimum height property. So you could have, for all kind of blocks, but it’s now available. And that’s really cool because then you can say, “Okay, my Core Block or my cover block has a certain minimum height to fill up and can also inherit that to the other blocks that are there.” Yeah. So it’s all cool.
\n\n\n\nYeah. And then the comment template, post comment count, post comment form and post common links, they all got now also spacing support. So for your site editor and template. So you can actually… then here you can remove the spacer block and control it all with the blocks there. For another social icon, they got a new attribute and that’s the rel attribute, R-E-L, which is needed for something that’s happened on the rest outside of the WordPress universe, which is that Twitter had some implosion things coming on.
\n\n\n\nRyan Welcher: Yeah, some stuff happened over there.
\n\n\n\nBirgit Pauli-Haack: Some stuff happened there. I don’t want to really belabor that, but if you want to… so the social link block now has a Mastodon block variation, but the Mastodon variation also lets you verify your website with your Mastodon account. So you can say or can prove, “Okay, I am the person who belongs to this website.” And it then gives you a check mark in the Mastodon profile. And George Hotelling, he’s a WordPress co con… what is it? A core contributor.
\n\n\n\nRyan Welcher: That’s it.
\n\n\n\nBirgit Pauli-Haack: And he wrote a short tutorial on how to do this and verify your WordPress site with Mastodon. So if you have the need or wish or just want to check it out on Mastodon as a replacement for Twitter, a lot of people have registered Mastodon accounts since Elon Musk took over Twitter. And I think they are now on 2 million within a week, new accounts. So there’s definitely a wave there. And you can’t leave Twitter until you tell your followers where you will be. So it’s definitely a good way to at least get a Mastodon account and get it verified.
\n\n\n\nRyan Welcher: I have to get a Mastodon account. Do you have one, Birgit? Do you have a Mastodon account?
\n\n\n\nBirgit Pauli-Haack: I have two, yes.
\n\n\n\nRyan Welcher: You have two? Wow.
\n\n\n\nBirgit Pauli-Haack: I have one on-
\n\n\n\nRyan Welcher: I’m always playing catch up with you. You’re so bleeding edge.
\n\n\n\nBirgit Pauli-Haack: Totally, totally.
\n\n\n\nRyan Welcher: These new technology, not only do you have an account, you have two accounts and you’re the lead community contributor.
\n\n\n\nBirgit Pauli-Haack: Well, I looked at the Mastodon account and then my browser kind of said, “Oh, you have an account? Here’s your password.” I said, “Oh?” And then I looked at it-
\n\n\n\nRyan Welcher: You’re an early adopter. Well before the Twitter nonsense.
\n\n\n\nBirgit Pauli-Haack: I looked at it and it was from 2017 and had not a single post and three followers.
\n\n\n\nRyan Welcher: All right.
\n\n\n\nBirgit Pauli-Haack: So I pinned on my new account on my profile. So if you want to follow me or you have left Twitter and you want to kind of look at it and you want to connect with me again, do that. I also pinned my Tumblr account, which I set up in 2008 I guess.
\n\n\n\nRyan Welcher: Yeah. I actually have a Tumblr account that I think I set up back when I was doing Flash development. That’s how long ago it was. So I need to get that updated.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah. Okay. So now we got that out of the way. The second account that I have was the Gutenberg Times of course. Yeah. It’s a separate account. So if you don’t want the other things that I post on Twitter or on Mastodon, yeah. And WordPress only then the Gutenberg Times account on TWiT Social actually. TWiT is a long time podcast and live show technology podcast by Leo Laporte. And I have been following this week in Google Show, that’s the since, I don’t know, 10 years ago. And they have a Mastodon instance on their server. I like the name of it. It’s not Twitter but it’s TWiT. It’s not social. So I like that. And they also have an instance that is a little bit more moderated so it’s not anybody could come because they want to kind of keep the community tech oriented. So I think that’s a good place to be. But you can follow from any other Mastodon instance on the Gutenberg Times Stream there.
\n\n\n\nRyan Welcher: Awesome.
\n\n\n\nBirgit Pauli-Haack: What else is in there?
\n\n\n\nRyan Welcher: I think we were on post editor. Yeah.
\n\n\n\nBirgit Pauli-Haack: I highlighted that, a little piece there, is just to reiterate that there is a distraction free mode in Gutenberg plugin now that kind of hides all the interface items when you write or at all. So the toolbar on top, the side settings, but also the block toolbar that comes up or any other things that sometimes spring up and distract you from ‘what does it now’ want kind of thing. And now also the notices are now improved that come up on the edit post screen. For instance, the saving part and the transform part when you transform things and all that. That’s nicely improved.
\n\n\n\nRyan Welcher: Yeah, it looks really nice on the screenshot that they have there.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nRyan Welcher: The next one there is…
\n\n\n\nBirgit Pauli-Haack: Go ahead.
\n\n\n\nRyan Welcher: So moving the document information into the outline deal, which is interesting to me. So if you want to know the word count and all that, you normally go up into the… there’s one of the buttons, I can’t remember what it was, what it looks like.
\n\n\n\nYeah. It’s a little I or the info one. But now it’s been moved down to the bottom of the list view, which I don’t necessarily hate. This is the first I’ve seen this one, but I wonder is that an option or is that only in specific instances or is it always going to be there?
\n\n\n\nBirgit Pauli-Haack: That’s always right now. I think the last word hasn’t been spoken yet about that. It definitely needs some additional accessibility review and improvements and it also is missing some information. So I think the time to read comes up if your post is longer than a minute, then you get the time to read. And the number of blocks is, I think, mission. But you also get the outline as well. And that’s a little bit of a duplication between… so the outline is just the headers that are in your document and in the list view, you also see all the blocks that are in there. So it’s kind of a reduced… I like that the information is now just in one panel and it declutters the top toolbar because I’m sure we’re going to get additional information there.
\n\n\n\nRyan Welcher: Almost guaranteed.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I know that some plugins you signed as well. Yeah.
\n\n\n\nRyan Welcher: Yeah. I would love to see this leverage the preferences. The preferences so a user can decide where they want that because that could be something that you… I can see use cases on both sides of it. I don’t care about it, I’m in distraction-free mode whatever. Or I just wanted to be able to be nice and quick because I have a word count that I’m trying to hit or something. So I can see that. I can see people loving this and handling this as with always the case with anytime we change anything. But I think it’s cool. It’s nice.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I definitely wanted to mention it here because I heard from quite a few people that thought, “Oh, it’s missing now, what did I do?” Kind of thing. It’s actually hidden and there is no notification that, “Look here if you’re looking for that” kind of thing.
\n\n\n\nRyan Welcher: Yeah, they used to do that a lot.
\n\n\n\nBirgit Pauli-Haack: And they haven’t done yet for this one.
\n\n\n\nRyan Welcher: They used to have those little blue arrows. Do you remember that pre-Gutenberg days when something would move and all of a sudden there’d be a little blue arrow that says, “Hey, this thing’s over here now”? Yeah, it’d be cool if they did that again.
\n\n\n\nBirgit Pauli-Haack: Yeah. Do they have that feature or kind of the API for that in Gutenberg? I think that will be a good API to have.
\n\n\n\nRyan Welcher: They have the modal that pops up the first time that you go into the Block Editor. That might be something to leverage when there’s an update that gets triggered again with like, “Hey, do you want to see what’s new?” And then everyone will hate it and turn it off. But it might be an interesting thing to leverage to kind of save people from trying to figure out where the heck something went or them feeling like they broke something and… anyways.
\n\n\n\nBirgit Pauli-Haack: No, I totally agree. I totally agree. There are quite a few apps that do this quite well that they have a little notification bell somewhere and they just change the color of it and you know there’s something new. So when you have time to browse that, yeah, you’re going to go there.
\n\n\n\nRyan Welcher: Yeah. Especially something where you’re using-
\n\n\n\nBirgit Pauli-Haack: Does Twitch have that?
\n\n\n\nRyan Welcher: Yeah, it does. And a lot of desktop apps will do that and stuff like that. So I think it’s a nice consideration for a user to be able to say, “Oh, hey. Something’s changed and you can opt into it.” So maybe just having it popped up is not the best way to doing it, but having some notification that shows up that says there’s been some changes to the UI, would you like to see what they are? I think that’d be kind of neat.
\n\n\n\nBirgit Pauli-Haack: And with all those changes coming…
\n\n\n\nRyan Welcher: So you talk to your people about that and I’ll talk to my people about that. We’ll see what happens. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nRyan Welcher: Anyhow, what’s the next thing?
\n\n\n\nBirgit Pauli-Haack: What’s the next thing? Yeah, I’m kind of browsing past the bug fixes and I saw a headline that’s called Meta Boxes. And I was looking at that and the PR is that perform has Meta Boxes check on every safe which I really appreciate now because there have been very much quite some instances where I changed something in a Meta Box but I didn’t hit save. And then I went out there and that thing was also not updated, although all the Block Editor edits were updated. So it now does that in every auto save as well so you’re not losing any data from your Meta Boxes. Yeah.
\n\n\n\nRyan Welcher: Now when you say Meta Boxes, are you saying… the first thing that comes to mind is register Meta Box in the original way that you’d do that. Is that what you’re talking about or just-
\n\n\n\nBirgit Pauli-Haack: Yeah. So the Meta Boxes on the bottom of a screen in the Block Editor like Yoast has them and newsletter…
\n\n\n\nRyan Welcher: Stuff like that. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah. And those boxes were not always saved unless you physically saved it. So the auto save would not catch up.
\n\n\n\nRyan Welcher: Oh, that’s great. That’s so nice because that is horribly annoying when you’ve been messing around with stuff and then you navigate away, that doesn’t trigger the ‘are you sure’? And then you’ve lost your work. That’s nice. That’s really nice.
\n\n\n\nBirgit Pauli-Haack: Especially when you’re so accustomed to the every 15 seconds auto save kicks in and you don’t have to worry about it. All of a sudden you have to worry again. Yeah, it’s a little bit counterintuitive.
\n\n\n\nAnd then we come to the documentation section and there was one thing, that was the Storyboard intro. And the Storybook, not Storyboard, Storybook. Storybook is a tool that allows you to see each WordPress component from the Block Editor in isolation. And you see what values are in there, what action you can have there and you can kind of make some changes and then see how that happens. And this Storybook site didn’t have an intro page. You landed there and it says hello world. And so a few of us got together and updated it so you can learn more about it and also how to…
\n\n\n\nRyan Welcher: Take the credit, Birgit. This was all you. You did this and some people helped. So props to you. It’s quite literally the definition of devral is making this easier to understand. I remember when I started first playing around with this Storybook instance, specifically I was like, “Why is it just say hello world?” And then it would fall off my radar. Yeah. So thank you. From the community, officially thanking you for doing this and making it better. So that’s great.
\n\n\n\nBirgit Pauli-Haack: Thank you.
\n\n\n\nRyan Welcher: I actually used this tool today. It’s so helpful not only for reference guides, but, for example, WordPress icons. Way down the bottom of that list on the left hand side, you can see all of the available icons. And so I was working on that plugin today and I used it and it’s a handy dandy little tool to show you what’s available and you can see it in real time and see the different states of things. It’s very cool.
\n\n\n\nBirgit Pauli-Haack: Yeah. No, I think it improves development. Not only improves it but also speeds it up because you can go there and say, “So what is that component?” You can grab the example code and put it in your component and see how the first version looks. And so it’s really good. We’ll share the tool in the show notes of course so you can check it out yourself and see if you want to use it for your development.
\n\n\n\nAnd the other documentation issue that I wanted to highlight was that the curating the editor experience is a page in the Block Editor handbook. And that was updated with the content lock ability or the content only lock ability. So it’s a WordPress 6.1 new feature and I also link to the developer notes in the show notes. But it practically lets you lock down a pattern for instance. Just that the user only can change the content of the headline, but not the headline itself, the content of the paragraph or just upload a new image. But a block pattern itself stays as it is. So I think that is pretty far reaching because a lot of people build custom blocks because they wanted to lock down content and not have people or users kind of change things. And there is actually no need for that if you now with the content only blocks or patterns because now you just use a normal Core Blocks, a collection of Core Blocks and lock down the changing and only open up the content for that.
\n\n\n\nRyan Welcher: Yeah, I think it’s super powerful. I know coming from the agency world, that was one thing that being able to stop people from creating every iteration of button color on the planet because you have to design for that and you have to count for that and stuff. So being able to just manage the content of something and leave everything else alone, I think, is going to help a lot of people. And this, sorry, explains it a little bit better.
\n\n\n\nBirgit Pauli-Haack: And, again, it speeds up building websites considerably if you don’t have to have a developer create your custom block to have that feature there. So really good.
\n\n\n\nRyan Welcher: Sure.
\n\n\n\nBirgit Pauli-Haack: Yeah. So that was the Gutenberg 14.5. And without any further ado, we go to Gutenberg 14.6 that came out this week.
\n\n\n\nOh we didn’t say 14.9, the release lead was Nick Diego and he also posted the release document. Gutenberg 14.6, Fabian Kagey, was the release lead and that was came out two days ago on Wednesday. And so, yeah, there are quite a few enhancements. Again, it’s a much richer plugin release than 14.5 was. And we have a few things that we wanted to point out. The first one is in the block library. So the navigation block is in major revamp just because you need more space to manage your menu.
\n\n\n\nAnd in 14.6, you now find that the navigation block has an added list view in the side bar and you can have more space to actually create your menu, select the menus, add a new link to a menu instead of doing it all in the small little space that you had next to the insert on the navigation block. So that’s definitely something to check out. And then also the navigation link. It now has a URL feed to the inspector control. So the inspector controls itself, you get a URL, you get names and all that additional features for your links and that is definitely useful. What else is in there?
\n\n\n\nRyan Welcher: Make author block, select or display all users instead of just 10. I just looked at that. It’s not all users, it’s a hundred users. If you have more than 100 users on your site, you’re kind of a special use case anyways I would imagine. So that should encompass the majority of users, but that’s pretty nice. Yeah. I’m not sure the column address.
\n\n\n\nBirgit Pauli-Haack: Yeah, the columns block now has a transform that kind of unwraps the content. Meaning if you get it out of the columns into a normal… so if you have a head and image in a paragraph in a column and you look at unwrap the content, it comes out of the column and-
\n\n\n\nRyan Welcher: Oh, that’s super handy. That’s super handy.
\n\n\n\nBirgit Pauli-Haack: Okay. I can’t figure out where I put this, but now I can kind of get it out of it.
\n\n\n\nRyan Welcher: And, I mean, try to drag it out of columns and figure that all out. Just one button doesn’t make that way easier.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah. Otherwise, you would have to drag and drop, for instance, three blocks instead of having a one button connection there. Yeah, yeah. You got it right. Yeah.
\n\n\n\nRyan Welcher: That’s neat. Oh, and the next one, so the group block now has a variation picker in the placeholder. Which looks really, again, helpful being able to just choose the thing you want, the variation, in there, which is really handy.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I like it that this surface the row and the stack variation right when you select the group block not only when you have it already on your canvas and then on the right hand side, you need to figure out the layouts of that. So, yeah, I really like that. Yeah.
\n\n\n\nRyan Welcher: I think that that’s a quality of life thing right there. So you don’t have to insert the block and then get to the block and then go over to the right like what you’re saying. Just make this nice and easy. You want a row, you get a row. Two clicks, you’re done.
\n\n\n\nBirgit Pauli-Haack: Right. Yeah.
\n\n\n\nRyan Welcher: Yeah. So the next one is under components, update the design of the focal point handle. What does that one look like? I think that’s… well, that’s nice. No, that’s nice. It’s like a little white circle with a little bit of opacity so you can see the stuff behind it. That’s super nice. I quite like that.
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nRyan Welcher: I love that people are actually taking the time and looking at these little… in a grand scheme WordPress, this is a tiny detail, but it just makes it that much nicer. It’s that little drop shadow, you can kind of see the image through it. I don’t know, that kind of stuff I’m always amazed because I don’t… I’m not a designer so I don’t look at things like that. If it was me, it’d be a big block, bright blue in there and it would look horrible but it would do the job. So it’s nice there’s this level of refinement happening to these existing tools.
\n\n\n\nBirgit Pauli-Haack: Yeah. A good job on the designers and they really figure out all the alignment like when they redesigned the whole setting section or the style section on a block where you have two things in one row, they’re all line up nicely. That was in a second iteration but they now have a standard how to do that. So it’s really good. And the next one is the same qua… it’s also a quality of life thing, but it also speeds up your writing. You can convert paragraphs to headings with a keyboard shortcut and the keyboard shortcut…
\n\n\n\nRyan Welcher: Ctrl+Alt.
\n\n\n\nBirgit Pauli-Haack: Ctrl+Alt and then the number for the heading. So for H2, it’s Ctrl+Alt 2 and for three is… H3 is Ctrl+Alt.
\n\n\n\nRyan Welcher: Yeah. If you’re on a Mac, I guess there’s options. So Ctrl+Options one to six.
\n\n\n\nBirgit Pauli-Haack: Ctrl+Options, yes. Yeah, yeah.
\n\n\n\nRyan Welcher: Which is nice because I just learned that you can do that in Google Docs. So that’s a nice carryover here.
\n\n\n\nBirgit Pauli-Haack: Yeah, yeah. And I wish Google would carry over the paste.
\n\n\n\nRyan Welcher: The link? Were you going to say the link?
\n\n\n\nBirgit Pauli-Haack: Link. Yeah.
\n\n\n\nRyan Welcher: Yes. Why does Google Docs not have that?
\n\n\n\nBirgit Pauli-Haack: It trips me up every time. Every time I have a link on a Google, it kind of trips me up.
\n\n\n\nRyan Welcher: Yeah, I know. And I just end up pasting over top of the text that I just wrote because I want put a link on it. Hey, Google. Hey, Google, if you’re listening. I’m going to trigger everyone’s Google Home now by saying that.
\n\n\n\nBirgit Pauli-Haack: Mine is downstairs so no problem with that.
\n\n\n\nRyan Welcher: Yeah. Oh, mine just triggered. I have one in the garage here and it just triggered. It just said, “I can’t hear what you’re saying.” Anyways.
\n\n\n\nBirgit Pauli-Haack: Well, ours, when it kind of gets triggered from something on the TV, it responds back in German. It’s so funny.
\n\n\n\nRyan Welcher: Oh, wow. Okay. Yeah. That’s funny.
\n\n\n\nBirgit Pauli-Haack: Yeah, the home devices. Yeah. Okay. And the next one is really the following, the change in vocabulary. We don’t say full site editor anymore, we do just site editor. And that, of course, needs to come through the whole interface and some other documentation. I think we will follow it quite a bit, but sooner or later we will all be there.
\n\n\n\nRyan Welcher: Yeah. It’s the same thing as trying not to call the Block Editor Site Editor Gutenberg, because Gutenberg’s the name… it’s the codename of the project, right? I know I’m very guilty of it just using it as a catchall tool. So I think this is just a matter of leading by example and having people, maybe not correcting everyone, but just kind of using it.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah. Exactly. Oh, we talked about the minimum height on the dimensions already, I think.
\n\n\n\nRyan Welcher: I think we did. Yeah.
\n\n\n\nBirgit Pauli-Haack: Yeah. But there’s also another design tool change or update. So on the right hand side, do you have the dimension controls and the spacing for padding and margin controls? And you notice when you go and change it in the step scale that it has a little visualizer around the block that you are editing in blue. And now that process also will hide the toolbar. So you really can concentrate on that block that you’re trying to place pixel perfect into your canvas. So I really like the spacing visualizer because I can never figure out is margin new outside or inside or is that padding outside on inside? So the visualizer really helps you with that.
\n\n\n\nRyan Welcher: That is really nice. Yeah. On the global styles, they have some elements of adding a tech text decoration control to link elements. That’s nice. Being able to manage that. Very cool. Blue typography, adjust font size, min and max rules. That’s great. These are all interface items. They’re all being added to-
\n\n\n\nBirgit Pauli-Haack: The theme JSON items.
\n\n\n\nRyan Welcher: Yeah. But are they adding controls for them as well like the one for the text link?
\n\n\n\nBirgit Pauli-Haack: Well, the text … Yeah.
\n\n\n\nRyan Welcher: Yeah. And I think some of these are sort of… the other one we were talking about, the min height I believe that was more about… the first thing we talked about was allowing it to work and the second one was giving a sort of a control and some tooling around that.
\n\n\n\nBirgit Pauli-Haack: And for fluid typography, I think they have started working on the interface or the user controls for it. But they’re right now only available through the theme JSON and they added minimum and maximum rules for the fun size. So you can actually change those, which was missing in 6.1 when the fluid topography came in the first time. And there is another global… so it’s also an attempt to see if you can generate random color palettes.
\n\n\n\nRyan Welcher: Pretty neat.
\n\n\n\nBirgit Pauli-Haack: It’s pretty neat for those that are having a hard time with the design that you can give a color and then it gives you additional colors that match that or kind of go well with it.
\n\n\n\nRyan Welcher: That’s super neat.
\n\n\n\nBirgit Pauli-Haack: Yeah. You don’t have to think about all the colors that you wanted to use. It’s really neat.
\n\n\n\nRyan Welcher: Yeah, that’s really neat. I can just hear the agency folks going, “No.” But, yeah, being able to generate… that’s so neat. For someone like me who’s not a designer, who’s colorblind, being able to pick one color I like and then having sort of other complimentary colors generated for me, I think that’s really cool. It’s a really cool idea. Hopefully you can disable that for certain individuals or certain use cases I should say.
\n\n\n\nBirgit Pauli-Haack: I hope so too. It’s actually in the style variations. Those, you can shut down quite a bit. I’m just going through the PR and looking for ‘to disable this, do this’ but I haven’t found it yet, but I’m also just scrolling through some of them. But those, okay, disable things will never be in the first iteration of a feature because you need to be pretty firm on how a feature works before you can say, “Okay, and now we disable it.” But given the history of whatever happened before, I think there’s a good chance that that will be added. Yeah.
\n\n\n\nRyan Welcher: Definitely. So some bug fixes there. Play board is in both front end and editor. Well, that seems like a good thing to do.
\n\n\n\nBirgit Pauli-Haack: Yeah, that bug has been fixed.
\n\n\n\nRyan Welcher: That’s great.
\n\n\n\nBirgit Pauli-Haack: Yeah. And other than that, I… or the Block Editor. So the list view has been updated to disable the branch expansion when a block editing is locked. So if you are not allowed to edit it or if you’re not allowed to move it or remove it and you can only edit the content, then it will not expand in the list view either.
\n\n\n\nRyan Welcher: Right. So an example would be you’ve got a group block that you’ve locked and so you can’t see any of the nested blocks in there. You can’t expand that tree to see that. I think that’s really smart. I think that’s really smart because there’s a way of getting around locking and why clutter up the list view if you can’t… if you’ve got 100 blocks in there, it’s a very complicated pattern. You’ve inserted it, but why mess up the list view with stuff you can’t even edit in the first place? That’s my opinion.
\n\n\n\nBirgit Pauli-Haack: Yeah, yeah. Then we have some experiments. We didn’t have a whole lot of experiments for a long time, but at the beginning of the Gutenberg development, there were a few experiments where developers wanted to just see how things work. And we are back to that. The navigation list view is actually an experiment. And then also inspector based navigation editing is also an experiment. So when you install the Gutenberg plugin, you need to go down to the menu where it says Gutenberg and then go to the experiments settings page and then enable those so you can test them. Yeah. What else?
\n\n\n\nRyan Welcher: You want to move on the documentation?
\n\n\n\nBirgit Pauli-Haack: Yep.
\n\n\n\nRyan Welcher: Yeah, a lot of nice little documentation changes, changing titles around working with JavaScript in Gutenberg as opposed to just being… oh, and this is another Birgit thing here. So it’s not about getting started with JavaScript, it’s about how to use JavaScript in Gutenberg. It’s a fundamental difference because the assumption is that you do know how to use some JavaScript when coming to working with the Block Editor and Gutenberg Project and stuff like that. So I think it was a misnomer. So nice job.
\n\n\n\nBirgit Pauli-Haack: Well, thank you.
\n\n\n\nYeah, there were quite a few posts in the community there where the PHP developer kind of started to figure out how that works with block development and all. And I saw if not twice, but three times that people didn’t get to that handbook section because of the title. It says How to Use JavaScript instead of ‘How to Use JavaScript With Gutenberg’ or with WordPress is actually the title now. WordPress Block Editor. Of course they’re not saying Gutenberg, but I think that helps people who kind of read through the handbook to get to those pages much earlier in their discovery and also save them some headaches on their way to discover that. Yeah.
\n\n\n\nRyan Welcher: Yeah. I mean it’s much more discoverable now and I think that’s great. That’s wonderful.
\n\n\n\nBirgit Pauli-Haack: And are you reorganized to create block documentation?
\n\n\n\nRyan Welcher: Yeah, yeah, yeah. We added another subsection. One of the things in the handbook is we have that massive left hand navigation that has accordions in it. And so for some of these packages, they can get quite lengthy those sections. So a while back, we worked on having the DocGen tool… so the DocGen tool is what generates the docs, but then get ingested into the Block Editor handbook from the Gutenberg repository. So we were working on ways of having sort of nested pages underneath those sort of subsections. And so that’s part of what one had done here. It’s great that it splits out to the available commands and kind of organizes that content a little bit better so it’s a little bit more palatable. Because, as we all know, the documentation in WordPress, there’s a zero to 100 thing. Here’s the basics and then here’s everything else you could ever need to know about it all on the same page. And that’s just hard to ingest and it’s hard to kind of parse through.
\n\n\n\nSo by doing this, and we’ll be doing this to some other packages as well, I have a pull request in place that I have to finish for the scripts package that does the same thing. That kind of breaks out some of the more complicated things, more advanced things into their own pages because for the majority of users, they don’t need that. They just need to know what commands are available, for example. So, yeah, that’s the motivation behind this.
\n\n\n\nBirgit Pauli-Haack: Yeah. I think it’s good kind of to go once in a while through documentation and do a little bit of an overhaul to update with the feedback from developers that have tried to insert information and say, “Okay. Well, it could be a little bit better.” So any improvement, you dear listeners, that you find or you couldn’t imagine, let us know on any places either WP Slack or a Twitter DM or on the Gutenberg Repo and we definitely are receptive to that and help out with making that happen.
\n\n\n\nRyan Welcher: Absolutely. Many hands make light work.
\n\n\n\nBirgit Pauli-Haack: Many eyeballs, bugs are shallow. It’s the same with documentation. Yeah.
\n\n\n\nRyan Welcher: Oh, okay. Yeah, totally.
\n\n\n\nBirgit Pauli-Haack: That’s great.
\n\n\n\nRyan Welcher: Okay. So that’s all the documentation stuff we’re going to go through. And then what’s next? Code quality or patterns?
\n\n\n\nBirgit Pauli-Haack: No. I think we are done a certain… yeah. Well, there is a view call…
\n\n\n\nRyan Welcher: There’s a few things bolded in the code quality ones, but I don’t know if that’s-
\n\n\n\nBirgit Pauli-Haack: I actually bolded them to do some more research on it, but I didn’t get to it.
\n\n\n\nRyan Welcher: I mean most of these things like the color palette, color box, kind of border box polish and dry prop types add default values. This is just making it easier to use the rename to .TS is for type script I guess. Yeah. I don’t know if there’s anything you want to specifically call it.
\n\n\n\nBirgit Pauli-Haack: Yeah. No, I don’t think we… there’s one change in the pattern directory API that it now supports pagination parameters, but that’s for Gutenberg developers or for contributors that use type into the pattern directory.
\n\n\n\nRyan Welcher: Oh, okay. Yeah.
\n\n\n\nBirgit Pauli-Haack: I don’t think it’s a public API. I wasn’t quite… oh, I think I was… yeah, I got the 401 kind of there not allowed, but I’m not quite sure.
\n\n\n\nRyan Welcher: Yeah. It’s probably locked down. You probably have to be… well, no. Maybe. I don’t know. I have to look here. Anyways, it’s giving us pagination, which is great.
\n\n\n\nBirgit Pauli-Haack: Yeah. So if you wanted to have more than 30 blocks or something like that so … No, it’s a 404 not found. So it’s kind of-
\n\n\n\nRyan Welcher: Okay. Yeah. So it’s locked down to somebody.
\n\n\n\nBirgit Pauli-Haack: Yeah, it’s locked down. All right, so that was the Gutenberg 14.6 release and now we are coming into section with what active development and discussions. And there are quite a few things that I find really, really exciting for the next iteration and I hope they make it all… there are still open PRs so you can test it. There is a different way how to test open PRs, but you get some great videos that demonstrate the features. So the first one is the design concepts for the browse method. So now that there are so many things that you can do in the site editor, the design team came up with how can we unify some of the interfaces. Some things are on the left column, some things are in the right column and can we have not all together, what about design?
\n\n\n\nAnd they have some nice ideas where the global styles will be taken out of the right hand side, put them on the left hand side, have a design sub menu for the site editor. Also have a template sub menu for the site editor, but it’s all in one place. It’s not kind of fragmented.
\n\n\n\nRyan Welcher: Yeah. It’s really nice. I’m just kind of scrolling through some of the design items in the ticket there. It looks great. The transitions that they have going, I just think it’s going to be really nice.
\n\n\n\nBirgit Pauli-Haack: And there’s also a browse mode. So when you click on the templates or page template, you see all the page templates in thumbnails. But they’re relatively big depending on your screen, but you see how they kind of can change when you change the style variation as well. So there’s a lot more ‘what you see is what you get.’ And also kind of keeping a broader view on your site, especially when you do a lot of customizations on your templates to make it a little bit more consistent. Also show you things that are not consistent. So I think that really helps with the customization for site owners and those who actually build themes through the interface to have a better view on how this all looks.
\n\n\n\nSo that’s one thing that I wanted to talk about. The other one is they’re working on a… and that’s more for the migration from classic themes to block themes that you can import widgets from the sidebar or that you’re using the sidebar that you can add them to block-based theme parts or template parts. And because the widget wasn’t available yet, there was a plugin available to add it to the site editor by Justin Tadlock called Classic Widgets. And this is the attempt to get it all into core, but that is definitely something to check out and see how that suits you. There’s not a whole lot of inter… yeah, there is a little video there on how to do that. So how it’s going to work, and I really like that.
\n\n\n\nRyan Welcher: Yeah, this stuff’s so cool. It’s just amazing. I don’t know. That’s the stuff that they’re working on. I’m just like, “I don’t even know how to start that. I don’t even know how to build that.” But you all are doing a fantastic job doing all these cool things, so yeah. Glad I got out of development when I did because clearly I’m not qualified to do it anymore.
\n\n\n\nBirgit Pauli-Haack: Yeah. And that’s certainly something that… it’s for web developers that come from the ’90s or early 2000s that kind of did all the database, the CSS, the HTML, the PHP, the JavaScript. I think it’s part of the times that you are not being expert in all of them as you were able to do in the early 2000s or mid 2000 or when WordPress came out with custom post types and you can do it all. Yeah.
\n\n\n\nSo, yeah, another thing that working on is actually managing the font sets for the global styles typography and how you can kind of make them available to more than one block or kind of have the settings. Okay, I want those… you cannot go to every block and change the font family. You need some more general places where you can just click on things and then that applies that particular font family to that series of blocks. So you can kind of get this a little bit better. But that is really hard. When I look at the interfaces and all the design interfaces, you get a good feeling how hard that actually is to make this palatable for non code users to put it in an interface that’s not crowded, that’s not give you a lot of cognitive overload.
\n\n\n\nRyan Welcher: And isn’t developer jargon loaded. It’s hard to be able to communicate what a font face means or font weight. I know what that means as a developer, but if you’re not, then how do you explain how thick your letters are basically. It’s kind of how it is, right? Letter thickness. Maybe that’s how you do it. I don’t know. I’ll leave that to the professionals.
\n\n\n\nBirgit Pauli-Haack: Yeah. And I mean the other interfaces like the text editors or like the Google Docs that have some of it, but then there is such a granular control that a theme developer would need as well that it kind of can really overload the things. Yeah.
\n\n\n\nRyan Welcher: For sure.
\n\n\n\nBirgit Pauli-Haack: And one feature I really like is that to make it possible that you push a local block style to the global styles. You say, “Oh, I like this block how it is and that post that I just wrote and I wish all my blocks, my paragraph blocks or my image blocks would look that way.” Now they’re working on it that you can push that to the global styles and then all of a sudden every…
\n\n\n\nRyan Welcher: So like reusable blocks, but for styles kind of?
\n\n\n\nBirgit Pauli-Haack: For styles, yeah. Reuseable for styles kind of thing.
\n\n\n\nRyan Welcher: Yeah. So anytime you insert a paragraph block, you’d have that style available to you even if it wasn’t defined as part of your theme. I think that’s super cool.
\n\n\n\nBirgit Pauli-Haack: Yeah, it’s super cool at the beginning when I think so. But if I think about, okay, how often do I change my mind? I said, “Oh, that could be really hard to kind of redo it.” Yeah, you want it on 15 blocks but not on 80 blocks kind of thing. Yeah.
\n\n\n\nRyan Welcher: Yeah, yeah. That’s true. Maybe they’ll need an interface for editing those curated things where you edit the style and everything just gets automatically, but who knows? Who knows?
\n\n\n\nBirgit Pauli-Haack: Yeah.
\n\n\n\nRyan Welcher: Sounds cool. Cool either way.
\n\n\n\nBirgit Pauli-Haack: You need to explore that and if you tested and use it and then all of a sudden you see what’s working and what’s not working. Yeah. Now the other two really exciting as well. Do you want to take the first one or?
\n\n\n\nRyan Welcher: Is that the pre-published one?
\n\n\n\nBirgit Pauli-Haack: Mm-hmm.
\n\n\n\nRyan Welcher: Yeah, so this one’s really cool. When you’re about to publish a post, if you have images that are external to the website. So if you imported a post from something and the URLs to your images are somewhere else, in the pre-published sidebar that says are you ready to publish, there’s a new panel being sort of suggested to be able to identify that you’ve got external images and give you the option to upload into your media library. I think that is such a handy thing. I know having done about a billion migrations that that’s a point of contention because it’s not easy to move those images programmatically. It can be done, but if you’ve imported stuff or copied and pasted and it’s there and you can just do it with a button, that’s so much simpler. I mean it’s not going to translate to doing 1000 posts all at once, but at least it’s such a nice feature. I think it’s so cool.
\n\n\n\nBirgit Pauli-Haack: Well, it’s only for that particular page, right?
\n\n\n\nRyan Welcher: Yeah, yeah. Exactly. It’s not bulk uploading for the entire site, it’s for that specific page. Which I think is great. So cool.
\n\n\n\nBirgit Pauli-Haack: Yeah, I really like that. And there was always a restriction before. There was a button on each image block that said upload image, but that was kind of hit and miss as well. With Google Docs for instance, it worked, but it didn’t work with other WordPress sites or certain WordPress sites on certain servers. But Ella put some research on it and found how that can be consistently work better now with that tool as well. And there’s another PR open to copy that over to make that even better.
\n\n\n\nRyan Welcher: Right. Yeah. I think it’s really nice. On the issue that I’m sure will be linked in the show notes, there’s a nice little graphical representation of what that looks like. It’s nice and slick and just seems super easy. Yeah. The next one is… this has been merged. It’s going to be the next version of Gutenberg I believe, but it’s an experimental feature that’s… so it’s an experiment on the experiment. In the sidebar, this is going to split block sidebar controls into tabs, which I think is super neat. So being able to define settings for a block and appearance or styles or whatever you want to call it in separate tabs. So that’s pretty exciting. As a block developer, I’m pretty excited about being able to do that because I know that that sidebar gets really… with really complicated blocks that are doing lots of things, that sidebar gets really tall. Really, really big and you have to have all your panels come in and they’re collapsed by default. But being able to split them out in into tabs will make that a much better experience I think.
\n\n\n\nI’m not sure about the technical implementation right now, but I would imagine though instead of just wrapping everything in inspector controls, you might have inspector control settings and inspector control appearance or whatever you want to call it. So, yeah, that’s something that I’m excited about is I nerd out about that kind of stuff.
\n\n\n\nBirgit Pauli-Haack: And I think it’s much easier also for a user to have that separate because sooner or later, you’re done with fiddling with the design of your site and now you’re putting content and you don’t have to touch those tires anymore or scroll past them all the time. So it’s really a good way to think about these things and put them in experiments so we all can experience them and kind of see what works and what doesn’t work out. Yeah.
\n\n\n\nRyan Welcher: Yeah.
\n\n\n\nBirgit Pauli-Haack: I think what’s active in development is so exciting for me to look forward and I hope all of this makes it into 6.2. That’s the next major version and we don’t have a plan yet for 6.2 and I think sooner or later, it will come out. I know that Hector and some of the core contributors are working on it and figuring out what will be a good release.
\n\n\n\nIt’s definitely going to be not in 2022, so it’ll be February or March of 2023. And maybe even before. Maybe not WordCamp Asia, but after WordCamp Asia. Yeah. Oh, speaking of which, what we haven’t announced yet is the State of the Word. That’s before the end of the show and we are all on the end of the show. The State of the Word will be happening in New York and on livestream on December 15th at 1:00 PM Eastern, that’s 5:00 PM UTC or 17:00 UTC… No, 1:00 PM Eastern is plus five, it’s 18:00 UTC and 17:00 Central European Time. And we share the announcement post to the State of the Word on the news section in the show notes, so you can all make your reservations. There’s also a form that you can apply to actually come to the event in New York. It’s, again, in the Automattic office like last year and the Automattic office and SOHO office in New York City in Manhattan. It’s going to be pretty cool. It’s scheduled for one hour and a half, and normally that’s kind of half an hour presentation by Matt Mullenweg and Josepha together. And then Q&A for another hour, both livestream and in-person. Yeah.
\n\n\n\nRyan Welcher: Very cool. Nice. Exclusive.
\n\n\n\nBirgit Pauli-Haack: Well, it’s published already.
\n\n\n\nRyan Welcher: Oh. Well, then it’s not that exclusive. I just haven’t seen it. It’s exclusive to me, I just haven’t seen it yet.
\n\n\n\nBirgit Pauli-Haack: Yeah. As always, the show notes will be published on gutenbergtimes.com/podcast. Well, it’s hard today. Published on the gutenbergtimes.com/podcast and this is episode 76. And if you have questions or suggestions or news that you want us to include, send them to changelog@gutenbergtimes.com. Yes, that’s an email address and that’s changelog@gutenbergtimes.com. So thank you so much, Ryan. It was wonderful to have you. Do you have anything that you want our listeners to know that you haven’t talked about yet or how can people reach you?
\n\n\n\nRyan Welcher: Well, I don’t have any exclusive things to announce today, but you can find me online. I’m @RyanWelcher on Twitter. I am Welcher or Welcher Ryan or Ryan Welcher on basically every other piece of social media. My Twitch, you can check me out at RyanWelchercodes. And that’s the same name for my YouTube channel, which is also Ryan Welcher codes. And I think that’s probably it. But, yeah, I’d love to have everyone come and hang out with me on Thursdays 10:30 Eastern when I do my livestream. But thank you for having me, Birgit. I know. Love coming here and hanging out and talking to all this cool code stuff.
\n\n\n\nBirgit Pauli-Haack: Yeah. And it’s so wonderful to have you. Yeah. To talk through those things and have all your excitement for the Gutenberg developer. Custom development is such a nice addition to the Gutenberg Changelog. Thank you so much.
\n\n\n\nRyan Welcher: Thank you for having me. Looking forward to the next one.
\n\n\n\nBirgit Pauli-Haack: Yeah, and this was it. Thank you all for listening. This is goodbye for me and talk to you the next 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 27 Nov 2022 14:58:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:19:"Gutenberg Changelog";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:13;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:35:"BuddyPress: BuddyPress 11.0.0-beta2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://buddypress.org/?p=327306";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:55:"https://buddypress.org/2022/11/buddypress-11-0-0-beta2/";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:3457:"Hello BuddyPress contributors!
\n\n\n\nIf you haven’t tested our first 11.0.0 beta release, here’s another opportunity to help us give the final touches to our next major release so that we make sure it will fit perfectly into your WordPress / BuddyPress specific configuration. Beta testing is very important and we need you all, whether you’re a regular or advanced user, a theme designer or a plugin author: please contribute!
\n\n\n\n\n\n\n\n\n\n\n\nPlease note the plugin is still in development, so we recommend running this beta release on a testing site.
\n\n\n\nYou can test BuddyPress 11.0.0-beta2 in 4 ways :
\n\n\n\nsvn co https://buddypress.svn.wordpress.org/trunk/git clone git://buddypress.git.wordpress.org/The current target for final release is December 14, 2022 
. We would greatly appreciate your help making sure this next major version of your community engine is as good as it can be.
Since beta1, we’ve fixed 12 new tickets and documented some important changes BP Themes or Plugins authors should definitely read:
\n\n\n\nIf you find something weird testing this beta, please report it on BuddyPress Trac or post a reply to this support topic.
";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, 25 Nov 2022 22:28: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:12:"Mathieu Viet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;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:58:"Post Status: WordPress is People (Weekly Community Update)";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=145168";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://poststatus.com/wordpress-is-people-weekly-community-update/";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:2397:"Yes, of course WordPress is software. It’s code. It’s several different programming languages. It’s blocks. It’s the editor. Yes, it''s all of the technology.
\n\n\n\nBut it’s people. It’s created by people. It’s used by people. It relies on people to move it forward, to modify it, to moderate it, and to build community around it.
\n\n\n\nJohn Donne said “No man is an island, entire of itself; every man is a piece of the continent.” The same is true about WordPress. Each of us is part of it. WordPress is you and me. It’s us.
\n\n\n\nIf you’re interested in volunteering your time, skills, and resources to the open source project, there are many ways to be involved (and most of them aren’t coding). Learn more about ways to get involved on the WordPress website.
\n\n\n\nHave you snagged some good deals? (I’ve found a few!) We’ve accumulated over 200 deals on our site. I bet whatever you might need is there. Find this year’s deals here.
\n\n\n\nDid someone say Black Friday? We have a deal, too! Get $100 off any level membership. (Gets you Slack access, too!)
USe code: BFCM
Effective 11/25 – 12/31
Have you ever wondered who it is that makes Post Status work? Look no further than our About Us page to meet the Post Status team: Cory, Lindsey, Michelle, Adam, and Olivia
\n\n\n\nThis article was published at Post Status — the community for WordPress professionals.
";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, 25 Nov 2022 18:35:23 +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:"Michelle Frechette";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:15;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:31:"WPTavern: Dig Into the Open Web";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=139721";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"https://wptavern.com/dig-into-the-open-web";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:4066:"As the American Thanksgiving holiday is coming up, I am so grateful for all of our Tavern readers and the people who make WordPress – 800 in the most recent 6.1 release with 35 percent of them being new contributors. This community has made remarkable progress this year, while navigating changes and uncertain times. Committed contributors continue to show up and make WordPress the best platform for publishing on the web.
\n\n\n\n\nThis time last year, WordPress didn''t have:
— Rich Tabor (@richard_tabor) November 23, 2022The Site Editor
2022 has been WORK.
Good stuff team!
The recent social media upheaval with Twitter has been an unexpected gift that has created an opportunity for a mass return to decentralization and open web protocols, like ActivityPub and RSS. The sting of the prospect of losing Twitter followers and the network that users worked to build, has underscored the importance of agency in social networking, the ability to take your data and connections with you to other networks on your own terms.
\n\n\n\nAlthough it is somewhat heartbreaking to see Twitter struggling to survive, one silver lining is that this situation is inspiring a drive towards a greater level of interoperability between apps, like Tumblr engineers working to add ActivityPub support so users can connect across Mastodon and other networks that use the same protocol.
\n\n\n\nPeople are steadily moving away from the all-powerful algorithms that steer consumers and subtly manipulate the public consciousness, and migrating away in search of healthier, more ethical social networking alternatives. The refreshing lack of ads and algorithms are winning people over in decentralized social networks, which are getting a second look from mainstream publications in light of Twitter’s loss of critical engineering teams.
\n\n\n\nI’m thankful for this renewed focus on networks that value the open web, where people are now exploring alternatives to walled gardens with their friends, instead of having to start over alone. Never underestimate the power of friction and crisis to refine how we communicate and motivate us to find a better way to stay connected. This is a moment that may have enough traction to change the course of social interaction on the web.
\n\n\n\nWith things changing all around, it’s heartening to know that WordPress is still here and going strong, for those of us who have chosen it as the home for our content. We’re fortunate to have so many plugins available that connect our ecosystem to the broader web, allowing us to syndicate content to almost anywhere. Let’s not miss this opportunity to dig into the open web and see where it takes us.
";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, 23 Nov 2022 21:06: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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;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:87:"Post Status: State of the Word 2022 • Dev Blog Beta • WP 3.7 – 4.0 Final 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:32:"https://poststatus.com/?p=145071";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:86:"https://poststatus.com/state-of-the-word-2022-dev-blog-beta-wp-3-7-4-0-final-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:17376:"As 2022 comes to an end, State of the Word will happen in NYC again. Apply to attend or tune in to the livestream. Check out the beta version of the WordPress Developer Blog. Still have sites on WordPress 3.7 – 4.0? It''s really time to upgrade as this will receive no further updates after December 1. It''s team rep nomination time too.
State of the Word 2022
WordPress Developer Blog is in public beta Final releases of WordPress 3.7 – 4.0
Team Rep Nominations, 2022
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.
Are you interested in giving back and contributing your time and skills to WordPress.org? 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.
You — and your whole team can Join Post Status too!
\n\n\n\nBuild your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. Listen to podcasts. Follow @Post_Status and LinkedIn.
This article was published at Post Status — the community for WordPress professionals.
";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, 23 Nov 2022 18:51:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:17;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:84:"WPTavern: #52 – Hannah Smith on Why We Need To Be Making Websites More Sustainable";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=139776";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:98:"https://wptavern.com/podcast/52-hannah-smith-on-why-we-need-to-be-making-websites-more-sustainable";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:46564:"Transcript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley.
\n\n\n\nJukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case making websites more sustainable.
\n\n\n\nIf 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.
\n\n\n\nIf you have a topic that you’d like us to feature on the podcast, well, I’m very 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.
\n\n\n\nSo on the podcast today, we have Hannah Smith. Hannah is the operations and training manager for the Green Web Foundation, and founder of The Let’s Green The Web campaign. She’s also co-founder of Green Tech Southwest.
\n\n\n\nHer background is in computer science. She previously worked as a freelance WordPress developer and also for the Environment Agency, where she managed business change projects.
\n\n\n\nIt’s pretty easy to forget that the device that you’re reading or listening to this podcast on is consuming power. We plug things in or charge them up, and they just work. They are sleek and sterile. No pollution comes out of the device directly. In fact, I’d go as far as to say that many of us never make the connection between our use of technology and the impact that this has on the environment.
\n\n\n\nEnter Hannah Smith. She’s been thinking about this for years and is on the podcast today to highlight the issue and hopefully get your ideas about what users of WordPress can do to make sure that the websites we create are having the smallest impact possible.
\n\n\n\nHer approach is not that we need to cease and desist using our technology. Rather it’s about coming up with new and innovative ways that we can reduce the impact that we have.
\n\n\n\nAs creators of websites, there are a whole raft of options available to us. Reducing the size of our images. Inspecting the HTML to remove bloat. Choosing hosting options that source renewable energy.
\n\n\n\nWith this in mind, Hannah and others have been working on a sustainability related blog post, which has been published on the Make WordPress site this week. This post is intended to trigger meaningful and open discussion in the global WordPress community about the topic of sustainability.
\n\n\n\nShe really wants to encourage others to weigh into this public conversation with their own thoughts, so that we can build on what is already happening to make WordPress more sustainable.
\n\n\n\nIt’s a fascinating and thought provoking topic, and if you’re interested in finding out more, you can get all of the links in the show notes by heading over to WPTavern.com forward slash podcast. Where you’ll find all of the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Hannah Smith.
\n\n\n\nI am joined on the podcast today by Hannah Smith. Hello Hannah.
\n\n\n\n[00:04:02] Hannah Smith: Hello Nathan. Thank you so much for having me today.
\n\n\n\n[00:04:05] Nathan Wrigley: You are so welcome. Hannah is here today to talk about the environmental impact of having WordPress websites, and I genuinely think this is going to be a real eye opener for many of us.
\n\n\n\nBefore we do that though Hannah, we always orientate our listeners by allowing the guests to just give us a bit of background on who they are and what their relationship is with WordPress. So if you don’t mind, I’m going to ask you that very generic question is just tell us a little bit about yourself and how come you are into WordPress.
\n\n\n\n[00:04:35] Hannah Smith: Thank you. I’m a massive fan of WordPress. I’ve so much love and admiration for the community. So my background is as a computer scientist, so that’s what I studied in my degree. Had, like many people, are very sort of winding interesting journey in and around different things.
\n\n\n\nAnd about eight years ago, I set myself up as a freelance WordPress developer. So having done sort of other careers within tech, I won’t give you the long winding path that I got there, but serendipity basically somehow landed me, as a freelance WordPress developer. Finding myself wanting to give it a go.
\n\n\n\nI was living in Bristol at the time, and wanted to learn more about WordPress and found that we had a meetup community in Bristol, and decided to pop along. Was made to feel very welcome, and learn loads from the awesome people there. So, a shout out to Simon, Janice, and Rob, who were the people that grounded me into that community.
\n\n\n\nAnd then it wasn’t long before I somehow found myself invited to help run that community and help drive that community, which I was very happy to do for a good few years. And then in 2019 we did WordCamp Bristol. We had about 200 odd people come to that, which was brilliant. And I’ve been quite involved in WordCamps and speaking at conferences. Try and contribute where I can.
\n\n\n\nThese days I’ve actually hung up my shoes, only recently as a WordPress developer, and I’ve transitioned to working full-time for the Green Web Foundation. But part of my role at the Green Web Foundation, so I do a lot of training and outreach and operations, because we’re small, so everyone wears lots of hats.
\n\n\n\nBut I do also manage our WordPress website as well and our WordPress estate too. So, whilst it might not be my full job title to have WordPress every single day, it is still very much a part of what I do.
\n\n\n\n[00:06:35] Nathan Wrigley: Thank you. What a, rich and interesting history you’ve had. We’ve met in person on a number of occasions, but it’s been a little while since we met up in person. But you came across my radar on the 1st of November because of a piece that you had written over on make.wordpress.org.
\n\n\n\nI will link to it in the show notes and, it may well be a good idea, if you’re listening to this podcast and you are anywhere near a device, it might be a good idea to pause the podcast actually. Go and read the piece it’s called, now we have a sustainability channel in making WordPress Slack, what should we do?
\n\n\n\nAnd the reason I’m asking you to potentially go and read that is because really it’s going to form the basis of everything that we are going to be talking about around the environment and so on. So tell us what was the concern? What was the primary motive for writing that piece?
\n\n\n\n[00:07:25] Hannah Smith: So, the piece was written very much in collaboration with four others, so I want to say from the outset that whilst it was my face next to the post when you read it, I was the nominated person to publish it. It was very much a collaborative effort with four others.
\n\n\n\nSo with Nora, Nahuai, Pace, and Csaba, who are placed in different places across Europe. And, Nahuai and Nora, I knew from some workshops I’d run back in the spring, exploring the topic of digital sustainability. But we were chatting and we all felt that where was the action in WordPress on sustainability?
\n\n\n\nWe were kind of looking around and, I’m very involved in the wider community around digital sustainability. But I was looking around and I was like, I just don’t feel this in WordPress. It’s just not surfaced enough. It’s very niche and, we are really getting to a point where sustainability can’t be a niche concern.
\n\n\n\nIt has to be a concern for everybody, everywhere because what’s happening around us in terms of the changing climate, in terms of our lack of sustainable approaches, does affect every single person, whether they want to admit that or not. We are all impacted by it. Rich, poor, young, old, we’re all going to face these consequences.
\n\n\n\nSo we were chatting and Nora and Nahuai I were at WordCamp Europe this year, and Nora actually asked a question in, you know the Q and A that Josepha and Matt have? So Nora asked a question about sustainability and stood up. I mean more power to her. She stood up in front of the whole crowd and said, hey, sustainability. We really care about this, but there’s nothing much happening, and Matt and Josepha said, well, okay, look. The very first thing we can do is set up a channel in Slack. So maybe that will help, WordPress Slack. You know to give people a collaboration space and a meeting space.
\n\n\n\nAnd they also said, well, and if you’ve got any ideas or specific proposals that you want to make, we are going to listen. The door is open, essentially. So Nora set this ball in motion really with her question. And then Josepha and Matt responded really well. And so since then, since the summer, a few of us have been sort of working, just informally, thinking, okay, well how do we capitalize upon this?
\n\n\n\nWordPress leadership is saying we’re listening, or, we are happy to collaborate with you. But now what we need to do is to get the community together and to get the community, A, to know who each other are, and B, to acknowledge this is a topic and to talk about it, and discuss it, and bring knowledge and ideas into a space together. So this is why we ended up writing the post. And the post is very much saying, hey, WordPress community, look, we’ve got this channel, but you know, a channel isn’t going to solve our problems.
\n\n\n\nIt’s, it’s you. You and your ideas that are going to solve these problems or that are going to make progress. So, could we please get into a discussion about what people’s ideas are? So we’ve invited people to share their ideas and particularly any vision that they have. Or ideas that they have around what sustainability and WordPress might look like in the future.
\n\n\n\nBecause if we can’t imagine it, we’re not going to get there. And I think a lot of the narrative around climate change is very doom and gloom. It’s very pessimistic. It feels almost like we’re accepting that we’ve been defeated. opposite. It’s so the opposite. We have every opportunity and potential here to turn things around and change things. It is not yet too late. So we wanted to really bring everyone together and imagine these ideas together and then see where that leads us.
\n\n\n\n[00:11:18] Nathan Wrigley: Thank you. That’s really helpful. You used the word sustainable a dozen times or more in, in that, last little section, and it occurs to me that there’s probably quite a few people listening who have some sort of conception of what we mean by sustainability, but I’m pretty sure that everybody’s conception of it will be slightly different to everybody else’s.
\n\n\n\nWhat exactly are you meaning when you say sustainability in WordPress or sustainability surrounding WordPress? What are the areas that you are touching on? What are the points of concern that we need to have drawn to our attention?
\n\n\n\n[00:11:54] Hannah Smith: Yeah, that’s a great question. You are absolutely right that most people will have slightly differing ideas of sustainability. Some people may even have a very narrow view of sustainability, which might be something called decarbonization. Which really relates around carbon emissions. But, Perhaps let me give a really sort of wide view of what sustainability is outside of the realms of tech or WordPress, and then we can kind of narrow in a bit and talk about how that relates then to tech or digital specifically, or WordPress specifically.
\n\n\n\nSo if we talk about sustainability or the word sustain, it means that we’re able to keep doing things into the long term. There’s this quote that’s often used. It’s about meeting the needs of the present without compromising the needs, or the ability of the future generations to meet their needs. So at it’s most basic level, sustainability can mean that. To get a bit more specific about it, I draw on something called the donor economics framework.
\n\n\n\nIf anybody here is interested in a really holistic way of thinking about sustainability, that’s a bit more in depth, I really recommend this as a resource to have a look at. Very accessible. Don’t let the fact that it’s about economics or economics turn you away, make you think it’s not for you. It is for everybody. And the way that donor economics talks about sustainability, I really love this is, it talks about sustainability as having humanity at the center of the story.
\n\n\n\nSo sustainability is much more than us thinking about the environmental ecosystems. It’s about thinking about how humanity sits within the environment. So if you can imagine a simple donut shape with a hole in the middle. Essentially what you get there is two circles, one smaller one inside, a bigger one. That smaller circle, we might often think of something that they term as the social foundation. And the social foundation is a set of 12 things that, when you consider them all in relation to one another, define the things that makes us human, and defines the things that just allow us to survive as humans, but allows us to really thrive as humans.
\n\n\n\nSo it’s more than just thinking about food, water, shelter, clothing. It’s also thinking about those emotional needs that we have as well around peace and justice. Around meaningful connections with other people around access to education and opportunities. So I love to think about our social foundation as the center of the story of sustainability. Because humans are a part of this planet. And it is a very dangerous mindset, or a very dangerous kind of thing to get into, to think that the only way that we become more sustainable is by not being here. And that’s really not a good story to tell, and it’s not the right story to tell. We are part of the planet, and we can live within the boundaries of what the planet can provide for us.
\n\n\n\nAnd that moves me onto the second circle, this outer circle. And donor economics talks about that as our ecological boundaries or our ecological ceiling. And that’s basically accepting that the planet has a finite amount of resources. There’s only so much wind that blows. There’s only so many raw materials in the ground. There’s only so much accessible water, drinkable water. There’s only so much land.
\n\n\n\nIt helps us understand that we have these boundaries in place. We have these limitations. So when we talk about sustainability, or when I’m talking personally talking about sustainability, I’m thinking about those concepts. I’m thinking about humanity being at the center of the planet. Being at the center of our concerns, but I’m also thinking that humanity has to live within these constraints that the world places upon us.
\n\n\n\nAnd in donor economics, if you have that donut shaped circle, if I’m hoping everyone listening can picture it or maybe you’ve looked it up online. If you’ve got this kind of circle, what you have is, the way the donor economics talks about it is we talk about sustainability as being this sweet spot in the middle where we are meeting everybody’s needs to thrive. But we are doing that within the boundaries of the planet. And that it is absolutely possible that we can have nice things and that we can be happy, healthy, joyful humans, but that we can live within the means of our planet.
\n\n\n\nSo for me, sustainability is that broad concept. And I’m just going to stop there, Nathan, because I know we haven’t actually talked about this before and I’m curious to know, how that resonates with you, as a definition of sustainability or as a way of thinking about it.
\n\n\n\n[00:17:05] Nathan Wrigley: Yeah, I fully understand where you are coming from. I guess the piece that I’m confronted with is that, I always think of, how to describe this. I very often think of conservation and I think about it in terms of we’ve got to do less things. We’ve got to drive the car less. We’ve got to consume less electricity, we’ve got to get on planes less. We’ve got to produce less.
\n\n\n\nAnd so the environmental debate always, for me at least anyway, comes back to reducing what we’re doing and kind of admitting to ourselves that the aspirations that we seem to have as a species, to rampantly consume everything and believe that we are fully in charge of everything on the planet.
\n\n\n\nIt feels as if we need to put the breaks on and actually, rather than that, we need to go in reverse. We need to, like I said, produce less things, consume less things. It sounds as if you’ve got a slightly different philosophy there, which is we’ve just got to figure out how we can carry on the way we are. But with cleverer solutions so that the things that we create, the plane journeys that we go on, the cars that we drive. All of that’s still possible, but we need to figure out how the impact of that would be lessened.
\n\n\n\n[00:18:28] Hannah Smith: Almost, yeah. That’s almost what I’m saying, but not quite. If we think about what we’re driving our cars for. What we are flying for. What are we doing these things for? It might be that the mechanism by which we create connection with one another or that we get from A to B, or that we see our family and friends, or that we have meaningful relationships with people.
\n\n\n\nIt might be that those things are done differently. And yeah, so it might mean that we reduce car use. We reduce airplane flights. But that doesn’t mean we don’t replace it with other things. Technology is amazing. I mean, look at, look at the internet. It’s absolutely incredible what digital technology enables us to do.
\n\n\n\nSo I think the story of sustainability, it’s very, very important to not get drawn into this narrative that we’ve all got to live like cave people, which is so often what people think being sustainable means. It means giving up all the things that bring us joy and bring us meaning in life.
\n\n\n\nAnd actually, I don’t buy that at all. I think that that is the wrong way to look at sustainability. I actually think what living in a truly sustainable way means is reducing the things that don’t give us those joyful things. Don’t provide meaningful connection in our life, and replacing them with the things that do. And do you know what? What’s amazing is that the things that genuinely, meaningfully do improve our lives, are generally sustainable, at the same time. Like riding a bike, walking, exercising, spending less time on social media, perhaps doing more time crafting or reading a book. Those things do all actually add to our lives, add to our happiness, add to our, you know, meaning and purpose.
\n\n\n\nSo I think it’s a really important starting point just to say to the WordPress community, hey, look, being sustainable doesn’t mean we’re going to lose all these things that we love. In fact, we are going to lose the things that don’t service and replace them with better, better, more meaningful things.
\n\n\n\n[00:20:39] Nathan Wrigley: Yeah. One of the things that I find tricky is I don’t really equate my use of the internet with the environmental consequences that there are from my use of the internet. Before we hit record, I was talking to you, I described how the technology that I’m using, so I’ve got a computer in front of me, I have a mobile phone. Unless I actually apply thought, my default in a way, is that they are completely benign and harmless. Typically, if I’m using my mobile phone say, there’s not really any part of me which is consciously thinking, okay, for every minute that I spend on this phone, there’s a consequence to this. There’s an environmental impact. I’m consuming electricity. That phone needed to be charged, and the same would go for any device, any piece of technology, any website that I visit.
\n\n\n\nJust not bridging that gap. Whereas other things, so for example, the driving of the car. I’m acutely aware of the consequences of that because there’s things actually coming out of the rear of that car through the exhaust system that I can detect. I can feel the harm from that.
\n\n\n\nYou know? There’s no way that if you told me to go and stand behind a car for 10 minutes and breathe in deeply. There’s no way that that’s going to be something that I wish to do. I can draw a, a line between the stuff that’s coming out the exhaust, and my health and lungs, I can completely understand that. Whereas the phone, like I said, is completely benign. I could do that for hours, and so, I do think it’s an interesting thing.
\n\n\n\nI wonder if you sense that generally speaking. When you have these discussions and you are trying to encourage people to equate internet use, technology use, whatever it may be, with the consequences of that, I’m wondering if people are generally, they’re open to it, they understand it, they draw that line themselves immediately.
\n\n\n\nOr is there a bit of, what, hang on a minute. I’ve, I’m going to have to apply some thought to this. What do you mean? How can my, how can my computer possibly be doing any harm?
\n\n\n\n[00:22:53] Hannah Smith: oh yeah, it’s such a good point. I mean, I can speak from my own experience as someone that has always been really interested in the environment, and really conscious of sustainability, environmentalism. And it wasn’t until I went to WordCamp Europe, when it was in Berlin actually, and Jack Lenox was giving a talk and Jack Lenox’s talk was, are website’s killing the planet? Something along those lines.
\n\n\n\nI had this like total mad aha moment where I was like, oh my God, right? Digital tech runs on electricity. Has to be built. All that stuff’s got to come from somewhere. So of course it has an impact. But it wasn’t until I heard Jack’s talk, and also around the same sort of time, I heard Whole Grain Digital talking as well, I put two and two together.
\n\n\n\nSo it’s funny, but once, as soon as someone told me, oh yeah, you are using electricity to run this stuff. And of course electricity is mostly coming from the burning of fossil fuels, and all this stuff has to be manufactured. So all the lithium and cobalt, gold and silver and all the stuff that’s in your phone all has to come from somewhere. And that’s really energy intensive and damaging to create, or extract.
\n\n\n\nAs soon as I was given that little push in the right direction, suddenly this whole cascade of implications unfolded in front of me, and I was like, oh, well, yeah obviously, now I see it. But I, like many people, I think just need to be given that little nudge. Really helps to hear someone say that explicitly. Hey, did you know that between, see if I can get the numbers right. 1.9 and 3.3% of the world’s global greenhouse gas emissions arise from our use of digital tech.
\n\n\n\nDid you know that that’s more than shipping and more than aviation? Did you know that that actually means that the internet becomes the world’s seventh biggest polluter is a country? When you start to hear those things, yeah, it dawns on you. And that’s certainly how I came into this space, or certainly how I kind of realized this for the first time.
\n\n\n\nMaybe many people listening to what I’ve just said, the light bulbs have just flicked on as well and gone, oh right, yeah, of course, good point. It’s unseen, isn’t it, this pollution? To your point earlier, it’s all been abstracted away from us, so that we have clean, convenient lives. As you rightly say, you know, our phones are really sleek. Our laptops are really sleek. And that’s part of the service I suppose, that we’re being provided. We’re being given this convenience. We’re being given beautiful, well designed things. But that impact, unfortunately, is still very real at the moment. Maybe in time to come, we’ll get to a place where it’s not.
\n\n\n\nWe’ll have some new technologies that perhaps use the regenerative techniques, where we’re not extracting materials from the ground. Maybe we can start to grow them or find other ways to create them. But right now, yeah, that impact is real. Whoever came up with the term cloud really like clever, but from a sustainability angle, not helpful.
\n\n\n\n[00:26:15] Nathan Wrigley: It’s about the most benign thing imaginable, isn’t it? It’s fluffy and, welcoming and, you know, they’re associated with the sun and all of that. Yeah, that’s interesting.
\n\n\n\n[00:26:24] Hannah Smith: Yeah, and it’s just not true. Like actually it’s like a big diesel plume. To your point, actually the reality is 62% of the world’s energy, electricity comes from fossil fuel sources. And we can think about it as the internet is actually the world’s largest coal fired machine. When you start to have those pictures in your head, it does change your relationship to what you’re doing and what you have in front of you a bit I think.
\n\n\n\n[00:26:51] Nathan Wrigley: And I guess that’s really the purpose of what it is that you are doing in the article that you wrote. Is you are, you’re keenly aware of this. It’s obviously something which is meaningful to you on a personal level. And you are, you’re really scouting out for ideas and suggestions and, for the community to gather around, and come up with what we can do.
\n\n\n\nSo, let’s lay out a few things in terms of WordPress. These are the things which just come into my mind as we’re sitting here talking to one another. I confess that there isn’t a great deal of backstory here. I’m just going to generate things as they come up into my mind.
\n\n\n\nSo the first thing is that our website’s dependent upon what is being presented to the end user. So, you know, if it’s a, if it’s a website, which is rich in large images. If it’s a website which is rich in video. If it’s a website which has huge amounts of JavaScript and CSS. We are pushing more bits over the wire. And so maybe there’s a piece there. Can we cut down the amount that WordPress needs to do, and needs to deliver?Would that have an impact?
\n\n\n\n[00:28:00] Hannah Smith: Definitely.
\n\n\n\n[00:28:02] Nathan Wrigley: Yeah. And then another thing which comes into my head is, at the end of the day when I finish with my computer, the last thing I do is I switch it off. I turn it off, and then when I need it again, I’ll switch it on and I’ll, whenever I’ve finished I turn it off again, so it’s on, off, on, off.
\n\n\n\nWhat I’m trying to say is that it’s off more than It’s on. Significantly more. But our website hosting, let’s just call it that, wherever that might be, whatever system you are using. We need that to be on all the time because our websites need to be available all the time. That’s one of the points is something which is, you know, you don’t have to go to a website and be visited by a page which says, one moment, we’re just going to switch the computer on, and come back in a moment and everything will be ready to go.
\n\n\n\nNo, you want it to be ready immediately. And in fact, we’re being told all the time that the faster our webpage is being served up, the better it’s going to do in search engine rankings, which is almost like a holy grail. So everything needs to be quicker and everything needs to be more available.
\n\n\n\nSo there’s just a couple of pieces there really, which came to my head, the first one being that can we reduce the amount that WordPress has to serve up, and will that have a positive effect? And obviously that very much feels like a seesaw. You could argue that from both sides. But also the machines that our websites are running on, there’s probably quite a lot of conversations that we could have around there. The kind of things that hosting companies are doing to source the power and so on and so forth.
\n\n\n\n[00:29:30] Hannah Smith: Yeah, I mean, it’s brilliant, isn’t it? You start to think about these things and you’ve hit upon two real, really key actionable things that we can look at within WordPress. So we’re talking at the moment about electricity and energy use, and I’m just going to sort put this into context and say, hey, don’t forget that electricity and energy use is just one aspect of sustainability. There is a little bit more to it than that.
\n\n\n\nBut I do think that when you are brand new to thinking about the impact of digital tech on sustainability, this is an absolutely awesome starting point. It’s very tangible and there’s quite a bit of research and tooling out there to help you. So I just want to kind of caveat and say, let’s deep dive into that for a little bit, awesome. But bear in mind, there’s more to think about.
\n\n\n\nThere is a very direct relationship between the amount of data that you send and the amount of CO2 emissions that that creates. So the more data to use your words, the more data, the more stuff you’re sending down the wire, the more pollution or the more energy that you’re using.
\n\n\n\nAnd there’s a simple way to calculate this. For anyone that wants to get into this. If you know how much data you are sending, we can estimate how much electricity that is going to use to send that data from A to B. Whole load of assumptions that you’ll have to make in order to make that estimation.
\n\n\n\nBut there’s some models out there that you can use. You can have a look at the sustainable web design website. So if you know how much data you’ve got, you can figure out an estimation of how much electricity that would use to send from A to B. And then we can use something called carbon intensity data.
\n\n\n\nAnd carbon intensity data allows us to understand how much CO2 emissions are created per unit of energy, or per unit of electricity that is created. So I mentioned to you that 62% of the worlds electricity is generated by fossil fuels. In different countries, and in different regions that will change. So I think Norway, for example, is 100% renewable energy.
\n\n\n\nSo depending on where you are in the world, you’ll have different carbon intensities to consider. But yeah, so essentially it can come down, a really good starting point is to think about performance and optimization, and think about how can I reduce the waste around this. There are dozens of reasons why we should be thinking about performance anyway.
\n\n\n\nThis is not a new ask of developers, or ask of technical people to think about performance. We have reasons around accessibility. We have reasons around cost. We also have reasons around SEO as well. The more performant and optimize something is, the better your SEO. And we also have things to think about in terms of people’s enjoyment of using said service, or said website.
\n\n\n\nAnd we can add another one, another cracking good reason to think about this optimization and performance, and that is also the sustainability angle. So, I mean, really this stuff is just stacking up and stacking up to be like a no brainer. If you want to be a sustainable web developer, your first job is to get good at performance and optimization.
\n\n\n\n[00:32:50] Nathan Wrigley: It’s interesting, the whole performance thing, while you were talking about that, I was thinking about the fact that performance really can go in two directions. The performance could be gained by cutting out waste, but it can also be gained by using more resources.
\n\n\n\n[00:33:05] Hannah Smith: Ha ha, yes, good shout.
\n\n\n\n[00:33:07] Nathan Wrigley: It is possible to simply say to yourself, I shall purchase more expensive hosting, which has got more CPUs and so on and so forth. And in that way, I cut out the need for me to make my website leaner, if you know what I mean. So, just to be clear, when you talk about performance, you really are talking about getting rid of the waste, considering whether that image needs to be that big or could it be smaller? Do I need to put that video on there? It’s more trimming things down as opposed to spending more money on a faster machine for example.
\n\n\n\n[00:33:39] Hannah Smith: Interesting point. I’m really glad we’re having this conversation. Yes and no I would answer that question. 100% the yes part is definitely around the waste. Is around just not sending stuff we don’t need. Not having analytics collecting that we don’t need. Not generating data that we don’t need.
\n\n\n\nThe resources part is a really interesting one, because there’s a piece around maybe using our resources more wisely. So there can be arguments for perhaps having better hosting. Because if that better hosting, say you are serving a website across, you’ve got users all across the world visiting your website. Actually having a better hosting service that makes really good use of CDNs, content delivery networks, actually can have an impact on sustainability.
\n\n\n\nBecause if you are serving your data closer to the person that actually wants to use that data, you can save quite a bit of energy, electricity, because you’re not sending it from one side of the world to the other. And there is an electricity cost to doing that. Again, it’s not seen by us, but it’s real. It is there.
\n\n\n\nSo the service side, the hosting side of things. Something very specific you can do there is look for hosting companies that are using renewable energy, using renewable energy sources to power themselves. And I’m going to plug the Green Web Foundation where I’m working now.
\n\n\n\nWe have a really awesome data set, which we’ve been collecting for 10 years or so on hosting companies that are powered by renewables. That’s a very specific action you can take. But yeah, to your point that you can make something really performant by chucking loads of resources at it. Yeah, that’s not what we are talking about here when we are talking about sustainability. We are talking about speeding things up through the use of wise resources instead.
\n\n\n\n[00:35:36] Nathan Wrigley: I know that time is pressing for you, so we’ll wrap up fairly shortly, but I just want to, just want to offer a few thoughts as well, and, the piece that I mentioned towards the beginning of the podcast where I said that, it’s very difficult I think for me, and I’m sure a lot of other people as well, to draw the line between the website and the impact on the environment, and I’m wondering if it might be that we need to be alerted to the consequences of our use of the internet.
\n\n\n\nSo just throwing out some ideas, which probably, may very well have no legs, but just some thoughts really. Would be interesting, for example, if in the WordPress backend we could see something which gave us a measure of what it was that our website was doing. So if it gave us a direct link to okay, every, every time somebody comes to this particular page, this is what you are sending to them, and that has this kind of consequence.
\n\n\n\nNow, obviously, that’s much more complicated, as you’ve described, because it depends on the hosting that you’re using. It depends whether they’re close or far away. But just some sort of broad metrics so that we could understand what the consequence of the thing that we’re building is. So I don’t even know what that would look like. Maybe it would be some sort of graph or chart or just raw number that would give us some indication.
\n\n\n\nAnd then also more broadly, just browsing the internet. If we could have this kind of information coming back to us. So, I don’t know, I’m thinking of like a browser extension or something like that, which would measure what it was that I was doing when I went around the internet, and then give me some kind of feedback for, okay, this week you consumed this much in terms of electricity or carbon that was produced as a result of your browsing the internet.
\n\n\n\nLast week it was this, the week before it was this, so you know you’re going in the right direction. Just those kind of things. I’m just wondering if there are things afoot. Maybe tools that exist already, or projects that you know about that can help us to understand the consequences of what we are doing.
\n\n\n\n[00:37:39] Hannah Smith: Definitely, and do you know what Nathan? These ideas absolutely have legs and these are exactly the kind of ideas that we are inviting people to come and share on our post with us. All of these suggestions, all of these ideas are relevant and very, very actionable, and have already been actioned in certain ways.
\n\n\n\nSo to your point about CO2, understanding CO2 emissions of websites, so there’s a fantastic tool called Website Carbon Calculator. I think the URL is websitecarbon.com. So you can go along to that and put any URL in, and immediately get a sense of how polluting that page is. And that is such an awesome tool to use with bosses or clients, who perhaps aren’t so interested in the nitty gritty technical detail, but want a number, or a statistic or a sense of how good or bad they’re doing.
\n\n\n\nAnd the Website Carbon Calculator has a little bit of JavaScript code that you can embed in your site that will give you a reading of each page of how much CO2 that that page is polluting. Now I believe that there is a plugin for that as well, and I don’t know if that would give you the information in the back end of WordPress, but Website Carbon Calculator’s being developed by Whole Grain Digital. If you’re interested in WordPress sustainability, I mean, they’re really thought leaders in this space, so definitely worth checking them out.
\n\n\n\nI had some conversations with Jenny Wong many years ago, and, and those of you that are in the UK WordPress community, you’ll probably know Jenny. I think most people do. And if you’re listening, Jenny, hello. Jenny and I exchanged some ideas around using Site Health, and actually building some of these ideas into Site Health. That section of the WordPress backend. It might be difficult to get that as a core contribution to begin with, but we could certainly look at making some plugins.
\n\n\n\nThere’s loads and loads of data out there that we could use to surface these emissions. And then to your point about browsers, yes. Actually at the Green Web Foundation, we’ve been talking quite a lot with the Firefox people, made by Mozilla. And there are some open issues in GitHub at the moment around integrating carbon emission readings and estimations into the Firefox browser.
\n\n\n\nI don’t know off the top of my head whether the intention would be to track it in the way that you’ve talked, but you know how if you’re a developer, you, you might be familiar with the web dev tooling that we have, say within Firefox or Chrome. The idea is to create a separate tab in the performance section, to start to give you a reading within the browser as well.
\n\n\n\nSo there are all these things happening, and this is where I really want to invite people to come and join us. Please let us share these initiatives that are happening. If you’ve got some time and capacity and you’ve got some energy, and you want to take action, we desperately want people to come and join in, and make these things happen. So yeah, please share these ideas that you have.
\n\n\n\n[00:40:49] Nathan Wrigley: Thank you. Yeah, that’s really, really interesting. Just before we wrap it up finally, it just occurs to me that we’re always looking for ways to, to have a competitive edge. If you are a freelancer or an agency, you’re always trying to figure out ways that you are different from your competition. And it just strikes me that maybe this, maybe this could be one of those ways. You are one of the developers who actually gives this some thought. And it may very well be that there are a whole load of clients out there for whom this would be a very important metric when making hiring decisions, so.
\n\n\n\n[00:41:24] Hannah Smith: Such a good point. As a freelance WordPress developer, uh, you know, people were, were starting to know me as someone who knew about digital sustainability and who could build sustainable WordPress sites, you know, efficient WordPress sites. And the demand was mad. I couldn’t keep up with it. I was constantly being like, oh, I need more people to recommend this work to. So yeah, I think this is a really strong selling point, and it makes you feel good as well, to know that you’re doing the best you can, you’re doing the right things.
\n\n\n\n[00:41:55] Nathan Wrigley: Hannah, just as a very final thing. If people have been interested in this, I will obviously link to the post in the show notes. You can check those out on wptavern.com, but if they want to contact you, are you available? And if so, where should we do that? What’s the best way to reach out to you?
\n\n\n\n[00:42:12] Hannah Smith: Yeah, well, I mean, I would love to chat with anyone that’s interested in bouncing some ideas around, or is interested in finding out more. The best way to get hold of me is through the Green Web Foundation, so hannah@thegreenwebfoundation.org, or if you’re in make WordPress you can also drop me a line. You’ll see me lurking around in the sustainability channel quite a lot in the make WordPress Slack space. You can drop me a line there too.
\n\n\n\n[00:42:38] Nathan Wrigley: Hannah Smith, thank you very much for joining us on the podcast.
\n\n\n\n[00:42:41] Hannah Smith: Oh, thank you Nathan. Thank you for making time for this today. I really appreciate it.
\nOn the podcast today, we have Hannah Smith.
\n\n\n\nHannah is the Operations and Training Manager for the Green Web Foundation and founder of the Let’s Green The Web campaign. She’s also co-founder of Green Tech South West.
\n\n\n\nHer background is in Computer Science. She previously worked as a freelance WordPress developer, and also for the Environment Agency, where she managed large business change projects.
\n\n\n\nIt’s pretty easy to forget that the device that you’re reading this post on is consuming power. We plug things in or charge them up, and they just work. They are sleek and sterile. No pollution comes out of the device directly. In fact, I’d go as far as to say that many of us never make the connection between our use of technology and the impact this has on the environment.
\n\n\n\nEnter Hannah Smith. She’s been thinking about this for years and is on the podcast today to highlight the issue, and hopefully get your ideas about what users of WordPress can do to make sure that the websites we create are having the smallest impact possible.
\n\n\n\nHer approach is not that we need to cease and desist using our technology. Rather, it’s about coming up with new and innovative ways that we can reduce the impact that we have.
\n\n\n\nAs creators of websites, there are a whole raft of options available to us. Reducing the size of our images. Inspecting the HTML to remove bloat. Choosing hosting options that source renewable energy.
\n\n\n\nWith this in mind, Hannah and others have been working on a sustainability related blog post which has been published on the Make WordPress site this week.
\n\n\n\nThis post is intended to trigger meaningful and open discussion in the global WordPress community about the topic of sustainability. She really wants to encourage others to weigh into this public conversation with their own thoughts, so we can build on what is already happening to make WordPress more sustainable.
\n\n\n\nIt’s a fascinating and thought-provoking topic.
\n\n\n\nThe Green Web Foundation website
\n\n\n\n\n\n\n\n\n\n\n\nSustainable Web Design website
\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, 23 Nov 2022 15:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;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:103:"WPTavern: BuddyPress 11.0.0 to Limit JavaScript and CSS Asset Loading to Community Pages Using a Filter";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=139798";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:114:"https://wptavern.com/buddypress-11-0-0-to-limit-javascript-and-css-asset-loading-to-community-pages-using-a-filter";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:3241:"BuddyPress will soon be improving the way it loads its JavaScript and CSS assets so that they are only loaded on community pages. Previously, the plugin would load them indiscriminately on every page.
\n\n\n\nBuddyPress lead developer Mathieu Viet said he’s not sure there is a specific reason explaining why this was kept in place. Before the plugin introduced the BP Theme Compat API in version 1.7, it was necessary to use a BuddyPress compatible theme like the one bundled by default (BP Default).
\n\n\n\n“I think we kept the way this theme was loading these assets into the first Template Pack (BP Legacy) we added to BuddyPress,” Viet said.
\n\n\n\nUsers have often requested BuddyPress only load its assets on community pages in hopes of further optimizing their websites. For example, in 2020, a user on the BuddyDev forums requested custom code to accomplish this. Experts recommended against doing it
\n\n\n\n“It is not going to help you much and will cause a lot of issues in future,” BuddyPress contributor Brajesh Singh said. “There are dependent plugins which may start throwing JavaScript errors and breaking some of your site functionality. It is not worth the effort.”
\n\n\n\nSingh recommended the user enable browser caching to avoid loading the assets multiple times and stick to best practices for enabling gzip compression and other optimization measure. He also recommended adding a plugin that would conditionally prevent loading BuddyPress on certain pages.
\n\n\n\nComing in version 11.0.0, BuddyPress core will progressively move towards loading only the assets it needs in community areas. This update will still load JS and CSS everywhere but will offer a filter that users can add to their bp-custom.php files in order to keep BP assets on community pages only:
\n\n\n\n\n\n\n\n\nadd_filter( ‘bp_enqueue_assets_in_bp_pages_only’, ‘__return_true’ );
\n
“If using the above filter, you notice something is going wrong with your website due to the use of a specific BP plugin or theme, report it here and we’ll then have another development cycle to fix things before we completely restrict these assets to BuddyPress generated pages in a second step in version 12.0.0,” Viet said.
\n\n\n\nVersion 11.0.0 is expected to be released on December 14, 2022. Early adopters and BuddyPress site owners who have always wished for the plugin to behave this way can take advantage of it after the next major update using the filter. The filter can also be easily removed if users are troubleshooting and having issues with plugins.
";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, 23 Nov 2022 00:28:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;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:60:"WPTavern: New Tool Checks If Google Fonts Are Hosted Locally";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=139780";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://wptavern.com/new-tool-checks-if-google-fonts-are-hosted-locally";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:3462:"Earlier this year, WordPress’ Themes Team began urging theme authors to switch to locally hosted fonts after a German court case decision, which fined a website owner for violating the GDPR by using Google-hosted webfonts. Since that ruling, German website owners have continued to receive threats of fines for not having their fonts hosted locally.
\n\n\n\nThe makers of the Fonts Plugin, a commercial product with a free version on WordPress.org, have created a tool called Google Fonts Checker that will help website owners discover where their fonts are hosted. The tool analyzes any URL entered and if the fonts are hosted by Google, it says “Google Fonts Connection Found” with a red ‘X.’ Sites that are in the clear will show a notice that a Google Fonts connection was not found:
\n\n\n\nGoogle Fonts Checker is useful for non-technical users who are not sure whether their theme or plugins are referencing fonts hosted on Google’s servers. Beyond delivering the simple connection message, the tool scans the website and returns a list of the font files used to render the page, which can be helpful in tracking down the specific extension loading these files.
\n\n\n\nMore than 200,000 people are using the Fonts Plugin to load assets from the Google Fonts Library. Although the Google Fonts Checker tool is free to use and doesn’t require any personal information or login, the free version of the Fonts Plugin doesn’t support hosting fonts locally. Users will either need to upgrade to the commercial version or use a different plugin, like Local Google Fonts or the OMGF | Host Google Fonts Locally plugin, both of which perform this for free.
\n\n\n\nThose who find a Google Fonts connection using the tool may also consider switching to Bunny Fonts, an open-source, privacy-first web font platform with no tracking or logging that is fully GDPR compliant. It can act as a drop-in replacement to Google Fonts. The Replace Google Fonts with Bunny Fonts plugin makes it easy to switch.
\n\n\n\nSome of WordPress’ older default themes are still loading fonts from Google. A ticket for bundling the fonts with the legacy default themes had patches and was on track to be included in WordPress 6.1, but ended up getting punted to a future release after it was determined the approach needed more work. In the meantime, those who are concerned about using Google Fonts in older default themes can use a plugin to host them locally.
";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, 22 Nov 2022 21:49:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:20;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:59:"WordPress.org blog: The Month in WordPress – October 2022";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=13988";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/2022/11/the-month-in-wordpress-october-2022/";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:12235:"With the end of the year fast approaching, the WordPress project has not slowed down. Read on to learn more about the latest major release, WordPress 6.1, and the State of the Word 2022 live event, among other exciting news. It’s time to catch up on all things WordPress!
\n\n\n\nThe third and last major release of 2022, WordPress 6.1 “Misha,” shipped on November 1, 2022. Named after jazz pianist Mikhail “Misha” Alperin, this release comes packed with many improvements that refine the site-building experience introduced earlier this year in WordPress 5.9 and 6.0, as well as accessibility and performance upgrades.
\n\n\n\nWordPress 6.1 is also bundled with a new default block theme, Twenty Twenty-Three (TT3), that features 10 style variations designed by WordPress community members. These intentionally unique designs ensure that you can change the visual details of your site with ease—and within a single theme.
\n\n\n\n\n\n\n\nLearn more about what’s in 6.1:
\n\n\n\n\n\n\n\nFollowing WordPress 6.1 “Misha”, a 6.1.1 maintenance release landed on November 15, 2022. This minor release includes about 50 bug fixes.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\nState of the Word 2022, the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg, will be held on December 15, 2022. The event will take place in person in New York City and live-streamed via various WordPress.org social media platforms.
\n\n\n\nYou can also host or join a State of the Word watch party to enjoy the event with your WordPress friends.
\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Two new versions of Gutenberg have shipped in the last month:
\n\n\n\n\n\n\n\n\n\n\n\n\nExplore some of the latest enhancements to the writing experience in this Core Editor Improvement post.
\n
\n\n\n\n\n\n\n\n\nEnjoy a spooky Halloween Mad Libs story completed by community contributors in Episode 42 of WP Briefing.
\n
\n\n\n\n\n\n\n\n\nWere you involved in WordPress 6.1? Share your thoughts on the release process by December 15, 2022.
\n
WordCamp São Paulo, Brazil on November 26, 2022 WordCamp Kolkata, West Bengal, India on December 17-18, 2022\n\n\n\n\n\n\n\n\nBoost your speaking confidence in WordPress events. Register for the How to Own Your Expertise & Start Speaking at WordPress Events online workshop happening December 7, 2022.
\n
Have a story that 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 edition of The Month in WordPress: @rmartinezduque, @webcommsat, @santanainniss, @dansoschin, @eidolonnight.
";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, 22 Nov 2022 11: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:"rmartinezduque";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:21;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:65:"Do The Woo Community: Building a Cloud-Based SaaS versus Hosted ";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=73737";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:62:"https://dothewoo.io/building-a-cloud-based-saas-versus-hosted/";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:377:"Learn why NitroPack made the decision to go cloud-based vs. self hosted with the SasS product.
\n>> The post Building a Cloud-Based SaaS versus Hosted appeared first on Do the Woo - a WooCommerce Builder 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:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Nov 2022 10:18:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:51:"WPTavern: WordPress Launches Developer Blog In Beta";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=139729";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:62:"https://wptavern.com/wordpress-launches-developer-blog-in-beta";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:3318:"WordPress.org will soon be launching a blog for developers. The blog went into beta at the end of last week and resides on a subdomain of the main site. It is sporting a design similar to WordPress’ general News blog.
\n\n\n\nOne of the big picture goals that WordPress’ Executive Director Josepha Haden-Chomphosy identified for 2022 was the creation of a developer-focused communications site. This new blog is the culmination of an effort that began earlier this year.
\n\n\n\n“Staying on top of the new features coming to the WordPress open-source project is one of the main barriers expressed by developers,” contributor Birgit Pauli-Haack said in the original proposal.
\n\n\n\n“The Make Core blog has a heavy emphasis on meeting notes for the various core teams, rather than highlighting new features. This makes it difficult for developers who are not contributors or who just occasionally contribute to find the relevant information among the team-related posts.”
\n\n\n\nContent on the new developer blog will be focused on updates applicable to theme and plugin creators, developers who work at agencies, Gutenberg API updates, advanced programming concepts, PHP gems, and developer case studies.
\n\n\n\nThere are already three posts published, which offer a hint at what kind of content WordPress developers can expect on the blog:
\n\n\n\nThe blog’s editorial process is being entirely managed on GitHub from pitches to publication. Anyone who wants to contribute can post to the Ideas board for discussion. Approved ideas become blessed tasks and drafts and go through two reviews. People can contribute by posting ideas, writing posts, or joining the editorial team that reviews posts.
\n\n\n\nNow that the blog is in beta, contributors are looking for feedback from WordPress’ developer community. Leave comments on the beta announcement or join the next meeting in the core-dev-blog WP Slack channel on December 1, at 13:00 UTC. Subscribe to the RSS feed to never miss a post from WordPress’ new developer blog.
";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, 22 Nov 2022 03:10: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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;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:87:"WPTavern: State of the Word 2022 Will Be Livestreamed from New York City on December 15";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=139734";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:98:"https://wptavern.com/state-of-the-word-2022-will-be-livestreamed-from-new-york-city-on-december-15";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:2961:"Matt Mullenweg’s annual State of the Word (SOTW) address will be delivered in New York City this year before a live audience, on December 15. The event format is similar to last year where a small group of invited guests will join in person.
\n\n\n\nTraditionally, the State of the Word has been given at WordCamp US, capping off the event with an inspiring review of WordPress’ progress and a lively Q&A session. Starting in 2020, due to the pandemic, the SOTW transitioned to a separate, smaller event that can be broadcast to all who cannot attend. Organizers are planning to livestream this year’s event across WordPress.org’s social media platforms.
\n\n\n\nUnlike last year, where prominent members of the community were invited to attend, organizers have created a form where anyone can request an invitation to attend. Seats are available to the public on a first-come, first-served basis. The form states that masks will not be required at the event, a policy that is as controversial today as it was last year, and makes it impossible for medically vulnerable people to attend:
\n\n\n\n\n\n\n\n\n“While at the event, masks are not mandatory but encouraged, as is using hand sanitizer and social distancing.”
\n
Since the majority of people will be watching via live stream, the Q&A portion of the event will be handled via email for virtual participants. Anyone can ask a question in advance by emailing ask-matt@wordcamp.org or may ask during the event in the live stream chat on YouTube. WordPress Executive Director Josepha Haden-Chomphosy said there may be a follow-up post published with answers to questions not covered at the event.
\n\n\n\nThe live stream will be embedded in the announcement post and will also air on WordPress’ YouTube channel on December 15, 2022, at 1–2:30 P.M. EST (18–19:30 UTC). Those who are hosting watch parties are encouraged to email support@wordcamp.org for additional resources from the Community Team.
";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, 21 Nov 2022 23:40:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:24;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:42:"WordPress.org blog: State of the Word 2022";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=13971";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/news/2022/11/state-of-the-word-2022/";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:8590:"\n\n\n\nHello, WordPress!
\n\n\n\nMark your calendars; it’s almost time for State of the Word 2022!
\n\n\n\nState of the Word is the annual keynote address delivered by the WordPress project’s co-founder, Matt Mullenweg. Every year, the event shares reflections on the project’s progress and the future of open source. Expect this and more in this year’s edition.
\n\n\n\nThis year’s event will take place in person in New York City and live-streamed via various WordPress.org social media platforms.
\n\n\n\nJoin Matt as he provides a retrospective of 2022, the latest WordPress releases, Site Editor advancements, and a return to in-person events around the globe, among other topics.
\n\n\n\nWhat: State of the Word 2022
\n\n\n\nWhen: December 15, 2022, 1–2:30 P.M. EST (18–19:30 UTC)
\n\n\n\nHow: If you’re watching from the comfort of your home or local watch party, the live stream will be embedded in this post and available through the WordPress YouTube channel.
\n\n\n\nWould you like to join the in-person audience? Request a seat by completing this survey.
\n\n\n\nState of the Word will include a Q&A session. If you want to participate, you can either send your question ahead of time to ask-matt@wordcamp.org or ask during the event in the live stream chat on YouTube.
\n\n\n\nGiven the volume of questions that are usually submitted, please note that it may not be possible to answer all of them in the live Q&A. A follow-up post will be published after the State of the Word to answer those not covered at the event.
\n\n\n\nFirst time attending State of the Word? Check out previous years’ recordings on WordPress.tv to get a sense of the event.
\n\n\n\nSee you in person or online on December 15!
\n\n\n\nCan’t make it to New York? No problem, organize or join a watch party in your community in person or online. Like last year, the Community team has resources available to help! Check out this handbook page, which includes event templates, information on requesting a Zoom account, and how to get some swag.
\n\n\n\nGather together to look back on how WordPress has grown in 2022 and what is ahead for 2023. Stay up-to-date as a group on the latest happenings in the WordPress world and collaborate together on any questions you might have for Matt!
\n\n\n\nBelow you can find a list of State of the Word watch parties that will be updated regularly as the event approaches. If you don’t see a watch party in your region, check this page on Meetup.com to see if your local WordPress group is organizing one.
\n\n\n\n Seattle WordPress Meetup – WordPress Developer Meetup: State of the Word/General Discussion Port-au-Prince WordPress Meetup Group – State of the Word Watch Party (Online) WordPress Meetups Genève (Geneva) – State of the Word “Watch Party” et plus/and more (FR/EN) WordPress WordPress Ancona Meetup – State of the Word Watch Party + Auguri di Natale + Proposte 2023 WordPress Sofia Meetup – “State of the Word 2022” watch party! Granada WordPress Meetup – ¡Veamos el State of the Word 2022! Kochi WordPress Meetup – State of the Word Watch Party (In-person) WordPress Meetup Tegal – Nonton bareng “State of the Word 2022” Tokyo WordPress Meetup – State of the Word から来年の WordPress を考えよう！+ 忘年会 WPGR – Grand Rapids WordPress Meetup – State of the Word Watch Party (In-person)If you are planning a watch party for State of the Word and have questions, please email support@wordcamp.org. A member of the WordPress community team will assist you in the best way possible.
";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, 21 Nov 2022 17:14:43 +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:7:"Josepha";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:25;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:96:"Gutenberg Times: Block Art, MindMap block, Slotfills, Patterns and more – Weekend Edition #236";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=22670";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:99:"https://gutenbergtimes.com/block-art-mindmap-block-slotfills-patterns-and-more-weekend-edition-236/";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:25645:"Howdy,
\n\n\n\nI am so excited about next week! Finally, there will be another Six-a-side Festival at the Sarasota International Cricket Club. I’ll be there Saturday and Sunday. I am excited to see all the friends again, most I haven’t seen in three years.
\n\n\n\nIf you are in the area, come on by. It’s a lot of fun, a diverse community, and you can meet cricketers from England, the Caribbean, and the West-Indies coming together to play cricket, party and play cricket again the next day and the next. It’s great fun for the whole family!
\n\n\n\nWhat are your plans for next week? I hope you have a fabulous one!
\n\n\n\n\n\nIn this edition, you’ll find a vast array of videos, blog posts and podcasts from Learn.WordPress, WordPress TV and around the community. Let’s get started!
\n\n\n\nYours, 💕
Birgit
Table of Contents
\n\n\n\n\nIf you found the Field guide of WordPress 6.1 too developer centric, yet the announcement post not detailed enough, then let Courtney Robertson, team rep of the WordPress Training team, show you What’s new in WordPress 6.1: Misha
\n\n\n\nHostinger’s Leonardus Nugraha, member of the WordPress docs team, published WordPress 6.1: What’s New in the New Major Release in collaboration with yours truly.
\n\n\n\n
\n\n\n\nAlso, part of WordPress 6.1 is a new default theme. In her post Introducing Twenty Twenty-Three, Beatriz Fialho, design lead, takes you a long for the journey exploring the new default theme and it’s community-submitted style variations.
\n\n\n\nYou’ll find more details about the features of Twenty Twenty-three in the End User documentation article
\n\n\n\nWordPress 6.1.1 was released, fixing a few bugs on the backend and frontend of the software. Core contributors and release leads JB Audras, Jeff Paul and George Mamadashvili, worked hard to get this out with two weeks of the 6.1 release. This was a really fast turn around.
\n\n\n\nIn his Design Share: Oct 24-Nov 4, Joen Asmussen lists the project the WordPress design team has been working on. The visuals representation of upcoming feature are absolutely exciting. First up are the screens of possible location for the Custom CSS feature, many of you found missing around the block themes. You can also see the design explorations for the interface to make a Group block sticky. You could use it for an ever present navigation bar or a public service announcement. Or an ongoing news ticker banner.
\n\n\n\nIf you use the latest version of the Gutenberg plugin, you might have noticed, that the the info screen with the meta information on word count, or the outline was moved into the List view as an additional tab. The design team also explored more delightful designs for this panel.
\n\n\n\nJames Koster tries to answer how to make it possible to push local block styles to global block styles. In other words, after you modified the look and feel of a single block, how can you make the styles persistent for all the blocks of that particular type on your site.
\n\n\n\n🎙️ New episode: Gutenberg Changelog #76 – The new developer blog’s public beta, Gutenberg 14.5 and 14.6, and what’s coming up in 6.2. with special guest, Ryan Welcher, and host Birgit Pauli-Haack.
\nThe WordPress meta, design, and marketing teams have been working on the redesign of the Showcase page on the main website. Joen Asmussen reports on the progress in his post A refresh of WordPress.org/Showcase. “The current work represents a starting point that will continue to be iterated upon as additional features, and content changes are explored.” he wrote. He also provides links to the Figma file and the Showcase GitHub repository.
\n\n\n\nNick Diego was the lead for last week’s Gutenberg plugin release. In his posts What’s new in Gutenberg 14.5? (9 November) he wrote: “It consolidates the list view and document information, expands margin and padding support while improving spacing visualizers, and sets the groundwork for future releases with numerous code quality improvements and bug fixes.”
\n\n\n\nSarah Gooding also reported on the latest release in Gutenberg 14.5 Introduces New “Document Overview” Panel, Improves Block Spacing Controls.
\n\n\n\nOne of the new features is a new Social Link Block for Mastodon accounts, Mastodon, is an open-source decentralized social network, that many feel comfortable as using while Twitter seems to be deteriorating fast.
\n\n\n\nGeorge Hotelling, WordPress core contributor, wrote a short tutorial on How to verify your WordPress site on Mastodon.
\n\n\n\nOn a side note, I just created the @gutenbergtimes account on the mastodon server at twit.social. If you want to follow, just search for https://twit.social/@gutenbergtimes on any mastodon server, and you can follow me there. It’s a new account so not much going on.
\n\n\n\nMy personal account is https://mastodon.social/@bph.
\n\n\n\nGutenberg 14.6 RC is already available for testing. The stable version will be release by Fabian Kägy on November 23, 2022
\n\n\n\nThien Nguyen published his Mindmap Block It’s a cool block that provides the conversion from Markdown input in the block editor to a Mind map display on the frontend. This could get fascinating when Phase 3 of the Gutenberg project progresses, as then you can use this to collaborate on mind maps, too. We’ll revisit this in two years or so. It’s not a free plugin, and it is available on Gumroad with single site or unlimited site levels.
\n\n\n\nToday’s count is 182 Themes supporting the Site editor in the WordPress Themes Directory. New themes are available by the Block Styles team, Brian Gardner, Blockify, Catch Themes, Wen Solutions, and by Wwwows.
\n\n\n\nAnother recently added theme is Loudness: A New Block Theme from Automattic It’s an artistic and opinionated theme . Sarah Gooding has the skinny for you.
\n\n\n\nRich Tabor and Courtney Portnoy discussed The creative side of blocks on WordPressTV. Rich Tabor walks the viewers through one of his block art creations. It’s quite inspiring to watch Tabor’s exploratory creative process using the block editor. I learned quite a few things about the power of the various color features: gradient, nested group blocks, and how to replace the theme’s primary and secondary colors for the whole site. You’ll also get an introduction to the Museum of Block Art, where Rich and other block artists showcase their creations.
\n\n\n\nOn the Torque Social Hour, host Doc Pop interviewed Roy Sivan and James Tryon about Block Styles Community and plugins built by the two. Gutenberg adopters of the first hour, the team aims to augment the Block editor with Block Styles to make it a professional page builder for power users. They created 160 input fields to customize a site.
\n\n\n\nThe most obvious styles enhancements are the tools to separate the page layout features by screen sizes for desktop, tablet, and mobile. It’s a bit unfortunate to give a product / membership service the same name as a WordPress feature. Plugin developers have the advantage of a shortened implementation time and run into the danger to be passed by core in the long run.
\n\n\n\nMissing Menu plugin and the newest block theme Gesso were also mentioned on the show.
\n\n\n\nDaisy Olsen wrote about Demystifying Home and Posts Templates in WordPress theme development, explains the WordPress Themes Hierarchy for both classic and block themes.
\n\n\n\nIn his post Creating Themes from a Pattern-First Mindset, Justin Tadlock helped theme developers interested in block themes to see the power of using pattern in their templates to reduce code redundancy and simplicity.
\n\n\n\nOn Tuesday next week (Nov 22) Daisy Olsen and Justin Tadlock, together with Damon Cook will hold a Hallway Hangout on Future of CSS in block themes. It will be in a casual chat about some Block Theme development-related features that are under active development. Hope to see you there 🙂
\n\n\n\nGanesh Dahal wrote about Managing CSS Styles in a WordPress Block Theme and took a deep dive into the migration from styles.css files to theme.json. “One of the major benefits of moving CSS to JSON is that JSON is a machine-readable format, which means it can be exposed in the WordPress Site Editor UI by fetching an API, thus allowing users to modify default values and customize a site’s appearance without writing any CSS at all.” he wrote.
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
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
Sarah Gooding reports on an update of the Create Theme plugin in her post: Gutenberg’s Roadmap for a “Font Library” Will Give Users an Interface for Registering and Managing Web Fonts. Besides the features: create a new theme, start with a blank theme, create a child theme, or create a style variation, in now sports a dedicated screen for managing fonts. In her post, Gooding also summarized the tracking ticket on the Webfonts API and links to design exploration for a font manager within the core app.
\n\n\n\nMike McAlister shows you Three beautiful font pairs to bring your design to life. “With all the new fonts out there, there’s no excuse to be using tired old fonts on your website. Here are a few fonts that should definitely be on your radar.” he wrote.
\n\n\n\nFränk Klein was a guest on the WP Jukebox podcast episode #50 and discussed with host Nathan Wrigley about How Gutenberg and Full Site Editing Are Bringing New Opportunities for WordPress Developers.
\n\n\n\nManoj Kumal wrote a tutorial on CSS-Tricks on Creating a Settings UI for a Custom WordPress Block. It’s the third post in the series “Working With External APIs in WordPress Blocks”. The first two post cover the rendering of external data on backend and frontend. The last post on “Saving custom block settings” is coming soon.
\n\n\n\nRyan Welcher is back streaming on Twitch again! This week’s topic was Working with Query Loop block variations, a new feature that came with the latest major WordPress 6.1. You can read the dev note on then WordPress make blog: Extending the Query Loop block.
\n\n\n\nAs always, if you read this post two weeks after it was published, you’ll find the recording of the Twitch streams on Ryan Welcher’s YouTube channel.
\n\n\n\nJonathan Bossenger and Álvaro Gómez ran a two-part workshop on Developing blocks without React. The recordings are now available on WordPress TV:
\n\n\n\nDan Knauss of Post Status reported on The Future of GiveWP and the Block Editor. He summarized: “The journey to GiveWP 3.0 is well underway — an open, iterative development process that fully embraces WordPress’s Gutenberg block editor. Give cofounder Matt Cromwell and development director Jason Adams share what they’ve learned so far.”
\n\n\n\nThe main reasons for the rebuild are that the plugin match visual experience of the block editor, the need for more form field flexibility and to simplify template building. “Taking advantage of the components and packages of the block editor, as visual builder framework, continually improved and maintained by the open-source project, the GiveWP developers were faster in getting specific features done in a matter of hours rather than months.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
New Date! December 16, 2022
WordFest Live Returns – the 24-hour Festival of WordPress
February 17 – 19, 2023
WordCamp Asia 2023 – the first round of speakers was announced
Have a look at the schedule of upcoming WordCamps to find one near you.
\n\n\n\nNovember 21, 2022 – 3 pm ET / 20:00 UTC
Intro to the Site Editor & Template Editor with Wes Theron
November 22, 2022 – 3:30 pm ET / 20:30 UTC
Hallway Hangout: Future of CSS in block themes
November 22, 2022 – 11 am ET / 16:00 UTC Repeated at 5 pm ET / 22:00 UTC
Designing in the Site Editor: A WordPress Block Theme Exploration
November 22, 2022 – 7 pm ET / 24:00 UTC – Repeated at 11 pm ET / 4:00 UTC
Demystifying Gutenberg
December 1, 2022 – 3 pm ET / 20:00 UTC
Builder Basics: Building with Columns, Groups, Rows and Stacks with Nick Diego
December 8, 2022 – 3 pm ET / 20:00 UTC
Builder Basics: Demystifying theme.json and Global Styles with Nick Diego
Featured Image: Early morning. Building with where the lights are on by Paal Joachim Romdaal found on WordPress.org/photos
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nDivi, the popular commercial WordPress theme and page builder created by Elegant Themes, has announced major changes coming in version 5.0 that constitute a complete rewrite of Divi’s core technologies. The update, which is expected to be released in beta next year, will focus on performance, stability, scalability, and extendability, but it will not introduce any new features.
\n\n\n\n“We are recreating Divi’s backend framework, cleaning up years of technical debt, changing Divi’s storage format and improving its rendering mechanism,” Elegant Themes CEO Nick Roach said. “This new version of Divi will be able to processes design settings much more quickly.”
\n\n\n\nOne of the most notable changes coming in 5.0 is that Divi will be migrating away from shortcodes.
\n\n\n\n“This change will bring Divi into alignment with the future of WordPress, which is evolving in a new direction,” Roach said.
\n\n\n\nDivi will migrate to a new JSON format that is similar to the way Gutenberg stores data. The legacy shortcodes will continue to work and for a time Divi will lazy load in the old framework as necessary.
\n\n\n\n“If you are using Divi shortcodes outside of your post content, it will be highly recommended to replace these shortcodes with our new json-based elements,” Roach said. “Otherwise, you are going to take a performance hit.”
\n\n\n\nAs part of the 5.0 update, Divi’s developers plan to include a button to perform the migration away from shortcodes, which will automatically change posts to use the new system.
\n\n\n\nDivi 5.0 will also introduce a new Builder API, which Roach said “may also open up opportunities for Divi/Gutenberg cross-compatibility:”
\n\n\n\n\n\n\n\n\nDevelopers familiar with creating blocks for WordPress will find a lot of similarities in the Divi 5.0 module API. WordPress blocks will be more easily adapted to Divi and WordPress developers will be able to jump head first into building things for our community. We are building this new version of Divi to work in harmony with WordPress.
\n
News of the coming update was well-received by Divi users who posted additional questions and concerns in the comments. A few users were skeptical about the new direction but willing to see how it pans out.
\n\n\n\nPeter R, a current user who said he appreciates Divi’s “nicer and smoother UX,” along with the collections of design settings, indicated that Divi seems to be falling behind what the block editor offers for building pages with dynamic data:
\n\n\n\n\n\n\n\n\nAs nice as Divi 5.0 sounds, it’s just sooo far away… especially since it won’t have the features I’m looking for at launch which will then take even longer if those features appear at all. I was really hoping Divi 5.0 would move more towards the Gutenberg block builder (other than back-end data storage etc).
\n\n\n\nThere seems to be a real arms race going on with block builders right now. Many are adding features that Divi simply can’t compete with now and will probably take years to match if at all. Far more flexible layouts especially when it comes to making your own post loops etc, more powerful features for displaying dynamic data or for collecting and storing data, and the ability to mix-and-match blocks from different creators so you don’t depend on a single provider like Divi.
\n
More than 2,425,411 live websites are currently using Divi and an an additional 1,486,812 sites that used the product historically, according to BuiltWith. The nearly 10-year-old product has grown steadily for years but seems to have plateaued beginning in 2020.
\n\n\n\nEmbracing the way WordPress is going will be important for the page builder’s continued success, and Elegant Themes seems to be acknowledging this with the planned update.
\n\n\n\n“On the block theme front, as a part of Divi 5.0, we are also transitioning into a Block Based theme, and since Divi 5.0 is actually internally built using the same ‘packages’ that Gutenberg itself is composed of, Divi 5.0 has a lot of compatibility built in from the core,” Elegant Themes developer Josh Ronk said.
\n\n\n\n“We are working diligently to push Divi 5.0 for maximum Gutenberg block compatibility, with the goal being that you would be able to use Gutenberg blocks inside of your Divi built pages, and then apply all of the Divi design options you love to the otherwise plain Gutenberg blocks you have installed. This means you won’t have to choose between Divi or Gutenberg, and rather you get Divi AND Gutenberg.”
\n\n\n\nDivi’s developers plan to ensure the old Divi modules built with the current Divi API are backwards-compatible, working on the front end but with a more limited capacity in the Visual Builder. They will be encouraging developers to move to the new API to take advantage of the performance benefits.
\n\n\n\nDivi 5.0 will not introduce new features or changes to Divi’s design, but the underlying architecture will be moving closer to Gutenberg compatibility.
\n\n\n\n“Divi 5.0 will use React and it will leverage more of the native Gutenberg packages,” Roach said. “At some point we hope that Divi and Gutenberg will work in harmony. We don’t want to fight against the direction that WordPress is heading.”
";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, 19 Nov 2022 00:07:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:27;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:40:"Post Status: WordPress Community Roundup";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144726";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:51:"https://poststatus.com/wordpress-community-roundup/";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:3370:"It sounds like a tall order, but there it is: over at Ollie, Mike McAlister has proposed “a thought experiment and design concept” called OpenPress:
\n\n\n\n\n\n\n\n\nWhat would it look like to start connecting millions of websites, users, and content that power half of the web in a more purposeful and open way?
\n
Alex Kirk drew attention to his work on a plugin I''d never heard of called Friends. Friends makes it easier to follow your selected blogs/RSS feeds inside WordPress — and restrict some posts to a private network of friends. There are content blocks with restricted visibility “for friends on a per-block basis.” Friends “supports IndieAuth” and “doesn’t interfere with other IndieWeb projects such as Webmentions.”
\n\n\n\nBlack Friday/Cyber Monday is coming quickly! Submit your deals here.
Find this year’s deals here. (More are being added weekly!)
Sabina Ionescu published a lot of different responses from people in the WordPress community to questions about the impact of the pandemic on them.
\n\n\n\nThe history of screen readers is incredible! Sheon Han tells their hidden story and how “blind programmers have been creating the tools their community needs” — for decades.
\n\n\n\nJoanne Limburg discusses the agonizing and awful, inadequate questions about disability in job applications, government forms, and thoughtless conversations.
\n\n\n\nDan Knauss blogged about “crip time.” What happens if we think about time management through disability, pain, grief, or the needs of children?
\n\n\n\nWordCamps are back. Check the schedule online!
\nThis article was published at Post Status — the community for WordPress professionals.
";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, 18 Nov 2022 20:30:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";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:28;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:67:"Post Status: WordPress Business Roundup for the Week of November 14";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144686";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://poststatus.com/wordpress-business-roundup-for-the-week-of-november-14/";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:6286:"Tom Willmot on the Challenges and Opportunities Facing Enterprise WordPress • Tom Lach on the costs of rapid growth — It''s not for everyone • The Future of GiveWP and the Block Editor • Evolving Edupack — and Sunsetting It • and more…
Estimated reading time: 8 minutes
\nSparked by Magne Ilsaas‘s ideas in The WordPress Enterprise Paradox, Tom started a Twitter thread and hosted a live discussion with Magne and others at enterprise WordPress agencies this week. Their main concern is the challenges that arise from not having a well-defined brand and market that allows “WordPress for the Enterprise” to stand out — without being ties to a particular WordPress company or host. After getting an outline of the problem as it stands today, I asked Tom what might help differentiate “Enterprise WordPress” as a collective or entire ecosystem of agencies operating within it. Can open-source values of sharing and cooperation shape a unique global identity for enterprise WordPress agencies? Is it time for an inter-agency association or “guild” to take on these challenges? LISTEN→
\n\n\n\nBack in 2019, Tom Lach‘s agency was a team of 10 people, and they were entering a space where they could easily start working with big enterprises. Their idea of the future was to scale up and grow. Of course it was. How honest conversations at WCEU changed that. READ→
\n\n\n\nThe journey to GiveWP 3.0 is well underway — an open, iterative development process that fully embraces WordPress''s Gutenberg block editor. Give cofounder Matt Cromwell and development director Jason Adams share what they''ve learned so far. READ→
\n\n\n\nBlake Bertuccelli shares how a plugin that tried to do it all led to an accessibility platform and enhanced client services. READ→
\n\n\n\nThis article was published at Post Status — the community for WordPress professionals.
";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, 18 Nov 2022 17:36:52 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";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:29;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:114:"Post Status: Tom Willmot on the Challenges and Opportunities Facing Enterprise WordPress — Post Status Draft 130";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144467";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:121:"https://poststatus.com/tom-willmot-on-the-challenges-and-opportunities-facing-enterprise-wordpress-post-status-draft-130/";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:9991:"Sparked by Magne Ilsaas‘s ideas in The WordPress Enterprise Paradox, Tom started a Twitter thread and hosted a live discussion with Magne and others at enterprise WordPress agencies this week. Their main concern is the challenges that arise from not having a well-defined brand and market that allows “WordPress for the Enterprise” to stand out — without being ties to a particular WordPress company or host. After getting an outline of the problem as it stands today, I asked Tom what might help differentiate “Enterprise WordPress” as a collective or entire ecosystem of agencies operating within it. Can open-source values of sharing and cooperation shape a unique global identity for enterprise WordPress agencies? Is it time for an inter-agency association or “guild” to take on these challenges?
Estimated reading time: 8 minutes
\nTom Willmot has been a WordPress pioneer and leader in the agency space since co-founding Human Made in 2010. Just in the past year, Human Made has more than doubled its size with a team of 100. Tom is also CEO and co-founder of Altis DXP, Human Made''s enterprise WordPress digital experience platform. I caught up with Tom this week to find out what he''s thinking about the challenges and opportunities of the enterprise market for WordPress agencies today.
\n\n\n\nSparked by Magne Ilsaas‘s ideas in The WordPress Enterprise Paradox, Tom started a Twitter thread and hosted a live discussion this week about the challenges of not having a well-defined brand and market for enterprise WordPress. In the minds of clients beyond the WordPress and open-source community not to mention unhelpful tech industry analysts, “WordPress” is something you can buy, and it''s often confused with any number of related brands: Automattic, WordPress VIP, and managed WordPress hosts that support enterprise clients.
\n\n\n\nAfter getting an outline of the problem as it stands today, I asked Tom what might help differentiate “Enterprise WordPress” as a collective or entire ecosystem of agencies operating within it. Can open-source values of sharing and cooperation shape a unique global identity for enterprise WordPress agencies? Is it time for an inter-agency association or “guild” to take on these challenges? (Human Made has an internal “guild” structure of cross-functional teams — what could it look like to extend them across the whole agency space?)
\n\n\n\nAnd how might that look within the WordPress ecosystem and others adjacent to it? Are more inter-agency gatherings needed along with greater participation in existing tech and design conferences? Will agencies like Human Made resume hosting conferences like their Day and Week of REST events in the past? Can the larger WordCamps cater to an enterprise track? Does Enterprise WordPress need its own conferences? I like Jeremy Keith and ClearLeft as a model for agency thought leadership. Magne has pointed to the Society of Digital Agencies (SoDA) as a model for organized peer collaboration and North Patrol as a model for a research and advisory firm that connects agencies with clients and reports on regional enterprise web tech markets.
\n\n\n\nThis is an open, ongoing conversation. If it piques your interest, connect with Tom on Twitter.
\n\n\n\n Sponsor: ElementorElementor enables web creators to build professional, pixel-perfect websites with an intuitive visual builder. Quickly create amazing websites for your clients or your business with complete control over every piece, without writing a single line of code. Join a vast community of web creators from all around the world who deliver exceptional websites using Elementor.
\n
Elementor\n\n\n\n
Mentioned in the show: You can follow Post Status and our guests on Twitter:The Post Status Draft podcast is geared toward WordPress professionals, with interviews, news, and deep analysis.
Browse our archives, and don’t forget to subscribe via iTunes, Google Podcasts, YouTube, Stitcher, Simplecast, or RSS. 
This article was published at Post Status — the community for WordPress professionals.
";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, 18 Nov 2022 16:30:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";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:30;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:79:"Do The Woo Community: A Sneak Peak into Do the Woo 4.0, Supporting Contributors";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=73436";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:77:"https://dothewoo.io/a-sneak-peak-into-do-the-woo-4-0-supporting-contributors/";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:422:"In a recent podcast I gave a bit more insights to what you will be seeing with out newest update in early 2023.
\n>> The post A Sneak Peak into Do the Woo 4.0, Supporting Contributors appeared first on Do the Woo - a WooCommerce Builder 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:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Nov 2022 10:27:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;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:63:"Post Status: WordPress Tech Roundup for the Week of November 14";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144586";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:74:"https://poststatus.com/wordpress-tech-roundup-for-the-week-of-november-14/";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:7153:"Learn Accessibility • The Return of SmashingConf • PHP 8.2 Release Delayed • Deno for Decoupled Front-End Development • LogoIpsum, Post to Telegram, and WP .gitgnore • Substack, the WordPress Plugin • Cool Tool: Restrict With Stripe
Estimated reading time: 8 minutes
\nDigital accessibility, commonly abbreviated a11y, is an important subject in web developer circles. More and more, folks are looking for solid guidance on designing and building websites and web apps that disabled people can interact with in a meaningful and equivalent way.
\n\n\n\nFortunately, thanks to Carie Fisher, with input and review from Alexandra White and Rachel Andrew, web developers can now take the free Learn Accessibility course at web.dev.
\n\n\n\nThis course is for beginner and advanced web developers. You can go through the series from start to finish to get a general understanding of accessibility practices and testing, or you can use it as a reference for specific subjects.
\n\n\n\nFront-end developers rejoice, the yearly SmashingConf hosted by the folks at Smashing Magazine is back in 2023!
\n\n\n\nSmashingConf has two events this year: one in San Fransisco, US, and one in Freiburg, Germany.
\n\n\n\nSmashingConf SF will cover everything from accessibility and advanced CSS to JavaScript gems and web performance, while SmashingConf Freiburg is all about front-end, UX, and design.
\n\n\n\nDue to some critical bugs related to OPcache that “are very likely to happen in a real-world use case” the PHP release managers have decided to add another PHP 8.2.0 RC and push back the final 8.2.0 release to December 8, 2022.
\n\n\n\nWith the fast pace at which new PHP releases have been coming out, it’s good to remember that early testing of release candidates is critical to solid releases.
\n\n\n\nIn a recent blog post on the Deno website, the team announced support for building WordPress themes using the Fresh framework as a front end for headless (or decoupled) WordPress.
\n\n\n\nDeno is a runtime for JavaScript, TypeScript, and WebAssembly that is based on the V8 JavaScript engine and the Rust programming language. Created by Ryan Dahl, the creator of the Node.js runtime, Deno aims to address some of Dahl’s regrets about the initial design decisions with Node.js.
\n\n\n\nWith the increased popularity of headless WordPress, this is an interesting entry into the space.
\n\n\n\nBen Thompson’s Stratechery was a Substack inspiration and has always run on WordPress, but did you know Substack started as a WordPress product?
\n\n\n\nEach week we feature one cool tool that can help make your life easier as a WordPress builder.
\n\n\n\nStranger Studios quietly launched a new e-commerce plugin for WordPress a few weeks ago: Restrict With Stripe. If you love Stripe, it''s for you. It connects to Stripe and lets you restrict a post, page, category, or tag by product so visitors must have purchased that product (or subscription) to get access to the restricted content. That''s it.
\nThis article was published at Post Status — the community for WordPress professionals.
";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, 18 Nov 2022 10:00:26 +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:"Jonathan Bossenger";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:32;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:62:"WPTavern: Jetpack Search Adds Free Tier and 3-Month Free Trial";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=139608";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:73:"https://wptavern.com/jetpack-search-adds-free-tier-and-3-month-free-trial";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:3568:"Jetpack Search, a plugin that enhances WordPress’ search capabilities, has added a free tier and a three-month free trial to what was previously only available as a paid upgrade. The plugin uses WordPress.com’s infrastructure to provide instant, more relevant search results without reloading the page, with real-time indexing, integration with WooCommerce, spelling correction, and more.
\n\n\n\nJetpack Search was launched as a standalone plugin earlier this year but the user base hasn’t grown beyond a couple hundred active installs. The new free tier and free trials enable prospective customers to try out the functionality on their sites before committing to a new annual subscription.
\n\n\n\nFree users are limited to 5k records (all posts, pages, and other types of content the site indexes) and 500 requests (every time a visitor searches for something on the site) per month. Sites that go over the limits will not be cut off for the first three months.
\n\n\n\nAt 10K records, pricing starts at $8.25/month, billed annually, and includes 10k requests, priority support, and unbranded search. When purchasing, Jetpack estimates the size of the site, but users who are not sure how many records they have can sign onto the free tier to find out.
\n\n\n\nThe previous pricing for Jetpack Search started at $2.50 per month (billed annually) for up to 100 records. The plugin’s support docs explain why Jetpack implemented this major pricing change:
\n\n\n\nJetpack assured existing search customers that the new pricing will not yet affect them until their plan renews and Automattic will contact them by email before the pricing changes.
\n\n\n\nJetpack Search is built on top of Elasticsearch, and currently uses version 7.16, which is Elastic’s proprietary offering after the company abandoned its open source licensing. As a consequence, Amazon forked Elasticsearch and Kibana at version 7.10 to create the OpenSearch project.
\n\n\n\n“We built our own solution on top of it. We use Elasticsearch to build Jetpack Search, but we also use a lot of our other systems, especially Jetpack Stats, to provide great search relevancy that you can’t get by just deploying Elasticsearch,” Jetpack Marketing Lead Rob Pugh said.
\n\n\n\n“We are running both OpenSearch and Elasticsearch for different services but Jetpack Search is on ES. We’ll continue to consider both in the future.”
";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, 18 Nov 2022 03:40:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;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:22:"Post Status: Two Tools";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144143";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:33:"https://poststatus.com/two-tools/";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:450:"Jetpack and WordPress.com can publish to Telegram.
\n\n\n\nThe ultimate gitignore for WordPress projects.
\nThis article was published at Post Status — the community for WordPress professionals.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 21:37:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"\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:45:"Post Status: Are WebP and SVG Pixels Greener?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144155";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:55:"https://poststatus.com/are-webp-and-svg-pixels-greener/";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:1204:"As a followup to my note in August on this topic, here''s what Tom Greenwood had to say about WebP''s value to sustainability in WordPress:
\n\n\n\n\n\nI think as most browsers support WebP now, there is a real benefit to serving this format as it saves a lot on data transfer and improves performance. The downside perhaps is that most images are uploaded as JPG and pretty much all implementations that I have seen will then generate the WebP files as duplicates, so there is unfortunately an increase in data storage. I think the trade-off is worth it though.
\n\n\n\nAs for SVG, these can be way more efficient in terms of both data storage and transfer compared to JPG or WebP, but of course they should be well optimised, and I''m not sure of an automated way to do that, so there is more hands on work there. The downside here is that complex SVG files could cause more CPU energy to be used on the end user''s device, so the simpler the design and more optimised the files the better.
\n
This article was published at Post Status — the community for WordPress professionals.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 17:46: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:10:"Dan Knauss";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;a:6:{s:4:"data";s:13:"\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:92:"Post Status: Pandemic experiences, “Are you disabled?” and the history of screen readers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=143978";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:95:"https://poststatus.com/pandemic-experiences-are-you-disabled-and-the-history-of-screen-readers/";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:1343:"Back in July, Sabina Ionescu published a lot of different responses from people in the WordPress community to questions about the impact of the pandemic on them. I missed it then, but it''s still relevant and worth reading.
\n\n\n\nSome other things I''ve enjoyed but haven''t slipped into a post yet:
\n\n\n\nJoanne Limburg discusses the agonizing and awful, inadequate disability/disabled questions that come with job applications, government forms, etc.:
\n\n\n\n\n\n\n\n\nDo you consider yourself to be a disabled person?
\n\n\n\nYes: ☐
\nNo:☐Prefer not to say:☐
The history of screen readers is incredible! Sheon Han tells their hidden story and how “blind programmers have been creating the tools their community needs” — for decades.
\nThis article was published at Post Status — the community for WordPress professionals.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 14:34: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:10:"Dan Knauss";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:92:"Do The Woo Community: Piccia Neri, a Rocking Good UX Designer Passionate About Accessibility";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=73508";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:90:"https://dothewoo.io/piccia-neri-a-rocking-good-ux-designer-passionate-about-accessibility/";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:475:"Piccia is passionate about good UX, and in this show offers some great user experience insights into both WordPress and WooCommerce sites.
\n>> The post Piccia Neri, a Rocking Good UX Designer Passionate About Accessibility appeared first on Do the Woo - a WooCommerce Builder 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:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 10:33:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;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:111:"Post Status: Patchstack enriches open vulnerability data with signals showing attack volume, method, and source";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144216";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:120:"https://poststatus.com/patchstack-enriches-open-vulnerability-data-with-signals-showing-attack-volume-method-and-source/";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:2682:"Back in August, Oliver Sild announced in Post Status Slack that Patchstack was opening up “additional data” to “enrich the vulnerability data” their service discloses, now “with [a] real-time IP feed of attackers who hit [Patchstack''s] virtual patches.”
\n\n\n\nVirtual patches are Patchstack''s quick interventions for customers'' sites when an official patch doesn''t exist yet for a newly disclosed vulnerability. In Oliver''s words, they are “security rules that protect from specific plugin/theme/core vulnerabilities.” So, if someone is actually hitting these virtual patches, it''s very likely they are trying to probe or exploit a vulnerability.
\n\n\n\nSince the large number of sites being protected by Patchstack''s virtual patches makes a very big (but impenetrable) attack surface for new vulnerabilities and zero-day attacks, it makes a perfect attack monitoring network — or possibly even a honeypot for attackers. The data Patchstack can get from hits to their patches “gives more context to all vulnerabilities.” In other words, they can see if a particular vulnerability is being targeted heavily — or not at all. Then they can prioritize the attention of their security network partners and “fight fearmongering (i.e low severity plugins that get to media, but we all know are not exploited).”
\n\n\n\nOliver breaks down the details:
\n\n\n\n\n\n\n\n\nWe create those virtual patches on a daily basis for all new security vulnerabilities that we add to the Patchstack Database and protect a very large number of sites globally. That gives us an accurate coverage of both small and big attack campaigns targeting WordPress sites and plugins, but more importantly — we are often able to identify the attackers and their new methods first. The cool thing is that since our virtual patches cause no false positives, the same quality applies to our IP threat feed.
\n
This is cool indeed! WordPress security could go on the offensive with information like this and shut down attackers with the help of hosting partners.
\n\n\n\nPatchstack is going to publicly release the actual attack levels for each vulnerability in their database, “but for anyone who needs such data in bulk (to apply on their entire hosting infrastructure or to network firewalls), here’s some more information already: https://patchstack.com/for-hosts/
\nThis article was published at Post Status — the community for WordPress professionals.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 05: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:10:"Dan Knauss";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"\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:53:"WPTavern: Loudness: A New Block Theme from Automattic";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=139475";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:63:"https://wptavern.com/loudness-a-new-block-theme-from-automattic";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:3200:"Automattic has released a new block theme called Loudness that is available on both WordPress.com and WordPress.org. It’s an artistic and opinionated theme based on the company’s Block Canvas starter theme. Although Loudness’ brief description suggests the theme was created for “music and learning,” the design and custom patterns lend themselves to a variety of different use cases. It could easily be used to whip up a quick event website with ticketing, an artist’s portfolio, or even a personal blog.
\n\n\n\nLoudness’ typography features the energetic combination of the sans-serif Rubik font for headers and DM Mono for paragraph text. The type design and font development for DM Mono was commissioned from Colophon Foundry, an award-winning type foundry based in London.
\n\n\n\nInstalling and activating the theme on a fresh website offers users a good experience, as it automatically puts everything in the design in place exactly like the live demo on WordPress.com. Users don’t have to figure out which patterns to add in order to get it looking like the demo.
\n\n\n\nLoudness packages 12 custom block patterns, which can be previewed on WordPress.org. The pattern organization in this theme could be improved, as Loudness’ patterns are intermixed with selections from the pattern directory. It’s not easy to differentiate which ones belong to the theme. For purists who like to use only the patterns included in the theme to keep the design tight, it’s much easier when a theme creates a custom label in the pattern explorer for its own patterns.
\n\n\n\nNot pictured in the demo is a full-width FAQ pattern with a dark color scheme, which matches the other quirky design elements in the theme.
\n\n\n\nIn addition to the instructors pattern and pricing table shown in the demo, Loudness includes artistic designs for a pullquote pattern and a section of large text.
\n\n\n\nTwo illustrations are included for use in the header area or to break up the design. They can easily be swapped out for a photo or a custom illustration from another source.
\n\n\n\nLoudness doesn’t include any style variations, likely because most of the patterns are highly dependent on the established color palette. Although users are free to alter it in the Site Editor, the results may not be as harmonious as expected when using the illustrations in the site design.
\n\n\n\nLoudness is a unique block theme that makes a strong impression and can be creatively applied to many different types of websites – from events to blogs to businesses and agencies. The theme is available for free from WordPress.org and is also available to users on WordPress.com.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 01:47:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:39;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:40:"Post Status: Catching up with 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:32:"https://poststatus.com/?p=143970";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:51:"https://poststatus.com/catching-up-with-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:3251:"Bob puts out so much writing and audio at Do the Woo and has so many different people featured, it''s hard to keep up! These are some recent ones I''ve taken note of but didn''t get into a post or newsletter. Definitely worth a listen:
\n\n\n\nThis article was published at Post Status — the community for WordPress professionals.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Nov 2022 00:29:01 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"\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:43:"Post Status: Naming is hard—but important";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144121";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:52:"https://poststatus.com/naming-is-hard-but-important/";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:502:"This is an important topic that came out of a Post Status Slack #security discussion involving Robert Rowley and John James Jacoby: WordPress Terminology Meta. It continued over at the WPwatercooler.
\n\n\n\n\nThis article was published at Post Status — the community for WordPress professionals.
";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, 16 Nov 2022 21:17:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";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:86:"Post Status: WordPress 6.1.1 • Team Rep Nominations • Codespaces for Contributions";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=144028";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:89:"https://poststatus.com/wordpress-6-1-1-team-rep-nominations-codespaces-for-contributions/";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:16163:"Time to update, WordPress 6.1.1 is out! GitHub has made Codespaces available for 60 hours/month, and WordPress is exploring Core contribution integrations with wordpress/wordpress-develop. It''s team rep nomination time too.
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.
Are you interested in giving back and contributing your time and skills to WordPress.org? 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.
You — and your whole team can Join Post Status too!
\n\n\n\nBuild your network. Learn with others. Find your next job — or your next hire. Read the Post Status newsletter. Listen to podcasts. Follow @Post_Status and LinkedIn.
This article was published at Post Status — the community for WordPress professionals.
";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, 16 Nov 2022 19:36:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;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:69:"WPTavern: WordCamp Asia 2023 Announces Speakers, Unveils Wapuu Mascot";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=139547";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/wordcamp-asia-2023-announces-speakers-unveils-wapuu-mascot";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:2443:"WordCamp Asia 2023, the first flagship event to take place in Asia, is just a few months away, scheduled for February 17-19, 2023, in Bangkok, Thailand. Organizers have announced the first round of speakers, a diverse selection of WordPress professionals from Asia and across the globe.
\n\n\n\nThe event has also unveiled its wapuu mascot. After receiving 10 design submissions from eight designers from India, Malaysia, Hong Kong, the Philippines, Taiwan, and Japan, organizers selected the Chao Phraya Boat Wapuu. Designer Chiaki Kouno explained the concept:
\n\n\n\n\n\n\n\n\nThis boat takes us to the venue “Icon Siam” on the Chao Phraya River! The boat contains the key colours of the WCA and the WCA logo is displayed on the ball. There is a splash of waves expressing a speedy feeling, showing everyone’s expectations for the last three years.
\n
WordCamp Asia is running a series of webinars for contributors and attendees. The first episode was broadcast on Twitter this week and is embedded below. Organizers are asking contributors to share their stories in text, audio, or video format, to encourage newcomers to participate in the Contributor Day event. The webinar also featured tours of ICONSIAM, a beautiful and modern venue where the first WordCamp Asia will take place.
\n\n\n\nOrganizers published a notice that there will be no childcare offered at the WordCamp, due to the potential for COVID-19 transmission. Nursing and changing facilities are available the 4th and 5th floor of the venue, which also offers some children’s entertainment options. Those who are 12 years old and younger can attend the conference for free if accompanied by an adult who has purchased a ticket.
\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, 16 Nov 2022 19:19:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"\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:87:"WPTavern: #51 – Adam Lowe on Building Websites With Pinegrow’s New WordPress Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=139471";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:98:"https://wptavern.com/podcast/51-adam-lowe-on-building-websites-with-pinegrows-new-wordpress-plugin";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:52951:"TranscriptJukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case using the new plugin from Pinegrow to create complex WordPress websites.
\n\n\n\nIf 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.
\n\n\n\nHead over to WPTavern.com forward slash contact forward slash jutebox and use the contact form there.
\n\n\n\nSo on the podcast today, we have Adam Lowe. Adam runs Peak Performance Digital, a small web consulting agency in Washington, DC, which specializes in providing website strategy along with custom WordPress solutions.
\n\n\n\nHe’s on the podcast today to talk about a new plugin from Pinegrow. Adam does not represent the company, but as an avid user of their products and experienced in how they work. The Pinegrow web editor is a desktop tool that lets you build websites with a graphical user interface.
\n\n\n\nThe closest comparison would be a page builder, but this is not entirely accurate. Unlike most page builders, which require very little technical expertise. Pinegrow does require an understanding of technology such as CSS, SASS Grid, Bootstrap, Tailwind CSS, to make use of the platform. The intention of the tool is to make it possible to create complex sites, but with a close eye on the HTML and CSS that is being output.
\n\n\n\nGiven the popularity of WordPress, the Pinegrow developers have created a WordPress plugin, which is just about to be released. It’s in closed beta and Adam has been using it as his go-to solution for several months now.
\n\n\n\nWe talk about what the platform can do and how it works. It’s not going to be a plugin for beginners, and there’s going to be a learning curve for those who do take the plunge. It’s intended as a bit of a bridge between novices and WordPress experts.
\n\n\n\nWe also get into a discussion about the fact that Pinegrow is intended to be a no dependency solution. Once you finished creating your theme block or whatever else you might want to create, you can export that in a way that no longer needs Pinegrow at all. If you’re curious about new ways to create websites in WordPress, have a listen to the podcast and see if Pinegrow is a good fit.
\n\n\n\nIf you’re interested in finding out more, you can find all of the links in the show notes by heading over to WPTavern.com forward slash podcast, where you’ll find all the other episodes as well.
\n\n\n\nAnd so without further delay, I bring you Adam Lowe.
\n\n\n\nI am joined on the podcast today by Adam Lowe. Hello, Adam.
\n\n\n\n[00:03:46] Adam Lowe: Hello.
\n\n\n\n[00:03:47] Nathan Wrigley: It is very nice to have you on the podcast today. We normally begin with a little bit of a brief introduction from our guests, just so that we can orientate ourselves around who you are, what your relationship is with WordPress. So if you wouldn’t mind, just for a few moments, just briefly describe your past in the WordPress space or with tech in a more general way.
\n\n\n\n[00:04:07] Adam Lowe: I had been in the website space for a long time. I started in the late nineties. I actually think that I built my first website and sold my first in website 1997. And I’ve been around WordPress since the very first version, I think that was called Miles Davis actually. Used it for quite a while. Took a little bit of time away while I worked in-house in corporate, using some enterprise products. And then I got back into it again, I guess six or seven years ago. So it’s been a really interesting journey and seeing how far it’s come in that time period has been incredible.
\n\n\n\n[00:04:36] Nathan Wrigley: You are on the podcast today to talk about a particular tool that you’ve been using. It’s a curious tool in that it is soon to be a WordPress plugin. So the features that the desktop version has had for a long time are being ported over into a WordPress plugin so that you can use it inside different installs of WordPress.
\n\n\n\nIt’s called Pinegrow. If you’ve not come across Pinegrow before, maybe it’s a good idea to pause the podcast and go Google Pinegrow. I’m sure you’ll find it. You can see exactly what it does, but would you be able to, first of all, lay out what Pinegrow is, and also would you just make it clear what your relationship to the company is? Because I think that might be an important thing to clarify right at the start.
\n\n\n\n[00:05:19] Adam Lowe: It definitely is and I appreciate that. So Pinegrow, it looks like a page builder. It acts like a page builder. It smells like a page builder, but it’s not a page builder. Pinegrow is actually a theme builder and a block plugin builder, and what it does is it lets you visually create websites and visually create blocks and themes, and then it takes what you create in their builder and it spits out WordPress native code.
\n\n\n\nSo it uses native WordPress functions and all of that to, spit out React blocks, and PHP themes that you can just move to your website and install like you would anything else that you had hand coded. So, whereas most page builders live inside of WordPress and require you to have it installed and running, Pinegrow doesn’t need that.
\n\n\n\nPinegrow is just a builder that lets you, build things, basically code in a very visual manner. My relation to them is, I’m just a user. I pay for the product. I didn’t even think that it was going to be my main product a year and a half ago, but the more that I’ve used it, the more I’ve come to rely on it and I see the benefits of it.
\n\n\n\nSo I have developed a very close relationship with the company. I’m not employed by them. They don’t pay me, nothing like that. I just feel very passionate about this as a product and it definitely suits my needs from a business standpoint.
\n\n\n\n[00:06:36] Nathan Wrigley: That’s good to clear up. Thank you for that. The intention of the product then, in the future will be that the desktop version that you’ve been using for years, is now going to be a WordPress plugin. In other words, you could install it on different sites, and you could modify all of the different pieces of your WordPress website.
\n\n\n\nBut just to be clear, once you have finished that work and exported a theme or a plugin, block, whatever it may be, you’re making the point that it’s no longer required. There isn’t a dependency to have that plugin installed any longer. You could whip it out. Remove all trace of Pinegrow, and everything should still just work.
\n\n\n\n[00:07:17] Adam Lowe: That’s absolutely right. And when I talked to Matjaž a few, I guess several months ago, and he was telling me about this project, I had asked him, hey, is it possible to be able to do this sort of thing? And he came back and said, yes. And my mind was completely blown. I just didn’t think that anyone was going to be, maybe brave enough or, able to build something like that.
\n\n\n\nAnd when he came back and said that, yes, this is the way that it already works, I was like, I need to get in this beta. And maybe two months ago he invited me into the private beta, and I’ve been testing it ever since. And yeah, it’s incredible that that’s what it does. It is just a builder that, it creates a plugin that you activate like a normal plugin or creates a theme that you activate like a normal theme. And once you’ve got it in there, the need for the Pinegrow builder plugin is gone. The only reason why you would potentially need or even want it, is if you wanted to make a change to that theme or to that block plugin. So there is still a benefit of having it on there, but it’s definitely not a dependency or a requirement.
\n\n\n\n[00:08:12] Nathan Wrigley: Yeah, that’s really quite interesting. Obviously, if we’re using a typical page builder, if we remove the page builder, the page will look entirely different. But in this scenario, everything should still look the same because it’s not requiring Pinegrow from that moment on.
\n\n\n\n[00:08:26] Adam Lowe: Exactly.
\n\n\n\n[00:08:27] Nathan Wrigley: I’ve watched a few of your YouTube videos and I think we should probably figure out who the target audience for this is first, because the promise of page builders really is that more or less anybody can start building a website. And obviously, the advent of Gutenberg and full site editing and so on, that is hoped to be the promise. That anybody can log in and with a little bit of orientation and familiarization, they can start dropping things into the page and come up with something, perhaps use templates and modify those templates and so on.
\n\n\n\nI think it’s fair to say that Pinegrow is not really aimed at that target audience. It feels to me like the barrier to entry may be a little bit higher than that. Have you got anything to, to add to that?
\n\n\n\n[00:09:10] Adam Lowe: You’re right on the money. It is definitely not aimed at the new person. It’s not aimed at the Elementor crowd. It’s not aimed at even the DIY person. Originally Pinegrow was aimed at developers, and the desktop version, which is continuing to be supported and available. The desktop version continues to have more and different features than the website plugin. But that is really aimed towards people who want to get into the weeds.
\n\n\n\nFor the WordPress plugin, they’ve definitely put some considerations in there for people who aren’t quite as comfortable in code. So we’ve got some quick start tutorials. We’ve got some more, a little bit more handholding, but not as much as you would get with an Elementor. The best audience for Pinegrow would be somebody who is comfortable with code but doesn’t want to use it.
\n\n\n\nOr maybe somebody who is trying to learn a little bit of code, or knows the concepts, but doesn’t want to get in there and write PHP, HTML, CSS all day long.
\n\n\n\n[00:10:06] Nathan Wrigley: Is the reason for that because you need to have some sort of understanding, familiarity with the way WordPress works internally. Because this is generating, essentially code? You need to really understand where that code needs to be deployed, which lines of the HTML for example, it is that you’re going to target with various things. You need to basically have some understanding, otherwise, is it just going to be a purely frustrating experience?
\n\n\n\n[00:10:32] Adam Lowe: That’s exactly what it is, and you need to have a conceptual understanding of how WordPress works and how code works. Not really a practical hands on understanding of it. So you don’t need to know what all the functions are and how to, how to write them from scratch. But you need to know when to use different things. You need to understand how the theme hierarchy works. You need to understand how WordPress calls different pieces. Again, what the names of some of those functions are so that you can apply them.
\n\n\n\n[00:11:00] Nathan Wrigley: So, from everything that you’ve said, it feels a little bit like a bridge between, let’s just use the word novice, a novice user, and somebody who essentially is a complete expert. They understand everything. They can just open up, sort of IDE, a text editor if you like, and happily type away and build up all of the bits and pieces that they need.
\n\n\n\nThis is somewhere in between. You need to be, not an expert, but not a complete novice. There’s going to be some handholding and the UI will assist you along that path. But there’s definitely going to be some requirement to understand bits and pieces of how WordPress works conceptually.
\n\n\n\n[00:11:34] Adam Lowe: That’s exactly what it is. And if you look at some of the more advanced page builders on the market, I’d say about half that crowd, the more advanced half of that crowd, would be perfect for using Pinegrow. And the less advanced half might get confused by it. And then you have the developer side, the people that can code who just don’t want to, and don’t want to do all that repetitive stuff. And that is definitely a great market for Pinegrow.
\n\n\n\n[00:11:56] Nathan Wrigley: In terms of the level of understanding that would be a sensible default. Where are we pitching that really? Do you have to understand pretty much all of HTML and CSS? Do you have to have any understanding of JavaScript and React and so on? What are the core principles that you’d have to know off the bat, just so that you could begin using it?
\n\n\n\nBecause, I get the impression, having looked at your YouTube videos, that if I put a complete inexperienced user in front of this, there would just be, well, 10 minutes of mayhem and then throwing the computer out the window because it would be a very frustrating experience, because you wouldn’t know what anything meant. Where would you pitch this in terms of your CSS knowledge, HTML knowledge, and so on?
\n\n\n\n[00:12:38] Adam Lowe: You definitely want to know HTML, and you want to understand, again, the concepts of CSS and maybe what the different things are called in there. Because Pinegrow has the visual controls for everything. You don’t need to remember what all the different classes are and what all the different properties are and everything like that.
\n\n\n\nYou can come in and click and start creating your CSS rules visually. So that’s great. But you do need to understand how CSS works, again, at a conceptual level. And the same thing with HTML. You don’t need to know all the different bits and pieces. You don’t have to memorize 300 and some odd elements. You need to have an understanding of what to use and when.
\n\n\n\n[00:13:12] Nathan Wrigley: Does the plugin, because I think really that’s what we’re focusing on here. Does plugin bring along any guidance or tutorials to help you bridge that gap? So, explanations of how the UI works, but also more broadly, explanations of how WordPress works and explanations of things like CSS so that you can be swept along, just following Pinegrow’s documentation.
\n\n\n\n[00:13:38] Adam Lowe: First of all, Pinegrow’s got an incredible amount of documentation on their website and they’ve got tutorials for just about everything. So if you’re interested in it, I would start there. The plugin does have a new tutorial section built in and they have one tutorial built that takes you kind of start to finish on how to create a block. And it walks you through how to use the interface, how to create CSS rules, how to put elements on the page. Basically how to do everything you need to do.
\n\n\n\nSo them, including that has been, a great way to get your feet wet and get a basic understanding. But then, you go to the website and they’ve got tutorials on how CSS works. They’ve got tutorials on how WordPress works. They’ve got tutorials on how to create a WooCommerce site from scratch. How to create themes from scratch, all of that stuff. And it’s really just a matter of going in, and the more you use it, and the more you do the tutorials yourself, the better you’re going to understand it.
\n\n\n\n[00:14:28] Nathan Wrigley: A typical page builder’s UI would contain a panel at some point on the page, which would have icons, and those icons would be indicative of what the thing that you are about to drop on the page, the element, the module, whatever it is. You’d drop that onto the page and then something would immediately appear and you would then go about tweaking. You’d maybe change some numbers if it was padding or margin or font size or what have you. You could type text and change different things like background layouts and all of that. Is that broadly what Pinegrow looks like? Could you just sort of give us some indication of what the UI looks like and what we can expect? I know that’s very difficult in audio, but it’s probably important to understand what you’re getting into.
\n\n\n\n[00:15:08] Adam Lowe: It really is, and you should see the hand gestures that I’m doing right now. They make absolutely no sense to anybody. So no, you’re definitely not dragging elements onto the page like you would with something like Elementor. You’re dragging raw HTML elements, which, if you don’t have any styling on them, they look like nothing, or they just look like plain text. It’s not until you start adding CSS to it that it does anything.
\n\n\n\nSo no, you don’t have those icons on there. You don’t have that kind of friendly thing. Again, I would equate it more to what you see with the advanced page builders in the WordPress space where you’re adding a section, you’re adding a column, you know, you’re adding in a header, you’re adding a text element. You do not get those predefined components. So you’re not going to get a menu builder. You’re not going to get a carousel element that you can just drag on there. You’re not going to get an accordion element that you can just drag onto there.
\n\n\n\nPinegrow does expect that you are able to either build that yourself or find libraries that are out there that you can just grab the code from and plop that into your page. They do include some starter libraries, and blocks, and components if you’re using something like Bootstrap or Tailwind. But if you’re just doing an HTML and CSS project, then no, you’re not going to get that.
\n\n\n\n[00:16:18] Nathan Wrigley: Does Pinegrow have a community of people that have been doing things for a while in the background there? So in other words, if I was to get into this, is there a forum of some kind where I could go and see other people’s work that’s already been created? Or am I very much looking at tutorials and then I’m on my own, I’ve gotta work it out for myself?
\n\n\n\n[00:16:37] Adam Lowe: So the Pinegrow website does have a very good forum. They’re not very active on Facebook. They’ve got their own reason, basically they don’t like Facebook and, and I’m okay with that. They’re not very active on Facebook, but if you go to pinegrow.com, they do have forums on there. It’s actually forum.pinegrow.com and that’s a great place to talk to other Pinegrow users, to get directly in touch with the company themselves. And they do have a section on there where people can showcase their work.
\n\n\n\nThe other place you can go, they’ve got a product called Pinegrow Online, which probably isn’t going anywhere, but it’s actually a very, very early version of this WordPress plugin. And if you go to pinegrowonline.com, I believe it is, or if you just Google Pinegrow online, you’ll see this. And right there on the page they’ve got, I don’t know, maybe 20 projects that people had submitted that you can come in, you can look at, and you can even open up the builder right there from the website and see how they’re created.
\n\n\n\n[00:17:31] Nathan Wrigley: That’s really nice to know. Yeah, thank you for that. With a page builder, the intention is very much to build a website. You install it. You add pages. Possibly some templates for various different things, categories and so on and so forth. And at the end of it, the website is built that really is the point.
\n\n\n\nNow, it feels to me that whilst that is also the point of Pinegrow, the intention is very much to create other things. So for example, to create blocks which you may wish to export and use elsewhere. Themes, which you may wish to use and export elsewhere? Have I got that? Have I understood that right? Is this not just a tool for building websites? This is also a tool for building components, themes, blocks, and so on. Plugins for other websites, other projects. So you could use it as a, as an example, you could have a standalone Pinegrow website, where you do all the building and then you could simply export the bits and pieces that you’ve built to use on your other client projects. That might be a possible use of it?
\n\n\n\n[00:18:27] Adam Lowe: Probably not. You know, it sounds like what you’re describing might be getting again into page builder territory. So when you say building a website, there’s really two different ways that I see that. One is building a static HTML site, and that’s something where you would use a Pinegrow desktop app that just spits out generic HTML and CSS that you upload to any place.
\n\n\n\nAnd then the other would be, you know, to use something inside a WordPress, it needs to be in either a theme or a block. So that’s how you enter your content. That’s how you make your pages look like something and do certain things. So Pinegrow doesn’t let you design pages. It lets you design those themes and those blocks that you can then activate on your site and start putting content into. Does that make sense?
\n\n\n\n[00:19:09] Nathan Wrigley: Yes. I guess what I was trying to say was, if you created an array of blocks, which let’s say for example, you’re in the real estate niche or something like that, and you have a block that you’ve created in Pinegrow, that really satisfies almost everything that a real estate agent might wish to do. House pictures and pricing and so on and so forth. And it would spit out a nice display on the front end of the website. That was what I was imagining. You could then create that block, take it, export it, put it on all your other client websites and future client websites, and deploy it in that way.
\n\n\n\n[00:19:41] Adam Lowe: Yes, absolutely. And here’s where we start getting into the gray area of whether the WordPress plugin version or the desktop plugin version makes more sense. So you can do that, and you can create those block libraries and export your themes and your blocks to use anywhere you want. On the WordPress plugin version, you’re kind of limited to everything being contained on that one site to build it.
\n\n\n\nAnd, if you want to export the block and use it somewhere else, that’s great, you can do that. But then to modify that block, you’ve gotta go back to the original project that lives on your source website, let’s just call it that. So that gets a little bit cumbersome. And this is where the desktop version really comes into play because it lets you create reusable libraries.
\n\n\n\nSo you can create those libraries of components, of code, of themes. You can create those master themes that you can drop into any project. So it really speeds up the workflow. So for example, I’ve got a component library that I’ve created over time for basically everything that I need. And when I fire up Pinegrow Desktop, I just come in and with a few clicks I can drop a carousel or I can drop a menu on to someplace.
\n\n\n\nI don’t have to recreate it from scratch. I don’t have to go back to an old project and copy paste code, like I would otherwise. That’s really the benefit there, and that’s part of the reason why you end up paying a little bit more for the desktop version than you will for the WordPress version.
\n\n\n\n[00:21:03] Nathan Wrigley: I understand. So the desktop version may be more suitable for building components which you use all over the place, because that’s the place where they’re originating from. And perhaps if you’re building client websites, the WordPress plugin, and we’ll find out about the pricing shortly, is going to be suitable to install on each individual website until it’s no longer needed. Right, got it.
\n\n\n\n[00:21:20] Adam Lowe: It is. And, while you can do what you were saying on the WordPress plugin, it’s just not going to be as efficient as you would be with the desktop.
\n\n\n\n[00:21:27] Nathan Wrigley: Right. Thank you. In terms of the way that the tool has been built, I don’t know if this question will be of great interest for everybody, but it may be to some. Presumably given what it’s trying to do and the way that it’s trying to do it, it had to work fairly tightly in the, I’m doing air quotes, in the WordPress way.
\n\n\n\nIt had to stick fairly closely to the WordPress way of doing things. Is that the case? Has it been built with WordPress standards and typical ways that people would hopefully build themes and blocks, in order to achieve what it is hopefully outputting?
\n\n\n\n[00:22:03] Adam Lowe: It has been. And there are a few places where it, kind of strays from that. And, just to give you an example. WordPress says that you should not include functionality in a theme. That a theme should be your design only, that if you’re going to put something in the WordPress repository that you really need to split functionality from design.
\n\n\n\nHowever, in practice when somebody’s building a website for a client or for themselves, they’re going to combine the two because you cannot really separate the two practically. So, while you can use Pinegrow and you can create a plugin that has all your blocks in it, with all the smarts, and then a separate theme that has just your templates in there.
\n\n\n\nPractically speaking, that doesn’t make sense. And all the tutorials and all the guidance says, just put it into the theme, that’s going to be the easiest way to go. So, yes you can do it 100% the WordPress way. You can completely work it if you want, or you can use a hybrid approach.
\n\n\n\n[00:22:57] Nathan Wrigley: I have a, I have a curious question about this idea of the business going out of existence. And so, for any WordPress company, let’s say a page builder. If that company folded, then you are to some extent left in the lurch. You know, you’re hoping that somebody maintains that project and carries it on and what have you.
\n\n\n\nWith this, it presents a slightly different problem in that everything will still continue to work, but the Pinegrow editor, you would no longer be able to use, well, I guess you could use it, if WordPress didn’t change in such a way that it made it impossible to use. But you could in theory carry on editing all of the bits and pieces that you’ve got with your IDE, in a text editor if you like. That would still be possible?
\n\n\n\n[00:23:39] Adam Lowe: It is, and this is actually one of the things that drove me to Pinegrow more than anything else. If you’ve been around WordPress for any period of time, you’ve seen the problem with abandoned plugins, You’ve seen the problem with things that just stop working. As a matter of fact, I’m working on a project right now where I have, out of 52 plugins, I think 10 of them are abandoned. Two of them have been removed from the repo, and more than half of them are older than three years old, and can’t be upgraded for one reason or another. So that’s the sort of thing that I fight against on a daily basis is, all these dependencies, all this crazy stuff that’s happening.
\n\n\n\nAnd then you’ve got your page builders where, okay, the page builder’s one dependency, but then on top of the page builder, you have all these other add-ons. You’ve got frameworks, you’ve got, extra components that are being put in there. And each of those things adds just one more dependency on top of it.
\n\n\n\nOne more dependency. And if any one of those companies goes out of business, stop supporting it, has a security problem that they can’t fix or won’t fix, then you’re kind of left having to either refactor the whole website, or you’ve got a insecure website that you’re dealing with. So this is one of the big challenges that I’ve been facing over and over again.
\n\n\n\nAnd when I saw Pinegrow and saw what they were doing with WordPress, this was one of the things that really drove me to it, was that it is creating native themes and native blocks that you would create them the same way if you were doing it by hand, using VS code or any other IDE.
\n\n\n\nAnd if Pinegrow were to go out of business, that’s not a problem at all. You’ve still got those things that don’t rely on the builder at all to use or to modify. You can just go right in, change your PHP, change your blocks and, keep using it as if nothing ever happened.
\n\n\n\n[00:25:19] Nathan Wrigley: Can you think of any caveats where that’s not necessarily the case? You know, this promise has been offered several times before, and then as you’ve described, it doesn’t actually bear out when the company does go out of existence. To your knowledge, I’m guessing, because you could simply remove Pinegrow and the whole thing still just works. There are no caveats to that as far as you know, there’s no dependency of any kind whatsoever. It’s just the ability to use their UI to modify things that you would lose out on if they disappeared.
\n\n\n\n[00:25:51] Adam Lowe: I would say yes and no to that. So, yes, it really is just the dependency on their builder for making changes to it. However, there are things like Tailwind and Bootstrap and Green Sock that are extra libraries that could be dependencies if you chose to use them. So Pinegrow does let you use those frameworks, Bootstrap and Tailwind, in both the desktop version and the WordPress version.
\n\n\n\nSo if something were to happen with either of those and they no longer were supported or maintained, then yes, you would have that dependency problem. Same thing for Green Sock. And Green Sock is an animation library. It’s really a JavaScript library that lets you do all sorts of things from creating menu animations to things flying all around your screen and all sorts of silliness. It’s a very powerful piece. But again, if something happened with any of those other component libraries that you chose to use in your project, then you would run into that problem.
\n\n\n\n[00:26:44] Nathan Wrigley: Just to be clear, that’s an option in Pinegrow or that’s a necessity. In other words, you don’t need to use Tailwind, you don’t need to use Bootstrap. And obviously if your site is animation free, you’re not going to be using any of that Green Sock either. All of that’s the case if you choose not to use those things, and just write native JavaScript, native CSS, we’re all good.
\n\n\n\n[00:27:03] Adam Lowe: Yep, 100% optional.
\n\n\n\n[00:27:05] Nathan Wrigley: Yeah. That’s great. The way that blocks have been growing over time, it feels like in the last year in particular, the complexity, the number of companies getting into this space has changed quite a lot. WordPress itself offering us heaps more functionality in the things that we can do. So for example, we’ve now got, full site editing, which enables us to do things on the back end. The capabilities and the different options available to us inside of blocks, too numerous to count.
\n\n\n\nBut each and every week it seems that there’s a new bit of news about something that’s going to be coming down in the next version of WordPress, which will alter the visual experience of how we interact with blocks. Have you noticed that Pinegrow, does it update basically? Does it watch the WordPress project closely to ensure that there’s compatibility, stability with the most recent versions of WordPress?
\n\n\n\n[00:27:57] Adam Lowe: It does, and you raised an interesting point there where you talked about sorry, the block themes. Because right now Pinegrow does not have anything built in that works directly with block themes or to directly create a block theme. It still does, what are called classic themes. They are working on, some things for the block themes, but like you mentioned right now, it’s moving so fast in the WordPress space and it’s changing so often, that even if you were to install a block theme, you’d see the word beta inside of WordPress.
\n\n\n\nSo, really Pinegrow is waiting for WordPress to stabilize a little bit before they go in and really start supporting or letting you create a block theme, using some of their helpers. That’s not to say that you can’t create a block theme using Pinegrow, because I have, and I’ve got several sites that are running block themes that I created with Pinegrow. But there’s a few other manual steps that you need to take.
\n\n\n\nIn terms of blocks themselves, I’ve got a love hate relationship with blocks. I think there are pain in the butt, I think is just the most clunky way to build a website. But frankly, it, again, it’s the WordPress way. So either get on the bus or get off. There’s so many other benefits to WordPress that I’m on that bus. So I deal with it, and the blocks are changing all the time and they’re adding new things.
\n\n\n\nSo being able to do more with typography in there. Using fluid typography. And even now we have the ability to do a little bit of block locking and, content locking in there. Those are all really good things, and those were problems that I initially had turned to Pinegrow to solve. So it looks like WordPress is starting to do a little bit of that on their own. They’re still not quite there yet. So, there’s definitely room for both.
\n\n\n\n[00:29:30] Nathan Wrigley: Tell me a little bit more about that. I know that the block locking capabilities in WordPress have been improved. Well, in the last few weeks we’ve had the ability to, with a click of a button, you can lock all the, the children of a particular parent block and so on and so forth. But the, the permissions model around that is not particularly, effective. There’s a lot that needs to be engineered to make that block locking solution work effectively. Are you saying that with. Pinegrow, you’re able to lock much more down?
\n\n\n\nYou can say, okay, you have a certain role or your username is this. You can only do this, this, this, but you’ve got a different role over there and you’ve got a different username, whatever it may be. You can do a whole bunch of other things. Does it have capabilities, permissions, which exceed what you can do with blocks at the moment, with blocks designed with Pinegrow?
\n\n\n\n[00:30:16] Adam Lowe: Yes and no. So to get that granular as to, you know, role-based permissions to, for example, change a picture or, you know, user specific permissions to edit a text field. That’s the sort of thing that you may need to come in and write a little bit of custom code to do. Or write some conditionals in there. I actually haven’t tried to do that at that level, so it might be a whole lot easier than what I’m thinking. And I’d love if the Pinegrow people could just jump in and tell me, rather than me having to research it myself. Because I think there is some benefit to that.
\n\n\n\nHow I’ve used it is, just being able to define what fields are editable, and using standard role-based permissions for that sort of thing. So a lot of times, when I’m working with a client, they’ve got a marketing team that comes in and helps to find how things are going to look. But then the people that are actually editing the content, shouldn’t be able to remove a block, or they shouldn’t be able to do certain things.
\n\n\n\nThey need to adhere to certain style standards. So that’s the sort of thing where, within Pinegrow, I can define here’s the fields that you’re able to modify. Here’s the properties you’re able to modify, on a field by field basis. Whereas with WordPress, it’s kind of all or nothing.
\n\n\n\n[00:31:22] Nathan Wrigley: That’s interesting. Thank you. In the preparation for this, I watched a few of the videos that you’ve made, more recently and, it’s certainly around Pinegrow but also around other different pieces. And one of the videos that I caught sight of was one where you were looking at the accessibility options in different page builders and, and how menus, for example, were accessible or were not accessible out of the gate.
\n\n\n\nIs there anything to be said about the way that Pinegrow handles accessibility? I’m guessing the answer is, because you can do anything, you can make it as accessible as you like or not. But does it handle that kind of thing natively or is it simply the fact that it opens up the options? You can manually insert them to make anything as accessible as possible.
\n\n\n\n[00:32:07] Adam Lowe: That’s exactly it. It opens up the options for you to make it as accessible as you want to or not. Again, it’s not going to make decisions for you. And, if you go to the forums, you’ll actually see a lot of conversations around people requesting that Pinegrow do certain things by default.
\n\n\n\nBut then they come back and, Pinegrow comes back and says, Well, you know, what about this case? What about this case? What about this case? And, the decision with Pinegrow is to leave things as open as possible for you to make those decisions rather than them forcing certain things on you.
\n\n\n\nAnd it even comes down to silly stuff like, do you have a trailing backslash at the end of a URL? Do you put a no opener at the end of a link? That sort of thing. Where they really try to make it as open as possible. So, yes, for accessibility. Again, this comes back to one of the reasons that, I wouldn’t say in love with, but one of the reasons why I’ve standardized on Pinegrow is because I can build accessibility into my projects and, and accessibility’s become more of a focus of my agency over the last 18 months to two years.
\n\n\n\nSo the fact that I can come in and make a completely accessible menu is amazing. That I can create all these components in very accessible ways. Whereas before, I might have to turn to three or four different block plugins because, maybe the carousel in plugin number one is accessible, but the rest of the things aren’t.
\n\n\n\nAnd the menu in another one is accessible, but the rest of the things aren’t. So, rather than cobble together all these bits and pieces that may or may not be the way that I want to accessibility wise, I just build. The templates are out there. The information’s out there. You just need to apply it.
\n\n\n\n[00:33:38] Nathan Wrigley: Yeah, thank you. That’s really helpful. tool itself, I think we’ve established, it is for intermediate or above users I’m guessing might be a reasonable way of describing it. Now, by pure good coincidence, we’ve recorded this episode right before, like, literally right before the release from beta into a stable version of the product.
\n\n\n\nCan you give us some indication, we are recording this right at the beginning of November. If memory serves, you are going to be, well, I say you, Pinegrow are going to be actually launching the product on the 17th of November, and given the date that this podcast is going to go out, that’s probably a day or two around that date. Have I got that right? The stable version’s coming out on the 17th of November, 2022.
\n\n\n\n[00:34:25] Adam Lowe: Fingers crossed, that is going to be the date. So I don’t see any reason why they won’t hit that date. And that’s the date that Pinegrow has released me to talk about. So, uh, yes. November 17th is going to be the date that they launch it. They’re going to launch a free version as well as a paid version.
\n\n\n\n[00:34:40] Nathan Wrigley: I think it’s probably apropos to say at this point that this isn’t a product which coming out of beta, is new is it? The change log for the desktop version extends back, well, years and years and years. And like you said, most of the functionality for this is ported from the desktop version.
\n\n\n\nSo, stepping in early, you are fairly confident that the product’s going to be, well, not just labeled stable, but will be stable. You’ve had a long, long play with the beta I guess?
\n\n\n\n[00:35:10] Adam Lowe: I’ve had a long play and I think we’ve had over 30 beta releases come out since I’ve been involved. You just said it right there, is that this is a product with a long history. It goes back to 2014. And the codebase is exactly the same across all of them. It’s built on node.js. So that core is the same on Mac, Windows, Linux, desktop and WordPress. There’s no difference at all in what the builder does, how it works, the code that it spits out. So everything that you’re doing, from a builder standpoint is tried and tested, and it’s been out there in the field for quite a long time.
\n\n\n\nThe new pieces are really the ways that it interacts with WordPress from a front end standpoint. So, things like making sure that only people with the correct permissions can open a project. That two people can’t open the same project and step on each other, so that we’re not introducing security problems inside of WordPress by running the builder. That’s the kind of thing that is new. Not the builder itself, and the code that it spits out for your websites.
\n\n\n\n[00:36:10] Nathan Wrigley: I’m going to link in the show notes to the desktop version, which has been out for a long time, but I’ll also, assuming that the links are live, I will endeavor to put in the plugin version as well. Just before we round it off, I think people will want to know what the opportunities are to get in here.
\n\n\n\nMy understanding is there’s going to be two pricing tiers for the paid version, but there’ll also be a free version. Now, just to be clear, the free version isn’t going to be available on the repo, but the free version, I’m guessing, will have a limited array of functionality. Maybe you could speak about that, but then could you also just highlight the pricing for the two models as you understand it?
\n\n\n\n[00:36:48] Adam Lowe: Sure, and I’m going to talk about the free version for a minute because I think Pinegrow’s absolutely insane for what they’re doing. When I asked what I could talk about for the free version and they came back and told me, I was blown away. So you can do pretty much everything with the free version, with just a few minor exceptions.
\n\n\n\nSo, the big one is that you can’t export themes with the free version. You can only export blocks. So that’s going to be one of your biggest limitations. The other big limitation is that you cannot do what are called inner blocks. So, inside of WordPress you can create blocks within blocks within blocks, Yeah. Blockception even. You can’t do that with the free version of Pinegrow. You can create your one main block and that’s it. So you can create blocks with it, but you cannot do themes. You can’t do inner blocks. And the other part is that you cannot import and export projects, to and from the desktop.
\n\n\n\nSo that’s your other big limitation. The only one other thing that I’m going to throw out there is that the Green Sock, what they call Pinegrow interactions, is not available in the free version because of licensing restriction with Green Sock themselves. So you do have to go to a paid version to be able to use that.
\n\n\n\nOtherwise, you can use the entire builder as much as you want. You really get a feel for how it works, how to do different things. And, quite frankly, you can build a whole website with this, with no problem. It’s pretty amazing what they’re giving away for free. And I’m happy to talk about pricing too, if you guys want to get into that.
\n\n\n\n[00:38:09] Nathan Wrigley: Two models. There’s a one site model and then there’s the unlimited sites, an interesting pricing structure. One site or unlimited. Tell us the pricing around those.
\n\n\n\n[00:38:18] Adam Lowe: Yeah. So it’s going to be $49 per year for a single site, or $199 a year for unlimited sites. And the reason why it’s so interesting to me is because once you build your site, there’s no dependency on Pinegrow anymore. So theoretically you could buy a single site license and export themes and blocks to use on as many sites as you want.
\n\n\n\nYou’re just not going to want to do that because, going back and modifying and editing those things is going to become a real pain in the butt. $199 is a fantastic price point for what you’re getting here, especially for a developer who, presumably is working on client sites and getting their money back for this thing.
\n\n\n\nIn addition, they’re also going to have Black Friday deal. So it’s going to be 35% off for Black Friday, and I think that sales going to start right around the same time that they launch this plugin. That’s a bonus. And then there’s also going to be a very steep discount for people who already have the Pinegrow desktop version.
\n\n\n\nSo if you want to own both the desktop and the WordPress version, I believe you get 50% off of the Pinegrow WordPress plugin. There’s a lot of incentive here and Pinegrow’s put a lot of time and effort into the WordPress space. They definitely see this as a strategic move to get into WordPress, and they’re doing everything they can to make it easy to use Pinegrow in there.
\n\n\n\n[00:39:28] Nathan Wrigley: Just before we round off, it strikes me that we’ve missed a particular piece of the puzzle here, and it’s not something that should be ignored I think. Having watched your videos, I confess I haven’t actually opened up the tool myself, but I’ve watched quite a large amount of what you’ve done.
\n\n\n\nIt really feels like this could be a good place to increase your knowledge of WordPress and how WordPress works. If you are prepared to go through the learning curve, you’re going to be seeing what WordPress is doing, or, or at least the way that it is intending to be doing things. The HTML that it requires to make things work, and the PHP, and the functions and so on.
\n\n\n\nSo really there’s that, that we missed just the fact that it could be a good tool, should you wish to learn a bit more about WordPress. It may be that if you feel that you are a little bit below the level that is required to get up and running straight away, it might be a good way to bridge that gap as well.
\n\n\n\n[00:40:18] Adam Lowe: It really is, and I can tell you I’ve learned so much about WordPress and even CSS just from using this tool. Because it has, it’s given me that bridge to go from the page builder world to, oh my gosh, I’m sitting here in front of a blank text editor. So it gives me those tools to be able to learn it and, so then I don’t get stuck in the process.
\n\n\n\nAs a matter of fact, it’s quite interesting, Pinegrow had a project that they used the early version of this WordPress plugin for, to teach kids how to do HTML. So that’s where a lot of this came into play. That’s actually part of the reason why they even built this WordPress plugin was for their, I forget what they call it, but it’s like, HTML academy for kids or something like that. So yeah, it is a great learning platform if you’re so inclined.
\n\n\n\n[00:41:00] Nathan Wrigley: Adam, just before we round off, if people are interested in this, they can obviously go to the Pinegrow website. You, as you said, are a very interested user. You’re not affiliated with Pinegrow but nevertheless people might wish to ask you some questions and, plunder your growing knowledge about how it works and whether or not it would be a good fit for position and what they’re trying to achieve with their clients or their own website. Where could we find you best?
\n\n\n\n[00:41:25] Adam Lowe: Two different places. My website is peakperformancedigital.com, and then I’ve been doing more and more on YouTube. So if you just search for Peak Performance Digital on YouTube, you’ll find my channel there. All the videos that I’ve created, and I try to be very responsive to anybody that leaves me a comment or sends me an email.
\n\n\n\n[00:41:40] Nathan Wrigley: Adam Lowe, I appreciate you joining us on the podcast today. Thanks very much indeed.
\n\n\n\n[00:41:45] Adam Lowe: Thank you, Nathan.
\nOn the podcast today we have Adam Lowe.
\n\n\n\nAdam Lowe runs Peak Performance Digital, a small web consulting agency in Washington, DC, that specialises in providing website strategy along with custom WordPress solutions.
\n\n\n\nHe’s on the podcast today to talk about a new plugin from Pinegrow. Adam does not represent the company, but is an avid user of their products, and experienced in how they work.
\n\n\n\nThe ‘Pinegrow Web Editor’ is a desktop tool that lets you build websites with a GUI. The closest comparison would be a page builder, but this is not entirely accurate. Unlike most page builders, which require very little technical expertise, Pinegrow does require an understanding of technologies such as CSS, SASS, CSS Grid, Bootstrap and Tailwind CSS to make use of the platform. The intention of the tool is to make it possible to create complex sites, but with a close eye on the HTML and CSS that is being output.
\n\n\n\nGiven the popularity of WordPress, the Pinegrow developers have created a WordPress plugin, which is just about to be released. It’s been in closed beta, and Adam has been using it as his go-to solution for several months now.
\n\n\n\nWe talk about what the platform can do, and how it works. It’s not going to be a plugin for beginners, and there’s going to be a learning curve for those who do take the plunge. It’s intended as a bit of a bridge between novices and WordPress experts.
\n\n\n\nWe also get into a discussion about the fact that Pinegrow is intended to be a ‘no dependency’ solution. Once you’ve finished creating your theme, block or whatever else you might want to create, you can export that in a way that no longer needs Pinegrow at all.
\n\n\n\nIf you’re curious about new ways to create websites in WordPress, have a listen to the podcast and see if Pinegrow is a good fit.
\n\n\n\nMeetup.com raised some concerns with the WordPress community (and the broader community of accessibility professionals) this week after it added an accessibility overlay to its website. The overlay, powered by EqualWeb, displays a list of settings that can be toggled, ostensibly to address various accessibility needs.
\n\n\n\n\nI''m super disappointed @Meetup added an #a11y overlay.
— Amber Hinds (@heyamberhinds) November 14, 2022
Time to look into event calendars for #WPA11yMeetup. We still have to be on Meetup to get events in #WordPress admin, but we don''t have to market those pages. Has the community team ever explored Meetup alternatives? https://t.co/pVgYdI5Qs3
Accessibility overlay products are often marketed as a quick fix solution that will make a website ADA compliant and immune from legal action, when accessibility had not been built in from the beginning.
\n\n\n\nIn May 2021, accessibility advocates signed an open letter urging people not to use accessibility overlay products like AccesiBe, EqualWeb, and others. Signatories published a four-part statement that articulates the reasons why overlays are harmful:
\n\n\n\nWordPress’ Community Team uses Meetup.com to organize local and virtual meetups, as well as educational events. Accessibility practitioners consider the use of overlay products a flagrant malpractice and are calling on Meetup.com to abandon this solution in favor of addressing inaccessibility at the root of the problem.
\n\n\n\nAfter receiving some complaints, Meetup appeared to take the overlay down but reinstated it the next day. At the time of publishing. the overlay is still on the website. WordPress community organizer Angela Jin offered to contact Meetup.com on behalf of concerned community members. In the meantime, accessibility evangelist Amber Hinds suggested the Community Team explore Meetup.com alternatives and said the WordPress Accessibility Meetup will be looking into using a different events calendar.
";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, 16 Nov 2022 03:55:49 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:45;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:63:"WPTavern: WordPress.com Adds Support for New Pocket Casts Block";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=139509";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:74:"https://wptavern.com/wordpress-com-adds-support-for-new-pocket-casts-block";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:2242:"WordPress.com has expanded its library of blocks to include a new Pocket Casts block that makes it easy to embed any show or episode in the WordPress editor. The block is branded for Pocket Casts and will display a podcast player and a selection of episodes when the show URL is selected. Alternatively, users can embed a specific episode by using its episode URL.
\n\n\n\n\n\n\n\nAutomattic acquired Pocket Casts in 2021 after the app began struggling financially. At the time, Automattic’s Head of Apps, Eli Budelli, said the company would explore building deep integrations with WordPress.com and Pocket Casts by developing ways to make it easier to distribute and listen to podcasts. This new Pocket Casts block delivers on that promise with a solid integration for WordPress.
\n\n\n\nLast month, Pocket Casts open sourced its mobile apps under the Mozilla Public License, a GPL-compatible copyleft license that encourages contributors to share their modifications of the code under the same license. The code for Pocket Casts iOS and Pocket Casts Android is available on GitHub.
\n\n\n\n“We believe that podcasting can not and should not be controlled by Apple and Spotify, and instead support a diverse ecosystem of third-party clients,” the Pocket Casts team said when announcing its open source podcasting client. Users and contributors can now more easily report bugs, suggest new features, and submit pull requests.
\n\n\n\nSelf-hosted WordPress users also have access to the new Pocket Casts block if using the latest version of WordPress. The Pocket Casts embed block variation was quietly added to Gutenberg 13.6, which was one of the releases that was rolled into WordPress core in 6.1.
";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, 15 Nov 2022 22:39:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;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:46:"Post Status: WordPress in Substack’s History";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=143953";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:54:"https://poststatus.com/wordpress-in-substacks-history/";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:2144:"I wish this was a WordPress story. It should''ve been and could still be — a simple publishing platform built around freemium newsletters — and writers.
\n\n\n\nIn a way, it is a WordPress story.
\n\n\n\nBen Thompson''s Stratechery was a Substack inspiration and has always run on WordPress, I believe.
\n\n\n\nThere''s also this:
\n\n\n\n\n\n\n\n\nOur plan was to build a subscriptions management system that would plug into WordPress.
\nHamish McKenzie, Substack Co-founder and Chief Writing Officer
I recall reading years ago that an early Substack proof-of-concept or early version was built on WordPress. That seems to be true according to this post by co-founder Hamish McKenzie''s on the occasion of Substack''s fifth birthday. It''s unclear how far they went with WordPress before making Substack a proprietary project:
\n\n\n\nSubstack was built around — and for writers — so they can get paid and do great work.
\n\n\n\nFormer Economist editor Bill Bishop launched the tremendously valuable Sinocisim as Substack blog #1:
\n\n\n\n\n\n\n\nThat''s something the WordPress ecosystem distinction lacks for and about itself — WordPress writers writing about WordPress professionally and for a living.
\nThis article was published at Post Status — the community for WordPress professionals.
";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, 15 Nov 2022 22:12:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dan Knauss";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"\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:55:"WordPress.org blog: WordPress 6.1.1 Maintenance Release";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=13918";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/2022/11/wordpress-6-1-1-maintenance-release/";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:9812:"This minor release features 29 bug fixes in Core and 21 bug fixes for the block editor. WordPress 6.1.1 is a short-cycle maintenance release. You can review a summary of the key updates in this release by reading the RC1 announcement.
\n\n\n\nThe next major release will be version 6.2 planned for 2023.
\n\n\n\nIf you have sites that support automatic background updates, the update process will begin automatically.
\n\n\n\nYou can download WordPress 6.1.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”.
\n\n\n\nFor more information, check out the version 6.1.1 HelpHub documentation page.
\n\n\n\nThe WordPress 6.1.1 release was led by Jonathan Desrosiers, George Mamadashvili, and Jeffrey Paul.
\n\n\n\nWordPress 6.1.1 would not have been possible without the contributions of more than 105 people. Their asynchronous coordination to deliver several enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.
\n\n\n\n10upsimon, Aaron Jorbin, Aaron Robertshaw, Adam Silverstein, Aki Hamano, alexstine, Andrei Draganescu, Andrew Ozz, Andrew Serong, Andre, Andy Fragen, Ari Stathopoulos, azurseisme, Ben Dwyer, Bernie Reiter, Bethany Chobanian Lang, Birgit Pauli-Haack, bjorn2404, Carlos Bravo, Carolina Nymark, Clayton Collie, codesdnc, Colin Stewart, Daniel Richards, David Baumwald, David Smith, David Vongries, Dilip Bheda, Dion Hulse, Dominik Schilling, Ella, Eugene M, Felix Arntz, fpodhorsky, franzaurus, gamecreature, Gary Pendergast, George Mamadashvili, gisgeo, glendaviesnz, Innovext, ironprogrammer, Isabel Brison, James, Jan Thiel, Javier Carazo, Jb Audras, jchambo, jeffpaul, joelmadigan, Joen A., John Blackbourn, John Watkins, Jonathan Desrosiers, Jonny Harris, jsh4, Juliette Reinders Folmer, K. Adam White, kacper3355, Kai Hao, Konstantin Obenland, konyoldeath, larsmqller, Lena Morita, Leo Milo, lozula, Marco Ciampini, Marin Atanasov, Marius L. J., Matt Keys, Michal Czaplinski, Miguel Axcar, Miguel Fonseca, Mukesh Panchal, mw108, Namith Jawahar, Nick Diego, Nik Tsekouras, Nithin SreeRaj, nuvoPoint, oakesjosh, ockham, Oliver Juhas, Pascal Birchler, Paul Biron, Peter Wilson, petitphp, pkolenbr, pypwalters, ramonopoly, Riad Benguella, rjasdfiii, Robert Anderson, rodricus, Ryan Kienstra, Sarah Norris, Sergey Biryukov, stentibbing, Stephen Bernhardt, Subrata Sarkar, Sybre Waaijer, Timi Wahalahti, Timothy Jacobs, Tonya Mork, Torsten Landsiedel, and vtad.
\n\n\n\nTo get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core and #6-1-release-leads channels. Need help? Check out the Core Contributor Handbook.
";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, 15 Nov 2022 19:51:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Jeffrey Paul";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:94:"Post Status: Keeping Higher Education Website Managers’ Dream Alive While Sunsetting Edupack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=128296";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://poststatus.com/keeping-higher-education-website-managers-dream-alive-while-sunsetting-edupack/";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:4975:"Every University IT department dreams of a self-service system in which they do not have to deal with outside vendors. The dream includes a simple form that its users can fill out to generate websites from a library of templates. With Nathan Monk and Matt Lees, I cofounded a project called Edupack to realize the dream of simplified website management with a single WordPress plugin.
\n\n\n\n
A screenshot of the Edupack plugin.\n\n\n\nAfter eighteen months, Edupack is stopping work and moving in a new direction.
\n\n\n\nAfter user studies with folks from over 40 universities, including Harvard and Georgetown, I realize that Edupack cannot simplify website management with one plugin.
\n\n\n\nUniversity users have particular website needs. We would have to build thousands of templates to satisfy the many detail-focused university users before. That design work is not affordable for many Higher Ed technology teams.
\n\n\n\nThat said, Higher Ed pros should keep their dream of simplified website management alive.
\n\n\n\nI encourage most Universities to give up templated solutions and restrict “self-service” controls. Templates do not meet specific user requirements. Technology teams should focus on websites that can’t be built on WordPress.com or Squarespace. Many self-service use cases, like faculty profiles, can be satisfied with simple forms instead of access to an entire Content Management System.
\n\n\n\nAnother key to simplified website management is increased resources. Website managers should argue the importance of their role. Websites are a key touchpoint for students. They not only include vital services like Student Information Systems, but websites also establish branding. Branding is an undervalued resource. Security teams rely on branding to establish official communication and brand awareness increases the marketing potential of any institution.
\n\n\n\nOf course, Harvard has one of the most recognizable brands. They also have one of the more successful web teams I’ve seen. The Harvard Web Publishing team fields tickets for new websites. Some of their websites are delivered as templated solutions. Other websites are built to the bespoke interests of their colleagues. Every new user goes through a content accessibility training course and their support staff is trained to answer most website publishing issues. That model allows Harvard to set their own requirements instead of relying on a third-party service while giving faculty and students a vital resource for promoting university-related work.
\n\n\n\nMost institutions do not have a budget to create their in-house web agency or hire third-party vendors. That fact troubles me. My only solution to that problem is for prominent universities to open-source their work and knowledge. Groups like WP Campus help share open-source web publishing knowledge. Without paying any membership fee, administrators at small schools can participate in the active WP Campus Slack channels and attend their annual conference. The onus is on university staff to contribute their knowledge to the group.
\n\n\n\nEdupack was born because of WP Campus. Matt, Nathan, and I saw reoccurring complaints about the complexity of website management on the WP Campus Slack. After many months of work, I hope lessons from Edupack inspire ever-better solutions.
\n\n\n\n
Blake Bertucelli is simplifying website management with Edupack, while building the world’s first accessibility platform, equalify.app, and supporting independent journalism with Decubing Web Services.
\n\n\n\n\nThis article was published at Post Status — the community for WordPress professionals.
";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, 15 Nov 2022 14:15: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:17:"Blake Bertuccelli";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:49;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:84:"Do The Woo Community: Krissie VandeNoord, Building Custom Solutions with WooCommerce";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=73496";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:82:"https://dothewoo.io/krissie-vandenoord-building-custom-solutions-with-woocommerce/";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:438:"Krissie VandeNoord shares insights and experiences with WooCommerce and WordPress through her agency North UX Design.
\n>> The post Krissie VandeNoord, Building Custom Solutions with WooCommerce appeared first on Do the Woo - a WooCommerce Builder 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:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 15 Nov 2022 10:14:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Thu, 01 Dec 2022 18:52:20 GMT";s:12:"content-type";s:8:"text/xml";s:13:"last-modified";s:29:"Thu, 01 Dec 2022 18:45:29 GMT";s:4:"vary";s:15:"Accept-Encoding";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:16:"content-encoding";s:4:"gzip";s:4:"x-nc";s:9:"HIT ord 1";}}s:5:"build";s:14:"20211221010300";}', 'no'); INSERT INTO `wpa5_options` VALUES (158, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1669963940', 'no'), (159, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1669920740', 'no'), (160, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1669963940', 'no'), (161, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '', 'no'), (162, 'can_compress_scripts', '1', 'no'), (163, '_site_transient_timeout_poptags_40cd750bba9870f18aada2478b24840a', '1669931543', 'no'), (164, '_site_transient_poptags_40cd750bba9870f18aada2478b24840a', 'O:8:"stdClass":100:{s:11:"woocommerce";a:3:{s:4:"name";s:11:"woocommerce";s:4:"slug";s:11:"woocommerce";s:5:"count";i:5853;}s:6:"widget";a:3:{s:4:"name";s:6:"widget";s:4:"slug";s:6:"widget";s:5:"count";i:4804;}s:4:"post";a:3:{s:4:"name";s:4:"post";s:4:"slug";s:4:"post";s:5:"count";i:2774;}s:5:"admin";a:3:{s:4:"name";s:5:"admin";s:4:"slug";s:5:"admin";s:5:"count";i:2647;}s:5:"posts";a:3:{s:4:"name";s:5:"posts";s:4:"slug";s:5:"posts";s:5:"count";i:2043;}s:9:"shortcode";a:3:{s:4:"name";s:9:"shortcode";s:4:"slug";s:9:"shortcode";s:5:"count";i:1894;}s:8:"comments";a:3:{s:4:"name";s:8:"comments";s:4:"slug";s:8:"comments";s:5:"count";i:1893;}s:3:"seo";a:3:{s:4:"name";s:3:"seo";s:4:"slug";s:3:"seo";s:5:"count";i:1604;}s:6:"images";a:3:{s:4:"name";s:6:"images";s:4:"slug";s:6:"images";s:5:"count";i:1558;}s:5:"image";a:3:{s:4:"name";s:5:"image";s:4:"slug";s:5:"image";s:5:"count";i:1539;}s:6:"google";a:3:{s:4:"name";s:6:"google";s:4:"slug";s:6:"google";s:5:"count";i:1539;}s:7:"twitter";a:3:{s:4:"name";s:7:"twitter";s:4:"slug";s:7:"twitter";s:5:"count";i:1514;}s:8:"facebook";a:3:{s:4:"name";s:8:"facebook";s:4:"slug";s:8:"facebook";s:5:"count";i:1498;}s:9:"ecommerce";a:3:{s:4:"name";s:9:"ecommerce";s:4:"slug";s:9:"ecommerce";s:5:"count";i:1431;}s:5:"email";a:3:{s:4:"name";s:5:"email";s:4:"slug";s:5:"email";s:5:"count";i:1349;}s:7:"sidebar";a:3:{s:4:"name";s:7:"sidebar";s:4:"slug";s:7:"sidebar";s:5:"count";i:1315;}s:7:"gallery";a:3:{s:4:"name";s:7:"gallery";s:4:"slug";s:7:"gallery";s:5:"count";i:1264;}s:4:"page";a:3:{s:4:"name";s:4:"page";s:4:"slug";s:4:"page";s:5:"count";i:1174;}s:6:"social";a:3:{s:4:"name";s:6:"social";s:4:"slug";s:6:"social";s:5:"count";i:1152;}s:5:"login";a:3:{s:4:"name";s:5:"login";s:4:"slug";s:5:"login";s:5:"count";i:1139;}s:8:"security";a:3:{s:4:"name";s:8:"security";s:4:"slug";s:8:"security";s:5:"count";i:1040;}s:10:"e-commerce";a:3:{s:4:"name";s:10:"e-commerce";s:4:"slug";s:10:"e-commerce";s:5:"count";i:1009;}s:5:"video";a:3:{s:4:"name";s:5:"video";s:4:"slug";s:5:"video";s:5:"count";i:987;}s:7:"widgets";a:3:{s:4:"name";s:7:"widgets";s:4:"slug";s:7:"widgets";s:5:"count";i:959;}s:5:"links";a:3:{s:4:"name";s:5:"links";s:4:"slug";s:5:"links";s:5:"count";i:900;}s:4:"spam";a:3:{s:4:"name";s:4:"spam";s:4:"slug";s:4:"spam";s:5:"count";i:866;}s:9:"analytics";a:3:{s:4:"name";s:9:"analytics";s:4:"slug";s:9:"analytics";s:5:"count";i:860;}s:6:"slider";a:3:{s:4:"name";s:6:"slider";s:4:"slug";s:6:"slider";s:5:"count";i:857;}s:7:"content";a:3:{s:4:"name";s:7:"content";s:4:"slug";s:7:"content";s:5:"count";i:856;}s:4:"form";a:3:{s:4:"name";s:4:"form";s:4:"slug";s:4:"form";s:5:"count";i:851;}s:7:"payment";a:3:{s:4:"name";s:7:"payment";s:4:"slug";s:7:"payment";s:5:"count";i:849;}s:9:"gutenberg";a:3:{s:4:"name";s:9:"gutenberg";s:4:"slug";s:9:"gutenberg";s:5:"count";i:799;}s:5:"media";a:3:{s:4:"name";s:5:"media";s:4:"slug";s:5:"media";s:5:"count";i:786;}s:10:"buddypress";a:3:{s:4:"name";s:10:"buddypress";s:4:"slug";s:10:"buddypress";s:5:"count";i:780;}s:6:"search";a:3:{s:4:"name";s:6:"search";s:4:"slug";s:6:"search";s:5:"count";i:765;}s:6:"editor";a:3:{s:4:"name";s:6:"editor";s:4:"slug";s:6:"editor";s:5:"count";i:763;}s:5:"block";a:3:{s:4:"name";s:5:"block";s:4:"slug";s:5:"block";s:5:"count";i:750;}s:15:"payment-gateway";a:3:{s:4:"name";s:15:"payment gateway";s:4:"slug";s:15:"payment-gateway";s:5:"count";i:747;}s:3:"rss";a:3:{s:4:"name";s:3:"rss";s:4:"slug";s:3:"rss";s:5:"count";i:729;}s:5:"pages";a:3:{s:4:"name";s:5:"pages";s:4:"slug";s:5:"pages";s:5:"count";i:727;}s:4:"menu";a:3:{s:4:"name";s:4:"menu";s:4:"slug";s:4:"menu";s:5:"count";i:716;}s:12:"contact-form";a:3:{s:4:"name";s:12:"contact form";s:4:"slug";s:12:"contact-form";s:5:"count";i:706;}s:9:"elementor";a:3:{s:4:"name";s:9:"elementor";s:4:"slug";s:9:"elementor";s:5:"count";i:691;}s:5:"embed";a:3:{s:4:"name";s:5:"embed";s:4:"slug";s:5:"embed";s:5:"count";i:682;}s:8:"category";a:3:{s:4:"name";s:8:"category";s:4:"slug";s:8:"category";s:5:"count";i:679;}s:4:"feed";a:3:{s:4:"name";s:4:"feed";s:4:"slug";s:4:"feed";s:5:"count";i:678;}s:4:"ajax";a:3:{s:4:"name";s:4:"ajax";s:4:"slug";s:4:"ajax";s:5:"count";i:668;}s:6:"jquery";a:3:{s:4:"name";s:6:"jquery";s:4:"slug";s:6:"jquery";s:5:"count";i:666;}s:7:"youtube";a:3:{s:4:"name";s:7:"youtube";s:4:"slug";s:7:"youtube";s:5:"count";i:627;}s:3:"css";a:3:{s:4:"name";s:3:"css";s:4:"slug";s:3:"css";s:5:"count";i:616;}s:4:"link";a:3:{s:4:"name";s:4:"link";s:4:"slug";s:4:"link";s:5:"count";i:604;}s:10:"javascript";a:3:{s:4:"name";s:10:"javascript";s:4:"slug";s:10:"javascript";s:5:"count";i:603;}s:9:"affiliate";a:3:{s:4:"name";s:9:"affiliate";s:4:"slug";s:9:"affiliate";s:5:"count";i:602;}s:3:"api";a:3:{s:4:"name";s:3:"api";s:4:"slug";s:3:"api";s:5:"count";i:596;}s:5:"share";a:3:{s:4:"name";s:5:"share";s:4:"slug";s:5:"share";s:5:"count";i:589;}s:7:"contact";a:3:{s:4:"name";s:7:"contact";s:4:"slug";s:7:"contact";s:5:"count";i:586;}s:10:"responsive";a:3:{s:4:"name";s:10:"responsive";s:4:"slug";s:10:"responsive";s:5:"count";i:583;}s:9:"dashboard";a:3:{s:4:"name";s:9:"dashboard";s:4:"slug";s:9:"dashboard";s:5:"count";i:580;}s:5:"theme";a:3:{s:4:"name";s:5:"theme";s:4:"slug";s:5:"theme";s:5:"count";i:573;}s:7:"comment";a:3:{s:4:"name";s:7:"comment";s:4:"slug";s:7:"comment";s:5:"count";i:566;}s:3:"ads";a:3:{s:4:"name";s:3:"ads";s:4:"slug";s:3:"ads";s:5:"count";i:565;}s:6:"custom";a:3:{s:4:"name";s:6:"custom";s:4:"slug";s:6:"custom";s:5:"count";i:558;}s:9:"marketing";a:3:{s:4:"name";s:9:"marketing";s:4:"slug";s:9:"marketing";s:5:"count";i:547;}s:8:"shipping";a:3:{s:4:"name";s:8:"shipping";s:4:"slug";s:8:"shipping";s:5:"count";i:545;}s:10:"categories";a:3:{s:4:"name";s:10:"categories";s:4:"slug";s:10:"categories";s:5:"count";i:538;}s:6:"events";a:3:{s:4:"name";s:6:"events";s:4:"slug";s:6:"events";s:5:"count";i:537;}s:4:"chat";a:3:{s:4:"name";s:4:"chat";s:4:"slug";s:4:"chat";s:5:"count";i:536;}s:4:"user";a:3:{s:4:"name";s:4:"user";s:4:"slug";s:4:"user";s:5:"count";i:530;}s:6:"button";a:3:{s:4:"name";s:6:"button";s:4:"slug";s:6:"button";s:5:"count";i:524;}s:14:"contact-form-7";a:3:{s:4:"name";s:14:"contact form 7";s:4:"slug";s:14:"contact-form-7";s:5:"count";i:522;}s:5:"forms";a:3:{s:4:"name";s:5:"forms";s:4:"slug";s:5:"forms";s:5:"count";i:515;}s:5:"popup";a:3:{s:4:"name";s:5:"popup";s:4:"slug";s:5:"popup";s:5:"count";i:508;}s:6:"mobile";a:3:{s:4:"name";s:6:"mobile";s:4:"slug";s:6:"mobile";s:5:"count";i:507;}s:4:"tags";a:3:{s:4:"name";s:4:"tags";s:4:"slug";s:4:"tags";s:5:"count";i:506;}s:5:"users";a:3:{s:4:"name";s:5:"users";s:4:"slug";s:5:"users";s:5:"count";i:506;}s:8:"calendar";a:3:{s:4:"name";s:8:"calendar";s:4:"slug";s:8:"calendar";s:5:"count";i:491;}s:10:"newsletter";a:3:{s:4:"name";s:10:"newsletter";s:4:"slug";s:10:"newsletter";s:5:"count";i:471;}s:11:"performance";a:3:{s:4:"name";s:11:"performance";s:4:"slug";s:11:"performance";s:5:"count";i:464;}s:10:"navigation";a:3:{s:4:"name";s:10:"navigation";s:4:"slug";s:10:"navigation";s:5:"count";i:464;}s:6:"blocks";a:3:{s:4:"name";s:6:"blocks";s:4:"slug";s:6:"blocks";s:5:"count";i:454;}s:5:"photo";a:3:{s:4:"name";s:5:"photo";s:4:"slug";s:5:"photo";s:5:"count";i:451;}s:9:"slideshow";a:3:{s:4:"name";s:9:"slideshow";s:4:"slug";s:9:"slideshow";s:5:"count";i:448;}s:5:"stats";a:3:{s:4:"name";s:5:"stats";s:4:"slug";s:5:"stats";s:5:"count";i:443;}s:10:"statistics";a:3:{s:4:"name";s:10:"statistics";s:4:"slug";s:10:"statistics";s:5:"count";i:434;}s:12:"social-media";a:3:{s:4:"name";s:12:"social media";s:4:"slug";s:12:"social-media";s:5:"count";i:428;}s:6:"photos";a:3:{s:4:"name";s:6:"photos";s:4:"slug";s:6:"photos";s:5:"count";i:426;}s:8:"redirect";a:3:{s:4:"name";s:8:"redirect";s:4:"slug";s:8:"redirect";s:5:"count";i:421;}s:12:"notification";a:3:{s:4:"name";s:12:"notification";s:4:"slug";s:12:"notification";s:5:"count";i:417;}s:4:"news";a:3:{s:4:"name";s:4:"news";s:4:"slug";s:4:"news";s:5:"count";i:416;}s:6:"import";a:3:{s:4:"name";s:6:"import";s:4:"slug";s:6:"import";s:5:"count";i:415;}s:10:"shortcodes";a:3:{s:4:"name";s:10:"shortcodes";s:4:"slug";s:10:"shortcodes";s:5:"count";i:409;}s:8:"tracking";a:3:{s:4:"name";s:8:"tracking";s:4:"slug";s:8:"tracking";s:5:"count";i:408;}s:7:"gateway";a:3:{s:4:"name";s:7:"gateway";s:4:"slug";s:7:"gateway";s:5:"count";i:406;}s:4:"code";a:3:{s:4:"name";s:4:"code";s:4:"slug";s:4:"code";s:5:"count";i:400;}s:7:"plugins";a:3:{s:4:"name";s:7:"plugins";s:4:"slug";s:7:"plugins";s:5:"count";i:395;}s:9:"multisite";a:3:{s:4:"name";s:9:"multisite";s:4:"slug";s:9:"multisite";s:5:"count";i:394;}s:4:"meta";a:3:{s:4:"name";s:4:"meta";s:4:"slug";s:4:"meta";s:5:"count";i:389;}s:3:"url";a:3:{s:4:"name";s:3:"url";s:4:"slug";s:3:"url";s:5:"count";i:386;}s:5:"cache";a:3:{s:4:"name";s:5:"cache";s:4:"slug";s:5:"cache";s:5:"count";i:385;}s:8:"payments";a:3:{s:4:"name";s:8:"payments";s:4:"slug";s:8:"payments";s:5:"count";i:381;}}', 'no'), (166, '_site_transient_update_plugins', 'O:8:"stdClass":5:{s:12:"last_checked";i:1669920759;s:8:"response";a:1:{s:19:"akismet/akismet.php";O:8:"stdClass":12:{s:2:"id";s:21:"w.org/plugins/akismet";s:4:"slug";s:7:"akismet";s:6:"plugin";s:19:"akismet/akismet.php";s:11:"new_version";s:5:"5.0.2";s:3:"url";s:38:"https://wordpress.org/plugins/akismet/";s:7:"package";s:56:"https://downloads.wordpress.org/plugin/akismet.5.0.2.zip";s:5:"icons";a:2:{s:2:"2x";s:60:"https://ps.w.org/akismet/assets/icon-256x256.png?rev=2818463";s:2:"1x";s:60:"https://ps.w.org/akismet/assets/icon-128x128.png?rev=2818463";}s:7:"banners";a:1:{s:2:"1x";s:61:"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904";}s:11:"banners_rtl";a:0:{}s:8:"requires";s:3:"5.0";s:6:"tested";s:5:"6.1.1";s:12:"requires_php";s:3:"5.2";}}s:12:"translations";a:0:{}s:9:"no_update";a:2:{s:9:"hello.php";O:8:"stdClass":10:{s:2:"id";s:25:"w.org/plugins/hello-dolly";s:4:"slug";s:11:"hello-dolly";s:6:"plugin";s:9:"hello.php";s:11:"new_version";s:5:"1.7.2";s:3:"url";s:42:"https://wordpress.org/plugins/hello-dolly/";s:7:"package";s:60:"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip";s:5:"icons";a:2:{s:2:"2x";s:64:"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855";s:2:"1x";s:64:"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855";}s:7:"banners";a:2:{s:2:"2x";s:67:"https://ps.w.org/hello-dolly/assets/banner-1544x500.jpg?rev=2645582";s:2:"1x";s:66:"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855";}s:11:"banners_rtl";a:0:{}s:8:"requires";s:3:"4.6";}s:23:"loginizer/loginizer.php";O:8:"stdClass":10:{s:2:"id";s:23:"w.org/plugins/loginizer";s:4:"slug";s:9:"loginizer";s:6:"plugin";s:23:"loginizer/loginizer.php";s:11:"new_version";s:5:"1.7.6";s:3:"url";s:40:"https://wordpress.org/plugins/loginizer/";s:7:"package";s:52:"https://downloads.wordpress.org/plugin/loginizer.zip";s:5:"icons";a:2:{s:2:"2x";s:62:"https://ps.w.org/loginizer/assets/icon-256x256.png?rev=1381093";s:2:"1x";s:62:"https://ps.w.org/loginizer/assets/icon-128x128.png?rev=1381093";}s:7:"banners";a:2:{s:2:"2x";s:65:"https://ps.w.org/loginizer/assets/banner-1544x500.jpg?rev=2668035";s:2:"1x";s:64:"https://ps.w.org/loginizer/assets/banner-772x250.jpg?rev=2668037";}s:11:"banners_rtl";a:0:{}s:8:"requires";s:3:"3.0";}}s:7:"checked";a:4:{s:19:"akismet/akismet.php";s:5:"5.0.1";s:73:"All-In-One-WP-Migration-With-Import-master/all-in-one-wp-migration-wi.php";s:4:"6.77";s:9:"hello.php";s:5:"1.7.2";s:23:"loginizer/loginizer.php";s:5:"1.7.6";}}', 'no'), (167, 'recently_activated', 'a:0:{}', 'yes'), (168, 'ai1wm_secret_key', 'Fm0ZEBOsfhEC', 'yes'), (175, 'finished_updating_comment_type', '1', 'yes'), (176, '_site_transient_timeout_browser_a818ab359804517f2549e94c88d03c0b', '1670525697', 'no'), (177, '_site_transient_browser_a818ab359804517f2549e94c88d03c0b', 'a:10:{s:4:"name";s:6:"Chrome";s:7:"version";s:9:"108.0.0.0";s:8:"platform";s:7:"Windows";s:10:"update_url";s:29:"https://www.google.com/chrome";s:7:"img_src";s:43:"http://s.w.org/images/browsers/chrome.png?1";s:11:"img_src_ssl";s:44:"https://s.w.org/images/browsers/chrome.png?1";s:15:"current_version";s:2:"18";s:7:"upgrade";b:0;s:8:"insecure";b:0;s:6:"mobile";b:0;}', 'no'), (198, 'ai1wm_status', 'a:3:{s:4:"type";s:5:"error";s:5:"title";s:16:"Unable to import";s:7:"message";s:163:"The archive file is corrupted. Follow this article to resolve the problem.";}', 'yes'), (376, '_transient_timeout_global_styles_twentytwentythree', '1669927480', 'no'), (377, '_transient_global_styles_twentytwentythree', 'body{--wp--preset--color--black: #000000;--wp--preset--color--cyan-bluish-gray: #abb8c3;--wp--preset--color--white: #ffffff;--wp--preset--color--pale-pink: #f78da7;--wp--preset--color--vivid-red: #cf2e2e;--wp--preset--color--luminous-vivid-orange: #ff6900;--wp--preset--color--luminous-vivid-amber: #fcb900;--wp--preset--color--light-green-cyan: #7bdcb5;--wp--preset--color--vivid-green-cyan: #00d084;--wp--preset--color--pale-cyan-blue: #8ed1fc;--wp--preset--color--vivid-cyan-blue: #0693e3;--wp--preset--color--vivid-purple: #9b51e0;--wp--preset--color--base: #ffffff;--wp--preset--color--contrast: #000000;--wp--preset--color--primary: #9DFF20;--wp--preset--color--secondary: #345C00;--wp--preset--color--tertiary: #F6F6F6;--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple: linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%);--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan: linear-gradient(135deg,rgb(122,220,180) 0%,rgb(0,208,130) 100%);--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange: linear-gradient(135deg,rgba(252,185,0,1) 0%,rgba(255,105,0,1) 100%);--wp--preset--gradient--luminous-vivid-orange-to-vivid-red: linear-gradient(135deg,rgba(255,105,0,1) 0%,rgb(207,46,46) 100%);--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray: linear-gradient(135deg,rgb(238,238,238) 0%,rgb(169,184,195) 100%);--wp--preset--gradient--cool-to-warm-spectrum: linear-gradient(135deg,rgb(74,234,220) 0%,rgb(151,120,209) 20%,rgb(207,42,186) 40%,rgb(238,44,130) 60%,rgb(251,105,98) 80%,rgb(254,248,76) 100%);--wp--preset--gradient--blush-light-purple: linear-gradient(135deg,rgb(255,206,236) 0%,rgb(152,150,240) 100%);--wp--preset--gradient--blush-bordeaux: linear-gradient(135deg,rgb(254,205,165) 0%,rgb(254,45,45) 50%,rgb(107,0,62) 100%);--wp--preset--gradient--luminous-dusk: linear-gradient(135deg,rgb(255,203,112) 0%,rgb(199,81,192) 50%,rgb(65,88,208) 100%);--wp--preset--gradient--pale-ocean: linear-gradient(135deg,rgb(255,245,203) 0%,rgb(182,227,212) 50%,rgb(51,167,181) 100%);--wp--preset--gradient--electric-grass: linear-gradient(135deg,rgb(202,248,128) 0%,rgb(113,206,126) 100%);--wp--preset--gradient--midnight: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(40,116,252) 100%);--wp--preset--duotone--dark-grayscale: url(''#wp-duotone-dark-grayscale'');--wp--preset--duotone--grayscale: url(''#wp-duotone-grayscale'');--wp--preset--duotone--purple-yellow: url(''#wp-duotone-purple-yellow'');--wp--preset--duotone--blue-red: url(''#wp-duotone-blue-red'');--wp--preset--duotone--midnight: url(''#wp-duotone-midnight'');--wp--preset--duotone--magenta-yellow: url(''#wp-duotone-magenta-yellow'');--wp--preset--duotone--purple-green: url(''#wp-duotone-purple-green'');--wp--preset--duotone--blue-orange: url(''#wp-duotone-blue-orange'');--wp--preset--font-size--small: clamp(0.875rem, 0.875rem + ((1vw - 0.48rem) * 0.24), 1rem);--wp--preset--font-size--medium: clamp(1rem, 1rem + ((1vw - 0.48rem) * 0.24), 1.125rem);--wp--preset--font-size--large: clamp(1.75rem, 1.75rem + ((1vw - 0.48rem) * 0.24), 1.875rem);--wp--preset--font-size--x-large: 2.25rem;--wp--preset--font-size--xx-large: clamp(4rem, 4rem + ((1vw - 0.48rem) * 11.538), 10rem);--wp--preset--font-family--dm-sans: "DM Sans", sans-serif;--wp--preset--font-family--ibm-plex-mono: ''IBM Plex Mono'', monospace;--wp--preset--font-family--inter: "Inter", sans-serif;--wp--preset--font-family--system-font: -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",sans-serif;--wp--preset--font-family--source-serif-pro: "Source Serif Pro", serif;--wp--preset--spacing--30: clamp(1.5rem, 5vw, 2rem);--wp--preset--spacing--40: clamp(1.8rem, 1.8rem + ((1vw - 0.48rem) * 2.885), 3rem);--wp--preset--spacing--50: clamp(2.5rem, 8vw, 4.5rem);--wp--preset--spacing--60: clamp(3.75rem, 10vw, 7rem);--wp--preset--spacing--70: clamp(5rem, 5.25rem + ((1vw - 0.48rem) * 9.096), 8rem);--wp--preset--spacing--80: clamp(7rem, 14vw, 11rem);}body { margin: 0;--wp--style--global--content-size: 650px;--wp--style--global--wide-size: 1200px; }.wp-site-blocks { padding-top: var(--wp--style--root--padding-top); padding-bottom: var(--wp--style--root--padding-bottom); }.has-global-padding { padding-right: var(--wp--style--root--padding-right); padding-left: var(--wp--style--root--padding-left); }.has-global-padding :where(.has-global-padding) { padding-right: 0; padding-left: 0; }.has-global-padding > .alignfull { margin-right: calc(var(--wp--style--root--padding-right) * -1); margin-left: calc(var(--wp--style--root--padding-left) * -1); }.has-global-padding :where(.has-global-padding) > .alignfull { margin-right: 0; margin-left: 0; }.has-global-padding > .alignfull:where(:not(.has-global-padding)) > :where([class*="wp-block-"]:not(.alignfull):not([class*="__"]),p,h1,h2,h3,h4,h5,h6,ul,ol) { padding-right: var(--wp--style--root--padding-right); padding-left: var(--wp--style--root--padding-left); }.has-global-padding :where(.has-global-padding) > .alignfull:where(:not(.has-global-padding)) > :where([class*="wp-block-"]:not(.alignfull):not([class*="__"]),p,h1,h2,h3,h4,h5,h6,ul,ol) { padding-right: 0; padding-left: 0; }.wp-site-blocks > .alignleft { float: left; margin-right: 2em; }.wp-site-blocks > .alignright { float: right; margin-left: 2em; }.wp-site-blocks > .aligncenter { justify-content: center; margin-left: auto; margin-right: auto; }.wp-site-blocks > * { margin-block-start: 0; margin-block-end: 0; }.wp-site-blocks > * + * { margin-block-start: 1.5rem; }body { --wp--style--block-gap: 1.5rem; }body .is-layout-flow > *{margin-block-start: 0;margin-block-end: 0;}body .is-layout-flow > * + *{margin-block-start: 1.5rem;margin-block-end: 0;}body .is-layout-constrained > *{margin-block-start: 0;margin-block-end: 0;}body .is-layout-constrained > * + *{margin-block-start: 1.5rem;margin-block-end: 0;}body .is-layout-flex{gap: 1.5rem;}body .is-layout-flow > .alignleft{float: left;margin-inline-start: 0;margin-inline-end: 2em;}body .is-layout-flow > .alignright{float: right;margin-inline-start: 2em;margin-inline-end: 0;}body .is-layout-flow > .aligncenter{margin-left: auto !important;margin-right: auto !important;}body .is-layout-constrained > .alignleft{float: left;margin-inline-start: 0;margin-inline-end: 2em;}body .is-layout-constrained > .alignright{float: right;margin-inline-start: 2em;margin-inline-end: 0;}body .is-layout-constrained > .aligncenter{margin-left: auto !important;margin-right: auto !important;}body .is-layout-constrained > :where(:not(.alignleft):not(.alignright):not(.alignfull)){max-width: var(--wp--style--global--content-size);margin-left: auto !important;margin-right: auto !important;}body .is-layout-constrained > .alignwide{max-width: var(--wp--style--global--wide-size);}body .is-layout-flex{display: flex;}body .is-layout-flex{flex-wrap: wrap;align-items: center;}body .is-layout-flex > *{margin: 0;}body{background-color: var(--wp--preset--color--base);color: var(--wp--preset--color--contrast);font-family: var(--wp--preset--font-family--system-font);font-size: var(--wp--preset--font-size--medium);line-height: 1.6;--wp--style--root--padding-top: var(--wp--preset--spacing--40);--wp--style--root--padding-right: var(--wp--preset--spacing--30);--wp--style--root--padding-bottom: var(--wp--preset--spacing--40);--wp--style--root--padding-left: var(--wp--preset--spacing--30);}a:where(:not(.wp-element-button)){color: var(--wp--preset--color--contrast);text-decoration: underline;}a:where(:not(.wp-element-button)):hover{text-decoration: none;}a:where(:not(.wp-element-button)):focus{text-decoration: underline dashed;}a:where(:not(.wp-element-button)):active{color: var(--wp--preset--color--secondary);text-decoration: none;}h1, h2, h3, h4, h5, h6{font-weight: 400;line-height: 1.4;}h1{font-size: clamp(2.719rem, 2.719rem + ((1vw - 0.48rem) * 1.742), 3.625rem);line-height: 1.2;}h2{font-size: clamp(2.625rem, calc(2.625rem + ((1vw - 0.48rem) * 8.4135)), 3.25rem);line-height: 1.2;}h3{font-size: var(--wp--preset--font-size--x-large);}h4{font-size: var(--wp--preset--font-size--large);}h5{font-size: var(--wp--preset--font-size--medium);font-weight: 700;text-transform: uppercase;}h6{font-size: var(--wp--preset--font-size--medium);text-transform: uppercase;}.wp-element-button, .wp-block-button__link{background-color: var(--wp--preset--color--primary);border-radius: 0;border-width: 0;color: var(--wp--preset--color--contrast);font-family: inherit;font-size: inherit;line-height: inherit;padding: calc(0.667em + 2px) calc(1.333em + 2px);text-decoration: none;}.wp-element-button:visited, .wp-block-button__link:visited{color: var(--wp--preset--color--contrast);}.wp-element-button:hover, .wp-block-button__link:hover{background-color: var(--wp--preset--color--contrast);color: var(--wp--preset--color--base);}.wp-element-button:focus, .wp-block-button__link:focus{background-color: var(--wp--preset--color--contrast);color: var(--wp--preset--color--base);}.wp-element-button:active, .wp-block-button__link:active{background-color: var(--wp--preset--color--secondary);color: var(--wp--preset--color--base);}.has-black-color{color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-color{color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-color{color: var(--wp--preset--color--white) !important;}.has-pale-pink-color{color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-color{color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-color{color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-color{color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-color{color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-color{color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-color{color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-color{color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-color{color: var(--wp--preset--color--vivid-purple) !important;}.has-base-color{color: var(--wp--preset--color--base) !important;}.has-contrast-color{color: var(--wp--preset--color--contrast) !important;}.has-primary-color{color: var(--wp--preset--color--primary) !important;}.has-secondary-color{color: var(--wp--preset--color--secondary) !important;}.has-tertiary-color{color: var(--wp--preset--color--tertiary) !important;}.has-black-background-color{background-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-background-color{background-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-background-color{background-color: var(--wp--preset--color--white) !important;}.has-pale-pink-background-color{background-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-background-color{background-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-background-color{background-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-background-color{background-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-background-color{background-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-background-color{background-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-background-color{background-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-background-color{background-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-background-color{background-color: var(--wp--preset--color--vivid-purple) !important;}.has-base-background-color{background-color: var(--wp--preset--color--base) !important;}.has-contrast-background-color{background-color: var(--wp--preset--color--contrast) !important;}.has-primary-background-color{background-color: var(--wp--preset--color--primary) !important;}.has-secondary-background-color{background-color: var(--wp--preset--color--secondary) !important;}.has-tertiary-background-color{background-color: var(--wp--preset--color--tertiary) !important;}.has-black-border-color{border-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-border-color{border-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-border-color{border-color: var(--wp--preset--color--white) !important;}.has-pale-pink-border-color{border-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-border-color{border-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-border-color{border-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-border-color{border-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-border-color{border-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-border-color{border-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-border-color{border-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-border-color{border-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-border-color{border-color: var(--wp--preset--color--vivid-purple) !important;}.has-base-border-color{border-color: var(--wp--preset--color--base) !important;}.has-contrast-border-color{border-color: var(--wp--preset--color--contrast) !important;}.has-primary-border-color{border-color: var(--wp--preset--color--primary) !important;}.has-secondary-border-color{border-color: var(--wp--preset--color--secondary) !important;}.has-tertiary-border-color{border-color: var(--wp--preset--color--tertiary) !important;}.has-vivid-cyan-blue-to-vivid-purple-gradient-background{background: var(--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple) !important;}.has-light-green-cyan-to-vivid-green-cyan-gradient-background{background: var(--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan) !important;}.has-luminous-vivid-amber-to-luminous-vivid-orange-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange) !important;}.has-luminous-vivid-orange-to-vivid-red-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-orange-to-vivid-red) !important;}.has-very-light-gray-to-cyan-bluish-gray-gradient-background{background: var(--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray) !important;}.has-cool-to-warm-spectrum-gradient-background{background: var(--wp--preset--gradient--cool-to-warm-spectrum) !important;}.has-blush-light-purple-gradient-background{background: var(--wp--preset--gradient--blush-light-purple) !important;}.has-blush-bordeaux-gradient-background{background: var(--wp--preset--gradient--blush-bordeaux) !important;}.has-luminous-dusk-gradient-background{background: var(--wp--preset--gradient--luminous-dusk) !important;}.has-pale-ocean-gradient-background{background: var(--wp--preset--gradient--pale-ocean) !important;}.has-electric-grass-gradient-background{background: var(--wp--preset--gradient--electric-grass) !important;}.has-midnight-gradient-background{background: var(--wp--preset--gradient--midnight) !important;}.has-small-font-size{font-size: var(--wp--preset--font-size--small) !important;}.has-medium-font-size{font-size: var(--wp--preset--font-size--medium) !important;}.has-large-font-size{font-size: var(--wp--preset--font-size--large) !important;}.has-x-large-font-size{font-size: var(--wp--preset--font-size--x-large) !important;}.has-xx-large-font-size{font-size: var(--wp--preset--font-size--xx-large) !important;}.has-dm-sans-font-family{font-family: var(--wp--preset--font-family--dm-sans) !important;}.has-ibm-plex-mono-font-family{font-family: var(--wp--preset--font-family--ibm-plex-mono) !important;}.has-inter-font-family{font-family: var(--wp--preset--font-family--inter) !important;}.has-system-font-font-family{font-family: var(--wp--preset--font-family--system-font) !important;}.has-source-serif-pro-font-family{font-family: var(--wp--preset--font-family--source-serif-pro) !important;}', 'no'), (378, '_transient_timeout_global_styles_svg_filters_twentytwentythree', '1669927480', 'no'), (379, '_transient_global_styles_svg_filters_twentytwentythree', '', 'no'); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_postmeta` -- CREATE TABLE `wpa5_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_postmeta` -- INSERT INTO `wpa5_postmeta` VALUES (1, 2, '_wp_page_template', 'default'), (2, 3, '_wp_page_template', 'default'); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_posts` -- CREATE TABLE `wpa5_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`ID`), KEY `post_name` (`post_name`(191)), KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), KEY `post_parent` (`post_parent`), KEY `post_author` (`post_author`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_posts` -- INSERT INTO `wpa5_posts` VALUES (1, 1, '2022-12-01 18:51:47', '2022-12-01 18:51:47', '\nWelcome to WordPress. This is your first post. Edit or delete it, then start writing!
\n', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2022-12-01 18:51:47', '2022-12-01 18:51:47', '', 0, 'https://irichcomputers.com/?p=1', 0, 'post', '', 1), (2, 1, '2022-12-01 18:51:47', '2022-12-01 18:51:47', '\nThis is an example page. It''s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:
\n\n\n\n\n\n\n\nHi there! I''m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin'' caught in the rain.)
...or something like this:
\n\n\n\n\n\n\n\nThe XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.
As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!
\n', 'Sample Page', '', 'publish', 'closed', 'open', '', 'sample-page', '', '', '2022-12-01 18:51:47', '2022-12-01 18:51:47', '', 0, 'https://irichcomputers.com/?page_id=2', 0, 'page', '', 0), (3, 1, '2022-12-01 18:51:47', '2022-12-01 18:51:47', 'Suggested text: Our website address is: https://irichcomputers.com.
Suggested text: When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Suggested text: If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Suggested text: If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Suggested text: Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Suggested text: If you request a password reset, your IP address will be included in the reset email.
Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
Suggested text: If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Suggested text: Visitor comments may be checked through an automated spam detection service.
', 'Privacy Policy', '', 'draft', 'closed', 'open', '', 'privacy-policy', '', '', '2022-12-01 18:51:47', '2022-12-01 18:51:47', '', 0, 'https://irichcomputers.com/?page_id=3', 0, 'page', '', 0), (4, 1, '2022-12-01 18:52:17', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2022-12-01 18:52:17', '0000-00-00 00:00:00', '', 0, 'https://irichcomputers.com/?p=4', 0, 'post', '', 0); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_termmeta` -- CREATE TABLE `wpa5_termmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `term_id` (`term_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -------------------------------------------------------- -- -- Table structure for table `wpa5_terms` -- CREATE TABLE `wpa5_terms` ( `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `slug` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0', PRIMARY KEY (`term_id`), KEY `slug` (`slug`(191)), KEY `name` (`name`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_terms` -- INSERT INTO `wpa5_terms` VALUES (1, 'Uncategorized', 'uncategorized', 0); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_term_relationships` -- CREATE TABLE `wpa5_term_relationships` ( `object_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`object_id`,`term_taxonomy_id`), KEY `term_taxonomy_id` (`term_taxonomy_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_term_relationships` -- INSERT INTO `wpa5_term_relationships` VALUES (1, 1, 0); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_term_taxonomy` -- CREATE TABLE `wpa5_term_taxonomy` ( `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `description` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `parent` bigint(20) unsigned NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`term_taxonomy_id`), UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), KEY `taxonomy` (`taxonomy`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_term_taxonomy` -- INSERT INTO `wpa5_term_taxonomy` VALUES (1, 1, 'category', '', 0, 1); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_usermeta` -- CREATE TABLE `wpa5_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_usermeta` -- INSERT INTO `wpa5_usermeta` VALUES (1, 1, 'nickname', 'admin'), (2, 1, 'first_name', ''), (3, 1, 'last_name', ''), (4, 1, 'description', ''), (5, 1, 'rich_editing', 'true'), (6, 1, 'syntax_highlighting', 'true'), (7, 1, 'comment_shortcuts', 'false'), (8, 1, 'admin_color', 'fresh'), (9, 1, 'use_ssl', '0'), (10, 1, 'show_admin_bar_front', 'true'), (11, 1, 'locale', ''), (12, 1, 'wpa5_capabilities', 'a:1:{s:13:"administrator";b:1;}'), (13, 1, 'wpa5_user_level', '10'), (14, 1, 'dismissed_wp_pointers', ''), (15, 1, 'show_welcome_panel', '1'), (16, 1, 'session_tokens', 'a:2:{s:64:"61325fa1de4604854fd833b97719adee9b852464987e2162d3a95f545038d862";a:4:{s:10:"expiration";i:1670093536;s:2:"ip";s:13:"197.89.21.124";s:2:"ua";s:111:"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36";s:5:"login";i:1669920736;}s:64:"4ccf1397a3b2b47beb41881dd9aa916ade8907d46b355580bf625a474765aa7c";a:4:{s:10:"expiration";i:1670093696;s:2:"ip";s:13:"197.89.21.124";s:2:"ua";s:111:"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36";s:5:"login";i:1669920896;}}'), (17, 1, 'wpa5_dashboard_quick_press_last_post_id', '4'), (18, 1, 'community-events-location', 'a:1:{s:2:"ip";s:11:"197.89.21.0";}'); -- -------------------------------------------------------- -- -- Table structure for table `wpa5_users` -- CREATE TABLE `wpa5_users` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_login` varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_pass` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_nicename` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_url` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', PRIMARY KEY (`ID`), KEY `user_login_key` (`user_login`), KEY `user_nicename` (`user_nicename`), KEY `user_email` (`user_email`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wpa5_users` -- INSERT INTO `wpa5_users` VALUES (1, 'admin', '$P$BtR2QYMrzI6Vmmolm8JVAUVNzXx/ph1', 'admin', 'admin@irichcomputers.com', 'https://irichcomputers.com', '2022-12-01 18:51:47', '', 0, 'admin'); -- -------------------------------------------------------- /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
