July 2022 brought a lot of exciting announcements and proposals for the WordPress project, from an updated timeline for the WordPress 6.1 release, to design updates on WordPress.org. Read on to learn more about the latest news from the community.
\n\n\n\nMark your calendars! The WordPress 6.1 development cycle has been published along with its release team. The expected release date has been updated to November 1, 2022, to incorporate feedback received on the first proposed schedule.
\n\n\n\nIn the meantime, you can upgrade WordPress to version 6.0.1. This maintenance release became available for download on July 12, 2022, and includes several updates since WordPress 6.0 in May 2022.
\n\n\n\n\n\n\n\n\n\n\n\n\nWant to get more involved with WordPress? Join Executive Director Josepha Haden Chomphosy, as she guides you through the five stages of contribution in a recent episode of WP Briefing.
\n
Following the revamp of WordPress.org/News and the Gutenberg page, further design updates are coming to WordPress.org to create a fresh and modern user experience that reflects the future of WordPress.
\n\n\n\nThe WordPress.org home and download pages will be the next pieces to get a refreshed look and feel. The redesign project kicked off on July 8, 2022, and the development work is already underway.
\n\n\n\n\n\n\n\n\n\n\n\n\nTake a look at the design mockups and join the conversation.
\n
Three new versions of Gutenberg have been released since last month’s edition of The Month in WordPress:
\n\n\n\n\n\n\n\n\n\n\n\n\nFollow the “What’s new in Gutenberg” posts to stay on top of the latest updates.
\n
\n\n\n\n\n\n\n\n\nWP Briefing celebrated World Wide Web Day 2022 with a special episode! Tune in to hear contributors from the community reflect on how WordPress impacts their world.
\n
\n\n\n\n\n\n\n\n\nThe Community Team is calling on all meetup members and organizers to complete the 2021-2022 Annual Meetup Survey. Your feedback will help strengthen the WordPress meetup program for years to come. Please respond and help spread the word.
\n
\n\n\n\n\n\n\n\n\nJoin #WPDiversity with a free, online speaker workshop for Indian women in the WordPress community. The event will take place on September 24-25, 2022. Sign up now!
\n
Have a story that we should include in the next issue of The Month in WordPress? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this edition of The Month in WordPress: @chaion07, @laurlittle, @mysweetcate, @sereedmedia, @dansoschin, @rmartinezduque.
\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:\"13306\";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: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:69:\"WP Briefing: Episode 37: The World of WordPress on World Wide Web Day\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"https://wordpress.org/news/2022/08/episode-37-the-world-of-wordpress-on-world-wide-web-day/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 01 Aug 2022 23:15: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: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=13198\";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:128:\"Celebrating WWW Day, Josepha invites contributors from around the globe to share stories of how WordPress impacts their worlds. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/08/WP-Briefing-037.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: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:\"\";}}}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:23689:\"\nIn the thirty-seventh episode of the WordPress Briefing, WordPress users and contributors reflect on how WordPress has changed their understanding of the web as we celebrate World Wide Web Day.
\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: Beatriz Fialho
Production: Santana Inniss & Chloé Bringmann
Song: Fearless First by Kevin MacLeod
Guests:
\n\n\n\nDiverse Speaker Training Group
\n\n\n\nSupport Underrepresented Speakers at WordCamp US
\n\n\n\nCall of Speakers – WordCamp Asia 2023
\n\n\n\nRefocusing the WordPress App on Core Features
\n\n\n\nWordPress.org Homepage and Download Redesign
\n\n\n\n[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. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:39]
\n\n\n\nToday is one of my favorite niche holidays – World Wide Web Day – which serves to raise awareness about the origins of the World Wide Web project. WordPress, as part of Web 2.0, only ever had a chance to exist because the web, as we have come to know it exists. So in order to mark this nerdy day on the WP Briefing, I invited a number of community members to share a bit about how WordPress has been a part of their lives.
\n\n\n\nBut first, let’s do some introductions.
\n\n\n\n[Adam Warner 00:01:07]
\n\n\n\nMy name is Adam Warner, and I’m originally from a small town in west Michigan, now residing in Orlando, Florida.
\n\n\n\n[Alice Orrù 00:01:15]
\n\n\n\nMy name is Alice Orrù. I’m Italian. I was born in the beautiful island of Sardinia, but I’ve been living in Spain in the province of Barcelona for 10 years.
\n\n\n\n[Dee Teal 00:01:26]
\n\n\n\nMy name is Dee Teal; Dee is short for Denise. I’m from New Zealand, but I live In Melbourne.
\n\n\n\n[Femy Praseeth 00:01:33]
\n\n\n\nYeah, my name is Femy Praseeth. I was born and raised in India and now live in San Jose, California, with my family and cuddly Doodle.
\n\n\n\n[Jill Binder 00:01:41]
\n\n\n\nMy name is Jill Binder, and I’ve just moved back to Vancouver, Canada.
\n\n\n\n[Mary Job 00:01:47]
\n\n\n\nMy name is Mary Job. I’ve been using WordPress since 2015, and I’m from Nigeria. I’m from the Western part of Nigeria. Ijebu precisely.
\n\n\n\n[Oneal Rosero 00:01:57]
\n\n\n\nYes. My name is Oneal Rosero. I am from the Philippines and I’ve been using WordPress since 2007.
\n\n\n\n[Theophilus Adegbohungbe 00:02:06]
\n\n\n\nThank you. My name is Theophilus Adegbohungbe . And I’m from Ilesa, Osun State in Nigeria.
\n\n\n\n[Ugyen Dorji 00:02:14]
\n\n\n\nMy name is Ugyen Dorji and I’m from Bhutan. And I’m working with WordPress for more than five years.
\n\n\n\n[Josepha Haden Chomphosy 00:02:22]
\n\n\n\nOne of the things I enjoy the most about being part of any community is being able to see how people change and grow over time as they learn and gain confidence in their own expertise. So a favorite early question is naturally, ‘How has WordPress changed your World?’
\n\n\n\n[Alice Orrù 00:02:37]
\n\n\n\nWordPress changed my world in many ways. But, uh, starting from the moment, it allowed me to become part of a global connected and welcome community. I started using WordPress as a blogger many, many years ago, but it was in 2015 that I started working behind the scenes of WordPress with a plugin company.
\n\n\n\nAnd that was the moment when everything changed, basically, because I realized that WordPress was much more than a CMS for creating websites. It was a world full of opportunities for networking, making new friends and walking a new professional path as well.
\n\n\n\n[Ugyen Dorji 00:03:15]
\n\n\n\nDuring one interview, I was asked many questions about WordPress and although I had a basic understanding of WordPress, I struggled to give detailed answers.
\n\n\n\nAfter that interview, I resolved to develop my skills and learn as much about WordPress as possible. A few months passed and I received a call from ServeMask In, [who] had developed a plugin called All-in-One WP Migration plugin. They offered me a position which fulfilled my wish to work with WordPress full time.
\n\n\n\nAnd because of that, I am now an active contributor to the WordPress community as bread and butter, with the best career in the world.
\n\n\n\n[Theophilus Adegbohungbe 00:04:03]
\n\n\n\nIf you are very familiar with my country, Nigeria things here, it’s not as smooth as it is in other parts of the world. That is, when you are done in school in my university, you have to find means of surviving yourself. There is nothing like the government have work for you. There is nothing like you finish our institution and you get job instantly. So it’s very tough here. And, year by year, schools keep producing graduates with no companies to employ them and no government job again as well.
\n\n\n\nSo I personally, I was able to gain freedom from this with the help of WordPress.
\n\n\n\n[Femy Praseeth 00:04:51]
\n\n\n\nWordPress completely changed my work life. I started working independently. I started freelancing with agencies and designers and, uh, building websites from their web designs. And this was around the time my son was born. Actually, he was in elementary school and I think this was around 2014 or so. I started working remotely when remote was not even a thing.
\n\n\n\nAnd there were very few companies that let you work from home and remote was not a mainstream thing at all, but with WordPress, I could set my own working hours while my son was in school.
\n\n\n\n[Josepha Haden Chomphosy 00:05:29]
\n\n\n\nAnd of course, my preferred follow-up question of, ‘How did you hear about us?’ or ‘How did you connect to this global community?’
\n\n\n\n[Oneal Rosero 00:05:36]
\n\n\n\nYes, actually what I love about WordPress is that it’s a community. It’s not a business. It’s not a company. It’s a community. It’s a community that’s always ready to help support, teach and encourage people. That’s how I felt when I joined the community. There’s always somebody who has your back.
\n\n\n\nThere’s always somebody who’s going to guide you. There’s always an expert who will take your hand and lead you into the beauty that is WordPress.
\n\n\n\n[Adam Warner 00:06:05]
\n\n\n\nThe way that I connect with the global community these days are one, of course, is .org Slack. Another of course is Twitter as there’s a very active WordPress community there.
\n\n\n\nAnd then with WordCamps all over the globe. I’m lucky enough to have been able to travel to several hundred WordCamps through the years in the US and abroad. And that’s one of the most rewarding parts is meeting people from all over the world and you see really how small and the world really is and how similar we really all are.
\n\n\n\n[Theophilus Adegbohungbe 00:06:39]
\n\n\n\nSo, not until 2020. I don’t know if you know this lady, a very vibrant lady in WordPress. She’s from Nigeria; her name is Mary Job, and she’s really promoting WordPress here. So it was through her that I got to know about the community. Yes.
\n\n\n\n[Jill Binder 00:06:54]
\n\n\n\nMy work is the global WordPress community. So we hold our three programs for the global WordPress community, and we are always trying to reach more and more countries. For quite a while, it was very North America-heavy, and then I made some efforts to expand. And it’s very exciting that this year, some contributors in our team have actually launched an Asia Pacific branch of our group.
\n\n\n\nAnd so we have two meetings every other week where we have the America/Europe and the APAC, and we’ve also been able to reach other countries as well, but we typically reach something like between 20 and 50 countries a year, depending on the year. So a hundred percent global. Yes.
\n\n\n\n[Josepha Haden Chomphosy 00:07:39]
\n\n\n\nHow has WordPress, either the CMS or the project, made you feel more connected? And are there any surprising connections that came from WordPress?
\n\n\n\n[Dee Teal 00:07:47]
\n\n\n\nI guess the surprising connections I think that have come from WordPress have been the fact that I feel like I’ve got friends all over the world. And a lot of those have come out of community involvement and from contributing. That I could go to a, a meetup pretty much anywhere in the world and probably find somebody I know, or at least a second degree connection of somebody that I haven’t, you know, that I might not have met, but know somebody that I know. And certainly that happens fairly regularly.
\n\n\n\n[Mary Job 00:08:13]
\n\n\n\nWordPress. The WordPress project, the community, has made me feel connected in a huge way, because I am literally surrounded by everything WordPress. So I like how, when you meet somebody who does WordPress, there’s this instant, ‘Oh, we’re brothers,’ or ‘Oh, we’re sisters!’ You know? There’s that feeling? That’s how I feel.
\n\n\n\nSo when I see somebody who does WordPress, as I do, I’m like, ‘Oh yeah, we’re, kin.’ You know? We are family. That’s how I feel when I meet people who do WordPress. And I’ve met quite a number of people who do WordPress from like around the world. Like I have a friend here, he’s from the Benin Republic, and we host started a dinner on Friday night and one of my guests was asking me, ‘How did you guys meet?’
\n\n\n\nI was like, ‘Oh yeah, we work in the same WordPress ecosystem.’ He attended our WordCamp, we became friends, and we just literally became really good friends. So I have tons of people that I’ve met like that I hold in high esteem.
\n\n\n\n[Ugyen Dorji 00:09:12]
\n\n\n\nWordPress Meetups are the seeds that lead to the growth of WordPress communities. WordCamp is a platform for plugin and theme developers to meet WordPress users and website developers. It’s a great environment where many incredible discussions about WordPress takes place. With each WordCamp there is a “tribe” meeting, where I think people [can] get more connected. It’s a fantastic opportunity for aspiring computer engineers, generators and get to showcase their talent and meet each other.
\n\n\n\n[Alice Orrù 00:09:51]
\n\n\n\nOn the project level, it has given me the opportunity to feel like an active part of a global project. The idea that I can give my contribution to making the web a better place – it’s amazing. And I do so with the Translation team, so making WordPress accessible to all the people that use the core plugins and themes in Italian, and prefer to do that in Italian.
\n\n\n\n[Josepha Haden Chomphosy 00:10:18]
\n\n\n\nWhat area of the WordPress world is most important to you?
\n\n\n\n[Jill Binder 00:10:21]
\n\n\n\nI have a little bit of a passion for diversity in tech and diversity in WordPress, specifically around events. And so, here’s a chance to name the three programs that we’ve been working on this year. So as mentioned a few times, we have our Diverse Speaker Workshop that helps people go from not even having the thought that people could step up on stage.
\n\n\n\nAnd then the second program is because of the pandemic. There was no longer the straight path from taking our workshop to speaking, because we used to hold them or people used to hold them for their WordCamps and meetups. And so it was like, okay, you’ve taken. Apply for our next WordCamp or meetup. But during the pandemic, that wasn’t a thing.
\n\n\n\nSo we have this amazing channel that we welcome everyone to join, allies and people from underrepresented groups who are interested in speaking or interested in supporting people and speaking. And that’s the Diverse Speaker channel diverse-speaker-support channel on the Make WordPress slack.
\n\n\n\nAnd the third program is, and we, we went through a name change recently. So I’ll try to remember the new change it’s Organizing Inclusive and Diverse WordPress Events. And this is for WordCamp and meetup organizers to learn. We’ve learned over the last couple years, how important it is to create inclusive spaces and be good allies.
\n\n\n\nBut how do we actually do that? And a few of us created a very action oriented workshop in 2019 for WCUS, and that is now the basis of the work that we are bringing to people and people are loving it.. We’ve had people report a 40%, self-report 40%, increase in feeling prepared to create an inclusive event from before and after taking that workshop, which is super cool.
\n\n\n\nYeah. So, that’s my passion.
\n\n\n\n[Oneal Rosero 00:12:13]
\n\n\n\nI really love helping the WP Diversity team. I love running the workshops. I love running the workshops for myself, because I used to do training for software back before the pandemic. I used to train up to a thousand people a year in person, sometimes like 500 people in a room at once.
\n\n\n\nBut of course I had to shift. I had to pivot to online training, which is what the training team has brought for me. And the focus on the diversity. I like running the workshops. I like running workshops for different groups, different countries, because it’s nice to meet new people. It’s nice to hear about their culture, about the limitations that people have in Africa with connectivity.
\n\n\n\nSo they, they resort to using WhatsApp on their phone in order to do a meetup. That’s how they do their, their meetings, their discussions. It’s unlike other countries where we can do video calls. They have to use their mobile phones because connectivity isn’t accessible.
\n\n\n\nPlaces like in the Philippines that get affected when it starts to rain a little bit, we lose our internet. So we have backups and our backups have backups. So there are many things that you learn that are different when you’re living in the city, when you’re living in the provinces, in the country. So it’s so many things that you learn about people and how they’re able to adapt.
\n\n\n\n[Adam Warner 00:13:35]
\n\n\n\nEnabling end users to reach their goals. And whether that means participating in contributing to the software, to the Core software itself, in terms of UI/UX usability. That can include participating in the community and sharing your knowledge proactively with users who may be new to the platform, or have used WordPress for a while, but now want to step up their game, get a little deeper into using their websites as a tool for growth, for whatever business that they’re in. So, I mean, overall, the, the most important part of the WordPress world to me are the end users. And, you know, there, there is this quote unquote inner circle of WordPress community people. People who are involved in .org, people who contribute to the software, people who contribute to the 20 plus make.wordpress.org teams.
\n\n\n\nThose we have to keep in mind, are not the average user by and far. They are not the typical user that hears the word WordPress and then goes out and searches it and then has to figure out how to use it. So I think user experience is probably the most important part for me and making sure that any of that innate knowledge that we have in that inner circle of WordPress because many of us have been using it for so long, keeping in mind that is not the norm. And it’s not the scale at which WordPress is used and, and making sure we translate complex concepts down to a layperson’s terms that might not be as familiar.
\n\n\n\n[Josepha Haden Chomphosy 00:15:17]
\n\n\n\nOne of the things that I have always found so fascinating about the web and WordPress’ role in it is how it has made the world simultaneously smaller and bigger. By giving voices to the voiceless we help each other find our community niches regardless of where they are in the world. Some of your closest friends could be people you would never meet in your own neighborhood. Well, let’s hear what some of our community members had to say about that.
\n\n\n\n[Dee Tea 00:15:42]
\n\n\n\nI think the thing that has been most empowering is, is coming into the project either in terms of contributing time and efforts to the community, which is where most of my contribution has been – has always been about this is a really cool thing, and I really want to build this.
\n\n\n\nAnd so I’ll put my time and efforts into building WordPress. Not for me, but because I see its value and I see its community and I see that the contribution that it’s making to the world and I, and that’s really important. But finding that on the other side of that was a huge amount of personal benefit for me in my career, in the friendships that I’ve made.
\n\n\n\nBut I feel like if I had been approaching the community with, I want a better career, I wanna meet all of these people and I want, and I want all of this. From, “I want” for me, instead of, I want for this project, for the community and effectively for the world with that, you know, that whole democratized, the democratizing of publishing is this thing that serves the world.
\n\n\n\nI think that’s been the key for me is that I absolutely have reaped amazing benefits from it, but it came out of that sense of, I see this value here and I want to contribute to that because it’s gonna have value, not just for me, but for a whole slew of people. And so, uh, you know, for much, much bigger impact than just on me.
\n\n\n\nAnd so I think that’s the important thing for me is that sense of, if you approach it with that attitude of what can I do to help? It’s amazing what you will find yourself helped with in return.
\n\n\n\n[Josepha Haden Chomphosy 00:17:24]
\n\n\n\nI hope that you enjoyed this tour of WordPress in the World Wide Web. I want to share a big thank you to all of the folks who contributed to our little WordPress Briefing celebration of World Wide Web Day today.
\n\n\n\nAnd that brings us now to our small list of big things. So firstly, we’ve got a couple of updates from our upcoming flagship events. WordCamp US has announced a speaker support fund specifically for historically underrepresented speakers at the event. You can donate to the fund on the page if you’d like, and there are also directions on how to request support, if you are part of an underrepresented group.
\n\n\n\nFrom the folks over at WordCamp Asia, the call for speakers is live. That’s taking place in February, 2023. But it’s never too early to brush up those presentations and get them submitted.
\n\n\n\nNext big thing is that there are some changes coming to the WordPress mobile app. A lot of the Jetpack functionality will be removed from it, so this is going to have a little bit of an effect on daily users of the app, but it will also have an effect on regular contributors. I’ll have a link to the full write up in the show notes so that you don’t have to guess or hold it all in your memory.
\n\n\n\nAnd finally, this excellent design that you see on wordpress.org/news is finally making its way out to the next parts of the wordpress.org website. Before you know, it, there will be a fresh looking homepage as well as few other pages and then… to infinity and beyond (or something like that).
\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 next up I’ll be taking just a mid-year break from the podcast. And so the next time that I actually see you again, will be in September.
\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:\"13198\";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:72:\"\n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"People of WordPress: Carla Doria\";s: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/07/people-of-wordpress-carla-doria/\";s: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, 31 Jul 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=13201\";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:324:\"In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature Carla Doria, a customer support specialist from South America on how WordPress opened up a new world for her, and gave her the ability to […]\";s: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:12021:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature Carla Doria, a customer support specialist from South America on how WordPress opened up a new world for her, and gave her the ability to help the local community.
\n\n\n\nFor Carla, working with WordPress is a vital part of her life. It gave her a career and a community, in which she she would organize the first WordCamp in her city, Cochabamba, and the first in Bolivia.
\n\n\n\nCarla studied industrial engineering and has a master’s degree in environmental studies.
Her first experience with WordPress was when she decided to start a small business designing and selling cushions and bedclothes. While Carla sat in the small store she had rented, hoping that people stopping at the shop windows would step in to buy something, she decided she needed to create a website.
Carla had no budget to hire somebody, but she felt confident she could learn things on her own.
\n\n\n\n\n\n\n\n“Learning to use WordPress requires no code skills or a technical background. It needs an adventurous and playful spirit.”
Carla Doria
She had always been studious, and decided she would figure out how to build a website herself. Carla ended up building a simple blog with WordPress. At the time, she didn’t even have a budget to buy a custom domain, so she used a free subdomain.
“Learning to use WordPress is easy. It requires no code skills or a technical background at all. It only needs an adventurous and playful spirit,” said Carla
There were no profits, and any income mainly went to pay the store’s rent. At the time, her previous company contacted her for a job opening that matched her profile. Carla needed that income and decided to closed the store and forget about being an entrepreneur.
\n\n\n\nBack in employee mode, Carla started her new job as a technical writer for a software development company. Since Carla had completed her master’s degree in the UK, she was proficient in English. Her close affinity for computers and technology made it easy for her to translate complex software jargon into simple tutorial steps.
\n\n\n\nAs Carla got more interested in technical writing and started to improve her writing skills. This reconnected her with her previous enthusiasm for writing, and she decided to channel that interest into a blog.
\n\n\n\nCreating her blog helped her become more familiar with WordPress and building websites. In 2015, Carla blogged about writing, her thoughts, book reviews, and everything that came to mind.
\n\n\n\nThrough looking for answers to specific issues using her WordPress blog, Carla found the support forums a useful place to go. Soon she realized that she could also help answer other people’s questions.
\n\n\n\nCarla began checking the forums as a hobby. She liked that she was able to help people and learn more while doing so.
\n\n\n\nInstead of surfing social media during her work breaks, Carla focused on checking the WordPress forums. Through this she learnt about a support job in one of the global firms.
\n\n\n\nShe felt the job was made for her and was excited to support people in building their websites with WordPress. The role offered the possibility to work remotely and travel while still working.
\n\n\n\nAfter three years as a technical writer, her career felt stuck. She was certain she did not want to return to any job related to industrial engineering.
\n\n\n\nCarla did not get through the selection process the first time. But after nearly 18 months between three applications and learning HTML and CSS, Carla finally secured a support job in 2016. With this job, WordPress became her main source of income.
\n\n\n\nOn the job, Carla learned about the WordPress communities around the world and WordCamps. But when somebody asked about the WordPress community where Carla lived, she didn’t know what to say. Was there a community?
\n\n\n\nShe discovered no local group existed, so she researched what was needed to setup a meetup. Carla discussed the idea with others, but hesitated as she thought it would require an expert WordPress developer to organize.
\n\n\n\nBut after trying to gauge interest, Carla realized that the only way to find community members was to start a community. In 2017, the WordPress community in Cochabamba was born.
\n\n\n\nThe group has had ups and downs, probably similar to any other community. Although Cochabamba is not a big city, they had issues finding a location that was free and available to anyone who wanted to join. People came with different levels of knowledge, from people with vast experience with WordPress to people with no experience but who wanted to learn.
\n\n\n\nThe community grew during the pandemic, as meetups went online and people from other cities in Bolivia were able to attend. After restrictions were lifted, there was a lot of excitement amongst members to meet each other in person.
\n\n\n\nThe community also helped Carla to develop a new skill in public speaking. She applied to be a speaker at WordCamp Mexico 2019 and 2020, WordCamp Guayaquil 2019, and WordCamp Colombia in 2020. Her confidence grew while she enjoyed connecting with other communities and meeting people who were on similar pathways. Not all of them were developers, as she had presumed. Many, like her, started out as bloggers.
\n\n\n\nFinally, after three years, Carla applied to organize her first WordCamp in 2021 in Cochabamba. She had never imagined organizing any WordCamp, and through this having the experience to talk to sponsors and contact companies, and lead a group of people with different talents and backgrounds. Carla felt she had learnt so much from the experience.
\n\n\n\nThanks to WordPress, Carla found a job she enjoyed, was able to work remotely, and help build something in her community to help people learn skills and find career opportunities.
\n\n\n\nCarla feels grateful for all she has been able to do thanks to WordPress. She said: “WordPress has led me to find good jobs. It also has allowed me to contribute to a community of friends that love learning about WordPress.”
\n\n\n\n\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Alison Rothwell (@wpfiddlybits), Abha Thakor (@webcommsat), Larissa Murillo (@lmurillom), Meher Bala (@meher), Chloe Bringmann (@cbringmann), and Surendra Thakor (@sthakor) for work on this feature, and to all the contributors who helped with the series recently. Thank you too to Carla Doria (@carlisdm) for sharing her experiences.
\n\n\n\nThank you to Josepha Haden (@chantaboune) and Topher DeRosia (@topher1kenobe) for their support of the People of WordPress series.
\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
\nIn the thirty-sixth episode of the WordPress Briefing, Josepha Haden Chomphosy revisits the Beginner’s Guide to Contributions to 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: Beatriz Fialho
Production: Santana Inniss
Song: Fearless First by Kevin MacLeod
[Josepha Haden Chomphosy 00:00:10]
\n\n\n\nHello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy.
\n\n\n\nHere we go.
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nWordPress is an open source software project and, like many other open source software projects, has an entire community of people who show up to help improve it however they can. Most of you probably use WordPress every day in some way. And I’m going to assume that since you listen to this podcast, you’re also interested in how this all works.
\n\n\n\nOne of the things I mention practically every episode is that WordPress works and continues to work because of generous contributions from people all around the world. I consider my work with WordPress to be my way of giving back for everything that this software enabled me and my family to do. But I once was a first-time contributor, and I remember what it felt like before I knew everything.
\n\n\n\nI felt like it moved at the speed of light and that I could never tell what to do now, let alone what to do next. And that everyone around me basically already knew everything. And if you are feeling that way right now, I encourage you to take a big deep breath [breathe] and let me help you get started.
\n\n\n\n[Josepha Haden Chomphosy 00:01:43]
\n\n\n\nI’m a roadmap sort of person. So I’m going to start by sharing the stages I’ve observed for folks who are contributing to open source. That way, you can tell where you are right now, which spoiler alert is probably a bit further along than you realize. Then I’ll give you some questions you can ask yourself for each stage to figure out what is a good fit for you. Think of it as a guided exploration.
\n\n\n\nAll right, the five stages. So these are they:
\n\n\n\n[Josepha Haden Chomphosy 00:03:08]
\n\n\n\nBefore we get any further, there are four important things to remember about those stages.
\n\n\n\nThe first thing to remember is that there is no set time between any of those stages. You can start in one and then three years later go to the next one, or you can start in one and go into the next stage tomorrow. The next thing to know is that each stage builds on the one before it. In my observation, anytime I have seen a contributor who feels like they’re really struggling, it’s because they skipped a stage in there, which really causes some trouble for them.
\n\n\n\nThe next thing to remember is that not everyone will make it through these stages, which is okay. The majority of the community stops at three. Most contributors stop at four. And that is perfectly fine. That is expected. That is normal and completely in line with what we expect from contribution.
\n\n\n\nUh, and the final thing to remember about that list of the phases is that very few people make it into that leadership stage. If we assume, like I do, that 1% of the people who are using WordPress also show up and contribute back to WordPress, then it’s kind of safe to assume also that about 1% of those people who have shown up to contribute to WordPress are moving into a space where they feel like they’re willing to take responsibility for making sure things get done in WordPress.
\n\n\n\n[Josepha Haden Chomphosy 00:04:31]
\n\n\n\nLike we all collectively feel responsible for WordPress’s success, but in that leadership area, you’re kind of taking responsibility for 40% of the web or whatever’s going on there. And not a lot of people make it there, and that is completely fine, too. So that’s our basic terminology today. Those are the caveats that go with our basic terminology.
\n\n\n\nMost difficulties that arise for new contributors happen because a stage got skipped somewhere along the way. It’s almost never intentional, but from what I’ve observed, that’s what makes it really difficult to get started and what makes it difficult to keep going once you’ve kind of already gotten in there.
\n\n\n\nSo, all right. Big breath, folks with me again [breathe]. Alright, it’s guided exploration time.
\n\n\n\nFirst phase, the connecting phase. Remember, this is where you’ve just learned the community exists, people are talking about it, you don’t know much more. The first step for you is asking yourself what it is you could do. Or if there’s a project out there that looks particularly interesting.
\n\n\n\n[Josepha Haden Chomphosy 00:05:36]
\n\n\n\nSo you can ask yourself questions, like, am I a writer? And if I am a writer, do I write technical or prose. The other thing you can ask is, am I a PHP developer, a JavaScript developer, Python, Go; which language am I writing in because I find it most beautiful. Another thing you can ask yourself is, am I a teacher or a mentor, or do I just generally like to be a mighty helper? And I like to make sure that things keep running.
\n\n\n\nSo once you’ve asked yourself those things, it’s on to phase two, the understanding phase. This is when you’re looking around at this new-to-you community to see what is happening where. So you take a look at the teams that are around, you think about whatever it was you said you were good at in the last question and you look at which teams might be a good fit.
\n\n\n\nSo if you said that you’re a good technical writer, then Docs probably is for you. Have you been training others to use WordPress for years? Then you might wanna look into Training. There are a lot of other things, obviously, like if you think you’re good at working with code PHP or JavaScript, you’re probably gonna end up in Core.
\n\n\n\n[Josepha Haden Chomphosy 00:06:46]
\n\n\n\nIf you are particularly good at any of the other tech stacks that we have around in our Trac area or an Openverse, then that’s where you’ll land over there. You have design options. Like if design is really your thing, we have a Design team, but we also have a Themes team. There are plenty of places that you can land depending on what it is that you feel like you are the best at and could really help the WordPress project. And so that’s your phase two.
\n\n\n\nNow that you have gotten a good guess at a team, we’re gonna swing through to phase three, which is the engaging phase. This is the phase that is the scariest for most people, but it’s okay. I am here for you. I am here for you in this podcast. So you have figured out what you want to do in order to contribute, and you’ve got a sense for the team that looks right. There are two things that you do next.
\n\n\n\n[Josepha Haden Chomphosy 00:07:34]
\n\n\n\nOne is that you can go to a meeting. There are many kinds of meetings. There are team meetings, bug scrubs, and testing sessions, but they’re all in Slack, which means that you can attend one from anywhere. When they kick off, you wave, you introduce yourself, you let everybody know that you’re there and you’re observing. Folks will welcome you and just kind of give you some concept of what they’re working on. Easy as that. You’ve done your first time meeting attendance.
\n\n\n\nAnother good option is to keep an eye out for specific events. Some of those events happen online, like Global Translation Day. But also some of them happen in person like, Meetups or WordCamps. And there again, you show up, you wave, you introduce yourself, see if you can make a connection or two, let people know that you’re new and you’re just trying to figure out where you are and what you wanna do.
\n\n\n\nIf you’ve made it now, all the way to phase four, the performing phase, then give yourself a little pat on the back! Figuring out where you want to go and who your friendly faces are is the biggest challenge when you get started. So congratulations!
\n\n\n\n[Josepha Haden Chomphosy 00:08:37]
\n\n\n\nPhase four is the phase where you’ve decided you’re brave enough to volunteer – to do some contribution. You’re volunteering your time. That’s where you are now. So oddly enough, you start this phase by assigning yourself something, assigning yourself, a task. This seems counterintuitive.
\n\n\n\nThere’s this feeling that you can’t say that you’re gonna do something. That you can’t just assign something to yourself and say that you’re gonna do it. But in open source projects, you always can. You find a task where you’re comfortable, and you just mention that you would like to give it a try while the team is having their weekly meeting. And it’s simple as that. And not big things either. Like organizing an event or maintaining a component, those are probably too big for your first time around.
\n\n\n\nI’m talking things like, ‘I will test that patch that you mentioned in the meeting.’ Or ‘I will review the docs and make sure that they’re up to date with the most recent release.’ Or ‘I can help run meetings for the next release.’
\n\n\n\n[Josepha Haden Chomphosy 00:09:40]
\n\n\n\nAnd then you have phase five, where you just repeat phase four until you are leading something! And I don’t mean leading in the 1950s sort of way, where you have like a corner office and you’re ordering people around. I mean, in the warm, inviting millennial way where you’re leading by inspiring people to do something or you’re leading because you make sure that the meeting happens every single week.
\n\n\n\nOr you’re leading because you added screenshots to tickets that needed testing and so you moved something forward in a way that was helpful. Easy peasy. You can go to your first contributor today or a WordPress Slack meeting and just be a contributor by the time you leave, right? You might feel like ‘easy as that isn’t quite the right set of words right there. And as a matter of fact, you might be thinking to yourself, this woman is just plain wrong. It could not possibly be that easy. And I agree. It really isn’t literally quote-unquote just that easy. Just like handing someone a notebook and a pen will not instantly make them an award-winning novelist, handing someone a wordpress.org profile and credentials to Slack won’t instantly make them a contributor.
\n\n\n\n[Josepha Haden Chomphosy 00:10:46]
\n\n\n\nFor both of those examples, what makes someone good is the ability to try and fail and still be encouraged to try again. So if it’s been a while since you contributed and you’re thinking about returning, or if you’ve been listening to me for a while and you’re ready to give this contribution thing a try, I hope this helps you to feel brave enough to try and brave enough to fail.
\n\n\n\nAnd I encourage you to be brave enough to try again.
\n\n\n\n[Josepha Haden Chomphosy 00:11:20]
\n\n\n\nLet’s take a look at our small list of big things. My friends, we have a Performance team. This team has been a working group for a long time and is focused on some deep, inner workings of WordPress and its surrounding ecosystem to make sure that we are as fast and slick as possible. You can check them out on make.wordpress.org/performance, their brand new site, and see when they’re meeting, what they’re aiming to get into the WordPress 6.1 release, and if that’s something that you would like to contribute to.
\n\n\n\nThe second thing is that there’s a brand new call out for testing. This time it’s focused on templates and retroactively applying them to an entire category of posts. So it’s a little bit workflow testing, a little bit technology testing, and we could really use your help in bug hunting for both of those things.
\n\n\n\nAnd the final thing is that you know since contribution is obviously the focus of today’s podcast, we are looking for table leads for WordCamp US’ contributor day that’s coming up in September. There’s a whole blog post about it, I’ll link to it in the show notes so that you’ll have all the info and can raise your hand if you want.
\n\n\n\n[Josepha Haden Chomphosy 00:12:25]
\n\n\n\nAnd speaking of things that I’ll have in the show notes, I also am going to put like a contributor quizlet guide thing. If the guided, figuring out of the teams in the phase two section, if that didn’t make any sense to you and you just need something to direct you specifically to potential teams, I’m gonna link to the contributor kind of sorting hat quiz that came out with WordCamp Europe. And that should help you work your way through phase two and get ready for phase three if that is where the spirit takes you.
\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:\"13162\";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: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.0.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/07/wordpress-6-0-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, 12 Jul 2022 16:58:14 +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.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:\"\";}i:2;a:5:{s:4:\"data\";s:5:\"6.0.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=13138\";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:236:\"WordPress 6.0.1 is now available for download. This maintenance release features several updates since the release of WordPress 6.0 in May 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:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5452:\"\nThis maintenance release features 13 bug fixes in Core and 18 bug fixes for the Block Editor. WordPress 6.0.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.1 planned for later in 2022.
\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.0.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.0.1 HelpHub documentation page.
\n\n\n\nThe WordPress 6.0.1 release is led by @sergeybiryukov and @zieladam.
\n\n\n\nWordPress 6.0.1 would not have been possible without the contributions of more than 50 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\nAdam Zielinski, Addie, Adil Öztaşer, Andrew Serong, annezazu, Bernie Reiter, Carlos Bravo, Carolina Nymark, Channing Ritter, Colin Stewart, Clement Boirie, Daniel Iser, denishua, Dion Hulse, Erik Betshammar, Gabriel Rose, George Mamadashvili, George Stephanis, Glen Davies, Grant M. Kinney, Greg Ziółkowski, ironprogrammer, James Koster, Jb Audras, jnz31, Jonathan Desrosiers, Jonny Harris, Kelly Choyce-Dwan, Knut Sparhell, Luis Herranz, Maggie Cabrera, manfcarlo, Manzur Ahammed, Matias Ventura, Michal Czaplinski, Miguel Fonseca, Mukesh Panchal, navigatrum, Nick Diego, Nik Tsekouras, Pascal Birchler, Peter Wilson, Presskopp, Ramon James Dodd, Ravikumar Patel, Riad Benguella, Sami Keijonen, Sergey Biryukov, Timothy Jacobs, tobifjellner (Tor-Bjorn Fjellner), Trinadin, and Ulrich Pogson.
\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:\"13138\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:61:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WP Briefing: Episode 35: Five for the Future’s True Intentions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wordpress.org/news/2022/07/episode-35-five-for-the-futures-true-intentions/\";s: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, 11 Jul 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=13132\";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:140:\"On this week\'s episode of the WordPress Briefing, Josepha answers questions about the intentions behind the Five for the Future initiative. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/07/WP-Briefing-035.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:14788:\"\nIn the thirty-fifth episode of the WordPress Briefing, Josepha Haden Chomphosy tackles questions about the true intentions of the Five for the Future initiative.
\n\n\n\nHave a question you’d like answered? You can submit them to You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nEditor: Dustin Hartzler
Logo: Beatriz Fialho
Production: Santana Inniss
Song: Fearless First by Kevin MacLeod
[Josepha Haden Chomphosy 00:00:10]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nToday I’m talking about Five for the Future– again. Before we get stuck right into the heart of it, 10 episodes ago, in episode 25, I focused on the Five for the Future initiative and I recommend that you listen to that before you join me in today’s episode. It’s only eight minutes and it gives you a history of the Five for the Future initiative, as well as some information on the Five for the Future program.
\n\n\n\nIt then goes on to talk about some of the original intentions behind that original initiative. The reason I bring this back up today is partially because one, I will talk about both the program and the initiative it’s based on literally anytime. I believe strongly that they are both a vital part of what will result in a triumph of the commons of WordPress, and keep this empowering project around for years to come.
\n\n\n\nBut I also bring it up today because there’s conversation about a post I published a couple of months back that has generated some dialogue around the intentions of this catchy call to contribution. So to make sure that as we move through this discussion together, we are working with as much factual information as possible, I present to you some facts.
\n\n\n\n[Josepha Haden Chomphosy 00:01:46]
\n\n\n\nFirst and foremost, the pillars of this initiative. The 5% in Five for the Future is aspirational. Contribution to open source is a question and indication of privilege. So the 5% is not a requirement, but rather it’s an aim. It could refer to 5% of your time or 5% of your resources, or just any amount of your time or resources around. Regardless of how you’re defining it, it is an aspiration, not a requirement.
\n\n\n\nThe second pillar, pledges show your intention and whatever contributions you are able to offer after you’ve made your pledge are always welcome. No one is out there checking for 100% completion of the hours that you intended to give back to WordPress versus the hours that you actually succeeded at giving back to WordPress.
\n\n\n\nThere are so many volunteers that make sure that this project is running and functional and has plenty of people knowing how to get things done and how to teach others how to get things done. It’s all coming from generosity of heart.
\n\n\n\n[Josepha Haden Chomphosy 00:02:52]
\n\n\n\nAnd speaking of generosity, the third thing that is important about this initiative is that it insists on and wants to celebrate a culture of generosity. Beyond the concept of a pledge, is the idea of generous collaboration toward the long term health and stability of our project for the future.
\n\n\n\nAs contributors, we understand that we are greater than the sum of our parts and what we build within WordPress empowers those who build with WordPress. So those are the pillars that went into that initial thought, that opening Five for the Future call to action that Matt gave to everybody in 2014.
\n\n\n\nAnd so now I want to share with you some of the pillars of the program that has grown up around it. So the Five for the Future initiative, if you’re not familiar, was started in 2014 and is a grand call to all of us to remember to give back to the shared commons of WordPress. Its aim was to help guard against what is called the “tragedy of the commons,” where resources are continually taken out and not necessarily reinvested in. No one’s necessarily putting anything back into those.
\n\n\n\n[Josepha Haden Chomphosy 00:04:06]
\n\n\n\nSo that’s the starting point for all of this. So the program, the Five for the Future program, in 2018 was built as a collaborative effort with full participation and buy-in from the contributors who were active in the project at the time. It allowed anyone to raise their hands, to show support of WordPress via a pledge and also started a multi-year discussion of how to define contributions in a way that let us automatically provide props and therefore more effectively put badges on people’s wordpress.org profiles.
\n\n\n\nAnd then in 2019, there was an additional pilot of the program, which kind of offered some team structure, which was intended to not only take on work that I don’t like to ask volunteers to do, but also to provide some checks and balances to an absolute raft of sponsored contributor hours that we had started to see show up.
\n\n\n\nWhich brings us then to the post that I mentioned at the start. Knowledgeable supporters of the WordPress open source project have debated next iterations to Five for the Future activity and programming. So, to bring the conversation to a central set of questions, or rather to bring the conversation to a central spot, I raised these two questions. One, what activities can we see inside our contributor networks? So wordpress.org, make.wordpress.org, the Rosetta sites that we have, Slack, et cetera.
\n\n\n\n[Josepha Haden Chomphosy 00:05:30]
\n\n\n\nSo what activities can we see inside the contributor networks that we can flag to enable easier distribution of props and therefore badges? The second question is, what activities can we see also in those contributor networks that appear to be contributions, but in the end are only benefiting the person or company that provides the contributions?
\n\n\n\nFor what it’s worth that discussion then also raised a third question that I don’t think we’ve even started to tackle, which is what about the activities that are not in the contributor network, but still do move WordPress forward? Cause there are so, so many of those things and it’s a great question. I don’t have an answer and just so that I don’t leave you all with a series of questions for which there are no answers provided in this particular podcast, I do have a few answers for questions that I have seen floating around this discussion.
\n\n\n\nSo the first question is actually a bunch of questions. There are like three parts to it. What are props, who gives props, and who tracks them? So ‘props’ is a term used in WordPress to describe shared recognition of a contribution. Think of it as like a hat tip or kudos or an assist. However you think about it, it’s recognition of the other people who helped to solve a problem along the way. That is what props are.
\n\n\n\n[Josepha Haden Chomphosy 00:06:47]
\n\n\n\nThe second part of that question is who gives props and historically developers have given props, which tends to mean that it’s mostly developers who get props. But now, also, any team rep during a release cycle can provide props to folks on their team, volunteers on their team who were really helpful during the course of the release.
\n\n\n\nAnd recently we also added the functionality for ad hoc props to be given in the Slack props channel, and those get added to your profile activity. So that someone can give you basically a public thanks for having helped on something that they were working on. And then that gets logged in your activity tracker on your WordPress.org profile.
\n\n\n\nAnd then the final question in that first big question is who tracks these props? And the answer is human beings! Which is why folks feel like they have to do a ton of things before they even get props. And that’s also why I’d like to automate more and more of them so that you don’t have to do a ton of things in order for someone to show up and acknowledge that you are part of a solution.
\n\n\n\n[Josepha Haden Chomphosy 00:07:51]
\n\n\n\nSo the second question that I’ve seen kind of running around is, where do props start? And that is a great question that has been asked year after year. And one that I think we should continue to ask. The reality is that we won’t be able to see every contribution to WordPress, but that doesn’t mean that they aren’t valuable. And it doesn’t mean that they don’t matter.
\n\n\n\nBuilding our culture of generosity helps us to better recognize and celebrate each other for all of our contributions, whether they are for a major release or a major event, or one of these new ad hoc props that you can offer to people. And if we see more and more of the same type of contributions being celebrated, then we can also work toward automating those as well, so that you don’t have to do a super ton of them before someone has noticed that you’ve done even one of them.
\n\n\n\nAnd the third big question that has been running around is, what about the people who don’t want the props? If people want to be literally anonymous, then deletion requests are probably your way to go. But I actually don’t think that’s the question here. I think the question is what if a prop holds no intrinsic value to you and then, you know, I wanna thank you for that spirit of generosity. And I also wanna say that I’m so glad you’re here.
\n\n\n\n[Josepha Haden Chomphosy 00:09:02]
\n\n\n\nHopefully, all of these answers clarify what lies at the heart of what is intended with the Five for the Future initiative and the program that’s built on top of it. And why I care so much about fixing the ways we offer props to folks. For me, it’s not about assessing the worthiness of people or companies or any of their contributions. For me, it’s about reinvesting in the shared commons of the WordPress ecosystem, by finding a way that our economy can entice folks to put back into WordPress, something close to the benefit that they receive from it.
\n\n\n\nAnd that brings us now to our small list of big things. Thank you all for making it into the final stretches with me. These three things that I’m sharing also have companion blog posts to go with them because they are very big questions or very big features, very big plugin kind of things that we’re looking at. And so you’ll be able to find those in the show notes, or you can go to wordpress.org/news if you’re listening to this in a podcast player of your choice that is not wordpress.org.
\n\n\n\n[Josepha Haden Chomphosy 00:10:10]
\n\n\n\nSo the first one on my list is a new plugin. It is called Create Block Theme. And it’s gonna make it easier for theme builders to use the existing site editor tools to create new block themes. I’m very excited about this. Uh, you can find it on make.wordpress.org/themes. And I will also include a link to it in the show notes below.
\n\n\n\nIf themes are not your area of expertise, but you are interested in documentation or the DevHub or to an extent design things, then the improvements that are being worked on for the DevHub are definitely in your area. That’s kind of a Meta task, but has a few other pieces involved as well. That can be found on make.wordpress.org/meta. But again, I will have a link to the very, very detailed blog post in the show notes.
\n\n\n\nIt’s got a bunch of hypothetical changes that are being suggested for the WordPress developer docs, uh, especially when it comes to the function reference. And so there are gonna be some slight design questions, but not like, graphic design/visual design, more in the like, can humans read this design area of things? And so that will be a good one to look at. If you are sort of in the Meta or Documentation vein of things in the way that you like to contribute to WordPress.
\n\n\n\n[Josepha Haden Chomphosy 00:011:30]
\n\n\n\nAnd then the final thing is about open sourcing theme designs. So open sourcing everything obviously is important to us. And the design tool that we use, this tool called Figma, is open to the public. And so it’s possible for folks to be able to kind of get in there and use and reuse any design elements.
\n\n\n\nAnd so there’s a discussion happening over on make.wordpress.org/design about how that can and should look in the future. And so if design is definitely your area, and again, this kind of lines up with themes a little bit, then wander over into that one, for which there will also be a link in the 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:\"13132\";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: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:36:\"The Month in WordPress – June 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:68:\"https://wordpress.org/news/2022/07/the-month-in-wordpress-june-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:\"Wed, 06 Jul 2022 14:19:50 +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=13069\";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:313:\"With WordPress 6.1 already in the works, a lot of updates happened during June. Here’s a summary to catch up on the ones you may have missed. WordPress 6.1 is Slated for Release on October 25, 2022 Planning for WordPress 6.1 kicked off a few weeks ago with a proposed schedule and a call for […]\";s: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:12416:\"\nWith WordPress 6.1 already in the works, a lot of updates happened during June. Here’s a summary to catch up on the ones you may have missed.
\n\n\n\nPlanning for WordPress 6.1 kicked off a few weeks ago with a proposed schedule and a call for contributors to the release team. This will be the third major release in 2022 and will include up to Gutenberg 14.1 for a total of 11 Gutenberg releases.
\n\n\n\nMatías Ventura published the preliminary roadmap for version 6.1, which is expected to refine the full site editing experience introduced in the last two major releases. Stay tuned for a companion post with more details on what’s to come.
\n\n\n\n\n\n\n\n\n\n\n\nTune in to the latest episode of WP Briefing to hear WordPress Executive Director Josepha Haden discuss planning for major releases and how you can get involved.
There are two new versions of Gutenberg since last month’s edition of the Month in WordPress:
\n\n\n\n\n\n\n\n\n\n\n\nFollow the “What’s new in Gutenberg” posts to stay up to date with the latest updates.
\n\n\n\n\n\n\n\nThe BlackPress community is a great place to connect with black African descent people in the WordPress space, access tech resources, and advance your career skills. Join the BlackPress Community.
\n\n\n\n\n\n\n\nWant to get involved in testing WordPress? Follow the “Week in Test” posts to find a handy list of links and opportunities.
\n\n\n\n\n\n\n\nThe #WPDiversity group has organized a free, online speaker workshop for Indian women in the WordPress community. The event will take place on September 24-25, 2022. Registration is now open.
Have a story that we could include in the next issue of The Month in WordPress? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @mysweetcate, @dansoschin, @lmurillom, @webcommsat, @chaion07, @rmartinezduque.
\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:\"13069\";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: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:30:\"People of WordPress: Leo Gopal\";s: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:65:\"https://wordpress.org/news/2022/06/people-of-wordpress-leo-gopal/\";s: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, 30 Jun 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: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=13020\";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:355:\"In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature Leo Gopal, from South Africa, a back-end Developer and Customer Support agent on the encouragement and learning support the WordPress community can give. Writing as […]\";s: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:11776:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature Leo Gopal, from South Africa, a back-end Developer and Customer Support agent on the encouragement and learning support the WordPress community can give.
\n\n\n\nCuriosity, writing, and resilience are recurring themes in Leo’s story, and have mapped with his WordPress journey.
\n\n\n\nHigh school was a difficult time for Leo, as he had a speech impediment which only subsided when he was with close friends or family.
\n\n\n\nHe began writing a journal as an avenue of expression and found every word arrived smoothly for him.
\n\n\n\nIn 2004, Leo discovered the joy of blogging as a way of combining keeping a journal with ‘conversations’ he could have with those who commented on his blogs. The potential and power of blogs would be an influence in the rest of his life.
\n\n\n\nAs Leo’s confidence grew through expressing himself in writing, he was determined that his stutter would ‘no longer hold power over him’. In 2005, with the encouragement of his blog readers, he spent his school summer break in his room working on reducing his stutter. WordPress would be the tool that would enable him to connect with his blog readers and to express his creativity and thoughts.
\n\n\n\nIn high school, Leo had opted for programming as one of his subjects. In 2008, he built his first website using WordPress for the students at the school. This was the first time he saw the real value of WordPress and open source.
\n\n\n\nDuring the following years, he increasingly spent time searching online for information on ‘Customising WordPress’ and ‘Making WordPress your own’.
\n\n\n\nLeo wanted to keep busy and as soon as he finished school, he applied for every entry-level web-related job that he could find. He was hired by a company for the role of webmaster for its Marketing team focused on WordPress.
\n\n\n\nHe continued to grow his skills as a WordPress developer with the help of useful documentation that he could find and through his helpful local WordPress Community. This helped him earn a living and support his family.
\n\n\n\nIn 2015, Leo moved full-time to Cape Town, South Africa, and started as a developer at a web development agency, eventually progressing to its Head of Development and managing a small team.
\n\n\n\nHe chose WordPress as his main platform for development mainly because of the community behind it.
\n\n\n\n\n\n\n\n“Had it not been for those searches on how to make WordPress your own, my life would have turned out a lot differently.”
Leo Gopal
Leo felt he had a hurdle to overcome working in web sector. He didn’t feel like a ‘real developer’ being self-taught. However, through the community, he realized that there were many self-taught developers and he was not alone.
\n\n\n\nAlongside his development path, Leo faced a mental health journey. He had suffered from depression and found the community to be accepting and understanding of this.
\n\n\n\nAt WordCamp Cape Town 2016, he stood in front of an audience and gave a talk: “The WordPress Community, Mental Wellness, and You”. Following this talk, he was greeted by many attendees who thanked him for talking so openly about mental health issues.
\n\n\n\nLeo has been diagnosed with bipolar, previously known as manic depression. In 2017, he hit a low period and struggled to keep going. He found support and understanding in the community in WordPress.
\n\n\n\nHe has openly written about his experiences with depression and started an initiative where topics of mental health and general wellbeing can be freely and non-judgmentally discussed.
\n\n\n\nHe said that by helping others, he is helping himself, every day.
\n\n\n\nLeo has contributed to the community as a Co-organizer in South Africa for the 2016 and 2017 WordCamp Cape Town, WordPress Meetup Cape Town 2015 – 2016, and WordPress Durban 2017 – 2020. He has also spoken at a number of WordCamps.
\n\n\n\nMaintaining connections with people he had met through these events Leo felt was a great aid to his mental wellbeing during the Covid pandemic.
\n\n\n\nHe has contributed to core and plugins and believes that WordPress and its community make it extremely easy to contribute.
\n\n\n\n\n\n\n\n“The cost to start contributing is extremely low – start now”.
Leo Gopal
When the ability to create and add patterns to the WordPress.org library came out in 2021, Leo used it almost immediately and created a call-to-action box which could be used by both his clients and the community. He plans to release a few more complex patterns.
\n\n\n\nLeo’s mantra is “I can do it!”
\n\n\n\nGetting over a stutter, overcoming poverty, being urgently self-taught, growing up in a country with “load shedding” electricity outages, and one of the slowest rated internet speeds in the developing world, and strengthening mental wellness are not easy feats., And yet, he knows he can do it.
\n\n\n\n\n\n\n\n“Never, ever think you do not have the ‘right’ circumstances for success. Just keep going, progress over perfection – you can do it.”
Leo Gopal
As Leo puts it, the WordPress community doesn’t just power a percentage of the internet; it empowers too.
\n\n\n\n\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Nalini Thakor (@nalininonstopnewsuk), Larissa Murillo (@lmurillom), Meher Bala (@meher), Abha Thakor (@webcommsat), Chloe Bringmann (@cbringmann) for work on this feature, and to all the contributors who helped with specific areas and the series this last few months. Thank you too to Leo Gopal (@leogopal) for sharing his experiences.
\n\n\n\nThank you to Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for support of the People of WordPress series.
\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
\nIn the thirty-fourth episode of the WordPress Briefing, hear WordPress Executive Director Josepha Haden Chomphosy discuss planning for the major release and how you can get involved in the WordPress 6.1 release cycle!
\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\n[Josepha Haden Chomphosy 00:00:10]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy.
\n\n\n\nHere we go.
\n\n\n\nAll right my friends. So it’s been about a month since WordPress 6.0 came out and you know what that means. It means we are already looking at the next major WordPress release because, as most of you know, WordPress never sleeps. Y’all are honestly up and hustling like 24/7 as far as I can tell, which is great! And is one of the many benefits of being a global community, I suppose.
\n\n\n\n[Josepha Haden Chomphosy 00:01:05]
\n\n\n\nBut anyway, back to this major release. There was a high-level roadmap shared by Mattias Ventura at the start of June. And it lists some focus areas for the Block Editor, continued refinements to the template editor and navigation block, and some work on global styles and more / better blocks and design tools that are slated to ship with WordPress 6.1. From the WordPress core side, though, there are a couple hundred tickets that are milestoned for the next major.
\n\n\n\nBeing milestoned for a release means that either a ticket wasn’t ready for the last release and was moved to the next available one, or a ticket has become ready for a release since the last major release occurred. That list as it stands might be a little bit too big for a single release. However, honestly, no list is too big if we have enough folks contributing.
So if you’ve never contributed to a major release of WordPress before, and you’re interested to know how that works, there are some things to keep an eye out for over the next few weeks. We are in what is considered the planning phase for the next big release. And so there are two or three things you’re gonna see pretty soon.
\n\n\n\n[Josepha Haden Chomphosy 00:02:11]
\n\n\n\nFirst is a planning kickoff post. That post gets published on make.wordpress.org/core, and it includes notes on volunteering for the release squad, some guesses at areas of focus based on the tickets that we’re seeing in track, a schedule, the whole kit, and caboodle. It’s all in there. If you are wanting to know how to lend a hand and how to take your first steps to core contribution, apart from the new contributor meeting that happens before the dev chat, that post is the place to start.
\n\n\n\nSo keep an eye out on make.wordpress.org/core for that. And then the second thing that shows up in the planning phase for any major release is bug scrub and ticket triage meetings. Like I mentioned, there are the new contributor meetings where they scrub tickets and talk through the basics of what we’re seeing on good first bugs.
\n\n\n\nAnd I mentioned that here often, I just mentioned it in the last, in the last bullet point, but there are also regular bug scrubs and ticket triaging sessions where a kind contributor chooses a set of tickets to review and then leads other contributors through the process of checking to see if a ticket is valid to see if it can be replicated to see if it has a patch.
\n\n\n\n[Josepha Haden Chomphosy 00:03:23]
\n\n\n\nIf there are decisions that are blocking it and how to move those decisions forward, and generally just kind of discuss what else has to be done in order to take the ticket to the next step. Those get announced in the dev chat every Wednesday, but also there is a post that will go up on make.wordpress.org/core.
\n\n\n\nI wish I had a faster way to say that instead of just racing through the whole URL every time. But it’ll be okay. We’ll put it in the show notes in case you would rather just click some stuff. And the third thing to keep an eye out for. If development is not your thing, so writing code is not already part of your tool belt, that’s totally fine. There are many other important areas where you can contribute, too. Design, training, support, polyglots, marketing, documentation, and more. These teams all do work in and around a release that is vital to WordPress’ overall success.
\n\n\n\n[Josepha Haden Chomphosy 00:04:19]
\n\n\n\nAnd a final thought of all. If that felt a little too intense if you want to see where this ship is headed, but you can’t quite commit to grabbing an oar today, that’s fine, too. The most important thing is that if you are a member of the community, as an extender or a user or a die-hard contributor, or a new contributor, the most important thing is that you have some general awareness of what the overall direction is.
\n\n\n\nYou might do that by experimenting with blocks in your products or by testing screen readers against your workflow or even by setting aside an hour to participate in the latest testing prompt. Being aware of what’s happening in and around your area of the project will help to keep you kind of prepared and knowledgeable to lend a hand whenever it is that you are ready.
\n\n\n\n[Josepha Haden Chomphosy 00:05:14]
\n\n\n\nAnd that then brings us to our small list of big things. My friends, registration is now open for the WordPress Speaker Workshop for Women Voices in India. That’s taking place on September 24th and 25th. Uh, it’s happening over Zoom, so location or travel shouldn’t really be an obstacle for you. I’m going to leave a link to some information about that in the show notes. It should be an excellent opportunity that [the] WP Diversity initiative that WordPress has, that the community team helps to foster, is really an excellent experience. And so I hope that you register and attend that.
\n\n\n\nAnd the second thing actually is a bit of a celebration. The Photo Directory recently hit a huge milestone of 3000 photos! And you also can submit your photos to wordpress.org/photos. If you feel so inclined to make a contribution of that type.
\n\n\n\n[Josepha Haden Chomphosy 00:06:07]
\n\n\n\nAnd then the third thing on my smallest of big things is actually kind of a, a WordPress tooltip a little bit of a WordPress project did-ya-know? So, there is a special channel in WordPress Slack for sharing thanks to folks who were especially helpful to you. It’s called the Props Channel. And when someone shares props with you, it even shows up in your activity on your wordpress.org profile. Pretty cool, huh? Props to the Meta team for that one.
\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:\"13013\";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: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:59:\"WP Briefing: Episode 33: Some Important Questions from WCEU\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wordpress.org/news/2022/06/episode-33-some-important-questions-from-wceu/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 13 Jun 2022 11:01: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: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=13005\";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:165:\"WordPress Executive Director Josepha Haden Chomphosy covers some important questions from WordCamp Europe on this special episode of the WordPress Briefing 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:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/06/WP-Briefing-033.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:13788:\"\nIn the thirty-third episode of the WordPress Briefing, hear Josepha Haden Chomphosy recap important questions from WordCamp Europe, and a selection of Contributor Day interviews.
\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.
[Daugirdas Jankus 00:00:04]
\n\n\n\nHonestly, it’s not a secret. It’s a big part of our business. And I think it’s like WordPress is a big part of all the hosting company, company’s, businesses, you know? So for us, it is like, we want to make it better. We want to give back. We want to understand, you know, where we can contribute the most. And we see it as a, you know, win, win, win situation for everyone, for clients, for the whole ecosystem.
\n\n\n\nAnd for us as a business, of course!
\n\n\n\n[Milana Cap 00:00:32]
\n\n\n\nMy favorite WordPress component is WP CLI. That’s my crush, haha, because I love terminal. I love doing it. I’m not a really UI type of person, I get lost in UI. But in terminal, you just type command and it does what you want. And a WP CLI is much more powerful than WordPress dashboard. You can do so many things there and you can have fun.
\n\n\n\nUh, so that’s my go-to tool!
\n\n\n\n[Josepha Haden Chomphosy 00:01:10]
\n\n\n\nHello everyone. And welcome to the WordPress Briefing– the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy.
\n\n\n\nHere we go!
\n\n\n\n[Josepha Haden Chomphosy 00:01:36]
\n\n\n\nMany, many people were at WordCamp Europe a couple of weeks ago. And at the end, Matt and I closed out the event sessions with a little question and answer time from the community. I was excited to see everyone and excited to answer their questions. But as with all spur of the moment answers, I experienced this l’esprit de l’escalier and I found that there were a few things that I would have answered a little more completely if I had taken more than two seconds to think about them.
\n\n\n\nSo today I’m going to augment some of the answers from that session with a little more context and clarity. There was a question from Laura Byrne about favorite blocks in recent WordPress releases. And given that I was exclusively holding WordCamp Europe information in my brain at the time, I couldn’t think of which block was my favorite. While I was sitting there on that stage,
\n\n\n\nI realized that one of my favorite things about WordPress’s 6.0 release, like Matt, wasn’t really a block, but it was a functional workflow sort of thing. So my favorite thing was the ability to lock blocks, but I mean, the question was about favorite blocks. And so I do know that some of the most anticipated blocks are the Flexbox layout blocks. Whew. What a sentence!
\n\n\n\n[Josepha Haden Chomphosy 00:02:46]
\n\n\n\nTry to say that three times fast! Those blocks are the Flexbox layout blocks, they are sort of shortcuts that show up when you’re selecting multiple blocks and allow for easy side-by-side layouts. I’m not explaining it in a way that does it much justice, but I will share a link in the show notes that has more information and you can kind of see how empowering that particular block is in the block editor.
\n\n\n\nThe next question I wanted to give a little more context to came from Courtney Robertson. She asked about how to make translated content more readily available on learn.wordpress.org. My answer was pretty far ranging and talked about why it’s harder to commit to prioritizing that over, for my example, translating WordPress core.
\n\n\n\nBut I also understand that there are people who want to help and just need someone to point them in the right direction. And so I want to be clear that it is possible to have workshops in any language on learn.wordpress.org right now. We just don’t have a lot of people contributing those translations.
\n\n\n\nSo there are conversations going on right now in the training team about using Glotpress on learn.wordpress.org, and also how to translate subtitles. So, if you are looking for ways to give back through translation and training is an important kind of area of your focus. I will have links to both of those things in the show notes as well.
\n\n\n\n[Josepha Haden Chomphosy 00:04:11]
\n\n\n\nI also gave a quick answer, uh, after this question about how hard it is to recognize contributions that are separate from a major event or major release. In this case, when I say recognize, that’s recognized as in thank, not recognize as in, know it exists. In case it’s not clear why that was connected, why that answer was connected to the question, training materials are self-serve and not always specific to individual releases of WordPress.
\n\n\n\nSo that means the maintenance of any content around training happens routinely over the course of time, rather than because of a specific release or a WordCamp. What sometimes can make it a little harder to entice people to join us in that work.
\n\n\n\nAnd now the third question I’d like to tackle is the one that came from Megan Rose. She asked how we can encourage better diversity as we go back to in-person events. My answer was more about the big picture, program-wide work that has been done and specific awarenesses that I, as a leader, have been keeping top of mind. That answer is still true and is still important, but again, it doesn’t really help anyone who’s wondering how they can show up today in their own communities, and do the hard work of fostering an inclusive space there so that we can confidently welcome more diverse voices together.
\n\n\n\n[Josepha Haden Chomphosy 00:05:27]
\n\n\n\nA great place to start is to have conversations with people who aren’t like you and really listen. Also recognizing that we all come from different backgrounds that give us more or less opportunity and always be asking yourself, who is missing from this conversation and why, how can I find them and invite them into our own WordPress spaces?
\n\n\n\nIf that all kind of feels right up your alley, I would check out the show notes. I’ll have some links in there to the community team’s site, as well as a few posts that will help you to explore that a bit further as well.
\n\n\n\nThere were also a couple of questions about market share slash usage of WordPress, and Five for the Future that I really do want to answer, but as I was writing up the context and just kind of exploring the questions that people were raising, it turned out to really be quite a big set of answers.
\n\n\n\nSo I will do those in either two separate episodes of their own or one surprisingly long, for me, episode. And so there you have it, a lightning round, deep dive on a few questions from WordCamp Europe.
\n\n\n\n[Jonathan Desrosiers 00:06:41]
\n\n\n\nYeah, it’s definitely great to be back in person. Um, it’s been a long two years, two or three years for a lot of people and it’s, it’s, it’s great that we’re such an asynchronous community and we can all stay connected online through Slack and different means. Um, but there are some things that you can’t replace, like making friends with people and learning people’s demeanors and having some discussions in person that you can’t replace.
\n\n\n\nAnd so, uh, I’m really excited to see people I haven’t seen in a long time. Meet new people and, um, you know, have some of those discussions here today in Portugal.
\n\n\n\n[Josepha Haden Chomphosy 00:07:21]
\n\n\n\nWhich then brings us to our small list of big things.
\n\n\n\nIf you missed the announcement, WordCamp Europe will be in Athens next year. And the call for organizers is open already. It’s an experience that is absolutely irreplaceable. So I’ll link to that in the show notes, in case you’ve always wanted to give back to WordPress that way.
\n\n\n\nThe second thing on my list is that work on the next major release of WordPress is already underway. There is a post with roadmap info that was published recently, as well as a slightly more casual thread on Twitter. I’ve linked both of those in the show notes, so that you have some concept of what it is that we are aiming for in 6.1, and also a concept of where to go to get started working on it if that’s what you feel like doing, uh, for the next three to four months– 120 days, roughly.
\n\n\n\nUh, and finally. This is less of like a thing to be aware of in the next two weeks and kind of a little WordPress project tool tip. Did you know that we have a calendar that shows all meetings for all teams all week long? It will make you feel tired by the amount of work that gets done in the WordPress project every week, but it’s right there on make.wordpress.org/meetings.
\n\n\n\nSo you never have to wonder where folks are meeting to talk about things ever again. And 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\n\n\n[Santana Inniss & Héctor Prieto 00:09:11]
\n\n\n\nHello! Mic test. One, two, one, two.
\n\n\n\nWe are testing the USB microphone. Let’s hope we’re using it actually.
\n\n\n\nI think so. I think so.
\n\n\n\nYes. Because now I am far, and now I am much closer to the microphone. Yes.
\n\n\n\nAnd I am sitting in the same spot.
\n\n\n\nGood. Hello?
\n\n\n\nHello!
\n\n\n\nMic test one, two.
\n\n\n\nMic test one, two.
\n\n\n\n[record scratching sound effect]
\n\n\n\n[laughter]
\n\n\n\nAnd, close.
\n\n\n\nMic check.
\n\n\n\nMic check.
\n\n\n\n[record scratching sound effect]
\n\n\n\nI’m close to the mic. I’m far from the mic.
\n\n\n\nI’m far from the mic. Wow.
\n\n\n\nNot so far.
\n\n\n\n[laughter]
\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:\"13005\";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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"The Month in WordPress – May 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:67:\"https://wordpress.org/news/2022/06/the-month-in-wordpress-may-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:\"Thu, 02 Jun 2022 11:35:47 +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=12993\";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:346:\"WordPress has a lot to celebrate this month. The newest release “Arturo” is here. WordPress turned 19 years old last week. And WordCamp Europe, the first in-person flagship WordCamp in two years, is starting today in Porto, Portugal. Read on to learn more about these and other exciting news around WordPress! Say hello to WordPress […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:12516:\"\nWordPress has a lot to celebrate this month. The newest release “Arturo” is here. WordPress turned 19 years old last week. And WordCamp Europe, the first in-person flagship WordCamp in two years, is starting today in Porto, Portugal. Read on to learn more about these and other exciting news around WordPress!
\n\n\n\nWordPress 6.0 “Arturo” was released on May 24, 2022. Named in honor of the Latin jazz musician Arturo O’Farrill, the awaited release brings more customization tools and numerous updates to make the site-building experience more intuitive.
\n\n\n\nCheck out the WordPress 6.0 video and the announcement post for an overview of the most important changes. Interested in knowing more about the features that will help you build with and extend WordPress? Then the WordPress 6.0 Field Guide might be for you.
\n\n\n\nOver 500+ people in 58+ countries made WordPress 6.0 possible – Thank you!
\n\n\n\nTime flies, doesn’t it? Believe it or not, May 27 marked the 19th anniversary of WordPress’ first release! To celebrate, the community put together a special site (wp19.day) where contributors shared thoughts, videos, live shows, and more.
\n\n\n\nYou can still join the fun using the hashtag #WP19Day on social media, or even contribute photos of the swag you used to celebrate to the WordPress Photo Directory.
\n\n\n\nTwo new versions of Gutenberg were released last month:
\n\n\n\nHave a story that we could include in the next issue of The Month in WordPress? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @rmartinezduque, @laurlittle, @harishanker.
\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:\"12993\";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: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:29:\"People of WordPress: Dee Teal\";s: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:64:\"https://wordpress.org/news/2022/05/people-of-wordpress-dee-teal/\";s: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, 31 May 2022 17:51:53 +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=12946\";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:90:\"This month\'s People of WordPress feature shares the story of Dee Teal, based in Australia.\";s: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:28:\"webcommsat AbhaNonStopNewsUK\";s: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:14938:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a WordPress development and large project specialist on the difference the software and community can make to your career and life.
\n\n\n\nDee’s story with computers started at school in New Zealand where discovering how a mouse worked and learning BASIC and Pascal was a catalyst for what later became a programming career.
\n\n\n\nAt a time when computers were just becoming mainstream, there were no opportunities for girls in her school to consider this as a further option. She recalls: “No one thought to say, ‘Dee, you look like you’re good at this, you should pursue it…’. I mean, I was a girl (and I was told girls didn’t ‘do’ computers). No one in the circles I moved in really had any idea where this technology revolution would take us.”
\n\n\n\nWith no particular career path into technology, Dee was encouraged in her final year of school to apply for a job in a bank where she worked and became a teller three years later. She gained financial independence, which enabled her to travel as a 20-year-old and spend the next three years exploring the US and Europe.
\n\n\n\nLooking back, she noted how the world had changed: the first computer mouse she had seen had come out in 1983, and 20 years later WordPress was founded.
\n\n\n\nDuring those 20 years, Dee worked as a nanny, working in child care centers, in customer support, and as a temp.
\n\n\n\nIn 1999, she packed up her bags once again, and moved from New Zealand to Australia. She took a place at a performing arts school where she honed her singing and performance skills and volunteered her time to the music director who was starting to experiment with sending out HTML newsletters and updates via email.
\n\n\n\n“And so my personal revolution began. On the day after I graduated from that course, I walked into a full-time role as that music director’s assistant and began my journey back to code.”
\n\n\n\nAs part of that job, Dee edited and sent HTML newsletters on a weekly basis. This ignited her interest in programming, and she bought books about coding for the web and experimented on her home-built PC making web pages.
\n\n\n\n\n\n\n\n“I’m sure, like a lot of us, I remember the thrill of creating that first HTML file and seeing a ‘Hello World’ or similar heading rendered in the browser. From there, I was completely hooked.”
Dee Teal
Later she moved to the IT department and took on maintenance of all the websites. By 2004, she was working full-time as a webmaster. A year later, she was running a small business creating sites on the side. Four years after that, her business became her full-time job as she left employment to pursue her Masters Degree in Digital Communication and Culture.
\n\n\n\nDee found the theory and sociology behind the web, and its facilitation of human and machine communication fascinating.
\n\n\n\nShe said: “I love the fact that the tech industry involves a constant constant curve of growth and discovery, which results in a perpetual exercise in finding creative elegant solutions for sticky problems.”
\n\n\n\nFor Dee, being able to use her innate curiosity to leverage processes, people, and tools, fuelled by a focus on communicating a message, has been a defining inspiration in her work.
\n\n\n\nThis combined fascination coincided with her meeting WordPress in 2009 and subsequently its community. She moved her existing blog to the software and it became the CMS of choice for all her client work.
\n\n\n\nIn 2011, she stumbled across WordCamps and by extension the WordPress community. Dee has reflected publicly that WordPress didn’t change her life, its community changed her world!
\n\n\n\nShe flew on a whim from her then home in Sydney to attend a WordCamp in Melbourne she had found after a search for ‘WordPress Conferences’.
\n\n\n\nShe said: “I met welcoming people, made friends, connected, and came back home excited and hopeful about continuing this connection with the wider WordPress community.”
\n\n\n\nBuilding a community locally around WordPress got off to a slow start in Sydney. From an inauspicious early WordPress Sydney meetup in the function room of a pub, her connection and involvement took off. Before long she was helping organize that meetup, and by the time she moved away from that great city it had branched into two meetups, and soon after, into three.
\n\n\n\nShe was so inspired by the community that at the end of that first year and her second WordCamp, she raised her hand to help organize a WordCamp Sydney in 2012, and after moving interstate, WordCamp Melbourne in 2013.
\n\n\n\n\n\n\n\n“WordPress and any other software package exist to serve people.”
Dee Teal
Dee said: “WordPress, software, technology, the Internet will come and go, morph, and change, evolve. Maybe WordPress will last forever, maybe it will morph into something else, maybe one day it will look completely different than it did when I first started (actually, that’s true now). The thing that doesn’t change is the humanity around it. WordPress and any other software package exist to serve people.”
\n\n\n\nShe added: “The thing that I have learned, not only through WordPress but in life, is that if we too serve the people around what we’re doing, we ourselves will grow, develop and change alongside the people we serve, and the tools we use to serve them.”
\n\n\n\nDee was a coordinator for WordPress 5.6 release in 2020 and was able to encourage others to learn about the process.
\n\n\n\nDee has been an advocate for cross-cultural collaboration and understanding in both WordPress and her work for a large distributed agency which has people from more than 24 countries and operates across 16 timezones. She has also written about closing the gap between diverse distributed teams and how to meet the challenges of cross cultural remote work.
\n\n\n\nDee has given talks at WordCamps, including at WordCamp Europe in 2019, on developing ourselves, our relationships, and our communities in increasingly diverse environments.
\n\n\n\nWith a strong desire to share her professional knowledge and experience, Dee hopes her involvement in the WordPress community from being part of a Release Squad in the Core Team, and volunteering in the community through organizing and speaking at WordCamp events, will inspire others to get involved.
\n\n\n\n\n\n\n\n“It’s the connections, it’s the friendships. It’s the network of work, referrals, support, help and encouragement.”
Dee Teal talking about the community that makes WordPress specialbenefits of the WordPress community
In contributing to WordPress and organizing community events around it, Dee found that for her: “At the end of the day it isn’t actually WordPress that matters. It’s those connections, it’s the friendships. It’s the network of work, referrals, support, help, encouragement that has kept me wired into this community and committed to helping other people find that connection and growth for themselves.”
\n\n\n\nDee’s career in WordPress has moved through coding, into project management of large scale WordPress projects, and now into delivery leadership. Her connections to community have helped ‘fuel the transitions’ through these chapters of her life.
\n\n\n\nShe said: “I believe that the place I’ve found and the opportunities I have had owe as much to my own desire and ambition as they do to the help, support and belief of the community around me; sometimes even more than I’ve felt in myself.”
\n\n\n\nShe feels that she is ‘living proof’ that by helping, connecting, and resourcing other people, you can be helped, resourced and connected into places you had never thought possible.
\n\n\n\nThis has enabled her to reach and have a career in technology that she did not know existed as a teenager playing with that first computer mouse and experimenting with code. Dee hopes her story will inspire others in their journey.
\n\n\n\n\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Abha Thakor (@webcommsat), Meher Bala (@meher), Mary Baum (@marybaum), Chloe Bringmann (@cbringmann), Nalini Thakor (@nalininonstopnewsuk), and Larissa Murillo (@lmurillom) for work on this feature. Thank you to Josepha Haden (@chanthaboune) and Topher DeRosia (@topher1kenobe) for support of the series. Thank you too to @thewebprincess for sharing her experiences.
\n\n\n\nThis article is inspired by an article 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 would otherwise go unheard.
Meet more WordPress community members in our People of WordPress series.
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 thirty-second episode of the WordPress Briefing, WordPress Executive Director Josepha Haden Chomphosy shares her open source reading list for that post-WordCamp Europe downtime.
Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\n[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 some of the ideas behind the WordPress open source project and the community around it. As well as get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nWith the approach of various mid-year breaks and the prospect of wandering off for some safe, restorative travel, I’ve been updating my to-read and re-read list. As I was looking at the queued books for my Northern hemisphere summer, there were some common threads, mostly around leadership, but there’s also like a chunk that’s about cross-cultural group theory and economics, and then like some beach reads, but there’s one group in particular that you all might find interesting.
\n\n\n\nAnd that’s a group that’s sort of like a back-to-FOSS basics list. So I’ll share my top few with you in case you want to pack a copy for your next getaway.
\n\n\n\nThe first one on our list is called Producing Open Source Software by Karl Fogel. I think everyone who contributes to FOSS projects has received this as one of their first recommendations. Like, y’all are building open software? Excellent, you need to read Producing Open Source Software. Like, that is just a sentence that comes out of everyone’s mouths. So this was one of the first open source books that was recommended to me when I joined the WordPress community. It was freshly revised in 2020, and I haven’t given it a read since then, which is why it is on my reread list this year.
\n\n\n\n[Josepha Haden Chomphosy 00:01:54]
\n\n\n\nHowever, it shaped the early days of the WordPress project’s leadership, and their lead developers, and some of WordPress’s basic philosophies. It’s all available online, under a creative commons, ShareAlike license. And so it’s worth the read. I’ll put a link to it in the show notes so it’s easy for everyone to find in the event that is your preferred beach read.
\n\n\n\nThe second one on this list is a book from Nadia Eghbal. She wrote the excellent Roads and Bridges report that also is probably not light beach reading, but you know, this one is on my list to read this summer because Eghbal always delivers truths about the reality of maintaining popular software, popular, open source software, in a way that’s easy for me to access and process rather than getting paralyzed by the enormity of it all.
\n\n\n\nFor what it’s worth your mileage may vary on that. I realized that, like, I live and breathe open source stuff. And so just because I am not paralyzed by the enormity of her explanations of things doesn’t necessarily mean that you will have a similar experience. And so I’m just going to claim that elephant in the room for all of us.
\n\n\n\nHowever, if you only read one book on this list this year, I think that this should be the one that you read.
\n\n\n\n[Josepha Haden Chomphosy 00:03:14]
\n\n\n\nThe third one is called Code: Collaborative Ownership and the Digital Economy. It was edited by Rishab Aiyer Ghosh. I am certain that I butchered that name. And so I apologize on my own behalf to everyone that knows whether or not I said it correctly.
\n\n\n\nThis book focuses on intellectual property rights and the original purpose of having anything like copyright in the world. So, right up my alley! The writers who contributed to this work promise exploration of the plight of creativity in the commons, the role of sharing in creative advancement, and a concept of what it would look like if intellectual property were to mean the second closing of an ecosystem versus a triumph of the commons.
\n\n\n\nI mean, obviously, this one is very light reading. You can take this topic to high tea and everyone will not know what you’re talking about. However, this one looks like a really interesting book to me and I am just super ready to read it.
\n\n\n\n[Josepha Haden Chomphosy 00:04:19]
\n\n\n\nThe second to last one on the list is a book called Humble Inquiry.
\n\n\n\nThis is a new-to-me book that seems right in line with one of my favorite books to recommend to leaders in the open source space. From reviews of it, I have gathered that it takes a hard look at the value of listening and asking for clarification in a world that puts a high value on an unsolicited hot take.
\n\n\n\nIt puts the importance of high trust relationship building, which is at the heart of any cross-culturally aware organization. And for folks who’ve been working with me for a while, you know, that relationship building is an important part of my leadership expectations for myself. So it puts relationship building at the front and center with a promise of practical applications for everyday life.
\n\n\n\nAnd if you ever have tried to tackle a complicated topic like this, you know that practical applications are really hard to come by and it’s often hard to understand it if you don’t have those practical applications. And so that is why this one is on my read and reread list this year.
\n\n\n\n[Josepha Haden Chomphosy 00:05:24]
\n\n\n\nAnd then finally the WordPress Milestones book.
\n\n\n\nSo this sounds like a shameless plug for WordPress. And on the one hand, this whole podcast is about WordPress. And so, yes! But on the other hand, I actually am reading this for two specific reasons. I’m rereading this actually. I read it when I first joined Automattic. And so the first of the two reasons that I’m rereading it this year is that volume two of this is, like the second decade of WordPress currently, being researched and written in preparation for WordPress’s 20th birthday next year.
\n\n\n\nSo I am rereading this to kind of get that all back in my mind as that work is getting done. And the second reason is that I honestly like to remind myself of how far we’ve come sometimes. I talk about our work frequently. And I talk about what we’re working on right now, all the time.
\n\n\n\nI talk about what we’re looking at three years from now, five years from now. The biggest concerns of today, tomorrow, and the future-future. And it’s very easy to forget how much success WordPress has had and how much growth the contributors that support us have had over the course of our long and storied history.
\n\n\n\n[Josepha Haden Chomphosy 00:06:40]
\n\n\n\nAnd so I like to go back to that just to kind of give myself some grounding in our progress, as well as get some concept for how we can move forward together. So that one is also available online. Also under a creative commons ShareAlike license and it is also worth the read. I will share a link to that with the other one in the show notes as well.
\n\n\n\nThat brings us now to our small list of big things. Let’s see what we got in the old lineup today.
\n\n\n\nSo, firstly WordCamp Europe is happening this week and it’s possible to watch the live stream from the comfort of your own home. There are some smart and talented speakers at the event. So I encourage you to catch a few if you have the time. I’ll include a link to the live stream information in the show notes below, and then also you can always keep an eye out on Twitter.
\n\n\n\nThere will be a lot of discussions, a lot of conversation there. And so you can engage with folks that are there at the time and catch up on those conversations, catch up on those presentations in your own time, as it fits into your day.
\n\n\n\n[Josepha Haden Chomphosy 00:07:50]
\n\n\n\nThe second thing is that WordPress’s community team is preparing the annual meetup survey right now. So if you participate in meetup events, keep an eye out for that because your feedback helps us to make plans to improve that program so that it works better for you. And it helps you to learn WordPress better and feel more confident with what you are taking out into the world that way.
\n\n\n\nBut, if you are wanting to use this as a chance to contribute, we actually will need folks who are able to translate the surveys as well. So I’ll leave a link to some information about that in the show notes. If all of that stuff about contribution didn’t make any sense, then just like keep an eye out from your meetup organizer and they will make sure that you have that survey so that you can have your voice heard.
\n\n\n\n[Josepha Haden Chomphosy 00:08:33]
\n\n\n\nAnd then item three is less of an item. I mean, it’s an item cause it’s in this list, but it’s less of, like, a thing to know and more of a general thing to be aware of. It’s a general awareness item. There’s a lot going on in WordPress right now. I can see how hard it is to keep track of some of these things these days.
\n\n\n\nAnd I know as someone who’s looking at this all day every day that, yeah, it’s a lot. And it’s hard to get your bearings. So if you have a team that you contribute to already, don’t forget to reach out to each other, just to check-in. Sometimes we don’t think to ask for help. Sometimes we don’t think to offer help and you know, if no one needs any help from you at that moment, a little hello also can brighten someone’s day.
\n\n\n\nAnd that, my friends, is your smallest 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:\"12940\";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: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:26:\"WordPress 6.0 “Arturo”\";s: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://wordpress.org/news/2022/05/arturo/\";s: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, 24 May 2022 20:01:05 +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: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.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:\"\";}i:2;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=12879\";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:278:\"Say hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. With nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Download it now! As of today, WordPress powers more than 42% of websites worldwide.\";s: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:\"Matt Mullenweg\";s: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:57729:\"\nSay hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. Known for his influence on contemporary Latin jazz, Arturo has pressed more than 15 albums spanning a body of work across five decades.
\n\n\n\nTake some time to explore WordPress 6.0, built to help you unlock your creative aspirations and make your site-building experience more intuitive. And check out some of Arturo’s inspirational sounds that span Afro Cuban jazz, contemporary Latin jazz, and so much more.
\n\n\n\nWith nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Download it now! As of today, WordPress powers more than 42% of websites worldwide.1
\n\n\n\nSite owners and administrators should upgrade to take full advantage of the many stability, performance, and usability enhancements today. 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\nExpanding Gutenberg into a full site editing experience in WordPress means that all of the problems the community had to address were complex and far-reaching. WordPress 6.0 is an example of the community’s commitment to tackling these tough challenges together. With thoughtful updates to the writing experience, building better block functionality, and adding a new intuitive style switcher, I’m really proud of the work that’s been done in this release to make a great site editing experience.
Josepha Haden Chomphosy, Executive Director
Writing improvements abound, whether you’re writing a brand new post or adding elements to an existing page. Explore more ways to streamline your content creation process, including:
\n\n\n\n[[
` to quickly access a list of recent posts and pages.Block themes now include the option to contain multiple style variations. This expands the new Style system even further and enables shortcuts to switch the look and feel of your site all within a single theme. In block themes that support this feature, you can change both the available settings, like the font-weight, and the style options, like the default color palette. Change the look and feel of your site with just a few clicks.
\n\n\n\nWordPress 6.0 includes five new template options for block themes: author, date, categories, tag, and taxonomy. These additional templates provide greater flexibility for content creators. Tailor each with the tools you already know or with the following new options in this release:
\n\n\n\nPatterns will now appear when you need them in even more places, like in the quick inserter or when creating a new header or footer. If you’re a block theme author, you can even register patterns from the Pattern Directory using `theme.json
`, enabling you to prioritize specific patterns that are most helpful to your theme’s users.
Design tools grow more powerful and intuitive with each release. Some highlights for 6.0 include:
\n\n\n\nNew keyboard shortcuts enable you to select multiple blocks from the list view, modify them in bulk, and drag and drop them within the list. List View can be opened and closed easily; it comes collapsed by default and it automatically expands to the current selection whenever you select a block.
\n\n\n\nNow you can lock your blocks. Choose to disable the option to move a block, remove a block, or both. This simplifies project handover, allowing your clients to unleash their creativity without worrying about accidentally breaking their site in the process.
\n\n\n\nThis release includes several updates focused on improving the performance of WordPress. These enhancements cover a range of performance areas including improving the page and post-load speed, reducing the execution time of various query types, caching, navigation menus, and much more. The performance team working group is an important focus area of the core development team. For more information on this group’s work, please follow their work on Making WordPress with the #performance hashtag.
\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.0 includes more than 50 updates specifically focused on enhancing the accessibility of the platform. You can read about these updates and learn more about the accessibility initiatives that are ongoing.
\n\n\n\nSee WordPress 6.0 in action! Watch a brief overview video highlighting some of the major features debuting in WordPress 6.0.
\n\n\n\nExplore learn.wordpress.org for quick how-to videos and lots more on new features in WordPress. Or join a live interactive online learning session on a specific WordPress topic.
\n\n\n\nDevelopers can explore the WordPress 6.0 Field Guide. It is overflowing with detailed developer notes to help you build with and extend WordPress.
\n\n\n\nRead the WordPress 6.0 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\nWordPress 6.0 would not have been possible without the contributions of more than 500 people in at least 58 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\nAaron Jorbin · Aaron Robertshaw · Abdullah Ramzan · Abha Thakor · Adam Silverstein · Adam Zielinski · Addie · adi64bit · Adil Öztaşer · Adil Ali · agepcom · Ahmed Chaion · Aki Hamano · Akira Tachibana · Alain Schlesser · Alan Jacob Mathew · alansyue · Albert Juhé Lluveras · albertomake · Alefe Souza · Aleksandar Kostov · Alex Concha · Alex Lende · Alex Mills · Alex Stine · aliakseyenkaihar · Alkesh Miyani · Alok Shrestha · Amanda Giles · Andrea Fercia · Andrei Draganescu · Andrei Surdu · Andrew Dixon · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrey \"Rarst\" Savchenko · André · Andy Fragen · Angelika Reisiger · Ankit K Gupta · Anne McCarthy · Anoop Ranawat · Anthony Burchell · Anthony Ledesma · Anton Vlasenko · antonrinas · Antony Booker · arcangelini · Ari Stathopoulos · Arne · Arpit G Shah · artdecotech · ArteMa · Arthur Chu · Asaquzzaman mishu · atomicjack · Aurélien Joahny · Aurooba Ahmed · Barry · Barry Ceelen · Bartosz Gadomski · Beda · Ben Dwyer · Benachi · Bernie Reiter · BettyJJ · Bhrugesh Bavishi · binarymoon · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Blair Williams · BlogAid · Boone Gorges · Brandon DuRette · Brandon Kraft · Brian Alexander · bronsonquick · Brooke Kaminski · Brooke. · Bruno Ribaric · caraya · Carlos Bravo · Carlos Garcia · Carolina Nymark · cbigler · Chad Chadbourne · Channing Ritter · charleyparkerdesign · charlyox · Chintan hingrajiya · Chloe Bringmann · Chouby · Chris Lubkert · Chris Van Patten · chriscct7 · clonemykey · Colin Stewart · conner_bw · Cory Hughart · Courtney Robertson · Crisoforo Gaspar · Dan Soschin · Daniel Bachhuber · Daniel Iser · Daniel Richards · danieldudzic · darerodz · Dat Hoang · Dave Smith · David Baumwald · David Biňovec · David Calhoun · David Gwyer · David Herrera · David Shanske · Deb Nath Utpol · Delowar Hossain · denishua · Dennis Claassen · Dennis Snell · Dhanendran · Dharmesh Patel · dhusakovic · Dilip Bheda · Dion Hulse · Dominik Schilling · donmhico · drago239 · Drew Jaynes · dromero20 · Eddy · ehtis · Eliezer Peña · Ella van Durpe · Emmanuel Hesry · Enrico Battocchi · eric3d · Erik Betshammar · espiat · Estela Rueda · etaproducto · EverPress · Fabian Kägy · Fabio Blanco · Faison · Felipe Elia · Felix Arntz · Femy Praseeth · Florian Brinkmann · Florian TIAR · FolioVision · Francesca Marano · Francisco Vera · frankei · furi3r · Gabriel Rose · gadhiyaravi · Garrett Hyder · Garth Mortensen · Gary Jones · Gary Pendergast · genosseeinhorn · George Hotelling · George Mamadashvili · George Stephanis · Gerardo Pacheco · Glen Davies · Grégory Viguier · Grant M. Kinney · Greg Ziółkowski · gregoiresailland · Guido Scialfa · gumacahin · gvgvgvijayan · Hareesh S · Hasanuzzaman · Hasnain Ashfaq · Hauwa Abashiya · Haz · Helen Hou-Sandi · HelgaTheViking · Henry Wright · Hilay Trivedi · Hitendra Chopda · HristoK · Hugh Lashbrooke · Héctor Prieto · Ian Belanger · Ian Dunn · ianatkins · ianmjones · ImanGM · imokol · Isabel Brison · ishitaka · itsamoreh · Iulia Cazan · Ivan Lutrov · jadpm · Jake Spurlock · jakeparis · James Koster · Jamie VanRaalte · Jan Weiss · janh2 · Jarret · Jason Johnston · Jason LeMahieu (MadtownLems) · Javier Arce · Javier Prieto · Jay Trees · jazbek · Jean-Baptiste Audras · Jeff Bowen · Jeff Matson · Jeff Ong · Jeff Paul · Jenny Dupuy · Jenny Wong · Jeremy Felt · Jeremy Herve · Jeremy Yip · Jez Emery · jhned · jhnstn · jigar bhanushali · jiteshdhamaniya · jnz31 · Joe Dolson · Joe McGill · Joen Asmussen · Johannes Kinast · John Blackbourn · John James Jacoby · John Regan · John Watkins · Jon Brown · Jonathan Champ · Jonathan Desrosiers · Jonny Harris · Jono Alderson · Jorge · Jorge Costa · José Arcos · Josepha · Josepha Dambul · Joshua Fredrickson · Joy · jrivett · jsnajdr · juanlopez4691 · JuanMa Garrido · Juliette Reinders Folmer · Junaid Ahmed · Justin Ahinon · Justin Busa · Justin Tucker · KafleG · Kai Hao · Kajal Gohel · kapacity · Kapil Paul · karolinakulinska · Kaspars · kbatdorf · Kelly Choyce-Dwan · Kemory Grubb · Kerry Liu · Kev Provance · Kharis Sulistiyono · Kirtan Gajjar · Kjell Reigstad · KMix · Knut Sparhell · Konrad.K · Konstantin Obenland · kpegoraro · kubiq · Kukhyeon Heo · laurlittle · Lena Morita · lenasterg · leskam · Lew Ayotte · linux4me2 · Lisa Schuyler · lkraav · Louis · Lovekesh Kumar · Lucas Karpiuk · Luis Felipe Zaguini · luisherranz · Luke Cavanagh · Lukman Nakib · M. van Dam · macbookandrew · Maciej · Maggie Cabrera · maguijo · Mahbub Hasan Imon · malthert · manfcarlo · Manzur Ahammed · Marcelo de Moraes Serpa · Marco Ciampini · Marcus Kazmierczak · Marin Atanasov · Marius L. J. · Mark Jaquith · Markus Kosmal · marv2 · Mary Baum · Mat Lipe · Mathieu · Matias Ventura · matiasbenedetto · Matt Chowning · Matt Martz · Matt Mullenweg · Matt Royal · Matt Stoney · Matt Wiebe · maur · Mauriac AZOUA · Max Kellermann · Mehedi Foysal · Meher Bala · mgol · Michael Burridge · Michal Czaplinski · Miguel Fonseca · Mike Auteri · Mike Schroder · miken32 · Milan Dinić · Milana Cap · Minal Diwan · Mirco Babini · MMDeveloper · Mohadese Ghasemi · Mohammad Ahsan Habib · Mohammad Rockeybul Alam · MohammadJafar Khajeh · Morten Rand-Hendriksen · moushik · mqudsi · Muhammad Faizan Haidar · Mukesh Panchal · Mustaque Ahmed · Nabil · Nagesh Pai - a11n · Nalini Thakor · Nathan · navigatrum · Nayana Maradia · Nicholas Garofalo · Nick Ciske · Nick Diego · Nicolas Juen · nidhidhandhukiya · Nik Tsekouras · Nil · nmschaller · Noah Allen · oakesjosh · oguzkocer · Oliver Campion · Omar Alshaker · opr18 · Otshelnik-Fm · overclokk · ovidiul · Paal Joachim Romdahl · Pablo Honey · Paolo L. Scala · Paragon Initiative Enterprises · Pascal Birchler · Paul Bearne · Paul Biron · Paul Ryan · Paul Von Schrottky · paulkevan · Pavan Patil · Pavlo · pbking · Pedro Mendonça · Petar Ratković · Peter Smits · Peter Westwood · Peter Wilson · petitphp · petrosparaskevopoulos · Petter Walbø Johnsgård · pgpagely · Phil Johnston · Pieterjan Deneys · pikamander2 · Piotrek Boniu · Pooja Derashri · Pooja N Muchandikar · Pravin Parmar · Presskopp · presstoke · Priyank · pypwalters · r-a-y · Rachel Baker · Rafi Ahmed · Ramanan · Ramon Ahnert · Ramon James · Ramona · Ravi Vaghela · Ravikumar Patel · Razvan Onofrei · Rehan Ali · Remy Perona · Riad Benguella · Rian Rietveld · Rich Tabor · Richard B. Kreckel · ricomoorman · Rob Scott · Robert Anderson · Rolf Allard van Hagen · Rolf Siebers · Rostislav Wolný · Rufus87 · Ryan Boren · Ryan Fredlund · Ryan McCue · Ryan Welcher · Sébastien SERRE · Sören Wrede · Sabbir Ahmed · Sabbir Hasan · Sami Falah · Sami Keijonen · Sanjeev Aryal · santosguillamot · Sarah Norris · Sarah Snow · sarayourfriend · Sathiyamoorthy V · Sayedul Sayem · sbossarte · sclayf1 · Scott Buscemi · Scott Reilly · Scott Taylor · Segayuu · Sergey Biryukov · sheepysheep60 · Shital Marakana · Shreyas Ikhar · siddharth ravikumar · Siddharth Thevaril · silb3r · Simon Blackbourn · Simon Prosser · simonhammes · Siobhan · Smit Rathod · snapfractalpop · socalchristina · Spencer Cameron-Morin · stacimc · stefanfisk · Stefano Lissa · Stefano Minoia · Stefanos Togoulidis · Stephen Bernhardt · Stephen Edgar · Stephen Harris · Steve Grunwell · Subrata Sarkar · Sumit Singh · Sumit Singh (WP Lovers) · Sumon Sarker · SunilPrajapati · sunyatasattva · Sven Wagener · Sybre Waaijer · Synchro · Takashi Kitajima · Tammie Lister · tharsheblows · Theo H · Thimal Wickremage · Thomas McMahon · Thomas Patrick Levy · Thomas Pike · Till Krüss · Tim Blankenship · Tim Nolte · Timothy Jacobs · tobifjellner (Tor-Bjorn Fjellner) · Tom · Tomasz Tunik · Tomek · Tomoki Shimomura · Tony Tahmouch · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Tracy · Tran Ngoc Tuan Anh · trex005 · Trinadin · tszming · tumas2 · twstokes · Tynan Beatty · tzipporahwitty · Uday Kokitkar · ugljanin · Ugyen Dorji · Ulrich · Utkarsh · valer1e · versusbassz · Vicente Canales · Vishal Kumar · vlad.olaru · Volodymyr Kolesnykov · vortfu · WebMan Design | Oliver Juhas · Wendy Chen · Wes Theron · Weston Ruter · whoisnegrello · Will Skora · wpmakenorg · wpsoul · WraithKenny · wslyhbb · Xidorn Quan · Yui · Yunus Ertuğrul · Zebulan Stanphill · znuff · Česlav Przywara
\n\n\n\nBy release day, 76 locales had translated 90-percent or more of WordPress 6.0 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 205 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\nSix-point-oh is here
Time to download and upgrade
Let’s pause, celebrate
1 According to W3Techs as of May 5, 2022.
\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:\"12879\";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: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:65:\"WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing\";s: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://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-3-rc3-now-available-for-testing/\";s: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, 17 May 2022 16:39:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.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:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12866\";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:166:\"WordPress 6.0 Release Candidate 3 is now available for testing! You can download and help test RC3 in three ways. 6.0 is planned for general release on May 24, 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4240:\"\nWordPress 6.0 is scheduled for release next week on May 24, 2022! This RC3 release is the final opportunity for you to test and help contribute to making the 6.0 release great.
\n\n\n\nYou can view changes since the RC2 release via Gutenberg and Trac.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC3 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC3 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the release candidate (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command:
\n\n\n\nwp core update --version=6.0-RC3
All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC3 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24.
\n\n\n\nReview the WordPress 6.0 Field Guide, for more details on this release.
\n\n\n\nReview additional information on the full 6.0 release cycle.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail upcoming changes.
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages.
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nIt’s near time for six
The reward is the journey
Just one week to go
Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat.
\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:\"12866\";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: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:127:\"WP Briefing: Episode 31: Open Source & Accessibility– Celebrating Global Accessibility Awareness Day With Guest Joe Devon\";s: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:140:\"https://wordpress.org/news/2022/05/episode-31-open-source-accessibility-celebrating-global-accessibility-awareness-day-with-guest-joe-devon/\";s: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, 16 May 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=12855\";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:392:\"In the thirty-first episode of the WordPress Briefing, GAAD Co-Founder Joe Devon joins WordPress Executive Director Josepha Haden Chomphosy to discuss Global Accessibility Awareness Day and the role of open source in accessibility. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Guest: Joe […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/05/WP-Briefing-031.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: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:\"\";}}}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:33186:\"\nIn the thirty-first episode of the WordPress Briefing, GAAD Co-Founder Joe Devon joins WordPress Executive Director Josepha Haden Chomphosy to discuss Global Accessibility Awareness Day and the role of open source in accessibility.
\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.
[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. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nY’all, we’ve got an absolutely jam-packed couple of weeks in WordPress. We’ve got events happening and releases shipping and contributor days being coordinated (I almost said contributor days being contributed). That’s also what they’re doing. I’ll share some of those highlights in today’s small list of big things, but I did want to specifically call out something that’s coming up this week on Thursday (May 19, 2022), and that something is Global Accessibility Awareness Day.
\n\n\n\nThe team of contributors over on the Accessibility team has participated in the Global Accessibility Awareness Day in the past. So I thought it would be interesting to hear from one of the co-founders of this particular day of awareness.
\n\n\n\n[Josepha Haden Chomphosy 00:01:27]
\n\n\n\nAll right. And with that, Joe Devin, would you like to tell us a little bit more about yourself?
\n\n\n\n[Joe Devon 00:01:34]
\n\n\n\nSure. So I am the co-founder of Global Accessibility Awareness Day, which is a day that goes viral every year on the third Thursday of May. We typically have the Twitter reach on the GAAD hashtag on Twitter of 200 million users, which is, I think, pretty much their active user count. We stopped counting once we hit their daily active user count.
\n\n\n\nAnd then, I am Chair of the GAAD Foundation, which we launched last year. And then I have a day job too, where I’m CEO and co-founder of Diamond, which is an inclusive digital agency that builds software accessibly by default.
\n\n\n\n[Josepha Haden Chomphosy 00:02:15]
\n\n\n\nWonderful. Well, we are so excited to have you today. I said we like it’s me and the mouse in my pocket—we in the WordPress community that’s going to listen to this. Super excited to have you today. So you mentioned GAAD, Global Accessibility Awareness Day. Last year was your 10th anniversary, which is very exciting, but like with so many good things, I hear it all started with a blog post and a blog post on WordPress, no less.
\n\n\n\nSo I’d love to hear about how GAAD evolved from that, with, as I understand it, your co-founder of Jennison (Asuncion). That must be where you met him, I assume.
\n\n\n\n[Joe Devon 00:02:51]
\n\n\n\nYes. Yes. So what happened was I started a WordPress blog called My SQL Talk. So it’s a database blog, and I just thought it was a brilliant name. I mean, My SQL Talk, like that, should be super popular.
\n\n\n\nAnd it probably had maybe ten people who ever looked. Um, and then my dad was getting older, and my dad was a survivor of the concentration camps, and he was a genius. He spoke ten languages. It, he was one of those people. That, when he walked into a room, he just commanded respect. You knew that there was history. I don’t know how to explain it really, but it was special when my dad walked into the room. And considering all of this that he suffered in his life, watching him get older and struggle, particularly with his banking, was very painful to see. And the bank wasn’t accessible, so I wrote this blog post proposing that we create a Global Accessibility Awareness Day.
\n\n\n\nSometimes I get these visions, and they never turn into anything. But while I think about it, I’m like, “all right, let’s write this blog post and this can definitely work. Right?” And then you finish the blog post to hit send, and you’re like, “this is not going to work.”
\n\n\n\nBut I wasn’t even smart enough to do social media on it. But fortunately, WordPress had an auto-tweet feature, and it tweeted it out, and Jennison Asuncion, my co-founder, happened to be around and not out that Saturday night. And he read the blog post, and he said, “this is a great idea. Let’s make it happen.”
\n\n\n\nAnd we had two busy people, but we both had a community. He had the accessibility community, and I was building a tech scene in Los Angeles. And what I discovered is if you combine a great idea with the community, great things can happen.
\n\n\n\n[Josepha Haden Chomphosy 00:04:49]
\n\n\n\nOh man, you’re speaking my language over here, helping people find their communities, knowing that community is the thing that is the lifeblood of society.
\n\n\n\nThat sounded like a tautology. It is not a tautology. You can have a society with an attempt to not have any sort of community around it, but I bet it doesn’t work very well. Well, that’s, that’s very interesting. And so you all just kind of talked through what that would look like, I assume in confidence, or that would have to take place, right? Or was it on Twitter in those days?
\n\n\n\n[Joe Devon 00:05:24]
\n\n\n\nOh, you could still look in the comments and see the back and forth of Jennison and a bunch of other people that got pretty involved with GAAD that are some legendary folks in there. It’s kind of mind-blowing because I dunno how, how you feel, but for me, when I used to code, uh, three months later, I’d look back at old code and be like, “oh, I suck,” you know, or write an email even and you look back on it a day later and are like “what a stupid email, how stupid am I?” You know? But I look back on that one after ten years; I was scared to look at it because I’m like, it must’ve been really bad. But you know, it kind of held up, and exactly what I wrote in there happened – to my utter shock.
\n\n\n\n[Josepha Haden Chomphosy 00:06:06]
\n\n\n\nBut also, it’s kinda nice, though, to look back and be like, “oh, I used to be much dumber.”
\n\n\n\nCause then you’re like, look how far I’ve come. I’m no longer that dumb. I’m a different kind of dumb now; good for me. I always hope to be a different kind of dumb as I go forward.
\n\n\n\nSo then, okay, so that was your ten-year anniversary last year. GAAD, in general, now has been going on for 11 years, and at the time of this recording, in a couple of weeks, but then probably a week when it finally publishes, you have your next, your next round of that going.
\n\n\n\nI think it seems safe to assume that awareness of the need for accessibility has increased during that time, but we all know that the work of accessibility is ongoing. And so, I’m just curious to hear from your perspective if the awareness of the need for accessibility has generally started to permeate developer communities.
\n\n\n\nAnd are you seeing more developer awareness around the need for accessibility in tech in general?
\n\n\n\n[Joe Devon 00:07:12]
\n\n\n\nYeah. You know, it’s not enough. It’s certainly improved a lot. I keynoted a conference probably four years after GAAD started, maybe five, and I kind of assumed nobody would have heard of accessibility, and I was taken aback when I asked who had heard of it, and a good chunk of the room had. So even then, there had been a difference, and I’d say now I see accessibility mentioned a lot more in conferences and stuff. But when it comes to actually building it, there’s a tremendous amount of ignorance. There, there still needs to be a lot more awareness.
\n\n\n\nAnd I think partially people are a little bit scared to dip their toe because they’re scared that they’re going to be told that “no, it’s not accessible,” or that they’re going to say the wrong word or offend somebody. So I’d say that there’s some degree of trepidation, but also developers, and it’s not just developers, designers, and product people. There’s so much to learn, and it’s like, “oh God, there’s another piece that I have to learn.”
\n\n\n\nAnd I’m so glad that you invited me on this podcast because it’s the developers that, you know, I am a developer, not anymore, I haven’t touched code in years, but that’s where I came from. Right? This is my peach, right? Particularly WordPress folks, because I had done a fair bit of WordPress before I moved on to some other things. And, I think we have to talk about usability and understand that accessibility is so much more than how we look at disability.
\n\n\n\nAnd if you don’t mind, I’m going to ask you a question. How do you think the typical WordPress developer or designer would define disability?
\n\n\n\n[Josepha Haden Chomphosy 00:09:05]
\n\n\n\nin the kinds of conversations that I’ve had over the years, it frequently has to do with visual things. Because it’s just screens all day, right? And that’s a primary area where our designers and developers really have made some effort.
\n\n\n\nBut my personal favorite sort of, of example, for like, when you’re looking at how to make sure that your products are accessible is, what, if you have to use your website, or you have to build your website using only one arm. Because that gives you an opportunity to kind of look at disability from a permanent standpoint.
\n\n\n\nLike if you have lost permanent use of one arm, but also gives you an opportunity to look at the temporary options for that sort of lack of mobility. Like you’re a mother with an infant, and so you have to be able to, you know, get your stuff done with one arm. And so I know that we paid a bunch of attention to screen readers and what works in not way back in 2018 and 2019 did a lot of work with. Literally zero screen. And can you still do the thing that you need to do, which was incredibly difficult. And I was really excited to see what our developers came up with around that. But I think that that is quite a bit of that discussion as we’re going through it from the beginning to the end.
\n\n\n\n[Joe Devon 00:10:27]
\n\n\n\nYeah. I mean, that’s a great answer, and you definitely understand some of the nuances way better than I think that the average creator, digital product creator, I’m including the, you know, the product people, the designers, and the developers.
\n\n\n\n[Josepha Haden Chomphosy 00:10:42]
\n\n\n\nWe’re very fortunate to have more than just developers in WordPress.
\n\n\n\n[Joe Devon 00:10:50]
\n\n\n\nThe reason I bring this up is that the WHO (World Health Organization) had to; they’re the ones that did massive research across the globe. And they had to, they had to come up with a definition, and in their definition, they needed to draw a line. Typically, I don’t remember the exact thing cause it’s a 350-page report, and I kept looking for where they defined it again.
\n\n\n\nIt was a little hard to find, but essentially it’s if there’s a major disability or a disability that impacts some significant portion of your day-to-day activities. And that’s really great when you’re trying to do a report on how many disabilities there are out there; what percentage of the population has a disability?
\n\n\n\nAnd their figures are something like 15% of the population has a disability, which is a huge number. But at the same time, they also mentioned that 2.2 billion people have a visual impairment. And we also know that over 33% of the population is over 50, and I’m included in that population. And I can say that when you’re over 50, you know, I’ve got clouds in my eyes.
\n\n\n\nI don’t know where they came from, but they definitely make it harder to see. When I’m in a restaurant, I can’t focus on the person across from me the same way. My hearing is not the same, and anybody over 50 is going to have certain impairments and won’t see as well; color contrast issues are a big deal.
\n\n\n\nBeing able to raise the font is a big deal. And I think that accessibility is connected in most people’s minds with disability. And they’ll attach that to something like being blind or being deaf or hard of hearing or having a missing limb or having some other kind of disability.
\n\n\n\nAnd, as a result, they’re like, “well, I don’t even know any people in that category possibly,” and as a result, they’re like, “well, how important is this?” Yes. They might feel guilty. I should do the right thing. This is the right thing to do. But honestly, like how much money should I spend on it? How much, what percentage of my time should I spend on it?
\n\n\n\nAnd it’s because they don’t realize that everybody has different abilities. And so, I’m starting to go away from even talking about disabilities and asking people to remember that all of us perceive things differently.
\n\n\n\nDo you remember the gold dress where they were trying to say, what color is this dress? Is it gold and white or blue and black? And it is blue and black, but to me, all I see is gold and white. And then there was Laurel or Yanny. Do you remember that?. And some people heard it, and typically older people heard it as Laurel, and I’ve, and I do this in some of my presentations. I play that, that sound. And usually, it’s Laurel for me, but sometimes it’s Yanny. Even personally, it changes.
\n\n\n\nAnd so, we have a totally different perception. Now think about memory. There’s a different kind of blindness. If you try and remember, let’s say a relative or a friend that is no longer. How well do you see that picture?
\n\n\n\nBecause for me, it is very, very vague, but for some people, they say, and I’ve been asking people, and I’d love your answer as well. How vivid is it? And some people say, I can read the, I can see the pattern on the shirt. It’s as vivid as if I see with opening my eyes, seeing, you know, the regular in front of me, and I can even read a name tag in the memory.
\n\n\n\nAnd I’m like, Woah, so maybe I’m blind in a way. Right? So how do you see it? How do you remember things?
\n\n\n\n[Josepha Haden Chomphosy 00:14:42]
\n\n\n\nOh, I’m a, I’m a real visual person and a tactile person. And so, like if I interacted with someone, I’m very likely to be able to picture, like, recreate that mental picture pretty well in my mind. I recently, very recently, met some of my first people in that executive leadership space who were like, yeah, I don’t, I don’t visualize things.
\n\n\n\nAnd I was like, what are you, how do you do this work? Because like, you have to be able to do that. And they were like, no, I don’t have mental pictures.
\n\n\n\n[Joe Devon 00:15:13]
\n\n\n\nSome people don’t have an inner dialogue.
\n\n\n\n[Josepha Haden Chomphosy 00:15:17]
\n\n\n\nI don’t understand that either,
\n\n\n\n[Joe Devon 00:15:19]
\n\n\n\nMe either. So accessibility studies all of these differences with respect to how you’re presenting all of this information.
\n\n\n\nAnd if you don’t pay attention to accessibility, you’re really just missing out. And then there’s colorblindness. If you’re creating something like slack that has an online/offline indicator, and you only use red and green for people who are colorblind, they see gray and gray. And so what I’m trying to teach the community with digital product creators is that no, you cannot ignore it.
\n\n\n\nYou can ignore accessibility, but then you’re not good at your job. I mean, I don’t mean to say it in an offensive way, but you’re not good at your job if you’re unaware. If you break a rule on purpose, great. But if you don’t know the rule, it’s just a lack of craft, and you absolutely should make it a priority.
\n\n\n\nAnd you’re not doing it as a charity. You’re doing it because you care about your users, and you care about your craft, and you want to build things well, and it’s a necessity. And I think that this is the kind of message that our community needs to hear.
\n\n\n\n[Josepha Haden Chomphosy 00:16:31]
\n\n\n\nI want to touch on something that you sort of brought up a bit, um, at the start of the answer there.
\n\n\n\nSo you brought up the concept of usability. And in the last time that I did a podcast about accessibility, I defined accessibility as a subset of usability. Do you think that if we were to consistently draw that line for people so that it’s not just like accessibility is this thing that you should do outside of usability?
\n\n\n\nIf we were to more consistently draw that line, do you think that that would help people to see and understand better that its shades of existence, usability, and accessibility?
\n\n\n\n[Joe Devon 00:17:10]
\n\n\n\nOh, 100%, a hundred percent. And in my company, we kind of realized that that’s exactly what we have to do. We have to see this as usability.
\n\n\n\nAnd I don’t, we talk about accessibility a lot, but I don’t want to. It’s part of the plumbing for us. We’ve made it part of the plumbing, and I can tell you it’s a struggle to take accessibility and make it part of an organization, even when you’re bringing it top-down, believe it or not. For our teams, particularly the designers, they are blown away by what they’re learning because they’re improving their craft.
\n\n\n\nAnd design is typically where there’s a struggle to get accessibility accepted because there seems to be a very strong idea of what a design should look like. And I think it’s really about the approach because UX and design it’s all about empathy for people. And when you approach it, not as, even though empathy should mean that, that, you know, do the right thing at the same time, it’s more about empathy for your user, and your user includes so much more than just people with disabilities that you haven’t run into somebody that has that disability and therefore you build it better, and it’s, it’s completely blown their mind. They love it. They love doing it. And I’m not hiring people with accessibility coming in. We’re training them to work accessibly.
\n\n\n\n[Josepha Haden Chomphosy 00:18:34]
\n\n\n\nSo I think it’s interesting that you talk about empathy as part of being able to make sure that you’re creating something that’s accessible because I actually feel like empathy is. Like it’s being considered this gold standard for many, many things right now. And I think it actually is more harmful in the long run than instead making altruistic choices.
\n\n\n\nAnd so, I have a blog post that I will link in our show notes that will kind of help everybody see more fully my concept there. But when you rely on empathy, you do kind of have to rely on one, being able to run into all of the issues you were mentioning. You have to know people who have problems in order to know that the problems exist.
\n\n\n\nAnd then you also kind of have to assume that once you have willingly put yourself into the discomfort of that kind of disability, whatever, wherever it exists on that spectrum, your experience of that discomfort is the same as someone who lives with it. And I just don’t think that we can necessarily do that.
\n\n\n\nI always think that trying to do the altruistic thing, like doing your research and figuring out what it is and trying to make decisions on behalf of other people as best you can, which is a terrible thing. Still, like decisions that take into account the experiences that people are sharing with you and then going to them and saying, “does this make that experience better or worse?” is the more sustainable option from my perspective, this is specifically leadership. Still, I think it’s true for accessibility as well, and probably product design as a whole, but it’s very difficult. Like people really feel like they understand the concept of empathy right now. And I do think that sometimes that leads us down the wrong path for things.
\n\n\n\nWhat’s your thought on that? I think you kind of agree based on what your answer was
\n\n\n\n[Joe Devon 00:20:33]
\n\n\n\nOh, no, absolutely. And you know, we, you, can’t never about us without us, as the common saying, and we’ve gathered a group of a hundred people with a wide variety of disabilities for research. Whenever we do any UX and research, and sometimes we’re asked to just do research projects, we go out and ask the users.
\n\n\n\nWe had some really interesting companies approach us to do innovation and accessibility, and they had strong assumptions. We looked at the assumptions and agreed with it, but we’re like, all right, they were smart. They said, “vet this with users for us, please,” because they didn’t want to gather their own group.
\n\n\n\nWe vetted with users, and we’re blown away, always blown away because there are so many things you just don’t know unless you’ve lived with a particular disability. You can’t guess, and you’ve got to speak to your users and a wide variety of them.
\n\n\n\n[Josepha Haden Chomphosy 00:21:30]
\n\n\n\nYes, absolutely. Absolutely. What role does open source play in expanding accessibility, either in specifically the digital space or just accessibility in general?
\n\n\n\n[Joe Devon 00:21:42]
\n\n\n\nI guess if the question is, what role does it play? I would say the role it plays is it is, unfortunately, it makes accessibility worse because, for the most part open source is not very accessible. And it’s a personal passion of mine, so I’m really glad that you brought that up.
\n\n\n\nYou know, it is so bizarre. You write a blog post and then it goes viral, and it goes viral every year to a degree that you can’t even believe it, that all these companies that you know are running events. Privately, publicly talking about it. And then you get all these people thanking you for what you’ve done year after year.
\n\n\n\nAnd then one year, you read on Twitter, The Blind Onion; I’m sure you’re familiar with The Onion, the satirical clip, there’s the Blind Onion. And they tweet out, “Now that Global Accessibility Awareness Day is over, we look forward to 364 days of global accessibility oblivion.” And that really hurt at the time, but at the same time, and I was told to ignore it, don’t worry about it, but I’m like, no, this is coming from a place of pain.
\n\n\n\nAnd the point of GAAD was to make a difference. It wasn’t too to just give everybody an opportunity to say, “Hey, look at what we’re doing,” and then not make a difference. So, as a result of that, I started to think about, well, where are we with this? And, and so I’ve created a state of accessibility report that through my company, we’re able to run for a few years, and it’s not, you know, the state is not great.
\n\n\n\nAnd I’m like, well, what can we do to change things? So, as a result of all of this, I really wanted to figure out, well, what can we do to make sure that GAAD does make a difference? And so, I came up with the idea of the GAAD pledge, which is specifically meant for open source frameworks.
\n\n\n\nAnd the idea of the GAAD pledge is that an open source framework, when they are ready, takes the pledge to make accessibility a core value of the framework. Now, terms of what that actually entails are different for every single project because every project is unique. We did create a bit of a framework, which had the idea of saying, okay, you’re going to, first of all, create an accessibility statement that says that this framework is going to conform to whatever, WCAG, which is Web Content Accessibility Guidelines, to whatever WCAG level is decided and is appropriate for the framework. That there’s going to be documentation for anybody that is downloading this piece of open source project and trying to implement it, that there should be guidelines for them, that all of the examples should be accessible.
\n\n\n\nIt’s really important because even the frameworks that try to pay attention to accessibility. You’ll often see that people from the community will provide examples, and they’re inaccessible. And it’s really sad when you see that because so many people are just copy-pasting. That’s typically how it works, and they’re going to copy-paste something bad. So putting a statement around it, I think, would be really great.
\n\n\n\nAnd what we’re hoping to see is that lots and lots of big open source communities decide to take the pledge. And then it’ll sort of be table stakes that any new open source projects as well look, all of these frameworks that made it, they took the pledge and therefore we should take the pledge as well.
\n\n\n\nAnd so the very first year, we had React Native take the pledge, and they put a lot of effort into their accessibility. The second group to take it was Ember.js, and they always put a lot of effort into their accessibility, and they continued that effort. We’re about to announce the next one, but we’re still two weeks away.
\n\n\n\nSo I can’t say anything yet, but yeah, we’re, uh, we’re hoping for a lot more uptake on, on the gap pledge because it, it affects so many people downstream. WordPress’s what percent of the web right now? 43%? So there you go. That’s so many people.
\n\n\n\n[Josepha Haden Chomphosy 00:25:57]
\n\n\n\nSo many people. Yeah, fun fact Gutenberg, our current rewriting of the editing experience in WordPress, primarily uses React. And so, I’m glad to hear that they have taken that pledge as well.
\n\n\n\nAs with any good cooking, it starts with good ingredients.
\n\n\n\n[Joe Devon 00:26:12]
\n\n\n\nYou said it. That was great. I wish I was a cook, though.
\n\n\n\n[Josepha Haden Chomphosy 00:26:23]
\n\n\n\nI love it. All right. Let’s what keeps you up at night when it comes to the state of accessibility?
\n\n\n\n[Joe Devon 00:26:29]
\n\n\n\nWhat keeps me up at night is how to move the needle. It is such a big thing to change. And there are so many angles that you can approach this with, but at the end of the day, it’s, it’s a monster.
\n\n\n\nIt’s a monster. There are so many legacy sites out there. If you look at WebAIM, they do a yearly report on the state of accessibility as well. They call it the WebAIM Million, and they’re typically seeing 97% inaccessible, 98%. It goes up and down a little bit every year. And that’s, that’s just a huge boat to move.
\n\n\n\nI think we need to at least get the newer, uh, newer websites and mobile apps to move. And what we’ve seen in our state of accessibility report is that only the very top companies seem to put in the effort to make their products accessible. There is a big push with the enterprise companies to do it.
\n\n\n\nThe CEOs are starting to talk about it, but what we need is the entire culture of software development to change. Or I should even say digital product development change and to move that boat is massive. And that’s I put it in my tagline in my email like that’s my mission in life, and I hope to achieve it before I die.
\n\n\n\nSo that keeps me up at night.
\n\n\n\n[Josepha Haden Chomphosy 00:27:52]
\n\n\n\nI think that would keep me up at night as well. I mean, it seems like you are really just personally mission-driven and impact-driven. Do you feel like, in the event that the work that you’ve accomplished so far is what you accomplish, you feel still like you’ve had an impact?
\n\n\n\nI feel like you have had an impact.
\n\n\n\n[Joe Devon 00:28:13]
\n\n\n\nI’m not one of those people that tries to have a legacy or like tries to focus on what my impact is and all of that. I just try and do good work. And hopefully, it just shows at the end of the day. I’m just trying to have the impact without the accolades.
\n\n\n\n[Josepha Haden Chomphosy 00:28:34]
\n\n\n\nI get it. Well, Joe, thank you so much for joining us here on this episode of WP Briefing. You have been a delight to chat with.
\n\n\n\n[Joe Devon 00:28:42]
\n\n\n\nLikewise, it’s really been a pleasure to meet you, and uh, and I appreciate the opportunity.
\n\n\n\n[Josepha Haden Chomphosy 00:28:54]
\n\n\n\nAnd now it’s time for our smallest of big things. As I mentioned at the start, it is packed. Number one tomorrow, May 17th, RC3. So one of the final RCs that we’re going to have for the WordPress 6.0 release, unless something goes horribly, horribly wrong, which I don’t think it will.
\n\n\n\nAnd then, two days after that, Global Accessibility Awareness Day, as I mentioned, will be on May 19th. So, this coming Thursday.
\n\n\n\nAnd then next week, we have the 6.0 release. We have the WordPress 6.0 release on May 24th.
\n\n\n\nThree days after that, WordPress turns 19 on May 27th, starting its final teenage year before we turn twenty in 2023. So that was the rapid-fire dance card for the next two weeks.
\n\n\n\nThe stuff that is happening with and around WordPress for everyone to know. As a heads up, also, many people are headed to WordCamp Europe in Porto(, Portugal). The first week of June, I am going to do a live from WordCamp Europe episode. It will not be live. I’ll just record it live. And so. You know you’ll get to hear me with my hoarsest voice and maybe singing to my computer. Cause that almost always happens at these things.
\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:\"12855\";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: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:65:\"WordPress 6.0 Release Candidate 2 (RC2) Now Available for Testing\";s: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://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-2-rc2-now-available-for-testing/\";s: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, 10 May 2022 18:06:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.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:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12840\";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:171:\"WordPress 6.0 Release Candidate 2 is now available for testing! You can \ndownload and help test RC2 in three ways. You can also help translate WordPress to 100+ languages.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4830:\"\nThe next release candidate for WordPress 6.0 is now available!
\n\n\n\nWordPress 6.0 is scheduled for release on May 24th, 2022 – just two weeks from today.
\n\n\n\n“Release Candidate” means that this version of WordPress is ready for release! Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.
\n\n\n\nThank you to everyone who has contributed towards testing and logging issues to help make WordPress 6.0 stable (and awesome). WordPress still needs your help testing, especially theme and plugin developers.
\n\n\n\nSince the RC1 release on May 3rd, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you RC2 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC2 in three ways:
\n\n\n\nwp core update --version=6.0-RC2
Additional information on the full 6.0 release cycle is available here.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.
\n\n\n\nAll plugin and theme developers should test their respective extensions against WordPress 6.0 RC2 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums so that these items can be investigated further prior to the final release date of May 24th.
\n\n\n\nReview the WordPress 6.0 Field Guide for more details on this release.
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages.
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nAnticipation
Sprinting toward G/A now
Please — test, translate — thanks!
Thank you to the following contributors for collaborating on this post: @dansoschin, @priethor.
\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:\"12840\";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: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:37:\"The Month in WordPress – April 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:69:\"https://wordpress.org/news/2022/05/the-month-in-wordpress-april-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:\"Thu, 05 May 2022 15:01:33 +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:22:\"the 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=12816\";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:329:\"This past month saw a lot of preparation work for WordPress 6.0, due to release on 24 May 2022. This major release brings exciting improvements – read on to find out more about the latest happenings in the WordPress project. WordPress 6.0 Release Candidate 1 The first release candidate (RC1) for WordPress 6.0 is now […]\";s: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:10652:\"\nThis past month saw a lot of preparation work for WordPress 6.0, due to release on 24 May 2022. This major release brings exciting improvements – read on to find out more about the latest happenings in the WordPress project.
\n\n\n\nThe first release candidate (RC1) for WordPress 6.0 is now available for download. Help improve the project by testing and translating this version to non-English languages. Check out the RC1 release post to learn what’s new and how to contribute. For a more in-depth look at the upcoming changes, you can refer to the WordPress 6.0 Field Guide.
\n\n\n\nWordPress 6.0 is packed with all kinds of improvements for everyone. It brings new blocks, accessibility enhancements, refined design tools, the ability to switch theme styles easily, multi-block partial text selection, and a new block locking interface, to name a few of its highlights.
\n\n\n\nHave a story that we could include in the next issue of The Month in WordPress? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @rmartinezduque, @cbringmann, @dansoschin.
\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:\"12816\";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: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:33:\"WordPress 6.0 Release Candidate 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2022/05/wordpress-6-0-release-candidate-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, 03 May 2022 17:18:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.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:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12799\";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:171:\"WordPress 6.0 Release Candidate 1 is now available for testing! You can \ndownload and help test RC1 in three ways. You can also help translate WordPress to 100+ languages.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7242:\"\nThe first release candidate (RC1) for WordPress 6.0 is now available!
\n\n\n\nThis is an important milestone on the 6.0 release cycle journey. “Release Candidate” means that this version of WordPress is ready for release! Before the official release date, time is set aside for the community to perform final reviews and help test. Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.
\n\n\n\nWordPress 6.0 is planned for official release on May 24th, 2022, three weeks from today.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you RC1 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 RC1 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the release candidate version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, or 4, on a case-insensitive filesystem, please use the following command:wp core update --version=6.0-RC1
Additional information on the full 6.0 release cycle is available here.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nSince Beta 4, various items have been addressed, including (but not limited to):
\n\n\n\nWordPress 6.0 is the second major release for 2022, following 5.9 which became generally available in January. This release includes nearly 1,000 fixes and enhancements spanning most areas of the WordPress platform. Some key highlights within the content creation and site-building feature sets include:
\n\n\n\nAll plugin and theme developers should test their respective extensions against WordPress 6.0 RC1 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24th.
\n\n\n\nReview the WordPress 6.0 Field Guide, for more details on what’s contained in this release.
\n\n\n\nDo you speak a language other than English? Help translate WordPress into more than 100 languages. This release also marks the hard string freeze point of the 6.0 release cycle.
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nRelease candidate
Our journey nearly done
Get ready, WordPress
Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat, and @annezazu.
\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:\"12799\";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:69:\"\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 6.0 Beta 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2022/05/wordpress-6-0-beta-4/\";s: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, 02 May 2022 16:46:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:5:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.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:\"\";}i:3;a:5:{s:4:\"data\";s:11:\"development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:8:\"releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12787\";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:103:\"WordPress 6.0 Beta 4 is now available for testing! You can download and help test Beta 4 in three ways.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5813:\"\nWordPress 6.0 Beta 4 is now available for testing!
\n\n\n\nBeta 4 was not part of the originally published development cycle. It is aimed at providing an opportunity for testing some specific issues that were resolved since Beta 3. WordPress will continue with the regularly scheduled release milestones on May 3rd, 2022, with the RC1 release.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you test Beta 4 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 Beta 4 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: Use WP-CLI to test: wp core update –version=6.0-beta4.
Do not use this option if your filesystem is case-insensitive.
The current target for the final 6.0 release is May 24, 2022, which is in less than a month!
\n\n\n\nAdditional information on the full 6.0 release cycle is available.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nSince Beta 3, various items have been addressed, including (but not limited to):
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nBeta four, surprise!
Iterating all day long
Time to share and test
Thank you to the following contributors for collaborating on this post:
@dansoschin, @annezazu, and @costdev
In the thirtieth episode of the WordPress Briefing, Executive Director Josepha Haden Chomphosy and special guest Channing Ritter give listeners a sneak peek into the WordPress 6.0 release ahead of the Release Candidate 1 (RC1).
\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\n[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. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:40]
\n\n\n\nTomorrow’s a big day. It marks the beginning of what is called the RC period, or release candidate period, for the current major release of the WordPress CMS. If you’re not super familiar with the way release cycles work, this is the point in the process where the code should pretty much be done changing.
\n\n\n\nThat way you can call in your designers, developers, and anyone else who builds things for others using your software. And they can either start testing their products on it, or they can figure out what new things they need to be able to teach their clients, whichever is most relevant to them. That is generally true for WordPress as well, but in true open source fashion, there is a caveat built in that helps us to get in last-minute, vital changes from contributors.
\n\n\n\nWe have a two-person sign-off rule that’s been around for about as long as I can remember, but lets things be added late in the release cycle, as long as there are two sign-offs from qualified contributors. Most of the time, those qualified contributors are lead developers of the project, but not always. We have a good group of people who are around helping us make sure that this is doable and the best thing that we can offer to all of our users.
\n\n\n\n[Josepha Haden Chomphosy 00:01:50]
\n\n\n\nAnd so, yeah, two-person sign-off, that is the little bit of release process trivia that you never knew you needed. And since we’re looking at a release trivia, kind of hidden bits of how software is made, I actually have a guest with me today, Channing Ritter. So Channing is a product and visual designer based in Brooklyn, New York.
\n\n\n\nShe’s a design director at Automattic and has been working on the WordPress project as a full-time sponsored contributor since January, 2021. She is joining us to share some behind the scenes intel on what’s going into the 6.0 release, her role in that process, and then we’ll just kind of see how the conversation goes from there.
\n\n\n\n[Josepha Haden Chomphosy 00:02:40]
\n\n\n\nWell, and with that, I’d like to welcome Channing to the WordPress Briefing. Hi Channing!
\n\n\n\n[Channing Ritter 00:02:45]
\n\n\n\nHey Josepha. Thanks so much for having me.
\n\n\n\n[Josepha Haden Chomphosy 00:02:48]
\n\n\n\nI’m excited to have you here. If I understand, you are working on the design side of things with the release. So why don’t you tell me a little bit about the role you’ve played?
\n\n\n\n[Channing Ritter 00:02:59]
\n\n\n\nI am. I am the design release lead for the 6.0 release. And if I understand correctly, this is a position that has been unfulfilled for the past few release cycles. So I’m kind of the first person to step in over the past few releases. And I think that’s really exciting, especially because design has started to play such a more important role in the WordPress project over the past few years.
\n\n\n\nSo it makes sense that design would have a seat at the table, and I’m really excited to be helping advocate for the design team and learning from other folks on the release squad. Who’ve been doing this for a while.
\n\n\n\n[Josepha Haden Chomphosy 00:03:33]
\n\n\n\nSo. First big question about 6.0, what is the feature that you are most excited about?
\n\n\n\n[Channing Ritter 00:03:39]
\n\n\n\nI’m most excited about the style switcher within the global styles panel. Um, so if folks still don’t know what I’m talking about there, it’s the ability to change between different variations of the theme.json without actually switching the theme.
\n\n\n\nSo this is a way to get a drastically different look and feels across your site with just a single click. And I see it as a really fun place to experiment and kind of get inspired for the different ways your site could appear without ever having to change your theme.
\n\n\n\nAnd in terms of the Twenty Twenty-Two variations, they’re just really gorgeous and all so diverse. Like you have the main default theme that has the deep green and kind of peachy colors and this really elegant type treatment with a really thin Serif typeface. But then the variations are so different from that. And I think my favorite one is the Swiss variation.
\n\n\n\n[Josepha Haden Chomphosy 00:04:36]
\n\n\n\nThe Swiss variation?
\n\n\n\n[Channing Ritter 00:04:38]
\n\n\n\nYeah, every graphic design nerd loves Swiss design.
\n\n\n\n[Josepha Haden Chomphosy 00:04:42]
\n\n\n\nOh, ok! Now I know!
\n\n\n\n[Channing Ritter 00:04:38]
\n\n\n\nReally awesome things found in there. It’s a really high contrast, bold variation. It’s kind of black and white with red accents. I just love how different it is from the default style and how easy it is to change up your site and just get a whole drastically different look and feel.
\n\n\n\n[Josepha Haden Chomphosy 00:05:00]
\n\n\n\nThat’s excellent. So for folks who do not know what we’re referring to, when we talk about the Twenty Twenty-Two variation, that is the default theme, Twenty Twenty-Two. I’ll put a link to both the classic and block-based versions in our show notes, but you’ll want to use the block-based version to look at these style variations that Channing has mentioned here.
\n\n\n\n[Channing Ritter 00:05:24]
\n\n\n\nYou know, we’re really excited that the first-ever default block theme was released with 5.9, which is when Twenty Twenty-Two first went out and was bundled with 5.9.
\n\n\n\nBut now, with 6.0, I think even more so it’s starting to showcase the real power of block themes and what can actually be done there. And style variations is a huge kind of first step into this new world of block themes and starting to really open up the possibilities and all the flexibility that you have there.
\n\n\n\n[Josepha Haden Chomphosy 00:05:55]
\n\n\n\nYeah, absolutely. So when we’re talking about the Twenty Twenty-Two default theme, when we’re talking about switching these variations inside the theme itself, that seems to me to be a very user-focused kind of feature. And when we talk about users in WordPress, there’s a lot of room for interpretation. Like if we look at it kind of in a framework of three types of users of WordPress, you have, like end-users. So people who are site owners using it as a site to, like, enable their business.
\n\n\n\nBut you also have mid-end users—people who use it to build sites for others. And what I like to call back-end users, people who are using WordPress as a framework. And of course at the start of the Gutenberg project, way back in forever, a million years ago, one of the big calls to action that we had around even, like, trying to do this, was that we wanted to make WordPress easier for users. Just plain users.
\n\n\n\nAnd, and to me, that means making WordPress easier for those mid-end users, people who are creating WordPress sites for other people. But also should give some power and autonomy back to those end-users, the people who are using sites to enable their business or are site owners.
\n\n\n\n[Josepha Haden Chomphosy 00:07:14]
\n\n\n\nAnd so in that context, between 5.9 and 6.0, do you feel like we have features that are really giving that kind of power and agency back to our end-users? Do you feel like we have some features that are really focused on those mid-end users, as opposed to our backend users? For a long time, we focused heavily on enabling our backend users, and now Gutenberg kind of moves us into those other two areas.
\n\n\n\nAnd so do you think that things like being able to switch between your style of variations, other things like that are moving us closer to that particular goal of Gutenberg?
\n\n\n\n[Channing Ritter 00:07:51]
\n\n\n\nThat’s a great question. I think it’s both. I think some of the features being released in 6.0 are absolutely going to empower that end-user.
\n\n\n\nParticularly in terms of improvements around design tools and some of the quality of life improvements. For example, partially selecting across multiple blocks and being able to partially select texts there. That’s the type of thing that really brings the writing experience in the editor to be on par with how you would expect a text editing experience to work.
\n\n\n\nAnd there are tons of small quality of life improvements in this release that I think are really gonna help those end-users. But there are also improvements around what we might call the maintainers who are building sites for others. I think block locking in particular is something that is really going to start filling a gap between people who build the sites and then people who do the day-to-day maintenance within a site.
\n\n\n\nFor example, in 6.0, we’re introducing some interface UI around block locking, but also there’ll be control around the ability to lock user roles.
\n\n\n\n[Josepha Haden Chomphosy 00:09:03]
\n\n\n\nWhich I think makes a lot of sense. I mean, we have all of these user roles in the CMS itself, and for a long time, we’ve just been like free for all on blocks, which was great and is great and should be available to people.
\n\n\n\nBut also if we are saying, like, it makes sense to have this gradient of users and their abilities for the CMS itself, and we are saying that we want to move control of the website and the content to be at the base layer in these blocks, then it also makes sense that we should be able to provide that same sort of granular level of access in the blocks.
\n\n\n\nSo I think that’s a great thing. If you all, if dear listeners, you do not know what we mean by “block locking,” I’m sure that I can find a link for us in our show notes below as well. If for anyone who’s been talking through Gutenberg things with me for a while, you know that this is one of the primary use cases that I think has been a long time coming.
\n\n\n\n[Josepha Haden Chomphosy 00:10:05]
\n\n\n\nIt was one of the first examples that I offered to folks when we had that question of like, who is this being built for? In what way is this beneficial to that mid-end user, as opposed to just giving all of the power and autonomy to users in a way that maybe is not the best for their visitors?
\n\n\n\nThis is one of those use cases that made the most sense to me being able to say, okay, well, the opportunity to, as somebody who runs an agency and is building websites for people to be able to say, yeah, ‘You can do anything that is possible in this instance of WordPress and all the things that you are allowed to do will not break your instance. It won’t break your website’.
\n\n\n\nAnd so it gives a lot of time back to agencies to focus on their client’s most important problems, as opposed to not knowing how to update the hours in their footer or something like that. And so I’m very excited about that particular feature.
\n\n\n\n[Channing Ritter 00:11:01]
\n\n\n\nIt’s such a long-requested feature. I mean, we’ve been hearing requests around this particular feature for years and, you know, often when something gets requested over a span of years like that, it’s because there are some complexities to figure out how it works.
\n\n\n\nAnd that’s definitely been the case with moving forward with block locking. And there are a lot of nuances there. But I think what you were saying, I totally agree with. There’s always a push and pull. And as we enable more and more flexibility for end-users, there needs to be a little bit of push from the other side to kind of give more granular controls, more locking options, and make sure that everything can still be easily maintained.
\n\n\n\n[Josepha Haden Chomphosy 00:11:43]
\n\n\n\nYeah, we mentioned in that answer the concept of maintainers. If you are a contributor, it’s not that kind of ‘maintainer.’ So if you’re a WordPress contributor and we said maintainers there, um, just know that that’s not what we’re referring to. If you don’t know what I’m talking about when I say ‘contributor,’ there is a whole community of open source people and maintainers are people who specifically take care of a particular part of the WordPress software or the WordPress project, um, that makes all this possible.
\n\n\n\nSo there’s, ya know….
\n\n\n\n[Channing Ritter 00:12:19]
\n\n\n\nSo true! The maintainer has another meaning in this context.
\n\n\n\n[Josepha Haden Chomphosy 00:12:20]
\n\n\n\nYeah, we have a mix in our audience and I love it, but it also makes me frequently spend like 10% of my podcast being like, by the way, when I said this, I didn’t mean you, but I did mean you, which makes it harder. I know.
\n\n\n\nSo. You’ve been with the project for a little bit, but if I recall correctly, this is the first time that you were, like, leading part of a release.
\n\n\n\nSo what would you say was the most challenging part of that?
\n\n\n\n[Channing Ritter 00:12:52]
\n\n\n\nAnother great question. This is my first time being this closely involved with the release. Although I was involved with the 5.9 release, but mostly in a release assets capacity. So I helped with the About Page and the welcome banner that goes on the dashboard.
\n\n\n\nSo I did get some insight in the last release cycle. Which was great preparation for being more involved as a release lead on this cycle. From the design perspective, one of the hardest things is always going to be figuring out what exactly goes into the release and what needs more time. In the sense, you know, that there might be some features that need to stay in the Gutenberg plugin for a while and get more testing before they get released to a much wider audience in a major WordPress release.
\n\n\n\nSo I think on the design side, we definitely have some goals that are big, long-term projects that are likely going to span across, you know, many releases, maybe even over many years. And I think the full site editor is a great example of that in a sense that it’s not something that you just were gone in one release and then it all gets released and then it’s all good to go.
\n\n\n\n[Channing Ritter 00:14:06]
\n\n\n\nIt’s something that has to be staggered across many releases, and there’s a lot of thought that goes into it; does this make sense in this more limited capacity, and what else needs to go in in order for this feature to go in? And the most complex things about the WordPress project is how interconnected things are.
\n\n\n\nSo when you start making those decisions about what should go in, what should get pulled out, often there’s sort of a domino effect of like, well, that would affect this feature and then, well, maybe they shouldn’t go in, or maybe this does need to go in. And that is really one of the most challenging, but also one of the most fascinating aspects of the release process.
\n\n\n\n[Josepha Haden Chomphosy 00:14:46]
\n\n\n\nYes. It is very, very true that there are kind of no small problems left in WordPress. *laughs* Yeah, when we, when we first started with this like bigger release squad, cause that has not been routine for the history of the project. When we first started with that, I know that expanding out the exposure to like how much one change affects 25 different things was really, it was really good for all of us to be reminded.
\n\n\n\nAnd as I mentioned at the top of our episode today, tomorrow begins the RC period. It begins the release candidate period, which is when it’s supposed to be, as locked down as possible. But if you all have been following along with our release process in general, which if you’re listening to this, you probably have, you know that last week or a couple of weeks ago, we had this whole question about the Webfonts API, and we had that conversation in a public space as best we could,
\n\n\n\nLike, there are always things that you can’t, like, fully disclose in public spaces, but we had a very open and transparent conversation about, like, who is most affected by putting it in, in the state that the API was in. And, who’s most affected if we take it out. And where can we make compromises on either side so that both sides are a little happy and a little unhappy?
\n\n\n\n[Josepha Haden Chomphosy 00:16:09]
\n\n\n\nAnd, like, that is all so hard to do. Not only in general. We have a 20-year-old code base and a five-year-old code base. And it’s all a big, big undertaking to understand what is happening and where it happens. And so there’s this moment always when we are trying to decide, like, is this baked enough? Did we put it in too early? Should we pull it out? How, if we pull it out, did we ask people to do too much work before we decided to pull it out anyway?
\n\n\n\nLike, you always have those kinds of questions about it. And honestly, I think that most of us weren’t around the last time, that WordPress was, was this experimental in public, like it’s always been open source. It’s always been experimental and iterating publicly, which is just the hardest way to work on anything. We like, we shipped our best guesses. Don’t be mad. It’ll be… we’re coming for it. We’re going to fix it. Like, that’s always hard, but the last time around, when it was this substantial a change was, like, 2008 or something, like, it was ages and ages ago.
\n\n\n\n[Josepha Haden Chomphosy 00:17:14]
\n\n\n\nAnd we were smaller than, we had a smaller number of contributors. We had a smaller group of people actually using the CMS. And so over time it has gotten more and more complicated. And, and I don’t think that we can ever understate the complexities of that. And so for you, you had a little bit of exposure to it in 5.9 and then showed up for like really doing it in 6.0.
\n\n\n\nHas it been a surprising change? Like, were you surprised much more by how complicated it was when you were closer to it?
\n\n\n\n[Channing Ritter 00:17:47]
\n\n\n\nYeah, definitely. It’s been a real learning process, especially coming to understand how much there really are no easy answers. I think a lot of us are in the release squad are real problem solver types of people and, and want it to, you know, be a really neat, tidy answer.
\n\n\n\nAnd it’s not always the case. You know, sometimes parts of the feature might go in, or some contingency plan might get put into place and things didn’t go exactly as planned. But what you said of being an experiment and being on kind of the cutting edge of trying out new things, I think there is a lot of passion around that in the WordPress project.
\n\n\n\nRight now, we’re in such a transitional period for the project, you know, moving from classic themes to block themes and really changing the ideas of how we approach designing sites. And because of that, I think there is a lot of momentum and energy around getting new features, as many new features as possible into each release. But there’s also, you know, a lot of testing and stuff that needs to happen.
\n\n\n\nAnd to make sure that, like you said, these things aren’t going out too early.
\n\n\n\n[Josepha Haden Chomphosy 00:19:01]
\n\n\n\nWell, and there’s always that difficulty, we’re going to just leap right into open source areas now. There’s always that difficulty around, like, there’s this concept that when, like, we always want to ship something that doesn’t break backward compatibility when possible, we don’t want to ship vulnerabilities. Like, that’s always true, but we are in an open source project, and open source projects are necessarily kind of tolerant of like, that’s not our best, but like it skates, right?
\n\n\n\nThis was, we aimed for Ferrari and got a skateboard because sometimes you got to start with a skateboard, right? *laughter* Like if it gets you from one place to another, that’s kind of where we’ve got to aim some days.
\n\n\n\n[Channing Ritter 00:19:45]
\n\n\n\nTotally.
\n\n\n\n[Josepha Haden Chomphosy 00:19:46]
\n\n\n\nAnd that’s always so, so difficult, especially cause, like, for the big change that 5.0 represented, and that 5.9 represented– 6.0 is not as big a shock as 5.9 was. But, like, as big a change as those represented, it still skates. And that’s, I think what makes the work especially hard, especially nuanced. And like, we haven’t gotten together as human beings in two years. And so sometimes people just kind of forget there’s a human being back there.
\n\n\n\nWe’re humans. Everyone be nice. Yeah. I don’t know that part of running a release definitely was surprising to me. My first release that I ran was 5.0 and…
\n\n\n\n[Channing Ritter 00:20:31]
\n\n\n\nOh, wow!
\n\n\n\n[Josepha Haden Chomphosy 00:20:32]
\n\n\n\nYeah, it was, like, that was 2018. And then I became the executive director at the top of 2019. And I distinctly remember one core chat where I showed up and just was like the most transparent, vulnerable person we’ve ever experienced in life.
\n\n\n\nThat’s not true. We have very vulnerable people in the project and very transparent people, but I told everyone like, there are a million of you and one of me, and it’s kind of terrifying that you’re leaping on me in this—like you’re scaring me a lot right now. And that was quite a thing to say to like, all these… it’s terrifying! Right?
\n\n\n\n[Channing Ritter 00:21:12]
\n\n\n\nI love when you see that type of vulnerability in the project. I think it takes… it takes a degree of comfort and familiarity with the project to even be able to admit to that. And to me, that’s a real sign of growth in the project. Like when I first started contributing, I don’t think I ever would have just said, like, ‘How is the feature supposed to work? I have no idea.’ That’s something that I say all the time now.
\n\n\n\n*Laughter*
\n\n\n\nAnd you know, that is completely fine and more than okay. It’s a massive project. There are folks who have done deep thinking about a feature over the course of years. You know, and there are experts who can help shed light on various problems that maybe you just haven’t had a chance to dive into yet and really understand the nuances of yet.
\n\n\n\nSo that’s the amazing thing about open source is that you can lean on folks who do have expertise in that particular area. You’re not expected to be an expert-expert in every single domain. It’s okay to say, I don’t really have a good idea or a good concept of this feature. I don’t have a good feeling for it. What do other folks think?
\n\n\n\n[Channing Ritter 00:22:24]
\n\n\n\nAnd even people who have been in the project for a long time, decade plus, still say that all the time. You know, or you might just say, like, I have a really rough idea of how this works, are other people seeing this the same way? Or did other people have a different, you know, mental picture of how this might work?
\n\n\n\nEven if, sometimes it feels like you’re over-communicating, it’s really helpful because often people do have really dramatically different ideas about how a feature might take shape.
\n\n\n\n[Josepha Haden Chomphosy 00:22:49]
\n\n\n\nAnd I hope that’s one of the things that we never lose in the project. Like we are an old, old project now and we support a bunch of the web with a tiny, tiny group of people compared to the amount of the web that we support.
\n\n\n\nAnd I hope that we always have that opportunity as senior leaders, which I am, and all of our upcoming leaders to all of us, just at some point, be like, can we stop the train? I don’t understand. I don’t understand that. Um, and not necessarily feel that that has made us a worse contributor. Cause I think that it’s when we are transparent about our lack of understanding.
\n\n\n\nThat’s when we have the opportunity to make what we’re offering to the world more solid and always better.
\n\n\n\n[Channing Ritter 00:23:35]
\n\n\n\nI love it. I think it’s the, one of the most lovely things about the WordPress community. There’s really low judgment around those types of questions and people are really inclusive and more than happy to take a moment to explain something to you or shed some light on an issue you might not have thought that much about.
\n\n\n\nI think that’s one of the best things you can always reach out for help. And folks are always willing to provide guidance or context or even historical information about, you know, whether it’s been tried in the past or previous explorations and that sort of thing.
\n\n\n\n[Josepha Haden Chomphosy 00:24:10]
\n\n\n\nAll right. Well, that covers all of my questions for you. Do you have a final thought about the release that you would like to share with everyone you don’t have to, if you don’t want to, not everyone has like a final sign off.
\n\n\n\n[Channing Ritter 00:24:25]
\n\n\n\nYeah. One of the things I’m most excited about for this 6.0 release is all of the improvements around design tools.
\n\n\n\nAnd these are just small improvements around a ton of different things, like the color panel, border controls, gap support, typography options, flexible container blocks, etc. These are the types of tools that are a designer’s dream. You know, they really make the difference between being able to make a really crisp, finished looking final product and having something that’s a little rough around the edges.
\n\n\n\nAnd as a designer, like those are the things that your eye goes straight towards. And all of these nuanced new tools, they really allow designers to have that fine detailed control to create really pixel perfect sites. And I think that’s something that, you know, myself and a lot of others on the design team are just so beyond excited about.
\n\n\n\n[Josepha Haden Chomphosy 00:25:25]
\n\n\n\nExcellent. Well, Channing, thank you so much for joining us today on the WordPress Briefing; it has been an absolute delight.
\n\n\n\n[Channing Ritter 00:25:32]
\n\n\n\nThank you for having me.
\n\n\n\n[Josepha Haden Chomphosy 00:25:41]
\n\n\n\nAnd now it is time, woohoo, for the small list of big things. My favorite part of this podcast, that’s not true. I have a lot of things that I love about this podcast. I just, in particular love being able to share like three things that are coming up in the next couple of weeks that everybody should be aware of. And I really particularly like the list I have this week.
\n\n\n\nFirst as of today, we are two weeks away from WordSesh. If you’re looking forward to your first in-person WordPress event, but feel like you could use a little foundation information, a little bit of a WordPress primer, then this event has a lot of excellent thought leaders in the project that you can learn from.
\n\n\n\nIf you’re looking for more practical or hands-on opportunities, uh, you can also check out social learning spaces. All of those are free for anyone. So I will include links to both of them in the show notes.
\n\n\n\n[Josepha Haden Chomphosy 00:26:30]
\n\n\n\nSecond, as of today, we are four weeks away from WordCamp Europe. This is one of our flagship events. So it also includes a contributor day, which I encourage you to look into. If you have never heard of one before. I will be there to meet some of the contributors that have joined the project since the end of 2019. And hopefully, I will see you there as well. If you’ve never heard of a contributor day, then I’ll include a link to the beginner’s guide to contributions, a little talk that I gave in 2017 in the show notes that should help you get your bearings or at the very least know what questions to ask yourself to figure out if a contributor day is right for you.
\n\n\n\nAnd then the third thing as of today, it has been one week since Ian Dunn and the Meta developers… Um, that sounds like a band… Ian Dunn and the Meta developers connected the props channel in the community Slack to WordPress.org profile activity. I’m really excited about this. It’s the first in a long list of changes that are part of a larger project to credit more non-code contributions, more contributions that are not specific to a major release or event.
\n\n\n\nAnd also to set us up to be able to provide more quality checks and balances for our growing Five for the Future program. If you’ve not been over there lately, if you’re not super sure what I’m talking about, there’s a link to the discussion post that we had about it, but also you can wander right over into the Making WordPress Slack and check out the props channel to just kind of see a running list of contributors that people are really grateful for. Which, frankly, if you ever are having a bad day, that is a wonderful place to just kind of wander in and see all of the positive vibes that people are sending around to each other.
\n\n\n\nUh, yeah, so the props channel, is always good. Uh, and that my friends is your small list of big things. Thank you for tuning in today for the WordPress Briefing.
\n\n\n\nI’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:\"12742\";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:75:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"People of WordPress: 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://wordpress.org/news/2022/04/people-of-wordpress-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 30 Apr 2022 09:20:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:7:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:9:\"HeroPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:15:\"WordCamp Mumbai\";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:5:{s:4:\"data\";s:16:\"wptranslationday\";s: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=12706\";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:106:\"This month\'s People of WordPress feature shares the story of developer and e-commerce builder 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"webcommsat AbhaNonStopNewsUK\";s: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:16742:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a Indian-based WordPress developer and long term contributor on how it helped her find a career and a local and global community to belong to.
\n\n\n\nWordPress is an inspiration to Meher Bala, a frontend web developer and community builder from India. From using the software as a basic website tool to helping entrepreneurs and good causes around the world fulfill their aspirations, she has overcome personal barriers and now aims to inspire others.
\n\n\n\nMeher found her vocation and learned new skills through WordPress. She also discovered a way to encourage other women to consider careers in IT.
\n\n\n\nAs a child, Meher was diagnosed with dyslexia (difficulty in reading the written word) and dyscalculia (difficulty in comprehending numbers and mathematical functions). With the support of her parents and a tutor, she was able to overcome this learning obstacle. She developed coping techniques and a determination to work to overcome challenges as they appeared later in life.
\n\n\n\nIn school, she got an opportunity to replace one subject with computer studies as an alternative. This proved to be an eye-opener to future career possibilities.
\n\n\n\nShe began to research not only what the internet had to offer but also how it worked, including the new and fascinating concepts of email and websites. Her father bought the family’s first desktop computer so she could do her research at home.
\n\n\n\nMeher’s father wanted to turn her love for computers into something that would serve her well in the future. In 2005, he enrolled her in a short computer course from a global IT training provider. The course tutor was so impressed with her performance, she was advised to enroll in a four year software development course.
\n\n\n\nThat meant she had studied the software development course alongside her higher education college course. Looking back, she enjoyed the dual challenge of the degree course in commerce, and the experience prepared her well to keep learning software while working as a developer. Within three years, she had learned C#, C, C++, HTML, Java, and .NET.
\n\n\n\nAfter graduation, she was in a dilemma to choose between commerce and IT. What to choose? She had a compulsory one-year technology internship to complete, and her choice of focus for that year would prove to be a defining moment.
\n\n\n\nIn 2009, on her birthday, Meher was offered an internship. On the first day of the internship, she was introduced to WordPress. Her initial assignment was to change the look and feel of the WordPress dashboard — in just six hours. But there was a problem – she had never worked with WordPress before!
\n\n\n\n\n\n\n\n“I stared at the whiteboard and thought that task given was impossible and difficult to meet the deadline. I wondered if my boss was joking and did not know then what you could do with WordPress as a developer and how it could slot into your toolbox. It opened my eyes.”
Meher Bala
Meher used her research skills to know more about using WordPress. She found a plugin that would help her achieve her task. She met the deadline and it ingrained an interest that she would never lose.
\n\n\n\nFive years after her initial WordPress experience, Meher was assigned to lead an international project in WordPress. She was hesitant — she had lost touch with the CMS during that five years, but the project was a great opportunity to become a team leader and lead from the front.
\n\n\n\nShe decided to update her WordPress skills, relying again on the strength of her research skills and determination. In the process, she also taught her team all about WordPress, inspiring many of those members to continue to develop their WordPress skill set.
\n\n\n\nThe success of that project was a pivotal moment for Meher and a new dawn as a developer specializing in WordPress.
\n\n\n\nAs a team lead, Meher soon found it was not possible to always have all the answers straight away. She found internet searches gave practical solutions—but rarely explained the theory behind it.
\n\n\n\nSo she went looking for a WordPress group to help her expand the scope and depth of her knowledge.
\n\n\n\nIn 2015, while browsing Facebook, Meher came across an advertisement for something called WordCamp Mumbai, an event that had taken two days before. She did a little digging to learn what a WordCamp was, and about the people behind it. She took the plunge and joined the WordPress Mumbai Meetup group.
\n\n\n\nHer first Meetup experience was not love at first sight. She felt the topics were for advanced users, and the timing late in the evening made it difficult to attend.
\n\n\n\nBut a few months later, the Meetup addressed a topic that could help her resolve an issue in one of her current projects. She made the effort to show up and came away with a number of important tips. The speaker had taken the time to speak to individual attendees. When he came to Meher, she took the opportunity to ask a couple of questions about her project issues.
\n\n\n\nThereafter she went to more Meetups and got to know the people behind this group, just as they started talking about WordCamp Mumbai 2016.
\n\n\n\nMeher expressed interest in being a part of the coming WordCamp Mumbai and started in an entry-level role with basic responsibilities.
\n\n\n\nAt first, she thought WordCamp was a formal conference with about 100 people. So on the first day of WordCamp Mumbai 2016, she was surprised to see so many WordCamp enthusiasts attending and enjoying such a relaxed and friendly conference.
\n\n\n\nAfter that great experience, Meher went to many more meetups and did more volunteering. She started taking on responsibilities in the coming WordCamps and getting to know the different aspects of the camp.
\n\n\n\nIn the following years, at each WordPress, she took up a new role like speaker vetting, sponsors, and volunteer coordination. This allowed her to know more about what an organizer needs to do, from planning to execution, to make WordCamp a successful event.
\n\n\n\nMeher is grateful for her WordPress journey which was fostered in the Mumbai community. It has been filled with beautiful surprises.
\n\n\n\nWhen people ask why she’s chosen to specialize professionally in WordPress, Meher says WordPress is easy to teach a non-technical person, yet it is still highly customizable. Being a WordPress developer has given her the opportunity to work remotely for global web development companies that let her think out of the box. And she learns new skills with every release.
\n\n\n\nMeher says that some of her most memorable WordPress moments have revolved around special friendships, trying new things, and participating in community building.
\n\n\n\nWordPress has let her explore different parts of India, make new friends locally and internationally, and encourage women to be a part of meetup groups and events across India.
\n\n\n\nOne of Meher’s biggest dreams was to lead WordCamp Mumbai as a lead organizer and show others what could be achieved by working together in open source. In 2019, she did just that and has volunteered at international WordCamps and meetups since.
\n\n\n\nAs part of her enthusiasm for sharing the opportunities WordPress can give people, especially women, she has given time to co-organize two global WordPress Translation month long events and contributor events in India.
\n\n\n\nMeher said: “I was first introduced to translation at one of the meetups which was organised to support the WordPress Translation Day. I realized this was another way to support my local communities and bring the power of WordPress to them by contributing in Gujarati and Hindi. I did not imagine I would a few years later be a global organizer for the event itself!”
\n\n\n\nWith her commitment to ongoing learning as a developer and to model what she believes about the value and community growth opportunities of open source, Meher has given time and energy to the Marketing Team, where she has been a Team Rep, to the Training Team, and to the Core Team contributing to multiple releases.
\n\n\n\n\n\n\n\nAt the start of my software developer journey, I always thought the C++ and Java were the only skills you required to excel in your career. From the time I started exploring WordPress in depth, I realized the potential and the power of WordPress in web development.
Meher Bala
Being a part of the WordPress community, Meher learned that there is so much more than just building blogs on WordPress. She started exploring different features of WordPress, created her first theme, and eventually specialized as a frontend specialist.
\n\n\n\nMeher now works as a consultant and front end developer with an international agency specializing in WordPress. Asked what she thought was the best thing about being a WordPress developer, Meher replied: “Through WordPress, I have an opportunity to build unique out of the box websites and work remotely for global web development companies that encourages you to think out of the box. There is always opportunity to continuously advance my coding skills and learn new techniques with every release.”
\n\n\n\nShe believes that there is no limit to where using the software can take you and what you can combine it with to find solutions to projects big and small.
\n\n\n\nIf you earn a living from WordPress, her advice is from the heart: try to give back to the WordPress community.
\n\n\n\n“I am sure you will learn or teach something new and definitely make friends across the world. There is no shame in making mistakes, as you can learn from them and develop your skills further. You can also help others as they build their skills.”
\n\n\n\nMeher added: “Don’t let the things you find difficult get in the way of your success.”
\n\n\n\n\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Abha Thakor (@webcommsat), Larissa Murillo (@lmurillom), Mary Baum (@marybaum), Chloé Bringmann (@cbringmann), and Meg Phillips (@megphillips91) for interviews, writing and image work on this story. Thank you to Meher Bala (@meher) for sharing her experiences and to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support of the series.
\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
\nWordPress 6.0 Beta 3 is now available for testing!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, or test this version of WordPress production or mission-critical websites. Instead, it is recommended that you test Beta 3 on a test server and site.
\n\n\n\nYou can test WordPress 6.0 Beta 3 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: Use WP-CLI to test: wp core update --version=6.0-beta3
.
Do not use this option if your filesystem is case-insensitive.
The current target for the final 6.0 release is May 24, 2022, which is in less than a month!
\n\n\n\nAdditional information on the full 6.0 release cycle is available here.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nSince Beta 2, various items have been addressed, including (but not limited to):
\n\n\n\nwp_enqueue_block_style()
to wp-includes/script-loader.php
, for better consistency #55182, #55148A prior announcement for WordPress 6.0 Beta 1 included a reference to “Webfonts API: Manage local fonts with PHP or theme.json”, as a feature that would be included in the release. WordPress 6.0 Beta 3 will allow theme authors to use webfonts in theme.json, with a public API for plugins to register and enqueue webfonts available in a future version for WordPress. Beta 3 will also include three new style variations to the Twenty Twenty-Two default theme.
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nThank you to the following contributors for collaborating on this post: @dansoschin @webcommsat, @audrasjb
\n\n\n\nAnd now another WordPress haiku:
\n\n\n\nRelease day is near
6.0 abounds with joy
New features soon here
WordPress 6.0 Beta 2 is now available for testing!
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you test Beta 2 on a test server and site.
\n\n\n\nYou can test the WordPress 6.0 Beta 2 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: Use WP-CLI to test: wp core update --version=6.0-beta2
Do not use this option if your filesystem is case-insensitive.
The current target for the final release is May 24, 2022, which is about five weeks away.
\n\n\n\nAdditional information on the full 6.0 release cycle is available.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.
\n\n\n\nAs a reminder, contributors have fixed 209 tickets in WordPress 6.0, including 110 new features and enhancements. Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. Here are a few of the changes you will find in Beta 2 specifically:
\n\n\n\nLast week’s announcement for WordPress 6.0 Beta 1 includes a reference to “Webfonts API: Manage local fonts with PHP or theme.json,” as a feature that would be included in the release. This specific functionality was not included in Beta 2 but may be available at RC.
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nThank you to the following contributors for collaborating on this post: @dansoschin, @annezazu, @costdev, @priethor
\n\n\n\nWe code fervently
\n\n\n\nA breathless pause for the test
\n\n\n\nKey tapping resumes
\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:\"12666\";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: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:53:\"WP Briefing: Episode 29: How to Make a WordPress 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wordpress.org/news/2022/04/episode-29-how-to-make-a-wordpress-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:\"Mon, 18 Apr 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=12658\";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:150:\"Join our host Josepha Haden Chomphosy as she takes us back to WordPress basics. Learn everything you need to know about how to make a WordPress 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:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/04/WP-Briefing-029.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:16764:\"\nIn the twenty-ninth episode of the WordPress Briefing, Executive Director Josepha Haden Chomphosy reminds us of our WordPress roots — blogging — and discusses the basics of starting your first blog on WordPress.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nJosepha 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. I’m your host, Josepha Haden Chomphosy.
\n\n\n\nHere we go.
\n\n\n\nJosepha Haden Chomphosy [00:00:39]
\n\n\n\nAll right. So you’ve been listening to this podcast for a while. You may be one of these contributors I keep mentioning; you may be an agency owner or freelancer. Maybe you’ve wondered how to make a WordPress blog for your big idea. Or, maybe you’re one of the many people who use WordPress for their project or business. Before WordPress was known as a content management system, as a way to get sites online fast, it was a blogging tool.
\n\n\n\nWe have long since outgrown that, but even 19 years into our journey, blogging is still a key part of what WordPress enables you to do. That’s because even after those 19 years, the mission of WordPress is still the same. And that is to democratize publishing, to help people have a place online where they can tell their stories or share their projects or set up their businesses.
\n\n\n\nIf you’ve ever tried to set up a blog, you know that there isn’t a lot of information about what to know before you get going at all. So I’m going to talk about that a little bit today. And just by the way, if you heard the word blog right now and thought, oh, Josepha, how old fashioned? I think it’s important to remember that there’s a business advantage to having well-written, relevant content on your website.
\n\n\n\nJosepha Haden Chomphosy [00:01:59]
\n\n\n\nAnd if you’re not blogging for business, because not all of us are, then the benefits are a little different but still important to my mind. Things like the cathartic benefits of journaling, a chance to build community, and the general importance of preserving wisdom for the ages. Anyway, back to the topic at hand. Before we can get to any of the fancy things that WordPress can do nowadays, it’s important to know a few things as you get ready to set up your first ever website.
\n\n\n\nSo let’s dive in. Here is how you need to get yourself started. First, have an idea and a plan. So have an idea for what you’re doing, the concept of your content, who you want to reach, and some concept of a domain name. I would encourage you to not necessarily get your heart set on a domain name at first. Cause, like, if you want the domain name, wordpress.org, like we own that, you can have that! But if you know that you want a domain like WordPressbloggingforthefuture.com, like that one might be more available. And if you know the kind of words you want in your domain, you can be a bit flexible about what is there.
\n\n\n\nJosepha Haden Chomphosy [00:03:09]
\n\n\n\nThe second thing that you need to do is that if you are just getting started, ask yourself the question, what sort of host do I want? We kind of mentioned all along the WordPress process that, like, you need a good host, but it’s not always clear where that decision has to happen. It happens right here at the start, before you even know what WordPress is most of the time.
\n\n\n\nSo, the earliest question that you have to answer for yourself is what sort of host do I want? Where do I want my site to live? So ask yourself how much you want to get into the maintenance and configuration of your website and the hardware that it lives on versus creating content or keeping your shop up to date.
\n\n\n\nThere’s this whole spectrum of hosting options, and they range from full service where they will keep your WordPress software up to date, provide daily backups, and have customer support if something goes really wrong. So it ranges all the way from full service like that all the way down to essentially zero services, just kind of hands-off.
\n\n\n\nJosepha Haden Chomphosy [00:04:11]
\n\n\n\nThey give you a space to keep your WordPress software, to keep your WordPress site. But they leave everything else up to you. They leave the backups up to you. They leave updating up to you, things like. So that’s the first thing you have to ask yourself. And the first question you have to be able to answer. Most of the time, you will want to start with one of the full-service options. That way, you know that your software is set up correctly and safely from the start. And as you learn more about the software and what you want and what you need, and you have the ability to learn in the time that you have, the more that you can add on either service with the existing hosts that you chose or moving to a different host; however that works out for you.
\n\n\n\nSo if that one sounds like the right option, then you choose a host, go to their site, and actually most of them will have a way to walk you through how to set up a WordPress site inside their system. Most of the time, it’s just one click and then they ask you some questions to get some configurations right.
\n\n\n\nJosepha Haden Chomphosy [00:05:10]
\n\n\n\nThe other option that on the like zero, zero service side, that’s not quite fair, but you know, the other side of that spectrum that probably will be appealing to you if you are already familiar with code or already know how to manage a server or, or you know how to work in this thing called c-panel, et cetera.
\n\n\n\nSo if you already have a lot of information on how all of that works, you can, if you want to, head over to wordpress.org/download, and you can download a zip file of the WordPress software and set that up in your own environment.
\n\n\n\nOkay, quick check here. If this all sounds roughly doable to you, or at least it feels like we’re in the right starting point, but you find yourself thinking, gosh, I just wish she would slow down a little.
\n\n\n\nI’ve got you covered. In the show notes, you’ll find a link to one of the Learn WP courses for getting started with WordPress. There’s a section on choosing a host as well as various other early steps of this process. So if you felt like I blazed through all of that, which honestly I kind of did, you can work through those lessons in that course, at your own pace, and it’s, and it’s really a very good guide.
\n\n\n\nJosepha Haden Chomphosy [00:06:24]
\n\n\n\nAll right. Let’s pretend we did all of that. Now you’ve got yourself a website. The thing that you will want to do next, or rather the first thing that you’ll notice once you get your site up and running, is that there’s this ‘Hello World’ post– there’s a post that already exists in there. The Hello World post is a placeholder for the common features of a blog post.
\n\n\n\nThere, you can find your featured image, your title, your content, and even some fake comments. You can either edit this post so that you can see how your writing will look from the start, and you can kind of compare like, okay, the Hello World part over here on this page, exists in this field over here on this page. So you can kind of see where everything works, how it all looks together. Or, if you’re more familiar with WordPress or CMS in general, you can simply remove that and start fresh.
\n\n\n\nJosepha Haden Chomphosy [00:07:17]
\n\n\n\nSo we’ve got now a website, we know, kind of, how to look at our posts and create posts, where comments are, where they can kind of be moderated and stuff. And so, the most fun task for everyone is choosing a theme. But if it’s not a fun task, if it doesn’t sound like a fun task to you, I can help you kind of do some, choose your own adventure guiding questions here.
\n\n\n\nFirstly, you can ask yourself how you want the site to look. Do you want it to mostly be a lot of photos or entirely words, mostly animations? You can head to the theme directory and search for a theme with most of the features that you want. There’s like a filtering system where you can put in, like, you want three columns so that you can have three columns of text if you want it to look kind of like an old school newspaper kind of layout and things like.
\n\n\n\nJosepha Haden Chomphosy [00:08:12]
\n\n\n\nThere’s also a way to look for themes inside your instance, your WordPress site, but like, if you haven’t set that up yet, but you do still want to see kind of what your theme options are, you can go to wordpress.org/themes and and take a look at what’s out there. Just as a quick side note, if you get to that theme directory, if you get to wordpress.org/themes, and it feels overwhelming, which I can understand, I recommend starting with a theme that is designed for blogging specifically so that you can see how things look right away.
\n\n\n\nAnd there’s actually a theme that does come with every WordPress site. So if you’re not ready, you can skip this thing entirely and just work with the theme that’s already there. Every word, press instance ships with a theme and it is fully functional when you, when you get your site up and running. So you don’t need to choose a theme right now if you don’t feel ready.
\n\n\n\nAnd then the other very fun thing that people do with their WordPress sites is to add plugins to them. So plugins are these little pieces of software that you add on to the WordPress software that lets it do additional things. It adds additional functionality. The questions that you can ask to kind of guide yourself through what sorts of plugins you might want, what sorts of functionality you might want to add to your site are a little similar to the ones that you want to ask for figuring out which theme.
\n\n\n\nJosepha Haden Chomphosy [00:09:36]
\n\n\n\nSo figure out if there are tasks that you need visitors to do. Do you need them to contact you? Do you want them to watch a video? Should they review and respond to questions?
\n\n\n\nIf you have a concept of the things that you want users to do on your website, then you can head to the plugin directory and search for a plugin with features that you need. Also, there are just endless lists of recommended plugins out there; if that is something that you find valuable as part of your research, those are also easy to find.
\n\n\n\nAnd as a general side note here, there are even more plugins than there are themes. So if you have gotten to this point and feel like you don’t quite know the answers to the questions that I shared, and, and it’s going to be a while until you feel like you can know what those answers are. That’s totally fine.
\n\n\n\nI’ll tell you this. I have never seen a site without a contact form. So feel free to begin your journey there. There are a lot of great plugins for contact forms and it can kind of help you figure out how to work with plugins in that way. So yeah, I made it sound like you can get a WordPress website built in like seven minutes and on the one hand you definitely can.
\n\n\n\nJosepha Haden Chomphosy [00:09:36]
\n\n\n\nAnd on the other hand, it’s still a little bit more complicated. So here I have a final note for everyone. You will hear around the WordPress ecosystem. And obviously, here, are some things that could make you feel a little nervous about doing this for the first time. Things like the five-second installation, which WordPress has been famous for years.
\n\n\n\nBut also about how easy and simple it all is. And as somebody who was once in the position of learning WordPress for the first time, like I first encountered a WordPress site in 2009 and I started learning how to use WordPress in 2010. So I can say with confidence that once you learn it, it’s easy.
\n\n\n\nWe are the easiest of the hard options for CMS. Like content management systems are just complicated, but we are the easiest one out there. And so, as you’re learning, I want to just remind you to celebrate your small wins along the way. If you feel like you’re late to this blogging game, like you should have had a website for years. I mean, sure that could be true. And yes, the best time to plant a tree was 20 years ago. But the second-best time to plant that tree is today.
\n\n\n\nWordPress didn’t start out powering over 40% of the web, and your first site can’t be immediately measured in the millions of readers. So, what will your small beginning lead you to?
\n\n\n\nJosepha Haden Chomphosy [00:12:25]
\n\n\n\nAnd now that brings us to our small list of big things.
\n\n\n\nThe first one, the next release of WordPress, WordPress 6.0, has reached its beta phase. That means the full focus is on finding and fixing the bugs we accidentally created during this development cycle. Beta two comes out tomorrow and you can follow along in the core channel in the Making WordPress Slack.
\n\n\n\nIf you’ve never seen how those releases get packaged, and if you just want to keep an eye on what everybody’s doing so that you can be the first to know, yeah, Making WordPress Slack is the way to go.
\n\n\n\nThe second thing on our small list is that speaking of WordPress 6.0, we had the public walk through a couple of weeks ago, which means that in a few weeks, I’ll do a WordPress 6.0 sneak peek. I’ll share some highlights of the release features and why I think they are super important for you to take a look. Sooner rather than later.
\n\n\n\nJosepha Haden Chomphosy [00:13:22]
\n\n\n\nAnd then the final, big thing, if you are new to WordPress and this episode has you all fired up to start your blog, we have a bunch of contributors over on the Learn WP team that have just the thing for you.
\n\n\n\nYou can join the online social learning space called How to Make a WordPress Blog. It’s a free online event that will help you get started. I’ll link the information in the show notes below. And I’ll also share in the show notes, a list of WordPress Meetup groups, where you can find more opportunities to learn and get support from other people locally who are also doing things with WordPress.
\n\n\n\nBut you can also find a list in the dashboard of your newly installed WordPress blog you no doubt have after this podcast.
\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:\"12658\";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: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:20:\"WordPress 6.0 Beta 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2022/04/wordpress-6-0-beta-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, 12 Apr 2022 19:08: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:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"6.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12644\";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:63:\"WordPress 6.0 Beta 1 is now available for download and testing.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Dan Soschin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:7809:\"\nWordPress 6.0 Beta 1 is now available for download and testing.
\n\n\n\nThis version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on a production or mission-critical website. Instead, it is recommended that you test Beta 1 on a test server and site.
\n\n\n\nYou can test the WordPress 6.0 Beta 1 in three ways:
\n\n\n\nwp core update --version=6.0-beta1
. The current target for the final release is May 24, 2022, which is about six weeks away.
\n\n\n\nAdditional information on the full 6.0 release cycle is available.
\n\n\n\nCheck the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.
\n\n\n\nTesting for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute. If you have never tested a beta release before, this detailed guide will walk you through how to get started.
\n\n\n\nTesting helps make sure that this and future releases of WordPress are as stable and issue-free as possible. And anyone can do it – especially great WordPress community members just like you.
\n\n\n\nWant to know more about testing releases like this one? Read about the testing initiatives that happen in Make Core. You can also join a publicly-accessible channel on the Making WordPress Slack workspace.
\n\n\n\nIf you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.
\n\n\n\nTo review features in the Gutenberg releases since WordPress 5.9 (the most recent major release of WordPress), access the What’s New In Gutenberg posts for 13.0 (release pending), 12.9, 12.8, 12.7, 12.6, 12.5, 12.4, 12.3, 12.2, 12.1, and 12.0.
\n\n\n\nBeyond the noted changes, which include more than 400 updates and 500 bug fixes for the editor, contributors have fixed 189 tickets for the WordPress 6.0 core, including 91 new features and enhancements. More fixes are on the way.
\n\n\n\nWant to know what’s new in version 6.0? Read on for some highlights.
\n\n\n\nThe WordPress 6.0 release will be packed with all kinds of improvements. Here are just a few:
\n\n\n\nThank you to the following contributors for collaborating on this post: @annezazu, @chanthaboune, @marybaum, @priethor, and @webcommsat.
\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:\"12644\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.9.3 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/04/wordpress-5-9-3-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, 05 Apr 2022 19:50:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{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:\"5.9\";s: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=12575\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"WordPress 5.9.3 is now available! This maintenance release features 9 bug fixes in Core and 9 bug fixes in the block editor.\";s: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:9:\"Jb Audras\";s: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:3896:\"\nWordPress 5.9.3 is now available!
\n\n\n\nThis maintenance release features 9 bug fixes in Core and 10 bug fixes in the block editor.
\n\n\n\nWordPress 5.9.3 is a short-cycle maintenance release. The next major release will be version 6.0.
\n\n\n\nYou can download WordPress 5.9.3 from WordPress.org, or visit your Dashboard → Updates and click “Update Now”.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nFor more information, browse the full list of both Trac and GitHub changes in the release candidate post, or check out the changelog of version 5.9.3 on HelpHub.
\n\n\n\nThe 5.9.3 release was led by Jb Audras and George Mamadashvili.
\n\n\n\nSpecial props to Sergey Biryukov for running mission control.
\n\n\n\nThank you to everyone who helped make WordPress 5.9.3 happen:
\n\n\n\nAki Hamano, Alex Stine, aliakseyenkaihar, Anton Vlasenko, binarymoon, Carlos Bravo, Colin Stewart, David Baumwald, Dion Hulse, George Mamadashvili, glendaviesnz, Greg Ziółkowski, ironprogrammer, Iulia Cazan, Jb Audras, Joe Dolson, Joen A., Jorge Costa, jsnajdr, Marius L. J., Nick Diego, Paul Biron, Peter Smits, pgpagely, Rafi Ahmed, Richard B. Kreckel, Robert Anderson, Rufus87, Sergey Biryukov, Tor-Bjorn Fjellner, Tonya Mork, Abha Thakor, Oliver Juhas, and Weston Ruter.
\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:\"12575\";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: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:37:\"The Month in WordPress – March 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:69:\"https://wordpress.org/news/2022/04/the-month-in-wordpress-march-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, 05 Apr 2022 13:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s: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:22:\"the 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=12583\";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:325:\"We hope that you and your beloved ones are staying safe during these difficult times. If you’re looking for a way to support the humanitarian crisis in Ukraine, you can refer to this episode of WP Briefing. There you will find a list of Non-Governmental Organizations (NGOs) that can help. In parallel to the work […]\";s: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:13376:\"\nWe hope that you and your beloved ones are staying safe during these difficult times. If you’re looking for a way to support the humanitarian crisis in Ukraine, you can refer to this episode of WP Briefing. There you will find a list of Non-Governmental Organizations (NGOs) that can help.
\n\n\n\nIn parallel to the work the community is doing in preparation for the next major release, WordPress 6.0, March has seen the launch of some exciting projects and proposals. Read on to find out more about the latest updates and how to get involved.
\n\n\n\nThe WordPress Pattern Creator is live! This new tool allows anyone with a WordPress.org user account to build, edit and submit their best block patterns to the Pattern Directory.
If you’ve used patterns in WordPress, you’ll know that they make it easy to add unique layouts to your website. These include galleries, testimonials, pricing tables, and more. Opening the directory to public submissions enables any WordPress user to enjoy a wider variety of patterns to use on their sites.
A few updates to the WordPress 6.0 planning were published last month. In case you missed them, today (April 5) at 15:00 UTC there is a live and interactive WordPress 6.0 walkthrough hosted by contributors of the release squad.
\n\n\n\nThe event will take place via Zoom and include a discussion on the new features, potential blockers, and a Q&A session with the community. Attendance is open to anyone who wants to know more about what’s coming in WordPress 6.0.
\n\n\n\nVersions 12.8 and 12.9 of the Gutenberg plugin were released last month. With them, some new exciting features and updates.
\n\n\n\nHave a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this Month in WordPress: @rmartinezduque, @mysweetcate, @anjanavasan.
\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:\"12583\";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: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:87:\"WP Briefing: Episode 28: Coming to a WordCamp Near You: A Return to In-Person WP Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wordpress.org/news/2022/04/episode-28-coming-to-a-wordcamp-near-you-a-return-to-in-person-wp-events/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 04 Apr 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=12506\";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:172:\"Curious about returning to WordPress events safely? Tune in as WordPress Executive Director Josepha Haden Chomphosy discusses guidelines for returning to in-person events. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2022/03/WP-Briefing-028.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:11997:\"\nIn the twenty-eighth episode of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy discusses returning to in-person WordPress events.
\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\nJosepha 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. I’m your host, Josepha Haden Chomphosy. Here we go.
\n\n\n\nJosepha Haden Chomphosy [00:00:40]
\n\n\n\nI was checking the list of upcoming events recently as part of just my regular work and saw that the call for organizers for WordCamp Asia is open. On the one hand, it made my heart skip a beat with excitement. That event is six years or so in the making. And on the other hand, it reminded me of February 10th, 2020, the day that Matt told me that we had to proactively cancel WordCamp Asia. That week was truly heartbreaking for me as well as I think the entire organizing team.
\n\n\n\nBut it also, fortunately, was prescient. As I think back over the two years since then, I’m grateful for our community wranglers and deputies who have consistently hosted important discussions about how to return to in-person events safely. And with two of our major flagship events returning this year, I’m here to summarize, sort of, what the rules and guidelines are.
\n\n\n\nBut certainly I hope that you come away from this with an idea of what’s being done to keep everyone safe as we are best able.
\n\n\n\nJosepha Haden Chomphosy [00:01:44]
\n\n\n\nFirstly, before we dig into specifics, I want to be clear upfront that the guidelines for COVID-aware events are mandatory, unless otherwise stated. For folks who’ve been attending WordPress events, or participating in the community for a long time, this is a change. As a program, we have always done our best to be flexible with guidelines so that we can prioritize local knowledge. But our responsibility is to the long-term success of this community and this program. So moving forward with in-person events that risk the health of our community members poses risks to the program itself. So with that in mind, let’s learn what we’re going to see at events for the rest of the.
\n\n\n\nJosepha Haden Chomphosy [00:02:28]
\n\n\n\nFor any WordPress event that is gathering more than 50 people, the new mandatory guidelines are:
\n\n\n\nNumber one, follow local laws and guidelines. If your area has suggested guidelines on top of the mandatory ones, follow those.
\n\n\n\nSecond, is if you are in a location where laws or guidelines require or permit venues to limit admission based on a person’s vaccination status and masking, then events can only happen in venues that are willing to provide staff to check for vaccination status at the door. And then also to remind participants to wear masks during the event.
\n\n\n\nAnd the third thing is if your area or venue legally cannot check vaccination status, your area must pass the in-person checklist, which I will link in the show notes below. But that in-person checklist has to be passed at the time of the application and then again at the time of the event. And in addition to that, the venue must be willing to provide staff who will remind participants to wear masks and check for temperature during the event.
\n\n\n\nJosepha Haden Chomphosy [00:03:33]
\n\n\n\nOrganizers in these areas must be prepared to move online or cancel if the region fails the safety checklist, which again, will be linked in the show notes below. So those are the three things and they are pretty dense, but also I think allow for a fair amount of flexibility. There is also a tidy flow chart linked in the sidebar of make.wordpress.org/community that will help you to decide what sort of event your own area can support right now.
\n\n\n\nSo those are the mandatory guidelines for WordPress events in general right now, but you probably also have a few specific questions. So I’ve got the three most common questions ready to go with answers from Angela Jin who helped me to kind of pull together the information for this particular podcast props to Angela. Thank you.
\n\n\n\nJosepha Haden Chomphosy [00:04:25]
\n\n\n\nSo, first question, anything specific to know about WordCamp Europe? WordCamp Europe will be following these guidelines as well. All attendees and participants are expected to wear a mask while they are at the event and catering will be offered outside so people can remove their masks to eat.
\n\n\n\nThe second common question is how will these guidelines change as countries and local governments begin deescalating restrictions and safety measures? We should consider these guidelines to be subject to evolution based on what the team is hearing and seeing from the community. But right now we intend to keep these stricter guidelines in place until we see how the loosened rules play out elsewhere.
\n\n\n\nAnd then a third frequent question is what’s going to happen to all these online events?
\n\n\n\nThe community team will continue to support online events right now. So if your community doesn’t feel ready to have an in-person event, but still wants to kind of get everyone together that is still allowed, and still encouraged. And finally the community team will continue to keep a close eye on situations around the world.
\n\n\n\nIf it becomes safe to do so, and your community is interested, they of course will be happy to chat with you about a WordCamp. There is an application that I will share the link to in the show notes below as well. In case that is something that your community is wanting to look into.
\n\n\n\nJosepha Haden Chomphosy [00:05:54]
\n\n\n\nOh, and I have a little postscript also. I know I was like finally, and now I’m doing a finally, finally. That’s what postscripts are about. P.S. If you have not stopped by the community team’s site or any of their meetings, they’ve been doing a really great job of keeping things moving through two years of unpredictable changes. If you are a community team member, I want to offer you a huge thanks. Thank you so much for helping us to stay aware and able to move forward.
\n\n\n\nIf you are an organizer, pat yourself on the back. I want to thank you for pivoting with us, moving through online events, even though they are not at all the same as in-person events and certainly they don’t share the reasons that we get people together sometimes.
\n\n\n\nAnd finally, if you are an end to end attendee, if you go to WordPress meetups or you go to any sort of WordPress online events or WordCamps, anything like that, thank your local organizer. They have been doing this probably for a while, and I’m sure that they are looking forward to getting back to in-person events themselves, but even, so they have been putting in a lot of volunteer hours to help make sure that we all know how to use WordPress.
\n\n\n\nAnd so find them, thank them, and I’m sure that they’ll appreciate it.
\n\n\n\nJosepha Haden Chomphosy [00:07:20]
\n\n\n\nAnd with that, it is time for our small list of big things. Number one, WordCamp Asia has a call for organizers open! This event will be in 2023. And I think that we all simply cannot wait. So I’ll link the call for organizers in the show notes. And then of course you can follow that whole site to stay up to date on what’s happening there.
\n\n\n\nThe second thing is, while we’re on the topic of events, there’s also an open discussion about how we can best support organizers who are getting back to in-person events. We’d like thoughts from both organizers and attendees. So feel free to drop by and leave a note in the comments section. And while you’re over there, the third thing in my small list of big things, there’s also an open discussion about regional events. So go over there, get all your thoughts about WordPress events together. Get them all sorted out in one go. Just leave comments, boom, boom, boom, boom, boom. All over the place.
\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.
\n\n\n\nAnd I’ll see you again in a couple of weeks.
\n\n\n\nJosepha Haden Chomphosy [00:08:54]
\n\n\n\nSo my most embarrassing WordCamp story actually has to do with where I was supposed to be versus where people thought I was supposed to be. This was early on in my time with WordPress, with Automattic. And I had convinced someone, I had convinced a colleague and friend of mine to go to my home WordCamp, WordCamp Fayetteville over there in Arkansas.
\n\n\n\nAnd then I didn’t go. But I knew I wasn’t going, I knew I was going to WordCamp Boston, but he did not know that I was not going to go. And so he arrived at WordCamp Fayetteville, WordCamp Northwest Arkansas. I can’t remember what it was called at the time. And immediately was confused about where I was and why I wasn’t there.
\n\n\n\nAnd so there was this excellent moment of mass confusion among states where the folks at WordCamp Fayetteville started tweeting about how I had convinced this contributor to go to that event and then didn’t show up. And then the folks at WordCamp Boston, we’re looking at all of those tweets, because if you are a WordCamp organizer, you are always looking at the tweets from all the other WordCamps happening in your weekend.
\n\n\n\nAnd people got very confused about why I was in Boston while they were thinking that I was in Fayetteville, even though the tweets were talking about how, like, I wasn’t in Fayetteville. They probably didn’t say that it was probably more along the lines of like, “Hey, let’s share a photo with Josepha” to, like, make fun of the fact that I wasn’t there.
\n\n\n\nAnd so I caused mass confusion in multiple states. That’s probably my most embarrassing WordCamp story. You’re welcome. Bye!
\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:\"12506\";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:75:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"People of WordPress: Juan Aldasoro\";s: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:72:\"https://wordpress.org/news/2022/03/people-of-wordpress-juanfra-aldasoro/\";s: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, 31 Mar 2022 21:42: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:8:\"category\";a:7:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:9:\"HeroPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:20:\"Polyglot Contributor\";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:5:{s:4:\"data\";s:12:\"Support 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12512\";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:120:\"The People of WordPress feature this month shares the story of web and plugin developer Juanfra Aldasoro from Argentina.\";s: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:28:\"webcommsat AbhaNonStopNewsUK\";s: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:20058:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website developer and product manager from Argentina, who found in the software a way to live his life in the way he dreamed.
\n\n\n\nWordPress offers something to everyone. For Juan Aldasoro, a developer and product manager for a large distributed company, it provides an opportunity to combine his different interests and skills to live the type of life he wanted.
\n\n\n\n“I like visual, creative and technical things. The joy of WordPress is that you can do all of these things, you don’t have to limit yourself to any one aspect . You can also do this from almost anywhere in the world!”
\n\n\n\nFrom working in products since 2012, Juan sees WordPress as a major part of his skillset and toolbox. He said: “It gives you an opportunity to be part of building a product which could potentially be used by thousands of people and more on your site. It encourages you to think about different languages and how you can make it accessible. It allows you to work on different platforms. Working in WordPress gives you this broad approach. Working this way on products ended up pushing me into learning about all these different things. Only in open source can you really do this and use your creative side to find solutions.”
\n\n\n\nBorn in a mid-sized city in Argentina, Juan was raised in a family in which music, arts and sports were always an essential part of everyday life.
\n\n\n\n“These activities encourage human beings to be creative and participative, and at the same time they are highly formative when it comes to mould people in order to become part of a group, a team, a community.”
\n\n\n\nThe youngest of five siblings, Juan became highly motivated, trying to follow the steps of his siblings. Having a computer at home, he started to make connections that laid the foundation for his career as a developer. His interest in computers grew through that access to a machine running MS-DOS – the one with the black screen command line! Mastering this became a challenge to him and something to share with others. Through doing this, he found a way to more social interaction and new friendships.
\n\n\n\n\n\n\n\nWithout being conscious of it, my friends and I were sharing pieces of code.
He said: “I started learning some super easy stuff that made me feel like Houdini at that time. I could save a game play, something intangible, on a floppy disk and carry that piece of plastic and magnetic material back home. I was saving the play or game in a square object and then loading that back at home. I now realize, those were my first interactions with computer commands. Without being conscious of it, my friends and I were sharing pieces of code in a unique way.”
\n\n\n\nThis interest grew further through computer magazines and experimenting as “there was always something new to learn.” Although sport became a big part of Juan’s life in his teens, he kept up his computer learning. Taking a new direction, he found online tutorials enabling him to learn how to play the guitar. This led to setting up a punk rock band with his friends.
\n\n\n\n“Education has always been important in my family, and thanks to my parent’s efforts, I attended a school where I learned to express myself in another language.” The school had hired a satellite internet connection in the mid-nineties and had HTML on the computer studies program. These facilities were not that common in Argentina or many other countries either at that time. Also, his parents had the foresight to secure a rare internet connection at the house in 1997.
\n\n\n\nJuan recalled: “Browsing around the Internet opened a new universe in my mind. This new universe was extremely fantastic but also extremely expensive. I needed to make the most of every second online.”
“It was a whole new world and one thing led to the other. I started learning a bit of everything, editing graphics, scripting and so on. I still remember my first website in the fantastic sunset strip, Geocities.”
After high school, Juan moved to the city along with his brother and began to study IT at University. When he was asked by a friend to work at a software company, he decided to try that whilst continuing his studies. Through his job he had the chance to explore web-related opportunities, and with a friend from university, they started managing teams and projects across Latin America and Spain.
Juan describes this experience as one of the most fulfilling in his life. He was able to travel abroad for work, experience remote working, manage teams, present projects and speak formally in front of senior people. As the company grew at a fast pace, they learned how to set up and run a large organization. Eventually, he decided to drop out of his university program and focus on the opportunity of learning first hand.
One of the key early learning from working internationally was that business and web development could be just as fast-moving and successful in Argentina as in other places. “I realized there’s no such thing as a secret sauce for success. Projects are backed by people’s talent and time, and you can find that in any latitude.”
By his mid-20s, Juan decided he wanted to try building something from scratch. He created a social network for photo sharing in Latin America, which was used by more than 30,000 people across Latin America and Spain in its time. Through this, he discovered that other people had a blog and he did not want to be left behind. The discovery of WordPress was to change the focus of his life.
Spending some time traveling around Europe, Juan found himself ‘surrounded by uncertainty’ and worried about what the future could bring. “I had some clues, but under uncertainty, the more you ask the less you answer. I started thinking about embracing the following philosophy: I didn’t want to be part of a large company, I didn’t want to continue studying and I wanted to travel as much as I could.” He did not realize at that time how this vision for his life was to mirror what he would find in WordPress.
\n\n\n\nHe started using WordPress for a few sites in 2005. By 2007 he was using it for almost everything. He was struck by the magnitude and range of what the software could do, from a simple tool used to create a blog in the blink of an eye through to complex projects.
\n\n\n\nHis first problem-solving project was simple and saved data received through a contact form plugin. “To complete this project I discovered the Codex and I learned how easy and intuitive it is to create a plugin. I had fallen in love with WordPress.”
\n\n\n\n\n\n\n\nI was truly amazed by how I could learn from others.
As he explored the options with the software, Juan was unsure of how intellectual property worked and wanted to be respectful of other people’s work. “I didn’t understand open source yet, and I wasn’t sure if I was stealing from others. That was my first interaction with GPL and open source. I was truly amazed by how I could learn from others and improve things created by others or by myself.”
\n\n\n\nHe realized: “WordPress was the way to go if I wanted to pursue a dream of traveling, skipping winter, and working at the same time; what we now call a digital nomad. I already knew how to work remotely, I could work for companies located anywhere, as long as they could communicate in English or Spanish.”
\n\n\n\nJuan started his own web agency, where he provided services to small and medium-sized companies abroad in the USA, UK, and Australia. He built his reputation and developed strong relationships in WordPress. “The experience couldn’t be better. I was learning, having fun, making a living out of it, and at the same time exploring the world.”
\n\n\n\nIn mid-2012, he discovered the full power of the WordPress community firsthand. In his spare time he started developing themes and from all he heard, wanted to attend a major event with lots of others in WordPress, a WordCamp. He took the plunge and booked for WordCamp in Edinburgh, in the UK. He said: “I got to meet many super talented people, and the atmosphere of the event was awesome. A place where competitors were also colleagues. Seeing the humility of somebody like Mike Little, the co-founder of WordPress, was amazing.”
\n\n\n\nHe added: “While there, unconsciously, I started dreaming of holding something like that in Argentina – the joy of hosting the WordPress community in my home country.”
\n\n\n\nBack home, while browsing the Codex, he happened to see that WordPress was turning 10. A lot of meetups were going to be organized worldwide to celebrate the birthday. But there was nothing organized in Argentina. This was a catalyst for starting a local meetup. Together with a colleague, he organized an Argentinian 10th birthday meetup.
\n\n\n\nMore than 20 people showed up. “There was a common denominator. We all loved WordPress, it was part of our day-to-day life. We wanted to share experiences, make new friends and continue growing from what we could learn from others. That day we were a group of people with shared interests. That’s the simplest way to define a community, isn’t it?” This early meetup led to the formation of what is now called WordPress Argentina.
\n\n\n\nIn his desire to skip winters and do more traveling, his next adventure was to take him to visit family working in the US and attend one of the biggest WordCamps in the world in San Francisco. His interest kept growing and he traveled across Europe to be part of the first edition of WordCamp Europe in the Netherlands in 2013.
\n\n\n\nHe said: “There’s almost nothing I could write to fully express what you experience in such events. They are the main WordPress events worldwide. The best part: I made a lot of good friends from many different places. I’m glad I have more excuses to continue traveling.”
\n\n\n\nOnce again in Argentina, our organization started growing thanks to the energy of the whole group, we started hosting formal meetups. In May 2015, we crowned all these efforts with a new WordCamp in Buenos Aires, Argentina.
\n\n\n\n“Organizing such an event in my home country with many of the contributors I had met from the very first meetup was an experience I will always keep with me.”
\n\n\n\nJuan believes one of his biggest contributions to open source was as part of being able to expand the community in Argentina and to share this with other Latin American and Spanish speaking countries. He also contributes as a volunteer translator in the Polyglots Team, to the Make WordPress Support team, and contributes to code blocks and Gutenberg. “I am really excited about seeing the future of Gutenberg as it is the future of WordPress.”
\n\n\n\nThroughout his time contributing, Juan believes in helping to set the foundations and encouraging others to give their time and talents. He is keen to share that contributing does not have to be the same all the time and that you can have breaks and focus on one area in a particular period too. He gives the example of how in his spare time he watches Trac, where tickets about the software are logged, and looks where he might be able to help or think of solutions.
\n\n\n\nHe said: “Anytime I find I can contribute to or make improvements in code-related areas, I will do as it is important to keep giving to the community. I enjoy crawling over meta, trac, GitHub and the different places that are requesting help. There is always somewhere you can help. At the moment, my focus is code and translations. I always try to save time to help these two areas. It is like you give and you get, you learn things. You meet amazing people and opportunities arrive.”
\n\n\n\n“Life is about experiences, it is about the people you surround yourself with and trying to do what you love. What you can find in an open source project like WordPress is an environment full of people who work with a tool they love. An environment that is ready to help and to give advice. Follow what makes you happy, try to be surrounded by people who make you better, try to empower others, try to give back. Try. Make your own path.”
\n\n\n\n\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 Juan Aldasoro (@juanfra) for sharing his story.
\n\n\n\nInterviews and feature by Abha Thakor (@webcommsat) and Surendra Thakor (@sthakor). Reviews by Mary Baum (@marybaum), Chloe Bringmann (@cbringmann), Meher Bala (@meher), Anjana Vasan (@anjanavasan) and Yvette Sonneveld (@yvettesonneveld).
\n\n\n\nThanks to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) and others for their support of this initiative.
\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
\nToday I share a Twitter thread, a post and a few of my own thoughts on that first WordCamp experience as well as tips for the all attendees.
\n>> The post That First WordCamp for WooCommerce and WordPress Builders 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, 12 Aug 2022 09:04: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: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:66:\"WPTavern: New Twenty Twenty-Three Default Theme Now in 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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=136881\";s: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://wptavern.com/new-twenty-twenty-three-default-theme-now-in-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:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4228:\"Last month, WordPress design contributors proposed creating a new kind of default theme that would bundle a curated set of style variations, instead of creating a new theme from scratch. This idea resonated with participants in the discussion and plans are now underway to use a stripped-back version of Twenty Twenty-Two as the base for the new theme.
\n\n\n\nAutomattic design director Channing Ritter published a preview of what the base theme might look like with sample variations applied, along with the Figma design mockups.
\n\n\n\n\n\n\n\nTwenty Twenty-Three’s predecessor has a highly opinionated design. The upcoming default theme is more like a blank canvas with the spotlight on the style variations. Headings are not as prominent, typography has been replaced with system fonts, and there are no images included. The theme will use the fluid typography feature released in Gutenberg 13.8, and has spacing presets in place.
\n\n\n\n“One important note is that we are limited in the number of fonts we can include with the theme and should aim to use 3–4 different typefaces across all variations (in addition to systems fonts),” Ritter said. The initial list includes the following fonts, but can evolve based on contributors’ feedback:
\n\n\n\nOne of the most exciting aspect of this project is that WordPress’ design contributors have invited the community to take a stab at submitting their own style variations for consideration. The variations that are selected will ship as part of the upcoming default theme.
\n\n\n\nWhereas many default themes in the past have come from a single designer or from an existing theme, Twenty Twenty-Three (TT3) will offer a kaleidoscope of style variations from different community contributors.
\n\n\n\nThe theme in progress is available on GitHub and anyone can try their hand at creating a style variation. There are three different ways to do it. The most straightforward for some will be to create an alternate theme.json file and edit the code directly.
\n\n\n\nThose who prefer to design their own variation visually in the editor can make changes to the Global Styles panel and then save them as a new style variation using the Create Block Theme plugin. This opens up contribution to anyone with design skills, even if they do not feel comfortable editing the theme.json file. Alternatively, contributors can design static mockups in Figma or another program.
\n\n\n\nMore detailed instructions for submitting a style variation are available in the post and those interested to contribute can join the new #core-themes-projects Slack channel to ask questions and connect with others who working on the same project. The first variation submission to the TT3 repository is from new contributor Colin Chadwick, who created an eggplant color scheme complemented by the DM Sans font.
\n\n\n\nThe WordPress community is full of talented designers and this call for style variations is an incredible opportunity to contribute without having to touch any code.
\n\n\n\nStyle variation submissions for this project will close on August 31. The final curated set will be announced on September 7. The new TT3 default theme will ship with WordPress 6.1, which is expected on October 25, 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:\"Fri, 12 Aug 2022 02:09: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: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: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:22:\"Matt: Telegram Channel\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=59104\";s: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:39:\"https://ma.tt/2022/08/telegram-channel/\";s: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:509:\"You can now subscribe to updates from this blog in this Telegram channel! Right now it will get updates from Ma.tt and Matt.blog, and hopefully my Tumblr in future once the bot supports that as a content source. If you’d like to set this up for your WordPress site, check out this tutorial on Jetpack.
\";s: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, 11 Aug 2022 19:50:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:64:\"Do The Woo Community: Plugins vs. SaaS with Danni, Josh and Vito\";s: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=72616\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://dothewoo.io/plugin-or-saas-wordpress-woocommerce-products/\";s: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:400:\"Listen as some WordPress and WooCommerce builders weigh in on choosing between a SaaS product or standalone plugin.
\n>> The post Plugins vs. SaaS with Danni, Josh and Vito 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, 11 Aug 2022 10: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: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: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:112:\"WPTavern: New Proposal Calls for Contributors to Stop Merging Experimental APIs from Gutenberg to WordPress Core\";s: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=136853\";s: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:123:\"https://wptavern.com/new-proposal-calls-for-contributors-to-stop-merging-experimental-apis-from-gutenberg-to-wordpress-core\";s: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:8398:\"The practice of merging experimental APIs from Gutenberg into WordPress core may soon be coming to an end. A new proposal, published by Automattic-sponsored contributor Adam Zielinski, calls for contributors to stabilize APIs before merging them into core.
\n\n\n\nOver the years, approximately 280 experimental APIs have been merged from the Gutenberg plugin, which Zielinski audited in a ticket he opened for the issue in April. In balancing the drive to move fast with iterating on the editor(s) against WordPress’ commitment to backwards compatibility, the number of experimental APIs has become untenable and the practice of merging them into core is now being actively reconsidered.
\n\n\n\nOfficially, the experimental APIs are flagged as such to discourage third-party use, since they are expected to change. In practice, people building for the block editor are using them anyway because they are in core and they want to extend the features these APIs enable.
\n\n\n\n“Plugin and theme authors are forced to rely on the __experimental
features that could get removed or changed in a backwards incompatible way at any time,” Zielinski said, echoing the frustration and concerns many developers have had with the project the past few years. “It is a serious maintenance burden. Every new Gutenberg/WordPress release means potentially breaking changes.”
WordPress core committer Peter Wilson commented on the ticket, saying he is in favor of limiting experimental APIs to bleeding edge product. Driving home the need for this change, he cited a host of negative impacts that these core experimental APIs have had on the ecosystem:
\n\n\n\n\n\n\n\n\n\n
- core committers unwilling to use certain library features to make core tasks easier because they don’t trust the reliability
- developers no longer upgrading WP client sites. As a core committer who has strived to maintain backward compatibility for years this disappoints me. As a security team member it’s greatly concerning
- developers deciding to include copies of packages in themes and plugins rather than rely on the
wp.*
globals. Again this concerns me from a security perspective but it also increases the JavaScript payload significantly more than maintaining backward compatibility- reports of backward compatibility breaks in minor versions: “you don’t expect a 5.9.1 release to break the responsiveness of a bunch of images in our sites outside the block editor”
- developers considering never using core blocks because they’re too unstable: “I stopped using/extending core blocks because they were changing too much and I’ve been using ACF Blocks so that I at least I know I can make blocks that won’t break. Granted the UI isn’t as good as core blocks but I’ll take stability over blocks breaking any time.”
The Gutenberg plugin was meant to function as a feature plugin where breaks in backwards compatibility are expected while contributors polish features before merging them into core. Getting back to the roots of this approach, and making the editor less experimental, is at center of this proposal.
\n\n\n\n“Instability between versions is already beginning to alienate some of the block-editors biggest external advocates,” Wilson said.
\n\n\n\nMaintaining this level of instability could discourage people from building on WordPress, pushing them away to other more straightforward projects that are managed in a different way. It is possible that the need to rely on experimental APIs has discouraged developers from building more products, slowing block editor adoption.
\n\n\n\n“As a plugin author that is currently using many __experimental
APIs, I would love to see these stabilized,” WP Engine-sponsored contributors Nick Diego said. “Most provide crucial functionality but building a product that relies on an __experimental
API is always a bit disconcerting. So long as the process is exceedingly transparent, is well publicized, and we provide plugin/theme authors with a guide on how to migrate to stable versions, then I like this initiative.”
After months of discussion on the ticket, Zielinski distilled contributors’ concerns into the plan of action proposed on the Make WordPress Core blog.
\n\n\n\nThe proposal indicates that most of the existing experimental APIs already merged into core would get a stable alias.
\n\n\n\n“It would preserve backwards compatibility and shouldn’t noticeably affect the bundle size,” Zielinski said. “Some will need a different treatment; let’s discuss that case-by-case.” He also recommended contributors consider whether an existing experimental API already in core needs to be removed. He doesn’t anticipate many instances of this but recommends these use established practices of contacting plugin authors, using soft deprecations, and publishing Core posts.
\n\n\n\n“I also see two things at play here: the use and abuse of experimental APIs during the API design (generally to be used and tested in the Gutenberg plugin) and the lack of a diligent process for stabilizing them when they satisfy design criteria,” Gutenberg lead architect Matias Ventura commented on the original ticket. “The ones that are to be considered de facto public are those that have existed for many releases in a stable form despite their nomenclature.”
\n\n\n\nIn the interest of preserving WordPress’ ability to deliver on its backwards compatibility promises, the proposal recommends experimental APIs be restricted to the Gutenberg plugin and never merged into core. In the instances where a stable feature depends on an experimental API, Zielinski identified a simple answer:
\n\n\n\n“Then it isn’t actually stable. Let’s stabilize the dependencies first.”
\n\n\n\nThis is essentially a new way of moving forward that should increase stability and confidence in WordPress’ APIs and updates, but it does have a few drawbacks.
\n\n\n\nUsers and contributors can expect that Gutenberg features may be slower merging into core, as they cannot rely on experimental APIs when they hit prime time distribution in major releases. Zielinski also noted that contributors may also have difficulty refactoring these APIs once they have shipped and go into use on millions of WordPress sites.
\n\n\n\nSo far the proposal has had overwhelmingly positive support, as many believe these APIs should never have arrived to core in the first place while still in the experimental stage.
\n\n\n\n“I’m very much in favor of this approach,” WordPress developer Mark Root-Wiley said. “I build custom themes and have a few simple plugins. For both, I have found myself somewhat frequently forced to deal with experimental APIs and the difficulties of keeping up to date with them when features are put in core that can only be turned off, adjusted, or extended through an experimental API.”
\n\n\n\n“A return to this sort of stability in core would go a long way to regaining some developer goodwill,” WordPress contributor Dovid Levine commented on the proposal.
\n\n\n\nThe deadline for commenting on the proposal is September 7, which would close out the discussion just shy of three weeks before WordPress 6.1 Beta 1 is expected. This gives contributors some time to more deeply audit the experimental APIs ahead of the next major release, should they reach a consensus on restricting them to the Gutenberg 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 11 Aug 2022 03:23: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: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:160:\"Post Status: Back Compat & Experimental APIs, Safely Handling SVG via “Insert URL”, WordPress 6.1 Bug Scrub Schedule, Database Performance Health Checks\";s: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=104146\";s: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:196:\"https://poststatus.com/wordpress/week-in-review/make-wordpress/back-compat-experimental-apis-safely-handling-svg-via-insert-url-wordpress-6-1-bug-scrub-schedule-database-performance-health-checks/\";s: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:15443:\"Is it safe to insert an SVG via URL? How healthy is your database? Performance Team Rep Nominations.
Give your feedback on this proposal to stop merging experimental APIs from Gutenberg to Core. Today, experimental APIs are merged to Core and sometimes removed later. See the WP 6.0 Experimental APIs.
>
.
.
>
.
As the WordPress handbook states: Historically, WordPress has been known for preserving backward compatibility across versions.
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.
On the podcast today we have Paul Bearne.
\n\n\n\nPaul is a WordPress enthusiast who loves to come up with ways to make WordPress do things it doesn’t normally do. Having engaged with WordPress almost from the start, he specialises in the creation of highly performant, scalable, accessible and SEO friendly code.
\n\n\n\nHe has contributed consistently to WordPress Core since version 3.9 as well as setting up a local meetup and speaking at WordCamps. He is currently being sponsored by XWP to work on Core as part of their Core initiatives.
\n\n\n\nIn the podcast today Paul talks about the many ways in which it’s possible to work within the WordPress ecosystem. He’s tried many of them out over the years.
\n\n\n\nMany of the jobs in and around the WordPress space require only a few things, access to power and internet and a computer. The geographical constraints for work are often non-existent. If you have the skills, can get online and put in the hours, then you might be good to go. The pandemic brought this distributed working model to the masses, as more and more organisations realised the benefits that working in this way affords.
\n\n\n\nPaul talks through some of the different ways that you can work and draws out the benefits and drawbacks that they have. How can you find the work and what can you do to make sure that it’s as stable as it can be?
\n\n\n\nIf you’re already a remote worker, much of this conversation will resonate with you, but if you’re not, but are curious about your options, this podcast will be of interest.
\n\n\n\nTypically, when we record the podcast, there’s not a lot of background noise, but that’s not always the case with these WordCamp Europe interviews. We were competing against crowds and the air-conditioning. In this episode both Paul and I wore face masks which you can also detect. Whilst the podcasts are more than listenable, I hope that you understand that the vagaries of the real world were at play.
\n\n\n\nTranscript[00:00:00] Nathan Wrigley: Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast which is dedicated to all things, WordPress, the people, the events, the plugins, the blocks, the themes, and in this case how WordPress can enable you to work and live in different ways.
\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 dot com forward slash feed forward slash podcast. And you can copy that URL in to 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 all your idea featured on the show. Head over to WPTavern dot com forward slash contact forward slash jukebox. And use the form there.
\n\n\n\nSo on the podcast today we have Paul Bearne. Paul is a WordPress enthusiast who loves to come up with ways to make WordPress do things it doesn’t normally do. Having engaged with WordPress almost from the start, he specializes in the creation of highly performant, scalable, accessible, and SEO friendly code.
\n\n\n\nHe has contributed consistently to WordPress Core since version 3.9, as well as setting up a local meetup and speaking at WordCamps. He’s currently being sponsored by XWP to work on Core as part of their Core initiatives.
\n\n\n\nIn the podcast today, Paul talks about the many ways in which it’s possible to work within the WordPress ecosystem. He’s tried many of them out over the years.
\n\n\n\nMany of the jobs in and around the WordPress space require only a few things, access to power and internet, and a computer. The geographical constraints for work are often non-existent. If you have the skills, can get online and put in the hours, then you might be good to go. The pandemic brought this distributed working model to the masses as more and more organizations realized the benefits that working in this way affords.
\n\n\n\nPaul talks through some of the different ways that you can work and draws out the benefits and drawbacks that they have. How can you find the work and what can you do to make sure that it’s a stable as it can be?
\n\n\n\nIf you’re already a remote worker, much of this conversation will resonate with you. But if you’re not, but are curious about your options, this podcast will be of interest.
\n\n\n\nTypically when we record the podcast, there’s not a lot of background noise, but that’s not always the case with these WordCamp Europe interviews. We were competing against crowds and the air conditioning. In this episode both Paul and I wore face masks, which you can also detect. Whilst the podcasts are more than listenable. I hope that you understand that the vagaries of the real world were at play.
\n\n\n\nIf you’re interested in finding out more, you can find all the links in the show notes by heading over to WPTavern dot com forward slash podcast, where you’ll find all the other episodes as well. And so without further delay, I bring you Paul Bearne.
\n\n\n\nI am joined on the podcast today by Paul Bearne. How are you doing?
\n\n\n\n[00:03:52] Paul Bearne: Thank you. All right. It’s been a hectic WordCamp, and feet haven’t touched the ground, but yeah, it’s good to be here.
\n\n\n\n[00:04:00] Nathan Wrigley: What have you mainly been doing over the last couple, well, I say a couple of days, maybe you weren’t here for contrib day.
\n\n\n\n[00:04:04] Paul Bearne: I was here for contrib day, because I’m a core contributor. I’ve been working on the performance plugin. I’m lucky to be sponsored by XWP to work on core projects. And we’ve been focusing on the performance enhancements. So in the last release, we got five queries out of a standard homepage load. You imagine what that’s done to a million sites. And the performance add-on, I’ve been working on the dominant color feature, which is coming in the next block.
\n\n\n\nThat’s gonna be interesting to see the reaction of that in the community as that comes out. Cause that’s a visual change. And the WebP stuff. So I’ve been working, busy doing that, as well as running my own premium plugin, business. And it’s really nice to be able to work part-time for one of the big agencies.
\n\n\n\n[00:04:48] Nathan Wrigley: Yeah, we’ll come onto that in a minute. You’ve got a talk here though, which kind of anchors us to what we’re gonna talk about. How did it go?
\n\n\n\n[00:04:55] Paul Bearne: I think it was well received. A lot of people said it was really good value for them. Yeah, I think it went down really well.
\n\n\n\n[00:05:03] Nathan Wrigley: Just broadly outline what the topic was that you covered.
\n\n\n\n[00:05:05] Paul Bearne: It’s a lifestyle talk. basically trying to expand and give people confidence that they can create a lifestyle, whatever lifestyle they want with WordPress. You know, whether they want to be a digital nomad whether they want to live in the countryside or live in the center of a city. There is employment available in all of those places. And you need to look at yourself, see what your strengths and weaknesses are.
\n\n\n\nAre you a city or a country person? Are you self-directed or do you need to be managed? What’s your timekeeping like? Can you do sales? Can you do administration of doing invoices and tax returns and things like that? Cause if you can’t, you can’t be freelance, or not, not easily.
\n\n\n\nI’m lucky that my wife is good at the sort of administration stuff. So I’ve been able to do more freelance work than really I should be able to. But now my life’s changed a little bit and having been able to work full time or be paid by XWP to work on core, which is like a dream job for me. It reduces the amount of administration my wife has to do, and I haven’t gotta go chasing freelance work. It’s coming to me. The work is being found for me, and it’s interesting work. You can create whatever life you want. There’s a niche in WordPress.
\n\n\n\n[00:06:29] Nathan Wrigley: Presumably, if that’s the case that you’ve been through a whole cycle of different types of work, maybe you work for an agency and a…
\n\n\n\n[00:06:37] Paul Bearne: I went through the various types of agencies. We looked at multinationals, we looked at small agencies, big agencies, government digital services, media companies, high end design agencies in the center of cities, and then the distributed agencies, and touched a little bit on what it’s like to have a plugin, a premium plugin. What it’s like to be as a freelance person, because I’ve done all of those in my career. So I was able to give some, hopefully some insight to what it’s like to do those. And what’s the pitfalls and the bonuses of working in those different environments.
\n\n\n\nSecond half the talk I tried to give some career advice and some, you know, you can do this. This is gotta get noticed. How do you stand out in the crowd? How do you price yourself as a freelance person, and a few things like that. Try to set some reasonable expectations of what the market, what you need to charge to actually be viable.
\n\n\n\n[00:07:33] Nathan Wrigley: If you look back on your life was it a series of trying things out and then ultimately dissatisfaction with the way that you were working and then try something new? Eventually find that that was not satisfactory and try something else and ultimately where you are now. And it sounds like at this point in time, you’re really happy with where you’re at.
\n\n\n\n[00:07:51] Paul Bearne: Yes, of course you have to take what comes. I talked in my talk about, details are okay. The trick is to fail fast and learn. So if you get into a situation where it isn’t right, don’t hang around. There is lots and lots of good freelance or good WordPress work out there, or just development work. You don’t have to put up with bad environments, horrible bosses, stupid hours. Not unless you are getting a reward.
\n\n\n\nAnd if you’re, if you are in a high end design agency, it’s a young game, and the burnout is quite high but they’re gonna pay you a little bit more. You’re gonna be working on really leading edge work. So you’ll put up with the hours. And you’ll be happy to go out and socialize with the team after work, because that’s part of the culture. But if that’s not what you want then there is other choices.
\n\n\n\nMaybe that’s a young person’s game and then you mature into a slower agency, a local agency, or a distributed agency, or you go freelance. You get a few clients and you run freelance. Or maybe you do partly your own freelance or partly on the freelance platforms like Codeable, and you work that way.
\n\n\n\n[00:09:13] Nathan Wrigley: I know that you said that failing fast is a desirable way to go about it. And I can see what you’re saying there in, in the sense that you’ve got a quickly figure out that this isn’t working, because then you need to quickly find something which is working. Presumably there’s gonna be a raft of people, anybody listening to this, there might be a load of people saying, yeah, that’s okay Paul, but I’ve already got the mortgage, and I am living hand to mouth, month to month. And I guess that plays in a little bit. You’ve gotta be a bit conservative in some regard.
\n\n\n\n[00:09:40] Paul Bearne: Yes of course. Okay, so there’s a number of scenarios that are out there. So say you are working for a small agency serving the local community, which I think is the hard end of the business. Because you have to be a Jack of all trades. you have to do whatever work the agency finds, yeah. There’s no real picking, you know, they ain’t fussy about what jobs they take on, and they’re gonna be small and bitty, and not spectacular. But you want to break out from that.
\n\n\n\nSo you’ve got things like, you could go freelance or semi freelance with the platforms. Codeable platforms, finding new work. But if you go freelance, you’ve gotta have enough money to pay for a laptop and have a space to work. You can’t do long term freelance from a coffee shop.
\n\n\n\nSo there is a little bit of a, you know, can you actually even afford to do freelance, to start up? Because a modern Mac isn’t cheap, or even a modern good laptop isn’t cheap, PC laptop. So that’s the dilemma and I understand that dilemma, But there are choices. The amount of stuff that’s remote, you know, look at a remote agency.
\n\n\n\nIf you are competent as a WordPress developer, you can be hired by a remote agency in no time. They are looking for people who are prepared to work, and they’re more interested in the attitude than your skill set. If you are, can get work done, they’ll hire you. And if you need to train up for a particular type of section of skill, to learn a bit more performance, you need to learn a bit more Gutenberg or whatever the flavor is. Yhey’ll train you. The good ones will. So you don’t need to stay where you are. There are options.
\n\n\n\n[00:11:22] Nathan Wrigley: Yeah. It’s interesting that you say that, you mentioned competence. I was kind of assuming that the competence would come before the attitude, but you’re saying it’s the other way around. Looking for people with a certain approach to work, who they can then up skill.
\n\n\n\n[00:11:33] Paul Bearne: I’ve hired people. I’ve hired students for year placements. I’ve hired people to work as colleagues. And when I do interview questions, I will start going down a technical tree somewhere. Cause I’m a geek. And I’ll keep going down a rabbit hole until they don’t know the answer. And then I explain the answer to them and I want to see a light bulb go off in their head. Oh, yes that makes sense. I understand what that was. And that’s what I’m looking for.
\n\n\n\nCause I can train that person. I can teach them. They will learn. Cause as a web developer, I will never, ever finish learning. Every time I open up a piece of code I will learn something. One of the things I do in Core is I write unit tests and so I’m looking at functions that I’ve never seen before. I learn what the Core of WordPress does, function by function. And there’s stuff in there that I, say, whoa, that’s interesting. Oh, that’s clever how they did that. So you never stop learning. And if you stop learning, especially if you stop learning in some environment, time to go.
\n\n\n\n[00:12:42] Nathan Wrigley: There must be drawbacks and there must be benefits to this whole approach. Let’s go with the good first. And that may be the time of day that you can work, the amount of money that you can earn, the location that you can put yourself in and so on. Over the course of the years that you’ve been changing things up, what have been some of the things that you’ve looked back and thought, uh, that aspect of that job was really good. And that aspect of that job was really good. Basically. What are the benefits of becoming a freelancer, I guess?
\n\n\n\n[00:13:05] Paul Bearne: You get to be your own boss and get to pick the clients and the work. You should pick the clients and the work. Don’t take everything that comes at you, because you need to pick work that you are an expertise in. Because if you are doing stuff where you are an expert, you can charge more.
\n\n\n\nThe downside is you gotta find it. It tends to be feast and famine in freelance. You’ve got too much work and then there’s no work. So you’re stressed because you can’t get the work done. And then you’re stressed because you’re looking for work, because you have nothing. So that is one of the major dilemmas of freelance. But you should earn more.
\n\n\n\nIn my talk, I talked about, if you expect your hourly salary to be say $60 an hour, talking universal currency of dollars, the freelance rate minimum is 120, 150 will be nice. That’s really what we’re aiming for. Because if you don’t charge enough, two things will happen. You will not be valued by your client, because, they’re cheap, they can’t be any good. And you’ll get crap work. I have a line in my slides, superstar prices get superstar contracts.
\n\n\n\nYou get better work if you charge more. It’s not a case of more work, better work. Better work pays better. You can have a better lifestyle because you’re not working 14 hours a day. You’re working five hours a day to get that contract done. And you’ve got three hours to do your administration and look for your next contract.
\n\n\n\n[00:14:44] Nathan Wrigley: So the flexibility’s there. You mentioned the downside of the fact that you’ve gotta create that work or somehow have it created for you. Any other downsides that you’ve figured out over the years?
\n\n\n\n[00:14:55] Paul Bearne: Freelancing can be lonely because you are one per, one person shop, effectively. You need to work at that not being a problem. So if you are in a, a reasonable metropolitan area, look for meetups, peer groups. Come to conferences. Remember, you gotta pay for them and you gotta manage the time off for that. Your clients aren’t paying you while you’re away. Your company doesn’t earn. So you gotta budget for that.
\n\n\n\n[00:15:20] Nathan Wrigley: Yeah. There may be other additional things, you know, like pension and healthcare and…
\n\n\n\n[00:15:24] Paul Bearne: You won’t have any healthcare cover. You may be able to insure yourself, but you’re taking the risk on yourself. Pensions, if you’re charging properly, you can push money into your pension, because you’ve got spare cash coming in. You’re cash rich because you’re charging properly.
\n\n\n\n[00:15:39] Nathan Wrigley: Do you need to be more self-disciplined? In other words, if you’re turning up to an agency at nine in the morning and you’re leaving at five and the work is handed out on plate and you’ve got briefings in the morning and then the briefings and blah, blah, blah. With this, you’ve gotta be a Jack of all trades a bit, but you’ve gotta be mindful that, you know, you, aren’t just sitting down having a coffee in front of the television, letting the work drift and drift and drift.
\n\n\n\n[00:16:02] Paul Bearne: Yeah, I have a friend in Canada he’s freelance business shall we say suffered? He let clients down badly. I picked a couple of clients up. He saw that I was linked to him on LinkedIn. They were chasing him and he was just got quiet on them. Awkward situation. I was able to pick some clients up because he wasn’t delivering. So you do need to have self discipline to be a freelancer.
\n\n\n\nIf you’re not, then look at the other choices. If you want to be remote, look at what are the remote agencies, and they’ll do it. If you want to be in an office, are you compared to travel into the city center? Then look for one of the big design houses in city center. If you are up for the pace. If not, maybe there’s a local agency who’s servicing the local community, that feels right for you. Because they tend to be nice and friendly and family like, yeah, they’re cozy. But the work won’t be stellarly interesting.
\n\n\n\n[00:17:00] Nathan Wrigley: I guess you’ve gotta be a bit, not just disciplined, you’ve gotta be self-motivated as well. You’ve got to be the kind of person that can incentivize themselves, because if you’re working for the man, as it were…
\n\n\n\n[00:17:10] Paul Bearne: Who will drive the direction and push you forward. Being self-aware of where your strengths are, is the most important thing you can acquire. If you can get that self-awareness and be honest to yourself about where you are, what sort of personality you are. You may need to work for somebody, in order to actually get anything done, and that’s not wrong. In fact, being honest about that is a really powerful thing, and it makes your life less stressful.
\n\n\n\nWhen I worked for corporate in multinationals, it was a doddle. Nine to five, ate in the canteen, endless coffee supply, projects took forever. Downside is our server was IIS, yeah. But when I had to go to the US I had to fly business class, you know. There are pros and cons to all environments,
\n\n\n\n[00:18:11] Nathan Wrigley: The WordPress ecosystem, obviously you are into the code, but you only have to look at the speeches that are on this weekend, and the presentations that are on to realize that code is a tiny fraction of the WordPress ecosystem. We’ve got SEO experts, and we’ve got copywriters and so on and so forth.
\n\n\n\nDid you ever stray into a different territory or have you always been code all the time and therefore sort of increasing your portfolio and your CV, if you like, one job after the other.
\n\n\n\n[00:18:35] Paul Bearne: I actually for a while ran social media for corporation. I got there because I realized that we needed to own the brand names and I stepped ahead above the parapet and said, oy, Mr. CTO, we need to own these. Shall I go and get them? Had a fun story around corporate name changing, but, I went out and registered all the, the corporate brands. And for four years, before marketed caught up with me, I was the owner and access gatekeeper to all of their social media accounts.
\n\n\n\nWe have wandered around a little bit but I am primarily a coder. That’s where my strength is. I understand by strength. That’s why I didn’t stay in social media. I’m not a writer, I’m not a content person. And so that’s part of me understanding my strengths and weaknesses.
\n\n\n\n[00:19:29] Nathan Wrigley: I kind of wonder if people who may be listening to this who figure, actually, I just wanna throw all the cards up in the air and see where they land. In other words, I just wanna try something new and everything that you’ve described so far fits that picture really nicely, you know?
\n\n\n\n[00:19:43] Paul Bearne: Yeah.
\n\n\n\n[00:19:43] Nathan Wrigley: All of this would work in, well, pretty much any industry I’m imagining.
\n\n\n\n[00:19:46] Paul Bearne: Yep, and detours are okay. Throw your ears up. You hear a sniff of something. Go knock on the door. Have a look in. Go and talk to people there. Go on interviews. I love interviews. I’d almost do it as a hobby, go on interviews. Go and see what they’re doing. And if it feels right, go and join them. If you don’t ask the question, it’s impossible for someone to say yes.
\n\n\n\nThey might have to say no, but people actually like saying yes. So go look. Take a Friday afternoon off and go for an interview somewhere. If you just chalk it up as interview practice, you are not that serious. You get to look behind the curtain a little bit. You get some reference points about what an alternative life would look like. Think about moving to the countryside. Think about moving to the city moving to another country.
\n\n\n\nYou can go and visit them. I emigrated from the UK to Canada in my fifties. I visited Canada a couple of times, found I liked it and then went through the immigration process. Uh, it took a couple of years to do that, but you get there.
\n\n\n\n[00:21:04] Nathan Wrigley: You mentioned earlier about, well you said the words feast and famine or something To that regard, and I’m just wondering, okay, so I’m not talking about the money where the money may go up and the money may I go down? I’m talking more about the pipeline of work. Have you ever struggled with that? Have you ever had periods where, there really is nothing on the horizon. What have I done?
\n\n\n\n[00:21:24] Paul Bearne: Oh totally and my solution in fact is to use Codeable. When I was freelancing, I was a member of Codeable from almost day one, very early joined there, and I’ve never done it as my full time gig. Now there are people who all the work comes through Codeable, but I’ve used it as my back fill. Whenever I’m a little bit short of work, I will go on a Codeable. I will bid for one of the contracts. Find a contract, get a contract and then do that project, because they’ve got so much work there.
\n\n\n\nYou could go and pick a contract up really easily. And you could find one that fits your skill set and your knowledge base. Yeah, so I’m an expert in sort of job boards and things like that. So I would always go and look for something in that space, because I can provide skills and knowledge in that space, and it becomes easy for me to complete the task.
\n\n\n\n[00:22:14] Nathan Wrigley: So you are kind of running those two things, not quite in parallel, but they happen concurrently. But you’ve got your work, which is the desired outcome, the stuff that you’ve put in place for yourself.
\n\n\n\n[00:22:25] Paul Bearne: I will get more income from that.
\n\n\n\n[00:22:26] Nathan Wrigley: And then the Codeable is when the gaps appear.
\n\n\n\n[00:22:29] Paul Bearne: Yeah. When the gaps backfill. If I’m short off work, I’ve got nothing to do for the end of the week I’ve got four hours. I can find a job on Codeable. Or I’ve got two days of spare capacity. Because everybody wants it done now on Codeable, brilliant. Rock up, log in. Go and see what the current list of open jobs are. Find a job that’s in your space that you can present value to. Don’t just go and do anything. And then go and fix that problem for that client.
\n\n\n\nAnd I’ve had repeating clients who’ve kept, effectively become part of my freelance stable, still through Codeable, I’ve done ongoing contracts with them. So it works really well. And the Codeable guys are really, really nice. You know they have a lovely active Slack channel. They do regular meets and training. They almost feel like a distributed agency. That hybrid space. And that everybody there is competent WordPress designer, editor content, it’s not just code at Codeable. Remember that, so there’s other skills that could, people will hire you for there.
\n\n\n\n[00:23:39] Nathan Wrigley: Would you therefore suggest that’s possibly a good place for somebody to just begin? If they’re tentative and they’re you know, they could slot a bit of that into their weekend with their regular job.
\n\n\n\n[00:23:48] Paul Bearne: They’ve got a regular nine to five job and they want to start learning, doing some freelance, it’s a really good place for them to get their feet wet, a little bit. In a very safe environment. Cause the money’s being collected by Codeable. It’s in the escrow. So you know you’re gonna get paid. If there’s a problem with the client the staff will wade in, and they’ll help you out. And if you get really, really stuck you can reach out to staff and they’ll find one of the other experts to come and help you. And if you get a problem, you could ping the Slack channel, say, how do I do this? And one of the other experts will wade in and help you. Very friendly.
\n\n\n\n[00:24:29] Nathan Wrigley: Is it difficult to differentiate yourself, to make yourself stand out? It’s just you pitching for work. Presumably on Codeable you’ve got a set number of fields that you’ve gotta fill out to demonstrate how good you are at a certain thing. And, and everybody else has got those same set of fields and…
\n\n\n\n[00:24:43] Paul Bearne: Yeah, yeah it is slightly difficult. They are quite good about saying no more than five experts should reply to a client’s inquiry. So you don’t get millions of people trying to bid for piece of work. And they don’t do the lowest price wins. They average out the price bids. Someone puts a, a thousand dollars in for a project and someone else puts in 800, the client’s gonna get told 900. They take a commission off the top, or they add a commission on top of that price and they charge the client to that. And then you get your money out in USD.
\n\n\n\n[00:25:20] Nathan Wrigley: One of the things that always attracted me, but I never managed to kind of make the leap, was this idea of being a digital nomad. So everything that you’ve just talked about, all of these rungs on the ladder of how to get work and how to manage your relationship with clients and build up your portfolio and all of that, all of that’s happened. And then you just don’t live in the same place for any great length of time. You flit about. You’ve sort of done that, you’ve moved a country. Do you know any people who do that?
\n\n\n\n[00:25:45] Paul Bearne: I have a good handful of friends who do that. Within XWP, I think have probably 20 or 30 people who are digital nomads within the company. I don’t think Codeable people tend to do that as much, because the infrastructure stuff that you need to do in addition to charging and billing and things like that, becomes difficult as you flip around the countryside and do stuff. Freelance people tend to hire local freelancers a little bit, so it tends to lock you into a country. And if you suddenly move, there’s some dynamics there.
\n\n\n\nMy recommendation, if you wanna do proper nomad work, go and talk to one of the distributed agencies, you know, Human Made, 10up, XWP, you know, that level of company. Especially if you are skilled as a WordPress developer. All of those are actively looking for people. I will personally recommend XWP. I do work there, but I’ve also worked at a few of the others.
\n\n\n\nThey’ve got it right. They’ve learned over the years how to do remote web development and manage the culture and the team so well. And it’s art, and I think they’ve nailed it because they’re based in Australia, you know, the corporate HQ is over there. So all of the European staff they’ve got here, they’ve got 60 people at this WordCamp or something. They’re all of remote. There’s only about two or three have flown all the way over for Australia. And so, because they’ve done it, it just, they just nailed it.
\n\n\n\n[00:27:22] Nathan Wrigley: Final question, did you ever, do you ever, sort of pinch yourself and reflect on how incredibly lucky you are? I say you, you, as in, all the people who have careers in the same manner that you do.
\n\n\n\n[00:27:38] Paul Bearne: Hey, I’m a guy who started as a tea boy on a building site, my first job. I now have a house on a lake with a motor boat tied up at the bottom. I would never have dreamt of that when I was a young lad. You really now in this day and age can work from anywhere. And as you know, Starlink and things like that are coming online, you really can go out into the sticks and work from anywhere.
\n\n\n\nAnywhere you can get decent internet is now fair game as a location to do web development work and design work and other services. I’m a developer, so I tend to think developer first, but there’s PMs, there’s sales, there’s HR, there’s marketing, there’s video production, there’s design, there’s content writing. All of those can be done remote.
\n\n\n\nUnless you are physically manufacturing something, and even some of that can be done remote in small batches now. Anything in this sort of digital space can be remote and often better done that way. Unless you really doing high cycle stuff, I think remote is the way to go.
\n\n\n\n[00:28:55] Nathan Wrigley: Paul Bearne, thank you for chatting to me today.
\n\n\n\n[00:28:58] Paul Bearne: My pleasure.
\nServerPress, makers of DesktopServer, a WordPress local development tool, announced it is shutting down after 12 years in business. The company emailed its customers and posted a farewell message on its website after disabling new purchases and is in the process of canceling renewals for existing subscriptions.
\n\n\n\nServerPress was founded by Steve Carnam in 2010. His leadership helped the company remain independent of large hosting companies that have scooped up WordPress development tools of all kinds. Carnam described how the market has changed, forcing ServerPress’ partners to make the difficult decision to close:
\n\n\n\n\n\n\n\n\nEarlier this year, one of the team members questioned whether or not DesktopServer v5.0 would have a viable market share. We had been so focused on building it out that throughout the development, we lost sight of constantly checking the temperature in the room. Once we started discussing this we came to the conclusion that DS5’s potential market share has changed significantly over the last 10 years. The WordPress development tool landscape has grown and diversified greatly. This has diluted DesktopServer’s overall market share. The time, effort, and costs to bring in new users to DesktopServer’s workflow would be too much overhead for ServerPress to be sustainable. While many larger, well-funded companies would be able to absorb such costs involved, a company of our position cannot.
\n
ServerPress did not communicate any plans for the future of its software products beyond the fact that they will no longer be supported. Longtime users and fans were disappointed to learn that the company is shutting down and some asked if they might consider making DesktopServer available to the public.
\n\n\n\n \n\n\n\n \n\n\n\nI asked Carnam if ServerPress is in talks with another company to sell or if they are considering making DesktopServer’s code available. He could not offer any further details but said he may have more news in the near future.
\n\n\n\n“With regards to selling, or open sourcing the code (which would be great); I’m unfortunately not at liberty to say at this time,” Carnam said.
\n\n\n\nThe small ServerPress team, which includes Stephen J Carnam, Marc Benzakein, and Gregg Franklin, have not yet announced what their next ventures will be, but they plan to support current customers for the duration of their subscriptions.
\n\n\n\n“If you are a Premium Subscriber, we will continue to support you until your subscription is up,” Carnam said. “For some, that will mean support on issues with DesktopServer v3.9.x. For others, it may mean assistance with migrating to another local development tool. We will continue to help those of you with Premium Memberships with site deployments until your subscription expires.”
\";s: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, 10 Aug 2022 01:26:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;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:83:\"WPTavern: WordCamp US 2022 Publishes Speaker Schedule, Livestream Will Be Available\";s: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=136774\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:93:\"https://wptavern.com/wordcamp-us-2022-publishes-speaker-schedule-livestream-will-be-available\";s: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:2409:\"WordCamp US (WCUS) kicks off one month from today in San Diego, CA, and organizers have published the full schedule for all sessions. The three-day event will feature three tracks with a combination of lightning talks (15 min), standard talks (45 min), and workshops (1 hr+).
\n\n\n\nThis year’s lineup is heavy on educating professionals on building with blocks. Attendees and livestream viewers can expect to learn how to customize core blocks for clients and create a custom block in 15 minutes. Speakers will also offer a glimpse into the future of designing themes for the block editor, the foundational concepts of the new era of block themes, and demonstrate how to build a block theme.
\n\n\n\nBlock themes and plugins aren’t the only things on the menu for WCUS attendees. The event will include a diverse range of topics, including WordPress and the creator economy, accessibility, multichannel e-commerce, performance, community, and creating editorial experiences.
\n\n\n\nThe sessions begin on September 9, and continue through the next day, capped off with a chat with Matt Mullenweg, who will also answer live questions from the audience. Contributor Day is scheduled for Sunday, September 11.
\n\n\n\nUnfortunately, for many hoping to attend, all 650 of the available tickets sold out within the first day. Everyone else across the world of WordPress will need to tune into the livestream, which organizers expect will be fairly popular this year due to the limited in-person tickets. The sessions in Sun track and Palm track will be live streamed, but the Surf track workshops will not. The livestream page is already published and no special tickets will be required.
\";s: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, 09 Aug 2022 21:30:02 +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:22:\"Matt: Gaiman on Tumblr\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=58841\";s: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:39:\"https://ma.tt/2022/08/gaiman-on-tumblr/\";s: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:3340:\"From a nice new Polygon article, Our favorite Neil Gaiman books, comics, and more:
\n\n\n\n\n\n\n\n\nBefore I elaborate — yes, people still use Tumblr and it’s far more popular than most people think. Neil Gaiman has been an active Tumblr user since 2011, and he still actively uses the microblogging platform to this day. This is notable, because celebrities have notoriously been bullied off of Tumblr. Yet somehow, Neil Gaiman has outlived them all, watching from the shadows of his own dashboard.
\n\n\n\nHe keeps his ask box open and answers questions from fans. He gives life and writing advice. He talks about the various adaptations of his works, giving information he is able to give and answering with a signature “wait and see” when he cannot. He plays along with dumb jokes and reblogs additions. He helps fans track down obscure lines he’s written. And as is the reality of the internet, he deals with his share of haters and trolls, but he’s always remarkably graceful toward them.
\n\n\n\nHe also reblogs posts, adding on new information, providing funny commentary, or giving helpful tips (this usually causes some surprise from people who organically stumble upon a comment from Neil Gaiman in the wild, and it’s always really amusing to see).
\n\n\n\nHe’s just a good presence on the internet, which is exceedingly rare to see these days.
\n
I’m seeing more and more people use Tumblr in this way, and it’s nice to be part of making the web a more interesting place. If you haven’t tried Tumblr recently, download the app and start with Neil’s blog as a subscription. Hat tip: Matthew Ryan.
\";s: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, 09 Aug 2022 14:05:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:100:\"Do The Woo Community: Software Licensing Solutions for WooCommerce Builders with Anh, Phil and James\";s: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=72597\";s: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://dothewoo.io/software-licensing-solutions-for-woocommerce-builders-with-anh-phil-and-james/\";s: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:498:\"A great discussion on the options for software licensing with WooCommerce, both out-of-the-box or should you roll your own custom built solution.
\n>> The post Software Licensing Solutions for WooCommerce Builders with Anh, Phil and James 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, 09 Aug 2022 10:08:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"BobWP\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}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:53:\"Post Status: Local Development Tools and 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:32:\"https://poststatus.com/?p=104119\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://poststatus.com/wordpress/features/local-development-tools-and-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:11151:\"Who is not using Local? Is it an Open Web tool? Let\'s review some “Local history” and consider where WP Engine\'s popular developer tools could be headed.
Estimated reading time: 2 minutes
\nOnce upon a time, I used XAMP. Then I used DesktopServer. I liked it and soon bought a subscription for updates and support. It was very host-agnostic and could be set up to push/pull to/from local and development sites. (In practice, this could be pretty difficult to get working.) MAMP remains a good choice for local development, but DesktopServer was probably seen as the best for WordPress until about 2019 when Local emerged. This past week DesktopServer closed its doors, noting how its independence from hosting platforms had become a significant disadvantage:
\n\n\n\n\n\n\n\n“We’re a small company that has remained independent of large hosting providers and their influential budgets; this choice had initial market share benefits but longer-term financial constraints.”
ServerPress (the parent company for DesktopServer) was typical of the classic small WordPress company and the small-scale success story associated with many WordPress businesses: well-liked and personable people involved in the WordPress community and its culture of giving back. Today, that story might be seen as ending in the era of product consolidation under big hosting platforms that are aiming at vertical integration in e-commerce, subscriptions, edutech — and the tools to build WordPress sites professionally.
\n\n\n\nThe ServerPress team also mentioned the diversification of the WordPress development tool landscape has become too complex to cope with too, but for the type of tool DesktopServer is, there is really only one solution now. It\'s a safe bet that whatever market share DesktopServer once had only three years ago went to Local — then named “Local by Flywheel” after that hosting company\'s 2016 acquihire of Clay Griffiths and Pressmatic. Pressmatic was first released that same year and cost its users $99 with no freemium pricing. Rebranded and rapidly developed for Mac, Linux, or Windows, Local was not open source but completely free — for a while.
\n\n\n\n\n\n\n\nConnectability — Anyone should be able to connect to anyone else who wants their connection. This is the foundation for community and well exemplified in tools that are easy to take for granted, like email and Open Source projects like Matrix.
The Open Web Manifesto
Next, WP Engine acquired Flywheel in 2019, and Local came along with it. Local was already a raging success, and it probably has only grown in its user base since then — if there was much remaining market share left to capture. To no one\'s surprise, a separate, subscription-based “Pro” version soon rolled out with the most useful basic features unbundled from the free version and bundled into the Pro version. Due to the negative reactions that came in, the plug was quickly pulled on Local Pro. Today, some features in Local still require additional subscription fees, but most users won\'t be crippled without them.
\n\n\n\n\n\n\n\nIf your host is able to open your books, why not ask them to open source the tools you use to build sites potentially on their platform?
The effort to monetize Local this way appears to have failed due to the developer community\'s reactions. At that point, Local had 300,000 developers using it, according to Sarah Gooding — and they strongly resisted “Pro” in force. Their resistance focused heavily on the lack of host-agnostic support for syncing files and databases.
\n\n\n\nMore specifically, I would say people who loved using Local hated how the Pro edition was packaged and designed to pull you into one particular host. If you paid to get more features, you also got more lock-in. And that hosting platform was designed completely around the concept of getting all your clients inside and handling things like billing — which is part of a paid extra, Flywheel\'s Growth Suite. In theory, Flywheel can know as much about your business as — maybe even more than — your accountant. That\'s not a service for everyone, as you might imagine, even if it was free. Trust really matters in that kind of relationship. If your host is able to open your books, why not ask them to open source the tools you use to build sites potentially on their platform?
\n\n\n\n\n\n\n\n“I feel it\'s time for a bump to this issue…. Connect is a closed aspect of Local and we don’t seem to have any sort of mechanism or ability to add to or modify it ourselves, meaning we can’t even write our own extensions to Connect for other hosts and feel this needs to be addressed in totality not just adding a new connection to appease just a handful of users.”
User dsnid3r on the Local Community Forum
Local has continued to advance. It remains widely used and is, as far as I know, unmatched in features with no direct competitors. There\'s integration with WP Engine\'s new tools for headless sites, like Atlas, along with Migrate and other tools acquired from Delicious Brains. Add Genesis — which represents WP Engine\'s “commitment to the open web,” and consider where it\'s likely headed with Full-Site Editing. (See the work Mike McAlister has been doing on FSE Studio.) You can imagine the end result being just about anything needed for WordPress site builds, from relatively simple content sites to complex applications and headless installs.
\n\n\n\n This quasi-promise was dangled for several years.\n\n\n\nLocal and newer developer tools in the WP Engine portfolio are all either free or reasonably priced freemium products today. I\'ve used and bought into almost all of them in the past. How well any of them will work with other hosting platforms down the line is the question that might have otherwise happy Local users a little worried. It\'s certainly been on my mind.
\n\n\n\nIn the past, Local\'s Connect feature (what makes it fundamentally useful) was promoted as one that would be opened to other hosts. From 2020-21 people were pointed to a form or a category in the Local Community forum to propose their preferred host(s). The form page now returns a 404.
\n\n\nDeveloper requests for this feature have never let up — not a surprise. And also the fact that it hasn\'t happened. Nevertheless, the goal of connecting to other hosts was expressed by the Local team as a possibility for years — has that door closed? All the way? For good? I imagine 300,000+ users might still have some say in that.
\n\n\n\nI\'d love it if Local and its MagicSync feature worked with any host — including SpinupWP and InstaWP. Local plus Migrate (which is host agnostic) would be terrific.
\n\n\n\nWill it happen? If it doesn\'t, can we really say Local supports 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Aug 2022 05:38: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: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: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:39:\"Post Status: Pentesting as Contributing\";s: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=104114\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"https://poststatus.com/wordpress/notes/pentesting-as-contributing/\";s: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:2305:\"Robert Rowley at Patchstack explains what I believe is the first-ever reported vulnerability in Gutenberg (the plugin, not in WordPress core) to make the National Vulnerability Database. Robert has opened an issue for discussion in the Gutenberg GitHub repo that has a good quick summary of the vulnerability. It appears to be only a theoretical vulnerability. To exploit it, an attacker would need the ability to create content in WordPress along with other conditions. As Robert explains:
\n\n\n\n\n\n\n\nGutenberg allows users to click “insert URL” and paste in a remote URL that points to an SVG file. Gutenberg then uses that value in the
Safely handling SVG via “Insert URL” (Discussion around CVE-2022-33994) #43039<img>
tag when generating the HTML. SVG files may contain javascript, which makes them a security concern similar to XSS.
There is no immediate risk of this vulnerability being exploited in the wild, so it represents a theoretical security concern that might help shape future development around SVGs in WordPress.
\n\n\n\nNotably, this theoretical vulnerability was discovered by Jitendra Patro, a software developer and WordPress user. Jitendra found the vulnerability in his own pentesting and has shared all the details on his blog. As a self-described WordPress enthusiast, Jitendra has had it as a goal to find a vulnerability in WordPress. That might seem like strange fan behavior outside open source, but it\'s actually a high compliment.
\n\n\n\nWhile closed source SaaS platforms seldom get their security issues aired widely in public, when they\'re massive like this recent one at Twitter, it\'s hard to hide.
\";s: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, 09 Aug 2022 05:30: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: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: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:85:\"WPTavern: Gutenberg 13.8 Introduces Fluid Typography Support and Revamped Quote 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=136772\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://wptavern.com/gutenberg-13-8-introduces-fluid-typography-support-and-revamped-quote-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:4354:\"Gutenberg 13.8 was released last week with some major enhancements that should delight block theme authors and users alike. The long-awaited fluid typography support landed in this version. It provides smooth scaling between smaller and larger viewports, adapting in a fluid way to varying widths.
\n\n\n\nRelease lead George Mamadashvili demonstrated how this works in a video:
\n\n\n\n\n\n\n\n“Contrast that idea with font sizes that respond to specific viewport sizes, such as those defined by media queries, but do nothing in between those sizes,” Automattic developer Ramon Dodd said in the fluid type PR.
\n\n\n\n“Theme.json already allows authors to insert their own fluid font size values. This won’t change, but this PR offers it to folks who don’t want to worry about the implementation details.”
\n\n\n\nTheme developers who want to opt into fluid typography need only set typography.fluid
to be true
in theme.json and add fluid
to each of the settings.typography.fontSizes
with min
and max
values.
Gutenberg contributors are requesting feedback from theme developers on this first iteration, as it is an experimental new feature. In the future, the feature may be configurable for users through the Global Styles UI.
\n\n\n\n“The intention is to garner feedback on the formulae and API, before we think about any editor UI and, beyond that, introducing fluidity to other properties such as spacing,” Dodd said.
\n\n\n\nTheme authors have already started updating to use the new fluid typography. Brian Gardner updated his Frost Theme to use the feature, and Rich Tabor updated his Wei and Wabi themes.
\n\n\n\n“As one of the bigger efforts towards making publishing beautifully rich pages in WordPress, fluid typography is a pretty big experience win for both the folks building with WordPress — and those consuming the content,” Tabor said in a tutorial on adding support for fluid typography in block themes.
\n\n\n\n“It’s also a part of making WordPress more powerful, while not more complicated (which we all know is quite the challenge).”
\n\n\n\nGutenberg 13.8 also includes a revamped Quote block that is capable of nesting other blocks inside. Previously, the Quote block did not allow inner blocks, but users have often requested the ability to add lists or headings inside of them.
\n\n\n\nOther user-facing improvements in 13.8 include the following:
\n\n\n\nThis update erased performance gains from previous updates in both the post and site editor but future improvements may be able to chisel the times back into the range of previous benchmarks.
\n\n\n\nCheck out the 13.8 release post for the full changelog and more details on all the enhancements and bug fixes.
\";s: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, 08 Aug 2022 20:28:15 +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: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:90:\"Gutenberg Times: Layouts and Wide Alignments in WordPress: Then, Now, and Upcoming Changes\";s: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=21803\";s: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://gutenbergtimes.com/layouts-and-wide-alignments-in-wordpress-then-now-and-upcoming-changes/\";s: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:6232:\"For most of WordPress’ history, the platform accepted a single layout width, defined by the active theme’s global $content_width
variable. Theme authors were required to handle the CSS for it and any other sizes they wanted on output.
When WordPress 5.0 launched the block editor, it introduced the concept of wide and full alignments (technically, they are “widths” or “sizes,” but let’s jump past this oddity of pigeon-holing sizing into the existing alignment system). Themes could add support via add_theme_support( \'align-wide\' )
to allow users to select these additional widths for blocks, which would expand beyond the content area:
The solution was a groundbreaking first step. However, once again, theme authors were mostly left to figure out how this worked on their own. The flagship Twenty Twenty-One theme had dozens of lines of CSS to cover various scenarios to get it to work. WordPress had yet to include a standardized layout system at that point.
\n\n\n\nFast forward to the WordPress 5.9 release in early 2022. The update added a global settings and styles feature, which included a layout system for handling wide sizes. Theme authors merely needed to define settings.layout.contentSize
and settings.layout.wideSize
in a theme.json
file, as shown in the following code snippet:
\n\n\nCode language: JSON / JSON with Comments (json){\n \"version\": 2,\n \"settings\": {\n \"layout\": {\n \"contentSize\": \"38rem\",\n \"wideSize\": \"64rem\"\n }\n }\n}\n
This meant that developers could remove most (all in some cases) of their custom CSS around content, wide, and full-width layouts. Compared to the previous default theme, Twenty Twenty-Two only had a handful of CSS workarounds for issues related to full-width alignments and root-level padding.
\n\n\n\nThe new layout system came with new “rules” for aligning nested children of container-type blocks, such as Group. And, WordPress would only show the wide and full options if they were allowed. This caused some compatibility issues for classic theme adoption of theme.json
, which we will get to. However, overall the system was finally coming together.
Users had a standard system that was cross-theme compatible (at least those with theme.json
support), and theme authors only had to plug in a few configuration values.
The introduction of WordPress’ built-in layout system made for a lot less hassle coping with the multitude of page designs that users might attempt. It gave theme authors a much-needed standard that core could build atop in the future. However, the new system broke compatibility with some scenarios in classic themes.
\n\n\n\nFor classic theme authors who adopted theme.json
, they began noticing two primary issues:
theme.json
-based system, child blocks fill the width of their parent.The default user experience changed and broke compatibility for classic themes that adopted theme.json
after the WordPress 5.9 release. The mere existence of this file moves the user to the new layout system, regardless of whether settings.layout
is explicitly set. Developers have no mechanism for opting out of it. This makes it a blocker for gradually adopting FSE components.
For this reason, I recommend classic theme authors temporarily postpone adopting theme.json
if they have an existing userbase. For new projects, adding support should be a non-issue.
There is good news in store. First, I (along with others) updated the layout documentation to provide a warning in the Theme Handbook about this issue.
\n\n\n\nHowever, a more permanent fix may be on the way. There is an open pull request to create a new content width layout type. It would also make this the default setting for newly-created Group blocks, returning the user experience to the original behavior. There is no set-in-stone deadline for this, but I hope it lands in WordPress 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:\"Sun, 07 Aug 2022 06:05: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:\"Justin Tadlock\";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:113:\"Gutenberg Times: Gutenberg Changelog #71 – Gutenberg 13.8, Fluid Typography, updates to the Block API and more\";s: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=21815\";s: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://gutenbergtimes.com/podcast/gutenberg-changelog-71-fluid-typography-block-api/\";s: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:64661:\"Grzegorz Ziolkowski subbed for Mary Job as co-host with Birgit Pauli-Haack. They discuss Gutenberg 13.8, Fluid Typography, updates to Block APIs and WordPress 6.1 Planning.
\n\n\n\n\n\n\n\nShow Notes
\n\n\n\nWordPress 6.1 Planning Roundup v2
\n\n\n\nProposal: A new kind of default theme
\n\n\n\nProposal: Moving Core block styling to JSON
\n\n\n\nPR in 13.5 Prototype: merge block CSS with theme.json styles
\n\n\n\nDesign Exploration: Encourage editor configuration during on-boarding
\n\n\n\nGiving FSE a More User Friendly Name
\n\n\n\nFSE Program Category Customization Summary
\n\n\n\nWhat’s new in Gutenberg 13.8? (3 August)
\n\n\n\nBlock supports: Add fluid typography
\n\n\n\nNew examples for Block Types Data (core/blocks package
\n\n\n\nBlocks: Further improve assets handling for blocks
\n\n\n\n\n\n\n\nInjecting dynamic data to block HTML markup in PHP
\n\n\n\nUpdated: Tracking: Add a Style Engine to manage rendering block styles
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nBirgit Pauli-Haack: Well, hello and welcome to our 71st episode of the Gutenberg Changelog. In today’s episode, we’ll talk about Gutenberg 13.8 release updates to the block APIs, WordPress 6.1 planning, giving FSE a new name and so much more. I am Birgit Pauli-Haack, curator at the Gutenberg Times and WordPress developer advocate, and today my cohost is Grzegorz Ziolkowski, JavaScript developer and WebPress core contributor. Thank you so much, Grzegorz for subbing for Mary today. Mary sends her regards. She’s really inundated with work, which is good at one point, but we miss her today, and she will be again on the next episode. So how are you, Grzegorz? Thanks for joining us.
\n\n\n\nGrzegorz Ziolkowski: Hello, Birgit. Hello, dear listeners. I’m great. So happy to join you again and talk about everything related to Gutenberg, which is always fun.
\n\n\n\nBirgit Pauli-Haack: Yeah, and we are so glad to have you. You will bring… We will talk about some block APIs because there are big changes coming. Can you let us in or should we wait ’til we get through the release?
\n\n\n\nGrzegorz Ziolkowski: Oh yeah. Like there are a lot of things going on. We are trying to better organize the roadmap for more technical aspects of Gutenberg. So that was one of the talking points during WordCamp Europe. Many core contributors brought that. It’s like the roadmap for user facing features is pretty well defined. You have a lot of references for that, but sometimes, like with so many open issues, it’s really hard to find what’s the most important bits on the technical level and how we can improve building blocks for core and for all extenders, how we can better integrate customizing blocks to work better with blog patterns and with teams in general. So this is what we are trying address with that and we can cover that at the end of the show.
\n\n\n\nBirgit Pauli-Haack: Yeah. And just wanted to tease it out so people stay on beyond the Gutenberg Changelog for the last Plugin release.
\n\n\n\nBut before we head into that, there are a few things that happen on the team. One is the WordPress 6.1 planning is done. We have a preliminary schedule and the post also contains a full slate of release leads. So the Feature-Freeze and Beta I for 6.1 is September 20th, and that brings us with Gutenberg up to the version 14.1 if the team keeps the two-week release cycle. There’s no reason why it wouldn’t. And then a release Candidate I would be October 11. That’s when all the Field Guide is going to be published and now more any string, it’s also hard string freeze so that the translators are able to kind of continue the work. And then the final release is November 1st. That moved from the preliminary schedule that was published four weeks ago or something like that, but with the comments from that planning, it didn’t have a third Beta release, but that is now on the schedule and that pushed the final release date a week into November 1st.
\n\n\n\nThe release squad is release leaders, Matt Mullenweg with the release candidate coordinators again with Hector Prieto and Jonathan Derosia, two veterans leading the release, coordinate the release. And then core-tech co-leads, sorry, is Mike Schroeder, David Bombard and Jeff Paul. And editor tech co-leads, Michael Chaplinsky and Bernie Reider. And then core triage co-leads is Jean-Baptiste Audras and Ahmad Jayon. And editor triage co-leads are Nick Diego and Anne McCarthy. Documentation co-leads is Milana Kapp and Femi Pressid, and yours truly again. So now I’m not a rookie anymore and it’s good to do two releases in a row, because first you learn a lot and the second one you can actually really contribute and not be a pain in the whatnot with all the questions. Marketing and communications lead is Jonathan Pantanni. Test lead is Brian Alexander and Ana Lakisik, and design lead is Rich Tabor. So this is a great squad, again, for the 6.1 release. That’s the third release in 2022.
\n\n\n\nGrzegorz Ziolkowski: Yeah, I think the squad is excellent. We have a lot of people that were involved in the previous release and also in the release from many months ago, so that’s always a good mix of people. And I guess you did excellent in the 6.0, Birgit, so you are too humble.
\n\n\n\nBirgit Pauli-Haack: Well, we also have something new on the release lead. Femi Pressid, she’s new to the release cycle, but she has been working on the Gutenberg end user documentation for about a year now and has done an excellent job keeping up with all of it. And now being on the Release co-lead for documentation means the end user documentation gets a lot more weight and she also can start earlier to triage what will be in the Release and what is user facing to update the documentation. If it’s not before the release, then it’s very close after the Release. So we give her all the support that she can get and if you, dear listeners, are inclined to do some writing and want to do some updates on the end user documentation, because you do it for your clients anyway, or you are, you always wanted to start contributing to the documentation team. Don’t hesitate to come and either ping me or ping Femi or Milana that you want to contribute. And believe me, we will put you to work, so you can definitely make a great difference on the documentation team for that.
\n\n\n\nGrzegorz Ziolkowski: Yes. It’s also the last release of the year, which means that there should be a new default team. I don’t know how it’s going to be handled this year, because with block teams, there are so many options. You can use block team variations or type variations. There’s many options like block patterns. So I have no idea how the design team is go going to sort that out. I know that Rich Tabor as a team lead, that’s an excellent choice. He has a lot of teams in the repository. I mean, in the directory, so you can check them out, look buy out or name and see what he’s capable of. So that’s going to be very interesting. And I also am really excited that the blog editor triage leads, this idea is continued. It was a last minute edition for 6.0 and Nick Diego, he did excellent job helping Core editor Dech Letes with picking the right back fixes and improvements, enhancements, and stuff like that during the holiday. So now having him and Anne McCarty that should be a dream team to work with.
\n\n\n\nBirgit Pauli-Haack: Yeah. I totally agree with that. He and George Mamadashvili, who also was release lead for this latest Gutenberg Plugin release, they do actually weekly triage meetings now in the Core editor channel and they started that, I think about a month ago. And this has been quite helpful because they sometimes close issues or can push some of the PRs further and see if it gets to a solution quicker. We also have, thank you for pointing out the proposal or mentioning the new default theme. If you missed that, there is a proposal for a new kind of default theme. What was that name? Man, Jenny Ritter. She posted that about two weeks ago and it’s more like it’s going to be a base theme, but then it’s a call for the community to send in style variations as well as for that theme that then totally can change how a site looks, even if it doesn’t change the theme.
\n\n\n\nSo I think it’s an excellent new approach using all the different tools that are available, especially the style variations. I find that very… And Rich Tabor also has, he’s not on the team for the default team, but he’s definitely raised his hand to say, “Well, I will contribute some style variation for the default theme.” And please, we will share the post in the show notes, of course so you can share your feedback. That’s one thing, but also you can be updated on the next version of this, because the next iteration will be that there will be a basic theme and then how to submit style variations that hasn’t been yet finalized. How the process going to work, it’s always with the new things. You need to find the right process to make it work, but Jenny Ritter and the design team and the theme team are working closely together to make this a great new default theme experience.
\n\n\n\nGrzegorz Ziolkowski: Yeah. So we have one more news to share. So because the date for the WordPress 6.1 is so far ahead, we are also preparing a bug fix release for WordPress major version, which is going to be 6.0.2. And we still didn’t decide on the exact dates, but we are shooting at the end of month and you should expect some official announcements soon, probably after The core chat that happens every Wednesday.
\n\n\n\nBirgit Pauli-Haack: Yeah, that is good. That’s good. There are a few bug fixes that came out and having them fixed sooner rather than later is really good. Thanks for pointing that out, Grzegorz. We also have a link to the design explorations that James Koster did and he published it on the Design Team post, and that is a new way to offer editor configuration to new people who encounter the blog editor for the first time to select on their, the placement of their toolbar and has some little jiffs in there that actually shows the user, what does it mean? One is the toolbar, the other one, and then the document tool being on top, and then the block toolbar, as well as the accessibility. Like you want to see only the icons or also the text for the buttons in the toolbar and similar things.
\n\n\n\nSo it’s very interesting. It makes the model, the grading model a little larger, but it actually conveys so much more information and it’s so much more helpful I find than the current user experience. So take a look at it. Right now, these are explorations. There’s nothing decided on yet, but that’s the right moment to offer your opinions and offer suggestions and ideas and be part of the process. So we will share that link in the show notes, of course, and it’s called “Design exploration, encourage editor configuration during onboarding.” So Ben Dwyer just merged a prototype to merge blog CSS with the theme JSON Styles. And that definitely is something that theme developers should take a look at to see if that works with how they want to approach it or with their themes. It’s in combination with a new post that says, “Moving core blog styling to JSON.” And that’s certainly something that is ahead of 6.1 to figure out, to make the process of, to give more customization optimizations options through the global styles UI, and that themes can override block JSON styles as well.
\n\n\n\nSo it’s going to be interesting to see how that is received by the design and theme developers, as well as the Plug-in developers. Do you have any thoughts on that?
\n\n\n\nGrzegorz Ziolkowski: Yeah, so like we are training in the very interesting situation because, so far team could have opinions about styles, like default styles for blogs, and that’s like something that can scale well, but sometimes, because we have this interface that unifies how you deal with so many aspects of how blogs look like. So you can change spacing, padding, fonts, and all the types, all that everything created to typography. You can change background color, foreground color, links, and so many things that we constantly see new things arriving. And that’s like in the past, you would customize that for the individual blogs using CSS. But now the same styles can be replaced by the same construct that exists for themes in the theme JSON file. So like the idea is how to leverage that also on the blog level.
\n\n\n\nAnd it brings a lot of power because you can use one language to change everything, but then it creates a lot of questions, like what comes first? Which one should be applied on top of another one? And there’s also a similar exploration for Plugins. So there’s Plugins that change a lot of things. For instance, WooCommerce comes and they can have opinions about styles for blocks as well. So they also trying to find a way using the same representation in the JSON file. So you could combine them together. And it’s definitely very powerful. The benefit of using this common language to express styles is that you can use all type of tools that we see popping up in the community. There is a few tools that allow you to generate those theme JSON files.
\n\n\n\nSo that could be extended for in the future for block JSON. And for maybe, I don’t know, what’s going to be for Plugins, maybe a theme JSON, but maybe Plugin JSON. Time will tell, but it’s about having programmatic control over all those things and having a coherent way to change the same aspects of the front, on the front end how everything looks like. And some people describe that this is how the design system gets introduced to WordPress which is like a good change from the design perspective. But it’s a very complex to come up with a good approach. So that’s why we have this proposal, the call for feedback. So people can share their ideas and their concerns, how that might evolve, how that might impact their projects and products and so on.
\n\n\n\nBirgit Pauli-Haack: Excellent. Yeah, it’s going to be… It’s some interesting times, especially as you said, kind of the roadmap for, at the beginning for UI and for the no code users is pretty much well spelled out and there’s a vision, but now that it’s almost done with the underlying architecture, there are now the things that need to be happening for extenders, for plugin developers, theme developers. And because everything is now at least understood how it’s in place, there are still a few things like the style engine and this, the common language of how blogs are styled that are coming together. And yeah, these are exciting times. I love it.
\n\n\n\nFor the community, so Josepha Haden Chomphosy, executive director of the WordPress open source project has posted a post with a headline, “Giving FSE a more user friendly name.” And the TLDR for it is that the terms full site editing or full site editor also abbreviated FSE were actually just a code name internally.
\n\n\n\nAnd they were developed to easily refer to all the collection of features under, that are for site editing and global styles and that. And I integrate in the WordPress experience, but how can we best update the wording to be more user friendly? Because it doesn’t tell the user anything. And naming is really hard. We see that all the time. There are few issues that she has with it, or sees with it that it’s already possible to edit every part on WordPress using code. So the term for that editing doesn’t differentiate between the phases of the project and does not show the new capabilities of the CMS per se. And it also implies the use of blocks, but for new users, there’s no reason for them to expect anything else. So the term isn’t descriptive enough for a user that comes to WordPress, what does it do?
\n\n\n\nAnd then she goes in a little bit more detail and asked then a few questions for you. We’ve referred to it this way for a long time is one of the reasons how can we tackle renaming it together? And then it’s in the code base. So how will we make sure people who aren’t regular contributors see that there will be a change and repeating in line? What other context do you think we need to be aware to look at when we refer to the collective work in the future? So this is one of the more discussed posts. But your opinion is definitely worth bringing in. There are 88 replies already, but I don’t think that a lot of people have seen that yet. So if you haven’t read it yet, and haven’t thought about that, it’s definitely worth your attention, unless you say, “Okay, well, I don’t know how, what they call it. I don’t care.”
\n\n\n\nSo, but yeah, most of the time, if you are an educator, if you are a theme developer, you have to talk to your users and just explain what it is. This is what we call full set editing now. And there might be a better way and there should be a better way, I think. So that’s one of the pieces I have for you and the other one… So there was a call for testing out from the FSE program, the 15th in a row. And Anne had a deadline of August 1st for comments. I think it ran for four weeks and she now published the summary post for it. And yeah, it was amazing. There were two translations again for the Japanese community, as well as for the Italian community. So there were other voices heard while speaking of translation. Yeah, full site editing doesn’t translate well into a lot of languages.
\n\n\n\nSo there was also a concern. And then she also used for the first time for a test release, a feature or a service called Insta WP, which lets her set up a site and give you a link to it, so you can spin up your own test website without having to do a local install or any of that. So you could use it for seven days to go through the test. That was really interesting. So the high level summary is there’s still a lot of confusion about certain things, especially it was heavy on the Query Loop, but it was also when you create a new template, you get an empty view. Is there a way to make it replicate some of the footers and headers that is on other templates also for a new one. So they know, okay, this is what I have on every website and something like that.
\n\n\n\nGrzegorz Ziolkowski: So to clarify, what was the text as exactly. I read that you were asked to go to the editor, like full site editor, just to make a pun of the name and then go to the toolbar and probably create a new template and pick a category, like version of the template and then like go and like use Query Loop to display all the posts from that category and provide everything else that you want to see on this type of pages. Right?
\n\n\n\nBirgit Pauli-Haack: Right. Right. And that was one task. And the other task was to create new posts, to explore patterns that were already available on the site. That’s why the Insta WP was an important, that a pattern for a new event announcement and a pattern for an event recap, meaning there were also additional information that we’re supposed to be in there in the pattern and how it worked.
\n\n\n\nGrzegorz Ziolkowski: Yeah. But still, this is very exciting that you can go and create a template using your browser without having any access to the server and like, you know it’s just like, it’s a so huge change for site owners.
\n\n\n\nBirgit Pauli-Haack: Yes. And up until those changes were in the block editor, it was always more like a catch up for what has been around in page builders for maybe a decade or something like, well, no, no six or seven years apart, that was not in core. But now with this new template editor, this is something that you couldn’t do before without code. That you have an author template and the in 13.7. There were a whole range of new templates available now. And in this version we have, yet another one and that is probably the conclusion of, how many different template types can we create. Yeah, I’m really excited about that. That’s a total new thing for site owners that don’t need any developer to not only have a new template, but also can create the pattern creation that is still the missing link.
\n\n\n\nBut you can do a combination of having for every new user on your site that edits, you could as a developer, you can actually have patterns for a certain blog type or post type show up in the create new methods. So that is also something that is highly underused right now. I think those things all come together with time and we need to really have more educational posts around that, like the call for testing. That’s the best way to learn what the new features are when you follow those calls for testing, because they’re very detailed and very distinct and make sure that you can accomplish that, but you learn so much. All right. Yeah, that brings us to what’s released?
\n\n\n\nGrzegorz Ziolkowski: I mean, finally, there is a lot of cover that’s happening in the community. That’s great.
\n\n\n\nBirgit Pauli-Haack: Yeah. So Gutenberg 13.8, it was released. George Mamadashvili, was a release lead and he noted that we are almost really 3 releases away from 6.1. I did some calculations and it seems that 14.1 will be the last Plugin release that will make it into 6.1. And that is supposed to come out on September 17, something like that. Yeah. So 13.8 comes with fluid typography, accessibility improvements, revamped quote blog template parts, UX enhancements. And it’s also of course always full of bug fixes and code quality improvements. So let’s take it from the top.
\n\n\n\nGrzegorz Ziolkowski: Yeah. So the flow typographic is a huge change. It’s something that probably a lot of designers expected to see and, it’s something that still isn’t exposed in the UI. So we need to wait for that. It’s a pretty common approach that we seen in the past. And we talk about the other future that our first available through code and then the UI comes after, after it’s properly tested. So maybe Birgit will tell more about what’s exciting about this feature.
\n\n\n\nBirgit Pauli-Haack: Well, the fluid topography, what that does is that you can, as a theme developer set a minimum size of your font sizes for the smaller screen and the maximum size for the big, big, big screens. And then what the theme does is, or WordPress does is kind of scales from the small to the screen, seamlessly the typography. So the size of the letters, the spacing of the letters, and also how the paragraphs kind of form. So there is no set viewpoint or view port for the mobile version or the tablet version. It is seamless. And that is kind of the approach that the Gutenberg developers have taken to more implement intrinsic design rather than the certain viewpoints that are along the way, which other page builders have. It’s now available in theme JSON and the fourth theme JSON. So you need to, can set it in the theme JSON file and then how to implement that is in the PR that’s 39529.
\n\n\n\nAnd I know there is a certain, a post in the works to flash that out a bit for the theme developers and it’s coming out in the next week or two, but in the PR which we will separately share in the show notes, you are able to set the settings dot typography dot font sizes, and then give it presets for your theme. You set the fluid field to true, and then you have the minimum size and the maximum size, or you can name them. And your theme then is able to, and WordPress will create the variables for it, for the units. It seems that the best use would be to use the REM units for the relative size propagation. Right now the maximum view port is 1600 pixels. And yeah, I don’t know if that’s right, that it says here 768 for the smaller size.
\n\n\n\nSo it will not go all the way down to the mobile, but this is the first version. So it’s not going to be perfect and it’s going to be, it’s really going to be rough. So the developers really need you to test it out and give some feedback on it, how your implementation is either stifled or what are the blockers? What does work, what does not work. How you would kind of proceed with that, because as Grzegorz said, the first version is just to get it out in front of the people to be testing and then iterate on the implementation with the feedback from the community.
\n\n\n\nGrzegorz Ziolkowski: Yeah. Although I must say that all the demos I’ve seen so far look pretty great. Maybe it isn’t like so rough, as you mentioned, maybe it’s like good enough for some themes to enable that and see how it plays in practice.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah. I certainly have a “it’s good enough kind of approach to many, many things.” But I know that separates me from the professional theme developers and designers. They want it to be pixel perfect. And they want it to be very granular, have flexibility, very granular form. So I think I would not be a good judge of the feature because I also don’t make a living selling themes. So I really would love to see what Anna Sekoda for instance does with it, or what Ellen Bauer who is also, has been a theme developer since the beginning of blocks and FSE. And they have already published quite a few like Rich Tabor, quite a few themes in the theme directory or also on the WooCommerce marketplace. So that is definitely something they will test it out and figure out what’s needs to be done.
\n\n\n\nSo other enhancements that we have in the 13.8 release is that the social icon block has a variation now or an icon for the WhatsApp app, has a WhatsApp icon. So you can also connect your profile, your WhatsApp profile on your website. What I also am quite excited about is actually talking about theme JSON, that quite a few things in this release that are concerning the theme JSON on file. This one is also support for heading and caption elements in the theme JSON schema, meaning that you can target with your CSS directly, the HTML elements without having to create another class name or something with your styling. One is also a little minor. That’s the merge of comments and post comments blocks. That’s a big deal, but it’s also kind of the merging of the old thing with a new thing. So when you use the old comments block and now use the new post comments block, it will update your comments.
\n\n\n\nGrzegorz Ziolkowski: Yeah. It’s mostly before the themes that use the old block. So right now, if you use that, it’ll migrate to the new one, but it will still retain the old behavior. And you will be able to switch to the version with blocks, which like within the blocks, which is like more powerful in terms of all the types of customization that users can do inside the editor in WordPress. Whereas the old one, it depends on templates that are PHP based. And in like by fault, it uses what every WordPress instance provides that can be written by teams, but every site could also provide their own. But you need to code that so that the new version is what we would prefer, because with the block concept, you can do more.
\n\n\n\nBirgit Pauli-Haack: Yeah. So another great feature is now added to the image block and that is border support for color, width and style. And I think that’s the last piece missing to make it really flexible what you do with themes. And George wrote that he’s very curious to see what the creative folks at the museum for block art can accomplish with that, because now you can actually change the border width and differently from the right and left on top and bottom, and then change the color of each. And it’s very flexible and you also can change the radius of the border. So you have round a corner on two sides and square corners on the other side. And it’s just really amazing what you can do with it when you have border controls. So yeah, definitely check it out and see what you want to do with it. The block museum for block art is definitely open for submissions. And I will share in the show notes, how you can submit your creations and see what you can come up with.
\n\n\n\nGrzegorz Ziolkowski: Yeah, there were also a couple of changes to template parts, which makes them even more powerful. The one thing that I like a lot is that right now it was quite difficult to explore existing template parts in the inserter because they were hidden and you had to insert the template part and you’d, once the block was in the editor canvas you had two options. One was, set existing template part, the other one, you could create it from the scratch. So right now all the existing template parts are also exposing the inserter, which is like a shortcut for everyone. It’s easier to find them, which is a good change. It also aligns more with how usable blocks work, which are in their own tab in this inserter here. Like those template parts, as far as I remember, there are inside blocks, which is like, might be a little bit confusing, so maybe that’s something that could be iterated full there. However, if you search, you don’t care so much and you will be able to see them. So I find it like a great step in their right direction.
\n\n\n\nBirgit Pauli-Haack: Yeah, definitely. Yeah, it’s interesting how people explore interfaces completely differently. So having multiple ways to do the same thing, really exposes more users to the intuition on how to change things and streamlining the process, like these shortcuts is definitely a way to go. Yay. There is a minor change to the color palette. It now displays of checkout preview background and the value is transparent. So you couldn’t see from the color settings, if there is a transparent color or transparent background on a group blog or on a cover block, now you can see it through the checkout preview. That’s definitely a quality of life kind of change that your brain really can absorb that and see that there and give you the signal. There’s a transparent value there. You can now also, and that was missing for a while, you could do the layout content size settings through the theme JSON, but the user didn’t have any way to correct that or change that. Now a site owner has. You can now do it through the interface that you can set the content with as well as the wide width and also the padding for, for those blocks. So that is really for the layout of the template, so that has…
\n\n\n\nGrzegorz Ziolkowski: There’s one change that I’m pretty excited about. It’s about the placement of the inline toolbar when using feature text tools like bold italic underlying. So at the moment, like in the past, like in most cases you would see that in the block toolbar that could be either dock to the header or on the top of your block, especially when you write a longer paragraph is like is far away when you want to use a mouse to interact with that. So now you can change the setting and that will be like a floating toolbar that’s always next to the text that you have highlighted, which is very similar to what you will see on mobile devices or tablets when you interact with the apps that come with the system, like iOS or Android. So I like that one. And I’m hoping that people find useful as well.
\n\n\n\nBirgit Pauli-Haack: Yeah. I really like that. I saw that first in medium, when they came out that they had this, you highlight a text and then they offered you a formatting toolbar. And I really loved that. And I was missing that in Gutenberg forever, obviously. But I also tested the distraction free writing tool that Rich Tabor and Jeffrey Carandang created that was the iceberg editor. And they actually implemented that as well. And I’m glad that it now came to core and that we have the first iteration of that. And I’m eager to test it out and use it.
\n\n\n\nGrzegorz Ziolkowski: Yeah. Also from the experience, I know it’s a bit tricky to use that feature, especially when you are using mobile devices because their system provides their own toolbar. So if in that context, it might be very disruptive, because you don’t know whether that toolbar will come from the system or from the block editor. So, not all features might be available if you see the system one. So, it’s something that needs to still to be tested, but because it’s a setting you can for the mobile, you can disable that. And for the browsers, you can have it enabled. So I’m sure that we all see some improvements on that front.
\n\n\n\nBirgit Pauli-Haack: Excellent, yes. And a whole new, so the quote has received a total revamp, so to speak the quote block, now you can use it and it’s coming out of experimentation with this 13.8 version. So it gets quite a few more testing in before it actually will come to 6.1. Now you can use nested blocks with your quote block. So you could have a quote from someone and add an image to it, or have multiple paragraphs in there, or have a list in a quote block. Often, you couldn’t do a list and make it a quote. So now you can, and I’m really happy that it made it into this version.
\n\n\n\nGrzegorz Ziolkowski: Yeah, it’s very powerful, especially for developers who use GitHub and they know what you can do using markdown that you often quote something which includes code examples, images, videos, and so on. So like this is like bringing the same functionality into the block ward. So I’m really excited about that one.
\n\n\n\nBirgit Pauli-Haack: Yeah, especially when you have code quotes and tutorials also. Yeah, it definitely helps to have that, also have the citation with it.
\n\n\n\nGrzegorz Ziolkowski: And also there’s ongoing work to bring the same set of features for the list block, which is another level of complexity. So now you would be able to have a quote that has a list that has inside that nester blocks, you can have paragraphs headings and code examples, even in list, which you know.
\n\n\n\nBirgit Pauli-Haack: Icon, emojis. Emojis in a list block. Yes. Nice.
\n\n\n\nGrzegorz Ziolkowski: These are much more complex because they’re like, at least are not two dimensional and it’s not only like the nest of blocks can be on one level, but you can have, the list itself can have a nest at least. So it’s like the interactions between those internal, nested blocks are much more complex. I don’t know if that’s going to be ready for 6.1, but it’s definitely in works and might happen.
\n\n\n\nBirgit Pauli-Haack: And if you are very interested in that list version two, list block version two is still in experiments. So you need to enable it through the experiment settings before you can test it out in your local or test site. I wouldn’t do it in production, but yeah, for testing, it’s definitely, you need to enable it in the experiment settings. Yeah, I’m really looking forward to that, especially because you’re not, so when you change from a bullet list to an ordered list, you change the whole mockup in it. So what happens then? There are quite some complexities there. We have seen that in discussions also with the table of contents block that comes out of the gate with a numbered list. But many people don’t like the numbered list and there is no way to change it over to a bulleted list. Say maybe the experiences that come with the list development with the list block version two can actually be replicated for other great blocks that are out there. So what else is in there? So anything that stood out for you?
\n\n\n\nGrzegorz Ziolkowski: Yeah, I think we covered the most important aspects, like enhancements and new features. That’s quite a huge list. There are some accessibility improvements as usual. It’s always great to see contributors focus on that area, which is like never good enough because the interactions in the editor are so complex. That is very hard to do it right on field first run.
\n\n\n\nBirgit Pauli-Haack: Yeah. There have been changes to the border controls, which are trigger quite some creativity. So getting that right for accessibility, with labeling and tool tips and field sets and legends that is now available in the Plugin. And then there were some fixes for descriptions or for some other labeling and semantics in the paragraph block. And then also to, they also replace some diff elements, clickable diff elements with actually buttons because that’s a better experience for all users.
\n\n\n\nGrzegorz Ziolkowski: There’s also, like in that, related to that, there’s a very interesting change now. When you are focused on the group block, you can use, enter key to create a new empty paragraph just after the group block. So before you would just like, it wouldn’t like, nothing would happen. So you would have to use maybe the drop down menu from the toolbar for the block to find insert a block after the group, or maybe like find some other way, like in between line easier there with mouse. Now it’s much more convenient just to press enter.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah, definitely. I always appreciated that with, for instance, the list block where you can enter, enter, and then you’re out of the list block and can start. But getting that to more than one blocks is really good. There are also some big change, not big, but yeah good changes in the documentation of things, especially, having many more examples in the core blocks, a data API on how you use it. And some of the examples are also with great comments, so you can make more sense out of things. I think that Ryan Welcher does the great work there and he definitely can use some help. He is determined to have for every function call or store call or something like that. He has an example that is ready to copy paste into some other code, or at least with adaptions. The docs for the block JSON are also updated because it was missing the block variations. And that has been added to the JSON schema definition so now.
\n\n\n\nNow you can point to the block variations as well as to the styles with your block metadata. And then the data module had some missing references and that have been updated. So you can actually find them in the documentation now.
\n\n\n\nAnd again, theme JSON got some clarifications on the null true and false values for the block gap setting. That was a little confusing before. So it’s now straight net, as I would say.
\n\n\n\nGrzegorz Ziolkowski: Yeah, it’s ongoing effort to improve developer documentation. There is a lot of public APIs that are documented, but they miss examples. And I think that the work that Ryan Welcher is shepherding is so important to get it because like having code examples makes it so much easier to actually use the code.
\n\n\n\nBirgit Pauli-Haack: Right. Yeah, totally agree with that. So I think we are at the end of the Changelog for the 13.8 Plugin release that happened this week on our third.
\n\n\n\nAnd now we come to the section, what’s an active development and what’s discussed. And before we head into the block API issues, I think there was one thing that I wanted to point out and that is that Ramon published an update also on the style engine tracking issue. So we will definitely point to that in the show notes, but he has, so the style engine is at an experimentation, right or is in experimentation right now. So, but it has a phase one which is block supports and building the foundation. And then the phase two is the global styles consolidation, reducing style tags. And in both, he has some updates on some of the issues. So make sure if you’re theme developer, you’re definitely interested in what’s coming down with the style engine development.
\n\n\n\nGrzegorz Ziolkowski: Yeah, it’s very related to what we are going to cover now, which is block API. So style engine is in fact, subset of that, it’s related to how class names and style attributes are added to the block HTML output. And the idea we style engine is that eventually we would have everything generated on the server only on the front end, so that means that only styles and class names would be included on the page when the given block is there, which means an excellent reduction of unused CSS, which a lot of websites struggle with today and the progress on that is really promising. And I hope that in a few months we will see all the benefits of the work happening on that front.
\n\n\n\nBirgit Pauli-Haack: All right. So you revamped some of the… You created a tracking issue for the block API that had quite a few chapters on it and does seem to only have 35 tasks and there are other tracking issues with much longer, but it covers issues that are around block assets, block registration, block attributes, variations, block supports, and then the inserting and moving blocks and block editing, dynamic block manipulation, server side rendering component and of course documentation. So what stands out for you on this? What is the big effort here?
\n\n\n\nGrzegorz Ziolkowski: So first of all, we have over 4,000 issues open in the Gutenberg repository. You know it’s very hard to triage all of them, go back and see what’s there. So the effort that I made together with Matias just was, can we identify the most common, occurring issue that people rise and they want to see improved and that we wanted to collect items that make the biggest impact in the short term. And it’s not like the list is close. We will be constantly revisiting whether the list makes sense. We will be adding new features based on the feedback from people in general. It’s just a way for us to bring better focus on what we can work on in the upcoming WordPress releases and Gutenberg releases and, like it’s dividing the sections, just like it tries to follow how the milestones for how the WordPress, the block editors and the full site editing should evolve.
\n\n\n\nIt’s always like milestone for template parts, milestone for global styles and so on. We try to mirror the same structure. And for now it’s because issues that we’ve been talking about, some of them for years now, and there were never clear focus to work on them. And we are trying to change that because we see that stuff like block validation and block deportation comes back every now and then, this people often complain about. So we just want to make sure that there is single place that people can go and see, “Okay, is that on the roadmap? Is that being tracked? How can I get involved and help move that forward?” So instead of saying that, find the issue on GitHub throughout all those 4,000 issues. Like there’s a single place. It’s pinned when you go to the Gutenberg repository and you go to issues like on the top of the page, there are three pinned issues.
\n\n\n\nIt’s one of them now. So it’s easy to find for people if they know about that thing. And so it’s easier to discover and this is also a good way to see what’s actually being worked on because if you go to this issue and the tracking number is 41236, you can see because there is an icon is a ranch or how you call it like that like…
\n\n\n\nBirgit Pauli-Haack: Oh, toolbox tool.
\n\n\n\nGrzegorz Ziolkowski: Toolbox.
\n\n\n\nBirgit Pauli-Haack: Tool set.
\n\n\n\nGrzegorz Ziolkowski: Toolbox, tool set. So you can see this icon. It means that someone is actually working on this feature or there is open PR, so you can leave your feedback there. And once we have some issues done, then we just be marked as finished. So people can see at some point a history of the progress what’s being worked there. It’s also a nice way if someone opens a new issue and you know, like Fabian Kagy, he opened recently some issues related to how we could better control inserting blocks in the editor.
\n\n\n\nSo you could define, for instance, this blog goes only when there is no block inside the template, or maybe I want to have only a single instance of this block when it is inside a given parent block, like very complex use cases and those type of issue, they’re great ideas, but it’s not so easy to define how that could be done. So this tracking issue will try to combine similar issues like that and put that into the tracking issue. So you can have a single reference and find those issues also from the perspective of project management, like when someone opens a new issue and we can easily say, “Okay, please check this tracking issue and see what we already have on this topic and see how that fits to the proposed solutions so far.” Like this type of capabilities are open and I mean, I’m really excited about that because so far it was really hard to identify how people can get involved to improve the API blocks.
\n\n\n\nSo it impacts how you develop blocks and to make it easier, more straightforward for all the developers. But also it impacts the core blocks. Everyone would benefit from the ideas that are in short in decision.
\n\n\n\nBirgit Pauli-Haack: Yeah. So, let’s see at some of the examples and so in the assets there isn’t one tasks to explore how to tree shake block styles on the front end and has an example issue and that is how, what does it mean? That’s kind of how the CSS cascades through the front end. Another one is combined.
\n\n\n\nGrzegorz Ziolkowski: Yes it is.
\n\n\n\nBirgit Pauli-Haack: Go ahead.
\n\n\n\nGrzegorz Ziolkowski: Yeah. So the idea here is for instance, the idea was whether we can find a way to define, okay, this style is present on the page when the following conditions happen. For instance, in the block has a special class name called, whatever. And then the system that would be built behind that could say, “Okay, and this blog doesn’t have this class. That means that we can skip that and we don’t have to serve it to the user.” So it’s fairly technical, but that gives you idea what exciting things we can do with blocks, having better understanding of how they are structured, what they contain and like these ideas. Also, there’s a lot of requests from Plugin outdoors. So they would like to have a better ways to inject their own styles to blocks or JavaScripts. So, we are discussing different ways how it to make it easier so you could just define okay to all blogs that met certain criteria, let’s add this style that brings some additional visual effects.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah. Okay, I understand that.
\n\n\n\nGrzegorz Ziolkowski: One of the things that we are actively working on is related to dynamic block manipulation. So we always wanted to have a way to, let’s say, use some data that comes from database or some external service. So for instance, the ideas are the simplest one, you have a block inside the footer that shows a copyright note, like in PHP it’s easy because you are using date function and just like changes every year. So you don’t have to go to your website and update that. And how to define some, some ways. So you could just insert a token that says, “Okay, this is a date.” And it displays a year and it will change automatically inside the block. So it’s shortening the database, something dynamic, on the render of the front end it changes.
\n\n\n\nSo, this is very advanced concept. And however we are now, we should see next week a proposal on make core block for something more simple. Often people want to replace some text or token or something, the credit that like a pattern inside your block. For instance, the cover block has a featured image and it’s really powerful. And we’ll be seeing a proposal for special API that will make that simpler so you can define like, let’s find this stack and change this attribute source with the value that comes from the featured image and this type of thing. So everything is very technical. And I think that is a good common, like good place for people who are very familiar with JavaScript, but also with PHP. So like everyone finds something to think about.
\n\n\n\nBirgit Pauli-Haack: Yeah, especially the inline token. We actually had Danny Schnell as a guest on our podcast here when he was working and trying to think through that. And he took us quite deeply into what needs to happen. And so make it complex, make it easy, make it simple. And we call it back then, we call it kind of the short codes 2.0, so it’s not nothing new to WordPress, but it’s the innovative version, the better blocks version for it to have these inline tokens for replacing some variable with something else or with some values. And I’m glad that you said that’s kind of in the works for next week to try out or to at least kick it around in theory, so that’s wonderful. There’s also something that’s in the works that’s…
\n\n\n\nGrzegorz Ziolkowski: And for block registration, there is like a very quite simple proposal. Like right now to define how the dynamic block gets rendered with PHP you need to like define a function. Inside this function you will get some, like content of the block attributes and the block type, and use all those variables to generate the output that’s going to be displayed on the front end. And we are also thinking ahead and trying to combine efforts with how in the future you could like to write simpler blocks in that you would provide a PHP template that generates that output instead. So you don’t have to deal with functions. You just provide a function that just prints everything. And this proposal covers that.
\n\n\n\nBirgit Pauli-Haack: That sounds really interesting.
\n\n\n\nGrzegorz Ziolkowski: So in the future, we could have something similar for JavaScript. So also you could provide like, depends would we peak and land on.
\n\n\n\nAnd, but there is this in the WordPress like organization on GitHub, there is block hydration, experiments, repository, and like explores exactly what I said for JavaScript, how to make blocks interactive on the front end. So for instance, they can have buttons that change state of the block, and you can have like dynamic data that updates, for instance the simple example, people always use the counter. Like you click the plus sign and the number changes, so this type of features. And at some point we hope that this PHP template and JavaScript template could be somehow unified. So maybe not in a sense that you would be writing a single code, but with some tooling, maybe we could have some format that allows you to generate PHP and JavaScript. So you don’t have to bother and write it twice.
\n\n\n\nBirgit Pauli-Haack: Yeah, yeah. Yeah, that was a big discussion between Helen Busandy and Mark Jakeworth and Riad Benguela about, I think it was in October last year. And then I know Michael Chaplinsky has done some more exploration. And then there was, did you work with Ellen Cherser on the, there is a new JavaScript.
\n\n\n\nGrzegorz Ziolkowski: Bento?
\n\n\n\nBirgit Pauli-Haack: Bento. Yeah, Bento JavaScript. Kind of replace the JavaScript framework with a different framework. It’s not certainly the best approach, but if it works for people who use that. Before that you can use it for blocks with different languages or languages and variations and frameworks.
\n\n\n\nGrzegorz Ziolkowski: In some ways the Bento components that Google is working on are similar to the ideas because it just exactly does that. So they have some way to define components and they have different representation for web components for PreAct and you can just, it’s the same UI, but you can use different code, depending whatever you want to have on your website. And it sort of falls in the same category. But it’s just like Bento is done by Google. And it’s hard to tell how it evolves. So we are exploring different parts for now.
\n\n\n\nBirgit Pauli-Haack: Yeah. No, I get it. Well, so is there anything else then, do you want to point out from this tracking issue or discussion?
\n\n\n\nGrzegorz Ziolkowski: Yeah. I guess I’m good. One of the ideas that Fabian mentioned is very interesting, so because the way to control where you display blocks has always been troublesome for people. So people want to have flexibility. For instance, you have custom post type, you don’t want to see all blocks, so how to do that. And we have some ways on the server you can provide allowed blocks to which is list of types of blocks that are allowed. But sometimes we want to have the positive approach. How do I say that? Which blocks I don’t want, and I want the rest. So that’s also some of the discussions happening that the people like our listeners could chime in and share their ideas. And in general, with WordPress 6.0, we added our sister Field, which allows you to define, “Okay, I want to have this block when one of the parent or grandparent or grand grandparent blocks are this and that block.”
\n\n\n\nAnd it’s gives more flexibility, like the comments lock uses that because it allows you have comments and you can have group, then you can have, I don’t know, what else do you want? You can have several groups and then you use a common title, for instance, I mean, in small complex, but make it shorter. And this gives a lot of flexibility and one of the ideas I had originally, how you say like, “I want to have this parent and this ancestor, but I don’t want to have this ancestor.” This type of way of defining, which would satisfy a lot of use cases.
\n\n\n\nBirgit Pauli-Haack: Yeah, indeed. And I think we need to really write much more use cases for it, and tutorials so people can actually imagine things here because theoretically, what’s an ancestor? What’s a parent, what’s a child, where’s a child? It’s all a little bit more, little bit too abstract when you’re kind of try to figure out how to get it all together. There are so many ways to skin, the cat. So are there answers, so I have a question for you and one is that, is there a way to actually pick up custom fields for custom post types if they were kind of already created or if they are kind of available to use them also in a template or? It’s probably very hard to do it via UI. That’s why our advanced custom fields is still for many developers that go to place instead of creating custom blocks for the custom fields. But I think that. Are there any thoughts on that, in this reiteration of the block API?
\n\n\n\nGrzegorz Ziolkowski: Yeah. So for now, the proposal, that’s going to be shared next week for replacing parts of HTML with API that allows you to change attributes. That could be a way, you could say that, “Okay, this field is like going to be replaced with custom field.” So you give you the name and something like that, but it’s still not good enough, in my opinion. We need to have a proper way for that in the future. And maybe even more advanced way of defining dynamic in my tokens. The way it works with blocks, ACF Plugin is that they allow linking between an attribute, so it stores the reference to the exact filter in the database. So it stores the number and based on that, it can provide the correct value. So whenever it changes, it updates on the server as well. So it’s not that easy to do that, but for that ACF has created a special way of writing templates, which takes that into account. It’s dynamic.
\n\n\n\nIt is able to link all the correct numbers and so on. So, I mean, it’s like having something like that in a more flexible way that works, not only with what ACF provides, it’s a bigger task and it is definitely something we would like to have, we just need to do it in steps.
\n\n\n\nBirgit Pauli-Haack: Yeah. Yeah, no, so that will be the block API, third iteration. Now it’s the second iteration and then the next iteration is going to maybe, kind of thinking about through that part. Well, excellent. Thank you so much for walking us all through that. And what’s in the works and what the next iteration of extensibility for blocks actually will look like. That is definitely now that the foundation is in place. Now extensibility has a higher priority, it seems for the Gutenberg project. So I’m really glad that this took a lot of work to find all the right issues and figure out how to structure that. So thank you for going through that and also leading us through that.
\n\n\n\nGrzegorz Ziolkowski: Although to be fair, most of the issues were opened by our excellent contributors. I just only did the part of finding them and putting them in one place.
\n\n\n\nBirgit Pauli-Haack: Yeah. And yeah, you helped a lot of people kind of get a good roadmap through that, or at least an idea of what the vision is going to be, so. Because that’s always a question that we get, so what’s the vision? And only these tracking issues and overview issues like Matias did and what you did and was also Andrew does for layouts and for style engine all that. Maybe I should share some of the tracking issues. I think I collected about 10 or 15 tracking issues now. From the Gutenberg project, it’s probably a better way to figure out what’s current on what people are working on. So yeah, that’s a call for me to maybe think about some curation of that.
\n\n\n\nAll right. Well, thank you very much. At the end of the show, we are way over whatever we wanted to do as an hour limit or so, but that’s okay because you brought so much more insights into what the second iteration of block API is going to hold. Is there anything else that you want to leave our listeners with?
\n\n\n\nGrzegorz Ziolkowski: I don’t have anything.
\n\n\n\nBirgit Pauli-Haack: You don’t have anything. I don’t have anything. I said everything that I wanted to say at the beginning in the announcement, in the community and no, I’m glad you were on the show. Thank you so much for coming. As always the listeners, the show notes will be published on Gutenberg Times.com/podcast. This is episode 71. And if you have questions, suggestions, especially answer for Grzegorz with all the questions that you might have for the blocks API, send them to changelog@gutenbergtimes.com, that’s changelog@gutenbergtimes.com or ping me or Grzegorz on Twitter or WebPress slack. My handle is BPH. That’s my initials on both of them. What’s yours, Jergus?
\n\n\n\nGrzegorz Ziolkowski: Mine is G-Z-I-O-L-O
\n\n\n\nBirgit Pauli-Haack: Giolo? Gizolo?
\n\n\n\nGrzegorz Ziolkowski: Yes.
\n\n\n\nBirgit Pauli-Haack: Yeah, cool. Well, this was it. And thank you very much for listening. If you find this helpful, create a review and we read that out loud here. So you would get a little shout out on the next episode. Thank you for listening, and I wish you a great week. And next two weeks until we hear you again.
\n\n\n\nGrzegorz Ziolkowski: Thank you for the invitation Birgit. It was as your role, a pleasure to catch up what’s happening with Gutenberg.
\n\n\n\nBirgit Pauli-Haack: Well, thank you so much, and it’s always a pleasure to have you thanks so much, Grzegorz.
\";s: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, 06 Aug 2022 21: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: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: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:103:\"Gutenberg Times: Fluid typography, Gutenberg 13.8, Moving block styling to JSON – Weekend Edition 225\";s: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=21775\";s: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:108:\"https://gutenbergtimes.com/fluid-typography-gutenberg-13-8-moving-block-styling-to-json-weekend-edition-225/\";s: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:27494:\"Howdy,
\n\n\n\nGreetings from Berlin with a view of The Cube near the main station of Berlin. My husband and I connected with family and did some sightseeing of the German capital. I also visited the Museum Barbarini in Potsdam and thoroughly enjoyed the exhibition: The Shape of Freedom. International Abstraction after 1945. Interestingly, enough, ‘Abstraction’ is also a topic for software makers. And that’s enough distraction. Let’s catch up together on two weeks of WordPress and Gutenberg news.
\n\n\n\nAs mentioned before, you don’t have to read it all in one sitting. You can always come back gain to read more. It’s summer time in the Northern hemisphere. Hope you can stay cool.
\n\n\n\nYours, ?
Birgit
Various team published new initiatives and updates.
\n\n\n\nAlways seeing the bigger picture, Josepha Haden Chomphosy, executive directory of the WordPress open-source project, ask for you help to Giving FSE a More User Friendly Name. Not all commenters are convinced that there needs to be a name change. I also wasn’t thrilled by the outlook to update lots of post, documentation etc, after discussion Full-Site Editing for over 2.5 years, but I must admit, it’s more the resistance to let go of something I am used to, then a good reason to not try for a more user-friendly name. Some commenters are delighted because they feel it doesn’t translate well into other languages and they already started shortening it to something like site editor or layout editor. I favor something that ends in ‘designer’, like Layout designer, or template designer. The comments are still open. Chime in with your opinion.
\n\n\n\nHector Prieto published WordPress 6.1 Planning Roundup v2 with the updated release schedule and the release squad. Feature Freeze and Beta 1 are scheduled for September 20, 2022, Release Candidate 1 for October 11, 2022 and final release will make WordPress 6.1 available on November 1, 2022.
\n\n\n\nFor the WordPress design team, Channing Ritter posted Project Update: WordPress.org Homepage and Download page mockups. I am excited about this new look of the WordPress open-source project on the Internet. What do you think? Share your comment on the post.
\n\n\n\nJames Koster, also on the WordPress Design team published about his Design Exploration: Encourage editor configuration during on-boarding. It shows a bigger Welcome guide that also help the user make decisions on several settings and features when they first start using the block editor.
\n\n\n\nBen Dwyer outlines in his post Moving Core block styling to JSON the reasoning behind an effort to enable styling of block via the block.json file rather then via css styling. This will have to standardize and streamline ways themes can override 3rd party plugins styling. It will also enable the user to modify the look and feel withouth the need to dive into CSS syntax and language.
\n\n\n\nIn her article, Gutenberg Contributors Experiment with Custom Labeling of Blocks in List View, Sarah Gooding explains the exploratory efforts by developers to allow users to name sections of their page/site to better find them in the List View. Dave Smith create the PR ready for review. If you haven’t tested a PR before the merge, I would recommend following Paal Joachim Romdahl‘s Testing a Gutenberg Pull Request (PR)
\n\n\n\nGeorge Mamadashvili was the release lead for the Gutenberg plugin v 13.8 release. In his post What’s new in Gutenberg 13.8? (3 August), he highlighted:
\n\n\n\nFluid typography has been requested by theme developers for quite some time. It’s only available to theme developers/designer via the theme.json for now. Before the settings can be made available via the Global Styles interface, this first iteration could use some thorough testing.
\n\n\n\nThis week, Grzegorz Ziolkowski and I discussed the Gutenberg 13.8 release, changes to the Block API and so much more for the next episode of the Gutenberg Changelog (episode 71). It will arrive at your favorite podcast player over the weekend.
\n\n\n\n?️ New episode: Gutenberg Changelog #71 – Gutenberg 13.8, Fluid Typography, updates to the Block API and more – with co-hosts Grzegorz Ziolkowski and Birgit Pauli-Haack
\n\n \n \n Howdy, Some great Block themes resources are now available. And if you haven’t yet, consider joining the Full-Site-Editing Outreach program channel on WordPress Slack. Anne McCarthy always invites members to… Read more. | \n
\n \n \n What happens when a theme registers a pattern with a third-party block? If the user has the block plugin installed, it appears as it should. WordPress also does a good… Read more. | \n
\n \n \n On July 22, 2022, Michael Piccorossi, Head of Digital Strategy and Seth Rubenstein, Lead Developer at Pew Research Center talked to co-hosts Anne McCarthy, WordPress Product Liason and Birgit Pauli-Haack,… Read more. | \n
Carolina Nymark updates instructions on how to implement Fluid Typography via Theme.json that are now available via 13.8. It’s part of the Typography lesson on of her Theme builder course for developers.
\n\n\n\nDaisy Olsen held a workshop on Learn. WordPress that is now available on WordPressTV: Theme Development Workflows For Different Types of Developers. During this workshop, Daisy Olsen discussed the different workflows that someone might use in the creation of block themes. Discover the best development workflow that is right for you.
\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
Anne McCarty published FSE Program Category Customization Summary of the 15th call for testing. It’s an interesting read to learn what people struggle with and also what they appreciate when creating category templates and interact with patterns for custom post types.
\n\n\n\nAri Stathopoulos, from the WordPress Themes team, details how themes submitted to teh themes directory are to Use locally-hosted Google fonts in themes and answer frequently asked questions.
\n\n\n\nShout-out for the theme.json feature of block themes by Daniel Schutzsmith via The Repository under A concept worth understanding he wrote. “As a developer, I’ve been playing with the new theme.json concept and I can easily say it is something we all should be adopting as we create new websites. The concept of using a JSON file to set up the common styles used throughout WordPress core works well, especially in a traditional version control workflow on a team. It’s worth digging into fullsiteediting.com and learn.wordpress.org. Both of these resources provide some terrific materials to make it all easier to understand.”
\n\n\n\nSean Blakeley was a guest on the WP Tavern Jukebox podcast and talked with Nathan Wrigley on Transitioning a Large Agency Over to Gutenberg. “After years of experiments with different approaches and collaborations between designers and developers, their team has begun to rely heavily on block patterns, and they’ve found it is greatly increasing their productivity. It’s fair to say that block patterns have revolutionised the team’s approach to the entire design process.” Wrigley sumarizes.
\n\n\n\nSean Blakeley also talked about Block Pattern Revolution at WordCamp Europe. The talk is available on WordPressTV.
\n\n\n\nIn his post and video , I’m Switching to Gutenberg For WordPress | And YOU SHOULD Too (Probably!), Paul Charlton of WPTutz talks about his reason, why he sticks with WordPress’ core block editor, plus 3rd party plugins to extend the features set to his needs, mostly more controlas for animation and grid block layouts. What are some of the tools you are using to augment the WordPress block editor?
\n\n\n\nVikas Singhal announced a new plugin Newsletter Block and Jamie Marsland reviewd it on his YouTube Channel and called it The Best WordPress Gutenberg Block for Mailchimp
\n\n\n\nIn his video on WordPressTV, Ben Evans introduces you to Nine Design Blocks. He shows you how these blocks behave differently on different screen sizes and let’s you take part on how he experiments making different layouts using these blocks.
\n\n\n\nWes Theron shows you the steps necessary to Create a landing page with a block theme. You’ll learn how to create a custom template and build two landing pages using different methods.
\n\n\n\nNick Diego‘s part 2 of Let’s Build a Custom Theme (No Coding Required) is now available on WordPress TV. Part 1 is also online
\n\n\n\nBerhard Kau helps fellow developers to creata A first simple block with some ES6 code – it’s not as scary as it sounds. It’s a follow-up post on creating a block via React. Kau suggests relying on the official scaffolding tool for block creation, tool called ‘create block’ that is available from the Gutenberg repository.
\n\n\n\nNick Diego helps you to Unlock the Power of the Block Locking API. In this article, Diego explored the block locking API, how to implement locking in a real-world example, and discussed ways to extend this functionality by restricting who can lock and unlock blocks. Coincidently, Core contributores also update the documentation with a new page in the handbook: Curating the Editor Experience
\n\n\n\nJonathan Bossenger‘s session on Let’s Code: An Introduction to Block Development is now available on WordPressTV. In this session, Bossenger walks you through the software required to develop blocks, and how to set it all up. Then he shows a tool called create-block to create our first block, and then looks at the code that this generates and what each piece does.
\n\n\n\nThe organizer at WordCamp US published the schedule of talks. it’s a great line-up of speakers. Below list might make it onto your calendar. The WordCamp will livetstream the sessions.
\n\n\n\nFriday, Septemberg 9, 2022
\n\n\n\nA series of 15-minute talks:
\n\n\n\n4 pm EDT / 20:00 UTC
Customizing Core Blocks for Clients with Alex Ball
5 pm EDT/ 21:00 UTC
Let’s Build a Custom Block in 15 Minutes with Nick Diego
5:15 pm EDT / 21:15 UTC
FSE For the Win with Evan Mullins
Saturday, September 10, 2022
\n\n\n\n12:15 PM EDT / 16:15 UTC
Build Your First Block Theme with Daisy Olsen, a 2 hrs Workshop
4 pm EDT / 20:00 UTC
A New Era of WordPress Themes is Here: Block Themes wtih Rich Tabor (45 min)
5pm EDT / 21:00 UTC
The Future Of Themes: Designing for the Block Editor and Beyond with Michelle Schlup (45 min)
Need 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.
November 18, 2022
WordFest Live 2022
Call for speakers ends August 15, 2022
September 2 + 3, 2022
WordCamp Jinja 2022, about 2 hrs West of Kampala, Uganda. Calls for sponsors, speakers, and volunteers are open now.
September 3 + 4, 2022
WordCamp Kathmandu, Nepal
September 9 – 11, 2022
WordCamp US in San Diego
September 15 + 16, 2022
WordCamp Netherlands at the Royal Burger’s Zoo in Arnhem
September 24 + 25, 2022
WordCamp Pontevedra
February 17 – 19, 2023
WordCamp Asia, Bangkok, Thailand
Call for speaker was just published. Deadline: September 15th, 2022 (UTC +7)
Contributor Day is planned for February 17, 2023 (Day 1)
August 10, 2022 – 3 pm EDT / 19:00 UTC
Block Theme Builders: Design With Figma w/ Damon Cook & Sarah Snow
August 16, 2022 – 5 pm EDT / 21:00 UTC
Showcasing Content with Query Loops with Wes Theron
Featured Image: The Cube at the main train station in Berlin, Germany. Photo by Birgit Pauli-Haack
\n\n\n\nDon’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nAdam Silverstein on Performance in large plugins, GDPR and accessibility, World Wide Web Day in the global WordPress community, Jonathan Wold on partnerships, women in software, and Michelle Frechette on building communities.
Get our weekly WordPress community news digest — Post Status\' Week in Review — also available in our newsletter.
And don\'t miss the latest updates from the people making WordPress. We\'ve got you covered with This Week at WordPress.org.
The next big version of Do the Woo is on the road map.
\n>> The post WooBits: Do the Woo 4.0 Coming Your Way 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, 05 Aug 2022 10:40: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: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:56:\"WordPress.org blog: The Month in WordPress – July 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=13306\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2022/08/the-month-in-wordpress-july-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:14623:\"July 2022 brought a lot of exciting announcements and proposals for the WordPress project, from an updated timeline for the WordPress 6.1 release, to design updates on WordPress.org. Read on to learn more about the latest news from the community.
\n\n\n\nMark your calendars! The WordPress 6.1 development cycle has been published along with its release team. The expected release date has been updated to November 1, 2022, to incorporate feedback received on the first proposed schedule.
\n\n\n\nIn the meantime, you can upgrade WordPress to version 6.0.1. This maintenance release became available for download on July 12, 2022, and includes several updates since WordPress 6.0 in May 2022.
\n\n\n\n\n\n\n\n\n\n\n\n\nWant to get more involved with WordPress? Join Executive Director Josepha Haden Chomphosy, as she guides you through the five stages of contribution in a recent episode of WP Briefing.
\n
Following the revamp of WordPress.org/News and the Gutenberg page, further design updates are coming to WordPress.org to create a fresh and modern user experience that reflects the future of WordPress.
\n\n\n\nThe WordPress.org home and download pages will be the next pieces to get a refreshed look and feel. The redesign project kicked off on July 8, 2022, and the development work is already underway.
\n\n\n\n\n\n\n\n\n\n\n\n\nTake a look at the design mockups and join the conversation.
\n
Three new versions of Gutenberg have been released since last month’s edition of The Month in WordPress:
\n\n\n\n\n\n\n\n\n\n\n\n\nFollow the “What’s new in Gutenberg” posts to stay on top of the latest updates.
\n
\n\n\n\n\n\n\n\n\nWP Briefing celebrated World Wide Web Day 2022 with a special episode! Tune in to hear contributors from the community reflect on how WordPress impacts their world.
\n
\n\n\n\n\n\n\n\n\nThe Community Team is calling on all meetup members and organizers to complete the 2021-2022 Annual Meetup Survey. Your feedback will help strengthen the WordPress meetup program for years to come. Please respond and help spread the word.
\n
\n\n\n\n\n\n\n\n\nJoin #WPDiversity with a free, online speaker workshop for Indian women in the WordPress community. The event will take place on September 24-25, 2022. Sign up now!
\n
Have a story that we should include in the next issue of The Month in WordPress? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to this edition of The Month in WordPress: @chaion07, @laurlittle, @mysweetcate, @sereedmedia, @dansoschin, @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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Aug 2022 08:57:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:105:\"Post Status: Building and Sustaining the WordPress Community Through Mentorship — Post Status Draft 123\";s: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=103831\";s: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:104:\"https://poststatus.com/podcast/draft/building-and-sustaining-the-wordpress-community-through-mentorship/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7367:\"\n\n\n\nMentor someone. Today! Don\'t wait. Start today! Talk to people. Connect with them. Go on Twitter. Just 15 minutes a day. Tell them why this community is great. Make them want to join!
Nyasha Green
For Nyasha Green, a healthy tech community prioritizes mentoring. She credits her mentors with helping her find her place in WordPress. How well does your part of the WordPress ecosystem support mentorship? Can we make mentoring a key way people contribute to WordPress\'s future?
Estimated reading time: 2 minutes
\nIn this episode of Post Status Draft, Nyasha Green joins Dan Knauss to tell her story about joining the WordPress community relatively recently. Ny is a Software Developer at Howard Development and Consulting as well as the Editorial Director for MasterWP. Ny credits Ken Elliot and Shambi Broome as mentors who got her into WordPress. Together they\'re getting two new WordPress Meetups up and running in Columbia, SC and Charlotte, NC.
\n\n\n\nPicking up on one of Kim Lipari‘s comments last week (“We\'re not a small village anymore.” A Conversation with Kim Lipari — Post Status Draft 121), Nyasha shares her thoughts on the ways the WordPress community can better embrace growth and change by enlarging its circles of leadership, innovation, and talent. For Ny, a culture that prioritizes mentoring relationships is essential. She sees value in paid internships at WordPress companies, intentional programming at Meetups and WordCamps, and the continued use of travel scholarships to welcome new people to an increasingly inclusive WordPress community.
\n\n\n\nFinally, we also talk about dealing with grief, loss, and emotional health in tech, how social media hurts and helps, and resources like Big Orange Heart that are there for you when you\'re all out of spoons.
\n\n\n\n\n\n\n\nA2Hosting offers solutions for WordPress and WooCommerce that are both blazing fast and ultra-reliable. WordPress can be easily deployed on ANY web hosting plan from A2: Shared, VPS, or Dedicated. A2 also offers Managed WordPress and WooCommerce Hosting. Take a look at a2hosting.com today!
\nThe 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.
Have you recently thought it would be nice to have one comprehensive source for all WordPress community events?
\n\n\n\nThanks to The Events Calendar and some nice people at StellarWP — Hazel Quimpo, Zach Tirrell, and Michelle Frechette — there\'s a great new place to go exactly for that: WP.events!
\n\n\n\nJavier Casares‘ wonderful wpcalendar.io has been deeply missed, as he covered all the meetups happening around the world. Maybe it will be back one day… Sounds like he needs time and maybe some help to revamp it. There\'s only so much you can do with RSS though.
\n\n\n\nStill, it\'s a wonderful open web technology…
\n\n\n\nAdam Silverstein talks about WordPress core performance and how it ties into the performance of larger plugins like WooCommerce.
\n>> The post WordPress Core Performance with Adam Silverstein 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, 04 Aug 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: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:94:\"Post Status: Free Rider Problem, JSON Core Block Styling, Redesigned Home & Download Pages\";s: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=103568\";s: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:137:\"https://poststatus.com/wordpress/week-in-review/make-wordpress/free-rider-problem-json-core-block-styling-redesigned-home-download-pages/\";s: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:16340:\"Have you seen the new home page demo? \nIs there a problem with Free Riders?\nDo you want block styling standardized?
Development work is already underway on a block-based theme implementing a new design. A recent copy of the theme is running on a temporary staging site.
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.
On the podcast today we have Jonathan Wold.
\n\n\n\nJonathan joined the WordPress community seventeen years ago, and he’s been here ever since.
\n\n\n\nHe likes to think about WordPress as an operating system for creating on the open web, and invests his time and energy into growing the WordPress ecosystem.
\n\n\n\nWith that in mind he gave a talk at the recent WordCamp Europe called “Growing in WordPress through partnerships”, in which he laid out his thoughts on how WordPress companies can enable greater growth by joining with other, like minded companies.
\n\n\n\nThere’s a lot of WordPress products out there, and whilst building a product can be a challenge, getting that product into the market, gaining growth and recognition can be another hurdle altogether.
\n\n\n\nJonathan talks today about how strategic partnerships can, in some cases, make the job of selling a product easier and more rewarding.
\n\n\n\nWe talk about how the WordPress ecosystem has grown over time, and how discoverability of your product is harder now that it used to be.
\n\n\n\nWe discuss the fact that WordPress has a heritage of solopreneurs who might not be as good at marketing as they are at coding, and how joining forces with partners can make it easier to succeed in the marketplace.
\n\n\n\nAre partnerships for everyone, or are they only for a subset of companies? How do you go about finding a partner and what are the ways that you can ensure that you’re working with the companies which offer the most benefit to you and your customers?
\n\n\n\nTypically, when we record the podcast, there’s not a lot of background noise, but that’s not always the case with these WordCamp Europe interviews. We were competing against crowds and the air-conditioning. Whilst the podcasts are more than listenable, I hope that you understand that the vagaries of the real world were at play.
\n\n\n\nTranscript[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, creating partnerships to grow your WordPress business.
\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 WP Tavern dot 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, I’m keen to hear from you, and hopefully we can get you or your idea featured on the show. Head over to WP Tavern dot com forward slash contact forward slash jukebox. And use the contact form there.
\n\n\n\nSo on the podcast today we have Jonathan Wold. Jonathan joined the WordPress community 17 years ago. And he’s been here ever since. He likes to think about WordPress as an operating system for creating on the open web, and invests his time and energy into growing the WordPress ecosystem.
\n\n\n\nWith that in mind, he gave a talk at the recent WordCamp Europe called growing in WordPress through partnerships, in which he laid out his thoughts on how WordPress companies can enable greater growth by joining with other like-minded companies.
\n\n\n\nThere’s a lot of WordPress products out there. And whilst building a product can be a challenge, getting that product into the market, gaining growth and recognition can be another hurdle all together.
\n\n\n\nJonathan talks today about how strategic partnerships can, in some cases, make the job of selling a product easier and more rewarding. We talk about how the WordPress ecosystem has grown over time, and how discoverability of your product is harder now than it used to be. We discussed the fact that WordPress has a heritage of solopreneurs who might not be as good at marketing as they are at coding. And how joining forces with partners can make it easier to succeed in the marketplace.
\n\n\n\nAre partnerships for everyone, or are they only for a subset of companies? How do you go about finding a partner and what are the ways that you can ensure that you’re working with the companies which offer the most benefit to you and your customers?
\n\n\n\nTypically when we record the podcast there’s not a lot of background noise. But that’s not the case with these WordCamp Europe interviews. We were competing against crowds and the air conditioning, and whilst the podcasts are more than listenable. I hope that you understand that the vagaries of the real world we’re at play.
\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 dot com forward slash podcast, where you’ll find all of the other episodes as well. And so, without further delay, I bring you Jonathan Wold.
\n\n\n\nI am joined on the podcast by Jonathan Wold. Hello?
\n\n\n\n[00:03:43] Jonathan Wold: Hey Nathan, how are you?
\n\n\n\n[00:03:44] Nathan Wrigley: Oh, you sound truly excellent on this microphone.
\n\n\n\n[00:03:47] Jonathan Wold: We have an awesome little set here.
\n\n\n\n[00:03:49] Nathan Wrigley: Yes. Well, we’re in the bowels of the Super Bock Arena in the most undiscoverable bit, but you’ve managed to find me. It’s early morning. It’s the first day. We’re you here yesterday?
\n\n\n\n[00:03:59] Jonathan Wold: Yeah, contributor day was fantastic. It’s so good to see so many faces, including faces that I thought I’d seen before, but hadn’t. You find out that people are taller or shorter than you expected.
\n\n\n\n[00:04:09] Nathan Wrigley: That’s right. Over Zoom over the last couple of years, you’ve basically been reduced to a postage stamp.
\n\n\n\n[00:04:13] Jonathan Wold:Yes.
\n\n\n\n[00:04:14] Nathan Wrigley: And people actually have legs. Yeah. So what did you contribute to, what was your bit?
\n\n\n\n[00:04:18] Jonathan Wold: I floated around. Mostly trying to support other folks. There are a lot of first time contributors yesterday, which is fantastic. It’s so good to see that. So I did what I could to support them.
\n\n\n\n[00:04:26] Nathan Wrigley: My understanding was that it was about 60% of people who showed up today will be first timers.
\n\n\n\n[00:04:33] Jonathan Wold: Yeah I think that’s fantastic. Like it’s so good to see so many returning faces, but really we want to see the new people coming in.
\n\n\n\n[00:04:40] Nathan Wrigley: You’re doing a talk we’re gonna talk about that I think. Tell us what the premise of the talk is.
\n\n\n\n[00:04:45] Jonathan Wold: The talk is focused on this idea of growing in WordPress through partnerships. I’ve had the privilege working with a lot of product businesses over the years and, I’ve seen this recurring theme of frustration where a product business, they’ll have a good product, they’ll get some good market validation. Maybe some customers that really love the product. And then this frustration where they can’t seem to tap into the larger ecosystem, like WordPress is huge. Or even just take a sub ecosystem like WooCommerce. There are millions of WooCommerce installs and for a product business, oh, we’re gonna serve WooCommerce customers.
\n\n\n\nAnd then it’s this challenge of how do you get to ’em? There’s not this like one central place. You could work with WooCommerce, certainly, but even if you do a partnership with WooCommerce, that doesn’t guarantee that you get in front of all their audience. So it becomes very challenging and frustrating for product businesses, because of how decentralized our ecosystem is. Of which there are many benefits and things that we enjoy.
\n\n\n\nIt can be challenging to say, okay, how do we navigate this? Who do we talk to? Where are all the customers? There’s some good reasons for that. So in my talk today, I’m trying to kind of unpack that. Give some perspective, especially to folks who are coming from outside the immediate ecosystem. There’s a lot of SaaS businesses that have built great products that work well with WordPress. They come in though, and they hit these roadblocks where they’re like, okay, what do we do? Like, how does this community work?
\n\n\n\nWhere do we go? How do we act? Where do we focus our energies? And I think it’s a lot harder right now than it needs to be. Like growth in WordPress is difficult if you don’t know where to go. And I think that hurts all of us. So, my intent anyway is to try and demystify some of that and then give a clearer path to like, hey, if you wanna grow a product business in the WordPress space, partnerships today is probably your best way of doing so, and here’s how to do that.
\n\n\n\n[00:06:32] Nathan Wrigley: Do you think this is a function of personality a bit? And what I mean by that is, if you are a born coder and you spend your time in your room and you’re extremely good at that, this comes out of personal experience. I’ve encountered lots of people who are extremely good at that side of things. And then they build the thing and the thing is brilliant, but they are not the person to make it go out into the ecosystem.
\n\n\n\nBecause they code and then they struggle with that piece of getting it recognized. So they contact podcast owners. They write to blog vendors and so on and so forth. But, it’s very difficult because you have to be that effervescent, outgoing marketing type of person.
\n\n\n\n[00:07:09] Jonathan Wold: That is part of it, but it’s also a timing thing because the coder, if you will, was able to pull it off before. If you think about how WordPress has grown over the past 18 plus years. In the early days, that was enough. You could build a great product and other people would do it for you.
\n\n\n\nRight? You go to a meetup, oh, you gotta use this plugin. That worked, and I think there are folks now who will look at that and like, why isn’t it working for me as well? Well, that worked more because of just where WordPress was and it’s life cycle at the time And it doesn’t work anymore. It’s just because of how big it is. Or rather it can still work. You can still absolutely grow something by word of mouth.
\n\n\n\nYou’re gonna hit a ceiling though. And if your ambitions are greater, if you’re wanting to create something that’s more ubiquitous that solves needs for a much larger swath of the ecosystem, that’s not gonna be enough. You’re] gonna have to do the work and get in front of the audience.
\n\n\n\n[00:07:58] Nathan Wrigley: Is it a product of geography as well? Where you are in the world?
\n\n\n\n[00:08:02] Jonathan Wold: That’s always a factor in that it can limit who you’re connected to. Because someone who’s a great coder, maybe they’re introverted and, but they’ve gone to their local WordCamps, and that’s where they make connections and other folks do the recommendations for them. And so yeah, in that sense, geography could be a limiting factor if you haven’t had the chance to go all the way around.
\n\n\n\n[00:08:19] Nathan Wrigley: So I was thinking of an example, let’s say that you live in North America or something. There’s hundreds of different events that you could attend and there’s conferences and there’s countless things where you could present your face. Whereas if you live in a different part of the world where the community just isn’t there, that’s gonna be a, a bit of a struggle.
\n\n\n\n[00:08:33] Jonathan Wold: It is, and from my point of view, the struggle existing doesn’t fit with the ethos of WordPress and it’s international nature. And that’s why I think at least in my experience so far and where I’ve seen product companies have success, like they’ll be something that very few folks will know about. And then they begin to do the partnership work and approach it in the WordPress way, and then they can build success on that.
\n\n\n\n[00:08:55] Nathan Wrigley: So map out for us what you actually mean by partnership. Obviously everybody gets what that word is basically, but tell us what is it that you are gonna be advising somebody who wants to make hay out of their brand new plugin, theme, block, whatever.
\n\n\n\n[00:09:07] Jonathan Wold: The way that I think about it, and at least I found most helpful is to start with the audience. You’re building a product. What audience are you focusing on? Who has a problem that you’re trying to solve? Be really clear who that is. You could say, oh, small business. Well, small business is still very broad and general. Maybe you have a specific type of small business, whatever that may be.
\n\n\n\nStart with that audience of like, okay, we’re gonna build a product or maybe you have a product already. And some folks will maybe have a product, they’re not sure what audience it’s for, but let’s just set that aside for a moment. But once you, as the product owner have a clear audience in mind, then it’s like, okay, who else is already serving that audience?
\n\n\n\nOne of the common mistakes I’ve seen folks make is they’ll make a product, and they’re like, okay, we need partnerships and they’ll go partner with, uh, a hosting company for instance, but that serves a different audience. Because it’s like once you know who your audience is, you find a potential partner where you can work together on it.
\n\n\n\nThen all you’re really doing is say, okay, what’s the mutual win. Like how can we together provide more value to that audience? Where I see most partnerships fall apart is where it’s an audience mismatch. Or maybe they got the right audience, but they still don’t have a clear value proposition for that audience. The ones that work really well are, same audience or very similar, nice overlap. And then they’re just providing them value in a way that benefits all the parties involved.
\n\n\n\n[00:10:26] Nathan Wrigley: I feel like a lot of the stuff that you’re saying makes perfect sense to you, you know, find the audience and so on and so forth. You’ve probably been through this many, many times. Those kind of processes aren’t necessarily obvious because you, you might just think I’ve got a plug in. It’s for every body, and the whole ecosystem can use this. What is the actual process? I mean, are you literally pen on paper? Have you got like a spreadsheet that you fill out or.
\n\n\n\n[00:10:47] Jonathan Wold: So, it’s a good point to bring up the, all the audience. I actually love working on plugins and with authors that are going for all of WordPress. It’s a smaller subset in general, right? Because like, one of the things I love about how we approach core development in WordPress is, what are the things that serve the 80%. Because WordPress, we’re not trying to, in the core solve for everyone. And in similar vein, there are product businesses that can be wildly successful that aren’t trying to do it for everyone in WordPress, right.
\n\n\n\nSo I think that’s worth calling out. There’s still a lot of opportunity to go for ubiquity in the ecosystem. Be clear though on whether that, whether or not that’s actually your intention. So let’s say for instance, you are not going for all of WordPress, you’re going for a, just a sub ecosystem. WooCommerce for instance, a smaller part of WordPress and within WooCommerce you could go for small businesses. You could go for mid-market. You could go for enterprise. Let’s say you went small business WooCommerce. This is the audience that we wanna work on. They do less than a million dollars a year in revenue, and we have a specific problem we’re solving for them.
\n\n\n\nSo in just this example, most folks I talk to, if they’re that clear, they’re more than halfway there, right. They’re often not though where it’s like, oh, we want to do this for everyone, right. It’s very difficult. And especially when it comes to partnerships where it’s like, we’ll work with everyone. In some cases that might be the play, but it’s often not. Does that make sense?
\n\n\n\n[00:12:06] Nathan Wrigley: Yeah for me, it’s the actual going through the process. Like, I usually need a form to fill out. Firstly, do this. Secondly, do this. And then, you know, it might be creating the customer avatar and giving them a name and trying to figure out what industry they’re in and so on. And having that structure, something to hang it on works for me. But it may not be the kind of thing that you would advise people to do when, when going out to get partnerships.
\n\n\n\n[00:12:27] Jonathan Wold: Yeah It’s a good question. It’s a good question, because I guess I am making the assumption that someone’s clear on who they want to serve.
\n\n\n\n[00:12:33] Nathan Wrigley: Yeah, and that’s difficult.
\n\n\n\n[00:12:34] Jonathan Wold: It can be difficult, because there’s an inherent choice in who you’re not gonna serve, right? And again, it’s worth calling out that when I think about positioning for a product company, to say who, okay, this is who we’re gonna serve. Doesn’t mean that you can’t also serve others who come to you. It’s not that you have to turn them away. It’s making a choice though, on who you’re gonna focus your energies and your messaging, your positioning on.
\n\n\n\nAnd that, it is hard. And it’s often hard because of that fear of what you’re gonna miss out on. But when it comes to your marketing efforts, your even your, like your product development, and then in this case, partnerships, if you’re not clear on who you’re serving, it’s very hard to find ways to reach them.
\n\n\n\n[00:13:13] Nathan Wrigley: Okay. So let’s assume that we’ve got that piece of the puzzle nailed down, and we know who we’re trying to serve. What’s the next step? What does a partner look like? How much are you giving away of your company? How do you contact these people? How do you give the pitch? In a way, trying to find a partner is perhaps equally as difficult as trying to find a customer.
\n\n\n\n[00:13:31] Jonathan Wold: Well, so it’s a fair point on what does it mean to partner. In general, what I’m talking about with these strategic partnerships would pretty much never involve any, like giving away part of the company. It’s more a transaction of like, hey, you have this audience, we have this product, how can we work together to serve them, right? And sure there are a lot of ways that could work. In some cases you might take investment from the partner that you’re working with.
\n\n\n\nThere’s lots of ways you can approach it. Which is, in my mind a key is to not go into these conversations with everything figured out, but to say, okay, how can we together provide more value to the audience? I sometimes I see folks jump too quickly to like, okay, what are the commercials?
\n\n\n\nAnd saying, that’s a little bit of the cart before the horse, right? Where’s the value we can provide for the audience. If we’re not both really clear on that value, it’s gonna make negotiations difficult, and ultimately probably not be as successful for either party. I’ve seen product companies do distribution deals with hosting companies, for instance, that are pretty terrible. Where it’s like, okay, we wanna get our product in front of all your customers. And they’re like, okay, well, here you go. And it’s not a good deal.
\n\n\n\n[00:14:36] Nathan Wrigley: Are events like this, like WordCamp Europe, are events like this a great way to sort of short circuit the whole finding a partner thing? There’s thousands of people in this case, all in one room. A proportion of those are they’re playing that game. They wanna find partners and they’re looking for people to hook up with. I mean, you’re in a room it’s difficult. There’s no sort of your head saying, I want to partner. So, is that a part of the jigsaw puzzle of an event like this?
\n\n\n\n[00:14:59] Jonathan Wold: It is, and this is perhaps where personality is more of a factor. I would not advise someone to approach events like this as okay, we’re gonna go get partners. This is really in my mind more about context development and connecting with folks. Like, yeah, you might have folks, this is someone who I’d like to work with. And WordCamp can be a great place to build some shared context.
\n\n\n\nIn general, for instance, I would see a WordCamp more as adding personal context to a conversation that’s already happening. You could certainly meet new folks, but I guess what I’m trying to say is like, I would hate to see someone put too much pressure on themself. To like attend a WordCamp and like try to get all this stuff done. That’s not really the vibe of it. It’s more about building context. If someone’s new to the space, it’s like go to contributor day first. Just soak it up a bit. Like one of the mistakes that I’ll see product companies from outside the ecosystem make, is just be really off on their messaging and positioning. Or being overly aggressive.
\n\n\n\nIt’s like, no. That stuff is fine. Like it’s good to see the ambition. Take some time though, to understand the ecosystem, and WordCamps to me are really good for that. So it’s more about go in curious, and see what you can learn and don’t make assumptions. And yes, you’ll probably find some really good opportunities. In general though, it’s like, if you had a list of folks that you want to connect with, be talking to them already before WordCamp, and WordCamp is more about just seeing them in person.
\n\n\n\n[00:16:19] Nathan Wrigley: So everything that you’ve just said, I totally identify with, and I do see people not doing that, and I see people showing up and they’ve clearly got the laundry list of people they want to contact. And it all feels a bit clumsy. Is that a unique thing about the WordPress ecosystem? And what I mean by that is the whole FOSS thing, the free open software. For example, if I was to attend, I don’t know, a conference about podcasting or something. Is the same audience there?
\n\n\n\nAre there different rules at play here? And it feels a little bit like you’ve got to be a bit more restrained. You’ve gotta do your homework a bit more because there’s trip wires everywhere, and sometimes even just etiquette and the things that you mentioned about just don’t overstep the line, we don’t know each other yet. We’re not ready for that bit, but maybe if you are a different kind of an event, that stuff is, I’m open for it.
\n\n\n\n[00:17:05] Jonathan Wold: In my experience, yes, but most of it’s hearing that relayed from a software as a service companies, for instance, who are used to other industries where it’s lot more, not business oriented, but yeah, perhaps more transactional. And it’s a bit of a system shock to come to a WordCamp. Or even just the idea of how involved volunteers are. Many of us, like if we’re involved, I’m helping organize WordCamp US this year. I’m doing it as a volunteer.
\n\n\n\nAnd that idea of volunteers is kind of an odd one for folks coming from outside. And I think that well typifies, like this is different. People are here because they really want to be here, at least from what I hear. And the other events I attend, it is a very different vibe. Which is why it’s like, yeah, you can prepare for it, but the starting point is just be open and put out your preconceived notions and take a deep breath. It’s gonna be okay.
\n\n\n\n[00:17:52] Nathan Wrigley: The whole partnerships thing, is that a piece of what you do when you’re not at a WordCamp? Is that part of your business life?
\n\n\n\n[00:17:59] Jonathan Wold: It is, mostly from like an advising perspective. Part of the challenge that I’m personally trying to see us solve is, I don’t like that there’s and it’s getting better, but having just a handful of folks who do partnerships work in the ecosystem is not good for the ecosystem. It’s something that I’d like us to see, just become a lot more professionalized and this is just how to do it. I don’t think it’s healthy to have it locked up in just a few people who do it.
\n\n\n\nSo yes, I’ll help folks do it. I’m much more interested though in seeing us open source, like how should this get done? How do we professionalize this aspect of our ecosystem? There’s a lot more of it starting to happen, but I feel like the advantage in our ecosystem is, has been more to like the few hosting companies who are better at it than others, or the product companies that are better at it than others. Where really, if we can all get better at it, I think the ecosystem as a whole benefits.
\n\n\n\n[00:18:49] Nathan Wrigley: So is this more that for the last decade or so, we’ve had a lot of people who’ve had a cottage industry for want better word for their job, and the ecosystem, I’m gonna use the word matured. I dunno the right word, but the ecosystem has matured. It’s become more professional, so the people who had the cottage industry need to up their game and figure out what the rules are, how to piece that jigsaw together.
\n\n\n\n[00:19:10] Jonathan Wold: Yes. There’s a few factors to it. There’s the folks who’ve come up through it, like upping their game, which is hard. Well, what’s happening is that there are a lot of folks, software as a service companies, for instance, wake up and say, hey, more than 30% of our customers are on WordPress. Like 40% of our customers are on WordPress. We need to have a strategy. We need to have an approach. Even just to serve our existing customers better.
\n\n\n\nThe company that wakes up and says, we need to have an integration. We need to have our own plugin. And there’s them serve their customers better, which is good for all of us. But then many of them will say, hey, we can grow through WordPress. Like there’s opportunities here to grow our audience.
\n\n\n\nSo it’s a bit of a clash where what’ll happen sometimes is these companies from outside will look in and they’ll see existing behavior and think that’s how it should be done. But they’re watching the cottage industry approach. And it’s like, no, we all need to grow here. The folks who have been in it this whole time, we need to get better at how we do this.
\n\n\n\nAnd then the folks who are coming from outside need to take a cue and say, okay, well, how do you change and, and work within this culture? It’s challenging. I’m encouraged with the progress that I’m seeing, but it’s not enough.
\n\n\n\n[00:20:15] Nathan Wrigley: It feels like you’re a bit worried that if we leave this whole partnership thing unchecked, a decade from now there’ll be a few major players. There’ll just be this pyramid structure with a…
\n\n\n\n[00:20:24] Jonathan Wold: Yeah, that’s part of it. And I think it’s just not healthy for the ecosystem as whole. A great example is contribution to core, right? What I love about all these new folks coming in. I’ve talked to some of them where they’ll explicitly call out, like it’s intimidating to go into like one of the core with thousands of people. And put a reference to a ticket or something. Yeah, it’s intimidating. And that’s why we have days like this to sit alongside someone and help them feel comfortable.
\n\n\n\nIf we’re gonna continue to grow as an ecosystem, we have to be welcoming to new ideas, new input, and we have to make it accessible for them. And I think partnerships is just a good example of that. Right now, because we’re so decentralized and may it ever be so, you have to do that work to make the connections happen. And I just, I see a lot of opportunity for that to become professionalized.
\n\n\n\n[00:21:11] Nathan Wrigley: That’s a really interesting point because when I started building websites, basically you built a website. You found a client, you built a website, you passed it on.
\n\n\n\nAnd then as the industry matured, the job of an SEO expert came along and the job of a copywriter came along. All these little jobs in, WordPress came along. And it feels like you are advocating for a job of some kind of partner interface career. That’s the job. You need people like that. You need little, little businesses that are set up to figure out how to get plugin company, a theme company, a hooked up with other company B.
\n\n\n\n[00:21:40] Jonathan Wold: Yep.
\n\n\n\n[00:21:41] Nathan Wrigley: So that they can figure out a way to move forward.
\n\n\n\n[00:21:43] Jonathan Wold: I’m sure I’m exaggerating, but if there were only 50 people like really doing this professionally today in the ecosystem, there needs to be a thousand. And this is not a new thing. Partnership management, like business development is not new. It’s well established, but the folks who, what I’ve noticed is folks will have those roles in software as a service companies. And just not know how to navigate our ecosystem because they didn’t grow up in it.
\n\n\n\nSo I think for the folks from the outside coming in, it’s figuring out how to do that same work, the WordPress way. And for us in, it’s like, how do you embrace that, and learn, okay, well, how do we have to think about this? Like where do we have to grow up? And I think we are more than big enough. And I think that that idea, if there’s 50 today, there should be a thousand next year.
\n\n\n\n[00:22:26] Nathan Wrigley: If somebody was thinking, actually, do you know what I would like to pivot and become that person? I wanna become some sort of partnership company, whatever it may be. What would be some sort of key things that you think they should be doing today in order to set that business up, you know, move away from whatever it is that they’re doing and stray into partnerships.
\n\n\n\n[00:22:42] Jonathan Wold: To me, these types of roles always start with curiosity. Being someone who’s curious, and really looking for the wins. At its simplest level, it’s a mutual win between three parties. The customer first, like the audience that you’re trying to create value for. And then the two other parties that serve that same audience. There will tend to be common patterns of what that looks like. For instance, a product company is often looking for distribution. Like they want to get in front of a bigger audience. And hosting companies often have the distribution.
\n\n\n\nSo there, there’ll be some common patterns. Yet, I think there’s a lot of room for creativity, especially in these earlier days. And it’s just being open and curious and staying focused on who are we serving and what problem can we solve for them, and letting that kind of direct how you go.
\n\n\n\n[00:23:26] Nathan Wrigley: We’ve got a few minutes left. So I’m gonna pivot the conversation just for a few minutes. We’re gonna go to acquisitions and mergers. Some interesting news over the last few days that a company that I’m sure many of us have heard of called Delicious Brains has just recently sold to WP Engine with kind of looks like 90% of their product suite, which is really interesting. But over the last couple of years, lots and lots and lots.
\n\n\n\nAre you sanguine about this? Is this a good thing on the whole? Does it concern you that a lot is being bought by the same few companies? And at some point we’re gonna be left with, well, if you wanna do anything with WordPress, you’re gonna have to go with this hosting company or this other company.
\n\n\n\n[00:24:00] Jonathan Wold: I’m, very optimistic by nature. So in general, it’s like, yeah, I think that’s all great. There are always trade offs with things I like this in particular. WP Engine they’ve made some great acquisitions. We could have a whole discussion on the strategy behind this because I think, I think you’re gonna have less if we just sort of continue as we are, you’re gonna have, there’s not that many more Delicious Brains left, no pun intended.
\n\n\n\nSo it makes sense at a high level. Advanced Custom Fields fits their narrative, like the nature of some of the plugins and their suite fits the WP Engine narrative, this focus on developer tools, what they’re doing with Atlas. At a high level, it makes sense.
\n\n\n\nAlso, I wasn’t surprised and it makes sense to see Spinup separated from that, right. That’s what they said they wanna focus on. So I like it. In terms of concerns or thinking about the ecosystem broadly, one of the limiting factors I think we have right now is that it is difficult for folks from outside the ecosystem to invest in the ecosystem.
\n\n\n\nI think it also comes to a bit to that, like professionalizing. There is plenty of capital out there and, I’ll talk to founders who don’t know how to get to it. Like they’re building a WordPress business. And so there’s an interesting disconnect right now where if you’re from outside the ecosystem, they might not get it. Like, what is this WordPress thing? Like, how does this work? They’ll hear the market share stuff. And it’s like, okay, we wanna invest, but where do we do that? How do we do that? There’s some curious gaps at the moment.
\n\n\n\nI’ll put it this way. WordPress businesses in general, in my experience are quite undervalued. If you compare a typical WordPress business to a SaaS, the SaaS will get multiples of value, quite higher than the WordPress business. Where the WordPress business, if you look at it objectively is a stronger investment. So there’s a disconnect there where the reality is there’s a lot of opportunity for investors, and the challenge for them is like, how do we navigate this?
\n\n\n\n[00:25:43] Nathan Wrigley: Curiously, it feels to me like the more things that are acquired, the more need there will be for partnerships.
\n\n\n\n[00:25:50] Jonathan Wold: Yeah.
\n\n\n\n[00:25:50] Nathan Wrigley: It kind of feels like the two go hand in hand, if there’s hosting company X over there, who’s acquired all the things. And you’ve got a rival of one of their things. Fighting their marketing machine is gonna difficult.
\n\n\n\n[00:26:00] Jonathan Wold: It’s gonna be difficult.
\n\n\n\n[00:26:01] Nathan Wrigley: So need a partner that can help you get through that. Yeah,
\n\n\n\n[00:26:04] Jonathan Wold: Put one way the downside of too much consolidation is that you risk losing the innovation and the market is way more than big enough for new players to be coming in. There’s lots of sub ecosystems. I think in general, folks just need more help navigating and, as long as we keep seeing new folks come in, we’re gonna be just fine.
\n\n\n\n[00:26:23] Nathan Wrigley: Very last question and a curious little bit of a curve ball. You were talking about the market. The watch word there seems to be growth, growth, growth, the market’s growing. And yet very interestingly over the last month or so we had some sort of interesting data. This first data point where the market just took a tiny little bit of a dive, not 0.2% or something like that. Any thoughts in your head that the curve is beginning to go in the other way? The seesaw has finally tipped.
\n\n\n\n[00:26:44] Jonathan Wold: We have different sources of data.
\n\n\n\n[00:26:45] Nathan Wrigley: That’s right.
\n\n\n\n[00:26:45] Jonathan Wold: So there’s a whole discussion first about you know, what’s our basis for data. I think we could have an interesting discussion if we felt confident that that was the case. I’m working with, um, the HTTP archive on the Web Almanac project this year. And we’re about to have a new set of data in the next month or so. No particular thoughts. I think, sometimes we overreact. While I am an optimist, we will hit a point at some point.
\n\n\n\nI’m much more interested right now in focusing on like for that big swath of market we already have, how can we serve them better?
\n\n\n\nBecause that’s really where the growth is gonna come from. Is how do we help more people have success in WordPress? Because in general, there’s a lot of frustration, like lots of success, lots of things that are going well. When it’s not working though, where are people going? And they’re tending to go to the proprietary platforms. Which is fine, but at the end of the day, if we want a healthy open web, we need a healthy WordPress ecosystem. And there’s still plenty of work to do, regardless of what the numbers are saying.
\n\n\n\n[00:27:41] Nathan Wrigley: Jonathan Wold. Thank you very much for talking to me today.
\n\n\n\n[00:27:44] Jonathan Wold: Thanks for having me.
\nIt is often said that life, adventure, challenge, growth, etc, begins at the end of your comfort zone. Like all much-abused aphorisms, that is both true and not. Yes, growth comes from outside your comfort zone, but then your comfort zone just becomes bigger.
\n\n\n\nBefore I get ahead of myself though, I should introduce myself. Hi, my name is Akshat, and I am the founder of BlogVault, MalCare, WP Remote, MigrateGuru and AirLift. I have spent 12 years on a rollercoaster WordPress journey, building these solutions for high performance WordPress sites.
\n\n\n\nToday, I am going to tell you about my comfort zone. If you are wondering what WordPress has to do with my comfort zone, you’re about to find out.
\n\n\n\nIn the pre-BlogVault world, I was working at Citrix, doing kernel hacking for a product called NetScaler. This is as far removed from WordPress as you can possibly imagine. I was about to discover my new path rather abruptly.
\n\n\n\nOne fine day, The Coding Horror blog crashed. In case you are unfamiliar with this stalwart of the programming world, it is Jeff Atwood’s blog. Jeff Atwood is the founder of StackOverflow, another keystone of the programming community. If Jeff Atwood’s blog didn’t have backups, I thought, what about the legions of sites out there?
\n\n\n\nThus, BlogVault was born; its siblings mentioned above soon to follow.
\n\n\n\nWhen I created BlogVault, I wasn’t thinking about building for people. I saw a problem that I could fix, and created a solution for it. In fact, I understood so little about how people purchase products that every time someone bought a subscription, I thought it was a miracle.
\n\n\n\nObviously, magic wasn’t part of the equation, so I figured that I would have to actually meet people in WordPress. I needed to understand them, and why they were buying my product at all. This was a big step out of my comfort zone, by the way. I do not excel at meeting new people. That may be the understatement of the year.
\n\n\n\nEnter WordCamps.
\n\n\n\nNow, everyone knows that WordCamps are events of inclusion, bringing people from all walks of life together. I didn’t at the time, and attending my first few conferences was me actively putting myself out there. I volunteered at a few, and spoke at others. None of this came easily or naturally, because it was innately difficult to interact with strangers.
\n\n\n\n\n\n\n\nOver a few events, the discomfort became less and less, till it has gone entirely.
I met wonderful people and built lasting friendships. For instance, I attended a WordCamp Europe in Spain one year, and got in touch with a friend who lived in the country. We’d never met before, but we’d corresponded a few times. He and his wife came to pick me up, and they showed me around for 2 days. It is incredible that someone can have so much generosity for a virtual stranger.
\n\n\n\nOnce I crossed the hurdle of interacting with strangers, I started to understand that building a product cannot be done in a vacuum. It is important to consider the people who are going to use it, why they would use it, and how it solves their problems.
\n\n\n\nThe WordPress community helped me reframe our products in terms of value propositions. Our marketing evolved to be about creating and showcasing value, and solving issues. I also learned how to use the right metrics to measure interaction. I found myself moving towards a more analytical mindset.
\n\n\n\nThis was in stark contrast to how I started: with a gut-based approach and the joy of making. I pivoted quickly to add people into the mix. It feels great—almost romantic—to say we build for the joy of making, but it is not a viable business model unless you factor in people.
\n\n\n\nBlogVault is a great backup product, even if I do say so myself. MalCare is too. MigrateGuru is the stuff of dreams, even. But. BUT. AirLift isn’t. Not yet, anyway.
\n\n\n\nThese are all products that we have made for WordPress, and have continued to improve over the years. It took us ages after we built MalCare to actually release it.
\n\n\n\n\n\n\n\nIt wasn’t perfect, how could we possibly release it?
Eventually, I realized that this wasn’t the way to grow. And, I’m not going to lie, it took a lot to overcome this mindset. There were unexpected cheerleaders in every corner, and bit by bit, we were emboldened to take a leap of faith. Customers who loved our existing products encouraged us to let them try our new ones.
\n\n\n\nSlowly I developed the courage to be imperfect, and trust in the process. We moved forward with the certainty that we would make it better.
\n\n\n\nWordPress has been around for decades, and there are competitors on every level. This knowledge contributed to the desire to perfect our product. How will something that is less-than compete with established products in the market? I needed to develop a competitive mindset!
\n\n\n\nNot quite. WordPress is big enough for everyone to thrive. But more than that, it isn’t a dog-eat-dog world.
\n\n\n\n\n\n\n\nThe community doesn’t have a win-at-all-costs mentality.
People here have a lifestyle approach to business, without the hyper competitive spirit. It is a wholesome and largely ethical ecosystem.
\n\n\n\nI discovered that the competitive spirit I thought I needed to develop—which didn’t come naturally—wasn’t necessary. I could succeed and make a mark, without that trample-to-get-ahead mentality.
\n\n\n\n(If only I could stop using trite-but-true phrases as adjectives as easily.)
\n\n\n\n12 years ago, I started my entrepreneurial journey with BlogVault, a definite outsider to WordPress. While I have encountered the boundaries of my comfort zone many times over the years, WordPress has helped me push past them. Today, I can proudly claim to not only be part of this amazing community, but contribute to it in a meaningful way. It is now my comfort zone.
\nThe post Life At The End Of Your Comfort Zone appeared first on 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:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 03 Aug 2022 02: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:16:\"Akshat Choudhary\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"Post Status: Barriers to Contributing\";s: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=103614\";s: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/features/barriers-to-contributing/\";s: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:3377:\"TL;DR: Small teams have common barriers to contributing to Five for the Future. Making efficient use of their time and team members is hard when tooling and communication can soak up the hours. Learning how to contribute — and keeping up with WordPress core — makes it hard to get started and sustain effective contributions. How much of this has to do with Trac/SVN and the Make WordPress Slack “firehose,” I wonder?
\n\n\n\nIn Post Status Slack last month, Cory got a number of responses when he asked,
\n\n\n\n\n\n\n\n“As a manager or owner of a WordPress company (or a WP professional), what are your obstacles/frustrations/challenges for contributing to Five for the Future?”
A helpful pattern emerged in the responses, which I hadn\'t considered previously.
\n\n\n\nPatrick Garman asked for clarity on what\'s wanted and what\'s actually being done for 5ftF. He also shared how tasking a dedicated staff member with a half day to contribute each week was far more effective than spreading it around his team on a totally voluntary basis. Sharing best practices for efficient contribution widely would be valuable.
\n\n\n\nJustin Sainton agreed that “sustainable” contribution for a 1-10 person agency needs a good working model, and he hasn\'t found one yet. Barriers “include infrastructural issues” on both ends — the contributor and project.
\n\n\n\nTimi Wahalahti also spoke to time management challenges in a small 8-person agency.
\n\n\n\nThomas Maier noted the challenges of keeping up with the firehose of WordPress core communication and information:
\n\n\n\n\n\n\n\nKeeping up to date with something happening in a team I am interested in working in already needs more than 5% of my and my companies time. That’s the burden for us. I don’t feel that there is a chance to make contributions that count to the project that only need 1-2 hours per week. Assuming that publishing code on GitHub or blogging about solutions don’t officially “count.”
Brian Coords also related to feeling like a few hours a week is not helpful or accomplishing much. He also opined that many employers might rather just donate money to a non-profit at arm\'s length from any interested parties in the WordPress community.
\n\n\n\nOne takeaway here for me is that learning/teaching how to contribute and keeping up with WordPress core is hard enough to make it feel like you can barely get to square one as a contributor with a few hours a week.
\n\n\n\nHow much of this has to do with things like Trac/SVN and the WordPress Slack “firehose,” I wonder?
\";s: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, 02 Aug 2022 22:03: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: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:84:\"Post Status: Laura Nelson on WordPress and Email Marketing — Post Status Draft 122\";s: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=101223\";s: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:76:\"https://poststatus.com/planet/laura-nelson-on-wordpress-and-email-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3230:\"Laura is the Content Marketer at WooCommerce — a popular email marketing plugin for WordPress. She’s been working in the WordPress space for the past eight years, with experience in both agency and in-house marketing teams.
\n\n\n\nLaura Nelson and Cory Miller talk about creating content for email marketing.
\n\n\n\n\n\n\n\nGravity Forms is a powerful form builder for WordPress and the #1 choice for businesses and web professionals across the globe. Its vast array of features, intuitive drag-and-drop form editor, and extensive ecosystem of add-ons, ensure customers can design beautiful, intelligent, and accessible forms for any project requirement.
\nThe 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.
Defining the parameters of what a WordPress or WooCommerce developer is has never been cut and dry.
\n>> The post What is a WordPress Developer with Ebonie, Lisa, Kathy and Robbie 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, 02 Aug 2022 09:43: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: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:79:\"Post Status: Does “Full-Site Editing” Need a New, “User-Friendly” Name?\";s: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=103515\";s: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:92:\"https://poststatus.com/wordpress/notes/does-full-site-editing-need-a-new-user-friendly-name/\";s: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:1821:\"I\'ve been thinking about this question and the others related to it that Josepha Haden Chomphosy posted last week. There\'s been a strong comment discussion so far, and I discovered what my view on it is now by noticing what is going on in the grammar of “Editing” versus “Editor.”
\n\n\n\n“Full Site Editing” ends with a gerund, which is a verb that\'s used like a noun, but even more specifically: “a gerund names or identifies actions, states of being, and states of mind rather than people, places, things, and ideas.”
\n\n\n\n\n\n\n\nA gerund isn’t a verb showing what someone or something is doing; it is the thing itself that’s doing something or being something or having something done to it.
“The … Editor” is a noun describing a thing that is also a place. You can “go into the editor.” But you “go into editing mode” — a change of state, not a different place. You acquire different capabilities.
\n\n\n\nMaybe eventually full site editing mode in some WordPress themes will mean you can edit layout (presentation) and content comprehensively. Maybe there will still need to be an option to zero in and focus on one piece of content. Currently, these are two distinct things that feel very different even in FSE themes. Complicating matters, classic, block, and hybrid themes without FSE are totally different user experience contexts.
\";s: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, 02 Aug 2022 03:38:53 +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:89:\"WordPress.org blog: WP Briefing: Episode 37: The World of WordPress on World Wide Web Day\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=13198\";s: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:91:\"https://wordpress.org/news/2022/08/episode-37-the-world-of-wordpress-on-world-wide-web-day/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:23625:\"In the thirty-seventh episode of the WordPress Briefing, WordPress users and contributors reflect on how WordPress has changed their understanding of the web as we celebrate World Wide Web Day.
\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: Beatriz Fialho
Production: Santana Inniss & Chloé Bringmann
Song: Fearless First by Kevin MacLeod
Guests:
\n\n\n\nDiverse Speaker Training Group
\n\n\n\nSupport Underrepresented Speakers at WordCamp US
\n\n\n\nCall of Speakers – WordCamp Asia 2023
\n\n\n\nRefocusing the WordPress App on Core Features
\n\n\n\nWordPress.org Homepage and Download Redesign
\n\n\n\n[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. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\n[Josepha Haden Chomphosy 00:00:39]
\n\n\n\nToday is one of my favorite niche holidays – World Wide Web Day – which serves to raise awareness about the origins of the World Wide Web project. WordPress, as part of Web 2.0, only ever had a chance to exist because the web, as we have come to know it exists. So in order to mark this nerdy day on the WP Briefing, I invited a number of community members to share a bit about how WordPress has been a part of their lives.
\n\n\n\nBut first, let’s do some introductions.
\n\n\n\n[Adam Warner 00:01:07]
\n\n\n\nMy name is Adam Warner, and I’m originally from a small town in west Michigan, now residing in Orlando, Florida.
\n\n\n\n[Alice Orrù 00:01:15]
\n\n\n\nMy name is Alice Orrù. I’m Italian. I was born in the beautiful island of Sardinia, but I’ve been living in Spain in the province of Barcelona for 10 years.
\n\n\n\n[Dee Teal 00:01:26]
\n\n\n\nMy name is Dee Teal; Dee is short for Denise. I’m from New Zealand, but I live In Melbourne.
\n\n\n\n[Femy Praseeth 00:01:33]
\n\n\n\nYeah, my name is Femy Praseeth. I was born and raised in India and now live in San Jose, California, with my family and cuddly Doodle.
\n\n\n\n[Jill Binder 00:01:41]
\n\n\n\nMy name is Jill Binder, and I’ve just moved back to Vancouver, Canada.
\n\n\n\n[Mary Job 00:01:47]
\n\n\n\nMy name is Mary Job. I’ve been using WordPress since 2015, and I’m from Nigeria. I’m from the Western part of Nigeria. Ijebu precisely.
\n\n\n\n[Oneal Rosero 00:01:57]
\n\n\n\nYes. My name is Oneal Rosero. I am from the Philippines and I’ve been using WordPress since 2007.
\n\n\n\n[Theophilus Adegbohungbe 00:02:06]
\n\n\n\nThank you. My name is Theophilus Adegbohungbe . And I’m from Ilesa, Osun State in Nigeria.
\n\n\n\n[Ugyen Dorji 00:02:14]
\n\n\n\nMy name is Ugyen Dorji and I’m from Bhutan. And I’m working with WordPress for more than five years.
\n\n\n\n[Josepha Haden Chomphosy 00:02:22]
\n\n\n\nOne of the things I enjoy the most about being part of any community is being able to see how people change and grow over time as they learn and gain confidence in their own expertise. So a favorite early question is naturally, ‘How has WordPress changed your World?’
\n\n\n\n[Alice Orrù 00:02:37]
\n\n\n\nWordPress changed my world in many ways. But, uh, starting from the moment, it allowed me to become part of a global connected and welcome community. I started using WordPress as a blogger many, many years ago, but it was in 2015 that I started working behind the scenes of WordPress with a plugin company.
\n\n\n\nAnd that was the moment when everything changed, basically, because I realized that WordPress was much more than a CMS for creating websites. It was a world full of opportunities for networking, making new friends and walking a new professional path as well.
\n\n\n\n[Ugyen Dorji 00:03:15]
\n\n\n\nDuring one interview, I was asked many questions about WordPress and although I had a basic understanding of WordPress, I struggled to give detailed answers.
\n\n\n\nAfter that interview, I resolved to develop my skills and learn as much about WordPress as possible. A few months passed and I received a call from ServeMask In, [who] had developed a plugin called All-in-One WP Migration plugin. They offered me a position which fulfilled my wish to work with WordPress full time.
\n\n\n\nAnd because of that, I am now an active contributor to the WordPress community as bread and butter, with the best career in the world.
\n\n\n\n[Theophilus Adegbohungbe 00:04:03]
\n\n\n\nIf you are very familiar with my country, Nigeria things here, it’s not as smooth as it is in other parts of the world. That is, when you are done in school in my university, you have to find means of surviving yourself. There is nothing like the government have work for you. There is nothing like you finish our institution and you get job instantly. So it’s very tough here. And, year by year, schools keep producing graduates with no companies to employ them and no government job again as well.
\n\n\n\nSo I personally, I was able to gain freedom from this with the help of WordPress.
\n\n\n\n[Femy Praseeth 00:04:51]
\n\n\n\nWordPress completely changed my work life. I started working independently. I started freelancing with agencies and designers and, uh, building websites from their web designs. And this was around the time my son was born. Actually, he was in elementary school and I think this was around 2014 or so. I started working remotely when remote was not even a thing.
\n\n\n\nAnd there were very few companies that let you work from home and remote was not a mainstream thing at all, but with WordPress, I could set my own working hours while my son was in school.
\n\n\n\n[Josepha Haden Chomphosy 00:05:29]
\n\n\n\nAnd of course, my preferred follow-up question of, ‘How did you hear about us?’ or ‘How did you connect to this global community?’
\n\n\n\n[Oneal Rosero 00:05:36]
\n\n\n\nYes, actually what I love about WordPress is that it’s a community. It’s not a business. It’s not a company. It’s a community. It’s a community that’s always ready to help support, teach and encourage people. That’s how I felt when I joined the community. There’s always somebody who has your back.
\n\n\n\nThere’s always somebody who’s going to guide you. There’s always an expert who will take your hand and lead you into the beauty that is WordPress.
\n\n\n\n[Adam Warner 00:06:05]
\n\n\n\nThe way that I connect with the global community these days are one, of course, is .org Slack. Another of course is Twitter as there’s a very active WordPress community there.
\n\n\n\nAnd then with WordCamps all over the globe. I’m lucky enough to have been able to travel to several hundred WordCamps through the years in the US and abroad. And that’s one of the most rewarding parts is meeting people from all over the world and you see really how small and the world really is and how similar we really all are.
\n\n\n\n[Theophilus Adegbohungbe 00:06:39]
\n\n\n\nSo, not until 2020. I don’t know if you know this lady, a very vibrant lady in WordPress. She’s from Nigeria; her name is Mary Job, and she’s really promoting WordPress here. So it was through her that I got to know about the community. Yes.
\n\n\n\n[Jill Binder 00:06:54]
\n\n\n\nMy work is the global WordPress community. So we hold our three programs for the global WordPress community, and we are always trying to reach more and more countries. For quite a while, it was very North America-heavy, and then I made some efforts to expand. And it’s very exciting that this year, some contributors in our team have actually launched an Asia Pacific branch of our group.
\n\n\n\nAnd so we have two meetings every other week where we have the America/Europe and the APAC, and we’ve also been able to reach other countries as well, but we typically reach something like between 20 and 50 countries a year, depending on the year. So a hundred percent global. Yes.
\n\n\n\n[Josepha Haden Chomphosy 00:07:39]
\n\n\n\nHow has WordPress, either the CMS or the project, made you feel more connected? And are there any surprising connections that came from WordPress?
\n\n\n\n[Dee Teal 00:07:47]
\n\n\n\nI guess the surprising connections I think that have come from WordPress have been the fact that I feel like I’ve got friends all over the world. And a lot of those have come out of community involvement and from contributing. That I could go to a, a meetup pretty much anywhere in the world and probably find somebody I know, or at least a second degree connection of somebody that I haven’t, you know, that I might not have met, but know somebody that I know. And certainly that happens fairly regularly.
\n\n\n\n[Mary Job 00:08:13]
\n\n\n\nWordPress. The WordPress project, the community, has made me feel connected in a huge way, because I am literally surrounded by everything WordPress. So I like how, when you meet somebody who does WordPress, there’s this instant, ‘Oh, we’re brothers,’ or ‘Oh, we’re sisters!’ You know? There’s that feeling? That’s how I feel.
\n\n\n\nSo when I see somebody who does WordPress, as I do, I’m like, ‘Oh yeah, we’re, kin.’ You know? We are family. That’s how I feel when I meet people who do WordPress. And I’ve met quite a number of people who do WordPress from like around the world. Like I have a friend here, he’s from the Benin Republic, and we host started a dinner on Friday night and one of my guests was asking me, ‘How did you guys meet?’
\n\n\n\nI was like, ‘Oh yeah, we work in the same WordPress ecosystem.’ He attended our WordCamp, we became friends, and we just literally became really good friends. So I have tons of people that I’ve met like that I hold in high esteem.
\n\n\n\n[Ugyen Dorji 00:09:12]
\n\n\n\nWordPress Meetups are the seeds that lead to the growth of WordPress communities. WordCamp is a platform for plugin and theme developers to meet WordPress users and website developers. It’s a great environment where many incredible discussions about WordPress takes place. With each WordCamp there is a “tribe” meeting, where I think people [can] get more connected. It’s a fantastic opportunity for aspiring computer engineers, generators and get to showcase their talent and meet each other.
\n\n\n\n[Alice Orrù 00:09:51]
\n\n\n\nOn the project level, it has given me the opportunity to feel like an active part of a global project. The idea that I can give my contribution to making the web a better place – it’s amazing. And I do so with the Translation team, so making WordPress accessible to all the people that use the core plugins and themes in Italian, and prefer to do that in Italian.
\n\n\n\n[Josepha Haden Chomphosy 00:10:18]
\n\n\n\nWhat area of the WordPress world is most important to you?
\n\n\n\n[Jill Binder 00:10:21]
\n\n\n\nI have a little bit of a passion for diversity in tech and diversity in WordPress, specifically around events. And so, here’s a chance to name the three programs that we’ve been working on this year. So as mentioned a few times, we have our Diverse Speaker Workshop that helps people go from not even having the thought that people could step up on stage.
\n\n\n\nAnd then the second program is because of the pandemic. There was no longer the straight path from taking our workshop to speaking, because we used to hold them or people used to hold them for their WordCamps and meetups. And so it was like, okay, you’ve taken. Apply for our next WordCamp or meetup. But during the pandemic, that wasn’t a thing.
\n\n\n\nSo we have this amazing channel that we welcome everyone to join, allies and people from underrepresented groups who are interested in speaking or interested in supporting people and speaking. And that’s the Diverse Speaker channel diverse-speaker-support channel on the Make WordPress slack.
\n\n\n\nAnd the third program is, and we, we went through a name change recently. So I’ll try to remember the new change it’s Organizing Inclusive and Diverse WordPress Events. And this is for WordCamp and meetup organizers to learn. We’ve learned over the last couple years, how important it is to create inclusive spaces and be good allies.
\n\n\n\nBut how do we actually do that? And a few of us created a very action oriented workshop in 2019 for WCUS, and that is now the basis of the work that we are bringing to people and people are loving it.. We’ve had people report a 40%, self-report 40%, increase in feeling prepared to create an inclusive event from before and after taking that workshop, which is super cool.
\n\n\n\nYeah. So, that’s my passion.
\n\n\n\n[Oneal Rosero 00:12:13]
\n\n\n\nI really love helping the WP Diversity team. I love running the workshops. I love running the workshops for myself, because I used to do training for software back before the pandemic. I used to train up to a thousand people a year in person, sometimes like 500 people in a room at once.
\n\n\n\nBut of course I had to shift. I had to pivot to online training, which is what the training team has brought for me. And the focus on the diversity. I like running the workshops. I like running workshops for different groups, different countries, because it’s nice to meet new people. It’s nice to hear about their culture, about the limitations that people have in Africa with connectivity.
\n\n\n\nSo they, they resort to using WhatsApp on their phone in order to do a meetup. That’s how they do their, their meetings, their discussions. It’s unlike other countries where we can do video calls. They have to use their mobile phones because connectivity isn’t accessible.
\n\n\n\nPlaces like in the Philippines that get affected when it starts to rain a little bit, we lose our internet. So we have backups and our backups have backups. So there are many things that you learn that are different when you’re living in the city, when you’re living in the provinces, in the country. So it’s so many things that you learn about people and how they’re able to adapt.
\n\n\n\n[Adam Warner 00:13:35]
\n\n\n\nEnabling end users to reach their goals. And whether that means participating in contributing to the software, to the Core software itself, in terms of UI/UX usability. That can include participating in the community and sharing your knowledge proactively with users who may be new to the platform, or have used WordPress for a while, but now want to step up their game, get a little deeper into using their websites as a tool for growth, for whatever business that they’re in. So, I mean, overall, the, the most important part of the WordPress world to me are the end users. And, you know, there, there is this quote unquote inner circle of WordPress community people. People who are involved in .org, people who contribute to the software, people who contribute to the 20 plus make.wordpress.org teams.
\n\n\n\nThose we have to keep in mind, are not the average user by and far. They are not the typical user that hears the word WordPress and then goes out and searches it and then has to figure out how to use it. So I think user experience is probably the most important part for me and making sure that any of that innate knowledge that we have in that inner circle of WordPress because many of us have been using it for so long, keeping in mind that is not the norm. And it’s not the scale at which WordPress is used and, and making sure we translate complex concepts down to a layperson’s terms that might not be as familiar.
\n\n\n\n[Josepha Haden Chomphosy 00:15:17]
\n\n\n\nOne of the things that I have always found so fascinating about the web and WordPress’ role in it is how it has made the world simultaneously smaller and bigger. By giving voices to the voiceless we help each other find our community niches regardless of where they are in the world. Some of your closest friends could be people you would never meet in your own neighborhood. Well, let’s hear what some of our community members had to say about that.
\n\n\n\n[Dee Tea 00:15:42]
\n\n\n\nI think the thing that has been most empowering is, is coming into the project either in terms of contributing time and efforts to the community, which is where most of my contribution has been – has always been about this is a really cool thing, and I really want to build this.
\n\n\n\nAnd so I’ll put my time and efforts into building WordPress. Not for me, but because I see its value and I see its community and I see that the contribution that it’s making to the world and I, and that’s really important. But finding that on the other side of that was a huge amount of personal benefit for me in my career, in the friendships that I’ve made.
\n\n\n\nBut I feel like if I had been approaching the community with, I want a better career, I wanna meet all of these people and I want, and I want all of this. From, “I want” for me, instead of, I want for this project, for the community and effectively for the world with that, you know, that whole democratized, the democratizing of publishing is this thing that serves the world.
\n\n\n\nI think that’s been the key for me is that I absolutely have reaped amazing benefits from it, but it came out of that sense of, I see this value here and I want to contribute to that because it’s gonna have value, not just for me, but for a whole slew of people. And so, uh, you know, for much, much bigger impact than just on me.
\n\n\n\nAnd so I think that’s the important thing for me is that sense of, if you approach it with that attitude of what can I do to help? It’s amazing what you will find yourself helped with in return.
\n\n\n\n[Josepha Haden Chomphosy 00:17:24]
\n\n\n\nI hope that you enjoyed this tour of WordPress in the World Wide Web. I want to share a big thank you to all of the folks who contributed to our little WordPress Briefing celebration of World Wide Web Day today.
\n\n\n\nAnd that brings us now to our small list of big things. So firstly, we’ve got a couple of updates from our upcoming flagship events. WordCamp US has announced a speaker support fund specifically for historically underrepresented speakers at the event. You can donate to the fund on the page if you’d like, and there are also directions on how to request support, if you are part of an underrepresented group.
\n\n\n\nFrom the folks over at WordCamp Asia, the call for speakers is live. That’s taking place in February, 2023. But it’s never too early to brush up those presentations and get them submitted.
\n\n\n\nNext big thing is that there are some changes coming to the WordPress mobile app. A lot of the Jetpack functionality will be removed from it, so this is going to have a little bit of an effect on daily users of the app, but it will also have an effect on regular contributors. I’ll have a link to the full write up in the show notes so that you don’t have to guess or hold it all in your memory.
\n\n\n\nAnd finally, this excellent design that you see on wordpress.org/news is finally making its way out to the next parts of the wordpress.org website. Before you know, it, there will be a fresh looking homepage as well as few other pages and then… to infinity and beyond (or something like that).
\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 next up I’ll be taking just a mid-year break from the podcast. And so the next time that I actually see you again, will be in September.
\";s: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, 01 Aug 2022 23:15:02 +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: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:92:\"Do The Woo Community: dev_life snippet: Back-end, Front-end WooCommerce Performance Insights\";s: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=72483\";s: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:72:\"https://dothewoo.io/back-end-front-end-woocommerce-performance-insights/\";s: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:436:\"When it comes to performance on a WooCommerce site, without proper diagnostics, you\'re wasting your time quite often.
\n>> The post dev_life snippet: Back-end, Front-end WooCommerce Performance Insights 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:\"Mon, 01 Aug 2022 09:42: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: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:52:\"WordPress.org blog: People of WordPress: Carla Doria\";s: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=13201\";s: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/07/people-of-wordpress-carla-doria/\";s: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:10299:\"In this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature Carla Doria, a customer support specialist from South America on how WordPress opened up a new world for her, and gave her the ability to help the local community.
\n\n\n\nFor Carla, working with WordPress is a vital part of her life. It gave her a career and a community, in which she she would organize the first WordCamp in her city, Cochabamba, and the first in Bolivia.
\n\n\n\nCarla studied industrial engineering and has a master’s degree in environmental studies.
Her first experience with WordPress was when she decided to start a small business designing and selling cushions and bedclothes. While Carla sat in the small store she had rented, hoping that people stopping at the shop windows would step in to buy something, she decided she needed to create a website.
Carla had no budget to hire somebody, but she felt confident she could learn things on her own.
\n\n\n\n\n\n\n\n“Learning to use WordPress requires no code skills or a technical background. It needs an adventurous and playful spirit.”
Carla Doria
She had always been studious, and decided she would figure out how to build a website herself. Carla ended up building a simple blog with WordPress. At the time, she didn’t even have a budget to buy a custom domain, so she used a free subdomain.
“Learning to use WordPress is easy. It requires no code skills or a technical background at all. It only needs an adventurous and playful spirit,” said Carla
There were no profits, and any income mainly went to pay the store’s rent. At the time, her previous company contacted her for a job opening that matched her profile. Carla needed that income and decided to closed the store and forget about being an entrepreneur.
\n\n\n\nBack in employee mode, Carla started her new job as a technical writer for a software development company. Since Carla had completed her master’s degree in the UK, she was proficient in English. Her close affinity for computers and technology made it easy for her to translate complex software jargon into simple tutorial steps.
\n\n\n\nAs Carla got more interested in technical writing and started to improve her writing skills. This reconnected her with her previous enthusiasm for writing, and she decided to channel that interest into a blog.
\n\n\n\nCreating her blog helped her become more familiar with WordPress and building websites. In 2015, Carla blogged about writing, her thoughts, book reviews, and everything that came to mind.
\n\n\n\nThrough looking for answers to specific issues using her WordPress blog, Carla found the support forums a useful place to go. Soon she realized that she could also help answer other people’s questions.
\n\n\n\nCarla began checking the forums as a hobby. She liked that she was able to help people and learn more while doing so.
\n\n\n\nInstead of surfing social media during her work breaks, Carla focused on checking the WordPress forums. Through this she learnt about a support job in one of the global firms.
\n\n\n\nShe felt the job was made for her and was excited to support people in building their websites with WordPress. The role offered the possibility to work remotely and travel while still working.
\n\n\n\nAfter three years as a technical writer, her career felt stuck. She was certain she did not want to return to any job related to industrial engineering.
\n\n\n\nCarla did not get through the selection process the first time. But after nearly 18 months between three applications and learning HTML and CSS, Carla finally secured a support job in 2016. With this job, WordPress became her main source of income.
\n\n\n\nOn the job, Carla learned about the WordPress communities around the world and WordCamps. But when somebody asked about the WordPress community where Carla lived, she didn’t know what to say. Was there a community?
\n\n\n\nShe discovered no local group existed, so she researched what was needed to setup a meetup. Carla discussed the idea with others, but hesitated as she thought it would require an expert WordPress developer to organize.
\n\n\n\nBut after trying to gauge interest, Carla realized that the only way to find community members was to start a community. In 2017, the WordPress community in Cochabamba was born.
\n\n\n\nThe group has had ups and downs, probably similar to any other community. Although Cochabamba is not a big city, they had issues finding a location that was free and available to anyone who wanted to join. People came with different levels of knowledge, from people with vast experience with WordPress to people with no experience but who wanted to learn.
\n\n\n\nThe community grew during the pandemic, as meetups went online and people from other cities in Bolivia were able to attend. After restrictions were lifted, there was a lot of excitement amongst members to meet each other in person.
\n\n\n\nThe community also helped Carla to develop a new skill in public speaking. She applied to be a speaker at WordCamp Mexico 2019 and 2020, WordCamp Guayaquil 2019, and WordCamp Colombia in 2020. Her confidence grew while she enjoyed connecting with other communities and meeting people who were on similar pathways. Not all of them were developers, as she had presumed. Many, like her, started out as bloggers.
\n\n\n\nFinally, after three years, Carla applied to organize her first WordCamp in 2021 in Cochabamba. She had never imagined organizing any WordCamp, and through this having the experience to talk to sponsors and contact companies, and lead a group of people with different talents and backgrounds. Carla felt she had learnt so much from the experience.
\n\n\n\nThanks to WordPress, Carla found a job she enjoyed, was able to work remotely, and help build something in her community to help people learn skills and find career opportunities.
\n\n\n\nCarla feels grateful for all she has been able to do thanks to WordPress. She said: “WordPress has led me to find good jobs. It also has allowed me to contribute to a community of friends that love learning about WordPress.”
\n\n\n\n\n\n\n\nHelp share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the People of WordPress series.
\n\n\n\nThanks to Alison Rothwell (@wpfiddlybits), Abha Thakor (@webcommsat), Larissa Murillo (@lmurillom), Meher Bala (@meher), Chloe Bringmann (@cbringmann), and Surendra Thakor (@sthakor) for work on this feature, and to all the contributors who helped with the series recently. Thank you too to Carla Doria (@carlisdm) for sharing her experiences.
\n\n\n\nThank you to Josepha Haden (@chantaboune) and Topher DeRosia (@topher1kenobe) for their support of the People of WordPress series.
\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
\nIt’s easy to get lost among a sea of Cover, Group, and Paragraph blocks while navigating the block editor’s List View. Clicking around wildly will generally surface the block you’re seeking, but it’s not efficient or intuitive. Gutenberg contributors have some ideas and prototypes aimed at giving the List View more context.
\n\n\n\nRich Tabor proposed a solution where users can double-click to rename a block within the list, giving it a unique identifier. Gutenberg developer Dave Smith created an experimental PR that adds custom labeling/naming of blocks in the List View. It currently works for Group blocks only. Tabor posted a demo to Twitter and the response was overwhelmingly positive.
\n\n\n\n \n\n\n\n“Custom block labels in the List view is a must-have,” Chris Bell commented on the original proposal. “It improves productivity and adds psychological order/control over the layout.
\n\n\n\n“I think popovers should only be used for extra long edge-case custom labels as I imagine most labels will be 2-3 words max.” He posted an example of what that might look like.
\n\n\n\nExtra long labels would simply be truncated to maintain the width of the List View:
\n\n\n\nSmith posted a list of questions regarding the technical implementation he proposed:
\n\n\n\nalias
attribute the best place to store the data?ENTER
-to-submit mechanic?Contributors are currently testing and weighing in on these questions. Smith recommended progress on the feature wait to align with the solution in another active ticket that seeks to add a metadata attribute to blocks, allowing section naming and future semantic meta information. Once that is resolved, custom labeling for blocks in the List View will have a more straightforward technical solution.
\n\n\n\nIn the meantime, Gutenberg 13.7 added a related update as a first step that improves navigation in the List View. It will now automatically display Heading content for the button label text when available.
\n\n\n\nIf you are using the Gutenberg plugin, this is available right now in the most recent update. Custom labels will be coming next to provide a clearer overview of other types of blocks and make page building/editing much easier.
\";s: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, 29 Jul 2022 20:23: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: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: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:54:\"Post Status: Post Status Picks for the Week of July 25\";s: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=103385\";s: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/post-status-picks-july-25-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:2581:\"Syntax.fm has an interview with Syed Balkhi about Awesome Motive, how WordPress and PHP are viewed by developers, and his charity efforts. The WP Minute features Amber Hinds on Equalize Digital’s first exit. Sean Blakeley talks about transitioning a large agency over to Gutenberg at the WP Tavern‘s Jukebox.
Get our weekly WordPress community news digest — Post Status\' Week in Review — also available in our newsletter.
And don\'t miss the latest updates from the people making WordPress. We\'ve got you covered with This Week at WordPress.org.
WebP, an image format developed by Google, which is intended to replace JPEG, PNG, and GIF file formats, will soon be generated by default for new JPEG image uploads in WordPress and used for website content. The main work for this feature was committed to core for inclusion in the upcoming WordPress 6.1 release.
\n\n\n\nThe initial proposal was revised after significant critical feedback. The most notable changes include automatically generating WebP versions of only core image sizes, keeping secondary (WebP) sub-sizes only if they are smaller than the primary MIME type, and only generating WebP images for image sizes that are intended for use in user-facing front-end content.
\n\n\n\nDespite a raft of revisions, and filters to control or disable WebP uploads, the proposal remained controversial. Contributors continue to report issues after testing. Many still have reservations about whether this should be opt-in or on by default.
\n\n\n\n“When converting medium-resolution photographs (approx 1600px – 2500px on the long edge), WebP files are often larger than the JPEG equivalent,” WordPress developer Mark Howells-Mead commented on the main ticket for WebP work. “(In my tests using my own photography, in around 60% of cases.) This change might make the ‘modern image format’ test of Page Speed Insights happy, but enforcing WebP by default on sites which use a lot of photography will often cause longer image loading times.”
\n\n\n\nSome developers are supportive of the change but prefer for it to be off by default when it is first rolled out, to allow the ecosystem to prepare for the change.
\n\n\n\n“I definitely see it as a big advantage to add Core support for additional MIME types for sub-sized image files,” Matthias Reinholz said. “But I can’t see adding conversion to a specific other file format as preferred behavior. This may help to optimize the market position of WebP but it will also be a serious threat to plugin authors and existing larger websites that do not pay attention to this change.
\n\n\n\n“Therefore, I’m questioning why this functionality should be activated by default at this stage. IMHO, it should be opt-in only. Plus ideally, we would already start to think about adding further image formats to be supported by this feature.”
\n\n\n\nNerdPress founder Andrew Wilder created a separate ticket urging contributors to consider making the feature opt-in, but the ticket was closed and conversation directed back to the main ticket so as not to splinter the discussion.
\n\n\n\n“Making these new features opt-in instead of opt-out would be the best way to be cautious about potential impacts,” Wilder said.
\n\n\n\n“There have been many requests for this to be opt-in (as well as some asking for a setting on the Media page, rather than only a filter for developers). So far there hasn’t been any open conversation about why that’s not being taken into consideration.”
\n\n\n\nThe notion that WebP by default should be opt-in was summarily dismissed and the conversation was not revisited before the changes were committed.
\n\n\n\n“The feature will have widespread benefits for users by opting in core sizes (to start) – if it were entirely opt-in it would have little impact – or benefit,” Google-sponsored Core Committer Adam Silverstein said in response to opponents.
\n\n\n\nIn response to suggestions that this feature ship with a UI for enabling it on the media page, Silverstein said, “We have discussed both suggestions in chats and issues with mixed responses. Project philosophy is regularly mentioned as aligning with the current approach.”
\n\n\n\nThe ticket remains open awaiting patches for a few loose threads on the technical implementation. Contributors have continued to chime in with additional concerns.
\n\n\n\nThe Performance team has a new blog where people can follow updates on their current projects and proposals. Now that the main WebP work has been committed, the next steps will discussed in future meetings with notes posted to the new Core Performance 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:\"Fri, 29 Jul 2022 17:47:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\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:113:\"Post Status: “We’re not a small village anymore.” A Conversation with Kim Lipari — Post Status Draft 121\";s: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=103274\";s: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://poststatus.com/not-a-small-village-anymore-kim-lipari/\";s: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:4561:\"WordPress as an economy or ecosystem is big, but the community and culture at its heart still feel small. Have we taken the time to really absorb the change that\'s come over the past decade? What questions should we be asking about what got us here and where we\'re going or want to go?
Estimated reading time: 1 minute
\nKim Lipari is our guest for this episode of Post Status Draft. Kim started building her career in WordPress over ten years ago, and her agency, Valet, is almost that old. WordPress isn\'t a small village community anymore, says Kim, but we still talk about it as if it is. That tightly knit community is still there because — not in spite of — incredible growth.
\n\n\n\nBut what does the fact of growth mean for a small village culture? Can it turn into an enclave or cult? Is the language of a small village still an appropriate language for leadership? Do we need to act more like we\'re a busy city — and make an effort to get to know our newer neighbors\' stories? Can we keep (let alone scale) the values, culture, and kindness of a healthy small community as we grow?
\n\n\n\n\n\n\n\nWP Engine is the WordPress Digital Experience Platform that drives your business forward faster. WP Engine makes WordPress easier and faster. It does the heavy lifting so you can focus on your core business and win online.
\nThe 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.
The WordPress Themes team is poised to change its guidelines on remote hosting Google Fonts and is once again strongly urging theme authors to host their fonts locally. Yoast-sponsored contributor Ari Stathopoulos published an update today to answer some questions the team has been receiving about fonts in themes:
\n\n\n\n\n\n\n\nHistorically, WordPress themes hosted in the w.org themes repository were not allowed to use third-party resources. This included images, javascript files, CSS files, webfonts, and other assets loaded from a remote server.
Google fonts was an exception to this rule because, at the time, there was no reliable way to implement locally-hosted webfonts, and typography is an integral part of a theme’s design.
Google fonts, however, can no longer be considered an exception to this guideline because of the GDPR and privacy implications.
The team is responding to a recent German court case, which fined a website owner for violating the GDPR by using Google-hosted webfonts. This case spurred a few other threats against website owners and many questions for the Themes team.
\n\n\n\nWhat was previously a strong recommendation from WordPress.org is now a warning that guidelines will be changing imminently.
\n\n\n\n“A theme should not be allowed to use external resources,” Stathopoulos said. “The guidelines right now allow for remote Google fonts, but that will probably change soon. If the theme is using external assets, then yes, it should call a privacy function and ensure that these assets don’t get loaded without the user’s explicit consent.”
\n\n\n\nA ticket for updating WordPress’ default themes to load Google fonts locally has a patch but the milestone is set for WordPress 6.1. This will make all the core themes GDPR compliant but will not arrive until October.
\n\n\n\nSome theme authors saw the writing on the wall a few weeks ago and have been working to update their themes to load fonts locally.
\n\n\n\n \n\n\n\n“I’ve decided to do this too,” Rough Pixels founder André Jutras said. “Although a few themes have a font-choosing option in the Customizer with the full Google selection. This is going to be hard to change with existing users that use it. My new theme will definitely have local fonts.”
\n\n\n\nOffering font selection for users inside the theme is not as straightforward as simply including one or two fonts bundled with the theme.
\n\n\n\n“I’ve been trying to do the same with Blockbase,” Automattic developer Jason Crist said. “But Blockbase ships with a LOT of fonts to choose from so it’s been a bit of a unique challenge.”
\n\n\n\nIn 2020, the Themes team created a package that helps theme authors host their webfonts locally. It was created in anticipation of removing Google Fonts as the exception to the rule prohibiting the use of CDNs to load assets.
\n\n\n\nBunny Fonts are are an alternative to Google Fonts that some plugin authors have on their radar now that some European jurisdictions are cracking down on Google-hosted fonts. It is an open-source, privacy-first web font platform with no tracking or logging and is fully GDPR compliant. Bunny Fonts is compatible with the Google Fonts CSS v1 API so it can function as a drop-in replacement to Google Fonts by just switching the hostname. If the Themes Team was to add any service to its exception list, Bunny Fonts would be a more privacy respecting option than Google Fonts.
\n\n\n\nThe Themes Team is waiting on core to implement better support for loading local fonts before making a sweeping requirement for themes hosted in the directory. In the meantime, WordPress theme authors have the time to update their themes to load Google Fonts locally before a requirement is put in place.
\";s: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, 28 Jul 2022 20:01: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: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:67:\"Do The Woo Community: When You Really Do the Woo with Ronald Gijsel\";s: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=72536\";s: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:46:\"https://dothewoo.io/woocommerce-ronald-gijsel/\";s: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:362:\"Co-host Ronald shares his experience so far having joined the WooCommerce team at Automattic.
\n>> The post When You Really Do the Woo with Ronald Gijsel 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, 28 Jul 2022 08:59: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: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:127:\"WordCamp Central: WordCamp Jinja: Diverse Speaker Sessions, Web Design Hackathon, Teachers Workshop and Fun at the Nile 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:39:\"https://central.wordcamp.org/?p=3151988\";s: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:148:\"https://central.wordcamp.org/news/2022/07/wordcamp-jinja-diverse-speaker-sessions-web-design-hackathon-teachers-workshop-and-fun-at-the-nile-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:13466:\"WordCamp Jinja 2022 (Fri 2nd– Sat 3rd Sept 2022) will be a major community event in Jinja City, Uganda, where WordPress developers, website designers, online publishers, students and teachers will converge to share comprehensive knowledge and experiences, and to meet other WordPress users. Its going to be a great networking event that will also attract guests from all over Uganda and beyond. The main host venue will be The Innovation Village, Plot 5 Main Street, Jinja City.
\n\n\n\nThere will be something for everyone – beginner’s training, inspirational talks, showcases, best practices, latest trends, plus an after party with lots of fun and camping at the Source of the Nile in Jinja!
\n\n\n\nFull schedule of activities will be published soon.
\n\n\n\nAccommodation For those coming to Jinja for their first time, there are several hotels and guest houses where you can reside. Check through this listing by booking.com: bit.ly/jinjahotels. You can also contact the WordCamp team at jinja@wordcamp.org for more inquiries and guidance.
\n\n\n\nThere are several ways to get involved! Check out the details below:
\n\n\n\nLooking forward to a wonderful WordCamp at the Nile 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 28 Jul 2022 08:00: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:15:\"Mukalele Rogers\";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:41:\"Post Status: EMEA and AMER Member Huddles\";s: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=103136\";s: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/emea-and-amer-member-huddles/\";s: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:1516:\"We are hosting Two Weekly Post Status Member Huddles now. Huddles open time and space for our community of peers designed for camaraderie and connection for all WordPress Professionals, even if you\'re not a member yet.
Sign up for one of our current Huddles:
What Days/Times Work Best To Join a Huddle? — We’re looking to expand our Member Huddles offerings with new days/times to support our global community and need host/facilitators.
\";s: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, 28 Jul 2022 01:18:53 +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:68:\"WPTavern: WordPress Contributors Consider Renaming Full-Site Editing\";s: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=136635\";s: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/wordpress-contributors-consider-renaming-full-site-editing\";s: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:3425:\"WordPress Executive Director Josepha Haden Chomphosy is proposing contributors rename the terms “full-site editing” and “full-site editor” to something more user friendly. The terms came into use as WordPress moved into the Customization phase and are still used to differentiate the work being done on site editing as opposed to content editing in the block editor.
\n\n\n\nHaden Chomphosy has identified two issues with using the term “full-site editing:”
\n\n\n\nContributors who work in WordPress every day may not be fully aware of how specialized some of these terms are and how little they mean to a newcomer. Haden Chomphosy proposes WordPress adopt a new term that is “immediately meaningful for new users of our software, while also being an easy to reference term for all of us building and supporting the software.”
\n\n\n\nShe opened a conversation today on updating our shared lexicon to use a new term for this aspect of editing and asked for feedback on additional contexts that need to be considered.
\n\n\n\nIdeas are already pouring in as it’s much easier to name something than to build it. “Site Editor” has been one of the must popular suggestions so far, but participants in the discussion have also suggested “Template Editor” and “Theme Builder,” as well as “Builder” and “Site Builder.”
\n\n\n\n“Future view, looking back from collaborative editing, what I would want to tell a user: The Editor,” Rob Glidden said. “In the WordPress editor you and your team can edit posts, pages and themes in the same, consistent user interface.”
\n\n\n\nWP Engine developer advocate Nick Diego suggested it’s too late to unring the bell on full-site editing and that WordPress should stick with the term.
\n\n\n\n“Many still refer to the Editor as Gutenberg,” Diego said. “I would be hesitant to introduce a new name when ‘Full Site Editing,’ now that it has been so publicly talked about, will likely live on for years and years to come.
\n\n\n\n“I kind of like the term ‘Full Site Editing.’ For new users in WordPress, it implies that they will be able to edit their entire site, which is true. Of course, there are many Classic themes and page builders that also allow you to do the same thing, but a theme that supports FSE differentiates it from traditional Classic themes.”
\n\n\n\nThe discussion was just opened today and the community is invited to participate with comments on the post. Those who have knowledge of what users, clients, and people outside of WordPress call the editor in the context of full-site editing should also weigh in to help contributors get a better picture.
\";s: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, 27 Jul 2022 21:46:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\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:107:\"Post Status: PHP 8.2 Compatibility, Renaming FSE, Custom Template Options, WP Feature Notifications 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://poststatus.com/?p=102947\";s: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:115:\"https://poststatus.com/php-8-2-compatibility-renaming-fse-custom-template-options-wp-feature-notifications-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:16930:\"Getting Ready for PHP 8.2, Rebooting Feature Notifications, Additional Custom Template Options, and Renaming Full Site Editing.
What\'s happening specific to Five for the Future? Provide your feedback on these posts:
\n\n\n\nThanks 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.
The boundaries between WordPress .com and .org have never been very clear. That may change as the WordPress mobile app sheds features the Jetpack app will gain.
Estimated reading time: 7 minutes
\nToday, Paul Von Schrottky, a core contributor and WordPress Mobile/iOS Engineer at Automattic announced some big changes on the Make WordPress Mobile blog. Currently in its 20.3 release, the mobile app has been part of the WordPress project since 2008 in the #Mobile team‘s care.
\n\n\n\nAccording to Paul\'s Make blog post, the WordPress app\'s features and user experience will be simplified this year to reflect the WordPress core experience — by removing its WordPress.com and Jetpack-enabled features. Core features enabled by the WordPress.com REST API will be removed from the WordPress app as well. Everything that\'s being removed from the WordPress mobile app will be added to the Jetpack counterpart app, which debuted in 2021 for iOS and Android.
\n\n\n\nStats, Activity Log, Backup, Sharing (Jetpack Social), Reader, Notifications, Jetpack Blocks (Gutenberg Editor), @-Mentions, Crossposting (Gutenberg Editor) — and potentially more features.
\n\n\n\n\nEverything being removed will be added to the WordPress app\'s Jetpack counterpart, which debuted in 2021 for iOS and Android.
The Jetpack app recently saw its 11.1 release and the first stages of decoupling its major features into standalone plugins. Currently, the Backup, Boost, Protect, Social, Search, and CRM add-ons for Jetpack can be downloaded separately from the WordPress.org directory. As mobile app features, they will become exclusively available through the Jetpack app.
\n\n\n\nAdditionally, People, Themes, and Menus are features in the WordPress mobile app that rely on the WordPress.com API and will be moved to the Jetpack app to refocus the WordPress app on core-provided APIs.
\n\n\n\nOne significant influence motivating these changes comes from user feedback in app reviews and support requests. These channels often “indicate confusion around which username and password people should use” to log into the app and their sites. Since it\'s possible to log into individual WordPress sites or use a WordPress.com account across multiple sites, it\'s not clear which should be used. Worse, “Using the wrong credentials can lead to vastly different experiences within the app, or frustrating experiences when creating a new account or resetting a password.”
\n\n\n\n\n\n\n\nWe’d like this change to help make those boundaries clear going forward. Jetpack powers WordPress.com as well as millions of self-hosted sites. For people that use Jetpack on a self-hosted site or via a WordPress.com site, the Jetpack app will be the best experience.
Automattic\'s Jetpack Team
Eventually, the goal for the WordPress app is to ask only for user credentials on the site being logged into. It\'s hoped this clearer distinction between Automattic properties (WordPress.com and Jetpack) and any particular WordPress site will foster greater community contribution to the WordPress mobile app. The WordPress mobile app hasn\'t been clearly represented as a community-owned part of the WordPress.org project for quite some time, so this is a needed and welcome clarification.
\n\n\n\nIt\'s not going to be an overnight transition, however. Paul\'s Make WordPress blog post notes user authentication is “a trickier challenge and something [the Mobile team is] still figuring out.” It\'s likely to take a longer time to transition .com logins out of the WordPress app to avoid stranding .com users who have been using it.
\n\n\n\nAnother reason for differentiating the WordPress mobile apps is that the Apple App Store and Google Play naturally focus on in-app purchases because they take a cut of those sales. In the past, Apple rejected the WordPress app because it wanted a 30% cut of non-existent sales in this free app without in-app purchases! To issue updates to the WordPress app, it had to take in some paid features to comply with Apple\'s rules. Now the Jetpack app will have the freemium model in the app store while the WordPress app will go back to being free without upselling anything to its users.
\n\n\n\nA large part of the problem for WordPress that Jetpack may help mitigate but can\'t address all by itself has been Automattic\'s branding and messaging. The differences between the WordPress.com and .org brands have always been indistinct. For example, the “WordPress mobile app” has been (and still is) identified as a “WordPress.com app” at apps.wordpress.com/mobile — but it\'s also the .org app. Referring to all instances of WordPress other than .com as “.org” is awkward too, and only WordPress community insiders are likely to be familiar with that term and its meaning.
\n\n\n\nFortunately, more consistent naming across Automattic properties is in the works, according to Sean Marier. Sean told me “references to the WordPress app will be updated as part of these changes. It’s worth noting that this may not be immediate but is part of an overall transition plan that the team will be working on in the coming months.”
\n\n\n\nAkismet has long been a standalone, mostly donation-based, virtually unmonetized plugin and a part of Jetpack, as well as fresh WordPress installs. It\'s not going anywhere amid all these other changes to the mobile apps. Akismet will remain everywhere, and based on current hiring at Automattic for a Director of Product Marketing for Jetpack, it looks like Akismet will have a place alongside Jetpack, WPScan, and VideoPress as mid-market products. We can expect to see them introduced with a new pricing structure in the near future.
\nI asked the team rolling out all these changes to the mobile apps how they hope Jetpack will be viewed by WordPress users who have looked at it with suspicion because of the blurred boundaries. Their answer:
\n\n\n\n\n\n\n\n“We’d like this change to help make those boundaries clear going forward. Jetpack powers WordPress.com as well as millions of self-hosted sites. For people that use Jetpack on a self-hosted site or via a WordPress.com site, the Jetpack app will be the best experience.”
Automattic\'s Jetpack.com team via Chenda Ngak, head of communications for WordPress.com
These changes to the WordPress and jetpack mobile apps definitely take big steps in the direction of better boundaries where the community and commercial editions of WordPress are clearly delineated. It\'s important this is happening with a focus on decentralization, core contributors, and the unique ways SaaS and self-hosted WordPress can work together to mutual benefit, as I wrote a few weeks ago.
\n\n\n\n\n\n\n\nIn an increasingly competitive market, WordPress can uniquely embrace the strengths of an open platform, taking form as either a SaaS or self-hosted platform — or a mix of both.
Jetpack is available now as an all-in-one plugin or an à la carte mix of freemium add-ons that allow any WordPress site to leverage WordPress.com\'s services and infrastructure. That\'s quite a step forward by going back to the product\'s original promise. Given sufficient clarity on the boundaries between the free .org community code and freemium .com features, this might be a good and needed model for others. In an increasingly competitive market, WordPress can uniquely embrace the strengths of an open platform, taking form as either a SaaS or self-hosted platform — or a mix of both.
\n\n\n\nCan the WordPress and Jetpack mobile apps help clarify the boundaries of the WordPress .org and .com brands and services — and improve the WordPress community\'s view of Jetpack?
\nThe WordPress mobile team announced today that it will be pulling all the Jetpack and WordPress.com features from the official WordPress mobile apps. They will be moved into the Jetpack app through a gradual process that is anticipated to conclude by the end of this year.
\n\n\n\n“Over the years, the WordPress app has evolved to meet a diverse range of site administration needs and use cases,” Automattic mobile engineer Paul Von Schrottky said. “Features like Stats, Reader, and Notifications were introduced with the hope of meeting some of these needs. However, these features require the Jetpack plugin or a WordPress.com account to function and can make the app overwhelming for folks who want a simpler experience.
\n\n\n\n“For the sake of clarity and closer-to-core experience, the mobile team will be working to refocus the app on staple features you’d find with a fresh download of WordPress.”
\n\n\n\nThe following features will be removed and relocated to the Jetpack app:
\n\n\n\nAutomattic’s products in the official WordPress apps have been a source of controversy for nearly a decade. Two years ago, when Automattic tangled with Apple over a lack of in-app purchases in the WordPress for iOS App, the community renewed its call for the company to separate its commercial interests from the official apps. Because Automattic has heavily subsidized the apps’ development, it has been able to add WordPress.com and Jetpack-specific features without contest, but these pose a conflict of interest and are unnecessary for many self-hosted site owners.
\n\n\n\nIn 2014, Automattic CEO Matt Mullenweg said the goal with the mobile apps was to get more mobile app users, which included developing things that Automattic deemed most compelling on mobile – notifications, stats, and the reader. The company has now changed its stance on this, citing “less user confusion” as a primary motivator for the upcoming change.
\n\n\n\n“By attempting to cater to such a diverse range of users and needs, there are flows in the app that present many options to users,” Von Schrottky said. “An example of this is the current login flow. User feedback (via the app reviews) and support channels indicate confusion around which username and password people should use when authenticating.”
\n\n\n\nHistorically, the mobile apps have had almost zero contributions from people outside of Automattic. Improving the contributor experience is one of the goals in decoupling Automattic’s commercial interests from the official apps.
\n\n\n\n“Although everything is open source, new contributors need to understand the blurred line between community-owned features and 3rd-party hosted services if all they want is to contribute to one or the other,” Von Schrottky said. “Also, it can be challenging to understand what functionality and which features are available based on the user’s authentication.”
\n\n\n\nThe user confusion and contributor complexities have been evident for years. Providing a more straightforward experience for users has just now become an actionable priority. It appears that this is because Automattic is planning to add more paid features. At this point, the more principled move is to expand commercial features in the Jetpack app, instead of bombarding self-hosted users with upgrade prompts.
\n\n\n\n“The mobile team has been trying for years to provide a solid, modern experience on mobile, with the goal of helping all users start their WordPress adventure,” Von Schrottky said. “We’ve learned from the diversity and evolving needs of the app user base. In addition to the confusion caused by the current arrangement, the team found that user expectations are confounded by a lack of paid features, such as domain purchases. To better serve the needs of both self-hosted and Jetpack/WordPress.com users in the future, the team is now convinced that adding these specific features in a separate app is the way forward.”
\n\n\n\nAutomattic plans to continue maintaining the official mobile apps, advancing the block editor development, and will be listed as the publisher in the store listings for the apps. Once the Jetpack features are removed, users will still be able to do everything included in the core publishing experience, as well as manage settings.
\n\n\n\n“With this change, we plan for the WordPress app to be a more focused companion to the WordPress.org open source project, leaving the Jetpack app to complement the WordPress.com experience,” Von Schrottky said. “This is more straightforward for users of the WordPress open source project and simplifies the relationship between the WordPress app and platform owners like Apple and Google.”
\n\n\n\nVon Schrottky said Automattic is not considering renaming the Jetpack app at this time. WordPress.com users will be able to access the Reader and other .com platform-specific features there. The transition will happen in phases and the mobile team will soon start introducing messages in the app to inform users about which features will be moved.
\n\n\n\n“The team is still working out the details of the plan as explained in the post, but this will be followed up with other relevant communications to make this change as frictionless as possible for users,” Von Schrottky said.
\";s: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, 27 Jul 2022 15:32: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: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:81:\"WPTavern: #36 – Sean Blakeley on Transitioning a Large Agency Over to Gutenberg\";s: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=136608\";s: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://wptavern.com/podcast/36-sean-blakeley-on-transitioning-a-large-agency-over-to-gutenberg\";s: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:38714:\"On the podcast today we have Sean Blakeley.
\n\n\n\nSean works for a large agency called Americaneagle.com, a platform agnostic organisation working with enterprise clients on a wide variety of projects.
\n\n\n\nAfter years of experiments with different approaches and collaborations between designers and developers, their team has begun to rely heavily on block patterns, and they’ve found it is greatly increasing their productivity. It’s fair to say that block patterns have revolutionised the team’s approach to the entire design process.
\n\n\n\nIn case you’ve not explored block patterns, they are collections of blocks which can be built by anyone. With thoughtful design, these blocks can be repurposed across pages and even different websites. Build once, deploy everywhere.
\n\n\n\nWe talk about how and why Sean’s team decided to jump in early with block patterns. When they did, this was a somewhat risky strategy. There was no guarantee that patterns would begin to be widely adopted, but this strategy is now starting to bear fruit. It’s allowing their team to work with their clients in new and unexpected ways.
\n\n\n\nClients are now working more closely with the American Eagle team in what Sean describes as less ‘impress us’ and more ‘collaborate with us’. It’s fostering a closer relationship with clients which encourages them to use the block editor and patterns and have some ownership in the process.
\n\n\n\nIt’s an interesting episode, and if you’re curious about how you can start to use blocks and patterns with your clients, there’s sure to be something here for you.
\n\n\n\nTypically, when we record the podcast, there’s not a lot of background noise, but that’s not always the case with these WordCamp Europe interviews. We were competing against crowds and the air-conditioning. Whilst the podcasts are more than listenable, I hope that you understand that the vagaries of the real world were at play.
\n\n\n\n[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 adoption of block patterns.
\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 and paste that URL into most podcast players. If there’s anything you’d like us to feature on the podcast, I’d love 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 contact form there.
\n\n\n\nSo on the podcast today, we have Sean Blakeley. Sean works for a large agency called American Eagle. A platform agnostic organization working with enterprise clients on a wide variety of projects. After years of experiments with different approaches and collaborations between designers and developers, their team has begun to rely heavily on block patterns. And they found it’s greatly increasing their productivity. It’s fair to say that block patterns have revolutionized the team’s approach to the entire design process.
\n\n\n\nIf you’ve not explored block patterns, they’re collections of blocks, which can be built by anyone. With thoughtful design, these blocks can be repurposed across pages and even different websites. Build once deploy everywhere.
\n\n\n\nWe talk about how and why Sean’s team decided to jump in early with block patterns. When they did, this was a somewhat risky strategy. There was no guarantee that patterns would begin to be widely adopted. But this strategy is now starting to bear fruit. It’s allowing their team to work with their clients in new and unexpected ways.
\n\n\n\nClients and are working more closely with the American Eagle team, in what Sean describes as, less impress us and more collaborate with us. It’s fostering a closer relationship with clients, which encourages them to use the block editor and patterns and have some ownership in the process.
\n\n\n\nIt’s an interesting episode. And if you’re curious about how you can start to use blocks and patterns with your clients, there’s sure to be something here for you.
\n\n\n\nTypically when we record the podcast, there’s not a lot of background noise, but that’s not always the case with these WordCamp Europeans have use. We were competing against crowds and the air conditioning. And whilst the podcasts are more than listenable, I hope that you understand that the vagaries of the real world we’re at play.
\n\n\n\nIf you’re interested in finding out more, you can find all the links in the show notes by heading over to WPTavern.com forward slash podcast. And you’ll find all of the other episodes there as well.
\n\n\n\nAnd so without further delay, I bring you. Sean Blakeley.
\n\n\n\nI am joined on the podcast today by Sean Blakeley. How are you doing Sean?
\n\n\n\n[00:03:48] Sean Blakeley: I’m doing very well. Thank you, Nathan.
\n\n\n\n[00:03:49] Nathan Wrigley: Sean and I have just been chatting for a few minutes and I think we’re going to be good friends.
\n\n\n\n[00:03:53] Sean Blakeley: I think you’re right.
\n\n\n\n[00:03:54] Nathan Wrigley: So you’re at WordCamp Europe. We’re currently sitting in the basement having a chat, but you did a presentation, which you are now very relieved to have done. It’s behind you now. What was it about?
\n\n\n\n[00:04:05] Sean Blakeley: I mean, it was a wonderful, it’s a wonderful feeling to have been the post talk feeling. Uh, it was about block patterns. The block pattern revolution. I was talking about how we’re using block patterns in our creative process. How we are evolving and adapting our creative process. Bringing together the designers and the developers, and we’re finding that block patterns is opening up all sorts of opportunities. Explore and adapt the collaborative space between designers and developers. So, I was really talking about those exciting opportunities that we see today.
\n\n\n\n[00:04:38] Nathan Wrigley: You’re working at the helm, maybe the helm’s the wrong word, but you’re near the helm of a very large agency. So I guess making that transition to block patterns was, is a big deal. You got a lot riding on that. Tell us a little bit about the company that you work for.
\n\n\n\n[00:04:54] Sean Blakeley: So I work for a company called American Eagle. American Eagle are 700 strong. It’s a large organization. It’s platform agnostic. Obviously there are dedicated teams to a number of sort of key platforms, including Sitecore and Sitefinity, but also of course WordPress. And that’s how it’s really reached that scale. What it tends to focus on is those big enterprise engagements and it, it’s able to address those kind of cross platform, those big digital transformation pieces, those big integrations.
\n\n\n\nAnd so you’re quite right that, you know, as we talk about transitions in organizations of that size, it can very challenging. But because we are, as we are building the WordPress enterprise team, we’re able to explore some of these different technologies and keep pushing at the boundaries of what we’re doing.
\n\n\n\nWe have this incredible opportunity to keep exploring. Exploring WordPress at scale, and I’m sure we’ll talk in a minute about the sort of headness and composable kind of paradigm, but it enables us to keep exploring, to keep pushing these boundaries, and block patterns increasingly feel like they’re part of that journey and are beginning to become an important part of that journey.
\n\n\n\n[00:06:07] Nathan Wrigley: I would imagine that if we asked a typical WordPress user, how do you build your website? I think there’s gonna be a significant proportion who, maybe do it the old fashioned way, but I feel that’s dwindling. Template files and all that.
\n\n\n\nAnd then there’ll be a proportion of people probably still I’m guessing the majority who are using page builders, the commercial page builders. There does seem to be, especially very recently, by that, I mean maybe in the last six months, it does feel like there’s a lot more chatter about blocks and patterns and almost like, okay, this is a thing now. The time has come, we’re gonna shift over in that direction.
\n\n\n\nBut, what would you say are the key benefits? The things that you identified in your business which made you say, oh, actually this is worthwhile now. We’ll stop doing it the way we used to do it, and we’re gonna start doing it with blocks. What were the key metrics that you judged that worthwhile against?
\n\n\n\n[00:06:52] Sean Blakeley: So, the commercial metrics is a kind of separate piece. And we’ll come back to that, because it is an interesting question. But from a technical or an implementation sort of perspective, it always felt jarring when we were bringing software, proprietary software, be it a page builder or some other service into the WordPress platform.
\n\n\n\nIt always felt like we were introducing something that we would either have to be pulling out of WordPress at a later date, or we’re then tying our clients to this particular tool that we had chosen, or, or maybe us as an agency, you know, we preferred a particular page builder. And so that’s the one that our clients got because that was our preferred approach. And that always felt jarring.
\n\n\n\nIt felt like there wasn’t, you know, we weren’t developing for the longevity. That we were slightly tunnel vision and, and narrow focused in terms of our needs as the agency, And so it always felt like we should be coming as close to core as we can. Moving our dependency to WordPress itself, rather than this sort of separate proprietary software. And it’s been a challenging journey at times as we’ve, we were early adopters for Gutenberg and, you know, we felt some of the pain that, that all of us, or many of us in the community have felt. Some of the challenges around creating custom blocks back in the day.
\n\n\n\nBut it was very clear that this felt like the right journey, and it was the right journey to go on. And as we thought about, and talked to our clients about their experience, and their experience for creating content, That goal to move from shortcodes and the abstraction of dropdowns and filling in an input box. And then that leap of faith, as you hope something has changed on the front of your website, and it’s gonna work in the way that you hoped it would.
\n\n\n\nWell, that WYSIWYG experience has been something that we’ve been asked for for years, and of course that’s where the page builder space came from. But to be able to fulfill that in a drag and drop within the WordPress editor itself is, it’s a great thing to be able to provide our clients with that experience, that true WYSIWYG experience. And so the goals are so clear as we’re on this journey together.
\n\n\n\nAnd so, and we’ll come back to that final point around the commercial decision in terms of investing our, our efforts as a technical team. I mean, it was very clear that this is, this is the longevity. This is where we are empowering our clients to own their UI, their UI components. They can start to build out some of their own UI components as well as custom blocks that we might build. And there isn’t a dependency. If they wanna move to, you know, they wanna change their implementations. They can keep WordPress exactly the same.
\n\n\n\nAnd that, that notion of switching a theme, and a theme should be easy to change. Your styling, you know, re styling, making small design changes should be relatively easy. Yeah, that’s becoming true within the Gutenberg paradigm. That we can offer that longevity of, of architecture of platform. And that they can iterate in terms of a design on top of that.
\n\n\n\nSo that’s been a hugely empowering journey, that incidentally that we’re, we’re still on. But we’re thoroughly enjoying the journey and it’s, you know, every step that we take can be daunting at times. But, we’ve found the value in each and every of those steps that we’ve been on so far as the community, working with Gutenberg.
\n\n\n\n[00:10:03] Nathan Wrigley: So at the point where you made the decision to hop on, presumably you’ve not just said, okay, everything from now on will be based upon Gutenberg. Maybe some clients are embedded in something in the WordPress space, like a proprietary page builder. Maybe you’re gonna carry that on, maybe not, I don’t know. But there must have been a lot of retraining, process changes, every which way for your staff. Just talk us through what that was, because obviously if you’re working within your company and building websites, you want to know, what’s the education piece? How am I gonna learn all of this stuff? What’s my company gonna provide for me to make sure that I’m skilled? Was there a lot of that, that had to be put into place?
\n\n\n\n[00:10:39] Sean Blakeley: There was a huge amount. There’s a kind of duality here that the first challenge was to enable developers to feel confident within React. And so feeling confident within a modern JavaScript framework. And we found that that was a hugely valuable first step to sort of, you know, allow them to ease them into familiarity with React.
\n\n\n\nOnce we did that, we then moved into Gutenberg specifically and sort of eased our developers into Gutenberg. And we did it some ways from the interface. So getting familiarity with the interface, but of course, things, and we’re talking maybe two or three years ago now, things were moving so quickly that actually, it was, it was often easier to actually go from the backend forward.
\n\n\n\nAnd so look at, the anatomy of a block. How a block fits together and, we had some really curious developers and developers that were often looking under the bonnet and seeing how these things were constructed and it added to that sense, less of intimidation and more of awe that we’re on a journey together. And actually, you know, we can be part of this dialogue.
\n\n\n\nWe can be part of this journey and, exploring the how we can evolve our processes. And I think that early, understanding the value that Gutenberg, this journey was gonna provide. Even when we were hesitant to put it into production, but it always felt like this was the direction we wanted to go in. We wanted to provide that extraordinary editorial, content creation experience. And then of course, you know, the value that we can give to end users as well.
\n\n\n\n[00:12:14] Nathan Wrigley: I’m imagining that if you had clients that were on the classic editor, There’s just no downside to that. One thing is nothing like the other, so a big boost. But I’m wondering about the clients who may be, were on those page builders. How are they coping, regardless of all that, how are they coping with the UI? Because even though it is a WYSIWYG, it’s kind of got some quirk still hasn’t it?
\n\n\n\nThe UI is a bit funky in places and things don’t quite match up on the back as they do in the front. I’m just wondering how your clients and, you’re a big agency, there must be a lot of feedback coming in. How are they adopting it? Are they welcoming of it?
\n\n\n\n[00:12:48] Sean Blakeley: Yes, so they are in…
\n\n\n\n[00:12:50] Nathan Wrigley: That sounded like aqualified yes.
\n\n\n\n[00:12:52] Sean Blakeley: Well, it is a qualified yes. There is hesitation there at times, because as you’re quite right to point out, there are some rough edges in the implementation. We try and make sure that we are very transparent. That this is an exciting yet evolving part of the WordPress ecosystem. You know, don’t consider this as fully finished. It’s still evolving and adapting. But what we’re increasingly doing is focusing on a opt in approach.
\n\n\n\nSo, the dashboard of blocks can be very intimidating. You know, there is a huge list, particularly if you include the embed options as well. That’s a huge list. If you happen to be running plugins on your site that are also introducing blocks, you can be talking about many dozens in that interface and you, and I might know the difference with a, a media and text block, but our clients aren’t going to know that unless we take them on that journey, unless we educate them.
\n\n\n\nSo what we find ourselves doing increasingly is, is white listing blocks. So actually removing, and, and increasingly this is, this is often a principle in enterprise when you’re working with large scale projects that, it’s actually putting the guardrails in place, you know. It’s, it’s having your brand library or implementation, maybe your UI components. But you are limiting the ability of the editorial team to kind of work within those guidelines, that framework. And that’s how we treat Gutenberg, is that we provide those atomic building blocks, you know, those core blocks, and maybe a few custom blocks as well. We then put limitations in.
\n\n\n\nSo those are your design system, essentially. Those are the UI, the library of UI components that our clients can use. And that’s really attractive then, because becomes very clear what the tools are that they can use to tell their stories, to tell their narratives to their users.
\n\n\n\nAnd it’s not this self serve mentality where you are kind of building from the atoms and trying to build everything from scratch. Actually they’re, they’re sort of pre-baked for you, and you are just going down and, and selecting the ones that you want.
\n\n\n\n[00:14:53] Nathan Wrigley: In WordPress 6.0, we’ve got, maybe it’s not the most fleshed out of block locking features, but does something, it puts a padlock icon there anyway, and you can unlock it. That feels like that would be a, a nice direction to go in as well. That particular feature, you know, the client can access this bit, but not that bit. And they can edit this bit, which our team have built. And if they don’t like the text, they can just go in and do it themselves. And it’s kind of empowering people to edit their own stuff, but not edit this piece.
\n\n\n\n[00:15:18] Sean Blakeley: We absolutely love this feature. And interestingly, we’re actually on a huge project at the moment, a huge headless project. And we were looking at our own custom solution for doing exactly this. So what we’re doing is, we’re bringing in quarter of a million programmatically generated pages, that we’re injecting into Gutenberg blocks.
\n\n\n\nSo we’re kind of generating these Gutenberg blocks. We’re creating these slot in between the blocks to enable them to insert custom content. But essentially we’re programmatically generating that content. And then we’re locking down certain aspects. It’s almost like a, it’s a programmatically generated templated page, if you like, which is locked. And then they can add in between these sort of sections or indeed update some of the images. And there are certain areas that we allow them to update and some not so. And so that feature of locking blocks has been already incredibly valuable for us.
\n\n\n\nAnd exactly, as you say, it chimes with that notion of guidelines, of having a brand language. Of having that visual rhythm, your design system, and then you are working within those confines of your visual language.
\n\n\n\n[00:16:33] Nathan Wrigley: The reason I was talking about it being fairly basic is it can be unlocked by anybody. Doesn’t matter who you are, you just click the button and you’ve unlocked it, but, maybe in the future there’ll be a more granular permissions model that, it doesn’t matter how many times you click the button, you’re not unlocking it. That will be nice, you know, so the editor can edit this, and the subscriber could edit this, and the administrator can obviously edit everything. That was a much needed feature, I think.
\n\n\n\n[00:16:54] Sean Blakeley: And I think you’re right. And incidentally, as we talk about maybe block patterns forming that kind of notion of templates that maybe you and I are gonna create a custom post type. And as we click into that custom post type, we’ve got these pre-baked templates that we can select from and using block patterns to do that.
\n\n\n\nYou’re exactly right that actually we can even allow editors to edit those templates, but we do have the challenge of permissions. And so we need to think about who has that meta level, almost like the super admin we could think of in terms of multisite. You know, who has that top level, that they can edit the template? And then who are the editorial level can just edit implementations of reflections of that.
\n\n\n\n[00:17:34] Nathan Wrigley: Really interesting. So let’s get into the whole block pattern thing. I would be staggered if anybody listening to this, hadn’t heard of them at least. But nevertheless, there’s probably some who haven’t. So let’s just address that. Tell us about block patterns. What are they? They’re in use, I think more and more. As each day goes by, there’s gonna be more and more use of them. But just tell us what they are briefly.
\n\n\n\n[00:17:54] Sean Blakeley: In the simplest terms, block patterns are a contain for blocks. They’re a kind of vessel, that contain these, whichever blocks you want to allow to be within this pattern. But that’s deceptively simple. And what I talk about, the analogy that I like to use is that there are a finite number of musical notes, and so whatever your piece of music, your chosen interest is, be it Pixie’s Debasser, or Mozart or Beethoven, they’re still utilizing that finite number of notes. And yet they can create truly extraordinary, original compositions from those finite number of notes.
\n\n\n\nAnd I think for us Gutenberg are our notes, and the patterns are our favorite songs. Are those extraordinary compositions that we can create.
\n\n\n\n[00:18:42] Nathan Wrigley: Here’s an interesting thought. If you have a Spotify account, there’s more songs than you can ever listen to. Block patterns, so in the same way, we’ve got plugins 50,000, 60,000, whatever the number is. There’s loads of plugins. If you want a form plugin, go and pick out of the 40 over there.
\n\n\n\nIs there gonna be overload? If everybody’s got hundreds and thousands and possibly millions in the future, of patterns. The impediment to creating patterns is so low. The impediment to creating a plugin is quite high. So it’s contained at roughly 50,000. But if block patterns are gonna be really, really easy to create, which they are, especially with things like the pattern creator tool. Then the library, the way that we download these is, presumably at some point gonna be deluged. Your clients may be faced with this atrophy of, I have no idea where to begin. There are 748,000 in there. And I do not even know where to start.
\n\n\n\n[00:19:33] Sean Blakeley: I think you’re quite right. That sort of paralysis, choice paralysis will undoubtedly be an issue that we need to deal with, but less like limiting the ability of people to create these block patterns. And really what we need to do is, is have a way of rating those block patterns or seeing those patterns, the popularity of those patterns. The one that seemed to be solving problems that maybe are achieving conversions in a greater way in your particular sector or your area.
\n\n\n\nAnd it’s, it’s having that validation. I think right now are in the, the wild west of we’re just so excited, and as you say, the friction is so low for creating block patterns. But that in and of itself, isn’t the goal. You know, and that’s not where we want to be. Where we want to be is creating truly original and amazing patterns that we can then validate against the use cases for our clients. The way that they want to introduce them into their sites. But yes, we will have a huge number of block patterns very soon.
\n\n\n\n[00:20:34] Nathan Wrigley: There is some editorial on the back of that. It’s not like you submit a block pattern and it’s just immediately in the library. There will be a team there looking and inspecting, and hopefully if your block pattern, I can’t remember what the exact reasons for dismissal were, but it was things along the lines of, if it’s not really using more than one block, if it’s not doing something innovative, for example, something along those lines. But given all of that, there could be this problem of just too many things to pick from.
\n\n\n\n[00:20:58] Sean Blakeley: I think you’re absolutely right. And then, trying to decide which patterns solve which problems and which to use. That choice paralysis will undoubtedly be an issue that as a community, we then need to start thinking about what’s the value, what’s the added value that block patterns are bringing and find a way of communicating that. Both to us as technologists, but also to our clients.
\n\n\n\n[00:21:18] Nathan Wrigley: One of the interesting ancillary bits of block patterns or blocks or WordPress in general. I don’t know if you’ve followed this thing, but the Openverse. The idea that you can submit block patterns that have all of the images already in, they’re probably placeholders. You probably won’t end up using them, but I do find that’s quite an interesting piece. For the first time you’ll be able to download these block patterns and you can actually stick with it. You can use that thing forever and a day, and there’ll be no license that you are treading on.
\n\n\n\nIt’s totally usable. And I think that’s really interesting. I’ve actually been taking tons of photos this week with the intention of, as soon as I get home and I’ve got a reliable internet, it’s just to stick them onto Openverse, then people can see pictures of Porto for free.
\n\n\n\n[00:22:02] Sean Blakeley: Beautiful. Definitely, and I think it then raises an interesting question about reusable blocks and how block patterns interact with reusable blocks. And if we have these that you can really just drop in and they’re instantly displaying those images or instantly sort of showing that you really, you don’t change, you just drop those in. Whether that’s more the direction that reusable blocks will go in. Those kind of global blocks. So global entities that we use repeatedly. Or whether block patterns will actually evolve into a version of that. That rather than just being templates, UI components that we reuse, maybe they will evolve into something equally like an opportunity to be global. So, there’s definitely areas to explore there.
\n\n\n\n[00:22:45] Nathan Wrigley: When you agreed to have a podcast with me, it sounds subtle, but when I was thinking about it, the more I thought about it, the more I thought, actually, this is fairly seismic. You said that your design process in your agency, as a result of using patterns and the block editor had moved away, I’ll quote, you said it has moved the expectation, and I’m guessing we’re talking about the clients expectation.
\n\n\n\nIt’s moved the expectation from impress us, to collaborate with us. And I think that’s really interesting because that is a big change. But it sounds like a really subtle one on the face of it. But so you are now it’s almost like do it, it’s not DIY, it’s more like do it with us.
\n\n\n\n[00:23:23] Sean Blakeley: It’s a profound change. You’re absolutely right .From being a passive consumer of that process.
\n\n\n\n[00:23:32] Nathan Wrigley: Taking it off the shelf, the website’s off the shelf. There it is. It’s a commodity.
\n\n\n\n[00:23:37] Sean Blakeley: Exactly that, but also, when we’ve struggled through a design process and we present that design and we’ve often got that big gamble moment when it’s sort of Tada, and hoping fingers cross the client likes the designs that we’ve created.
\n\n\n\nThat’s what we’re trying to address is, want to move away from these big gamble moments. These big, almost waterfall by designers. We’re doing big design stages and then big build processes. And so Bringing the clients in closer. Often I feel that we solve thousands of micro problems in the course of the design process and the course of the development process, but we kind of hide that away.
\n\n\n\nWe’re not very good at being communicative and transparent about all of those problems that we’ve solved on that journey. And as we try and bring clients in closer, we want them to own the outcomes. We want them to be on that journey of, here’s some problems, like framing the problem and, and helping them to go on that journey of, okay, there’s some compromises here and there’s some reasoning here that maybe we need to be more mindful of.
\n\n\n\nAnd so when they’ve been part of that process, when they reach the outcomes, when we present that design, it’s no longer a Tada moment where there’s surprise, actually they become champions of that design because they have a sense of ownership. That they’ve bought into it, because they’ve been part of that ideation session and part of those sessions.
\n\n\n\nAnd so, they go into their organizations and they defend those designs. They can answer any questions about what’s the reasoning behind this? Or, or why is this like this? Well, well they know, they’ve been part of those processes.
\n\n\n\nNow, that’s when it works beautifully, and I’m not gonna pretend for one moment that we’ve found the unicorn, that we can all rest happy in our beds, that we’ve solved design and development, project builds. But with the right client and that right collaboration spirit, we are seeing huge value from this approach to design and development.
\n\n\n\n[00:25:37] Nathan Wrigley: I’m really curious as to what that actually looks like on the ground. In other words, presumably there was a transition over to this during the pandemic. Was this, like okay, we’re gonna screen share on Zoom, and we’re gonna show you what we’re doing and you are gonna interrupt us and tell us what you want us to do. Is it literally that? That they are contributing as they watch you do things and learning the process? Or is there more kind of instructional things that you are sending out to them and they approve one as opposed to the other? I’m just curious what the process really, really looks like.
\n\n\n\n[00:26:09] Sean Blakeley: So there’s no one size fits all. We tend to kind of move with the needs of the client and some clients are more collaborative than others. It sort of bubbled up to two approaches. So one might be that we are providing more regular feedback and regular check-ins. It’s worth mentioning because it’s, often designers work in sort of isolation and they, they don’t like to show their workings out. They don’t like to show the rough edges. They want to show something that’s beautiful that they’ve, worked very hard to create.
\n\n\n\nSo it’s often quite hard to get them to actually be more transparent in terms of that process. In terms of their building up of ideas and their iterative, internal iterative approach. And so we’re increasingly encouraging that. And sometimes that might be the collaboration is that they’re seeing things much earlier.
\n\n\n\nBut, with the right type of client, we can go much deeper. And so what we do is, and I think Nathan, you were kind of alluding to, this is actually we create collaboration sessions. We jump on zoom or equivalent, and we get the designers, we get the developers there, we open up Codepen or something similar.
\n\n\n\nAnd really we start like through the conduit, we kind of play what Dan Mall calls the kind of hot potato process where, you know, maybe the designer is center stage for a moment as we are looking at some typography and maybe some color elements, maybe we’ve already got a palette established from the guidelines from a brand existing brand guidelines.
\n\n\n\nAnd then the developer using Tailwind, or again, something similar, you know, there’s that friction to getting something on the screen is very low. We can start to explore and collaborate together. And, and this is where the client’s opinion can start to come in, you know? Well, well, what do you think about the use of, this color in, in this formation. Or, what do you feel about the interplay of these different elements?
\n\n\n\nAnd so what we’ve found is that trying to do that at the meta level, trying to do that in a kind more old fashioned template driven design. That’s really challenging. Because that, that doesn’t really work until you see the whole, and the interplay of all of those components. It’s, it’s hard to kind of break it down.
\n\n\n\nIf you are truly component driven. Well then you can break off, let’s work on the hero component. And what’s incredibly valuable about these sessions is the client can tell you instantly that, oh no, we can’t do that because the marketing team must have a dot, dot dot. Or actually we sell a bit of, we get some, a revenue stream from one of those. It has to be a carousel because we get a revenue stream from one of their slides.
\n\n\n\nNow that minutiae insight is very hard to unfold in a discovery and definition process. That complexity emerges over time. But if you are in that space, if you are collaborating in real time, you get those insights. You get the business objective insights, coming right into the design and development process.
\n\n\n\n[00:28:58] Nathan Wrigley: How do you feel about, I’m pretty sure that I know that you don’t use any of these, but just as a sort of short circuit. How do you feel about these pattern libraries, which have popped up in the last year or so. Where you can go and you can discover template libraries and block pattern libraries. And so these are not the free open source ones that you can get through WordPress, but the proprietary ones.
\n\n\n\nHave you embedded and explored any of those and decided to use them. A minute ago, you were talking about the fact that you were free of all of that with Gutenberg. And I just wondered if you’d strayed into any of that or had any thoughts.
\n\n\n\n[00:29:32] Sean Blakeley: So I felt a for a long time that I don’t like to bring proprietary software into WordPress. As we should all be very mindful of creating dependencies. And that was always true of page builders. It was always a concern that we’re creating a dependency, a future dependency for our clients, you know, whatever our choice of page builder may have been.
\n\n\n\nAnd so the exact principle, the same principle applies here, that we are really creating a dependency. And exactly, as you say, Nathan, this is a young and evolving and adapting area, and maybe we back the wrong horse. You know, maybe the one that we choose is the one that just deprecates into GitHub.
\n\n\n\nAnd then we’ve suddenly got this dependency in one or two of our sites that we have to maintain. And, you know, the support desk need to learn this particular implementation. So, you know, it’s always interesting to explore. It’s always interesting to see what the community are creating both in terms of commercial offerings as well as open source.
\n\n\n\nBut I’m very mindful that we are, it’s an infinite game. We’re not looking for those quick shortcuts in terms of implementing something today. And then we are thinking about that partnership with our clients, that life cycle of a platform, you know, of a, a true solution to their needs.
\n\n\n\nAnd that almost invariably means trying to stay as close to core as we can. We’re trying to reduce dependencies. We’re trying to reduce any sort of proprietary dependencies. With those sort of parameters in mind, it’s not really been part of our journey and I don’t, as yet, you know, we haven’t seen something that has bubbled up that has, has seemingly been so good that we feel like it’s worthy, worth taking in that compromise.
\n\n\n\n[00:31:12] Nathan Wrigley: Sean Blakeley, thank you for joining me on the podcast.
\n\n\n\n[00:31:16] Sean Blakeley: Thank you.
\nA story, to be effective, has to have certain components to help people understand that story and to reach and to be moved by that story.
\n>> The post What Storytelling Means to a WooCommerce Product Builder 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:\"Wed, 27 Jul 2022 08: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: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: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:85:\"Gutenberg Times: Conditionally Registering Patterns in Themes with Third-Party Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=21723\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://gutenbergtimes.com/conditionally-registering-patterns-in-themes-with-third-party-blocks/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8608:\"What happens when a theme registers a pattern with a third-party block? If the user has the block plugin installed, it appears as it should. WordPress also does a good job at handling the flipside of this scenario: the user does not have the block installed.
\n\n\n\nWhen users attempt to use such a pattern in the editor, they will see an error like the following for self-closing blocks:
\n\n\n\n\n\n\n\nYour site doesn’t include support for the “pluginslug/test” block. You can leave this block intact or remove it entirely.
If the block encompasses some HTML, the user will see a different message sitting above the HTML output:
\n\n\n\n\n\n\n\nYour site doesn’t include support for the “pluginslug/test” block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely.
On the front end, self-closing blocks are simply not shown. However, if the block has HTML, its output will appear. This system is better than something like a fatal PHP error on the front end. However, it is often not ideal.
\n\n\n\nLast week, WordPress.org began showing pattern previews in the theme directory, as shown in the following screenshot from the Bright Mode theme page:
\n\n\n\nThis change is a huge win in showing off a theme’s design. In the past, users could not see the patterns without manually installing and testing.
\n\n\n\nHowever, it brought back that original question about dealing with third-party blocks in patterns. WordPress.org’s preview system does not have these blocks installed, so it has no way of showing them. There is currently an open Meta ticket to address this issue, and the ideal solution would be for the theme directory to simply not attempt to preview patterns for unsupported blocks.
\n\n\n\nRegardless of how things are handled in the theme directory, WordPress theme authors have control over whether their patterns appear. Plus, it is generally good practice to not clutter the UI with patterns that do not work.
\n\n\n\nThe easiest way to disable a pattern, keeping it from showing in the UI, is by checking if a particular plugin is active. All you need to know is a function or class name from the plugin.
\n\n\n\nThemes can register patterns either via the register_block_pattern()
function or by placing headered files into the /patterns
subfolder. I will cover each scenario in this tutorial. Then, I will offer a couple of alternative solutions that may work, depending on the scenario.
If registering a pattern via the register_block_pattern()
function, you should only need to check if a plugin is active before calling the function. The simplest way to do this is to conditionally check for the plugin via function_exists()
or class_exists()
.
\n\n\nCode language: PHP (php)add_action( \'init\', function() {\n if ( function_exists( \'pluginslug_some_function\' ) ) {\n register_block_pattern( \'themeslug/pattern-abc\' );\n }\n} );
This method is no different from classic PHP-based themes when calling a function or class from a third-party plugin.
\n\n\n\nPatterns housed in the /patterns
folder are auto-registered by WordPress on the init
action hook. There is currently no filter to short-circuit this process. This method requires unregistering the pattern instead.
Once again, you must conditionally check if a function or class exists. If not, unregister the pattern:
\n\n\n\n\n\nCode language: PHP (php)add_action( \'init\', function() {\n if ( ! function_exists( \'pluginslug_some_function\' ) ) {\n unregister_block_pattern( \'themeslug/pattern-abc\' );\n }\n} );
It is possible to register a pattern while conditionally supporting a particular block. For example, suppose your theme supports a contact form block named pluginslug/contact
that you want to display in a “Contact” pattern. Further suppose that the contact form only makes up one section of the pattern but isn’t necessarily a requirement for the layout to work.
This method allows all users to make use of the pattern but does not require the third-party block to be installed. It will simply not be a part of the pattern if the user doesn’t have it.
\n\n\n\nSince we have access to PHP when building patterns, we can do the same conditional check within the pattern itself. The following is an example of a such a pattern:
\n\n\n\n\n\nCode language: PHP (php)/*\n * Title: Contact\n * Slug: themeslug/contact\n */\n \n<!-- some core WordPress blocks -->\n\n if ( function_exists( \'pluginslug_some_function\' ) ) : \n <!-- wp:pluginslug/contact /-->\n endif \n\n<!-- some other core WordPress blocks -->
\n
This method can grow complex quickly for themes that require multiple third-party blocks in a pattern or need to perform checks in dozens of pattern files. It is more suited to simple or one-off uses. Otherwise, it may become a management headache.
\n\n\n\nIt is also possible to check if a specific block is registered instead of relying on a plugin function/class name. However, this only works if the block is registered on the server-side.
\n\n\n\nWordPress does not have a dedicated is_block_type()
or is_registered_block_type()
helper function, but the WP_Block_Type_Registry
class does have a public is_registered()
method that you can use to check if a block exists:
\";s: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, 27 Jul 2022 08:01:28 +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:\"Justin Tadlock\";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:40:\"HeroPress: Finding My Place In The World\";s: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:56:\"https://heropress.com/?post_type=heropress-essays&p=4641\";s: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:132:\"https://heropress.com/essays/finding-my-place-in-the-world/#utm_source=rss&utm_medium=rss&utm_campaign=finding-my-place-in-the-world\";s: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:22222:\"Code language: PHP (php)if ( WP_Block_Type_Registry::get_instance()->is_registered( \'pluginslug/test\' ) ) {\n register_block_pattern( \'themeslug/pattern-abc\' );\n}
Tämä kirjoitus on luettavissa myös suomeksi.
\n\n\n\nHere is Timi reading his own story aloud.\n\n\n\nFrom a young age, I’ve been interested in computers. That probably comes from our family tree, as my grandad was a home appliance repairer and father has had a career related to the Internet since the early 2000s dot-com boom.
\n\n\n\nI remember looking at schematics of different household appliances at our grandad’s repair shop. Thinking how on earth the television game shows, where you could send a text message to “throw” a ball towards the goal on the virtual background behind the host, do work. Spending time at the computer, going thru different websites and being impressed by those. Father being head of e-commerce for a hairdressing industry chain and seeing the growth of e-commerce during the mid-2000s.
\n\n\n\nAt that time I was in primary school and didn’t understand much of what all that was about. And surely wouldn’t have even guessed that someday I would have a career in IT.
\n\n\n\nSure, back in the days, you had MySpace, virtual horse stables, guestbooks, IRC-Galleria, and different “website builders”… everyone explored the possibilities of these tools and technologies. You almost weren’t cool if you didn’t. So of course I built a few websites mainly just for fun, like almost everyone else of my age at that time. I also purchased my first domains and made a few sites public. One of those, for a scout group, was “coded” with excel. That’s how I started learning HTML and CSS.
\n\n\n\nWhen secondary school started, I did get really interested in sewing, and light-and-audio equipment for live productions. And politics.
\n\n\n\n\n\n\n\nCopyright, patent law, freedom of information and net neutrality were hot topics around that time in Finland.
I felt that the Internet I had grown with, was threatened. The Pirate Party movement had just landed in Finland and they were defending everything I believed in: open access to information and people’s online rights. Despite my young age, they welcomed me, so I got involved with registering the party for elections and in general.
\n\n\n\nThey used IRC for all the communications, and soon I became frustrated because of missed conversations due to shutting off the computer and thus signing off from IRC as well. That led me to assemble, install and run my first home server so I would always have IRC on. Of course, the new server intrigued me and almost invited to try out hosting the websites myself. That way I learned the basics about Linux, Apache, PHP and MySQL. My interest in these things was understood by only a few classmates and for everyone else, I was a bit of a weirdo. Because of that, I didn’t make many friends from the same age group with me – and that stays true to this day.
\n\n\n\nAt some point in all this, I found WordPress. It was around 2009 and version 2.8 when I installed WordPress for the first time. I immediately started looking for ways to modify and extend the website. One thing lead to another. Soon I had installed WordPress quite a few more times, and even helped one of my friends to set up a website for their parliamentary election campaign. For getting the timeline right in this post, I looked up my old websites and found out that in 2010 I had published a guide on how to translate WordPress into Finnish and even offered some theme translations to download.
\n\n\n\nAnd yet I still didn’t think that IT, servers, websites or WordPress could be my career. When secondary school ended, I applied to study live production. Like audio and lights in concerts and all that stuff. Didn’t get selected for that school, because of the low numbers on the diploma. That was devastating.
\n\n\n\nBut little did I know. The third school I applied to, selected me and there I was, going to study multimedia for three years. Photography, video editing, design and a little bit of web development.
\n\n\n\nLooking back, this was one of the most pivotal points in my life. Three years in that school taught me how to be creative with design and boosted my self-confidence in coding skills. Starting almost from the first web development classes, teachers saw my skills and encouraged me to continue coding. I started helping other students during the classes, as most of the web development stuff was already familiar to me. I really enjoyed the print design classes, photography and school in general after a long time.
\n\n\n\nI had also become active in running one of the few Internet cafes in Helsinki that were left in the early 2010s. At the time, we were one of the few places which served only vegetarian food, had open wifi and laptops available for customers. As I was interested in tech and some knowledge, the natural thing was to be involved with maintaining those laptops and the website for the cafe.
\n\n\n\nSome same founders of that cafe cooperative had founded another cooperative in the early 2000s, to offer reasonably priced hosting and email services for associations and other NGOs. After some time, they invited me to join and soon I started helping with server upkeep and customer service. I would also make a number of websites with WordPress for our clients.
\n\n\n\n\n\n\n\nFor the first time in my life, I was getting some money from doing things on the Internet.
I started to feel that I had found what I want to do in my life.
\n\n\n\nThen my partner at the time did get severely ill mentally. That started to affect me as well, and the last year of school with one half at on-the-job training and another half at school doing a bigger final project was very emotional and filled with deep worry. During that year we broke up and that led to depression.
\n\n\n\nI didn’t go to school. I didn’t answer the emails or phone calls from my teachers. For a good few months, my life was filled with going out to nightclubs and doing the cooperative work for which I felt a responsibility.
\n\n\n\nOne day, when one of the teachers was calling yet again, I gathered myself and picked up the phone. It was only a month before graduation and I had some courses and a final project to complete before that. Somehow we managed to arrange everything and with the support of all my teachers, the last course was accepted as completed two days before the graduation ceremony.
\n\n\n\nRight after graduation, I started looking for a job in the web industry. Tens of applications lead to few interviews, but nobody wanted to hire a newly graduated 18-year-old. I had some experience working in the kitchen from summer jobs, so I started applying to those types of openings, from fast-food chains to being a dishwasher at restaurants in need of income.
\n\n\n\n\n\n\n\nFinally, one small school kitchen hired me to do the salads and desserts and help with dishwashing.
A few months passed, and even though the school kitchen work was nice, I knew that it was something I didn’t want to do for too long. Finland has mandatory military or civil service for all adult males, so I started planning to complete my service soon with the hopes of finding a job in web development after that.
\n\n\n\nOnly a few weeks before my civil service was due to start, one of the companies I had applied to reached out to me and offered a job. Being thrilled about finally getting a job offer in the industry, I did take that offer right away to learn that I would be a sole developer. At the age of 19. At a company with multiple seriously big clients and custom systems written in PHP.
\n\n\n\nDuring that time, I also learned about the WordPress community in Finland and attended a few very early unofficial meetups. A bit earlier, I had met Rolle online, who happened to found a WordPress agency around the same time we started offering WordPress websites, on my initiative, at the company I was working for. At its best, we chatted daily and helped each other with our work.
\n\n\n\nFast-forward a year. I was hired by a newly founded digital agency whose owners previously used me as a freelancer. It was really inspiring. I learned a lot and submitted my first patch to WordPress core during that employment. But something was missing. The owners didn’t really see the value in the community and, in fact, denied me from attending the first WordCamp in Finland.
\n\n\n\nBeing very stubborn at that age and really interested in the community based on meetups, I cheated a little and booked train tickets to WordCamp Finland 2015. Ignoring the fact that my bosses haven’t allowed using one workday for that.
\n\n\n\nIt was worth it and a second pivotal point in my life. I finally met Rolle in person and many other Finnish WordPress’ers I looked up to. Including Daniel, who was responsible for Finnish translations for years and Mikko, who was considered a WordPress guru.
\n\n\n\nThe experience was so great and the community so warm, that it pulled me all the way in. I started attending official meetups and over the years first became a volunteer at WordCamp, then organiser and lead the organiser. I also moved to another city and was the first hire in Rolle’s company.
\n\n\n\nNowadays, multiple years later, I’m a partner in the very same company called Dude. A Community Deputy and a WordCamp mentor. Our company sponsors my time partially for the WordPress project. I’ve built WordPress websites for Finnish government agencies and big corporates. Mentored WordCamp Europe. Helped numerous WordPress’ers around the world in various ways.
\n\n\n\nAnd found my place in the world. From an industry and community, I could not have predicted, but to which the journey is quite obvious when looking back. A community that does not only share the same ideology that is still important to me, the freedom of information, but helps to make it true. A community whose members I consider close friends, some even as an extended family.
\n\n\n\nFor those who are interested in my journey in WordPress Community, there’s a post titled “12 years with WordPress” in my personal blog waiting for you.
\n\n\n\n\n\n\n\n
Olin kiinnostunut tietokoneista ja nuoresta iästä lähtien. Sukurasite todennäköisesti, vaari kun oli kodinkonekorjaaja ja isä luonut uraa Internetin parissa 2000-luvun huumasta lähtien.
\n\n\n\nMuistan ihmetelleeni eri kodinkoneiden korjauskaavioita vaarin pajalla. Miettineeni miten television peliohjelmat, joissa pystyit “heittämään” palloa tekstarilla virtuaalisen taustan edessä kekkuloivan juontajan iloksi, voi toimia. Kuluttaneeni aikaa tietokoneella selaten läpi Internetiä. Näheeni valtakunnallisen kampaamoketjun verkkokauppapäällikön, isäni, kautta verkkokaupan kasvun 2000-luvun puolivälissä.
\n\n\n\nTuohon aikaan olin ala-asteella enkä ymmärtänyt isommassa mittakaavassa mitä ympärilläni tapahtui. Enkä olisi koskaan osannut edes arvata, että joku päivä olisin IT-alalla.
\n\n\n\nToki MySpace, virtuaalitallit, erilaiset vieraskirjat, IRC-Galleria, Suntuubi ja vastaavat oli tuohon aikaan pienimuotoinen juttu. Kaikki kokeilkivat ja testailivat näitä uusia työkaluja sekä tekniikoita. Et lähestulkoon ollut cool, jos et testaillut. Niinpä minkäkin rakensin ensimmäisiä verkkosivujani, kuten moni oman ikäiseni noihin aikoihin. Hankin myös muutaman ensimmäisen verkkotunnukseni ja laitoin sivuja julkiseksi. Yksi noista oli partiolippukunnalle excelillä “koodattu” sivusto. Tällä tavoin aloin oppimaan HTML:ää sekä CSS:ää.
\n\n\n\nYlä-asteen alkaessa kiinnostuin todella ompelusta sekä livetuotantojen ääni- ja valotekniikasta. Ja politiikasta.
\n\n\n\nNoihin aikoihin tekijänoikeusasiat, patenttilaki, tiedon vapaus ja nettineutraliteetti olivat tapetilla suomessa. Tunsin, että Internet jonka kanssa olin kasvanut oli uhattuna. Piraattiliike oli juuri saapunut suomeen ja he puolustivat kaikkea mihin uskoin: vapaata pääsyä tietoon sekä ihmisten oikeuksia Internetissä. Nuoresta iästäni huolimatta minut toivotettiin tervetulleeki ja näin osallistuin Piraattipuolueen puoluerekisteriin saamiseen.
\n\n\n\nPiraattipuolueessa käytettiin IRC:iä kaikkeen kommunikointiin, ja pian turhauduinkin kun menetin chattilokeja tietokoneen sammuttamisen takia. Näin päädyin rakentamaan, asentamaan ja pyörittämään ensimmäistä kotipalvelintani – jotta voisin pitää IRC:iä päällä koko ajan. Luonnollisesti tämä houkutti ja lähes kutsui minua testaamaan nettisivujen hostaamista itsekkin. Näin aloin oppimaan perusteita Linuxista, Apachesta, PHP:sta aj MySQL:ästä. Ainoastaan muutama luokkakaverini ymmärsi kiinnostukseni näihin asioihin, muille olin hieman outolintu. Ehkä siksi en saanutkaan kovin montaa ystävää oman ikäisistäni – asia joka muuten pätee edelleen.
\n\n\n\nJossain kohtaa kaikkea tätä löysin WordPressin. Se oli joskus vuonna 2009 ja version 2.8 paikkeilla, kun asensin WordPressin ensimmäistä kertaa. Välittömästi aloin tutkia tapoja muokata sekä laajentaa luomaani nettisivua. Yksi asia johti toiseen. Pian olinkin asentanut WordPressin jo useampaan kertaan ja jopa auttanut ystävääni luomalla hänen eduskuntavaalikampanjasivuston. Tutkistekin tätä kirjoitusta varten vanhoja sivustojani, ja huomasin että 2010 olen julkaissut ohjeen miten saada WordPress suomeksi ja tarjosin jopa muutaman teeman käännöstä ladattavaksi.
\n\n\n\nSilti en vieläkään uskonut, että IT, palvelimet, nettisivut tai WordPress voisi olla joskus ura minulle. Peruskoulun lähestyessä loppuaan, hain opiskelemaan livetuotantojen tekniikkaa. En tullut valituksi päättötodistuksen huonojen arvosanojen takia. Olin lannistunut.
\n\n\n\nMutta vähänpä tiesin. Pääsin kolmanteen hakuvaihtoehtooni ja siinä minä olin, aloittamassa media-assistentin opinnot. Valokuvausta, videoiden editointia, suunnittelua ja vähän nettisivujen tekemistä.
\n\n\n\nTaaksepäin katsoen tämä oli yksi elämäni käännekohdista. Kolme vuotta ammattikoulussa opetti minulle luovuutta ja vahvisti itsetuntoani koodaustaidoistani. Melkein ensimmäisistä tunneista lähtien, opettajat huomasivat kykyni ja kannustivat jatkamaan. Aloin auttamaan muita oppilaita verkkoviestinnän tunneilla, koska lähes kaikki mitä opiskelimme koodaamiseen liittyen oli jo tuttua minulle. Nautin printtimateriaalien suunnittelusta, valokuvauksesta ja pitkästä aikaa koulusta.
\n\n\n\nNoihin aikoihin olin myös ryhtynyt aktiiviseksi yhdessä Helsingin ainoista jäljellä olevista internetkahviloista. Tuohon aikaan osuuskuntamme oli yksi harvoista, joilla oli täysin lihaton valikoima, vapaasti käytettävissä oleva langaton verkko sekä läppäreitä lainaan asiakkaille. Luonnollisesti, koska olin kiinnostunut teknologiasta ja jonkin verran kokenut, päädyin auttamaan näiden läppäreiden sekä kahvilan nettisivujen ylläpitämisessä.
\n\n\n\nSamat perustajat olivat perustaneet toisen osuuskunnan 2000-luvun alussa, tarjotakseen järkevästi hinnoiteltuja verkkopalveluita yhdistyksille sekä yhteisöille. Tulin kutsutuksi mukaan tuohon osuuskuntaan ja pian aloin auttamaan palvelinten ylläpidossa sekä asiakaspalvelussa. Tein myös jonkin verran WordPress-sivustoja asiakkaillemme. Ensimmäistä kertaa elämässäni sain rahaa siitä, että tein asioita Internetissä.
\n\n\n\nAlkoi tuntumaan, että olen löytänyt sen mitä haluan tehdä elämässäni.
\n\n\n\nSitten silloinen kumppanini sairastui mielenterveydeltään vakavasti. Se alkoi vaikuttaa myös minuun ja viimeinen vuosi koulussa, toinen puolisko työssäoppimassa ja toinen lopputyön parissa, täyttyi vahvoilla tunteilla sekä syvällä huolella. Erosimme tuon vuoden aikana, ja masennuin.
\n\n\n\nEn mennyt kouluun. En vastannut opettajien puheluihin tai sähköposteihin. Muutaman kuukauden ajan elämäni täyttyi yökerhoissa käymisellä sekä osuuskunnan töillä, joihin koin velvollisuutta.
\n\n\n\nEräs päivä, kun yksi opettajista soitti jälleen, keräsin itseni ja vastasin. Oli noin kuukausi valmistumiseen ja minulla oli muutama kurssi suoritettavana sekä lopputyö kesken. Jollain tavalla saimme asiat järjestynään opettajieni tuella, ja viimeinen kurssi merkittiin suoritetuksi kaksi päivää ennen valmistujaisia.
\n\n\n\nVälittömästi valmistumisen jälkeen aloin etsimään töitä. Kymmenet hekmukset johtivat muutamaan haastatteluun, mutta kukaan ei halunnut palkata 18 vuotiasta vastavalmistunutta. Olin saanut kesätöistä jonkin verran koemusta keittiössä työskentelemisestä, joten rahan tarpeessa aloin hakemaan työpaikkoja mistä tahansa ravintola-alalta, pikaruokaketjuista aina ravintoloiden tiskariksi. Lopulta eräs pienempi koulukeittiö palkkasi minut auttamaan salaattien, jälkiruokien sekä tiskien kanssa.
\n\n\n\nJokunen kuukausi kului ja vaikka työ oli mukavaa, tiesin etten halua tehdä sitä turhan pitkään. Niinpä aloin suunnittelemaan siviilipalvelukseen astumista ja toivoin, että löytäisin sen jälkeen oman alan töitä.
\n\n\n\nVain muutama viikko ennen palvelukseen astumista, eräs yrityksistä joihin olin hakenut palasi asiaan ja tarjosi töitä. Olin innoissani, eikä tarvinnut miettiä pitkään paikan vastaanottamista. Pian kuitenkin opin, että tulisin olemaan yrityksen ainoa koodari. 19 vuoden ikäisenä. Yrityksessä jolla oli isoja asiakkuuksia ja lukuisia itse kehitettyjä PHP-sovelluksia.
\n\n\n\nNoihin aikoihin tulin myös tietoiseksi suomen WordPress-yhteisöstä ja osallistuin muutamaan ensimmäisistä epävirallisista tapaamisista. Hieman aiemmin, olin tustunut netissä Rolleen, joka sattui perustamaan WordPress-toimiston samoihin aikoihin kuin meidän yritys alkoi tarjoamaan WordPress-sivustoja aloitteestani. Parhaimmillaan juttelimme päivittäin ja autoimme toisiamme työssämme.
\n\n\n\nPikakelataan vuosi. Olin palkattu vastaperustettuun digitoimistoon, joiden omistajille olin tehnyt joitain vuosia aiemmin hommia freelancerina. Tuo aika oli todella inspiroivaa. Opin paljon uutta ja lähetin jopa ensimmäisen pienen korjaukseni WordPressin ytimeen. Mutta jotain puuttui. Omistajat eivät oikein nähneet arvoa yhteisössä, ja itseasiassa kielsivät osallistumasta suomen enimmäiseen WordCamp-tapahtumaan.
\n\n\n\nJääräpäinen kun olin, ja erittäin kiinnostunut yhteisöstä, huijasin hieman ja varasin junaliput osallistuaakseni WordCamp Finland 2015 -tapahtumaan. Huolimatta siitä, että minua oli kielletty kuluttamasta työpäivää siihen.
\n\n\n\nOsallistuminen oli sen arvoista ja toinen käännekohdista elämässäni. Tapasin vihdoin Rollen ensimmäistä kertaa livenä, sekä muita suomen WordPress-maailman hahmoja joita ihailin. Mukaanlukien Daniel joka vastasi suomenkielisistä käännöksistä pitkään sekä Mikon, jota pidettiin lähes WordPress-guruna.
\n\n\n\nKokemus oli niin mahtava ja yhteisö niin lämmin, että se veti heti mukaansa. Aloin osallistumaan virallisiin WordPress meetuppeihin säännöllisesti ja vuosien aikana ilmoittauduin ensin vapaaehtoiseksi WordCamppiin, sitten järjestäjäksi ja lopulta pääjärjestäjäksi. Muutin toiseen kaupunkiin ja olin Rollen perustaman firman ensimmäinen palkkaus.
\n\n\n\nNykyään, vuosia myöhemmin, olen osakas tuossa samassa firmassa nimeltään Dude. Osa kansainvälistä yhteisötiimiä ja mentoroin WordCamppeja. Firma sponsoroi osan työajastani WordPress yhteisön hyväksi. Olen ollut mukana tekemässä nettisivuja valtionhallionhallinnolle ja isoille korporaatioille. Mentoroinut maailmans suurinta WordCampia. Auttanut lukuisia WordPressin käyttäjiä ympäri maailman.
\n\n\n\nJa löytänyt paikkani maailmassa. Alalta ja yhteisöstä jota en olisi voinut koskaan ennustaa, mutta johon matka on selkeästi nähtävissä kun katsoo taaksepäin. Yhteisössä, joka ei ainoastaan jaa kanssani samaa ideologiaa joka on edelleen minulle tärkeä, tiedon vapaus, vaan myös auttaa tekemään siitä totta. Yhteisössä, jonka jäsenet ovat tärkeitä ystäviä ja osa jopa melkein kuin perhettä.
\n\n\n\nMatkastani WordPress-yhteisössä kiinnostuneille, henkilökohtaisesta blogistani löytyy kirjoitus “12 years with WordPress”.
\nThe post Finding My Place In The World appeared first on 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:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Jul 2022 08:00: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:14:\"Timi Wahalahti\";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:91:\"WPTavern: Akismet 5.0 Adds New Spam Detection Feature That Analyzes How Comments Are Posted\";s: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=136573\";s: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://wptavern.com/akismet-5-0-adds-new-spam-detection-feature-that-analyzes-how-comments-are-posted\";s: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:2157:\"For years, the vast majority of Akismet releases have been centered around bug fixes and improving compatibility with various plugins. Version 5.0 was released today, following 4.2.5 earlier this month, with a new feature that should improve Askismet’s ability to detect spam comments.
\n\n\n\nAkismet engineer Christopher Finke explained how the plugin will now analyze how a comment is posted, in addition to analyzing what is posted:
\n\n\n\n\n\n\n\nA typical human commenter on the Web takes about 40 seconds to read a blog post and another 40 seconds to write and submit a comment. Their typing speed varies significantly throughout the creation of their comment, and they regularly use their mouse to click around the page. An automated spambot (even one programmed to act like a person) doesn’t act so human-like: its typing speed and mouseclick speed are superhumanly consistent. It doesn’t spend time “reading” blog posts. Its mouse usage is sparse.
This new feature can detect spam that is posted in a machine-like fashion, even if the spambot is attempting to post a comment with content identical to one that has already been approved.
\n\n\n\n“The Akismet plugin will begin observing these behaviors so that they can be used as part of the spam-checking process,” Finke said. “None of this data is personally identifiable, and it won’t be used for any purpose other than identifying spam.”
\n\n\n\nAkismet is bundled with WordPress and is active on more than 5 million sites. More than 62% of users are running on 4.2.x and ~38% are on version 4.1 or older. WordPress users who are having a lot of spam breaking through Akismet’s protection will want to upgrade to take advantage of the new spambot detection features in version 5.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:\"Tue, 26 Jul 2022 18:26: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:\"\";}}}}}}}}}}}}}}}}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:\"Fri, 12 Aug 2022 09:44:44 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Fri, 12 Aug 2022 09:30:12 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20220215094112\";}','no'),(4089,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1660340684','no'),(4090,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1660297484','no'),(4091,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1660340684','no'),(4092,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b',' ','no'),(4093,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1660297634;s:7:\"checked\";a:6:{s:5:\"astra\";s:5:\"3.9.1\";s:14:\"twentynineteen\";s:3:\"2.3\";s:15:\"twentyseventeen\";s:3:\"3.0\";s:12:\"twentytwenty\";s:3:\"2.0\";s:15:\"twentytwentyone\";s:3:\"1.6\";s:15:\"twentytwentytwo\";s:3:\"1.2\";}s:8:\"response\";a:0:{}s:9:\"no_update\";a:6:{s:5:\"astra\";a:6:{s:5:\"theme\";s:5:\"astra\";s:11:\"new_version\";s:5:\"3.9.1\";s:3:\"url\";s:35:\"https://wordpress.org/themes/astra/\";s:7:\"package\";s:53:\"https://downloads.wordpress.org/theme/astra.3.9.1.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.3\";}s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"2.3\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.2.3.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"3.0\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.3.0.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"2.0\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.2.0.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentytwentyone\";a:6:{s:5:\"theme\";s:15:\"twentytwentyone\";s:11:\"new_version\";s:3:\"1.6\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentyone/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentyone.1.6.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.6\";}s:15:\"twentytwentytwo\";a:6:{s:5:\"theme\";s:15:\"twentytwentytwo\";s:11:\"new_version\";s:3:\"1.2\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentytwo/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentytwo.1.2.zip\";s:8:\"requires\";s:3:\"5.9\";s:12:\"requires_php\";s:3:\"5.6\";}}s:12:\"translations\";a:0:{}}','no'),(4103,'_transient_timeout_global_styles_twentyseventeen','1660298242','no'),(4104,'_transient_global_styles_twentyseventeen','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--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: 13px;--wp--preset--font-size--medium: 20px;--wp--preset--font-size--large: 36px;--wp--preset--font-size--x-large: 42px;}.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-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-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-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;}','no'),(4105,'_transient_is_multi_author','0','yes'),(4106,'_transient_timeout_global_styles_svg_filters_twentyseventeen','1660298242','no'),(4107,'_transient_global_styles_svg_filters_twentyseventeen','','no'),(4108,'_site_transient_timeout_available_translations','1660309023','no'),(4109,'_site_transient_available_translations','a:129:{s:2:\"af\";a:8:{s:8:\"language\";s:2:\"af\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-05-13 15:59:22\";s:12:\"english_name\";s:9:\"Afrikaans\";s:11:\"native_name\";s:9:\"Afrikaans\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8-beta/af.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"af\";i:2;s:3:\"afr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Gaan voort\";}}s:2:\"am\";a:8:{s:8:\"language\";s:2:\"am\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-06 20:56:57\";s:12:\"english_name\";s:7:\"Amharic\";s:11:\"native_name\";s:12:\"አማርኛ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/am.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"am\";i:2;s:3:\"amh\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"ቀጥል\";}}s:3:\"arg\";a:8:{s:8:\"language\";s:3:\"arg\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-06-14 22:54:15\";s:12:\"english_name\";s:9:\"Aragonese\";s:11:\"native_name\";s:9:\"Aragonés\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/6.0.1/arg.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"an\";i:2;s:3:\"arg\";i:3;s:3:\"arg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continar\";}}s:2:\"ar\";a:8:{s:8:\"language\";s:2:\"ar\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-30 20:47:16\";s:12:\"english_name\";s:6:\"Arabic\";s:11:\"native_name\";s:14:\"العربية\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/ar.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:2;s:3:\"ara\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:3:\"ary\";a:8:{s:8:\"language\";s:3:\"ary\";s:7:\"version\";s:6:\"4.8.19\";s:7:\"updated\";s:19:\"2017-01-26 15:42:35\";s:12:\"english_name\";s:15:\"Moroccan Arabic\";s:11:\"native_name\";s:31:\"العربية المغربية\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.8.19/ary.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:3;s:3:\"ary\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:2:\"as\";a:8:{s:8:\"language\";s:2:\"as\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2021-09-08 17:57:56\";s:12:\"english_name\";s:8:\"Assamese\";s:11:\"native_name\";s:21:\"অসমীয়া\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.4/as.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"as\";i:2;s:3:\"asm\";i:3;s:3:\"asm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"az\";a:8:{s:8:\"language\";s:2:\"az\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-06 00:09:27\";s:12:\"english_name\";s:11:\"Azerbaijani\";s:11:\"native_name\";s:16:\"Azərbaycan dili\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/az.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:2;s:3:\"aze\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Davam\";}}s:3:\"azb\";a:8:{s:8:\"language\";s:3:\"azb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-12 20:34:31\";s:12:\"english_name\";s:17:\"South Azerbaijani\";s:11:\"native_name\";s:29:\"گؤنئی آذربایجان\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/azb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:3;s:3:\"azb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:3:\"bel\";a:8:{s:8:\"language\";s:3:\"bel\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2019-10-29 07:54:22\";s:12:\"english_name\";s:10:\"Belarusian\";s:11:\"native_name\";s:29:\"Беларуская мова\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.9.20/bel.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"be\";i:2;s:3:\"bel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Працягнуць\";}}s:5:\"bg_BG\";a:8:{s:8:\"language\";s:5:\"bg_BG\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-10 19:34:56\";s:12:\"english_name\";s:9:\"Bulgarian\";s:11:\"native_name\";s:18:\"Български\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/bg_BG.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bg\";i:2;s:3:\"bul\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Напред\";}}s:5:\"bn_BD\";a:8:{s:8:\"language\";s:5:\"bn_BD\";s:7:\"version\";s:6:\"5.4.10\";s:7:\"updated\";s:19:\"2020-10-31 08:48:37\";s:12:\"english_name\";s:20:\"Bengali (Bangladesh)\";s:11:\"native_name\";s:15:\"বাংলা\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.4.10/bn_BD.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"bn\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:23:\"এগিয়ে চল.\";}}s:2:\"bo\";a:8:{s:8:\"language\";s:2:\"bo\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2020-10-30 03:24:38\";s:12:\"english_name\";s:7:\"Tibetan\";s:11:\"native_name\";s:21:\"བོད་ཡིག\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8-beta/bo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bo\";i:2;s:3:\"tib\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:33:\"མུ་མཐུད་དུ།\";}}s:5:\"bs_BA\";a:8:{s:8:\"language\";s:5:\"bs_BA\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-09 10:47:25\";s:12:\"english_name\";s:7:\"Bosnian\";s:11:\"native_name\";s:8:\"Bosanski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/bs_BA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bs\";i:2;s:3:\"bos\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:2:\"ca\";a:8:{s:8:\"language\";s:2:\"ca\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-03 13:13:58\";s:12:\"english_name\";s:7:\"Catalan\";s:11:\"native_name\";s:7:\"Català\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/ca.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ca\";i:2;s:3:\"cat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:3:\"ceb\";a:8:{s:8:\"language\";s:3:\"ceb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-02 17:25:51\";s:12:\"english_name\";s:7:\"Cebuano\";s:11:\"native_name\";s:7:\"Cebuano\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/ceb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"ceb\";i:3;s:3:\"ceb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Padayun\";}}s:5:\"cs_CZ\";a:8:{s:8:\"language\";s:5:\"cs_CZ\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-12 07:59:05\";s:12:\"english_name\";s:5:\"Czech\";s:11:\"native_name\";s:9:\"Čeština\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/cs_CZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cs\";i:2;s:3:\"ces\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Pokračovat\";}}s:2:\"cy\";a:8:{s:8:\"language\";s:2:\"cy\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-11 11:10:19\";s:12:\"english_name\";s:5:\"Welsh\";s:11:\"native_name\";s:7:\"Cymraeg\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/cy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cy\";i:2;s:3:\"cym\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Parhau\";}}s:5:\"da_DK\";a:8:{s:8:\"language\";s:5:\"da_DK\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-27 09:48:50\";s:12:\"english_name\";s:6:\"Danish\";s:11:\"native_name\";s:5:\"Dansk\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/da_DK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"da\";i:2;s:3:\"dan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsæt\";}}s:14:\"de_CH_informal\";a:8:{s:8:\"language\";s:14:\"de_CH_informal\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-24 08:57:04\";s:12:\"english_name\";s:30:\"German (Switzerland, Informal)\";s:11:\"native_name\";s:21:\"Deutsch (Schweiz, Du)\";s:7:\"package\";s:73:\"https://downloads.wordpress.org/translation/core/6.0.1/de_CH_informal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_AT\";a:8:{s:8:\"language\";s:5:\"de_AT\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-03-17 12:58:14\";s:12:\"english_name\";s:16:\"German (Austria)\";s:11:\"native_name\";s:21:\"Deutsch (Österreich)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/de_AT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_DE\";a:8:{s:8:\"language\";s:5:\"de_DE\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-18 19:50:09\";s:12:\"english_name\";s:6:\"German\";s:11:\"native_name\";s:7:\"Deutsch\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/de_DE.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:12:\"de_DE_formal\";a:8:{s:8:\"language\";s:12:\"de_DE_formal\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-18 19:51:43\";s:12:\"english_name\";s:15:\"German (Formal)\";s:11:\"native_name\";s:13:\"Deutsch (Sie)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/6.0.1/de_DE_formal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_CH\";a:8:{s:8:\"language\";s:5:\"de_CH\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-24 09:00:33\";s:12:\"english_name\";s:20:\"German (Switzerland)\";s:11:\"native_name\";s:17:\"Deutsch (Schweiz)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/de_CH.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:3:\"dsb\";a:8:{s:8:\"language\";s:3:\"dsb\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-16 12:13:09\";s:12:\"english_name\";s:13:\"Lower Sorbian\";s:11:\"native_name\";s:16:\"Dolnoserbšćina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/6.0.1/dsb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"dsb\";i:3;s:3:\"dsb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Dalej\";}}s:3:\"dzo\";a:8:{s:8:\"language\";s:3:\"dzo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-06-29 08:59:03\";s:12:\"english_name\";s:8:\"Dzongkha\";s:11:\"native_name\";s:18:\"རྫོང་ཁ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/dzo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"dz\";i:2;s:3:\"dzo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"el\";a:8:{s:8:\"language\";s:2:\"el\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-05 18:29:18\";s:12:\"english_name\";s:5:\"Greek\";s:11:\"native_name\";s:16:\"Ελληνικά\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/el.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"el\";i:2;s:3:\"ell\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Συνέχεια\";}}s:5:\"en_GB\";a:8:{s:8:\"language\";s:5:\"en_GB\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-05 17:05:41\";s:12:\"english_name\";s:12:\"English (UK)\";s:11:\"native_name\";s:12:\"English (UK)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/en_GB.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_ZA\";a:8:{s:8:\"language\";s:5:\"en_ZA\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2021-12-24 12:36:39\";s:12:\"english_name\";s:22:\"English (South Africa)\";s:11:\"native_name\";s:22:\"English (South Africa)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/en_ZA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_NZ\";a:8:{s:8:\"language\";s:5:\"en_NZ\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-04-01 22:35:34\";s:12:\"english_name\";s:21:\"English (New Zealand)\";s:11:\"native_name\";s:21:\"English (New Zealand)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/en_NZ.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_CA\";a:8:{s:8:\"language\";s:5:\"en_CA\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-06-09 10:19:51\";s:12:\"english_name\";s:16:\"English (Canada)\";s:11:\"native_name\";s:16:\"English (Canada)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/en_CA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_AU\";a:8:{s:8:\"language\";s:5:\"en_AU\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-18 03:40:33\";s:12:\"english_name\";s:19:\"English (Australia)\";s:11:\"native_name\";s:19:\"English (Australia)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/en_AU.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"eo\";a:8:{s:8:\"language\";s:2:\"eo\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-18 14:16:16\";s:12:\"english_name\";s:9:\"Esperanto\";s:11:\"native_name\";s:9:\"Esperanto\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/eo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eo\";i:2;s:3:\"epo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Daŭrigi\";}}s:5:\"es_VE\";a:8:{s:8:\"language\";s:5:\"es_VE\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-07 20:37:41\";s:12:\"english_name\";s:19:\"Spanish (Venezuela)\";s:11:\"native_name\";s:21:\"Español de Venezuela\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_VE.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CO\";a:8:{s:8:\"language\";s:5:\"es_CO\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-22 14:08:10\";s:12:\"english_name\";s:18:\"Spanish (Colombia)\";s:11:\"native_name\";s:20:\"Español de Colombia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_CO.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_DO\";a:8:{s:8:\"language\";s:5:\"es_DO\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2021-10-08 14:32:50\";s:12:\"english_name\";s:28:\"Spanish (Dominican Republic)\";s:11:\"native_name\";s:33:\"Español de República Dominicana\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.4/es_DO.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_PE\";a:8:{s:8:\"language\";s:5:\"es_PE\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2021-10-04 20:53:18\";s:12:\"english_name\";s:14:\"Spanish (Peru)\";s:11:\"native_name\";s:17:\"Español de Perú\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.4/es_PE.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_UY\";a:8:{s:8:\"language\";s:5:\"es_UY\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-03-31 18:33:26\";s:12:\"english_name\";s:17:\"Spanish (Uruguay)\";s:11:\"native_name\";s:19:\"Español de Uruguay\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/es_UY.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CL\";a:8:{s:8:\"language\";s:5:\"es_CL\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-06-14 16:02:22\";s:12:\"english_name\";s:15:\"Spanish (Chile)\";s:11:\"native_name\";s:17:\"Español de Chile\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/es_CL.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_PR\";a:8:{s:8:\"language\";s:5:\"es_PR\";s:7:\"version\";s:6:\"5.4.10\";s:7:\"updated\";s:19:\"2020-04-29 15:36:59\";s:12:\"english_name\";s:21:\"Spanish (Puerto Rico)\";s:11:\"native_name\";s:23:\"Español de Puerto Rico\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.4.10/es_PR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_MX\";a:8:{s:8:\"language\";s:5:\"es_MX\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-06 15:13:59\";s:12:\"english_name\";s:16:\"Spanish (Mexico)\";s:11:\"native_name\";s:19:\"Español de México\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_MX.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_GT\";a:8:{s:8:\"language\";s:5:\"es_GT\";s:7:\"version\";s:6:\"5.2.15\";s:7:\"updated\";s:19:\"2019-03-02 06:35:01\";s:12:\"english_name\";s:19:\"Spanish (Guatemala)\";s:11:\"native_name\";s:21:\"Español de Guatemala\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.2.15/es_GT.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_AR\";a:8:{s:8:\"language\";s:5:\"es_AR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-24 21:42:31\";s:12:\"english_name\";s:19:\"Spanish (Argentina)\";s:11:\"native_name\";s:21:\"Español de Argentina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_AR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_ES\";a:8:{s:8:\"language\";s:5:\"es_ES\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-28 15:24:06\";s:12:\"english_name\";s:15:\"Spanish (Spain)\";s:11:\"native_name\";s:8:\"Español\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_ES.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_EC\";a:8:{s:8:\"language\";s:5:\"es_EC\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-01 00:22:12\";s:12:\"english_name\";s:17:\"Spanish (Ecuador)\";s:11:\"native_name\";s:19:\"Español de Ecuador\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_EC.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CR\";a:8:{s:8:\"language\";s:5:\"es_CR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-17 18:49:06\";s:12:\"english_name\";s:20:\"Spanish (Costa Rica)\";s:11:\"native_name\";s:22:\"Español de Costa Rica\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/es_CR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"et\";a:8:{s:8:\"language\";s:2:\"et\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2020-08-12 08:38:59\";s:12:\"english_name\";s:8:\"Estonian\";s:11:\"native_name\";s:5:\"Eesti\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8-beta/et.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"et\";i:2;s:3:\"est\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Jätka\";}}s:2:\"eu\";a:8:{s:8:\"language\";s:2:\"eu\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-09 11:26:03\";s:12:\"english_name\";s:6:\"Basque\";s:11:\"native_name\";s:7:\"Euskara\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/eu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eu\";i:2;s:3:\"eus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Jarraitu\";}}s:5:\"fa_AF\";a:8:{s:8:\"language\";s:5:\"fa_AF\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-17 02:46:53\";s:12:\"english_name\";s:21:\"Persian (Afghanistan)\";s:11:\"native_name\";s:31:\"(فارسی (افغانستان\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/fa_AF.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fa\";i:2;s:3:\"fas\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"fa_IR\";a:8:{s:8:\"language\";s:5:\"fa_IR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-19 05:33:03\";s:12:\"english_name\";s:7:\"Persian\";s:11:\"native_name\";s:10:\"فارسی\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/fa_IR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fa\";i:2;s:3:\"fas\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:2:\"fi\";a:8:{s:8:\"language\";s:2:\"fi\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-23 18:39:08\";s:12:\"english_name\";s:7:\"Finnish\";s:11:\"native_name\";s:5:\"Suomi\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/fi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fi\";i:2;s:3:\"fin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Jatka\";}}s:5:\"fr_CA\";a:8:{s:8:\"language\";s:5:\"fr_CA\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-13 18:56:33\";s:12:\"english_name\";s:15:\"French (Canada)\";s:11:\"native_name\";s:19:\"Français du Canada\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/fr_CA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_FR\";a:8:{s:8:\"language\";s:5:\"fr_FR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-02 12:52:42\";s:12:\"english_name\";s:15:\"French (France)\";s:11:\"native_name\";s:9:\"Français\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/fr_FR.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"fr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_BE\";a:8:{s:8:\"language\";s:5:\"fr_BE\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-02-22 13:54:46\";s:12:\"english_name\";s:16:\"French (Belgium)\";s:11:\"native_name\";s:21:\"Français de Belgique\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/fr_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:3:\"fur\";a:8:{s:8:\"language\";s:3:\"fur\";s:7:\"version\";s:6:\"4.8.19\";s:7:\"updated\";s:19:\"2018-01-29 17:32:35\";s:12:\"english_name\";s:8:\"Friulian\";s:11:\"native_name\";s:8:\"Friulian\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.8.19/fur.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"fur\";i:3;s:3:\"fur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"gd\";a:8:{s:8:\"language\";s:2:\"gd\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-08-23 17:41:37\";s:12:\"english_name\";s:15:\"Scottish Gaelic\";s:11:\"native_name\";s:9:\"Gàidhlig\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/gd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"gd\";i:2;s:3:\"gla\";i:3;s:3:\"gla\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"Lean air adhart\";}}s:5:\"gl_ES\";a:8:{s:8:\"language\";s:5:\"gl_ES\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-08 19:03:15\";s:12:\"english_name\";s:8:\"Galician\";s:11:\"native_name\";s:6:\"Galego\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/gl_ES.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gl\";i:2;s:3:\"glg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"gu\";a:8:{s:8:\"language\";s:2:\"gu\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2018-09-14 12:33:48\";s:12:\"english_name\";s:8:\"Gujarati\";s:11:\"native_name\";s:21:\"ગુજરાતી\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.20/gu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gu\";i:2;s:3:\"guj\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:31:\"ચાલુ રાખવું\";}}s:3:\"haz\";a:8:{s:8:\"language\";s:3:\"haz\";s:7:\"version\";s:6:\"4.4.27\";s:7:\"updated\";s:19:\"2015-12-05 00:59:09\";s:12:\"english_name\";s:8:\"Hazaragi\";s:11:\"native_name\";s:15:\"هزاره گی\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.4.27/haz.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"haz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"he_IL\";a:8:{s:8:\"language\";s:5:\"he_IL\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-10 09:13:56\";s:12:\"english_name\";s:6:\"Hebrew\";s:11:\"native_name\";s:16:\"עִבְרִית\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/he_IL.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"he\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"המשך\";}}s:5:\"hi_IN\";a:8:{s:8:\"language\";s:5:\"hi_IN\";s:7:\"version\";s:6:\"5.4.10\";s:7:\"updated\";s:19:\"2020-11-06 12:34:38\";s:12:\"english_name\";s:5:\"Hindi\";s:11:\"native_name\";s:18:\"हिन्दी\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.4.10/hi_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hi\";i:2;s:3:\"hin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"जारी रखें\";}}s:2:\"hr\";a:8:{s:8:\"language\";s:2:\"hr\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-05 17:59:23\";s:12:\"english_name\";s:8:\"Croatian\";s:11:\"native_name\";s:8:\"Hrvatski\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/hr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hr\";i:2;s:3:\"hrv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:3:\"hsb\";a:8:{s:8:\"language\";s:3:\"hsb\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-18 19:40:10\";s:12:\"english_name\";s:13:\"Upper Sorbian\";s:11:\"native_name\";s:17:\"Hornjoserbšćina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/6.0.1/hsb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"hsb\";i:3;s:3:\"hsb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:4:\"Dale\";}}s:5:\"hu_HU\";a:8:{s:8:\"language\";s:5:\"hu_HU\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-09 19:59:16\";s:12:\"english_name\";s:9:\"Hungarian\";s:11:\"native_name\";s:6:\"Magyar\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/hu_HU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hu\";i:2;s:3:\"hun\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Folytatás\";}}s:2:\"hy\";a:8:{s:8:\"language\";s:2:\"hy\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-03 16:21:10\";s:12:\"english_name\";s:8:\"Armenian\";s:11:\"native_name\";s:14:\"Հայերեն\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/hy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hy\";i:2;s:3:\"hye\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Շարունակել\";}}s:5:\"id_ID\";a:8:{s:8:\"language\";s:5:\"id_ID\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-19 14:21:02\";s:12:\"english_name\";s:10:\"Indonesian\";s:11:\"native_name\";s:16:\"Bahasa Indonesia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/id_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"id\";i:2;s:3:\"ind\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Lanjutkan\";}}s:5:\"is_IS\";a:8:{s:8:\"language\";s:5:\"is_IS\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2018-12-11 10:40:02\";s:12:\"english_name\";s:9:\"Icelandic\";s:11:\"native_name\";s:9:\"Íslenska\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.20/is_IS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"is\";i:2;s:3:\"isl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Áfram\";}}s:5:\"it_IT\";a:8:{s:8:\"language\";s:5:\"it_IT\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-01 08:19:40\";s:12:\"english_name\";s:7:\"Italian\";s:11:\"native_name\";s:8:\"Italiano\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/it_IT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"it\";i:2;s:3:\"ita\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:2:\"ja\";a:8:{s:8:\"language\";s:2:\"ja\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-05 13:00:02\";s:12:\"english_name\";s:8:\"Japanese\";s:11:\"native_name\";s:9:\"日本語\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/ja.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"ja\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"次へ\";}}s:5:\"jv_ID\";a:8:{s:8:\"language\";s:5:\"jv_ID\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2019-02-16 23:58:56\";s:12:\"english_name\";s:8:\"Javanese\";s:11:\"native_name\";s:9:\"Basa Jawa\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.20/jv_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"jv\";i:2;s:3:\"jav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Nerusaké\";}}s:5:\"ka_GE\";a:8:{s:8:\"language\";s:5:\"ka_GE\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-08 19:36:41\";s:12:\"english_name\";s:8:\"Georgian\";s:11:\"native_name\";s:21:\"ქართული\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/ka_GE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ka\";i:2;s:3:\"kat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"გაგრძელება\";}}s:3:\"kab\";a:8:{s:8:\"language\";s:3:\"kab\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-09 09:53:03\";s:12:\"english_name\";s:6:\"Kabyle\";s:11:\"native_name\";s:9:\"Taqbaylit\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/6.0.1/kab.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"kab\";i:3;s:3:\"kab\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Kemmel\";}}s:2:\"kk\";a:8:{s:8:\"language\";s:2:\"kk\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2018-07-10 11:35:44\";s:12:\"english_name\";s:6:\"Kazakh\";s:11:\"native_name\";s:19:\"Қазақ тілі\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.20/kk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"kk\";i:2;s:3:\"kaz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Жалғастыру\";}}s:2:\"km\";a:8:{s:8:\"language\";s:2:\"km\";s:7:\"version\";s:6:\"5.2.15\";s:7:\"updated\";s:19:\"2019-06-10 16:18:28\";s:12:\"english_name\";s:5:\"Khmer\";s:11:\"native_name\";s:27:\"ភាសាខ្មែរ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.2.15/km.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"km\";i:2;s:3:\"khm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"បន្ត\";}}s:2:\"kn\";a:8:{s:8:\"language\";s:2:\"kn\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-10 02:38:33\";s:12:\"english_name\";s:7:\"Kannada\";s:11:\"native_name\";s:15:\"ಕನ್ನಡ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/kn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"kn\";i:2;s:3:\"kan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"ಮುಂದುವರಿಸು\";}}s:5:\"ko_KR\";a:8:{s:8:\"language\";s:5:\"ko_KR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-29 09:37:03\";s:12:\"english_name\";s:6:\"Korean\";s:11:\"native_name\";s:9:\"한국어\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/ko_KR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ko\";i:2;s:3:\"kor\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"계속\";}}s:3:\"ckb\";a:8:{s:8:\"language\";s:3:\"ckb\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2021-12-07 16:32:30\";s:12:\"english_name\";s:16:\"Kurdish (Sorani)\";s:11:\"native_name\";s:13:\"كوردی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.8.4/ckb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ku\";i:3;s:3:\"ckb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"بهردهوام به\";}}s:2:\"lo\";a:8:{s:8:\"language\";s:2:\"lo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 09:59:23\";s:12:\"english_name\";s:3:\"Lao\";s:11:\"native_name\";s:21:\"ພາສາລາວ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/lo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lo\";i:2;s:3:\"lao\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"ຕໍ່ໄປ\";}}s:5:\"lt_LT\";a:8:{s:8:\"language\";s:5:\"lt_LT\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-03-23 12:35:40\";s:12:\"english_name\";s:10:\"Lithuanian\";s:11:\"native_name\";s:15:\"Lietuvių kalba\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/lt_LT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lt\";i:2;s:3:\"lit\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Tęsti\";}}s:2:\"lv\";a:8:{s:8:\"language\";s:2:\"lv\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-28 18:55:10\";s:12:\"english_name\";s:7:\"Latvian\";s:11:\"native_name\";s:16:\"Latviešu valoda\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/lv.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lv\";i:2;s:3:\"lav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Turpināt\";}}s:5:\"mk_MK\";a:8:{s:8:\"language\";s:5:\"mk_MK\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-04-12 12:32:07\";s:12:\"english_name\";s:10:\"Macedonian\";s:11:\"native_name\";s:31:\"Македонски јазик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/mk_MK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mk\";i:2;s:3:\"mkd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Продолжи\";}}s:5:\"ml_IN\";a:8:{s:8:\"language\";s:5:\"ml_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:43:32\";s:12:\"english_name\";s:9:\"Malayalam\";s:11:\"native_name\";s:18:\"മലയാളം\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ml_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ml\";i:2;s:3:\"mal\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"തുടരുക\";}}s:2:\"mn\";a:8:{s:8:\"language\";s:2:\"mn\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-12 07:29:35\";s:12:\"english_name\";s:9:\"Mongolian\";s:11:\"native_name\";s:12:\"Монгол\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/mn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mn\";i:2;s:3:\"mon\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"Үргэлжлүүлэх\";}}s:2:\"mr\";a:8:{s:8:\"language\";s:2:\"mr\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2019-11-22 15:32:08\";s:12:\"english_name\";s:7:\"Marathi\";s:11:\"native_name\";s:15:\"मराठी\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.20/mr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mr\";i:2;s:3:\"mar\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"सुरु ठेवा\";}}s:5:\"ms_MY\";a:8:{s:8:\"language\";s:5:\"ms_MY\";s:7:\"version\";s:5:\"5.5.9\";s:7:\"updated\";s:19:\"2022-03-11 13:52:22\";s:12:\"english_name\";s:5:\"Malay\";s:11:\"native_name\";s:13:\"Bahasa Melayu\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.5.9/ms_MY.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ms\";i:2;s:3:\"msa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Teruskan\";}}s:5:\"my_MM\";a:8:{s:8:\"language\";s:5:\"my_MM\";s:7:\"version\";s:6:\"4.2.32\";s:7:\"updated\";s:19:\"2017-12-26 11:57:10\";s:12:\"english_name\";s:17:\"Myanmar (Burmese)\";s:11:\"native_name\";s:15:\"ဗမာစာ\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.2.32/my_MM.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"my\";i:2;s:3:\"mya\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:54:\"ဆက်လက်လုပ်ဆောင်ပါ။\";}}s:5:\"nb_NO\";a:8:{s:8:\"language\";s:5:\"nb_NO\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-05 23:14:19\";s:12:\"english_name\";s:19:\"Norwegian (Bokmål)\";s:11:\"native_name\";s:13:\"Norsk bokmål\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/nb_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nb\";i:2;s:3:\"nob\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsett\";}}s:5:\"ne_NP\";a:8:{s:8:\"language\";s:5:\"ne_NP\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-01 07:16:04\";s:12:\"english_name\";s:6:\"Nepali\";s:11:\"native_name\";s:18:\"नेपाली\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/ne_NP.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ne\";i:2;s:3:\"nep\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:43:\"जारी राख्नुहोस्\";}}s:5:\"nl_NL\";a:8:{s:8:\"language\";s:5:\"nl_NL\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-12 14:34:34\";s:12:\"english_name\";s:5:\"Dutch\";s:11:\"native_name\";s:10:\"Nederlands\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/nl_NL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:12:\"nl_NL_formal\";a:8:{s:8:\"language\";s:12:\"nl_NL_formal\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-06-02 21:03:02\";s:12:\"english_name\";s:14:\"Dutch (Formal)\";s:11:\"native_name\";s:20:\"Nederlands (Formeel)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/6.0.1/nl_NL_formal.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nl_BE\";a:8:{s:8:\"language\";s:5:\"nl_BE\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-01 16:21:40\";s:12:\"english_name\";s:15:\"Dutch (Belgium)\";s:11:\"native_name\";s:20:\"Nederlands (België)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/nl_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nn_NO\";a:8:{s:8:\"language\";s:5:\"nn_NO\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-03-18 10:59:16\";s:12:\"english_name\";s:19:\"Norwegian (Nynorsk)\";s:11:\"native_name\";s:13:\"Norsk nynorsk\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/nn_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nn\";i:2;s:3:\"nno\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Hald fram\";}}s:3:\"oci\";a:8:{s:8:\"language\";s:3:\"oci\";s:7:\"version\";s:6:\"4.8.19\";s:7:\"updated\";s:19:\"2017-08-25 10:03:08\";s:12:\"english_name\";s:7:\"Occitan\";s:11:\"native_name\";s:7:\"Occitan\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.8.19/oci.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"oc\";i:2;s:3:\"oci\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Contunhar\";}}s:5:\"pa_IN\";a:8:{s:8:\"language\";s:5:\"pa_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-16 05:19:43\";s:12:\"english_name\";s:7:\"Punjabi\";s:11:\"native_name\";s:18:\"ਪੰਜਾਬੀ\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/pa_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pa\";i:2;s:3:\"pan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"ਜਾਰੀ ਰੱਖੋ\";}}s:5:\"pl_PL\";a:8:{s:8:\"language\";s:5:\"pl_PL\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-19 10:58:06\";s:12:\"english_name\";s:6:\"Polish\";s:11:\"native_name\";s:6:\"Polski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/pl_PL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pl\";i:2;s:3:\"pol\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Kontynuuj\";}}s:2:\"ps\";a:8:{s:8:\"language\";s:2:\"ps\";s:7:\"version\";s:6:\"4.3.28\";s:7:\"updated\";s:19:\"2015-12-02 21:41:29\";s:12:\"english_name\";s:6:\"Pashto\";s:11:\"native_name\";s:8:\"پښتو\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.3.28/ps.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ps\";i:2;s:3:\"pus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"دوام ورکړه\";}}s:5:\"pt_PT\";a:8:{s:8:\"language\";s:5:\"pt_PT\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-09 12:26:10\";s:12:\"english_name\";s:21:\"Portuguese (Portugal)\";s:11:\"native_name\";s:10:\"Português\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/pt_PT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:10:\"pt_PT_ao90\";a:8:{s:8:\"language\";s:10:\"pt_PT_ao90\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-09 12:26:21\";s:12:\"english_name\";s:27:\"Portuguese (Portugal, AO90)\";s:11:\"native_name\";s:17:\"Português (AO90)\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/translation/core/6.0.1/pt_PT_ao90.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_BR\";a:8:{s:8:\"language\";s:5:\"pt_BR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-03 04:00:34\";s:12:\"english_name\";s:19:\"Portuguese (Brazil)\";s:11:\"native_name\";s:20:\"Português do Brasil\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/pt_BR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pt\";i:2;s:3:\"por\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_AO\";a:8:{s:8:\"language\";s:5:\"pt_AO\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2021-11-27 16:28:47\";s:12:\"english_name\";s:19:\"Portuguese (Angola)\";s:11:\"native_name\";s:20:\"Português de Angola\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.4/pt_AO.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:3:\"rhg\";a:8:{s:8:\"language\";s:3:\"rhg\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-16 13:03:18\";s:12:\"english_name\";s:8:\"Rohingya\";s:11:\"native_name\";s:8:\"Ruáinga\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/rhg.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"rhg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"ro_RO\";a:8:{s:8:\"language\";s:5:\"ro_RO\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-12 06:50:24\";s:12:\"english_name\";s:8:\"Romanian\";s:11:\"native_name\";s:8:\"Română\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/ro_RO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ro\";i:2;s:3:\"ron\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuă\";}}s:5:\"ru_RU\";a:8:{s:8:\"language\";s:5:\"ru_RU\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-06 10:04:56\";s:12:\"english_name\";s:7:\"Russian\";s:11:\"native_name\";s:14:\"Русский\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/ru_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ru\";i:2;s:3:\"rus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продолжить\";}}s:3:\"sah\";a:8:{s:8:\"language\";s:3:\"sah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-21 02:06:41\";s:12:\"english_name\";s:5:\"Sakha\";s:11:\"native_name\";s:14:\"Сахалыы\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/sah.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"sah\";i:3;s:3:\"sah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Салҕаа\";}}s:3:\"snd\";a:8:{s:8:\"language\";s:3:\"snd\";s:7:\"version\";s:6:\"5.4.10\";s:7:\"updated\";s:19:\"2020-07-07 01:53:37\";s:12:\"english_name\";s:6:\"Sindhi\";s:11:\"native_name\";s:8:\"سنڌي\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/5.4.10/snd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"sd\";i:2;s:3:\"snd\";i:3;s:3:\"snd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"اڳتي هلو\";}}s:5:\"si_LK\";a:8:{s:8:\"language\";s:5:\"si_LK\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 06:00:52\";s:12:\"english_name\";s:7:\"Sinhala\";s:11:\"native_name\";s:15:\"සිංහල\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/si_LK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"si\";i:2;s:3:\"sin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:44:\"දිගටම කරගෙන යන්න\";}}s:5:\"sk_SK\";a:8:{s:8:\"language\";s:5:\"sk_SK\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-03 07:55:52\";s:12:\"english_name\";s:6:\"Slovak\";s:11:\"native_name\";s:11:\"Slovenčina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/sk_SK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sk\";i:2;s:3:\"slk\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Pokračovať\";}}s:3:\"skr\";a:8:{s:8:\"language\";s:3:\"skr\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-14 18:02:49\";s:12:\"english_name\";s:7:\"Saraiki\";s:11:\"native_name\";s:14:\"سرائیکی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/6.0.1/skr.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"skr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"جاری رکھو\";}}s:5:\"sl_SI\";a:8:{s:8:\"language\";s:5:\"sl_SI\";s:7:\"version\";s:5:\"5.9.3\";s:7:\"updated\";s:19:\"2022-02-01 10:20:40\";s:12:\"english_name\";s:9:\"Slovenian\";s:11:\"native_name\";s:13:\"Slovenščina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.9.3/sl_SI.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sl\";i:2;s:3:\"slv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Nadaljuj\";}}s:2:\"sq\";a:8:{s:8:\"language\";s:2:\"sq\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-16 11:26:37\";s:12:\"english_name\";s:8:\"Albanian\";s:11:\"native_name\";s:5:\"Shqip\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/sq.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sq\";i:2;s:3:\"sqi\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Vazhdo\";}}s:5:\"sr_RS\";a:8:{s:8:\"language\";s:5:\"sr_RS\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2021-08-01 21:21:06\";s:12:\"english_name\";s:7:\"Serbian\";s:11:\"native_name\";s:23:\"Српски језик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.8.4/sr_RS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sr\";i:2;s:3:\"srp\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:14:\"Настави\";}}s:5:\"sv_SE\";a:8:{s:8:\"language\";s:5:\"sv_SE\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-05 06:43:41\";s:12:\"english_name\";s:7:\"Swedish\";s:11:\"native_name\";s:7:\"Svenska\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/sv_SE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sv\";i:2;s:3:\"swe\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Fortsätt\";}}s:2:\"sw\";a:8:{s:8:\"language\";s:2:\"sw\";s:7:\"version\";s:6:\"5.3.12\";s:7:\"updated\";s:19:\"2019-10-13 15:35:35\";s:12:\"english_name\";s:7:\"Swahili\";s:11:\"native_name\";s:9:\"Kiswahili\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.3.12/sw.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sw\";i:2;s:3:\"swa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Endelea\";}}s:3:\"szl\";a:8:{s:8:\"language\";s:3:\"szl\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-24 19:58:14\";s:12:\"english_name\";s:8:\"Silesian\";s:11:\"native_name\";s:17:\"Ślōnskŏ gŏdka\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/szl.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"szl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:13:\"Kōntynuować\";}}s:5:\"ta_IN\";a:8:{s:8:\"language\";s:5:\"ta_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:22:47\";s:12:\"english_name\";s:5:\"Tamil\";s:11:\"native_name\";s:15:\"தமிழ்\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ta_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ta\";i:2;s:3:\"tam\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"தொடரவும்\";}}s:5:\"ta_LK\";a:8:{s:8:\"language\";s:5:\"ta_LK\";s:7:\"version\";s:6:\"4.2.32\";s:7:\"updated\";s:19:\"2015-12-03 01:07:44\";s:12:\"english_name\";s:17:\"Tamil (Sri Lanka)\";s:11:\"native_name\";s:15:\"தமிழ்\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.2.32/ta_LK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ta\";i:2;s:3:\"tam\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"தொடர்க\";}}s:2:\"te\";a:8:{s:8:\"language\";s:2:\"te\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:47:39\";s:12:\"english_name\";s:6:\"Telugu\";s:11:\"native_name\";s:18:\"తెలుగు\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/te.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"te\";i:2;s:3:\"tel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"కొనసాగించు\";}}s:2:\"th\";a:8:{s:8:\"language\";s:2:\"th\";s:7:\"version\";s:5:\"5.8.4\";s:7:\"updated\";s:19:\"2022-06-08 04:30:30\";s:12:\"english_name\";s:4:\"Thai\";s:11:\"native_name\";s:9:\"ไทย\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.8.4/th.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"th\";i:2;s:3:\"tha\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"ต่อไป\";}}s:2:\"tl\";a:8:{s:8:\"language\";s:2:\"tl\";s:7:\"version\";s:6:\"4.8.19\";s:7:\"updated\";s:19:\"2017-09-30 09:04:29\";s:12:\"english_name\";s:7:\"Tagalog\";s:11:\"native_name\";s:7:\"Tagalog\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8.19/tl.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tl\";i:2;s:3:\"tgl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Magpatuloy\";}}s:5:\"tr_TR\";a:8:{s:8:\"language\";s:5:\"tr_TR\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-17 18:26:53\";s:12:\"english_name\";s:7:\"Turkish\";s:11:\"native_name\";s:8:\"Türkçe\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/tr_TR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tr\";i:2;s:3:\"tur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Devam\";}}s:5:\"tt_RU\";a:8:{s:8:\"language\";s:5:\"tt_RU\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-20 20:20:50\";s:12:\"english_name\";s:5:\"Tatar\";s:11:\"native_name\";s:19:\"Татар теле\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/tt_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tt\";i:2;s:3:\"tat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"дәвам итү\";}}s:3:\"tah\";a:8:{s:8:\"language\";s:3:\"tah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-06 18:39:39\";s:12:\"english_name\";s:8:\"Tahitian\";s:11:\"native_name\";s:10:\"Reo Tahiti\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/tah.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"ty\";i:2;s:3:\"tah\";i:3;s:3:\"tah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"ug_CN\";a:8:{s:8:\"language\";s:5:\"ug_CN\";s:7:\"version\";s:6:\"4.9.20\";s:7:\"updated\";s:19:\"2021-07-03 18:41:33\";s:12:\"english_name\";s:6:\"Uighur\";s:11:\"native_name\";s:16:\"ئۇيغۇرچە\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.9.20/ug_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ug\";i:2;s:3:\"uig\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:26:\"داۋاملاشتۇرۇش\";}}s:2:\"uk\";a:8:{s:8:\"language\";s:2:\"uk\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-05-24 11:42:59\";s:12:\"english_name\";s:9:\"Ukrainian\";s:11:\"native_name\";s:20:\"Українська\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/uk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uk\";i:2;s:3:\"ukr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продовжити\";}}s:2:\"ur\";a:8:{s:8:\"language\";s:2:\"ur\";s:7:\"version\";s:6:\"5.4.10\";s:7:\"updated\";s:19:\"2020-04-09 11:17:33\";s:12:\"english_name\";s:4:\"Urdu\";s:11:\"native_name\";s:8:\"اردو\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.4.10/ur.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ur\";i:2;s:3:\"urd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"جاری رکھیں\";}}s:5:\"uz_UZ\";a:8:{s:8:\"language\";s:5:\"uz_UZ\";s:7:\"version\";s:8:\"5.8-beta\";s:7:\"updated\";s:19:\"2021-02-28 12:02:22\";s:12:\"english_name\";s:5:\"Uzbek\";s:11:\"native_name\";s:11:\"O‘zbekcha\";s:7:\"package\";s:67:\"https://downloads.wordpress.org/translation/core/5.8-beta/uz_UZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uz\";i:2;s:3:\"uzb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Davom etish\";}}s:2:\"vi\";a:8:{s:8:\"language\";s:2:\"vi\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-03 11:30:24\";s:12:\"english_name\";s:10:\"Vietnamese\";s:11:\"native_name\";s:14:\"Tiếng Việt\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/6.0.1/vi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"vi\";i:2;s:3:\"vie\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Tiếp tục\";}}s:5:\"zh_CN\";a:8:{s:8:\"language\";s:5:\"zh_CN\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-08-12 08:01:44\";s:12:\"english_name\";s:15:\"Chinese (China)\";s:11:\"native_name\";s:12:\"简体中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/zh_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"继续\";}}s:5:\"zh_TW\";a:8:{s:8:\"language\";s:5:\"zh_TW\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-12 07:42:16\";s:12:\"english_name\";s:16:\"Chinese (Taiwan)\";s:11:\"native_name\";s:12:\"繁體中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/zh_TW.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}s:5:\"zh_HK\";a:8:{s:8:\"language\";s:5:\"zh_HK\";s:7:\"version\";s:5:\"6.0.1\";s:7:\"updated\";s:19:\"2022-07-15 15:25:03\";s:12:\"english_name\";s:19:\"Chinese (Hong Kong)\";s:11:\"native_name\";s:16:\"香港中文版 \";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/6.0.1/zh_HK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}}','no'); /*!40000 ALTER TABLE `wp_options` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_postmeta` -- DROP TABLE IF EXISTS `wp_postmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) 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 AUTO_INCREMENT=36 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_postmeta` -- LOCK TABLES `wp_postmeta` WRITE; /*!40000 ALTER TABLE `wp_postmeta` DISABLE KEYS */; INSERT INTO `wp_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'),(3,4,'_elementor_edit_mode','builder'),(4,4,'_elementor_template_type','kit'),(5,1,'_uag_page_assets','a:7:{s:3:\"css\";s:0:\"\";s:2:\"js\";s:0:\"\";s:18:\"current_block_list\";a:1:{i:0;s:14:\"core/paragraph\";}s:8:\"uag_flag\";b:0;s:11:\"uag_version\";s:10:\"1644918235\";s:6:\"gfonts\";a:0:{}s:14:\"uag_faq_layout\";b:0;}'),(6,7,'_wpcode_auto_insert','1'),(7,7,'_wpcode_auto_insert_number','1'),(8,8,'_wpcode_auto_insert','1'),(9,8,'_wpcode_library_id','12'),(10,10,'_wp_attached_file','2022/08/espresso.jpg'),(11,10,'_wp_attachment_metadata','a:6:{s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:4:\"file\";s:20:\"2022/08/espresso.jpg\";s:8:\"filesize\";i:93540;s:5:\"sizes\";a:7:{s:6:\"medium\";a:5:{s:4:\"file\";s:20:\"espresso-300x180.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:7442;}s:5:\"large\";a:5:{s:4:\"file\";s:21:\"espresso-1024x614.jpg\";s:5:\"width\";i:1024;s:6:\"height\";i:614;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:44890;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:20:\"espresso-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:4134;}s:12:\"medium_large\";a:5:{s:4:\"file\";s:20:\"espresso-768x461.jpg\";s:5:\"width\";i:768;s:6:\"height\";i:461;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:28653;}s:9:\"1536x1536\";a:5:{s:4:\"file\";s:21:\"espresso-1536x922.jpg\";s:5:\"width\";i:1536;s:6:\"height\";i:922;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:87842;}s:30:\"twentyseventeen-featured-image\";a:5:{s:4:\"file\";s:22:\"espresso-2000x1200.jpg\";s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:108444;}s:32:\"twentyseventeen-thumbnail-avatar\";a:5:{s:4:\"file\";s:20:\"espresso-100x100.jpg\";s:5:\"width\";i:100;s:6:\"height\";i:100;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:2476;}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(12,10,'_starter_content_theme','twentyseventeen'),(13,10,'_customize_draft_post_name','espresso'),(14,11,'_wp_attached_file','2022/08/sandwich.jpg'),(15,11,'_wp_attachment_metadata','a:6:{s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:4:\"file\";s:20:\"2022/08/sandwich.jpg\";s:8:\"filesize\";i:171858;s:5:\"sizes\";a:7:{s:6:\"medium\";a:5:{s:4:\"file\";s:20:\"sandwich-300x180.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:12751;}s:5:\"large\";a:5:{s:4:\"file\";s:21:\"sandwich-1024x614.jpg\";s:5:\"width\";i:1024;s:6:\"height\";i:614;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:89660;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:20:\"sandwich-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:6418;}s:12:\"medium_large\";a:5:{s:4:\"file\";s:20:\"sandwich-768x461.jpg\";s:5:\"width\";i:768;s:6:\"height\";i:461;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:56777;}s:9:\"1536x1536\";a:5:{s:4:\"file\";s:21:\"sandwich-1536x922.jpg\";s:5:\"width\";i:1536;s:6:\"height\";i:922;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:168760;}s:30:\"twentyseventeen-featured-image\";a:5:{s:4:\"file\";s:22:\"sandwich-2000x1200.jpg\";s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:201066;}s:32:\"twentyseventeen-thumbnail-avatar\";a:5:{s:4:\"file\";s:20:\"sandwich-100x100.jpg\";s:5:\"width\";i:100;s:6:\"height\";i:100;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:3493;}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(16,11,'_starter_content_theme','twentyseventeen'),(17,11,'_customize_draft_post_name','sandwich'),(18,12,'_wp_attached_file','2022/08/coffee.jpg'),(19,12,'_wp_attachment_metadata','a:6:{s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:4:\"file\";s:18:\"2022/08/coffee.jpg\";s:8:\"filesize\";i:117713;s:5:\"sizes\";a:7:{s:6:\"medium\";a:5:{s:4:\"file\";s:18:\"coffee-300x180.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:9082;}s:5:\"large\";a:5:{s:4:\"file\";s:19:\"coffee-1024x614.jpg\";s:5:\"width\";i:1024;s:6:\"height\";i:614;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:57102;}s:9:\"thumbnail\";a:5:{s:4:\"file\";s:18:\"coffee-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:5173;}s:12:\"medium_large\";a:5:{s:4:\"file\";s:18:\"coffee-768x461.jpg\";s:5:\"width\";i:768;s:6:\"height\";i:461;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:36609;}s:9:\"1536x1536\";a:5:{s:4:\"file\";s:19:\"coffee-1536x922.jpg\";s:5:\"width\";i:1536;s:6:\"height\";i:922;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:107588;}s:30:\"twentyseventeen-featured-image\";a:5:{s:4:\"file\";s:20:\"coffee-2000x1200.jpg\";s:5:\"width\";i:2000;s:6:\"height\";i:1200;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:138346;}s:32:\"twentyseventeen-thumbnail-avatar\";a:5:{s:4:\"file\";s:18:\"coffee-100x100.jpg\";s:5:\"width\";i:100;s:6:\"height\";i:100;s:9:\"mime-type\";s:10:\"image/jpeg\";s:8:\"filesize\";i:2934;}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(20,12,'_starter_content_theme','twentyseventeen'),(21,12,'_customize_draft_post_name','coffee'),(22,13,'_customize_draft_post_name','home'),(23,13,'_customize_changeset_uuid','990ef852-493f-4c7e-88d4-a7b8db8016d0'),(24,14,'_thumbnail_id','11'),(25,14,'_customize_draft_post_name','about'),(26,14,'_customize_changeset_uuid','990ef852-493f-4c7e-88d4-a7b8db8016d0'),(27,15,'_thumbnail_id','10'),(28,15,'_customize_draft_post_name','contact'),(29,15,'_customize_changeset_uuid','990ef852-493f-4c7e-88d4-a7b8db8016d0'),(30,16,'_thumbnail_id','12'),(31,16,'_customize_draft_post_name','blog'),(32,16,'_customize_changeset_uuid','990ef852-493f-4c7e-88d4-a7b8db8016d0'),(33,17,'_thumbnail_id','10'),(34,17,'_customize_draft_post_name','a-homepage-section'),(35,17,'_customize_changeset_uuid','990ef852-493f-4c7e-88d4-a7b8db8016d0'); /*!40000 ALTER TABLE `wp_postmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_posts` -- DROP TABLE IF EXISTS `wp_posts`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext 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 AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_posts` -- LOCK TABLES `wp_posts` WRITE; /*!40000 ALTER TABLE `wp_posts` DISABLE KEYS */; INSERT INTO `wp_posts` VALUES (1,1,'2021-11-02 06:49:23','2021-11-02 06:49:23','\nWelcome to WordPress. This is your first post. Edit or delete it, then start writing!
\n','Hello world!','','publish','open','open','','hello-world','','','2021-11-02 06:49:23','2021-11-02 06:49:23','',0,'https://wordpress-56409-0.cloudclusters.net/?p=1',0,'post','',1),(2,1,'2021-11-02 06:49:23','2021-11-02 06:49:23','\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','','','2021-11-02 06:49:23','2021-11-02 06:49:23','',0,'https://wordpress-56409-0.cloudclusters.net/?page_id=2',0,'page','',0),(3,1,'2021-11-02 06:49:23','2021-11-02 06:49:23','Suggested text: Our website address is: https://wordpress-56409-0.cloudclusters.net.
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','','','2021-11-02 06:49:23','2021-11-02 06:49:23','',0,'https://wordpress-56409-0.cloudclusters.net/?page_id=3',0,'page','',0),(4,0,'2021-11-02 07:05:59','2021-11-02 07:05:59','','Default Kit','','publish','closed','closed','','default-kit','','','2021-11-02 07:05:59','2021-11-02 07:05:59','',0,'https://wordpress-56409-0.cloudclusters.net/?p=4',0,'elementor_library','',0),(7,1,'2022-08-12 09:37:02','0000-00-00 00:00:00','Thank you for reading this post, don\'t forget to subscribe!','Display a message after the 1st paragraph of posts','','draft','closed','closed','','','','','2022-08-12 09:37:02','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?post_type=wpcode&p=7',0,'wpcode','',0),(8,1,'2022-08-12 09:37:03','0000-00-00 00:00:00','add_action(\'admin_init\', function () {\r\n // Redirect any user trying to access comments page\r\n global $pagenow;\r\n \r\n if ($pagenow === \'edit-comments.php\') {\r\n wp_safe_redirect(admin_url());\r\n exit;\r\n }\r\n\r\n // Remove comments metabox from dashboard\r\n remove_meta_box(\'dashboard_recent_comments\', \'dashboard\', \'normal\');\r\n\r\n // Disable support for comments and trackbacks in post types\r\n foreach (get_post_types() as $post_type) {\r\n if (post_type_supports($post_type, \'comments\')) {\r\n remove_post_type_support($post_type, \'comments\');\r\n remove_post_type_support($post_type, \'trackbacks\');\r\n }\r\n }\r\n});\r\n\r\n// Close comments on the front-end\r\nadd_filter(\'comments_open\', \'__return_false\', 20, 2);\r\nadd_filter(\'pings_open\', \'__return_false\', 20, 2);\r\n\r\n// Hide existing comments\r\nadd_filter(\'comments_array\', \'__return_empty_array\', 10, 2);\r\n\r\n// Remove comments page in menu\r\nadd_action(\'admin_menu\', function () {\r\n remove_menu_page(\'edit-comments.php\');\r\n});\r\n\r\n// Remove comments links from admin bar\r\nadd_action(\'init\', function () {\r\n if (is_admin_bar_showing()) {\r\n remove_action(\'admin_bar_menu\', \'wp_admin_bar_comments_menu\', 60);\r\n }\r\n});','Completely Disable Comments','','draft','closed','closed','','','','','2022-08-12 09:37:03','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?post_type=wpcode&p=8',0,'wpcode','',0),(9,1,'2022-08-12 09:43:47','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2022-08-12 09:43:47','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?p=9',0,'post','',0),(10,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','','Espresso','','auto-draft','open','closed','','','','','2022-08-12 09:55:06','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/wp-content/uploads/2022/08/espresso.jpg',0,'attachment','image/jpeg',0),(11,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','','Sandwich','','auto-draft','open','closed','','','','','2022-08-12 09:55:07','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/wp-content/uploads/2022/08/sandwich.jpg',0,'attachment','image/jpeg',0),(12,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','','Coffee','','auto-draft','open','closed','','','','','2022-08-12 09:55:08','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/wp-content/uploads/2022/08/coffee.jpg',0,'attachment','image/jpeg',0),(13,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','\nWelcome to your site! This is your homepage, which is what most visitors will see when they come to your site for the first time.
\n','Home','','auto-draft','closed','closed','','','','','2022-08-12 09:55:09','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?page_id=13',0,'page','',0),(14,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','\nYou might be an artist who would like to introduce yourself and your work here or maybe you’re a business with a mission to describe.
\n','About','','auto-draft','closed','closed','','','','','2022-08-12 09:55:10','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?page_id=14',0,'page','',0),(15,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','\nThis is a page with some basic contact information, such as an address and phone number. You might also try a plugin to add a contact form.
\n','Contact','','auto-draft','closed','closed','','','','','2022-08-12 09:55:10','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?page_id=15',0,'page','',0),(16,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','','Blog','','auto-draft','closed','closed','','','','','2022-08-12 09:55:10','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?page_id=16',0,'page','',0),(17,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','\nThis is an example of a homepage section. Homepage sections can be any page other than the homepage itself, including the page that shows your latest blog posts.
\n','A homepage section','','auto-draft','closed','closed','','','','','2022-08-12 09:55:10','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?page_id=17',0,'page','',0),(18,1,'2022-08-12 09:55:10','0000-00-00 00:00:00','{\n \"widget_text[2]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjc6IkZpbmQgVXMiO3M6NDoidGV4dCI7czoxNjg6IjxzdHJvbmc+QWRkcmVzczwvc3Ryb25nPgoxMjMgTWFpbiBTdHJlZXQKTmV3IFlvcmssIE5ZIDEwMDAxCgo8c3Ryb25nPkhvdXJzPC9zdHJvbmc+Ck1vbmRheSZuZGFzaDtGcmlkYXk6IDk6MDBBTSZuZGFzaDs1OjAwUE0KU2F0dXJkYXkgJmFtcDsgU3VuZGF5OiAxMTowMEFNJm5kYXNoOzM6MDBQTSI7czo2OiJmaWx0ZXIiO2I6MTtzOjY6InZpc3VhbCI7YjoxO30=\",\n \"title\": \"Find Us\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"119711175074fe86a117df98d6646a75\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"widget_search[3]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YToxOntzOjU6InRpdGxlIjtzOjY6IlNlYXJjaCI7fQ==\",\n \"title\": \"Search\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"23ef4e7ef8b189f14da6f28057d78dea\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"widget_text[3]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjE1OiJBYm91dCBUaGlzIFNpdGUiO3M6NDoidGV4dCI7czo4NToiVGhpcyBtYXkgYmUgYSBnb29kIHBsYWNlIHRvIGludHJvZHVjZSB5b3Vyc2VsZiBhbmQgeW91ciBzaXRlIG9yIGluY2x1ZGUgc29tZSBjcmVkaXRzLiI7czo2OiJmaWx0ZXIiO2I6MTtzOjY6InZpc3VhbCI7YjoxO30=\",\n \"title\": \"About This Site\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"b5e530315f1381720be813a3188e4e43\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"sidebars_widgets[sidebar-1]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-2\",\n \"search-3\",\n \"text-3\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"widget_text[4]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjc6IkZpbmQgVXMiO3M6NDoidGV4dCI7czoxNjg6IjxzdHJvbmc+QWRkcmVzczwvc3Ryb25nPgoxMjMgTWFpbiBTdHJlZXQKTmV3IFlvcmssIE5ZIDEwMDAxCgo8c3Ryb25nPkhvdXJzPC9zdHJvbmc+Ck1vbmRheSZuZGFzaDtGcmlkYXk6IDk6MDBBTSZuZGFzaDs1OjAwUE0KU2F0dXJkYXkgJmFtcDsgU3VuZGF5OiAxMTowMEFNJm5kYXNoOzM6MDBQTSI7czo2OiJmaWx0ZXIiO2I6MTtzOjY6InZpc3VhbCI7YjoxO30=\",\n \"title\": \"Find Us\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"119711175074fe86a117df98d6646a75\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"sidebars_widgets[sidebar-2]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-4\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"widget_text[5]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjE1OiJBYm91dCBUaGlzIFNpdGUiO3M6NDoidGV4dCI7czo4NToiVGhpcyBtYXkgYmUgYSBnb29kIHBsYWNlIHRvIGludHJvZHVjZSB5b3Vyc2VsZiBhbmQgeW91ciBzaXRlIG9yIGluY2x1ZGUgc29tZSBjcmVkaXRzLiI7czo2OiJmaWx0ZXIiO2I6MTtzOjY6InZpc3VhbCI7YjoxO30=\",\n \"title\": \"About This Site\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"b5e530315f1381720be813a3188e4e43\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"widget_search[4]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YToxOntzOjU6InRpdGxlIjtzOjY6IlNlYXJjaCI7fQ==\",\n \"title\": \"Search\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"23ef4e7ef8b189f14da6f28057d78dea\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"sidebars_widgets[sidebar-3]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-5\",\n \"search-4\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menus_created_posts\": {\n \"starter_content\": true,\n \"value\": [\n 10,\n 11,\n 12,\n 13,\n 14,\n 15,\n 16,\n 17\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Top Menu\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"custom\",\n \"title\": \"Home\",\n \"url\": \"https://wordpress-56409-0.cloudclusters.net/\",\n \"position\": 0,\n \"nav_menu_term_id\": -1,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-2]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 14,\n \"position\": 1,\n \"nav_menu_term_id\": -1,\n \"title\": \"About\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-3]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 16,\n \"position\": 2,\n \"nav_menu_term_id\": -1,\n \"title\": \"Blog\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-4]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 15,\n \"position\": 3,\n \"nav_menu_term_id\": -1,\n \"title\": \"Contact\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"twentyseventeen::nav_menu_locations[top]\": {\n \"starter_content\": true,\n \"value\": -1,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Social Links Menu\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Yelp\",\n \"url\": \"https://www.yelp.com\",\n \"position\": 0,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-6]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Facebook\",\n \"url\": \"https://www.facebook.com/wordpress\",\n \"position\": 1,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-7]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Twitter\",\n \"url\": \"https://twitter.com/wordpress\",\n \"position\": 2,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-8]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Instagram\",\n \"url\": \"https://www.instagram.com/explore/tags/wordcamp/\",\n \"position\": 3,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"nav_menu_item[-9]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Email\",\n \"url\": \"mailto:wordpress@example.com\",\n \"position\": 4,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"twentyseventeen::nav_menu_locations[social]\": {\n \"starter_content\": true,\n \"value\": -5,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"show_on_front\": {\n \"starter_content\": true,\n \"value\": \"page\",\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"page_on_front\": {\n \"starter_content\": true,\n \"value\": 13,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"page_for_posts\": {\n \"starter_content\": true,\n \"value\": 16,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"twentyseventeen::panel_1\": {\n \"starter_content\": true,\n \"value\": 17,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"twentyseventeen::panel_2\": {\n \"starter_content\": true,\n \"value\": 14,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"twentyseventeen::panel_3\": {\n \"starter_content\": true,\n \"value\": 16,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n },\n \"twentyseventeen::panel_4\": {\n \"starter_content\": true,\n \"value\": 15,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2022-08-12 09:55:10\"\n }\n}','','','auto-draft','closed','closed','','990ef852-493f-4c7e-88d4-a7b8db8016d0','','','2022-08-12 09:55:10','0000-00-00 00:00:00','',0,'https://wordpress-56409-test.cloudclusters.net/?p=18',0,'customize_changeset','',0); /*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_term_relationships` -- DROP TABLE IF EXISTS `wp_term_relationships`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_term_relationships` ( `object_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`object_id`,`term_taxonomy_id`), KEY `term_taxonomy_id` (`term_taxonomy_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_term_relationships` -- LOCK TABLES `wp_term_relationships` WRITE; /*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */; INSERT INTO `wp_term_relationships` VALUES (1,1,0),(7,2,0),(7,3,0),(7,4,0),(7,5,0),(8,4,0),(8,6,0),(8,7,0),(8,8,0),(8,9,0); /*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_term_taxonomy` -- DROP TABLE IF EXISTS `wp_term_taxonomy`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `taxonomy` varchar(32) 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 AUTO_INCREMENT=10 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_term_taxonomy` -- LOCK TABLES `wp_term_taxonomy` WRITE; /*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */; INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1),(2,2,'wpcode_type','',0,1),(3,3,'wpcode_location','',0,1),(4,4,'wpcode_tags','',0,2),(5,5,'wpcode_tags','',0,1),(6,6,'wpcode_type','',0,1),(7,7,'wpcode_location','',0,1),(8,8,'wpcode_tags','',0,1),(9,9,'wpcode_tags','',0,1); /*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_termmeta` -- DROP TABLE IF EXISTS `wp_termmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_termmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) 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; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_termmeta` -- LOCK TABLES `wp_termmeta` WRITE; /*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_terms` -- DROP TABLE IF EXISTS `wp_terms`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_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 AUTO_INCREMENT=10 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_terms` -- LOCK TABLES `wp_terms` WRITE; /*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */; INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0),(2,'text','text',0),(3,'after_paragraph','after_paragraph',0),(4,'sample','sample',0),(5,'message','message',0),(6,'php','php',0),(7,'everywhere','everywhere',0),(8,'disable','disable',0),(9,'comments','comments',0); /*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_usermeta` -- DROP TABLE IF EXISTS `wp_usermeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) 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 AUTO_INCREMENT=21 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_usermeta` -- LOCK TABLES `wp_usermeta` WRITE; /*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */; INSERT INTO `wp_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,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','1'),(16,1,'session_tokens','a:1:{s:64:\"665c12a73d879bc8b106f4b6ab1d60081e3b1d8c167360c20e656e18dc43a7b1\";a:4:{s:10:\"expiration\";i:1660469400;s:2:\"ip\";s:13:\"113.246.94.82\";s:2:\"ua\";s:110:\"Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36\";s:5:\"login\";i:1660296600;}}'),(17,1,'wp_dashboard_quick_press_last_post_id','9'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:12:\"113.246.94.0\";}'),(19,1,'theme-min-version-notice-min-ver','3.7.5'),(20,1,'w3tc_features_seen','a:2:{i:1;s:12:\"imageservice\";i:2;s:11:\"setup_guide\";}'); /*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_users` -- DROP TABLE IF EXISTS `wp_users`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_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 AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_users` -- LOCK TABLES `wp_users` WRITE; /*!40000 ALTER TABLE `wp_users` DISABLE KEYS */; INSERT INTO `wp_users` VALUES (1,'admin','$P$BpVHGAvkdTgrOFW8fYsuvcyeRZkyC7.','admin','example@cloudclusters.io','https://wordpress-56409-0.cloudclusters.net','2021-11-02 06:49:23','',0,'admin'); /*!40000 ALTER TABLE `wp_users` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!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 */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2022-08-12 10:02:45