 to be said for really new perspectives and I love when people comment saying, hey, this is my first time using full site editing and here are my thoughts. That&rsquo;s excellent. But the idea of quality over quantity, I think is really key, for this phase of testing. I think when things actually get merged into core and certain aspects get merged into core, that&rsquo;s when things can open up and be a bit more, having 2000 people give feedback, but yeah, I don&rsquo;t think there&rsquo;s ever enough testing and honestly, I do worry about that.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>And it&rsquo;s something, one of the things I&rsquo;ve been very intentional about is reaching out to the accessibility team to try and get people to help give feedback so that we&rsquo;re thinking about accessibility needs and reaching out to folks in the polyglot space so that we have translations of these posts so that people can participate. I only speak English and I had been in countries where all of a sudden, you see something in English and it&rsquo;s like this it&rsquo;s like such a relief to have a menu in English. Like, Oh yes, this is so nice. And I want that outreach to happen because I think sometimes the software development I&rsquo;ve seen this like arrogance of, oh well, we&rsquo;ll just be doing the work and if they&rsquo;re curious, they can come to us. And I actually think this is one of those situations where we need to go to them. And that&rsquo;s what the outreach program is all about is meeting people where they are doing the outreach. Bringing people along with us and learning from them as we go. Part education, part feedback loop, and part, hey, here&rsquo;s a really easy way to get involved and walk you through what&rsquo;s coming.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>I would love to see more engagement from folks who are non-English speaking. We&rsquo;ve had Italian, Spanish and Japanese translations very consistently. I&rsquo;m so grateful for the people who&rsquo;ve done that. I think it&rsquo;s just, oh, I&rsquo;m so bad at languages that it just amazes me. I also think everything looks better in a different language. So it&rsquo;s neat to see my own words translated, which is a kind of a wild experience that I never thought would happen, but I&rsquo;d love to see more engagement. In those polyglot and local spaces, because the last thing you want is for all of a sudden it to land and only a specific audience benefits or sees this or understands it or knows what&rsquo;s coming, right. There&rsquo;s a big responsibility for 40% of the internet. And I&rsquo;ll never forget the day that Matt at a State of the Word said that non-English downloads passed English downloads. And so when you think about that 40% I think a lot of us English speaking, Western world think of a certain type of person, but really it&rsquo;s much more expansive than that.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>So I&rsquo;ve been really hammering the polyglot space as much as I can, as much as volunteer time people can give to translate those posts and to try and get feedback. But it&rsquo;s something that I&rsquo;d love to see more of.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-1\"><div class=\"chat-author chat-author-nathanwrigley vcard\"><cite class=\"fn\">Nathan Wrigley</cite> [00:32:22]</div> <div class=\"chat-text\"><p>I&rsquo;m curious actually, if you&rsquo;ve got a really nice concrete example of an instance where somebody&rsquo;s feedback turned into something actual. It was realized off the back of a piece of feedback, which you passed on to the team, and somebody reached out said, I would like this. And you were able to provide this, Hearing those stories. Ah, it is possible.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"><div class=\"chat-author chat-author-annemccarthy vcard\"><cite class=\"fn\">Anne McCarthy</cite> [00:32:44]</div> <div class=\"chat-text\"><p>Yeah, I can think of a really specific example that I was actually thinking about this morning when I was making coffee. A blind developer, I got connected with her through actually posting in a different Slack community. So, you would not believe how many Slack communities I&rsquo;m a part of and how much I try to drop links and engage people in different spaces. And I got connected because someone said, hey, I have a friend she&rsquo;s blind, she&rsquo;s a WordPress developer, and she cannot use full site editing. And I was like, whoa, tell me everything.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>How can I get in touch, and got in touch, her name&rsquo;s Taylor. And she very kindly jumped on for about 30 minutes. We recorded the session so that I could pass along the feedback. She just walked me through the experience of both using of using two different screenreader tools. And. It was fascinating. It was awesome.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>We found so many bugs. It was one of those things where I think the biggest, the most jarring one that I keep thinking about that I actually want to see if we can get some development in on ASAP, is that the save button, and the saving process for full site editing right now is pretty non-intuitive, it&rsquo;s a little bit clunky and it&rsquo;s something that&rsquo;s come up with sighted folks as well. What is the saving process, how does it work? But for people who rely on screen readers, it&rsquo;s really impossible to save. Like you basically have to search for the phrase save in order to find the save button because there isn&rsquo;t an aria label. And so that&rsquo;s a big one that came up and on top of that in just the session, I worked with her another piece of feedback that came up with the columns block.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>So if you have columns and you&rsquo;re imagining, let&rsquo;s say two columns and you are using a screen reader, it doesn&rsquo;t tell you which column is which. So all of you here just announces column, column it doesn&rsquo;t say like column one or column two or right column or left column. There&rsquo;s no identifier for how to navigate.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>And so that&rsquo;s actually, there&rsquo;s a PR right now that&rsquo;s underway. I actually just filed it for the accessibility team last week to see if someone could review and someone already stepped in to offer some thoughts to fix that, to actually announce, I think they&rsquo;re going with like column one and column two and column three rather than right and left due to internationalization. And that&rsquo;s going to be a huge improvement because right now Taylor was just like, columns block is so confusing. This is almost useless. Another one is the spacer block. I&rsquo;d love to hear. If you use a screen reader, I&rsquo;d love to hear your experiences with the spacer block, because that&rsquo;s a really confusing block for people I&rsquo;m relying on screen readers.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>And I opened up an issue for that, and we&rsquo;ve had some discussion back and forth about improvements that need to be made there as well. So those are some of the, and I can tell you, there&rsquo;s probably about. I think six issues I opened just from that 30 minute conversation. Some are like a work in progress, but this was very recent and something I keep thinking about, especially as we start to refine things and decision points come up because we don&rsquo;t want to release something that has such blatant problems with it.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-1\"><div class=\"chat-author chat-author-nathanwrigley vcard\"><cite class=\"fn\">Nathan Wrigley</cite> [00:35:24]</div> <div class=\"chat-text\"><p>It marks a very big change for WordPress this last couple of years have been really extraordinarily different, the experience that we&rsquo;re all going through, but in particular, around full site editing How do you calm people&rsquo;s fears that things in the future are going to be going in the direction that they wish it to go in. So, as an example, let&rsquo;s imagine that we&rsquo;re a theme developer. We may be getting concerned that themes are going to become a thing of the past that the livelihood that we&rsquo;ve created for ourselves is going to disappear before our eyes. People concerned that the way that they&rsquo;re working with at the moment, the way that they&rsquo;ve taught their clients to work, this is how WordPress works, and this is how you can manage your website for yourself, and so on. What do you say to people? What is the golden light on the hill? The thing that you draw attention to, to say, look, all of this will be worth it. How do you keep people focused on the positives and not worrying about all the different things that are going on left right and center?</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"><div class=\"chat-author chat-author-annemccarthy vcard\"><cite class=\"fn\">Anne McCarthy</cite> [00:36:20]</div> <div class=\"chat-text\"><p>Yeah. The biggest thing I say is there&rsquo;s a reason that the last milestone is gradual adoption. And one of the things that I also love to talk about is the fact that full site editing is a bunch of sub projects actually gives us the flexibility to ship reliable items rather than shipping it all at once.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>Yes, they&rsquo;re interdependent. Yes. And some cases they rely on each other and there needs to be probably a certain order or approach to releasing things. But by having so many different tools that provide value. It actually gives us the ability to step back and say, okay, what&rsquo;s ready. And that should be a big relief to people.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>It&rsquo;s not like there&rsquo;s going to be this on-off switch full savings here is taking over your site. Good luck. That&rsquo;s not going to happen. Gradual adoption is the game plan. It is the final step. And I imagine right now, a gradual adoption as a milestone is not fleshed out. But I imagine, especially you have to 5.8, that will become a much more fleshed out milestone in the same way you see other milestones, I think, Josepha has talked a lot about this, and I really love the way she basically says we want to fulfill the WordPress promise. We want to keep that trust and we want to release things in the best state possible while at the same time, recognizing that there&rsquo;s this urgency to offer tools that people are just lacking right now, at some point, we need to get those out in front of people and to provide value and making that determination is super tricky. But the good news is like I was saying earlier, we have that flexibility built into the fact that these are all sub projects and that many of them can be shipped independently.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>And for theme authors, Themes are going to be so important in a full siding world. And one of the things I am so excited about is that there&rsquo;s going to be a ton of what they&rsquo;re calling. I .. the idea of these hybrid universal themes that can work with for example, template editing.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>So going and being able to edit like your single page template, your homepage template, or your 404 template. You could have a theme, that&rsquo;s a classic theme or traditional theme, whatever you want to call it. And you could use template editing. You could update your theme to hook into the tools have been made to allow for template editing.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>Same thing goes for global styles. You could just use one part of the full site editing machine, so to speak and all the projects and slowly integrate, more and more, as you want to, like theme authors will have a lot of control of what they opt into and what they opt out of. And for us building it, it&rsquo;s on us to make it so desirable to opt in.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>Right, and that&rsquo;s where the gradual adoption, so many pathways are going to be created. And I&rsquo;m actually really excited to see people move from this framework of anxiety to looking out across the space and going, hmm, what can I use? What is it that I hear from people all the time that I can integrate into this and moving into an exciting creative space rather than thinking, hh, I got to get caught up, I&rsquo;m behind. This is so bad. Like that kind of feeling, which I hear from a lot of people was like, I don&rsquo;t have time to get up to speed. And the ideal is that we&rsquo;re actually providing tools that save you time and add value. And that makes me really excited. I fully understand the fear. I fully understand the fear.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>I don&rsquo;t say that lightly. As someone who is thinking about like how it&rsquo;s going to land in 40% of the internet and who every single day is talking to people who are giving feedback about, what&rsquo;s not quite there, I don&rsquo;t spend a lot of time talking to people who are just like, oh, I&rsquo;m so excited about this.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>People don&rsquo;t go out of their way to tell you that you often hear from the people who are upset or something&rsquo;s missing or promises broken or whatever it is. And it&rsquo;s something I think about a lot. And I understand why there is panic there, especially with livelihood in the situation that we&rsquo;re in.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>And I have a lot of empathy for that. And I think in the future, and one of the things that I think you&rsquo;ll hear from leadership and you&rsquo;ve, everyone&rsquo;s priority heard this from leadership. It&rsquo;s just that we are purposely moving slowly and things get pooled for a reason. And it is to fulfill that promise and to think about backwards compatibility, but at the same time, balancing that with wanting to provide value for users and empowering users, especially in a day and age, when a lot of tech companies are actually taking away a lot of the power, whether it&rsquo;s in the form of privacy or what have you.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>I think open source and the way WordPress is working is actually trying to resist that and really focus on giving everything we can to the user, to build the site that they want and to have the experience that they want. And also to free them up, to focus on what the site actually gives them, whether it&rsquo;s a business or platform.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>I think that&rsquo;s the part that makes me&hellip; that hopefully makes other people excited. And that makes me really excited.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-1\"><div class=\"chat-author chat-author-nathanwrigley vcard\"><cite class=\"fn\">Nathan Wrigley</cite> [00:40:26]</div> <div class=\"chat-text\"><p>Speaking to that. You&rsquo;ve done an incredible job answering all of my questions and you&rsquo;ve obviously got to wear the Automattic hat during a discussion like this. I&rsquo;m curious if we cast away the Automattic hat just for a moment and we ask you personally, what in the next six months to a year, what&rsquo;s the one single thing, the thing that you are most excited about, the thing that you most want to see happen, the thing that gets you personally switched on about the project.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"><div class=\"chat-author chat-author-annemccarthy vcard\"><cite class=\"fn\">Anne McCarthy</cite> [00:40:54]</div> <div class=\"chat-text\"><p>It&rsquo;s a great question. I would have to say block patterns, because we&rsquo;re talking about all these tools and features and things coming along, but ultimately as a user, it&rsquo;s like, what can I do, and what can I do quickly? And block patterns will really be the glue that ties together all these projects. You can insert a block pattern, manipulate it as you want to. And when you&rsquo;re manipulating it, you probably won&rsquo;t be thinking about the fact that you might be using global styles or that the block pattern is relying on block styles or whatever it is.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>But the power of that. And the promise of that, I think is just such a high impact, such a high impact feature that will really be like a cherry on top. And we&rsquo;ll bring together a lot of the things that we&rsquo;re talking about in a way that will be really tangible. And especially in this world of, you know, we&rsquo;re not able to gather in person we&rsquo;re not able to have those moments.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>I think having something that is easy to understand almost the point of being, so intuitive that it&rsquo;s like, why didn&rsquo;t we do this years ago? That&rsquo;s what I want the feeling to be. And that&rsquo;s when I had someone in design, tell me this one time. And it always stuck with me as like the best ideas are the ones where you&rsquo;re like, well, no, duh, like, yeah, of course.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>And that&rsquo;s what block patterns I think you&rsquo;re going to feel like, and I think it&rsquo;s really gonna fulfill a lot of these things and bring a lot of these things that we&rsquo;re talking about together in a way that will be really fun to play with. And also people will be able to submit to the block pattern directory, ideally in the future, similar to the block plugin directory.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"><p>So personally, I&rsquo;m most excited to see the marriage between block patterns and full site editing along with these hybrid themes.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-1\"><div class=\"chat-author chat-author-nathanwrigley vcard\"><cite class=\"fn\">Nathan Wrigley</cite> [00:42:24]</div> <div class=\"chat-text\"><p>I know there will be no metric to judge this, but it would be fascinating in a couple of years time. Were we able to measure it, to see just how much of humanity&rsquo;s time has been saved by something like block patterns, the fact that you don&rsquo;t have to do things over and over again. Yeah. I completely understand why you&rsquo;ve selected that one. We have gone through so many questions. If somebody at the end of this, has been listening to this and thinks I would like to help, but I want to contact Anne directly before I go to these Slack channels and Github repos and so on. How might somebody get in touch with you should they wish to?</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"><div class=\"chat-author chat-author-annemccarthy vcard\"><cite class=\"fn\">Anne McCarthy</cite> [00:43:01]</div> <div class=\"chat-text\"><p>I would say go to my website. I am a weird millennial without social media. I jump on and off of Instagram. That&rsquo;s my one holdout. I love photography too much, but yeah, my website is nomad.blog and I have a contact page and I truly welcome to hear from anyone seriously. All I ask, and this is on my website as well. I like to do pen pal. Kind of writing back and forth. I think we don&rsquo;t rely, I think email, I&rsquo;ve read too many books about this, but I think email has ruined our ability to relax and unwind, and I refuse to opt into this always responding world. So as long as you&rsquo;re patient with me, and if I get a bunch of emails, as long as you&rsquo;re patient with me responding, I promise I will respond genuinely with a lot of thought. I do not like to do short, low quality responses. So if you&rsquo;re willing to engage there, that would be awesome to hear from you. I&rsquo;m also an annezazu in WordPress dot org Slack, if you end up joining there as well.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-1\"><div class=\"chat-author chat-author-nathanwrigley vcard\"><cite class=\"fn\">Nathan Wrigley</cite> [00:43:53]</div> <div class=\"chat-text\"><p>Well, thank you very much. I appreciate all of the hard work that you and everybody connected in the project is doing. It&rsquo;s making great inroads into our editing experience in WordPress. Greatly appreciated. Thanks for coming on the podcast.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"><div class=\"chat-author chat-author-annemccarthy vcard\"><cite class=\"fn\">Anne McCarthy</cite> [00:44:06]</div> <div class=\"chat-text\"><p>Of course. Thank you so much for having me.</p>\n</div></div><div class=\"chat-stanza chat-row chat-speaker-2\"> <div class=\"chat-text\"></div></div></div></div>\";s: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, 21 Apr 2021 14:00:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Nathan Wrigley\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:60:\"HeroPress: You Don’t Have To Want What Everyone Else Wants\";s:7:\"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=3539\";s:7:\"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:166:\"https://heropress.com/essays/you-dont-have-to-want-what-everyone-else-wants/#utm_source=rss&utm_medium=rss&utm_campaign=you-dont-have-to-want-what-everyone-else-wants\";s: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:6215:\"<img width=\"1024\" height=\"512\" src=\"https://heropress.com/wp-content/uploads/2021/04/042121-min.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: You don\'t have to want what everyone else wants.\" /><p>I launched a WordPress-based business sometime around 2013. Starting a business is a goal for a lot of people, but it was never something I intentionally set out to do. I was in university at the time and blogging about books &#8212; just doing something I loved. But then I had an idea for a WordPress plugin that would make book bloggers’ lives easier. Although I did decide to sell it instead of releasing it for free, making a lot of money was never my goal. I thought maybe I’d make $500 overall if I was lucky. But three months in I’d already made nearly $1500 and those numbers would only continue to climb.</p>\n<p>By the time I graduated university, this little business of mine was already fully paying my bills. I went straight from graduation to running a full time business. Over the next few years, I sold pre-made plugins, built custom plugins, launched custom websites for authors and bloggers, dipped into the managed WordPress hosting space, and created WordPress e-courses. Objectively, business was great.</p>\n<blockquote><p>But by 2016, I was waking up every morning and thinking, <i>“What the hell am I doing?”</i></p></blockquote>\n<p>The more my business grew, the more I was afraid it was about to crash and burn.</p>\n<p>The more I diversified, the less confident I felt about what I was doing.</p>\n<p>Above everything, I was <i>tired</i>.</p>\n<h2>Turns out, I’m not a businesswoman</h2>\n<p>I was tired of selling, of marketing, of advertising, of promoting. I was tired of asking myself <i>“will this sell?”</i> before I started a new project. I missed creating just for the sheer fun and joy of it, which was how my very first plugin even came to be. I just wanted to build cool things and quietly release them into the wild. I love to <i>create</i> but I don’t love to <i>sell</i>.</p>\n<p>Perhaps I could have hired people to help me with the aspects of my business I didn’t enjoy, but although business was going well for a one person show, I didn’t feel like it was going well enough to hire more people and confidently feel like I could pay their salary every month. And the thought of having that responsibility just brought me even more anxiety.</p>\n<blockquote><p>I felt stuck and, honestly, ashamed of how I felt about my business. Was I being ungrateful?</p></blockquote>\n<p>I had this incredible thing going for me &#8212; I was paying all my bills, working flexible hours (and from home!), and calling all the shots. This is what other people aspire to have, and I had it! I was embarrassed to admit that maybe I didn’t like it anymore. I didn’t want to be in charge. I didn’t want to have the entire success or failure of a business resting on my shoulders.</p>\n<p>I remember looking through job listings trying to imagine myself doing something else &#8212; anything else. But another problem I had was that running my own business straight out of school had spoiled me. I didn’t want to be in charge, but I also still wanted to work from home. I still wanted flexible hours. I didn’t want to sacrifice my 3pm gym session. I still wanted a certain degree of freedom in what I did each day. I wanted all the benefits of running my own business, without any of the downsides I had come to dread.</p>\n<h2>A well timed opportunity</h2>\n<p>In late 2016, sheer luck and good timing brought me to Sandhills Development. I was offered a job at a company that could amazingly check every box on my dream list. I could work from home, set my own hours, have a weird schedule, still make the gym at 3pm, and most importantly: my job would just be <i>one</i> thing. I could focus on building really cool stuff, and nothing else. I wouldn’t have to think about marketing or sales or profit.</p>\n<p>It’s been over four years since then and I’m now the lead developer for Easy Digital Downloads &#8212; the plugin I originally used to sell my first product. So I think things are going pretty well! My old business does still exist, but in a very low key way. I still work on and maintain the products out of love and passion for them, but with zero pressure to actually make sales or be successful.</p>\n<blockquote><p>The biggest difference is the boundaries I’ve been able to create in my life.</p></blockquote>\n<p>When running my own business, I didn’t work all day long, but I did tend to think about work all the time. Growth was always on my mind because making that happen was purely up to me. I was putting so much pressure on myself to do well, that I couldn’t stop thinking about it. But now, work goes away as soon as I decide I’m done for the day. I don’t think about it after hours. There’s comfort in the fact that although I care about the company, it’s not <i>my</i> company, and the success &#8212; or failure &#8212; of the company isn’t purely up to me; if something does go wrong when I’m gone, there’s someone else capable of handling it.</p>\n<h2>What works for someone else may not work for you</h2>\n<p>Some people would consider it a downgrade to go from business owner to employee, but it was absolutely the right move for me. Running your own business is often glamorized, but not everyone is cut out to wear all the hats that a one-person business requires, and not everyone has the drive to grow a business into something larger. And that’s okay. At the time, it was immensely hard for me to admit that out loud because I thought it would make me a failure.</p>\n<p>There is no “one size fits all” dream job and I learned that being the owner of a company is not mine. If what you’re doing now isn’t working then there’s absolutely no shame in bowing out, even if you’re currently living someone else’s dream.</p>\n<p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/you-dont-have-to-want-what-everyone-else-wants/\">You Don&#8217;t Have To Want What Everyone Else Wants</a> appeared first on <a rel=\"nofollow\" href=\"https://heropress.com\">HeroPress</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 21 Apr 2021 08:27:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Ashley Gibson\";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:62:\"WPTavern: WordPress Contributors Propose Blocking FLoC in 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=115316\";s:7:\"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:169:\"https://wptavern.com/wordpress-contributors-propose-blocking-floc-in-core?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-contributors-propose-blocking-floc-in-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:7493:\"<p>WordPress contributors are <a href=\"https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/\">proposing</a> the project take an active position on Google&rsquo;s Federated Learning of Cohorts (FLoC). This particular mechanism is Google&rsquo;s alternative to third-party cookies that doesn&rsquo;t require collecting users&rsquo; browsing history. The <a href=\"https://github.com/WICG/floc\">GitHub repository for FLoC</a> explains how Google will group people together and label them using machine learning:  </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>We plan to explore ways in which a browser can group together people with similar browsing habits, so that ad tech companies can observe the habits of large groups instead of the activity of individuals. Ad targeting could then be partly based on what group the person falls into.</p><p>Browsers would need a way to form clusters that are both useful and private: Useful by collecting people with similar enough interests and producing labels suitable for machine learning, and private by forming large clusters that don&rsquo;t reveal information that&rsquo;s too personal, when the clusters are created, or when they are used.</p></blockquote>\n\n\n\n<p>WordPress contributors are proposing blocking FLoC in core, citing the Electronic Frontier Foundation&rsquo;s article titled &ldquo;<a href=\"https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea\">Google&rsquo;s FLoC Is a Terrible Idea</a>.&rdquo; </p>\n\n\n\n<p>&ldquo;WordPress powers approximately 41% of the web &ndash; and this community can help combat racism, sexism, anti-LGBTQ+ discrimination and discrimination against those with mental illness with a few lines of code,&rdquo; the proposal states.</p>\n\n\n\n<p>One of the more controversial aspects of the original proposal was that it was spectacularly miscategorized as a security concern, clouding the issue at hand. It identified FLoC as a security issue for the sake of getting it into core on a more aggressive timeline, which was outlined as follows:</p>\n\n\n\n<ol><li>Include the&nbsp;patch&nbsp;the next&nbsp;minor release, rather than waiting for the next&nbsp;major release;</li><li>Back-port the patch to previous versions of WordPress.</li></ol>\n\n\n\n<p>The proposal was later revised to clarify that treating FLoC like a security concern referenced only the timeline of accelerated development and back-porting.</p>\n\n\n\n<p>Although blocking FLoC seemed to have wide support in the comments on the post, the premature suggestion of treating it as a security concern weakened the proposal. </p>\n\n\n\n<p>WordPress core committer Ryan McCue said that while he is in agreement with the overall sentiment, rolling it out like a security updatet would abuse users&rsquo; trust in automatic updates:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>The implicit contract with users for security autoupdates is that they are used in order to protect the user from their site (data or codebase) being compromised imminently. This isn&rsquo;t the case with FLoC, and may in some cases damage the site&rsquo;s behaviour.</p><p>More concretely: as someone who operates a hosting service where we keep users up-to-date with security patches, this changes our approach substantially. Right now, we can confidently roll out security updates trusting the update has minimal effect outside of purely security changes, but breaching that barrier means that now scrutiny needs to be applied to every security update in order to avoid rolling out potentially breaking changes to our clients.</p><p>That erosion of trust would ultimately hurt WP&rsquo;s users.</p></blockquote>\n\n\n\n<p>The proposal has started an active discussion with more than 100 commenters, including participation from the Chrome DevRel team who added more context on the current status of the experiment.</p>\n\n\n\n<p>&ldquo;It&rsquo;s also worth noting that because this is an origin trial it means that nothing is set in stone &mdash; this is an experiment to gather feedback,&rdquo; Chrome Developer lead Rowan Merewood said. &ldquo;The API may change, the opt-out mechanism may change, the eligibility criteria may change. Any code changes relating to an origin trial should also be treated as temporary and experimental.&rdquo;</p>\n\n\n\n<p>Those who were critical of the proposal consider FLoC a personal privacy issue that is not WordPress&rsquo; problem to solve. Others believe a proposal to block FLoC is reactionary at this point, since Google has not yet finalized its FLoC experiment. </p>\n\n\n\n<p>&ldquo;Thinking about users&hellip; i.e. the readers of a&nbsp;blog, they deserve choice,&rdquo; Andy Beard commented.</p>\n\n\n\n<p>&ldquo;They can choose which browser they use.<br />&ldquo;They can choose settings in the browser.<br />&ldquo;They can choose some overall options on a Google privacy site.<br />&ldquo;They can install a multitude of plugins.</p>\n\n\n\n<p>&ldquo;Alternatively, if WordPress blocks FLoC by default, that actually removes a choice &ndash; the choice of a user to see more relevant advertising.&rdquo;</p>\n\n\n\n<p>Several participants in the discussion were opposed to FLoC but also not supportive of a WordPress core effort to block it.</p>\n\n\n\n<p>&ldquo;While I&rsquo;m not pro-FLoC (and won&rsquo;t have my browsers using it) I certainly wouldn&rsquo;t expect a website to make the choice to opt-out for me, and I can&rsquo;t see why the majority of WordPress users and people visiting WordPress sites would expect that either,&rdquo; WordPress lead developer Dion Hulse commented.</p>\n\n\n\n<p>&ldquo;Perhaps more importantly, would WordPress also continue to opt out all future browser protocols too? Once you delve into blocking one, you&rsquo;ve either got to block them all, or you&rsquo;re playing favorites.&rdquo;</p>\n\n\n\n<p>Mika Epstein, who also expressed her opinion as anti-FLoC, said she is not in support of backporting a block due to the practicality of such an effort.</p>\n\n\n\n<p>&ldquo;If the decision is made to include this, I would support it as a&nbsp;<em>filterable privacy&nbsp;enhancement</em>&nbsp;only, not security,&rdquo; Epstein said.</p>\n\n\n\n<p>&ldquo;That said, I do&nbsp;<strong>not</strong>&nbsp;support backporting with the precedent that we did not&nbsp;backport&nbsp;the GDPR exporting stuff. Having it exist as a&nbsp;plugin&nbsp;(there are three already) is sufficient for those who are on older versions. The undue strain of increased backporting needs to be minimized, not maximized in my opinion.&rdquo;</p>\n\n\n\n<p>Others commented on the harm to independent publishers whose main source of revenue is often advertising.</p>\n\n\n\n<p>WordPress lead developer Helen Hou-Sandi requested the proposal be re-written to clarify the differences between disabling FLoC on a site level vs the browser level as a consumer. She also discouraged referring to the matter as a security issue and recommended the proposal&rsquo;s proponents justify the work required to backport the block. Hou-Sandi recommended opening a trac ticket as a more appropriate avenue of discussion regarding core implementation and inclusion, as contributors have not yet reached a consensus.</p>\n\n\n\n<p>The topic will be up for discussion at the next core developers&rsquo; chat on Wednesday, April 21, 2021. Representatives from the Chrome team <a href=\"https://make.wordpress.org/core/2021/04/20/dev-chat-agenda-for-april-21-2021/#comment-41165\">will also be attending</a> to answer any questions about FLoC.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 21 Apr 2021 05:17:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:114:\"WPTavern: Patchstack Whitepaper: 582 WordPress Security Issues Found in 2020, Over 96% From Third-Party Extensions\";s:7:\"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=115396\";s:7:\"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:267:\"https://wptavern.com/patchstack-whitepaper-582-wordpress-security-issues-found-in-2020-over-96-from-third-party-extensions?utm_source=rss&utm_medium=rss&utm_campaign=patchstack-whitepaper-582-wordpress-security-issues-found-in-2020-over-96-from-third-party-extensions\";s: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:4647:\"<p class=\"has-drop-cap\">Patchstack, which recently <a href=\"https://wptavern.com/webarx-rebrands-to-patchstack-combines-services-to-focus-on-wordpress-plugin-and-theme-security\">rebranded from WebARX</a>, released its <a href=\"https://patchstack.com/wordpress-security-2020/\">2020 security whitepaper</a>. The report identified a total of 582 security vulnerabilities. However, only 22 of the issues came from WordPress itself. Third-party plugins and themes accounted for the remaining 96.22%.</p>\n\n\n\n<p>&ldquo;These are all security issues disclosed by the Patchstack internal research team, Patchstack Red Team community, by third-party security vendors, and by other independent security researchers,&rdquo; said Oliver Sild, Patchstack founder and CEO. &ldquo;So it includes all public information about vulnerabilities.&rdquo;</p>\n\n\n\n<p>Patchstack is a security company that focuses on third-party extensions to WordPress. Its <a href=\"https://patchstack.com/database/\">vulnerability database</a> is public and available for anyone to view.</p>\n\n\n\n<p>In the second quarter of 2020, Patchstack surveyed nearly 400 web developers, freelancers, and agencies about web security. &ldquo;Over 70% responded that they were increasingly worried about the security of their website, and the top reason was &lsquo;vulnerabilities in third-party plugins,\'&rdquo; according to the whitepaper. &ldquo;About 45% of respondents saw an increase in attacks on websites they were managing, and 25% had to deal with a hacked website in the month prior to participating in the survey.&rdquo;</p>\n\n\n\n<p>Ranking at the top, 211 of the vulnerabilities found were Cross-Site Scripting (XSS) issues, 36.2% of the total.</p>\n\n\n\n<p>&ldquo;XSS in WordPress plugins almost always happens because user input data is directly printed onto the screen without any sanitization,&rdquo; said Sild. &ldquo;<code>esc_html</code> would be used to convert certain characters to their HTML entities, so it will be literally printed onto the screen. Then you also have <code>esc_attr</code> for user input variables, which need to be used in HTML attributes. There are many good resources published by <a href=\"https://owasp.org/\">OWASP</a> (The Open Web Application Security Project), such as the &lsquo;Secure Coding Practices.\'&rdquo;</p>\n\n\n\n<p>Injection vulnerabilities ranked second with 70 unique cases. It was followed by 38 Cross-Site Request Forgery (CSRF) issues and 29 instances of sensitive data exposure.</p>\n\n\n\n<p>&ldquo;The vulnerabilities found in plugins and themes tend to be more severe than those found in WordPress core,&rdquo; wrote Sild in the whitepaper. &ldquo;What makes matters worse is that many popular plugins have millions of active installations, and the numbers aren&rsquo;t pretty when we look at how many websites are affected by the vulnerable plugins.&rdquo;</p>\n\n\n\n<p>The total number of active and vulnerable theme and plugin installations throughout the year was 70 million. <a href=\"https://central.wordcamp.org/about/\">According to WordCamp Central</a>, WordPress is installed on 75 million websites. Many sites likely had more than one vulnerable plugin during 2020 rather than 70 million individual sites being at risk.</p>\n\n\n\n<p>Patchstack surveyed 50,000 websites and found that they averaged 23 active plugins at a time. About four on each site were outdated with an upgrade available, which often increases the risk of a security issue.</p>\n\n\n\n<p>WordPress plugins accounted for 478 vulnerabilities in the report. However, there were only 82 unique theme issues. While themes are typically far more limited in scope, they can do anything a plugin can do with a few exceptions.</p>\n\n\n\n<p>It is not surprising to see that number lower for themes. However, one has to wonder if the <a href=\"https://wptavern.com/upcoming-changes-and-steps-for-an-overhauled-wordpress-theme-review-system\">ongoing plan</a> to loosen the WordPress.org theme directory review guidelines will factor into that in the coming year or two. Currently, reviewers for the official directory perform extensive code checks that may be more likely to catch issues before themes arrive in users&rsquo; hands. If the trade-off is better automation, it could also mean stricter coding standards and fewer security issues that human reviewers might miss.</p>\n\n\n\n<p>&ldquo;Vulnerabilities from third-party code remain as one of the biggest threats to websites build on WordPress,&rdquo; concluded Sild in the report. &ldquo;We already see a growth in unique vulnerabilities reported in the WordPress plugins and themes comparing 2020 with the beginning of 2021.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 20 Apr 2021 20:47: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: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: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:87:\"WPTavern: Recreating the Classic Wedding WordPress Theme Homepage With 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=115369\";s:7:\"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:219:\"https://wptavern.com/recreating-the-classic-wedding-wordpress-theme-homepage-with-the-block-editor?utm_source=rss&utm_medium=rss&utm_campaign=recreating-the-classic-wedding-wordpress-theme-homepage-with-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6345:\"<p class=\"has-drop-cap\">I simply do not understand it. For at least the better part of a decade, theme authors have asked for the tools to create more complex layouts with WordPress. They have asked for the ability to allow end-users to more easily recreate their demos. They have wanted methods to bypass the &ldquo;restrictive&rdquo; theme review guidelines.</p>\n\n\n\n<p>Over the past couple of years, WordPress has consistently delivered features that theme authors have asked for. Yet, themes that use them are few and far between.</p>\n\n\n\n<p>During my weekly perusal of the latest themes to land in the directory, a new <a href=\"https://wordpress.org/themes/classic-wedding/\">wedding theme</a> caught my attention last week. Of course, I downloaded, installed, and activated it only to find that I had no idea how to recreate the homepage design. There were no instructions. The theme options in the customizer seemed to make little sense. Nearly all of the decorative images were non-existent in the theme folder.</p>\n\n\n\n<p><em>Did I need to upgrade to the pro version to get what was in the screenshot?</em> There seems to be a plan for such a version, but it is not available yet.</p>\n\n\n\n<img />Classic Wedding theme screenshot.\n\n\n\n<p>I am no rookie, but I was stuck. I liked the simplicity of the design. However, I could not imagine setting up a wedding site with this theme. From a user&rsquo;s standpoint, it should not take more than a few mouse clicks. After that point, it should only be a matter of customizing the content.</p>\n\n\n\n<p>I recognize that there is still a sort of love/hate divide for the block editor in the <em>inner</em> WordPress community. However, theme authors are not doing any favors for the overall WordPress user base by not taking advantage of the tools available.</p>\n\n\n\n<p>So, I recreated the Classic Wedding theme homepage from scratch. Using the block editor. With a theme that supports it.</p>\n\n\n\n<h2>Creating a Wedding Homepage</h2>\n\n\n\n<p class=\"has-drop-cap\">My goal was simple. There was no demo to work from, and all I had to go on was an 800-pixel wide screenshot from the <a href=\"https://www.theclassictemplates.com/themes/free-wedding-wordpress-theme/\">theme page</a> on the author&rsquo;s site. Like I <a href=\"https://wptavern.com/recreating-the-music-artist-wordpress-theme-homepage-with-the-block-editor\">recreated the Music Artist homepage</a> several weeks ago, I wanted to do the same for Classic Wedding. With a couple of exceptions, which could have been handled by the theme, I was successful.</p>\n\n\n\n<p>Because Classic Wedding does not support the block editor itself, I could not recreate its homepage via the block editor while using the theme. It was not happening &mdash; I tried. I knew that the <a href=\"https://wptavern.com/eksell-portfolio-theme-now-available-in-wordpress-themes-directory\">Eksell WordPress theme</a> had a &ldquo;canvas&rdquo; template that allowed users to edit the entire page, so it was an easy choice.</p>\n\n\n\n<p>I also loaded the Kaushan Script and Lora fonts to more closely match the original theme. This was unnecessary for the experiment, but I wanted my recreation to at least look somewhat similar.</p>\n\n\n\n<p>I immediately knew that I would have one hurdle to overcome. The theme used an image that overlapped both the section above and below it. This requires margin controls, particularly the ability to add negative margins. Unfortunately, this is a missing component of the block editor today. It does not mean that theme authors cannot do it with custom block styles or patterns. It simply means that end-users are unable to control it from the interface.</p>\n\n\n\n<p>Because I did not want to spend my time writing the code for this, I leaned on my usual safety net, the <a href=\"https://wordpress.org/plugins/editorplus/\">Editor Plus</a> plugin. While it can be a little clunky sometimes and feel like overkill, it does include those missing features like margin options.</p>\n\n\n\n<img />Adding negative margin to an image.\n\n\n\n<p>I used <code>px</code> units there because it was easy. In a real-world project, <code>%</code> or <code>rem</code> would have been better. But I was just doing a quick proof-of-concept.</p>\n\n\n\n<p>Everything else in the content area was straightforward. I needed a Cover block with an Image, Heading, Paragraph, and Button tucked inside. I needed a Group block as a container for Image, Heading, and Paragraphs in the bottom section.</p>\n\n\n\n<p>Because the theme did not package its decorative images &mdash; <em>again, how would users recreate the homepage without them?</em> &mdash; I opted for a simple striped SVG background instead of the flowers in the original. Since I already had Editor Plus installed, I added an SVG from <a href=\"https://heroicons.com/\">Hero Icons</a> as the main background.</p>\n\n\n\n<img />Wedding page content recreation.\n\n\n\n<p>My original idea was to recreate the &ldquo;content&rdquo; part of the homepage only. However, it was a bit boring on its own. Therefore, I transformed everything into a Columns block and added the sidebar. I recreated the primary elements using the Image, Heading, Paragraph, and Navigation blocks. Then, I added a Social Icons block for fun.</p>\n\n\n\n<img />Full wedding homepage design.\n\n\n\n<p>I did hit one snag with the Navigation block. WordPress does not currently offer a method of centering each link in the list when using the vertical block variation. I had to write a couple of lines of CSS to make this happen. This seems like an oversight and one area where the block editor failed to meet my expectations. Of course, this could be handled on the theme side of things.</p>\n\n\n\n<p>Overall, this was a relatively simple project. However, this experiment added some complexities that were not present when I recreated the Music Artist homepage. Margin controls and vertical Navigation block alignments are must-haves. Using a third-party plugin and writing custom CSS is not ideal, and these were requirements to make this happen straight from the editor.</p>\n\n\n\n<p>All of this is possible from the theme end. Each piece of this design could have been packaged as a block pattern. The overlapping image effect would have made for a neat block style. I just wish that theme authors would start utilizing the features that are being hand-fed to them.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 19 Apr 2021 21:42: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: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:42;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Automattic Launches Jetpack Boost: A New Performance Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=114913\";s:7:\"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:181:\"https://wptavern.com/automattic-launches-jetpack-boost-a-new-performance-plugin?utm_source=rss&utm_medium=rss&utm_campaign=automattic-launches-jetpack-boost-a-new-performance-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4877:\"<p>The Jetpack team has been quietly testing a new plugin called <a href=\"https://wordpress.org/plugins/jetpack-boost/\">Jetpack Boost</a>, which addresses website owners&rsquo; performance and SEO concerns. Version 1.0 was released today, one month after the final pre-release came out in March.</p>\n\n\n\n<p>Boost is a separate plugin under the Jetpack brand and it does not require Jetpack core to work. The first iteration bundles three performance modules:</p>\n\n\n\n<ol><li><em><strong>Local Critical CSS</strong></em>&nbsp;generates optimized styles for the homepage, posts, and pages to display content faster, especially for visitors on mobile devices.</li><li><em><strong>Defer Non-Essential Javascript</strong></em>&nbsp;moves some tasks to after the page loads, so visible items load faster.</li><li><em><strong>Lazy Image Loading</strong></em>&nbsp;loads images as the visitor scrolls them into view. </li></ol>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Once the plugin is installed, users can toggle the modules on or off. Optimizing the site&rsquo;s CSS can be a lengthy process but it shows a progress bar and alerts you if are trying to navigate away from the page before it&rsquo;s finished. Jetpack Boost displays an initial score when it&rsquo;s first installed and will update after optimizations are put in place. </p>\n\n\n\n<p>Here&rsquo;s an example score from a relatively unoptimized simple blog with 20 active plugins:</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>After installing Jetpack Boost, there was a significant improvement on scores in the dashboard. It&rsquo;s not a magic wand but it&rsquo;s a fairly user-friendly way to tackle some basic performance issues that may translate into a better visitor experience. </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Checking the before and after scores on <a href=\"https://web.dev/measure/\">web.dev</a> demonstrates a noticeable improvement on the Core Web Vitals assessment. For some websites this could mean the difference between passing or not (meaning 75% of pages on the domain pass).</p>\n\n\n\n<div class=\"wp-block-image\"><img />Before installing Jetpack Boost</div>\n\n\n\n<img />After installing Jetpack Boost\n\n\n\n<p>Automattic engineer Nauris P&#363;&#311;is, who worked on the project, said one reason the plugin was created was to help users &ldquo;get their Web Vitals up and make the web a better place.&rdquo;</p>\n\n\n\n<p>Google Search will be <a href=\"https://wptavern.com/google-search-to-add-page-experience-to-ranking-signals-in-may-2021\">adding Page Experience to ranking signals</a> in May 2021, and WordPress sites need all the help they can get. Page Experience is measured by a website&rsquo;s <a href=\"https://web.dev/vitals/#core-web-vitals\">Core Web Vitals</a>&nbsp;metrics, but these scores are not easy to improve without some technical knowledge and troubleshooting.</p>\n\n\n\n<p>Despite Jetpack already including so many different, varied features, Automattic opted to put the Boost modules in a separate plugin. </p>\n\n\n\n<p>&ldquo;We want Jetpack Boost to have a life of its own &ndash; focused on performance and make it available to everyone, including people who don&rsquo;t want to use the main Jetpack plugin,&rdquo; P&#363;&#311;is said.</p>\n\n\n\n<p>The plugin was built with the same modular structure as Jetpack core, so users can easily deactivate modules they don&rsquo;t want to use. This is helpful for ensuring compatibility with other performance or caching plugins that website owners may already be using.<br /><br />&ldquo;You&rsquo;ve probably noticed that both Jetpack and Boost have lazy loading images &ndash; it&rsquo;s the exact same module,&rdquo; P&#363;&#311;is said. &ldquo;If the user happens to have both Jetpack and Jetpack Boost active &ndash; it&rsquo;ll just use the most recent version of Lazy Loading Images.&rdquo;</p>\n\n\n\n<p>The features in version 1.0 are just the beginning of Automattic&rsquo;s plans for Jetpack Boost. The project appears to be on track to become a full-blown performance plugin that may even migrate some of Jetpack core&rsquo;s performance-related functionality.</p>\n\n\n\n<p>&ldquo;Version 1.0.0 is being released the &ldquo;<a href=\"https://ma.tt/2010/11/one-point-oh/\">one-point-oh</a>&rdquo; way,&rdquo; P&#363;&#311;is said. &ldquo;We&rsquo;re releasing as early as we can call it stable &ndash; but there&rsquo;s so much that we want to do. Starting with simple modules that package up other typical optimization techniques (like concatenation, minification, maybe even photon?) &ndash; all the way to more advanced ideas like performance tracking, intelligent performance suggestions, etc.&rdquo; </p>\n\n\n\n<p>P&#363;&#311;is said none of these ideas are set in stone and the team is open to exploring and building modules that will have the highest performance impact after getting more feedback.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 19 Apr 2021 17:37:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"Gutenberg Times: Page Template Editor for WordPress 5.8, Videos and Plugins – Weekend Edition #166\";s:7:\"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=17602\";s:7:\"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:105:\"https://gutenbergtimes.com/page-template-editor-for-wordpress-5-8-videos-and-plugins-weekend-edition-166/\";s: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:14988:\"<p>Howdy, </p>\n\n\n\n<p>Yes, it&#8217;s been a while that you received a fully curated Weekend edition. After the move it took a while to get my office operational again. We still have too many boxes to unpack, though.  </p>\n\n\n\n\n\n<p>Nevertheless, let&#8217;s catch up on Gutenberg news together! </p>\n\n\n\n<p>All the best, <br />Birgit 💕</p>\n\n\n\n<h2>Gutenberg 10.4 Released (and 10.4.1) </h2>\n\n\n\n<p>The <strong><a href=\"https://gutenbergtimes.com/podcast/changelog-42-full-site-editing-scope-for-wordpress-5-8/\">Gutenberg Changelog episode 42</a></strong> is now available. <strong>Grzegorz (&#8220;Greg&#8221;) Ziolkowski </strong>and I discuss Full-site Editing Scope for WordPress 5.8, Gutenberg’s 10.4,  Gallery Block Refactor and Block-Based Theme updates.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong>Sarah Gooding</strong> of the WP Tavern wrote about the Gutenberg 10.4 release: <a href=\"https://wptavern.com/gutenberg-10-4-introduces-block-widgets-in-the-customizer\">Gutenberg 10.4 Introduces Block Widgets in the Customizer</a></p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<h2>Full-Site Editing and WordPress 5.8 </h2>\n\n\n\n<p>If you now find yourself in the position to learn more about the extent of Full-Site Editing experience, I have a real treat for you: <a href=\"https://gutenbergtimes.com/video-full-site-editing-overview-with-anne-mccarthy/\">A 30-min video Full-Site Editing Overview by</a>, Anne McCarthy, Developer Relations for the Gutenberg project. </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>On April 14, 2021, the Gutenberg and 5.8 release leads held a meeting, with Matias Venture giving a tour of the current state of the Phase 2 of Gutenberg development. The outcome of the meeting was a decision on Go/NoGo for component that make it into core for WordPress 5.8.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy</strong> provide in <a href=\"https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/\">her follow-up post </a>a list of the detailed scope, the video of the meeting and a transcript of the recording. </p>\n\n\n\n<h3>The block editor scope </h3>\n\n\n\n<ul><li>Improvements from Gutenberg 9.9 to 10.7 plugin version. </li><li>Introduce 25 new blocks (Query, Site Logo, Navigation,Posts, Comments, Archives etc. ), the most valuable among them will be the Query Block. </li><li><code>theme.json</code> Mechanism for Theme builders (<a href=\"https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/\">see developer documentation</a>)</li><li>Template Editor for Pages/Blank Template. (<a href=\"https://youtu.be/c4IFn73Nzvk?t=2859\">see demo by Marcus Kazmierczak</a>)</li><li>Widgets Screen &amp; Block widgets in Customizer.</li><li>Design tools: Duotone, Layout controls, padding, etc.</li></ul>\n\n\n\n<p>There is the caution stated in the post: <em>&#8220;Not all the above are currently ready, but there’s some level of confidence that they can be by the time of 5.8.&#8221;</em></p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>For the <strong>Template Editor for Pages/Blank Template</strong> you can see it <a href=\"https://youtu.be/c4IFn73Nzvk?t=2859\">in action in a demo</a> by <strong>Marcus Kazmierczak</strong>, he gave at the Mega Meetup last week. </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong>Bud Kraus</strong> of JoyofWP showed us in his video, <a href=\"https://joyofwp.com/whats-the-future-of-the-wordpress-widget/\">how the Widget screen will look like in the future.</a> It does not show the Widget handling in the Customizer yet, but that is to come to WordPress 5.8. You could see a short piece of it in Matias Ventura&#8217;s demo video from the release leads meeting. It is now already available in the latest Gutenberg plugin release. </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n\n<p><strong> <a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/\" target=\"_blank\" rel=\"noreferrer noopener\">&#8220;Keeping up with Gutenberg &#8211; Index 2021&#8221;</a> </strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. <a href=\"https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/\">The index 2020 is here</a></p>\n\n\n\n\n<p><strong>Justin Tadlock</strong> summarized last week&#8217;s announcements in <strong><a href=\"https://wptavern.com/full-site-editing-is-partly-a-go-for-wordpress-5-8\">Full Site Editing Is Partly a ‘Go’ for WordPress 5.8</a></strong></p>\n\n\n\n<h2>Testing Full-Site Editing</h2>\n\n\n\n<p>As the latest Full-Site Editing Call of Testing, <strong>Anne McCarthy</strong> has a <strong><a href=\"https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/\">Query Quest for you.</a></strong> Again with a great set of test instruction, you are guided towards usage and various features of the Query Block and its accompanying new post blocks for title, content, comments, feature image and pagination.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong>Justin Tadlock</strong> discussed this task a bit further in his article: <strong><a href=\"https://wptavern.com/fse-outreach-round-5-venturing-out-a-query-quest\">FSE Outreach Round #5: Venturing out a Query Quest</a>.</strong> &#8220;Testing never has to be boring. I encourage participants to grab inspiration from their lives as they venture out on their Query Quest.&#8221; he wrote. </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>Apropos Testing: <strong>Sarah Gooding</strong> wrote about our Gutenberg Nightly plugin to get the latest development of the block-editor in an easy to handle plugin. <strong><a href=\"https://wptavern.com/set-up-a-gutenberg-test-site-in-2-minutes-with-the-gutenberg-nightly-plugin\">Set Up a Gutenberg Test Site in 2 Minutes with the Gutenberg Nightly Plugin</a></strong>.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n\n<p><strong><a href=\"https://gutenbergtimes.com/need-a-zip-from-master/\">Need a plugin .zip from Gutenberg&#8217;s main (trunk) branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>\n\n\n\n<p><img alt=\"GitHub all releases\" src=\"https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge\" /></p>\n\n\n\n<p></p>\n\n\n\n\n<p><strong>Anne McCarthy</strong> curated all the feedback from the fourth testing call: <a href=\"https://make.wordpress.org/test/2021/03/30/fse-program-custom-404-page-testing-summary/\"><strong>FSE Program Custom 404 Page Testing Summary</strong></a></p>\n\n\n\n<h2>Block-Based Themes</h2>\n\n\n\n<p><strong>Helen Hou-Sandi</strong> streamed on Twitch her <a href=\"https://www.twitch.tv/videos/981424705\">exploration session to create a block-based theme</a> for the Full-Site Editing.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong>Kjell Reigstad</strong> opened an issue for <a href=\"https://github.com/WordPress/gutenberg/issues/30508\"><strong>Query Block Pattern inspirations.</strong></a> There are great examples posted that could be converted to pattern, that could be bundled with WordPress 5.8  </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong>Marcus Kazmierczak</strong> also used Twitch to stream his <a href=\"https://www.twitch.tv/mkaz7000\">Lunch &amp; Learn series on Block-based themes.</a></p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>Keep abreast on specific Theme related development and discussions with the weekly round-up from the Themes Team. <strong>Kjell Reigstad</strong> posted this week&#8217;s edition. <a href=\"https://make.wordpress.org/themes/2021/04/16/gutenberg-themes-week-of-apr-12-2021/\"><strong>Gutenberg + Themes: Week of Apr 12, 2021</strong></a></p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>A couple of PRs that should help with <strong>transitioning existing themes to be block-based:</strong></p>\n\n\n\n<ul><li><a href=\"https://github.com/WordPress/gutenberg/pull/30345\"><strong>Add do_block_template_part function</strong></a><br />New gutenberg_block_template_part(), gutenberg_block_header_area(), and gutenberg_block_footer_area() functions to help pull block-based template parts into existing PHP templates: </li><li><a href=\"https://github.com/WordPress/gutenberg/pull/30438\"><strong>Allow creating custom block templates in classic themes</strong></a> Allowing people to create and use block-based page template for certain pages on their site, even while using a non-block-based theme.</li></ul>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>In their latest episode of WPCafe co-hosts <strong>Mark Wilkinson</strong> and <strong>Keith Devon</strong> talked about <a href=\"https://www.youtube.com/watch?v=jAIlY3lTAos\">Building Twenty-Twenty-One with Caroline Nymark and Mel Choyce-Dwan</a>. </p>\n\n\n\n<h2>Plugins for the Block Editor</h2>\n\n\n\n<p><strong><a href=\"https://wordpress.org/plugins/gutentor/\">Gutentor</a></strong> published a collection of 70+ Blocks and layouts for Gutenberg Editor. </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>If you are working on your set of Blocks for the editor, <strong>Justin Tadlock</strong> has some thoughts to consider: <a href=\"https://wptavern.com/yet-another-wordpress-block-library-plugin\"><strong>Yet Another WordPress Block Library Plugin</strong></a>. He is making a well though through case to suggest more unique blocks to fill the gap to the core blocks. It seems to me that, two years of seeing block collections being acquired by big companies like Atom Blocks, Co Blocks and latest <a href=\"https://wptavern.com/ithemes-acquires-kadence-wp-plans-to-sunset-legacy-themes-in-2022\">Kadence Blocks</a>, might tempt a small developer team to come up with  another set of blocks matching a specific theme and hope for an acquisition by another big company in the space. There might be space for a few more, indeed. </p>\n\n\n\n<p>Tadlock&#8217;s longs for something new, a unique extension of core or a missing tool:</p>\n\n\n\n<ul><li><a href=\"https://wptavern.com/display-digital-sheet-music-with-the-wordpress-block-editor\">Display Digital Sheet Music With the WordPress Block Editor</a></li><li><a href=\"https://wptavern.com/block-a-saurus-embeds-a-side-scrolling-t-rex-game-via-the-block-editor\">Block-a-saurus Embeds a Side-Scrolling T-Rex Game via the Block Editor</a></li><li><a href=\"https://wptavern.com/emoji-conbini-and-the-case-for-a-block-enhancements-directory\">Emoji Conbini and the Case for a Block Enhancements Directory</a></li><li><a href=\"https://wptavern.com/insert-font-awesome-icons-into-the-block-editor-via-the-jvm-gutenberg-rich-text-icons-plugin\">Insert Font Awesome Icons Into the Block Editor via the JVM Gutenberg Rich Text Icons Plugin</a></li><li><a href=\"https://gutenbergtimes.com/writers-rejoice-iceberg-delivers-distraction-free-writing-for-wordpress/\">Writers Rejoice! Iceberg Delivers Distraction-free Writing for WordPress</a></li></ul>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong><a href=\"https://wordpress.org/plugins/conditional-blocks/\">Conditional Blocks</a></strong> by Morgan Hvidt allows you to create block that are displayed when certain conditions apply. We saw other plugins that offer that, like <a href=\"https://wordpress.org/plugins/block-visibility/\">Block Visibility by Nick Diego</a>. This one is a bit different. It allows you to change content depending on HTTP referrer, so if someone comes from Twitter, they could see a different message than someone coming from a Google Search or a link in a newsletter or an affiliate link. The plugin is also available as a pro version with premium features at <a href=\"https://conditionalblocks.com\">conditionalblocks.com</a>. </p>\n\n\n\n\n<p> <a href=\"https://gutenbergtimes.com/podcast/changelog-42-full-site-editing-scope-for-wordpress-5-8/\"><strong>Episode #4</strong>2 is now available</a>, with new co-host <strong>Grzegorz Ziolkowski</strong></p>\n\n\n\n<p> <strong>Subscribe to the&nbsp;<a href=\"https://gutenbergtimes.com/podcast/\">Gutenberg Changelog</a>&nbsp;podcast </strong><br />🎙️&nbsp;<a href=\"https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe\">Spotify</a>&nbsp;|&nbsp;<a href=\"https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0\">Google</a>&nbsp;|&nbsp;<a href=\"https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475\">iTunes</a>&nbsp;|&nbsp;<a href=\"https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf\">PocketCasts</a>&nbsp;|&nbsp;<a href=\"https://www.stitcher.com/show/gutenberg-changelog\">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href=\"https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast\">Pod Bean</a>&nbsp;|&nbsp;<a href=\"https://castbox.fm/channel/Gutenberg-Changelog-id2173375\">CastBox</a>&nbsp;|&nbsp;<a href=\"https://www.podchaser.com/podcasts/gutenberg-changelog-878239/\">Podchaser</a>&nbsp;|&nbsp;<a href=\"https://gutenbergtimes.com/feed/podcast\">RSS Feed</a>&nbsp;</p>\n\n\n\n<img />\n\n\n\n\n<h2>People and Community</h2>\n\n\n\n<p>It&#8217;s been already a year that <strong>Anne McCarthy</strong> joined the Gutenberg team as a developer relations wrangler. It has been a great pleasure meeting Anne and collaborating with her has been quite inspiring, and I learned a lot from her wisdom and her wealth of ideas. She has also become a good friend. She is som much better and being a remote friend that I ever will be. On her personal block Anne published <a href=\"https://nomad.blog/2021/04/17/one-year-in-devrel/\"><strong>One year in DevRel</strong></a></p>\n\n\n\n<p>Anne&#8217;s pioneer work with WordPress open-source project has been so successful that <a href=\"https://boards.greenhouse.io/automatticcareers/jobs/2937422\">Automattic wants to sponsor another person for developer relations.</a></p>\n\n\n\n<h2>Developing with ReactJS and Gutenberg Blocks. </h2>\n\n\n\n<p><strong>Rob Stinson</strong> wrote a tutorial on how <a href=\"https://studiopress.blog/the-ultimate-guide-to-building-custom-collections-in-genesis-blocks/\">to building custom Collections in Genesis Blocks.</a> Now Collections in this context are Layout templates, that extend existing Genesis blocks. </p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p><strong> Mark Howells-Mead </strong>uses <a href=\"https://permanenttourist.ch/2021/04/using-react-and-wordpress-to-build-an-interactive-performant-single-page-application\">ReactJS to build interactive single page applications with WordPress</a> and wrote a tutorial. It&#8217;s not at all about Blocks and Gutenberg, but it&#8217;s related to the skill set of learning ReactJS and hopefully inspired developer to gradually make the transition. </p>\n\n\n\n\n\n<p></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 18 Apr 2021 23:33: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"WPTavern: Gutenberg 10.4 Introduces Block Widgets in the Customizer\";s:7:\"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=115274\";s:7:\"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:179:\"https://wptavern.com/gutenberg-10-4-introduces-block-widgets-in-the-customizer?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-10-4-introduces-block-widgets-in-the-customizer\";s: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:3021:\"<p>The latest release of the Gutenberg plugin (<a href=\"https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/\">10.4)</a> brings <a href=\"https://github.com/WordPress/gutenberg/issues/29285\">block widgets into the Customizer</a>. When customizing widget-enabled areas, a new block inserter icon is now available for dropping blocks into sidebars. This is the first iteration of <a href=\"https://github.com/WordPress/gutenberg/issues/26900\">block management in the Customizer</a>, tackling the technical integration for editing blocks while also taking advantage of the live preview in the Customizer.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Version 10.4 includes several design updates to the&nbsp;Site Editor List View, bringing more consistency to the icon sizing and spacing, as well as&nbsp;new colors for hover, focus, and select states. The publishing UI has been updated to <a href=\"https://github.com/WordPress/gutenberg/pull/30231\">display the site icon and name</a>, adding a more personal touch to this flow while also making it more clear for full-screen or mobile users.</p>\n\n\n\n<img />Gutenberg 10.4 <a href=\"https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/\">release post</a>\n\n\n\n<p>More progress on site editing experiments includes the following notable updates:  </p>\n\n\n\n<ul><li>the ability to revert template customizations directly in the editor</li><li>many improvements to the Navigation block, including&nbsp;a&nbsp;<a rel=\"noreferrer noopener\" href=\"https://github.com/WordPress/gutenberg/pull/30403\" target=\"_blank\">new &ldquo;Post Format Link&rdquo; variation</a>, a&nbsp;<a rel=\"noreferrer noopener\" href=\"https://github.com/WordPress/gutenberg/pull/30281\" target=\"_blank\">clearer placeholder state</a>, and more style updates</li><li><a href=\"https://github.com/WordPress/gutenberg/pull/30521\">Better labeling</a> for differentiating &ldquo;Custom Styles&rdquo; vs global style changes in the site editor saving panel </li><li>New &ldquo;<a href=\"https://github.com/WordPress/gutenberg/pull/29839\">manage with live preview link</a>&rdquo; in the Widgets editor</li></ul>\n\n\n\n<p>The block editor still <a href=\"https://github.com/WordPress/gutenberg/issues/29976\">fails to deliver a consistent preview</a> of core blocks on the frontend in many cases. Version 10.4 brings greater parity between the editor/frontend with more consistent markup for archives, latest comments, quote, and separator blocks, with improved default padding to match the browser&rsquo;s default.  The GitHub <a href=\"https://github.com/WordPress/gutenberg/issues/29976\">issue</a> for this improvement contains a to-do list for additional blocks that need more polishing on previews, including search, paragraph, columns, embed, post title, and more.</p>\n\n\n\n<p>For a full list of all the enhancements and bug fixes, check out the <a href=\"https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/\">10.4 release post</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 17 Apr 2021 13:59: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: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:69:\"Gutenberg Times: Video: Full-Site Editing Overview with Anne McCarthy\";s:7:\"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=17545\";s:7:\"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://gutenbergtimes.com/video-full-site-editing-overview-with-anne-mccarthy/\";s: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:53595:\"<p>As part of the <a href=\"https://www.youtube.com/watch?v=c4IFn73Nzvk\">Meta Meetup on April 15th 2021</a>, Anne McCarthy gave a presentation on what Full-Site Editing entails, the updated scope of WordPress 5.8, what the FSE outreach program is and what issues surfaced during the four calls for testing from the group. </p>\n\n\n\n<p>It&#8217;s a fantastic and fast-paced presentation and covers a lot of ground. It&#8217;s ideal for WordPress users that just now want to catch up on all the buzz around Full&#8211;Site Editing and learn what will come to WordPress in the 5.8 release in July 2021. </p>\n\n\n\n<p>Big Thank You to Anne for allowing us to publish the video here with the transcript. </p>\n\n\n\n<p><em>For those interested how the template editor works,  <a href=\"https://youtu.be/c4IFn73Nzvk?t=2909\">jump right in to Marcus Kasmierczak&#8217;s live demo</a> portion of the WordPress Mega Meetup recording</em></p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"toolbelt-video-wrapper\"></div>\n</div>\n\n\n\n<h2 id=\"0-sha\">Shared Resources</h2>\n\n\n\n<ul><li><a href=\"https://wordpress.org/about/roadmap/\">Roadmap showing phase 2</a>&nbsp;&nbsp;</li><li><a href=\"https://github.com/WordPress/gutenberg/issues/24551\">Full Site Editing Milestones</a>&nbsp;&nbsp;</li><li><a href=\"https://github.com/WordPress/gutenberg/issues/30662\">Special shoutout to the Gradual Adoption Milestone</a>&nbsp;&nbsp;</li><li><a href=\"https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/\">Query Quest &#8211; Call for testing the Query Block</a>&nbsp;&nbsp;</li><li><a href=\"https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/\">Go/No go</a> &nbsp;</li><li><a href=\"https://github.com/WordPress/gutenberg/issues/29398\">Preview</a>&nbsp;&nbsp;</li><li><a href=\"https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/\">FSE Outreach Program</a>:&nbsp;&nbsp;</li><li><a href=\"https://make.wordpress.org/core/2021/03/16/high-level-feedback-from-the-fse-program-march\">High-level feedback from the Full Site Editing Program thus far</a></li><li><a href=\"https://critterverse.blog/2021/03/23/full-site-editor-404-test/\">404 design</a></li><li><a href=\"https://www.twitch.tv/mkaz7000\">Marcus Kazmierczak Streams on Twitch</a>  </li></ul>\n\n\n\n<p><em><a href=\"https://gutenbergtimes.com/feed/#transcript\">See transcript below</a></em></p>\n\n\n\n<div class=\"ngl-articles ngl-articles-50_50 ngl-articles-frontend\">\n\n	\n	<div class=\"ngl-articles-wrap\">\n	\n			<!--[if !mso]><\\!-->\n			<div class=\"ngl-article-left-mobile\">\n				<table border=\"0\" width=\"100%\" cellpadding=\"10\" cellspacing=\"0\">\n					<tr>\n						<td valign=\"top\">\n							<div class=\"ngl-article-mob-wrap\">\n							<div class=\"ngl-article-featured\"><a href=\"https://gutenbergtimes.com/full-site-editing/\" target=\"_self\" rel=\"\"><img src=\"https://i2.wp.com/gutenbergtimes.com/wp-content/uploads/2021/02/vidar-nordli-mathisen-4NlLMwdFoLY-unsplash.jpg?w=640&ssl=1\" /></a></div><div class=\"ngl-article-title\"><a href=\"https://gutenbergtimes.com/full-site-editing/\" target=\"_self\" rel=\"\"><span>Full-Site-Editing &#8211; the Ultimate Resource List</span></a></div><div class=\"ngl-article-excerpt\">Nothing in life is to be feared, it is only to be understood. Now is the time to understand more, so that we may fear less.&nbsp;— Marie Curie&nbsp;</div><div class=\"ngl-article-date\">18 Apr 2021</div>							</div>\n						</td>\n					</tr>\n				</table>\n			</div>\n			<!-- <![endif]-->\n\n			<div class=\"ngl-article ngl-article-img-left\">\n\n				\n				<div class=\"ngl-article-left\"><div class=\"ngl-article-featured\"><a href=\"https://gutenbergtimes.com/full-site-editing/\" target=\"_self\" rel=\"\"><img src=\"https://i2.wp.com/gutenbergtimes.com/wp-content/uploads/2021/02/vidar-nordli-mathisen-4NlLMwdFoLY-unsplash.jpg?w=640&ssl=1\" /></a></div></div><div class=\"ngl-article-right\"><div class=\"ngl-article-title\"><a href=\"https://gutenbergtimes.com/full-site-editing/\" target=\"_self\" rel=\"\"><span>Full-Site-Editing &#8211; the Ultimate Resource List</span></a></div><div class=\"ngl-article-excerpt\">Nothing in life is to be feared, it is only to be understood. Now is the time to understand more, so that we may fear less.&nbsp;— Marie Curie&nbsp;</div><div class=\"ngl-article-date\">18 Apr 2021</div></div>\n			</div>\n\n		\n			<!--[if !mso]><\\!-->\n			<div class=\"ngl-article-left-mobile\">\n				<table border=\"0\" width=\"100%\" cellpadding=\"10\" cellspacing=\"0\">\n					<tr>\n						<td valign=\"top\">\n							<div class=\"ngl-article-mob-wrap\">\n							<div class=\"ngl-article-featured\"><a href=\"https://gutenbergtimes.com/full-site-editing-mvp-can-i-build-a-landing-page/\" target=\"_self\" rel=\"\"><img src=\"https://i2.wp.com/gutenbergtimes.com/wp-content/uploads/2021/03/kelly-sikkema-gcHFXsdcmJE-unsplash.jpg?w=640&ssl=1\" /></a></div><div class=\"ngl-article-title\"><a href=\"https://gutenbergtimes.com/full-site-editing-mvp-can-i-build-a-landing-page/\" target=\"_self\" rel=\"\"><span>Full-site Editing MVP: Can I Build a Landing Page?</span></a></div><div class=\"ngl-article-excerpt\">Josepha Haden Chomphosy was the featured guest on the inaugural episode of the WPTavern Jukebox podcast, hosted by Nathan Wrigley. Chomphosy explained her unofficial benchmark for the Go/NoGo decision on Full-site Editing for the WordPress core merge.&nbsp;</div><div class=\"ngl-article-date\">27 Mar 2021</div>							</div>\n						</td>\n					</tr>\n				</table>\n			</div>\n			<!-- <![endif]-->\n\n			<div class=\"ngl-article ngl-article-img-left\">\n\n				\n				<div class=\"ngl-article-left\"><div class=\"ngl-article-featured\"><a href=\"https://gutenbergtimes.com/full-site-editing-mvp-can-i-build-a-landing-page/\" target=\"_self\" rel=\"\"><img src=\"https://i2.wp.com/gutenbergtimes.com/wp-content/uploads/2021/03/kelly-sikkema-gcHFXsdcmJE-unsplash.jpg?w=640&ssl=1\" /></a></div></div><div class=\"ngl-article-right\"><div class=\"ngl-article-title\"><a href=\"https://gutenbergtimes.com/full-site-editing-mvp-can-i-build-a-landing-page/\" target=\"_self\" rel=\"\"><span>Full-site Editing MVP: Can I Build a Landing Page?</span></a></div><div class=\"ngl-article-excerpt\">Josepha Haden Chomphosy was the featured guest on the inaugural episode of the WPTavern Jukebox podcast, hosted by Nathan Wrigley. Chomphosy explained her unofficial benchmark for the Go/NoGo decision on Full-site Editing for the WordPress core merge.&nbsp;</div><div class=\"ngl-article-date\">27 Mar 2021</div></div>\n			</div>\n\n		\n		\n		</div>\n\n</div>\n\n\n<p class=\"has-large-font-size\" id=\"transcript\">Transcript </p>\n\n\n\n<div class=\"wp-block-group has-background\"><div class=\"wp-block-group__inner-container\">\n<div class=\"wp-block-sortabrilliant-guidepost\"><ul><li><a href=\"https://gutenbergtimes.com/feed/#0-sha\">Shared Resources</a></li><li><a href=\"https://gutenbergtimes.com/feed/#0-strong-milestones-of-full-site-editing-experience-strong\">Milestones of Full-Site Editing Experience</a><ul><li><a href=\"https://gutenbergtimes.com/feed/#1-strong-infrastructure-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-strong\">Infrastructure&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</a></li><li><a href=\"https://gutenbergtimes.com/feed/#2-strong-browsing-templates-and-template-parts-strong\">Browsing Templates and Template Parts</a></li><li><a href=\"https://gutenbergtimes.com/feed/#3-strong-styling-global-styles-theme-json-strong\">Styling &#8211; Global Styles + theme.json</a></li><li><a href=\"https://gutenbergtimes.com/feed/#4-strong-20-theme-blocks-strong\">20+ Theme Blocks</a></li><li><a href=\"https://gutenbergtimes.com/feed/#5-strong-query-block-the-loop-or-post-list-strong\">Query Block &#8211; The Loop or Post List</a></li><li><a href=\"https://gutenbergtimes.com/feed/#6-strong-navigation-block-strong\">Navigation Block</a></li><li><a href=\"https://gutenbergtimes.com/feed/#7-strong-gradual-adoption-widgets-customizer-hybrid-themes-nbsp-strong\">Gradual Adoption &#8211; Widgets, Customizer, Hybrid Themes&nbsp;</a></li></ul></li><li><a href=\"https://gutenbergtimes.com/feed/#8-strong-whats-coming-to-word-press-5-8-strong\">What&#8217;s coming to WordPress 5.8</a><ul><li><a href=\"https://gutenbergtimes.com/feed/#9-strong-short-demo-template-editing-navigation-block-and-multi-entity-saving-strong\">Short Demo: Template Editing, Navigation Block and Multi-Entity Saving</a></li></ul></li><li><a href=\"https://gutenbergtimes.com/feed/#10-strong-timeline-of-5-8-release-strong\">Timeline of 5.8 Release</a></li><li><a href=\"https://gutenbergtimes.com/feed/#11-strong-what-is-the-fse-outreach-experiment-program-strong\">What is the FSE Outreach Experiment Program?</a><ul><li><a href=\"https://gutenbergtimes.com/feed/#12-strong-whats-the-goal-strong\">What&#8217;s the goal</a></li><li><a href=\"https://gutenbergtimes.com/feed/#13-strong-why-was-it-started-strong\">Why was it started?</a></li><li><a href=\"https://gutenbergtimes.com/feed/#14-strong-how-to-join-fse-outreach-experiment-strong\">How to Join FSE Outreach Experiment</a></li></ul></li><li><a href=\"https://gutenbergtimes.com/feed/#15-strong-high-level-feedback-from-calls-for-testing-strong\">High-Level Feedback from Calls for Testing</a><ul><li><a href=\"https://gutenbergtimes.com/feed/#16-strong-preview-content-strong\">Preview Content</a></li><li><a href=\"https://gutenbergtimes.com/feed/#17-strong-saving-process-strong\">Saving Process</a></li><li><a href=\"https://gutenbergtimes.com/feed/#18-distinction-between-editing-area\">Distinction between editing area.</a></li><li><a href=\"https://gutenbergtimes.com/feed/#19-rethinking-width-and-alignment\">Rethinking Width and Alignment.</a></li><li><a href=\"https://gutenbergtimes.com/feed/#20-strong-general-usability-improvements-strong\">General usability improvements.</a></li><li><a href=\"https://gutenbergtimes.com/feed/#21-strong-improving-placeholders-strong\">Improving Placeholders.</a></li></ul></li><li><a href=\"https://gutenbergtimes.com/feed/#22-strong-will-full-site-editing-take-over-my-site-strong\">Will full site editing take over my site?</a></li><li><a href=\"https://gutenbergtimes.com/feed/#23-strong-what-about-the-block-based-navigation-and-widget-screens-strong\">What about the block-based navigation and widget screens?</a></li><li><a href=\"https://gutenbergtimes.com/feed/#24-strong-site-builders-strong\">Site builders</a></li><li><a href=\"https://gutenbergtimes.com/feed/#25-strong-how-is-this-going-to-impact-themes-strong\">How is this going to impact themes?</a></li><li><a href=\"https://gutenbergtimes.com/feed/#26-strong-what-pathways-are-going-to-be-created-strong\">What pathways are going to be created?</a></li><li><a href=\"https://gutenbergtimes.com/feed/#27-strong-whats-the-best-way-to-prepare-nbsp-strong\">What&#8217;s the best way to prepare?&nbsp;</a></li><li><a href=\"https://gutenbergtimes.com/feed/#28-strong-stay-connected-with-anne-mc-carthy-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-strong\">Stay connected with Anne McCarthy</a></li></ul></div>\n</div></div>\n\n\n\n<p class=\"has-small-font-size\"><em>Featured image: 404 template by Channing Ritter on critterverse.blog</em></p>\n\n\n\n<p>Howdy. To start, thanks so much for having me. This is a presentation about full site editing. I&#8217;m very excited to talk with you. This is a feature I&#8217;ve been thinking a lot about over the last year and I&#8217;m excited to share with you all. I&#8217;m also really keen to learn from each of you what you&#8217;re worried about, what you&#8217;re excited about, how you think full-site editing can improve your workflows, and more. So this is prerecorded because I wanted to make sure with so much information going around, wanted to make sure I had all the details lined up and so I could pause and rework certain sections. But please know that I welcome questions. So while you can&#8217;t interrupt me during the presentation, there will be a whole section at the end. Pull out your pen and paper, write them down, and know that they&#8217;re very, very welcomed. But for now, let&#8217;s dig in.</p>\n\n\n\n<p>So briefly about me, I&#8217;m actually originally from Winter Park, Florida. So I haven&#8217;t been home in about a year and a half, and thank you for letting me virtually return home by participating in this meetup. In 2011, I first found WordPress as a student at UNC Chapel Hill. I worked on their multi-site, had a great time. 2013, I went to my first ever WordCamp. 2014, joined Automatic as a happiness engineer focused on VaultPress and had a great time focusing on security of websites. It gave me a really interesting look into concerns people have about websites that most people don&#8217;t think about. Then 2020, I switched into the developer relations position at Automatic and have been there ever since.</p>\n\n\n\n<p>So let&#8217;s get meta and talk about the talk. (laughing). So to start, I&#8217;m going to zoom out really big and then slowly put pieces together until we kind of get a nice map of what full-site editing is with all the details. So this will look kind of like first answering some big, high-level questions, digging into then how the work is actually being done, so going from high level, &#8220;What is this? Why does it help me?&#8221; to &#8220;How is this work actually being approached? What are the pieces of the work that I need to know, the role of the outreach program?&#8221; Then I want to address some key topics and questions that I often get asked when I&#8217;ve presented at other places and talked on other podcasts about full-site editing or just one-on-one with people. I love to talk about full-site editing. So hopefully some of the key topics and questions can help get people thinking about other things they want to ask about.</p>\n\n\n\n<p>So let&#8217;s dig into the first big picture question. Why is this being done at all? Simply put, it&#8217;s to empower users. Rather than having a specific part of the site locked away in a theme or requiring a plugin, full-site editing will basically open it up to customize any part of your site the way you want to, or, on the flip side, you can let it be, or if you&#8217;re an agency, you could lock certain sites down or certain parts of a site down, depending upon how you want users to have access. So it&#8217;s a pretty powerful, big mission to actually deliver on full site editing.</p>\n\n\n\n<p>So I answered why is this being done. Now let&#8217;s dig into how does this fit into the WordPress roadmap? So full-site editing is a major part of phase two of the current roadmap. It&#8217;s not the only part, though. There&#8217;s actually other interrelated projects, including things like block patterns, the block directory, block-based themes. So it&#8217;s just one piece of this larger roadmap, but it&#8217;s one of the major grounding points of phase two of the roadmap.</p>\n\n\n\n<p>So what is full-site editing at a high level? Essentially, it&#8217;s a collection of features, and it&#8217;s important that you get the collection part. But it&#8217;s a collection of features that bring the familiar experience of blocks to all parts of your site, rather than just posts and pages. But Anne, what does a collection of features mean? Basically, I&#8217;ve noticed people tend to refer to full-site editing as one big thing. It&#8217;s like an on-off switch. It&#8217;s this monolith, and it&#8217;s actually not. It&#8217;s not this binary thing. It&#8217;s way better to talk about how there&#8217;s different pieces that fit together and interrelate, because it actually gives flexibility for release squads to release what&#8217;s ready, rather than all of it at once. So while it might be easier to talk about how it&#8217;s this one big thing, I encourage you all to kind of think about the different pieces, if you can, and I&#8217;ll touch on this more in a bit.</p>\n\n\n\n<p>Okay. So what does full-site editing actually allow me to do, right? So cool, Anne, a collection of features, but show me the money. (laughing). So this is an example of a 404 page. So a 404 page, typically you&#8217;re not actually able to edit, but with full-site editing, you could actually create this 404 page. This was actually done by one of the automatic designers, Channing. Shout-out to Channing. She did this as part of one of the tests for full-site editing, the outreach program. So it&#8217;s a pretty beautiful thing. While we all might not have the design chops that Channing does, it is pretty neat to see kind of a very tangible, hands-on example of what full-site editing unlocks you to be able to do.</p>\n\n\n\n<p>To get more specific, basically, if you&#8217;re a user, imagine editing the template that a specific post has for a specific category. For theme authors, you&#8217;ll be able to tap into design tools that allow you to focus more on actually creating a really compelling experience and less on getting the code in place and hacking things up. You can also out in and out of whatever you&#8217;re ready for, which is really exciting. But ideally, for theme authors, it&#8217;s going to be a huge change. It&#8217;ll allow creating themes to be much, much easier. If you&#8217;re an agency, you&#8217;ll have greater control over what you can offer clients, including setting custom brand colors with presets to locking down various aspects for consistency, such as typography or wanting only certain default colors to be used.</p>\n\n\n\n<h2 id=\"0-strong-milestones-of-full-site-editing-experience-strong\">Milestones of Full-Site Editing Experience</h2>\n\n\n\n<p>So how is this work being done? So rather than trying to go through everything in one go, this project has actually been broken down into seven different milestones. Some of these milestones are completely separate, their own thing. Some are very interrelated. Some mix and match in different ways. But we&#8217;re going to go through each of them so you can get a sense of how this is being done. I&#8217;m going to try to stay at a high level before going into a very brief demo midway through the presentation. But hopefully this&#8217;ll give you a sense of what this looks like.</p>\n\n\n\n<h3 id=\"1-strong-infrastructure-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-strong\">Infrastructure&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</h3>\n\n\n\n<p>So milestone one, this was actually such a big milestone that it was broken into two parts. Essentially, this is all about laying the foundation, everything from multi-entity saving, which is actually being displayed here in the GIF that you see, where you can actually update multiple things at once, including a template part. You update your header, you update a post, and you update your footer. It&#8217;ll show all the changes happening and allow you to check and uncheck different boxes to save. Basically, just think about this as building the foundation of the experience, the technical foundation, unlocking things like being able to edit a template directly to working on specific blocks for full-site editing, like the site title. So we have a site title block, and it updates everywhere you have it listed.</p>\n\n\n\n<h3 id=\"2-strong-browsing-templates-and-template-parts-strong\">Browsing Templates and Template Parts</h3>\n\n\n\n<p>Milestone two, browsing. Again, there&#8217;s another little visual so you can see what this actually looks like. This is basically giving you a map and a GPS to know your location, how to get where you need to go for your site. So because there are these new parts of editing your site that are unlocked with full-site editing, like template editing and template parts, like a header or footer, there needs to be a way to navigate between them. So this milestone is dedicated to that. How can we make it as easy as possible for you to you get where you need to go?</p>\n\n\n\n<h3 id=\"3-strong-styling-global-styles-theme-json-strong\">Styling &#8211; Global Styles + theme.json</h3>\n\n\n\n<p>Milestone three, styling. So this actually covers a couple different layers. I&#8217;m going to break it down in this slide and then the next one to help give you a sense visually of what this looks like. But this includes everything from the technical requirements to make various levels work and the UI for users. So you can actually see a depiction of the future design for the UI that users will interact with in the imagery here. So there&#8217;s generally three layers, including selling for local blocks, theme defaults, and then global modifications or what we often call global styles. You can think of global styles as basically having the option to edit all aspects of your site. So if you want to set a typography that goes across your entire site, if you want to have certain colors for all H1 headers, you can set that up with global styles.</p>\n\n\n\n<p>Currently, much of the work has been focused on the technical underpinnings, especially around aspects like theme.json, which is a very key component for block themes and a really big tool for block theme authors. But for 5.8, the focus is generally going to be on merging the non-user interface parts of global styles. So don&#8217;t expect to interact with this system unless you&#8217;re a theme author. If you are a theme authro, get really excited. Here&#8217;s a little visual, just you can get a sense of it. So these are the different layers that have to interact in the styling system and hierarchy that needs to be thought of when working on this milestone.</p>\n\n\n\n<h3 id=\"4-strong-20-theme-blocks-strong\">20+ Theme Blocks</h3>\n\n\n\n<p>Milestone four, theme blocks. So because full-site editing opens up so many more aspects of the site to edit, new blocks had to be created, basically. So if you&#8217;re creating a new template for a specific category and you&#8217;re putting in post content and you want to add the post author block, which you can see here, you can quickly add it in, customize it to your liking, add in post comment, add in post data, remove the post date. You can edit each parts of these things, which pretty excited about this, is there&#8217;s actually 20-plus blocks that fall into this category. If all goes as planned, some of those will be released for 5.8 and available potentially for all sites. So even if you&#8217;re not using a block theme, you could have access to these theme blocks, which is pretty powerful and pretty cool.</p>\n\n\n\n<h3 id=\"5-strong-query-block-the-loop-or-post-list-strong\">Query Block &#8211; The Loop or Post List</h3>\n\n\n\n<p>Query block. So the query block has its own milestone, because it&#8217;s a pretty powerful block. It&#8217;s also meant to be a theme author tool, so in the long run, if you&#8217;re a user, imagine that you interact with what we call block variations, which basically are just different variations of a block, as the name implies. But imagine you want to add in your latest post. You&#8217;ll add the latest post block, but underneath it, what will be powering that experience of adding your latest post will be the query block. Essentially, as the name implies, it allows you to query posts and pages and display them in different arrangements on the page. I&#8217;m very excited, actually. In Gutenberg 10.5, which will be released in just about two weeks, there&#8217;s going to be some new patterns. You can see right here, large, medium, small are the current selection of patterns that you have for the query block. But pretty soon, there&#8217;s going to be a grid pattern and a couple other cool ones, which is pretty exciting. Generally speaking, though, if you&#8217;re an end user, don&#8217;t expect to interact with this. If you&#8217;re a theme author, get excited.</p>\n\n\n\n<h3 id=\"6-strong-navigation-block-strong\">Navigation Block</h3>\n\n\n\n<p>Navigation block. Again, this is just a single block, but don&#8217;t be fooled. It&#8217;s definitely a mighty one. So this last one is dedicated to all things navigation block, both in terms of structure and design. You can see in this little GIF I have going on, I&#8217;m just kind of making little design changes and moving things around so you can get a sense of what it&#8217;s like to interact with this block. This milestone actually includes everything from how do you build a really simple menu with a few items to thinking about how to create a really large mega menu and add in new blocks, like the search block that you can see here. We&#8217;re even adding sub-menus, different designs, different layouts, and more.</p>\n\n\n\n<h3 id=\"7-strong-gradual-adoption-widgets-customizer-hybrid-themes-nbsp-strong\">Gradual Adoption &#8211; Widgets, Customizer, Hybrid Themes&nbsp;</h3>\n\n\n\n<p>So the last piece of the milestones is the gradual adoption. I hope this GIF makes you laugh, but also seriously, this is the intent, is we slowly want people to be able to adapt in the way that they can. Once more of these pieces are completed, there&#8217;s basically a ton of room to start exploring how adoption might look like for those who can&#8217;t or don&#8217;t want to restructure a full theme. So this might be an intermix of block-based things and regular PHP templates, or it might be covered by projects like the block-based widget editor and the navigation screen. Both of those projects I&#8217;ll cover later, but for now, just keep in mind that this is intentionally a milestone. We want to allow for gradual adoption and want people to have lots of pathways in to taking advantage of full site editing.</p>\n\n\n\n<h2 id=\"8-strong-whats-coming-to-word-press-5-8-strong\">What&#8217;s coming to WordPress 5.8</h2>\n\n\n\n<p>So what&#8217;s coming to WordPress 5.8? So just last week, a post went out from Josepha, who is the executive director of the WordPress project. I want to read a quote from it just to kind of set the tone and give you a sense. So full-site editing is a collection of projects, and together, they represent a big change, arguably too much for a single release. The most important context to share is that it isn&#8217;t shipping as the full default experience for users. One of the clearest pieces of feedback from the phase one merge process was that there wasn&#8217;t enough time for extenders, agencies, theme authors, plugin developers, site builders, et cetera to prepare for the upcoming changes. With that in mind, this merge process won&#8217;t be an on-off switch, and you can see I&#8217;ve bolded various specific parts that I hope you take home with you.</p>\n\n\n\n<p>All right. So let&#8217;s talk WordPress 5.8 plans. This is up-to-date information as of today. A post was released from Josepha on [inaudible 00:12:21], if you&#8217;d like to check it out. From the call that the project leadership had, this is what they came up with for the 5.8 plans. This includes improvements from Gutenberg 9.9 and beyond. So we always package different versions of Gutenberg into major releases. This release is no different. There&#8217;ll be an introduction of new blocks, including query, site logo, navigation, et cetera. These are each very powerful blocks, very exciting to see. theme.json mechanism, this is part of what allows block themes to use different global styling, which will be very cool for block authors to get their hands on.</p>\n\n\n\n<p>The template editor for pages and a blank template, I&#8217;ll actually be showing a demo of this in a moment. So hang tight there, but it&#8217;ll all make sense in a bit. The widget screen and block widgets in the customizer, this is basically work being done to bring blocks to the widgets experience. I will talk more about that later, about how it&#8217;s a stepping stone towards full-site editing. Then finally, design tools, so even more design tools that people can hook into, including duotone, which adds a really cool color filter, layout controls, padding, and more.</p>\n\n\n\n<h3 id=\"9-strong-short-demo-template-editing-navigation-block-and-multi-entity-saving-strong\">Short Demo: Template Editing, Navigation Block and Multi-Entity Saving</h3>\n\n\n\n<p>So at this point, let&#8217;s pause for a minute and actually show off one of the features that is aimed to be included in 5.8.&nbsp;</p>\n\n\n\n<p>I&#8217;m going to show you template editing, the navigation block, and just some of the cool flows with multi-entity saving is one of the things that we talked about that will make it into this release. So I&#8217;m in the post editor. I have a new post. I love to blog and write and present. I hit Update. Super happy, whatever. Open up the post settings, and there&#8217;s this new section that allows you to both create a brand new template. This will ideally be used both in themes that are block-based themes, so they&#8217;re ready for full-site editing, and potentially for classic themes. There&#8217;s actually work underway so that this will be available in anything being used in WordPress right now.</p>\n\n\n\n<p>So right now, if I hit Edit, this will take me into the template that this post is using. So let&#8217;s do that now. So as you can see, this drops me into what looks like the entire site. So you can see I have my header up here, I have the footer down here, and I can make changes directly to them. So, for example, if I jump in here, this is the navigation block, and I haven&#8217;t yet set it up. So I can say add all pages, and I can start empty. In this case, I&#8217;ll say, &#8220;You know what? Let&#8217;s start empty.&#8221; Let&#8217;s say I want to add a custom link. One of the cool things you can actually do, you can quickly select from here, or let&#8217;s say I want to add a new post. Let me first select post link.</p>\n\n\n\n<p>So adventures around the world. Let&#8217;s pretend I&#8217;m just inspired where I&#8217;m writing this. I can actually create a draft post, which is pretty cool, and it&#8217;ll show up here. It will not show up on the front end, since it&#8217;s a draft, but it actually creates a page draft for this with this title automatically. So let&#8217;s say I&#8217;m scrolling through here. I&#8217;m going, &#8220;Oh, this looks pretty good. Actually, I kind of want to see what it looks like if I add an image to the post here.&#8221; Pull up an image block. Oh, my media library. Hammocks. Can&#8217;t get enough hammocks. Going to throw that in there. Great. So at this point, I&#8217;ve made changes to the actual header. I&#8217;ve made changes to the post. I&#8217;m just going to apply and see what happens.</p>\n\n\n\n<p>So this is the multi-entity saving that I mentioned earlier. Now, as you can see, it has a section for posts, so it&#8217;s saying, &#8220;Hey, you edited this post,&#8221; and it has a section saying, &#8220;Hey, you edited the header.&#8221; So at this point, I&#8217;m going to hit Save, because I want both those changes to propagate. Now I&#8217;m back into my post, into the writing flow, and I can easily switch back and forth. I can also select a new one. But yeah, hopefully this gives you a good sense of one of the key parts that&#8217;s being worked on for inclusion in 5.8. There will be a demo later, but this is just a taste.</p>\n\n\n\n<h2 id=\"10-strong-timeline-of-5-8-release-strong\">Timeline of 5.8 Release</h2>\n\n\n\n<p>To help set the stage for what you can prepare for, here are some upcoming dates to keep in mind. If you&#8217;re like me, time is moving really strangely, so I like to have dates to kind of anchor me. Feel free to take a screenshot of this or write it down if you&#8217;d like. So April 13th and April 27th, these are the go and no-go decision dates. So right now, project leadership actually has gathered. So you might notice if you are good with dates and good with time right now, April 13th has come and gone. So this date has passed, and project leadership has met actually to go through different FSE-related features and projects to figure out what might be ready for 5.8. I would expect to see more high-level posts throughout the month, especially after the second date, the April 27th date. That&#8217;s when final decisions will be made around 5.8.</p>\n\n\n\n<p>Then if all goes well, the beta period for WordPress 5.8 will start on June 8th. So people can actually start getting their hands on the tools that are going to be in place in the actual release and testing it and finding bugs and improving things from there. July 20th is the actual date of WordPress 5.8 and when it&#8217;s released. This is being considered as an open beta, where theme authors, plugin authors, agencies, and more can dig into the tools that are being offered and that I went over previously. Then in December 2021, that&#8217;s around the time when WordPress 5.9 will be released, and this is when I expect to move from tools for extenders into tools actually for users and more user-facing interactions with full-site editing and having things unlocked in the interface that previously in 5.8, most users won&#8217;t notice and won&#8217;t interact with. In 5.9, I expect that to be more visible.</p>\n\n\n\n<p>So some key takeaways. I know this is a lot of information. So only what&#8217;s ready from the various milestones will be shipped. This is not an on-off switch, and it won&#8217;t take over your site. The focus right now is on giving tools to extenders first, before user-facing changes. That&#8217;s a big lesson that was learned from the 5.0 merge, where Gutenberg and the core editor was brought into the WordPress experience. This is something that, thankfully, we&#8217;re in a position where because of these interrelated projects, we&#8217;re able to move in a more flexible and adaptable way to release what&#8217;s ready and not anything else.</p>\n\n\n\n<h2 id=\"11-strong-what-is-the-fse-outreach-experiment-program-strong\">What is the FSE Outreach Experiment Program?</h2>\n\n\n\n<p>All right. At this point, let&#8217;s jump into the full-site editing outreach program. As a reminder, this is the program that I actually run, so consider this free rein to ask me whatever question you&#8217;d like, because I think probably too much about this program. But it&#8217;s something I&#8217;m really excited to talk to you about, and I think it&#8217;s a really neat vehicle for both feedback and education about full site editing.</p>\n\n\n\n<p>So let&#8217;s go over some big picture questions, kind of like we did earlier on, and just get the details of the way. So let&#8217;s start. What is it? So essentially, it&#8217;s just a program focused on full-site editing. It&#8217;s in the form of a Slack channel right now. I&#8217;ll go over how to join it in a bit. But it has curated calls for testing, summary posts of the feedback that we get, and various educational opportunities that you can hop in on, mainly in the form of live streams. I&#8217;m running some hallway hangouts, which are basically just Zoom calls. People can come in, and we can talk about full site editing.</p>\n\n\n\n<h3 id=\"12-strong-whats-the-goal-strong\">What&#8217;s the goal</h3>\n\n\n\n<p>What&#8217;s the goal? So the goal is pretty simple, help improve full-site editing experience by gathering feedback from WordPress site builders. While the group originally started solely to be about feedback, there&#8217;s actually this really neat educational component that has come up as the feature has developed and as more people have gotten curious about it. So people can join just to build their own awareness about what&#8217;s happening with full-site editing and kind of just look at a glance or just help amplify the posts that are coming through.</p>\n\n\n\n<h3 id=\"13-strong-why-was-it-started-strong\">Why was it started?</h3>\n\n\n\n<p>Why was it started? So I&#8217;m going to quote Josepha from the kickoff post. During the WordPress 5.0 retrospective, which is when Gutenberg was merged and the core editor was merged, one of the things that came up routinely was the need for better engagement with users. It was generally agreed from all levels and area of contribution that users would be most impacted by Gutenberg, but the users were also the group we had the least channels of communication to. To help get user feedback to WordPress developers a little bit more seamlessly, I&#8217;m going to try and experiment outreach program. So basically, this is a lesson that was learned from the 5.0 release. In order to prevent another situation where people are caught by surprise, this program is in place to help people get excited and on ramped and on boarded onto full-site editing, as well as getting feedback so that we know if a major workflow change is coming into play, we can actually get user feedback to make it a little bit easier.</p>\n\n\n\n<h3 id=\"14-strong-how-to-join-fse-outreach-experiment-strong\">How to Join FSE Outreach Experiment</h3>\n\n\n\n<p>All right. At this point, I bet you&#8217;re just so stoked. You&#8217;re ready to dive in. Awesome. (laughing). All you&#8217;ve got to do is join FSE Outreach Experiment in Make WordPress Slack, and then you&#8217;re all set. You&#8217;ll just get a bunch of annoying pings for me with prompts for how to test, interesting posts related to full site editing, and more. I promise it&#8217;s also not as scary as this dive, which looks absolutely terrifying, but also beautiful.</p>\n\n\n\n<h2 id=\"15-strong-high-level-feedback-from-calls-for-testing-strong\">High-Level Feedback from Calls for Testing</h2>\n\n\n\n<p>So because at this point, we&#8217;re on our fifth call for testing, I want to go over some high-level pieces of feedback that we&#8217;ve actually gotten about the experience so far. Basically, across all the calls for testing, these are repeated themes that have come up. But keep in mind that because there are certain aspects that we actually haven&#8217;t tested, so global styles, for example, the UI isn&#8217;t available really for users, and it&#8217;s not refined for users, so it&#8217;s not something that we&#8217;ve had as a focus part of testing, even though there is a UI that is available. So certain things are left out purely because they aren&#8217;t necessarily ready for testing, but these are the top pieces of feedback. So bear with me.</p>\n\n\n\n<h3 id=\"16-strong-preview-content-strong\">Preview Content</h3>\n\n\n\n<p>Previewing content. Publish a post. You want to go preview it, or you&#8217;re editing a post. You want to go preview the content. The same thing is true with full site editing. This is a big thing that kept coming up. My question is, is this a necessary workflow, or is it a symptom of other problems? Because in general, the site editor should be as WYSIWYG, as what you see is what you get, as possible.</p>\n\n\n\n<p>So if you&#8217;re making a change, it should look exactly the same as the front end of your site, and because it doesn&#8217;t right now, it&#8217;s causing this tension. There actually is a preview site option under discussion, as well as a browse mode option, which basically, if you&#8217;re actually editing your site, it would turn off everything that wouldn&#8217;t actually show up on the front end. So if you only have one page of posts, but you have pagination set up so if you had multiple pages, that would actually go away. So as you can imagine, this is currently up for discussion, but there actually are a couple different pathways to try and address this problem. But it&#8217;s a very important one to address.</p>\n\n\n\n<h3 id=\"17-strong-saving-process-strong\">Saving Process</h3>\n\n\n\n<p>Saving process. I like to say it&#8217;s technically reliable, but not yet delightful. So basically, it&#8217;s left a lot to be desired right now, and it&#8217;s resulted in a fair bit of confusion. There&#8217;s a lot of feature requests and enhancements and bugs that have come up related to saving. This is likely because the multi-entity saving aspect that I demoed earlier is very new for WordPress users. It&#8217;s not something we&#8217;re used to having as part of our workflow. So it&#8217;s something that inherently needs some work on. So whether it was people requesting more granular saving options to show specifically what was being changed to issues with saving for screen readers to confusion around even just what the general parts mean, like what you&#8217;re actually selecting or unselecting, This was definitely a big, big area of feedback.</p>\n\n\n\n<h3 id=\"18-distinction-between-editing-area\">Distinction between editing area.</h3>\n\n\n\n<p>Distinction between editing area. So basically, because you can edit all parts of your site, it&#8217;s hard to know, &#8220;Am I editing the header for all of my site, or am I editing just a specific piece of content on a post?&#8221; This kind of distinction, jumping between different levels of, &#8220;Oh, you&#8217;re changing this. This will change everything&#8221; to &#8220;You&#8217;re just changing this one thing in this one spot&#8221; is pretty tricky. Right now, there&#8217;s not a lot of friction, and there&#8217;s not a lot clarity in the actual experience to show when you&#8217;re actually jumping between those different levels. So this was a big piece that&#8217;s come up, and it&#8217;s something that is an active area of iteration and exploration to kind of get the right amount of friction in place.</p>\n\n\n\n<h3 id=\"19-rethinking-width-and-alignment\">Rethinking Width and Alignment.</h3>\n\n\n\n<p>So rethinking width and alignment. Previously, alignment in full-site editing worked to optimize how traditional things worked, where basically, traditional things provided their own alignment styles. This worked okay for the project up until this point. But recently, work has been shipped to reimagine how this dynamic should work to allow for actually more control over alignments when using the site editor. This should actually help make sure that whether you want something that&#8217;s full width or you want to change the actual width of your content that&#8217;s showing up that it&#8217;ll actually be what you see is what you get. Right now, this is another piece of feedback at a high level that&#8217;s impacted what you see is what you get experience.</p>\n\n\n\n<h3 id=\"20-strong-general-usability-improvements-strong\">General usability improvements.</h3>\n\n\n\n<p>Generally usability improvements. I admit this is totally a catchall, and it covers a ton of stuff, but it&#8217;s actually a very important one to think of, because it&#8217;ll actually move the site editing experience from being just functional to actually delightful, which is really exciting. There&#8217;s a ton of issues that are included in this, including some enhancement requests, bug reports, all that good stuff. One of my favorites to talk about is creating a background image on a template part. So imagine you have a header. You&#8217;re working on it. You&#8217;re super excited, and you&#8217;re almost done. Then you&#8217;re like, &#8220;Oh, do you what would be really cool is if I had mountains in the background. Maybe I&#8217;ll add a cover block in the background and add an image and set the opacity pretty low, but have mountains going in the background of the site.&#8221; That&#8217;s really hard to do.(laughing). You basically would have to delete everything and add the block in and then add everything back. So those are the kinds of experiences that we&#8217;re trying to improve right now.</p>\n\n\n\n<h3 id=\"21-strong-improving-placeholders-strong\">Improving Placeholders.</h3>\n\n\n\n<p>Improving placeholders. So placeholders, especially for some of the newer blocks, are a powerful way to both guide people and a current point of confusion. So you probably saw this with the navigation block earlier, where it had those little grayed boxes. It&#8217;s like, &#8220;How do we explain to people, &#8216;Hey, this is something you have to set up and engage with, but here&#8217;s generally what it will look like and what it will do&#8217;?&#8221;&nbsp;</p>\n\n\n\n<p>The feedback for this mainly came into play with the query block, social icon block, featured image block, and the navigation block. Each currently actually also get users started in different ways. So not only are there different placeholders for different experiences, the actual experience of interacting with the placeholders are all pretty inconsistent right now. So I think in the long run, it seems that users will benefit a bunch from a standardized, consistent way to interact with placeholder content so that it becomes a really familiar interaction when you&#8217;re working with a more powerful block. This especially is true for the query block and navigation block.</p>\n\n\n\n<p>Okay, now that we&#8217;ve covered the milestones, the outreach program, high-level pieces of feedback, I&#8217;m going to quickly run through some key topics that I imagine you&#8217;re going to have questions about. Just because I cover them here does not mean I don&#8217;t want to answer questions, so please don&#8217;t see this as a sign that you can&#8217;t also still ask questions about these topics. This is just what I&#8217;ve been hearing from folks.</p>\n\n\n\n<h2 id=\"22-strong-will-full-site-editing-take-over-my-site-strong\">Will full site editing take over my site?</h2>\n\n\n\n<p>Hopefully by this point, you all can say no in a resounding way. But no, this is not something that&#8217;s going to all of a sudden, on-off switch, you upgrade to 5.8, it takes everything over. Not at all. You very much have to opt into it through using a theme blocking that supports, actually, these features. In time, more pathways are going to be built as well so that when you&#8217;re actually using full-site editing, you&#8217;ll likely be using pieces in all of it. So you could just be using the query block, or you could just be using global styles without it taking over your entire site.</p>\n\n\n\n<h2 id=\"23-strong-what-about-the-block-based-navigation-and-widget-screens-strong\">What about the block-based navigation and widget screens?</h2>\n\n\n\n<p>What&#8217;s the deal there? So in case you missed it, there&#8217;s actually two additional projects that are dedicated to bringing blocks to more areas of the site outside of full site, I think. This include the navigation screens. You can build out menus and the widget screens. You can build out your widget sections, and this is pretty powerful and high-impact work. They are both separate projects that are tangential to full-site editing, but you can think of them as stepping stones, basically. So you could have a theme that is a classic theme, but it uses a block-based widget screen so that people can have the power blocks with their widgets. Essentially, the whole point, like I said, it&#8217;s a stepping stone to get people used to using blocks more places.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>\n\n\n\n<h2 id=\"24-strong-site-builders-strong\">Site builders</h2>\n\n\n\n<p>I could write a thesis about this, because there&#8217;s so much to talk about here. I imagine I&#8217;m going to get questions about this, but essentially, full-site editing is being built partially so people don&#8217;t get stuck or locked into one site builder or another. It&#8217;s also being built in a way that site builders can actually hook into what&#8217;s being created if they choose to. I&#8217;ve heard from a lot of folks, though, that they expect full-site editing to actually fully replicate their favorite site builder&#8217;s functionality, and I&#8217;m here to say that while the goals between full-site editing and site builders are pretty similar in terms of empowering users and giving better tools to customize a site, the difference is that we&#8217;re building for 40% of the Internet, and we&#8217;re building even for site builders, where site builders have a much more targeted approach.</p>\n\n\n\n<p>In the future, I do think there will always be room for specific takes of how to have an ideal site editing experience, whether that&#8217;s geared to a specific group, like a marketing style approach, or if you want to have things locked down or if you want to have things opened up. But generally speaking, full-site editing is meant to actually expand the way WordPress as a whole uses blocks, so don&#8217;t expect it to fully replicate any sort of site builder, your favorite site builder, essentially.</p>\n\n\n\n<h2 id=\"25-strong-how-is-this-going-to-impact-themes-strong\">How is this going to impact themes?</h2>\n\n\n\n<p>How is this going to impact themes? So in the long run, this should actually make theme development much easier. I think Marcus&#8217;s demonstration later will show that, and much simpler, especially with the design tools that will be essentially ready at your fingertips to tap into. Ideally, because of what&#8217;s being released, it should allow theme authors to focus less on coding and functions and more on design aesthetics, integrating block patterns, and all that good stuff. But because one of the key things I wanted to really drive home in this section, though, is that because full-site editing requires a block-based theme or a theme with certain functionality enabled, this makes theming extremely important to get right. So I&#8217;ve heard people say like, &#8220;Oh, themes are a thing of the past.&#8221; It&#8217;s very much not true. I&#8217;d actually argue the opposite, that theme is almost key to this experience, to having it be delightful and having it makes sense.</p>\n\n\n\n<h2 id=\"26-strong-what-pathways-are-going-to-be-created-strong\">What pathways are going to be created?</h2>\n\n\n\n<p>I know I&#8217;ve talked a lot about pathways this entire time, but it is the entire focus of the final month milestone for full-site editing. So expect a lot of pathways. For now, this includes everything from having a classic theme that can take advantage of global styles to template editing or a block-based widget screen. This also includes things like allowing certain full-site editing, really, blocks to be available for users, regardless of if they&#8217;re using a classic theme or a block theme or enabling the ability to edit block templates directly, kind of like I showed in the demo earlier. So there&#8217;s going to be a ton of options here, and I&#8217;m actually really excited to see what happens once 5.8 kind of sparks the creativity of the community, because I imagine both that people will create their own pathways and start experimenting, and we&#8217;ll also get a very clear sense of, &#8220;Hey, I actually really need X, Y, and Z pathway.&#8221; We&#8217;ll get a sense of demand from the community of core, which is super exciting to have.</p>\n\n\n\n<h2 id=\"27-strong-whats-the-best-way-to-prepare-nbsp-strong\">What&#8217;s the best way to prepare?&nbsp;</h2>\n\n\n\n<p>So this depends on who you are. (laughing). So depending on whoever you are, at a high level, this is what I recommend. Join the FSE Outreach Program. I know this is the thing that I run. I&#8217;m very biased. But seriously, join it. I think it&#8217;s really, really helpful to get a sense both of feedback, what&#8217;s being currently iterated on, and just general education opportunities. If you&#8217;re a theme author, I really recommend checking out the theme experiments repo and joining the block-based theme meetings to learn about the latest and greatest, because lots of good information is shared there. In general, too, it&#8217;s often also helpful to join the weekly core editor meetings, because there&#8217;s regular updates about the projects and PRs people working on. Finally, pay attention to upcoming content on Learn WordPress, because I think there&#8217;s going to be a ton of stuff coming up about full-site editing, depending upon what&#8217;s scoped for 5.8 and 5.9, including building a block-based theme, for example. That will really help, I think, everyone level up.</p>\n\n\n\n<h2 id=\"28-strong-stay-connected-with-anne-mc-carthy-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-nbsp-strong\">Stay connected with Anne McCarthy</h2>\n\n\n\n<p>All right. So we&#8217;re at the very end. At this point, if you want to stay connected with me or you have follow-up questions after this talk, I very much welcome them. You can find me on WordPress or on Slack @annezazu, or you can reach me at my site, nomad.blog. I will also try and drop my automatic email address separately. I just won&#8217;t on a live presentation, in case you want to follow up directly via email. I&#8217;m not on Twitter. I&#8217;m not on Facebook. I&#8217;m on and off of Instagram. So please don&#8217;t try to contact me those ways.</p>\n\n\n\n<p>Finally, I just want to say thanks so much for your time. Let&#8217;s hear your questions at this point. I&#8217;m really excited to hear what you all are thinking and curious about. I do want to say I don&#8217;t know everything, but I can find anything, and I&#8217;ve talked with David about how he can follow up after this presentation to get you all information and answers that you all want to questions that I might not be able to answer. So at this point, I&#8217;m going to pass it off to live and current Anne and give a high-five from past Anne.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 16 Apr 2021 18:21:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Birgit Pauli-Haack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"WPTavern: Enō: ‘Probably This Is the Best Blogging Theme Ever’\";s:7:\"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=115149\";s:7:\"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:163:\"https://wptavern.com/eno-probably-this-is-the-best-blogging-theme-ever?utm_source=rss&utm_medium=rss&utm_campaign=eno-probably-this-is-the-best-blogging-theme-ever\";s: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:4460:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Sometimes a theme&rsquo;s description is so moving that one must install, activate, and test the project. I often rail against the obviously keyword-stuffed text in the free WordPress theme directory. But, I am pleasantly surprised from time to time.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>En&#333; is an elegant, modern and functional WordPress theme. Probably this is the best blogging theme ever. Just see the demo at&hellip;It supports Gutenberg block editor and has a lot of Customizer options&hellip;</p></blockquote>\n\n\n\n<p>Thus began my journey into <a href=\"https://webminimalism.com/blog/eno-wordpress-theme/\">En&#333;</a>, an upcoming theme by Ivan Fonin. I could have been partially a language-barrier thing. Or, the author could have just been having a bit of fun. Nevertheless, it was the sort of description that stood out enough to pull into my test environment. Any blogging theme claiming the title of &ldquo;the best&rdquo; was at least worth a look.</p>\n\n\n\n<p>What I found was a well-designed theme that focused on some of those timeless elements, such as generous use of whitespace and sound typography. I would not go so far as crowning it the best ever created, but it will undoubtedly be the perfect fit for many bloggers in the future.</p>\n\n\n\n<p>Currently, the theme is awaiting a review before it lands in the official WordPress theme directory. However, those who want to try it out early can snag a copy of the ZIP file from its <a href=\"https://themes.trac.wordpress.org/ticket/97585\">Trac ticket</a>.</p>\n\n\n\n<p>En&#333; tackles the intricacies of block editor design like a pro. In areas where so many &ldquo;block-ready&rdquo; themes fail to live up to expectations, it is a textbook example of working alongside the block system.</p>\n\n\n\n<p>Where it falls short is that it does not go beyond nailing down the basics of block design. The theme bundles no patterns, which would allow users to quickly drop in more advanced layouts. It also does not include block styles or even a custom color palette. There are no unique elements in the design where the author stamps his own signature in bold. It is almost formulaic, but that is not necessarily a bad thing. Formula can feel good. It can be comforting when you need something that simply gets out of the way and allows your content to shine.</p>\n\n\n\n<p>While Fonin bills the project as a blogging theme, it stands out as a solid option for photographers. The open-canvas layout leaves ample room for large images and galleries, and the <a href=\"https://demo.webminimalism.com/eno/\">theme&rsquo;s demo</a> is filled with examples.</p>\n\n\n\n<img />Gallery examples from the  En&#333; theme.\n\n\n\n<p>What would make this theme even better would be a few image and gallery styles, allowing end-users to spruce up their blocks a little more.</p>\n\n\n\n<p>As much as I like the theme, it does tick one of the boxes from my most-irritating-things-that-themes-do checklist. It outputs the featured image on single post views above the post content. This creates the dreaded double-image issue when a user also uses the same image in the post itself. The easy fix for this is to provide a theme option for not showing the featured image on single posts.</p>\n\n\n\n<img />No customizer option to disable post featured image on single views.\n\n\n\n<p>It is a surprise that the theme does not have this option because it allows users to enable or disable nearly everything possible outside of the post content. It has three different areas where metadata can be shown: before the post title, after the title, and after the content. Users can pick and choose what appears where via a series of checkboxes. The approach is convoluted at best and is a good representation of why we need the site editor. This is not so much the fault of the theme as it is a limitation of the customizer. Instead of ticking and unticking boxes, users could simply move blocks around to their desired location.</p>\n\n\n\n<p>The comments are broken in the theme at the moment. Each comment&rsquo;s text is outputting a simple comma instead of the content. I am sure this will come up in the theme review and be addressed before it goes live.</p>\n\n\n\n<p>For users looking for a minimalist, block-ready theme, this will be a solid option once it makes it through the review process. I look forward to the day when themes like En&#333; are the baseline when designing for the block system.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 16 Apr 2021 17:20:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:66:\"WPTavern: Full Site Editing Is Partly a ‘Go’ for WordPress 5.8\";s:7:\"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=115193\";s:7:\"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:165:\"https://wptavern.com/full-site-editing-is-partly-a-go-for-wordpress-5-8?utm_source=rss&utm_medium=rss&utm_campaign=full-site-editing-is-partly-a-go-for-wordpress-5-8\";s: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:6930:\"<p class=\"has-drop-cap\">Today, Josepha Haden Chomphosy <a href=\"https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/\">announced the results</a> of yesterday&rsquo;s &ldquo;go/no-go&rdquo; demo and decision on <a href=\"https://wptavern.com/will-full-site-editing-land-in-wordpress-5-8-a-decision-is-forthcoming\">whether Full Site Editing (FSE) would land in WordPress 5.8</a>. The site editor and global styles are not landing in the next release. However, several other features should launch and allow users to build their sites with blocks in new ways.</p>\n\n\n\n<p>The following people attended the demo:</p>\n\n\n\n<ul><li>Mat&iacute;as Ventura &ndash; Demo Host and Gutenberg Project Lead</li><li>Matt Mullenweg &ndash; WordPress Project Lead</li><li>Helen Hou-Sand&iacute; &ndash; Lead Developer</li><li>Josepha Haden Chomphosy &ndash; Executive Director</li><li>H&eacute;ctor Prieto &ndash; Technical Project Manager</li><li>Chlo&eacute; Bringmann &ndash; Assisting with administrative and operational logistics</li></ul>\n\n\n\n<p>Ventura walked the group through the various FSE features that could be ready for WordPress 5.8, taking questions and discussing along the way. There was also a discussion afterward that focused on ideas beyond the next release.</p>\n\n\n\n<p>The following FSE-related features are expected to ship:</p>\n\n\n\n<ul><li>Improvements from Gutenberg 9.9+.</li><li>New theme-related blocks like Query, Site Logo, Navigation, and more.</li><li><code>theme.json</code> integration, which allows themes to define block defaults and settings.</li><li>Template-editing mode for the block editor.</li><li>Block-based widgets screen and customizer integration.</li><li>New block design tools, such as duotone (SVG filters for images), layout controls, padding, and more.</li></ul>\n\n\n\n<p>&ldquo;Not all of the above are currently ready but there&rsquo;s some level of confidence that they can be by the time of 5.8,&rdquo; noted Haden Chomphosy in the post.</p>\n\n\n\n<p>This list feels like a solid compromise between launching some of the more polished FSE features and trying to force in those that are probably out of reach for a July 2021 release. The features also provide current users access to new block tools without activating a block-based theme.</p>\n\n\n\n<p>The group focused on the Query block for much of the early discussion. The Gutenberg development team will likely change the block&rsquo;s user-facing name to something less confusing. It also needs a bit more polishing to make things more user-friendly.  I am interested in seeing how theme authors use this in conjunction with patterns once this launches.</p>\n\n\n\n<p>One other feature that users should look forward to is the <a href=\"https://wptavern.com/first-look-at-initial-designs-for-wordpress-block-pattern-directory\">pattern directory</a>. While it is not ready for integration into the WordPress admin UI, it does not need to be. Users will be able to copy patterns from the directory and paste them directly into their editor. In time, it should become a part of the built-in experience.</p>\n\n\n\n<p>The group seems to have made a good call on which features to include. It is easy to want to push forward and get everything into the hands of users. It can be tougher to pull back and compromise.</p>\n\n\n\n<p>Full video of the demo:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>I had two takeaways that stood out to me more than anything in the meeting.</p>\n\n\n\n<h2>Takeaway #1: Page Template Editor</h2>\n\n\n\n<p class=\"has-drop-cap\">In WordPress 5.8, users should gain access to the <a href=\"https://wptavern.com/first-round-of-the-fse-outreach-program-concludes-identifies-template-editing-mode-problems\">template editor</a>. On the page-editing screen, it allows users to switch out of content-editing mode. From there, they can work on the overall template. Essentially, for this release, it would serve as a landing page builder.</p>\n\n\n\n<p>This is a sort of middle ground between just the block editor and the eventual site editor. I like this route because it does not overwhelm end-users with a complete site-editing experience at once. It is a helping hand, a transition from the current phase to the next, allowing users to familiarize themselves with more advanced tools.</p>\n\n\n\n<p>The template editor will work for all users too. They will not be required to run a block-based theme to access it. Because each template would be a one-off use case, WordPress can serve this up without theme authors opting into it.</p>\n\n\n\n<p>Many block-ready themes have already been including an &ldquo;open canvas&rdquo; type of template. This would remove the need for those unless also including it for third-party builders. It would also solve the portability issue when users switch from a theme that bundles the template and one that does not.</p>\n\n\n\n<h2>Takeaway #2: Many Block-Based Themes</h2>\n\n\n\n<p class=\"has-drop-cap\">At the end of the discussion, the group was more or less spitballing some ideas beyond version 5.8. In particular, Hou-Sand&iacute; shared a vision of what theme development for the official directory could look like in the era of FSE.</p>\n\n\n\n<p>&ldquo;Because the full site editing, like from a user-facing point of view, is not about page building all the time,&rdquo; she said. &ldquo;It&rsquo;s about tweaking what&rsquo;s there. Yeah. So I feel like the correct thing for core to do in terms of bundled themes is actually a bunch of small bundled themes.&rdquo;</p>\n\n\n\n<p>I have previously written about how work on <a href=\"https://wptavern.com/work-on-the-twenty-twenty-two-default-wordpress-theme-should-already-be-underway\">Twenty Twenty-Two should already be underway</a> instead of waiting until the last moment to piece a new default theme together for the end-of-the-year launch. The yearly default theme system has served the community well for over a decade now. I am already warming to the idea of turning it on its head and forging a new path.</p>\n\n\n\n<p>With FSE, developers do not necessarily have to follow all of the rules of traditional themes. Themes like Kjell Reigstad&rsquo;s <a href=\"https://wptavern.com/carrd-like-theme-experiment-provides-a-glimpse-into-the-future-of-theming\">Carrd-like, two-column landing page theme</a> would be well-suited to such an experiment. Smaller, more experimental projects like this could replace the old Twenty* theme system with something new or even complement it.</p>\n\n\n\n<p>Hou-Sand&iacute; also threw out a few ideas around building block-based themes via a library of CC0 images, the patterns directory, and copying/pasting things from WordPress.org. She likened it to the CSS Zen Garden era. It could even open the possibility of bypassing the theme review process since everything would be pre-vetted.</p>\n\n\n\n<p>But, these are thoughts for tomorrow. For now, we are at least getting some initial FSE components.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 15 Apr 2021 21:54: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: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:77:\"WPTavern: Zerodium Temporarily Triples Payout to $300K for WordPress Exploits\";s:7:\"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=115080\";s:7:\"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:197:\"https://wptavern.com/zerodium-temporarily-triples-payout-to-300k-for-wordpress-exploits?utm_source=rss&utm_medium=rss&utm_campaign=zerodium-temporarily-triples-payout-to-300k-for-wordpress-exploits\";s: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:4216:\"<p><a href=\"https://zerodium.com/\">Zerodium</a>, one of the most well-known security vulnerability brokers, announced that it is tripling payouts for remote code execution exploits on default WordPress installations. Payouts are typically $100K but have been temporarily increased to $300K. </p>\n\n\n\n<p>The company focuses on acquiring original and previously unreported zero-day research. It pays researchers for high-risk vulnerabilities and fully functional exploits, with the highest rewards at $2.5M for &lsquo;full chain, zero-click, with persistence&rsquo; Android exploits. This price tag was increased from $200K in September 2019, suggesting Android exploits have become more difficult to find or that demand for them has increased significantly.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">We\'re temporarily increasing our payouts for WordPress RCEs to $300,000 per exploit (usually $100K). <br /><br />The exploit must work with latest WordPress, default install, no third-party plugins, no auth, no user interaction!<br /><br />If you have this gem, contact us: <a href=\"https://t.co/PBuS1nnpED\">https://t.co/PBuS1nnpED</a></p>&mdash; Zerodium (@Zerodium) <a href=\"https://twitter.com/Zerodium/status/1380489573009031170?ref_src=twsrc%5Etfw\">April 9, 2021</a></blockquote>\n</div>\n\n\n\n<p>Exploit resellers operate within a sort of grey area of security research. As a standard practice, security researchers are encouraged to report vulnerabilities to the original developer of the software, not an intermediary that may pass it along to a party that may not use the information for good. The appeal of these companies is that they pay more than most organizations, hence the tagline: &ldquo;<em>We pay BIG bounties, not bug bounties.&rdquo;</em></p>\n\n\n\n<p>WordPress has an account with <a href=\"https://hackerone.com/wordpress/\">Hackerone</a> to pay security researchers for vulnerabilities but <a href=\"https://hackerone.com/wordpress/hacktivity?type=team\">payouts</a> are much smaller in comparison to what exploit brokers pay. This makes it a tough choice for security researchers who do this for a living. Professional zero-day hunters are looking for the highest payouts for the vulnerabilities they find, which can sometimes take months or longer.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Zerodium does not reveal who its clients are or what their purpose is for buying the the vulnerabilities. The best case scenario would be a government entity wanting to secure its own systems. Even then one cannot guarantee that they use the exploit ethically or that they don&rsquo;t inadvertently leak the exploits where they could be used maliciously by others. </p>\n\n\n\n<p>Zerodium did not elaborate on why it has increased payouts for WordPress exploits to $300K. <a href=\"https://blog.wpscan.com/2021/04/10/zerodium-wordpress-exploit.html\">WPScan</a> speculates that the company may suddenly have a greater demand for WordPress RCE exploits, combined with WordPress becoming more secure:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>This could indicate that WordPress is becoming more secure and that it is getting harder to find the critical security issues that buyers want. On the other hand, we must also assume that these types of exploits already exist and are already being actively sold on Zerodium and other similar platforms.</p><p>We could also conclude that if a government is going to pay more than $300,000 on a WordPress RCE exploit, that they intend to use it. World governments may even barter over the exploits so that the seller, in this case, Zerodium, gets the best price.</p></blockquote>\n\n\n\n<p>WPScan also emphasized that with WordPress having such a large presence on the web, an exploit against core with those particular characteristics &ldquo;would be devastating to the web as a whole if it landed in the wrong hands.&rdquo;</p>\n\n\n\n<p>&ldquo;Zerodium increasing their prices may indicate that it is becoming harder to find these critical issues in WordPress Core,&rdquo; WPScan founder and CEO Ryan Dewhurst said. &ldquo;That, at least, should be good news for WordPress and the web as a whole.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 15 Apr 2021 18:11:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\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:\"WordPress.org blog: WordPress 5.7.1 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10144\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8387:\"<p>WordPress 5.7.1 is now available!</p>\n\n\n\n<p>This security and maintenance release features <a href=\"https://core.trac.wordpress.org/query?milestone=5.7.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority\">26 bug fixes</a> in addition to two security fixes. Because this is a <strong>security release</strong>, it is recommended that you update your sites immediately. All versions since WordPress 4.7 have also been updated.</p>\n\n\n\n<p>WordPress 5.7.1 is a short-cycle security and maintenance release. The next major release will be version 5.8.</p>\n\n\n\n<p>You can download WordPress 5.7.1 by downloading from WordPress.org, or visit your Dashboard → Updates and click Update Now.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h3>Security Updates</h3>\n\n\n\n<p>Two security issues affect WordPress versions between 4.7 and 5.7. If you haven’t yet updated to 5.7, all WordPress versions since 4.7 have also been updated to fix the following security issues:</p>\n\n\n\n<ul><li>Thank you <a href=\"https://www.sonarsource.com/\">SonarSource</a> for reporting an XXE vulnerability within the media library affecting PHP 8.</li><li>Thanks <a href=\"https://mikaelkorpela.fi/\">Mikael Korpela</a> for reporting a data exposure vulnerability within the REST API.</li></ul>\n\n\n\n<p>Thank you to all of the reporters for <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">privately disclosing the vulnerabilities</a>. This gave the security team time to fix the vulnerabilities before WordPress sites could be attacked.</p>\n\n\n\n<p>Props to <a href=\"https://profiles.wordpress.org/zieladam/\">Adam Zielinski</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/ehtis/\">Ehtisham Siddiqui</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a> and the WordPress security team for their work on these issues.</p>\n\n\n\n<p>For more information, browse the <a href=\"https://core.trac.wordpress.org/query?milestone=5.7.1&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority\">full list of changes</a> on Trac, or check out the <a href=\"https://wordpress.org/support/wordpress-version/version-5-7-1/\">version 5.7.1 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks and props!</h2>\n\n\n\n<p>The 5.7.1 release was led by <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">@peterwilsoncc</a> and <a href=\"https://profiles.wordpress.org/audrasjb/\">@audrasjb</a>.</p>\n\n\n\n<p>In addition to the security researchers and release squad members mentioned above, thank you to everyone who helped make WordPress 5.7.1 happen:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/ninetyninew/\">99w</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/annalamprou/\">annalamprou</a>, <a href=\"https://profiles.wordpress.org/anotherdave/\">anotherdave</a>, <a href=\"https://profiles.wordpress.org/aristath/\">Ari Stathopoulos</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/bobbingwide/\">bobbingwide</a>, <a href=\"https://profiles.wordpress.org/brechtvds/\">Brecht</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">David Baumwald</a>, <a href=\"https://profiles.wordpress.org/dkoo/\">dkoo</a>, <a href=\"https://profiles.wordpress.org/ocean90/\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/dragongate/\">dragongate</a>, <a href=\"https://profiles.wordpress.org/eatsleepcode/\">eatsleepcode</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/kebbet/\">Erik</a>, <a href=\"https://profiles.wordpress.org/fabianpimminger/\">Fabian Pimminger</a>, <a href=\"https://profiles.wordpress.org/flixos90/\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/mista-flo/\">Florian TIAR</a>, <a href=\"https://profiles.wordpress.org/gab81/\">gab81</a>, <a href=\"https://profiles.wordpress.org/galbaras/\">Gal Baras</a>, <a href=\"https://profiles.wordpress.org/geoffrey1963/\">Geoffrey</a>, <a href=\"https://profiles.wordpress.org/mamaduka/\">George Mamadashvili</a>, <a href=\"https://profiles.wordpress.org/glendaviesnz/\">Glen Davies</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Greg Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/grzim/\">grzim</a>, <a href=\"https://profiles.wordpress.org/ipstenu/\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/jaymanpandya/\">Jayman Pandya</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/joen/\">Joen A.</a>, <a href=\"https://profiles.wordpress.org/jonkastonka/\">Johan Jonk Stenström</a>, <a href=\"https://profiles.wordpress.org/goaroundagain/\">Johannes Kinast</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/joseeyoast/\">Josee Wouters</a>, <a href=\"https://profiles.wordpress.org/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/k3nsai/\">k3nsai</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/gwwar/\">Kerry Liu</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/mihdan/\">Mikhail Kobzarev</a>, <a href=\"https://profiles.wordpress.org/mmuyskens/\">mmuyskens</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/nicegamer7/\">nicegamer7</a>, <a href=\"https://profiles.wordpress.org/otshelnik-fm/\">Otshelnik-Fm</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/palmiak/\">palmiak</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/pwallner/\">pwallner</a>, <a href=\"https://profiles.wordpress.org/rachelbaker/\">Rachel Baker</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/rinatkhaziev/\">Rinat Khaziev</a>, <a href=\"https://profiles.wordpress.org/noisysocks/\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/rogertheriault/\">Roger Theriault</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/yakimun/\">Sergey Yakimov</a>, <a href=\"https://profiles.wordpress.org/sirstuey/\">SirStuey</a>, <a href=\"https://profiles.wordpress.org/stefanjoebstl/\">stefanjoebstl</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\">Stephen Bernhardt</a>, <a href=\"https://profiles.wordpress.org/sumitsingh/\">Sumit Singh</a>, <a href=\"https://profiles.wordpress.org/cybr/\">Sybre Waaijer</a>, <a href=\"https://profiles.wordpress.org/synchro/\">Synchro</a>, <a href=\"https://profiles.wordpress.org/terriann/\">Terri Ann</a>, <a href=\"https://profiles.wordpress.org/tigertech/\">tigertech</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/tobiasbg/\">TobiasBg</a>, <a href=\"https://profiles.wordpress.org/hellofromtonya/\">Tonya Mork</a>, <a href=\"https://profiles.wordpress.org/toru/\">Toru Miki</a>, <a href=\"https://profiles.wordpress.org/grapplerulrich/\">Ulrich</a>, and <a href=\"https://profiles.wordpress.org/vladytimy/\">Vlad T</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 15 Apr 2021 03:05:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Peter Wilson\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Thu, 13 May 2021 10:14:45 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Thu, 13 May 2021 10:00:08 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:2:\"br\";}}s:5:\"build\";s:14:\"20201104100447\";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(11735, 'can_compress_scripts', '1', 'no'),
(1044, 'hide_menu_bh_plugin', '{\"administrator\":[\"edit-tags.php?taxonomy=link_category\",\"edit-comments.php\",\"edit.php\",\"edit.php?post_type=portfolio\",\"edit.php?post_type=staff\",\"edit.php?post_type=testimonial\",\"edit.php?post_type=slide\",\"edit.php?post_type=faq\",\"themes.php\",\"plugins.php\",\"tools.php\",\"options-general.php\",\"cff-top\",\"hide-admin-menu\",\"vc-general\",\"revslider\",\"mailchimp-for-wp\",\"_options\",\"envato-market\"]}', 'yes'),
(11807, '_transient_health-check-site-status-result', '{\"good\":\"10\",\"recommended\":\"7\",\"critical\":\"3\"}', 'yes'),
(1041, 'bsr_data', 'a:8:{s:13:\"select_tables\";a:24:{i:0;s:14:\"wp_commentmeta\";i:1;s:11:\"wp_comments\";i:2;s:8:\"wp_links\";i:3;s:10:\"wp_options\";i:4;s:11:\"wp_postmeta\";i:5;s:8:\"wp_posts\";i:6;s:16:\"wp_revslider_css\";i:7;s:20:\"wp_revslider_css_bkp\";i:8;s:29:\"wp_revslider_layer_animations\";i:9;s:33:\"wp_revslider_layer_animations_bkp\";i:10;s:24:\"wp_revslider_navigations\";i:11;s:28:\"wp_revslider_navigations_bkp\";i:12;s:20:\"wp_revslider_sliders\";i:13;s:24:\"wp_revslider_sliders_bkp\";i:14;s:19:\"wp_revslider_slides\";i:15;s:23:\"wp_revslider_slides_bkp\";i:16;s:26:\"wp_revslider_static_slides\";i:17;s:30:\"wp_revslider_static_slides_bkp\";i:18;s:21:\"wp_term_relationships\";i:19;s:16:\"wp_term_taxonomy\";i:20;s:11:\"wp_termmeta\";i:21;s:8:\"wp_terms\";i:22;s:11:\"wp_usermeta\";i:23;s:8:\"wp_users\";}s:16:\"case_insensitive\";s:3:\"off\";s:13:\"replace_guids\";s:3:\"off\";s:7:\"dry_run\";s:3:\"off\";s:10:\"search_for\";s:29:\"https://kbcf.snippetsweb.com/\";s:12:\"replace_with\";s:26:\"https://www.kbfair.org.au/\";s:15:\"completed_pages\";i:4;s:11:\"total_pages\";i:24;}', 'yes'),
(1045, 'hide_sub_menu_bh_plugin', '[]', 'yes'),
(1046, 'hide_top_menu_bh_plugin', '{\"administrator\":[\"my-account\",\"wp-logo\"]}', 'yes'),
(1047, 'category_children', 'a:0:{}', 'yes'),
(3245, 'auto_core_update_notified', 'a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:19:\"web@snippetsweb.com\";s:7:\"version\";s:5:\"5.5.5\";s:9:\"timestamp\";i:1620876872;}', 'no'),
(22072, '_site_transient_timeout_php_check_6a93f292d9a273c004fc36e1f86d97b3', '1621505174', 'no'),
(22073, '_site_transient_php_check_6a93f292d9a273c004fc36e1f86d97b3', 'a:5:{s:19:\"recommended_version\";s:3:\"7.4\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:0;s:9:\"is_secure\";b:0;s:13:\"is_acceptable\";b:0;}', 'no'),
(22074, '_site_transient_timeout_browser_43c406b46e0b645f7aa35d2e26088d48', '1621505673', 'no'),
(22075, '_site_transient_browser_43c406b46e0b645f7aa35d2e26088d48', 'a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:12:\"90.0.4430.93\";s:8:\"platform\";s:7:\"Windows\";s:10:\"update_url\";s:29:\"https://www.google.com/chrome\";s:7:\"img_src\";s:43:\"http://s.w.org/images/browsers/chrome.png?1\";s:11:\"img_src_ssl\";s:44:\"https://s.w.org/images/browsers/chrome.png?1\";s:15:\"current_version\";s:2:\"18\";s:7:\"upgrade\";b:0;s:8:\"insecure\";b:0;s:6:\"mobile\";b:0;}', 'no'),
(22076, '_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3', '1620944084', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(22077, '_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3', 'a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\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:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"News –  – WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"https://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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"WordPress 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:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 May 2021 01:04:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"en-US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=5.8-alpha-50847\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:10:{i:0;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:32:\"WordPress 5.7.2 Security 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:68:\"https://wordpress.org/news/2021/05/wordpress-5-7-2-security-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:\"Thu, 13 May 2021 01:04:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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:8:\"Security\";s:7:\"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=10334\";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:356:\"WordPress 5.7.2 is now available. This security release features one security fix. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated. WordPress 5.7.2 is a short-cycle security release. The next major release will be version 5.8. You can update to [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Peter Wilson\";s: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:2091:\"\n<p>WordPress 5.7.2 is now available.</p>\n\n\n\n<p>This security release features one security fix. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.</p>\n\n\n\n<p>WordPress 5.7.2 is a short-cycle security release. The next major release will be version 5.8.</p>\n\n\n\n<p>You can update to WordPress 5.7.2 by downloading from WordPress.org, or visit your Dashboard → Updates and click Update Now.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h3>Security Updates</h3>\n\n\n\n<p>One security issue affecting WordPress versions between 3.7 and 5.7. If you haven’t yet updated to 5.7, all WordPress versions since 3.7 have also been updated to fix the following security issue:</p>\n\n\n\n<ul><li>Object injection in PHPMailer, <a href=\"https://nvd.nist.gov/vuln/detail/CVE-2020-36326\">CVE-2020-36326</a> and <a href=\"https://nvd.nist.gov/vuln/detail/CVE-2018-19296\">CVE-2018-19296</a>.</li></ul>\n\n\n\n<p>Thank you to the members of the WordPress security team for implementing these fixes in WordPress.</p>\n\n\n\n<p>For more information refer to <a href=\"https://wordpress.org/support/wordpress-version/version-5-7-2/\">the version 5.7.2 HelpHub documentation</a> page.</p>\n\n\n\n<h3>Thanks and props!</h3>\n\n\n\n<p>The 5.7.2 release was led by <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">@peterwilsoncc</a> and <a href=\"https://profiles.wordpress.org/audrasjb/\">@audrasjb</a>.</p>\n\n\n\n<p>Thank you to everyone who helped make WordPress 5.7.2 happen: <a href=\"https://profiles.wordpress.org/audrasjb\">@audrasjb</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans\">@ayeshrajans</a>, <a href=\"https://profiles.wordpress.org/desrosj\">@desrosj</a>, <a href=\"https://profiles.wordpress.org/dd32\">@dd32</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc\">@peterwilsoncc</a>, <a href=\"https://profiles.wordpress.org/SergeyBiryukov\">@SergeyBiryukov</a>, and <a href=\"https://profiles.wordpress.org/xknown\">@xknown</a>.</p>\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:\"10334\";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: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:\"Welcome to Openverse\";s:7:\"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/2021/05/welcome-to-openverse/\";s: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, 11 May 2021 12:42:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10325\";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:369:\"Following the recent statement by WordPress&#8217;s co-founder Matt Mullenweg and the Creative Commons CEO, Catherine Stihler’s post, I&#8217;m happy to formally announce that CC Search (with the new name Openverse) is now part of the WordPress open source project. Both Matt and I are long-time supporters of Creative Commons. I hope that this will provide [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2211:\"\n<p>Following the <a href=\"https://ma.tt/2021/04/cc-search-to-join-wordpress-org/\">recent statement by WordPress&#8217;s co-founder Matt Mullenweg</a> and the <a href=\"https://creativecommons.org/2021/05/03/cc-search-to-join-wordpress/\">Creative Commons CEO, Catherine Stihler’s post</a>, I&#8217;m happy to formally announce that CC Search (with the new name Openverse) is now part of the WordPress open source project. Both Matt and I are long-time supporters of Creative Commons. I hope that this will provide a long-term, sustainable challenger to closed source photo libraries and further enhance the WordPress ecosystem.</p>\n\n\n\n<h3><strong>How Does This Affect Current Users?</strong></h3>\n\n\n\n<p>Current CC Search users will continue searching and using openly licensed images from around the internet. WordPress plans to continue the great work started by the Creative Commons project and expand search capabilities and features.</p>\n\n\n\n<h3><strong>What’s Next?</strong></h3>\n\n\n\n<p>We look forward to indexing and searching additional media, such as audio and video. As we expand our capabilities and grow the project, we look forward to integrating directly into WordPress and the media library. We hope to not only allow search and embeds of openly licensed media but pay it forward by additionally licensing and sharing your media back.</p>\n\n\n\n<h3><strong>How Can You Contribute?&nbsp;</strong></h3>\n\n\n\n<p>Stop by the Slack channel, <a href=\"https://wordpress.slack.com/archives/C02012JB00N\">#openverse</a>, and take a look at the code repositories moved under the WordPress organization <a href=\"https://github.com/wordpress/?q=openverse\">here on GitHub</a>. You can also follow along with the project on its own make page at: <a href=\"https://make.wordpress.org/openverse\">https://make.wordpress.org/openverse</a>. We are working on setting up the new team, process, and procedures.<br></p>\n\n\n\n<p>Join us in welcoming the team and community. As a treat, check out the most recent WP Briefing episode, <a href=\"https://wordpress.org/news/2021/05/the-commons-of-images/\">The Commons of Images</a>, in which Matt and I discuss CC Search and our hopes for it as part of the WordPress community.</p>\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:\"10325\";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: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:32:\"People of WordPress: Fike Komala\";s:7:\"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/2021/05/people-of-wordpress-fike-komala/\";s: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, 10 May 2021 22:50: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: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:1;a:5:{s:4:\"data\";s:16:\"ContributorStory\";s:7:\"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=10270\";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:158:\"Discover Fike Komala‘s story of using #WordPress to enjoy a remote working career across the globe in this month’s People of WordPress feature. #Indonesia\";s: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:11106:\"\n<p><em>WordPress is open source software, maintained by a global network of contributors. There are many examples of how WordPress has changed people’s lives for the better. In this monthly series, we share some of the amazing stories that are not as well known.</em><br><br>Creating content with WordPress and blogging helped Fike Komala, from Indonesia, build a career where she can work remotely from different locations in the world. <br></p>\n\n\n\n<p>In 2020, Fike joined a US-based company that specializes in form building to work as a content marketer. Using her experience as a freelancer and later a full time employee, she encourages others, particularly women in Asia, to consider remote work as a career option. She is so impressed by remote working benefits, that she is now considering writing about it for a thesis for her Master&#8217;s Degree, which she started this year in Europe.<br></p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"387\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/05/B5939AF2-DFFD-4471-B3F1-7738F82CEF8A.png?resize=632%2C387&#038;ssl=1\" alt=\"Fike pictured with a snow background\" class=\"wp-image-10291\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2021/05/B5939AF2-DFFD-4471-B3F1-7738F82CEF8A.png?w=1024&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/05/B5939AF2-DFFD-4471-B3F1-7738F82CEF8A.png?resize=300%2C184&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/05/B5939AF2-DFFD-4471-B3F1-7738F82CEF8A.png?resize=768%2C470&amp;ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>As a keen blogger, WordPress immediately impressed Fike. Her dad is a programmer, and he helped her create the first of many blogs starting when she was 10 years old. She had private and public blogs, and even an English language one to help her practice and improve her skills. </p>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p><strong>“I got satisfaction and happiness from pouring my thoughts in writing and publishing them in my blog. Writing my thoughts and feelings often helped me process them, and does even now.”</strong></p><cite>Fike Komala</cite></blockquote></figure>\n\n\n\n<p>With a natural talent and love for languages, Fike pursued an Information Systems degree after graduating from high school. Her course covered business learning Java, HTML, CSS, Javascript, and Android programming. She also took courses to learn Bootstrap and Ruby on Rails.&nbsp;</p>\n\n\n\n<h2>Earning Through Building With WordPress</h2>\n\n\n\n<p>Fike’s parents had a business building websites. She was drawn to this work and would help proofread and format the articles. This is how she first encountered WordPress, which was to play a pivotal role in her future career. <br></p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>“I saw WordPress as something more advanced than other platforms, with more themes and plugins to choose from. The default WordPress websites already looked more professional than others.”</p><cite>Fike Komala</cite></blockquote>\n\n\n\n<p>Throughout school, Fike’s experience with WordPress and blogging helped her earn extra money safely online, including translating texts from English to Indonesia, online surveys, and writing articles in English.</p>\n\n\n\n<h2>Discovering Work You Enjoy&nbsp;</h2>\n\n\n\n<p>The last year at University required a year-long full-time internship. Fike worked as an intern at a big general insurance company within the IT quality control staff. She enjoyed working with the people she met and learned a lot through this opportunity, but she declined the offer of a full-time position.&nbsp;</p>\n\n\n\n<p>Fike is a good student who loves learning and did well in her education. Through her traditional internship experience,  she found that programming in an office job did not fulfill her. It strengthened her belief in a finding a career where she could have the freedom and creativity of working remotely.</p>\n\n\n\n<p>“I was a good student, I love learning algorithms, but I didn’t love programming. I’m not that person who can stay calm finding errors in their codes, and then finding out that it’s only missing a character,” said Fike. She added: “I don’t really like the fact that I have to wake up at 6 AM and be back home at 7 PM, and do it all over again the next day.”</p>\n\n\n\n<h2>Adventure Into Remote Work&nbsp;</h2>\n\n\n\n<p>Fike spent time improving her freelance profile, revising it, and applying to jobs as a virtual assistant. She was willing to do any small website jobs such as formatting WordPress posts, designing social media posts, and processing orders for online shops. Through a freelance job submission site, she was able to work with people from across the globe, including Singapore, Australia, Europe, and America. Through the site, Fike was able to gain experience with remote working tools like Slack, Asana, Trello, and Google Suites, and the work gave her practice writing in English.&nbsp;</p>\n\n\n\n<p>It was through this site that Fike saw a job opportunity with a WordPress plugin company. She sent in her profile and blog.&nbsp;</p>\n\n\n\n<p>“This was my first time being interviewed via a video call. I was ecstatic but panicked. On the day, I woke up at 4 AM, got dressed, and opened my laptop. Weirdly, my wi-fi died that morning. So I went to the nearest cafe to get the interview done, and it went great!”</p>\n\n\n\n<p>She was hired to deliver consistency on the company’s blog.&nbsp;</p>\n\n\n\n<p>Through her job, Fike first began to contribute within the WordPress community and was able to attend her first WordCamp, WordCamp Jakarta 2018, sponsored by her firm. Through WordPress, Fike has met many generous, trusting, and helpful people. </p>\n\n\n\n<p>She said: “Because I’ve experienced the generosity of the WordPress people, I wanted to give back to the community.”</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh5.googleusercontent.com/ZDAmqCcebOQII99V2RMYmJikoQ3u-tjy6BcCT39QWsOUrAqq2_HeqJ1735UoxVyQHTO_S_V9lzZEJ7WayLb8kY3or78oqG4Xt5ujbNUpt7Vcz7r20lp9XopkPwh85imnvRxjpWTx\" alt=\"WordCamp swag\" /><figcaption>Swag from WordCamp Jakarta 2018, that’s Wapuu ondel-ondel!</figcaption></figure>\n\n\n\n<figure class=\"wp-block-pullquote\"><blockquote><p><strong>“I got to know the amazing community behind WordPress. How people voluntarily contribute their time, energy, and skills to the community, from development, marketing to translating.</strong> <strong>It was really inspiring.”</strong></p><cite>Fike Komala</cite></blockquote></figure>\n\n\n\n<h2>You Can Inspire Others Through Contributing</h2>\n\n\n\n<p>Fike has been an inspiration to people in her local community and globally within the WordPress community through her enthusiasm and energy.&nbsp;</p>\n\n\n\n<p>She <a href=\"https://www.youtube.com/watch?v=KHSAV_NJtTA\">talks about her joy in contributing</a> during a live interview as part of WordPress Translation Day in 2020.&nbsp;</p>\n\n\n\n<p>So determined to encourage others to become translators of WordPress, she joined the Global Translation Day event with the Indonesian Community last year and took part in wider marketing of the event. She is pictured below with some of the Indonesian polyglots team.</p>\n\n\n\n<p>She continues to support the polyglots and is a General Translation Editor for the Indonesian language. Last year, she also voiced an <a href=\"https://youtu.be/Ifqabp-36_c\">Indonesian translation of the onboarding video</a> for new contributors joining WordPress.org. She has been a regular contributor to the PerempuanWP, an initiative for Indonesian women working in the WordPress world. Working with a firm which uses the WordPress platform has strengthened her familiarity with projects in the community and encourages her interest in contributing.</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh4.googleusercontent.com/H-8VelQbbEb9f5MM-SUXNudVD9U1DNs546yt_cWGRU--GSLm-PCUunnHDNFmquv9w3rWOUadxkbYr9bYsRU1Ecmhb6Ee_Deg_paNEIyyqs91_3DjgtlmfgCA_P45GNA5nf5rmpCe\" alt=\"Indonesian translation team \" /></figure>\n\n\n\n<p>To learn more about contributing to WordPress, visit <a href=\"https://make.wordpress.org/\">make.wordpress.org/</a> and follow the “get involved” link. You can join any of the weekly team meetings to get started, and there is a lot of help available.&nbsp;</p>\n\n\n\n<p>Fike says, “I want to represent Asian women. In the future, I hope I can inspire more women, especially Asians, to work remotely.” She is now studying in Europe for a Master&#8217;s in Digital Communication Leadership. She hopes to use her learning to help other women, particularly back in her home country of Indonesia.</p>\n\n\n\n<p>She continues to share her energy for learning and remote working. </p>\n\n\n\n<p>“<strong>Just learn things. As much as you can. From anywhere, about anything. Keep an open mind. Read books, listen to podcasts, and learn new skills.”</strong></p>\n\n\n\n<p><strong>She added: “If you’re working in the WordPress world, join the WordPress community. It’s a great place to learn from and connect with great people.”</strong></p>\n\n\n\n<h2>Contributors</h2>\n\n\n\n<p>Thanks to Abha Thakor (<a href=\"https://profiles.wordpress.org/webcommsat/\">@webcommsat</a>) and Meg Phillips (<a href=\'https://profiles.wordpress.org/megphillips91/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>megphillips91</a>) for writing this feature, to Surendra Thakor (<a href=\'https://profiles.wordpress.org/sthakor/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>sthakor</a>), Meher Bala (<a href=\'https://profiles.wordpress.org/meher/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>meher</a>), Larissa Murillo (<a href=\'https://profiles.wordpress.org/lmurillom/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>lmurillom</a>), Josepha Haden (<a href=\"https://profiles.wordpress.org/chanthaboune/\">@chanthaboune</a>), Chloé Bringmann (<a href=\'https://profiles.wordpress.org/cbringmann/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>cbringmann</a>) for additional support and graphics, and to Topher DeRosia (<a href=\"https://profiles.wordpress.org/topher1kenobe/\">@topher1kenobe</a>) who created HeroPress. Thank you to Fike Komala (<a href=\'https://profiles.wordpress.org/fikekomala/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>fikekomala</a>) for sharing her #ContributorStory.</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh4.googleusercontent.com/FEZ2FQJ0vQ311YoPfh6ny15NXh8saTLH_RjyDO4pUOuEGBTa-Czk63PGoWL04FawKviRfNx0QXePx-goK04X12ry1BR_WXh-kVPIfsEeItPAX6reN5fHS96q6-8dUI506ZO38Z0G\" alt=\"HeroPress logo\" /></figure>\n\n\n\n<p><em>This post is based on an article originally published on HeroPress.com. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.</em></p>\n\n\n\n<p><em>Meet more WordPress community members in our <a href=\"https://wordpress.org/news/category/heropress/\">People of WordPress series</a>.</em></p>\n\n\n\n<p><em>#ContributorStory #HeroPress #WPTranslationDay</em></p>\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:\"10270\";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:58:\"\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:34:\"WP Briefing: The Commons of Images\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://wordpress.org/news/2021/05/the-commons-of-images/\";s: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, 10 May 2021 12:00:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;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=10266\";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:238:\"In this episode, Josepha is joined by the co-founder and project lead of WordPress, Matt Mullenweg. Tune in to hear Matt and Josepha discuss the relaunch of CC Search (Openverse) in WordPress and the facets of the open source ecosystem. \";s: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/2021/05/WP-Briefing-008.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:24991:\"\n<p>In this episode, Josepha is joined by the co-founder and project lead of WordPress, Matt Mullenweg. Tune in to hear Matt and Josepha discuss the relaunch of CC Search (Openverse) in WordPress and the facets of the open source ecosystem.&nbsp;</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<ul><li>Editor:<a href=\"https://profiles.wordpress.org/dustinhartzler/\"> Dustin Hartzler</a></li><li>Logo:<a href=\"https://profiles.wordpress.org/beafialho/\"> Beatriz Fialho</a></li><li>Production:<a href=\"https://profiles.wordpress.org/mkaz/\"> </a><a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>\n\n\n\n<h2>References</h2>\n\n\n\n<p><strong>Openverse Repositories </strong></p>\n\n\n\n<ul><li>Catalog:&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://github.com/wordpress/openverse-catalog\">https://github.com/wordpress/openverse-catalog</a></li><li>API:&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://github.com/wordpress/openverse-api\">https://github.com/wordpress/openverse-api</a></li><li>Frontend:&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://github.com/wordpress/openverse-frontend\">https://github.com/wordpress/openverse-frontend</a></li></ul>\n\n\n\n<p><strong>Tech Stack Outline</strong></p>\n\n\n\n<ul><li><strong>Frontend</strong>&#8211; Languages: <ul><li>JavaScript, CSS/SCSS</li><li>Libraries/Services: Vue.js, Nuxt.js#&nbsp;</li></ul></li><li><strong>API</strong>&#8211; Languages: <ul><li>Python, PostgreSQL</li><li>Libraries/Services: Django, Elasticsearch, Redis</li></ul></li><li><strong>Catalogue</strong>&#8211; Languages: <ul><li>Python, PostgreSQL</li><li>Libraries/Services: Apache Airflow, PySpark</li></ul></li></ul>\n\n\n\n<p>Join the WordPress Slack instance, #openverse</p>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id=\"more-10266\"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:10</p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing. This is usually the podcast where you can catch quick explanations of some of the ideas is behind the WordPress open source project. Today, I have a little bit of a different topic. It&#8217;s still WordPress, it&#8217;s still open source, but it&#8217;s kind of peering into some stuff for the future as opposed to looking at where we are today or how we got to where we are today.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:36</p>\n\n\n\n<p>You might have recently seen an announcement from Matt that CC Search is joining the WordPress project. This is a really exciting thing for open source, for sure, and definitely, from my perspective, for WordPress. And so I invited Matt to join me today to take a look at what he had in mind with bringing that particular project into our project and what we have in mind for the future. And so, today, this is the WordPress Briefing with Matt and Josepha. And I hope you enjoy the conversation we had. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>01:22</p>\n\n\n\n<p>So, we recently announced for WordPress that we essentially acquired CC Search, a project that&#8217;s been part of Creative Commons. And they recently chose a different kind of roadmap for the work they&#8217;re doing in the future. And so it seemed like a really great opportunity to bring this tool and this, I don&#8217;t know, this kind of experience for our users into the WordPress project. So Matt, what are your thoughts about how, like this commitment to images with CC licenses, with Creative Commons licenses, can impact WordPress and how we work in the open web.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>02:09</p>\n\n\n\n<p>I think it&#8217;s pretty exciting because Creative Commons exists to do for media, you know, images, audio, etc., what open source has done for code. And so for people who choose to want to donate their creative work under these licenses, much like anyone who contributes a plugin, or code or documentation or translations for WordPress, now people for whom their method of expression is, let&#8217;s say, photography, can put that into the comments like literally, I like why it&#8217;s called the Creative Commons, it&#8217;s such a good name. It can be accessed within everyone&#8217;s dashboard for WordPress. And those images can start to really be part of the fabric of the web the same way that code that runs WordPress or its plugins is part of the fabric of the web.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>02:57</p>\n\n\n\n<p>For anyone who&#8217;s listening who&#8217;s not actually already familiar with this concept of the tragedy of the commons, do you want to give us the elevator pitch of what that means and why it&#8217;s so important for WordPress to try to counterbalance that in our work?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>03:12</p>\n\n\n\n<p>Sure, the tragedy of the commons, you know, I think the canonical example is as a shared field in a town, and it doesn&#8217;t belong to anyone, so anyone can use it. And when too many farmers took their sheep there, they would overeat the grass, and then there was no more grass left because it was being overutilized, and there was no one owning the field to say, Hey, we need to practice a more sustainable amount of sheep. grass in</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>03:39</p>\n\n\n\n<p>Put more grass in there.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>03:41</p>\n\n\n\n<p>So basically, the idea is like a shared resource that gets overused and then disappears. With software, we have the opportunity to have the opposite, which is a wealth of comments where every person using the thing actually has the opportunity to make it a little bit better. And that is really beauty of like Wikipedia, open source where every person using it might contribute a small fix, or a translation or a bug report or tell a friend about it, or basically be part of making this thing better, which you know, WordPress is history is very much an example of, and then as it gets better, more people want to use it. And the beautiful thing about software is you can have economics of abundance versus the economics of scarcity. There&#8217;s not one field used, but every additional incremental user of WordPress makes this community stronger and creates a larger market for the products inside it. So those types of dynamics can have the opposite of the tragedy of the commons.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>04:39</p>\n\n\n\n<p>Absolutely. I love this idea that you brought it up in your question, not your question, in your answer right at the top. I love this idea of acknowledging that code isn&#8217;t the only fabric available in open source and certainly not the only fabric of the internet as we know it. This idea of like, let&#8217;s bring Creative Commons licensed images into a more long-term space for WordPress. Do you think that that at some point can apply to videos and other sorts of audio files?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>05:21</p>\n\n\n\n<p>Absolutely. There already is a ton of Creative Commons licensed content out there that people can use. But there&#8217;s a discoverability problem, you know? Each individual image or audio file or video is, is a little bit of an island. So that&#8217;s why it&#8217;s so important that there&#8217;s the equivalent of a search engine that allows people to discover all the great stuff that&#8217;s out there. And what happens today is there&#8217;s stock photography sites, some of which used to be Creative Commons-based, but many have moved away from that. So they essentially relicense their user contributions. Or people, if we&#8217;re being real, people just go to Google images, and they might utilize images that they don&#8217;t actually have rights to. It&#8217;s not the end of the world, but it&#8217;s not ideal. And so we can create this really compelling directory experience of imagery, which people have chosen to share and want to be used. I think that&#8217;s a much better outcome than the equivalent of piracy.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>06:21</p>\n\n\n\n<p>Yeah, yeah, absolutely. So I leapt right into this and didn&#8217;t really give any context to what CC Search is or anything, but for anyone who is not familiar with this tool already, CC Search is, as Matt mentioned, a search engine that currently is focused specifically on images that use open licenses. The Creative Commons licenses are like the content-specific version of GPL for code, which is a really big deal, I think. If wishes were fishes, Matt, and you had your total hope ahead of you, what is your hope for the relaunch of this product and this tool in WordPress?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>07:15</p>\n\n\n\n<p>Well, first and foremost, I think we can improve the experience of designing and contributing themes and then modifying them with this really fantastic image directory if we&#8217;re able to build it in the media library. And lots of plugins like Jetpack do some version of this. I think that Jetpack uses Pexels or one of the proprietary, but open libraries. And so we can make it fully, like you said, the equivalent of GPL and open source, all the better. I think longer-term, I&#8217;d love to have a way for people who are adding media to the WordPress site to set it to be available under a Creative Commons license. So just to make it easy and built-in for people to create more Creative Commons license imagery. And then, you know, with the integration of Gutenberg and other things, we can make it easy for other people to use it and credit back the original author if they choose to. And what we find is that even though with CC0, which is essentially a kind of like putting something into the public domain, credit is not required. If you make it the default to link back to the original photographer, author, most people believe that because they like creating things that they use. So you get the best of both worlds; you have the freedom of use for any purpose, including not requiring the credit. But then, just by having it by default, when you insert one of these images, a lot of people are going to leave that and link back to the original author, which I think is also really cool. Like you&#8217;re not required to have a credit link on WordPress, but most people leave the Powered BY WordPress on there.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>08:45</p>\n\n\n\n<p>One of the interesting areas, you mentioned Pexels in this case. One of those interesting areas that we, as a project, can really explore here is how to make it so that the metadata gives you confidence in the origin of the image. Like I don&#8217;t believe that there are any set standards for that. I&#8217;ve just started my research, obviously, because they&#8217;re brand new to us, but I just don&#8217;t think there are any standards available there. And, I think that there is an opportunity for WordPress as a true supporter of the open web to help change the fact that we don&#8217;t have that’s one of the main competitive disadvantages that open source libraries have been trying to combat and especially with Unsplash, who eventually did get purchased by Getty Images. Still, I feel like part of what must have driven that decision to change the licensing terms had to be that they are up against that behemoth of Getty Images where people know where the things came from. They know where the images came from, and they can trust that lineage and model releases and all that stuff. I&#8217;m just really interested to see how we can; I don&#8217;t know; I hate to say dignify contributors who are offering their contributions to open source in this way. But, it also is kind of that there&#8217;s no sense in saying that just because you did not accept payment from getting images, your photos weren&#8217;t any good, or your images did not have an excellent path to where they are housed at that moment.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>10:39</p>\n\n\n\n<p>I mean, it&#8217;s really fun to contribute to something larger than yourself. And for many folks, you know, their gift, their craft is something like photography. And so there&#8217;s always going to be the sort of paid marketplaces and, and something like Shutterstock, I think really fantastic companies and services. I think a marketplace for paid content. But we just want to make an alternative, so those who want to donate their work to the world, much like engineers, and designers, and translators of WordPress, donate their work some of that effort to the world, they can do so. Right now, there are some places for that, but we&#8217;re going to try to create one that is fully open, has no advertising, has an open API. So other CMSs can access it too.&nbsp; You know, we&#8217;re going to try to bring the WordPress philosophy to this space.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>11:29</p>\n\n\n\n<p>Gosh, I just love that. While we&#8217;re on the question of contributing to something bigger than yourself, bringing the WordPress philosophy into this space, how do you think CC Search will impact the current media library and how WordPress handles media in general? Or do you have an idea about how it will impact that? Sometimes we don&#8217;t know until we get in?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>11:53</p>\n\n\n\n<p>Yeah, I think within Gutenberg, the idea of adding an image from an online library or a search is something we&#8217;ve wanted to do for a while. But either the licensing made it a little tricky, or, you know, some of the sites that did have open things, maybe the site itself had like a lot of advertising or pop-ups or things like that. So by having this hosted by wordpress.org, we&#8217;ll have a clean, open source, and ad-free place that people can access. I suppose it&#8217;s also worth saying that CC Search, which we&#8217;re rebranding as Openverse, is actually all the code behind is open source as well. So there is going to be a new project on WordPress&#8217;s GitHub that will be this open source search engine. So that&#8217;s also part of the contributions; we&#8217;ll be pointing this search engine to try to index and collect Creative Commons license media, but perhaps it could also provide a base for someone else wanting to build a different characters engine or just host Openverse themselves and run it themselves; that is totally fine.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>13:00</p>\n\n\n\n<p>I should probably mention, for any of the WP Briefing listeners who are contributing to the WordPress project itself, there is a brand new team that we&#8217;re working on building, and for one wander over and welcome everybody, we are welcoming in an open source community into our open source community. And so, of course, we want to make sure that they know how to get around and feel welcome in the space. But also, anything that you are interested in helping to contribute to that particular project, I think would be helpful. WordPress is big; we have a long history. And so I think I feel confident in saying that, if I were on that team that&#8217;s bringing in this new tool, I would hope that there were some OG WordPressers, who were available to help me discover the ins and outs of things, especially as its 18 years of us.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>14:04</p>\n\n\n\n<p>Yeah, it&#8217;s also a new technology stack. So let&#8217;s say you want to be involved in WordPress, but your expertise is more on the Python side, or Elastic Search or something like that. We now have a project where people who are into that or want to learn about it can get involved. Because, of course, you know, contributing and being involved with open source is probably the best way to learn a technology, better than any college degree.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>14:28</p>\n\n\n\n<p>I was just talking to some folks about that; our active learning opportunities and our passive learning opportunities get into a different balance as we get older. And active learning opportunities are for real in school, right? And our passive learning opportunities where you get to look at someone else&#8217;s code, you get to review proposals on user flows, and things are harder and harder to come by unless you happen to be in an open source project where we&#8217;re just working on that in the open all day, every day. And I&#8217;ll put a link to the repos in the show notes, and also, I&#8217;ll include a list of the tech stack that we&#8217;re looking at there, just so that no one has to like, chase it down. But yeah, I&#8217;m excited about this new integration, not only for the CMS but also for the community.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>15:26</p>\n\n\n\n<p>And the whole library will be available to any plug-in who wants to call to it. And like we said, even other CMSs, much like we designed Gutenberg to be able to be used by other CMSs, how cool would it be if Drupal or Joomla or others were also able to leverage this library and allow their users to contribute to it as well?</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>15:47</p>\n\n\n\n<p>Yeah, absolutely. Absolutely. There is a burning question that I feel like we probably should just go ahead and answer here. I&#8217;ve been asked a few times, and I think you have been asked a few times whether this is an actual acquisition. And If yes, then what entity is it under? Is it under the WordPress Foundation? Is it under Automattic?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>16:10</p>\n\n\n\n<p>It&#8217;s a little complicated because, as you know, WordPress.org is not part of the Foundation. So basically, Automattic paid Creative Commons, the nonprofit. They will essentially redirect the old URL, so old links to Creative Commons Search won&#8217;t break. And we ended up hiring some of the people that they were parting ways with into Automattic. And then we put that open source code, and we&#8217;ll run the service on WordPress.org, and then those we hired, Automattic hired, will contribute to WordPress.org and the open source projects that power what we&#8217;re calling Openverse now.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>16:54</p>\n\n\n\n<p>I am.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>16:56</p>\n\n\n\n<p>That&#8217;s kind of an acquisition, but also from a nonprofit, and then going into something, which is not a nonprofit, but is open source and sort of freely available, which is WordPress.org, the website.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>17:06</p>\n\n\n\n<p>Yeah, that has been hard for me to answer because you&#8217;re right, it&#8217;s not like it was donated to WordPress or something. But everything that we&#8217;re doing is being donated back to the project, and of course, hopefully, really living into that WordPress ethos that we have of giving back to, to the project, something that made your work and your life better. So there&#8217;s some, some finger-crossing going on in there.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>17:37</p>\n\n\n\n<p>We could have skipped some of the steps because the code was open source; we could have just used it or something like that. But it was also a good opportunity, I think, to support the Creative Commons organization. And like we said, as part of that donation, there&#8217;ll be redirecting Creative Commons Search to WordPress.org. And honestly, we don&#8217;t need that, but it just from the point of view of keeping links workings, which is a big passion of mine. I like that none of the links will break or things to the Creative Commons Search, which I think has been around for&#8230; I don&#8217;t actually know the exact timeline, but a very long time. It&#8217;s been part of the internet for a long time. So we&#8217;re happy that it can now continue and be something that can plausibly be around for many decades to come.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>18:23</p>\n\n\n\n<p>Yeah, we&#8217;re going to build ourselves a little sustainable program around this project, and it&#8217;s going to be beautiful; I&#8217;m excited.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>18:31</p>\n\n\n\n<p>I did want to give everybody a cultural heads up. When I say crossing my fingers, I know that for some of our cultures, that means I was lying. That is not what I&#8217;m saying—crossing my fingers and moving forward on this with a lot of hope.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>18:51</p>\n\n\n\n<p>I tried to be careful about my local idioms when I&#8217;m talking to folks who don&#8217;t know that I&#8217;m from Arkansas, so I sometimes say weird things. But I&#8217;ve given up on y&#8217;all, for instance, like that has made its way right back into my language.&nbsp;</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>19:09</p>\n\n\n\n<p>Y&#8217;all is great. In Texas, we had a funny thing, which maybe applies to you now, which is &#8220;more nervous than a long-tailed cat in a room full of rocking chairs.&#8221; I bet you haven&#8217;t heard that one.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>19:21</p>\n\n\n\n<p>I have not, but I love it, and I&#8217;m going to fold it into my personal vocabulary for later use.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>19:30</p>\n\n\n\n<p>The response to this has been overwhelmingly positive, and I know that I am incredibly positive. I just mentioned like I&#8217;m moving forward through this with hope, even though there&#8217;s a lot of stuff that I don&#8217;t actually know about how we can implement it. I have never brought an existing open source community into an open source community that I&#8217;m currently working with. So there&#8217;s a lot of learning to be done in there. But, from your side Matt, like, are there any things that you are feeling anxiously hopeful about for this? Anything that you hope is right, but you&#8217;re not sure about?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>20:14</p>\n\n\n\n<p>Oh, this is just the first step of many. So just having the search engine, is I think good to provide a service to the internet. But where we can really leverage it is those next steps we already talked about, which is really building out the API and integrating the API with the WordPress admin to make it easily accessible within people&#8217;s dashboards. And the Gutenberg blocks to embed these images, quickly and easily, and with all the proper credit and everything. And then the next step, which was probably the one I&#8217;m most excited about, which is enabling folks to contribute to the Creative Commons. And by that, I mean the Commons of Images, which have open licenses and are encouraged for reuse and remixing and all those sorts of great things. And I think that anything we can do to increase more of that stuff on the internet also enables a lot of creativity and innovation.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>21:10</p>\n\n\n\n<p>All right. Well, that was an excellent conversation. I am really excited about this. I want to, for my work, just say a huge welcome to the folks over at CC Search and our brand new group around Openverse, and a big thanks to the folks over at the Creative Commons group. Matt, do you have anything else you want to share with any of our audience?</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>21:39</p>\n\n\n\n<p>No, I feel great that we could support the Creative Commons, keep this going for the open internet, and so excited to work alongside the folks who have been working on Openverse and take it to the next iterations and the next level.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>21:56</p>\n\n\n\n<p>Beautiful. Well, Matt, thank you so much for joining me today. This was a wonderful conversation. My friends, this has been Matt Mullenweg, WordPress project co-founder, and project lead.</p>\n\n\n\n<p><strong>Matt Mullenweg&nbsp; </strong>22:08</p>\n\n\n\n<p>Thank you so much for having me.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>22:17</p>\n\n\n\n<p>Thank you for tuning in today to the WordPress Briefing. I hope that conversation made you as excited as I am about this new adventure that we&#8217;re embarking on with CC Search and that whole team. I&#8217;m going to put in the show notes a few links to where you can find them, where they&#8217;re doing their work, what you can collaborate on, and also some notes about the tech stack that goes into it. I&#8217;m your host, Josepha Haden Chomphosy.Thanks again for joining me and I&#8217;ll see you in a couple of weeks.</p>\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:\"10266\";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:57:\"\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:\"The Month in WordPress: April 2021\";s:7:\"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/2021/05/the-month-in-wordpress-april-2021/\";s: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, 04 May 2021 15:00:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10253\";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:297:\"As WordPress grows, both in usage as a CMS and in participation as a community, it’s important for us to shed the idea that software creation is only about what literally can be done to code or what literally can be done to core or what literally can be done to the CMS.&#160; That was [&#8230;]\";s: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:\"Hari Shanker R\";s: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:11530:\"\n<blockquote class=\"wp-block-quote\"><p>As WordPress grows, both in usage as a CMS and in participation as a community, it’s important for us to shed the idea that software creation is only about what literally can be done to code or what literally can be done to core or what literally can be done to the CMS.&nbsp;</p></blockquote>\n\n\n\n<p class=\"has-drop-cap\">That was <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden Chomphosy</a> on the “<a href=\"https://wordpress.org/news/2021/04/your-opinion-is-our-opportunity/\">Your Opinion is Our Opportunity</a>” episode of the <a href=\"https://wordpress.org/news/podcast/\">WP Briefing Podcast</a>, speaking about the importance of co-development and testing for the continued growth and maintenance of WordPress. This month’s updates align closely with these ideas. Read on and see for yourself.&nbsp;</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.7.1 is launched</h2>\n\n\n\n<p>WordPress security and maintenance release &#8211; <a href=\"https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/\">5.7.1</a> came out in April. The release fixes two major security issues and includes 26 bug fixes. You can update to the latest version directly from your WordPress dashboard or by <a href=\"https://wordpress.org/download/\">downloading</a> it from WordPress.org.</p>\n\n\n\n<p>Want to contribute to WordPress 5.8? Check out the <a href=\"https://make.wordpress.org/core/5-8/\">5.8 Development Cycle</a>. To contribute to core, head over to <a href=\"https://core.trac.wordpress.org/\">Trac</a>, and<a href=\"https://core.trac.wordpress.org/report/6\"> pick a 5.8 ticket</a> –– more info in the <a href=\"https://make.wordpress.org/core/handbook/\">Core Contributor Handbook</a>. Don’t forget to join the WordPress <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel in the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a> and follow the <a href=\"https://make.wordpress.org/core/\">Core Team blog</a>. The Core Team hosts weekly chats on Wednesdays at <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=5&amp;min=00&amp;sec=0\">5 AM</a> and <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=20&amp;min=00&amp;sec=0\">8 PM</a> UTC.&nbsp;</p>\n\n\n\n<h2>Gutenberg Version 10.3, 10.4, and 10.5 are out</h2>\n\n\n\n<p>Contributor teams released Gutenberg <a href=\"https://make.wordpress.org/core/2021/04/02/whats-new-in-gutenberg-10-3-31-march/\">version 10.3</a> on April 2, <a href=\"https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/\">version 10.4</a> on April 14, and <a href=\"https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/\">version 10.5</a> on April 30! <a href=\"https://make.wordpress.org/core/2021/04/02/whats-new-in-gutenberg-10-3-31-march/\">Version 10.3</a> improves the block toolbar and the navigation editor, whereas <a href=\"https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/\">version 10.4</a> adds block widgets to the customizer and improvements to the site editor list view. In <a href=\"https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/\">version 10.5</a>, you will find a set of new block patterns and enhancements to the template editing mode, along with the ability to embed PDFs.&nbsp;</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core Team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a>. The “<a href=\"https://make.wordpress.org/core/2021/03/08/whats-next-in-gutenberg-march-2021/\">What’s next in Gutenberg</a>” post offers more details on the latest updates. If you are unfamiliar with the Gutenberg plugin, <a href=\"https://wordpress.org/news/2021/04/become-an-early-adopter-with-the-gutenberg-plugin/\">learn more in this post</a>.</p>\n\n\n\n<h2>Full Site Editing updates</h2>\n\n\n\n<p>Following the <a href=\"https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/\">Full Site Editing (FSE) feature demo</a> hosted by <a href=\"https://profiles.wordpress.org/matveb/\" target=\"_blank\" rel=\"noreferrer noopener\">Matías Ventura</a>, the project leadership decided that WordPress 5.8 will only include some FSE features, such as a template editor for pages/blank templates, a widget editor screen, and the theme.json mechanism. Other features like the Global Styles interface and Site Editor (managing all templates) will be made available later. The team has <a href=\"https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/\">started working on the next steps</a> in shipping these chosen FSE features with version 5.8.</p>\n\n\n\n<p>New to FSE? Check out <a href=\"https://wordpress.org/news/2021/04/curious-about-full-site-editing/\">this blog post</a> for a high-level overview of the project. You can help test FSE by participating in the <a href=\"https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/\">latest FSE Outreach Program testing call </a>–– leave your feedback by May 5th. Want to participate in future testing calls? Stay updated by following the <a href=\"https://make.wordpress.org/test/2021/04/22/upcoming-fse-outreach-program-schedule/\">FSE outreach schedule</a>. You can also <a href=\"https://make.wordpress.org/test/2021/04/28/fse-program-bring-your-questions-round-two/\">submit your questions</a> around FSE right now.</p>\n\n\n\n<h2>WordCamp Europe 2021 is on the calendar</h2>\n\n\n\n<p>One of the most exciting WordPress events,&nbsp; <a href=\"https://europe.wordcamp.org/2021/\">WordCamp Europe 2021</a>, will be held online on June 7-9, 2021! Event organizers have opened up calls for <a href=\"https://europe.wordcamp.org/2021/call-for-sponsors/\">sponsors</a> and <a href=\"https://europe.wordcamp.org/2021/call-for-media-partners-and-supporters/\">media partners</a>. Free tickets for the event will be available soon — <a href=\"https://europe.wordcamp.org/2021/#subscribe-email\">sign up for email updates</a> to be notified when they are out!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading</h2>\n\n\n\n<ul><li>WordPress now powers <a href=\"https://w3techs.com/technologies/details/cm-wordpress\">41% of the web</a>!</li><li><a href=\"https://make.wordpress.org/updates/2021/04/15/quarterly-updates-q1-2021/\">Q1 2021 updates from the WordPress project</a> have been published.</li><li>The Core Team discussed a <a href=\"https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/\">proposal</a> to treat Federated Learning of Cohorts (FLoC), a Google Chrome feature, as a security concern. The team <a href=\"https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/#comment-41207\">eventually decided</a> to track the status of the FLoC trial/implementation in a <a href=\"https://core.trac.wordpress.org/ticket/53069\">Trac ticket</a> and monitor periodically.&nbsp;</li><li>The Core Team will <a href=\"https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/\">remove Internet Explorer 11 support in WordPress version 5.8</a>.&nbsp;</li><li>The Community Team has opened up a <a href=\"https://make.wordpress.org/community/2021/04/26/discussing-the-path-to-in-person-wordcamps/\">discussion on the path to in-person WordCamps</a> and is requesting feedback from community members.</li><li>The Community Team is also <a href=\"https://make.wordpress.org/community/2021/04/19/discussion-companies-who-run-competitive-ads-against-wordpress-and-apply-to-sponsor-wordcamps/\">requesting feedback</a> on whether companies who run competitive ads against WordPress can apply to sponsor WordCamps.&nbsp;</li><li><a href=\"https://centroamerica.wordcamp.org/2021/\">WordCamp Centroamérica 2021</a> and <a href=\"https://greece.wordcamp.org/2021/\">WordCamp Greece 2021</a> were held successfully in April. Videos of WordCamp Centroamérica are now available <a href=\"https://wordpress.tv/event/wordcamp-centroamerica-2021/\">on WordPress.tv</a>! While you are at it, don&#8217;t miss this<a href=\"https://central.wordcamp.org/news/2021/04/29/making-a-great-online-conference-experience-at-wordcamp-prague/#\"> excellent recap of WordCamp Prague 2021</a> on the WordCamp Central blog.</li><li>Contributor teams are actively working on building the <a href=\"https://wordpress.org/patterns/\">Block Pattern Directory</a>. You can read about work updates on this project from the <a href=\"https://make.wordpress.org/meta/2021/04/28/block-pattern-directory-update/\">Meta Team</a> and the <a href=\"https://make.wordpress.org/design/2021/03/30/wordpress-org-patterns-directory/\">Design Team</a>.</li><li>Check out the <a href=\"https://wordpress.org/news/2021/04/getting-started-with-the-figma-wordpress-design-library/\">blog post on getting started with the Figma WordPress Design Library</a>. You can use the library to create design prototypes for the WordPress UI in <a href=\"https://www.figma.com/\">Figma</a>.</li><li>The Polyglots Team is making significant progress on the <a href=\"https://make.wordpress.org/polyglots/2021/04/26/polyglots-training-working-group-update-3/\">Polyglots Training course</a>.</li><li>The Training Team has <a href=\"https://make.wordpress.org/training/2021/04/23/discussion-contributor-ladders-for-the-training-team-and-learn-wordpress/\">proposed a contributor ladder</a> as a resource for team contributors to understand ways to participate and find growth opportunities.&nbsp;</li><li>The <a href=\"https://github.com/WordPress/Requests\">Requests library</a> has moved to the WordPress GitHub organization and has a new release: <a href=\"https://github.com/WordPress/Requests/releases/tag/v1.8.0\">version 1.8.0</a>.&nbsp;</li><li>The Docs Team is<a href=\"https://make.wordpress.org/docs/2021/04/05/update-on-the-revision-of-documentation/\"> working on redesigning HelpHub</a> by reviewing its content and design.</li><li>The Themes Team has shared a proposal on <a href=\"https://make.wordpress.org/themes/2021/04/22/removing-blockers-for-block-themes/\">fixing upload issues for block themes</a>.</li><li><a href=\"https://wordpress.org/news/2021/04/people-of-wordpress-tyler-lau/\">Tyler Lau</a> from the U.S. was featured in April’s <a href=\"https://wordpress.org/news/category/heropress/\">People of WordPress</a>.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it using this form</em></a><em>.</em></p>\n\n\n\n<p><em>The following folks contributed to April’s Month in WordPress: <a href=\'https://profiles.wordpress.org/andreamiddleton/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>andreamiddleton</a> <a href=\'https://profiles.wordpress.org/cbringmann/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>cbringmann</a> <a href=\'https://profiles.wordpress.org/chaion07/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chaion07</a> <a href=\'https://profiles.wordpress.org/hlashbrooke/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>hlashbrooke</a> and <a href=\'https://profiles.wordpress.org/jrf/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jrf</a>&nbsp;</em></p>\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:\"10253\";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:57:\"\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:55:\"Getting Started with the Figma WordPress Design Library\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"https://wordpress.org/news/2021/04/getting-started-with-the-figma-wordpress-design-library/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 28 Apr 2021 17:52:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Uncategorized\";s:7:\"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=10173\";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:53:\"Get Started with the Figma WordPress Design Library! \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:26010:\"\n<p>Created by James Koster, (<a href=\'https://profiles.wordpress.org/jameskoster/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jameskoster</a>)</p>\n\n\n\n<p>As the name suggests, the WordPress Design Library is a library of WordPress design assets, enabling anyone to quickly create design prototypes for WordPress UI in Figma.</p>\n\n\n\n<p>These tools are useful for designers when creating new UI and for anyone looking to contribute ideas, enhancements, or even solutions to bug reports. Sometimes pictures really do speak a thousand words.</p>\n\n\n\n<p>In this post, we&#8217;ll talk about some key features of Figma before diving into a practical example that demonstrates some of the WordPress Design Library utilities.</p>\n\n\n\n<h2><strong>What Is Figma?</strong></h2>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large is-resized\"><img loading=\"lazy\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?resize=632%2C296&#038;ssl=1\" alt=\"\" class=\"wp-image-10174\" width=\"632\" height=\"296\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?resize=1024%2C481&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?resize=300%2C141&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?resize=768%2C361&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?resize=1536%2C722&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?w=1770&amp;ssl=1 1770w, https://i2.wp.com/wordpress.org/news/files/2021/04/image8.png?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></div>\n\n\n\n<p><a rel=\"nofollow\" href=\"https://www.figma.com/\">Figma</a> is a collaborative design tool that members of the WordPress project&#8217;s design team have<a href=\"https://make.wordpress.org/design/2018/11/19/figma-for-wordpress/\"> been using</a> for several years to work on and share design concepts. It offers a variety of handy features such as: in-browser access, rich prototyping tools, component libraries, code inspectors, live embeds, inline commenting, plugins, and much much more.</p>\n\n\n\n<p>Perhaps best of all, it is totally free to sign up and start playing around. If you join the WordPress.org Figma organization (instructions below), you&#8217;ll gain access to the WordPress Design Library enabling you to design WordPress UI in no time.</p>\n\n\n\n<h2><strong>What Is the WordPress Design Library?</strong></h2>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>In Figma, you can share components and styles by publishing them, transforming your file into a library so that you can use instances of those components in other files.</p><p></p><p></p><cite><a rel=\"nofollow\" href=\"https://www.figma.com/best-practices/components-styles-and-shared-libraries/#:~:text=Libraries%3A%20In%20Figma%2C%20you%20can,instances%20of%20your%20components%20live.\">Figma.com</a></cite></blockquote>\n\n\n\n<p>It may be easiest to think of the WordPress Design Library as a visual representation of all the javascript components that compose UI in the WordPress codebase. As an end user of the library, you can use those components in a self-contained environment to create new interface designs. It&#8217;s kind of like a big LEGO box containing all the UI pieces (buttons, form inputs, etc.) that you can use to create and try out new designs.</p>\n\n\n\n<figure class=\"wp-block-jetpack-image-compare\"><div class=\"juxtapose\" data-mode=\"horizontal\"><img loading=\"lazy\" id=\"10175\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image13.png?resize=632%2C340&#038;ssl=1\" alt=\"\" width=\"632\" height=\"340\" class=\"image-compare__image-before\" data-recalc-dims=\"1\" /><img loading=\"lazy\" id=\"10176\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image6.png?resize=632%2C340&#038;ssl=1\" alt=\"\" width=\"632\" height=\"340\" class=\"image-compare__image-after\" data-recalc-dims=\"1\" /></div></figure>\n\n\n\n<p>Creating designs with these assets enables rapid ideation on new interfaces by removing mundane processes that one would ordinarily have to work through. Nobody wants to repeatedly double-check that the button they made perfectly matches the buttons rendered by the code! And on the flip-side of that coin, anyone sharing a design with others will generally endeavor to make specific elements (like buttons) match what exists in the code as closely as possible. The WordPress Design Library solves both these headaches and more.</p>\n\n\n\n<p>An additional benefit to these assets visually matching what exists in the codebase is that any designs you create with them will inherently make use of the latest WordPress design language and consequently <em>feel</em> like WordPress with almost no effort required. Passing such designs on to developers makes them easier to interpret and implement too.</p>\n\n\n\n<h2><strong>Figma Fundamentals</strong></h2>\n\n\n\n<p>Before getting into the practical section of this post, let&#8217;s quickly cover some of the fundamental features of Figma libraries. This will help prepare us for working with the WordPress Design Library.</p>\n\n\n\n<h3><strong>Components</strong></h3>\n\n\n\n<p>As we touched on above, the library consists of &#8220;components&#8221; that serve as visual counterparts to their code-based equivalents. That is to say, there is a Button component in Figma, <em>and</em> a matching Button component in the WordPress codebase.</p>\n\n\n\n<p>But what <em>is</em> a Figma component?</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Components are elements you can reuse across your designs. They help to create and manage consistent designs across projects.</p><p></p><cite><a rel=\"nofollow\" href=\"https://help.figma.com/hc/en-us/articles/360038662654-Guide-to-Components-in-Figma\">help.figma.com</a></cite></blockquote>\n\n\n\n<p>Let&#8217;s quickly explore some of the properties of Figma components to understand the ways they help when working on our next design.</p>\n\n\n\n<h3><strong>Variants</strong></h3>\n\n\n\n<p>Some Figma components offer variants. One example is Button(s) which all have the following states:</p>\n\n\n\n<ul><li>Resting</li><li>Hover</li><li>Focus</li><li>Disabled</li></ul>\n\n\n\n<p>These can be manipulated via the variants interface in Figma:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"449\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image7-2.gif?resize=632%2C449&#038;ssl=1\" alt=\"\" class=\"wp-image-10179\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image7-2.gif?resize=1024%2C727&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/04/image7-2.gif?resize=300%2C213&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/04/image7-2.gif?resize=768%2C545&amp;ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>Other examples of components with variants are form inputs and menu items. Variants are a new feature in Figma, so we&#8217;ll be adding more over time.</p>\n\n\n\n<h3><strong>Overrides</strong></h3>\n\n\n\n<p>Although any components you insert are intrinsically linked to the master component in the library, it is possible to override some properties.</p>\n\n\n\n<p>While working with an instance of the Button component, you can change things like the label, or even the background color, while maintaining the link to the master component in the library. If you&#8217;re familiar with git workflows, this is kind of like creating a local branch. Any changes you make can easily be reset in a couple of clicks.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"527\" src=\"https://i0.wp.com/wordpress.org/news/files/2021/04/image10.gif?resize=632%2C527&#038;ssl=1\" alt=\"\" class=\"wp-image-10180\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2021/04/image10.gif?resize=1024%2C854&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/04/image10.gif?resize=300%2C250&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/04/image10.gif?resize=768%2C641&amp;ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>Overrides made to your local instance will persist even when the master component is updated. So if your design calls for a button with a green background, you can apply that override safely with the knowledge that even if the master component is updated, your button can inherit those updates and remain green.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p>We&#8217;ve only really scratched the surface of components here. So I would recommend the official <a rel=\"nofollow\" href=\"https://help.figma.com/hc/en-us/articles/360038662654-Guide-to-Components-in-Figma\">Figma documentation</a> for more advanced information.</p>\n\n\n\n<h3><strong>Figma Styles</strong></h3>\n\n\n\n<p>In addition to components, styles are also published as part of the WordPress Design Library. They have similar properties to components in that a master style exists in the library and can be utilized in your local Figma file. Just like Components, Styles will receive updates when changes to the library are published.</p>\n\n\n\n<p>Styles are used to define colors, typographical rules, and effects like drop-shadows present in the WordPress codebase. They enable you to apply things like text or background colors that will match other UI parts.</p>\n\n\n\n<p>Using Styles from the library, you ensure that your creations match existing UI elements, making it easier to implement.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"799\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image11.png?resize=632%2C799&#038;ssl=1\" alt=\"\" class=\"wp-image-10181\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image11.png?resize=810%2C1024&amp;ssl=1 810w, https://i1.wp.com/wordpress.org/news/files/2021/04/image11.png?resize=237%2C300&amp;ssl=1 237w, https://i1.wp.com/wordpress.org/news/files/2021/04/image11.png?resize=768%2C971&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/04/image11.png?w=1152&amp;ssl=1 1152w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p>To learn more about styles in Figma, I recommend the <a rel=\"nofollow\" href=\"https://help.figma.com/hc/en-us/articles/360039238753-Styles-in-Figma\">official documentation</a>.</p>\n\n\n\n<h3><strong>Views and Stickers</strong></h3>\n\n\n\n<p>&#8220;Stickers&#8221; are simply arrangements of Components and Styles that have been combined to represent common UI elements. They are not good candidates for full componentization due to their frequent customization needs. Examples of Stickers include the Inspector sidebar and the block inserter:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"770\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image16.png?resize=632%2C770&#038;ssl=1\" alt=\"\" class=\"wp-image-10182\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image16.png?resize=841%2C1024&amp;ssl=1 841w, https://i1.wp.com/wordpress.org/news/files/2021/04/image16.png?resize=246%2C300&amp;ssl=1 246w, https://i1.wp.com/wordpress.org/news/files/2021/04/image16.png?resize=768%2C935&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/04/image16.png?w=1113&amp;ssl=1 1113w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>Their utility is simple: find the sticker you need, peel (copy) it from the WordPress Design Library, and stick (paste) it into your local file before customizing as needed.</p>\n\n\n\n<p><em>Stickers</em> are not Figma features like Components and Styles, but any stickers you copy to a working file will stay up to date by virtue of their underlying assets.</p>\n\n\n\n<p><em>Views</em> are arrangements of components, styles, <em>and</em> stickers.</p>\n\n\n\n<h2><strong>Designing a Block Using the WordPress Design Library</strong></h2>\n\n\n\n<p>Okay, now that we have a handle on the basics of Figma libraries and their features and the utilities of the WordPress Design Library like Stickers and Views, let&#8217;s work through a practical example – designing the UI for a brand new block.</p>\n\n\n\n<h3><strong>Getting Started</strong></h3>\n\n\n\n<p>All you need to get started is a Figma account added to the WordPress.org Figma organization.</p>\n\n\n\n<p>Once you&#8217;ve signed up at<a href=\"https://www.figma.com/\"> Figma</a>, simply join the<a href=\"http://wordpress.slack.com/messages/design/\"> #Design</a> channel on the community Slack and request an invite. Include your Figma username, and a friendly community member will help get you set up in no time.</p>\n\n\n\n<p>Now the fun begins!</p>\n\n\n\n<p>To create a fresh new design file in Figma, visit the<a href=\"https://www.figma.com/files/project/1339415/Gutenberg?fuid=652576565531990233\"> Gutenberg project</a> and click the &#8220;+ New&#8221; button.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"395\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image15.png?resize=632%2C395&#038;ssl=1\" alt=\"\" class=\"wp-image-10183\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image15.png?resize=1024%2C640&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/04/image15.png?resize=300%2C187&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/04/image15.png?resize=768%2C480&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/04/image15.png?w=1469&amp;ssl=1 1469w, https://i2.wp.com/wordpress.org/news/files/2021/04/image15.png?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>Now let&#8217;s include the WordPress Design Library in our working file so that we have access to all the goodies we&#8217;ll need:</p>\n\n\n\n<ol><li>Open the &#8220;Assets&#8221; panel and click the little book icon to view the available Team Libraries.</li><li>In the modal, toggle the WordPress Design Library on. You can leave the others off for now.</li></ol>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"341\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image18.gif?resize=632%2C341&#038;ssl=1\" alt=\"\" class=\"wp-image-10184\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image18.gif?resize=1024%2C553&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/04/image18.gif?resize=300%2C162&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/04/image18.gif?resize=768%2C415&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/04/image18.gif?resize=1536%2C829&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/04/image18.gif?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>After closing the modal, you&#8217;ll notice a number of components become visible in the assets panel. To insert them, they can be dragged on to the canvas:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"341\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image5.gif?resize=632%2C341&#038;ssl=1\" alt=\"\" class=\"wp-image-10185\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image5.gif?resize=1024%2C553&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/04/image5.gif?resize=300%2C162&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/04/image5.gif?resize=768%2C415&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/04/image5.gif?resize=1536%2C829&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/04/image5.gif?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>It&#8217;s kind of like inserting a block <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\n\n\n<h3><strong>Creating a Pizza Block <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f355.png\" alt=\"🍕\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></strong></h3>\n\n\n\n<p>I love to eat pizza, so for fun, I&#8217;m going to design a new block that simply allows the user to display a delicious pizza in their posts and pages. I want the block to include options for a total number of slices and different toppings.</p>\n\n\n\n<h3><strong>Work Out the Flow</strong></h3>\n\n\n\n<p>I always like to concentrate on individual flows when designing blocks. That is to say, the linear steps a user will take when working with that block. In this case, I want to create visualizations of the following steps/views in our Figma file:</p>\n\n\n\n<ol><li>Inserting the block from the Block Inserter</li><li>The Pizza Block placeholder state including options in the block, its Toolbar, and the Inspector</li><li>The configured Pizza Block settings</li><li>The end result – a delicious pizza sitting comfortably on the canvas</li></ol>\n\n\n\n<h3><strong>Sketch the New States</strong></h3>\n\n\n\n<p>Thanks to the WordPress Design Library, I&#8217;ll be using as many existing UI components as possible, but I still need a rough idea of how they will be composed in the new interfaces that my Pizza block will require. I normally find it helpful to sketch these out on paper.</p>\n\n\n\n<p>Here&#8217;s the placeholder state which users will see when they first insert the block. This should be all I need:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"843\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image2.png?resize=632%2C843&#038;ssl=1\" alt=\"\" class=\"wp-image-10186\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image2.png?w=768&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/04/image2.png?resize=225%2C300&amp;ssl=1 225w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h3><strong>Prepare the Views and Stickers</strong></h3>\n\n\n\n<p>Helpfully, there are Views in the WordPress Design Library I can use for each of the steps in the flow outlined above.</p>\n\n\n\n<p>I open the library, navigate to the Views page, find the views I need, copy them, and paste into my working file.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"374\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image3.gif?resize=632%2C374&#038;ssl=1\" alt=\"\" class=\"wp-image-10187\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image3.gif?resize=1024%2C606&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/04/image3.gif?resize=300%2C178&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/04/image3.gif?resize=768%2C455&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/04/image3.gif?resize=1536%2C910&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/04/image3.gif?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>It is very important to <strong>copy</strong> (not cut) Views from the library so that they remain intact and other people can still access them. If you cut them, they&#8217;ll be gone forever, so please don&#8217;t do that <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\n\n\n<p>I&#8217;m also going to need a block placeholder sticker, so I navigate to the Stickers page, copy the one that most closely resembles my sketch from before, and paste it into my working file.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"374\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image12.gif?resize=632%2C374&#038;ssl=1\" alt=\"\" class=\"wp-image-10188\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image12.gif?resize=1024%2C606&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/04/image12.gif?resize=300%2C178&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/04/image12.gif?resize=768%2C455&amp;ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>As with views, please only <strong>copy</strong> stickers; do not cut them.</p>\n\n\n\n<h3><strong>Gather the Components</strong></h3>\n\n\n\n<p>Referring back to the placeholder state I sketched out on paper (it can be helpful to import this into your Figma file), I can see that I&#8217;m going to need some form elements to realize the design.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"446\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?resize=632%2C446&#038;ssl=1\" alt=\"\" class=\"wp-image-10189\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?resize=1024%2C722&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?resize=300%2C211&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?resize=768%2C541&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?resize=1536%2C1083&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?w=1999&amp;ssl=1 1999w, https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?w=1264&amp;ssl=1 1264w, https://i2.wp.com/wordpress.org/news/files/2021/04/image4.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>I navigate to the Assets panel, locate the components I need, and drag them into my file:</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh5.googleusercontent.com/UDyZdtZGo9N0e2qwgyIyz8V3xu9_zwGW9qBbBnozvwmXmVYURZ-ROLANtW7FafWYbQRnPQNWeRupk_9_1nzmKn8gRBlYDMKYR3QpwAubv8ZKAPMS_uV9VaYHsjfPItfqPiY0d1X5\" alt=\"\" /></figure>\n\n\n\n<p>Helpful tip: Once a component has been inserted, you can transform it into another component via its settings panel. Sometimes it is easier to copy/paste a component you already inserted and transform it this way, rather than opening the assets panel over and over.</p>\n\n\n\n<h3><strong>Arrange the Views, Stickers, and Components to Create a Coherent Design</strong></h3>\n\n\n\n<p>Now that we’ve gathered all the individual pieces we need, it&#8217;s simply a case of arranging them so that they resemble each of the steps of the flow we outlined before. This is done with simple drag and drop.</p>\n\n\n\n<p>If you&#8217;re familiar with software like Photoshop, Sketch, and others, this should feel very familiar.</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh3.googleusercontent.com/DVeU3I9ajqRvMD_e5q6G5vctb4TGbgA9CsIR9xYZ3yPqtmPhbDP9cODTHH4KS-I8GB9R4UF2DV6SSsayKpy45AEDvvY2gLbMsCA0ivfsqGcm509OWeTOpaMuQcv7TFz6-xoiKFfo\" alt=\"\" /></figure>\n\n\n\n<p>Once everything is in place, our flow is complete:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"97\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?resize=632%2C97&#038;ssl=1\" alt=\"\" class=\"wp-image-10238\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?resize=1024%2C157&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?resize=300%2C46&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?resize=768%2C118&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?resize=1536%2C235&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?w=1999&amp;ssl=1 1999w, https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?w=1264&amp;ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2021/04/image14-1.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure>\n\n\n\n<p>I still find it incredible that we&#8217;re able to do this in just a few short moments.</p>\n\n\n\n<h3><strong>Hook up the Prototype</strong></h3>\n\n\n\n<p>With each step of our flow created, the last piece of the puzzle is to connect them and form a clickable prototype.</p>\n\n\n\n<p>I switch to the Prototype panel and create click behaviors by selecting a layer, then dragging the white dot to the corresponding frame.</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh5.googleusercontent.com/i0fLdjWZhRTNFCKvHLLEfUnFx5CIm7p014R1avEV02F_B4DrG1v6Cw-XqYBth9JVYylylM7_mkqcALWEWcUVf0dRhgixJRtmsRIDHyMIZyom2cPdetMAFixgsvsmrqT03Xevync7\" alt=\"\" /></figure>\n\n\n\n<p>There are a variety of behaviors that the Figma prototyping tools support, such as a hover, drag, and click. It is even possible to create smart animations. Perhaps that&#8217;s something we can explore in another tutorial, but for now, I will refer you to the <a rel=\"nofollow\" href=\"https://help.figma.com/hc/en-us/articles/360040314193-Guide-to-prototyping-in-Figma\">Figma documentation</a> for more advanced prototyping.</p>\n\n\n\n<p>Now that I&#8217;ve connected all the appropriate elements, I am able to take my prototype for a test drive by clicking the Play <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/25b6.png\" alt=\"▶\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /> icon:</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh3.googleusercontent.com/nBmEr4ohZ8RsjLM5wm4u8UY_zzTE0V1bXj-uoNV79WDibl5bgkZXY64ixl_BgNutg74fvxRZokUtLzWuWVlD46W4tAD_-Dcf-TclgIR9UoO73oCmNxmfcSEmUDgDG0e5WYFJ80tH\" alt=\"\" /></figure>\n\n\n\n<p>You can try it too; just click <a href=\"https://www.figma.com/proto/BmRYWzfrakFwsmIQa24xqx/Pizza-Block?page-id=0%3A1&amp;node-id=48%3A767&amp;viewport=1792%2C385%2C0.46477335691452026&amp;scaling=min-zoom\">here</a>.</p>\n\n\n\n<h2><strong>That&#8217;s All, Folks!</strong></h2>\n\n\n\n<p>I tried to keep this tutorial fairly simple and concise; even though we only really got to grips with the basics here, you can see the power of Figma and the WordPress Design Library when it comes to trying out new designs.</p>\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:\"10173\";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:32:\"Curious About 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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2021/04/curious-about-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 27 Apr 2021 17:26: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:2:{i:0;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:1;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=10190\";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:296:\"The second major release of the year is right around the corner. You might have heard a bit of buzz about full site editing around your WordPress circles, so this post will give you some big picture things to know as well as a few wayfinding links for anyone who wants to know more. For [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2792:\"\n<p>The second major release of the year is right around the corner. You might have heard a <a href=\"https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/\">bit of buzz</a> about full site editing around your WordPress circles, so this post will give you some big picture things to know as well as a few wayfinding links for anyone who wants to know more.</p>\n\n\n\n<p><strong>For Site Owners and Operators</strong></p>\n\n\n\n<p>If you own and operate a WordPress site, updating to version 5.8 should be a seamless experience, just like any other update. All the conversation around full site editing is very exciting, but shouldn’t be alarming—<strong>everything in the next release that relates to full site editing is opt-in</strong>. To experiment freely with it, you need a theme that is built for it. Check the links at the end to see a few examples!</p>\n\n\n\n<p><strong>For Agencies and Theme/Plugin Developers</strong></p>\n\n\n\n<p>If you extend the functionality of the WordPress CMS for clients, updating to version 5.8 should also be seamless. As always, it’s smart to spot-check custom implementations in a staging environment or fully test when the release candidate is made available. Want to test your products and get everything client-ready? Check out any of the testing options below.</p>\n\n\n\n<p><strong>For Contributors and Volunteers</strong></p>\n\n\n\n<p>If you contribute time and expertise to the WordPress project, you can join us in the interesting work leading up to the WordPress 5.8 release and update your site with the deep satisfaction of a job well done. There is a lot that goes into every release—from design and development to documentation and translation; if you’ve got some time to spare, and want to help support the project that supports the tool that supports your site (whew!), check out the links below.</p>\n\n\n\n<h2>Resources</h2>\n\n\n\n<ul><li>A few block themes: <a href=\"https://wordpress.org/themes/tt1-blocks/\">TT1 Blocks</a>, <a href=\"https://wordpress.org/themes/hansen/\">Hansen</a>, <a href=\"https://wordpress.org/themes/block-based-bosco/\">Block-based Bosco</a>, <a href=\"https://wordpress.org/themes/q/\">Q</a></li><li>A few focus areas: <a href=\"https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/\">Gutenberg plugin focuses</a></li><li>A few ways you can test: <a href=\"https://wordpress.org/plugins/gutenberg/\">Gutenberg plugin</a>, <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">Beta testing plugin</a>, <a href=\"https://gutenbergtimes.com/need-a-zip-from-master/#nightly\">Gutenberg Times nightly build</a></li><li>A few pieces of documentation: <a href=\"https://developer.wordpress.org/block-editor/handbook/full-site-editing/\">Full Site Editing Overview</a></li></ul>\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:\"10190\";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:58:\"\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:44:\"WP Briefing: Your Opinion is Our Opportunity\";s:7:\"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/2021/04/your-opinion-is-our-opportunity/\";s: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, 26 Apr 2021 15:24: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:8:\"category\";a:1:{i:0;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=10171\";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:148:\"In this episode, Josepha discusses the importance of co-development and testing for the continued growth and maintenance of the WordPress project. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/04/WP-Briefing-007.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:13068:\"\n<p>In this episode, Josepha discusses the importance of co-development and testing for the continued growth and maintenance of the WordPress project.&nbsp;</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href=\"mailto:wpbriefing@wordpress.org\">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2><strong>Credits</strong></h2>\n\n\n\n<ul><li>Editor:<a href=\"https://profiles.wordpress.org/dustinhartzler/\"> Dustin Hartzler</a></li><li>Logo:<a href=\"https://profiles.wordpress.org/beafialho/\"> Beatriz Fialho</a></li><li>Production:<a href=\"https://profiles.wordpress.org/mkaz/\"> </a><a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>\n\n\n\n<h2>References</h2>\n\n\n\n<ul><li><a href=\"https://wordpress.org/news/2008/10/usability-testing-report-25-and-crazyhorse/\">2.5 Usability Testing Report&nbsp;</a></li><li><a href=\"https://europe.wordcamp.org/2021/\">WordCamp Europe 2021</a></li><li><a href=\"https://www.meetup.com/Pune-WordPress-Knowledge-Exchange/events/277520243/\">Pune Work Along (Self Study) Meetup</a></li><li><a href=\"https://fr.wordpress.org/2021/04/09/le-30-avril-2021-rejoignez-nous-pour-un-nouveau-wordpress-translation-day-fr/\">French Mini-Translation Day, April 30, 2021</a></li><li><a href=\"https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/\">April 14, 2021, Full Site Editing Go/No-Go Demo Recap</a></li><li><a href=\"https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/\">Full Site Editing Go/No-Go Next Steps</a></li><li><a href=\"https://make.wordpress.org/test/\">Test WordPress.org</a></li></ul>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id=\"more-10171\"></span>\n\n\n\n<p>0:10</p>\n\n\n\n<p>Hello, 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&#8217;m your host, Josepha Haden Chomphosy. Here we go!</p>\n\n\n\n<p>0:39</p>\n\n\n\n<p>Prior to Gutenberg, our current multi-year project that is changing the way we see WordPress, another multi-year project changed the way we saw WordPress. Starting in 2008, substantial changes to the WordPress interface came in a series of major releases, starting with WordPress 2.5. That was before my time in the project; I&#8217;ve only ever worked with the current dashboard in WordPress. But, from what I&#8217;ve read, the user testing that would have gone into it was a huge undertaking and very well coordinated. Now, WordPress has not taken on that type of robust testing project since, but starting around 2014 or 2015, a community testing practice was started. I&#8217;ve shared these calls for testing frequently, both on Twitter and in this podcast. But you may not really know why I find the testing program so valuable. So today, I&#8217;m going to explore with you the concept of co-developers in open source.</p>\n\n\n\n<p>1:52</p>\n\n\n\n<p>Open source software, like WordPress, is built by the people who show up. There are a few obvious groups when you think of software, the developers, designers, technical writers, folks who monitor the forums, and really, all the teams you find in our WordPress project. Co-developers or co-creators, if you&#8217;ll join me in making our tent a little bigger, refers to the users of an open source product who actively engage and contribute to the work by using the software and sharing any bugs that they find.</p>\n\n\n\n<p>2:25</p>\n\n\n\n<p>I mentioned this group in the episode about how WordPress improves. Specifically in that episode, I underlined that if you consider users to be part of the collaborative process, as long as people use your product, those people will have opinions about your product’s needs. And today, I&#8217;m extending that thought a bit further to say that, as long as there are opinions, there are opportunities.</p>\n\n\n\n<p>2:51</p>\n\n\n\n<p>When you know what isn&#8217;t working, you can focus your attention on a solution, you can focus on making sure that you can make it work. The existence of co-creators is one of the great things about open source. No designer or developer or product owner has to know every sort of user to be able to get feedback from them. If they show up, test the software and get their thoughts written down, then you can start to see patterns and common pain points. It is also, unfortunately, one of the great difficulties of being an open source project. After all, if users don&#8217;t show up, or don&#8217;t test, or don&#8217;t write down their feedback, it&#8217;s impossible to know what worked for them and what didn&#8217;t. And on top of that, with such a large percentage of the web being supported by WordPress in this case, not every problem is part of a pattern. And not all patterns are part of the current priorities.</p>\n\n\n\n<p>3:54</p>\n\n\n\n<p>Looking beyond that double-edged sword. Let&#8217;s say that this idea of a co-creator makes sense to you. And more than that, you feel like it describes you. What does it mean for you to show up in WordPress? There are lots of good ways to offer this sort of feedback and contribute to those patterns that can help us see through the fog. So I have for you a mini list and, of course, a bunch of links in the show notes for you.&nbsp;</p>\n\n\n\n<p>So some good ways. First, you can participate in any of the dedicated calls for testing. They are short and frequently have a guide. I participate in them and generally find them fun. I say generally because sometimes I also find them frustrating. That&#8217;s really okay too; the frustrations helped me to identify that I found a problem. And if I can find a problem, then I have saved someone else from finding that problem in the future. The second thing you can do is file a bug report with information about what happened when you ran into a problem and how someone like me could make your bug happen on their site. Bug</p>\n\n\n\n<p>5:00</p>\n\n\n\n<p>Reporting is one of the things I&#8217;ve grown to really love in my time and open source; I did not love it. At first, I was really scared to do it. I mostly used to send videos of the bugs that I found to other people and ask them to file the bug reports for me. But then, of course, I never knew whether they got fixed or not. So I was scared to do it at first. But once I figured out what makes a “good report,” I felt like I was helping circle hidden treasure on a map or something. I realized also not everyone&#8217;s excited about finding hidden treasure on a map. But I play video games and finding hidden treasure on maps is, like, a thing.</p>\n\n\n\n<p>5:43</p>\n\n\n\n<p>A third really great way to contribute like this is that you can join any community meeting to learn more about what&#8217;s happening now and in the future, or just to see what makes WordPress work. As a heads up, these meetings go really fast. And they&#8217;re all in text. And there&#8217;s sometimes, but not all the time, a little bit of jargon that you have to head to your favorite search engine to find. But I sit in on about half of them myself and get a lot of really good information about things that I&#8217;ve been wondering about, things that looked broken, but actually are functioning exactly the way that they should. And I just didn&#8217;t want them to function that way. And more often than not, I found out that something that I thought was broken, was already identified and being fixed. Those are three great ways to show up and help give feedback that helps make WordPress better and more functional for more people.&nbsp;</p>\n\n\n\n<p>There are also a few other ways that we see people trying to share that feedback that don&#8217;t work quite as well. And I&#8217;m going to touch on a few of them just because it&#8217;s important to know, as you&#8217;re trying to figure out how to get started with this. The first one is just tweeting your frustrations, and I get it like that&#8217;s literally what Twitter is for.</p>\n\n\n\n<p>7:03</p>\n\n\n\n<p>But also it&#8217;s hard to create a block from “I am frustrated, behold my hateful rhetoric.” Not that any of you, my dear listeners, ever tweet hateful rhetoric. Still, that is really hard for anyone to figure out what was actually wrong in that moment. Another thing that is not the most functional way to give feedback is review brigading. The Internet rewards this kind of behavior, but I have found at least for WordPress, those false positives and false negatives can be really confusing for our new users. And the third way, that&#8217;s not our best way, and probably is the least best way, is just by giving up and not telling anyone what broke for you.</p>\n\n\n\n<p>7:45</p>\n\n\n\n<p>I know that I already said it&#8217;s not possible to fix everyone&#8217;s problems. But while it&#8217;s not possible to fix everyone&#8217;s problems the moment they get shared, it&#8217;s also truly impossible to fix any problems that no one knows exist. And so giving up and not sharing an issue so that we can identify it as part of a pattern of problems is probably the least effective way to help us help you get your problem solved.</p>\n\n\n\n<p>8:13</p>\n\n\n\n<p>This brings me back to the question of the value of WordPress users as co creators in the development process. As WordPress grows, both in usage as a CMS and in participation as a community, it&#8217;s important for us to shed the idea that software creation is only about what literally can be done to code or what literally can be done to core or what literally can be done to the CMS. It&#8217;s also important for us to constantly remind ourselves that the best outcomes are the result of collaboration with the people who use WordPress the most. I know that not every type of user we have is showing up to give us feedback about where WordPress doesn&#8217;t work for them. And I would love to see more feedback that helps us to figure out where our patterns are.</p>\n\n\n\n<p>9:03</p>\n\n\n\n<p>So the bottom line is this without user feedback that has some clarity of what was expected versus what happened, the work to make a good choice involves a whole lot of guessing. So since open source software is built by the people who show up, I hope this gives you an idea of how you can show up and help improve the tool that powers your sites.</p>\n\n\n\n<p>9:32</p>\n\n\n\n<p>That brings us to today&#8217;s community highlight every episode or so I share either a great story of WordPress success or a great story of a WordPress contributor who helped some folks along the way. Today&#8217;s <a href=\"https://twitter.com/trishacodes/status/1357382647274762244\">community highlight</a> comes from @trishacodes who shared one of her early to WordPress mentors. She says “@RianRietveld was such an encouragement and helped me find the courage to speak up.” I have had myself many conversations with <a href=\"https://profiles.wordpress.org/rianrietveld/\">Rian</a>, and that rings true for me as well.&nbsp;</p>\n\n\n\n<p>10:00</p>\n\n\n\n<p>That brings us to the moment you&#8217;ve all been waiting for, the small list of big things. It&#8217;s actually kind of a medium list. Today, I&#8217;ve got four whole things to share with you all. The first thing on my list is that WordCamp Europe is coming, that will be June 7th through the 10th. It&#8217;s a multi-day online event. I will share in the show notes a link to the main website; there you can get an idea of what will happen, the schedule, and get your hands on some tickets so that you can get it in your calendar and prepare yourselves.&nbsp;</p>\n\n\n\n<p>The second thing I want to share is for all of our polyglots out there. The French team is planning a translation day coming up on April 30. I will share a link to that as well so that you can get an idea of what that takes if you&#8217;re feeling like you want to do some translation work. The third thing I want to share is that the Indian community in Pune actually started a new meetup series. It is a translation work along self-study &#8211; also for all of our polyglots out there. I would love to see as many people as are interested in both learning about how to do translations and certainly translating WordPress get registered for that. A final thing I want to share with you all is that if you are curious about what full site editing features will be included in the 5.8 release, that&#8217;s the WordPress release that&#8217;s coming out in the middle of July, you can check out my recap and recording of the demo that was held with Matt, Matias, and the rest of the team. There’s are also a number of other posts of next step ideas that I will share in the show notes as well.</p>\n\n\n\n<p>11:51</p>\n\n\n\n<p>That, my friends, is your small list of big things. Thank you for joining in today for the WordPress briefing. I&#8217;m your host, Josepha Haden Chomphosy. I&#8217;ll see you again in a couple of weeks!</p>\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:\"10171\";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: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:49:\"Become an Early Adopter With 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://wordpress.org/news/2021/04/become-an-early-adopter-with-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:\"Wed, 21 Apr 2021 21:03: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:13:\"Uncategorized\";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:9:\"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:35:\"https://wordpress.org/news/?p=10164\";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:372:\"Copy by Anne McCarthy (@annezazu) and Design by Mel Choyce-Dwan (@melchoyce) In WordPress circles (whether it’s your local meetup, a trusted publication, or your networking group), you may have heard terms like Core Editor, Gutenberg, and the Block Editor used interchangeably over the last four years. And if you’re following contributor work on the project [&#8230;]\";s: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:\"\";}}}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:4695:\"\n<p><strong><em>Copy by Anne McCarthy (<a href=\'https://profiles.wordpress.org/annezazu/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>annezazu</a>) and Design by Mel Choyce-Dwan (<a href=\'https://profiles.wordpress.org/melchoyce/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>melchoyce</a>)</em></strong></p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large is-resized\"><img loading=\"lazy\" src=\"https://i2.wp.com/wordpress.org/news/files/2021/04/Frame-1.png?resize=632%2C354&#038;ssl=1\" alt=\"\" class=\"wp-image-10165\" width=\"632\" height=\"354\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2021/04/Frame-1.png?resize=1024%2C575&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2021/04/Frame-1.png?resize=300%2C169&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2021/04/Frame-1.png?resize=768%2C431&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2021/04/Frame-1.png?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure></div>\n\n\n\n<p>In WordPress circles (whether it’s your local meetup, a trusted publication, or your networking group), you may have heard terms like Core Editor, Gutenberg, and the Block Editor used interchangeably over the last four years. And if you’re following contributor work on the project itself, you may also have heard some additional nuances—Gutenberg plugin, Gutenberg, or Block Editor.&nbsp;</p>\n\n\n\n<p>It can get a little confusing, so let’s take a look at four terms that will help you find your way:&nbsp;</p>\n\n\n\n<ul><li>WordPress &#8211; WordPress refers to the open source software but also to the community that surrounds it.&nbsp;</li><li>Gutenberg &#8211; Gutenberg is the code name for a multi-year project to update editing areas for the WordPress software.</li><li>Editor &#8211; The editor refers to a section of the software that allows you to update content on your site’s posts and pages.&nbsp;</li><li>Gutenberg Plugin &#8211; The Gutenberg plugin is where early work to update the editor is shared.</li></ul>\n\n\n\n<h2>The Gutenberg Plugin</h2>\n\n\n\n<p>Now that we’ve cleared up the definitions, let’s talk about the plugin. When might you use it? What would you use it for? You can think of it as an early access program or a “WordPress lab.” The plugin is updated every two weeks, which means that bugs that have been reported are often fixed and that what you see changes rapidly.&nbsp;</p>\n\n\n\n<p>The Gutenberg plugin also contains features that aren’t yet ready for their WordPress debut but are ready for curious users to test and provide feedback. This is a common practice that allows stable features to make it to your site in WordPress releases while allowing experimental features to be tested and refined. To get a sense of whether using the Gutenberg Plugin might be something you want to explore to get access to earlier features, check out the <a href=\"https://make.wordpress.org/core/tag/gutenberg-new/\">“What’s New” release posts </a>and the <a href=\"https://make.wordpress.org/core/tag/core-editor-improvement/\">Core Editor Improvement post series</a>. </p>\n\n\n\n<h2>Do I Need the Plugin to Use Gutenberg?</h2>\n\n\n\n<p>It depends on your comfort level! Generally speaking, it is not recommended to use the plugin on a site that has launched and is actively in use unless you’re very comfortable with the code side of WordPress. Fortunately, each WordPress release comes ready to go with <a href=\"https://developer.wordpress.org/block-editor/handbook/versions-in-wordpress/\">multiple versions of the Gutenberg plugin</a>.&nbsp;</p>\n\n\n\n<p>But if you are a keen beta tester who loves reporting feedback, or you feel comfortable navigating how to opt-in/out of the experimental aspects of the plugin, here are a few reasons you might want to dig into what the Gutenberg Plugin has to offer:</p>\n\n\n\n<ul><li>Test new features and give helpful feedback. For example, you can use the plugin to <a href=\"https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/how-to-test-fse/\">help test Full Site Editing</a>.&nbsp;</li><li>Get early access to the latest &amp; greatest while navigating when to opt-in or out of experimental features.&nbsp;</li><li>Prepare for the future whether you’re a theme author, plugin developer, agency owner, etc.&nbsp;</li></ul>\n\n\n\n<p><em>Do you use the Gutenberg plugin and </em><a href=\"https://github.com/WordPress/gutenberg/issues\"><em>share feedback on GitHub</em></a><em>? Thank you! This kind of feedback is what helps ensure stability in what’s shipped in WordPress releases.&nbsp;</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p></p>\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:\"10164\";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: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:48:\"WordPress 5.7.1 Security and 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:84:\"https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-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:\"Thu, 15 Apr 2021 03:05:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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:8:\"Security\";s:7:\"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=10144\";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:365:\"WordPress 5.7.1 is now available! This security and maintenance release features 26 bug fixes in addition to two security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 4.7 have also been updated. WordPress 5.7.1 is a short-cycle security and maintenance release. The next [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Peter Wilson\";s: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:8461:\"\n<p>WordPress 5.7.1 is now available!</p>\n\n\n\n<p>This security and maintenance release features <a href=\"https://core.trac.wordpress.org/query?milestone=5.7.1&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">26 bug fixes</a> in addition to two security fixes. Because this is a <strong>security release</strong>, it is recommended that you update your sites immediately. All versions since WordPress 4.7 have also been updated.</p>\n\n\n\n<p>WordPress 5.7.1 is a short-cycle security and maintenance release. The next major release will be version 5.8.</p>\n\n\n\n<p>You can download WordPress 5.7.1 by downloading from WordPress.org, or visit your Dashboard → Updates and click Update Now.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h3>Security Updates</h3>\n\n\n\n<p>Two security issues affect WordPress versions between 4.7 and 5.7. If you haven’t yet updated to 5.7, all WordPress versions since 4.7 have also been updated to fix the following security issues:</p>\n\n\n\n<ul><li>Thank you <a href=\"https://www.sonarsource.com/\">SonarSource</a> for reporting an XXE vulnerability within the media library affecting PHP 8.</li><li>Thanks <a href=\"https://mikaelkorpela.fi/\">Mikael Korpela</a> for reporting a data exposure vulnerability within the REST API.</li></ul>\n\n\n\n<p>Thank you to all of the reporters for <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">privately disclosing the vulnerabilities</a>. This gave the security team time to fix the vulnerabilities before WordPress sites could be attacked.</p>\n\n\n\n<p>Props to <a href=\"https://profiles.wordpress.org/zieladam/\">Adam Zielinski</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/ehtis/\">Ehtisham Siddiqui</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a> and the WordPress security team for their work on these issues.</p>\n\n\n\n<p>For more information, browse the <a href=\"https://core.trac.wordpress.org/query?milestone=5.7.1&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">full list of changes</a> on Trac, or check out the <a href=\"https://wordpress.org/support/wordpress-version/version-5-7-1/\">version 5.7.1 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks and props!</h2>\n\n\n\n<p>The 5.7.1 release was led by <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">@peterwilsoncc</a> and <a href=\"https://profiles.wordpress.org/audrasjb/\">@audrasjb</a>.</p>\n\n\n\n<p>In addition to the security researchers and release squad members mentioned above, thank you to everyone who helped make WordPress 5.7.1 happen:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/ninetyninew/\">99w</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/annalamprou/\">annalamprou</a>, <a href=\"https://profiles.wordpress.org/anotherdave/\">anotherdave</a>, <a href=\"https://profiles.wordpress.org/aristath/\">Ari Stathopoulos</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/bobbingwide/\">bobbingwide</a>, <a href=\"https://profiles.wordpress.org/brechtvds/\">Brecht</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">David Baumwald</a>, <a href=\"https://profiles.wordpress.org/dkoo/\">dkoo</a>, <a href=\"https://profiles.wordpress.org/ocean90/\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/dragongate/\">dragongate</a>, <a href=\"https://profiles.wordpress.org/eatsleepcode/\">eatsleepcode</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/kebbet/\">Erik</a>, <a href=\"https://profiles.wordpress.org/fabianpimminger/\">Fabian Pimminger</a>, <a href=\"https://profiles.wordpress.org/flixos90/\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/mista-flo/\">Florian TIAR</a>, <a href=\"https://profiles.wordpress.org/gab81/\">gab81</a>, <a href=\"https://profiles.wordpress.org/galbaras/\">Gal Baras</a>, <a href=\"https://profiles.wordpress.org/geoffrey1963/\">Geoffrey</a>, <a href=\"https://profiles.wordpress.org/mamaduka/\">George Mamadashvili</a>, <a href=\"https://profiles.wordpress.org/glendaviesnz/\">Glen Davies</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Greg Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/grzim/\">grzim</a>, <a href=\"https://profiles.wordpress.org/ipstenu/\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/jaymanpandya/\">Jayman Pandya</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/joen/\">Joen A.</a>, <a href=\"https://profiles.wordpress.org/jonkastonka/\">Johan Jonk Stenström</a>, <a href=\"https://profiles.wordpress.org/goaroundagain/\">Johannes Kinast</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/joseeyoast/\">Josee Wouters</a>, <a href=\"https://profiles.wordpress.org/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/k3nsai/\">k3nsai</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/gwwar/\">Kerry Liu</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/mihdan/\">Mikhail Kobzarev</a>, <a href=\"https://profiles.wordpress.org/mmuyskens/\">mmuyskens</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/nicegamer7/\">nicegamer7</a>, <a href=\"https://profiles.wordpress.org/otshelnik-fm/\">Otshelnik-Fm</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/palmiak/\">palmiak</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/pwallner/\">pwallner</a>, <a href=\"https://profiles.wordpress.org/rachelbaker/\">Rachel Baker</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/rinatkhaziev/\">Rinat Khaziev</a>, <a href=\"https://profiles.wordpress.org/noisysocks/\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/rogertheriault/\">Roger Theriault</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/yakimun/\">Sergey Yakimov</a>, <a href=\"https://profiles.wordpress.org/sirstuey/\">SirStuey</a>, <a href=\"https://profiles.wordpress.org/stefanjoebstl/\">stefanjoebstl</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\">Stephen Bernhardt</a>, <a href=\"https://profiles.wordpress.org/sumitsingh/\">Sumit Singh</a>, <a href=\"https://profiles.wordpress.org/cybr/\">Sybre Waaijer</a>, <a href=\"https://profiles.wordpress.org/synchro/\">Synchro</a>, <a href=\"https://profiles.wordpress.org/terriann/\">Terri Ann</a>, <a href=\"https://profiles.wordpress.org/tigertech/\">tigertech</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/tobiasbg/\">TobiasBg</a>, <a href=\"https://profiles.wordpress.org/hellofromtonya/\">Tonya Mork</a>, <a href=\"https://profiles.wordpress.org/toru/\">Toru Miki</a>, <a href=\"https://profiles.wordpress.org/grapplerulrich/\">Ulrich</a>, and <a href=\"https://profiles.wordpress.org/vladytimy/\">Vlad T</a>.</p>\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:\"10144\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n	hourly	\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n	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:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"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:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Thu, 13 May 2021 10:14:43 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Thu, 13 May 2021 01:04:30 GMT\";s:4:\"link\";s:63:\"<https://wordpress.org/news/wp-json/>; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20201104100447\";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(22057, '_site_transient_update_core', 'O:8:\"stdClass\":4:{s:7:\"updates\";a:3:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:7:\"upgrade\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.7.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.7.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.7.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.7.2-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"5.7.2\";s:7:\"version\";s:5:\"5.7.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.6\";s:15:\"partial_version\";s:0:\"\";}i:1;O:8:\"stdClass\":11:{s:8:\"response\";s:10:\"autoupdate\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.7.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.7.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.7.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.7.2-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"5.7.2\";s:7:\"version\";s:5:\"5.7.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.6\";s:15:\"partial_version\";s:0:\"\";s:9:\"new_files\";s:1:\"1\";}i:2;O:8:\"stdClass\":11:{s:8:\"response\";s:10:\"autoupdate\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.6.4.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.6.4.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.6.4-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.6.4-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"5.6.4\";s:7:\"version\";s:5:\"5.6.4\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.6\";s:15:\"partial_version\";s:0:\"\";s:9:\"new_files\";s:1:\"1\";}}s:12:\"last_checked\";i:1620909044;s:15:\"version_checked\";s:5:\"5.5.5\";s:12:\"translations\";a:0:{}}', 'no');

-- --------------------------------------------------------

--
