In this episode, Josepha is joined by Matías Ventura, also known as “the spark behind the vision of Gutenberg.” Josepha and Matías discuss full site editing and answer your questions, from “is full site editing a standalone plugin?” to “will full site editing break my current site?”
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Twenty Twenty One theme
- Word Camp Central America
- 2Q21 Listening Hours with Matt Mullenweg and Josepha Haden Chomphosy
Transcript
\n\n\n\n\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha [0:41]: This month, we have a bonus briefing, so I’ve asked my dear friend and colleague Matías Ventura to join me. Matías was recently called “the spark behind the vision of Gutenberg.” With full site editing coming our way in 202, I asked if he would join me for a quick Q&A. Welcome, Matías.
\n\n\n\nMatías [0:56]: Hello, hello! Thanks for inviting me. It’s a pleasure to be here.
\n\n\n\nJosepha [1:00]: Well, I’m delighted to have you. And I think that we have a lot of excellent questions. All right, so Matías, we actually ended up with questions in about three different groupings. And so I’m going to start with the “what is it about full site editing,” sorts of questions that people had. We’re gonna work our way into “what are we doing with it?” and then “how are we planning on getting this out the door?” Then, a couple of big picture questions that people asked. We’re just gonna leap right in this full site editing part of the Gutenberg plugin, or is it a standalone plugin?
\n\n\n\nMatías [1:39]: Okay, we’ll start with the basics. Full site editing is part of the Gutenberg plugin right now. I think it’s important to mention that full site editing is like an umbrella for several projects that we’re working on. They are all aiming to bring blocks into more parts of your site so that editing becomes easier and more expressive, and so on. So full site editing right now encompasses adding a ton of new blocks. I think we have around 20 new blocks coming in, including navigation query, site, title, logo, etc. There’s also the interface to interact with templates outside of the content; that’s another big part of the full site editing project. We also have a lot of new design tools included, many of these have been released in previous major releases, but they still comprise a strong part of what full site editing is. We also have something called Global Styles, which aims to allow people to configure the visual aspects of blogs across the entire site, not just on any individual blog. And of course, then there’s a whole layer of how we utilize these tools. It can get complex because there are many layers and projects that need to come together. So yeah, all of these are accessible through the Gutenberg plugin right now.
\n\n\n\nJosepha [3:07]: Yeah. So it’s not a standalone plugin. If you wanted to check out full site editing the site editor experience as it is now, you would just have to make sure you had the Gutenberg plugin on your site. Right?
\n\n\n\nMatías: Yes, correct.
\n\n\n\nJosepha: So a couple of the questions related to this are how exactly do I enable it on my site? And what is the easiest and safest way to try this on my site? And I think the answer is, is right in there. It’s in the Gutenberg plugin. And so if you have that plugin, you don’t need the testing plugin or anything else to make that work, right?
\n\n\n\nMatías [3:51]: No, you like, you might need to install a theme like Twenty Twenty One blocks that unlock some of these new interfaces that we just talked about. Like other of these pieces are available for anything. But some of these, like the interface to edit templates, right now only talk with things that know how to express their desire.
\n\n\n\nJosepha [4:14]: And I think we have less than 10 themes right now that do that, but I’ll leave some links to at least 2021 blocks in the show notes. And then, if there are another one or two themes that I can find, I can add those in there as well.
\n\n\n\nSo you have to have the Gutenberg plugin; you have to have a theme that works with that site editor kind of experience. And then you’re safe to try everything out. It shows up in your left toolbar just like any other thing, like if you were working with plugins, or if you were adding a post or anything else, right?
\n\n\n\nMatías [4:51]: Yes, correct. And so, some of these details are being worked on right now. Like how and where you access things, and so on. These things are subject to change, but right now, you have this site editor beta in the sidebar when both you have the plugin running and a theme that’s capable.
\n\n\n\nJosepha [5:10]: Yeah. Excellent note. If you are running this on a production website, I would recommend you not do that unless you are very, very good with WordPress. It’s a really safe and easy thing to test and try out. But because it is still in beta, I recommend always putting it on a test site. I have a couple of different test sites that I run on myself. Another question that I had was, “will full site editing slow down my site?” And I think we have some refreshed performance tests coming out about that. And maybe they’ll be out by the time we publish this podcast.
\n\n\n\nMatías [5:49]: Yeah, I mean, like the performance has been one of the major focuses for the whole project. In many cases, it should speed up things because we’re like, I think one of the big pieces that these projects bring into the picture, especially for themes, is that it allows only the necessary assets to be loaded on the front end. For example, if for a given page, there are, I don’t know, 10-15 blocks being used, you would only get the CSS and scrapes and so on related to those blocks. This can cut down on a lot a ton of CSS that themes used to end queue on a side, particularly if you were trying to customize many widgets and so on, like a lot of themes have the full styles or multiple widgets, even third party plugins, and so on. So one of the advantages of having this blog system is that we can know at the time of rendering what blogs are being used and only load those assets.
\n\n\n\nJosepha [6:50]: Excellent. Another big question that we have is, “does full site editing work with the classic editor? And does it work with other builders?” I think that’s a really big answer if you’re going to get super deep into it. But I think that the short answer is yes, it does. Is that fair?
\n\n\n\nMatías [7:08]: Yeah, I don’t think it touches a bit on that full site editing is not like a single thing. There are multiple projects around it. So again, like the template editor that only deals with blogs, it doesn’t have a lot to do with a classic editor. But the classic editor use for both doesn’t change anything at all; like the same way that when the block editor was introduced, it didn’t change how you could still write posts in the classic editor. You will still be able to do that.
\n\n\n\nJosepha [7:41]: And if you are brand new to WordPress person, or, I mean, I guess at this point, you don’t have to be super brand new. If you’re fairly new to WordPress person and have no idea what we’re talking about when we say the classic editor, you don’t really have to worry about it either. You don’t have to go and find out what that is; the block editor that you have right now works perfectly for what you’re trying to do. So if you don’t know what I mean when I say classic editor, don’t worry about chasing it down either.
\n\n\n\nI think that this last question we accidentally answered earlier, but I’m going to go ahead and ask it anyway since I received it. “I keep hearing that you can use the site editor with the 2021 theme. But I don’t seem to be able to. What am I missing?” I think the answer is that there’s the Twenty Twenty One theme shipped with the WordPress release 5.6. And then there is the Twenty Twenty One blocks theme; those are two different themes. The link to the Twenty Twenty One block theme is going to be in our show notes this time around. And so, if you have been trying to use the full site editor with Twenty Twenty One and not succeeding, try the link to the one below. And I bet that that will work for you.
\n\n\n\nMatías [8:50]: Yes, that’s correct.
\n\n\n\nJosepha [8:51]: All right, excellent. Well, that brings us kind of into our second set of questions, which is about how we are doing it. The first one that folks have is “will full site editing be on by default in the next release. In this context, the next release is WordPress 5.8. But I think it’s a safe question to ask if full site editing will be on by default in the release that it’s planned for.
\n\n\n\nMatías [9:15]: Yeah, and for this, I need to go back to the same principle of many projects because there are many pieces of full site editing, and we have been merging them in major releases, particularly like the blocks and the design tools. There are more coming in that we want to make accessible as soon as possible. The full experience that requires a theme to opt-in to templates using blogs won’t be by default; it requires a specific theme running. A lot of these details we’re still like determining exactly what projects are ready to be merged and so on. But yeah, if you have a theme right now that works the way you want, it doesn’t change anything there. If anything, it adds some more capabilities and more customization tools, and so on. And the theme can also regulate how much they want to incorporate.
\n\n\n\nJosepha [10:13]: Matías, you’ve mentioned a couple of times in this podcast so far like this is a really complex and really complicated part of this work. And just for anyone out there who’s either encountering Gutenberg or full site editing or this podcast for the first time, I think a tiny bit of context that’s worth having here is that Matías and I have been working on this together in various capacities for like, five years. And Matías has probably been working on this for practically a decade. So, when we say that this is a really complicated problem, and when we say that this is a complex set of issues that we’re working with like, it is all that we have been thinking about for I want to say at least the last three or four years, but certainly it’s all that we have been trying to untangle for quite a bit of time before that as well. So we don’t take it lightly when we’re like, “this is complicated;” we mean it. It’s really complicated. And we’re trying our hardest over here as WordPress.
\n\n\n\nThe next big question, since we’re all stuck in the “it’s very complicated,” part of things is the question, “will this update break my current site?” Like, if I have a site that is updated and ready, and it’s exactly as I wanted it to be, and it took me two years to get there will full site editing, whichever release it’s in. Currently, 5.8 is what we’re planning for. Will that break anything on my site as I know it right now?
\n\n\n\nMatías [11:44]: No, not at all. One of the major things that the WordPress team, the WordPress community, always cares so much about, never to break things. Many of these things are stepping stones that you can adopt, as we’ve talked about full site editing. But for example, we also have a few concurrent projects around the widget screen and the navigation screen that are meant to bring blocks into existing interfaces. So again, the theme doesn’t need to change, and a lot of care is being put into making this more like you’re unlocking new features, and nothing really breaks or falls apart.
\n\n\n\nJosepha [12:23]: This update, like all the other updates, should have minimal, minimal impact on what you have to actively fix on your site. Every once in a while, a bug is gonna get by. We can’t say that we’re 100% perfect with not breaking things. But also, we always and I and I know that we’re planning on this for our remaining releases for the rest of the year. At the very least, I can’t imagine we’d ever change it. But after every major release, we always make a plan to have a minor release within the next one or two weeks. Because we know that a broken thing on a site is really incredibly impactful, even if you’re only 1% of the sites that had that happen to it. And so I think that’s true in this case, too. And getting that feedback back from all of the people who are actually using WordPress is the thing that makes us be able to kind of move quickly when we do see those problems.
\n\n\n\nOne of the questions that we have been getting is, “can I see a live preview without saving the changes that I made?” When I got this question, I didn’t actually understand it. And so I went and looked at a site without the Gutenberg plugin on it, and then a site with the Gutenberg plugin on it. And of course, on sites without Gutenberg, without the block editor, without full site editing, when you are looking to preview, you have the option to open up your preview in a new window. And you don’t have that with Gutenberg because it’s supposed to be a true WYSIWYG editor. A true what you see is what you get, editor. I think that the answer to this is, yes, you can see a live preview without actually saving the changes on the front end of your site. But you don’t actually have to reload anything. You don’t have to open it up in a new window. You don’t have to, like, actively click “please show me a preview” because what you see in your editing screen should be what you see at the end of your app as an end-user.
\n\n\n\nMatías [14:28]: Yeah, that’s the sort of the main gist to it. Yes, the site editor is built so that it always reflects the front end as truly as possible, so that’s one layer. Also, the preview tools should allow you to see in different devices like mobile breakpoints, and I don’t know if they will have breakpoints and stuff like that. There are a lot of things in the current interface that is just not enabled. There are some challenges in the sidebar. Because the site editor is not just focused on a single post, it’s focused on the entire site. So, there can be many, many changes that need to be shadowed for the site.
\n\n\n\nIf you’re changing the site title, some of the global styles, aspects, and so on need to be orchestrated. So, to see in the previewing new window, there are some challenges there to integrate. Again, the interface is not final yet; a lot of these things are still being tweaked and improved. There are many things from the regular post editor that are not enabled yet. But they will be enabled. So yeah, it’s a, I guess, it’s not a simple thing to answer. Because, again, the idea of previewing the site that’s core to the whole project is that you’re always interacting in the same way that when you’re in the customizer, you’re seeing the preview all the time. That’s the main scope of this project,
\n\n\n\nJosepha [15:54]: Excellent. Changes like that changes to your workflow can be really hard to get your mind around, especially if part of that existing workflow was there to create some confidence in what you’re seeing with your users. And so I understand. Now that I’ve researched that question a bit, I see where that’s coming from. Based on existing workflows and existing patterns that we have for ourselves in WordPress, will we need to have a theme to use the full site editor?
\n\n\n\nMatías [16:33]: I think we’ve already covered some of these. And again, they are tools that can work on any existing theme. There is other stuff that needs space-specific themes to opt-in into these tools, like blog templates and so on.
\n\n\n\nJosepha [16:50]: Yes, I think the question that we have next, because I see that the literal next question I have is actually something we have covered; just because we’re being pretty conversational about it, not because anyone already asked the question. So I’m actually going to skip to the last question of this section that I received. I got this next one via Twitter. The question is, “how do you view the role of themes once full site editing is fully rolled out and all the page elements (content, headers, widgets, footers, etc.) and all the views are managed via blocks and block patterns? Will things become typographic and block styles?”
\n\n\n\nMatías [17:28]: I think this is a great question because it goes to the heart of, why are we doing all this. One of the main reasons is to empower users more. WordPress has been democratizing publishing for a while; this is another step into allowing themes to get more customization tools and more control over their site if they want to. I think the recent call for testing has focused on the 404 page, for example. That’s something that forever has been locked away from users. And it’s also something that, as a theme developer, and I used to develop themes a long time ago, that was one of the things where you decide what sort of approach you take for the 404 page. Maybe sometimes you want to have something more whimsical. Sometimes you need something more serious. And committing to one when you can have such a diverse and broad user base can be challenging. With these, it becomes as easy as offering a few different patterns for that template. Then the user will always be able to change the copy and modify something. So again, it opens up a lot of these things that used to be locked down. However, from a theme perspective, I think this doesn’t reduce the theme at all. If anything, it allows the theme to focus less on coding and functions and more on design expression and aesthetics. I don’t think that would ever be exhausted. That will always remain as diverse as humans are interacting with WordPress. And so it’s not that I don’t see it’s just as like, typographic and block styles. How do you express a template, how do you express the structure, what choices you quote, what choices you make as a theme builder? And of course, there are many degrees of control there. Because a site maintainer may not want the 404 template to be editable, that sort of control will always be present.
\n\n\n\nJosepha [19:38]: Yeah. And really fast. I have to add a caveat to a thing that you said in there. For anyone who’s listening keenly, you may have heard Matías say that the users can update any of the content there – any of the copy. In this context, we’re talking about users as in the people who are maintaining the site, not people who are visiting your site. Visitors to your site will not be able to change any copy on your page unless you’ve done something very interesting with your WordPress site, which is also fine if that’s what you prefer to do. By default, your visitors can’t change everything on your website, which is good news, frankly.
\n\n\n\nSo I’ve got one logistics question, which I’m happy to take. And then one is kind of a big picture question that I also got from Twitter. “What about the classic editor block; what is going to happen to that? And when will we know?” So ages and ages ago, before COVID? I think so. Probably maybe a couple of years ago, Matt said that the classic editor plugin would be supported through the end of 2021. And that is still the case; there will be active support on that through the end of 2021. After that, it will not be actively supported anymore. It won’t be removed from any place that you can get access to right now. In a “this is the end of its lifecycle” sort of way, we just won’t have anyone who is currently committed to maintaining that plugin anymore. So that’s what’s happening at the end of the year. And yeah, at the end of 2021. The big question that we have is, “why is full site editing being so rushed?” I think this is a bit of a loaded question.
\n\n\n\nMatías [21:32]: Yeah, I think I think it’s still a fair question, though. I think we’re dealing with two things here. And one is ensuring that we release things in the best state possible. And also, some of the urgency is to offer tools that we know that people lack right now and that could really benefit from. Making that determination is very tricky. The full site editing project has been in the works for the last couple of years. If we count the initial phase of Gutenberg, that’s four to five years. We’ve been doing many calls for testing, which I think have been super useful to catch issues and reflect as a community on where things are going; how do we integrate with these? How do we use it? What are the shortcomings? What do we need to do? Based on all of these, we’ll continue to make decisions on when things become ready. We’re not committed to releasing something that’s not in a good state. And I think we will always be very careful about that. There are these two competing senses of the urgency – of getting some of these tools out, and because it also benefits from the feedback loops. I always say that, in many ways, the initial phase of Gutenberg, to me, is not finished. We took the initial two years to do the 5.0 release, the initial block editor, and so on. But, it’s still being improved at a very fast pace, among all the recent major releases improvements to the editor were included; that will continue to be the case. In many ways, phase one is not finished. And the moment we choose to release some of these tools or editing tools, it won’t be finished either. They will need to continue to grow, mature, and incorporate a lot of the feedback. Even the things that the ecosystem is building around. I’ve seen a few themes already that are incorporating a blank canvas template so that you can use them in some pages and take over and do everything with blocks. So even the community and ecosystem as a whole is also sort of paving the way for what needs to come.
\n\n\n\nJosepha [24:06]: I think from my perspective, and of course, I’m on the people side of things, the communication side of things, the logistics side of things; I have a frequently a very different view from what a lot of other folks are seeing. And so from my side of things, I have to say, I’m communicating about this change in a really broad way, which has not been happening since 2019 when we started the work. We’ve been communicating broadly with the WordPress community, but not with everybody who uses WordPress. So, I think that for a lot of people, this looks like a project that we started really actively working on in the last six months or so. And now we’re just racing toward a finish line. I think that there’s, there’s not been a lot of awareness of everything that’s gone into it. And so, on the one hand, it feels a little less rushed to me knowing the full length of the history on this. But also, as you said, I really think that this gets a bunch of tools to people who otherwise have not been able to accomplish these things in WordPress or otherwise. I am so anxious to get something to people who really can benefit from this change the most. And it’s the nature of the open source, right that like, one, as long as you have users, you’re going to have stuff you have to fix in your software. So we’re never really, really going to be done with this; there’s not going to be like a done point of WordPress. And the second thing is, I think it’s generally true that you don’t really start getting full user feedback until after you have launched your major release. I think that we see that a lot in open source software; you can bring in as many people as you think you can in your user tests heading up to it. And in your accessibility tests. And, in general, quality assurance tests. You can bring in a lot of people and still not have gotten the full understanding of the various niche use cases that your users will bring to you. Because at this point, we’re like 40% of the web. And that means that we’re serving this majority collection of increasingly minority voices and niche voices in the space. And so, a little bit I feel a sense of urgency; I feel a bit of anxiousness about trying to get this out there for one, to get the tools in the hands of the people who can benefit the most from them, but also so that we can start really getting the full stress test of this software out and get that feedback in so that we can really build something responsive to what our users need our long tail, “anyone who ever uses WordPress ever,” definition of users. And so, that’s why I feel a sense of urgency around it. Even though you know, as I said, you and I have been working on this for like five years, and you’ve been working on it for a decade or something. I actually don’t know how long it’s been worked on.
\n\n\n\nMatías [27:35]: Now that makes me feel a bit old.
\n\n\n\nJosepha [27:40]: Nobody makes Matías feel old. He is a lovely, wonderful colleague. Sorry, Matías, If I made you feel old.
\n\n\n\nMatías [27:46]: No, that’s totally fine. I also want to add that full site editing is not like a single toggle that’s going to drop into a major release. So I think that’s important to consider, I think this entire year is going to see a lot of these tools being, and sometimes the sort of the end-user is not the, again, the site maintainer. Still, you can also be the theme developer; I think there are many tools that would be empowering for theme developers to use. Again, we mentioned there are like five to ten themes, block themes right now. That needs to grow a lot, and that only grows through these sorts of feedback loops. And the theme community pushing things forward and seeing where things can lead to. I’m very excited about the pattern directory integration because I think that can also combine with blog themes in very powerful ways. Imagine if, I don’t know many of these patterns that are very common on the web and very needed, that if we can refine them together with a second community and make them available across themes, you can combine a header from one theme with a content of another; all these sorts of mixtures could happen. All of this needs exploration, the creativity of the entire community, and so on. In that sense, getting all these tools, even if it doesn’t immediately change anything for like the site itself, starts to unlock a lot of things.
\n\n\n\nJosepha [29:27]: I’m going to take a bit of your answer from there and tie it all the way back to your first answer that we had when you joined me today. And say, I think you’re absolutely right. We have a set of users in our theme authors and our plugin developers as well that we desperately need to get looking at this set of tools. I hope that what we are shipping in the first iteration of this serves as an opportunity for all of those theme authors and agency owners, plugin authors, WordPress site configurers freelancers. Like, I really hope that this puts it into a really accessible, easy-to-access space for them so that they can do those experiments based on what they know their users need the most. They are the group that has the closest access to site maintainers. And what they need compared to, for instance, me or a potential you like we have a lot of information, you and I, we do a lot of tests, we have a strong sense of what is needed at the moment, but we don’t have as a close connection that our theme and agency and plugin folks all have. And so that’s another part of why I’m so excited to get this out in the current iteration of it.
\n\n\n\nJosepha [31:04]: That was a lot of questions in a little bit of time. This is going to be officially my longest WordPress briefing. Matías, I am so glad that you were able to join me today. And I think that everyone’s going to be really, really excited to hear your answers to these questions.
\n\n\n\nMatías [31:23]: Thank you for having me.
\n\n\n\nJosepha [31:25]: All right, my friends. That brings us into our small list of big things. I’m going to skip our community highlight today just because we had a slightly longer word press briefing in our bonus iteration today. But the small list of big things. The first thing is WordCamp Central America is coming up on April 15; there is a registration link in the show notes that you can access your tickets with. I recommend that you go; we’ve got a lot of excellent speakers coming up there and a lot of good content and good training and learning for y’all. The second thing is that Matt Mullenweg and I have listening hours coming up with the community in the first week of April. I’ll add the link to register for those in the show notes as well; it’s just a few minutes for you all to stop by, check-in, see what’s going on, and share some celebrations or concerns with us. And I hope that I see you there.
\n\n\n\nSo that my friends is your small list of big things. Thank you for joining in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"10013\";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: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:35:\"WP Briefing: How WordPress Improves\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2021/03/how-wordpress-improves/\";s: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, 15 Mar 2021 15:08: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: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:52:\"https://wordpress.org/news/?post_type=podcast&p=9980\";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:178:\"In this episode, Josepha Haden Chomphosy explores the WordPress release process. Tune in to learn about what goes into a release and catch this week’s small list of big things.\";s: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/03/WP-Briefing-004.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: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:10233:\"\nIn this episode, Josepha Haden Chomphosy explores the WordPress release process. Tune in and learn the phases of a release and catch this week’s small list of big things.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- WordPress 5.7 “Esperanza”
- Esperanza Spalding
- Gutenberg Tutorial: Reusable Blocks
- make.wordpres.org/test
- GitHub repository
Transcript
\n\n\n\n\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nAll right, so last week, we wrapped up and shipped the WordPress 5.7 release. The release team this time around was smaller than we’ve had in the last couple of years. By the numbers, it looks really good: 66 enhancements or feature requests went in, 127 bugs were fixed, and seven versions of a Gutenberg plugin were merged and backported. If you use WordPress, you are probably aware that we have new releases throughout the year, but you probably don’t know much about the release process. There’s not really a reason to know unless you’re actively contributing to a release. For those interested in knowing more about how we improve WordPress, this week’s exploration is for you.
\n\n\n\nWe’re gonna take a look at what goes into WordPress releases and just kind of zoom our way in from the highest level. At the highest level, there are three major WordPress releases a year, plus the minor releases, plus Gutenberg releases. So if you’re following current WordPress work and future WordPress work, that’s going to get you to probably around 30 releases a year. If we zoom in one level to the release itself, a single release of WordPress takes four to five months from start to the day that we ship, and an additional four to six weeks on support and translations, and minor releases after that. If you’re looking from my vantage point, you’ll see that WordPress releases have essentially five parts, some of which happen kind of simultaneously.
\n\n\n\nThe first part is planning and includes the project lead, lead developers, design; groups like that. The second phase is the creation phase when we’re actually building the things that have to go into the CMS that involves the design, core, editor, mobile, and other teams. Then there’s this phase that I like to refer to as the distribution phase. This is mostly done by the teams that make sure that WordPress is widely distributable; the polyglots team work on translations, accessibility does some work, docs make sure that everything is documented, and training, of course, gets things ready for when we have to be able to tell people how to use the release.
\n\n\n\nThen there is the fourth phase; I really don’t think they go sequentially or in a waterfall format. The fourth-ish phase that I include, and that I tend to see, is this extending and iteration phase. It’s the phase where we see our theme authors and our plugin authors, folks who are doing support, show up and help us to make sure that WordPress is available not only widely but broadly to ensure that their audiences as theme authors and plugin authors are covered in the features that they need based on what they are using WordPress for. The fifth phase is the part of our communication that involves the community team, especially marketing, WordPressTV, and learn.wordpress.org. Basically, anyone who’s showing up to make sure that we all share what happened in the release, the features that are coming, and how that affects the users is involved in that particular phase. So five big phases of what happens over those four to five months, and then for the month or month and a half afterward.
\n\n\n\nIf we zoom in a bit more on the creation phase, each release has people who lead the work and coordinate contributor efforts during the course of the release. For any given release, hundreds of people contribute and receive credit for moving the WordPress project forward. Okay, hold on a second. Let’s pump the brakes and zoom in a bit on that. Hundreds of people work on every major release for a project that powers over 40% of the web that feels like a small number. But for the people who process the contributions in preparation for release, it’s actually pretty substantial. For every release, there is a small team of leaders who asked the hard questions. Is this a usable feature? Does this make WordPress better overall? And, of course, is this ready to ship? Some of those leaders, a smaller subset of even the leaders that we have already, are committers who actually prep and merge patches to the CMS; they don’t do all the work to create a design or write all the code. This tiny group of people processes hundreds and hundreds of bug fixes, improvements, and enhancements that have been submitted over the course of months and sometimes years. As a side note, that whole process is a little smaller, a little faster in the Gutenberg featured plugin, but the basic parts are still there. Alright, so we’ve zoomed from the big picture way into some of the finer details, and it really looks like any other project cycle. So now, I’m going to layer in the filter of open source to that process.
\n\n\n\nThere are a couple of things that make building software in an open source environment so different. The first is that the code is readily available. If you have a basic understanding of the languages, you can see the code, learn from it, and make suggestions about improving it. Second, you consider the user a co-developer in the process, which means that as long as people use your product, they will have opinions on what you shipped. This way of iterating improves WordPress and ties back to one of my favorite open source principles. The idea that with many eyes, all bugs are shallow. To me, that means that with enough people looking at a problem, someone is bound to be able to see the solution.
\n\n\n\nThis brings us to our community highlight, the segment where I share a note about contributors who have helped others along the way or a WordPress success story. This week’s highlight is from Nok in our Bangkok community. When asked to help her find her way into the WordPress community, she said, “@shinichiN who started the WordPress community in Bangkok and encouraged me to contribute, and also @mayukojpn has introduced me to the WP community team to join as a deputy. “ Thank you for sharing those two inspiring people with us. And if you, listener, have any stories that you would like to share of your own WordPress success or people that you have been so grateful to help you find your way in the project, you can feel free to email those to me at wpbriefing@wordpress.org.
\n\n\n\nThat brings us to our final segment of the WP Briefing, the small list of big things. I only have three things to share with you this week. The first one is that about a week ago, we had our first release of 2021. It was the WordPress 5.7 release, titled Esperanza. If you have not yet seen it, go ahead and update your website or check with your host and make sure that they have updated you if you’re on a managed host. And then take a listen to the artists that it’s named after.
\n\n\n\nThe second thing that I want you to keep an eye out for is wordpress.org/news. We are starting a new series of content that gets at the heart of some of Gutenberg’s basic parts; there’s a lot of change coming up in the next few releases of WordPress. And the most important thing to me is that you understand what we’re trying to change and where those changes are primarily taking place. There will be a couple of tutorials that go up there over the course of the of the next few weeks. The third item on the small list of big things is to remind you of our call for testing. As I mentioned earlier in the podcast, the users of any open source software are the code developers; the software built is supposed to make your life and work easier. When you test things and find interactions that can use a little bit of refinement or features that are not working exactly as expected, it’s incredibly helpful for us to have that information to always make sure that we’re solving problems instead of accidentally creating them. If you want to participate in the Current call for testing, you can head over to make.wordpress.org/test. Or, if you’ve been doing your own testing, you can also submit any bugs you have found in the GitHub repo, which I will share in the show notes below. So that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9980\";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: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:29:\"WordPress 5.7 “Esperanza”\";s:7:\"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:45:\"https://wordpress.org/news/2021/03/esperanza/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Mar 2021 20:52:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9888\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:355:\"Meet “Esperanza”, the first WordPress release of 2021. “Esperanza” is named in honor of Esperanza Spalding, a modern musical prodigy. Her path as a musician is varied and inspiring—learn more about her and give her music a listen! With this new version, WordPress brings you fresh colors. The editor helps you work in a few places […]\";s: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://s.w.org/images/core/5.7/about-57-drag-drop-image.mp4\";s:6:\"length\";s:6:\"183815\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:40520:\"\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2021/03/about-header-brushes.png?resize=632%2C327&ssl=1\")
WordPress 5.7 “Esperanza”
\n\n\n\nBringing you fresh colors in the admin, simpler interactions in the editor, and controls right where you need them, WordPress 5.7 lets you focus on the content you create.
\n\n\n\n\n\n\n\n\nMeet “Esperanza”, the first WordPress release of 2021. “Esperanza” is named in honor of Esperanza Spalding, a modern musical prodigy. Her path as a musician is varied and inspiring—learn more about her and give her music a listen!
\n\n\n\nWith this new version, WordPress brings you fresh colors. The editor helps you work in a few places you couldn’t before without getting into code or hiring a pro. The controls you use most are right where you need them. Layout changes that should be simple, are even simpler to make.
\n\n\n\nNow the new editor is easier to use
\n\n\n\nFont-size adjustment in more places: now, font-size controls are right where you need them in the List and Code blocks. No more trekking to another screen to make that single change!
\n\n\n\nReusable blocks: several enhancements make reusable blocks more stable and easier to use. And now they save automatically with the post when you click the Update button.
\n\n\n\nInserter drag-and-drop: drag blocks and block patterns from the inserter right into your post.
\n\n\n\nYou can do more without writing custom code
\n\n\n\nFull-height alignment: have you ever wanted to make a block, like the Cover block, fill the whole window? Now you can.
\n\n\n\nButtons block: now you can choose a vertical or a horizontal layout. And you can set the width of a button to a preset percentage.
\n\n\n\nSocial Icons block: now you can change the size of the icons.
\n\n\n\n![\"\"](\"https://i0.wp.com/s.w.org/images/core/5.7/about-57-cover.jpg?w=632&ssl=1\")
A simpler default color palette
\n\n\n\nThis new streamlined color palette collapses all the colors that used to be in the WordPress source code down to seven core colors and a range of 56 shades that meet the WCAG 2.0 AA recommended contrast ratio against white or black.
\n\n\n\nFind the new palette in the default WordPress Dashboard color scheme, and use it when you’re building themes, plugins, or any other components. For all the details, check out the Color Palette dev note.
\n\n\n\nFrom HTTP to HTTPS in a single click
\n\n\n\nStarting now, switching a site from HTTP to HTTPS is a one-click move. WordPress will automatically update database URLs when you make the switch. No more hunting and guessing!
\n\n\n\nNew Robots API
\n\n\n\nThe new Robots API lets you include the filter directives in the robots meta tag, and the API includes the max-image-preview: large directive by default. That means search engines can show bigger image previews, which can boost your traffic (unless the site is marked not-public).
Lazy-load your iFrames
\n\n\n\nNow it’s simple to let iframes lazy-load. By default, WordPress will add a loading=\"lazy\" attribute to iframe tags when both width and height are specified.
Ongoing cleanup after update to jQuery 3.5.1
\n\n\n\nFor years jQuery helped make things move on the screen in ways the basic tools couldn’t—but that keeps changing, and so does jQuery.
\n\n\n\nIn 5.7, jQuery gets more focused and less intrusive, with fewer messages in the console.
\n\n\n\nCheck the Field Guide for more!
\n\n\n\nCheck out the latest version of the WordPress Field Guide. It highlights developer notes for each change you may want to be aware of. WordPress 5.7 Field Guide.
\n\n\n\nThe Squad
\n\n\n\nThe WordPress 5.7 release comes to you from a small and experienced release squad:
\n\n\n\n- Release Lead: Matt Mullenweg (@matt)
- Triage Lead: Tonya Mork (@hellofromtonya)
- Release Coordinator: Ebonie Butler (@metalandcoffee)
- Core Tech Lead: Sergey Biryukov (@sergeybiryukov)
- Editor Tech Lead: Robert Anderson (@noisysocks)
- Design Lead: Tim Hengeveld (@hedgefield)
- Accessibility Lead: Sarah Ricker (@sarahricker)
- Documentation Lead: Jb Audras (@audrasjb)
- Test Lead: Monika Rao (@monikarao)
This release is the reflection of the hard work of 481 generous volunteer contributors. Collaboration occurred on nearly 250 tickets on Trac and over 950 pull requests on GitHub.
\n\n\n\n7studio, aaribaud, Aaron Brazell, Aaron D. Campbell, Aaron Jorbin, aaronrobertshaw, abagtcs, acerempel, activecoder, ad7six, Adam Bosco, Adam Silverstein, adamboro, Addison Stavlo, aduth, Ahmad Awais, Ahmed Saeed, Albert Juhé Lluveras, albertomake, Alex Lende, Alex Woollam, alex27, Alexander Lueken, alexstine, allancole, Allen Snook, almendron, Amanda Riu, ambienthack, Amol Vhankalas, Andrea Fercia, Andrei Draganescu, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrew Serong, André Maneiro, Andy Fragen, Andy Peatling, Ankit Panchal, Anne McCarthy, Anthony Burchell, Anton Lukin, Anton Timmermans, Anyssa Ferreira, archon810, Ari Stathopoulos, Arslan Ahmed, Artur Piszek, Aurélien Denis, Ayesh Karunaratne, bartosz777, basscan, bduclos, becdetat, Bego Mario Garde, Ben Dwyer, Bernhard Reiter, Bernhard Reiter, bhanusinghkre, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, bonniebeeman, Boone Gorges, Boy Witthaya, Brandon Kraft, Brent Swisher, brijeshb42, burnuser, Caleb Burks, Cameron Voell, Carike, carloscastilloadhoc, carlosgprim, Carolina Nymark, celendesign, Cenay Nailor, ceyhun0, chexwarrior, Chip Snyder, Chloé Bringmann, Chouby, Chris Van Patten, Christian Sabo, Christina Workman, Christopher Finke, clayray, Clayton Collie, Code Amp, Collins Agbonghama, Copons, Corey, cristinasoponar, Damian Nowak, Dan Farrow, Daniel Richards, Daniele Scasciafratte, Danny van Kooten, Daria, Darren Ethier (nerrad), Dave Whitley, David Anderson, David Baumwald, David Biňovec, David Calhoun, David Herrera, David Page, dbtedg, dd32, Debabrata Karfa, dekervit, Denis Yanchevskiy, denishua, Diane Co, Dilip Bheda, Dominik Schilling, donmhico, dratwas, Drew Jaynes, Dávid Szabó, e_baker, Ebonie Butler, Edi Amin, Ella van Durpe, Ella van Durpe, Elliott Richmond, Enej Bajgorić, Enrico Carraro, epicfaace, epiqueras, Eric Andrew Lewis, Eric Binnion, Eric Mann, Erik Betshammar, Erin \'Folletto\' Casali, Estela Rueda, etoledom, eventualo, Fabian Kägy, Felipe Elia, Felix Arntz, Florian TIAR, Florian Ziegler, floriswt, Francesca Marano, Frank Klein, fullofcaffeine, Gan Eng Chin, Garrett Hyder, Gary Pendergast, GeekPress, geekzebre, Geoff Guillain, George Stephanis, geriux, gKibria, glendaviesnz, gmariani405, Gord, greatsaltlake, Greg Ziółkowski, grzim, gumacahin, gunnard, Gustavo Bordoni, Hans-Christiaan Braun, Hardeep Asrani, Hareesh, hauvong, Haz, Helen Hou-Sandi, helmutwalker, Hemant Tejwani, Herre Groen, hirasso, hmabpera, Howdy_McGee, hsingyuc7, Ian Dunn, ianmjones, ibiza69, Igor Radovanov, ingereck, iprg, Ipstenu (Mika Epstein), Isabel Brison, Ismail El Korchi, iviweb, J.D. Grimes, jadeddragoon, Jake Spurlock, jakeparis, jakub.tyrcha, James Golovich, James Huff, James Koster, James Nylen, James Rosado, Jan Thiel, Jason Adams, Jason LeMahieu (MadtownLems), Jason Ryan, Jayman Pandya, Jean-Baptiste Audras, Jeff Chandler, Jeff Farthing, Jeff Paul, Jennifer M. Dodd, Jenny Dupuy, Jeremy Felt, Jeremy Yip, Jeroen Rotty, Jessica Duarte, Jessica Lyschik, joanrho, Joe Dolson, Joe McGill, joelclimbsthings, Joen Asmussen, Johannes Kinast, John Blackbourn, John James Jacoby, John Watkins, Jon Surrell, Jonathan Champ, Jonathan Desrosiers, Jonathan Stegall, Jonny Harris, Jono Alderson, Joost de Valk, jordesign, Jorge Costa, José Miguel, Jose Luis, Joseph Karr O'Connor, Josepha Haden, joshuatf, JoshuaWold, JOTAKI, Taisuke, Joy, JS Morisset, jsnajdr, Juliette Reinders Folmer, Julio Potier, Justin Ahinon, Justin Sainton, Justin Sternberg, kafleg, Kai Hao, Kailey (trepmal), Kalpesh Akabari, kara.mcnair, Karolina Vyskocilova, Kelly Choyce-Dwan, Kerry Liu, kimdcottrell, Kiril Zhelyazkov, Kirsty Burgoine, Kite, Kjell Reigstad, Knut Sparhell, Konrad Chmielewski, Konstantin Obenland, Konstantinos Xenos, Kurt Payne, Kyle B. Johnson, Lara Schenck, laurelfulford, Laxman Prajapati, leogermani, Levdbas, litemotiv, Lovro Hrust, lucasbustamante, Luigi Cavalieri, Lukas Pawlik, Luke Carbis, Luke Cavanagh, Luke Walczak, Magali, magnuswebdesign, Mahafuz, Mahdi Akrami, malinajirka, mallorydxw, mallorydxw-old, Manzoor Wani, Manzur Ahammed, marcelo2605, Marcio Zebedeu, Marcus, Marcus Kazmierczak, Marie Comet, Marijn Koopman, Marin Atanasov, Marius Jensen, Mark D Wolinski, Mark Howells-Mead, Mark Robson, Mark Uraine, Marko Andrijasevic, Markus, Mary Baum, Mathieu Berard Smartfire, Mathieu Viet, Matias Ventura, Matt Chowning, Matt Mullenweg, Matt Wiebe, Maxime Pertici, Mayank Majeji, mdrockwell, Meg Phillips, Megan, Meher Bala, Mehrshad Darzi, Mehul Kaklotar, Mel Choyce-Dwan, mendezcode, mgol, Michael Arestad, Michael Babker, Miguel Fonseca, Miina Sikk, Mike Schroder, Milan Dinić, Milana Cap, mirka, Mohamed El Amine DADDOU, Monika, Monika Rao, morenaf, mrjoeldean, Mukesh Panchal, munyagu, mzorz, Naveen, net, nicky, Nico, Nico Martin, Nicola Laserra, Nicolas Juen, NicolasKulka, Nik Tsekouras, Noah Allen, nwjames, oakesjosh, Olga Gleckler, ovidiul, oxyc, Paal Joachim Romdahl, Pascal Birchler, patopaiar, Paul Bearne, Paul Biron, Paul Bunkham, Paul Schreiber, Paul Von Schrottky, pawki07, pbking, Pedro Mendonça, Pete Nelson, Peter Smits, Peter Wilson, Pinkal Devani, Piotrek Boniu, Prem Tiwari, presstoke, prettyboymp, Prince, pypwalters, Q, r-a-y, Rafael Galani, rafhun, Rami Yushuvaev, Ramon Ahnert, ratneshk, Ravi Vaghela, ravipatel, retrofox, Reza Ardestani, Riad Benguella, Rian Rietveld, Richard Tape, Robert Anderson, Rodrigo Primo, roger995, Rolf Siebers, Romain, Ronnie Burt, Ross Wintle, Ryan Boren, Sébastien SERRE, Sören Wrede, Saša, Sanket Chodavadiya, Sarah Ricker, sarayourfriend, Scott Taylor, Sebastian Pisula, SeBsZ, Sergey Biryukov, Sergey Yakimov, sergiomdgomes, Shahin Sid, shaunandrews, Shital Marakana, Slava Abakumov, snapfractalpop, souri_wpaustria, Stefano Minoia, Stefanos Togoulidis, Stephen Bernhardt, Stephen Edgar, Steven Word, Subrata Sarkar, Sunny, t-p, Takashi Kitajima, Tammie Lister, Tanvirul Haque, Tapan, TeamDNK, TeBenachi, Thierry Muller, thorlentz, Tim Hengeveld, Tim Nolte, Timi Wahalahti, Timothy Jacobs, tinodidriksen, Tkama, tmatsuur, Tobias Zimpel, tobifjellner (Tor-Bjorn Fjellner), Toni Viemerö, Tony A, Tonya Mork, tonysandwich, Torsten Landsiedel, Toru Miki, transl8or, Tyler Tork, Ulrich, Umang Vaghela, vandestouwe, vcanales, Vipul Chandel, Vlad T., webcommsat AbhaNonStopNewsUK, WebMan Design | Oliver Juhas, Wendy Chen, wesselvandenberg, Weston Ruter, Willis Allstead, worldedu, WP OnlineSupport, Xristopher Anderton, Yann Kozon, Yoav Farhi, yscik, Yui, yuliyan, Zebulan Stanphill, and zieladam.\n\n\n\n\n\n\n\nCode is poetry.
\nWordPress 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 lesser-known.
\n\n\n\nFrom a natural interest in computers and fixing things as a young woman, Olga Gleckler from St Petersburg, Russia, found WordPress took her on a journey to becoming a successful female tech entrepreneur. On International Women’s Day, we share her story.
\n\n\n\n![\"Olga](\"https://i2.wp.com/wordpress.org/news/files/2021/03/WCEU-2020-online.jpg?resize=580%2C768&ssl=1\")
Finding your path can take longer than you expect
\n\n\n\nFrom the age of 15, Olga found herself under pressure to find a free place for her professional studies. She said: “I didn’t know how high or low my chances were even if I had very good marks. I could have been just the biggest fish in a small pond. But anyway, I made up my mind to go to technical school.”
\n\n\n\nOn leaving school in St Petersburg with her certificate, Olga felt her knowledge of opportunities was very narrow. She had pictured being an ecologist or guide translator based on the subjects she had been taught at school. There was also an advertising boom in Russia and she began to explore this as a career avenue. She had developed her computer skills and found opportunities to practise by helping her teachers with administrative work.
\n\n\n\nThough she did not have access to any formal career advice, her journey led her into programming. She said: “The range of technical schools was not wide. I spent four years studying transistor markings, soldering and drawing PCB layouts. Programming courses using Pascal didn’t do anything useful with it.”
\n\n\n\nA lack of suitable access to English-language courses made things harder for Olga. She was determined that she would master the language later in her life. In the meantime, she left technical school with an honors degree and improved typing skills.
\n\n\n\n“I faced it was a wild, unfriendly market. I didn’t know how to recognize a genuine job offer or how to avoid the bad ones. It was difficult and I don’t know how long I would’ve looked for work without help.”
\n\n\n\nThink differently to find where you belong
\n\n\n\nOlga’s father worked in an IT company and was able to give her some advice and help with potential introductions. When she was still studying, he suggested her strong technical skills might be useful as a substitute typist. When she finished her studies, he helped her apply for a job updating a legal system on clients’ computers.
Six months later, she got a full-time job in the same service department. She liked her position and her clients. However, she was given friendly advice that without a university degree she would not be able to have any further promotions.
At this time, Olga was trying to study PHP from a book. She found it very exciting at first, but a lot of their functions did not give her explanations on how to build something useful. She found when she tried to build practical items from book reading, it did not always make sense and the solutions would often fail.
\n\n\n\nShe said: “It was hard to admit a failure even to myself and it was nagging me for a long time. I had to choose something I could handle, that I was interested in and could afford. It turned out to be advertising.”
\n\n\n\nShe spent most of the family’s holidays on learning sessions during the next six years. Olga recalled: “It was tricky for my husband to make me leave a computer, once I was glued to it, so he bought me my first laptop. English was still hard for me, I got high marks through just memorizing all the words in a textbook and how they should sound.”
\n\n\n\n\n\n\n\nDoubting your professional skills can happen when you are at home isolated looking after children. Keeping up your interests is important.
Olga’s life took a change after having a new baby and she spent three years doubting her professional skills and her chances of getting a good job. She tried to get back into other interests through studying, baking and drawing, but found ‘the pram was pulling me back’. She found she became very isolated and felt less able to contribute as the family was relying on her husband’s income as she tried to focus on looking forward.
\n\n\n\nShe said: “I was convinced (and saw) that not too many companies wanted a woman in the office, who with a small baby might need lots of leave.”
\n\n\n\nShe finished her education when she returned to work after three years caring for her son. She secured a promotion but with changes in the company’s staffing, things were tense. She found the difficulties there had become more heightened and felt that young female colleagues were treated as ‘pieces of furniture’ by one manager. She did not want to stay in this environment and in a few months time decided to leave.
\n\n\n\nYour next chapter may be nearby
\n\n\n\nDetermined to not repeat this type of experience, Olga looked at the brighter side. She said: “I wanted to be a marketer. Knowing how tricky it is to sell intangibles, I wanted a solid product to work with.”
\n\n\n\nIt turned out to be more difficult to find a job outside traditional IT as a young mother. Some human resource officers advised her to remain within the technology arena.
\n\n\n\nOlga remained hopeful and continued to study hard. She had many learning experiences along the way, which she hopes others can learn from too. One was setting a low bar to employers. She said: “Companies I worked in wanted to get all publicity and sales increases achieved through deductions from my salary.” This happened once and the next time she was in this situation she asked specifically about the budget before signing up. “I was assured this would not be the case, but again I found the budget for publicity came out of my wages. It was a tough period of disappointments. So when I was offered a part-time administrative job with basic sick leave, I took it gladly as a reprieve.”
\n\n\n\nThe job was far from home and involved a lot of travelling. Olga spent two to three hours a day on buses with Harry Potter audio books for company. “In these traffic jams, I started to feel English at last and loved it. It gave me a freedom no money can buy. Life was getting better.”
\n\n\n\nThough the job did not pay highly, it gave her something valuable – a working website. After her boss and the developer parted company, she was asked to maintain the site. Through some studying and reverse engineering, she discovered how it worked and it gave her an insight into how to write simple websites from scratch.
\n\n\n\nOlga’s first encounter with JavaScript wasn’t easy: “My first JavaScript calculator almost made me crazy, but I pursued it.”
\n\n\n\nQuickly she started to get small tasks from friends and relatives, usually to solve some urgent problems and started to meet popular content management systems. One of the first she met with was WordPress. There was an issue in a website theme used by a website which had been changed and not maintained. It took a whole weekend to solve, but she was determined to work it out. Back then, WordPress was ‘just a system’. She didn’t know then how much it was to become part of her life.
\n\n\n\nOlga spent the next two years in this role. As time went on, she started to feel worried and less satisfied with the work. The last straw for her was a negative statement from her boss, who was not a programmer and who hadn’t seen any of the work done on the website. She felt the approach was unfair as she had done extensive work on the site. She recalls: “I became angry, but it was exactly what I needed to move jobs.”
\n\n\n\nWhen Olga was job hunting, she didn’t feel she had the courage to apply for a developer’s role, despite the learning and work she had already done. So instead she started working on projects where she felt she was more like a ‘seller of box-ready websites’. It was another tough half a year for her with a lot of work, low payment and plans not turning out as she had hoped. On top of long hours, she ended up with pneumonia. She said: “I see now that I was doing a disservice to customers, websites are not a microwave meal – quick, cheap and dummy. There was no life in the sites without a lot of work which no one was willing to buy. Most of the sites I sold back then died after the first year and they never were truly alive and useful.”
\n\n\n\nYou need to be brave and have courage
\n\n\n\n![\"Olga](\"https://i2.wp.com/wordpress.org/news/files/2021/03/Berlin-2019.jpg?resize=632%2C422&ssl=1\")
Olga really wanted a developer job but seeking jobs of this type was very frustrating. From the job adverts she found, it felt like most IT companies were asking for geniuses who already knew a lot of technologies and frameworks. She found this very demotivating.
\n\n\n\nShe then found a job offer on a website outside the most popular job portals and it seemed like a perfect fit. They wanted someone with experience to write from scratch, understand someone else’s code and maintain it, with an ability to translate technical documentation and articles, and make simple designs for printing products. After completing a trial task, she was taken on, and enjoyed a better salary, in a calm environment with good colleagues and without the requirement for a lot of extra hours.
\n\n\n\nThe advert turned out to be a direct ad from one of the sales departments in a technology company. By succeeding in the task set, Olga had bypassed the Human Resources team which she felt would not normally have considered her.
\n\n\n\nHer boss agreed to her working remotely most of the time. It solved any potential leave problems which Olga had thought may be an obstacle.
\n\n\n\nFor Olga it had been 14 years since the original decision to become a programmer and it was only the beginning.
\n\n\n\nAfter a few years at what she describes as an ‘amazing experience’ in this workplace, Olga felt able to move on to her next challenge as a developer.
\n\n\n\nDecision-making can benefit from wider knowledge
\n\n\n\nAfter working with different systems Olga became sure that WordPress is the best CMS for developers and clients. But she was disappointed to find that the ease of use meant that good code was not always a priority for some of the sites she looked at.
\n\n\n\n“The biggest flaw of WordPress – it’s so easy to make things work that some may feel they don’t need to bother to do things right, but this becomes a problem later.”
\n\n\n\nIn custom themes for a site, she also saw sites being made and clients left without any further support, or items hard coded when clients actually needed more control to change regularly.
\n\n\n\nOlga used to rely on examples she could easily find, documentation and search engines to improve her understanding in using WordPress. She discovered that just by searching for a specific feature or a solution, you can miss the whole picture.
\n\n\n\nShe turned to online courses to get more comprehensive knowledge and then started to attend WordPress events, firstly online and then by foot, trains and planes! She discovered a worldwide community that was very much alive. She didn’t know when she started studying online materials and attending discussions that she would end up contributing herself to the Learn WordPress platform a few years later.
\n\n\n\nWordCamps and contributor days became a big part of her life. From her early days attending events and starting out contributing to WordPress, she is an active member of the WordPress.org Global Marketing and Polyglots Teams, and supported the recent WordPress release. She is just beginning her first WordCamp organiser experience, joining WordCamp Europe 2021 on the Contribute Team.
\n\n\n\n![\"Olga](\"https://i1.wp.com/wordpress.org/news/files/2021/03/St-Petersburg-2018.jpg?resize=632%2C602&ssl=1\")
Olga said: “Through the wider WordPress community, I knew not only where to look but also whom to ask. Most importantly, I found allies who don’t think I’m going crazy by speaking with delight about work, and with whom I share a passion and fondness for WordPress. This is what matters.
\n\n\n\n“Now, after more than seven years of full time development, I am still enjoying endless learning, frequent discoveries, mistakes and an impassioned wish to do better.”
\n\n\n\nThis and a desire to help others use WordPress.org is part of Olga’s continued contribution to its Support and Marketing Teams, and led her to be involved in the Release Marketing questions and answers in 2020.
\n\n\n\nThere is no chequered flag on the way
\n\n\n\n![\"Olga](\"https://i1.wp.com/wordpress.org/news/files/2021/03/Berlin-2019-1.jpg?resize=632%2C946&ssl=1\")
The road to freedom and becoming her own boss has not been easy for Olga. It is the path that got her where she is today, and she continues to find joy in it. She retains the lessons she’s learned and is always hungry to learn more.
\n\n\n\n“I travelled through a very uneven path, with a lot of obstacles and noise, but for me it’s like a kaleidoscope where a little turn presents a new picture, a new “ah-ha” moment, new excitement after seemingly pointless efforts.”
\n\n\n\nShe added: “When in doubt I remind myself about David Ogilvy (generally considered the Founding Father of the modern advertising industry) who tried a lot of things before he struck gold with advertising, and maybe that’s why he did.”
\n\n\n\nFinally, she learned not only to keep a good spirit and try different things, but also to dare as you move forward.
\n\n\n\nContributors
\n\n\n\nThanks to Abha Thakor (@webcommsat), Nalini Thakor (@nalininonstopnewsuk), Larissa Murillo (@lmurillom), Meher Bala (@meher), Josepha Haden (@chanthaboune), Chloé Bringmann (@cbringmann) and Topher DeRosia (@topher1kenobe). Thank you to Olga Gleckler (@oglekler) for sharing her #ContributorStory.
\n\n\n\n![\"HeroPress](\"https://lh3.googleusercontent.com/Y3odYTyvSfJbVxUxUWEgKxOprox2zxVwhk7_vdW-AIs4IlE-jK0Zt1itCj867x0dIAbIiK-VeuTLMZr6BjNEY0fkTf--4dT1hkLbnGtsPFNfyrVBYIN59IirTkNnqiQgqxk6E1MI\")
This post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.
\n\n\n\nMeet more WordPress community members in our People of WordPress series.
\n\n\n\n#ContributorStory #HeroPress
\n\n\n\n\n\n\n\nPhoto credits: 2nd and 4th Pablo Gigena, Berlin, 2019
\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:4:\"9875\";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:37:\"The Month in WordPress: February 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:72:\"https://wordpress.org/news/2021/03/the-month-in-wordpress-february-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:\"Wed, 03 Mar 2021 16:00:41 +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:34:\"https://wordpress.org/news/?p=9842\";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:293:\"You don’t have to be rich to have an online presence. You don’t have to find loopholes in proprietary platforms and hope that they never change their terms of service. You own all of the content that you create on a WordPress site and have the liberty to move it to a new host if […]\";s: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:15761:\"\n\n\n\n\nYou don’t have to be rich to have an online presence. You don’t have to find loopholes in proprietary platforms and hope that they never change their terms of service. You own all of the content that you create on a WordPress site and have the liberty to move it to a new host if you need to, or switch your theme if it fits your mood.
That was Josepha Haden Chomphosy on WordPress is Free(dom) episode of the WP Briefing Podcast, speaking about the four freedoms of open-source software. Those four freedoms are core to how WordPress is developed. A lot of the updates we bring you this month will resonate with those freedoms.
\n\n\n\n\n\n\n\n
WordPress now powers 40% of the web
\n\n\n\nW3Techs reported that WordPress now powers 40% of the top 10 million websites in the world! Every two minutes, a new website using WordPress says, “Hello world”! For the top 1000 sites, the market share is even higher at 51.8%. Over the past 10 years, the growth rate has increased, which is reflected by the fact that 66.2% of all new websites use WordPress!
\n\n\n\nWordPress release updates
\n\n\n\nFebruary was an eventful month for WordPress releases!
\n\n\n\n- WordPress maintenance releases — version 5.6.1 and version 5.6.2 — came out this in February. Update to the latest version directly from your WordPress dashboard or by downloading it from WordPress.org.
- Members of the Core team are working hard on WordPress 5.7, due in March. Beta 1, Beta 2, and Beta 3 versions of WordPress 5.7 launched in February. The first and second release candidates of WordPress 5.7 are also out! You can test the Beta versions and the release candidate by downloading them from WordPress.org or using the WordPress Beta Tester plugin. To know more about WordPress 5.7, check out its field guide.
Want to contribute to upcoming WordPress releases? Join the WordPress #core channel in the Make WordPress Slack and follow the Core team blog. The Core team hosts weekly chats on Wednesdays at 5 AM and 8 PM. UTC. You can also contribute to WordPress 5.7 by translating it into your local language. Learn more on the translation status post.
\n\n\n\nGutenberg celebrates its 100th release with version 10
\n\n\n\nThe 100th release of the Gutenberg plugin — Version 10, launched on February 17th, more than four years after the project was first announced at WordCamp US 2016. Matias Ventura’s post offers a bird’s eye view of the project over the last four years. Version 10 adds the basic pages block and makes the parent block selector visible in the block toolbar. Version 9.9 of Gutenberg — coincidentally, the 99th release of the plugin, which is also the latest Gutenberg release that will be featured in WordPress 5.7, also came out in February. Key highlights of the release include custom icons and background colors in social icons, a redesigned options modal for blocks (which is now called block preferences), and text labels in the block toolbar.
\n\n\n\nWant to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\nFull Site Editing updates
\n\n\n\nFull Site Editing (FSE) is an exciting new WordPress feature that allows you to use blocks outside the post or page content. The main focus of the Core team for 2021 is to merge FSE into WordPress core. Here’s the latest on the Full Site Editing project:
\n\n\n\n- The second call for testing as part of the Full Site Editing outreach program is out! To participate, check out the second testing call on the Make/Test blog and join the #fse-outreach-experiment Slack channel. Deadline: March 5, 2021.
- In case you missed participating in the FSE outreach program, you can now test FSE anytime —check out this handbook page on testing FSE to learn more.
- Contributor teams are asking for help from local WordPress Communities to support the FSE Project. Learn more on how you can contribute.
- Check out these answers for the most common FSE questions on the Make/Test blog.
- @chanthaboune has provided an update on the current status of the FSE and themes.
Decision-making checklist for in-person meetups
\n\n\n\nThe Community Team has published handbook pages and a decision-making checklist for organizers to restart in-person meetups at areas where it is safe to do so (e.g., countries such as New Zealand, Australia, and Taiwan, where there are lower COVID-19 risks). However, WordPress meetups and WordCamps in most parts of the world will remain online due to COVID-19.
\n\n\n\n\n\n\n\n
Further Reading
\n\n\n\n- The Polyglots team has kicked-off a proposal to create a working group of contributors to develop training resources for translation contributors.
- The Meta team is actively working on a tool to help the Themes team automate the theme testing process. The team has already shipped a proof-of-concept of the Theme Review Action tool to test the process and is looking for feedback. The Meta team is also working on reducing the Plugin team’s workload by improving the code scanner tool used for scanning plugins.
- The Themes team met with the WordPress project leadership team (Matt Mullenweg and Josepha Haden) about improving the Theme directory. They decided to reframe the theme review process by adding “review guard rails” with automated tooling.
- The Plugin Review Team reiterated that forked premium plugins are not allowed in the Plugin directory.
- After three weekends of celebrating WordPress, WordCamp India 2021 concluded on February 15. WordCamp Prague 2021 took place on February 27. WordCamp India videos are already available, and videos of both camps will soon be uploaded to WordPress.tv.
- Several online WordCamps were scheduled this month. WordCamp Centroamérica, WordCamp Greece, and WordCamp North East Ohio are scheduled for April 2021. WordCamp Japan takes place in June and has opened-up their call for speakers in English and Japanese. Meanwhile, the inaugural WordCamp Cochabamba (Bolivia) runs in July!.
- The Community Team wants feedback on how to improve online WordCamps. The team has also announced a revamped 2021 Global Community sponsorship program to support online events.
- The Design Team is reviewing the user experience for learn.wordpress.org. Please share any design-feedback that you have as comments on the post.
- The Accessibility Team is working on publishing the updated accessibility standards document (with regard to WCAG 2.1 changes) alongside the WordPress version 5.7 release. The team has also started brainstorming goals for WordPress 5.8 and beyond.
- The Support Team is rethinking the use of the master list used for troubleshooting recurring issues. The team is also removing plugin/theme names used as topic tags in forums.
- The Training Team has kicked off their March 2021 sprint planning to work on their goals.
- The WP Notify project working group (which is working toward a better notification system for WordPress) has completed the first version of the requirements document, and officially kicked off active development of the feature plugin. Contact the team in the #feature-notifications Slack channel if you would like to contribute. You can start by reviewing the list of the current issues.
- Pooja Derashri of India was featured in February’s People of WordPress series. A cross-team initiative led by the Marketing Team with support from HeroPress, the series aims to highlight lesser-known stories of WordPress contributors. The Contributor Story series is collecting new features. If you are an active contributor to a WordPress.org team or a local WordCamp, contact the Marketing Team in the #marketing Slack channel for more information.
Have a story that we should include in the next “Month in WordPress” post? Please submit it using this form.
\n\n\n\nThe Month in WordPress post series is a collective effort, and it would not be possible without contributions from different members of the WordPress Community. Starting this month, we would like to credit and thank all individuals that support this effort with their contributions. I would like to thank the following folks for their contributions to February’s Month in WordPress: @adityakane @chaion07 @courtneypk @kristastevens and @psykro.
\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:4:\"9842\";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: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:33:\"WordPress 5.7 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2021/03/wordpress-5-7-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 02 Mar 2021 20:49: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:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9829\";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:394:\"The second release candidate for WordPress 5.7 is now available! 🎉 You can test the WordPress 5.7 release candidate in two ways: Try the WordPress Beta Tester plugin (choose the “Bleeding edge” channel and Beta/RC Only” stream options) Or download the release candidate here (zip). Thank you to all of the contributors who tested the Beta/RC releases and gave […]\";s: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:\"Ebonie Butler\";s: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:2713:\"\nThe second release candidate for WordPress 5.7 is now available! ![\"🎉\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f389.png\")
You can test the WordPress 5.7 release candidate in two ways:
\n\n\n\n- Try the WordPress Beta Tester plugin (choose the “Bleeding edge” channel and Beta/RC Only” stream options)
- Or download the release candidate here (zip).
Thank you to all of the contributors who tested the Beta/RC releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.
\n\n\n\nPlugin and Theme Developers
\n\n\n\nPlease test your plugins and themes against WordPress 5.7 and update the Tested up to version in the readme file to 5.7. If you find compatibility problems, please be sure to post to the support forums, so those can be figured out before the final release.
\n\n\n\nThe WordPress 5.7 Field Guide will give you a more detailed dive into the major changes.
\n\n\n\nHow to Help
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages!
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nProps to @lukecarbis for the haiku and @audrasjb and @hellofromtonya for peer reviewing!
\n\n\n\n\n\n\n\n
Five-seven next week
So test your plugins and themes
Update your readme
In this episode, Josepha Haden Chomphosy speaks to her role as the Executive Director of WordPress. Learn about the day-to-day of her role and how it supports the mission of WordPress.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n\n\n\n\nTranscript
\n\n\n\n\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nI’ve been asked many times what the day-to-day work looks like for the Executive Director of the WordPress project. I don’t really think I’ve done a great job of answering that question. My default answer is either too broad, and I say, “I helped turn the WordPress vision into reality by supporting the community of contributors,” or way too narrow, and I start telling people what’s on my calendar. Probably no one cares about each entry on my calendar, and almost every contributor is covered by “I get things done by helping people.” So today, I invite you to join me in exploring the type of work required and the balance it takes to keep WordPress working.
\n\n\n\nFirst, some context on the weekly activity I see in WordPress, on average, 1,800 to 2,000 contributors a week, participate in conversations and tickets across the entire WordPress project in our entire ecosystem. There are about 20 volunteer teams that are each led by two to three team reps. Each of those teams actually has smaller groups that work on specific things; all told, it’s probably about 50 distinct teams. And probably quite a few more if you are very generous in your counting about what makes up a team for us.
\n\n\n\nAmong those teams, a minimum of about 35 meetings a week are held, plus more for working groups. That doesn’t take into account the things most people are aware of externally. It doesn’t take into account the big quarterly or annual activity things like WordPress software releases or any of our events. When those sorts of things do happen, there’s a bit of an increase in our activity.
\n\n\n\nI work 40 to 60 hours a week on WordPress, depending on what’s going on, to make sure that I know what’s happening now; so that I have insight into what the next three to five years will bring. All of that is in support of the WordPress community, which I define as anyone who has ever interacted with WordPress ever, regardless of whether they know it or not. In case you’re feeling a bit lost right now, we can shorthand that entire context as this is really big and really complex.
\n\n\n\nGiven that giant scope, it makes sense that people wonder what the work looks like. So I’ll talk about it in three big chunks: what I focus my time on, what I focus my attention on, and what helps me balance my decisions.
\n\n\n\nSo first, what I focus my time on. I spend about a quarter of my time in meetings, mostly with current contributors, project leadership, and community members. I spend another quarter of my time in WordPress community outreach, checking in with current folks, reaching out to future WordPressers, and checking in with people that I haven’t heard from in a long time to make sure that I know what they need and if there’s anything that I can do to help. After that, I spend a bit under 15% of my time each on writing/communications work or ad hoc project work. I then spend 10% of my time reviewing proposals, editing, communication drafts for others, and determining my stances on discussions that we’re having in tickets and elsewhere. I spend all of my remaining time planning for various goals, projects, initiatives and personally working to remove blockers for our volunteer contributors. So the bulk of my time, about 50% or more, is spent in calls with people, which makes sense if you’ve ever worked with me; personal connections with the community have been the best part of my job for a long time. Since the community is what makes WordPress so great, it’s only natural that I want to stay connected.
\n\n\n\nThe second big chunk is what I focus my attention on. I pay attention to four big pillars of work in the project. The first one is the WordPress CMS itself. So that’s the core team, accessibility, design, and many, many others. The second one is the WordPress community. And that’s the training team, everybody who is working on the Learn initiative, and the actual community team as well.
\n\n\n\nThe third big pillar that I focus on is the WordPress contributor experience, which is mostly the meta team but includes all of the teams they work with: plugins, themes, polyglots, etc. The fourth big pillar that I turn my attention to is our communication; what I am saying about the WordPress project to people outside of it and what I am helping our team reps to say about the work that we’re accomplishing for the WordPress project inside the project. In general, we have to make sure that we coordinate a big group of contributors around a common idea or a common practice as we move forward.
\n\n\n\nNow, the way I focus both my time and attention probably isn’t quite right if you’re focused on a single feature or team. And it’s definitely not right if you aren’t spending 40 hours a week in the project; what that probably looks like for you is more like an hour in a team meeting, 30 minutes or so on clarifying conversations, and any remaining time that you are able to contribute focused on the feature that you’re actually contributing to. And so, there you have it all my time and attention. That is WordPress in a nutshell.
\n\n\n\nThis brings us to the third chunk, the balance part. You might be wondering, how do I make sure I am fair and balanced in decisions that I have to make. That is something that I think about all the time, and I take very seriously. It’s hard to make decisions that might affect 2,000 people. It’s even harder when those decisions might affect 40% of the web. I know that I don’t have all the answers. And I’m fortunate enough to have 50 or 60 people in the community who offer me advice and guidance every single week. I’m in constant contact with the project lead, of course, but I also prioritize messages and concerns raised from team reps. And I always strive to understand before I try to problem solve. I don’t always get it right, but I do always work to get better. And that is the day-to-day work of a WordPress executive director.
\n\n\n\nThat brings us to our community highlight. I tweeted out into the community asking for excellent examples of Freelancer success stories, and today I’m going to share a story from Arūnas Liuiza. Their story goes like this:
\n\n\n\n“For almost a decade, freelance WordPress gigs allowed me to support myself and my family and keep my full-time teaching position at the local college, which was paying peanuts but was an awesome, meaningful, and fulfilling. I am sincerely grateful for that.”
\n\n\n\nThat brings us to our final segment of this brief podcast. The small list of big things to keep an eye out for in the next two weeks in WordPress. I only have two things this week. The first one is daylight saving time. It is that time of year where daylight saving time starts or stops at various parts in the globe. If you are a team rep here at WordPress, don’t forget to talk to your teams in your meetings in the next few weeks to decide what you’re going to do. You can move your team meeting if you want, and you can keep it where it is and see what new voices show up when it moves around for various people. Either way, make sure that you chat it out with your team and make sure that everybody understands what is and isn’t moving on your calendar. That will also be relevant to any of our brand new work-from-home folks in the middle of this global pandemic.
\n\n\n\nThe second thing to share is that there is a major release of WordPress coming up that’s going to happen on March 9th. It’s WordPress 5.7; it’s going to be a good release. We’ve been working on it since December or maybe a little bit earlier. So keep an eye out for announcements about that here on wordpress.org/news, or if you want to follow more about the developer details and the process details you can head on over to wordpress.org/core. That, my friends, is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9825\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:72:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n\n\n\n\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:35:\"Did You Know About Reusable Blocks?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wordpress.org/news/2021/02/gutenberg-tutorial-reusable-blocks/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 24 Feb 2021 19:17: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:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s: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:\"\";}i:2;a:5:{s:4:\"data\";s:9:\"tutorials\";s:7:\"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:34:\"https://wordpress.org/news/?p=9777\";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:55:\"Learn about reusable blocks in this Gutenberg tutorial.\";s: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:9:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:61:\"https://wordpress.org/news/files/2021/02/1_create_content.mov\";s:6:\"length\";s:7:\"1586076\";s:4:\"type\";s:15:\"video/quicktime\";}}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:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:66:\"https://wordpress.org/news/files/2021/02/2_convert_to_reusable.mov\";s:6:\"length\";s:7:\"2637657\";s:4:\"type\";s:15:\"video/quicktime\";}}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:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:66:\"https://wordpress.org/news/files/2021/02/3_reusable_blocks_tab.mov\";s:6:\"length\";s:7:\"1482152\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:68:\"https://wordpress.org/news/files/2021/02/4_saving_global_changes.mov\";s:6:\"length\";s:7:\"2110818\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:73:\"https://wordpress.org/news/files/2021/02/5_manage_all_reusable_blocks.mov\";s:6:\"length\";s:7:\"2310871\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:60:\"https://wordpress.org/news/files/2021/02/6_tip_name_them.mov\";s:6:\"length\";s:7:\"1498729\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:64:\"https://wordpress.org/news/files/2021/02/7_tip_place_in_flow.mov\";s:6:\"length\";s:7:\"8545345\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:7;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:66:\"https://wordpress.org/news/files/2021/02/8_tip_import_export-1.mov\";s:6:\"length\";s:7:\"5534991\";s:4:\"type\";s:15:\"video/quicktime\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:8;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:65:\"https://wordpress.org/news/files/2021/02/10_complex_layouts-2.mov\";s:6:\"length\";s:8:\"22852109\";s:4:\"type\";s:15:\"video/quicktime\";}}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:8397:\"\nCreated by Joen Asmussen, @joen
\n\n\n\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2021/02/Reusable-Blocks-featured.png?resize=585%2C329&ssl=1\")
The WordPress block editor (a.k.a. Gutenberg) comes with a feature called “reusable blocks.” They are blocks, saved for later, edited in one place.
\n\n\n\nHave you ever wanted to:
\n\n\n\n- Re-use the same snippet of text across posts and pages?
- Save complex layouts to spare you having to copy/paste from one post to another?
Reusable blocks can do these things.
\n\n\n\nLike templates, you mean?
\n\n\n\nNot quite. Think of reusable blocks as snippets of globally synchronized content that are personal to you. You can edit all your reusable blocks in one place, and any post or page you inserted that block into, get the updated version as well.
\n\n\n\nWhere you might use templates to structure your website, you can use reusable blocks to structure your content. For example:
\n\n\n\n- A testimonial on your homepage and your product page.
- A “this post is part of a series” box that you insert part-way through your article.
- A “Follow me on social media” section you can weave into the prose of your popular article.
- Complex but static blocks, such as a “Subscribe to my newsletter” box, a contact form, a survey, quiz, or polls.
Key properties are that reusable blocks are unbeatable when you want to reuse a snippet of content, edit it in one place, and have the changes propagate to every instance.
\n\n\n\nShow me how
\n\n\n\nTo create a reusable block, open the block editor and create the content you want to reuse:
\n\n\n\nNow select the content you want to turn into a reusable block, then click the three-dot “More” menu and choose “Add to Reusable blocks.”
\n\n\n\nVoilà, you’ve now created a reusable block. From now on, you can find this block, and any other you create, in the “Reusable blocks” tab in the block library:
\n\n\n\nThis is also where you can insert the newly created block on any of your posts or pages.
\n\n\n\nWhere do I edit my existing reusable blocks?
\n\n\n\nTo edit a reusable block, select it and make your edits. When you make an edit, the Publish button will have a little dot indicator:
\n\n\n\nThis dot indicates you’ve made a global change that potentially affects posts beyond just the one you’re editing, the same as when you’re editing templates. This lets you confirm the change was intentional.
\n\n\n\nAnother way to edit your reusable blocks is to click the global three-dot “More” menu and selecting “Manage all reusable blocks”:
\n\n\n\nThis takes you to a section letting you edit, rename, export, or delete every reusable block you created.
\n\n\n\nWhat else can I do?
\n\n\n\nHere are a couple of tips and tricks you can leverage to get the most out of reusable blocks.
\n\n\n\nGive them a good name
\n\n\n\nWhen you name a reusable block, you are essentially choosing your search terms, as the name is what you search for in the block library (or when you use the “slash command,” typing / in an empty paragraph):
\n\n\n\nAvoid names such as “Gallery” or “Image,” as that’ll be annoying when you just want to insert one of those. You can avoid that with a unique name, such as “My author biography.”
\n\n\n\nInsert in the best place of your content flow
\n\n\n\nOne obvious benefit of reusable blocks is that they are just blocks, just like everything else in the block editor. That means you can insert it anywhere in your content. You might want your rich author biography to sit at the top or bottom of the post, but This post is part of a series box that might sit well two or three paragraphs not to disrupt the reading flow.
\n\n\n\nA design shortcut
\n\n\n\nMaybe you created a complex layout you’re happy with, a call to action with the right image and buttons, and it took a while to get it just right. Go on and save it as a reusable block: even if you mean to insert it only to convert it to a regular block, it might still save you a minute.
\n\n\n\nTo convert a reusable block to regular (blocks, select it and click the “Convert to regular blocks”:
\n\n\n\n\n\n\n\nDesign by Beatriz Fialho.
\n\n\n\nTip: You can also find some nice patterns on Gutenberg Hub or ShareABlock.
\n\n\n\nTake it with you
\n\n\n\nNeed to move to another site? You can both export and import reusable blocks. Go to the Manage all reusable blocks section from the global three-dot “More” menu, hover over the block you want to export, and click “Export as JSON”:
\n\n\n\nThe downloaded file can be imported on any WordPress 5.0 or newer website.
\n\n\n\nTry it
\n\n\n\nCreate a draft post and play around with Reusable Blocks to see how you might start using them. You can always delete them when you’re done playing.
\n\n\n\nYou can test importing and using a small reusable block I created as an example. It’s a “Further reading” block that shows the four latest posts from the category “Featured”:
\n\n\n\n![\"\"](\"https://lh6.googleusercontent.com/33_L1WQrTxNiidm8IKcSfn7_nYjcpq5zpSzycmKliDnGzFI_hLu7yLPV1vnqWgCS7H6JtFAGEXz-AVkNBLtQQEM80VA6KUfcmj1JAoVZ5ZNMavVzlGzBPEiqiD3-eUzZSvOTYm_E\")
It might work well as a highlight in an article, giving the reader something new to read or awareness of your other content.
\n\n\n\nThe videos in this post show the reusable blocks flow in the upcoming WordPress 5.7.
\n\n\n\nDownload the block from this gist, import it to your WordPress site, then customize to make it yours.
\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:4:\"9777\";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:31:\"WordPress 5.7 Release Candidate\";s:7:\"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/02/wordpress-5-7-release-candidate/\";s: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, 23 Feb 2021 21:07:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9773\";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:374:\"The first release candidate for WordPress 5.7 is now available! 🎉 Please join us in celebrating this very important milestone in the community’s progress towards the final release! “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. […]\";s: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:\"Ebonie Butler\";s: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:3842:\"\nThe first release candidate for WordPress 5.7 is now available!
Please join us in celebrating this very important milestone in the community’s progress towards the final release!
\n\n\n\n“Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.7 is slated for release on March 9, 2021, but your help is needed to get there—if you haven’t tried 5.7 yet, now is the time!
\n\n\n\nYou can test the WordPress 5.7 release candidate in two ways:
\n\n\n\n- Try the WordPress Beta Tester plugin (choose the “Bleeding edge” channel and Beta/RC Only” stream options)
- Or download the release candidate here (zip).
Thank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.
\n\n\n\nWhat’s in WordPress 5.7?
\n\n\n\n- Robots API and Media Search Engine Visibility
- Detect HTTPS support
- Lazy-load iframes
- jQuery migrate-related Deprecation notice clean-up
- Admin color palette standardization
- Version 9.9 of the Gutenberg plugin.
Plugin and Theme Developers
\n\n\n\nPlease test your plugins and themes against WordPress 5.7 and update the Tested up to version in the readme file to 5.7. If you find compatibility problems, please be sure to post to the support forums, so those can be figured out before the final release.
\n\n\n\nThe WordPress 5.7 Field Guide will give you a more detailed dive into the major changes.
\n\n\n\nHow to Help
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.7 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nProps to @audrasjb for copy suggestions and @davidbaumwald for final review.
\n\n\n\n\n\n\n\n
Test this test that
Catch everything that you can
Before it’s live…![\"🤯\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f92f.png\")
WordPress 5.6.2 is now available!
\n\n\n\nThis maintenance release includes 5 bug fixes. These bugs affect WordPress version 5.6.1, so you’ll want to upgrade.
\n\n\n\nYou can download WordPress 5.6.2 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process.
\n\n\n\nWordPress 5.6.2 is a small maintenance release focused on fixing user-facing issues discovered in 5.6.1. The next major release will be version 5.7, currently scheduled for release on March 9, 2021.
\n\n\n\nTo see a full list of changes, you can browse the list on Trac, read the 5.6.2 RC1 post, or visit the 5.6.2 documentation page.
\n\n\n\nThanks and props!
\n\n\n\nThe 5.6.2 release was led by @desrosj. Special props to @isabel_brison and @talldanwp for helping to prepare the block editor related fixes, and @audrasjb and @sergeybiryukov for helping with other release related tasks.
\n\n\n\nProps to everyone who helped make WordPress 5.6.2 happen:
\n\n\n\naaronrobertshaw, Addie, André Maneiro, archon810, Ari Stathopoulos, bartosz777, Bernhard Reiter, Daniel Richards, David Anderson, dbtedg, glendaviesnz, hmabpera, ibiza69, Isabel Brison, Jason Ryan, Jb Audras, Juliette Reinders Folmer, Kai Hao, Kerry Liu, Konrad Chmielewski, Jorge Costa, magnuswebdesign, Marius L. J., Matt Wiebe, Mukesh Panchal, Paal Joachim Romdahl, Prem Tiwari, Q, Riad Benguella, Robert Anderson, roger995, Sergey Biryukov, Sergey Yakimov, Steven Stern (sterndata), Takashi Kitajima, tonysandwich, worldedu, Yui.
\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:4:\"9764\";s: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:\"Tue, 30 Mar 2021 04:04:13 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:\"Mon, 29 Mar 2021 15:05:35 GMT\";s:4:\"link\";s:63:\"I am uncertain of how I first came across the Meow Gallery WordPress plugin. It was a pinned tab in my browser for a while, but it has recently become one of those projects that I keep coming back to. I delight in the imagery of the Meow Apps brand, created by Japan-based software developer Jordy Meow. It has the sort of fun and artistic visuals that are often missing in the WordPress business ecosystem. This creativity also comes across in the Meow Apps plugins.
\n\n\n\nThe problem with WordPress gallery plugins is that I find a new one I want to use every other week. It is a bit of an obsession. There are so many different options that it is tough to grow comfortable with a solution before finding something new and shiny to tinker with.
\n\n\n\nSuch is the case with Meow Gallery. From the simplicity of its options to the range of layouts that the plugin provides, it has found its way onto my ever-growing list of favorite gallery-related plugins.
\n\n\n\nI also prefer the decoupled, modular nature of what Meow Apps is doing with its plugins. Meow Gallery keeps a tight focus on the gallery layout itself. Users can select an image lightbox/overlay extension separately. Meow Lightbox is recommended, of course. However, both are developed to work alongside third-party gallery or lightbox plugins. It is the sort of building-block solution that more developers in the community should embrace, ultimately offering end-users more freedom.
\n\n\n\nMeow Gallery is straightforward to use. It works similarly to the core Gallery block. When first adding images, users can drag-and-drop them directly into it or select from their media library. From that point, the experiences begin to diverge.
\n\n\n\nInstead of selecting the number of columns, whether to crop, or the image size, the Meow Gallery block automatically handles this based on the type of layout chosen. Options may change based on the layout too. The following are available:
\n\n\n\n- Tiles
- Masonry
- Justified
- Square
- Cascade
- Carousel (pro only)
- Map (pro only)
The block also offers a handful of basic animations, link options, and more. However, the gutter setting provides more control over the output. The gutter is the horizontal and vertical space between images. Users can choose between 0 and 100. Gutter spacing is the one option from the plugin that WordPress should adopt, allowing theme authors to opt-into a default and users to customize.
\n\n\n\nThe plugin also has commercial features, but they are value-added upsells instead of necessary functionality. The pro version includes extras like more layouts, new animations, and infinite scrolling for galleries with many images.
\n\n\n\nThe one off-putting issue with Meow Gallery is that it creates a custom block. Having already seen solutions from other plugin authors that extend the default Gallery block, I was hoping this plugin would go in the same direction. Extending the core block makes it easier for end-users to switch gallery plugins at any point. However, users can transform Meow Gallery blocks into Gallery blocks and vice versa.
\n\n\n\nKeep in mind that the WordPress Gallery block is also undergoing drastic changes. Currently, the plan is to make it more of a container block that houses nested Image blocks. By not extending the core block, plugin users will miss out on some of the advantages this change brings. Of course, the plugin developer could follow suit and add the same features to the project.
\n\n\n\nMeow Gallery relies on the WordPress gallery shortcode. Therefore, it will continue working regardless of whether users deactivate the plugin in the future. As a fallback, it is not a perfect solution. Users of the block editor would likely rather have it revert to the core Gallery block — the shortcode and block are not remotely the same. However, it is a bit of a compromise between showing a working gallery or nothing at all.
I suspect the reliance on the shortcode is for historical reasons. Meow Gallery existed in the pre-block era. However, the developer has managed to keep up with the times, offering support for both the block and classic 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 29 Mar 2021 21:26:37 +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:1;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"WordPress.org blog: WP Briefing: How WordPress Improves\";s:7:\"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:52:\"https://wordpress.org/news/?post_type=podcast&p=9980\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2021/03/how-wordpress-improves/\";s: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:10231:\"In this episode, Josepha Haden Chomphosy explores the WordPress release process. Tune in and learn the phases of a release and catch this week’s small list of big things.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- WordPress 5.7 “Esperanza”
- Esperanza Spalding
- Gutenberg Tutorial: Reusable Blocks
- make.wordpres.org/test
- GitHub repository
Transcript
\n\n\n\n\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nAll right, so last week, we wrapped up and shipped the WordPress 5.7 release. The release team this time around was smaller than we’ve had in the last couple of years. By the numbers, it looks really good: 66 enhancements or feature requests went in, 127 bugs were fixed, and seven versions of a Gutenberg plugin were merged and backported. If you use WordPress, you are probably aware that we have new releases throughout the year, but you probably don’t know much about the release process. There’s not really a reason to know unless you’re actively contributing to a release. For those interested in knowing more about how we improve WordPress, this week’s exploration is for you.
\n\n\n\nWe’re gonna take a look at what goes into WordPress releases and just kind of zoom our way in from the highest level. At the highest level, there are three major WordPress releases a year, plus the minor releases, plus Gutenberg releases. So if you’re following current WordPress work and future WordPress work, that’s going to get you to probably around 30 releases a year. If we zoom in one level to the release itself, a single release of WordPress takes four to five months from start to the day that we ship, and an additional four to six weeks on support and translations, and minor releases after that. If you’re looking from my vantage point, you’ll see that WordPress releases have essentially five parts, some of which happen kind of simultaneously.
\n\n\n\nThe first part is planning and includes the project lead, lead developers, design; groups like that. The second phase is the creation phase when we’re actually building the things that have to go into the CMS that involves the design, core, editor, mobile, and other teams. Then there’s this phase that I like to refer to as the distribution phase. This is mostly done by the teams that make sure that WordPress is widely distributable; the polyglots team work on translations, accessibility does some work, docs make sure that everything is documented, and training, of course, gets things ready for when we have to be able to tell people how to use the release.
\n\n\n\nThen there is the fourth phase; I really don’t think they go sequentially or in a waterfall format. The fourth-ish phase that I include, and that I tend to see, is this extending and iteration phase. It’s the phase where we see our theme authors and our plugin authors, folks who are doing support, show up and help us to make sure that WordPress is available not only widely but broadly to ensure that their audiences as theme authors and plugin authors are covered in the features that they need based on what they are using WordPress for. The fifth phase is the part of our communication that involves the community team, especially marketing, WordPressTV, and learn.wordpress.org. Basically, anyone who’s showing up to make sure that we all share what happened in the release, the features that are coming, and how that affects the users is involved in that particular phase. So five big phases of what happens over those four to five months, and then for the month or month and a half afterward.
\n\n\n\nIf we zoom in a bit more on the creation phase, each release has people who lead the work and coordinate contributor efforts during the course of the release. For any given release, hundreds of people contribute and receive credit for moving the WordPress project forward. Okay, hold on a second. Let’s pump the brakes and zoom in a bit on that. Hundreds of people work on every major release for a project that powers over 40% of the web that feels like a small number. But for the people who process the contributions in preparation for release, it’s actually pretty substantial. For every release, there is a small team of leaders who asked the hard questions. Is this a usable feature? Does this make WordPress better overall? And, of course, is this ready to ship? Some of those leaders, a smaller subset of even the leaders that we have already, are committers who actually prep and merge patches to the CMS; they don’t do all the work to create a design or write all the code. This tiny group of people processes hundreds and hundreds of bug fixes, improvements, and enhancements that have been submitted over the course of months and sometimes years. As a side note, that whole process is a little smaller, a little faster in the Gutenberg featured plugin, but the basic parts are still there. Alright, so we’ve zoomed from the big picture way into some of the finer details, and it really looks like any other project cycle. So now, I’m going to layer in the filter of open source to that process.
\n\n\n\nThere are a couple of things that make building software in an open source environment so different. The first is that the code is readily available. If you have a basic understanding of the languages, you can see the code, learn from it, and make suggestions about improving it. Second, you consider the user a co-developer in the process, which means that as long as people use your product, they will have opinions on what you shipped. This way of iterating improves WordPress and ties back to one of my favorite open source principles. The idea that with many eyes, all bugs are shallow. To me, that means that with enough people looking at a problem, someone is bound to be able to see the solution.
\n\n\n\nThis brings us to our community highlight, the segment where I share a note about contributors who have helped others along the way or a WordPress success story. This week’s highlight is from Nok in our Bangkok community. When asked to help her find her way into the WordPress community, she said, “@shinichiN who started the WordPress community in Bangkok and encouraged me to contribute, and also @mayukojpn has introduced me to the WP community team to join as a deputy. “ Thank you for sharing those two inspiring people with us. And if you, listener, have any stories that you would like to share of your own WordPress success or people that you have been so grateful to help you find your way in the project, you can feel free to email those to me at wpbriefing@wordpress.org.
\n\n\n\nThat brings us to our final segment of the WP Briefing, the small list of big things. I only have three things to share with you this week. The first one is that about a week ago, we had our first release of 2021. It was the WordPress 5.7 release, titled Esperanza. If you have not yet seen it, go ahead and update your website or check with your host and make sure that they have updated you if you’re on a managed host. And then take a listen to the artists that it’s named after.
\n\n\n\nThe second thing that I want you to keep an eye out for is wordpress.org/news. We are starting a new series of content that gets at the heart of some of Gutenberg’s basic parts; there’s a lot of change coming up in the next few releases of WordPress. And the most important thing to me is that you understand what we’re trying to change and where those changes are primarily taking place. There will be a couple of tutorials that go up there over the course of the of the next few weeks. The third item on the small list of big things is to remind you of our call for testing. As I mentioned earlier in the podcast, the users of any open source software are the code developers; the software built is supposed to make your life and work easier. When you test things and find interactions that can use a little bit of refinement or features that are not working exactly as expected, it’s incredibly helpful for us to have that information to always make sure that we’re solving problems instead of accidentally creating them. If you want to participate in the Current call for testing, you can head over to make.wordpress.org/test. Or, if you’ve been doing your own testing, you can also submit any bugs you have found in the GitHub repo, which I will share in the show notes below. So that, my friends, is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 29 Mar 2021 15:15:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"WordPress.org blog: WP Briefing: My Typical Day as WordPress’s Executive Director\";s:7:\"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:52:\"https://wordpress.org/news/?post_type=podcast&p=9825\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wordpress.org/news/2021/03/my-typical-day-as-wordpresss-executive-director/\";s: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:9925:\"In this episode, Josepha Haden Chomphosy speaks to her role as the Executive Director of WordPress. Learn about the day-to-day of her role and how it supports the mission of WordPress.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n\n\n\n\nTranscript
\n\n\n\n\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nI’ve been asked many times what the day-to-day work looks like for the Executive Director of the WordPress project. I don’t really think I’ve done a great job of answering that question. My default answer is either too broad, and I say, “I helped turn the WordPress vision into reality by supporting the community of contributors,” or way too narrow, and I start telling people what’s on my calendar. Probably no one cares about each entry on my calendar, and almost every contributor is covered by “I get things done by helping people.” So today, I invite you to join me in exploring the type of work required and the balance it takes to keep WordPress working.
\n\n\n\nFirst, some context on the weekly activity I see in WordPress, on average, 1,800 to 2,000 contributors a week, participate in conversations and tickets across the entire WordPress project in our entire ecosystem. There are about 20 volunteer teams that are each led by two to three team reps. Each of those teams actually has smaller groups that work on specific things; all told, it’s probably about 50 distinct teams. And probably quite a few more if you are very generous in your counting about what makes up a team for us.
\n\n\n\nAmong those teams, a minimum of about 35 meetings a week are held, plus more for working groups. That doesn’t take into account the things most people are aware of externally. It doesn’t take into account the big quarterly or annual activity things like WordPress software releases or any of our events. When those sorts of things do happen, there’s a bit of an increase in our activity.
\n\n\n\nI work 40 to 60 hours a week on WordPress, depending on what’s going on, to make sure that I know what’s happening now; so that I have insight into what the next three to five years will bring. All of that is in support of the WordPress community, which I define as anyone who has ever interacted with WordPress ever, regardless of whether they know it or not. In case you’re feeling a bit lost right now, we can shorthand that entire context as this is really big and really complex.
\n\n\n\nGiven that giant scope, it makes sense that people wonder what the work looks like. So I’ll talk about it in three big chunks: what I focus my time on, what I focus my attention on, and what helps me balance my decisions.
\n\n\n\nSo first, what I focus my time on. I spend about a quarter of my time in meetings, mostly with current contributors, project leadership, and community members. I spend another quarter of my time in WordPress community outreach, checking in with current folks, reaching out to future WordPressers, and checking in with people that I haven’t heard from in a long time to make sure that I know what they need and if there’s anything that I can do to help. After that, I spend a bit under 15% of my time each on writing/communications work or ad hoc project work. I then spend 10% of my time reviewing proposals, editing, communication drafts for others, and determining my stances on discussions that we’re having in tickets and elsewhere. I spend all of my remaining time planning for various goals, projects, initiatives and personally working to remove blockers for our volunteer contributors. So the bulk of my time, about 50% or more, is spent in calls with people, which makes sense if you’ve ever worked with me; personal connections with the community have been the best part of my job for a long time. Since the community is what makes WordPress so great, it’s only natural that I want to stay connected.
\n\n\n\nThe second big chunk is what I focus my attention on. I pay attention to four big pillars of work in the project. The first one is the WordPress CMS itself. So that’s the core team, accessibility, design, and many, many others. The second one is the WordPress community. And that’s the training team, everybody who is working on the Learn initiative, and the actual community team as well.
\n\n\n\nThe third big pillar that I focus on is the WordPress contributor experience, which is mostly the meta team but includes all of the teams they work with: plugins, themes, polyglots, etc. The fourth big pillar that I turn my attention to is our communication; what I am saying about the WordPress project to people outside of it and what I am helping our team reps to say about the work that we’re accomplishing for the WordPress project inside the project. In general, we have to make sure that we coordinate a big group of contributors around a common idea or a common practice as we move forward.
\n\n\n\nNow, the way I focus both my time and attention probably isn’t quite right if you’re focused on a single feature or team. And it’s definitely not right if you aren’t spending 40 hours a week in the project; what that probably looks like for you is more like an hour in a team meeting, 30 minutes or so on clarifying conversations, and any remaining time that you are able to contribute focused on the feature that you’re actually contributing to. And so, there you have it all my time and attention. That is WordPress in a nutshell.
\n\n\n\nThis brings us to the third chunk, the balance part. You might be wondering, how do I make sure I am fair and balanced in decisions that I have to make. That is something that I think about all the time, and I take very seriously. It’s hard to make decisions that might affect 2,000 people. It’s even harder when those decisions might affect 40% of the web. I know that I don’t have all the answers. And I’m fortunate enough to have 50 or 60 people in the community who offer me advice and guidance every single week. I’m in constant contact with the project lead, of course, but I also prioritize messages and concerns raised from team reps. And I always strive to understand before I try to problem solve. I don’t always get it right, but I do always work to get better. And that is the day-to-day work of a WordPress executive director.
\n\n\n\nThat brings us to our community highlight. I tweeted out into the community asking for excellent examples of Freelancer success stories, and today I’m going to share a story from Arūnas Liuiza. Their story goes like this:
\n\n\n\n“For almost a decade, freelance WordPress gigs allowed me to support myself and my family and keep my full-time teaching position at the local college, which was paying peanuts but was an awesome, meaningful, and fulfilling. I am sincerely grateful for that.”
\n\n\n\nThat brings us to our final segment of this brief podcast. The small list of big things to keep an eye out for in the next two weeks in WordPress. I only have two things this week. The first one is daylight saving time. It is that time of year where daylight saving time starts or stops at various parts in the globe. If you are a team rep here at WordPress, don’t forget to talk to your teams in your meetings in the next few weeks to decide what you’re going to do. You can move your team meeting if you want, and you can keep it where it is and see what new voices show up when it moves around for various people. Either way, make sure that you chat it out with your team and make sure that everybody understands what is and isn’t moving on your calendar. That will also be relevant to any of our brand new work-from-home folks in the middle of this global pandemic.
\n\n\n\nThe second thing to share is that there is a major release of WordPress coming up that’s going to happen on March 9th. It’s WordPress 5.7; it’s going to be a good release. We’ve been working on it since December or maybe a little bit earlier. So keep an eye out for announcements about that here on wordpress.org/news, or if you want to follow more about the developer details and the process details you can head on over to wordpress.org/core. That, my friends, is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 29 Mar 2021 15:15:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"WordPress.org blog: WP Briefing: Talking Full Site Editing with Matías Ventura\";s:7:\"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=10013\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wordpress.org/news/2021/03/talking-full-site-editing-with-matias-ventura/\";s: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:31281:\"In this episode, Josepha is joined by Matías Ventura, also known as “the spark behind the vision of Gutenberg.” Josepha and Matías discuss full site editing and answer your questions, from “is full site editing a standalone plugin?” to “will full site editing break my current site?”
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nCredits
\n\n\n\n- Editor: Dustin Hartzler
- Logo: Beatriz Fialho
- Production: Chloé Bringmann
- Song: Fearless First by Kevin MacLeod
References
\n\n\n\n- Twenty Twenty One theme
- Word Camp Central America
- 2Q21 Listening Hours with Matt Mullenweg and Josepha Haden Chomphosy
Transcript
\n\n\n\n\n\n\n\nHello, everyone, and welcome to the WordPress briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha [0:41]: This month, we have a bonus briefing, so I’ve asked my dear friend and colleague Matías Ventura to join me. Matías was recently called “the spark behind the vision of Gutenberg.” With full site editing coming our way in 202, I asked if he would join me for a quick Q&A. Welcome, Matías.
\n\n\n\nMatías [0:56]: Hello, hello! Thanks for inviting me. It’s a pleasure to be here.
\n\n\n\nJosepha [1:00]: Well, I’m delighted to have you. And I think that we have a lot of excellent questions. All right, so Matías, we actually ended up with questions in about three different groupings. And so I’m going to start with the “what is it about full site editing,” sorts of questions that people had. We’re gonna work our way into “what are we doing with it?” and then “how are we planning on getting this out the door?” Then, a couple of big picture questions that people asked. We’re just gonna leap right in this full site editing part of the Gutenberg plugin, or is it a standalone plugin?
\n\n\n\nMatías [1:39]: Okay, we’ll start with the basics. Full site editing is part of the Gutenberg plugin right now. I think it’s important to mention that full site editing is like an umbrella for several projects that we’re working on. They are all aiming to bring blocks into more parts of your site so that editing becomes easier and more expressive, and so on. So full site editing right now encompasses adding a ton of new blocks. I think we have around 20 new blocks coming in, including navigation query, site, title, logo, etc. There’s also the interface to interact with templates outside of the content; that’s another big part of the full site editing project. We also have a lot of new design tools included, many of these have been released in previous major releases, but they still comprise a strong part of what full site editing is. We also have something called Global Styles, which aims to allow people to configure the visual aspects of blogs across the entire site, not just on any individual blog. And of course, then there’s a whole layer of how we utilize these tools. It can get complex because there are many layers and projects that need to come together. So yeah, all of these are accessible through the Gutenberg plugin right now.
\n\n\n\nJosepha [3:07]: Yeah. So it’s not a standalone plugin. If you wanted to check out full site editing the site editor experience as it is now, you would just have to make sure you had the Gutenberg plugin on your site. Right?
\n\n\n\nMatías: Yes, correct.
\n\n\n\nJosepha: So a couple of the questions related to this are how exactly do I enable it on my site? And what is the easiest and safest way to try this on my site? And I think the answer is, is right in there. It’s in the Gutenberg plugin. And so if you have that plugin, you don’t need the testing plugin or anything else to make that work, right?
\n\n\n\nMatías [3:51]: No, you like, you might need to install a theme like Twenty Twenty One blocks that unlock some of these new interfaces that we just talked about. Like other of these pieces are available for anything. But some of these, like the interface to edit templates, right now only talk with things that know how to express their desire.
\n\n\n\nJosepha [4:14]: And I think we have less than 10 themes right now that do that, but I’ll leave some links to at least 2021 blocks in the show notes. And then, if there are another one or two themes that I can find, I can add those in there as well.
\n\n\n\nSo you have to have the Gutenberg plugin; you have to have a theme that works with that site editor kind of experience. And then you’re safe to try everything out. It shows up in your left toolbar just like any other thing, like if you were working with plugins, or if you were adding a post or anything else, right?
\n\n\n\nMatías [4:51]: Yes, correct. And so, some of these details are being worked on right now. Like how and where you access things, and so on. These things are subject to change, but right now, you have this site editor beta in the sidebar when both you have the plugin running and a theme that’s capable.
\n\n\n\nJosepha [5:10]: Yeah. Excellent note. If you are running this on a production website, I would recommend you not do that unless you are very, very good with WordPress. It’s a really safe and easy thing to test and try out. But because it is still in beta, I recommend always putting it on a test site. I have a couple of different test sites that I run on myself. Another question that I had was, “will full site editing slow down my site?” And I think we have some refreshed performance tests coming out about that. And maybe they’ll be out by the time we publish this podcast.
\n\n\n\nMatías [5:49]: Yeah, I mean, like the performance has been one of the major focuses for the whole project. In many cases, it should speed up things because we’re like, I think one of the big pieces that these projects bring into the picture, especially for themes, is that it allows only the necessary assets to be loaded on the front end. For example, if for a given page, there are, I don’t know, 10-15 blocks being used, you would only get the CSS and scrapes and so on related to those blocks. This can cut down on a lot a ton of CSS that themes used to end queue on a side, particularly if you were trying to customize many widgets and so on, like a lot of themes have the full styles or multiple widgets, even third party plugins, and so on. So one of the advantages of having this blog system is that we can know at the time of rendering what blogs are being used and only load those assets.
\n\n\n\nJosepha [6:50]: Excellent. Another big question that we have is, “does full site editing work with the classic editor? And does it work with other builders?” I think that’s a really big answer if you’re going to get super deep into it. But I think that the short answer is yes, it does. Is that fair?
\n\n\n\nMatías [7:08]: Yeah, I don’t think it touches a bit on that full site editing is not like a single thing. There are multiple projects around it. So again, like the template editor that only deals with blogs, it doesn’t have a lot to do with a classic editor. But the classic editor use for both doesn’t change anything at all; like the same way that when the block editor was introduced, it didn’t change how you could still write posts in the classic editor. You will still be able to do that.
\n\n\n\nJosepha [7:41]: And if you are brand new to WordPress person, or, I mean, I guess at this point, you don’t have to be super brand new. If you’re fairly new to WordPress person and have no idea what we’re talking about when we say the classic editor, you don’t really have to worry about it either. You don’t have to go and find out what that is; the block editor that you have right now works perfectly for what you’re trying to do. So if you don’t know what I mean when I say classic editor, don’t worry about chasing it down either.
\n\n\n\nI think that this last question we accidentally answered earlier, but I’m going to go ahead and ask it anyway since I received it. “I keep hearing that you can use the site editor with the 2021 theme. But I don’t seem to be able to. What am I missing?” I think the answer is that there’s the Twenty Twenty One theme shipped with the WordPress release 5.6. And then there is the Twenty Twenty One blocks theme; those are two different themes. The link to the Twenty Twenty One block theme is going to be in our show notes this time around. And so, if you have been trying to use the full site editor with Twenty Twenty One and not succeeding, try the link to the one below. And I bet that that will work for you.
\n\n\n\nMatías [8:50]: Yes, that’s correct.
\n\n\n\nJosepha [8:51]: All right, excellent. Well, that brings us kind of into our second set of questions, which is about how we are doing it. The first one that folks have is “will full site editing be on by default in the next release. In this context, the next release is WordPress 5.8. But I think it’s a safe question to ask if full site editing will be on by default in the release that it’s planned for.
\n\n\n\nMatías [9:15]: Yeah, and for this, I need to go back to the same principle of many projects because there are many pieces of full site editing, and we have been merging them in major releases, particularly like the blocks and the design tools. There are more coming in that we want to make accessible as soon as possible. The full experience that requires a theme to opt-in to templates using blogs won’t be by default; it requires a specific theme running. A lot of these details we’re still like determining exactly what projects are ready to be merged and so on. But yeah, if you have a theme right now that works the way you want, it doesn’t change anything there. If anything, it adds some more capabilities and more customization tools, and so on. And the theme can also regulate how much they want to incorporate.
\n\n\n\nJosepha [10:13]: Matías, you’ve mentioned a couple of times in this podcast so far like this is a really complex and really complicated part of this work. And just for anyone out there who’s either encountering Gutenberg or full site editing or this podcast for the first time, I think a tiny bit of context that’s worth having here is that Matías and I have been working on this together in various capacities for like, five years. And Matías has probably been working on this for practically a decade. So, when we say that this is a really complicated problem, and when we say that this is a complex set of issues that we’re working with like, it is all that we have been thinking about for I want to say at least the last three or four years, but certainly it’s all that we have been trying to untangle for quite a bit of time before that as well. So we don’t take it lightly when we’re like, “this is complicated;” we mean it. It’s really complicated. And we’re trying our hardest over here as WordPress.
\n\n\n\nThe next big question, since we’re all stuck in the “it’s very complicated,” part of things is the question, “will this update break my current site?” Like, if I have a site that is updated and ready, and it’s exactly as I wanted it to be, and it took me two years to get there will full site editing, whichever release it’s in. Currently, 5.8 is what we’re planning for. Will that break anything on my site as I know it right now?
\n\n\n\nMatías [11:44]: No, not at all. One of the major things that the WordPress team, the WordPress community, always cares so much about, never to break things. Many of these things are stepping stones that you can adopt, as we’ve talked about full site editing. But for example, we also have a few concurrent projects around the widget screen and the navigation screen that are meant to bring blocks into existing interfaces. So again, the theme doesn’t need to change, and a lot of care is being put into making this more like you’re unlocking new features, and nothing really breaks or falls apart.
\n\n\n\nJosepha [12:23]: This update, like all the other updates, should have minimal, minimal impact on what you have to actively fix on your site. Every once in a while, a bug is gonna get by. We can’t say that we’re 100% perfect with not breaking things. But also, we always and I and I know that we’re planning on this for our remaining releases for the rest of the year. At the very least, I can’t imagine we’d ever change it. But after every major release, we always make a plan to have a minor release within the next one or two weeks. Because we know that a broken thing on a site is really incredibly impactful, even if you’re only 1% of the sites that had that happen to it. And so I think that’s true in this case, too. And getting that feedback back from all of the people who are actually using WordPress is the thing that makes us be able to kind of move quickly when we do see those problems.
\n\n\n\nOne of the questions that we have been getting is, “can I see a live preview without saving the changes that I made?” When I got this question, I didn’t actually understand it. And so I went and looked at a site without the Gutenberg plugin on it, and then a site with the Gutenberg plugin on it. And of course, on sites without Gutenberg, without the block editor, without full site editing, when you are looking to preview, you have the option to open up your preview in a new window. And you don’t have that with Gutenberg because it’s supposed to be a true WYSIWYG editor. A true what you see is what you get, editor. I think that the answer to this is, yes, you can see a live preview without actually saving the changes on the front end of your site. But you don’t actually have to reload anything. You don’t have to open it up in a new window. You don’t have to, like, actively click “please show me a preview” because what you see in your editing screen should be what you see at the end of your app as an end-user.
\n\n\n\nMatías [14:28]: Yeah, that’s the sort of the main gist to it. Yes, the site editor is built so that it always reflects the front end as truly as possible, so that’s one layer. Also, the preview tools should allow you to see in different devices like mobile breakpoints, and I don’t know if they will have breakpoints and stuff like that. There are a lot of things in the current interface that is just not enabled. There are some challenges in the sidebar. Because the site editor is not just focused on a single post, it’s focused on the entire site. So, there can be many, many changes that need to be shadowed for the site.
\n\n\n\nIf you’re changing the site title, some of the global styles, aspects, and so on need to be orchestrated. So, to see in the previewing new window, there are some challenges there to integrate. Again, the interface is not final yet; a lot of these things are still being tweaked and improved. There are many things from the regular post editor that are not enabled yet. But they will be enabled. So yeah, it’s a, I guess, it’s not a simple thing to answer. Because, again, the idea of previewing the site that’s core to the whole project is that you’re always interacting in the same way that when you’re in the customizer, you’re seeing the preview all the time. That’s the main scope of this project,
\n\n\n\nJosepha [15:54]: Excellent. Changes like that changes to your workflow can be really hard to get your mind around, especially if part of that existing workflow was there to create some confidence in what you’re seeing with your users. And so I understand. Now that I’ve researched that question a bit, I see where that’s coming from. Based on existing workflows and existing patterns that we have for ourselves in WordPress, will we need to have a theme to use the full site editor?
\n\n\n\nMatías [16:33]: I think we’ve already covered some of these. And again, they are tools that can work on any existing theme. There is other stuff that needs space-specific themes to opt-in into these tools, like blog templates and so on.
\n\n\n\nJosepha [16:50]: Yes, I think the question that we have next, because I see that the literal next question I have is actually something we have covered; just because we’re being pretty conversational about it, not because anyone already asked the question. So I’m actually going to skip to the last question of this section that I received. I got this next one via Twitter. The question is, “how do you view the role of themes once full site editing is fully rolled out and all the page elements (content, headers, widgets, footers, etc.) and all the views are managed via blocks and block patterns? Will things become typographic and block styles?”
\n\n\n\nMatías [17:28]: I think this is a great question because it goes to the heart of, why are we doing all this. One of the main reasons is to empower users more. WordPress has been democratizing publishing for a while; this is another step into allowing themes to get more customization tools and more control over their site if they want to. I think the recent call for testing has focused on the 404 page, for example. That’s something that forever has been locked away from users. And it’s also something that, as a theme developer, and I used to develop themes a long time ago, that was one of the things where you decide what sort of approach you take for the 404 page. Maybe sometimes you want to have something more whimsical. Sometimes you need something more serious. And committing to one when you can have such a diverse and broad user base can be challenging. With these, it becomes as easy as offering a few different patterns for that template. Then the user will always be able to change the copy and modify something. So again, it opens up a lot of these things that used to be locked down. However, from a theme perspective, I think this doesn’t reduce the theme at all. If anything, it allows the theme to focus less on coding and functions and more on design expression and aesthetics. I don’t think that would ever be exhausted. That will always remain as diverse as humans are interacting with WordPress. And so it’s not that I don’t see it’s just as like, typographic and block styles. How do you express a template, how do you express the structure, what choices you quote, what choices you make as a theme builder? And of course, there are many degrees of control there. Because a site maintainer may not want the 404 template to be editable, that sort of control will always be present.
\n\n\n\nJosepha [19:38]: Yeah. And really fast. I have to add a caveat to a thing that you said in there. For anyone who’s listening keenly, you may have heard Matías say that the users can update any of the content there – any of the copy. In this context, we’re talking about users as in the people who are maintaining the site, not people who are visiting your site. Visitors to your site will not be able to change any copy on your page unless you’ve done something very interesting with your WordPress site, which is also fine if that’s what you prefer to do. By default, your visitors can’t change everything on your website, which is good news, frankly.
\n\n\n\nSo I’ve got one logistics question, which I’m happy to take. And then one is kind of a big picture question that I also got from Twitter. “What about the classic editor block; what is going to happen to that? And when will we know?” So ages and ages ago, before COVID? I think so. Probably maybe a couple of years ago, Matt said that the classic editor plugin would be supported through the end of 2021. And that is still the case; there will be active support on that through the end of 2021. After that, it will not be actively supported anymore. It won’t be removed from any place that you can get access to right now. In a “this is the end of its lifecycle” sort of way, we just won’t have anyone who is currently committed to maintaining that plugin anymore. So that’s what’s happening at the end of the year. And yeah, at the end of 2021. The big question that we have is, “why is full site editing being so rushed?” I think this is a bit of a loaded question.
\n\n\n\nMatías [21:32]: Yeah, I think I think it’s still a fair question, though. I think we’re dealing with two things here. And one is ensuring that we release things in the best state possible. And also, some of the urgency is to offer tools that we know that people lack right now and that could really benefit from. Making that determination is very tricky. The full site editing project has been in the works for the last couple of years. If we count the initial phase of Gutenberg, that’s four to five years. We’ve been doing many calls for testing, which I think have been super useful to catch issues and reflect as a community on where things are going; how do we integrate with these? How do we use it? What are the shortcomings? What do we need to do? Based on all of these, we’ll continue to make decisions on when things become ready. We’re not committed to releasing something that’s not in a good state. And I think we will always be very careful about that. There are these two competing senses of the urgency – of getting some of these tools out, and because it also benefits from the feedback loops. I always say that, in many ways, the initial phase of Gutenberg, to me, is not finished. We took the initial two years to do the 5.0 release, the initial block editor, and so on. But, it’s still being improved at a very fast pace, among all the recent major releases improvements to the editor were included; that will continue to be the case. In many ways, phase one is not finished. And the moment we choose to release some of these tools or editing tools, it won’t be finished either. They will need to continue to grow, mature, and incorporate a lot of the feedback. Even the things that the ecosystem is building around. I’ve seen a few themes already that are incorporating a blank canvas template so that you can use them in some pages and take over and do everything with blocks. So even the community and ecosystem as a whole is also sort of paving the way for what needs to come.
\n\n\n\nJosepha [24:06]: I think from my perspective, and of course, I’m on the people side of things, the communication side of things, the logistics side of things; I have a frequently a very different view from what a lot of other folks are seeing. And so from my side of things, I have to say, I’m communicating about this change in a really broad way, which has not been happening since 2019 when we started the work. We’ve been communicating broadly with the WordPress community, but not with everybody who uses WordPress. So, I think that for a lot of people, this looks like a project that we started really actively working on in the last six months or so. And now we’re just racing toward a finish line. I think that there’s, there’s not been a lot of awareness of everything that’s gone into it. And so, on the one hand, it feels a little less rushed to me knowing the full length of the history on this. But also, as you said, I really think that this gets a bunch of tools to people who otherwise have not been able to accomplish these things in WordPress or otherwise. I am so anxious to get something to people who really can benefit from this change the most. And it’s the nature of the open source, right that like, one, as long as you have users, you’re going to have stuff you have to fix in your software. So we’re never really, really going to be done with this; there’s not going to be like a done point of WordPress. And the second thing is, I think it’s generally true that you don’t really start getting full user feedback until after you have launched your major release. I think that we see that a lot in open source software; you can bring in as many people as you think you can in your user tests heading up to it. And in your accessibility tests. And, in general, quality assurance tests. You can bring in a lot of people and still not have gotten the full understanding of the various niche use cases that your users will bring to you. Because at this point, we’re like 40% of the web. And that means that we’re serving this majority collection of increasingly minority voices and niche voices in the space. And so, a little bit I feel a sense of urgency; I feel a bit of anxiousness about trying to get this out there for one, to get the tools in the hands of the people who can benefit the most from them, but also so that we can start really getting the full stress test of this software out and get that feedback in so that we can really build something responsive to what our users need our long tail, “anyone who ever uses WordPress ever,” definition of users. And so, that’s why I feel a sense of urgency around it. Even though you know, as I said, you and I have been working on this for like five years, and you’ve been working on it for a decade or something. I actually don’t know how long it’s been worked on.
\n\n\n\nMatías [27:35]: Now that makes me feel a bit old.
\n\n\n\nJosepha [27:40]: Nobody makes Matías feel old. He is a lovely, wonderful colleague. Sorry, Matías, If I made you feel old.
\n\n\n\nMatías [27:46]: No, that’s totally fine. I also want to add that full site editing is not like a single toggle that’s going to drop into a major release. So I think that’s important to consider, I think this entire year is going to see a lot of these tools being, and sometimes the sort of the end-user is not the, again, the site maintainer. Still, you can also be the theme developer; I think there are many tools that would be empowering for theme developers to use. Again, we mentioned there are like five to ten themes, block themes right now. That needs to grow a lot, and that only grows through these sorts of feedback loops. And the theme community pushing things forward and seeing where things can lead to. I’m very excited about the pattern directory integration because I think that can also combine with blog themes in very powerful ways. Imagine if, I don’t know many of these patterns that are very common on the web and very needed, that if we can refine them together with a second community and make them available across themes, you can combine a header from one theme with a content of another; all these sorts of mixtures could happen. All of this needs exploration, the creativity of the entire community, and so on. In that sense, getting all these tools, even if it doesn’t immediately change anything for like the site itself, starts to unlock a lot of things.
\n\n\n\nJosepha [29:27]: I’m going to take a bit of your answer from there and tie it all the way back to your first answer that we had when you joined me today. And say, I think you’re absolutely right. We have a set of users in our theme authors and our plugin developers as well that we desperately need to get looking at this set of tools. I hope that what we are shipping in the first iteration of this serves as an opportunity for all of those theme authors and agency owners, plugin authors, WordPress site configurers freelancers. Like, I really hope that this puts it into a really accessible, easy-to-access space for them so that they can do those experiments based on what they know their users need the most. They are the group that has the closest access to site maintainers. And what they need compared to, for instance, me or a potential you like we have a lot of information, you and I, we do a lot of tests, we have a strong sense of what is needed at the moment, but we don’t have as a close connection that our theme and agency and plugin folks all have. And so that’s another part of why I’m so excited to get this out in the current iteration of it.
\n\n\n\nJosepha [31:04]: That was a lot of questions in a little bit of time. This is going to be officially my longest WordPress briefing. Matías, I am so glad that you were able to join me today. And I think that everyone’s going to be really, really excited to hear your answers to these questions.
\n\n\n\nMatías [31:23]: Thank you for having me.
\n\n\n\nJosepha [31:25]: All right, my friends. That brings us into our small list of big things. I’m going to skip our community highlight today just because we had a slightly longer word press briefing in our bonus iteration today. But the small list of big things. The first thing is WordCamp Central America is coming up on April 15; there is a registration link in the show notes that you can access your tickets with. I recommend that you go; we’ve got a lot of excellent speakers coming up there and a lot of good content and good training and learning for y’all. The second thing is that Matt Mullenweg and I have listening hours coming up with the community in the first week of April. I’ll add the link to register for those in the show notes as well; it’s just a few minutes for you all to stop by, check-in, see what’s going on, and share some celebrations or concerns with us. And I hope that I see you there.
\n\n\n\nSo that my friends is your small list of big things. Thank you for joining in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy. I’ll see you again in a couple of weeks!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 29 Mar 2021 15:05:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Chloe Bringmann\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"Gutenberg Times: New Gallery Block, Convert Blocks, Business News and more Weekend Edition #164\";s:7:\"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=17347\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://gutenbergtimes.com/gallery-block-convert-blocks-business-weekend-edition-164/\";s: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:21372:\"Howdy,
\n\n\n\nDespite the new spread of the coronavirus in Europe and the problems around vaccinations, I am quite hopeful to be able to travel again in the second half of the year and visit the homeland after two years. Patience is a virtue.
\n\n\n\nToday, we have a full roster of content for developers, content creators, theme authors, implementers and contributors. Again I am awed by the astonishing creativity in the WordPress space!
\n\n\n\nRemember, you don’t need to read it all in one sitting. It’ll keep the whole week!
\n\n\n\nYours 💕
Birgit
Full-Site Editing + Themes
\n\n\n\nWPTavern has a podcast again! The WordPress Juke Box. For the inaugural episode host Nathan Wrigley interviewed. Among other things, Josepha Haden Chomphosy talked about her benchmark for the Go/NoGo decision to merge Full-Site Editing into core for the 5.8 release in July. Find additional thoughts in my post: Full-site Editing MVP: Can I Build a Landing Page?
\n\n\n\n\n\n\n\n
Anne McCarthy posted the fourth call for testing: Building a restaurant themed header, with instructions to use columns, navigation block and other features for the header template part.
\n\n\n\n\n\n\n\n
There is a lot of movement on the Gutenberg Repo and the Themes Team keeps a list of relevant issues and discussions for theme developers. Maggie Cabrera published the round-up post Gutenberg + Themes: Week of March 25, 2021. It’s an excellent reading list if you need to dive deeper in the upcoming changes for your theme or your customer. One of the issues caught my eye: the discussion and work around block alignment settings for themes. The current way predates the revamp of the Inner Blocks. There is some work to be done, streamlining the styling for themes. Join the discussion on GitHub.
\n\n\n\n\n “Keeping up with Gutenberg – Index”
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. The index 2020 is here
Refactor of the Gallery Block, using image blocks.
\n\n\n\nIf you love to take a sneak peek at the new version of the Gallery block, heed the call for testing by Glen Davies: Gallery Block Update – Call for Testing. The refactored version is now using single image blocks inside the Gallery block. You can us all the great features: individual links per image, block styles, choices for size and editing capabilities. If you also use a plugin with your site, like CoBlocks, you can still apply the great filters and animations to your gallery block. In his post, Davies walks you through the few features and asked to test all the many facets of the new Gallery block.
\n\n\n\nOn the WPTavern, Justin Tadlock explains how this new change can make a lot of difference on how gallery layouts will be built. Among other ideas, he pictures that among images, a Pull Quote block could be added. Refactoring Gutenberg’s Gallery Block To Support Nested Images.
\n\n\n\nI posted my first impression as a comment and created a bug report on GitHub when my images lost all their styling when I added the gallery block to a group. I suggested making it possible to apply block styles to more than one image at a time, and that the gallery block / image block copies the respective Alt texts from the media library. Both suggestions made it into the project board.
\n\n\n\nBlock editor for content creators
\n\n\n\nLiam Dempsey asked his Twitter followers for recommendation of Block plugins. He collected all the suggestions in this blog post: Community Recommendations for Gutenberg Blocks in WordPress.
\n\n\n\n\n\n\n\n
Amie Suzan at at Virfice reviewed the Blocksy Theme and gives 18 Unavoidable Reasons to Build Sites With It. The theme received some attention after Chris Lema revamped his site using the block editor it now runs on the Blocksy theme. Justin Tadlock at the WPTavern also found the Blocksy theme to provide a solid block editor experience
\n\n\n\n\n\n\n\n\n\n\n\n
Anders Norén published a new free theme in the WordPress Repository, named Eskell, inspired by the Swedish graphic designer Olle Eksell. In his introduction to the theme, Andres wrote: “(…) the star of the show in Eksell is the archive page, which features a masonry grid of posts and a category filter that updates the grid with posts from the selected category without a hard reload.” In includes full color settings and dark mode for devices that support it. He continues: “The Blank Canvas Template hides everything on the page except the blocks you add to the Block Editor content. That gives users the freedom to create entirely custom pages, with whatever blocks they want. It feels like a little preview of what we’ll be able to do once Full Site Editing is merged into WordPress Core.”
\n\n\n\nJustin Tadlock published a review Eksell theme creates art with blocks and a follow-up article on the WPTavern.
\n\n\n\n\n\n\n\nShould you switch to the block editor?
\n\n\n\nBenjamin Intal from Stackable posted Why You Should Switch to the Gutenberg WordPress Editor. He wrote: “In this article, we enumerate some reasons why the Gutenberg WordPress editor might be your new primary choice for page building. Read on, and we might just convince you to give Gutenberg another shot.”
\n\n\n\n\n\n\n\n
WordPressVIP post takes us Behind the scenes of News UK’s rampant speed to value. News UK is the powerhouse behind some of the UK’s most famous news, media, and lifestyle brands. Its reach ranges from the highly respected the London Times to the hugely popular Sun. In the more detailed case study, you’ll learn from the editor’s perspective how the usage of the block editor has streamlined content production, increased productivity and fosters a culture of innovation between teams.
\n\n\n\n\n\n\n\n
On the WPBuild podcast A-Z of WordPress this week, Nathan Wrigley and David Walmsley tackled the letter G – Gutenberg. If the early controversy in 2018 had you shy away from trying it out, but now you heard so much positive about it, this episode will give you an update on how people are using the block-editor now and what’s in store for 2021.
\n\n\n\n\n\n\n\n
Let Allie Nimmons of WPBuffs tell you Why and How to use the WordPress block editor. It’s an excellent introduction and tutorial with dozens of links to learn more.
\n\n\n\n\n\n\n\n
For those of us who are worried about migrating a ton of content from classic editor and short codes to block editor, Darshan Sawardekar, lead web engineer at the web agency 10up, has good news. This week, he announced the release of the Convert to Blocks plugin. Convert to Blocks converts your content to blocks on the fly and those changes will be saved when you update the post. It’s not a Bulk Converter, it only converts content once it is opened in the block editor.
\n\n\n\n\n\n\n\nA couple of months ago, the WPTavern published the article How To Bulk Convert Classic WordPress Posts To Blocks?. Justin Tadlock listed two more plugins for the purpose: Bulk Convert to Blocks (still in development) and Bulk Block Converter, last updated a year ago. We used it at a recent project and it worked very well.
\n\n\n\nBusiness News around Gutenberg
\n\n\n\nExtendify
\n\n\n\nWPTavern has the scoop: Extendify recently aquired plugin EditorPlus and joined forces with Munir Kamal and his team around Gutenberg Hub. Back in November 2020, they also acquired Redux Framework, and hired its creator, Dōvy Paukstys, part-time.
\n\n\n\nPlugins now owned by Extendify:
\n\n\n\n\n\n\n\nPeople behind Extendify
\n\n\n\nChris Lukbert and Artur Grabowski, co-founders of Extendify, are former Automattic employees. So is Tammie Lister, Extendify’s Head of Design. Lister has been a major WordPress contributor on the Gutenberg block-editor as co-lead since the beginning in 2017. She participated in one of our first Live Q & As in November 2018 with her Gutenberg co-leads Joen Asmussen and Matias Ventura. You can also read more about Lister on HeroPress: Discovering Your Place.
\n\n\n\nGoDaddy
\n\n\n\nGoDaddy is sponsoring George Mamadashvili to contribute on the WordPress Gutenberg project full-time. Mamadashvili was one of the developers behind the cool blocks published under the brand of SortaBrilliant in 2018 and 2019. Recently, he released Toggles, an accordion block for FAQs, and other use cases. You can also use it to hide spoilers in Movie or Book reviews.
\n\n\n\nDeveloping for the block editor
\n\n\n\nMatt Watson published his 5th tutorial Create a Customizer Panel using Gutenberg Components for developers. You should read his previous posts before tackling this one.
\n\n\n\n- Creating a Plugin for the Block Editor
- Using Options to Store Data in the Block Editor
- Add Entry Points to the Create-Block Script
- Create a Settings Page using Gutenberg Components
\n\n\n\n
On WordPressTV you’ll find Chris van Patten‘s The Ultimate Beginner’s Guide to the Gutenberg Data API. The Data API is how you get data in and out of Gutenberg, track changes across blocks, and execute events around the editor.
\n\n\n\n\n\n\n\n
The WordCamp India presentation by Grzegorz “Greg” Ziółkowski Block Development with scaffolding helps you get started building a single block plugin with the create-block-script.
\n\n\n\n\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
![\"GitHub](\"https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge\")
WordPress Events
\n\n\n\nApril 6, 2021 9 am EDT / 14:00 UTC
WPCafe: Building the Twenty Twenty-One with Caroline Nymark and Mel Dwan-Choyce, live on YouTube
April 6, 2021 9 am EDT / 14:00 UTC
WPCafe: Building the Twenty Twenty-One with Caroline Nymark and Mel Dwan-Choyce, live on YouTube
April 15, 2021 6:30 pm EDT / 23:30 UTC
South Florida Mega Meetup “New Site Builder Edition”
April 15 – 17, 2021
WordCamp Centroamérica 2021
April 27 and 28th
Expand 2021 – a virtual event hosted by GoDaddy that brings the web design and developer community together to share ideas and experiences, make connections and support each other.
May 24 – 27. 2021
WordSesh 2021
Speaker submissions are due on Monday! (March 29th)!
\n\n\n\n
On the Calendar for WordPress Online Events you’ll find a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\n\n\n\n\n\n\n\n\n\n\n
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 27 Mar 2021 20:30: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: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:5;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"WPTavern: WordPress to Drop Support for IE11 in Upcoming 5.8 or 5.9 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:30:\"https://wptavern.com/?p=114416\";s:7:\"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:195:\"https://wptavern.com/wordpress-to-drop-support-for-ie11-in-upcoming-5-8-or-5-9-release?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-to-drop-support-for-ie11-in-upcoming-5-8-or-5-9-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:3258:\"
In early March, WordPress contributors began discussing the possibility of dropping support for IE11 in the near future after usage fell below ~1%. This week, the discussion’s facilitator, Héctor Prieto, confirmed the majority of participants are in agreement to move forward and set a timeline for discontinuing support. Contributors are now considering either the 5.8. or 5.9 release.
\n\n\n\n“The argument for dropping in 5.8 is to realize the change and improvement quicker, while others are inclined to wait until 5.9 to provide a longer window between the official announcement and the effective date,” Prieto said. The final call is up the the 5.8 release team, which has not yet been identified.
\n\n\n\nThe release scope and schedule hinges on whether or not the April go/no-go conditions are met for including full-site editing in the merge for 5.8 (July 2021) or 5.9 (December 2021). Teams for 5.8 will be finalized in April/May, and they will decide how to proceed for discontinuing IE11.
\n\n\n\nJb Audras suggested that if 5.8 release leads elect to drop support for IE11, he could work with other contributors to update the BrowseHappy notice in one of the upcoming minor versions.
\n\n\n\n“Even if the BrowseHappy notice can be updated independently from Core releases, I think it’s better to update alongside a release, to give better visibility to this change,” Audras said.
\n\n\n\nMicrosoft 365 apps and services will no longer support IE11 beginning August 17, 2021. Drupal recently went through a similar process of deciding to drop IE11 support with the upcoming Drupal 10 release, anticipated in June 2022. Those who have to use IE11 retain the option to remain on Drupal 9’s LTS release until the end of 2023. Participants in the discussion cited many of the same considerations now facing WordPress contributors.
\n\n\n\nMatt Mullenweg commented on the preliminary discussion to suggest giving IE11 users a path forward if they land on wp-admin using an unsupported browser:
\n\n\n\n\n\n\n\nSupportive of dropping support, and if someone visits on an explicitly dropped browser like IE11 showing them a friendly message saying why wp-admin is not accessible and next steps they can take.
The technical implementation is being discussed in the ticket Riad Benguella created to discourage IE11 usage and WordPress’ projects and teams will begin examining the practical implications of dropping support.
\";s: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, 26 Mar 2021 23:32:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:6;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:95:\"WPTavern: 10up Creates Classic Post Migration Route With Its Convert to Blocks WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=114406\";s:7:\"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:235:\"https://wptavern.com/10up-creates-classic-post-migration-route-with-its-convert-to-blocks-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=10up-creates-classic-post-migration-route-with-its-convert-to-blocks-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3803:\"Yesterday, 10up officially announced Convert to Blocks, a WordPress plugin for transforming classic posts into blocks. The goal is to provide users with a safe migration route for old content while removing the burdens of other options in the space.
\n\n\n\nI briefly mentioned this plugin in an article covering bulk conversion in the Ask the Bartender series. However, I could not recommend it to most users because it was hosted on GitHub, a site that is geared toward developers. With it now officially in the WordPress plugin directory, it is a much more user-friendly option.
\n\n\n\nMost conversion options either convert posts in bulk or through a manual process, such as the user clicking a button. Bulk converters can be problematic at a large scale simply because there is no reliable way for users to check the success of each post’s conversion to blocks. Of course, users could check these posts individually, but that is impractical when dealing with more than a few dozen posts.
\n\n\n\nBulk converters are also done so in conjunction with a database backup. It is sensible to do this when altering large amounts of content at once just to be on the safe side.
\n\n\n\n“We saw a space for a third way — a solution that eliminates editors stumbling upon Classic blocks and needing to know how to convert them, while also holding back on content transformation until content needs to be modified — at which point it is also, typically, checked again on the front end of the site,” wrote Darshan Sawardekar, a 10up lead web engineer, in the announcement.
\n\n\n\n“That’s where the idea for Convert to Blocks came into play. It began as a creative engineering solution to mitigate risk and improve content mapping. Its success inspired the development and public release of the plugin to help others facilitate safe content migrations to the WordPress block editor.”
\n\n\n\n10up’s solution is a bit of a middle ground. It only converts a post when a user enters the editing screen for it. From that point, the user can check whether the conversion looks correct, fix any problems if they arise, and save the post.
\n\n\n\nEssentially, it works the same as the default convert-to-blocks options in WordPress without the manual step.
\n\n\n\nFor many users, this is the ideal solution. Because classic content works the same as it always has on the front end, it is unnecessary to convert it unless the need to edit the post also arises.
\n\n\n\nConvert to Blocks also adds a new column to the manage posts screen named “Editor.” It lists whether the post content was created with either the block or classic editor, providing users with an at-a-glance look without checking posts individually.
\n\n\n\nLike other plugins, Convert to Blocks uses the core transformation feature, which is an imperfect solution. Depending on the content of the post, the conversion will sometimes throw an error. That is why bulk solutions are often problematic. With this plugin, users will know immediately upon editing a post if there is an issue.
\n\n\n\nGiven the plugins available today for converting classic posts to blocks, this would be my top choice. It focuses on transforming to blocks where it matters — during the editing process — and removes some manual work for the user.
\";s: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, 26 Mar 2021 16:01:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"WPTavern: Free Software Community Condemns Richard Stallman’s Reinstatement to FSF Board of Directors\";s:7:\"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=114253\";s:7:\"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:245:\"https://wptavern.com/free-software-community-condemns-richard-stallmans-reinstatement-to-fsf-board-of-directors?utm_source=rss&utm_medium=rss&utm_campaign=free-software-community-condemns-richard-stallmans-reinstatement-to-fsf-board-of-directors\";s: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:7505:\"GPL author Richard Stallman announced this week that he has rejoined the board of the Free Software Foundation (FSF), which he established in 1985, and is not planning to resign a second time:
\n\n\n\n\n\n\n\n“I have an announcement to make. I’m now on the Free Software Foundation Board of Directors once again. We were working on a video to announce this with, but that turned out to be difficult, we didn’t have experience doing that sort of thing so it didn’t get finished but here is the announcement. Some of you will be happy at this, and some might be disappointed, but who knows? In any case, that’s how it is, and I’m not planning to resign a second time.”
In 2019, Stallman resigned as director of the board and president of the FSF, and was subsequently ousted by GNU project maintainers from his position as head of the project. Calls for his removal were precipitated by Stallman’s controversial remarks on rape, assault, and child sex trafficking, along with two decades of behaviors and statements that many have found to be disturbing and offensive. His return came as a shock to the free software community, though some suspect he never really left.
\n\n\n\n“I did not support the decision to reinstate RMS,” former FSF board member Kat Walsh said after resigning from the board yesterday. “I made my arguments and placed my opposing vote; while I was glad I was able to do that I regret not being able to turn the decision the other way.
\n\n\n\n“I wish the organization well; my departure is not a rejection of the ideas of free software, only a belief that my role in the organization was no longer the best way to put them forward into the world.”
\n\n\n\nStallman’s reinstatement came with a staggering lack of transparency from FSF’s board of directors and has triggered a cascade of condemnation from individuals and organizations across the tech industry. Among the many critical responsibilities it maintains, the FSF currently holds the copyrights to enforce the GPL.
\n\n\n\nThe Open Source Initiative published a statement this week, calling for Stallman’s removal from FSF’s leadership:
\n\n\n\n\n\n\n\nThe Open Source Initiative calls upon the Free Software Foundation to hold Stallman responsible for past behavior, remove him from the organization’s leadership and work to address the harm he caused to all those he has excluded: those he considers less worthy, and those he has hurt with his words and actions. We will not participate in any events that include Richard M. Stallman and we cannot collaborate with the Free Software Foundation until Stallman is removed from the organization’s leadership.
Red Hat announced that it is suspending all funding of the FSF and any FSF-hosted events. Mozilla joined the Open Source Diversity Community, Outreachy, and the Software Conservancy project in supporting an open letter that calls for the removal of the entire Board of the Free Software Foundation, along with the removal of Stallman from all leadership positions, including the GNU Project. The letter states that the undersigned do not acknowledge Stallman’s leadership of the FSF and do not condone his actions and opinions:
\n\n\n\n\n\n\n\nThere has been enough tolerance of RMS’s repugnant ideas and behavior. We cannot continue to let one person ruin the meaning of our work. Our communities have no space for people like Richard M. Stallman, and we will not continue suffering his behavior, giving him a leadership role, or otherwise holding him and his hurtful and dangerous ideology as acceptable.
The petition has been signed by more than 2400 free software advocates. Notable signatories include Molly de Blanc (Debian Project, GNOME Foundation), Elana Hashman (Debian Technical Committee Member, Open Source Initiative Director, Kubernetes SIG Instrumentation Chair), Neil McGovern (GNOME Foundation Executive Director, Former Debian Project Leader), and Luis Villa (Former Director of the Open Source Initiative and the GNOME Foundation; contributor to the GPL v3 drafting process).
\n\n\n\nThe Electronic Frontier Foundation (EFF) published a statement urging the voting members of the FSF board to call a special meeting to reconsider Stallman’s reinstatement, in support of the “long-term viability of the free software movement:”
\n\n\n\n\n\n\n\nFree software is a vital component of an open and just technological society: its key institutions and individuals cannot place misguided feelings of loyalty above their commitment to that cause. The movement for digital freedom is larger than any one individual contributor, regardless of their role. Indeed, we hope that this moment can be an opportunity to bring in new leaders and new ideas to the free software movement.
Stallman still has many staunch supporters, as more than 2,000 people have signed an open letter in support of him and his leadership. They contend that removing RMS “will hurt FSF’s image and will deal a significant blow to the momentum of the free software movement.”
\n\n\n\nStallman is still listed among the FSF’s board of directors, but the board appears to be reorganizing. A preliminary statement on upcoming changes to the board’s governance said they are moving to adopt a transparent, formal process for identifying candidates and appointing new board members. The board intends to require existing board members to submit to this process as well “to decide which of them remain on the board,” with a deadline of 30 days to complete the changes.
\n\n\n\nBy allowing Stallman to resume his position, the FSF squandered the opportunity it had to redefine itself following his resignation in 2019. The organization missed the chance to carve out a new future that would be free from his damaging influence. If the board doesn’t act in the best interests of the greater community, by remedying its lack of transparency and accountability, it may permanently resign the organization to irrelevance.
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 26 Mar 2021 05:46:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"Gutenberg Times: Full-site Editing MVP: Can I Build a Landing Page?\";s:7:\"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=17337\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://gutenbergtimes.com/full-site-editing-mvp-can-i-build-a-landing-page/\";s: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:6562:\"Josepha Haden Chomphosy was the featured guest on the inaugural episode of the WPTavern Jukebox podcast, hosted by Nathan Wrigley. In their conversation, they covered a lot of ground. The show is definitely worth your 40 minutes of listen.
\n\n\n\nAround minute 23 of the audio they talked a bit more about Full-Site Editing and its merge into the core. Chomphosy said she knows ‘this summer’ is an ambitions goal, and she also assured the listeners that the team won’t release something that’s not functional and usable.
\n\n\n\nGo/NoGo Mid to End of April
\n\n\n\nThe Core release and Gutenberg teams will make the Go/NoGo decision to merge Full-Site Editing for the next WordPress release in July (5.8) on April 17 or on April 23. In other words, the state of Full Site editing in Gutenberg plugin version 10.4 and 10.5. If it doesn’t get merged into 5.8, Full-Site Editing will be merged in WordPress 5.9 to be released in December 2021
\n\n\n\nChomphosy also shared her – unofficial – benchmark of what should be possible with the prototype of the Site Editor by April: Can you – without writing code – create a landing page with Full-site editing tools. She calls it “the smallest viable sentence. The I-AM of websites.”
\n\n\n\nA Landing page is the smallest viable unit
\n\n\n\nThis single web page consists of a header, a footer, a hero image with a button, some text, a form or a call to action. This narrows the focus of the MVP, the prototype, considerably. It also increases the probability that the first low-key, opt-in version of Full-Site editing might actually make it into the next WordPress version. A narrow scope will also help content creators, teachers and developers get started working on their discovery of the new WordPress feature. As soon as it is merged into WordPress core, plugin developer and theme builders can test their ideas against it and get familiar with the underlying concepts.
\n\n\n\nIt’s a good way to ease-in content creators, too. When you are not dealing with the header and footer of a big site, but just for a single page, it’s not so critical if you get lost on the way from content editing to template part (header, footer) editing and back again. It’s all on the same page, literally.
\n\n\n\nThis transition was one of the major causes of confusion during the first few testing calls for the FSE outreach program and the developers are working on making it less confusing. With this unofficial benchmark of a single landing page creation, the team will have additional time and input on how to better handle that switch between editing a template that is used for many pages and the content of a single post or page content.
\n\n\n\nA very tangible goal, “Can I build a landing page with the tools available?” makes it straightforward for WordPress contributors who work on the parts that make that are not code, like documentation, marketing, training and testing.
\n\n\n\nCall For Testing: Create a Header
\n\n\n\nThe 4th call for testing via the WordPress FSE-Outreach program asks you to create a header for a Restaurant. Anne McCarthy has detailed instructions for you as well as video if you are in a testing mood. Your input is definitely wanted!
\n\n\n\nChomphosy also added that Matias Ventura, the technical lead for Gutenberg, might have different benchmarks for the MVP. I am curious, and answer Josepha’s call for questions on Full-Site Editing for her next episode of the WPBriefing podcast when Matias will be her guest.
\n\n\n\nFull-Side Editing project encompasses a lot more than the Site Editor with template parts. There are Global Styles, Widgets in Customizer, a new Navigation and Widget screen, block-based themes with a theme.json file and query block. Some of it will work its way into the MVP. We will see how far the team progresses on their journey, that will only begin once Full-Site editing comes to Millions of WordPress users. No Fear, though. It will all be opt-in. Nothing will break.
\n\n\n\n“Given enough eyeballs, all bugs are shallow” — Eric Raymond’s Linus’ Law
\n\n\n\nTake a deep dive into
\n\n\n\n\n\n\n\n\nWith the release of Editor Plus 2.7 in recent weeks, Extendify stamped its brand name on the plugin. The company officially acquired the plugin months ago. However, this was its first public outing as the new owner of a project that has seen a steady uptick in its popularity, recently surpassing 5,000 active installations.
\n\n\n\nExtendify was busy in late 2020. The company quietly purchased the Redux Framework in November. Dōvy Paukstys, the creator, remained on board part-time with the financial backing needed to continue the project. In December, Extendify joined forces with Munir Kamal and his team behind Editor Plus and Gutenberg Hub.
\n\n\n\n“Our mission is to turn WordPress into a superpower for entrepreneurs around the world,” said Extendify co-founder Chris Lubkert. “As you know, despite its unrivaled popularity, many users still struggle to use WordPress to create the site they need. We see tremendous potential to empower WordPress users to create a Gutenberg-native website in a few clicks. By bringing together Redux, Editor Plus, and Gutenberg Hub, we have the foundational pieces to create a world-class onboarding and site-building experience.”
\n\n\n\nThere are no plans to build a “super” plugin that combines Editor Plus and Redux. Gutenberg Hub will continue providing resources to help users leverage the block editor.
\n\n\n\n“Currently, the Redux template library and the library in Editor Plus are separate,” said Lubkert. “But we are heavily investing in making the Extendify library the best solution for users and eventually plan to introduce this to the Redux user base as well.”
\n\n\n\nExtendify’s first public act as Editor Plus’s owner was not to introduce new features in its recent major-release, version 2.7. Instead, users were presented with a limitation on features they previously had access to for free.
\n\n\n\nVersion 2.7 limits the template and pattern inserter, introduced in 2.6, to three imports. Beyond that, users must upgrade to one of the Extendify Pro paid tiers. The single-site option is $99 per year with an introductory rate of $49. The unlimited sites tier is $299, and it currently has a $149 limited-time offer.
\n\n\n\nAt first glance, it seemed like a cash grab from new owners. There were no public announcements or explanations for the change outside of a minor note in the plugin’s change log — just new ownership and upsells. Lubkert said he plans to rectify this by publishing an announcement post next week.
\n\n\n\nExtendify had already been involved with new feature development for months. The API behind the template inserter was coming from their server in Editor Plus 2.6. It was the groundwork for Extendify Pro, but it was also still under development.
\n\n\n\n“We’re a small, nimble team, and it was a development timing issue,” said Lubkert. “We finished the library approximately three weeks before we finished paid plans, and we certainly didn’t want to delay users getting their hands on the library while we finished up work on Extendify Pro.”
\n\n\n\nUsers will not lose any previously-imported templates. However, importing anything beyond three additional templates in Editor Plus 2.7 or newer will require a purchase of Extendify Pro for an API key.
\n\n\n\n“We are now offering an added layer of value for users who want to benefit from the power of Editor Plus but may not be in a position to use it to create their site from scratch,” said Lubkert. “For those users, we are creating the most beautiful and effective Gutenberg-native templates, built with Editor Plus, as part of the Extendify Pro template library. As you know, we launched the initial beta version a few weeks ago. A subscription is required for unlimited access to the library, but all users can import any three templates or patterns for free.”
\n\n\n\nWith the launch of the template inserter in 2.6, there was no public mention of it being a beta version.
\n\n\n\nTemplates and patterns from Gutenberg Hub remain free. Users can still browse the site, copy a template code snippet, and paste it into the block editor.
\n\n\n\nThe team removed the custom blocks extension in Editor Plus 2.7.1, released earlier today. This feature allowed end-users to copy blocks from the Gutenberg Hub block library, paste them into the plugin, and save them for use on the site. Users could also add custom blocks via this settings screen.
\n\n\n\n“The custom block feature in Editor Plus was an experiment that was pretty cool, actually,” said Lubkert. “However, [Kamal] suggested removing it from Editor Plus since it is now very similar to the reusable block functionality in core. We want Editor Plus to push the envelope of what is possible with Gutenberg, and having a duplicate feature that is available in core doesn’t add real, incremental value for our users.”
\n\n\n\nUpdating to 2.7+ will also likely deactivate the plugin for end-users. The primary plugin filename changed from index.php to editorplus.php. Developers should generally avoid doing this because WordPress uses this filename to determine if a plugin is active.
I remain optimistic about Editor Plus’s future now that it has the financial backing it deserves. Having been an early supporter of the project, I knew this day would come. Nearly every time I spoke with Kamal in the past, I asked him about plans for monetizing the product. It had grown beyond what one developer could reasonably handle and scale without a business plan in place.
\n\n\n\n“We agree with your sentiment that WordPress projects need to generate revenue in order to fund the development of truly transformational experiences,” said Lubkert. “We have been investing in our team as well. Tammie Lister joined us as Head of Design. We’ve also added engineering, support, and QA team members.”
\";s: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, 25 Mar 2021 21:44: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:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"WordPress Foundation: 5 tips for organizing a successful online do_action charity hackathon\";s:7:\"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:41:\"https://wordpressfoundation.org/?p=182733\";s:7:\"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:107:\"https://wordpressfoundation.org/2021/5-tips-for-organizing-a-successful-online-do_action-charity-hackathon/\";s: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:6491:\"In 2020, unfazed by the COVID-19 pandemic, community organizers rallied together and worked hard to give a WordPress-powered web presence for charities through online charity hackathons. Our passionate and resilient community members are pulling out all stops this year to continue the good work. We already have two applications for do_action events in the queue, with more in the pipeline! This post aims to encourage all our zealous organizers with tips on how best to organize successful online do_action charity hackathons.
\n\n\n\n- Recruit a core team and prepare an event plan
Enlist a team of 5-10 members to wrangle the event. Much like a WordCamp, organizers need to plan do_action events down to the last detail. Make sure you have a plan for the entire event lifecycle – including selecting nonprofits, finding volunteers, finding sponsors, task management, and execution. For inspiration, check out how the do_action Japan team came up with a plan for the event beforehand! Having a solid communication strategy and setting deadlines is equally important. Finding answers to questions like: “When do volunteer teams meet?”, “How often should there be check-ins?”, “How do we track tasks?”, “How do we measure progress?” and “ What deadlines do we need to meet?” for instance, will help in devising a strategy. - Finding non-profits and volunteers
Finding eligible non-profits for your event could be a challenge. When your event publishes the call for non-profits, share it widely on social media. Since this is a charitable event, we have noticed that getting PR from local news media outlets is a lot easier. You might also want to reach out to Non-profit organizations and offer assistance proactively. You can follow the same approach for volunteer recruitment too. - Fix your collaboration tools and communication strategy
Since this will be an online event, you will need the right collaboration tools to make the event successful. Please note: A doaction.org G Suite/Google Workspace account will be provided to all do_action event organizers in 2021 and beyond! Feel free to use that account for all your needs. Check out the handbook page for more information. Here are some tools that you can use for your event:- doaction.org website (call for nonprofits & hackathon participants)
- Slack (overall event prep, communication on the event days) – A free plan will be sufficient.
- Zoom (event organizer & inter-team meetings, opening/closing remarks) – WordPress Community zoom accounts can be used.
- Google Workspace tools (provided to all 2021 organizers in the location@doaction.org format) – Gmail (inquiries & sponsor communication), Google Forms (call for organizers & sponsors, post-event survey), Google Sheets (task & data management), Google Docs (collaborative editing of documents, Google Drive (for storage needs), and Google Slides (opening/closing remarks presentation)
- WordPress.com P2 – for task management
- Trello – for task management.
- Figma (design)
- Finding sponsors
For online do_action events, organizers need not worry about venue or catering expenses. Hence, sponsorship benefits for these events can be passed along directly to non-profits. Most WordPress companies are passionate about supporting non-profits, and providing product/service licenses is a cost-effective way for them to support the community. Consider reaching out to specific companies as per your needs. Sponsorship benefits that do_action events in 2020 had availed include:- Free domain and web hosting for non-profits
- Sponsored premium plugins and themes (Only 100% GPL Compliant themes and plugins are allowed)
- Sponsored website services (backups, caching, security, optimization, etc.)
- Find a way to offer post-event support for non-profit websites
Make sure that once the event is over, each non-profit is trained on how to use and update the site. Perhaps a few volunteers could provide post-event support for a short while (while ensuring that the right expectations are set on both sides). Offering post-event support as a sponsorship benefit could also be a solution to that problem.
Does all of this sound exciting? Would you like to support your local community by organizing a do_action event? Send in your application right away! You can read more about do_action in the event handbook. Thank you for all that you do to support the global community through WordPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 25 Mar 2021 03:50:25 +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:\"Hari Shanker\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"WPTavern: #1 – Josepha Haden Chomphosy on the Past, Present, and Future of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://wptavern.com/?post_type=podcast&p=113869\";s:7:\"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:211:\"https://wptavern.com/podcast/1-josepha-haden-chomphosy-on-the-past-present-and-future-of-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=1-josepha-haden-chomphosy-on-the-past-present-and-future-of-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:50139:\"About this episode.
\n\n\n\nThe podcast today features Josepha Haden Chomphosy.
\n\n\n\nJosepha is the Executive Director of the WordPress project, and as such, she has been at the forefront of WordPress’ evolution for many years. For the last six years, Josepha has worked full time on the project, and has been the release lead, as well as being involved with community events.
\n\n\n\nMany of the WordPress updates that you’ve seen recently have been under her stewardship, and she’s heavily involved in the project’s roadmap, and so talking with her about the past, present and future of WordPress seemed like the perfect topic.
\n\n\n\nBriefly, the points discussed are:
\n\n\n\n- Josepha’s discovery of WordPress and its community;
- how she considers that community in the many decisions she needs to make to push the project forward;
- who can be involved and how one can join in;
- the release of Gutenberg and how the turbulence of its introduction into WordPress core led her to rethink how the community is involved in such releases;
- the concern that contributors are sometimes working in ways that are not sustainable;
- how Josepha wants to ensure that contributors have the tools that they need to do their work; and
- how she wants to leverage LearnWP to make it easier for WordPress’ growing audience to make the most of the software.
If any of the points raised here resonate with you, please leave a comment below.
\n\n\n\nIf you have any thoughts on what we should include in future episodes of the podcast, please go to the podcast contact form and tell us what you think.
\n\n\n\nMentioned in this episode.
\n\n\n\n- Josepha’s ‘Big Picture Goals 2021’ post
- Site Editing Milestones
- Making WordPress Releases Easier
- WordPress Contributors Discuss Scaling Back Releases: “4 Major Releases Is Not a Viable Plan in 2021”
- The first episode of Josepha’s podcast, WP Briefing
- Josepha’s personal blog
Welcome to the first edition of the WP Tavern podcast, which we’re calling Jukebox. My name is Nathan Wrigley and as this is the first ever episode of the podcast, I’m going to spend a few moments, setting your expectations. Our aim here is to create a podcast and transcript for people who are interested in WordPress and the WordPress community.
\nAs a starting point, we’re going to produce one episode each month, but that may change down the road. We’re not bound to any particular subject, so it might be an interview with a core contributor one time and an organizer of WordCamps the next. A panel discussion about a broad subject, such as the future of WordPress or an episode about a very specific topic.
\nAs I say, we’re not bound to anything except that it’s going to have WordPress at its heart.
\nWith that in mind, it would be great to receive suggestions from you, the audience. I’d like to hear from you directly about what you’d like the podcast to feature. That may be a topic that you’re curious about, a person that you’d like to hear from or anything else that comes to mind.
\nYou can do that by going to wptavern.com forward slash contact forward slash Jukebox. And there you’ll find a form to complete. Once again, that URL, wptavern.com forward slash contact forward slash Jukebox, and thanks in advance to anyone who reaches out.
\nOkay. So the podcast today features Josepha Haden Chomphosy. Josepha is the executive director of the WordPress project. And as such, she has been at the forefront of WordPress’ evolution for many years. For the last six years, Josepha has worked full time on the project and has been the release lead as well as being involved with community events.
\nMany of the WordPress updates that you’ve seen recently have been under her stewardship, and she’s heavily involved in the project’s roadmap, and so talking with her about the past present and future of WordPress seemed like the perfect topic. We talk about her discovery of WordPress and its community and how she considers that community in her decisions. Who can be involved and how. We also get into the subject of Gutenberg and how the turbulence of its introduction into WordPress core led her to rethink how the community is involved in such releases. Towards the end, we discuss how, in the future, Josepha wants to ensure that contributors have the tools that they need to do their work and how she wants to leverage LearnWP to make it easier for WordPress’ growing audience to make the most of the software. If any of the points raised here resonate with you be sure to head over and find the post at wptavern.com forward slash podcast, and leave a comment there. And so without further delay, I bring you Josepha Haden Chomphosy.
\nI am here with Josepha Haden Chomphosy. Josepha, welcome to the podcast.
\nThanks for having me, Nathan.
\nYou’re very welcome. Now it strikes me, it is possible that there are some people out there in the WordPress community who don’t actually know who you are and what your role is. So the first question is exactly that. Could you tell us a little bit about yourself and what your role is in WordPress?
\nYeah. Well, my name, as you mentioned is Josepha Haden Chomphosy, and I am the executive director of the WordPress project. And, I help to make sure that whatever the vision is of the technology and the community and the ecosystem around it has everything that it needs to succeed, and so I look after the people who are here contributing, and I look after the tools that they need in order to contribute, and of course, look after all of our products, our events in person and online, as well as our CMS and all of the kind of design and stuff that goes into it.
\nSo quite a lot. Yeah, quite a lot. About that, what do you find yourself doing on a day-to-day basis other than coming on podcast episodes like this? What typically would you find yourself doing in a normal week?
\nYeah. In a normal week, I probably have about 50% of my time is taken up with meetings either in voice or video or on Slack, and a huge amount of my time is helping to make decisions from like the medium to large scale of things. And so, yeah, it’s a lot of talking to people, making sure that I know what they need, making sure that I know how to get them what they need once we get there. And yeah, it’s mostly, I guess, mostly my job is talking, planning and solving problems, which frankly sounds like a fun job to me. I realize not everyone.
\nNo, that sounds good to me. Did you start with WordPress a very long time ago? Is this something you’ve been doing for a really long time? In other words, what’s your path? How did you get to where you are now from where you first made contact with a CMS called WordPress?
\nYeah, I think at this point I’m technically considered a WordPress veteran, but I actually have not been in the project for as long as some people have. I first discovered, learned the word WordPress in 2009. My mom actually introduced me to the CMS. In 2010, I started, my local community with a couple of other folks in Kansas City, and then it kind of all grew from there. I actually have been, I just recently passed my six year anniversary with being a full time sponsored contributor through Automattic. So yeah, I think that makes me technically a veteran of WordPress. Matt and I were talking about that during WordCamp India this past weekend.
\nYou obviously liked the sort of the FOSS model that we’ve got in the WordPress community. I don’t know if you have a history of working in industry or something like that. Is this the kind of community, the kind of decision-making process that speaks to you where there’s an open way of doing things, which can be different to a more top down approach in business.
\nYeah. I came into WordPress and into leadership probably from a pretty unusual path. And so there’s that to start with. I’m not a natural born leader. I spent a lot of time learning how to do it. And as I was learning all about how to lead the way that made the most sense to me from the start was leading from within and leading from whatever seat you happen to occupy in your group at the time. And so it’s a lot of this concept of servant leadership and a lot leading groups as they exist as their own organism, as opposed to top down, just like trying to manage them. I really love group dynamics and leading mass groups of people. It is a particular passion of mine. And there are times when you do have to just say, I’m sorry, everyone, I know that this doesn’t make us happy, but we’ve got to do this because we must do this for the health of our organization or whatever it is, you know, like mask mandates to be terribly topical.
\nIn my experience of working with nonprofits and volunteering during the course of my life. There was no other leadership style that really was as sustainable and resilient and brought people into the organization as much as this kind of style of leadership that I have now. And it happens to fit really, really well in open source and for the most part also fits really, really well in WordPress. So I guess I kind of just got lucky.
\nYeah, it’s a really nice community to be in. And it occurs to me that many people that interact with WordPress will, well, I say many people, I don’t know what the figures would be, but they would go and download the software let’s say from wordpress.org and upload it to their server, and they’re good to go. That’s their relationship with WordPress. They’re happy with that. They use it. New features come out and they’re delighted. It’s great. New features come out and they’re kind of concerned and that’s great. How do things actually get done though? How is the project moving forward? I suppose it boils down to who makes the decisions, but also what is the consultation approach? How does the consultation occur to iterate the project forward? Because I suspect there will be many people listening to this who will have, no conception of how that’s done or how the software got to where it is today, as opposed to two years ago.
\nYeah. I’m going to answer that question in two parts. The first part I’m going to take is how are these decisions generally made? And that part comes with a big caveat of… in a perfect situation, this is how this will occur. And then the second thing that I want to address in there is the question of how it probably should happen, especially for open source at scale as WordPress is.
\nSo to answer the first part. The way that I always want it to work. And the way that when things are optimally occurring, these decisions should be made. A good idea can come from anywhere. And so anytime that a contributor brings a good idea to their team rep or to me, or to a trusted fellow contributor, and they want to get an idea of whether it would succeed or not. There is historically this idea of feature proposals, which we do in some of our teams right now, but not in all of our teams where that idea gets a review from the full community, or however many people are showing up on the blog at the moment. And after they’ve had a bit of a conversation figured out the rough parts figured out what the solution, what the problem is they’re trying to solve what the users most beneficial way forward would be, once they figure all those things out, then they bring it to in a lot of cases, Matt, in a lot of cases, me, and then we figure out based on feedback from team reps and committers and major maintainers and contributors, what are the things that we need to know about these proposals to make sure that we get the right decision in place. That is how it should work if everything’s optimal right now, there are a lot of places where people don’t feel like they are able to raise their voice for questions. There are a lot of places where there is not enough support either from the volunteers who are showing up or just from the concept of the overall roadmap, where the people aren’t there to help make the, make it past that first hurdle of, someone help me figure out if this is a good idea. For the 40% of the web that we’re supporting. And so that’s how it should work optimally. It doesn’t always work perfectly well. In cases where anyone gets a proposal or a suggestion that is, has not been discussed in their community, and hasn’t been discussed in the project and we have to kind of figure out ad hoc, what is the right way forward here?
\nI actually do have a number of the people that I personally speak to, to get advice on the best way forward. I’ve got some technical people who’ve been in the project for ages that I look to for advice. I reach out to some of the industry partners. I hesitate to call WordPress an industry. For some reason. The WordPress ecosystem sustaining partners, we have folks like the people over at SiteGround or Yoast or depending on who I need to talk to any other sort of company that fits in with the questions that I have, and then a bunch of our long-term community maintainers, people like Andrea Middleton or folks like that who can make sure that I understand what all of our benefits are, what all of our risks are, what all the hurdles are like. It’s been a long time since one person could do all of this work, reliably alone. And so I make a strong use of a bunch of really dedicated contributors, I would say people who are really looking out for the community and I reach out to them quite frequently.
\nAs far as how it should go in the future, I do think that most of the lessons in the cathedral and the Bazaar, which is kind of the canonical source of how to do open source were written for much smaller projects than we are. And so I think that, there’s a feeling right now in the community of there is this cathedral and it’s not the community, the community is the Bazaar.
\nAnd on the one hand, I think that is true. Like the community itself does represent this beautiful chaotic kind of crackling energy sort of thing that we have. But I actually think our community, as small as it is compared to the number of users that WordPress has is actually that central part of what makes WordPress successful and functional. And the bizarre is actually all of those users that we don’t have any access to. Access to… that sounds really weird. We don’t have any way to talk to predictably right now. And so I think that we are due for a change in our mindsets around that it is, a one percenter thing to be able to contribute to an open source project. And we should not be forgetting that we are building this on behalf of a huge portion of the population,
\nOne of the things which seems to crop up from time to time is exactly what you’ve just mentioned. That the user base is enormous, but the community of people who are actually building it is obviously much smaller. And whether there’s a disconnect, in some instances between what the, as you described, the 1% might feel is required, and the Bazaar, if you’d like what they feel is required. And I really, struggle to understand how on earth one would communicate between those two different sides of the coin. If you liked it, we really want you to understand that this is what we’re proposing, this is what we feel is the future for WordPress, but how do we join those two streams together? Over here, the cathedral over here, the bazaar, and I just don’t even know how to square that circle and imagine that’s an enormous challenge.
\nYeah, it is. So, reconciling the question of building for all of our users versus building for all of our developers or for all of our, what I call our extender community. It’s a really hard task. Every feature that gets put into WordPress, whether it’s the CMS or how we manage a team or how we put our tools together. Every single feature decision that’s made is made with the best knowledge that anybody has at that moment for one, and for two, the closer and closer you get into the really heart of the work being done on the project, the more and more that you are trying to make decisions for all of core and all of the active contributors and all of the theme authors and plugin authors and all of the users of WordPress and all of their visitors to their websites. That is a huge burden. You have to think about so many groups and the community reminds me personally of this a lot. Like it comes up frequently that, we, I’m told, don’t know who our audience is and on the one hand that’s right, we don’t literally know every single type of visitor that we have here. And every single type of thing that people are building using WordPress. And on the one hand, like that’s the beauty of it is that we don’t have to know who you are to want to give you the freedoms of open-source. And on the other hand, it does really bring up a lot of, for a lot of people, some ethical questions of, should we be making decisions on behalf of other people. But I honestly, Helen said it in a core chat a few months ago, when you are making software, you’re always making decisions on behalf of other people.
\nEven if you do know exactly who you’re talking to. And so it’s not necessarily possible to talk to all of our audiences at the same time and it’s definitely not possible to make all of our audiences, all of our users happy in one go, but the blizzard community pretty famously many, many years ago said we serve a majority group of minority voices and we will always make someone mad and we just want to not always make the same people mad because then we’re making blind choices or at least biased choices. I think about that often.
\nSo when decisions are made which the community, maybe 50% of them are going in one direction and 50% think actually this doesn’t seem like the right direction. Good example may be when 5.0 came along and Gutenberg, I should say Gutenberg because that’s probably more correct, was put into core that obviously there was a real bifurcation of where the community was going at that point to some extent. How do you cope with that kind of thing? How do you tackle when people are disgruntled, when people are bringing things to you where they’re dissatisfied or they believe they’ve somehow been ignored? Is it a question of saying to them, look, you just need to be involved. If you’re involved, then we know what you’re saying. How do you deal with it?
\nYeah. Well, I first have to say that I think that communities that are comfortable dissenting, are really healthy. When we see groups of people, when we see communities where people are all constantly, always agreeing and always in the same direction, it looks great on the outside, but from the standpoint of a maintainer of that community, cause I’m a maintainer of the WordPress community itself. That is a really unhealthy organization when I wasn’t hearing anything from anyone except for when they were, shouting at each other on Twitter, that was a sign of real organizational unhealth in my mind. So I think that healthy organizations are ones that are comfortable enough to say I do have worries about this. Cause if we don’t know where the worries are, we don’t know how to make solutions to avoid the worries. But I never did say to anyone and I don’t feel like the answer was well, if you’re upset about it, you should get in here.
\nI don’t think that’s a fair response, especially because like I said earlier, contributing to open source is a really, really privileged thing to do. You got to have a lot of extra time to do that. And, time is money in a lot of cases. And so I never did say that. I actually, 5.0 merge was really, really hard, that whole process and not a lot of people believed in the way forward on it. And they were raising the concerns, but this was the vision that had been set out. And so what I did was not to say, well, if you’re mad show up and do some work on things, what I did was say, Hey, I know you’re mad and I’m going to come and let you tell me how mad you are. And I actually did a six month listening tour. To hear what everyone was the angriest about. And it led up to a very lengthy 5.0 slash block editor merge retrospective post, where I had spoken to basically all of the committers, basically everyone who was writing code to create Gutenberg, everyone who was writing the core code to make sure that it was ready and a bunch of our agencies in the ecosystem, a bunch of our theme authors and plugin authors. I spoke to a ton of people over those six months just to see what they were the angriest about. And we’ve been since then making changes to fix it. It is fair that they were worried and it’s fair that they had something to say about that. And I don’t think, I never did think, that the right answer was to say, well, If you’ve got an anger, you got a job. That’s not what they were trying to tell me. You know.
\nIt seems that you’re concerned with communicating and making sure that communication out to the community is a part of your role, and although I don’t really want to go into this in great depth. You’ve recently launched a bite-size if you like, a short 10 minute to 12 minute length podcast, every couple of weeks, we’ve got two episodes so far, it’s called WP Briefing. Is that an effort from you to try and get the message out in a different way that people can consume. Bite-sized, often, easy to understand.
\nYeah. So something like this, a way for WordPress leadership to communicate more frequently, and with a little bit more ease has been on my list of goals, list of needs that the WordPress project needs since about 2018. I did not think that I was going to be the one to do it. I was hoping that we would get a more technology project sort of person available, but at the end of the day, I was talking through it with Matt, at sometime last year, sometime in 2020 and we both kind of collectively came to the decision that, yeah, it would be nice to have some technology folks. So the way that I hope that we can do open source in WordPress and the way that I hope that we can, that I can lead a group of people while always remembering their humanity and always adhering to my concept of basic ethical practices at scale. Like why wouldn’t I be the person who should show up and say, hey, this is how I think that… we can do this in WordPress. I think it’s a good opportunity for people to hear what goes into WordPress, because it’s really easy to be like WordPress is free and it’s just available by magic, and you don’t know that there are 2000 volunteer contributors that show up every single week to make that happen for 40% of the web. You just don’t know what you don’t know when you’re first getting involved in WordPress. And so like this, I think is a good opportunity to uncover all of the hard work of the community.
\nI agree. I think it’s a great initiative. I’m going to pivot the conversation slightly because we’ve had Gutenberg for several years now and we’ve got a big year ahead. There’s an awful lot going on. If you’ve been following the roadmap, you’ll understand that this year is a really, really major year. So I’m just wondering where we’re at, what is in store for this year and how you feel we’re aligned to deliver on the things that you hope in your aggressive roadmap. What’s the chances of achieving them all?
\nYeah, firstly, I do see all of the flags being raised about my aggressive timeline and my incredibly full set of goals for the WordPress project for the year, and there is a lot out there and I know tha. I am fully prepared to say that, at the end of the year, we’re going to look back and we will have missed some of those goals. And that’s going to be fine too, for a lot of things. Now, the one that is really, really raising, some eyebrows is this full site editing merge, and the merge process. Last time, you know, it took us a whole year, and so the idea that we can say at the start of 2021, we’re going to get it in by the summer has been really, really shocking to folks because it cuts that time in half. And on the one hand yeah, it is, it’s really aggressive, but on the other hand, I know absolutely that the community can rise to that challenge. Like we always do. It’s a lovely group of people that really show up to make the best solution for the WordPress users that they can, and I have been really pleased to see all of the work that’s gone into full site editing over the last 12 months already and longer technically, but definitely the last 12 months it’s made huge strides.
\nSo I want to clarify for all of your listeners that like the first primary target date to look out for is that April 2021 date. That’s what I am considering the go, no go date because I will never take something that is super duper broken and users can’t use, and say we’re getting it in to 5.8 because I made a promise to myself. Like I’m not going to ship a broken tool when I can help it. And there is probably, I think if my guess is right, there’s going to be a Gutenberg plugin release on the 17th of April and then the 23rd of April as well. And those will be our two moments when we can say we believe we can do this.
\nAnd there’s been a lot of discussion around okay, but what is the MVP that you think is going to get in there? And I have been directing people to these milestones that there’s this ticket that has the milestones for full site editing, and we did clear one of those milestones and are getting it ready for testing right now. And this is an unofficial concept of the MVP, but I do think I’m right about this. The guiding question that I have been asking myself as I am watching full site editing, kind of get pulled together is could I using the blocks available, pull together the major functional parts of a campaign landing page.
\nThat is what I’m using as my guiding light for do I think this is ready or not? And, you know, campaign landing pages, that’s like the smallest sentence of a smallest viable sentence. It is the I am of websites. Right. Like, you’ve got your header and footer. You’ve got your hero image. You probably have a button on the hero or a slider if you’re feeling fancy and then you’ve got text, you need to have a form you need to have a way to have a call to action. It is a functional website on its own. But it is the smallest version of a website. And so the question that I have is can you without code, pull that together? And I don’t know if that is, for instance, like Mathias Ventura. I don’t know if that is the guiding question that he’s asking himself as he’s looking toward what makes an MVP possible, but it’s hard to build software in the open, right? And so like you have to have a big enough goal so that you can display a plausible promise, to the users so that you can say this is what we believe this is going to look like, but not so big that you have gotten so far ahead of them that they don’t feel like they can catch up and finding that really narrow space between far enough that you can tell what it’s supposed to be, but that you don’t feel overwhelmed by how much has changed is really hard to get to. And so that’s why I’m bringing us into some really clear focus around like we’re driving to April so that we can ask ourselves as we go, those really poignant questions of does this get us closer to the MVP? Does this help us solve this problem for our users? Because honestly, full site editing is this intersection of the promise of the technology and the promise of the philosophy. This is where the rubber meets the road on what we’ve been saying about Gutenberg for so long, all of our promise lies in here. And so, it’s important to get the tool right, but it’s also important to get the proper landing area for the first foray of the tool, right.
\nOkay. So I’ll link in the, in the show notes that we put together for this I’d link to your big picture goals, 2021 article, which promoted the debate about the MVP, but I’ll also make sure to link to the site editing milestones GitHub piece as well so that people can figure out exactly what’s going on.
\nJust turning away from the full site editing thing, as much as I want to keep talking about that. There’s more going on, isn’t there because in the near future, you’re highlighting a couple of other things, the need for LearnWP to become a real resource for people to get up to date, upskill their interactions with WordPress, and also contributor tools, and although we haven’t got a lot of time for those, maybe pick one of those and tell me why you’re so bullish about those.
\nGosh, let’s go with Learn. I’m bullish about contributor tools because I desperately want our community to have tools that are easy to use.
\nOkay. That’s good. Yeah.
\nI’m really excited for the work on Learn for a number of reasons. For one, we are a global project and right now, so much of our training about how to even get your bearings in WordPress before you are able to get to the 101 content that’s out there happens at an event. And in order to get to an event, you have to pay basically three ways. You have to pay with your money in a lot of cases, you have to pay with your time. And for any entrepreneur, you’re also potentially paying with an opportunity cost. All the time that you spend there, not only are you not working, but you’re also not working to fill your funnel. And so finding a way to take that training opportunity and remove as many barriers as possible and make it available online for anyone who needs it, to be able to get to no matter where they are, that is so important to me and so compelling. That’s my big picture, hope there. And right now there are still quite a few barriers to entry. We mostly have English based workshops and tutorials there. And so if any of your listeners are interested in joining that effort, we need a lot of translations. We need a lot of workshops\\ in other languages and various things like that. But I really believe that this is a space where WordPress can be really forward facing in owning the fact that we know how to use our tools the best and that our community is the best group of people to tell each other and to tell future community members what can happen and not happen with WordPress, they are the people who know what is needed. They are the subject matter experts of their own business and their own plugins that they needed to do those things. And so getting that opportunity with as few barriers as possible, but, to really be able to say we are a canonical source of good information about how to use this, especially when you don’t know even remotely what you’re doing yet. I think that’s a good step forward for you.
\nYeah. With any software with just about any product, in fact, in the world, having fantastic documentation that you can understand and consume, and there’s one, as you said, canonical source that you can go to and if it’s not exactly there, you may well pick up another path to finding exactly where it is, and so, I just think that’s such a great thing now that we’re hitting 40% of the internet, this seems like a really valuable project.
\nWith time being limited. I’m going to pivot once more and talk about the longer term, the things that are off in the horizon. And it’s a very broad question because I don’t want to stifle you. What are the things in the longer term, after this year that you’re getting excited about in the WordPress space?
\nGosh, you asked me a really big question and I have 20 answers. I’m going to tell you some of the things that I’m super excited about. I am for one super excited about really continuing to remove these barriers to entry for future WordPressers. I define our community as anyone who has interacted with WordPress, whether they know it or not. And at 40% of the web, it is increasingly true that the people in the, don’t know, they interacted with WordPress group is also getting bigger and because the work of all of our contributors, all of our entire community that shows up to help get this done, no matter which team they get it done in, because every time they commit changes to the work and to the greater collective project that they’re working on that change and their name with that change and their work lives in the entire history of that. They add, they take 17 years of learning that came before them add in a new learning based on new information we have today, and then they are forever in the history of what made WordPress successful and getting to a point where our 40% of the web, just websites, and also the people who interact with that 40% have some concept of what goes into that work and this community that is behind it. The more and more that they have a deep understanding of that just like wine appreciation or something, jazz appreciation. The more that you understand that the more that you see the value in what is happening here with open source. Cause you know, open source is a contentious kind of space in the world. If you look at it and how it applies to businesses and how it applies to in some cases, governmental structures and things like that. And I really feel like the more that we dignify the work that goes into this tool, and the more that we can subvert that feeling of WordPress isn’t secure because of whatever reasons, like the more that we can change those narratives, the more that we dignify the professions of all of the WordPress contributors that show up in their very tiny spare time, because they’re giving back to a project that gave them so much in the work that they do today.
\nI just… this is going to sound really sappy is the honor of my career to be doing this work with WordPressers, and the fact that the general public has a tendency to say Oh, well, WordPress is terrible because it’s by volunteers is just not fair to them and it’s not accurate to what they’re doing either and so I feel like the sooner that we can really shore up this concept of yeah, it is volunteers, but they are all absolutely experts in whatever field they’re in and in their spare time, they give back to something that made them so good. The sooner we can do that for the community as a whole, I think the better just dignifying the profession of being in WordPress.
\nI’m going anchor my reply to that, to an article that you posted recently called making WordPress releases easier. I’ll link to it in the show notes and on some of the points that you drew out in there, marry perfectly to what you’ve just said, because one of the concerns that you were raising in the longer term is the idea of things like this discussion can came up in the context of the release cycle and whether or not we should be trying to go for a specific number four releases per year, or whether there should be some flexibility there, whatever that number may be. But you express concern for things like developer fatigue and the fact that we need to realign the number of core developers that we’ve got and the number of designers, who are helping in the system. So what were you meaning when you were describing your worry about the developers that were currently using exhibiting signs of fatigue and so on?
\nAs with every single time I talk about the deepest parts of my work… have to start by saying like my whole job is identifying our risks and our most weak places and finding ways to make them stronger and finding ways to steer around the risks that we have, and so sometimes what I say sounds super duper dire, but yeah, in general, I think that WordPress is in a really good space right now. It’s in a really good position, especially considering that we are still in the middle of a global pandemic. And so that general context for what I’m about to say, which is going to sound a little dire. We have a number of committers and a number of maintainers that show up to do this work every day. And that is not only for the code, but also for the design work. It’s also for our translations, it’s for folks in the support forums, like all of our 25 teams or something, everyone who shows up to do that work every day. It’s really hard in a global pandemic situation to keep everyone feeling resilient and feeling like everyone around them as a human being and keeping them mindful of the fact that they are also a human being.
\nEverything is really stressful for the world and for them and for our users and people who are trying to, replace their income by coming up with a WordPress site, using a WooCommerce solution or whatever it is. And it’s… on the one hand true that we would have had a little bit of difficulty with fatigue with our maintainers and committers even before this, but especially right now, especially in the context that we find ourselves in, it’s really hard for people to recharge and all of the work that would have needed to happen in order to get us to four releases this year should have happened in 2020, but we were all really, really focused on pivoting an entire arm of our community into a space that we are not necessarily terribly familiar with online events. It’s just not something that we as a project did a lot of, and so I guess my overall concern is we have two major projects that go at the same time at the same pace and the more and more people use WordPress and Gutenberg, the more and more we have tickets that are opened. And we have roughly the same number of people who can help us to make the decision, write the code create the design, whatever it is, and then review it, test it, commit it. It’s the same general number of people right now as it was in 2019. And it’s getting harder and harder for me to find ways to reliably feel like they’re getting themselves recharged and practicing sustainable self care work.
\nIs this a job of recruiting more people in or trying to, like you have obviously have been doing trying to get more people in the community involved. Is it a bums on seats to use a crude analogy? Is that what’s required?
\nI think it’s a bit of both. I think it’s a little bit… Get more people in here who can help us do the work, which is hard to do in a normal setting and is also harder to do when we’re not seeing each other in person. I have a whole thing about that. Um, many, many thoughts, but it’s a little bit getting people in here. And also it’s a little bit making it very clear to the people who are using 100% of their spare time. Like they have two hours a week. And so they did a patch and they showed up and they’re like, please take my patch. And if they know that we don’t have it about 110 people reviewing and testing and committing things, we really have 30. It can help to give those 30 committers a little bit more space because people don’t expect that 30 people can manage 300 new tickets every hour or something. Just to kind of uncover the mountain that we’re working with, I guess, to give everybody a little bit more breathing room, I guess that’s it.
\nWell, Josepha, I know that your time is valuable and I know that I’ve consumed probably already more of it than was allowed. So just I’d just like, say thank you. I know that you have an awful lot sitting on your shoulders, certainly from my part greatest appreciation. Thanks for all the work that you do and thank you for coming on the podcast and talking to me today.
\nThanks for having me. I thought this was really fun.
\nJoris van Montfort, a freelance WordPress developer, released the JVM Gutenberg Rich Text Icons plugin over the weekend. The goal was simple: allow users to insert icons nearly anywhere in the block editor at the click of a button.
\n\n\n\nThe plugin uses version 4.7 of the Font Awesome library out of the box. However, developers can modify this to include custom icon sets.
\n\n\n\nLike many of the most useful plugins, it stays in its lane, performing a simple task and doing it well. The plugin presents users with a “flag” button in the editor toolbar whenever they edit a Rich Text field.
\n\n\n\nRich Text is a block editor component for entering text. Anywhere users can type in the editor canvas is fair game for inserting an icon. This includes paragraphs, headings, image captions, and more. It also extends to blocks from other plugin developers. If they employ a Rich Text field anywhere, the “flag” button will appear, and users can plop an icon in it.
\n\n\n\nIcons inserted through the plugin automatically inherit the surrounding text size. If you stick it in a Heading block, it will grow larger. If you stick it in a Button block, it will match up with the Button text. The same is true for the colors too.
\n\n\n\nBecause it is impossible to match each theme’s design perfectly, some minor spacing or alignment adjustments may be needed. For the most part, the icons looked good when I tested them with various themes. However, there were a couple of one-pixel-off issues and minor alignment miscues with some blocks. On the whole, I did not run into any design-breaking issues. The plugin displayed its icons as it should.
\n\n\n\nOne usability issue I encountered was being unable to delete an icon via the Backspace or Delete keys on my keyboard in use with the Buttons block. It worked well with other blocks. The solution for this was to click on the inserted icon. Then, select the “flag” icon in the toolbar to reopen the inserter. After choosing no replacement, the old one disappeared.
The plugin developer provided filter hooks for third-party developers to implement icon sets other than Font Awesome via a custom JSON file. Instructions are outlined in the plugin’s readme. There are also hooks for uploading or overwriting the stylesheet and classes.
\n\n\n\nWhile I like the plugin’s execution, I dislike that it loads its own Font Awesome stylesheet. If using another plugin or theme that does the same, its inclusion increases the page load size for end-users by loading multiple copies of the same code. This is not the fault of the plugin developer. It is a limitation created by WordPress’s lack of a dependency system. However, users who give the plugin a try should be mindful of this potential issue.
\";s: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, 24 Mar 2021 23:07: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:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"WPTavern: Chrome 90 to Use HTTPS by Default in the Address Bar\";s:7:\"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=114269\";s:7:\"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/chrome-90-to-use-https-by-default-in-the-address-bar?utm_source=rss&utm_medium=rss&utm_campaign=chrome-90-to-use-https-by-default-in-the-address-bar\";s: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:2895:\"Chrome’s upcoming version 90 will use https:// by default in the address bar, bringing a significant improvement to security and loading speed. HTTPS adoption has shot up significantly over the past six years after Google announced in 2014 that HTTPS would be used as a ranking signal in search results.
\n\n\n\nIn February 2021, W3Techs found that 82.2% of websites use a valid SSL certificate. Today, more than 98% of pages loaded in Chrome use HTTPS as the default protocol, making this change to using HTTPS as the default for navigations long overdue.
\n\n\n\nFirefox Telemetry charts HTTPS adoption at more than 84% of web pages for all users and 92% for traffic originating in the USA.
\n\n\n\nCurrently, anytime a user puts a site into the address bar without specifying the protocol, such as “example.com,” Chrome uses HTTP by default and then has to retry for HTTPS.
\n\n\n\nThe update in Chrome 90 is good news for Chrome users, because it improves the loading speed for sites that support HTTPS by cutting out the redirection loop after the initial load. A gif on the Chromium blog illustrates this in a nice way:
\n\n\n\nThose who are using Chrome Canary can access experiments to try it out ahead of the version 90 release. Navigate to the following URL to mark the experimental feature as enabled:
\n\n\n\nchrome://flags/#omnibox-default-typed-navigations-to-https
\n\n\n\nWordPress site owners will want to make sure their sites are using HTTPS in order to take advantage of the speed boost this change introduces. Fortunately, for those who haven’t migrated over yet, the latest 5.7 release makes it easy to update with the click of a button. WordPress can detect if the site’s hosting environment supports HTTPS and then offers a one-click update process via the Site Health screen. It even handles mixed content rewrites where possible, so site owners will not have to worry about having a bunch of broken links after migrating.
\n\n\n\nChrome 90 went into beta in mid-March. The stable release is scheduled for 20 days following beta on April 13, 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:\"Wed, 24 Mar 2021 17:28:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"HeroPress: My Journey From Freelancer To Product Maker\";s:7:\"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=3513\";s:7:\"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:160:\"https://heropress.com/essays/my-journey-from-freelancer-to-product-maker/#utm_source=rss&utm_medium=rss&utm_campaign=my-journey-from-freelancer-to-product-maker\";s: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:9826:\"![\"Pull](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/032321-min.jpg\")
Like many others in our industry, my WordPress journey started a while ago.
\nI built my first website using GeoCities when I was 14 years old, 21 years ago (boy am I getting old). At the time I was obsessed with skateboarding, the website was for friends I used to hang out and ride around with from school. I remember how excited I felt when I could see that my website was online and I would literally show it to everyone I could, even though looking back at it now it was extremely brightly coloured and scrappy!
\nBack then, with my family’s 56k connection, whenever I connected to the internet it would take over the landline, so I was only allowed to go online for an hour per day. So I spent the days fiddling with Front Page, just waiting for my 1 hour to upload the code and share the updates with my MIRC friends (kinda like a Stone Age version of Slack).
\nThat’s about the time I also picked up a guitar for the first time….
\nMusic, business and websites
\nTo start I borrowed a super cheap electric guitar from a friend to learn how to play, and impress a girl I liked. After playing all evening, I felt so inspired that the guitar ended up next to me while I slept in bed. It was love at first chord.
\nBecause I was so obsessed, I couldn’t stop practicing and quickly I became pretty good (for a kid). So much so that I formed a band with some friends and started performing wherever we could. For the next decade, I focused on becoming the best rock musician I could.
\nI didn’t want to just play the guitar in a band that was performing at local events and school, I wanted us to go places and started treating it as a business. I began studying business by reading every book I could, which led me to take courses and become a certified business and digital consultant.
\nDuring my studies, I learned WordPress and the entire Adobe suite. This was my first introduction to WordPress and it made me love designing and developing websites even more than I already did.
\nI had fun during this time, but they were some tough years and despite all of my efforts, my band wasn’t doing very well.
\n\nAfter everything I had put into it, I thought I’d have my own episode on MTV Cribs already!
We decided the band needed a change.
\nWe rebranded, wrote new stuff, this time in English to maximise our reach, and did an online launch using everything I learned.
\nWithin a month of the launch, my local band from a small town in Israel was signed to release an album worldwide through a British label.
\nWe were stoked!
\nWe decided to drop everything, come to the UK and start touring Europe. And so we did!
\nStarting from scratch, we began building our audience at small venues and pubs, while really pumping things up online, using WordPress to build our website and promote!
\nWe went from playing to sometimes less than 10 people to hundreds, then thousands. Playing with some of the artists we grew up listening to.
\nIt was pretty amazing, but I was still broke surprisingly!
\n![](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/image1.jpg\")
Luckily though, from my efforts in promoting the band using our website and designs on social media, my work began to get noticed and I started to attract clients.
\nWith little to no money in my bank account, I started freelancing out the back of our tour van and built clients websites while touring Europe. Free McDonalds WiFi became my best friend and no matter where we went, there was always one nearby.
\nWhile I drew in more clients and started generating revenue for myself, unfortunately my band ended up splitting up. It was unavoidable and in the end, it was the best thing that could have happened to me (even though it was devastating at the time).
\nI then thought, “you know what, I’m going to start taking this freelancing thing seriously.”
\n\nI started building my own business, using my rediscovered passion for the web and WordPress in particular.
As I got deeper into building websites, I began to insert myself more into the WordPress community, which filled the void of being “the band guy”. As my time now wasn’t being taken up by touring, I employed my first designer and this is where my agency took off.
\nWe managed to pull in 6 figures within the first year, and we kept growing!
\n![](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/image2.jpg\")
Within a few years, my agency grew to 12 employees. As I acquired more clients, I realized there was something holding me back.
\nFrom Agency To Product Maker
\nAs we began dealing with more and more clients day-to-day, it became blindingly apparent that we simply did not have the correct tools to deal with the volume efficiently.
\nSo, I went on the hunt for a platform or tool that could help organize and deal with client requests quickly and easily. We already had a ticketing system in place, while using emails, phone calls and face to face meetings, but it was just all a mess.
\nThere are solutions to the problems of project management BUT I struggled to find a purely dedicated platform that was for a web design agency.
\n\nI arranged a meeting with my team and we decided, let’s just build our own solution.
We had the designers and developers to make it happen, so…we did! We developed a simple WordPress plugin that we could use to take requests from our clients across all of their websites, and after it was implemented, it worked like a dream.
\nBeing the person I am though, I didn’t stop there. I thought, “other people should be using this” and that’s where my product, Atarim, was born. I reached out to the WordPress community wherever I could and got a bunch of beta testers to try it out with their own clients.
\nThe feedback was so positive that we developed the plugin even further and started charging monthly and annual plans for other agencies and freelancers to start using it. We are now a fully fledged agency management platform serving thousands of freelancers and agencies and helped deliver tens of thousands of website projects. In just short of two years.
\nNow we only deal with a couple of legacy clients who have been with us for a while, and we use our own platform to manage them.
\nThe WP Community
\nI’ve been part of the WordPress community for a long time now, and I’m humbled and honored to say that without it, my product would not be where it is today.
\nBefore COVID, I was a regular at every event I could get to, whether it was in London (where I live) or another country.
\n\nI’ve made some lifelong friends within the community and it has made working day-to-day an absolute blast
…(obviously with some major stresses in between, but hey you aren’t doing it right if you aren’t stressed most of the time!).
\nBecause of COVID though, I was driven to creating our own event online. Last year we had our first and we are currently gearing up for the second one to go live very soon!
\nThe Atarim Web Agency Summit was born out of love for the WordPress Community. An online event that spans 4 days where we can all come together and listen to some of the greatest minds in our industry talk about their craft and how we can improve our agencies and freelance businesses.
\nWe managed to develop the summit into the biggest online event in the WordPress space and it was incredibly humbling to partner with some of the largest companies and famous speakers. Companies that have products I myself have been using for years, and speakers that I used to watch on YouTube!
\nAlso, the feedback we received from our initial beta test and the feedback we continue to get from our current users, helps shape the product every single day. The WordPress community is integral for it’s success and I can’t thank it enough.
\nI love that our platform is helping agencies and freelancers that are experiencing the exact same stresses and problems I was facing when growing my agency. This is what drives my team and I to continue working and evolving Atarim, until it is the only way to manage website projects.
\nWhat’s Next?
\nNext, I want to make our platform accessible on any type of website, whether it’s WordPress, Drupal, Shopify or built purely from custom HTML & CSS. I want Atarim to be accessible to any type of agency owner and freelancer so they can implement our platform and reap the benefits.
\nI’m continuing to build the team as our product gets more and more users, so we can up development on a weekly basis and release updates that enhance the experience for our current and bring in new users.
\nAs for me personally, I’m learning new and exciting things every day, attending courses and webinars where I can to ensure that I’m doing the best I can to steer Atarim in the right direction. I’ve been at this for nearly 2 years now, the plan is to go for another 8 years and re-evaluate from there.
\nI’m excited for the future!
\nThe post My Journey From Freelancer To Product Maker appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 24 Mar 2021 08:01:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Vito Peleg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: Eksell Portfolio Theme Now Available in WordPress Themes Directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=114120\";s:7:\"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/eksell-portfolio-theme-now-available-in-wordpress-themes-directory?utm_source=rss&utm_medium=rss&utm_campaign=eksell-portfolio-theme-now-available-in-wordpress-themes-directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2805:\"Anders Norén’s new Eksell theme is now available for download from the WordPress Themes directory. Eksell was inspired by Swedish graphic designer Olle Eksell. It arrives a year and a half after Norén’s popular Chaplin theme was released.
\n\n\n\nLast week Justin Tadlock published a preview of the theme while it was still making its way through the review system. Since that time, Norén has added to the five block patterns he originally submitted with the theme. There are now 12 block patterns that help users create stacked galleries, calls to action, multiple columns with pullquotes, and more.
\n\n\n\nEksell also includes a unique “Blank Canvas” page template that only displays content added in the block editor, which Norén said offers a preview of what users will be able to do once Full Site Editing (FSE) is merged into core.
\n\n\n\nThe Eksell announcement post is a sobering reminder of the uncertainty facing even the most experienced theme developers with changes coming later this year. Norén said he is not planning to update his existing 20 themes to support FSE:
\n\n\n\n\n\n\n\nMy current belief is that I won’t update my existing themes to take advantage of Full Site Editing. Not because I don’t buy into the vision of Full Site Editing, but because I don’t think anyone would be well-served by six year old themes (like Hoffman) very much not built for FSE being updated to sorta-kinda support it. I would rather spend that time on themes built from the ground up to take advantage of the new tools Full Site Editing gives us.
Once FSE is released, Norén said themes not updated to support it will immediately feel outdated “much like Classic Editor themes felt in the spring of 2019.” Theme developers don’t yet know what shape themes will take or how difficult it may be to update them once FSE is in core.
\n\n\n\nNorén is considering updating Eksell to bridge the gap between the world before FSE and whatever themes look like after it lands in core, but reserved the right to leave it behind with the others. For the time being, it is one of the best themes around for the block editor, but it may be the last of the truly classic themes before the dawn of a new era in theming.
\";s: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, 24 Mar 2021 01:28:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: Refactoring Gutenberg’s Gallery Block To Support Nested 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=114179\";s:7:\"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:187:\"https://wptavern.com/refactoring-gutenbergs-gallery-block-to-support-nested-images?utm_source=rss&utm_medium=rss&utm_campaign=refactoring-gutenbergs-gallery-block-to-support-nested-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4957:\"Like many others, I often have pinned tabs of all sorts of things in my browser. Some of them linger there for months. Others for years, I shamefully admit. Of the handful of Gutenberg-related browser tabs I have had pinned since late 2020, one of them finally had the sort of movement I have been waiting on. The Gallery block was finally getting the much-needed refactor it needed.
\n\n\n\nA gallery is essentially a container with nested images. The concept of nested blocks has existed and has been in use for a long while now. However, the core Gallery block does not make use of this capability. This means that users have no access to existing Image block features.
\n\n\n\nWant to customize the link for individual images? No can do with the Gallery block. Instead, users must use Columns and drop Image blocks in. It is such a fundamentally broken part of the user experience there is little wonder that users have looked outside of core WordPress for alternative solutions. And it has been a problem since the introduction of galleries via the shortcode system in WordPress 2.5.
\n\n\n\nWant to alternate styles for each image in the gallery? That has traditionally been impossible too. However, when each image is an Image block, users can alternate between square and round styles, for example.
\n\n\n\nUsers can even use a plugin like Editor Plus with its extended Image block styles to create a Gallery of “image blobs” or animate them individually.
\n\n\n\nThis change could open some layout possibilities where users control the positioning of each item in the grid. And, why stop with images? There is no reason that core could not open the block up to other types of nesting in the future, such as videos, quotes, and more.
\n\n\n\nThe downside to this new feature is that it could require more work from developers who have already built on top of the Gallery block. That is why it is fundamental that they test this change now.
\n\n\n\nTesters can see the change by switching to the gallery refactor branch via GitHub or grab a ZIP file of the build. It adds a new “Gallery Refactor” option to Gutenberg’s Experimental setting screen, which must be enabled.
\n\n\n\nOnly newly-added Gallery blocks will use the new format. Nothing changed about it at first glance. However, by selecting an individual image, users can use the typical Image block settings. The two exceptions are the align and resize options, removed because they would break the layout. New galleries also do not work in the site editor yet.
\n\n\n\n“While the expectation is nothing changes in terms of output, this is a pretty major change on a technical level for a very popular block, so it’d be a huge help to gather as much testing feedback as possible,” wrote Glen Davies in the announcement post.
\n\n\n\nThis statement could be misleading. There are fundamental, backward-incompatible changes to the markup output with the new implementation.
\n\n\n\nIn previous iterations of the gallery, it had a wrapper container (<div>) and an unordered list (<ul>) of images. The proposed change would remove the list entirely, dropping the Image blocks as direct children of the containing element. This will break custom theme styles and potentially plugin integration.
On a technical level, I do not see the need to change the outer markup galleries. It is only the image part of the equation that needs to change. If this is because of limitations with the InnerBlocks system (nested blocks feature), perhaps it is not robust enough to meet developers’ needs.
With continual breaking changes to markup and CSS in the core block system, coding the entirety of a site’s CSS from scratch is probably a thing of the past. This is not the first instance of such breakage and will undoubtedly be the last, a rarity in the pre-block era. The best course of action is for theme authors to leave core styles in place and extend them, even if it means some bloat for page loads. It is not a fool-proof plan, but it lightens the burden.
\n\n\n\nOverall, I welcome the Gallery block enhancement, even it breaks a few things. It potentially opens a world of possibilities and is necessary if the project ever wants to provide end-users with anything other than super basic functionality.
\";s: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, 23 Mar 2021 17:39:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"WPTavern: Ulysses 22 Adds WordPress Post Updating\";s:7:\"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=114118\";s:7:\"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:143:\"https://wptavern.com/ulysses-22-adds-wordpress-post-updating?utm_source=rss&utm_medium=rss&utm_campaign=ulysses-22-adds-wordpress-post-updating\";s: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:1429:\"Ulysses, the writing app for Mac, iPad and iPhone, released version 22 this week with support for updating WordPress posts as the headline feature. The app aims to provide a distraction-free writing experience and has offered the ability to export to WordPress for years.
\n\n\n\nUlysses began alpha testing the highly requested WordPress post updating feature in early February. Updating an existing post is as simple as making a change and clicking ‘Publish’ again. It’s important to note that users can only update a post from the same device where it was originally published, due to a technical issue with iCloud syncing.
\n\n\n\nThe Ulysses development team is working on syncing the publishing state across devices and plans to add post updating for other services in the future. Version 22 introduces a new integration with the Micro.blog service.
\n\n\n\nOne improvement to document management in the app is the ability to add color to the icons in the document library. Users now have the option to add large headers in the editor. Version 22 also includes a host of UI updates that make navigating panels and sheets easier. Check out the release post for a full rundown.
\";s: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, 23 Mar 2021 16:36:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:18;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: New Private Slack Channel Created for Full-Time Sponsored WordPress Contributors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=114088\";s:7:\"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:225:\"https://wptavern.com/new-private-slack-channel-created-for-full-time-sponsored-wordpress-contributors?utm_source=rss&utm_medium=rss&utm_campaign=new-private-slack-channel-created-for-full-time-sponsored-wordpress-contributors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5360:\"As part of an experiment designed to improve coordination of contributor teams, WordPress has launched a new Slack channel for full-time sponsored contributors. Josepha Haden Chomphosy, the project’s executive director, announced the new closed Slack channel on Friday evening in a post that drew critical feedback from contributors who pushed for more clarification.
\n\n\n\n“2020 was filled with hardships for many of us in the WordPress community, and we saw a predictable downturn in the level of volunteer contributions,” Haden Chomphosy said. She noted that during difficult times WordPress relies on these company-sponsored contributors to keep the project going:
\n\n\n\n\n\n\n\nIn the near future, you will see a few more sponsored contributors around to make sure we are keeping up with the necessary tasks, from marketing professionals to backend developers. To assist in coordinating, I have created an experimental Slack channel for contributors who are sponsored for 32 hours or more.
Haden Chomphosy hints at more sponsored contributors being added to the pipeline but didn’t specify where they are coming from. The announcement did not identify a specific reason for the formation of the new channel but briefly outlined its purpose as follows:
\n\n\n\n\n\n\n\nIt is primarily an opportunity for those who are contributing full-time to WordPress to gain valuable knowledge of how we lead with a global mindset and how WordPress applies open source methodologies in a broader context than software development.
Since the new channel is limited to full-time sponsored contributors, the enculturation process she described would exclude those who are not fortunate enough to be sponsored by a company. Traditionally, the WordPress community has worked towards transparency in decision-making as much as possible and in all aspects of development. This channel has the potential to create an imbalance between those with full-time status and those who can only volunteer part-time.
\n\n\n\n“It can be difficult to not start making decisions wherever there is a discussion while working on WordPress,” WordPress core contributor Jeremy Felt commented on the post. “In some ways, every decision made in private can make it harder for future contributors who were not able to see the conversation. We are historically (core team, IMO) not good about documenting the—high bandwidth, in person—decisions that happen at WordCamps and other meetups. I think we can sometimes also be not so great at more permanently documenting decisions that are made in public chats.”
\n\n\n\nFelt suggested WordPress consider making the channel read-only for non-participants or publish the chat log as a way to improve the documentation for private discussions.
\n\n\n\nJoost de Valk requested the goal be more specific so participants can understand what falls within the scope of the private channel vs a discussion that should be public.
\n\n\n\n“I’m honestly kind of radical about transparency and think there’s too much secrecy already, but I also understand the need to be able to discuss without being interrupted,” de Valk said. “It’s a hard balance. I wish Slack had the equivalent of ‘voice’ of IRC, so we could make some of these types of channels public but not allow everyone to post in them.”
\n\n\n\nThe most critical feedback on the announcement came from WordPress Community Deputy Timi Wahalahti, who said he doesn’t necessarily oppose the experiment but felt strongly that it was “a bad call to start the experiment with just notification without any prior public discussion about it.” He also said the explanation in the announcement doesn’t adequately justify the need for the channel.
\n\n\n\n“Where was this proposed and discussed?” Wahalahti said. “To my knowledge, WordPress as a project lives from proposals, discussions and transparency. I’m quite sure it’s not the intention, but the project executive director making this kind of big decision that potentially impacts the transparency without transparent proposal and discussion looks like disparaging the project principles.”
\n\n\n\nWahalahti asked what kind of discussion Haden Chomphosy envisions for the channel. He suggested that since these contributors already belong to multiple teams in the project, it might be “more important to improve the conversational connection between sponsored and volunteer contributors,” instead of focusing on strengthening the bond between full-time sponsored contributors.
\n\n\n\nThe matter of hosting the experiment seems to be settled already but Haden Chomphosy is open to circling back to review the channel’s efficacy after the next major release of WordPress.
\n\n\n\n“I will revisit the implementation post-WP5.8 to make sure it’s useful, focused, avoiding black box decisions, and committing to transparency,” Haden Chomphosy.
\";s: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, 22 Mar 2021 19:48:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"WPTavern: WebARX Rebrands To Patchstack, Combines Services To Focus on WordPress Plugin and Theme 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:30:\"https://wptavern.com/?p=113659\";s:7:\"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:255:\"https://wptavern.com/webarx-rebrands-to-patchstack-combines-services-to-focus-on-wordpress-plugin-and-theme-security?utm_source=rss&utm_medium=rss&utm_campaign=webarx-rebrands-to-patchstack-combines-services-to-focus-on-wordpress-plugin-and-theme-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5680:\"In 2018, WebARX launched the first version of its security platform and grew to 3,000 users. Earlier this month, the company decided to rebrand to Patchstack. Outside of customers getting the name wrong, the company had grown beyond its original SaaS product, providing other services like PlugBounty, an open-source bug-hunting platform. Earlier this year, they also acquired ThreatPress, a WordPress security service provider. Combining the three created an opportunity to relaunch the brand.
\n\n\n\nPatchstack is a website security company. Instead of focusing directly on the core WordPress software, it dives into the world of third-party extensions. For WordPress, that means monitoring and patching vulnerabilities in plugins, themes, and any other components users might install. The service’s primary audience includes developers and digital agencies. It helps them to identify issues and provides almost real-time patching to eliminate threats.
\n\n\n\nOliver Sild, Patchstack founder and CEO, already had the PlugBounty idea back in 2018. “I realized it’s impossible to tackle the security issues in the WordPress ecosystem if we don’t have a big and strong community behind security as there is behind plugin/theme developers. I created a platform where security researchers can quickly put together a detailed security report for any WordPress plugin and which then will be delivered to the plugin developer.”
\n\n\n\nThe new Patchstack Red Team was what was previously the PlugBounty project. His company and other WordPress ecosystem members contribute to the “prizepool,” cash paid out monthly to the top security researchers based on scores from their contributions. All findings are also made publicly available for free through the Patchstack Database.
\n\n\n\n“We manage the triage process by following a strict responsive disclosure policy and make sure the information reaches the right person and that the vulnerability will get properly fixed,” said Sild.
\n\n\n\nPatchstack had already kept an internal database to compare customer software versions. After adding PlugBounty to the mix, it needed a public database to give credit to the community of security researchers.
\n\n\n\n“We had discussions with different database vendors in the ecosystem, but the vision really clicked with ThreatPress,” said Sild. “The founder of ThreatPress also joined our team and is now running the Patchstack Database and Patchstack Red Team operations. Patchstack Database will be providing information about security vulnerabilities in the WordPress ecosystem and will remain free to use for the public. We also have API which hosting companies can use to notify their customers about vulnerabilities within the websites.”
\n\n\n\nSild said that approximately 95% of security vulnerabilities in the WordPress ecosystem are from third-party code. “The best thing you could do is making sure you have your websites updated,” he said when asked about the low-hanging fruit that any site owner could take care of.
\n\n\n\n“The second big issue is the pirated and nulled plugins — keep in mind that if you found a premium plugin/theme for free, then there is a reason behind this,” he said. “It’s a trap many people fall into, and without their knowledge, they infect their own website with malware and backdoors. And how can I not mention passwords? Please use password management tools such as LastPass, KeePass, and try to enable two-factor authentication on all your accounts.”
\n\n\n\nFree versions of commercial plugins and themes that are secure and up to date are possible to find. However, the average end-user would have no way of knowing if that was the case.
\n\n\n\nPatchstack is a SaaS product. Once users create an account through its system, it will guide them to connect their website with the Patchstack WordPress plugin.
\n\n\n\n“Once the website is connected, it sends environment details (plugin, theme, core, PHP, etc. versions) to Patchstack,” said Sild. “Patchstack then compares all the versions with known security issues and notifies the user if outdated/vulnerable code is detected.”
\n\n\n\nPatchstack has different security modules, which can be enabled or disabled from the settings screen. One that is on by default is WordPress Virtual Patches. This feature detects if a vulnerable plugin is in use on the site and sends virtual patches immediately.
\n\n\n\nThe service has a cloud-based dashboard, allowing users to access details for all of their sites in one place.
\n\n\n\n“Patchstack allows you to create custom security alerts and send them on emails and Slack channels when vulnerable or outdated plugins are detected,” said Sild. “It provides a central overview on all the different security issues across an unlimited number of sites, and you can export a monthly PDF report for each website if needed. Additionally, to how many vulnerabilities and security issues you have on your websites — the Patchstack dashboard is also telling you when any of the vulnerable plugins/themes on your websites have been attacked, and you’ll have granular details about each threat that has been blocked.”
\";s: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, 22 Mar 2021 18:36:18 +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:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"Gutenberg Times: Building Forms with Blocks, Work w/ Blocks via GraphQL API, and more – Weekend Edition #163\";s:7:\"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=17282\";s:7:\"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:47:\"https://gutenbergtimes.com/weekend-edition-163/\";s: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:16804:\"Howdy,
\n\n\n\nIt’s another month, until we know if the Full-site editing experience is good enough for the merge into core. It still has many moving parts that need to fit neatly together to make it a good user experience and allow site owners to design their site within the boundaries of their block-based theme.
\n\n\n\n\n\nDiscover two plugins to build forms with the editor and read two articles on how to work with blocks in decoupled (also called headless) WordPress via GraphQL. Some developers might find it as exciting as I do.
\n\n\n\nEnjoy the plugins shared and check out the upcoming WordPress events.
\n\n\n\nYours 💕
Birgit
\n\n\n\n\n
“Keeping up with Gutenberg – Index”
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. The index 2020 is here
Gutenberg team released version 10.2 of the plugin.
Release notes by Bernhard Reiter
WPTavern post: Gutenberg 10.2 Adds Spacers To Navigation Lists, Lets Users Categorize Template Parts, and Introduces Scoped Patterns
\n\n\n\n
Anne McCarthy shared high level feedback from the FSE Program.
\n\n\n\nThe 3rd Call for Testing is only open until March 23, 2021. If you have about 20 minutes, build a fun 404 page via the new Site Editor in WordPress. Anne McCarthy has some very details instructions. Please share your experience as a comment on the post.
\n\n\n\n\n\n\n\n
Monday started with This Week in WordPress live show #154, a podcast by Nathan Wrigley and Paul Lacey. This week Anne McCarthy and Joe Casabona were on the show as guests, and they covered the new features in WordPress 5.7 and more Full-Site Editing. Head on over to YouTube!
\n\n\n\n\n\n\n\n\n Subscribe to the Gutenberg Changelog podcast
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed
Plugins for the Block Editor
\n\n\n\nFormality is an all-in-one WordPress form plugin for the block editor. Michele Giorgi, who built it for fun and “because he hates the gym.” I definitely can relate to the sentiment, although, I get cranky when I skip our lunch runs for too many days. The plugin comes with 12 blocks that include usual form elements, multi-steps layout, and ratings. You’ll also find 24 templates with backgrounds from Unsplash and corresponding color palettes. For developers, there are hooks and filter to extend it for your needs. Ben Townsend of LayerWP reviewed it on YouTube.
\n\n\n\n🌐 Website | GitHub | Gist | WPRepo
\n\n\n\n\n\n\n\n
Gutenberg Forms is another block editor only plugin to create forms for your page and post. The author, Munir Kamal, also created add-ons for Mailchimp, Mailpoet and Akismet. All his code it open-source, and maybe he inspires you to create your special integration as well. You can also read Justin Tadlock’s review from last summer
\n\n\n\n🌐 Docs | WPRepo | Website | GitHub
\n\n\n\n\n\n\n\n
The plugin Full Screen Galleries by Nick Halsey creates an automatic full-screen slideshow mode for images on your page or post. It works on both, block editor and classic editor. It’s designed to work with any theme out of the box. See the plugin page for code snippets to add custom styling and a launch button. It’s a focused way to showcase travel photos or art work. This week, Justin Tadlock of WPTavern published a review.
\n\n\n\n\n\n\n\n\n\n\n\n
K2 Blocks is one of the Block collections extending the core block editor with additional blocks. The most interesting to me would be the Counter and Time blocks as well as the Magic Image block. The PookiDevs team from Islamabad posted screenshots and more details.
\n\n\n\n\n\n\n\n\n\n\n\n\n
Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Gutenberg for Developers
\n\n\n\nRyan McCue, director of product at the agency HumanMade, shared some experimentation with the navigation components in Gutenberg and created a new WP-Admin navigation bar outside the editor. He “based this stand-along plugin on existing work in WooCommerce.” You can follow the discussion on Twitter.. The code is available on GitHub for your perusal.
\n\n\n\n\n\n\n\n
Justin Ferriman of LearnDash shared how they leveraged Gutenberg to make a Certificate Builder in LearnDash. You can see short demos on how it works.
\n\n\n\n\n\n\n\n
As an alternative to Jason Bahl‘s work with Gutenberg and WordPress decoupled sites a couple of weeks ago, Leo Losoviz published his proposal on how to handle blocks with a decoupled WordPress and GraphQL site. The two different approaches are a deep dive into both plugins that provide GraphQL APIs for WordPress.
\n\n\n\nWPGraphQL and GraphQL API for WordPress
\n\n\n\n\n\n\n\n
Speaking of Headless or Decoupled: Michal Trykoszko started a three-part series of blog posts: Headless WordPress Gutenberg & NextJS with Creating a block with React.
\n\n\n\nWordPress Events
\n\n\n\nMarch 23 – 26th, 2021
Atarim Web Agency Summit
March 24, 2021 – 10 AM EDT / 14:00 UTC
Intro to Publishing with the Block Editor (Demo + Discussion group) with contributors of Learn. WordPress program
March 26, 2021 – 10 AM EDT / 15:00 UTC
Creating and Registering Block Patterns (Demo + Discussion group) with Daisy Olsen from via Learn WordPress program
If you want to come prepared with questions, watch the workshops Intro to Block Patterns and Registering Block Patterns
April 6, 2021 9 am EDT / 14:00 UTC
WPCafe: Building the Twenty Twenty-One with Caroline Nymark and Mel Dwan-Choyce, live on YouTube
April 15, 2021 6:30 pm EDT / 23:30 UTC
South Florida Mega Meetup “New Site Builder Edition”
April 15 – 17, 2021
WordCamp Centroamérica 2021
April 27 and 28th
Expand 2021 – a virtual event hosted by GoDaddy that brings the web design and developer community together to share ideas and experiences, make connections and support each other.
May 24 – 27. 2021
WordSesh 2021
Speaker submissions are due on March 29!
\n\n\n\n
On the Calendar for WordPress Online Events you’ll find a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\n\n\n\n\n\n\n\n\n
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Featured image: Photo by Glen Carrie on Unsplash
\n\n\n\n\n\n\n\n\nThank you to our in-kind Sponsors!
\n\n\n![\"Sponsored](\"https://i0.wp.com/gutenbergtimes.com/wp-content/uploads/2018/03/Sponsored-by-Pantheon.png?fit=300%2C111&ssl=1\")
![\"Pauli](\"https://i2.wp.com/gutenbergtimes.com/wp-content/uploads/2018/07/cropped-paulisystems-trademark-no-tagline.gif?fit=300%2C77&ssl=1\")
![\"\"](\"https://i2.wp.com/gutenbergtimes.com/wp-content/uploads/2021/02/logo_brand24_black_small.png?fit=300%2C64&ssl=1\"){kind=logo}
On Wednesday, WordPress executive director Josepha Haden Chomphosy posted the next steps forward for themes and reviews for the official theme directory. In the post, she describes the tools and types of access the Themes Team needs. She also laid out some other goals for the system. The timeline is to have much of this in place by early 2022.
\n\n\n\nTwo months ago, things were coming to a head. Project lead Matt Mullenweg saw much of what we have all been seeing. Creative contributions to the free directory were few and far between, many of the submissions merely being stripped-down “lite” themes with commercial interests.
\n\n\n\nThere was some disagreement on why the directory was not producing the high-quality projects users should expect from an official source. Mullenweg cited the rules and update mechanism as problem areas.
\n\n\n\nHowever, others like Joost de Valk, the CPO of Yoast, said the reality of the situation is that money is now a part of the equation. Producing high-quality products, maintaining them, and supporting them is not sustainable without the financial resources in place. Because WordPress.org provides no path for developers to make money directly, upsell-motived themes are the result. Eric Karkovack expanded upon this in his piece for Speckyboy, Are High-Quality Free WordPress Themes a Thing of the Past?
\n\n\n\nSome of the Themes Team members disagreed that the rules were the problem. At the heart of the team’s handbook is the idea that themes should be GPL-compatible, secure, and not break things.
\n\n\n\nThe problem is not necessarily specific guidelines but the process. Mullenweg wanted to switch to a post-commit strategy that would see themes move into the directory more quickly. The goal is to be a little more like the plugin directory and let users guide others through the star-rating review system.
\n\n\n\nHowever, themes and plugins are different beasts. Themes must follow some standard patterns and do some specific things to actually work. The best way to make that happen is with automated tools performing the grunt work that humans have been doing for the past decade. Many guidelines could become a line of code in a script. Each new line would lighten the burden on volunteers.
\n\n\n\nThe Themes Team agreed with his assessment of the theme quality. However, some did feel like the theme system was the oft-forgotten stepchild who received all the hand-me-downs from its preferred sibling, the plugin directory. They needed resources from the community to drive any sort of change. Team members had little power outside of their gatekeeping responsibilities and were short on volunteers.
\n\n\n\nChanging Hearts and Minds
\n\n\n\nHaden Chomphosy published notes on the meeting in February. The post detailed the ideas and what took place. However, much of it seemed vague in terms of actionable items. It was the groundwork phase.
\n\n\n\nIn a private discussion with one of the Themes Team reps, they said the meeting was productive not because of action taking place but through the changing of outlooks. More of the team reps warmed to the idea of reducing the requirements and moving forward with a change. The meeting was more about winning hearts and minds, which was a necessary first step.
\n\n\n\nThis changed outlook did not mean throwing caution to the wind and flipping the switch overnight. The team wanted to set some guardrails in place, particularly surrounding high-priority issues like proper licensing.
\n\n\n\n“In the meeting, we discussed the need to change the review process,” said team rep Ari Stathopoulos. “All guidelines have a reason they exist. They were all added after some things got abused. But the process followed had an unfortunate side-effect; the rules that were added to avoid abuse by a few bad apples are the same rules that hinder innovation and deter people from submitting a theme in the repository.”
\n\n\n\nHe brought up the universal rules of not doing evil things, disrespecting others, or abusing the system. Citing them as the foundation of what the guidelines should be. “But then, of course, everyone has a different definition of evil, disrespect, and abuse, so something a bit more verbose may be needed but obviously not as verbose as the dozens upon dozens of guidelines we currently have.”
\n\n\n\nThe Next Steps: Tools and a User-First Strategy
\n\n\n\nThe first goal is to have access to a functional meta environment for testing. One of the team reps currently has this. However, others would need access in the long term. Moderator tools are also on the list for reviewers, likely similar to what the Plugin Review Team has.
\n\n\n\nThose are some of the baseline things. The next item will be more automation. Dion Hulse is currently working on automated security checks, which should help with a consistent problem area. Steve Dufresne is working on an automated code-scanning solution.
\n\n\n\nOne idea for a post-commit strategy is flagging themes with “quality tags.” These include items like Gutenberg-ready, security, last updated, translation-ready, and accessibility. It is not clear how this system would work, but it could be a way to surface themes in the directory that meet standards. Perhaps a new featured-theme algorithm should be in the works?
\n\n\n\nThe last piece of the proposal introduces the concept of a yes/no voting mechanism for end-users. These would be “trust tags” that allowed users to mark themes as updated, visually broken, and more. The goal is to hand over much of the gatekeeping responsibility to users, putting them in the driver’s seat of what they want out of the theme directory.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 19 Mar 2021 16:16:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"WPTavern: Gutenberg 10.2 Adds Spacers To Navigation Lists, Lets Users Categorize Template Parts, and Introduces Scoped Patterns\";s:7:\"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=113984\";s:7:\"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:295:\"https://wptavern.com/gutenberg-10-2-adds-spacers-to-navigation-lists-lets-users-categorize-template-parts-and-introduces-scoped-patterns?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-10-2-adds-spacers-to-navigation-lists-lets-users-categorize-template-parts-and-introduces-scoped-patterns\";s: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:6487:\"Yesterday, version 10.2 of the Gutenberg WordPress plugin landed. Users can now add a Spacer block between Navigation items, categorize custom template parts, and pick between patterns when inserting the Query block.
\n\n\n\nThe user experience continues to improve in some areas. The Media & Text block, one of the few holdouts, can now be transformed into Columns. The transformation results in two columns with the media and the text separated. This is a one-way transform, however. It is a necessary enhancement for users who write out their text column to realize they can only add uploaded media instead of something like a YouTube embed to the Media & Text block. Making a quick switch over to Columns solves the issue.
\n\n\n\nThe “Start writing or type / to choose a block” prompt only appears for the first empty paragraph when there are subsequent paragraphs. It is a trivial change, but it removed a minor annoyance.
\n\n\n\nThe development team squashed 30 bugs for Gutenberg 10.2. They also continued work toward improving experimental features such as the site editor, global styles, and block-based nav menus. Full Site Editing is shaping up, but it will still be a while before we know whether it will be ready for inclusion in WordPress 5.8.
\n\n\n\nAs I write this post, I am also doing so in a broken editor. Gutenberg 10.2, yet again, changed either its markup or CSS, which means I will have to do some digging to find out why all of our paragraphs are misaligned in the editor. But, that is a job for tomorrow. This should be a theme-specific fix and an isolated issue.
\n\n\n\nNesting Spacer Blocks Within Navigation Lists
\n\n\n\nIn one of the worst ideas the Gutenberg project has brought us, users can now insert spacer blocks between horizontal Navigation block items. And they can increase or decrease the space in pixels. The idea of spacing is not in and of itself bad, but the solution used is.
\n\n\n\nAs far as I know, the <div> tag is not allowed as a direct child of <ul>. That is where <li> elements go. Maybe it is my old-school HTML upbringing, but it does not feel right to throw other things in the mix. List items are the children of lists.
Fortunately, there are solutions for this sort of horizontal spacing that have been available to web designers for decades: margin and padding.
\n\n\n\nThe Spacer block has never felt right since it was introduced into Gutenberg. I always assumed it was an unfortunate stopgap solution for vertical spacing until we got proper margin and padding block options. I never imagined we would find new and inventive ways to use it for defiling a site’s markup.
\n\n\n\nTemplate Part Categories
\n\n\n\nUsers can now save template parts to a specific category or “area,” as they are called in the site editor UI. In Gutenberg 10.1, the development team introduced a new categorization system for theme authors that would automatically place template parts into the Header, Footer, Sidebar, or General categories. The same system is now open for user-created template parts.
\n\n\n\nWhen saving a template part via the site editor, users must open the “Advanced” block tab. There is a new “Area” option. The Sidebar category is missing in this release. Nevertheless, it is a welcome step toward template-part management.
\n\n\n\nQuery Block Patterns
\n\n\n\nThe Query block is at the heart of Full Site Editing. It will eventually be one of the primary components both developers and users interact with as they build sites.
\n\n\n\nThe development team introduced a new concept for end-users when first inserting the Query block. In the past, users saw several block variations. Now, they can choose between patterns that are specific to the block.
\n\n\n\nOut of the box, there are Large, Medium, and Small patterns. Users can also opt to start from a blank slate.
\n\n\n\nFor developers, this change introduces scoped patterns. It is a new layer to the Block Patterns API that should offer a ton of flexibility in the long run. While the feature only works with the Query block right now, theme and plugin authors could create predefined layouts for blocks that users can choose from in the future.
\n\n\n\nImagine having several different styles of post loops that you want to offer to your users. With a few lines of code, you could register each of these as selectable Query patterns.
\n\n\n\nThe new part of the API adds a scope argument that looks like:
\'scope\' => [\n \'inserter\' => false, // Whether to show in the main block inserter.\n \'block\' => [ \'core/query\' ] // The container block for the pattern.\n]This is still in the experimental stage, so things could change as the feature is further developed.
\n\n\n\nFollowing the core example, I created a quick Query pattern with the following code:
\n\n\n\nadd_action( \'init\', function() {\n\n register_block_pattern(\n \'tavern-query\',\n [\n \'title\' => \'Tavern Query\',\n \'scope\' => [\n \'inserter\' => false,\n \'block\' => [ \'core/query\' ],\n ],\n \'content\' =>\n \'<!-- wp:post-title {\"isLink\":true} /-->\n <!-- wp:post-featured-image {\"isLink\":true,\"align\":\"wide\"} /-->\n <!-- wp:post-excerpt /-->\n <!-- wp:separator -->\n <hr class=\"wp-block-separator\"/>\n <!-- /wp:separator -->\n <!-- wp:post-date /-->\'\n ]\n );\n} );Elementor users who haven’t updated recently will want to get on the latest version 3.1.4 as soon as possible. Researchers at Wordfence disclosed a set of stored Cross-Site Scripting (XSS) vulnerabilities in the plugin to its authors in February, which was partially patched at that time and additional fixes were released the second week of March.
\n\n\n\nWordfence summarized the vulnerabilities in a post published yesterday, accompanied by a detailed walkthrough of how an attacker might compromise sites using Elementor:
\n\n\n\n\n\n\n\nThese vulnerabilities allowed any user able to access the Elementor editor, including contributors, to add JavaScript to posts. This JavaScript would be executed if the post was viewed, edited, or previewed by any other site user, and could be used to take over a site if the victim was an administrator.
Many of the plugin’s “elements,” or components, accept an html_tag parameter, which was output without escaping and could be set to execute a script. A few of the vulnerable elements include the column, accordion, heading, divider, icon box, and image box.
At the time of publishing, less than half of all Elementor installs are running on version 3.1.x, leaving millions of sites still vulnerable. Wordfence confirmed this morning that they are not currently seeing active exploits against these vulnerabilities.
\n\n\n\n“Due to the privileges required, we expect it to be used primarily in targeted attacks rather than widespread attempts,” Wordfence security researcher Ram Gall said. “That is, it is likely to be used for privilege escalation once an attacker has been able to get a foot in the door, rather than a complete start-to-finish exploit chain. This is going to be more of a concern for sites that have many contributor or author users, as this means a wider attack surface. The main reason this is a concern is the sheer number of installations.”
\n\n\n\nGall, who discovered the vulnerabilities, described a scenario in which they are most easily exploited. A contributor on the site re-uses a password that has been in a data breach. The attacker finds that password, logs in, and adds a post with malicious code. The administrator sees the post from the contributor in the admin. Visiting that post will run the malicious JavaScript in the browser, which Gall said could infect the site with new rogue admin accounts or code to take over the site.
\n\n\n\nApart from a brief mention in the changelog, Elementor did not alert its users to the security issues on the product’s blog or social media accounts:
\n\n\n\n- Fix: Hardened allowed options in the editor to enforce better security policies
- Fix: Removed
htmloption in Lightbox module to prevent security issues
“Elementor was very responsive initially, though they didn’t keep us updated about the patches after the initial report,” Wordfence representative Kathy Zant said. “They do have a security contact listed on their site, which is always helpful. Often, security researchers have a difficult time identifying and contacting the right person with whom to share vulnerability proof-of-concepts, so we’re always grateful when we’re able to easily start those discussions.”
\n\n\n\nThe latest version 3.1.4 contains the patches for these vulnerabilities, along with fixes for other less severe bugs in the plugin. Elementor users are advised to update as soon as possible to avoid the vulnerabilities being used for site takeover.
\";s: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, 18 Mar 2021 17:41:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Work on the Twenty Twenty-Two Default WordPress Theme Should Already Be Underway\";s:7:\"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=113906\";s:7:\"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:225:\"https://wptavern.com/work-on-the-twenty-twenty-two-default-wordpress-theme-should-already-be-underway?utm_source=rss&utm_medium=rss&utm_campaign=work-on-the-twenty-twenty-two-default-wordpress-theme-should-already-be-underway\";s: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:5806:\"\n\n\n\n[The Eksell theme] does such a great job of selling a block editor-driven WordPress. It was a missed opportunity to not pair something of this quality with the block editor when WordPress 5.0 was released.
It’s responsive! I’m amazed this stands out as a highlight for me, but, as the official theme, Twenty Twenty-One breaks in pretty basic ways in multiple places for different screen widths. I think this visual approach is also probably more approachable as “good design” for the average person than Twenty Twenty-One’s attempt at a more typographical approach…
Daniel
In hindsight, it is easy to look back at past default themes and find fault. There is always something better around the corner. However, Daniel makes some good points in his comment on our recent review of the Eksell theme. The theme does sell the idea of blocks to the user far more so than many others.
\n\n\n\nIt would be hard to convince me that launching a great block-ready theme with 5.0 would have been feasible, given that so much about the new block editor was changing at a lightning-quick pace. But, a year or two later? Probably.
\n\n\n\nTwenty Nineteen, which launched with WordPress 5.0 and its block editor, is the worst-rated (3.5 stars) default theme in history. Twenty Twenty was a decent block-ready outing. It also happened to be forked from Chaplin, a theme built by Eksell’s designer, Anders Norén. While I still believe that Twenty Twenty-One was a refreshing shift and a fun experiment at the time, my fondness for it has waned in the last few months.
\n\n\n\nNone make a convincing case for the block editor. If we are being honest, there are not that many third-party themes in the official directory making it either.
\n\n\n\nI may have already said it thousand times, so once more will not hurt. Themes are the face of WordPress. They are often a new user’s first introduction to our beloved platform and blogging in general. And, the default themes are the first they see.
\n\n\n\nThe defaults also have another role they need to play today. They need to showcase blocks to all the old-timers among us who have clung to the classic editor and page builders we have used over the years.
\n\n\n\nIt is no doubt a tough job working on a default theme. We have world-class developers and designers putting in the hours to create something that needs to work on millions of websites. However, part of the toughness of the job is in the process.
\n\n\n\nEach of the last three default themes was announced in September or October of the year before a November – December release. While I am not privy to any private discussions or work that went on beforehand, the bulk of the theme-building and testing process has happened in a small window. WordPress has also forked at least the last two themes from existing projects, presumably because of the time constraints.
\n\n\n\nIn 2021, the community should expect its fourth default theme, Twenty Twenty-Two, in the block era. It is time we begin thinking about what that should be instead of waiting until the 11th hour.
\n\n\n\nWe are in mid-March. WordPress 5.9 is currently scheduled for December 2021, which should coincide with the Twenty Twenty-Two theme launch.
\n\n\n\nBy starting the research phase now, it gives us the head-start we lacked in years past. The development team would also not need to fork an existing theme. Forks are not necessarily bad, but starting early means the team can go down the from-scratch route if preferred. It is an opportunity to rethink the approach to default themes and do more community outreach before laying down the first code.
\n\n\n\nWhat are the trending features this year?
\n\n\n\nWhich types of themes are most popular?
\n\n\n\nWhat has the community been asking for that we have yet to deliver?
\n\n\n\nWill this be the first block-based default theme to showcase Full Site Editing?
\n\n\n\nThere are tons of questions we should be asking, and more-seasoned designers are better suited to the task than I am.
\n\n\n\nLike Daniel said in the comments, we are not asking for Eksell to be ported to default-theme status. However, something with that design-quality level is what the community should expect. Make us believe; make us passionate; make us want to build our sites with it.
\n\n\n\nHigh-quality themes meant for public release are not built overnight. Except in the rarest cases, they are not created in a month. Client projects can often move faster because they are typically under controlled settings with fewer edge cases. Publicly-released themes do not have the same benefit because they need to handle everything users will throw at it and work alongside untold numbers of plugins. While all designers and developers have different processes and work at different paces, three months is easily the minimum amount of time to code and test a well-rounded theme for modern sites. Some of the best theme authors I know spend upwards to half a year fine-tuning their creations.
\n\n\n\nWe need research, followed by a decision about what type of theme we are building. We need an outline of the goals it should achieve and its primary audience. Rounds of mockups before the code hits a repository. A real community effort.
\n\n\n\nThree months ago was the best time to begin planning for Twenty Twenty-Two. The second best time is today.
\";s: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, 17 Mar 2021 22:20:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"Post Status: Chris Hardie on WP Lookout, WordPress updates and information flows\";s:7:\"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:31:\"https://poststatus.com/?p=81771\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://poststatus.com/chris-hardie-on-wp-lookout-wordpress-updates-and-information-flows/\";s: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:2819:\"Chris Hardie has been a web developer since the late 1990s. In this episode of the Post Status Draft podcast, Chris talks with Brian Krogsgard about his career as a deep generalist. Chris has worked as a writer, journalist, political candidate, and consultant, as well as a technologist and web developer.
\n\n\n\nThis conversation touches on the challenges of winding down an agency and handling clients. Chris also talks about his experiences with the Special Projects team at Automattic, running for local office, being a journalist, and now launching WP Lookout to help site owners and developers safely update WordPress websites.
\n\n\n\n![\"☝\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/261d.png\")
Safe WordPress Updates
\n\n\n\nAutomatic updates are great, but what if you could get critical information about potentially breaking changes to WordPress core? What if you could get notified about changes to the plugins and themes you and your clients rely on?
\n\n\n\nWP Lookout is a new service that monitors WordPress core, plugin, and theme updates so you can apply them safely. You can subscribe to get notices about potentially breaking changes to the software you and your business depend on.
\n\n\n\n\n\n\n\n![\"🔗\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f517.png\")
Topics mentioned in the show
\n\n\n\n\n\n\n\n![\"👍\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f44d.png\")
Sponsor: Bluehost
\n\n\n\nEverything your website needs — from start-up to success story — is at Bluehost. Whether you\'re looking to create a website, blog, or online store, Bluehost will get you started with an all-in-one website platform tailored to your specific needs. Get a free domain name in your first year, free 24/7 lifetime support, and total design freedom with WordPress at Bluehost.
\";s: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, 17 Mar 2021 20:54:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Dan Knauss\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"WPTavern: WooCommerce Live Africa to Host First Online Meetup Event, March 18, 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=113837\";s:7:\"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:207:\"https://wptavern.com/woocommerce-live-africa-to-host-first-online-meetup-event-march-18-2021?utm_source=rss&utm_medium=rss&utm_campaign=woocommerce-live-africa-to-host-first-online-meetup-event-march-18-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2421:\"WooCommerce Live Africa is hosting its first online meetup on Thursday, March 18, 2021, from 5:30 PM to 7:00 PM GMT+1. The new regional group is part of the WooCommerce network of more than 100 meetups with nearly 30,000 members across 40 countries. Events will be focused on topics pertinent to store owners and entrepreneurs with a focus on making it easy for anyone to get started with e-commerce.
\n\n\n\nMary Job and Sunday Ukafia will be hosting the first event, titled “Getting Started in eCommerce” that will guide new store owners from idea to first customer. No technical knowledge is required to join the session, since it’s aimed at absolute beginners. Topics include basic business concepts:
\n\n\n\n1. Choosing an audience
2. Finding a problem to solve
3. Selling your product before you make it
4. Creating the product
5. Choosing an operating system
6. Delivering the product to your customer
7. Creating happy customers
“What inspired the new group is the zeal to help every individual succeed in their eCommerce venture, connect with Woo individuals and businesses to learn more about how they use Woo and how we can all help each other overcome challenges and succeed,” Mary Job said.
\n\n\n\nIn Nigeria, where Job is located, many store owners are using WooCommerce but most tend to focus on selling more via social media channels. Job said she hopes the group can help merchants be as successful with their WooCommerce stores as they already are with Whatsapp, Telegram, and social media.
\n\n\n\n“The local entrepreneur community is pretty optimistic, despite the environmental challenges that comes with doing business in our country,” Job said. “Add to that the irregular and inconsistent government policies (speaking for Nigeria alone here), can’t speak precisely for other African nations.”
\n\n\n\nThe organizing team plans to focus future sessions on a range of skill levels from beginner to advanced. Registration is free and the link to the online event will be visible after you sign up.
\";s: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, 17 Mar 2021 17:39:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"HeroPress: Empowered To Make A Change\";s:7:\"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=3502\";s:7:\"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:126:\"https://heropress.com/essays/empowered-to-make-a-change/#utm_source=rss&utm_medium=rss&utm_campaign=empowered-to-make-a-change\";s: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:9237:\"![\"Pull](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/031621-min.jpg\")
The good part; When writing this, I am working with the top companies in the WooCommerce ecosystem, partnering with creative minds, making things happen that can make a massive difference to many users, or even an essential lifeline to their business survival due to a lockdown. As a partnership manager at YITH, I also had* the privilege of traveling worldwide and attended various WordCamps and WordPress events. I’ve co-organized WordCamps, Meetups, and with 28 WooCommerce London Meetups in 2020 alone.
\n* We are still in a local lock down due to covid at the time of writing this.
The rubbish part; Okay, nine years ago, life was not great, my daughter passed away, and I was stuck as a restaurant owner, working hard and not making much money, plus soon after, I started a court case against my landlord. Maybe this was the year I lost most of my hair, and it also caused my flare-up of UC… so hopefully, you get it, it was not a good time of my life, and I probably had every reason to find ‘the bottle’ more attractive.
\nFrom The Rubbish To The Good Part
\nWhen bad things happen to people, some will hide and go downhill, whereas others use this negative energy into something positive. I can’t say, I fall in either camp, but having been influenced by the right people around me, decisions I made, and by chance, I was being drawn towards the latter one.
\nSoon after our daughter died, my wife, Nihan enrolled in the open university to finish her Computer Science degree. I have massive admiration for Nihan’s strong determination, and I wholeheartedly supported her in this decision. We managed to finance this with an adult learning grant and working as a chef in various local pubs.
\nMy wife’s coursework interested me a lot, and very soon, we started following the lectures together, plus extra course work I was practicing myself too.
\nThen came the idea of affiliate commission earnings through blogging, which I started out using Joomla as a CMS platform. Creating websites was slowly becoming a passion for me, and in these first few years, I enjoyed every part of the steep learning curb tackling the basics to more advanced coding and designs.
\nDiving Into The Web
\nAfter reducing hours as a chef, I followed various online courses in coding and e-commerce, SEO, and online marketing. One of the training courses I signed up for was a lifetime deal for OSTraining. The lessons came in particularly useful when I applied for a job as a WordPress designer. Please note that at this time, I had heard of WordPress and used it as a blogging platform but not played with it as a designer. One of the tutors on OSTraining became my absolute savior in the next two weeks before my interview for a new WordPress job. His name is Topher, also well-known for being the founder of HeroPress.
\nHaving binge-watched various WP development topics and getting familiar with the structures, I was rather lucky to have been given the job. Still, this was only the beginning of my journey into the world of WordPress.
\nA year later, my boss asked me whether I would consider taking over the business and clients. Together with my wife, we started a new brand and company that we then build up over the years. This path naturally leads us into a niche of working with WooCommerce in combination with Online marketing.
\n\nAs I often say to people, WordPress is just one of the tools in my box, just like a carpenter can’t do without a hammer.
The skill in using it efficiently comes over time and even then, there are different techniques. We all look back at projects and think: “ouch, why did I do it that way?” I often hear the term ‘imposter syndrome.’ I don’t believe in this, as I think whoever progresses and explores is eager to learn and wants to improve. It is frankly in human nature to drive ourselves forward. WordPress has evolved in so many branches that require different skills, and thank goodness for that, or we’d all be in competition. Instead, there are 100’s of areas of expertise, roles, and jobs that complement WordPress to make it what it is. A big part of that is each person’s personal background complements their skillsets. Think about it, who you are and what you do is influenced by what you have done and learned. Cherishing this, adding your culture, language, and experience and you suddenly find yourself more than qualified. And often these are not skills or certificates you list on a CV as they might be good and also bad experiences.
\nJoining A Business
\nThe next part of this chapter was my dealings with YITH. As a long-term customer and having met some of the team at WordCamp London, I got into discussions to represent them at events held in the UK. This soon went global with me attending WordCamps in 3 other countries… and this was the moment I realized I could do much more with my connections and create meaningful partnerships. Within a few weeks, I crafted my dream job and sent a proposal to Nando, the CEO of YITH.
\n\nIt is not easy to pitch yourself with an idea hoping that someone, I never met or spoken, understands this vision.
The doubts went through my head; “do I give up my business and work for the benefit of another company? What if I don’t get on? After all, I met 2 out of a team of 40 only three years ago… What do I do with my customers? Thinking of which, they have been demanding and not paying us on time. Plus, they annoy me when I want to be on holiday, not just that, they cause arguments between my wife and me. Because what is more important, family time or a site down and a business that is not earning enough money? Okay, this could work out, and I will try it for a year; if not, I can pick up my business again while my wife continues running it.” That was my thought process every day for months…
\nThen we agreed, and I was not sure if I should be happy or not. A year later, I can only say that working for Nando at YITH has been the best choice. He has been my mentor, supporter, devil’s advocate, and friend, but not a ‘boss.’ He has never told me what to do, but instead, asked questions to make me realize what is achievable, or even better, simply suggests me to read a book and come to my conclusions. YITH is an organization without hierarchy based on a holacratic structure.
\n![](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/DSC5927-scaled.jpg\")
The Yith Team\nLooking Back
\nI often think back to the moment my daughter passed away. She only lived for a few days, but ask any bereaved parent; it is often the thought of: ‘what could have been.’ It will have been nine years, and every day, I wonder how events would have unfolded if she had survived. So, maybe her memory lives on in every decision I make and the paths I decide to take. But did I make the right decisions? I would have said yes, though only last week, my wife suggested she never really processed the events nine years ago. The path ahead will not always be straight, but whatever the next turning is, I hope I can nudge it in the right direction. After all, I have big and exciting plans ahead!
\nIs this story helpful to someone? Maybe it is for one of two reasons.
\n\nIf you struggle to change your career, you can do this, though it might take a couple of years of a transitional period.
Only looking back do I realize that each small step slowly made a difference in my life. I am no guru or dare-devil entrepreneur that will tell you how to do things. No, I am an ordinary person with dreams and aspirations, just like there are so many in the world. But as I write this, it was WordPress that made this world smaller and empowered me to make a change. Learning from someone on the other side of the world and even getting work and customers from companies and people I never met before. Feeling welcomed into the WordPress community through Meetups and WordCamps added this human dimension and confidence that I can do ‘this’ too.
\nFor those who had a personal tragedy, I hope that I can give you hope and strength to try and put your energy into something else that can lead to more significant changes in your life. Our minds are mighty and the tiny small decisions of: ‘if I do this then that, and if this then that’ – you see life is like a game of chess and you can influence the outcome a lot… I accept, not always, but take it as one positive decision at a time.
\n![](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/PXL_20200912_144823691.MP_-scaled.jpg\")
The post Empowered To Make A Change appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 17 Mar 2021 08:13:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Ronald Gijsel\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"WPTavern: Automatically Create Image Slideshows With the Full Screen Galleries 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=113770\";s:7:\"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:215:\"https://wptavern.com/automatically-create-image-slideshows-with-the-full-screen-galleries-plugin?utm_source=rss&utm_medium=rss&utm_campaign=automatically-create-image-slideshows-with-the-full-screen-galleries-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:2946:\"Earlier today, core WordPress contributor Nick Halsey released Full Screen Galleries, a plugin that automatically creates a full-screen slideshow when site visitors click on an image. The plugin works with all images, regardless of whether they are in a gallery block. It also supports both the classic and block editors.
\n\n\n\nLightbox-type plugins are a dime a dozen. It is tough to wade through them to find the perfect solution. However, sometimes the simplest solution is the way to go. Halsey’s plugin has no settings screen, post metadata, or block options. It is plug-and-play. The only configuration is in activating the plugin itself.
\n\n\n\nFull Screen Galleries creates a slideshow-style overlay for all images located on a post or page. When a visitor clicks on one, the full-screen slideshow takes over the page.
\n\n\n\nHalsey has a demo page on his site where potential users can see the plugin in action.
\n\n\n\nThere are more advanced options out there. Some show EXIF data, create transition effects and other types of animation, and offer a boatload of customizable settings. However, I prefer the simplicity of something that I can activate and forget. Over the years, I have come to appreciate these types of plugins more and more. They let me get back to focusing on the parts of my sites that I care about.
\n\n\n\nFull Screen Galleries also figures out the full-sized image URL automatically. If a gallery uses thumbnail-sized images and links to the attachment page, the slideshow will still display it in full.
\n\n\n\nEach slide outputs forward and back arrows to scroll between the images. In the top left corner is an exit button. In the top right, the plugin outputs a northeast arrow button that links to the original image. It also displays the image caption if it is available.
\n\n\n\nFor many users, this is all they need. I am particularly interested in it because it works well with classic content. Many of the sites I am involved with have years of galleries from the pre-block era.
\n\n\n\nOne of the downsides is that the plugin relies on jQuery. The plugin’s code has a small footprint, but jQuery has grown into a bit of a beast over the years and is becoming less and less relevant with more recent features of modern JavaScript. For many WordPress sites, this may be a non-issue because their theme or some other plugin is already loading the jQuery library. This plugin will be a lightweight addition. For others who are keeping it lean, they might want to seek out alternative solutions.
\n\n\n\nRegardless, this plugin is going into my toolbox, ready to pull out when I need it. Overall, it is a dependable version 1.0.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 16 Mar 2021 22:41:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"BuddyPress: BuddyPress 7.2.1 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=317662\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://buddypress.org/2021/03/buddypress-7-2-1-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2581:\"BuddyPress 7.2.1 is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.
\n\n\n\nThe 7.2.1 release addresses 5 security issues which were reported privately to the BuddyPress team by Kien Hoang, in accordance with WordPress’s security policies:
\n\n\n\n- A vulnerability was fixed that could allow a privilege escalation from a regular user to Administrator, using the BuddyPress REST API
buddypress/v1/members/meendpoint. - A vulnerability was fixed that could allow a member to force a friendship on behalf of another member, using the BuddyPress REST API
buddypress/v1/friendsendpoint. - A vulnerability was fixed that could allow a member to read private messages in a thread they were not invited to, using the BuddyPress REST API
buddypress/v1/messagesendpoint. - A vulnerability was fixed that could allow a member to invite another member to join a group without being friends when that group restricted invites to friends only, using BuddyPress Nouveau and the BuddyPress REST API
buddypress/v1/groups/invitesendpoint. - A vulnerability was fixed that could allow a user that has just been demoted from an Administrator role to a Subscriber to add/edit/delete BuddyPress Member Types from the Administration screens introduced in the 7.0.0 release.
The BuddyPress Team also conducted a comprehensive security audit on all BuddyPress REST API endpoints, which led to:
\n\n\n\n- Improving all permission methods to use a WP_Error object as the default return value.
- Fixing unintended behavior allowing any member to edit their own Member Type.
- Fixing unintended behavior that allowed any logged in member to list the members of a private group.
For an even deeper dive, visit the 7.2.1 changelog.
\n\n\n\nOur deepest gratitude goes out to Kien for practicing coordinated disclosure and being extremely patient while we worked through these issues.
\n\n\n\nUpdate to BuddyPress 7.2.1 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.
\";s: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, 16 Mar 2021 20:45:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"WPTavern: Attackers Continue to Exploit Vulnerabilities in The Plus Addons for Elementor 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=113763\";s:7:\"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:235:\"https://wptavern.com/attackers-continue-to-exploit-vulnerabilities-in-the-plus-addons-for-elementor-plugin?utm_source=rss&utm_medium=rss&utm_campaign=attackers-continue-to-exploit-vulnerabilities-in-the-plus-addons-for-elementor-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:2911:\"Last week, security researchers at Seravo and WP Charged reported a critical zero-day vulnerability in The Plus Addons for Elementor on March 8, 2021. WPScan categorized it as an authentication bypass vulnerability:
\n\n\n\n\n\n\n\nThe plugin is being actively exploited to by malicious actors to bypass authentication, allowing unauthenticated users to log in as any user (including admin) by just providing the related username, as well as create accounts with arbitrary roles, such as admin. These issues can be exploited even if registration is disabled, and the Login widget is not active.
It’s important to note that this particular vulnerability affects users of the commercial version of The Plus Addons for Elementor, not the free version, and not core Elementor.
\n\n\n\nThe plugin’s authors pushed out a partially patched version 4.1.6 after disclosure and then a second version 4.1.7 to more fully address the issue.
\n\n\n\nWordfence is reporting that they are still blocking attempts on sites that are using unpatched. They have blocked 1900 site takeover attempts from a specific username, blocked 1170 attempts from a specific email, and blocked 4,000 attempts over the past week. Attackers are still targeting sites that have not updated to the patched version.
\n\n\n\n“Evidence suggests it had been actively exploited for ~5 days before that,” Wordfence threat analyst Chloe Chamberland said on the Wordfence Live show today. “Our earliest date of compromise was March 5th that we know of so far. There was a vulnerability for a few days that nobody really knew about except for this attacker who was going out and exploiting it.”
\n\n\n\nThose whose sites have been exploited have seen malicious admin accounts created. Others have experienced every URL on their sites redirecting, making it very difficult to clean. Attackers have also been installing malicious plugins called “WP Strongs” and “WP Staff.” Those who cannot access the admin dashboard will have a more difficult time removing these plugins.
\n\n\n\nElementor users who have the Plus Addons plugin installed are advised to update to the latest version and check for malicious plugins and files. Ideally, site owners who were subject to exploits would have a backup to restore. Chamberland concluded the Wordfence Live broadcast today by walking users through manually cleaning up exploited sites, including replacing the wp-includes and wp-admin folders, along with standard files outside those directories. The recording might be helpful for those who are struggling to clean up the damage.
\";s: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, 16 Mar 2021 19:26:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Google Accuses Microsoft of “Breaking the Open Web”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=113773\";s:7:\"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/google-accuses-microsoft-of-breaking-the-open-web?utm_source=rss&utm_medium=rss&utm_campaign=google-accuses-microsoft-of-breaking-the-open-web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4506:\"Just before the weekend, Google published a caustic statement on Microsoft’s public support of Australia’s new law that forces Google and Facebook to pay publishers for their content. The law requires the companies to negotiate licensing agreements with publishers in order to include news articles in both search and news feeds, including snippets.
\n\n\n\nLast month, Microsoft published its endorsement of the Australian proposal and stated intentions for its Bing search engine to comply.
\n\n\n\n“In the hunt for better ideas, Google’s threat to boycott an entire country got our attention,” Microsoft President Brad Smith said.
\n\n\n\n“Satya Nadella and I reached out to Prime Minister Morrison. It was an opportunity to combine good business with a good cause and, as we explained, even if Google wanted to leave Australia, we would stay.”
\n\n\n\nAfter negotiations, Facebook decided to simply block Australian publishers from posting and block users from sharing any news originating from the country. In a full reversal, the company inked a three-year agreement with News Corp today, which covers The Australian national newspaper and several metropolitan papers.
\n\n\n\nSimilarly, Google did not make good on its threat to remove its search engine from Australia, reluctantly making deals with Australian publishers and News Corp a few weeks ago. The company’s statement on Friday characterizes Microsoft’s position and its overt contrasting with Google, as “naked corporate opportunism” and an attack:
\n\n\n\n\n\n\n\nWe also believe that this important debate should be about the substance of the issue, and not derailed by naked corporate opportunism … which brings us to Microsoft’s sudden interest in this discussion. We respect Microsoft’s success and we compete hard with them in cloud computing, search, productivity apps, video conferencing, email and many other areas. Unfortunately, as competition in these areas intensifies, they are reverting to their familiar playbook of attacking rivals and lobbying for regulations that benefit their own interests. They are now making self-serving claims and are even willing to break the way the open web works in an effort to undercut a rival. And their claims about our business and how we work with news publishers are just plain wrong.
The historic rivalry has been reignited, as Google fired back at Microsoft’s insinuation that the company doesn’t support journalism and is unwilling to collaborate with publishers.
\n\n\n\n“Proposals that would disrupt access to the open web (such as requiring payment for just showing links to websites) would hurt consumers, small businesses, and publishers,” Google’s SVP of Global Affairs Kent Walker said. “That’s why we’ve engaged constructively with publishers around the world on better solutions and will continue to do so.”
\n\n\n\nMicrosoft supports Australia’s new law as a means to rectify “competitive imbalance between the tech sector and an independent press.” It also gives the company a high perch from which to call out Google and Facebook as “profitable tech gatekeepers on which businesses must advertise to reach consumers.” Microsoft believes its endorsement spurred Google to reverse its decision in order to remain in competition for the Australian search market.
\n\n\n\n“Unlike Google, if we can grow, we are prepared to sign up for the new law’s obligations, including sharing revenue as proposed with news organizations,” Brad Smith said. “The key would be to create a more competitive market, something the government can facilitate. But, as we made clear, we are comfortable running a high-quality search service at lower economic margins than Google and with more economic returns for the press.”
\";s: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, 16 Mar 2021 03:13:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: Compatibility Is Not Enough: The Eksell WordPress Theme Creates Art With Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=113779\";s:7:\"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:221:\"https://wptavern.com/compatibility-is-not-enough-the-eksell-wordpress-theme-creates-art-with-blocks?utm_source=rss&utm_medium=rss&utm_campaign=compatibility-is-not-enough-the-eksell-wordpress-theme-creates-art-with-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6218:\"It is easy to become jaded after reading the same old keyword-stuffed theme descriptions. After viewing the same hero-plus-three-boxes theme designs. After seeing another theme with “block editor styles” that utterly fails to deliver on its promise.
\n\n\n\nAs I peruse the demo of Anders Norén’s latest WordPress theme, Eksell, I am reminded that artists still exist in the WordPress theming realm. For those familiar with his past theming work, this is not revelatory. Most of his 20+ free themes have 1,000s of active installations — Chaplin even became the base of the Twenty Twenty default theme.
\n\n\n\nAwaiting a theme from Norén is almost like counting down the days until your favorite director’s film hits the theater. You know you are going to like it before you see it. Even the worse outing is better than everything else spilling through the pipeline. Every now and then, you are greeted with something special.
\n\n\n\nI could not wait this time. Norén’s latest project is at a pitstop in the review system, so it is not officially available in the WordPress theme directory yet. In the meantime, anyone can still grab a ZIP file from its Trac ticket and upload it the old-fashioned way.
\n\n\n\nEksell is a love letter to the block editor.
\n\n\n\nIt is more than just making a few style adjustments to work around any quirks of the default block styles. It is an extension of those styles to create something unique. It is more than running a theme through a few tests and calling it compatible. It is looking at common problems and making sure they are styled correctly on the front end. And it is more than slapping a few blocks together and calling them a pattern. It is about providing users with a one-click solution for custom-designed or tough-to-build elements.
\n\n\n\nBuilding WordPress themes means being able to wrangle tons of elements that users can rearrange on a whim. The block editor has increased those pieces at least tenfold. It is rare to see a theme that manages to handle every edge case, and I am sure there are some that Eksell misses. However, the whole of the work is one of — if not the best — block-ready themes available today.
\n\n\n\nIf there is one area in which Eksell did not go far enough, it is with block patterns. The theme registers five of them:
\n\n\n\n- Cover Header
- Featured Items
- Call to Action
- Contact Details
- Stacked Full Groups
Each of these is in the demo. However, there are some missed opportunities, such as the following three-column “pattern”:
\n\n\n\nPros at building layouts with blocks could recreate that in minutes. A one-click option for inserting it into a post might save a headache or two for average users.
\n\n\n\nThis is not the only example. Eksell’s demo is full of experimental groupings that showcase the flexibility of the block system. As bold as it is, the theme is a bit timid with its patterns. There is no need to be. They are already there. They simply need to be registered in the system.
\n\n\n\nUsers can stack individual Image and Gallery blocks, making them appear as part of the same gallery. The theme automatically adjusts the margins between the blocks, bringing them together.
\n\n\n\nAnother candidate for a block pattern.
\n\n\n\nAnd, here’s the thing. I firmly believe the traditional theming paradigm held back this theme. Its uniqueness is in its handling of blocks, which are still limited to the content area in WordPress. When the site editor and global styles land in WordPress later this year, a theme like this would already be miles ahead of others in integrating with Full Site Editing.
\n\n\n\nEksell is more than just a theme that does cool stuff with the block editor. It is a genuinely useful portfolio theme. Instead of marketing it as yet another multipurpose general-purpose project, it has a target audience. Despite that, it is well-rounded enough to handle a variety of situations. Norén made sure the theme would work for blogging with on-point typography.
By default, the theme displays blog posts in a grid-style portfolio. However, Jetpack users can opt to use the plugin’s portfolio project post type to keep their portfolio separate from their blog.
\n\n\n\nOne feature that might go overlooked is that Eksell provides an option to upload a fallback featured image. Far too often, portfolio-style themes with post-image grids fail to load a default image. The expectation is that the user will have featured images for every post, which is not always the case. When a theme is built around this idea, it needs to cover all of its bases, covering edge cases where things might fall apart. Eksell handles this, but Norén is an old pro at this point. He doubtless knows these common pitfalls.
\n\n\n\nThe theme does not overwhelm users with options. It provides enough flexibility to personalize the theme’s color scheme and make a few layout-related decisions.
\n\n\n\nOld-school theme options will be a thing from a past era in the coming years. It is best to focus on the elements users will be working with for the long term. The customization power is with what users decide to do with blocks, and Eksell is ready for whatever users might throw at it.
\n\n\n\nEvery WordPress theme author should dive into the Eksell theme. Consider it a free masterclass in building on top of the block editor. It is the standard by which we should be judging all other offerings.
\";s: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, 15 Mar 2021 22:54:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"Gutenberg Times: Gutenberg, Block Editor and WordPress Roadmap\";s:7:\"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:34:\"https://gutenbergtimes.com/?p=6188\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://gutenbergtimes.com/mullenweg-on-gutenberg-roll-out-plan/\";s: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:51059:\"Last updated March 14, 2021
\n\n\n\nFull-Site Editing Go/NoGo decision for 5.8
\n\n\n\nNow that WordPress 5.7 is released since March 9th, 2021, the core team is planning 5.8 and putting the next release team together.
\n\n\n\nJosepha Haden Chomphosy published two posts with additional information.
\n\n\n\n- Full-site editing pre-merge overview an updated time line of decision-making on the prototype/MVP and communication roll-out for the merge of Full-Site Editing (FSE) into the core software.
- In a follow-up post, Josepha shared the core team’s early thoughts on 5.8 Planning and elaborated on the changes, depending on if FSE will be merged or not in assembling the release team.
The team will decide on April 13 or 27, if a successful merge can be achieved for the 5.8 release in July (Yes, it was moved a month) or if it will be pushed to 5.9 in December 2021.
\n\n\n\nBig Picture Goals 2021
\n\n\n\nJosepha Haden set the goal posts for the WordPress projects for 2021
\n\n\n\n- Timeline for Full Site Editing:
- MVP in the plugin by April 2021
- v1 in Core by WordPress 5.8.
- Learn.WordPress
- regularly publish new workshops and lesson plans,
- maintain a high pass rate on workshop quizzes to establish learner success and comprehension.
- Block Editor related Workshops
- Contributor tools decrease the manual overhead of maintenance work for teams through better tooling.
Follow along with these resources:
\n\n\n\n- WordPress 5.7 Development Cycle
WordPress 5.7 Beta 1 is scheduled for February 2nd, 2021. - Keeping up with Gutenberg Index
if you missed a week or month with updates from team you can always go back - Weekend Edition of the Gutenberg Times Archive
- Gutenberg Changelog Podcast, every other week.
State of the Word 2020
\n\n\n\nDecember 17, 2020, Matt Mullenweg gave his State of the Word talk with an extensive Q & A afterwards with him and other team members.
\n\n\n\n\n\n\n\nWordPress 5.7 – March 2021
\n\n\n\nWordPress 5.7 planning has already begun.
\n\n\n\n- WordPress 5.7 Development Cycle
- Francesca Marano posted WordPress 5.7: What’s on your wishlist? to collect input from the WordPress Community.
- JB Audras posted a Call for Volunteers – Early bug scrubs for WordPress 5.7
Block Editor in 2021 – Full-Site Editing and Global Styles
\n\n\n\nMatias Ventura posted a Status Check: Site Editing and Customization. In this post, Ventura summarizes the current status of Gutenberg’s Phase 2 Projects: Site Editor, Block-based Themes, Navigation Block, Query Block, and Global Styles.
\n\n\n\nHe ends with: “In terms of timelines, all of these are in advanced stages and can be used in the Gutenberg plugin already. The main hurdle to include the work in major WordPress releases are the various dependencies between each project when it comes to ensuring a great user experience. The immediate focus is then on completing the milestones, stabilizing the work, and doing as much testing with different kinds of users as possible. For that last purpose, there will be some calls for testing announced soon as part of the Site Editing Outreach Program.”
\n\n\n\n🔖 Bookmark “Keeping up with Gutenberg – Index”
The WordPress Make Blog posts from various teams involved in Gutenberg development Phase 2 are listed on one page: Design, Theme Review Team, Core Editor, Core JS, Core CSS from June to December 2020
WordPress 5.6 – December 2020
\n\n\n\n\n\n\n\n\n\n\n\nUpdate May 13, 2020: Josepha Haden posted
\n\n\n\n\n\n\n\nWP5.5 – August Release
\n\n\n\n- Feature Plugin: Automatic updates functionality for major WordPress Core releases (opt-in).
- Complete: Convert the widgets-editing areas complete.
- Complete: Functionality for full site editing complete behind experimental flag in the plugin.
- Complete: Global styles behind experimental flag in the plugin.
- Ship: Update WordPress Core to include current releases of the Gutenberg plugin.
- Ship: Navigation menus block in Core.
- Ship: Automatic updates for plugins and themes in Core.
- Ship: Block directory in Core.
- Ship: XML Sitemaps
- Ship: Lazy Loading
Quoted from Josepha’s post, these are planned items.
\n\n\n\n“Current release of Gutenberg plugin”, means the current version at time of 5.5 Beta 1, which is planned for July 7, 2020. It probably will be Gutenberg 8.5 or 8.6. Final release of 5.5 is scheduled for August 11, 2020.
\n\n\n\nDesign & Dev Updates in May 2020
\n\n\n\n- What’s next in Gutenberg? (May) by Riad Benguella
- Gutenberg Phase 2 Friday Design Update #52
- Gutenberg Phase 2 Friday Design Update #51
Matt Mullenweg at WPBlockTalk
\n\n\n\nMatt Mullenweg open the April 2, 2020, WPBlockTalk conference with an updated Gutenberg Roadmap and what’s next in Gutenberg and Matias showed off the Full-site Editing experience.
\n\n\n\n\n\n\n\nDesign updates Gutenberg Phase 2
Jan – April 2020
\n\n\n\nApril 2020
\n\n\n\n\nMarch 2020
\n\n\n\n\nJan / February 2020
\n\n\n\n\nUpdate on nine focus projects
\n\n\n\nIn December 2019, Josepha Haden, executive direct of the open-source projects published an update on the nine focus projects.
\n\n\n\nThe migration of the widgets to blocks and the merge of the Site Health project into core were shipped in 5.3.
\n\n\n\nFor the work in progress, Josepha also added the targeted versions, when we can expect them in core.
\n\n\n\n- Navigation Block to build menus (5.5)
- Block Directory for discovery and installation single block plugins from the Block Inserter (5.5)
- Automating update opt-in for plugins and themes (5.5)
- Themes registering content areas for block editor (5.6)
- Widget areas and Customizer are able to use blocks (5.6)
- Automatic update of major core releases (5.6)
The WordPress Core Roadmap page shows the target dates for the next releases. WordPress 5.5 is planned for August 2020 (Call for tickets has already been published) and WordPress 5.6 is slated to be released in December 2020.
\n\n\n\nGutenberg Phase 2 Updates
September – December 2019
\n\n\n\nNov / December 2019
\n\n\n\n\nOctober 2019
\n\n\n\n\nSeptember 2019
\n\n\n\n\nState of the Word 2019 – Matt Mullenweg
\n\n\n\n\n\n\n\nDuring his State of the Word 2019 in St. Louis in October 2019, Matt Mullenweg talked a lot about the first full year of Gutenberg.
\n\n\n\nThe Four Phases of Gutenberg.
\n\n\n\n- Easier Editing – already in Core, refinement is ongoing
- Customization – Full Site editing, Block Patterns, Block Directory, Block based themes
- Collaboration – A more Google Doc co-authoring
- Multi-lingual – Core implementation for Multi-lingual sites.
Currently, it’s all about Phase 2, and not only to make the post / page content editable via the block editor but add site-building capabilities to the block editor. The goal is to provide a single interface for all site customizations.
\n\n\n\n\n\n\n\n
Gutenberg Phase 2 Updates
June – August 2019
\n\n\n\nAugust 2019
\n\n\n\n\nJuly 2019
\n\n\n\n\nJune 2019
\n\n\n\n\n*There is no Update #25
\nUpdated July 4th, 2019 with Mullenweg’s Summer update.
\n\n\n\nWordCamp Europe 2019
\n\n\n\nAt WordCamp Europe, Matt Mullenweg gave his Summer Update.
\n\n\n\n\n\n\n\n\n\n\n\nWeekly Gutenberg Phase 2 Updates
March – May 2019
\n\n\n\nMay 2019
\n\n\n\n\nApril 2019
\n\n\n\n\nMarch 2019
\n\n\n\n\nProgress on Nine Projects.
\n\n\n\nFebruary 11, 2019.
\n\n\n\n- #1 Navigation Menu is still in discussion on GitHub. (#13690)
- #2 has been moved forward already for quite a bit. The latest Gutenberg release(5.0), incorporated the RSS widget. Mel Choyce publishes regular updates on this particular project
- #3 is coupled with #2
- #4 hasn’t started yet
- #5 Partial integration in core is scheduled for the WordPress 5.1 release
- #6 & #7 haven’t started yet
- #8 hastn’t started yet. It is the one that’s most exciting to me, as the proliferation of blocks are getting a bit overwhelming.
- #9 The Core is still discussing best methodology and taxonomy for ticket gardening. Jon Desrosiers published a proposal on how to handle punted tickets in the short term and also how to manage the other open tickets.
Design Updates for Gutenberg Phase 2
\n\n\n\nEvery Friday, Mark Uraine publishes Updates for Gutenberg Phase 2 on the make/design blog. Here is the list:
\n\n\n\nFebruary 2019
\n\n\n\n- Update #7 (Feb 22, 2019)
- Update #6 (Feb 15, 2019)
- Update #5 (Feb 8, 2019)
- Update #4 (Feb 1, 2019)
January 2019
\n\n\n\nUpdate #3 (Jan 25, 2019Update #2 (Jan 18, 2019) Update #1 (Jan 11, 2019
\nNine Projects for 2019
\n\n\n\nDec 8th, 2019. A couple days after the WordPress 5.0 release, Matt Mullenweg posted on the make/core blog the 9 projects for 2019, highlighting what he outlined in his State of the Word at WordCamp US 2018
\n\n\n\n- Creating a block for navigation menus.
- Porting all existing widgets to blocks.
- Upgrading the widgets-editing areas in
wp-admin/widgets.phpand the Customizer to support blocks. - Providing a way for themes to visually register content areas, and exposing that in Gutenberg.
- Merging the site health check plugin into Core, to assist with debugging and encouraging good software hygiene.
- Providing a way for users to opt-in to automatic plugin and theme updates.
- Providing a way for users to opt-in to automatic updates of major Core releases.
- Building a WordPress.org directory for discovering blocks, and a way to seamlessly install them.
- Forming a Triage team to tackle our 6,500 open issues on Trac.
WordPress 5.0 “Bebo” released on December 6th, 2018
\n\n\n\nDecember 6th, 2018. Today around 1:30pm ET, the core team released the WordPress 5.0 and with it the new block editor as default editor for content creators.
\n\n\n\n- New Gallery Block, Convert Blocks, Business News and more Weekend Edition #164 \n
- Full-site Editing MVP: Can I Build a Landing Page? \n
- Full-Site-Editing – the Ultimate Resource List \n
\n\n\n\n
December 3rd, 2018. Matt Mullenweg posted the new target date for the WordPress 5.0: December 6th, 2018, the same day PHP 7.3 will be released. WordPress 5.0 includes not only the new Block editor but also compatibility fixes for the new PHP version.
\n\n\n\nBased on the stability, testing, and reports on the release candidates for WordPress 5.0 so far, we are now targeting Thursday December 6th for public release and announcement. 5.0.1 will open for commits soon, and will be an area people can choose to focus on at the contributor day at WordCamp US in Nashville this Sunday.
As before, if new information arises that indicates the software is not stable, we will adjust or remove the target date.
Below Questions and Answers are taken from Matt Mullenweg’s Gutenberg FAQs as well as from his post about the new target date.
Not at all. When it’s released, you get to choose what happens. You can install the Classic Editor plugin today and when 5.0 is released, nothing will change. We’ve commited to supporting and updating Classic Editor until 2022. If you’d like to install Gutenberg early, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.
Some people think so, some don’t. There have been 9 major WordPress releases in previous Decembers. December releases actually comprise 34% of our major releases in the past decade.
That’s totally okay, there’s nothing that says you must update the moment there’s a new version released. You can push the button whenever you’re ready.
No problem, install the Classic Editor plugin and 5.0 will be indistinguishable from 4.9.8 for your posting and editing experience, and you’ll still get the other improvements and fixes that have gone into 5.0. Classic Editor is supported until 2022, and now allows you to switch between Classic and Gutenberg on a per-user or per-post level.
November 30, 2018. WordPress 5.0 RC2 is scheduled for today. Earlier this morning the team released Gutenberg 4.6.1. “This brings plugin up to parity with RC2 packages” noted Matias Ventura on the #core-editor Slack channel.
Read also today’s status update on the Make.Core Blog
When will 5.0 be released?
\n\n\n\nRead Matt Mullenweg’s answer in his blog post: “WordPress 5.0: A Gutenberg FAQ“
\n\n\n\nWe have had a stable RC1, which stands for first release candidate, and about to do our second one. There is only currently one known blocker and it’s cosmetic. The stability and open issues in the release candidates thus far makes me optimistic we can release soon, but as before the primary driver will be the stability and quality of the underlying software. We made the mistake prior of announcing dates when lots of code was still changing, and had to delay because of regressions and bugs. Now that things aren’t changing, we’re approaching a time we can commit to a date soon.
Matt Mullenweg answer in his blog post Nov 29, 2018
\n\n\n\n
November 23, 2018 WordPress 5.0 RC1 – the first release candidate was released about 4 days late. On Nov 21, Matias Ventura wrote: “The date for 5.0 release is under consideration, given it’s not plausible for it to be the on 27th. “
\n\n\n\n\n\n\n\nGutenberg 4.5.1 was released Nov 20th. This is the last Gutenberg version before the 5.0 Final release. There will be bug fixes in between, but no more changes to API etc. – or so I hear. It’s included in the WordPress 5.0 Release candidate 1 version. You can test both via the WordPress Beta plugin.
\n\n\n\n\n\n\n\nThe WordPress 5.0 release date has shifted from the 27th to give more time for the RC to be fully tested. A final release date will be announced soon, based on feedback on the RC.
Matias Ventura, on the make.core blog
Unless they are blockers to the 5.0 release, newly found issues will be tagged for Gutenberg 4.6 and 5.0.1.
November 9, 2018. Developer lead for Gutenberg, Matias Ventura announced today the updated schedule for WordPress 5.0 release:
\n\n\n\n- Final release scheduled for November 27, 2018
- Beta 4: Monday November 12, 2018
- Beta 5: Thursday, November 15, 2018
- Release Candidate 1: Monday November 19, 2018
\n\n\n\n\n\n\n\nAfter listening to a lot of feedback — as well as looking at current issues, ongoing pull requests, and general progress — we’re going to take an extra week to make sure everything is fully dialed in (…)
Matias Ventura, on make.blog November 9th, 2018.
October 31, 2018. After the first beta release date slipped to October 24, Gary Pendergast updated the release schedule yesterday. He added a few more Beta release dates, which pushed the RC 1 to November 12th. The final release date of November 19, hasn’t been moved, though.
\n\n\n\n- Beta 2 released Oct 30
- Beta 3: released Nov 5, 2018
- Beta 4: November 5, 2018
- RC 1: November 12, 2018
- Final release: November 19, 2018
Details can be viewed in the post on make.wordpress
\n\n\n\nUpdated Nov 6, 2018: updated with release dates and post for Betas 2 + 3 bph
\n\n\n\n\n\n\n\nAlso updated the photo credit. The feature image was shot by Val Vesa and can be found on WCEU’s Flickr account
\n\n\n\n\n\n\n\n
On October 3rd, 2018, Matt Mullenweg published “A Plan for 5.0” on the WordPress Make Blog with the leadership team that will push Gutenberg over the finish line of becoming the default editor for WordPress.
\n\n\n\nGary Pendergast, WordPress Core Developer, followed suit with his post; Proposed WordPress 5.0 Scope and Schedule
\n\n\n\nThe Scope:
\n\n\n\n- Merging the Gutenberg plugin into trunk.
- Updating the default themes to work well with the block editor
- Creating the new Twenty Nineteen theme.
- Creating an upgrade experience to remove the Gutenberg plugin and offer the Classic Editor plugin.
The Schedule
\n\n\n\n- October 3, 2018 WordPress 5.0 Kickoff meeting
- October 19: Beta 1
- October 30: RC 1
- November 19: Release
“We know there is a chance that 5.0 will need additional time, so these dates can slip by up to 8 days if needed. If additional time beyond that is required, we will instead aim for the following dates:” Gary wrote,
\n\n\n\n- Secondary RC 1: January 8, 2019
- Secondary Release: January 22, 2019
The following days, strong voices suggested to make Plan B to Plan A and not release WordPress 5.0 until after the busiest online business time of the year for the United States universe.
\n\n\n\nHere an opinion piece on the WPTavern: “If Deadlines Are Not Arbitrary, Why Not Release WordPress 5.0 in the Beginning of January?“
\n\n\n\nAt Pauli Systems, we plan to beta-best WordPress 5.0, help surfacing problems and report them either on Trac or on GitHub. The amount of issues and the time it will take to fix them will determine the final release date for WordPress 5.0.
\n\n\n\n\n\n\n\nWith the track record on estimating release dates this year, there might be a RC (Release Candidate) in November. It seems to be a given that the final release will be pushed into late January 2019.
Birgit Pauli-Haack,Oct 3rd, 2018 0 Pauli Systems
WordPress 5.0 Kick-off Meeting
\n\n\n\n\n\n\n\nupdated: October 5, 2018 / bph
\n\n\n\n\n\n\n\n
At WordCamp Europe, co-founder of WordPress and CEO of Automattic, Matt Mullenweg, laid out the Gutenberg roadmap for the next three months.
\n\n\n\nFor the rest of June, the development team will work on the few issues and features that are identified to land in the first core version.
\n\n\n\nIn July more users will be able to use Gutenberg on wordpress.com as well as on self-hosted WordPress sites via a “Try Gutenberg” prompt in a future 4.9.x version.
\n\n\n\nIn August, the team will work on bug fixes and the merge proposal to land in WordPress Core. Mullenweg said that after one hundred thousand users and two hundered fifty thousand blog posts, Gutenberg could be ready to be released with WordPress 5.0 as soon as August. He also stress he is not making any promises, though.
The Gutenberg Roadmap
\n\n\n\nJune 2018
\n\n\n\n- Freeze new features into Gutenberg
- Hosts, agencies and teachers invited to opt-in sites they have influence over.
- Opt-in for wp-admin users on WP.com
- Mobile App support in the Aztec editor across iOs and Android.
July 2018
\n\n\n\n- 4.9.x release with a strong invitation to install either Gutenberg or Classic Editor plugin
- Opt-out for wp-admin users on WP.com
- Heavy triage and bug gardening, getting blockers to zero
- Explore expanding Gutenberg beyond the post into site customization.
August 2018 and beyond
\n\n\n\n- All critical issues resolved
- Integration with Calypso, offering opt-in users.
- 100k+ sites having makde 250k+ post using Gutenberg
- Core merge, beginning the 5.0 release cycle.
- 5.0 beta releases and translations completed
- Mobile version of Gutenberg by the end of the year.
Video: Gutenberg Roadmap section of Matt Mullenweg’s Keynote
\n\n\n\nFind the transcript below.
\n\n\n\n\n\n\n\nUpdate July 6, 2018
So far the Gutenberg section of Matt Mullenweg’s “Summertime Update”. Earlier this month, the volunteers of WordCamp Europe uploaded the video of the whole keynote to WordPress TV.
![\"WP](\"https://i0.wp.com/wpbuffs.com/wp-content/uploads/2017/11/Care-Plan-Wide.jpg?w=640&ssl=1\")
\n\n\n\nFeatured Image: Photo by Stephen M. Blythe, allmyfriendsarejpegs.com
\n\n\n\nTranscript: Matt Mullenweg’s Keynote at WordCamp Europe (Excerpt)
\n\n\n\n(…) The major features that are in effect so far are we have a block based writing experience, with over 20 blocks built in. Gutenberg is fully adaptive, meaning that whether you’re looking at it on a small screen, a medium screen, a large screen, a huge screen, the design and the functionality adapts to be fluid and easy to use on any of those.
\n\n\n\nThere is ah, there we go … Optimized for direct manipulation of content, so we’re bringing it closer to where what you’re editing looks a lot more like what you’re seeing on the front page. They have a block aid [inaudible 00:00:43], support for static and dynamic blocks.
\n\n\n\nMatt’s Favorite Gutenberg Feature: Copy/Paste API
\n\n\n\nThis is one of my favorite, the universal API, which is copy and paste. Who’s ever tried to copy and paste things into the WordPress editor, or anyplace else, and it just goes kind of sideways?
\n\n\n\nGutenberg already has support for fully supported copy and paste from Google Docs, a Apple’s Pages, everyone’s favorite Microsoft Word, Office 365, Evernote, Legacy WordPress, random webpages, and then finally something that I know will be very popular with this audience is Markdown.
\n\n\n\nThat’s actually what you are seeing in this little GIF there, is a copy and paste from a Markdown source. That’s a note editor or for wherever you want. You paste into Gutenberg, it translates it just instantly into Gutenberg blocks. It’s very, very slick. If you haven’t tried this yet, I’d highly recommend trying it. It’s one of my favorite hidden features alongside … I’ll tell you about my other favorite hidden feature. Which is that when you copy and paste the URL onto some text, it auto links it. Saves a ton of time.
\n\n\n\nTemplates, Shared Blocks, Nested Blocks and Child Blocks
\n\n\n\nThere are templates for predefined blocks. This is starting to go into where you can see hints of where we are going to end up, with full site customization with this. Which basically allows you to create for your users or for yourself kind of pre-built layouts where you can say, “Okay. A title goes here, an image goes here, some text goes here, a map goes here.” That can be reused over and over again, or assigned to entire pages. There’s shared blogs, so if you do want to reuse things across the entire site, that can be a shared unified resource. So when you edit it once, it shows up everywhere.
\n\n\n\nAnd finally, we are very excited about, that we have nested blocks and child blocks. These are blocks within blocks. Like it’s turtles and blocks all the way down, and child blocks, which only work if the parent block is there. Perhaps like your children. Media drag and drop. Extensions where you can add extra things to the sidebar. Like this beautiful “Hello Belgrade” extension here.
\n\n\n\n30 Gutenberg releases, 1,700 issues open , 1,100 closed
\n\n\n\nThere have been 30 Gutenberg releases, since we started, and 12 just since WordCamp US in December. As you can see, this is kind of running through all the different releases. There have been over 1,700 issues opened, and 1,100 closed in the Gutenberg Project thus far. From the development point of view, I’m very proud of it. We have open development, design-led testing in our releases, presentations across pretty much every WordCamp now, including here. It’s developed a wide awareness. Support and awareness in every single page builder out there. You know the names.
\n\n\n\nWe already have people who’ve extended Gutenberg through plugins they are starting to pick up in the directory, and major sites. Agencies and others have been building and launching things with Gutenberg because, to be honest, it works. It’s not perfect yet. We’re not ready to release it yet, but for the things it does, it does them well. You can actually start using this in production already.
\n\n\n\nThere are now 14,000 sites actively using Gutenberg. So this isn’t just installed it’s actually active. Just released this week are tools for enterprises. This one called Gutenberg Ramp, which is a new plugin from VIP which basically allows them to turn Gutenberg on for certain post ID’s, page ID’s or content text. So that way you can start to phase in. Say you have a really complex setup of WordPress and maybe certain post types of things, extra customization. You can start to turn Gutenberg on for parts of it, not for others until you get to the point where you have everything on and fully done.
\n\n\n\nBut the question I’m going to preempt it, so you don’t need to ask it is “What’s coming next in the world of Gutenbergification?” Which is just kinda fun to say. It sounds almost like a German word right?
\n\n\n\nRoadmap For Gutenberg Roll-Out
\n\n\n\nHappening in June
\n\n\n\nHere’s the roadmap. So these are things happening in June which means they are highly .. [inaudible] . First I’m going to freeze new features coming in to Gutenberg. We’ve reached a point where there is a functionality that matches in affect of in the area it exceeds what we accomplished in the editor. We’re gonna encourage host agencies and teachers to start opting in folks that they have influence over to start using Gutenberg. Now very much … especially if it’s someone who you’re working with close to so that you can start to gather feedback from third party users of it, people who are involved in development everyday and pass that back, of course, to developers. This is to compliment the user testing, since the user testing that we’ve already been doing.
\n\n\n\nOne of the hosts that’s gonna be sort of contributing to this is WordPress.com so there is several hundred thousand, in the high numbers of thousands folks from WordPress.com that actually use wp-admin interface primarily. So we’re gonna be offering a call to action to opt-in. You can start using it very soon. One of the key measures that we are tracking there are the number of sites and the number of posts that are using this.
\n\n\n\nThen finally the mobile apps, which I said are getting more and more popular. Right now, if you move between editing things in the mobile apps, Gutenberg, it breaks in pretty spectacular fashion. So within the next few weeks that will be all fixed up across both IOS and Android.
\n\n\n\nComing up in July: Thousands more users .org and .com
\n\n\n\nComing up in July, there is going to be a 4.9 point WordPress release that has a strong invitation in the dashboard. The first time we’ve had this, to either install Gutenberg or the Classic Editor Plugin. So basically we will be encouraging people to get on the train early, or if when 5.0 comes out and your site is not gonna be ready for it, install the Classic Editor Plugin. For those who don’t know, basically locks in your site to use how WordPress WYSIWYG editor works today. So it kinda opts you out of Gutenberg. We’re, of course, going to be tracking the use of both those.
\n\n\n\nWe’re gonna switch to opt-in for their wp-admin on dot com to be opt-out and I’m tracking who opts out and trying to gather as much data from them as well because there’s gonna be a lot of information there, especially from people who might be using third party plugins on WordPress.com. Be a heavy, heavy triage on bug gardening, getting all the blockers to zero. Then finally, we’re gonna actually kick off and maybe even branch off the customization leads to start the work for what we wanna launch hopefully this year. Which is more of the full site editing experience of Gutenberg.
\n\n\n\nIn August and Beyond: Merge Proposal
\n\n\n\nSo in August and beyond we’ll have all critical issues resolved. It’ll be integrated with the Calypso interface on WordPress.com, which is where the majority of people use it. I want to have 100,000 sites, 250,000 posts made, so 100,000 sites active with Gutenberg over 10x, where it is today, about 10x where it is today. A quarter million posts I think we’ll be able to say that a lot of the bugs will be worked out. We’re gonna merge with Core beginning the 5.0 release cycle. So beta releases, translations and then finally we are planning … there’s work undergoing, it’s not ready yet, but there will be full mobile versions of Gutenberg at the end of the year in the iOS and Android app.
\n\n\n\nBy August, they won’t break when you move between them. Of course, Gutenberg is done in a way that makes the content and the Markup backwards compatible. We’re actually gonna have the blocks supported in the mobile apps so that as you drag and drop blocks, move them around, have different sort of fun things you can do, that’ll all be there.
\n\n\n\nWe could have a 5.0 as soon as August. Some of these things that I put up there, I’m very, very sure about. The big thing that we’re not sure about is as we vastly increase the average usage of Gutenberg across hopefully 100,000 sites. “What’s gonna come in?”
\n\n\n\nNot date promised, though.
\n\n\n\nThe non-deterministic nature of fixing bugs means that I don’t know exactly the issues that could raise. Whether they’re going to be small tweaks or rather they might be sort of huge things that are going to require a few weeks of development. That is why I can’t promise you a date but we’ve done a lot of testing this far so the nature of bugs that we find … there’s no black swans in there of bugs. I do think that 5.0 is gonna be ready within a relatively short time frame. And that’s all I got so thank you very much.
\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 14 Mar 2021 22:30:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:34;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:109:\"Gutenberg Times: Full-Site Editing Testing, Merge Timeline, and Plugins for Block Editor Weekend Edition #162\";s:7:\"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=17216\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://gutenbergtimes.com/full-site-editing-testing/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:18059:\"Howdy,
\n\n\n\nWith the WordPress 5.7 out of the way, the next couple of month are all about Full-site Editing testing and planing for 5.8.
\n\n\n\nI love it when a plan comes together! The WordPress team responsible for the release of the 5.7 version delivered on time. Meet “Esperanza”, the first WordPress release of 2021. Marvel again at the numbers: Contributors (457), Trac tickets (250) and Pull Requests on GitHub(950).
\n\n\n\nJean-Baptist Audras, team rep of the core team, documentation release lead and data wizard compiled additional information about contributors, by country and employers. Have a sneak peek on his material, JB will soon share in a blog post.
\n\n\n\nIf it’s been a while since you checked on the Gutenberg state of affairs, there are plenty of resources in today’s edition. Let me get out of your way now.
\n\n\n\nYours, 💕
Birgit
PS: 🎙️ The new episode, number #39 of the Changelog is now available with show notes and transcript.
\n\n\n\n\n\nFull Site Editing Updates
\n\n\n\nJosepha Haden Chomphosy published in her full-site editing pre-merge overview an updated time line of decision-making on the prototype/MVP and communication roll-out for the merge of Full-Site Editing (FSE) into the core software. As far as I understood it, the team will decide on April 13 or 27, if a successful merge can be achieved for the 5.8 release in July (Yes, it was moved a month) or if it will be pushed to 5.9 in December 2021.
\n\n\n\nJosepha wrote: “The following is an outline of the communication work needed in the pre-merge period for Phase 2 of the Gutenberg project. This will put us in a position to merge Full Site Editing later this year while raising awareness and increasing the skills of our community as we go.” She lists in bullet points, the who, what, why, of the various teams to work together on this feature’s roll-out.
\n\n\n\nIn a follow-up post, Josepha shared the core team’s early thoughts on 5.8 Planning and elaborated on the changes, depending on if FSE will be merged or not in assembling the release team.
\n\n\n\n\n “Keeping up with Gutenberg – Index”
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. The index 2020 is here
\n\n\n\n
Geoff Graham discussed The WordPress Evolution Toward Full-Site Editing at CSS-Tricks. He wrote: “I’m personally all-in on this direction. I’d even go so far as to say (peeking over my shoulder at Chris) that CSS-Tricks is all-in on this as well. We made the switch to blocks last year, and it has reinvigorated our love for writing blog posts just like this one.”
\n\n\n\n\n\n\n\n
Calls for Testing Full-Site Editing
\n\n\n\nAre you as excited about Full-Site Editing as I am? Well, I can’t wait to follow Anne McCarthy’s third call for FSE testing. This time she envisions you to create a fun 404 page, something you normally couldn’t do without touching a php file and look at code. It’s called 404 because that’s the error code from web servers when they receive a browser request for a URL that doesn’t exist. If you need some inspiration the people at CreativeBloq have a great collection of 404 pages.
\n\n\n\n\n\n\n\n
Sarah Gooding walked the path before you, and shared her experience on the WPTavern, calling it the Full Site Editing Testing Challenge.
\n\n\n\n\n\n\n\n
The results of the second testing call are in. Anne McCarthy published the summary overall comments: FSE Program Build a Homepage Testing. The team gained invaluable information from those tests reports. 29 GitHub Issues were either confirmed, commented on or newly filed.
\n\n\n\n\n\n\n\n\n
Need a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Block Editor for Content Creators
\n\n\n\nChanning Ritter, a new contributor on the design team she designed a site with large type, Dark Mode detection, and other accessibility-friendly styling such as visible underlines and focus states on links with the block editor. In her article Accessibility in the Block Editor: A Beginners Guide. She wrote about the “many useful accessibility features available and provide some context about how recent improvements are helping take accessibility and usability to the next level.” She elaborates on recent Keyboard Navigation, Keyboard Shortcuts, and other Usability updates of the block-editor.
\n\n\n\n\n\n\n\n
To learn about keyboard shortcuts the block-editor the documentation team just published a comprehensive list of shortcuts and what they do, for both, Windows and Mac Operating Systems.
\n\n\n\n\n\n\n\n
Will Morris, staff writer at WordCandy, published an in-depth article on the Torque Magazine: What Is Gutenberg Full-Site Editing (And How to Access It Today). He wrote: “The upcoming Full-Site Editing (FSE) feature promises to be the next major step in WordPress design and development. By getting some hands-on experience now, you can ensure your site is prepared for the changes ahead.”
\n\n\n\n\n\n\n\n
Fantastic Blocks and Where To Find Them is the title of Laura Byrne‘s talk at the WordPress NYC Meetup group on Tuesday, March 16th, 2021 at 7:00 pm. She wrote:“With so many blocks to choose from (both native and 3rd party blocks) and more being added every day, which are the most vital ones to have in your content creation arsenal? Pick up indispensable tips and tricks for yourself and your clients.” It’ll be a fast-paced presentation and Laura has a wealth of knowledge. Come for the blocks and stay for the second talk: The Three Layers of WP Maintenance with Mervin Hernandez. I definitely try to make it. Will we see you there, too?
\n\n\n\nBlock Editor for Themes builders
\n\n\n\nGiven the above mentioned timeline for the merge of Full Site Editing, it’s no surprise that Hector Pietro grouped the focus projects for March around that feature and the possible adoption path for conventional Themes. He covers: Widget Screen, Navigation Screen, and Full-Site Editing. You might appreciate the section “Areas to be aware of” for block and plugin developers, theme builders, contributors and designers.
\n\n\n\n\n\n\n\n
Jeffrey Pears again keeps everyone updated on the specific discussions and issues around Themes in the Gutenberg + Themes: Week of March 11, 2021 for this week.
\n\n\n\n\n\n\n\n
In Recreating the Music Artist WordPress Theme Homepage With the Block Editor, Justin Tadlock walks us through his experience to replicate the theme’s design sections with the block editor and patterns starting with a theme already supporting the block editor. It’s a great example, how theme developers and site builders could embrace the Block editor and create new designs fast and support their users. Not all the modifications are yet available in Gutenberg. Justin use the EditorPlus plugin by Munir Kamal to add additional styling.
\n\n\n\nDevelopers and Block Building
\n\n\n\nJustin Ahinon updated the WordPress community on the block editor handbook restructuring project. “The idea is to build technical documentation around four parts: tutorials, how-to guides, technical reference and explanation.” he wrote.
\n\n\n\nJason Bahl, creator of the WPGraphQL plugin, tackled the topic Gutenberg and Decoupled Applications. He walks you through three different approaches to use Gutenberg in a decouple application environment and lists the trade-offs for each.
\n\n\n\n\n\n\n\n
Greg Ziolkowski shared on the core blog what it takes to Publishing WordPress packages to npm, the NodeJS package manager registry. As of today, there are nearly 80 actively maintained packages under the WordPress organization available. Greg shared some details about the latest addition to the process and summarize the overall strategy for publishing.
\n\n\n\n\nSubscribe to the Gutenberg Changelog podcast via your favorite podcast apps!
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed
Plugins for the Block Editor
\n\n\n\nMeet Oliver Campion and his plugin Options for Twenty-Twenty One. This plugin adds a ton, over 70 modification options to the default WordPress theme. James Huff, calls Oliver “the most active helper in the Twenty-Twenty-one support forum”
\n\n\n\nHe also created the plugin Display Remote Posts Block, used to display recent posts from a WordPress or Blogger sites, bringing back the blog roll.
\n\n\n\n\n\n\n\n
Speaking of Blog roll, Michael Beckwith released the Blogroll Block plugin. Justin Tadlock wrote about it for the WPTavern.
\n\n\n\n\n\n\n\n
The Newspack team at Automattic published their Newspack-Newsletter plugin in the WordPress repository. Similar to the Newsletter Glue plugin, that I use here, this plugin also enables you to use the block-editor design your newsletters, store them on your site and send them through Mailchimp or Constant Contact. Besides an account at one of the offered providers you also to apply for a free API key at MJML.org
\n\n\n\n\n\n\n\n
GeneratePress offers their future GP Theme Builder plugin in public beta. It brings you theme building using the core block editor and the GenerateBlocks plugin.
\n\n\n\n\n\n\n\n
The Gutenberg Block Manager Plugin by Darren Cooney helps you organize the hundreds of blocks on your site on various screens. It definitely will help you get organized. Sarah Gooding reviewed it for the WPTavern.
\n\n\n\n\n\n\n\n
WordPress Events
\n\n\n\nMarch 16, 2021, 7:00 PM to 9:00 PM EDT
WordPress NYC Meetup Group
Fantastic Blocks and Where To Find Them with Laura Byrne
The Three Layers of WP Maintenance with Mervin Hernandez
March 18, 2021 6:30 – 8:30 PM EDT
Mega-Meetup South Florida
April 15 – 17, 2021
WordCamp Centroamérica 2021
April 16th – 18th, 2021.
WordCamp Greece 2021 Online.
The organizer published the call for speakers.
April 16th – 18th, 2021
WordCamp Northeast Ohio
Take a look at the Call for Sponsors
May 24 – 27. 2021
WordSesh 2021
\n\n\n\n
On the Calendar for WordPress Online Events you’ll find a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\";s: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, 13 Mar 2021 21:44:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Gutenberg Block Manager Plugin Enables Global Block Removal and Recategorization\";s:7:\"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=113596\";s:7:\"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:225:\"https://wptavern.com/gutenberg-block-manager-plugin-enables-global-block-removal-and-recategorization?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-block-manager-plugin-enables-global-block-removal-and-recategorization\";s: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:3249:\"The world of Gutenberg blocks is expanding. WordPress’ official block directory launched in June 2020 with just 60 single-block plugins. Today, it has grown to more than 480 blocks. As users incorporate more blocks into their websites, the block inserter can become a very long list to scroll when browsing.
\n\n\n\nBlock management capabilities were added to Gutenberg in version 5.3, released in 2019. It allows users to search for a block and turn individual blocks and sections on or off in the block inserter. The feature hasn’t changed much over the past two years but will soon be getting a major update that will relocate it to the Preferences modal and redesign it to use panels with support for toggling block variations on and off.
\n\n\n\nIf you need more fine-grained block management, Darren Cooney‘s Gutenberg Block Manager plugin offers an admin interface for removing and recategorizing blocks. It is different from the core capabilities in that site admins can globally manage the enabled/disabled state of each block and changes will be reflected in the block inserter for all users. The plugin provides a full-screen interface for managing blocks on its own settings page outside of the editor.
\n\n\n\nEach block has a description and a toggle button for disabling it. There is enough space to include the number of instances for each block, and this seems like something useful the plugin could add in the future. Block categories are available as a quick navigation list in the sidebar and entire categories can be turned on or off with one click.
\n\n\n\nThe latest version of the plugin adds Category Switcher support for all blocks, including core Gutenberg blocks. Changing a block’s category will update its location in the block inserter.
\n\n\n\nThis plugin could be useful for periodically tidying up, improving the organization of blocks within the block inserter. Paring back the list of available blocks could also make it easier for website managers to have access to only the blocks that are necessary for their work. The plugin includes a filter for controlling the status of blocks across multiple WordPress environments.
\n\n\n\nAfter testing the Gutenberg Block Manager, my only criticism is that the plugin’s name is the same as the core WordPress feature, making it somewhat confusing. It might be more clear to focus on its distinctions and include that in the name, such as “Global Block Manager” or some variation. Other than that, it functions just as advertised and is available for free in the official plugins directory.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 13 Mar 2021 03:14:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: 2nd Annual Atarim Web Agency Summit Kicks Off March 23\";s:7:\"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=113661\";s:7:\"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:173:\"https://wptavern.com/2nd-annual-atarim-web-agency-summit-kicks-off-march-23?utm_source=rss&utm_medium=rss&utm_campaign=2nd-annual-atarim-web-agency-summit-kicks-off-march-23\";s: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:6118:\"Atarim is launching its 2nd annual Web Agency Summit in a couple of weeks. The free event will run from March 23 – 26. The goal of the event is to help agencies and freelancers in the WordPress space grow sustainable businesses.
\n\n\n\nAtarim is the company formerly known as WP Feedback. In February, the business rebranded because its primary product had grown beyond a mere feedback plugin into an across-the-board agency solution.
\n\n\n\n“While I’m a big fan of WordCamps and a big believer in the value that events can bring to personal growth, we found that most events in our space focus on the technical aspect of building a website,” said Vito Peleg, Atarim’s founder. “We take a more business-oriented approach. From finding the first clients through building solid recurring revenue and all the way to lessons from some of the biggest agencies in the world at full scale.”
\n\n\n\nThe event has 36 sessions, which are broken down into four categories that focus on:
\n\n\n\n- Build: Best practices for performance, SEO, accessibility, and the future of building websites.
- Expand: Building recurring revenue and maintaining profits.
- Scale: Project management, completing services, payment, and getting projects unstuck.
- Thrive: Hiring, community building, profitability at scale, and exit strategies.
Peleg hopes that attendees can glean some knowledge in the sessions while saving years of trial and error.
\n\n\n\n“All are delivered through our own summit platform, so attendees don’t need to jump around between Zoom calls, YouTube Lives, and Slack channels,” he said. “We brought it all into our own interactive platform.”
\n\n\n\nAtarim has made several sessions publicly available from 2020’s event. For those on the fence, it should provide insight into the types of talks they can expect.
\n\n\n\n- Lee Jackson: Mastering Content Creation and the New Work Environment
- Clifford Almeida: Blueprint To Building a Six-Figure Recurring Revenue Business
- Alex Panagis: Developing a Simple and Replicable SEO Strategy for Your Business
- Alison Rothwell: The Path To Selling Profitable WordPress Care Plans
- Kristina Romero: Remotely Managing Projects and Your Team
This year, each session will be running live — last year’s sessions were pre-recorded. This will allow attendees to be involved in real-time. There will also be a designated Q&A time for each session.
\n\n\n\nThe event is free to attend through the last week of March for anyone. However, the sessions will eventually fall behind a paywall, which helps cover costs.
\n\n\n\n“We offer an All Access Pass for those that want to watch the replays for $97, which is the investment for those that get it before the event,” said Peleg. “This also includes 30+ sessions from last year’s event for a total of 50+ hours of expert advice, specifically designed to help web freelancers and agencies build a solid business.”
\n\n\n\nSuccess and Lessons Learned From 2020
\n\n\n\nLast year’s event kick-started as a response to the changing nature of conferences in the Covid-era. Peleg described the initiative as a way of “licking our own wounds” after his company had planned to attend, sponsor, and have its own retreat at WordCamp Asia in Thailand, which was canceled in 2020.
\n\n\n\n“This drove me into action, wanting to lift some spirits in the community,” he said. “I didn’t know that we would end up with the biggest event in the WordPress space and have such incredible partners that came along for the ride.”
\n\n\n\nLast year’s event had 5,725 attendees from 126 countries. In total, they watched 53,945 hours of videos. They also won 1,000s of prizes at sponsor booths that included iPads, board games, and more.
\n\n\n\n“This was way more than what we expected, and the summit platform even broke on the first day when we were getting more than 240,000 requests to the server in an hour,” said Peleg. “Luckily, there isn’t a better community for something like this to happen. Very quickly, some of the sponsors joined forces with some of the speakers and our team and got us back on the air for a full week of action. While they were working to get this sorted, I was mostly pacing back and forth in my office like a headless chicken, but this year we’ve come prepared, with load balancers, auto-scaling processes, and a much leaner platform to sustain the scale.”
\n\n\n\nThere are no plans to switch to a physical Web Agency Summit in the coming years. For now, the virtual model is working.
\n\n\n\n“I’m very much looking forward to the return of WordCamps as physical events when [Covid-19] blows over, but I believe that virtual events are here to stay, so for the foreseeable future, once a year, we’ll bring back our summit as a celebration of the business side of the WordPress industry.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Mar 2021 17:16:36 +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:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"Post Status: Post Status Excerpt (No. 1) – WordPress 5.7 & Plugin Rank\";s:7:\"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:31:\"https://poststatus.com/?p=81617\";s:7:\"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:45:\"https://poststatus.com/post-status-excerpt-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3013:\"Learn what\'s new in WordPress 5.7 this week ![\"🆕\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f195.png\")
\n\n\n\nWith this episode of Post Status Excerpt — the first of many to come — David Bisset and Cory Miller kick off the new show with a quick chat about the latest WordPress release (5.7 “Esperanza”) — what it addresses, and maybe a pet peeve or two about the new editor.
\n\n\n\nAlso covered: PluginRank.com and the way it might be useful for WordPress entrepreneurs. ![\"🔌\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f50c.png\")
Every week Post Status Excerpt will brief you on important WordPress news relevant to the Post Status community — in about 15 minutes or less! Learn what\'s new in WordPress in a flash.![\"⚡\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a1.png\")
Mentioned in the show
\n\n\n\n- David Bisset (Twitter)
- Cory Miller (Twitter)
- Some 5.7 release highlights
- WordPress 5.7 Field Guide
- WPBeginner Guide To WordPress 5.7
- PluginRank.com
Sponsor: GoDaddy Pro
\n\n\n\nManage your clients, websites, and tasks from a single dashboard with GoDaddy Pro. Perform security scans, backups, and remote updates to many sites on any host. Check up on site performance, monitor uptime and analytics — and then send reports to your happy clients. ![\"🙌\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f64c.png\")
GoDaddy Pro is free — and designed to make your life better. Try it today, for free.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Mar 2021 16:45:24 +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:\"David Bisset\";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:88:\"WPTavern: Publish Text, Image, and Gallery Snippets With the Shortnotes WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=113624\";s:7:\"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:217:\"https://wptavern.com/publish-text-image-and-gallery-snippets-with-the-shortnotes-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=publish-text-image-and-gallery-snippets-with-the-shortnotes-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4448:\"Yesterday, Happy Prime owner and engineer Jeremy Felt released Shortnotes, a plugin for writing notes from the WordPress editor. The intention is for users to create short pieces of content, such as that found on Twitter, Instagram, and similar social networks. However, it does not come with a front-end posting interface, at least not in version 1.0.
\n\n\n\nThe plugin works just like the post and page editor. It should be straightforward for most users.
\n\n\n\nWhile the Shortnotes plugin is relatively bare-bones for now, it serves as a foundation of something that could be more. Part of what makes social networks appealing is the ease of publishing quick content. Publishing notes through the plugin requires visiting the WordPress admin, clicking “Add New,” writing the content, publishing, and clicking a new link to view it on the front end. A quick-publishing interface either through a Dashboard widget or a front-end form would be a useful addition.
\n\n\n\nSome new concepts that not all users may be familiar with are the “Reply to URL” and “Reply to name” fields. These are semantic fields for creating a note in reply to another post or person on the web. The plugin will automatically output this reply link on the front end.
\n\n\n\nThe plugin integrates with the Webmention plugin. A Webmention is a standardized protocol for mentions and conversations across the web. The goal is a decentralized social “network” of sorts where everyone owns and controls their content. It is an alternative to what IndieWeb calls the “corporate” web in which large tech companies have control.
\n\n\n\nWhen entering a Reply to URL, Shortnotes will automatically send that URL through the Webmentions plugin system. It will also parse URLs in the post content as webmentions if they exist.
\n\n\n\nUsers may also notice that the note title field is missing. This is intentional. The plugin automatically generates titles. They are needed for the <title> tag, which tools like search engines use.
The idea is for titles to not appear as part of the theme layout. Because most themes are not coded to check for post-type support before displaying them, there is a high chance that a user’s theme will output the auto-generated title on the front end. For now, that means editing a bit of theme code for those who do not want them to appear. Felt has an example of how he modified this for his site’s custom Twenty Twenty-One child theme. In the long run, as more themes begin supporting the upcoming site editor, users will be able to make this customization directly in the WordPress admin.
\n\n\n\nWith a few tweaks like removing the title and some minor CSS adjustments, I was able to create a clean Notes archive page using the Genesis Block theme:
\n\n\n\nOne of my interests in checking this project out was diving into a real-world example of a plugin that limited which blocks could be used with the editor. The notes post type only allows the Paragraph, Image, and Gallery blocks. Again, the idea is to replicate the feel of what you can do on social networks. Overall, this feature worked as it should, limiting the notes to a subset of blocks.
\n\n\n\nHowever, I ran across a bug with the block editor. All block patterns, regardless of what blocks they contained, appeared in the inserter. Clicking on one containing a disallowed block would not insert it into a post. However, the editor did add a pop-up note that it had. There is a GitHub issue for this bug that has seen little movement since it was opened in June 2020.
\n\n\n\nFelt created a plugin to solve this called Unregister Broken Patterns. It removes any patterns that contain blocks that a post type does not support. At best, it is a temporary measure and needs to be addressed 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 11 Mar 2021 22:04:40 +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: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:75:\"WPTavern: New Full Site Editing Testing Challenge: Create a Custom 404 Page\";s:7:\"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=113522\";s:7:\"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:193:\"https://wptavern.com/new-full-site-editing-testing-challenge-create-a-custom-404-page?utm_source=rss&utm_medium=rss&utm_campaign=new-full-site-editing-testing-challenge-create-a-custom-404-page\";s: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:7250:\"The Full Site Editing (FSE) Outreach program has launched its third testing call, continuing the effort to engage users in a structured testing flow focused on specific practical tasks. Previous rounds had testers building a custom homepage and exploring the distinction between editing modes (template vs page/post).
\n\n\n\nThe challenge in round #3 is to create a fun, custom 404 page. This page is often an opportunity for brands and individuals to inject a little humor and creativity into their websites, transforming a potentially negative experience into a path back to working links. In the past, site owners not comfortable with code had to rely on plugins in order to design their 404 pages. The new FSE capabilities will open a whole new world of customization.
\n\n\n\nTesters who want to jump in on this challenge will need to set up a testing environment that uses WordPress 5.7, the TT1 Blocks Theme, and Gutenberg 10.1.1 (latest version). Nothing special is required so it’s easy to jump in and start testing right away.
\n\n\n\nAnne McCarthy, who is spearheading the FSE Outreach program, has published a detailed testing flow that provides a guided exploration of the 404 template and simple tasks like adding navigation and other blocks.
\n\n\n\nThis challenge seemed like a good place to dip my toe into FSE testing and check out the progress the team has made in the past few months. Here is what I set out to do: add a funny gif, a search form, and a button to get back home.
\n\n\n\nOne of the first steps is to open the Navigation Toggle and head to Templates > 404. The “Navigation Toggle” refers to the WordPress icon in the top left corner of the page, but as a new user I would expect that to take me back to the dashboard. The naming doesn’t seem clear and I had to look up what was meant by Navigation Toggle.
\n\n\n\nFollowing the instructions, I selected the Header template part and removed it from the 404 page, but I don’t think it’s obvious to users that it’s possible to delete the entire template part in one go. Without the instructions, I probably would have started deleting all the blocks within the header template part before trying to figure out how to remove the entire thing.
\n\n\n\nThe testing flow asks users to insert a Template Part Block, select the “New Template Part” option, and add a custom title like “404 Header.” While this feature technically works, it seems like power user knowledge and I don’t see less technical site owners having any idea that this is possible or understanding its purpose without reading tutorials.
\n\n\n\nOne aspect of it that could be improved is that new Template Parts don’t save until you click “Update Design.” If you move away from the block and continue other parts of the design, it appears that it hasn’t saved and you may be tempted to create it again, as I was. Clicking “Update Design” will show you all the Template Parts you have created and requires confirmation to save them. This can get confusing if you don’t make a point to stop and save periodically.
\n\n\n\nOnce the design is saved, there is no confirmation but the button is no longer operable. The interface could communicate this better.
\n\n\n\nI didn’t encounter anything that was broken, though several aspects of it could be significantly improved. Everything outlined in the testing flow seems to work as it should, if users can ever find it. It is going to be a real challenge to make the interface spectacularly simple enough for ordinary users to feel comfortable knowing when and how to create their own template parts.
\n\n\n\nAdding more blocks was easy enough when I customized the 404 page content. I skipped the part of the testing script that involved creating a menu.
\n\n\n\n![\"404](\"https://cldup.com/fSlprFinO2.gif\")
\nUnfortunately, the preview looked nothing like the display on the frontend, but I assume that is still in progress. After trying multiple sources, I found that embeds didn’t work and some of the block styles were off.
\n\n\n\nThe testing flow for this challenge focused primarily on creating content within the new Template Part. That aspect of the test seemed to work, but there are a few things that could be significantly improved. The last part of the challenge is to answer the following questions:
\n\n\n\n- Did the experience crash at any point? No
- Did the saving experience work properly? Yes but it was confusing without any confirmation.
- Did the saving experience make sense when making changes to the Template Part vs the general content? It did after taking some time to explore it, but it’s not a concept that would be immediately evident to beginners.
- What did you find particularly confusing or frustrating about the experience? Saving template parts was confusing, and the previews are much better than what you get on the frontend.
- What did you especially enjoy or appreciate about the experience? I appreciated the ability to edit templates and template parts without jumping into code.
- Did you find that what you created in the Site Editor matched what you saw when you viewed your 404 page? No, it was far from similar to the preview.
- Did it work using Keyboard only? No
- Did it work using a screen reader? Did not test
My expectation when I began testing the 404 page design editing experience was that it would be a simple and enjoyable customization process with a few bugs. It ended up frustrating in the end because I could not trust the previews at all.
\n\n\n\nIs WordPress close to having an MVP of full site editing ready for 5.8? All the bones are in place. It feels like a rough prototype with enough momentum to reach MVP status in a few months. Editing and saving template parts works but the current interface design falls squarely within the realm of power users.
\n\n\n\nIf you want to join this challenge, follow the testing flow and post your feedback by March 23, 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:\"Thu, 11 Mar 2021 16:14:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:82:\"WPTavern: A Throwback To the Past: Introducing the Blogroll Block WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=113555\";s:7:\"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:207:\"https://wptavern.com/a-throwback-to-the-past-introducing-the-blogroll-block-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=a-throwback-to-the-past-introducing-the-blogroll-block-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4838:\"It was 2003. I was just getting my first taste of blogging and similar experiments on the world wide web. Seemingly every blog I toured showcased a long list of the owner’s friends. These were all the other cool kids jumping onto this blogging bandwagon — the blogroll was almost a status symbol. You had a sense of belonging with your online clique.
\n\n\n\nLet’s face it. Many of the people blogging in that era were loners, geeks, nerds, artists, and people who generally did not feel they fit into groups of “normal” people. Perhaps that is overly stereotypical, but that was the culture I found exploring this new world. It was a breakthrough for me as a person. I could let my geek flag fly in this new group of non-normal-but-so-much-more-interesting people than those I grew up with from my small hometown. Blogs were a home away from home for those who felt like outsiders.
\n\n\n\nI could share that I cared more about comic books than football on my little corner of the web. I could link to like-minded people in my blogroll. And they would link back to me.
\n\n\n\nIt has been eight years since the death of the link manager in WordPress. The underlying code is still there, only shown for those with existing links or the Link Manager plugin installed.
\n\n\n\nIt was the end of an era. Social media had taken over much of that camaraderie from my early venture into the blogging world, replacing it with a much more toxic version. There are groups and pockets within the social spheres that replicate that feeling, but it is all on a third-party server. The people no longer control their content or their content’s fate. Our likes and shares and retweets are lost in the endless void of memes, parodies, and libelous hot-takes. We no longer curate our links, cutting out the cruft to make room for the things representing who we are in the moment.
\n\n\n\nOne of the early highlights of my development career was building an image gallery using the WordPress links system. I was able to showcase all of my must-read WordPress blogs on one page.
\n\n\n\nI also used the link manager as a menu-management interface for my theme users long before WordPress adopted its nav menu system. Themes at the time were still using a page-listing function that often required end-users to edit code to manage.
\n\n\n\nNot only was the blogroll a vital aspect of my introduction to blogging, but it was also equally as crucial to my evolution as a developer. WordPress’s built-in link manager allowed me to step outside the box and innovate.
\n\n\n\nMaybe I am a bit nostalgic for blogrolls adorning every blog’s sidebar. There was a bit of a trust system built into it. If I liked your blog, there was a good chance that I would find something interesting in the links that you decided to share.
\n\n\n\nSure, there are other ways to achieve the same result today. However, the blogroll was a neon-sign in pitch black that shouted, “Hey, check out these cools things!”
\n\n\n\nThat is why I am giddy any time I see something that takes me down the memory lane of nearly two decades ago. It reminds me of how far we have come and how the web has changed over the years. And how much I wish things would sometimes stay the same.
\n\n\n\nMichael Beckwith released the Blogroll Block plugin two weeks ago. While I do not see a blogrolling revolution any time soon, it is nice to see a block-editor option for those of us who are still clinging to our links.
\n\n\n\nBlogroll Block requires the Link Manager plugin, which still has 60,000 active installs despite no updates since it was first dropped into the WordPress plugin directory. Maybe there is hope for a comeback.
\n\n\n\nThe block is straightforward. It replicates most of the options for the wp_list_bookmarks() function, which outputs the links. The downside to the plugin is there is no live preview in the editor. It currently outputs a box with a link to the developer reference. I am hoping this is a stopgap measure between version 1.0 and the next iteration.
I would also like to see the option to include link images in a grid. That way, I could recreate my “bookmarks gallery” with the block editor. That would be a fun afternoon project.
\n\n\n\nIf we had a blogroll on the Tavern, I like to think that we would link to Beckwith’s blog. We are on his. It would only be fair.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 10 Mar 2021 23:45:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:162:\"HeroPress: How WordPress Made Space For Me As A Kid Who Grew Up With MS – Come WordPress Mi Ha Accolta Quando Ero Una Bambina Crescendo Con La Sclerosi Multipla\";s:7:\"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=3492\";s:7:\"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:194:\"https://heropress.com/essays/how-wordpress-made-space-for-me-as-a-kid-who-grew-up-with-ms/#utm_source=rss&utm_medium=rss&utm_campaign=how-wordpress-made-space-for-me-as-a-kid-who-grew-up-with-ms\";s: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:12228:\"![\"Pull](\"https://s20094.pcdn.co/wp-content/uploads/2021/03/030821-min.jpg\")
Questo saggio è disponibile anche in italiano.
\nI was first introduced to WordPress when I was 13 years old. My parents had the idea to give me my very own WordPress website. I was able to use, play, test, and try whatever I wanted with it.
\nMy First Encounter With WordPress
\nWhile the technical aspects of my new WordPress website intrigued me, I was more interested in the space it made for me to write. All throughout my childhood I had struggled with chronic pain, fatigue, and other unexplained symptoms. Having a private world I could call my own, I was able to write my story.
\nAnd there is something truly amazing about having a place to tell your story.
\nWhen doctors, nurses, specialists, and the best hospitals I could go to struggled to find answers for me and my parents, I felt like my life and world were out of control. But logging onto my little website and typing away on the computer keys gave me a sense of control. I couldn’t always do things that other kids had the energy to do. But I could get lost in writing for hours. I couldn’t control my life story, but I could write about it.
\nIt felt like writing letters to my future self, “Look at what you went through, look how strong you were.” And even now, when I go on, I feel like I’m writing letters to my past self, “Look at you, look how you made it.”
\nWordPress In The Real World
\nI swear I thought that when I grew up, that I’d be healthy. I thought that “unhealthiness” was a part of being a kid. Something as terrible as having a bedtime, or having to eat carrots.
\nAnd like most kids, I couldn’t wait to be a grown up so that I could stay up as late as I wanted, never eat carrots again, and— be healthy.
\nBut growing up didn’t change that. In fact, my condition grew slowly worse as years went by. I was diagnosed with Multiple Sclerosis, a decade later at 18 years old.
\nI realized that I couldn’t handle a 9-5 work schedule, I couldn’t drive to a job on some days (shout-out to my mom for driving me) and I knew deep down that I would need to find another way to work.
\nI began writing music and book reviews online. I wrote blog posts. They were getting published and I was getting paid too. WordPress felt familiar, typing on the computer keys felt comfortable, and sharing my words with the world felt surreal.
\nI think I believed WordPress was mine somehow. I was learning that WordPress is something that belongs to everyone in some way. And I loved it.
\nMy WordPress Job at Valet
\nThe thing I love about WordPress is that it’s not just for developers or bloggers or SEO experts. I began to meet more people in the community and was delighted to find people like me, who didn’t know the technical stuff, but were a part of WordPress.
\nThere were social media managers, there were designers, there was a place for everyone. And the community felt as important as the rest of everything that makes WordPress what it is. It felt like it was about people and relationships as well as codes and databases.
\nI was hired at Valet in 2020 thanks to my relationships with people, in this case, my very own dad.
\nI like being a part of a WordPress company, and I love that I contribute to a team that helps people with their websites. I understand the importance of having a space that’s yours. Whether it’s a business or personal site, having a website gives you the power of telling your own story.
\nI didn’t have to work 9-5 jobs, or have my mom drive me to work, I didn’t have to worry about days when I needed to just stay in sweats. I have a 100% remote job which I can do despite the plot twists in my story, thanks to WordPress and the people in it.
\nWelcomed Into The WordPress Community
\nKimberly Lipari was the first person to repeatedly tell me that I was really indeed a part of the WordPress community. It felt unreal. I wasn’t a dev, I don’t know how to code, and yet I got to be a part of it all? I felt like I was a fake. But she continues to remind me that I’m real, I get to be here, I get to stay, I have a place.
\nWhen Michelle Frechette told me I could contribute to Big Orange Heart, I was honored. I was typing my words, pieces of my story, and sharing them with a community of people.
\nAnd when Topher contacted me to write my WordPress Story for HeroPress I could only say yes.
\nI could go on and on, this community is not perfect, but everyone here is constantly working to be better and do better.
\nMy WordPress Story
\nI’m proud and grateful to be sharing my story today.
\nI hope that maybe it can be a letter to anyone out there thinking, “I won’t make it.”
\nI hope that it will remind anyone reading this that WordPress is a space for everyone. Healthy or not, developer or not, blogger or not— WordPress belongs to you too.
\nI hope most of all that my story can somehow remind you that your story is important.
\n\n
Come WordPress Mi Ha Accolta Quando Ero Una Bambina Crescendo Con La Sclerosi Multipla
\nSono stata introdotta a WordPress per la prima volta quando avevo 13 anni. I miei genitori hanno avuto l’idea di darmi un sito WordPress personale, tutto mio. Cosi potevo usarlo, provare e riprovare, o fare quello che volevo. Nessuno di noi sapeva l’importanza che WordPress avrebbe nel mio futuro.
\nIl mio primo incontro con WordPress
\nMentre gli aspetti tecnici del mio nuovo sito Web WordPress mi hanno incuriosita, ero più interessata nel fatto che ha creato uno spazio per scrivere.
\nPer tutta la mia infanzia soffrivo con dolore cronico, stanchezza e altri sintomi inspiegabili. Avere quel mondo privato che era tutto mio, avevo la possibilità di scrivere la mia storia. E c’è qualcosa di veramente potente nell’avere un posto dove raccontare la tua storia.
\nQuando i medici ed infermieri, nei migliori ospedali facevano fatica a trovare risposte per me e per i miei genitori, mi sentivo come se la mia vita e il mio mondo fossero fuori controllo. Ma l’accesso al mio piccolo sito web e la digitazione sui tasti del computer mi dava semrpre un senso di controllo. Non riuscivo a fare tante cose che gli altri ragazzi riuscivano a fare. Ma potevo perdermi nella scrittura per ore ed ore. Non potevo controllare la storia della mia vita, ma la potevo scrivere.
\nEra come scrivere lettere al mio sé futuro, “Guarda cos’hai passato, guarda quanto eri forte”. E anche ora, quando torno a scrivere lì, mi sento come se stessi scrivendo lettere alla persona che ero nel passato, “Guardati, guarda come ce l’hai fatta”.
\nWordPress nel mondo reale
\nGiuro che pensavo che una volta cresciuta, sarei stata in buona salute. Ho pensato che la “malasanità” fosse una parte dell’essere una bambina. Qualcosa di fastidioso come andare a dormire ad una certa ora, o dover mangiare le carote. E come la maggior parte dei bambini, non vedevo l’ora di crescere per poter stare sveglia fino a tardi, non mangiare mai più le carote e poi— essere sana.
\nMa crescere non ha cambiato niente. In effetti, la mia salute continuava a peggiorare lentamente con il passare degli anni. Mi è stata finalmente diagnosticata la sclerosi multipla, dieci anni dopo, quando avevo 18 anni.
\nMi sono resa conto che non potevo gestire un orario di lavoro a tempo pieno, non riuscivo nemmeno a guidare certi giorni (ringrazio mia mamma per avermi accompagnata tantissime volte al lavoro), e sapevo in fondo che avrei dovuto trovare un altro modo per lavorare.
\nHo iniziato a scrivere recensioni di libri e musica online. Ho scritto vari post per diversi blog. A volte venivo anche pagata. WordPress per me era familiare, digitare sui tasti del computer era comodo, e condividere le mie parole con il mondo era surreale. Penso che a quel tempo credevo che WordPress fosse solo mio in un certo senso. Ma stavo imparando che WordPress è qualcosa che in un modo o l’altro appartiene a tutti. E adoravo questo fatto.
\nIl mio lavoro WordPress presso Valet
\nLa cosa che amo di WordPress è che non è solo per sviluppatori del web, blogger o esperti sul SEO. Ho iniziato a conoscere sempre più persone nella comunità, e sono stata felice di trovare persone come me, che non conoscevano le cose tecniche, ma facevano comunque parte di WordPress.
\nC’erano i social media manager, e anche designer, c’era un posto per tutti. E la comunità veniva apprezzata tanto quanto il resto di tutto ciò che rende WordPress quello che è. Erano importanti le persone e le relazioni, proprio come erano importanti i codici ed i database.
\nSono stata assunta da Valet nel 2020 grazie ai miei rapporti con le persone, in questo caso, mio padre. Mi piace far parte di un’azienda WordPress e mi piace contribuire ad un team che aiuta le persone con i loro siti web. Capisco l’importanza di avere uno spazio che è tutto tuo. Che si tratti di un sito aziendale o personale, avere un sito web ti dà il potere di raccontare la tua storia.
\nNon dovevo lavorare a tempo pieno, o farmi accompagnare da mia madre al lavoro, non dovevo preoccuparmi dei giorni in cui riuscivo solo a stare in pigiama a letto. Ho un lavoro remoto al 100% che posso fare nonostante i colpi di scena nella mia storia.
\nIl Benvenuto nella comunità di WordPress
\nKimberly Lipari è stata la prima persona a dirmi piu volte che facevo davvero parte della comunità di WordPress. Sembrava irreale. Non ero uno sviluppatore web, non so costruire un sito, eppure posso farne parte? Mi sentivo come se fossi un’intrusa nella comunità. Ma lei continua a ricordarmi che non sono un’intrusa, posso rimanere qui, ho un posto e uno spazio tutto mio qui.
\nQuando Michelle Frechette mi ha detto che potevo contribuire a Big Orange Heart, ero così contenta e sorpresa. Posso scrivevo le mie parole, pezzi della mia storia, e li posso condividere con una comunità di persone carissime.
\nE quando Topher mi ha contattato per scrivere la mia storia di WordPress per HeroPress, potevo solo dire di sì.
\nPotrei andare avanti all’infinito, questa comunità non è perfetta, ma tutti qui lavorano costantemente per diventare sempre migliori.
\nLa mia storia di WordPress
\nSono grata di condividere la mia storia con voi oggi.
\nSpero che forse possa essere una lettera a chiunque pensa come pensavo io, “Non ce la farò”.
\nSpero che ricorderà a chiunque legga questo articolo che WordPress è per tutti. Sano o no, sviluppatore o no, blogger o no, WordPress appartiene anche a te.
\nSpero soprattutto che la mia storia possa in qualche modo possa ricordare a tutti che ognuno ha una storia, ed ogni storia ha importanza e valore infinita.
\nThe post How WordPress Made Space For Me As A Kid Who Grew Up With MS – Come WordPress Mi Ha Accolta Quando Ero Una Bambina Crescendo Con La Sclerosi Multipla appeared first on HeroPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 10 Mar 2021 09:05:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Allie Dye\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}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:70:\"WPTavern: WordPress.com and Jetpack Launch Story Block for Mobile Apps\";s:7:\"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=113427\";s:7:\"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/wordpress-com-and-jetpack-adds-story-block-for-mobile-apps?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-com-and-jetpack-adds-story-block-for-mobile-apps\";s: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:5217:\"Automattic-owned WordPress.com launched its new Story-publishing feature today. Currently, only users with the WordPress for Android or iOS apps can add stories. Self-hosted users with Jetpack-connected sites can publish via the mobile apps too.
\n\n\n\nThe development team previewed the Story feature in January, launching a public beta on the Android app.
\n\n\n\nStories are essentially media and text slideshows. They have become popular on the web via sites like Instagram and Facebook. Solutions for Stories already exist in the WordPress space, such as Google’s Web Stories and the MakeStories plugins, both of which provide a more robust experience than Automattic’s offering at the moment.
\n\n\n\nHowever, more options and tools do not always create a better overall user experience. WordPress.com’s Stories feature has a more streamlined process, allowing users to build Story slides without much fuss.
\n\n\n\nTo create Stories, users must click the “New” icon from their site’s home screen in the mobile app. From there, they should see an option for adding a Story post. First-time users will see a Stories welcome screen.
\n\n\n\n![](\"https://wptavern.com/wp-content/uploads/2021/03/wpcom-site-home-1.jpg\")
![](\"https://wptavern.com/wp-content/uploads/2021/03/wpcom-story-start-1.jpg\")
![](\"https://wptavern.com/wp-content/uploads/2021/03/wpcom-story-welcome-1.jpg\")
The user experience in terms of editing slides for a Story was straightforward. I ran into no issues adding images, text, and customizing colors.
\n\n\n\nRight now, users cannot do much more. They are prompted to upload media when first creating a story. Each chosen media item automatically becomes a slide — users can add more later.
\n\n\n\nFont customization options are limited to a handful of presets. Text can be aligned or increased in size. Users can also change the color of the text and its background. For WordPress.com users who want more, they will have to wait. For self-hosted WordPress users, they have other plugin options.
\n\n\n\n![](\"https://wptavern.com/wp-content/uploads/2021/03/wpcom-story-slide-text-colors-1.jpg\")
![](\"https://wptavern.com/wp-content/uploads/2021/03/wpcom-story-slide-text-edit-1.jpg\")
![](\"https://wptavern.com/wp-content/uploads/2021/03/wpcom-story-publish-1.jpg\")
![Navigation Toggle](\"https://cldup.com/UzP6gqLQYP.png\"){kind=link}
I prefer the lighter experience. The learning curve is next to nonexistent, and the team can always tack on features later. The kitchen-sink route of launching with hundreds of options is prone to more errors. It also often include features that are not needed by a majority of the user base. I will take a smaller start with focused iteration any day.
\n\n\n\nMy first attempt at creating Story had its share of issues, introducing speedbumps in the publishing and updating process. Not all of my slides were published. Some of the text I had worked so hard on disappeared. At first, I thought I might have messed something up along the way. It was my first attempt, after all. Following repeated attempts to update, the issues persisted. I re-added the text. Whether it became a part of the published Story was hit or miss. I put new slides in. One randomly duplicated itself, and others disappeared.
\n\n\n\nIt was an hour-long exercise in frustration to publish a basic recipe. Even now, readers cannot learn how to make my Italian-style steamed Chinese pork buns. On the positive side, I did get four likes on my incomplete post.
\n\n\n\nDetermined not to be defeated, I attempted a second Story. Publishing went off without a hitch. For good measure, I updated the Story and added a new slide. Once again, no issues.
\n\n\n\nI knew the publishing experience could not be that broken after the initial ease of creating the Story slides.
\n\n\n\nMaybe the development team fixed a bug between my first and second attempts. Maybe something simply broke down on the technological highway. I will chalk my first attempt up to the internet gods playing a cruel trick on me.
\n\n\n\nThe Story feature is technically a block included with Jetpack that can only be edited in the mobile apps. The version I am waiting on is when it works via the browser-based editor. At that point, we will be able to compare it to existing plugins.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Mar 2021 22:17:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:149:\"WPTavern: WordPress 5.7 Introduces Drag-and-Drop for Blocks and Patterns, Streamlined Admin Color Palette, and One-Click Migration from HTTP to HTTPS\";s:7:\"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=113299\";s:7:\"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:339:\"https://wptavern.com/wordpress-5-7-introduces-drag-and-drop-for-blocks-and-patterns-streamlined-admin-color-palette-and-one-click-migration-from-http-to-https?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-7-introduces-drag-and-drop-for-blocks-and-patterns-streamlined-admin-color-palette-and-one-click-migration-from-http-to-https\";s: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:5269:\"WordPress 5.7 “Esperanza” was released today, named for Esperanza Spalding, an American jazz bassist who became an accomplished singer, songwriter, and composer in her early 20’s.
\n\n\n\nVersions 9.3 – 9.9 of the Gutenberg plugin are rolled into this update, bringing hundreds of enhancements and bug fixes that make working in the block editor more efficient and enjoyable.
\n\n\n\nOne of the highlights is the new drag-and-drop capabilities in the block inserter. Users can now drag blocks and block patterns directly into the post content area, making page building even faster.
\n\n\n\n\n\n\n\nMany of the user-facing editor enhancements in this release give the user more control when using existing blocks:
\n\n\n\n- Full height alignment: Blocks such as the Cover block now can have an option to expand to fill the entire viewport.
- Buttons block: The Buttons block now supports vertical alignments, and you can set the width of a button to a preset percentage.
- Social Icons block: You can now change the size of the icons in the Social Icons block.
- Font size in more places: You can now change the font size in the List and Code blocks
This release also improves the UI for block variations to include the icon and description for the variation in the block inspector and a new dropdown to allow for switching between variations. Reusable blocks have been updated to be saved at the same time the post is saved. Quite a few more improvements have been added in version 10.1 of the Gutenberg plugin, which is not yet included core. If you use Reusable blocks frequently, you may want to install the plugin to take advantage of the expanded UI.
\n\n\n\nIn addition to all the editor improvements, WordPress 5.7 introduces a streamlined color palette for the admin. It standardizes the palette to seven core colors and a range of 56 shades. One of the benefits is that all the shades meet the requirements for WCAG 2.0 AA recommended contrast ratio against white or black.
\n\n\n\nTheme and plugin developers who want to better match the admin color scheme can easily reference the new standardized shades to make their products more at home in the WordPress admin. WordPress’ existing core classes have also been updated with the new color palette so plugin authors can use them to work within the new standardized palette.
\n\n\n\nOne of the most exciting technical enhancements in 5.7 is a new one-click migration from HTTP to HTTPS. WordPress can now detect if the user’s hosting environment has support for HTTPS and update with the click of a button, handling mixed content rewrites where possible. This feature is available on the Site Health recommendations screen.
\n\n\n\nWordPress 5.7 continues the ongoing cleanup after the update to jQuery 3.5.1, which will eventually result in the removal of jQuery Migrate plugin. It fixes numerous jQuery deprecations in external libraries, cleaning up many JQMIGRATE warnings.
Developers may also be interested in the new filter-based Robots API included in 5.7. It enables the central management of the content of the robots meta tag injected into the page, and includes a setting to toggle whether search engines are allowed to display large media from the site. By default, a max-image-preview:large robots directive which will be injected into the robots meta tag based on the new setting.
Version 5.7 also includes native support for lazy loading iframes, a follow-up to WordPress’ support for lazy loading for images that came in 5.5. This should improve loading for pages that include embeds and other types of iframes.
\n\n\n\nCheck out the WordPress 5.7 field guide for technical details on everything new in this release. This update is the result of work from 481 volunteer contributors who collaborated on 250 tickets on Trac and more than 950 pull requests on GitHub.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Mar 2021 21:02:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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: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:49:\"WordPress.org blog: WordPress 5.7 “Esperanza”\";s:7:\"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:34:\"https://wordpress.org/news/?p=9888\";s:7:\"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:45:\"https://wordpress.org/news/2021/03/esperanza/\";s: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:39664:\"WordPress 5.7 “Esperanza”
\n\n\n\nBringing you fresh colors in the admin, simpler interactions in the editor, and controls right where you need them, WordPress 5.7 lets you focus on the content you create.
\n\n\n\n\n\n\n\n\nMeet “Esperanza”, the first WordPress release of 2021. “Esperanza” is named in honor of Esperanza Spalding, a modern musical prodigy. Her path as a musician is varied and inspiring—learn more about her and give her music a listen!
\n\n\n\nWith this new version, WordPress brings you fresh colors. The editor helps you work in a few places you couldn’t before without getting into code or hiring a pro. The controls you use most are right where you need them. Layout changes that should be simple, are even simpler to make.
\n\n\n\nNow the new editor is easier to use
\n\n\n\nFont-size adjustment in more places: now, font-size controls are right where you need them in the List and Code blocks. No more trekking to another screen to make that single change!
\n\n\n\nReusable blocks: several enhancements make reusable blocks more stable and easier to use. And now they save automatically with the post when you click the Update button.
\n\n\n\nInserter drag-and-drop: drag blocks and block patterns from the inserter right into your post.
\n\n\n\n\n\n\n\nYou can do more without writing custom code
\n\n\n\nFull-height alignment: have you ever wanted to make a block, like the Cover block, fill the whole window? Now you can.
\n\n\n\nButtons block: now you can choose a vertical or a horizontal layout. And you can set the width of a button to a preset percentage.
\n\n\n\nSocial Icons block: now you can change the size of the icons.
\n\n\n\n\n\n\n\nA simpler default color palette
\n\n\n\nThis new streamlined color palette collapses all the colors that used to be in the WordPress source code down to seven core colors and a range of 56 shades that meet the WCAG 2.0 AA recommended contrast ratio against white or black.
\n\n\n\nFind the new palette in the default WordPress Dashboard color scheme, and use it when you’re building themes, plugins, or any other components. For all the details, check out the Color Palette dev note.
\n\n\n\nFrom HTTP to HTTPS in a single click
\n\n\n\nStarting now, switching a site from HTTP to HTTPS is a one-click move. WordPress will automatically update database URLs when you make the switch. No more hunting and guessing!
\n\n\n\nNew Robots API
\n\n\n\nThe new Robots API lets you include the filter directives in the robots meta tag, and the API includes the max-image-preview: large directive by default. That means search engines can show bigger image previews, which can boost your traffic (unless the site is marked not-public).
Lazy-load your iFrames
\n\n\n\nNow it’s simple to let iframes lazy-load. By default, WordPress will add a loading=\"lazy\" attribute to iframe tags when both width and height are specified.
Ongoing cleanup after update to jQuery 3.5.1
\n\n\n\nFor years jQuery helped make things move on the screen in ways the basic tools couldn’t—but that keeps changing, and so does jQuery.
\n\n\n\nIn 5.7, jQuery gets more focused and less intrusive, with fewer messages in the console.
\n\n\n\nCheck the Field Guide for more!
\n\n\n\nCheck out the latest version of the WordPress Field Guide. It highlights developer notes for each change you may want to be aware of. WordPress 5.7 Field Guide.
\n\n\n\nThe Squad
\n\n\n\nThe WordPress 5.7 release comes to you from a small and experienced release squad:
\n\n\n\n- Release Lead: Matt Mullenweg (@matt)
- Triage Lead: Tonya Mork (@hellofromtonya)
- Release Coordinator: Ebonie Butler (@metalandcoffee)
- Core Tech Lead: Sergey Biryukov (@sergeybiryukov)
- Editor Tech Lead: Robert Anderson (@noisysocks)
- Design Lead: Tim Hengeveld (@hedgefield)
- Accessibility Lead: Sarah Ricker (@sarahricker)
- Documentation Lead: Jb Audras (@audrasjb)
- Test Lead: Monika Rao (@monikarao)
This release is the reflection of the hard work of 481 generous volunteer contributors. Collaboration occurred on nearly 250 tickets on Trac and over 950 pull requests on GitHub.
\n\n\n\n7studio, aaribaud, Aaron Brazell, Aaron D. Campbell, Aaron Jorbin, aaronrobertshaw, abagtcs, acerempel, activecoder, ad7six, Adam Bosco, Adam Silverstein, adamboro, Addison Stavlo, aduth, Ahmad Awais, Ahmed Saeed, Albert Juhé Lluveras, albertomake, Alex Lende, Alex Woollam, alex27, Alexander Lueken, alexstine, allancole, Allen Snook, almendron, Amanda Riu, ambienthack, Amol Vhankalas, Andrea Fercia, Andrei Draganescu, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrew Serong, André Maneiro, Andy Fragen, Andy Peatling, Ankit Panchal, Anne McCarthy, Anthony Burchell, Anton Lukin, Anton Timmermans, Anyssa Ferreira, archon810, Ari Stathopoulos, Arslan Ahmed, Artur Piszek, Aurélien Denis, Ayesh Karunaratne, bartosz777, basscan, bduclos, becdetat, Bego Mario Garde, Ben Dwyer, Bernhard Reiter, Bernhard Reiter, bhanusinghkre, Birgir Erlendsson (birgire), Birgit Pauli-Haack, bobbingwide, bonniebeeman, Boone Gorges, Boy Witthaya, Brandon Kraft, Brent Swisher, brijeshb42, burnuser, Caleb Burks, Cameron Voell, Carike, carloscastilloadhoc, carlosgprim, Carolina Nymark, celendesign, Cenay Nailor, ceyhun0, chexwarrior, Chip Snyder, Chloé Bringmann, Chouby, Chris Van Patten, Christian Sabo, Christina Workman, Christopher Finke, clayray, Clayton Collie, Code Amp, Collins Agbonghama, Copons, Corey, cristinasoponar, Damian Nowak, Dan Farrow, Daniel Richards, Daniele Scasciafratte, Danny van Kooten, Daria, Darren Ethier (nerrad), Dave Whitley, David Anderson, David Baumwald, David Biňovec, David Calhoun, David Herrera, David Page, dbtedg, dd32, Debabrata Karfa, dekervit, Denis Yanchevskiy, denishua, Diane Co, Dilip Bheda, Dominik Schilling, donmhico, dratwas, Drew Jaynes, Dávid Szabó, e_baker, Ebonie Butler, Edi Amin, Ella van Durpe, Ella van Durpe, Elliott Richmond, Enej Bajgorić, Enrico Carraro, epicfaace, epiqueras, Eric Andrew Lewis, Eric Binnion, Eric Mann, Erik Betshammar, Erin \'Folletto\' Casali, Estela Rueda, etoledom, eventualo, Fabian Kägy, Felipe Elia, Felix Arntz, Florian TIAR, Florian Ziegler, floriswt, Francesca Marano, Frank Klein, fullofcaffeine, Gan Eng Chin, Garrett Hyder, Gary Pendergast, GeekPress, geekzebre, Geoff Guillain, George Stephanis, geriux, gKibria, glendaviesnz, gmariani405, Gord, greatsaltlake, Greg Ziółkowski, grzim, gumacahin, gunnard, Gustavo Bordoni, Hans-Christiaan Braun, Hardeep Asrani, Hareesh, hauvong, Haz, Helen Hou-Sandi, helmutwalker, Hemant Tejwani, Herre Groen, hirasso, hmabpera, Howdy_McGee, hsingyuc7, Ian Dunn, ianmjones, ibiza69, Igor Radovanov, ingereck, iprg, Ipstenu (Mika Epstein), Isabel Brison, Ismail El Korchi, iviweb, J.D. Grimes, jadeddragoon, Jake Spurlock, jakeparis, jakub.tyrcha, James Golovich, James Huff, James Koster, James Nylen, James Rosado, Jan Thiel, Jason Adams, Jason LeMahieu (MadtownLems), Jason Ryan, Jayman Pandya, Jean-Baptiste Audras, Jeff Chandler, Jeff Farthing, Jeff Paul, Jennifer M. Dodd, Jenny Dupuy, Jeremy Felt, Jeremy Yip, Jeroen Rotty, Jessica Duarte, Jessica Lyschik, joanrho, Joe Dolson, Joe McGill, joelclimbsthings, Joen Asmussen, Johannes Kinast, John Blackbourn, John James Jacoby, John Watkins, Jon Surrell, Jonathan Champ, Jonathan Desrosiers, Jonathan Stegall, Jonny Harris, Jono Alderson, Joost de Valk, jordesign, Jorge Costa, José Miguel, Jose Luis, Joseph Karr O'Connor, Josepha Haden, joshuatf, JoshuaWold, JOTAKI, Taisuke, Joy, JS Morisset, jsnajdr, Juliette Reinders Folmer, Julio Potier, Justin Ahinon, Justin Sainton, Justin Sternberg, kafleg, Kai Hao, Kailey (trepmal), Kalpesh Akabari, kara.mcnair, Karolina Vyskocilova, Kelly Choyce-Dwan, Kerry Liu, kimdcottrell, Kiril Zhelyazkov, Kirsty Burgoine, Kite, Kjell Reigstad, Knut Sparhell, Konrad Chmielewski, Konstantin Obenland, Konstantinos Xenos, Kurt Payne, Kyle B. Johnson, Lara Schenck, laurelfulford, Laxman Prajapati, leogermani, Levdbas, litemotiv, Lovro Hrust, lucasbustamante, Luigi Cavalieri, Lukas Pawlik, Luke Carbis, Luke Cavanagh, Luke Walczak, Magali, magnuswebdesign, Mahafuz, Mahdi Akrami, malinajirka, mallorydxw, mallorydxw-old, Manzoor Wani, Manzur Ahammed, marcelo2605, Marcio Zebedeu, Marcus, Marcus Kazmierczak, Marie Comet, Marijn Koopman, Marin Atanasov, Marius Jensen, Mark D Wolinski, Mark Howells-Mead, Mark Robson, Mark Uraine, Marko Andrijasevic, Markus, Mary Baum, Mathieu Berard Smartfire, Mathieu Viet, Matias Ventura, Matt Chowning, Matt Mullenweg, Matt Wiebe, Maxime Pertici, Mayank Majeji, mdrockwell, Meg Phillips, Megan, Meher Bala, Mehrshad Darzi, Mehul Kaklotar, Mel Choyce-Dwan, mendezcode, mgol, Michael Arestad, Michael Babker, Miguel Fonseca, Miina Sikk, Mike Schroder, Milan Dinić, Milana Cap, mirka, Mohamed El Amine DADDOU, Monika, Monika Rao, morenaf, mrjoeldean, Mukesh Panchal, munyagu, mzorz, Naveen, net, nicky, Nico, Nico Martin, Nicola Laserra, Nicolas Juen, NicolasKulka, Nik Tsekouras, Noah Allen, nwjames, oakesjosh, Olga Gleckler, ovidiul, oxyc, Paal Joachim Romdahl, Pascal Birchler, patopaiar, Paul Bearne, Paul Biron, Paul Bunkham, Paul Schreiber, Paul Von Schrottky, pawki07, pbking, Pedro Mendonça, Pete Nelson, Peter Smits, Peter Wilson, Pinkal Devani, Piotrek Boniu, Prem Tiwari, presstoke, prettyboymp, Prince, pypwalters, Q, r-a-y, Rafael Galani, rafhun, Rami Yushuvaev, Ramon Ahnert, ratneshk, Ravi Vaghela, ravipatel, retrofox, Reza Ardestani, Riad Benguella, Rian Rietveld, Richard Tape, Robert Anderson, Rodrigo Primo, roger995, Rolf Siebers, Romain, Ronnie Burt, Ross Wintle, Ryan Boren, Sébastien SERRE, Sören Wrede, Saša, Sanket Chodavadiya, Sarah Ricker, sarayourfriend, Scott Taylor, Sebastian Pisula, SeBsZ, Sergey Biryukov, Sergey Yakimov, sergiomdgomes, Shahin Sid, shaunandrews, Shital Marakana, Slava Abakumov, snapfractalpop, souri_wpaustria, Stefano Minoia, Stefanos Togoulidis, Stephen Bernhardt, Stephen Edgar, Steven Word, Subrata Sarkar, Sunny, t-p, Takashi Kitajima, Tammie Lister, Tanvirul Haque, Tapan, TeamDNK, TeBenachi, Thierry Muller, thorlentz, Tim Hengeveld, Tim Nolte, Timi Wahalahti, Timothy Jacobs, tinodidriksen, Tkama, tmatsuur, Tobias Zimpel, tobifjellner (Tor-Bjorn Fjellner), Toni Viemerö, Tony A, Tonya Mork, tonysandwich, Torsten Landsiedel, Toru Miki, transl8or, Tyler Tork, Ulrich, Umang Vaghela, vandestouwe, vcanales, Vipul Chandel, Vlad T., webcommsat AbhaNonStopNewsUK, WebMan Design | Oliver Juhas, Wendy Chen, wesselvandenberg, Weston Ruter, Willis Allstead, worldedu, WP OnlineSupport, Xristopher Anderton, Yann Kozon, Yoav Farhi, yscik, Yui, yuliyan, Zebulan Stanphill, and zieladam.\n\n\n\n\n\n\n\nCode is poetry.
\nA new proposal on WordPress.org explores the ramifications of dropping support for Internet Explorer 11 (IE11). Héctor Prieto summarized the current state of IE usage among WordPress users, citing three metrics that demonstrate declining usage that is now cumulatively below ~1%:
\n\n\n\n- 0.71% from StatCounter’s GlobalStats
- 1.2% from W3 Counter
- 0.46% from WordPress.com
StatCounter’s GlobalStats record IE11 having dipped below 1.0% for the first time in August 2020, and it has continued declining steadily since then.
\n\n\n\nThe numbers cited in the proposal are similar to those contributors used when WordPress 4.8 officially dropped support for IE versions 8, 9, and 10 in 2017. These types of browser support decisions are always carefully considered, as they affect more users than one might guess, given the scale of a software project with more than 40% market share of all websites.
\n\n\n\n“It’s important to keep in mind that when viewing these statistics in the context of WordPress, these percentages represent tens (if not hundreds) of thousands of users that could potentially be left behind if support for IE11 is dropped,” Prieto said.
\n\n\n\nMost of the people still using IE11 are doing so because of forces outside their control. They may not have the ability to simply download an alternative browser. This is more common for users working inside major institutions like banking, government, and education.
\n\n\n\nAt this point in WordPress’ history, the benefits for the web seem to heavily outweigh the negative impacts on a small percentage of users who might be affected by lack of IE11 support. Improving the performance of the editor is one driving factor in this decision. Prieto shared stats from an exploration by Gutenberg developer Riad Benguella, where he measured the impact of dropping IE11 support, demonstrating an 84.9 kB (7%) reduction in Gutenberg JavaScript build files.
\n\n\n\n“Dropping support would result in smaller scripts, lower maintenance burden, and decrease build times,” Prieto said.
\n\n\n\n“The smaller downloads would positively impact all users, especially those on slower networks, or computing devices. We expect a result of dropping IE11 support to improve performance for the vast majority of users.”
\n\n\n\nMost of those participating in the discussion on WordPress.org are strongly in favor of dropping support for IE11, but a few cautioned that it must be done in a controlled way, with an EOL date announced months in advance. There are some institutions that selected WordPress for their projects based solely on the fact that it offers IE11 support, and they need time to plan a transition.
\n\n\n\n“I can see the crowd cheering for finally getting rid of IE and trust me I’ll be the first to pop champagne when that day has finally come,” WordPress developer Thomas Kräftner said. “Still I believe we need to make sure this is done in a slow, controlled and careful way so the effort saved for not supporting IE doesn’t backfire with extra, even more hellish work for those that don’t yet have the choice to drop IE.”
\n\n\n\nApproximately 16 months ago, Riad Benguella proposed WordPress add a notice to discourage Internet Explorer usage. Shortly thereafter, the Browse Happy API was updating to consider all versions of Internet Explorer as insecure. In the most recent conversation on WordPress.org, contributors suggested taking it a step further and change the notice to state that IE11 support will be dropped in WP-Admin by the end of year. Many shared additional benefits not outlined in the proposal.
\n\n\n\n“There’s lots of things we can’t use right now because of the IE11 constraint: CSS Variables, CSS grid, Modern JS are just the 1st things that come to mind,” Ari Stathopoulos commented. “We would be able to ship smaller files to 40% of the web, so the environmental impact of this change would be quite big, a huge win for our sustainability efforts! 99% of WP’s userbase has suffered enough already because of the IE limitation, and removing support for it can really make a dent and urge the few remaining IE users to use a better/newer browser.”
\n\n\n\nPrieto said the initial proposal was just to get the conversation started and was not meant to go into technical implementation details. WordPress contributors are invited to offer feedback about the proposal in the comments before March 18.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Mar 2021 05:34:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"WordPress.org blog: People of WordPress: Olga Gleckler\";s:7:\"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:34:\"https://wordpress.org/news/?p=9875\";s:7:\"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/03/people-of-wordpress-olga-gleckler/\";s: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:16620:\"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 lesser-known.
\n\n\n\nFrom a natural interest in computers and fixing things as a young woman, Olga Gleckler from St Petersburg, Russia, found WordPress took her on a journey to becoming a successful female tech entrepreneur. On International Women’s Day, we share her story.
\n\n\n\n\n\n\n\nFinding your path can take longer than you expect
\n\n\n\nFrom the age of 15, Olga found herself under pressure to find a free place for her professional studies. She said: “I didn’t know how high or low my chances were even if I had very good marks. I could have been just the biggest fish in a small pond. But anyway, I made up my mind to go to technical school.”
\n\n\n\nOn leaving school in St Petersburg with her certificate, Olga felt her knowledge of opportunities was very narrow. She had pictured being an ecologist or guide translator based on the subjects she had been taught at school. There was also an advertising boom in Russia and she began to explore this as a career avenue. She had developed her computer skills and found opportunities to practise by helping her teachers with administrative work.
\n\n\n\nThough she did not have access to any formal career advice, her journey led her into programming. She said: “The range of technical schools was not wide. I spent four years studying transistor markings, soldering and drawing PCB layouts. Programming courses using Pascal didn’t do anything useful with it.”
\n\n\n\nA lack of suitable access to English-language courses made things harder for Olga. She was determined that she would master the language later in her life. In the meantime, she left technical school with an honors degree and improved typing skills.
\n\n\n\n“I faced it was a wild, unfriendly market. I didn’t know how to recognize a genuine job offer or how to avoid the bad ones. It was difficult and I don’t know how long I would’ve looked for work without help.”
\n\n\n\nThink differently to find where you belong
\n\n\n\nOlga’s father worked in an IT company and was able to give her some advice and help with potential introductions. When she was still studying, he suggested her strong technical skills might be useful as a substitute typist. When she finished her studies, he helped her apply for a job updating a legal system on clients’ computers.
Six months later, she got a full-time job in the same service department. She liked her position and her clients. However, she was given friendly advice that without a university degree she would not be able to have any further promotions.
At this time, Olga was trying to study PHP from a book. She found it very exciting at first, but a lot of their functions did not give her explanations on how to build something useful. She found when she tried to build practical items from book reading, it did not always make sense and the solutions would often fail.
\n\n\n\nShe said: “It was hard to admit a failure even to myself and it was nagging me for a long time. I had to choose something I could handle, that I was interested in and could afford. It turned out to be advertising.”
\n\n\n\nShe spent most of the family’s holidays on learning sessions during the next six years. Olga recalled: “It was tricky for my husband to make me leave a computer, once I was glued to it, so he bought me my first laptop. English was still hard for me, I got high marks through just memorizing all the words in a textbook and how they should sound.”
\n\n\n\n\n\n\n\nDoubting your professional skills can happen when you are at home isolated looking after children. Keeping up your interests is important.
Olga’s life took a change after having a new baby and she spent three years doubting her professional skills and her chances of getting a good job. She tried to get back into other interests through studying, baking and drawing, but found ‘the pram was pulling me back’. She found she became very isolated and felt less able to contribute as the family was relying on her husband’s income as she tried to focus on looking forward.
\n\n\n\nShe said: “I was convinced (and saw) that not too many companies wanted a woman in the office, who with a small baby might need lots of leave.”
\n\n\n\nShe finished her education when she returned to work after three years caring for her son. She secured a promotion but with changes in the company’s staffing, things were tense. She found the difficulties there had become more heightened and felt that young female colleagues were treated as ‘pieces of furniture’ by one manager. She did not want to stay in this environment and in a few months time decided to leave.
\n\n\n\nYour next chapter may be nearby
\n\n\n\nDetermined to not repeat this type of experience, Olga looked at the brighter side. She said: “I wanted to be a marketer. Knowing how tricky it is to sell intangibles, I wanted a solid product to work with.”
\n\n\n\nIt turned out to be more difficult to find a job outside traditional IT as a young mother. Some human resource officers advised her to remain within the technology arena.
\n\n\n\nOlga remained hopeful and continued to study hard. She had many learning experiences along the way, which she hopes others can learn from too. One was setting a low bar to employers. She said: “Companies I worked in wanted to get all publicity and sales increases achieved through deductions from my salary.” This happened once and the next time she was in this situation she asked specifically about the budget before signing up. “I was assured this would not be the case, but again I found the budget for publicity came out of my wages. It was a tough period of disappointments. So when I was offered a part-time administrative job with basic sick leave, I took it gladly as a reprieve.”
\n\n\n\nThe job was far from home and involved a lot of travelling. Olga spent two to three hours a day on buses with Harry Potter audio books for company. “In these traffic jams, I started to feel English at last and loved it. It gave me a freedom no money can buy. Life was getting better.”
\n\n\n\nThough the job did not pay highly, it gave her something valuable – a working website. After her boss and the developer parted company, she was asked to maintain the site. Through some studying and reverse engineering, she discovered how it worked and it gave her an insight into how to write simple websites from scratch.
\n\n\n\nOlga’s first encounter with JavaScript wasn’t easy: “My first JavaScript calculator almost made me crazy, but I pursued it.”
\n\n\n\nQuickly she started to get small tasks from friends and relatives, usually to solve some urgent problems and started to meet popular content management systems. One of the first she met with was WordPress. There was an issue in a website theme used by a website which had been changed and not maintained. It took a whole weekend to solve, but she was determined to work it out. Back then, WordPress was ‘just a system’. She didn’t know then how much it was to become part of her life.
\n\n\n\nOlga spent the next two years in this role. As time went on, she started to feel worried and less satisfied with the work. The last straw for her was a negative statement from her boss, who was not a programmer and who hadn’t seen any of the work done on the website. She felt the approach was unfair as she had done extensive work on the site. She recalls: “I became angry, but it was exactly what I needed to move jobs.”
\n\n\n\nWhen Olga was job hunting, she didn’t feel she had the courage to apply for a developer’s role, despite the learning and work she had already done. So instead she started working on projects where she felt she was more like a ‘seller of box-ready websites’. It was another tough half a year for her with a lot of work, low payment and plans not turning out as she had hoped. On top of long hours, she ended up with pneumonia. She said: “I see now that I was doing a disservice to customers, websites are not a microwave meal – quick, cheap and dummy. There was no life in the sites without a lot of work which no one was willing to buy. Most of the sites I sold back then died after the first year and they never were truly alive and useful.”
\n\n\n\nYou need to be brave and have courage
\n\n\n\n\n\n\n\nOlga really wanted a developer job but seeking jobs of this type was very frustrating. From the job adverts she found, it felt like most IT companies were asking for geniuses who already knew a lot of technologies and frameworks. She found this very demotivating.
\n\n\n\nShe then found a job offer on a website outside the most popular job portals and it seemed like a perfect fit. They wanted someone with experience to write from scratch, understand someone else’s code and maintain it, with an ability to translate technical documentation and articles, and make simple designs for printing products. After completing a trial task, she was taken on, and enjoyed a better salary, in a calm environment with good colleagues and without the requirement for a lot of extra hours.
\n\n\n\nThe advert turned out to be a direct ad from one of the sales departments in a technology company. By succeeding in the task set, Olga had bypassed the Human Resources team which she felt would not normally have considered her.
\n\n\n\nHer boss agreed to her working remotely most of the time. It solved any potential leave problems which Olga had thought may be an obstacle.
\n\n\n\nFor Olga it had been 14 years since the original decision to become a programmer and it was only the beginning.
\n\n\n\nAfter a few years at what she describes as an ‘amazing experience’ in this workplace, Olga felt able to move on to her next challenge as a developer.
\n\n\n\nDecision-making can benefit from wider knowledge
\n\n\n\nAfter working with different systems Olga became sure that WordPress is the best CMS for developers and clients. But she was disappointed to find that the ease of use meant that good code was not always a priority for some of the sites she looked at.
\n\n\n\n“The biggest flaw of WordPress – it’s so easy to make things work that some may feel they don’t need to bother to do things right, but this becomes a problem later.”
\n\n\n\nIn custom themes for a site, she also saw sites being made and clients left without any further support, or items hard coded when clients actually needed more control to change regularly.
\n\n\n\nOlga used to rely on examples she could easily find, documentation and search engines to improve her understanding in using WordPress. She discovered that just by searching for a specific feature or a solution, you can miss the whole picture.
\n\n\n\nShe turned to online courses to get more comprehensive knowledge and then started to attend WordPress events, firstly online and then by foot, trains and planes! She discovered a worldwide community that was very much alive. She didn’t know when she started studying online materials and attending discussions that she would end up contributing herself to the Learn WordPress platform a few years later.
\n\n\n\nWordCamps and contributor days became a big part of her life. From her early days attending events and starting out contributing to WordPress, she is an active member of the WordPress.org Global Marketing and Polyglots Teams, and supported the recent WordPress release. She is just beginning her first WordCamp organiser experience, joining WordCamp Europe 2021 on the Contribute Team.
\n\n\n\n\n\n\n\nOlga said: “Through the wider WordPress community, I knew not only where to look but also whom to ask. Most importantly, I found allies who don’t think I’m going crazy by speaking with delight about work, and with whom I share a passion and fondness for WordPress. This is what matters.
\n\n\n\n“Now, after more than seven years of full time development, I am still enjoying endless learning, frequent discoveries, mistakes and an impassioned wish to do better.”
\n\n\n\nThis and a desire to help others use WordPress.org is part of Olga’s continued contribution to its Support and Marketing Teams, and led her to be involved in the Release Marketing questions and answers in 2020.
\n\n\n\nThere is no chequered flag on the way
\n\n\n\n\n\n\n\nThe road to freedom and becoming her own boss has not been easy for Olga. It is the path that got her where she is today, and she continues to find joy in it. She retains the lessons she’s learned and is always hungry to learn more.
\n\n\n\n“I travelled through a very uneven path, with a lot of obstacles and noise, but for me it’s like a kaleidoscope where a little turn presents a new picture, a new “ah-ha” moment, new excitement after seemingly pointless efforts.”
\n\n\n\nShe added: “When in doubt I remind myself about David Ogilvy (generally considered the Founding Father of the modern advertising industry) who tried a lot of things before he struck gold with advertising, and maybe that’s why he did.”
\n\n\n\nFinally, she learned not only to keep a good spirit and try different things, but also to dare as you move forward.
\n\n\n\nContributors
\n\n\n\nThanks to Abha Thakor (@webcommsat), Nalini Thakor (@nalininonstopnewsuk), Larissa Murillo (@lmurillom), Meher Bala (@meher), Josepha Haden (@chanthaboune), Chloé Bringmann (@cbringmann) and Topher DeRosia (@topher1kenobe). Thank you to Olga Gleckler (@oglekler) for sharing her #ContributorStory.
\n\n\n\n\n\n\n\nThis post is based on an article originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.
\n\n\n\nMeet more WordPress community members in our People of WordPress series.
\n\n\n\n#ContributorStory #HeroPress
\n\n\n\n\n\n\n\nPhoto credits: 2nd and 4th Pablo Gigena, Berlin, 2019
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 08 Mar 2021 22:30:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:\"\";}}}}}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:76:\"WPTavern: Proposal and Steps To Dual-License Gutenberg Under the GPL and MPL\";s:7:\"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=113368\";s:7:\"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/proposal-and-steps-to-dual-license-gutenberg-under-the-gpl-and-mpl?utm_source=rss&utm_medium=rss&utm_campaign=proposal-and-steps-to-dual-license-gutenberg-under-the-gpl-and-mpl\";s: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:7122:\"The GPL is so embedded into WordPress that it is not just the license the platform is under but a part of the community’s culture. Friends have been gained and lost over discussions of it. Bridges burned. Battles waged. People cast out to the dark corners of the web that “we don’t talk about.” There was even a time when one could expect a fortnightly GPL dust-up in which the inner WordPress world argued the same points over and over, ad nauseam.
\n\n\n\nIt might be hard to imagine a world where — outside of third-party libraries — direct contributions to the software are under anything other than the GPL. However, the wheels are now in motion. The Gutenberg project, which is the foundation of WordPress going forward, may soon be under both the GNU General Public License (GPL) v2 and the Mozilla Public License (MPL) v2.0.
\n\n\n\nThe goal is to allow Gutenberg to be used in proprietary applications, particularly in the mobile space, where it can be a hurdle to ship GPL code.
\n\n\n\nMobile Team contributor Maxime Biais proposed the change in July 2020. “Gutenberg supports two main platforms, the web and the native mobile apps. The GPL v2.0 license is a blocker for distributing the Gutenberg library in proprietary mobile apps.”
\n\n\n\nAt the moment, the WordPress for Android and WordPress for iOS apps use Gutenberg. Both of these apps are also licensed under the GPL, so it is a non-issue for them. However, it is uncommon for mobile apps to use the GPL. Thus, it limits Gutenberg’s potential reach.
\n\n\n\n“Rich text editor libraries in the mobile space are lacking,” wrote Biais. “There is no well known open source rich text editor for Android or iOS. We believe that Gutenberg could be a key library for many mobile apps, but that will never happen with the GPL v2.”
\n\n\n\nThe proposal was announced on the Make Core blog in September 2020. It garnered three comments. WordPress project lead Matt Mullenweg was in favor of the change, pointing out that it could help Gutenberg become a cross-CMS standard.
\n\n\n\n“Right now it’s easy to distribute Gutenberg with web apps that aren’t GPL, due to the way browsers link and bundle things, but embedding Gutenberg inside a native app on desktop, iOS, Android, or beyond is not possible unless the entire application is also GPL,” he wrote. “Allowing people the option to embed Gutenberg under the MPL I think will increase its usage outside of WordPress, bring more contributors to the core experience, and continue the Cambrian explosion of blocks that will give Gutenberg users more tools to fully express their creativity and vision.”
\n\n\n\nThe problem with switching licenses is that Gutenberg needs permission from every contributor who has added code to the project to make this change. The GitHub repository lists 721 individual contributors since the project began in 2016. To change licenses, each one must consent because they still own the copyright to their code.
\n\n\n\nSome of these people may not be involved any longer and not respond to the consent request. Others may refuse — as is their right. In either case, the Gutenberg team will need to either remove or rewrite the code.
\n\n\n\nThe proposal outlines four stops on the timeline before Gutenberg can be officially dual-licensed:
\n\n\n\n- March 19: All future contributions will be under both the GPL and MPL.
- April 2: Seek consent via GitHub from past contributors and contributors from open pull requests.
- Three months later: Begin removing or rewriting code that cannot be relicensed.
- Future: Once all removed or rewritten code is squared away, update Gutenberg as a whole to a GPL/MPL dual license.
For a licensing discussion, only a few people have chimed in. However, some have brought up concerns.
\n\n\n\n“WordPress has historically strongly believed in the GPL,” wrote core WordPress contributor Aaron Jorbin in the comments. “It has gone so far as to call the Four Freedoms of the GPL it’s ‘Bill Of Rights.’ And now what is being said is that only sometimes do you get these freedoms. Anyone is welcome to take the code and remove these freedoms. Instead of empowering users, this move is empowering the removal of freedom. To me, this feels like a very pro-business move and a very anti-user one.”
\n\n\n\nThe MPL is not considered viral in the same way as the GPL. Applications built with GPL-licensed code must allow for the same freedoms or more. App developers can distribute MPL-licensed code as long as it is in a separate file from their proprietary code. This lets businesses restrict parts of the codebase. Users might not have the freedom to use, fork, modify, and share all of an application’s code.
\n\n\n\nMost who have commented on the official threads so far have been excited or OK with the proposal. It can open Gutenberg to a new market. If developers in the mobile space begin using it for their apps, it could bring in fresh talent to the WordPress project as a whole.
\n\n\n\n“Our app sorely lacks a WYSIWYG editor,” wrote Radek Pietruszewski, the tech lead for Nozbe Teams, on the GitHub ticket in July 2020. “We had a working implementation on web, but we decided to scrap it because there was no way to port it on iOS and Android. There are pretty much no viable rich text editors for iOS or Android, let alone both. But even then, shipping three completely separate, but somehow compatible editors would be a vast amount of work. And you know yourself, making a good rich text editor from scratch is incredibly hard. It’s not something we could do ourselves. Gutenberg could solve this problem for us if it wasn’t for the licensing.”
\n\n\n\nHow things move forward comes down to the 700+ contributors. Will the Gutenberg team be rewriting swaths of code? Or, will most developers sign off on the license change?
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 08 Mar 2021 22:03:16 +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:138:\"Gutenberg Times: Using the Block Editor For Content Upgrades, Help Test New Gutenberg Features, Newsletter plugin – Weekend Edition #161\";s:7:\"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=17170\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://gutenbergtimes.com/using-the-block-editor-for-content-upgrades/\";s: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:11344:\"Howdy, howdy!
\n\n\n\nI found some spectacular content for the various use cases of the Block Editor, especially for Content Creators and Site Owners, also new plugins and updates from the WordPress teams.
\n\n\n\nEnjoy!
\n\n\n\nYours, 💕
Birgit
\n\n\n\n\n
Table of Contents
\n\n\n\nBlock Editor for Content Creators and Site Owners
\n\n\n\n19 Gutenberg Features You Might Not Be Aware Of (But Should!)
Nick Schäferhoff collected for on the Torque Magazine a great list of block editor features, I would call the secrete features. Most end users don’t know about them. Not all featured mentioned are in core, though. You would need to use the Gutenberg plugins to, for instance, use Blocks in Widgets, the Navigation block, the query block or work with Block Themes. Probably the most current of Listicles post about the block editor.
\n\n\n\n
In Core Editor Improvement: New Preferences experience, Anne McCarthy describes the new modal for preference settings of your workspace coming to WordPress 5.7. The new interface allows you in a more compact way to toggle on or off General settings, appearance settings, the block manager and remove panels in the sidebar you don’t need for instance,tags or comments.
\n\n\n\n![\"\"](\"https://i0.wp.com/make.wordpress.org/core/files/2021/02/Screen-Shot-2021-02-10-at-11.06.45-AM.png?w=640&ssl=1\")
\n\n\n\n\n\n\n\n
Bud Kraus, JoyofWP, has published two video tutorials on using Block Patterns and the Block Directory. They are quick reminders on how both features work, how you can discover new blocks and how you can integrate them into your workflow as content creators.
\n\n\n\n\n\n\n\n
In his post How do I use Gutenberg blocks?, Chris Lema wrote that with the plugin Blocky, “I can create what I want, place it where I want, for however long I want.” and use it for content upgrades, for upsells, for offers, for announcements and so much more! In his video Lema demos his workflow and in his post also have a few ideas how to apply it to your online business website.
\n\n\n\nBlock Editor for Developers
\n\n\n\nTesting WordPress and Gutenberg
\n\n\n\nJustin Tadlock described all the different User-Friendly Methods for Testing Gutenberg Enhancements and Bug Fixes on the WPTavern and mentioned the GB Nightly.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s master branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
There are times when you want to test single PRs before they are merged into the trunk code base. Paal Joachim Romdahl‘s tutorial on Testing a Gutenberg Pull Request (PR) that has not yet been merged into the plugins code base.
\n\n\n\nIn theory each PR added to the repository will run a build process for this particular code change and other people can test a new feature or a bug fix to gauge if it’s ready to be merged.
\n\n\n\n\n\n\n\n
Plugins for the Block Editor
\n\n\n\nThere have been a few plugins lately that caught my attention:
\n\n\n\nBlock Patterns Collection by Jyoti Shukla, a freelance WordPress and React Developer, providing – for now – two patterns: for statistics and a combine pattern with Heading, Text and Button blocks. On her blog, Jyoity Shukla writes about JavaScript and WordPress development.
\n\n\n\n\n\n\n\n
Developers at Automattic released the Newspack-Newsletters plugin in the WordPress Repository. With it, you can use the block editor to build newsletters and connect them with Email Marketing Providers, Mailchimp or Constant Contact, right from your WP Admin. You will need an API Key from MJML.
\n\n\n\n\n\n\n\n
WordPress Team Updates
\n\n\n\nMatt Chowning posted about Dual-Licensing Gutenberg: Next Steps on the Make Core Blog.
\n\n\n\n\n\n\n\n
Gutenberg + Themes: Week of March 4, 2021: The weekly roundup by Jeffrey Pearce and the Themes Team on theme-related discussions, fixes, and developments in Gutenberg. Please weigh in on the tickets listed — your voice and feedback are welcome! In this list, I found the list of Medium projects by Matias Ventura, that shows that beyond the focus on Full-Site Editing, Global Styles and Site editor, the team is also working on refinements on the block editor especially on Cover, Image, Columns and Gallery blocks, as well as continue working on Reusable blocks.
\n\n\n\nGutenberg 10.1 was released
\n\n\n\n- Read the release notes: What’s new in Gutenberg 10.1? (3 March) by Nik Tsekouras
- Get the skinny from Justin Tadlock: Gutenberg 10.1 Enhances Reusable Blocks, Updates Social Icons Spacing Options, and Normalizes Image Block Toolbar
- Core Editor Improvement: Need for (page/post) Speed
The new episode, number #39 of the Changelog will come to your favorite podcast app on Monday.
\n\n\n\n\nSubscribe to the Gutenberg Changelog podcast via your favorite podcast apps!
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed
WordPress Events
\n\n\n\nMarch 8, 2021 7:00 pm – 8:30 pm
Philly’burbs WordPress Meetup
Bringing a WordPress Plugin to the Marketplace with Brad Williams and Corey Salzano
March 16, 2021, 7:00 PM to 9:00 PM EDT
WordPress NYC Meetup Group
Fantastic Blocks and Where To Find Them with Laura Byrne
The Three Layers of WP Maintenance with Mervin Hernandez
April 16th – 18th, 2021.
WordCamp Greece 2021 Online.
The organizer published the call for speakers.
April 16th – 18th, 2021
WordCamp Northeast Ohio
Take a look at the Call for Sponsors
\n\n\n\n
On the Calendar for WordPress Online Events you can browse a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 07 Mar 2021 15:17:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:94:\"Post Status: Angela Jin on WordCamp US 2020 Cancellation and the Future of WordPress Education\";s:7:\"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:31:\"https://poststatus.com/?p=81417\";s:7:\"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://poststatus.com/future-of-wordcamp-us-and-wordpress-education/\";s: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:2679:\"What can the WordPress community look forward to in future WordCamps? ![\"🏕\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f3d5.png\")
\n\n\n\nIn this episode of Post Status Draft, David Bisset talks with Angela Jin about WordCamp US 2020. David recorded this interview around the time WCUS normally would have taken place in St. Louis, Missouri. The conference organizers decided to cancel the event months before, due to COVID-19. ![\"😷\"](\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f637.png\")
Angela has been organizing, starting conversations, and setting policies for WordCamps since she joined Automattic in 2018. She is one of the community organizers for the WordPress open source project and was part of the WCUS 2020 team also.
\n\n\n\nThen and now, there were questions about what led to the decision to cancel such a major event. Why didn\'t WCUS become a virtual conference, like WordCamp Europe? What are organizers planning for future WordCamp US events and WordPress education in general?
\n\n\n\nDavid sat down with Angela to get a better understanding of the WordPress community and its needs during a pivotal time of change. Join us as we discuss what the future holds for the conferences, meetups, and other social gatherings we\'ve enjoyed together in the past.
\n\n\n\n\n\n\n\n WCUS 2020 and other topics mentioned in the show
\n\n\n\n- Angela Jin (Twitter)
- WordCamp US 2020 Official Cancellation Notice
- WordCamp US 2020 Cancellation Q&A; with Organizers
- Learn WordPress
Sponsor: Pagely
\n\n\n\nPagely offers best-in-class managed WordPress hosting, powered by Amazon\'s Cloud, the Internet’s most reliable infrastructure. Pagely helps big brands scale WordPress.Thank you to Pagely for being a Post Status partner!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 05 Mar 2021 23:45:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"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:\"Tue, 30 Mar 2021 04:04:14 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Tue, 30 Mar 2021 03:45:07 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:\"20201210060712\";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (123844, '_site_transient_timeout_browser_d00214e45a2e527c7e30d0a066411384', '1617681850', 'no'), (123845, '_site_transient_browser_d00214e45a2e527c7e30d0a066411384', 'a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:12:\"89.0.4389.90\";s:8:\"platform\";s:9:\"Macintosh\";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'), (123907, '_site_transient_timeout_theme_roots', '1617096699', 'no'), (123855, '_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1617120253', 'no'), (123856, '_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1617077053', 'no'), (123859, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1617120254', 'no'), (123860, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1617077054', 'no'), (123861, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1617120254', 'no'), (123862, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '', 'no'); -- -------------------------------------------------------- -- -- Table structure for table `wp_postmeta` -- CREATE TABLE `wp_postmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `post_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_postmeta` -- INSERT INTO `wp_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES (25, 15, '_edit_last', '2'), (26, 15, '_edit_lock', '1600962734:2'), (27, 15, '_wp_page_template', 'default'), (28, 17, '_edit_last', '2'), (29, 17, '_edit_lock', '1600962777:2'), (30, 17, '_wp_page_template', 'default'), (55, 25, '_edit_last', '2'), (56, 25, '_wp_page_template', 'default'), (57, 25, '_edit_lock', '1615213049:2'), (68, 32, '_wp_attached_file', '2017/02/pgsfavicon2.png'), (69, 32, '_wp_attachment_metadata', 'a:5:{s:5:\"width\";i:512;s:6:\"height\";i:512;s:4:\"file\";s:23:\"2017/02/pgsfavicon2.png\";s:5:\"sizes\";a:4:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:23:\"pgsfavicon2-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";}s:6:\"medium\";a:4:{s:4:\"file\";s:23:\"pgsfavicon2-300x300.png\";s:5:\"width\";i:300;s:6:\"height\";i:300;s:9:\"mime-type\";s:9:\"image/png\";}s:8:\"2_column\";a:4:{s:4:\"file\";s:23:\"pgsfavicon2-260x260.png\";s:5:\"width\";i:260;s:6:\"height\";i:260;s:9:\"mime-type\";s:9:\"image/png\";}s:8:\"3_column\";a:4:{s:4:\"file\";s:23:\"pgsfavicon2-160x160.png\";s:5:\"width\";i:160;s:6:\"height\";i:160;s:9:\"mime-type\";s:9:\"image/png\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'), (70, 33, '_wp_attached_file', '2017/02/cropped-pgsfavicon2.png'), (71, 33, '_wp_attachment_context', 'site-icon'), (72, 33, '_wp_attachment_metadata', 'a:5:{s:5:\"width\";i:512;s:6:\"height\";i:512;s:4:\"file\";s:31:\"2017/02/cropped-pgsfavicon2.png\";s:5:\"sizes\";a:8:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";}s:6:\"medium\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-300x300.png\";s:5:\"width\";i:300;s:6:\"height\";i:300;s:9:\"mime-type\";s:9:\"image/png\";}s:8:\"2_column\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-260x260.png\";s:5:\"width\";i:260;s:6:\"height\";i:260;s:9:\"mime-type\";s:9:\"image/png\";}s:8:\"3_column\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-160x160.png\";s:5:\"width\";i:160;s:6:\"height\";i:160;s:9:\"mime-type\";s:9:\"image/png\";}s:13:\"site_icon-270\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-270x270.png\";s:5:\"width\";i:270;s:6:\"height\";i:270;s:9:\"mime-type\";s:9:\"image/png\";}s:13:\"site_icon-192\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-192x192.png\";s:5:\"width\";i:192;s:6:\"height\";i:192;s:9:\"mime-type\";s:9:\"image/png\";}s:13:\"site_icon-180\";a:4:{s:4:\"file\";s:31:\"cropped-pgsfavicon2-180x180.png\";s:5:\"width\";i:180;s:6:\"height\";i:180;s:9:\"mime-type\";s:9:\"image/png\";}s:12:\"site_icon-32\";a:4:{s:4:\"file\";s:29:\"cropped-pgsfavicon2-32x32.png\";s:5:\"width\";i:32;s:6:\"height\";i:32;s:9:\"mime-type\";s:9:\"image/png\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'), (205, 88, '_edit_last', '2'), (206, 88, '_edit_lock', '1600962678:2'), (207, 88, '_wp_page_template', 'default'), (1274, 139, '_wp_attachment_metadata', 'a:5:{s:5:\"width\";i:355;s:6:\"height\";i:52;s:4:\"file\";s:18:\"2017/06/button.jpg\";s:5:\"sizes\";a:5:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:17:\"button-150x52.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:52;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:6:\"medium\";a:4:{s:4:\"file\";s:17:\"button-300x44.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:44;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:8:\"1_column\";a:4:{s:4:\"file\";s:15:\"button-50x7.jpg\";s:5:\"width\";i:50;s:6:\"height\";i:7;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:8:\"2_column\";a:4:{s:4:\"file\";s:17:\"button-260x38.jpg\";s:5:\"width\";i:260;s:6:\"height\";i:38;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:8:\"3_column\";a:4:{s:4:\"file\";s:17:\"button-160x23.jpg\";s:5:\"width\";i:160;s:6:\"height\";i:23;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'), (311, 139, '_wp_attached_file', '2017/06/button.jpg'), (313, 139, '_edit_lock', '1500936138:2'), (360, 150, '_edit_last', '2'), (361, 150, 'special_html', 'Contents:\n
\n
\n\nPrivacy Policy:
\nYOURSITENAME (\"YOURSITENAME\") operates YOURDOMAIN.COM and may operate other websites. It is YOURSITENAMEPOSSESSIVE policy to respect your privacy regarding any information we may collect while operating our websites. We do comply with General Data Protection Regulation (GDPR) (EU) 2016/679.\nWebsite Visitors
\nLike most website operators, YOURSITENAME collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request. YOURSITENAMEPOSSESSIVE purpose in collecting non-personally identifying information is to better understand how YOURSITENAMEPOSSESSIVE visitors use its website. From time to time, YOURSITENAME may release non-personally-identifying information in the aggregate, e.g., by publishing a report on trends in the usage of its website.\nInformation Collection And Use
\nWe collect several different types of information for various purposes to provide and improve our Service to you.\nTypes of Data Collected
\nPersonal Identifiable Information
\nWhile using our Service, we may ask you to provide us with - or gather automatically - certain personally identifiable information that can be used to contact or identify you (\"Personal Data\"). Personally identifiable information collected by YOURSITENAME includes:\n\n
\nUsage Data
\nWe collect information about how our Service is accessed and used (\"Usage Data\"). This Usage Data may include information such as your computer\'s Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.\nTracking & Cookies Data
\nWe use cookies and similar tracking technologies to track the activity on our Service and hold certain information.\n\nCookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Service.\n\nYou can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service.\n\nExamples of Cookies we use:\n\n
\nIP Address
\nAny time you visit this website, a record of that visit is stored on this website\'s servers. This data is used to identify any technical issues with the website and is stored by a 3rd party for 36 months.\nEmail Address
\nIf you leave a comment on this website, you are required to include an email address. This email address is not displayed publicly but is available to the website administrator and stored on the website\'s servers until such time as the comment is deleted. That information is used to determine whether future comments should be automatically approved or manually reviewed by the website administrator before the comment can be published in order to reduce spam.\n\nYou may request that your comment and email address stored on the website\'s servers be deleted at any time by contacting the administrator using the form on this page: Contact Form.\n
Use of Data
\nYOURSITENAME uses the collected data for various purposes:\n- \n
- To provide and maintain the Service \n
- To notify you about changes to our Service \n
- To allow you to participate in interactive features of our Service when you choose to do so \n
- To provide customer care and support \n
- To provide analysis or valuable information so that we can improve the Service \n
- To monitor the usage of the Service \n
- To detect, prevent and address technical issues \n
Transfer Of Data
\nYour information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.\n\nIf you are located outside the United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to the United States and process it there.\n\nYour consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.\n\nYOURSITENAME will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.\nDisclosure Of Data
\nLegal Requirements
\nYOURSITENAME may disclose your Personal Data in the good faith belief that such action is necessary to:\n- \n
- To comply with a legal obligation \n
- To protect and defend the rights or property of YOURSITENAME \n
- To prevent or investigate possible wrongdoing in connection with the Service \n
- To protect the personal safety of users of the Service or the public \n
- To protect against legal liability \n
Security Of Data
\nThe security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.\nService Providers
\nWe may employ third party companies and individuals to facilitate our Service (\"Service Providers\"), to provide the Service on our behalf, to perform Service-related services or to assist us in analyzing how our Service is used.\n\nThese third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.\nAnalytics
\nWe may use third-party Service Providers to monitor and analyze the use of our Service.\n- \n
- Google Analytics \n
- Google Webmaster Tools/Google Search Console \n
Aggregated Statistics
\nYOURSITENAME may collect statistics about the behavior of visitors to its websites. YOURSITENAME may display this information publicly or provide it to others. However, YOURSITENAME does not disclose personally-identifying information other than as described above.\nProtection of Certain Personally-Identifying Information
\nYOURSITENAME discloses potentially personally-identifying and personally-identifying information only to those of its employees, contractors and affiliated organizations that (i) need to know that information in order to process it on YOURSITENAMEPOSSESSIVE behalf or to provide services available at YOURSITENAMEPOSSESSIVE websites, and (ii) that have agreed not to disclose it to others. Some of those employees, contractors and affiliated organizations may be located outside of your home country; by using YOURSITENAMEPOSSESSIVE websites, you consent to the transfer of such information to them. YOURSITENAME will not rent or sell potentially personally-identifying and personally-identifying information to anyone. Other than to its employees, contractors and affiliated organizations, as described above, YOURSITENAME discloses potentially personally-identifying and personally-identifying information only in response to a subpoena, court order or other governmental request, or when YOURSITENAME believes in good faith that disclosure is reasonably necessary to protect the property or rights of YOURSITENAME, third parties or the public at large. If you are a registered user of an YOURSITENAME website and have supplied your email address, YOURSITENAME may occasionally send you an email to tell you about new features, solicit your feedback, or just keep you up to date with what\'s going on with YOURSITENAME and our products. If you send us a request (for example via email or via one of our feedback mechanisms), we reserve the right to publish it in order to help us clarify or respond to your request or to help us support other users. YOURSITENAME takes all measures reasonably necessary to protect against the unauthorized access, use, alteration or destruction of potentially personally-identifying and personally-identifying information.\nBusiness Transfers
\nIf YOURSITENAME, or substantially all of its assets, were acquired, or in the unlikely event that YOURSITENAME goes out of business or enters bankruptcy, user information would be one of the assets that is transferred or acquired by a third party. You acknowledge that such transfers may occur, and that any acquirer of YOURSITENAME may continue to use your personal information as set forth in this policy.\nLinks To Other Sites
\nOur Service may contain links to other sites that are not operated by us. If you click on a third party link, you will be directed to that third party\'s site. We strongly advise you to review the Privacy Policy of every site you visit.\n\nWe have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.\nAds
\nAds appearing on any of our websites may be delivered to users by advertising partners, who may set cookies. These cookies allow the ad server to recognize your computer each time they send you an online advertisement to compile information about you or others who use your computer. This information allows ad networks to, among other things, deliver targeted advertisements that they believe will be of most interest to you. This Privacy Policy covers the use of cookies by YOURSITENAME and does not cover the use of cookies by any advertisers.\nPrivacy Policy Changes
\nAlthough most changes are likely to be minor, YOURSITENAME may change its Privacy Policy from time to time, and in YOURSITENAMEPOSSESSIVE sole discretion. YOURSITENAME encourages visitors to frequently check this page for any changes to its Privacy Policy. If you have a YOURDOMAIN.COM account, you might also receive an alert informing you of these changes. Your continued use of this site after any change in this Privacy Policy will constitute your acceptance of such change.\nContact Information
\nIf you have any questions about our privacy policy or data collection and usage, please contact the website administrator using the form on this page: Contact Form.\n\nBack to top\n\nTerms of Service:
\nThe following terms and conditions govern all use of the YOURDOMAIN.COM website and all content, services and products available at or through the website (taken together, the Website). The Website is owned and operated by YOURSITENAME (\"YOURSITENAME\"). The Website is offered subject to your acceptance without modification of all of the terms and conditions contained herein and all other operating rules, policies (including, without limitation, YOURSITENAMEPOSSESSIVE Privacy Policy) and procedures that may be published from time to time on this Site by YOURSITENAME (collectively, the \"Agreement\").\n\nPlease read this Agreement carefully before accessing or using the Website. By accessing or using any part of the web site, you agree to become bound by the terms and conditions of this agreement. If you do not agree to all the terms and conditions of this agreement, then you may not access the Website or use any services. If these terms and conditions are considered an offer by YOURSITENAME, acceptance is expressly limited to these terms. The Website is available only to individuals who are at least 13 years old.\n- \n
- Your YOURDOMAIN.COM Account and Site. If you create a blog/site on the Website, you are responsible for maintaining the security of your account and blog, and you are fully responsible for all activities that occur under the account and any other actions taken in connection with the blog. You must not describe or assign keywords to your blog in a misleading or unlawful manner, including in a manner intended to trade on the name or reputation of others, and YOURSITENAME may change or remove any description or keyword that it considers inappropriate or unlawful, or otherwise likely to cause YOURSITENAME liability. You must immediately notify YOURSITENAME of any unauthorized uses of your blog, your account or any other breaches of security. YOURSITENAME will not be liable for any acts or omissions by You, including any damages of any kind incurred as a result of such acts or omissions. \n
- Responsibility of Contributors. If you operate a blog, comment on a blog, post material to the Website, post links on the Website, or otherwise make (or allow any third party to make) material available by means of the Website (any such material, \"Content\"), You are entirely responsible for the content of, and any harm resulting from, that Content. That is the case regardless of whether the Content in question constitutes text, graphics, an audio file, or computer software. By making Content available, you represent and warrant that:\n
- \n
- the downloading, copying and use of the Content will not infringe the proprietary rights, including but not limited to the copyright, patent, trademark or trade secret rights, of any third party; \n
- if your employer has rights to intellectual property you create, you have either (i) received permission from your employer to post or make available the Content, including but not limited to any software, or (ii) secured from your employer a waiver as to all rights in or to the Content; \n
- you have fully complied with any third-party licenses relating to the Content, and have done all things necessary to successfully pass through to end users any required terms; \n
- the Content does not contain or install any viruses, worms, malware, Trojan horses or other harmful or destructive content; \n
- the Content is not spam, is not machine- or randomly-generated, and does not contain unethical or unwanted commercial content designed to drive traffic to third party sites or boost the search engine rankings of third party sites, or to further unlawful acts (such as phishing) or mislead recipients as to the source of the material (such as spoofing); \n
- the Content is not pornographic, does not contain threats or incite violence towards individuals or entities, and does not violate the privacy or publicity rights of any third party; \n
- your blog is not getting advertised via unwanted electronic messages such as spam links on newsgroups, email lists, other blogs and web sites, and similar unsolicited promotional methods; \n
- your blog is not named in a manner that misleads your readers into thinking that you are another person or company. For example, your blog\'s URL or name is not the name of a person other than yourself or company other than your own; and \n
- you have, in the case of Content that includes computer code, accurately categorized and/or described the type, nature, uses and effects of the materials, whether requested to do so by YOURSITENAME or otherwise. \n
\n - Payment and Renewal.\n
- \n
- General Terms.\nBy selecting a product or service, you agree to pay YOURSITENAME the one-time and/or monthly or annual subscription fees indicated (additional payment terms may be included in other communications). Subscription payments will be charged on a pre-pay basis on the day you sign up for an Upgrade and will cover the use of that service for a monthly or annual subscription period as indicated. Payments are not refundable. \n
- Automatic Renewal. \nUnless you notify YOURSITENAME before the end of the applicable subscription period that you want to cancel a subscription, your subscription will automatically renew and you authorize us to collect the then-applicable annual or monthly subscription fee for such subscription (as well as any taxes) using any credit card or other payment mechanism we have on record for you. Upgrades can be canceled at any time by submitting your request to YOURSITENAME in writing. \n
\n - Services.\n
- \n
- Fees; Payment. By signing up for a Services account you agree to pay YOURSITENAME the applicable setup fees and recurring fees. Applicable fees will be invoiced starting from the day your services are established and in advance of using such services. YOURSITENAME reserves the right to change the payment terms and fees upon thirty (30) days prior written notice to you. Services can be canceled by you at anytime on thirty (30) days written notice to YOURSITENAME. \n
- Support. If your service includes access to priority email support. \"Email support\" means the ability to make requests for technical support assistance by email at any time (with reasonable efforts by YOURSITENAME to respond within one business day) concerning the use of the VIP Services. \"Priority\" means that support takes priority over support for users of the standard or free YOURDOMAIN.COM services. All support will be provided in accordance with YOURSITENAME standard services practices, procedures and policies. \n
\n - Responsibility of Website Visitors. YOURSITENAME has not reviewed, and cannot review, all of the material, including computer software, posted to the Website, and cannot therefore be responsible for that material\'s content, use or effects. By operating the Website, YOURSITENAME does not represent or imply that it endorses the material there posted, or that it believes such material to be accurate, useful or non-harmful. You are responsible for taking precautions as necessary to protect yourself and your computer systems from viruses, worms, Trojan horses, and other harmful or destructive content. The Website may contain content that is offensive, indecent, or otherwise objectionable, as well as content containing technical inaccuracies, typographical mistakes, and other errors. The Website may also contain material that violates the privacy or publicity rights, or infringes the intellectual property and other proprietary rights, of third parties, or the downloading, copying or use of which is subject to additional terms and conditions, stated or unstated. YOURSITENAME disclaims any responsibility for any harm resulting from the use by visitors of the Website, or from any downloading by those visitors of content there posted. \n
- Content Posted on Other Websites. We have not reviewed, and cannot review, all of the material, including computer software, made available through the websites and webpages to which YOURDOMAIN.COM links, and that link to YOURDOMAIN.COM. YOURSITENAME does not have any control over those non-YOURSITENAME websites and webpages, and is not responsible for their contents or their use. By linking to a non-YOURSITENAME website or webpage, YOURSITENAME does not represent or imply that it endorses such website or webpage. You are responsible for taking precautions as necessary to protect yourself and your computer systems from viruses, worms, Trojan horses, and other harmful or destructive content. YOURSITENAME disclaims any responsibility for any harm resulting from your use of non-YOURSITENAME websites and webpages. \n
- Copyright Infringement and DMCA Policy. As YOURSITENAME asks others to respect its intellectual property rights, it respects the intellectual property rights of others. If you believe that material located on or linked to by YOURDOMAIN.COM violates your copyright, you are encouraged to notify YOURSITENAME in accordance with YOURSITENAMEPOSSESSIVE Digital Millennium Copyright Act (\"DMCA\") Policy. YOURSITENAME will respond to all such notices, including as required or appropriate by removing the infringing material or disabling all links to the infringing material. YOURSITENAME will terminate a visitor\'s access to and use of the Website if, under appropriate circumstances, the visitor is determined to be a repeat infringer of the copyrights or other intellectual property rights of YOURSITENAME or others. In the case of such termination, YOURSITENAME will have no obligation to provide a refund of any amounts previously paid to YOURSITENAME. \n
- Intellectual Property. This Agreement does not transfer from YOURSITENAME to you any YOURSITENAME or third party intellectual property, and all right, title and interest in and to such property will remain (as between the parties) solely with YOURSITENAME. YOURSITENAME, YOURDOMAIN.COM, the YOURDOMAIN.COM logo, and all other trademarks, service marks, graphics and logos used in connection with YOURDOMAIN.COM, or the Website are trademarks or registered trademarks of YOURSITENAME or YOURSITENAMEPOSSESSIVE licensors. Other trademarks, service marks, graphics and logos used in connection with the Website may be the trademarks of other third parties. Your use of the Website grants you no right or license to reproduce or otherwise use any YOURSITENAME or third-party trademarks. \n
- Advertisements. YOURSITENAME reserves the right to display advertisements on your blog unless you have purchased an ad-free account. \n
- Attribution. YOURSITENAME reserves the right to display attribution links such as \'Blog at YOURDOMAIN.COM,\' theme author, and font attribution in your blog footer or toolbar. \n
- Partner Products. By activating a partner product (e.g. theme) from one of our partners, you agree to that partner\'s terms of service. You can opt out of their terms of service at any time by de-activating the partner product. \n
- Domain Names. If you are registering a domain name, using or transferring a previously registered domain name, you acknowledge and agree that use of the domain name is also subject to the policies of the Internet Corporation for Assigned Names and Numbers (\"ICANN\"), including their Registration Rights and Responsibilities. \n
- Changes. YOURSITENAME reserves the right, at its sole discretion, to modify or replace any part of this Agreement. It is your responsibility to check this Agreement periodically for changes. Your continued use of or access to the Website following the posting of any changes to this Agreement constitutes acceptance of those changes. YOURSITENAME may also, in the future, offer new services and/or features through the Website (including, the release of new tools and resources). Such new features and/or services shall be subject to the terms and conditions of this Agreement. \n \n
- Termination. YOURSITENAME may terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. If you wish to terminate this Agreement or your YOURDOMAIN.COM account (if you have one), you may simply discontinue using the Website. Notwithstanding the foregoing, if you have a paid services account, such account can only be terminated by YOURSITENAME if you materially breach this Agreement and fail to cure such breach within thirty (30) days from YOURSITENAMEPOSSESSIVE notice to you thereof; provided that, YOURSITENAME can terminate the Website immediately as part of a general shut down of our service. All provisions of this Agreement which by their nature should survive termination shall survive termination, including, without limitation, ownership provisions, warranty disclaimers, indemnity and limitations of liability. \n \n
- Disclaimer of Warranties. The Website is provided \"as is\". YOURSITENAME and its suppliers and licensors hereby disclaim all warranties of any kind, express or implied, including, without limitation, the warranties of merchantability, fitness for a particular purpose and non-infringement. Neither YOURSITENAME nor its suppliers and licensors, makes any warranty that the Website will be error free or that access thereto will be continuous or uninterrupted. You understand that you download from, or otherwise obtain content or services through, the Website at your own discretion and risk. \n
- Limitation of Liability. In no event will YOURSITENAME, or its suppliers or licensors, be liable with respect to any subject matter of this agreement under any contract, negligence, strict liability or other legal or equitable theory for: (i) any special, incidental or consequential damages; (ii) the cost of procurement for substitute products or services; (iii) for interruption of use or loss or corruption of data; or (iv) for any amounts that exceed the fees paid by you to YOURSITENAME under this agreement during the twelve (12) month period prior to the cause of action. YOURSITENAME shall have no liability for any failure or delay due to matters beyond their reasonable control. The foregoing shall not apply to the extent prohibited by applicable law. \n
- General Representation and Warranty. You represent and warrant that (i) your use of the Website will be in strict accordance with the YOURSITENAME Privacy Policy, with this Agreement and with all applicable laws and regulations (including without limitation any local laws or regulations in your country, state, city, or other governmental area, regarding online conduct and acceptable content, and including all applicable laws regarding the transmission of technical data exported from the United States or the country in which you reside) and (ii) your use of the Website will not infringe or misappropriate the intellectual property rights of any third party. \n
- Indemnification. You agree to indemnify and hold harmless YOURSITENAME, its contractors, and its licensors, and their respective directors, officers, employees and agents from and against any and all claims and expenses, including attorneys\' fees, arising out of your use of the Website, including but not limited to your violation of this Agreement. \n
- Miscellaneous. This Agreement constitutes the entire agreement between YOURSITENAME and you concerning the subject matter hereof, and they may only be modified by a written amendment signed by an authorized executive of YOURSITENAME, or by the posting by YOURSITENAME of a revised version. Except to the extent applicable law, if any, provides otherwise, this Agreement, any access to or use of the Website will be governed by CITY/STATE/COUNTRY, excluding its conflict of law provisions, and the proper venue for any disputes arising out of or relating to any of the same will be the state and federal courts located in YOURCOUNTYANDSTATEORCOUNTRY. Except for claims for injunctive or equitable relief or claims regarding intellectual property rights (which may be brought in any competent court without the posting of a bond), any dispute arising under this Agreement shall be finally settled in accordance with the Comprehensive Arbitration Rules of the Judicial Arbitration and Mediation Service, Inc. (\"JAMS\") by three arbitrators appointed in accordance with such Rules. The arbitration shall take place in YOURCITYANDCOUNTRY, in the YOURLANGUAGE language and the arbitral decision may be enforced in any court. The prevailing party in any action or proceeding to enforce this Agreement shall be entitled to costs and attorneys\' fees. If any part of this Agreement is held invalid or unenforceable, that part will be construed to reflect the parties\' original intent, and the remaining portions will remain in full force and effect. A waiver by either party of any term or condition of this Agreement or any breach thereof, in any one instance, will not waive such term or condition or any subsequent breach thereof. You may assign your rights under this Agreement to any party that consents to, and agrees to be bound by, its terms and conditions; YOURSITENAME may assign its rights under this Agreement without condition. This Agreement will be binding upon and will inure to the benefit of the parties, their successors and permitted assigns. \n
Thanks for contacting us! We will be in touch with you shortly.<\\/p>\",\"message_scroll\":\"1\",\"page\":\"25\",\"redirect\":\"\"}}},\"meta\":{\"template\":\"contact\"}}', 'My Contact Form', '', 'publish', 'closed', 'closed', '', 'my-contact-form', '', '', '2020-09-23 21:15:35', '2020-09-23 21:15:35', '', 0, 'https://healthtimesonline.com/?post_type=wpforms&p=350', 0, 'wpforms', '', 0), (373, 2, '2021-03-08 14:12:26', '2021-03-08 14:12:26', '', 'About', '', 'inherit', 'closed', 'closed', '', '25-autosave-v1', '', '', '2021-03-08 14:12:26', '2021-03-08 14:12:26', '', 25, 'https://healthtimesonline.com/25-autosave-v1/', 0, 'revision', '', 0), (384, 2, '2021-03-27 09:46:49', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2021-03-27 09:46:49', '0000-00-00 00:00:00', '', 0, 'https://healthtimesonline.com/?p=384', 0, 'post', '', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_smush_dir_images` -- CREATE TABLE `wp_smush_dir_images` ( `id` mediumint(9) NOT NULL, `path` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `path_hash` char(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `resize` varchar(55) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `lossy` varchar(55) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `error` varchar(55) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `image_size` int(10) UNSIGNED DEFAULT NULL, `orig_size` int(10) UNSIGNED DEFAULT NULL, `file_time` int(10) UNSIGNED DEFAULT NULL, `last_scan` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `meta` text COLLATE utf8mb4_unicode_520_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -------------------------------------------------------- -- -- Table structure for table `wp_termmeta` -- CREATE TABLE `wp_termmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `wp_terms` -- CREATE TABLE `wp_terms` ( `term_id` bigint(20) UNSIGNED NOT NULL, `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_terms` -- INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES (1, 'Uncategorized', 'uncategorized', 0), (2, 'Main', 'main', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_relationships` -- CREATE TABLE `wp_term_relationships` ( `object_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_term_relationships` -- INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES (213, 2, 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_taxonomy` -- CREATE TABLE `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL, `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_term_taxonomy` -- INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES (1, 1, 'category', '', 0, 0), (2, 2, 'nav_menu', '', 0, 1); -- -------------------------------------------------------- -- -- Table structure for table `wp_usermeta` -- CREATE TABLE `wp_usermeta` ( `umeta_id` bigint(20) UNSIGNED NOT NULL, `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_usermeta` -- INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (1, 2, 'nickname', 'Editor'), (2, 2, 'first_name', 'Your Name'), (3, 2, 'last_name', ''), (4, 2, 'description', ''), (5, 2, 'rich_editing', 'true'), (6, 2, 'comment_shortcuts', 'false'), (7, 2, 'admin_color', 'fresh'), (8, 2, 'use_ssl', '0'), (9, 2, 'show_admin_bar_front', 'true'), (10, 2, 'locale', ''), (11, 2, 'wp_capabilities', 'a:1:{s:13:\"administrator\";b:1;}'), (12, 2, 'wp_user_level', '10'), (13, 2, 'dismissed_wp_pointers', 'cntctfrm_install_multi_tooltip,text_widget_custom_html,theme_editor_notice,wp496_privacy'), (14, 2, 'show_welcome_panel', '0'), (16, 2, 'wp_dashboard_quick_press_last_post_id', '384'), (19, 2, 'wp_user-settings', 'editor=html&libraryContent=browse'), (20, 2, 'wp_user-settings-time', '1530185017'), (21, 2, 'itsec_user_activity_last_seen', '1617077050'), (22, 2, 'itsec-settings-view', 'grid'), (23, 2, 'managenav-menuscolumnshidden', 'a:5:{i:0;s:11:\"link-target\";i:1;s:11:\"css-classes\";i:2;s:3:\"xfn\";i:3;s:11:\"description\";i:4;s:15:\"title-attribute\";}'), (24, 2, 'metaboxhidden_nav-menus', 'a:2:{i:0;s:12:\"add-post_tag\";i:1;s:15:\"add-post_format\";}'), (25, 2, 'nav_menu_recently_edited', '2'), (26, 2, '_yoast_wpseo_profile_updated', '1581655738'), (27, 2, 'wpseo_title', ''), (28, 2, 'wpseo_metadesc', ''), (29, 2, 'wpseo_metakey', ''), (30, 2, 'wpseo_noindex_author', ''), (31, 2, 'wpseo_content_analysis_disable', ''), (32, 2, 'wpseo_keyword_analysis_disable', ''), (33, 2, 'googleplus', ''), (34, 2, 'twitter', ''), (35, 2, 'facebook', ''), (37, 2, 'wpseo-dismiss-onboarding-notice', 'seen'), (98, 2, 'wp_wpseo-dismiss-tagline-notice', 'seen'), (39, 2, 'wpseo-remove-upsell-notice', '1'), (46, 2, 'closedpostboxes_post', 'a:0:{}'), (47, 2, 'metaboxhidden_post', 'a:7:{i:0;s:16:\"tagsdiv-post_tag\";i:1;s:11:\"postexcerpt\";i:2;s:13:\"trackbacksdiv\";i:3;s:10:\"postcustom\";i:4;s:16:\"commentstatusdiv\";i:5;s:7:\"slugdiv\";i:6;s:9:\"authordiv\";}'), (51, 2, 'closedpostboxes_single', 'a:0:{}'), (89, 2, 'jpibfi_pro_notice_date', '2020-05-28'), (52, 2, 'metaboxhidden_single', 'a:2:{i:0;s:10:\"wpseo_meta\";i:1;s:7:\"slugdiv\";}'), (49, 2, 'closedpostboxes_ftcpt1_product', 'a:0:{}'), (50, 2, 'metaboxhidden_ftcpt1_product', 'a:2:{i:0;s:10:\"wpseo_meta\";i:1;s:7:\"slugdiv\";}'), (71, 2, 'jpibfi_review_notice', '1'), (56, 2, 'closedpostboxes_single_product', 'a:0:{}'), (57, 2, 'metaboxhidden_single_product', 'a:5:{i:0;s:7:\"acf_174\";i:1;s:7:\"acf_173\";i:2;s:7:\"acf_171\";i:3;s:7:\"acf_172\";i:4;s:16:\"commentstatusdiv\";}'), (64, 2, 'closedpostboxes_review_post', 'a:0:{}'), (62, 2, 'closedpostboxes_multiple_product', 'a:0:{}'), (63, 2, 'metaboxhidden_multiple_product', 'a:5:{i:0;s:7:\"acf_174\";i:1;s:7:\"acf_173\";i:2;s:7:\"acf_172\";i:3;s:7:\"acf_160\";i:4;s:16:\"commentstatusdiv\";}'), (65, 2, 'metaboxhidden_review_post', 'a:5:{i:0;s:7:\"acf_174\";i:1;s:7:\"acf_173\";i:2;s:7:\"acf_171\";i:3;s:7:\"acf_160\";i:4;s:16:\"commentstatusdiv\";}'), (66, 2, 'closedpostboxes_list_post', 'a:0:{}'), (67, 2, 'metaboxhidden_list_post', 'a:5:{i:0;s:7:\"acf_174\";i:1;s:7:\"acf_171\";i:2;s:7:\"acf_172\";i:3;s:7:\"acf_160\";i:4;s:16:\"commentstatusdiv\";}'), (68, 2, 'closedpostboxes_how_to_post', 'a:0:{}'), (69, 2, 'metaboxhidden_how_to_post', 'a:5:{i:0;s:7:\"acf_173\";i:1;s:7:\"acf_171\";i:2;s:7:\"acf_172\";i:3;s:7:\"acf_160\";i:4;s:16:\"commentstatusdiv\";}'), (72, 2, 'community-events-location', 'a:1:{s:2:\"ip\";s:12:\"87.118.135.0\";}'), (75, 2, 'wpseo-reindex-links', 'seen'), (97, 2, 'wp_wpseo-dismiss-gsc', 'seen'), (85, 2, '_itsec_has_logged_in', '1527731318'), (99, 2, 'itsec-password-strength', '4'), (100, 2, '_itsec_password_requirements', 'a:1:{s:16:\"evaluation_times\";a:1:{s:8:\"strength\";i:1551817303;}}'), (152, 2, 'metaboxhidden_dashboard', 'a:0:{}'), (137, 2, 'syntax_highlighting', 'true'), (138, 2, 'itsec_last_password_change', '1551817210'), (140, 2, 'itsec_logs_page_screen_options', 'a:6:{s:8:\"per_page\";i:20;s:12:\"default_view\";s:9:\"important\";s:5:\"color\";b:1;s:10:\"show_debug\";b:0;s:12:\"show_process\";b:0;s:9:\"last_seen\";i:0;}'), (150, 2, 'session_tokens', 'a:2:{s:64:\"7167f7237858017a3464ed80b67a3d46314c0d2d56fd500b9a83e899688786d8\";a:4:{s:10:\"expiration\";i:1617188357;s:2:\"ip\";s:10:\"88.6.48.99\";s:2:\"ua\";s:114:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36\";s:5:\"login\";i:1617015557;}s:64:\"5ef73c037efd2345d519c598a169d82fddf09c78cf2bf79a4bcddddb54980b43\";a:4:{s:10:\"expiration\";i:1617249849;s:2:\"ip\";s:13:\"87.118.135.66\";s:2:\"ua\";s:120:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36\";s:5:\"login\";i:1617077049;}}'), (151, 2, 'closedpostboxes_dashboard', 'a:1:{i:0;s:27:\"wpforms_reports_widget_lite\";}'), (153, 2, 'wpseo-dismiss-configuration-notice', 'yes'), (155, 2, 'closedpostboxes_page', 'a:0:{}'), (156, 2, 'metaboxhidden_page', 'a:0:{}'), (157, 2, 'meta-box-order_page', 'a:4:{s:6:\"normal\";s:36:\"wpseo_meta,wpassetcleanup_asset_list\";s:4:\"side\";s:27:\"wpassetcleanup_page_options\";s:15:\"acf_after_title\";s:0:\"\";s:8:\"advanced\";s:0:\"\";}'); -- -------------------------------------------------------- -- -- Table structure for table `wp_users` -- CREATE TABLE `wp_users` ( `ID` bigint(20) UNSIGNED NOT NULL, `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_users` -- INSERT INTO `wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES (2, 'mallwadmin', '$P$B8U5DUSjyZJo7/xnVVV1D2tS97Th2n.', 'editor', 'putyouremail@here.com', 'https://healthtimesonline.com/about', '2017-02-25 22:52:06', '', 0, 'Editor'); -- -------------------------------------------------------- -- -- Table structure for table `wp_wpforms_tasks_meta` -- CREATE TABLE `wp_wpforms_tasks_meta` ( `id` bigint(20) NOT NULL, `action` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL, `data` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `date` datetime NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wp_wpforms_tasks_meta` -- INSERT INTO `wp_wpforms_tasks_meta` (`id`, `action`, `data`, `date`) VALUES (1, 'wpforms_process_entry_emails_meta_cleanup', 'Wzg2NDAwXQ==', '2020-09-23 21:15:44'), (2, 'wpforms_admin_notifications_update', 'W10=', '2020-09-23 21:15:54'), (3, 'wpforms_admin_notifications_update', 'W10=', '2020-11-13 20:17:43'), (4, 'wpforms_admin_notifications_update', 'W10=', '2020-11-16 20:46:36'), (5, 'wpforms_admin_notifications_update', 'W10=', '2020-11-18 18:01:07'), (6, 'wpforms_builder_help_cache_update', 'W10=', '2020-11-18 18:11:16'), (7, 'wpforms_admin_notifications_update', 'W10=', '2020-12-12 10:08:55'), (8, 'wpforms_admin_notifications_update', 'W10=', '2020-12-14 08:00:32'), (9, 'wpforms_process_entry_emails_meta_cleanup', 'Wzg2NDAwXQ==', '2020-12-16 11:04:51'), (10, 'wpforms_admin_notifications_update', 'W10=', '2020-12-29 10:40:55'), (11, 'wpforms_admin_notifications_update', 'W10=', '2021-01-16 09:34:20'), (12, 'wpforms_admin_notifications_update', 'W10=', '2021-01-16 09:34:49'), (13, 'wpforms_admin_notifications_update', 'W10=', '2021-02-27 10:56:08'), (14, 'wpforms_admin_notifications_update', 'W10=', '2021-02-27 10:56:58'), (15, 'wpforms_admin_notifications_update', 'W10=', '2021-03-07 11:59:53'), (16, 'wpforms_admin_notifications_update', 'W10=', '2021-03-08 14:06:59'), (17, 'wpforms_admin_notifications_update', 'W10=', '2021-03-10 10:12:35'), (18, 'wpforms_admin_notifications_update', 'W10=', '2021-03-16 09:27:31'), (19, 'wpforms_admin_notifications_update', 'W10=', '2021-03-19 15:23:03'), (20, 'wpforms_admin_notifications_update', 'W10=', '2021-03-27 09:46:49'), (21, 'wpforms_admin_notifications_update', 'W10=', '2021-03-29 12:26:44'); -- -------------------------------------------------------- -- -- Table structure for table `wp_yoast_indexable` -- CREATE TABLE `wp_yoast_indexable` ( `id` int(11) UNSIGNED NOT NULL, `permalink` longtext COLLATE utf8mb4_unicode_520_ci, `permalink_hash` varchar(40) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `object_id` bigint(20) DEFAULT NULL, `object_type` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL, `object_sub_type` varchar(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `author_id` bigint(20) DEFAULT NULL, `post_parent` bigint(20) DEFAULT NULL, `title` text COLLATE utf8mb4_unicode_520_ci, `description` mediumtext COLLATE utf8mb4_unicode_520_ci, `breadcrumb_title` text COLLATE utf8mb4_unicode_520_ci, `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `is_public` tinyint(1) DEFAULT NULL, `is_protected` tinyint(1) DEFAULT '0', `has_public_posts` tinyint(1) DEFAULT NULL, `number_of_pages` int(11) UNSIGNED DEFAULT NULL, `canonical` longtext COLLATE utf8mb4_unicode_520_ci, `primary_focus_keyword` varchar(191) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `primary_focus_keyword_score` int(3) DEFAULT NULL, `readability_score` int(3) DEFAULT NULL, `is_cornerstone` tinyint(1) DEFAULT '0', `is_robots_noindex` tinyint(1) DEFAULT '0', `is_robots_nofollow` tinyint(1) DEFAULT '0', `is_robots_noarchive` tinyint(1) DEFAULT '0', `is_robots_noimageindex` tinyint(1) DEFAULT '0', `is_robots_nosnippet` tinyint(1) DEFAULT '0', `twitter_title` text COLLATE utf8mb4_unicode_520_ci, `twitter_image` longtext COLLATE utf8mb4_unicode_520_ci, `twitter_description` longtext COLLATE utf8mb4_unicode_520_ci, `twitter_image_id` varchar(191) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `twitter_image_source` text COLLATE utf8mb4_unicode_520_ci, `open_graph_title` text COLLATE utf8mb4_unicode_520_ci, `open_graph_description` longtext COLLATE utf8mb4_unicode_520_ci, `open_graph_image` longtext COLLATE utf8mb4_unicode_520_ci, `open_graph_image_id` varchar(191) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `open_graph_image_source` text COLLATE utf8mb4_unicode_520_ci, `open_graph_image_meta` mediumtext COLLATE utf8mb4_unicode_520_ci, `link_count` int(11) DEFAULT NULL, `incoming_link_count` int(11) DEFAULT NULL, `prominent_words_version` int(11) UNSIGNED DEFAULT NULL, `created_at` datetime DEFAULT NULL, `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `blog_id` bigint(20) NOT NULL DEFAULT '1', `language` varchar(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `region` varchar(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `schema_page_type` varchar(64) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `schema_article_type` varchar(64) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `has_ancestors` tinyint(1) DEFAULT '0', `estimated_reading_time_minutes` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wp_yoast_indexable` -- INSERT INTO `wp_yoast_indexable` (`id`, `permalink`, `permalink_hash`, `object_id`, `object_type`, `object_sub_type`, `author_id`, `post_parent`, `title`, `description`, `breadcrumb_title`, `post_status`, `is_public`, `is_protected`, `has_public_posts`, `number_of_pages`, `canonical`, `primary_focus_keyword`, `primary_focus_keyword_score`, `readability_score`, `is_cornerstone`, `is_robots_noindex`, `is_robots_nofollow`, `is_robots_noarchive`, `is_robots_noimageindex`, `is_robots_nosnippet`, `twitter_title`, `twitter_image`, `twitter_description`, `twitter_image_id`, `twitter_image_source`, `open_graph_title`, `open_graph_description`, `open_graph_image`, `open_graph_image_id`, `open_graph_image_source`, `open_graph_image_meta`, `link_count`, `incoming_link_count`, `prominent_words_version`, `created_at`, `updated_at`, `blog_id`, `language`, `region`, `schema_page_type`, `schema_article_type`, `has_ancestors`, `estimated_reading_time_minutes`) VALUES (1, 'https://healthtimesonline.com/author/editor/', '44:e592d7f9903257eb4be04d8605627009', 2, 'user', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, NULL, NULL, NULL, NULL, 'https://secure.gravatar.com/avatar/ab360dc255d82e418f2867d93f19d1ae?s=500&d=mm&r=g', NULL, NULL, 'gravatar-image', NULL, NULL, 'https://secure.gravatar.com/avatar/ab360dc255d82e418f2867d93f19d1ae?s=500&d=mm&r=g', NULL, 'gravatar-image', NULL, NULL, NULL, NULL, '2020-09-23 21:06:22', '2021-03-29 11:26:45', 1, NULL, NULL, NULL, NULL, 0, NULL), (2, 'https://healthtimesonline.com/wp-content/uploads/2017/02/pgsfavicon2.png', '63:42b8d3c9e13a1dda1910d348ed6e0eaf', 32, 'post', 'attachment', 2, 0, NULL, NULL, 'pgsfavicon2', 'inherit', 0, 0, 0, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, 'https://healthtimesonline.com/wp-content/uploads/2017/02/pgsfavicon2.png', NULL, '32', 'attachment-image', NULL, NULL, 'https://healthtimesonline.com/wp-content/uploads/2017/02/pgsfavicon2.png', '32', 'attachment-image', '{\"width\":512,\"height\":512,\"url\":\"https://healthtimesonline.com/wp-content/uploads/2017/02/pgsfavicon2.png\",\"path\":\"/home/proheal6/public_html/HealthTimesOnline.com/wp-content/uploads/2017/02/pgsfavicon2.png\",\"size\":\"full\",\"id\":32,\"alt\":\"\",\"pixels\":262144,\"type\":\"image/png\"}', 0, NULL, NULL, '2020-09-23 21:06:22', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (3, 'https://healthtimesonline.com/9d469821ccb11b14b7c7aa22e9024c01/', '55:9bf121a3887be1fa80a343487bb7be50', 349, 'post', 'oembed_cache', 2, 0, NULL, NULL, '', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-09-23 21:06:23', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (4, 'https://healthtimesonline.com/wp-content/uploads/2017/02/cropped-pgsfavicon2.png', '71:601baa045f2625333865697f1a3d9016', 33, 'post', 'attachment', 2, 0, NULL, NULL, 'cropped-pgsfavicon2.png', 'inherit', 0, 0, 0, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, 'https://healthtimesonline.com/wp-content/uploads/2017/02/cropped-pgsfavicon2.png', NULL, '33', 'attachment-image', NULL, NULL, 'https://healthtimesonline.com/wp-content/uploads/2017/02/cropped-pgsfavicon2.png', '33', 'attachment-image', '{\"width\":512,\"height\":512,\"url\":\"https://healthtimesonline.com/wp-content/uploads/2017/02/cropped-pgsfavicon2.png\",\"path\":\"/home/proheal6/public_html/HealthTimesOnline.com/wp-content/uploads/2017/02/cropped-pgsfavicon2.png\",\"size\":\"full\",\"id\":33,\"alt\":\"\",\"pixels\":262144,\"type\":\"image/png\"}', 0, NULL, NULL, '2020-09-23 21:06:23', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (5, 'https://healthtimesonline.com/wp-content/uploads/2017/06/button.jpg', '58:3eedf8fc41416837d945e48d42102ef9', 139, 'post', 'attachment', 2, 0, NULL, NULL, 'button', 'inherit', 0, 0, 0, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, 'https://healthtimesonline.com/wp-content/uploads/2017/06/button.jpg', NULL, '139', 'attachment-image', NULL, NULL, 'https://healthtimesonline.com/wp-content/uploads/2017/06/button.jpg', '139', 'attachment-image', '{\"width\":355,\"height\":52,\"url\":\"https://healthtimesonline.com/wp-content/uploads/2017/06/button.jpg\",\"path\":\"/home/proheal6/public_html/HealthTimesOnline.com/wp-content/uploads/2017/06/button.jpg\",\"size\":\"full\",\"id\":139,\"alt\":\"\",\"pixels\":18460,\"type\":\"image/jpeg\"}', 0, NULL, NULL, '2020-09-23 21:06:23', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (6, 'https://healthtimesonline.com/privacy-terms-service/', '43:4d403b9b1b05c36a227683bed715e65c', 15, 'post', 'page', 2, 0, NULL, NULL, 'Privacy Policy and Terms of Service', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1, NULL, '2020-09-23 21:06:23', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (7, 'https://healthtimesonline.com/sitemap/', '29:18becd87685a7ab0bd490892747ef0f1', 17, 'post', 'page', 2, 0, NULL, NULL, 'Sitemap', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 3, NULL, NULL, '2020-09-23 21:06:24', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (8, 'https://healthtimesonline.com/about/', '27:7a8cb03ad9f8e8f251607391254f541f', 25, 'post', 'page', 2, 0, NULL, NULL, 'About', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1, NULL, '2020-09-23 21:06:24', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (9, 'https://healthtimesonline.com/contact/', '29:8ff4b6da0e895f9479fbfd32dfcb3c0d', 88, 'post', 'page', 2, 0, NULL, NULL, 'Contact', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1, NULL, '2020-09-23 21:06:24', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (10, NULL, NULL, 348, 'post', 'post', 2, 0, NULL, NULL, 'Auto Draft', 'auto-draft', 0, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-09-23 21:06:25', '2020-11-13 13:20:55', 1, NULL, NULL, NULL, NULL, 0, NULL), (11, 'https://healthtimesonline.com/uncategorized/', '35:6ec8ec69b45a0b5c1a6624c0322424ad', 1, 'term', 'category', NULL, NULL, NULL, NULL, 'Uncategorized', NULL, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-09-23 21:06:25', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (12, NULL, NULL, NULL, 'system-page', '404', NULL, NULL, 'Page not found %%sep%% %%sitename%%', NULL, 'Error 404: Page not found', NULL, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '2020-09-23 21:06:25', '2020-09-23 20:06:25', 1, NULL, NULL, NULL, NULL, 0, NULL), (13, NULL, NULL, NULL, 'system-page', 'search-result', NULL, NULL, 'You searched for %%searchphrase%% %%page%% %%sep%% %%sitename%%', NULL, NULL, NULL, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '2020-09-23 21:06:25', '2020-09-23 20:06:25', 1, NULL, NULL, NULL, NULL, 0, NULL), (14, NULL, NULL, NULL, 'date-archive', NULL, NULL, NULL, '%%date%% %%page%% %%sep%% %%sitename%%', '', NULL, NULL, 0, 0, NULL, NULL, NULL, NULL, NULL, NULL, 0, 1, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '2020-09-23 21:06:25', '2020-09-23 20:06:25', 1, NULL, NULL, NULL, NULL, 0, NULL), (15, 'https://healthtimesonline.com/', '30:7ba7a5681b39f93a5d555ff6d7087fc0', NULL, 'home-page', NULL, NULL, NULL, '%%sitename%% %%page%% %%sep%% %%sitedesc%%', 'Health and Wellness News, Tips and Resources', 'Home', NULL, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, 0, 0, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL, '', '', '', '', NULL, NULL, NULL, NULL, NULL, '2020-09-23 21:06:25', '2020-12-29 10:48:15', 1, NULL, NULL, NULL, NULL, 0, NULL), (16, 'https://healthtimesonline.com/?post_type=wpforms&p=350', '46:aebfddb552902d00e2fda69c0b8b5721', 350, 'post', 'wpforms', 2, 0, NULL, NULL, 'My Contact Form', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-09-23 21:15:21', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (26, 'https://healthtimesonline.com/home-2/', '28:1aa91a4f55954fe8f850174b2c68be74', 213, 'post', 'nav_menu_item', 2, 0, NULL, NULL, 'Home', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-13 20:24:22', '2020-11-16 20:51:17', 1, NULL, NULL, NULL, NULL, 0, NULL), (27, 'https://healthtimesonline.com/?post_type=acf-field&p=228', '56:51cc7a4e23a41b736068fc31f741fb25', 228, 'post', 'acf-field', 2, 219, NULL, NULL, 'HTP Tracking ID 1', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:54:56', '2020-11-16 20:54:56', 1, NULL, NULL, NULL, NULL, 0, NULL), (28, 'https://healthtimesonline.com/?post_type=acf-field-group&p=219', '62:629f8c1177016d466841cd1fb7234a64', 219, 'post', 'acf-field-group', 2, 0, NULL, NULL, 'How To Post Group', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:54:56', '2020-11-16 20:54:56', 1, NULL, NULL, NULL, NULL, 0, NULL), (29, 'https://healthtimesonline.com/?post_type=acf-field&p=236', '56:ccbccd65642bd2ea80d5aa0b3d575c4a', 236, 'post', 'acf-field', 2, 219, NULL, NULL, 'HTP Tracking ID 2', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:54:56', '2020-11-16 20:54:56', 1, NULL, NULL, NULL, NULL, 0, NULL), (30, 'https://healthtimesonline.com/?post_type=acf-field&p=240', '56:3f4a4806639a5f7da96dee69ba749797', 240, 'post', 'acf-field', 2, 239, NULL, NULL, 'LP Tracking ID 1', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:55:47', '2020-11-16 20:55:47', 1, NULL, NULL, NULL, NULL, 0, NULL), (31, 'https://healthtimesonline.com/?post_type=acf-field-group&p=239', '62:3372f0424e94d9768077ebc2fa826fe0', 239, 'post', 'acf-field-group', 2, 0, NULL, NULL, 'List Post Group', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:55:47', '2020-11-16 20:55:48', 1, NULL, NULL, NULL, NULL, 0, NULL), (32, 'https://healthtimesonline.com/?post_type=acf-field&p=262', '56:137a203c89445f9231901fddbc9bfac4', 262, 'post', 'acf-field', 2, 239, NULL, NULL, 'LP Tracking ID 2', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:55:47', '2020-11-16 20:55:47', 1, NULL, NULL, NULL, NULL, 0, NULL), (33, 'https://healthtimesonline.com/?post_type=acf-field&p=264', '56:c6ec97e2fa08fb6ccb81ab7182b2423b', 264, 'post', 'acf-field', 2, 239, NULL, NULL, 'LP Tracking ID 3', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:55:47', '2020-11-16 20:55:47', 1, NULL, NULL, NULL, NULL, 0, NULL), (34, 'https://healthtimesonline.com/?post_type=acf-field&p=266', '56:f959209af9a197e6826f2b6b6dd587b6', 266, 'post', 'acf-field', 2, 239, NULL, NULL, 'LP Tracking ID 4', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:55:47', '2020-11-16 20:55:47', 1, NULL, NULL, NULL, NULL, 0, NULL), (35, 'https://healthtimesonline.com/?post_type=acf-field&p=268', '56:85592241e95f7b6554585f7ee38d6495', 268, 'post', 'acf-field', 2, 239, NULL, NULL, 'LP Tracking ID 5', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:55:47', '2020-11-16 20:55:47', 1, NULL, NULL, NULL, NULL, 0, NULL), (36, 'https://healthtimesonline.com/?post_type=acf-field&p=283', '56:0d6fb1fd700e3b42531b5efd75d089ba', 283, 'post', 'acf-field', 2, 281, NULL, NULL, 'MPP Tracking ID 1', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:32', '2020-11-16 20:56:32', 1, NULL, NULL, NULL, NULL, 0, NULL), (37, 'https://healthtimesonline.com/?post_type=acf-field-group&p=281', '62:59feb26a585f1a6507dbd6f93d772c4d', 281, 'post', 'acf-field-group', 2, 0, NULL, NULL, 'Multiple Products Group', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:32', '2020-11-16 20:56:32', 1, NULL, NULL, NULL, NULL, 0, NULL), (38, 'https://healthtimesonline.com/?post_type=acf-field&p=304', '56:1628a8a4e1eb805269a51bf7428976db', 304, 'post', 'acf-field', 2, 281, NULL, NULL, 'MPP Tracking ID 2', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:32', '2020-11-16 20:56:32', 1, NULL, NULL, NULL, NULL, 0, NULL), (39, 'https://healthtimesonline.com/?post_type=acf-field&p=307', '56:0006106892375f96041734e9cee40b58', 307, 'post', 'acf-field', 2, 281, NULL, NULL, 'MPP Tracking ID 3', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:32', '2020-11-16 20:56:32', 1, NULL, NULL, NULL, NULL, 0, NULL), (40, 'https://healthtimesonline.com/?post_type=acf-field&p=310', '56:0581ba9fde7c43580cc9fc65a3cfed76', 310, 'post', 'acf-field', 2, 281, NULL, NULL, 'MPP Tracking ID 4', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:32', '2020-11-16 20:56:32', 1, NULL, NULL, NULL, NULL, 0, NULL), (41, 'https://healthtimesonline.com/?post_type=acf-field&p=313', '56:37ccefef6109da0bfdaac2e42bd279e1', 313, 'post', 'acf-field', 2, 281, NULL, NULL, 'MPP Tracking ID 5', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:32', '2020-11-16 20:56:32', 1, NULL, NULL, NULL, NULL, 0, NULL), (42, 'https://healthtimesonline.com/?post_type=acf-field&p=317', '56:0cab01de53ee5091ae7a410e888bb7e4', 317, 'post', 'acf-field', 2, 316, NULL, NULL, 'SPP Tracking ID', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:46', '2020-11-16 20:56:46', 1, NULL, NULL, NULL, NULL, 0, NULL), (43, 'https://healthtimesonline.com/?post_type=acf-field-group&p=316', '62:40d352c17f8e19c72874990891f64b7e', 316, 'post', 'acf-field-group', 2, 0, NULL, NULL, 'Single Products Group', 'publish', NULL, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, '2020-11-16 20:56:46', '2020-11-16 20:56:46', 1, NULL, NULL, NULL, NULL, 0, NULL), (51, 'https://healthtimesonline.com/?p=384', '36:7e0cc125f702cb140df77ff03bd8a454', 384, 'post', 'post', 2, 0, NULL, NULL, 'Auto Draft', 'auto-draft', 0, 0, NULL, NULL, NULL, NULL, NULL, 0, 0, NULL, 0, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '2021-03-29 12:26:45', '2021-03-29 11:26:45', 1, NULL, NULL, NULL, NULL, 0, NULL); -- -------------------------------------------------------- -- -- Table structure for table `wp_yoast_indexable_hierarchy` -- CREATE TABLE `wp_yoast_indexable_hierarchy` ( `indexable_id` int(11) UNSIGNED NOT NULL DEFAULT '0', `ancestor_id` int(11) UNSIGNED NOT NULL DEFAULT '0', `depth` int(11) UNSIGNED DEFAULT NULL, `blog_id` bigint(20) NOT NULL DEFAULT '1' ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wp_yoast_indexable_hierarchy` -- INSERT INTO `wp_yoast_indexable_hierarchy` (`indexable_id`, `ancestor_id`, `depth`, `blog_id`) VALUES (1, 0, 0, 1), (6, 0, 0, 1), (7, 0, 0, 1), (8, 0, 0, 1), (9, 0, 0, 1), (11, 0, 0, 1), (15, 0, 0, 1), (27, 28, 1, 1), (29, 28, 1, 1), (30, 31, 1, 1), (32, 31, 1, 1), (33, 31, 1, 1), (34, 31, 1, 1), (35, 31, 1, 1), (36, 37, 1, 1), (38, 37, 1, 1), (39, 37, 1, 1), (40, 37, 1, 1), (41, 37, 1, 1), (42, 43, 1, 1), (51, 0, 0, 1); -- -------------------------------------------------------- -- -- Table structure for table `wp_yoast_migrations` -- CREATE TABLE `wp_yoast_migrations` ( `id` int(11) UNSIGNED NOT NULL, `version` varchar(191) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wp_yoast_migrations` -- INSERT INTO `wp_yoast_migrations` (`id`, `version`) VALUES (1, '20171228151840'), (2, '20171228151841'), (3, '20190529075038'), (4, '20191011111109'), (5, '20200408101900'), (6, '20200420073606'), (7, '20200428123747'), (8, '20200428194858'), (9, '20200429105310'), (10, '20200430075614'), (11, '20200430150130'), (12, '20200507054848'), (13, '20200513133401'), (14, '20200609154515'), (15, '20200616130143'), (16, '20200617122511'), (17, '20200702141921'), (18, '20200728095334'), (19, '20201202144329'), (20, '20201216124002'), (21, '20201216141134'); -- -------------------------------------------------------- -- -- Table structure for table `wp_yoast_primary_term` -- CREATE TABLE `wp_yoast_primary_term` ( `id` int(11) UNSIGNED NOT NULL, `post_id` bigint(20) DEFAULT NULL, `term_id` bigint(20) DEFAULT NULL, `taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL, `created_at` datetime DEFAULT NULL, `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `blog_id` bigint(20) NOT NULL DEFAULT '1' ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -------------------------------------------------------- -- -- Table structure for table `wp_yoast_seo_links` -- CREATE TABLE `wp_yoast_seo_links` ( `id` bigint(20) UNSIGNED NOT NULL, `url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_id` bigint(20) UNSIGNED NOT NULL, `target_post_id` bigint(20) UNSIGNED NOT NULL, `type` varchar(8) COLLATE utf8mb4_unicode_520_ci NOT NULL, `indexable_id` int(11) UNSIGNED DEFAULT NULL, `target_indexable_id` int(11) UNSIGNED DEFAULT NULL, `height` int(11) UNSIGNED DEFAULT NULL, `width` int(11) UNSIGNED DEFAULT NULL, `size` int(11) UNSIGNED DEFAULT NULL, `language` varchar(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `region` varchar(32) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wp_yoast_seo_links` -- INSERT INTO `wp_yoast_seo_links` (`id`, `url`, `post_id`, `target_post_id`, `type`, `indexable_id`, `target_indexable_id`, `height`, `width`, `size`, `language`, `region`) VALUES (25, 'http://www.icann.org/en/registrars/registrant-rights-responsibilities-en.htm', 15, 0, 'external', 6, NULL, NULL, NULL, NULL, NULL, NULL), (23, 'http://YOURDOMAIN.COM/contact/', 15, 0, 'external', 6, NULL, NULL, NULL, NULL, NULL, NULL), (24, 'http://YOURDOMAIN.COM/contact/', 15, 0, 'external', 6, NULL, NULL, NULL, NULL, NULL, NULL), (31, 'https://healthtimesonline.com/privacy-terms-service/', 17, 15, 'internal', 7, 6, NULL, NULL, NULL, NULL, NULL), (30, 'https://healthtimesonline.com/contact/', 17, 88, 'internal', 7, 9, NULL, NULL, NULL, NULL, NULL), (29, 'https://healthtimesonline.com/about/', 17, 25, 'internal', 7, 8, NULL, NULL, NULL, NULL, NULL); -- -------------------------------------------------------- -- -- Table structure for table `wp_yoast_seo_meta` -- CREATE TABLE `wp_yoast_seo_meta` ( `object_id` bigint(20) UNSIGNED NOT NULL, `internal_link_count` int(10) UNSIGNED DEFAULT NULL, `incoming_link_count` int(10) UNSIGNED DEFAULT NULL ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `wp_yoast_seo_meta` -- INSERT INTO `wp_yoast_seo_meta` (`object_id`, `internal_link_count`, `incoming_link_count`) VALUES (227, 0, 0), (228, 0, 0), (229, 0, 0), (230, 0, 0), (231, 0, 0), (232, 0, 0), (233, 0, 0), (234, 0, 0), (235, 0, 0), (222, 0, 0), (223, 0, 0), (225, 0, 0), (226, 0, 0), (236, 0, 0), (237, 0, 0), (238, 0, 0), (239, 0, 0), (240, 0, 0), (248, 0, 0), (241, 0, 0), (242, 0, 0), (249, 0, 0), (243, 0, 0), (244, 0, 0), (245, 0, 0), (246, 0, 0), (247, 0, 0), (215, 0, 0), (214, 0, 0), (216, 0, 0), (217, 0, 0), (15, 0, 0), (221, 0, 0), (219, 0, 0), (218, 0, 0), (220, 0, 0), (224, 0, 0), (326, 0, 0), (327, 0, 0), (329, 0, 0), (333, 0, 0), (335, 0, 0), (336, 0, 0), (337, 0, 0), (338, 0, 0), (339, 0, 0), (340, 0, 0), (341, 0, 0), (342, 0, 0), (343, 0, 0), (344, 0, 0), (345, 0, 0), (334, 0, 0), (346, 0, 0), (347, 0, 0); -- -- Indexes for dumped tables -- -- -- Indexes for table `wp_actionscheduler_actions` -- ALTER TABLE `wp_actionscheduler_actions` ADD PRIMARY KEY (`action_id`), ADD KEY `hook` (`hook`), ADD KEY `status` (`status`), ADD KEY `scheduled_date_gmt` (`scheduled_date_gmt`), ADD KEY `args` (`args`), ADD KEY `group_id` (`group_id`), ADD KEY `last_attempt_gmt` (`last_attempt_gmt`), ADD KEY `claim_id` (`claim_id`); -- -- Indexes for table `wp_actionscheduler_claims` -- ALTER TABLE `wp_actionscheduler_claims` ADD PRIMARY KEY (`claim_id`), ADD KEY `date_created_gmt` (`date_created_gmt`); -- -- Indexes for table `wp_actionscheduler_groups` -- ALTER TABLE `wp_actionscheduler_groups` ADD PRIMARY KEY (`group_id`), ADD KEY `slug` (`slug`(191)); -- -- Indexes for table `wp_actionscheduler_logs` -- ALTER TABLE `wp_actionscheduler_logs` ADD PRIMARY KEY (`log_id`), ADD KEY `action_id` (`action_id`), ADD KEY `log_date_gmt` (`log_date_gmt`); -- -- Indexes for table `wp_commentmeta` -- ALTER TABLE `wp_commentmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `comment_id` (`comment_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_comments` -- ALTER TABLE `wp_comments` ADD PRIMARY KEY (`comment_ID`), ADD KEY `comment_post_ID` (`comment_post_ID`), ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), ADD KEY `comment_date_gmt` (`comment_date_gmt`), ADD KEY `comment_parent` (`comment_parent`), ADD KEY `comment_author_email` (`comment_author_email`(10)); -- -- Indexes for table `wp_css_js_manager` -- ALTER TABLE `wp_css_js_manager` ADD PRIMARY KEY (`id`); -- -- Indexes for table `wp_duplicator_packages` -- ALTER TABLE `wp_duplicator_packages` ADD PRIMARY KEY (`id`), ADD KEY `hash` (`hash`); -- -- Indexes for table `wp_itsec_bans` -- ALTER TABLE `wp_itsec_bans` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `host` (`host`), ADD KEY `actor` (`actor_type`,`actor_id`); -- -- Indexes for table `wp_itsec_distributed_storage` -- ALTER TABLE `wp_itsec_distributed_storage` ADD PRIMARY KEY (`storage_id`), ADD UNIQUE KEY `storage_group__key__chunk` (`storage_group`,`storage_key`,`storage_chunk`); -- -- Indexes for table `wp_itsec_fingerprints` -- ALTER TABLE `wp_itsec_fingerprints` ADD PRIMARY KEY (`fingerprint_id`), ADD UNIQUE KEY `fingerprint_user__hash` (`fingerprint_user`,`fingerprint_hash`), ADD UNIQUE KEY `fingerprint_uuid` (`fingerprint_uuid`); -- -- Indexes for table `wp_itsec_geolocation_cache` -- ALTER TABLE `wp_itsec_geolocation_cache` ADD PRIMARY KEY (`location_id`), ADD UNIQUE KEY `location_host` (`location_host`), ADD KEY `location_time` (`location_time`); -- -- Indexes for table `wp_itsec_lockouts` -- ALTER TABLE `wp_itsec_lockouts` ADD PRIMARY KEY (`lockout_id`), ADD KEY `lockout_expire_gmt` (`lockout_expire_gmt`), ADD KEY `lockout_host` (`lockout_host`), ADD KEY `lockout_user` (`lockout_user`), ADD KEY `lockout_username` (`lockout_username`), ADD KEY `lockout_active` (`lockout_active`); -- -- Indexes for table `wp_itsec_logs` -- ALTER TABLE `wp_itsec_logs` ADD PRIMARY KEY (`id`), ADD KEY `module` (`module`), ADD KEY `code` (`code`), ADD KEY `type` (`type`), ADD KEY `timestamp` (`timestamp`), ADD KEY `user_id` (`user_id`), ADD KEY `blog_id` (`blog_id`), ADD KEY `init_timestamp` (`init_timestamp`); -- -- Indexes for table `wp_itsec_mutexes` -- ALTER TABLE `wp_itsec_mutexes` ADD PRIMARY KEY (`mutex_id`), ADD UNIQUE KEY `mutex_name` (`mutex_name`); -- -- Indexes for table `wp_itsec_opaque_tokens` -- ALTER TABLE `wp_itsec_opaque_tokens` ADD PRIMARY KEY (`token_id`), ADD UNIQUE KEY `token_hashed` (`token_hashed`); -- -- Indexes for table `wp_itsec_temp` -- ALTER TABLE `wp_itsec_temp` ADD PRIMARY KEY (`temp_id`), ADD KEY `temp_date_gmt` (`temp_date_gmt`), ADD KEY `temp_host` (`temp_host`), ADD KEY `temp_user` (`temp_user`), ADD KEY `temp_username` (`temp_username`); -- -- Indexes for table `wp_itsec_user_groups` -- ALTER TABLE `wp_itsec_user_groups` ADD PRIMARY KEY (`group_id`); -- -- Indexes for table `wp_links` -- ALTER TABLE `wp_links` ADD PRIMARY KEY (`link_id`), ADD KEY `link_visible` (`link_visible`); -- -- Indexes for table `wp_options` -- ALTER TABLE `wp_options` ADD PRIMARY KEY (`option_id`), ADD UNIQUE KEY `option_name` (`option_name`), ADD KEY `autoload` (`autoload`); -- -- Indexes for table `wp_postmeta` -- ALTER TABLE `wp_postmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `post_id` (`post_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_posts` -- ALTER TABLE `wp_posts` ADD PRIMARY KEY (`ID`), ADD KEY `post_name` (`post_name`(191)), ADD KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), ADD KEY `post_parent` (`post_parent`), ADD KEY `post_author` (`post_author`); -- -- Indexes for table `wp_smush_dir_images` -- ALTER TABLE `wp_smush_dir_images` ADD UNIQUE KEY `id` (`id`), ADD UNIQUE KEY `path_hash` (`path_hash`), ADD KEY `image_size` (`image_size`); -- -- Indexes for table `wp_termmeta` -- ALTER TABLE `wp_termmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `term_id` (`term_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_terms` -- ALTER TABLE `wp_terms` ADD PRIMARY KEY (`term_id`), ADD KEY `slug` (`slug`(191)), ADD KEY `name` (`name`(191)); -- -- Indexes for table `wp_term_relationships` -- ALTER TABLE `wp_term_relationships` ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`), ADD KEY `term_taxonomy_id` (`term_taxonomy_id`); -- -- Indexes for table `wp_term_taxonomy` -- ALTER TABLE `wp_term_taxonomy` ADD PRIMARY KEY (`term_taxonomy_id`), ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), ADD KEY `taxonomy` (`taxonomy`); -- -- Indexes for table `wp_usermeta` -- ALTER TABLE `wp_usermeta` ADD PRIMARY KEY (`umeta_id`), ADD KEY `user_id` (`user_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_users` -- ALTER TABLE `wp_users` ADD PRIMARY KEY (`ID`), ADD KEY `user_login_key` (`user_login`), ADD KEY `user_nicename` (`user_nicename`), ADD KEY `user_email` (`user_email`); -- -- Indexes for table `wp_wpforms_tasks_meta` -- ALTER TABLE `wp_wpforms_tasks_meta` ADD PRIMARY KEY (`id`); -- -- Indexes for table `wp_yoast_indexable` -- ALTER TABLE `wp_yoast_indexable` ADD PRIMARY KEY (`id`), ADD KEY `object_type_and_sub_type` (`object_type`,`object_sub_type`), ADD KEY `object_id_and_type` (`object_id`,`object_type`), ADD KEY `permalink_hash_and_object_type` (`permalink_hash`,`object_type`), ADD KEY `subpages` (`post_parent`,`object_type`,`post_status`,`object_id`), ADD KEY `prominent_words` (`prominent_words_version`,`object_type`,`object_sub_type`,`post_status`); -- -- Indexes for table `wp_yoast_indexable_hierarchy` -- ALTER TABLE `wp_yoast_indexable_hierarchy` ADD PRIMARY KEY (`indexable_id`,`ancestor_id`), ADD KEY `indexable_id` (`indexable_id`), ADD KEY `ancestor_id` (`ancestor_id`), ADD KEY `depth` (`depth`); -- -- Indexes for table `wp_yoast_migrations` -- ALTER TABLE `wp_yoast_migrations` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `wp_yoast_migrations_version` (`version`); -- -- Indexes for table `wp_yoast_primary_term` -- ALTER TABLE `wp_yoast_primary_term` ADD PRIMARY KEY (`id`), ADD KEY `post_taxonomy` (`post_id`,`taxonomy`), ADD KEY `post_term` (`post_id`,`term_id`); -- -- Indexes for table `wp_yoast_seo_links` -- ALTER TABLE `wp_yoast_seo_links` ADD PRIMARY KEY (`id`), ADD KEY `link_direction` (`post_id`,`type`), ADD KEY `indexable_link_direction` (`indexable_id`,`type`); -- -- Indexes for table `wp_yoast_seo_meta` -- ALTER TABLE `wp_yoast_seo_meta` ADD UNIQUE KEY `object_id` (`object_id`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `wp_actionscheduler_actions` -- ALTER TABLE `wp_actionscheduler_actions` MODIFY `action_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=644; -- -- AUTO_INCREMENT for table `wp_actionscheduler_claims` -- ALTER TABLE `wp_actionscheduler_claims` MODIFY `claim_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=840; -- -- AUTO_INCREMENT for table `wp_actionscheduler_groups` -- ALTER TABLE `wp_actionscheduler_groups` MODIFY `group_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3; -- -- AUTO_INCREMENT for table `wp_actionscheduler_logs` -- ALTER TABLE `wp_actionscheduler_logs` MODIFY `log_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=872; -- -- AUTO_INCREMENT for table `wp_commentmeta` -- ALTER TABLE `wp_commentmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_comments` -- ALTER TABLE `wp_comments` MODIFY `comment_ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_css_js_manager` -- ALTER TABLE `wp_css_js_manager` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_duplicator_packages` -- ALTER TABLE `wp_duplicator_packages` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10; -- -- AUTO_INCREMENT for table `wp_itsec_bans` -- ALTER TABLE `wp_itsec_bans` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT for table `wp_itsec_distributed_storage` -- ALTER TABLE `wp_itsec_distributed_storage` MODIFY `storage_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=641; -- -- AUTO_INCREMENT for table `wp_itsec_fingerprints` -- ALTER TABLE `wp_itsec_fingerprints` MODIFY `fingerprint_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_itsec_geolocation_cache` -- ALTER TABLE `wp_itsec_geolocation_cache` MODIFY `location_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_itsec_lockouts` -- ALTER TABLE `wp_itsec_lockouts` MODIFY `lockout_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=85; -- -- AUTO_INCREMENT for table `wp_itsec_logs` -- ALTER TABLE `wp_itsec_logs` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=54082; -- -- AUTO_INCREMENT for table `wp_itsec_mutexes` -- ALTER TABLE `wp_itsec_mutexes` MODIFY `mutex_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_itsec_temp` -- ALTER TABLE `wp_itsec_temp` MODIFY `temp_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3288; -- -- AUTO_INCREMENT for table `wp_links` -- ALTER TABLE `wp_links` MODIFY `link_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_options` -- ALTER TABLE `wp_options` MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=123924; -- -- AUTO_INCREMENT for table `wp_postmeta` -- ALTER TABLE `wp_postmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3318; -- -- AUTO_INCREMENT for table `wp_posts` -- ALTER TABLE `wp_posts` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=385; -- -- AUTO_INCREMENT for table `wp_smush_dir_images` -- ALTER TABLE `wp_smush_dir_images` MODIFY `id` mediumint(9) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_termmeta` -- ALTER TABLE `wp_termmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_terms` -- ALTER TABLE `wp_terms` MODIFY `term_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; -- -- AUTO_INCREMENT for table `wp_term_taxonomy` -- ALTER TABLE `wp_term_taxonomy` MODIFY `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; -- -- AUTO_INCREMENT for table `wp_usermeta` -- ALTER TABLE `wp_usermeta` MODIFY `umeta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=159; -- -- AUTO_INCREMENT for table `wp_users` -- ALTER TABLE `wp_users` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3; -- -- AUTO_INCREMENT for table `wp_wpforms_tasks_meta` -- ALTER TABLE `wp_wpforms_tasks_meta` MODIFY `id` bigint(20) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=22; -- -- AUTO_INCREMENT for table `wp_yoast_indexable` -- ALTER TABLE `wp_yoast_indexable` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=52; -- -- AUTO_INCREMENT for table `wp_yoast_migrations` -- ALTER TABLE `wp_yoast_migrations` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=22; -- -- AUTO_INCREMENT for table `wp_yoast_primary_term` -- ALTER TABLE `wp_yoast_primary_term` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_yoast_seo_links` -- ALTER TABLE `wp_yoast_seo_links` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=32; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;