ity is wired into applications. And that functionality as in Internet Explorer has access to files on your computer, as well as the web at the same time is wired into a lot of applications, which is why you often see these very advanced tools that people are using in say a bank or a doctor&#8217;s office that can only use Internet Explorer, because it&#8217;s also the file explorer, So there&#8217;s decisions made early on in a rapidly evolving space, lead to enormous legacy debt that is almost impossible to get out of. in the open source world, that legacy debt is the lack of governance protocols for how decisions are made. And what you see in the open source world is that ad hoc governance models are introduced, like a very poorly defined consensus model. Because of a lack of existing models. But then due to how the community has over time, and the freedom given to contributors, it&#8217;s very hard to go and say, now that we are successful, we&#8217;re going to start imposing rules onto the way we work. Because then all the people who came in when there was free to do whatever you want, will be like, hey, why are you suddenly restricting my freedoms?</p>\n\n\n\n<p>Why are you standing in the way of me doing things the way I want to? this is what you see anytime you try to bring these issues up that people are saying, you&#8217;re standing in the way of what I&#8217;m doing. again, this becomes a scale problem because, from the individual contributors perspective, when you are working in open source, you&#8217;re really solving your own problems.</p>\n\n\n\n<p>You&#8217;re saying, I want this feature, and I believe that this feature is something someone else would have so I&#8217;m going to make it and put it into the project. But if you&#8217;re doing that on a project that influences or impacts tens of thousands of businesses, for example. Say you&#8217;re making an e-commerce platform, every change you make will have mission critical impact on all the people who use it.</p>\n\n\n\n<p>So you&#8217;re not making a decision for yourself. You&#8217;re making a decision for all the other people who are using the thing. And, when I spoke, I speak at an open source conferences, I always start by saying the people in this room are the 1% of open source. Because by being at an open source conference, you are identifying yourself as not being a standard open source user. The normal open source user, never interfaces with the community at all.</p>\n\n\n\n<p>They download the software and use it as is. That&#8217;s it. That&#8217;s their interface with the community. By being an active part of the community, you are identifying yourself as a privileged person within the community. You have more knowledge of the software than anyone else. You have more influence over the project than anyone else.</p>\n\n\n\n<p>And you do not use the software the way your users use it. So you are not developing the software for you. You&#8217;re developing the software for someone you don&#8217;t fully understand because you&#8217;re not that person anymore. And that&#8217;s a scale thing. Understanding that is very difficult.</p>\n\n\n\n<p>It&#8217;s a skill that you have to constantly train yourself to maintain and understanding that a trivial decision has an impact on a thousand or ten thousand or a hundred thousand or a million people, is very difficult, because it makes it challenging to even do anything, unless you then go, actually, no, it&#8217;s just from me. And I have the power to do it because it&#8217;s open source.</p>\n\n\n\n<p>[00:37:48] <strong>Nathan Wrigley:</strong> One of the things which comes out of your piece is a desire people, going to use the word remunerated, not strike a balance of what it is that you actually want to say, but I&#8217;ll use it anyway, are remunerated for the work that they do. In the sense that, volunteering is laudable. It&#8217;s an altruistic thing. I don&#8217;t think in any walk of life, anybody is going to say that volunteering is not something to be commended, but presumably there is some line in the sand, I don&#8217;t know where that line lives exactly, there&#8217;s a line at which perhaps you feel that remuneration ought to take place.</p>\n\n\n\n<p>And I don&#8217;t know what the criteria for that is/ maybe it&#8217;s the legacy of things that you&#8217;ve done in the past. Maybe it&#8217;s the of the thing that you&#8217;re about to commit. I don&#8217;t know. But I&#8217;d be curious if you could develop that a little bit. Talk about how it is that you feel people desiring remuneration.</p>\n\n\n\n<p>And in the case of some recent events, how perhaps they felt challenged and perhaps bullied is the right word by larger entities who almost imagined that they were employees of theirs. In the case of Log 4 j, being contacted via email by people who just assumed that their software was something that they could force them to update, after sending them a snotty email. So let&#8217;s develop that a little bit.</p>\n\n\n\n<p>[00:39:09] <strong>Morten Rand-Hendriksen:</strong> I&#8217;m going to say two very contradictory things. I don&#8217;t think anyone should be paid for open source development. I also think that all open source developers should be paid for open source development. The reason is, in an ideal world, open source should be completely free, and we should all have the capability to contribute what we can, and build software that has no strings attached. That is the ideal. That is the dream of open source. That open source software exists independent of capitalism. That we can say, you build software, people use it, no one ever attaches any strings to any of that. If you can contribute, you contribute. If you have something meaningful to contribute, you can. It&#8217;ll get included. You can fork it. Everything will be fine.</p>\n\n\n\n<p>However, and this was the dream of the GNU manifesto, that this would be the future we would be building. Where it would no longer be necessary to get paid because dynamically people would just get paid through other means somehow, I don&#8217;t know. It&#8217;s very unclear how that&#8217;s going to happen, but that was the dream. However, we live in a real world and the real world is a capitalist world, where your contributions have value, whether you are paid for them or not. And this has become exceptionally clear in the open source space because in the open source spaces, there are corporations that have billion dollar valuations, that are built either on the open source software or basically represent the open source software itself. Who for every contribution that&#8217;s made by a volunteer, an unpaid volunteer contributor, the corporation is able to pull significant monetary value from the project. At that point, you get this enormous power imbalance between the volunteer, unpaid contributor, and the corporations who earn billions of dollars off the application, and are able to spend some of that money putting contributors into the project. When you have that kind of power imbalance, the only responsible thing to do is to put a monetary value on contribution and say, we are going to redistribute the wealth. And the insane part about this is this was actually addressed by the new manifesto. I have it open here.</p>\n\n\n\n<p>All sorts of development can be funded with a software tax. I&#8217;m just reading verbatim, right? By the way. Suppose everyone who buys a computer has to pay X percent of the price as a software tax. The government gives this to an agency like the NSF, that&#8217;s the organization that he was running at the time, to spend on software development. But if the computer buyer makes a donation to software development itself, he can take a credit against the tax.</p>\n\n\n\n<p>He can donate to the project of his own choosing, often chosen because he hopes to use the results when it&#8217;s done. He can take a credit for any amount of donation up to the total tax he had to pay. The total tax rate could be decided by a vote of the payers of the tax weighted against the amounts they will be taxed on.</p>\n\n\n\n<p>And the consequences for that would be the computer using community support, software development. The community decides what level of support is needed, and users who care, which project their share is spent on can choose this for themselves.</p>\n\n\n\n<p>So, in this, which partly makes sense, and partly is just a utopian fever dream, he lays out in very clear language. There should be a software tax. If you talk to open source leaders, they will aggressively fight this idea. And I think part of the reason for that, and this is purely my opinion and observation, is the second we start paying people for contribution, the power balance shifts dramatically within the open source communities, because there is a large portion of people in the world who do not have the privilege of contribution right now, who just can&#8217;t. Either their jobs preclude them from doing it to begin with. Not because the company&#8217;s saying you can&#8217;t contribute, but because their jobs are too overwhelming to spend time contributing to open source. Their lives may be in the way. They may not have time in their lives to do open source contribution. They may not be in a position where they can volunteer their time because their monetary value they derive from their time in a work is more important to them than being able to contribute.</p>\n\n\n\n<p>And people find themselves in a myriad of circumstances where just volunteerism of any kind is not possible. In addition to that, you have all the socioeconomic factors and the social factors that impact how we interact with other people. All the things that impact our interactions with people impact open source contribution. Including gender representation, sex representation, race, culture, creed, religion, physical location, ethnicity, how you present yourself to the world, neurodivergence, disability, all of these things come into play, right? So the assumption that open source has the best contributors, because the best contributors bubble to the top, assumes everyone is the same. In reality, everyone is not the same. There is a small handful of people who fall into that category of, just being able to contribute their time freely.</p>\n\n\n\n<p>The majority of us can&#8217;t do that. The majority of us are dependent on money to pay for housing, to pay for food, to pay for our kids, to pay for being able to function in the world. And all of those people are more or less excluded from contribution. So therefore you get a subset of the population during the contribution. In that scenario, when you at the same time, have corporations deriving billions of dollars out of the source project, you cannot argue that, no, we should continue to not pay contributors.</p>\n\n\n\n<p>And then you get to that whole question that you brought up with, like, how do you do this? How do you pay contributors? Because how do you measure. Let&#8217;s say someone who goes and rewrites all the PHP in the project from someone who runs one of the support groups on a Slack channel, right?</p>\n\n\n\n<p>Both of those things are valid contributions to the project. One of them is easily measurable. The other one is very difficult to measure. Which one of them have the most impact on the project? I would say if you want to follow like the open source ideology of like in the future, everything will be free no one will have to be paid for anything. would say the measure should be time. It should not be what you do. It should be time. And then you have to qualify the time and say like, if you spend eight hours doing something that should have taken you two minutes, probably shouldn&#8217;t be paid eight hours of work. But if you are spending eight hours on something that someone who is more skilled than you would do in hours, you should probably be paid for the eight hours of work because it&#8217;s a learning process. But then if you go down that route, you then ask, who pays and the simple answer is the people who earn money from this should pay a part of that money back into the community. And it should not be 5%, because their entire financial basis is built on the platform of the open source software.</p>\n\n\n\n<p>The wealth of these companies that are built on top of open source is entirely contingent on the free labor of the volunteers, which is insane and would never fly in any other context, right? If you want to use Marxian terms, it&#8217;s exploitation of labor, right? And you&#8217;re taking the free labor of someone else and turning it into money and not giving money back to them. And no amount of oh, but my corporation volunteers its people back into the community, will account for that because that&#8217;s not what&#8217;s happening. If you have a corporation that&#8217;s financially dependent on the success of the open source project, and you put some of your people back into the project, you are not volunteering anything. Those people are now paid to direct the project in directions that are fruitful to your company so that you can derive more money from it. And if that&#8217;s the model you want to run, that&#8217;s fine. Then that has to be explicitly stated, that this open source project is actually a money machine for me, and I&#8217;m going to put my people into it, and they are being paid to direct the project in directions that are fruitful to me. And if you contribute that as on you. Gatsby actually does this, right. Gatsby used to have two websites. They used to have the dot org version of Gatsby, the open source project. And then they had gatsby.com, which was Gatsby cloud and their commercial offering. They combined them and they said we&#8217;re not going to pretend what&#8217;s happening here. There&#8217;s a commercial project called Gatsby that has an open source component to it. So you can use Gatsby any way you want, but we&#8217;re going to be crystal clear about this being a commercial venture. And when you contribute to Godspeed, you are putting money in our pockets. And it&#8217;s a very open way of dealing with this problem.</p>\n\n\n\n<p>So as long as you have interests within the community that are deriving value from the open source community, they should be paying back into the community. And the way that practically this should be done would probably be something like having a foundation of some kind, or an organization within the community that collects money that anyone can pay to. If you&#8217;re a user and you go, I want to, I can&#8217;t contribute in terms of writing software or being in the community, but I can give some money. Or if you&#8217;re a company that relies on the software, you can pay into this organization, and then that organization determines how to distribute that money, not through what is of interest to the corporate interest, but just like looking at the project, where should we funnel money right now to get things done?</p>\n\n\n\n<p>This is what the open JS foundation does. So they have foundation where you can pay in money and then they will distribute the money according to need, both for the project and for the people who contribute to it so that you can actually get work done. There is no reason why open source projects can&#8217;t have this. Other than that it&#8217;s resisted by the leadership, because it shifts, power. That&#8217;s the way it is. It&#8217;s a power thing. When you give people money for work, you&#8217;re changing the structure of how things are done. And that&#8217;s not something people who are driving massive amounts of money from a project want because then the power shifts.</p>\n\n\n\n<p>[00:49:10] <strong>Nathan Wrigley:</strong> What would you say to somebody, I suspect this imaginary person wouldn&#8217;t be tremendously difficult to find, but what would you say to somebody who said, am totally happy with the way it is now? am really content with volunteering. Some time literally volunteering it with no expectation of anything. Just to be a good citizen, to be a part of the community and to see the project that I&#8217;m involved with over time. Don&#8217;t want to see financial reward or whatever it may be, I just want to contribute and see it grow for growth&#8217;s sake.</p>\n\n\n\n<p>[00:49:41] <strong>Morten Rand-Hendriksen:</strong> Congratulations on being a white man living in north America or Western Europe, is what I would to say to that. That is basically the person you&#8217;re describing. That is a person with enormous privilege. Doesn&#8217;t have to be the person I just described, but it&#8217;s very likely to be that person I described. A person who has the privilege, not only of contributing their free time to a project like this without any expectation of renumeration, and who has the worldview that this is something everyone can do, and therefore it&#8217;s okay, is a person with enormous privilege. This is basic deontology, right. Duty ethics. If you do something, you are saying that this is the model you want everyone else to follow. It also implies that if you think that this is okay, you are saying, this is okay for everyone.</p>\n\n\n\n<p>This is part of the problem that we have. The ideology that underpins this assumes equity in the system. When we know the system is not equitable. When we know that there are people with enormous power within all these open source projects, who earn millions of dollars off the open source project, where there are other people, with great ideas who earned zero dollars off the project who have no power because they don&#8217;t get paid for it, and they don&#8217;t have the ability to contribute. And that&#8217;s when you get this whole like, decisions are made by the people who show up and the people who show up are the people with privilege. So that means decisions are made by the people with privilege. And that&#8217;s how you get things like open source projects that disregard accessibility, because people with accessibility issues have a much higher threshold to walk across to get into the project and be able to contribute. And they are facing challenges in their lives that make it more difficult for them to be able to contribute without getting paid. As a result, the voices that would argue for more accessibility are effectively excluded from the conversation because they are not contributing as much as everyone else and thereby their views of the world are not embedded into the project because they&#8217;re never heard.</p>\n\n\n\n<p>So it&#8217;s about privilege, and it&#8217;s a very privileged position to say, I&#8217;m fine with not getting paid. I&#8217;m one of those people, who, when I was contributing to open source projects, when I still contribute to open source project, I do that while I&#8217;m being paid by my company to do that.</p>\n\n\n\n<p>Part of my job is to be embedded in open source projects to see what&#8217;s going on. And I use part of that time to help open source projects. But that means I am not the normal contributor. And that also means I have freedoms that other people don&#8217;t have to do things that other people can&#8217;t do. And I have to keep that in mind because that means I need to then bring those voices that can&#8217;t be at the table to the table, or represent the ideas of those voices at the table, ensure that those voices are heard in some way. part of that is me having conversations like this and saying, the fact that you don&#8217;t have equity in your system that the system is inequitable, and that the system will remain inequitable until you actively do something about it.</p>\n\n\n\n<p>And the clearest path to doing that is by paying people. then you could extend that and say, people can choose. If you work for a company that&#8217;s paying for a contribution, then you don&#8217;t get paid. you don&#8217;t work for a company that&#8217;s paying for your contributions and you&#8217;re doing it on your own, then you can go apply to get paid.</p>\n\n\n\n<p>[00:52:59] <strong>Nathan Wrigley:</strong> As with all of these things, the broad brush strokes of the idea are easy to crystallize. It&#8217;s straightforward conceive of these things. My guess is that some parts of the internet where you live, these ideas are crystallizing and they&#8217;re up for discussion, and this debate is ongoing. Where do you go to discover these ideas? What communities are you in, where these kinds of things are up for debate and so on.</p>\n\n\n\n<p>[00:53:24] <strong>Morten Rand-Hendriksen:</strong> Open source projects are grassroots political organizations pretending to be software development communities. If you go look at grassroots political organizations, you very quickly see that it&#8217;s the same thing. ad hoc communities that grow over time, power. There&#8217;s power struggles within those communities. And eventually someone realizes, hey, doesn&#8217;t work, so they start implementing governance rules and they turn into either functioning organizations or they collapse, or they fracture, or fork into multiple different versions of themselves. Acknowledgement of this fact a long way to understanding how to move forward. Because the notion that, if you talk to individual open source contributors, especially powerful open source contributors who have significant sway on projects, they will always talk about the project as if it&#8217;s still some sort of hobby thing that they and their friends are doing on their spare time for fun. And in that frame that anyone who comes in and says, hey, we should do things differently are infringing on their freedom to do whatever they want in their spare time, as a hobby, Someone is coming to me and telling me I can&#8217;t drive my RC boats in the local lake. how it&#8217;s approached in reality. not what it is at all. It&#8217;s more like, you started with your little RC boat in a lake, now you&#8217;re running the main transportation hub for people who are moving from one island to another, but you&#8217;re still acting as if it&#8217;s just some hobby project. It&#8217;s not. There&#8217;s a disconnect between the reality of the impact people have how they treat it. And a grassroots political organization, the impact of the work you do become immediately apparent to you because you interface with the people you&#8217;re working with all the time, and you can see the real world impact .</p>\n\n\n\n<p>In software development you never interface with the people you impact, or you only interface with the people, a small handful of them in very specific circumstances. you don&#8217;t really have a full understanding of what you are doing to the people you are building software for. I very intentionally say what you are doing to the people, because when you do any kind of design or development work, you&#8217;re really using people a vehicle to bring forth a view of the world or your vision of what the future should be like. It&#8217;s instrumentalism, you&#8217;re, quite literally building tools for people to use, and when they use those tools, they build the future that you devised for them. And that future is to your design. Software development gives you enormous power, but it also removes you from seeing the consequences of what you&#8217;re doing. And it gives you this cushion that you can sit on where you say, no, it&#8217;s just me mucking around with some software, it&#8217;s not a big deal. Meanwhile, it is a huge deal for a lot of people. So it&#8217;s a very sticky problem because it has to do with changing the way people think about open source software contribution, not as something you&#8217;re doing because you like it, but it&#8217;s something you&#8217;re doing that is changing the world.</p>\n\n\n\n<p>And it&#8217;s funny because the open source contributors will very, very happily talk about the enormous impacts open source software has on the world until you ask them, how are you held accountable for this, at which point they are very quick to tell you, oh no one is allowed to restrict my creativity and freedom in doing any kind of development. How dare you bring this up, right?</p>\n\n\n\n<p>[00:56:43] <strong>Nathan Wrigley:</strong> I feel like we&#8217;ve just scratched the surface. We&#8217;re the best part of an hour in, and I know that you&#8217;re constrained by time, but I&#8217;m sure that for those people who have been intrigued, they&#8217;ll be keen to make contact with you and discover about your thoughts. you have a place, some places on the internet where you can be best discovered?</p>\n\n\n\n<p>[00:57:06] <strong>Morten Rand-Hendriksen:</strong> Yeah. I&#8217;m on Twitter @mor10, mor 10, cause that&#8217;s my name. You can also find me on LinkedIn. I&#8217;m Morten Rand-Hendriksen on LinkedIn. I should be fairly easy to find. And I have a website, Mor10.com, one zero dot com. I&#8217;m I cross post everything. I post elsewhere onto my website too, so that I have control over my own content.</p>\n\n\n\n<p>And I&#8217;m on TikTok now, at mor 10 web, so mor one zero web, because there&#8217;s someone else by the moniker Morten who&#8217;s not using their account, so you can find me there as well. Reach out to me from any platform. You&#8217;ll find me.</p>\n\n\n\n<p>[00:57:41] <strong>Nathan Wrigley:</strong> Absolutely fascinating discussion. I hope that you get some reaching out to you and continuing the discussion and the debate and thank you so much for joining us.</p>\n</div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 23 Feb 2022 15:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:90:"WordCamp Central: Nexcess joins the WordPress global community sponsorship program in 2022";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:39:"https://central.wordcamp.org/?p=3146022";s:7:"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:118:"https://central.wordcamp.org/news/2022/02/23/nexcess-joins-the-wordpress-global-community-sponsorship-program-in-2022/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1270:"<p><span>We couldn’t be happier to welcome </span><strong><span><a href="https://www.nexcess.net/">Nexcess</a></span></strong><span> to the <a href="https://central.wordcamp.org/sponsor-multiple-wordcamps/">WordPress global community sponsorship program</a></span><span> in 2022! They’re sponsoring at the Gold level, supporting official WordPress community events around the globe.</span></p>\n<p><a href="https://central.wordcamp.org/files/2019/02/Nexcess-Logo-Horiz.png"><img /></a></p>\n<p><span>Nexcess provides a fully managed, high-performance, and best-in-class cloud solution built to optimize WordPress and WooCommerce sites and stores. For over 20 years</span><span>, our holistic, hands-on approach to managed products and solutions has provided users with tools that help them create better websites and e-commerce stores along with expert, on-demand support. By removing the stress of managing the day-to-day operations of their site or store, we afford our customers the ability to </span>PRESS<span> forward and focus more on what inspires them.</span></p>\n<p><span>Whether you&#8217;re a small business owner, designer, developer, or a small to medium-sized agency, Nexcess has a solution </span><span>to help you and your business succeed.</span></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 23 Feb 2022 14:00: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:6:"Isotta";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:56:"WPTavern: The Case for a Shared CSS Toolkit 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:30:"https://wptavern.com/?p=130404";s:7:"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://wptavern.com/the-case-for-a-shared-css-toolkit-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6789:"<p class="has-drop-cap">Earlier today, Mark Root-Wiley published an in-depth <a href="https://mrwweb.com/standardized-design-tokens-css-wordpress-future/">proposal around standardized design tokens and CSS</a> for WordPress. The goal is to create a consistent, customizable, and interoperable system around the design tools in core. Essentially, he is proposing a standardized design framework or, as he refers to it, a &#8220;shared CSS toolkit&#8221; that WordPress, themes, and plugins can rely on.</p>\n\n\n\n<p>The blog post clocks in at nearly 4,000 words. He also added a shorter version of the <a href="https://github.com/WordPress/gutenberg/issues/38998">proposal via a Gutenberg GitHub ticket</a>. However, the post expands on the idea, linking to resources that span a few years.</p>\n\n\n\n<p>I responded to Root-Wiley via email. This was a subject near and dear to me. It has also been a source of frustration from other theme authors I have had the privilege of talking to over the last few years. These are themers who have been 100% behind the block system since Day 1, not the random guy in the back shouting, &#8220;Gutenberg sucks!&#8221;</p>\n\n\n\n<p>The primary thought I shared was that there has been a bit of fatigue on the topic. There is a push to bring standard presets to core every so often. But, it always feels like the wheels are spinning in the mud until everyone gets out of the car when they realize it&#8217;s not moving.</p>\n\n\n\n<p>Root-Wiley pointed to my 2019 post, <a href="https://wptavern.com/themes-of-the-future-a-design-framework-and-a-master-theme">Themes of the Future: A Design Framework and a Master Theme</a>, as a common ancestor to his deep dive into the bowels of this issue. But, others and I have been talking about it even before the launch of the block editor in WordPress 5.0.</p>\n\n\n\n<p>In part, this is because we were excited about the potential of more standardization. WordPress could finally correct some of its longstanding issues and usher in a utopian era of theme creation based on well-designed conventions.</p>\n\n\n\n<p>WordPress 5.0 rolled out theme-support flags for custom font sizes and a color palette. The features in and of themselves were a welcome first step, but they did not go far enough. WordPress should have leaped ahead and set standards from the outset.</p>\n\n\n\n<p>Instead, we got a mish-mash of default font size and color names with no guidelines on what they meant. <em>How huge is the &#8220;huge&#8221; font size? What if I need to follow that naming scheme and need something larger? What should I name it?</em> (For a potentially educational tangent on size names, see my <a href="https://wptavern.com/feed#a-never-before-published-list-of-sizes">notes at the end of this post</a>.)</p>\n\n\n\n<p>I still cringe every time I see classes like <code>.has-luminous-vivid-orange-background-color</code>.</p>\n\n\n\n<p>However, I will not continue bashing the mistakes of the platform&#8217;s past. It is time to look forward. Root-Wiley notes in his post:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>I would like to propose a path toward standardizing how CSS for WordPress designs and layouts are created so they are more transparent, efficient, and customizable. Not only can this approach simplify core styles, it would address a number of long-term WordPress pain points that predate even the block editor&#8217;s release in WordPress 5.0.</p></blockquote>\n\n\n\n<p>I want to see presets for everything users can select via the block design tools. For example, instead of setting absolute units for margins, they can choose predefined sizes from WordPress and/or their theme. However, there should be standards for naming these presets.</p>\n\n\n\n<p><em>Why is this so important?</em> Imagine setting a top margin of <code>20px</code> on a block in some blog post. It looks good and matches your current theme, and you repeat this process dozens or more times on various elements. Then, you change designs down the road. This could be a full theme switch or a change via the global styles system. This new design implements a different vertical spacing system. <code>24px</code> might make more sense than the <code>20px</code> littered throughout the site.</p>\n\n\n\n<p>The old setting would be tied to a global value in an ideal world, not the block. This would allow it to match whatever design system is in place.</p>\n\n\n\n<p>Margins are just one piece of a much larger puzzle. And, presets for the various design tools do not even cover everything in Root-Wiley&#8217;s proposal. That is why I encourage all theme and plugin authors to review it.</p>\n\n\n\n<p>There are a few items I disagree with in the proposal. However, those involve the low-level implementation work, not the concept of creating a standardized system. I had planned to discuss those in detail, but doing so would get into what a former team member I worked with called &#8220;weed discussions.&#8221; They get in the way of the big picture.</p>\n\n\n\n<p>If there is one thing Root-Wiley and I agree on, it is that big picture of creating a CSS toolkit to carry WordPress into the future.</p>\n\n\n\n<h2 id="a-never-before-published-list-of-sizes">A Never-Before-Published List of Sizes</h2>\n\n\n\n<p>This is a bit of a side tangent, but I did do a ton of research on size names following the WordPress font-size model. And, because I will likely never have a reason to publish my findings elsewhere, I might as well post them here.</p>\n\n\n\n<p>If you were ever wondering what specific sizes are bigger or smaller than others (e.g., Colossal vs. Titanic), I present to you a <em>somewhat-educated-but-may-not-be-100%-correct</em> list:</p>\n\n\n\n<ul><li>Diminutive (2XS)</li><li>Tiny (XS)</li><li>Small</li><li>Normal (Medium, Regular, Base)</li><li>Large</li><li>Extra Large (XL)</li><li>Huge (2XL)</li><li>Gargantuan (3XL)</li><li>Colossal (4XL)</li><li>Titanic (5XL)</li><li>Olympic (6XL)</li><li>Planetary (7XL)</li><li>Galactic (8XL)</li><li>Universal (9XL)</li></ul>\n\n\n\n<p>That is likely not an exhaustive list, but I spent several weeks looking up and comparing definitions and resources. I added a few alternatives in the mix for reference.</p>\n\n\n\n<p>I also wanted to post this to show how naming things can break the user experience. The average user should not have to think about which sizes are the biggest or smallest. A naming system like this is a recipe for confusion. Even if the user experience works, the code-based slugs should not confuse developers.</p>\n\n\n\n<p>This same rule applies to colors and all other presets. Naming things is hard, but it is even tougher when you have already made a mess and need to fix it later. It starts at the foundation, especially when everything added today will be a part of the legacy code set for years to come.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 23 Feb 2022 02:01:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:115:"WPTavern: Amazon Drops “Elasticsearch” From Product Names To Settle Trademark Infringement Lawsuit With Elastic";s:7:"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=130400";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:120:"https://wptavern.com/amazon-drops-elasticsearch-from-product-names-to-settle-trademark-infringement-lawsuit-with-elastic";s: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:3117:"<p>Elastic has resolved a trademark infringement lawsuit related to usage of the term &#8220;Elasticsearch.&#8221; Amazon has agreed to drop the term from its product line. </p>\n\n\n\n<p>&#8220;We believe this resolution will remove confusion in the marketplace and provide much-needed clarity to our community and customers,&#8221; Elastic CEO Ashutosh Kulkarni said in the <a href="https://www.elastic.co/blog/elastic-and-amazon-reach-agreement-on-trademark-infringement-lawsuit">announcement</a>.</p>\n\n\n\n<p>&#8220;There is only one Elasticsearch, and it comes from Elastic.&#8221; </p>\n\n\n\n<p>In January 2021, <a href="https://wptavern.com/elasticpress-io-service-considers-next-move-after-elasticsearch-abandons-open-source-licensing">Elastic abandoned Elasticsearch&#8217;s open source licensing</a>, claiming that AWS&#8217;s behavior &#8220;forced&#8221; the company to switch from the <a rel="noreferrer noopener" href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank">Apache 2.0-license</a> to be dual-licensed under the <a rel="noreferrer noopener" href="https://www.mongodb.com/licensing/server-side-public-license" target="_blank">Server Side Public License (SSPL)</a> and the <a rel="noreferrer noopener" href="https://github.com/elastic/elasticsearch/blob/0d8aa7527e242fbda9d84867ab8bc955758eebce/licenses/ELASTIC-LICENSE.txt" target="_blank">Elastic License</a>. Elastic cited examples of what they perceived to be &#8220;ethically challenged behavior.&#8221; </p>\n\n\n\n<p>Shortly after, Amazon led a community effort to fork the project in order to maintain its open source license. In September 2021, Amazon <a href="https://aws.amazon.com/blogs/aws/amazon-elasticsearch-service-is-now-amazon-opensearch-service-and-supports-opensearch-10/">renamed</a> its Amazon Elasticsearch Service to Amazon OpenSearch Service after adopting the fork.</p>\n\n\n\n<p>Elastic initiated the trademark infringement lawsuit in 2019 after AWS <a href="https://aws.amazon.com/blogs/aws/new-open-distro-for-elasticsearch/">launched an Open Distro for Elasticsearch</a> in partnership with Expedia and Netflix. AWS said the motivation was to keep Elasticsearch open, because some of the more recent additions were proprietary. Amazon said the open distro was created &#8220;to accelerate open source Elasticsearch innovation.&#8221; Elastic claimed that the branding for this open distro violated their trademark.</p>\n\n\n\n<p>AWS has agreed to drop all instances of Elasticsearch from its product line. The only Elasticsearch service listed on the AWS Marketplace now is the one from Elastic Cloud. Elastic has eased its prior animosity in communication and is now working towards a more amicable partnership in promoting Elastic Cloud in the AWS marketplace.</p>\n\n\n\n<p>&#8220;Looking ahead, we’ll focus on collaborating with Amazon for the benefit of our shared customers who use Elastic on AWS,&#8221; Kulkarni said. &#8220;We are already seeing tremendous momentum in our partnership around our recent areas of investment to streamline data ingestion and simplify onboarding to Elastic Cloud on AWS.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Feb 2022 23:46: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:21;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:88:"Post Status: Post Status Excerpt (No. 47) — Should WordPress Adopt The Block Protocol?";s:7:"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=93789";s:7:"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:34:"https://poststatus.com/excerpt-47/";s: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:4406:"<h2 id="it-is-now-time-for-the-community-to-weigh-in-and-decide-whether-wordpress-should-stop-and-refuel-in-this-new-port-leonardo-losoviz">&#8220;It is now time for the community to weigh in and decide whether WordPress should stop and refuel in this new port.&#8221; —Leonardo Losoviz</h2>\n\n\n\n<p class="has-drop-cap">In this episode of Post Status Excerpt, David talks with Leonardo Losoviz about <a href="https://blockprotocol.org/">The Block Protocol</a> and why it might benefit WordPress to adopt it and allow other platforms to share and reuse blocks. Matt Mullenweg <a href="https://twitter.com/photomatt/status/1486793646045216769">has expressed interest</a> in taking this path.</p>\n\n\n\n<p><strong>Why This Is Important:</strong> Gutenberg, according to Matt, is &#8220;bigger than WordPress,&#8221;, especially in the context of the Open Web. The Block Protocol is a way to create and share content across WordPress, half-WordPress, and non-WordPress sites, which supports the project''s mission to democratize publishing.</p>\n\n\n\n\n\n\n\n<p class="has-background">Every week <strong><a href="https://poststatus.com/podcast/the-excerpt/">Post Status Excerpt</a></strong> will brief you on important WordPress news — in about 15 minutes or less! Learn what''s new in WordPress in a flash. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/26a1.png" alt="⚡" class="wp-smiley" /><br /><br />You can listen to <a href="https://poststatus.com/podcast/the-excerpt/">past episodes</a> of <strong>The Excerpt</strong>, <a href="https://poststatus.com/category/post-status-podcasts/">browse all our podcasts</a>, and don’t forget to subscribe on <a href="https://open.spotify.com/show/1m3xwXbe0MG5BzFVPtB0A7">Spotify</a>, Amazon Music, <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zaW1wbGVjYXN0LmNvbS8ySkU5c2M4UA">Google Podcasts</a>, <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">iTunes</a>, <a href="https://castro.fm/podcast/c53552c6-1ee0-4fc4-9de4-08ed6bf1ee4d">Castro</a>, <a href="https://www.youtube.com/c/PostStatus">YouTube</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, <a href="https://player.fm/series/wordpress-post-status-podcasts">Player.fm</a>, <a href="https://pca.st/05rR">Pocket Casts</a>, <a href="https://wordpress-post-status-draft-podcast.simplecast.com/">Simplecast</a>, or by <a href="https://feeds.simplecast.com/2JE9sc8P">RSS</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f3a7.png" alt="🎧" class="wp-smiley" /></p>\n\n\n\n<h3 id="h-mentioned-in-the-show"><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f517.png" alt="🔗" class="wp-smiley" /> Mentioned in the show:</h3>\n\n\n\n<ul><li><a href="https://www.smashingmagazine.com/2022/02/implications-wordpress-joining-block-protocol/">Implications Of WordPress Joining The Block Protocol</a></li><li><a href="https://www.joelonsoftware.com/2022/01/27/making-the-web-better-with-blocks/">Making The Web Better With Blocks</a></li><li><a href="https://blockprotocol.org/">The Block Protocol</a></li><li><a href="https://twitter.com/photomatt/status/1486793646045216769">Matt Mullenweg on Twitter</a></li><li><a href="https://twitter.com/losoviz">Leonardo Losoviz</a> (Twitter)</li><li><a href="https://twitter.com/dimensionmedia" target="_blank" rel="noreferrer noopener">David Bisset</a> (Twitter)</li><li><a href="https://twitter.com/post_status" target="_blank" rel="noreferrer noopener">Post Status</a> (Twitter)</li></ul>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<hr class="wp-block-separator logo is-style-default" />\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<h3 id="sponsor-gravity-forms"><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> Sponsor: Gravity Forms</h3>\n\n\n\n<p>Gravity Forms is a powerful form builder for WordPress and the #1 choice for businesses and web professionals across the globe. Its vast array of features, intuitive drag-and-drop form editor, and extensive ecosystem of add-ons, ensure customers can design beautiful, intelligent, and accessible forms for any project requirement.</p>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<hr class="wp-block-separator logo is-style-default" />\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<h2 id="h-transcript"><strong>Transcript</strong></h2>\n\n\n\n<p>Coming Soon</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Feb 2022 23:00: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: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: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:49:"BuddyPress: BuddyPress 10.1.0 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://buddypress.org/?p=323557";s:7:"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://buddypress.org/2022/02/buddypress-10-1-0-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1865:"<p>Immediately available is&nbsp;<a href="https://downloads.wordpress.org/plugin/buddypress.10.1.0.zip">BuddyPress 10.1.0</a>. This maintenance release fixes ten bugs. For details on the changes, please read the&nbsp;<a href="https://codex.buddypress.org/releases/version-10-1-0/">10.1.0 release notes</a>.</p>\n\n\n\n<p>Update to BuddyPress 10.1.0 today in your WordPress Dashboard, or by&nbsp;<a href="https://wordpress.org/plugins/buddypress/">downloading from the WordPress.org plugin repository</a>.</p>\n\n\n\n<h2 id="many-thanks-to-9-2-0-contributors">Many thanks to 10.1.0 contributors&nbsp;<span class="dashicons dashicons-heart"></span></h2>\n\n\n\n<p><a href="https://profiles.wordpress.org/muhittinsahilli">muhittinsahilli</a>, <a href="https://profiles.wordpress.org/oztaser">oztaser</a>, <a href="https://profiles.wordpress.org/r-a-y">r-a-y</a>, <a href="https://buddypress.trac.wordpress.org/query?status=!closed&reporter=niftythree">niftythree</a>, <a href="https://profiles.wordpress.org/vapvarun">vapvarun</a>, <a href="https://buddypress.trac.wordpress.org/query?status=!closed&owner=dcavins">dcavins</a>, <a href="https://profiles.wordpress.org/sx1001/">sx1001</a>, <a href="https://profiles.wordpress.org/espellcaste">espellcaste</a>,&nbsp;<a href="https://profiles.wordpress.org/dd32">dd32</a>&nbsp;&amp;&nbsp;<a href="https://profiles.wordpress.org/imath/">imath</a>.</p>\n\n\n\n<p>Special mentions to <a href="https://buddypress.trac.wordpress.org/query?status=!closed&reporter=niftythree">niftythree</a> who reported 5 bugs <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f60d.png" alt="😍" class="wp-smiley" /> &nbsp;and to <a href="https://profiles.wordpress.org/oztaser">oztaser</a> who contributed with 5 patches to fix 40% of the bugs <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f4aa.png" alt="💪" class="wp-smiley" />.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Feb 2022 21: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:23;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:82:"WordCamp Central: WooCommerce sponsors WordPress community events across the globe";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:39:"https://central.wordcamp.org/?p=3146014";s:7:"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:112:"https://central.wordcamp.org/news/2022/02/22/woocommerce-sponsors-wordpress-community-events-across-the-globe-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1876:"<p><span>We’d like to thank </span><strong><span><a href="https://www.woothemes.com/woocommerce/">WooCommerce</a></span></strong><span> for their continuing support by participating in the </span><strong><span><a href="https://central.wordcamp.org/sponsor-multiple-wordcamps/">WordPress global sponsorship program</a></span></strong><span>! By generously sponsoring at the Gold level across the globe, WooCommerce helps make local community events (like WordPress meetup groups and WordCamps) better for WordPress enthusiasts and easier to organize for our wonderful group of hardworking volunteers.</span></p>\n<p><a href="https://central.wordcamp.org/files/2022/02/Copy-of-woocommerce-logo-color-black@2x.png"><img /></a></p>\n<p><span>WooCommerce is a customizable, open-source eCommerce platform built on WordPress. </span></p>\n<p><span>Sell anything online with the flexibility and freedom of the world’s most popular CMS.</span></p>\n<ul>\n<li><strong><span><a href="https://wordpress.org/plugins/woocommerce/stats/">4+ million active installations</a></span></strong></li>\n<li><span>55+ million downloads</span></li>\n<li><span>450+ extensions to add and extend functionality</span></li>\n</ul>\n<p><span>Whether you’re selling a few handcrafted items to a niche market, taking an existing business online, or going global with an enterprise-level eCommerce business WooCommerce gets you set up and selling fast, scaling securely as you grow.</span></p>\n<p><span>Your content is forever yours and customizable down to the button color. Plus you’re joining a supportive, </span><strong><span><a href="https://woocommerce.com/meetups/">global community</a></span></strong><span> of developers and store owners.</span></p>\n<p><span>Developed and supported by a distributed team, WooCommerce is powered by Automattic, the creators of Jetpack and WordPress.com.</span></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Feb 2022 16:00: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:6:"Isotta";s: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:55:"WordPress.org blog: WordPress 5.9.1 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=12266";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2022/02/wordpress-5-9-1-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7742:"<p>WordPress 5.9.1 is now available!</p>\n\n\n\n<p>This maintenance release features&nbsp;82 bug fixes in both Core and the block editor.</p>\n\n\n\n<p>WordPress 5.9.1 is a short-cycle maintenance release. The next major release will be version&nbsp;<a href="https://make.wordpress.org/core/6.0/">6.0</a>.</p>\n\n\n\n<p>You can <a href="https://wordpress.org/wordpress-5.9.1.zip">download WordPress 5.9.1 from WordPress.org</a>, or visit your Dashboard&nbsp;→ Updates and click &#8220;Update Now&#8221;.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<p>For more information, browse the <a href="https://make.wordpress.org/core/2022/02/16/wordpress-5-9-1-rc-1/">full list of both Trac and GitHub changes in the release candidate post</a>, or check out the&nbsp;<a href="https://wordpress.org/support/wordpress-version/version-5-9-1/">version 5.9.1 HelpHub documentation page</a>.</p>\n\n\n\n<h2 id="thanks-and-props">Thanks and props!</h2>\n\n\n\n<p>The 5.9.1 release was led by <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a> and <a href="https://profiles.wordpress.org/mamaduka/">George Mamadashvili</a>.</p>\n\n\n\n<p>Special props to <a href="https://profiles.wordpress.org/sergeybiryukov/" class="mention"><span class="mentions-prefix">@</span>sergeybiryukov</a> for running mission control.</p>\n\n\n\n<p>Thank you to everyone who helped make WordPress 5.9.1 happen:</p>\n\n\n\n<p><a href="https://profiles.wordpress.org/aljullu/">Albert Juhé Lluveras</a>, <a href="https://profiles.wordpress.org/ajlende/">Alex Lende</a>, <a href="https://profiles.wordpress.org/alexstine/">alexstine</a>, <a href="https://profiles.wordpress.org/oandregal/">André</a>, <a href="https://profiles.wordpress.org/antonvlasenko/">Anton Vlasenko</a>, <a href="https://profiles.wordpress.org/aristath/">Ari Stathopoulos</a>, <a href="https://profiles.wordpress.org/madeinua/">ArteMa</a>, <a href="https://profiles.wordpress.org/scruffian/">Ben Dwyer</a>, <a href="https://profiles.wordpress.org/blogaid/">BlogAid</a>, <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a>, <a href="https://profiles.wordpress.org/critterverse/">Channing Ritter</a>, <a href="https://profiles.wordpress.org/chrisvanpatten/">Chris Van Patten</a>, <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a>, <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a>, <a href="https://profiles.wordpress.org/davidbinda/">David Biňovec</a>, <a href="https://profiles.wordpress.org/get_dave/">David Smith</a>, <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a>, <a href="https://profiles.wordpress.org/ocean90/">Dominik Schilling</a>, <a href="https://profiles.wordpress.org/eddystile/">Eddy</a>, <a href="https://profiles.wordpress.org/ellatrix/">Ella van Durpe</a>, <a href="https://profiles.wordpress.org/kebbet/">Erik</a>, <a href="https://profiles.wordpress.org/fabiankaegy/">Fabian Kägy</a>, <a href="https://profiles.wordpress.org/azouamauriac/">Flinim Asso</a>, <a href="https://profiles.wordpress.org/gadhiyaravi/">gadhiyaravi</a>, <a href="https://profiles.wordpress.org/revgeorge/">George Hotelling</a>, <a href="https://profiles.wordpress.org/mamaduka/">George Mamadashvili</a>, <a href="https://profiles.wordpress.org/glendaviesnz/">glendaviesnz</a>, <a href="https://profiles.wordpress.org/gziolo/">Greg Ziółkowski</a>, <a href="https://profiles.wordpress.org/ianatkins/">ianatkins</a>, <a href="https://profiles.wordpress.org/ianbelanger/">Ian Belanger</a>, <a href="https://profiles.wordpress.org/ironprogrammer/">ironprogrammer</a>, <a href="https://profiles.wordpress.org/itsamoreh/">itsamoreh</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a>, <a href="https://profiles.wordpress.org/jffng/">Jeff Ong</a>, <a href="https://profiles.wordpress.org/jeherve/">Jeremy Herve</a>, <a href="https://profiles.wordpress.org/joedolson/">Joe Dolson</a>, <a href="https://profiles.wordpress.org/joen/">Joen A.</a>, <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a>, <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a>, <a href="https://profiles.wordpress.org/jrf/">Juliette Reinders Folmer</a>, <a href="https://profiles.wordpress.org/kafleg/">KafleG</a>, <a href="https://profiles.wordpress.org/kapilpaul/">Kapil Paul</a>, <a href="https://profiles.wordpress.org/kjellr/">Kjell Reigstad</a>, <a href="https://profiles.wordpress.org/linux4me2/">linux4me2</a>, <a href="https://profiles.wordpress.org/pyrobd/">Lukman Nakib</a>, <a href="https://profiles.wordpress.org/manfcarlo/">manfcarlo</a>, <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/mgol/">mgol</a>, <a href="https://profiles.wordpress.org/nidhidhandhukiya/">nidhidhandhukiya</a>, <a href="https://profiles.wordpress.org/ntsekouras/">Nik Tsekouras</a>, <a href="https://profiles.wordpress.org/alshakero/">Omar Alshaker</a>, <a href="https://profiles.wordpress.org/pls78/">Paolo L. Scala</a>, <a href="https://profiles.wordpress.org/swissspidy/">Pascal Birchler</a>, <a href="https://profiles.wordpress.org/pbearne/">Paul Bearne</a>, <a href="https://profiles.wordpress.org/malinevskiy/">Pavlo</a>, <a href="https://profiles.wordpress.org/petaryoast/">Petar Ratković</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/walbo/">Petter Walbø Johnsgård</a>, <a href="https://profiles.wordpress.org/johnstonphilip/">Phil Johnston</a>, <a href="https://profiles.wordpress.org/boniu91/">Piotrek Boniu</a>, <a href="https://profiles.wordpress.org/ravipatel/">ravipatel</a>, <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a>, <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a>, <a href="https://profiles.wordpress.org/rolfsiebers/">Rolf Siebers</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/stacimc/">stacimc</a>, <a href="https://profiles.wordpress.org/sabernhardt/">Stephen Bernhardt</a>, <a href="https://profiles.wordpress.org/mahype/">Sven Wagener</a>, <a href="https://profiles.wordpress.org/staatic/">Team Staatic</a>, <a href="https://profiles.wordpress.org/tnolte/">Tim Nolte</a>, <a href="https://profiles.wordpress.org/hellofromtonya/">Tonya Mork</a>, <a href="https://profiles.wordpress.org/webcommsat/">webcommsat AbhaNonStopNewsUK</a>, <a href="https://profiles.wordpress.org/webmandesign/">WebMan Design | Oliver Juhas</a>, <a href="https://profiles.wordpress.org/antonynz/">wpcharged</a>, <a href="https://profiles.wordpress.org/wpsoul/">wpsoul</a>, <a href="https://profiles.wordpress.org/dolphingg/">Yunus Ertuğrul</a>, and <a href="https://profiles.wordpress.org/rafiahmedd/">Rafi Ahmed</a>.</p>\n\n\n\n<p>Thanks to <a href="https://profiles.wordpress.org/estelaris/" class="mention"><span class="mentions-prefix">@</span>estelaris</a>, <a href="https://profiles.wordpress.org/pbiron/" class="mention"><span class="mentions-prefix">@</span>pbiron</a>, <a href="https://profiles.wordpress.org/ironprogrammer/" class="mention"><span class="mentions-prefix">@</span>ironprogrammer</a>, <a href="https://profiles.wordpress.org/bph/" class="mention"><span class="mentions-prefix">@</span>bph</a>, <a href="https://profiles.wordpress.org/abhanonstopnewsuk/" class="mention"><span class="mentions-prefix">@</span>abhanonstopnewsuk</a> and <a href="https://profiles.wordpress.org/threadi/" class="mention"><span class="mentions-prefix">@</span>threadi</a> for their help to test the release package.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Feb 2022 15:49: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:9:"Jb Audras";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:106:"WPTavern: QuickPost Plugin Allows Users To Create New or Duplicate Posts from the WordPress Content Editor";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=130353";s:7:"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:117:"https://wptavern.com/quickpost-plugin-allows-users-to-create-new-or-duplicate-posts-from-the-wordpress-content-editor";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4397:"<p>There is not much I miss about the classic editor. It was dead to me when the block system became the new normal. However, there might be a feature or two that I miss.</p>\n\n\n\n<p><em>The biggest of those features?</em> The &#8220;Add New&#8221; button at the top of the post editor.</p>\n\n\n\n<img />&#8220;Add New&#8221; button in the classic editor.\n\n\n\n<p>So, when Aurooba Ahmed mentioned that she was building a plugin to address this very problem on Twitter, I took note, eagerly awaiting the day of its release. Losing the button for adding a new post was a user experience regression, and her <a href="https://wordpress.org/plugins/quickpost/">QuickPost plugin</a> rights one of the wrongs with the block editor that has long gone unfixed.</p>\n\n\n\n<p>This is particularly true for fullscreen users. They have no quick access to the Add New links available via the toolbar or admin menu. Neither are shown in fullscreen mode.</p>\n\n\n\n<p>The plugin works right out of the box. There are no settings to configure. Just install, activate, and look for the Add New button to appear when editing a post.</p>\n\n\n\n<img />Block editor with &#8220;Add New&#8221; button.\n\n\n\n<p>The button also comes with an extra option for duplicating posts. It is available by clicking the vertical ellipsis icon on the side of the button.</p>\n\n\n\n<p>Ahmed argues in her <a href="https://aurooba.com/quickpost/">announcement post</a> that the duplicate-post feature is a fundamental part of content publishing:</p>\n\n\n\n<blockquote class="wp-block-quote has-primary-font-family is-style-default has-lg-font-size"><p>This functionality is core to anything that provides a content creation experience (excluding social media). Can you imagine Microsoft Word without the &#8220;Save As..&#8221; feature, that essentially serves as a way to duplicate documents? Or the &#8220;Open a copy&#8221; feature they later introduced?</p></blockquote>\n\n\n\n<p>I agree. It has long been needed as a core feature and the active install numbers from <a href="https://wordpress.org/plugins/search/duplicate+post/">plugins that offer it</a> back it up.</p>\n\n\n\n<p>To copy a post, users need to only click the &#8220;Duplicate Post&#8221; button. The plugin will create the copy and transfer the user over to the editing screen for it:</p>\n\n\n\n<img />Duplicated post.\n\n\n\n<p>The plugin automatically copies the post data and metadata. It only changes the title of the duplicate post to &#8220;Copy of Post Title.&#8221; Ahmed noted in the announcement that she might add a feature for customizing this in the future.</p>\n\n\n\n<p>She also said she is thinking of other features to improve the plugin. The ideas include batch duplication, a new post keyboard shortcut, and more UI improvements.</p>\n\n\n\n<p>For my own workflow where I might be working on multiple pieces of content at once, QuickPost feels like it is mere inches away from perfection. One of the downsides of the plugin&#8217;s &#8220;Add New&#8221; button is that it is literally a <code>&lt;button></code> element. This means that users cannot right-click on it and open a new post editor in another browser tab/window. For that functionality, the button would need to be a link (<code>&lt;a></code>) element. This is also the difference between the plugin and the classic editor.</p>\n\n\n\n<p>QuickPost is also a quick answer for a more in-depth issue around navigating content. Ahmed recently <a href="https://github.com/WordPress/gutenberg/issues/38554">opened a ticket</a> for adding a sidebar while in fullscreen mode, which would house links to Posts, Add New Post, and Duplicate Post. The proposal would create a UI that could look like the following:</p>\n\n\n\n<img />Proposed UI (draft) for adding content navigation.\n\n\n\n<p>Do not expect this to land in WordPress any time soon. A <a href="https://github.com/WordPress/gutenberg/issues/23328">browse mode</a> for the site editor is on the 6.0 roadmap, but bringing such a navigation element to the content editor will have to wait.</p>\n\n\n\n<p>There is a ton of discussion to unpack in Ahmed&#8217;s ticket, and it is probably deserving of its own post here at the Tavern. For now, at least some users have access to much-needed features via the QuickPost plugin.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<blockquote class="wp-embedded-content"><a href="https://wordpress.org/plugins/quickpost/">QuickPost</a></blockquote>\n</div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 22 Feb 2022 00: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: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: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:62:"WPTavern: How to Build a vCard Website with a Video Background";s:7:"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=130318";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"https://wptavern.com/how-to-build-a-vcard-website-with-a-video-background";s: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:3027:"<img />\n\n\n\n<p>Today we are continuing on with our new <a href="https://wptavern.com/category/building-with-blocks">Building with Blocks</a> series, where we demonstrate some fun things you can create with blocks. </p>\n\n\n\n<p>In this tutorial I am going to show you how to build a simple vCard website with a video background in under five minutes. I wanted to build a website like this awhile back and searched for a block theme that would work but didn&#8217;t find anything that would instantly give me what I was looking for. I also searched the <a href="https://wordpress.org/patterns/">WordPress Pattern Directory</a> for a vCard style pattern and could not find one. Fortunately, this type of a site is easy to build in just a few minutes with a handful of blocks. </p>\n\n\n\n<p>I selected the free <a href="https://wordpress.org/themes/eksell/">Eksell theme</a> for this project, because it includes a <a href="https://andersnoren.se/themes/eksell/blank-canvas/">Blank Canvas Template</a> for pages that removes the menu, header, and footer. The only content that appears are the blocks you add to the page. Eksell is also a full-featured portfolio theme that you can grow into, if you decide to expand beyond a simple vCard website. </p>\n\n\n\n<p>The five-minute video below walks you through adding the theme, starting from one of the included patterns, and adding all the necessary blocks for the social icons and the video background.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n\n</div>\n\n\n\n<p>A few notes about specifics: I found the video examples used in this tutorial on <a href="https://pixabay.com/videos/waves-ocean-sea-beach-byron-bay-70796/">Pixabay</a>, which has a nice selection of short videos that lend themselves well to looping in the background of a website. </p>\n\n\n\n<p>If you have some extra white space at the bottom after adding the video to the cover block, you can set the minimum height. Go to your cover block, click Settings, and scroll down to Dimensions where you can adjust the minimum height of the cover.</p>\n\n\n\n<p>Here is the CSS for the border around the circular profile image. You can add this to the Additional CSS section of the Customizer:</p>\n\n\n\n<pre class="wp-block-code"><code>.wp-block-image.is-style-rounded img {\n    border-style: solid;\n    border-color: #FFFFFF;\n    border-width: 10px;\n	\n}</code></pre>\n\n\n\n<p>If you plan to keep the website simple in vCard format, you will want to assign the page you created as the Homepage. This can be done in the Customizer under the Homepage Settings panel. </p>\n\n\n\n<p>As an alternative to using Eksell, if your site is on WordPress.com, you can achieve a similar result by using Automattic&#8217;s Blank Canvas theme and adding and arranging the blocks individually.</p>\n\n\n\n<p>This is a fast way to customize a site after a new domain purchase. Choose any combination of blocks to create a nice placeholder until you decide to add more to the website. If you end up building this, drop a link in the comments so we can check it out. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 21 Feb 2022 18:14: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: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:89:"WordCamp Central: Weglot joins the WordPress global community sponsorship program in 2022";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:39:"https://central.wordcamp.org/?p=3145890";s:7:"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:117:"https://central.wordcamp.org/news/2022/02/21/weglot-joins-the-wordpress-global-community-sponsorship-program-in-2022/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1805:"<p><span>We couldn’t be happier to welcome </span><strong><span><a href="https://weglot.com/integrations/wordpress-translation-plugin/">Weglot</a></span></strong><span> to the </span><strong><span><a href="https://central.wordcamp.org/sponsor-multiple-wordcamps/">WordPress global community sponsorship program</a></span></strong><span> in 2022! They’re sponsoring at the Gold level, supporting official WordPress community events across the globe.</span></p>\n<p><a href="https://central.wordcamp.org/files/2022/01/Weglot-CPT-logo.png"><img /></a></p>\n<p><strong><span><a href="https://weglot.com/integrations/wordpress-translation-plugin/">Weglot</a></span></strong><span> is a WordPress multilingual plugin to translate and display your website in multiple languages. It provides a fast first layer of automated translation which you can easily edit yourself or by adding teammates, or collaborate with pro-translators through the Weglot dashboard. </span></p>\n<p><span>Trusted by more than </span><b>50,000 website</b><span> owners and developers and with a </span><b>5-star rating</b><span> on the WordPress directory (1000+ reviews) &#8211; you can have a multilingual website up and running in minutes. </span></p>\n<p><span>Key benefits include: </span></p>\n<ul>\n<li><span>Simple and quick set-up &#8211; </span><span>Multilingual SEO best practices (translated URLs &amp; metadata)</span></li>\n<li><span>Compatibility with any Themes and Plugins (incl. WooCommerce)</span></li>\n<li><span>Automatic and human translations</span></li>\n<li><span>A unique dashboard with an &#8216;in context editor&#8217;, easily edit translations &amp; invite teammates to collaborate on projects</span></li>\n<li><span>Expert support: a fully dedicated technical support team at your disposal</span></li>\n</ul>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 21 Feb 2022 13:46:13 +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:6:"Isotta";s: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:78:"WordPress.org blog: WP Briefing: Episode 25: Five Cents on Five for the Future";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/news/?post_type=podcast&p=12288";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"https://wordpress.org/news/2022/02/episode-25-five-cents-on-five-for-the-future/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10284:"<p>In this twenty-fifth episode of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy discusses future-proofing the WordPress project with the Five for the Future pledge. </p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href="mailto:wpbriefing@wordpress.org">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2 id="credits">Credits</h2>\n\n\n\n<ul><li>Editor:&nbsp;<a href="https://profiles.wordpress.org/dustinhartzler/">Dustin Hartzler</a></li><li>Logo:&nbsp;<a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a></li><li>Production:&nbsp;<a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a> &amp; <a href="https://profiles.wordpress.org/santanainniss/">Santana Inniss</a></li><li>Song: Fearless First by Kevin MacLeod</li></ul>\n\n\n\n<h2 id="references">References</h2>\n\n\n\n<ul><li><a href="https://ma.tt/2014/09/five-for-the-future/">Five for the Future</a>, on ma.tt circa 2014</li><li><a href="https://www.cambridge.org/core/books/governing-the-commons/A8BB63BC4A1433A50A3FB92EDBBB97D5">Governing the Commons</a>, Elinor Ostrom</li><li><a href="https://wordpress.org/five-for-the-future/files/2022/01/WP-Sponsored-Contributor-Team-White-Paper-Google-Docs.pdf">Five for the Future White Paper</a></li><li><a href="https://make.wordpress.org/core/2022/02/16/wordpress-6-0-planning-roundup/">6.0 Planning Roundup</a></li><li><a href="https://learn.wordpress.org/course/simple-site-design-with-full-site-editing/">Part I: Full Site Editing Course</a></li><li><a href="https://learn.wordpress.org/course/part-2-personalized-site-design-with-full-site-editing-and-theme-blocks/">Part II: Full Site Editing Course</a></li><li><a href="https://learn.wordpress.org/course/part-3-advanced-site-design-with-full-site-editing-site-editor-templates-and-template-parts/">Part III: Full Site Eiditing Course</a></li></ul>\n\n\n\n<h2 id="transcript">Transcript</h2>\n\n\n\n<span id="more-12288"></span>\n\n\n\n<p>Episode 25</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:00:00]&nbsp;</strong></p>\n\n\n\n<p>Hello everyone, and welcome to the WordPress Briefing. The podcast where you can catch quick explanations of the ideas behind the WordPress open source project. Some insight into the community that supports it and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy &#8211; here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:00:42]&nbsp;</strong></p>\n\n\n\n<p>I have a non-mailbag mailbag question that I would like to answer for y&#8217;all today. Non-mailbag because no one actually emailed me about it and mailbag because Twitter is basically like a giant mailbag. And I do get a lot of DMS about this particular topic. If you want to send something to my actual WP Briefing mailbag, you can send it to <a href="mailto:wpbriefing@worpress.org">wpbriefing@worpress.org</a>.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:01:06]&nbsp;</strong></p>\n\n\n\n<p>But the question that I frequently get asked in my DMS on Twitter is: what is Five for the Future? It&#8217;s not always that tidy the question, but that still is the question we&#8217;re answering today. So if you take a casual survey of active contributors to the WordPress project, the high-level answer that you&#8217;re likely to get to that question is “a way to remind people to give back to the project.” Or, if you run in more business-y circles, you might hear that it is an initiative that encourages companies to give back 5% of their resources.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:01:40]&nbsp;</strong></p>\n\n\n\n<p>And both of those answers are true. So a quick mini-history lesson; the original concept of Five for the Future came from Matt Mullenweg in 2014. There&#8217;s a lovely blog post on it that I will link in the notes below, but it was essentially a call to any companies experiencing success with WordPress to contribute back to the project and make sure that the project was a success.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:02:07]&nbsp;</strong></p>\n\n\n\n<p>The initial program then included outreach recognition, et cetera, proposed in 2017 by <a href="https://wordpress.org/support/users/liljimmi/">Tracy Levesque</a> and <a href="https://wordpress.org/support/users/iandunn/">Ian Dunn</a>. Then that was defined and formalized with the help of the WordPress community in 2018. And then, in 2019, we had our first trial run with entire dedicated teams sponsored by companies inside the WordPress ecosystem.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:02:36]&nbsp;</strong></p>\n\n\n\n<p>So that&#8217;s the mini-history lesson chronology of this program. The intentions that informed the work of building the program in 2017 have become a bit lost to the ages. So I&#8217;m here to share it with you. The basic heart and soul of the Five for the Future program is to make sure that there is a way to refresh the commons of the WordPress community and ecosystem.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:03:00]&nbsp;</strong></p>\n\n\n\n<p>And as a result, ensure that the common resources of WordPress are available long after we have stopped being available to care for them. If you are familiar with the concept of the tragedy of the commons, Five for the Future was created to help avoid that tragedy. There were two original goals for formalizing the program.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:03:22]&nbsp;</strong></p>\n\n\n\n<p>The first one was to acknowledge companies that participated in Five for the Future by sponsoring contributors to work on the WordPress project. And the second was to motivate more companies to sponsor more volunteers. Either by hiring them and paying them to contribute or by assigning their existing employees to contribute to the WordPress project.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:03:46]&nbsp;</strong></p>\n\n\n\n<p>Of course, it&#8217;s hard to quantify participation and hard to qualify what should be seen as an impactful contribution, which is why when the program was originally created, it was in partnership with team reps and community members who were active at the time. There are many posts around that discuss the next steps for this program.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:04:07]&nbsp;</strong></p>\n\n\n\n<p>And as I&#8217;m looking through them, the next steps revolve around some of the hardest and most important questions that we have to answer as a project and as stewards of open source. Those questions are things like:</p>\n\n\n\n<ul><li> How do we remain true to these gloriously subversive values of WordPress and open source while also finding a way to thoughtfully secure our organization&#8217;s future?</li><li>Does contributing without the expectation of reciprocity hold up when we are looking at how to acknowledge contributors who sustain us?</li></ul>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:04:40]&nbsp;</strong></p>\n\n\n\n<p>And if you&#8217;re familiar with Elinor Ostrom&#8217;s award-winning work, Governing the Commons, you may also be wondering how this particular program aligns with her eight principles designed to sustain organizations like ours.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:04:57]&nbsp;</strong></p>\n\n\n\n<p>As an aside to that last question, this particular program does not have all eight principles accounted for, but among WordPress&#8217;s many programs, we do account for most of them. Although imperfectly, as is the way with human beings, that&#8217;s probably a whole episode unto itself, I did want to quickly answer that particular question.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:05:16]&nbsp;</strong></p>\n\n\n\n<p>So to get back to my non-mailbag, mailbag question, if I had to tell you in the span of an elevator ride what Five for the Future was, this would be my answer. <strong>It is a v1 program with a dual goal of boldly declaring the need to refresh the shared resources of WordPress and offering the ways and means for communities and individuals alike to participate in refreshing those resources</strong>.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:05:45]&nbsp;</strong></p>\n\n\n\n<p>If you want to learn more about the Five for the Future initiative, you can check out wordpress.org/5. Like literally just the number five. Or, if you want to learn more about the program that has grown from the Five for the Future initiative, you can check out the white paper that&#8217;s linked in the notes below.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:06:11]&nbsp;</strong></p>\n\n\n\n<p>And that brings us now to our small list of big things. Number one on my small list, the planning post for WordPress 6.0 is out. I&#8217;ve included a link in my massive list of links below. But it includes our best guess at timing, features that we intend to include, and a call for volunteers as well. So if you are looking for ways to give back, that is a clear and immediate option.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:06:38]&nbsp;</strong></p>\n\n\n\n<p>The second thing on the list is if you are a team rep, don&#8217;t forget that we have daylight saving time ending and starting depending on your hemisphere within the month. If you move meetings, if you&#8217;re in a team that moves your meetings, discuss it now so that folks have time to adjust their calendars.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:06:55]&nbsp;</strong></p>\n\n\n\n<p>And the third thing on my small list of big things is that there&#8217;s a suite of Full Site Editing courses that are now available on learn.wordpress.org. I will add that to my giant list of links below, but I encourage you to wander on over and see what all the fuss is about. I think the courses are excellent. They&#8217;re great for folks who don&#8217;t quite know what Full Site Editing is yet, but then also they give you a few intermediate tips and tricks as you&#8217;re getting your legs underneath you.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy [00:07:27]&nbsp;</strong></p>\n\n\n\n<p>So, that my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host, Josepha Haden Chomphosy. I&#8217;ll see you again in a couple of weeks.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 21 Feb 2022 12:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:71:"WPTavern: Unearthing Hidden Treasures in the Wabi WordPress Block Theme";s:7:"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=130278";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:82:"https://wptavern.com/unearthing-hidden-treasures-in-the-wabi-wordpress-block-theme";s: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:5436:"<p>After being involved in web design for almost 19 years now, there are grinding days where nothing feels fresh. However, there are also moments where you look at another web developer&#8217;s approach to problems and feel like there is a whole world of possibilities that you have yet to step into. And, it is rarely something complicated. The best developers make it look simple, and <a href="https://richtabor.com/wabi/">Rich Tabor&#8217;s Wabi</a> is dotted with those little tricks that make poring over WordPress block theme code feel exciting again.</p>\n\n\n\n<p>Earlier today, the WordPress theme directory hit 50 block themes. However, I was more interested in what was waiting in the review queue. Tabor had <a href="https://themes.trac.wordpress.org/ticket/113267">submitted his project</a> less than 24 hours before, but I spun it up anyway. I had to see what one of the more prolific <a href="https://richtabor.com/category/themes/">writers on block theme development</a> had built. While he had contributed to GoDaddy&#8217;s Go theme before taking a job with Extendify, this was the first theme submission from his personal account.</p>\n\n\n\n<p>I love diving into themes where I can learn something. That is the best way that I can describe Wabi.</p>\n\n\n\n<p>It is primarily geared toward bloggers and writers. It features the type of design those who want nothing to overpower their content would appreciate. However, it has enough whimsy thrown in to not be an entirely boring black-and-white affair.</p>\n\n\n\n<p>One of Wabi&#8217;s unique features is its per-post accent color selector. The control is located under the &#8220;Status &amp; Visibility&#8221; panel in the post sidebar and allows users to select from the theme&#8217;s color palette. This accent is primarily used for the background behind the header and post title area. However, it is sprinkled around various other elements and blocks.</p>\n\n\n\n<img />Selecting a post accent color.\n\n\n\n<p>I have yet to see a block theme utilize custom post metadata. This is likely because few developers know how to create the components in the post sidebar after relying on the old meta box system over the years. The theme&#8217;s accent-related JavaScript is structured well enough that other themers can pick it apart and build similar features in their designs. If this has been a holdup in block theme development for anyone, it is well worth doing a deep dive into the mere 117 lines of JavaScript used to make this feature.</p>\n\n\n\n<p>A nice touch Tabor added to the global styles&#8217; color palette was a custom background for the accent color. Instead of showing a solid-colored circle, it is a conic gradient of all the available variations.</p>\n\n\n\n<img />Accent color wheel in the palette.\n\n\n\n<p>This detail might seem insignificant, but it is a visual cue that this particular color is different than the others. Users can still edit it to set the default, but they can also override it on a per-post basis.</p>\n\n\n\n<p>In a post on <a href="https://wptavern.com/building-a-scotch-tape-image-block-style">creating a custom block style</a> earlier this week, I said the feature was underutilized when building WordPress themes. Many were not pushing it forward with unique design variations for users. Wabi includes a little over a dozen custom styles, but I have not seen any like those it offers for Image and Video blocks.</p>\n\n\n\n<p>The theme registers Bottom Right, Bottom Left, and Center styles. Each changes the position of the image within its <code>&lt;figure&gt;</code> container as shown in the following screenshot:</p>\n\n\n\n<img />Image block styles and accent color.\n\n\n\n<p>The styles are not particularly complex. They are simple twists to offer some visual <em>oomph</em> that can sometimes lack in text-heavy blog posts. And, they are unique, something you would not be able to build with the core design tools. To top off the feature, the background color behind the media uses the theme&#8217;s accent color.</p>\n\n\n\n<p>That is the type of creative thinking around block styles that I expect from theme authors. It is not that I think others are incapable of it, but building projects with blocks sometimes requires approaching design in new ways.</p>\n\n\n\n<p>Wabi also supports <a href="https://wptavern.com/global-style-variations-skins-for-themes-have-landed-in-gutenberg">global style variations</a>, an upcoming feature expected to land in WordPress 6.0. To see it in action, users must activate the Gutenberg plugin.</p>\n\n\n\n<img />Dark style variation.\n\n\n\n<p>The theme packages four style variations, including the default. Each of them offers alternative color palettes, including a dark scheme.</p>\n\n\n\n<p>Wabi also includes 15 patterns. Most of them are variations for headers, footers, and post loops, but in the spirit of keeping things unique, there are style-guide patterns too.</p>\n\n\n\n<img />Wabi style guide patterns.\n\n\n\n<p>Users can look through the theme&#8217;s color palette and typography by inserting them into a post. They may not be needed for use on the front end for most sites, but they offer a quick glance at the theme&#8217;s overall style.</p>\n\n\n\n<p>The theme works well enough for blogging. Post content is readable with it, and it makes generous use of white space. It will not get any complaints from me in that department.</p>\n\n\n\n<p>I only wonder what other little treasures Wabi holds that I have yet to discover.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 19 Feb 2022 03:15:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:108:"WPTavern: UpdraftPlus 1.22.3 Patches Severe Vulnerability Through Forced Security Update from WordPress.org";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=130267";s:7:"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:118:"https://wptavern.com/updraftplus-1-22-3-patches-severe-vulnerability-through-forced-security-update-from-wordpress-org";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2261:"<p><a href="https://wordpress.org/plugins/updraftplus/">UpdraftPlus</a>, a plugin that allows users to backup to various cloud providers, has patched a severe security vulnerability that would allow logged-in users to download a site’s latest backups. The patched version (1.22.3)&nbsp;was sent out via a forced auto-update, a measure reserved for severe vulnerabilities that affect a large number of users. UpdraftPlus is active on more than 3 million WordPress sites.</p>\n\n\n\n<p>The vulnerability was <a href="https://jetpack.com/2022/02/17/severe-vulnerability-fixed-in-updraftplus-1-22-3/">discovered</a> by Jetpack Scan&nbsp;Security researcher Marc Montpas during an internal audit. UpdraftPlus explained the vulnerability to users in an <a href="https://updraftplus.com/updraftplus-security-release-1-22-3-2-22-3/">advisory</a> after the update went out: </p>\n\n\n\n<blockquote class="wp-block-quote"><p>This defect allows any logged-in user on a WordPress installation with UpdraftPlus active to exercise the privilege of downloading an existing backup, a privilege which should have been restricted to administrative users only. This was possible because of a missing permissions check on code related to checking current backup status. This allowed the obtaining of an internal identifier which was otherwise unknown, and could then be used to pass a check upon permission to download.</p></blockquote>\n\n\n\n<p>The issue affects both the paid and free versions of the plugin. A fix was pushed to paid customers within an hour of receiving the report. Every version of the free plugin between 1.16.7 and 1.22.3 is vulnerable. UpdraftPlus claims the majority of sites have been updated. WordPress.org stats show that ~35% of Updraft users have not updated to the latest, which leaves more than a million installations still vulnerable.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>So far there are no confirmed reports of exploits. For more details on the vulnerability, check out Montpas&#8217; <a href="https://jetpack.com/2022/02/17/severe-vulnerability-fixed-in-updraftplus-1-22-3/">report</a> on the Jetpack website. UpdraftPlus users are encouraged to check their websites to ensure the plugin is running on the latest, patched version. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Feb 2022 22:14:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:34:"WPTavern: Piklist Is Shutting Down";s:7:"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=130185";s:7:"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://wptavern.com/piklist-is-shutting-down";s: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:2696:"<p><a href="https://github.com/piklist/piklist">Piklist</a>, a development framework that helped people build things faster with WordPress, is shutting down. Its creators, Steve Bruner and Kevin Miller, launched the framework on June 12, 2012, at WordCampNYC. Over the next nine years it gained a devoted following.</p>\n\n\n\n<p>The framework was used by developers to speed up tasks such as creating fields for settings pages, registering custom post types and custom taxonomies, and adding post-to-post relationships. </p>\n\n\n\n<p>This week Piklist&#8217;s creators announced  that the plugin will no longer be updated at WordPress.org, and the website, support forum, and documentation have been archived on Github pages. With competing obligations, they were never able to properly monetize the framework:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>We released 92 versions, making it more stable and secure, but we never had time to take it to the next level.</p><p>We&#8217;re partners in Piklist, but we have our own separate WordPress development shops and use Piklist with our clients. Every day, we worked on improving it, but sadly life just got in the way. We both have families, and our client work took precedence over making a business out of Piklist.</p></blockquote>\n\n\n\n<p>After WordPress 5.0 introduced Gutenberg, the goal for the next major version of Piklist (2.0) was to allow it to be used with or without Gutenberg or the Classic Editor so that users could move forward without any issues. The team had been <a href="https://web.archive.org/web/20210414022032/https://piklist.com/2018/12/05/piklist-and-gutenberg/">working on it since 2018</a> but were not able to resolve all the issues. </p>\n\n\n\n<p>&#8220;The block editor definitely increased the delays in getting out another major version, but we also saw a lot of opportunity there,&#8221; Bruner told the Tavern. </p>\n\n\n\n<p>&#8220;Letting go of the project was tough. Piklist has a dedicated user base that stuck with us all these years. But we just couldn’t get to a 2.0, which wasn’t fair to our users, so we decided to shut it down instead of dragging it out.&#8221;  Bruner emphasized how much his team loved their users and how proud they were of the support they provided over the past nine years.</p>\n\n\n\n<p>&#8220;Not only did we educate users on how to use Piklist, we educated them on how WordPress worked,&#8221; he said. &#8220;Though the plugin is no longer available, users’ data is still safely stored in their database. Piklist did things the WordPress way and data was stored normally. Any plugin or library that can pull standard metadata, can be used to access the data Piklist saved.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Feb 2022 19:23:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:128:"WPTavern: Gutenberg 12.6 Enhances Transforming Blocks, Adds Read More and Post Author Bio Blocks, and Enables Social Icon Labels";s:7:"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=130153";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:137:"https://wptavern.com/gutenberg-12-6-enhances-transforming-blocks-adds-read-more-and-post-author-bio-blocks-and-enables-social-icon-labels";s: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:10200:"<p>Gutenberg 12.6 landed in the WordPress plugin directory yesterday. The update includes several transform-related enhancements and new Read More and Post Author Biography blocks. Users can now also show visible labels via the Social Icons block.</p>\n\n\n\n<p>Nothing seems to be broken with this release, which is always welcome. Gutenberg has not fundamentally wrecked something I relied on in a long while. There were a few growing pains, but the software has become more stable in the past year. I just wanted to add a note to commend the people working on it every day.</p>\n\n\n\n<p>As usual, I have a few nit-picks, but this looks like yet another solid release overall.</p>\n\n\n\n<h2 id="transforming-blocks">Transforming Blocks</h2>\n\n\n\n<img />Transforming a Tag Cloud to Categories block.\n\n\n\n<p>Developers went <em>all in</em> on block transforms in Gutenberg 12.6. The following blocks now support switching between one another:</p>\n\n\n\n<ul><li><a href="https://github.com/WordPress/gutenberg/pull/38324">Calendar <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2194.png" alt="↔" class="wp-smiley" /> Archives</a></li><li><a href="https://github.com/WordPress/gutenberg/pull/38295">Code <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2194.png" alt="↔" class="wp-smiley" /> Paragraph</a></li><li><a href="https://github.com/WordPress/gutenberg/pull/38566">Tag Cloud <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2194.png" alt="↔" class="wp-smiley" /> Categories</a></li><li><a href="https://github.com/WordPress/gutenberg/pull/36202">Group <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2194.png" alt="↔" class="wp-smiley" /> Row</a> (via the Variation control)</li></ul>\n\n\n\n<p>A new mechanism for <a href="https://github.com/WordPress/gutenberg/pull/37596">retaining styles during transforms</a> also landed in this release. It currently supports font size and color options. For example, users can switch between a Heading and Paragraph block, a run-of-the-mill use case, without losing those specific customizations. However, other settings are lost, even when shared across blocks. <em>There is not much I would not give to retain text alignment in this scenario.</em></p>\n\n\n\n<p>Anchors on the Heading block are <a href="https://github.com/WordPress/gutenberg/pull/38604">omitted when transforming</a> to a Paragraph in this release. The reason for this change was that WordPress auto-generates them. However, manually-added anchors are also removed.</p>\n\n\n\n<p>When transforming a Gallery to an Image block, the link destination, link target, and image size settings were previously lost. A new patch <a href="https://github.com/WordPress/gutenberg/pull/38642">adds those missing attributes</a>.</p>\n\n\n\n<h2 id="social-icon-labels">Social Icon Labels</h2>\n\n\n\n<img />Enabling Social Icon text labels.\n\n\n\n<p>If there is one thing that I am particularly ecstatic about with the Gutenberg 12.6 release, it is the <a href="https://github.com/WordPress/gutenberg/pull/38152">option to show text labels</a> via the Social Icons block. Previously, these were only displayed for screen readers. However, users can now toggle them on for everyone.</p>\n\n\n\n<p>This addition can open a ton of design variations for the block. Of course, I have already put my own spin on it with a hand-drawn border design, as shown in the above screenshot.</p>\n\n\n\n<p>WP Tavern actually played a small role in making this feature happen. When discussing a similar control with Nick Diego in his <a href="https://wptavern.com/nick-diego-forks-core-wordpress-block-creates-social-sharing-plugin">Social Sharing block</a>, I mentioned an open ticket for the core Social Icons block. It was not long before Diego had a patch ready, and now it is in Gutenberg.</p>\n\n\n\n<h2 id="color-panel-uses-tools-panel-component">Color Panel Uses Tools Panel Component</h2>\n\n\n\n<img />Color, typography, and border options all using the Tools Panel component.\n\n\n\n<p>The latest update switches block <a href="https://github.com/WordPress/gutenberg/pull/38511">color options to the Tools Panel component</a>. In most scenarios, the text and background colors are shown with the link color available through the &#8220;view options&#8221; dropdown (ellipsis button).</p>\n\n\n\n<p>To create a more unified and clean UI, it seems we have now added more clutter for several blocks. As shown in the screenshot above for the Pullquote block, the color, typography, and border panels are all permanently open. The Group block is even heavier with its addition of a dimensions section. Users have no way to hide them or the default controls.</p>\n\n\n\n<p>When the Tools Panel component was first introduced, it had a decluttering effect because it meant that some controls were tucked away. However, now that more panels are using it, that minuscule real estate in the block options sidebar has disappeared. Expect to scroll through several form fields to find just the right setting.</p>\n\n\n\n<p>Can we make them collapsible again? Or, better yet, can we have a combination of tabs and the Tools Panel component?</p>\n\n\n\n<h2 id="post-author-biography-block">Post Author Biography Block</h2>\n\n\n\n<img />Post author biography section.\n\n\n\n<p>A <a href="https://github.com/WordPress/gutenberg/pull/38269">Post Author Biography block</a> landed in Gutenberg 12.6. Its purpose is to display a user&#8217;s &#8220;biographical info,&#8221; which can be set via their user profile page in the admin. It covers most of the base design options but is missing border support.</p>\n\n\n\n<p>It is a solid start, but there is still one looming issue. It does not run <code>wpautop()</code> over the output. This means that the content is not wrapped in a <code>&lt;p&gt;</code> tag. Because of this, it also does not respect double-line breaks entered via the user-editing screen. WordPress has never had a standard function for outputting and formatting the user bio, allowing theme authors to handle it. However, some users may expect their custom formatting to work.</p>\n\n\n\n<p>We are inching closer to a <a href="https://github.com/WordPress/gutenberg/issues/35596">complete set of author-related blocks</a>. WordPress initially shipped a Post Author block that did a little bit of everything. Because of this, it made it next to impossible to consistently use for post bylines or other single-line metadata areas in themes. It also limited the design range of &#8220;about the author&#8221; sections often shown at the end of a post.</p>\n\n\n\n<p>We must now wait for the <a href="https://github.com/WordPress/gutenberg/pull/38265">Post Author Avatar block</a> to round out the set.</p>\n\n\n\n<h2 id="read-more-block-added">Read More Block Added</h2>\n\n\n\n<img />Read More block added inside a Query Loop / Post Template.\n\n\n\n<p>Gutenberg 12.6 adds a dedicated <a href="https://github.com/WordPress/gutenberg/pull/37649">Read More block</a> for theme authors to work into their Query Loop designs. It is merely an HTML permalink to the post. This is separate from the link output by the Post Excerpt block. Unfortunately, it has multiple issues and needs more testing before practical use.</p>\n\n\n\n<p>Users can add a background color to it but no text color. This makes it easy to create unreadable text. I was able to work around this by putting it in a Group block and changing the link color from there. </p>\n\n\n\n<p>It supports most border options, but the style control is missing. It also does not have a block-level HTML wrapper, so there is no way to align it horizontally without wrapping it in another block.</p>\n\n\n\n<p>This is an odd case. I am not sure if there are any other inline HTML elements (technically, it is set as a block element via CSS) for any top-level blocks elsewhere in WordPress.</p>\n\n\n\n<p>The other issue is the potential for two &#8220;read more&#8221; links. One via its dedicated block and the other through the Post Excerpt block. There is a draft patch to <a href="https://github.com/WordPress/gutenberg/pull/38662">toggle the link</a> for the latter.</p>\n\n\n\n<h2 id="responsive-handling-for-classic-images">Responsive Handling for Classic Images</h2>\n\n\n\n<img />Block images vs. classic images.\n\n\n\n<p>For posts written in the classic editor with large images, the media would blow outside the content area when using a block theme. Gutenberg <a href="https://github.com/WordPress/gutenberg/pull/38399">decoupled its responsive image handling</a> from the core Image block as a fix. This change is marked to be backported to a minor WordPress release, so users should not have to wait for WordPress 6.0.</p>\n\n\n\n<p>While this provides a fix for images, it does not address the issue of block themes not handling classic content or styling simple HTML. As an example from our site, I recently added a <code>&lt;table&gt;</code> element because the core Table block lacks some features. Since this was custom HTML, none of the block&#8217;s CSS was loaded, leaving it essentially unstyled. The same issue exists for classic content.</p>\n\n\n\n<p>One issue at play here is that WordPress is pushing CSS styles at the block level via <code>theme.json</code>. However, it only allows styling a handful of HTML elements, such as links and headings. This type of component-based design works well when everything is wrapped into a component (i.e., block).</p>\n\n\n\n<p>It makes more sense to style the underlying HTML elements than their representative blocks. That way, it is a shared style across any blocks that use the element, including third-party plugins.</p>\n\n\n\n<h2 id="large-quote-style-removed">Large Quote Style Removed</h2>\n\n\n\n<p>Finally, someone <a href="https://github.com/WordPress/gutenberg/pull/37580">removed the &#8220;large&#8221; Quote style</a>. It has been unnecessary since adding a font-size control for the block.</p>\n\n\n\n<p>I have made a point, several times at least, that WordPress should avoid shipping custom block styles of its own. In most cases, this is best left in the capable hands of theme authors. At the very least, new block styles should be avoided until the design tools are more well-rounded. Deprecating block styles creates legacy CSS baggage loaded with every WordPress site.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Feb 2022 04:00:20 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:42:"WPTavern: WordPress News Gets a New Design";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=130189";s:7:"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://wptavern.com/wordpress-news-gets-a-new-design";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2980:"<img />\n\n\n\n<p><a href="https://wordpress.org/news/">WordPress.org&#8217;s News</a> section is sporting a new design with a bold color scheme and updated typography. The design was created by Automattic-sponsored contributor, <a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a>, who unveiled earlier versions of the update in June 2021.</p>\n\n\n\n<p>Fialho selected <a href="https://fonts.google.com/specimen/Inter">Inter</a>, an open source font, for paragraphs and functional text, and <a href="https://fonts.google.com/specimen/EB+Garamond?query=eb+g">EB Garamond</a> for headings.</p>\n\n\n\n<p>As design trends change on the web, colors come in and out of fashion. WordPress appears to be moving away from its signature dusty blue color, which Fialho has scrapped in favor of a blue that commands your attention. The color reminds me of <a href="https://hyperallergic.com/615971/meet-yinmn-the-first-new-shade-of-blue-in-two-centuries/">YInMn</a>, the first inorganic blue pigment invented in 200 years, which was recently approved for commercial use. The vibrant hue and new typefaces work together to create a modern, opinionated design that is more befitting world-class publishing software.</p>\n\n\n\n<p>&#8220;The new design leans on the aesthetics of jazz, intrinsically connected to WordPress and which ultimately translates its uniqueness, historic significance and future potential,&#8221; Automattic-sponsored designer Kelly Hoffman said. </p>\n\n\n\n<p>&#8220;Among other improvements, the new design leaves more space for content and includes new typefaces for better readability. It also uses a color palette intended to reflect the evolving Gutenberg language.&#8221;</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>The new design&#8217;s header and footer have been rolled out to the entire WordPress.org site  and Hoffman said the idea is to &#8220;improve the site iteratively.&#8221; (In the meantime, the selected page indicator in the menu and the &#8220;Get WordPress&#8221; button do not match the old blue, in case that was perplexing when visiting the other pages.)</p>\n\n\n\n<p>I would not be surprised if the block editor adopts the bolder blue aspect of the new color scheme, as Fialho said it is &#8220;intended to reflect the evolving Gutenberg language.&#8221; It would provide a more consistent visual experience for WordPress across different mediums.</p>\n\n\n\n<p>The new design is a fork of <a href="https://github.com/Automattic/themes/tree/trunk/blockbase">Blockbase</a>, Automattic&#8217;s open source &#8220;<a href="https://wptavern.com/block-fse-hybrid-universal-what-do-we-call-these-new-wordpress-themes">Universal</a>&#8221; starter theme. Now that it&#8217;s live, future discussions on the project will happen in the <a href="http://wordpress.slack.com/">#design channel on Slack</a>.  Bugs and suggestions for the design can be <a href="https://github.com/WordPress/wporg-news-2021/issues">reported on GitHub</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Feb 2022 01:50:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:73:"Post Status: How Can We Increase Qualified Applicants for WordPress Jobs?";s:7:"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=89123";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:74:"https://poststatus.com/increasing-qualified-applicants-for-wordpress-jobs/";s: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:18826:"<p class="has-drop-cap">Have you heard? There are jobs in the WordPress industry — <a href="https://make.wordpress.org/training/2021/08/08/who-can-learn-help/">lots of jobs and many different roles</a>. See the job postings on the Post Status<a href="https://poststatus.com/jobs/"> Job Board</a>,<a href="https://jobs.wordpress.net/"> WordPress Jobs</a>, and even<a href="https://www.linkedin.com/jobs/search/?f_TPR=r2592000&f_WT=2&keywords=wordpress%20developer"> LinkedIn Jobs</a>.&nbsp; There are a lot of job seekers in the web development world. How are job seekers preparing for the workforce? What are employers doing to find qualified talent? </p>\n\n\n\n<p>The future of WordPress is in the training. It’s time we consider wages and connect employers with training providers as we develop software <em>and</em> people.&nbsp;</p>\n\n\n\n<h2 id="h-adequate-compensation-is-a-problem-for-employers-and-employees-alike">Adequate compensation is a problem for employers and employees alike</h2>\n\n\n\n<p>The strength of WordPress is its community. Even if you’ve never attended a WordCamp or participated in a Make WordPress team — which I hope you do — WordPress has been a lasting success because the community supports itself by sharing knowledge. As that happens, relationships develop alongside the software.&nbsp;</p>\n\n\n\n<p>Despite WordPress occupying such a dominant market share, WordPress businesses struggle to draw on a sufficiently large talent pool of qualified applicants to fill <a href="https://make.wordpress.org/training/2021/08/08/who-can-learn-help/">important roles</a> on their teams. One reason for the lack of qualified applicants has to do with pay and benefits. The WordPress ecosystem is still catching up to the compensation offered to people filling comparable roles outside of the WordPress ecosystem.&nbsp;</p>\n\n\n\n<blockquote><p>We need backward-compatible <em>and</em> forward-thinking solutions in the WordPress workforce.</p></blockquote>\n\n\n\n<p>Many companies within the WordPress ecosystem indicate they do not hire entry-level developers. Look at today’s job listings. Compared to senior roles, junior roles are hard to find. Skilled staff often work in advanced customer support roles with all the skills of a junior developer but for much less pay while seeking opportunities to take on development work. Support roles can be pathways to developer roles, but companies also could hire more junior developers. Hiring only experienced staff can save the upfront training for new talent but also lose the opportunity to form habits into the specific skills vital to your organization.</p>\n\n\n\n<p>Another complex challenge in a global workforce is providing adequate pay and benefits across vastly different national economies. Workers tread cautiously through scenarios comparing their own pay to others in very different economic climates. Fair and competitive compensation is no small decision for business owners to make. Often, the more complex a global payroll becomes in a distributed company, the more human resources will need to hire additional staff to cope.</p>\n\n\n\n<h2 id="h-acquisitions-and-marketplace-needs-are-upping-the-game-for-human-resources-and-job-candidates">Acquisitions and marketplace needs are upping the game for human resources and job candidates</h2>\n\n\n\n<p>A surge in corporate acquisitions and mergers in the WordPress space reached a new peak in 2021. This trend is partly driven by big WordPress employers'' need to acquire talent as well as products. What are the barriers to growing a deeper and broader talent pool? How can the WordPress community and employers help? What are the risks if they don''t?&nbsp;</p>\n\n\n\n<p>Acquisitions can serve several purposes for the purchasing company. New technology and a solid user base flow to the new owners, but so does a team of skilled staff. Briefly scan the<a href="https://poststatus.com/acquisitions/"> </a>Post Status <a href="https://poststatus.com/acquisitions/">acquisition tracker</a>. It will show you the companies that have been &#8220;acquihiring&#8221; or being acquired for their talent.&nbsp;</p>\n\n\n\n<p>Has your employer been acquired? Michelle Frechette has helped us consider, from the employee perspective, <a href="https://poststatus.com/your-wordpress-company-has-been-acquired-now-what/">what you need to know and do in an acquisition</a>. Being acquired can be a career-changing event for employees.</p>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<div class="wp-block-media-text alignwide is-stacked-on-mobile has-background"><img width="250" height="250" src="https://cdn.poststatus.com/wp-content/uploads/2021/09/RtpKYzps_400x400.png" alt="Get Hired" class="wp-image-85823 size-full" /><div class="wp-block-media-text__content">\n<p class="has-text-align-left has-normal-font-size" id="h-get-ready-for-remote-work"><strong>Get started today!</strong> Build your career in WordPress.</p>\n\n\n\n<p class="has-text-align-left has-small-font-size"><strong>Build your network. Learn with others. Find your next job.</strong> Read the <strong>Get Hired</strong> <a href="https://poststatus.com/get-hired/#%f0%9f%93%a7-subscribe-to-the-get-hired-newsletter">newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2709.png" alt="✉" class="wp-smiley" /> Listen to the <strong>Get Hired</strong> <a href="https://poststatus.com/podcast/get-hired/">podcast</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /> Follow <a href="https://twitter.com/gethiredwp">@GetHiredWP</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /></p>\n</div></div>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<p>Recently we''ve seen many startup WordPress companies mature along with the growing WordPress marketplace. Once small bootstrapped teams now have grown-up responsibilities like hiring skilled staff and paying competitive wages. Companies that previously could hire people with general WordPress user skills now have a more rigorous hiring process with heightened expectations about specific technical skills and experience. Enterprise-level agencies and larger product companies have staff dedicated to talent acquisitions, recruiters, and staff dedicated to the interview process.&nbsp;</p>\n\n\n\n<h2 id="h-relearning-wordpress-again-and-again">Relearning WordPress — again and again</h2>\n\n\n\n<p>The shift to block-based web development in WordPress, thanks to Gutenberg, has really brought forward the need for end-users and developers alike to relearn WordPress. For many, the classic editor experience, page builders, and premium themes have created an understanding of development and website creation that is increasingly obsolete. We now have a very different experience which we can opt-in to using as adoption of the block editor and full site editing increases.</p>\n\n\n\n<p>Many long-time WordPress developers began by learning theme development on classic themes like Kubrick, starter frameworks like Underscores, and they could look to Hello Dolly to learn how basic plugins work.&nbsp; As time went on, more options became available for advanced development in both WordPress and its product ecosystem. Blocks require developers to pivot to face a more JavaScript-oriented codebase. Theme template partials and unit tests are increasingly layered into our workflows.&nbsp;</p>\n\n\n\n<p>Newcomers to WordPress may not need to relearn some of these new knowledge areas. An entirely new generation of WordPress users will experience WordPress for the first time with the block editor in their posts, pages, paratextual content, navigation, and themes. How we build plugins for a block-based world will look very different than plugins that were created for WordPress in its classic editor days. These users do not need to unlearn older methods, but the barriers to entry may be higher and their learning curve may be steeper. Depending upon their careers, they may need to learn special methods for backward compatibility with older themes, plugins, and programming techniques.&nbsp;</p>\n\n\n\n<blockquote><p>Many freelancers, contractors, and small business website creators implement and maintain a small amount of custom code to extend off-the-shelf plugins and themes to fit their clients'' needs.</p></blockquote>\n\n\n\n<p>Today, any seasoned developers may want to yell “Get off my lawn!” or “Back in my day…” or “we always did it this way.”&nbsp; I hold a deep appreciation for the contributions made and work put into our classic methods. I learned PHP because I wanted to register a sidebar with a widget in the Revolution theme before that functionality existed in WordPress. We don''t need things to remain as they always were — or require new learners to struggle the same way we have.</p>\n\n\n\n<p>We need backward-compatible <em>and</em> forward-thinking solutions in the WordPress workforce.&nbsp;</p>\n\n\n\n<h2>Software updates drive the need for employee upskilling and training upgrades</h2>\n\n\n\n<p>In addition to new hires with in-demand skills who are at the beginning of their careers in WordPress, employers need to retrain existing staff to keep up with the ever-evolving methods and tools of the trade. Beyond the languages, frameworks, APIs, and core WordPress codebase itself, there are things like build tools and entirely new ways to host and deploy WordPress sites that emerge periodically. It isn''t necessarily harder — but it''s definitely not easier — to keep up than it used to be.&nbsp;</p>\n\n\n\n<h2 id="h-small-business-needs-call-for-generalists">Small business needs call for generalists</h2>\n\n\n\n<p>Small businesses running on WordPress often don''t need people with deep technical skills. There is an entire ecosystem of website builders, integrators, implementors, maintainers, and marketing consultants who deliver, host, and support sites for clients with low or no-code solutions. Many freelancers, contractors, and small business website creators implement and maintain a small amount of custom code to extend off-the-shelf plugins and themes to fit their clients'' needs. <a href="https://mattreport.com/growth-of-wordpress/">Liam Dempsey</a> and <a href="https://mattreport.com/growth-of-wordpress/">Matt Medeiros</a><a href="https://hallwaychats.com/episodes/episode-125-matt-medeiros/"> have described this line of work</a> as the domain of the &#8220;digital&#8221; or &#8220;blue-collar&#8221; &#8220;web&#8221; or &#8220;WordPress worker.&#8221;</p>\n\n\n\n<p>That''s not to say the blue-collar builder, WordPress freelancer, or generalist doesn''t need to stay engaged with ongoing learning in their careers. They do. WordPress workers serving small business and agency needs must adapt to Full Site Editing, page builders, block-based themes, plugins, and blocks. They must not only excel in them as tools but learn to market and sell them to clients with their value-added services. The tools they use most commonly keep changing too, and lately the pace feels faster.</p>\n\n\n\n<p>In addition to the skills required to host, set up, customize, and develop with WordPress, small WordPress business owners also need business skills! In enterprise-level agencies and product-oriented companies, executive and management roles are far more specialized. Within small businesses, one person may need to cover a wider variety of tasks, from marketing to finance, to some of the technical work.</p>\n\n\n\n<h2 id="h-corporate-needs-call-for-specialists-who-are-up-to-date">Corporate needs call for specialists who are up-to-date</h2>\n\n\n\n<p>Chris Wiegman recently mapped out the <a href="https://chriswiegman.com/2021/08/the-changing-wordpress-ecosystem/">technologies that developers frequently use</a> today. It''s quite a list. Learning WordPress and being proficient at your job aren’t easy things to attain. There are a lot of skills you need, from programmatic languages to build tools — and more.&nbsp;</p>\n\n\n\n<p>Adapting to the constant growth of languages and tools isn''t a new challenge. Adjusting to Gutenberg and Full-Site Editing isn''t even a new need at this point. Beyond WordPress, web development is rapidly adapting to shifts in technology as well.</p>\n\n\n\n<blockquote><p>In the sea of resources that exist for learning WordPress and web tech skills, learners are still expected to plot their own course. </p></blockquote>\n\n\n\n<p>Ongoing training for specialized areas of technical knowledge, staying current with the work happening in Gutenberg before documentation is available, and implementing what is currently stable are all vying for staff learning time and attention which puts them in competition with the business imperative of delivering quality products and services in a timely manner.</p>\n\n\n\n<h2 id="h-wordpress-training-lags-behind-today-s-workforce-needs">WordPress training lags behind today’s workforce needs</h2>\n\n\n\n<p>Surveying the landscape of training opportunities adjacent to the WordPress ecosystem is fascinating. Despite having such a vast market share, we have yet to land on a common set of competencies for the many different careers that exist in the WordPress industry.</p>\n\n\n\n<p>In the sea of resources that exist for learning WordPress and web tech skills, learners are still expected to plot their own course. But what happens if you are still in the phase <em>where you don''t know what you don''t know?</em> What if you want a guide? It''s really hard to figure out what to learn, in what order, and from what training providers. Training programs may also be struggling to know what you need from them.</p>\n\n\n\n<blockquote><p>The future of WordPress is in the training. It’s time we consider wages and connect employers with training providers as we develop software <em>and</em> people.&nbsp;</p></blockquote>\n\n\n\n<p>Where do you turn to learn and relearn WordPress deeply? YouTube is filled with videos about WordPress, many of which are quickly outdated or biased vehicles for affiliate links. There are <a href="https://poststatus.com/professional-wordpress-plugin-development-interview-with-the-authors/">a few great books about WordPress development</a>, but if that isn''t your learning style, that too becomes a challenge. Courses exist, but without any standardization or accreditation, it falls to a few individuals to define training goals, standards, and priorities. Generally, these courses are not vetted by the industry itself.</p>\n\n\n\n<p>To this point, people have been rather self-sufficient in acquiring the skills needed for jobs. High schools, career technical schools, colleges, and universities have incorporated WordPress instruction into their programs. Often, this reaches as far as installing and configuring themes and plugins while building a website. These programs often stop short of actual development, such as creating plugins, building blocks, or designing themes from scratch.&nbsp;</p>\n\n\n\n<p>In the developer bootcamp world, often it is assumed that PHP is dead and WordPress is easy to learn. Yet entire educational organizations exist to help prepare their students for work. Few bootcamps offer a focus on WordPress development, and yet they want their graduates to be adequately trained for roles in WordPress product companies. Often these programs are aimed at<a href="https://generalassemb.ly/education/getting-started-with-wordpress/new-york-city"> content marketers</a>.&nbsp;</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Does NO ONE do a web dev bootcamp that includes <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a>? <br /><br />Was just looking at a few popular ones and noticed they don’t even include PHP. It’s literally all about JavaScript, which is also great, but show those students how they can be useful with React in WordPress!</p>&mdash; Daniel <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f389.png" alt="🎉" class="wp-smiley" />44 on 2sday 2/22/22 <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f973.png" alt="🥳" class="wp-smiley" /> (@schutzsmith) <a href="https://twitter.com/schutzsmith/status/1487799454828843010?ref_src=twsrc%5Etfw">January 30, 2022</a></blockquote>\n</div>Daniel Schutzsmith notices how little WordPress is represented in developer training programs.\n\n\n\n<h2>What''s to be done? What questions must we ask — and answer?</h2>\n\n\n\n<p>I have to wonder, what would happen if official guidance was available to such organizations? What might the job pipeline look like globally in website development if training providers knew exactly what skills are needed?</p>\n\n\n\n<h3 id="h-we-badly-need">We badly need:</h3>\n\n\n\n<ol><li><strong>Pathways for Learning</strong> — For the main types of job pathways, a sequential order for learning WordPress should be available. See the<a href="https://make.wordpress.org/training/2021/05/03/high-level-roadmap-to-learning-wordpress-development/"> High-Level Roadmap</a>.</li><li><strong>Learning Styles</strong> — Whether it’s a preference based in personal disposition, accessibility needs, culture, connectivity, or other factors, how people learn varies. Our training should cater to common differences to lower the barriers to entry.&nbsp;</li><li><strong>Advisement</strong> — Employers in the industry can attest to the gaps in talent and areas where applicants lack adequate skills. As general standards for various roles become more apparent, training programs and learners have clearer goals.&nbsp;</li><li><strong>Certification</strong> — There are many ways to attain the necessary skills for jobs. Some careers require degrees and certification. Many don’t need either. The purpose of certification is to define and verify key skill areas needed in the workforce.&nbsp;</li></ol>\n\n\n\n<p class="has-background"><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2709.png" alt="✉" class="wp-smiley" /> <a href="https://poststatus.com/get-hired/#subscribe-to-the-get-hired-newsletter">Subscribe</a> to the <strong>Get Hired Newsletter</strong> for <a href="https://poststatus.com/jobs/">the latest WordPress job opportunities</a> from great employers — plus our latest podcast episodes, articles, and career tips. <em>Delivered to you every week!</em></p>\n\n\n\n<h2 id="h-help-us-solve-this-puzzle-together">Help us solve this puzzle together!</h2>\n\n\n\n<ol><li>Join the<a href="https://make.wordpress.org/training"> Make WordPress Training team</a>. Contribute or revise content, collaborate on ideas, and develop the Learn WordPress website’s functionality.&nbsp;</li><li>Come to the<a href="https://wpcareersummit.com/"> WP Career Summit</a> as we match employers, employes, and job seekers with training providers.&nbsp;</li></ol>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Feb 2022 20:15:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:56:"WPTavern: Building a “Scotch Tape” Image Block Style";s:7:"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=130151";s:7:"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:61:"https://wptavern.com/building-a-scotch-tape-image-block-style";s: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:7542:"<p class="has-drop-cap">In today&#8217;s post, Tavern readers are in for something a little different than our regular stream of news and opinion. Welcome to the <a href="https://wptavern.com/category/building-with-blocks">Building with Blocks</a> series. It is a new type of post we are trying out to show people some of the fun, unique, or creative things they can do with WordPress blocks.</p>\n\n\n\n<p>Our team decided to split the series into both developer and user-centric tracks. Posts may cover creating an &#8220;about me&#8221; page, coding custom block styles, piecing together a pattern, or something else entirely.</p>\n\n\n\n<p>Since I am kicking off this series, I wanted to answer a question we already received from one of our readers. I had previously shared a custom block style with a &#8220;Scotch tape&#8221; look in my coverage of the <a href="https://wptavern.com/fse-program-the-media-experience-and-its-future-in-wordpress">FSE Outreach Program&#8217;s call for media testing</a>:</p>\n\n\n\n<img />Original block style.\n\n\n\n<p>Devendra Meena <a href="https://wptavern.com/fse-program-the-media-experience-and-its-future-in-wordpress#comment-414720">asked in the comments</a>:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Hey man, how to get the &#8220;tape&#8221; custom block image?</p></blockquote>\n\n\n\n<p>This felt like a natural starting point with my first post in the series.</p>\n\n\n\n<p>The design shows a piece of tape holding a Polaroid-style, framed image. Technically, I also had an alternate style with two pieces of tape at the corners. However, this tutorial will focus on the former. The two-corner design requires overwriting some editor-specific CSS, technically breaking functionality, and is not something I should encourage.</p>\n\n\n\n<p>I also wanted to begin with block styles because they are underutilized. Most variations I have seen have been simple changes like adding borders and removing margins. These are often best left to block design tools. Of course, themers are adding these styles because WordPress currently lacks or has previously lacked the UI controls for handling them. It is also one of the reasons so many have asked to <a href="https://github.com/WordPress/gutenberg/issues/14598">mix and match multiple block styles</a> &#8212; themes are doing the work that core should be doing. More tools are continually being added, but we still have a long way to go.</p>\n\n\n\n<p>When I think of block styles, I want to create designs that are unlikely to be available via the standard design tools. I want to serve something unique to theme users. That is where we are starting today.</p>\n\n\n\n<p>As a bonus, custom block styles work in classic and block themes.</p>\n\n\n\n<p>Despite having written hundreds of tutorials in my life, this exercise turned out to be a little tougher than I had anticipated. It is easy to forget that everything I code starts with a base of &#8220;fixing&#8221; the things that I find odd about the default block library styles. This makes my life easier. However, many theme authors will lean on core&#8217;s defaults, so I needed to make this general enough to work for them.</p>\n\n\n\n<p>Therefore, I opted to start from the default Twenty Twenty-Two theme. In testing, I suggest working with it. The CSS code in the following section may need slight alterations for others.</p>\n\n\n\n<h2 id="creating-the-scotch-tape-block-style">Creating the &#8220;Scotch Tape&#8221; Block Style</h2>\n\n\n\n<p>The first step is to register a custom block style via the theme. WordPress has both <a href="https://developer.wordpress.org/block-editor/reference-guides/block-api/block-styles/">server-side and JavaScript APIs</a> for this feature. Using PHP is easier to set up if you do not already have an editor script file to drop the code into.</p>\n\n\n\n<p>To register the custom block style, add the following code to your theme&#8217;s <code>functions.php</code> file:</p>\n\n\n\n<pre class="wp-block-code"><code>// Register block styles on the init hook.\nadd_action( ''init'', ''tavern_register_block_styles'' );\n\n// Wrapper function for registering all block styles.\nfunction tavern_register_block_styles() {\n\n        register_block_style( ''core/image'', &#91;\n        	''name'' => ''scotch-tape'',\n        	''label'' => __( ''Scotch Tape'', ''tavern'' )\n        ] );\n}</code></pre>\n\n\n\n<p>Doing so will register the style in the editor. You can test this by adding an Image block on the post-editing screen. &#8220;Scotch Tape&#8221; should be selectable under the styles tab.</p>\n\n\n\n<img />Registered style correctly appears for the Image block.\n\n\n\n<p>Registering a style is the easy part. Writing the code is where things can get dicey. WordPress has so many methods of loading CSS styles that you might not know where to start.</p>\n\n\n\n<p>The <code>register_block_style()</code> function used earlier allows developers to add a <code>style_handle</code>, a reference to a registered stylesheet. Themers can also add an inline style directly via the <code>inline_style</code> argument. For just a few lines of CSS, this works well.</p>\n\n\n\n<p>In my own themes, I <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_block_style/">register block-specific stylesheets</a> via the <code>wp_enqueue_block_style()</code> function &#8212; <em>yes, the function names are terribly confusing</em>. This was officially added in WordPress 5.9. It will only output the CSS when a block is used on the page. For example, I add a <code>core-image.css</code> file to house all Image block CSS. This is the method I recommend.</p>\n\n\n\n<p>However, for the sake of simplicity, I added the following code to the end of Twenty Twenty-Two&#8217;s <code>style.css</code> file:</p>\n\n\n\n<pre class="wp-block-code"><code>/* Design for the &lt;figure> wrapper. */\n.wp-block-image.is-style-scotch-tape {\n	position:         relative;\n	overflow:         visible;\n	padding:          1rem;\n	background-color: #fff;\n	box-shadow:       0 4px 10px 0 rgba( 0, 0, 0, 0.3 ),\n	                  0 0 4rem rgba( 255, 255, 235, 0.5 ) inset;\n}\n\n/* Design for the "tape". */\n.wp-block-image.is-style-scotch-tape::before {\n	content:    "";\n	display:    block;\n	position:   absolute;\n	width:      7rem;\n	height:     2rem;\n	margin:     auto auto auto -3.5rem;\n	z-index:    1;\n	left:       50%;\n	top:        -0.5rem;\n	background: rgba( 255, 255, 235, 0.5 );\n	box-shadow: 0 4px 10px 0 rgba( 0, 0, 0, 0.3 );\n}\n\n/* Remove TT2''s image shadow. */\n.wp-block-image.is-style-scotch-tape img {\n	box-shadow: none;\n}\n\n/* Adjustments for the caption. */\n.wp-block-image.is-style-scotch-tape figcaption {\n	display:     block;\n	margin:      1rem 0 0;\n	line-height: 1;\n	font-size:   1rem;\n	font-family: ''Fuzzy Bubbles'', sans-serif;\n}</code></pre>\n\n\n\n<p>With the CSS in place, it is merely a matter of finding an image to test with. I chose <a href="https://wordpress.org/photos/photo/9146203d37/">Marcus Burnette&#8217;s whale shark</a> from WordPress Photos.</p>\n\n\n\n<img />Adding images in style!\n\n\n\n<p>If you want to add a bit of flair to your captions, load up <a href="https://fonts.google.com/specimen/Fuzzy+Bubbles">Fuzzy Bubbles</a> or another handwriting font from Google Fonts.</p>\n\n\n\n<p>This style does not necessarily need to be tied to the Image block. There is no reason it could not apply to Paragraphs, Groups, and more with some adjustments.</p>\n\n\n\n<p>For now, I hope you all have fun with it. Also, feel free to share in the comments where you would like to see the new &#8220;Building with Blocks&#8221; series head in the future.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 17 Feb 2022 02:48: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: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:104:"Post Status: When, Not Why, Store Owners Choose an E-Commerce Platform — The Woo Snippet (February 14)";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=93485";s:7:"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://poststatus.com/when-not-why-store-owners-choose-an-e-commerce-platform-the-woo-snippet-february-14/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2657:"<h2 id="h-woocommerce-6-3-beta-1-ready-for-testing">WooCommerce 6.3 Beta 1 Ready for Testing</h2>\n\n\n\n<p>Time for testing with <a href="https://developer.woocommerce.com/2022/02/15/woocommerce-6-3-beta-1/">the release</a> of <strong>WooCommerce 6.3 Beta 1</strong> in preparation for next month''s release. Both <strong>WooCommerce Blocks</strong> and <strong>Admin</strong> have been updated. And speaking of blocks, <strong>WooCommerce Blocks 7.0.0</strong> <a href="https://developer.woocommerce.com/2022/02/16/woocommerce-blocks-7-0-0-release-notes/">has been released</a>. It brings <strong>Global Styles</strong> support to more blocks and improves editor capabilities.</p>\n\n\n\n<p>After having been an opt-in feature for some time, the new product filtering mechanism in WooCommerce announced a few months ago is rolling out for the public in <strong>WooCommerce 6.3</strong>. A post is up on the Woo developer blog outlining <a href="https://developer.woocommerce.com/2022/02/02/new-product-filtering-by-attributes-rolling-out-in-woocommerce-6-3">what you need to know as a shop administrator</a>.</p>\n\n\n\n<h2>Woo versus Ecwid</h2>\n\n\n\n<p>In other news, <strong>Forbes</strong> <a href="https://www.forbes.com/advisor/business/software/woocommerce-vs-ecwid/">published an article</a> comparing WooCommerce to <strong>Ecwid</strong>. The bottom line for the authors: Woo is the choice for WordPress users and Ecwid for all those &#8220;other&#8221; existing websites. I guess it''s that simple, huh?</p>\n\n\n\n<h2><s>Why</s> When Store Owners Choose an E-Commerce Platform</h2>\n\n\n\n<p>At the <strong>Post Status</strong> partners retreat last week, members <strong>David Mainayar</strong> (Co-Founder at <strong>PeachPay</strong>), <strong>Aaron Campbell</strong> (WordPress Ecosystem at <strong>Newfold</strong>), and <strong>Jonathan Wold</strong> (Partnerships at <strong>Post Status</strong>) got into a discussion about eCommerce site ownership. A good insight I took away is that owning your own site and content is not really a selling point, even with WooCommerce, when a business first goes online. Ownership tends to matter at the moment when the shop owner realizes they need it. Being there at the point in time is a challenge for Woo and the whole Woo/WordPress ecosystem.</p>\n\n\n\n<h2>WooCommerce Brand Management</h2>\n\n\n\n<p>Lately, I''ve been curious about how WooCommerce manages its own branding. Tune in and listen to Woo team members <strong>Fernando Perez</strong> and <strong>Andrei Slobtsov</strong> share <a href="https://dothewoo.io/woocommerce-branding-design">insights around branding and design, behind the scenes at WooCommerce</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Feb 2022 20:57:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Bob Dunn";s: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:103:"Post Status: Post Status Excerpt (No. 46) — Contributor Recognition and Certification with Lesley Sim";s:7:"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:61:"https://poststatus.com/?p=93398&preview=true&preview_id=93398";s:7:"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://poststatus.com/post-status-excerpt-no-46-contributor-recognition-and-certification-with-lesley-sim/";s: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:25961:"<p class="has-drop-cap">In this episode of Post Status Excerpt, David <a href="https://poststatus.com/excerpt/45/">continues a conversation</a> with <strong>Lesley Sim</strong> to pick her brain about some ideas she has for rewarding core contributors to WordPress. Last month on Twitter and <a href="https://twitter.com/lesley_pizza/status/1480849910530396166">Post Status Slack</a> Lesley <a href="https://twitter.com/lesley_pizza/status/1480849910530396166">floated the idea of special contributor badges on WordPress.org</a>. These badges would give developers who earned them a boost to their plugin and theme rankings. The goal would be to encourage new contributors to enter the WordPress ecosystem and recognize those in the community who are doing typically unpaid work that carries the project forward.</p>\n\n\n\n<p><strong>Why This Is Important:</strong> Improving the contributor onboarding experience will help WordPress gain more core contributors. Some ideas going around the WordPress community involve additional sponsorships, new sources of funding, and public recognition. Some ideas will never make it off the ground but might lead to better ideas that do take off. We should never stop thinking about how to make the human factor in contribution to the project better for everyone. <a href="https://poststatus.com/wordpress-as-a-commons/">Maintaining a commons</a>, like WordPress as an open source project, is a constant challenge for the WordPress community, as Lesley recently wrote for Post Status.</p>\n\n\n\n\n\n\n\n<p class="has-background">Every week <strong><a href="https://poststatus.com/podcast/the-excerpt/">Post Status Excerpt</a></strong> will brief you on important WordPress news — in about 15 minutes or less! Learn what''s new in WordPress in a flash. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/26a1.png" alt="⚡" class="wp-smiley" /><br /><br />You can listen to <a href="https://poststatus.com/podcast/the-excerpt/">past episodes</a> of <strong>The Excerpt</strong>, <a href="https://poststatus.com/category/post-status-podcasts/">browse all our podcasts</a>, and don’t forget to subscribe on <a href="https://open.spotify.com/show/1m3xwXbe0MG5BzFVPtB0A7">Spotify</a>, Amazon Music, <a href="https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5zaW1wbGVjYXN0LmNvbS8ySkU5c2M4UA">Google Podcasts</a>, <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">iTunes</a>, <a href="https://castro.fm/podcast/c53552c6-1ee0-4fc4-9de4-08ed6bf1ee4d">Castro</a>, <a href="https://www.youtube.com/c/PostStatus">YouTube</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, <a href="https://player.fm/series/wordpress-post-status-podcasts">Player.fm</a>, <a href="https://pca.st/05rR">Pocket Casts</a>, <a href="https://wordpress-post-status-draft-podcast.simplecast.com/">Simplecast</a>, or by <a href="https://feeds.simplecast.com/2JE9sc8P">RSS</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f3a7.png" alt="🎧" class="wp-smiley" /></p>\n\n\n\n<h3 id="h-mentioned-in-the-show"><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f517.png" alt="🔗" class="wp-smiley" /> Mentioned in the show:</h3>\n\n\n\n<ul><li><a href="https://twitter.com/lesley_pizza">Lesley Sim</a> (Twitter)</li><li><a href="https://twitter.com/dimensionmedia" target="_blank" rel="noreferrer noopener">David Bisset</a> (Twitter)</li><li><a href="https://twitter.com/post_status" target="_blank" rel="noreferrer noopener">Post Status</a> (Twitter)</li></ul>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<hr class="wp-block-separator logo is-style-default" />\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<h3><img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> Sponsor: <a href="http://poststatus.com/godaddy">GoDaddy Pro</a></h3>\n\n\n\n<p>Manage 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 clients. GoDaddy Pro is free — and designed to make your life better.</p>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<hr class="wp-block-separator logo is-style-default" />\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<h2 id="h-transcript"><strong>Transcript</strong></h2>\n\n\n\n<p>Conversation with Lesley part 2</p>\n\n\n\n<p><strong>David Bisset:</strong> Just repeat what you just said, because I want my wife to hear this</p>\n\n\n\n<p><strong>Lesley Sim:</strong> nice haircut</p>\n\n\n\n<p><strong>David Bisset:</strong> because she''s the one that gave it to me.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Oh, cool. Yeah. Yeah. On your anniversary</p>\n\n\n\n<p><strong>David Bisset:</strong> In another six months, I''ll look, I''ll look like a normal human being again. How about you? Wow. You have an impressive microphone.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> It''s it''s new, new wish to see you on</p>\n\n\n\n<p><strong>David Bisset:</strong> that.</p>\n\n\n\n<p>Well, you''ve been doing a lot of podcasts lately, so you need a good microphone. Yeah. I''m still waking up and your probably heading into the night. W uh, well, first of all, let''s confirm again, where do you reside?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> I live in Singapore. Southeast Asia is UTC plus eight on a Steve. You could spend the entire recording, listening to me, complain about people not using the UTC type standard.</p>\n\n\n\n<p><strong>David Bisset:</strong> It might offend some horrible at math. So I had to ask you to translate probably for me two or three times to book this, but so what time is it over there?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> It is 9:30 PM for me.</p>\n\n\n\n<p><strong>David Bisset:</strong> There''s been a lot of stuff to talk about actually in the WordPress community. I thought January is usually a slow time. And I guess maybe we make up for if at all these acquisitions and our attention has been focused, but when December, January are quiet, we kind of make up our own stuff to talk about. There was lots of been talking about contributions and boy that is just a long string of dominoes. I mean, this talk has always gone on, but from the log four scene to a Joomla, to other things that have been happening, comments and so forth.</p>\n\n\n\n<p>And even recently about, I did a podcast about documentation team about how that''s underpowered and they need more sponsored contributors and all of that. And then Matt state of the word.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> We have three now, right?</p>\n\n\n\n<p><strong>David Bisset:</strong> I think so. Yeah, but that can obviously change at any time. And we, you know, we''re throwing out ideas on Post Status slack.</p>\n\n\n\n<p>I think that''s a really great environment to throw out ideas. And I''m really glad we do because some of these ideas, I think we know will probably never come to pass, at least in the way that we''re sharing them. But. They do present interesting things to think about and maybe lead to some, even better ideas.</p>\n\n\n\n<p>And you actually brought one of those up in terms of contributor badges. So did you, did you want to kind of like take it from there?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> I can''t remember what led me to them. It''s probably some kind of just being on the Post Status slack a lot, um, talking to people, um, and it''s like, you know, just this kind of iterative process, um, which incident incidentally, I think is a really important part of the WordPress community and like how it stays healthy and like, you know, like the disagreements and the sharing of ideas, even if they never actually get made. I think all that stuff like, so that as new people come in without years and years of context and background, like they kind of see the bigger picture as well.</p>\n\n\n\n<p>Um, so I''m a fan of all of that. The contributor badges idea. Maybe I should talk about what it is first. So</p>\n\n\n\n<p><strong>David Bisset:</strong> Those who think we don''t need those badges, yes we do.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Um, so the idea is like, I, I''m a huge fan of nonfinancial incentives. So a lot of people like to talk about, you know, oh, we don''t have enough country contributed to is it''s because we''re not paying them enough.</p>\n\n\n\n<p>So like here''s. Here''s a million bucks at like that''s materialized these contributors out of thin air because now we have a million bucks to, to make it happen. Um, and I don''t think it works that way. And so, like, I kind of like coming up with ideas that are more status oriented or like more fulfillment oriented and that''s where the badges come in.</p>\n\n\n\n<p><strong>David Bisset:</strong> Ego oriented?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> So my idea for, sorry. Yeah. Ego. Yeah.</p>\n\n\n\n<p><strong>David Bisset:</strong> I couldn''t hold that one in, sorry</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Ego in a good way, I think. So the idea is that you would go through different levels. And so, um, you know, a level one contributor doesn''t necessarily even have to. Um, put anything in GitHub or like any of that stuff, or maybe level one, contributor could just be competing something from Learn WP not WordPress.</p>\n\n\n\n<p>Right. Um, and that just kind of ensures that they know how to write code in the WordPress way, or they know how to answer support tickets in the WordPress way and things like that. And it goes, you know, up and up from there and you get the badges and the badges then give you, then allow you to rank higher in the WordPress directory.</p>\n\n\n\n<p>So for example, you know, if, if Yoast, like let''s say Yoast is a huge company they''ve been contributing for years and , let''s say if you have a level 20 badge or something like that, that gives them a boost in the WordPress directory in comparison to me, you know, cause like I came up with a SEO plugin yesterday. I don''t know anything about coding on WordPress.</p>\n\n\n\n<p>Um, and so like it only makes sense that my slightly dodgy plugin that I only made yesterday doesn''t um, get the same level of, uh, authority as someone with a level 20 contributor badge. Um, and I think like that works on many levels. So from a contributor point of view, um, it works because. You know, the badge and the authority and the status and all of that.</p>\n\n\n\n<p>Um, it helps their business because if they rank higher than people would download their plugins. And then presumably if they are trying to sell plugins, they, you know, get more sales are, if they''re not, then they just kind of like having that status that, that works well as well. Um, it works from the WordPress open source project perspective because now you''ve got lots of contributors who are incentivized to contribute.</p>\n\n\n\n<p>And that kind of gives like the long tail of contributions, which I think is important and it''s kind of, what''s missing right now as well. Um, and then, sorry, one last one.</p>\n\n\n\n<p><strong>David Bisset:</strong> We edit all this out. Anyway, my interruptions,</p>\n\n\n\n<p><strong>Lesley Sim:</strong> um, it also helps the users, the end user, because the end user who''s going on the dark shoes, obviously wanting to use, um, SEO plugin.</p>\n\n\n\n<p>They don''t want to use the buggy one that I made yesterday. And so by being able to see the contributor badges, it kind of helps them make. Slightly more, um, thoughtful decision. Um, and also, you know, , uh, one of the high contributor badge is ranked higher and then that also kind of helps surface the right plugins at the right level.</p>\n\n\n\n<p>Um, and you know, like, as I''m saying is I can kind of already hear what the oppositions to the idea would be that, you know, it''s unfair someone, you know, you''re just kind of like giving more advantages to. Someone with like lots of resources to even have a contributor level 20 badge in the first place.</p>\n\n\n\n<p>And that just like widens the gap and it makes it impossible for someone new to catch up. Um,</p>\n\n\n\n<p><strong>David Bisset:</strong> so what would, what would be your response to that? Because like Yoast would have, like, their people would have all of the badges, right. Or like all of the top badges. So what, what would be your response to that?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> So, so my response would be not the response that most people want to hear my response is firstly, this is something that has to be worked out. So, you know, these ideas don''t emerge in the world fully formed. They are kind of, it comes out and then, you know, people argue about it. We iterate on it. Be like lunch, a version of wine.</p>\n\n\n\n<p>It falls flat. You know, people say it''s awful. They hate it. They''re leaving WordPress. They write blog posts to heat it up, right? Yeah, exactly. That''s the first thing. Yeah, that''s the power.</p>\n\n\n\n<p><strong>David Bisset:</strong> Why can''t I use this for good.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> So that, I mean, that''s, that''s honestly the first, the first thing and that, you know, that''s the reality of how these things go.</p>\n\n\n\n<p>Um, but the second is like, you know, the nice thing about contributor, badgers, like, oh, I''m all the things that I''m seeing. These are just kind of ideas of how you can incentivize. But the underlying kind of concept is to do the sort of intrinsic motivation type stuff, or like this like status badges type stuff.</p>\n\n\n\n<p>Um, you know, whether, whether it''s someone gets me, maybe the badges aren''t even seen on the front end. So like as a developer, you can see the badge, but then as a user, you can not see the badge, you just, um, your, your. Um, plugin just gets ranked higher or something and that''s the only outcome. So all of this stuff can be tweaked in a million different ways.</p>\n\n\n\n<p>And, um, I like thinking about this kind of stuff. So I think that could be pretty cool to figure out. Um, but it''s kind of, I guess, similar to how Google and back links work, you know, like that kind of works as an authority thing as well. So like, if you have a backlink from a high authority site, you get ranked higher.</p>\n\n\n\n<p>And so this is kind of the same thing. I mean, Google has clearly made it work. Although some people argue that they haven''t, but, you know, um,</p>\n\n\n\n<p><strong>David Bisset:</strong> has anybody really, is there anybody really that has, is there anybody really that has nailed this open source or not in, in, in tech as far as your concerned. Has anybody nailed this concept or concept of just awarding badges for things?</p>\n\n\n\n<p>Or do you think there''s always going to be some problems with this idea?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> I mean, so I think that, um, this is, I guess, kind of a philosophical take, but I feel like there''s always two sides of things. So like what is problematic to one person is going to be advantageous to the other person. So I don''t think.</p>\n\n\n\n<p>You know, binary sent, see, has anyone nail this and made it 1000% fair in every single way. And nobody, once</p>\n\n\n\n<p><strong>David Bisset:</strong> you bring the F-word into it, once you bring the F word into it, fair, I don''t, you know, it''s all out the window from here, but I mean, let''s, I mean, there are badges. I mean, wordpress.org has badges.</p>\n\n\n\n<p>Right. And I would say they''re almost like, um, Oh, I was never a boy scout in the U S and I don''t know what the equivalent is outside of the U S but girl Scouts and boy Scouts. They have these patches on the sashes that of once they''ve accomplished something. And I guess maybe some, some countries militaries, too, they have pins or markers denoting, their rank and their accomplishments or maybe awards that they''ve been given.</p>\n\n\n\n<p>So it''s a, it''s, it''s a fairly well-known concept. And you''re looking at the badges in terms of ranking, you know, like a leaderboard type of a thing. I, it sounds like to me, um, yeah, the other is an incentive for continuing to contribute. And because like you said before, if you have a million dollars, that''s I think Matt said this before.</p>\n\n\n\n<p>It''s kind of hard to distribute that evenly and fairly in that I, you know, there I am using the F word again. But I th would you agree that there is also just me be as much about it''s op it''s about as much of recognition than, than, than anything else, or is at least partly because of recognition, um, respecting people''s time and effort, all the blood, sweat, and tears that they put into it.</p>\n\n\n\n<p>Not just respect from say automatic or the WordPress community, but respect from. You know, you''ve worked something for really hard on something and it gets, it gets very harshly criticized, maybe in their opinion. What do you think, do you think badges would solve this? Um, would solve some emotional hole of people that think they''re not being recognized for their work?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> I think so. Probably, um, again, like the answer is, it depends, um, Honestly, I think that when it comes to recognition, it''s not, it''s, it''s so difficult because people don''t actually want to be recognized by, or don''t necessarily want to be equally recognized by, you know, 5,000 different people. They want to be recognized by like the one or two people that they really look up to.</p>\n\n\n\n<p>And then maybe like, 10 people within their, um, social circle and then maybe like very, very broadly 5,000 people. Right. Um, and so like all of those dynamics come into play as well. So I''m not sure that like just the badges themselves. Yeah would necessarily mean anything. Um, if you had just kind of going go all out or recognition, I think like part of why I''m talking about tying the badges to some kind of incentive is, um, specific to the idea of getting more contributors.</p>\n\n\n\n<p>Um, so I think like when it comes to contributors there. There are a couple of now a couple of, um, problems, but they arem''t the problems that people think they are. So like, it''s definitely not a matter of just like let''s throw money at the problem, which is often what the problem people think. Oh, the, what they think is the problem.</p>\n\n\n\n<p>So it''s often it''s not just throw my money at the problem. You don''t have enough money.</p>\n\n\n\n<p><strong>David Bisset:</strong> Um, cause you want to compensate people because just to pause there, you want to compensate people for their time because they''re doing this not, we''re not talking about the sponsored people. We''re talking people that are volunteering their time and they obviously, if they''re not being compensated in some way, it''s harder.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Getting more of those people on. Um, so, so I think like there''s like a long tail of contributions that needs to happen. So, um, I think WordPress now is already getting pretty good at this like whole concept of sponsored contributors. There are a lot of, um, companies that are doing that increasing increasingly, and I think that''s really, really awesome.</p>\n\n\n\n<p>And like another, the model is kind of there and has been proven out, I think. Very short, like in like one or two years, this will not be a problem anymore. They''ll just be lots of sponsored contributors and it''ll be fine. So like, I think the problem is actually the long tail of contributors. So, you know, you were talking about the documentation team, right?</p>\n\n\n\n<p>There''s not enough people there. And I know having three full-time people dedicated to it is great, but then you also need like 500 people to. Do you know, to look at typos, to do the translations, to do the super tiny documents, which are really important, but no one really wants to write because they''re kind of boring and blah, blah, blah, blah.</p>\n\n\n\n<p>Or you need someone to like go through, you know, documents from 2007 and update screenshots, right? Like that''s the long tail of contributions. And I think like having some kind of incentives to allow for that kind of work. Like someone can just come in, spend half an hour, get some screenshots, you know, get bumped up another badge level and you''ll go about their day.</p>\n\n\n\n<p>Like, I think that kind of thing would be really cool.</p>\n\n\n\n<p><strong>David Bisset:</strong> It''s like experience points too, if you''ve ever played the old.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Yeah, exactly.</p>\n\n\n\n<p><strong>David Bisset:</strong> I don''t know. Is it RP? No, it''s RPGs. I forgot what they''re called. Um, I''ll edit in whatever it is the later, but I remember playing old computer games where he had so many experience points in the more experience points you get you level up and you get, I''m not sure though what, what, you know, besides just the bragging rights, what you would get, uh, out of more points, but you definitely would be able to be recognized if, for example, like, let''s say post status integrated some sort of little badge thing into your profile or something like that now. No, both you and I have badges already on wordpress.org. Um, repo. Do we, I think we do at least I do. I''m pretty sure you do. I just automatically assume you do because you have a plugin and you''ve contributed before as well.</p>\n\n\n\n<p>Um, so they have a number of badges for like plug-in team and theme team and, you know, translations and all of that. I, for some reason, I think the translation team does a pretty good job of incentivizing people. They seem to get a lot of non-English speakers involved with that. Maybe eventually that''s something that we look down, but, but yeah, I, I think, I dunno, we''re in, in, in, in our world, there''s, there''s a.</p>\n\n\n\n<p>Incentive for us to keep contributing. But like you said, you want to bring in new contributors in a new contributors would love to be recognized for their initial work. There is also, um, so what, what would be an example just to kind of wrap up this a little bit, uh, and then moving on, what would be an example of a badge that you think would be a good badge to have?</p>\n\n\n\n<p>Um, or how would that work? Like, for example, If I''m, if I''m making certain number of contributions, what would that badge look like? Would I have more than one? Would it just be one badge? And I just keep changing it out or what? I collect a series of badges in your, in your, in your idea.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> I feel like that''s too specific.</p>\n\n\n\n<p>I can''t answer that.</p>\n\n\n\n<p><strong>David Bisset:</strong> No problem. What I was thinking, what I thought was a pretty good badge when I was listening to your idea was like my first commit back. Or a first flight. Uh, and it''s usually like, it''s usually the easy ones, you know, how we in WordPress tag the easy, um, issues for beginners.</p>\n\n\n\n<p>So if they can get that and then get a badge real quick, that would be an instant gratification. And then kind of maybe move on from there.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> I think, I think if you call to have, for someone to map out, where are the typical. So I think of contributions, the contributor journey kind of as like a marketing or sales funnel.</p>\n\n\n\n<p>Um, and once you do that, um, a lot of the problems you can kind of frame the problems in a more easy to understand or well known kind of way. And then, you know, like a lot of the vague problems, like suddenly like kind of cooking to pace. So if you think about it from a contributor fan or like a contributors journey. Um, and you think about, you know, where the, um, common drop off points in that funnel. Um, you can actually kind of like put badges strategically in those pieces to incentivize people to kind of go over the hump. So for example, um, one of the one, like in my very, very limited experience, um, one of the difficulties is actually kind of wrapping your head around.</p>\n\n\n\n<p>Um, contributing to begin with works. Um, there isn''t really a good way to, to understand this a site from, um, going on mate, make wordpress.org. Um, and then from there they kind of like direct you to the slack. And then it''s like really tricky to even get onto the stack in the first place. And then you get on there and it''s just like a whole bunch of texts and you have no context or anything and it''s overwhelming.</p>\n\n\n\n<p>Um, so like, Again, this is like completely just an idea, but like, given that, you know, this, uh, is like, uh, um, identified common exit point. What can be done around there to both like, make that better, that, you know, um, iron out the, the huddles there, but then also on the users and other contributors and.</p>\n\n\n\n<p>Give them a badge. So like that''s how you get your level one comtributer a batch, for example, by, uh, I dunno, taking ticketing and a test that proves that you understand it. Are you not taking a test because everyone hates that, but you know what I mean? Right now, would you</p>\n\n\n\n<p><strong>David Bisset:</strong> support some sort of, um, certification process?</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Yeah, for sure. So I think that certification should be a part of the badgers. So like, you know, if you pass five tests, you get to level five and you know, that already should bump you up in the directory because they see you''ve, you''ve done a bunch of tests proving that, you know how to write a in well, properly security, then you should get like, 1.2 X the ranking versus somebody who hasn''t taken any of those tests and maybe writing a really crappy plugin</p>\n\n\n\n<p><strong>David Bisset:</strong> sounds like we need to create like a role-playing adventure.</p>\n\n\n\n<p>Just, just make it all, make it all contributor, you know, contributors and experience points and leveling up. And instead of getting a sword, I just get a better editor, but I really appreciate what you do. And we are sharing your opinions, especially in post-data slack. So, uh, look forward to seeing.</p>\n\n\n\n<p><strong>Lesley Sim:</strong> Yeah, same.</p>\n\n\n\n<p>Thanks, David.</p>\n\n\n\n<p>Okay.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Feb 2022 19:48: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: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:40:"WordPress.org blog: A New WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=12244";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2022/02/a-new-wordpress-news/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2413:"<img width="2560" height="1605" src="https://i1.wp.com/wordpress.org/news/files/2022/02/news_responsive_sizes-scaled.jpg?resize=2560%2C1605&ssl=1" alt="" class="wp-image-12279" />\n\n\n\n<p>In June 2021, <a href="https://profiles.wordpress.org/beafialho/" class="mention"><span class="mentions-prefix">@</span>beafialho</a> in collaboration with <a href="https://profiles.wordpress.org/pablohoney/" class="mention"><span class="mentions-prefix">@</span>pablohoney</a> <a href="https://make.wordpress.org/design/2021/06/03/redesign-of-wordpress-org-news/">floated the idea</a> of giving WordPress News a new look. Today, those ideas become a reality—we&#8217;re excited to share that redesign of <a href="https://wordpress.org/news/">WordPress News</a> is live!</p>\n\n\n\n<p>The new design leans on the aesthetics of jazz, intrinsically connected to WordPress and which ultimately translates its uniqueness, historic significance and future potential. Among other improvements, the new design leaves more space for content and includes new typefaces for better readability. It also uses a color palette intended to reflect the evolving Gutenberg language.</p>\n\n\n\n<img width="2560" height="1605" src="https://i0.wp.com/wordpress.org/news/files/2022/02/news_postpages-scaled.jpg?resize=2560%2C1605&ssl=1" alt="" class="wp-image-12260" />\n\n\n\n<img width="2560" height="1605" src="https://i2.wp.com/wordpress.org/news/files/2022/02/news_communitypodcast-scaled.jpg?resize=2560%2C1605&ssl=1" alt="" class="wp-image-12262" />\n\n\n\n<p>The revamp of the WordPress News page includes the header and footer of the page. We also shipped those two global elements to all pages of WordPress.org. However, there’s more work to do within the header to improve the information architecture. This new design is just the first, small step to modernize and improve the site iteratively. Any further discussion on future redesigns will occur in the <a href="http://wordpress.slack.com">#design channel on Slack</a>.</p>\n\n\n\n<img width="2560" height="1605" src="https://i1.wp.com/wordpress.org/news/files/2022/02/news_mobile_menu-scaled.jpg?resize=2560%2C1605&ssl=1" alt="" class="wp-image-12263" />\n\n\n\n<p>Take a look around and subscribe to WordPress News if you haven’t already. If you see something in the design that doesn’t look right, please submit an issue on <a href="https://github.com/WordPress/wporg-news-2021/">GitHub</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Feb 2022 17:56:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Kelly Hoffman";s: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:59:"Post Status: This Week at WordPress.org (February 14, 2022)";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:61:"https://poststatus.com/?p=93426&preview=true&preview_id=93426";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://poststatus.com/this-week-at-wordpress-org-february-14-2022/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10969:"<p>Each week we are highlighting the news from WordPress.org that you don''t want to miss.  If you or your company create products or services that use WordPress, we''ve got the news you need to know. Be sure to share this resource with your product and project managers.</p>\n\n\n\n<h2 id="h-news"><a href="http://wordpress.org/news">News</a></h2>\n\n\n\n<ul><li><a href="https://wordpress.org/news/2022/02/a-new-wordpress-news/">A New WordPress News</a></li><li><a href="https://make.wordpress.org/project/2022/02/11/a-theory-of-technology-adoption-in-the-wordpress-project/">A Theory of Technology Adoption in the WordPress&nbsp;Project</a></li><li><a href="https://make.wordpress.org/core/2022/02/16/wordpress-6-0-planning-roundup/">WordPress 6.0 Planning Roundup</a></li><li><a href="https://make.wordpress.org/core/2022/02/16/wordpress-5-9-x-release-team-and-5-9-1-schedule/">WordPress 5.9.x release team and 5.9.1 schedule</a><a href="https://make.wordpress.org/core/2022/01/26/preliminary-roadmap-for-6-0/"></a></li><li><a href="https://wordpress.org/news/2022/02/the-month-in-wordpress-january-2022/">The Month in WordPress – January 2022</a></li><li><a href="https://make.wordpress.org/test/2022/02/02/fse-program-exploration-all-things-media/">FSE Program Exploration: All Things Media</a></li></ul>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<hr class="wp-block-separator logo is-style-default" />\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<div class="wp-block-columns">\n<div class="wp-block-column">\n<h2 id="h-accessibility"><a href="https://make.wordpress.org/accessibility">Accessibility</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/accessibility/2022/01/08/accessibility-teams-goals-for-wordpress-6-0-and-beyond/">The Accessibility Team’s Goals for WordPress 6.0 and Beyond</a></li></ul>\n\n\n\n<h2 id="h-community"><a href="http://make.wordpress.org/community">Community</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/community/2022/02/15/meetup-organizer-newsletter-february-2022/">Meetup Organizer Newsletter: February 2022</a></li><li><a href="https://make.wordpress.org/community/2022/02/15/tuesday-training-topical-resources-for-meetup-organizers/">Tuesday Training: Topical Resources for Meetup Organizers</a></li><li><a href="https://make.wordpress.org/community/2022/02/16/proposal-refurbishing-camera-kits/">Proposal: Refurbishing Camera Kits</a></li><li><a href="https://make.wordpress.org/community/2022/02/08/discussion-diversity-in-wordpress-events/">Discussion: Diversity in WordPress Events</a></li><li><a href="https://make.wordpress.org/community/2022/02/07/2022-wordpress-community-support-financial-update/">2022 WordPress Community Support Financial Update</a></li><li><a href="https://make.wordpress.org/community/2022/02/04/upcoming-wpdiversity-events-february-2022/">Upcoming #WPDiversity Events: February 2022</a></li><li><a href="https://make.wordpress.org/community/2022/02/03/open-invitation-diverse-speaker-training-group-wpdiversity-zoom-call/">Open Invitation: Diverse Speaker Training group (#WPDiversity) Volunteers Zoom Call</a></li><li><a href="https://make.wordpress.org/community/2022/02/02/community-team-goals-2022-open-discussion-sessions/">Community Team Goals 2022: Open Discussion Sessions</a><a href="https://make.wordpress.org/community/2022/01/10/proposal-mandatory-safety-measures-for-in-person-wordpress-events-in-2022/"></a></li></ul>\n\n\n\n<h2 id="h-design"><a href="https://make.wordpress.org/design">Design</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/design/2022/02/14/design-share/">Design Share</a></li></ul>\n\n\n\n<h2 id="h-hosting"><a href="https://make.wordpress.org/hosting">Hosting</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/hosting/2022/01/10/wordpress-5-9-and-php-8-0-8-1/">WordPress 5.9 and PHP 8.0-8.1</a></li></ul>\n\n\n\n<h2 id="h-marketing"><a href="https://make.wordpress.org/marketing">Marketing</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/marketing/2021/12/01/help-contribute-to-social-media-materials-for-5-9-release/">Help contribute to social media materials for the 5.9 release</a></li><li><a href="https://make.wordpress.org/marketing/2022/01/25/social-media-drafting-update-for-5-9/">Social media drafting update for 5.9</a></li></ul>\n\n\n\n<h2 id="h-meta"><a href="https://make.wordpress.org./meta">Meta</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/meta/2022/02/10/new-wordpress-make-team-the-photo-directory/">New WordPress Make Team: the Photo Directory</a></li></ul>\n\n\n\n<h2 id="h-polyglots"><a href="https://make.wordpress.org/polyglots/">Polyglots</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/polyglots/2022/02/08/call-for-early-testers-glotpress-feedback-feature/">Call for Early Testers: GlotPress Feedback Feature</a></li></ul>\n\n\n\n<h2 id="h-plugins"><a href="https://make.wordpress.org/plugins">Plugins</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/updates/2022/02/15/plugin-review-team-14-february-2022/">Plugin Review Team: 14 February 2022</a></li></ul>\n\n\n\n<h2 id="h-mobile"><a href="https://make.wordpress.org/mobile">Mobile</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/mobile/2022/01/24/call-for-testing-wordpress-for-ios-19-1/"></a><a href="https://make.wordpress.org/mobile/2022/02/08/call-for-testing-wordpress-for-ios-19-2/">Call for Testing: WordPress for iOS 19.2</a></li><li><a href="https://make.wordpress.org/mobile/2022/02/08/call-for-testing-wordpress-for-android-19-2/">Call for Testing: WordPress for Android 19.2</a></li></ul>\n</div>\n\n\n\n<div class="wp-block-column">\n<h2 id="h-project"><a href="https://make.wordpress.org/project">Project</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/project/2022/02/11/a-theory-of-technology-adoption-in-the-wordpress-project/">A Theory of Technology Adoption in the WordPress&nbsp;Project</a></li></ul>\n\n\n\n<h2 id="h-core"><a href="https://make.wordpress.org/core">Core</a> </h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/core/2022/02/16/wordpress-5-9-x-release-team-and-5-9-1-schedule/">WordPress 5.9.x release team and 5.9.1 schedule</a></li><li><a href="https://make.wordpress.org/core/2022/02/16/wordpress-6-0-planning-roundup/">WordPress 6.0 Planning Roundup</a></li><li><a href="https://make.wordpress.org/core/2022/02/09/core-editor-improvement-curated-experiences-with-locking-apis-theme-json/">Core Editor Improvement: Curated experiences with locking APIs & theme.json</a></li><li><a href="https://make.wordpress.org/core/2022/02/09/cover-block-refactor-dev-note/">Cover Block Refactor Dev Note</a></li><li><a href="https://make.wordpress.org/core/2022/02/03/whats-new-in-gutenberg-12-5-february-2nd/">What’s new in Gutenberg 12.5? (February 2nd)</a></li><li><a href="https://make.wordpress.org/core/2022/01/31/ensuring-proper-attribution-for-contributions-to-wordpress-on-github/">Ensuring Proper Attribution for Contributions to WordPress on GitHub</a></li><li><a href="https://make.wordpress.org/core/2022/02/07/a-week-in-core-february-7-2022/">A Week in Core – February 7, 2022</a></li><li><a href="https://make.wordpress.org/core/2022/01/27/wordpress-5-9-simone-retrospective/">WordPress 5.9 ‘Joséphine’ Retrospective</a></li><li><a href="https://make.wordpress.org/core/2022/01/26/proposed-improvements-to-the-core-editor-chat-agenda-and-format/">Proposed improvements to the Core Editor chat agenda and format</a></li><li><a href="https://make.wordpress.org/core/2022/02/01/wp-notify-status-update/"></a><a href="https://make.wordpress.org/core/2022/02/01/wp-notify-status-update/">WP Notify Status Update</a></li></ul>\n\n\n\n<h2 id="h-test"><a href="https://make.wordpress.org/test">Test</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/test/2022/02/02/fse-program-exploration-all-things-media/">FSE Program Exploration: All Things Media</a></li></ul>\n\n\n\n<h2 id="h-docs"><a href="https://make.wordpress.org/docs">Docs</a></h2>\n\n\n\n<h4 id="h-developer">Developer: </h4>\n\n\n\n<ul><li><a href="https://developer.wordpress.org/themes/block-themes/converting-customizer-settings-to-block-patterns/">Converting customizer settings to block patterns</a></li><li><a href="https://developer.wordpress.org/block-editor/reference-guides/packages/packages-style-engine/">@wordpress/style-engine&nbsp;</a></li></ul>\n\n\n\n<h2 id="h-training"><a href="https://make.wordpress.org/training">Training</a></h2>\n\n\n\n<ul><li><a href="https://make.wordpress.org/training/2022/01/31/faculty-program-structure-proposal/">Faculty Program: Structure Proposal</a></li></ul>\n\n\n\n<h4 id="h-workshops">Workshops: </h4>\n\n\n\n<ul><li><a href="https://learn.wordpress.org/workshop/templates/">Templates</a></li></ul>\n\n\n\n<h4 id="h-lesson-plans">Lesson Plans: </h4>\n\n\n\n<ul><li><a href="https://learn.wordpress.org/lesson-plan/templates/">Templates</a></li></ul>\n\n\n\n<h4 id="h-courses">Courses:</h4>\n\n\n\n<ul><li><a href="https://learn.wordpress.org/course/simple-site-design-with-full-site-editing/">Part 1: Simple Site Design with Full Site Editing</a></li><li><a href="https://learn.wordpress.org/course/part-2-personalized-site-design-with-full-site-editing-and-theme-blocks/">Part 2: Personalized Site Design with Full Site Editing and Theme Blocks</a></li><li><a href="https://learn.wordpress.org/course/part-3-advanced-site-design-with-full-site-editing-site-editor-templates-and-template-parts/">Part 3: Advanced Site Design with Full Site Editing: Site Editor, Templates and Template Parts</a></li></ul>\n\n\n\n<h4 id="h-social-learning-spaces">Social Learning Spaces:</h4>\n\n\n\n<ul><li><a href="https://learn.wordpress.org/social-learning/">Calendar</a></li></ul>\n</div>\n</div>\n\n\n\n<div class="wp-block-spacer"></div>\n\n\n\n<div class="wp-block-media-text alignwide is-stacked-on-mobile has-background"><a href="https://poststatus.com/"><img src="https://cdn.poststatus.com/wp-content/uploads/2021/09/vertical-post-status-logo-250.png" alt="Post Status" class="wp-image-85823 size-full" /></a><div class="wp-block-media-text__content">\n<p class="has-text-align-left has-normal-font-size" id="h-get-ready-for-remote-work">You — and <a href="https://poststatus.com/business-membership/">your whole team</a> can <a href="https://poststatus.com/post-status-membership-club/">Join Post Status</a> too!</p>\n\n\n\n<p class="has-text-align-left has-small-font-size"><strong>Build your network. Learn with others. Find your next job — or your next hire.</strong> Read the <strong>Post Status</strong> <a href="https://poststatus.com/newsletter/">newsletter</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2709.png" alt="✉" class="wp-smiley" /> Listen to <a href="https://poststatus.com/podcasts/">podcasts</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png" alt="🎙" class="wp-smiley" /> Follow <a href="https://twitter.com/post_status/">@Post_Status</a>. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /></p>\n</div></div>\n\n\n\n<div class="wp-block-spacer"></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Feb 2022 16:41:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Courtney Robertson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:89:"WPTavern: #14 – Dave Smith, Isabel Brison and Joen Asmussen on the New Navigation Block";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=129791";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://wptavern.com/podcast/14-dave-smith-isabel-brison-and-joen-asmussen-on-the-new-navigation-block";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:59576:"<p>On the podcast today we have three guests… Dave Smith, Isabel Brison and Joen Asmussen.</p>\n\n\n\n<p>They’re all employed by Automattic, and whilst, as you will hear, they’ve had a variety of backgrounds, most recently they’ve been working on the new Navigation Block.</p>\n\n\n\n<p>Up until now WordPress menus have had their own dedicated area of the admin, but as of the most recent release of WordPress, 5.9, this has changed. If you have a block based theme you now create and edit menus in the block editor with the navigation block.</p>\n\n\n\n<p>Perhaps you were very happy with the way that menus have worked until now, but on the podcast today we explore why navigation was given such a large overhaul. It&#8217;s a complete break from the past and may need some getting used to for yourself, or possibly your clients.</p>\n\n\n\n<p>So why did this all happen? What was wrong with what we had until now?</p>\n\n\n\n<p>These are the topics that we discuss on the podcast today. Along with:</p>\n\n\n\n<ul><li>What are the options available in the new UI?</li><li>Does the navigation block have any benefits over a dedicated menu screen?</li><li>Will the classic way of doing things be supported?</li><li>What’s on the roadmap for the future of WordPress navigation?</li></ul>\n\n\n\n<h2 id="useful-links">Useful links.</h2>\n\n\n\n<p>To get in touch with the guests on the &#8216;Making WordPress&#8217; Slack:</p>\n\n\n\n<ul><li>Dave: @getdave</li><li>Isabel: @tellthemachines</li><li>Joen: @joen</li></ul>\n\n\n\n<p><a href="https://wordpress.org/support/plugin/gutenberg/">Gutenberg support</a></p>\n\n\n\n<p><a href="https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/">Full Site Editing Outreach Program</a></p>\n\n\n\n<p><a href="https://github.com/WordPress/gutenberg/issues/38275">Navigation Block Tracking Issue i3&nbsp;#38275</a></p>\n\n\n\n<p><a href="https://www.youtube.com/channel/UCfNHY9rIXHPUru_CiK0GcoA">Dave on WP (YouTube channel)</a></p>\n\n\n\n<p><a href="https://make.wordpress.org/test/2022/02/02/fse-program-exploration-all-things-media/">FSE Program Exploration</a> &#8211; call for testing</p>\n\n\n\n<p><a rel="noreferrer noopener" href="https://make.wordpress.org/core/tag/core-editor-summary/" target="_blank">Core Editor chat summaries</a></p>\n\n\n\n<p><a rel="noreferrer noopener" href="https://make.wordpress.org/core/2022/01/07/the-new-navigation-block/" target="_blank">The new Navigation block entry in the WP 5.9 release notes</a></p>\n\n\n\n<p><a href="https://wordpress.org/support/article/navigation-block/">Navigation Block</a> &#8211; an article explaining how the navigation block works</p>\n\n\n\nTranscript<div>\n<p>[00:00:00] <strong>Nathan Wrigley:</strong> Welcome to the Jukebox podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast which is dedicated to all things WordPress. The people, the events, the plugins, the blocks, the themes, and in this case, the new navigation block. Before we begin, I would encourage you to subscribe to the podcast so that you can get all the episodes automatically each and every week.</p>\n\n\n\n<p>You can do that by searching for WP Tavern in your favorite podcast player, or by going to WP tavern dot com forward slash feed forward slash podcast. And you can copy and paste that URL into most podcast players too. I&#8217;d really like to hear from anyone out there who would like to come onto the podcast and talk about whatever it is that you do with WordPress.</p>\n\n\n\n<p>It may be that you&#8217;re a developer, a WordCamp organizer, a contributor, a designer. Honestly, if it&#8217;s about WordPress, I&#8217;m really keen to hear from you. And hopefully get you on the show. Head over to WP tavern. dot com forward slash contact forward slash jukebox. And use the contact form there.</p>\n\n\n\n<p>So, on the podcast today, we have three guests, Dave Smith, Isabel Brison and Joen Asmussen. They&#8217;re all employed by Automattic and whilst, as you will hear, they&#8217;ve had a variety of backgrounds, most recently they&#8217;ve been working on the new navigation block.</p>\n\n\n\n<p>Up until now, WordPress menus have had their own dedicated area of the admin. But as of the most recent release of WordPress, 5.9, this has all changed. If you have a block-based theme, you can now create an edit menus in the block editor with the navigation block. Perhaps you were very happy with the way that menus have worked until now, but on the podcast today, we explore why navigation was given such a large overhaul.</p>\n\n\n\n<p>It&#8217;s a complete break from the past and may need some getting used to by yourself, or possibly your clients. So why did all this happen? What was wrong with what we had until now? Well, these are the topics that we&#8217;re going to be discussing today. Along with: what are the options available in the new UI? Does the navigation block have any benefits over a dedicated menu screen? Will the classic way of doing things be supported. And what&#8217;s on the roadmap for the future of WordPress navigation.</p>\n\n\n\n<p>If you&#8217;re interested in finding out more, you can find all the links in the show notes. Head over to WP tavern dot com forward slash podcast. And look for episode number 14. And so without further delay, I bring you, Dave Smith, Isabel Brison And Joen Asmussen.</p>\n\n\n\n<p>I am joined on the podcast today by three people. I&#8217;m not sure that we&#8217;ve done this too often in the past, but three people we have with us today. We have in no particular order, Isabel Brison, Dave Smith, and Joen Asmussen. We&#8217;ll go through one at a time, perhaps if we start with Isabel and then go to Dave and then Joen toward the end, and just introduce yourselves, tell the listeners who you are, and how come you&#8217;re on the podcast today talking about navigation menus in WordPress.</p>\n\n\n\n<p>[00:03:44] <strong>Isabel Brison:</strong> Hi, I&#8217;m Isabel. I am a front-end engineer at Automattic. I&#8217;m dedicated full-time to working on WordPress. That means Gutenberg most of the time. And I&#8217;ve been working on the navigation block for, oh, I don&#8217;t know. It feels like a year probably I&#8217;ve have been mostly dedicated to that. It&#8217;s an extremely complex block. That&#8217;s why it took so long to get it ready.</p>\n\n\n\n<p>[00:04:10] <strong>Nathan Wrigley:</strong> Well, thank you, and Dave.</p>\n\n\n\n<p>[00:04:12] <strong>Dave Smith:</strong> Yeah. Hi, I&#8217;m Dave Smith. I&#8217;m getdave on core Slack, and get underscore dave on dot org annoyingly. I&#8217;m a software developer and based in the UK. And I also work for Automattic. Been here for about three years now. Before that I worked at various digital agencies using WordPress. So I must&#8217;ve used it for about 10 years now, I guess. But I&#8217;m lucky enough now that I get to contribute full-time to the Gutenberg editor and that&#8217;s part of Automattic&#8217;s five for the future commitment.</p>\n\n\n\n<p>And of course I&#8217;m principally focused on all aspects of navigation and particularly the block, which is presumably why I&#8217;m here today. I also run a YouTube channel called Dave on WordPress, where I try to provide my insights as a full-time Gutenberg developer on how to best make use of the block editor.</p>\n\n\n\n<p>[00:04:56] <strong>Nathan Wrigley:</strong> Thank you very much Dave, I will make sure that the link for your YouTube channel and various other bits and pieces do make it into the show notes, but that&#8217;s very kind of you, and finally Joen.</p>\n\n\n\n<p>[00:05:06] <strong>Joen Asmussen:</strong> Hello? Yes, I&#8217;m Joen. I&#8217;m a product designer in Denmark for Automattic. I have been working on the block editor project ever since the beginning and the navigation block for more than a year. It has been fun.</p>\n\n\n\n<p>[00:05:19] <strong>Nathan Wrigley:</strong> Thank you very much indeed. So obviously we&#8217;ve got the panel. If we were to be talking about WordPress navigation and the future of WordPress navigation, you really are the people to be discussing it with. So just last week, we&#8217;re recording this at the very beginning of February, just last week, The way that menus are handled within WordPress got a bit of a shakeup. You&#8217;ve been thinking about it for a long, long time, but the vast majority of WordPress users probably came across it for the first time this week. I don&#8217;t know who wishes to answer this, it doesn&#8217;t really matter. You could all overtalk each other or interrupt, that&#8217;s completely fine by me. Why do we now have a navigation block and why are we no longer using the tried and trusted appearances menu section. What&#8217;s the point of that?</p>\n\n\n\n<p>[00:06:05] <strong>Dave Smith:</strong> Yeah, absolutely. I&#8217;m happy to give that a go if you would like. So menu system in WordPress has obviously existed for quite some time, and we&#8217;re now calling that the classic menu system. And that&#8217;s where you go into WP admin. You go to the menu screen and you can start building out your menu from there.</p>\n\n\n\n<p>But obviously with the advent of Gutenberg, and particularly with the advent of full site editing, we&#8217;re moving towards say a, sort of a more wysiwyg approach or direct editing paradigm. If you will, whereby we want to be able to create things directly in the site editor canvas. So that we have a one-to-one representation between what you see in the editor and what you see on the front of your site.</p>\n\n\n\n<p>So the goal of the navigation block is really to facilitate that within the editor. So it&#8217;s part of a new way of building out menus in WordPress, and really, it gives you a lot more control over the style, but it also removes that disconnect that we felt with the menu screen perhaps. As I said, I worked in agency background previously and I worked with a lot of clients and they often struggled to understand, I&#8217;m editing this menu, this navigation in the menu screen. How is that actually going to affect what I see on the front of the site? We&#8217;re hoping that with the new navigation block, it becomes a lot easier to appreciate that, because all you do is you go into the site editor, you look for where your navigation is that you see on the front of your site, within the editor and you start making changes directly there. You hit save, and on the front of your site, you get to see exactly the same. And that&#8217;s really, really powerful. And I think that&#8217;s the principle reason why we, why we started on this project, but, Joen and Isabel might have some other insight as well.</p>\n\n\n\n<p>[00:07:42] <strong>Nathan Wrigley:</strong> Yeah, feel free Joen or Isabel to give us your take on that as well please.</p>\n\n\n\n<p>[00:07:46] <strong>Isabel Brison:</strong> I think on top of that, we&#8217;ve tried to create more flexibility regarding the navigation layout. Yes, it&#8217;s the visual experience of being able to edit the navigation in place, but it&#8217;s also that you can now do a lot more with that navigation in terms of positioning the elements and putting in other elements that did not fit into a classic menu, such as your site logo or a search bar, and displaying them as an overlay or not. So there&#8217;s a bunch new things that we can do with the navigation in terms of layout that are a lot more complex than we used to be able to. Or things that possibly could be done by a theme, but then they were fixed in that theme, and you wouldn&#8217;t have the opportunity to customize them.</p>\n\n\n\n<p>[00:08:29] <strong>Nathan Wrigley:</strong> Thank you very much, and Joen it sounded like you had something to contribute there.</p>\n\n\n\n<p>[00:08:33] <strong>Joen Asmussen:</strong> Yeah. So I think those were some great points already made. I would add that one of the aspects of the navigation block is specifically that it is a block. The idea being that with the block editor, everything is a block, widgets embeds, all of it is blocks. And so once you learn the block editor, ideally, the jump to full site editing, in some cases it just means the addition of the header and the footer in the same canvas become available using the same block interface. So ideally, less to learn because you already know how to use the block editor.</p>\n\n\n\n<p>[00:09:09] <strong>Nathan Wrigley:</strong> The thing which I, well the takeaways which I have from my brief forays into using the navigation block are, number one to Dave&#8217;s point, the fact that it&#8217;s all happening on the screen is really, it&#8217;s quite interesting. It made me sort of sit up and think, okay, this is where it is now. This is new, this is interesting. I never quite found the difficulty in having a menu section. I think after a certain period of time, it kind of became instinctive. But then again, I was always playing with WordPress pretty much all day, every day. So I think Dave&#8217;s point is a really good one.</p>\n\n\n\n<p>Now everything&#8217;s handled in the same place. The UI is the same. It&#8217;s easy to understand. And speaking to Isabel&#8217;s point, the fact that you can surround your navigation with whatever you choose. It&#8217;s no longer just what the theme handles. It can be anything, you know, so you could put a logo right next to it, or a button to the right of it, or anything you like. You can just surround it by other blocks if you so choose. So I can see that promise is really good. Are you happy with the implementation that you&#8217;ve got at the minute? Because obviously, there&#8217;s things which I&#8217;m sure you&#8217;ll be telling us later about roadmap features and so on. Do you feel that the jump, which people are going to have to go through on day one, so if they install a block-based theme and they&#8217;re suddenly confronted with navigation being something that&#8217;s done inside the block editor, do you feel that the UI is intuitive at the moment or are there things that you would like to have. Implemented fairly soon?</p>\n\n\n\n<p>[00:10:37] <strong>Joen Asmussen:</strong> I can take a quick stab I think it&#8217;s important to look at what is available in the block today and you can import an existing menu, you can create a new one from scratch, you can swap menus, you can edit them, move these blocks around. You can collapse it into this little hamburger menu with a toggle in the sidebar, and instantly you see the effect in the canvas. You see it becomes that little menu button. You can create all these sub menus, build them visually. There are a number of styling options available. And in fact, you can accomplish some pretty complex layouts by combining this block, as you just said, with a number of other blocks. And being such a key part of full site editing it is in almost every website. The very header that makes up your primary point of interaction. It was very important to get the block out there, and I think with the experience we are shipping in 5.9, and the features it&#8217;s definitely ready to get some feedback. But I would also say that 5.9 is a great opportunity to find out some of those rough edges and figure out how to prioritize the next steps. There&#8217;s a lot of work to be done still. Some of those changes affect the block editor directly, like selecting the right block, moving it around, the right nesting level. All of these things, when fixed in the block editor itself, improved in the block editor itself, elevate the rest of the block editor UI. For example, the gallery block is also receiving nesting. So whatever we can improve there, will benefit both navigation and other nested blocks as well. So there&#8217;s definitely lots to do still, but it&#8217;s in a good place to use on your website even today, I would say.</p>\n\n\n\n<p>[00:12:25] <strong>Nathan Wrigley:</strong> Thank you. Dave or Isabel.</p>\n\n\n\n<p>[00:12:27] <strong>Isabel Brison:</strong> I agree with that assessment. I think it&#8217;s in a good place. And I think Joen said something very interesting here, which is, a lot of the improvements that we can make to it, our general block editor improvements. So things that will make the experience of nested blocks better. We&#8217;ll also as a consequence, make the navigation block, which is a series of nested blocks better.</p>\n\n\n\n<p>I&#8217;m looking in particular to few accessibility issues. You mentioned accessibility earlier. I&#8217;d say, yeah, there are points that can be improved at the moment, particularly with keyboard accessibility, but those are overwhelmingly issues that affect the editor as a whole. So the nested blocks are complicated structures that we&#8217;re still working through in terms of usability.</p>\n\n\n\n<p>So there are definitely improvements to look out for in the near future with regards to that.</p>\n\n\n\n<p>[00:13:19] <strong>Nathan Wrigley:</strong> Thank you, Dave.</p>\n\n\n\n<p>[00:13:21] <strong>Dave Smith:</strong> Yeah, absolutely, and all the points that&#8217;ve made so far been really accurate and really great. I think there&#8217;s also two ways of looking at this, because you can have coming to the navigation block from a classic world of WordPress and you&#8217;ve already used WordPress and it&#8217;s something you&#8217;re familiar with and you&#8217;re familiar with the menu screen. Or you can be coming to WordPress as a brand new user, you&#8217;re landed in full site editing and you experience navigation block. And I think there&#8217;s going to be two perspectives then, two different experiences. And as I said previously again, I worked for agencies and I can imagine some of the clients I used to work with. They&#8217;ve got familiar with the menu screen. They&#8217;re very happy with how it works. They&#8217;ve worked around the quirks of it, and then they are being asked to use this completely new interface. And obviously with any change like that, there&#8217;s going to be a bit of friction. There&#8217;s going to be a bit of pushback, and there&#8217;s going to be some overhead for people who&#8217;re having to teach these people how to use the new interface.</p>\n\n\n\n<p>But again, the direct editing paradigm really makes things a lot easier because the overhead to learning how to use this new system is much, much lower. It is. Point and click, change things that are there and they&#8217;ll look like that on the front of the site. And that&#8217;s a really big win. And that also carries over really nicely into first-time WordPress users, because they won&#8217;t have that backstory of having used the existing menu screen. They will be probably familiar with other systems where they are more of a wysiwyg system, what you see is what you get, and that&#8217;s the acronym. And they will be familiar with something where they can just point and click and change things. And I think that really helps. So, yes, I definitely definitely agree, there are rough edges around the block. It is a V1, but we&#8217;re looking for feedback from WordPress 5.9, so if people have that feedback, they find these edge cases, all these frustrations, the best thing to do is to let us know. And yeah, we can look to address those in future releases as required.</p>\n\n\n\n<p>[00:15:10] <strong>Nathan Wrigley:</strong> Dave, could I ask at this point, given that that&#8217;s the case and you are looking for feedback actively, what is the best way that people could provide that feedback?</p>\n\n\n\n<p>[00:15:19] <strong>Dave Smith:</strong> Yeah, absolutely. There are a number of ways, different people might find different channels helpful. I think perhaps one of the first ones might be the Gutenberg plugin forums, which you can reach at wordpress dot org, we&#8217;ll put a link to those, and there are plenty of contributors who go into those forums and regularly check them for people who are providing feedback.</p>\n\n\n\n<p>Also there&#8217;s the full site editing outreach program, which is run by Anne McCarthy. Who&#8217;s a colleague of ours at Automattic. And she often has these series of sessions where we&#8217;ll go out saying we&#8217;re going to focus down on one particular aspect. And so there might be opportunity to provide feedback. There&#8217;s also make blog posts that came out, around these topics, which you can follow up with and leave your comments there. And there&#8217;s obviously also Github as well, where you can raise issues about your frustrations. Or if you&#8217;re really, really keen, you could join us in WordPress core Slack, everyone&#8217;s a friendly bunch and, you can just drop into the channels and say, hey, I&#8217;ve got this frustration, I&#8217;ve got this feedback. And someone will pick up that, and put you in the right direction and help you to get an answer and resolve those things. Joen and Isabel, have you got any other suggestions? You probably know some more, other interesting places.</p>\n\n\n\n<p>[00:16:28] <strong>Joen Asmussen:</strong> I thought that was very exhaustive. I would only echo that we are very appreciative of all these thoughts. One of the opportunities we have with listening to that feedback and the plugin model where we can land features in the plugin. Already now, if you install the plugin, you&#8217;ll see some changes based on what we&#8217;ve learned already with the first set up state for the navigation block, it&#8217;s already being tweaked in the plugin. So we can react relatively quickly, and you can see those changes in the plugin and then eventually they&#8217;ll land in the next version. So definitely don&#8217;t hold back on the feedback.</p>\n\n\n\n<p>[00:17:04] <strong>Nathan Wrigley:</strong> Just for the benefit of users, when you, I think it&#8217;s probably clear to all of us what you&#8217;re describing there, when you say the plugin, just explain for the listeners who perhaps don&#8217;t know what that step involves and what it means.</p>\n\n\n\n<p>[00:17:16] <strong>Joen Asmussen:</strong> Thank you, and I do apologize. So the Gutenberg plugin was the plugin project to create the block editor, way back for WordPress five point zero. And it has since become the testing ground for development. So what happens is we work in Github on the Gutenberg project to create these new features, fix these bugs. And then every, I think it&#8217;s every two weeks we land these new features in the Gutenberg plugin, so you can test them out. It&#8217;s fairly stable and we definitely push patches to make sure it&#8217;s pretty stable. It&#8217;s not going to be quite as stable as the full WordPress releases 5.9, 6.0 and so on. But it is a way to preview what&#8217;s coming next. You can activate the plugin, just search for Gutenberg in the plugins page. You can activate it, see these new things. You can deactivate it again if you like.</p>\n\n\n\n<p>[00:18:10] <strong>Nathan Wrigley:</strong> That clarifies it beautifully. So the intention there is that if you want to live on the bleeding edge and be involved with seeing what&#8217;s coming with Gutenberg, and in this case the navigation block, then that is the process that you would go through and you&#8217;ll be using something which may not be mission critical ready, but we&#8217;ll certainly be a lot of fun to play with, that&#8217;s for sure.</p>\n\n\n\n<p>I don&#8217;t know who wants to take this one, but working on the basis that some of the listeners by now simply will never have touched WordPress 5.9. Would one of you take on the onerous task of trying to describe the differences in the UI? So I&#8217;m meaning things like the fact that we&#8217;ve now got edits site as a menu option. The fact that the traditional area where you would go and customize things, the customizer has been removed, if you use a block based theme. And then moving on to, how do you actually get a navigation area onto the website and, what&#8217;s the process that you go through basically? I know there&#8217;s an awful lot to unpack there, but it just occurs to me that there&#8217;ll be quite a lot of people who haven&#8217;t yet tried 5.9. Maybe they have, but they&#8217;ve stuck with their old theme and they don&#8217;t wish to dabble. So we&#8217;re trying to persuade them I think that it&#8217;s not as difficult as it sounds.</p>\n\n\n\n<p>[00:19:23] <strong>Joen Asmussen:</strong> I could take a quick stab because I think it could be worth it to clarify one thing right upfront. That existing WordPress themes should work just as they already do, with the existing navigation screen and all that stuff. The new navigation block would be available for the block editor, but the site editor is primarily available when you activate a block theme. For example, Twenty Twenty-Two, which is just the most beautiful theme. If you haven&#8217;t seen it yet, I definitely recommend, just take a look, try it out. It is the most wonderful thing I&#8217;ve seen in a decade. And notably, if you are a WordPress developer, do download that theme, unpack the zip, take a look at the structure and see how it&#8217;s built. It is something else, makes me very excited about the future of theme development.</p>\n\n\n\n<p>You can also mix and match between block themes and let&#8217;s call it classic themes, towards these hybrid themes. So you can, sort of, gradually opt to these new paradigms. But assuming you activate Twenty Twenty-Two today on a fresh install and you want to see all the new stuff, you go into appearance, you have this edit site button which lets you see the whole of Twenty Twenty-Two. Header and footer and the loop in the middle. With everything being blocks, you can click everything and edit it right there. It should be pre-populated because it comes with these templates, it already includes a header. It already includes a place for your navigation. So ideally the experience is that you activate this theme, you click the navigation block and then you, you start the flow, either create a new menu from scratch or import an existing</p>\n\n\n\n<p>[00:21:07] <strong>Dave Smith:</strong> Great points that Joen&#8217;s made that. One of the key things, if you&#8217;re more of a developer mindset as well, is that we&#8217;ve moved away from a lot of the theme chrome as you might say. So that things like the header, the footer, the sidebar, instead of those being controlled via PHP templates in the theme, they&#8217;re now controlled via the site editor, with this again, direct manipulation paradigm, which I keep going on about, but it&#8217;s so critical to how full site editing editing works.</p>\n\n\n\n<p>And so you can just go in and previously you&#8217;d have to, as a user, if you want to change, I don&#8217;t know, let&#8217;s say something like, you&#8217;ve got a list of posts and you&#8217;ve got an avatar picture of yourself, next to each one of those posts. You say, oh, actually, do you know what? I want to move my avatar over to the right hand side.</p>\n\n\n\n<p>Now in classic WordPress, the only way you could do that is either you&#8217;d have to dig into the template files and understand a bit of PHP and HTML and move that and possibly, change some CSS styling as well. But with full site editing, what you can do is just go straight into the loop, like Joen&#8217;s mentioned, click on the avatar, the author, avatar and manipulate it however you&#8217;d like with the controls that the editor provides you. Now, of course you may not have all the controls you want from the get go, especially with 5.9. But the goal is that you can just do that directly and you don&#8217;t have to go then to your developer or your technical person to get that done.</p>\n\n\n\n<p>And I think it&#8217;s like really democratizing design. We talk about this a lot of time in WordPress, democratizing publishing, but this is like democratizing the design of themes and of your site and giving users power. I hear a lot of, this is a scary thing to a lot of people, and I get that. I come, as I said, from an agency background and I&#8217;d be thinking, goodness, me, I don&#8217;t want to give my clients too much control, lest they do something to their site that would be less than desirable. But, I think we give the controls to be able to lock a lot of these features down and those will only improve.</p>\n\n\n\n<p>But the key thing is that if you&#8217;re someone who just wants to start a website and you don&#8217;t have the technical expertise, you can do so much more now with full site editing, than you could ever do with classic themes without having to have that technical knowledge. And I think that&#8217;s a key thing.</p>\n\n\n\n<p>[00:23:18] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s a nice answer. Isabel, anything to add there?</p>\n\n\n\n<p>[00:23:21] <strong>Isabel Brison:</strong> Yeah, to add specifically to the issue of it being scary that people have all these power. That won&#8217;t necessarily happen. It depends also on how the theme is structured. So you can implement controls in the theme to limit the amount of editability of the various site areas.</p>\n\n\n\n<p>So that&#8217;s something that would potentially also be very convenient for agencies to use. It makes it a little bit less scary.</p>\n\n\n\n<p>[00:23:47] <strong>Nathan Wrigley:</strong> Yeah. Good point. The way that you would interact with it then is you have a block. The best way to describe it really would be to go and install Twenty Twenty-Two and as Joen said, click on the navigation block, perhaps open up the list view. In fact, I would say, open up the list view first and you&#8217;ll be able to see the stack of things that may or may not be contained within the navigation. So for example there may be sub-pages that you&#8217;ve listed depending on how the menu is structured. And so let&#8217;s get into what the sort of features are that you can have inside of the navigation block.</p>\n\n\n\n<p>If we click on the navigation block itself, we&#8217;re presented with some features in the menu on the right, some styling options and so on. So tell us what&#8217;s there at the moment. What can we configure? What can we change? Whoever wishes to take that.</p>\n\n\n\n<p>[00:24:34] <strong>Isabel Brison:</strong> One thing I think it&#8217;s very important to keep in mind when we start working with the navigation block is, we create the block and let&#8217;s say we add a bunch of pages to it, links maybe a few social icons, whatever we want inside it. And then the block is saved and the contents of that block are going to be reusable in others. So I can have exactly the same navigation in two different templates. I can have it on my header and then again on my footer, and the changes that I make to the content of the navigation are going to be reflected in all the places that it&#8217;s used. But in terms of the presentation, that will be specific to the place where the navigation is.</p>\n\n\n\n<p>So we have this difference between what the content is, so the links that make up the navigation, and then the presentational aspects that will be specific to wherever. So in the navigation being used in the header, it might have a background color. It might be set to be a hamburger menu on desktop and mobile.</p>\n\n\n\n<p>And then the very same navigation being reused in the footer might have no background color. It might be set to always show all the links, and not turn into a hamburger at any point. So there&#8217;s this distinction that&#8217;s important to make between the presentation.</p>\n\n\n\n<p>There&#8217;s a lot you can change, well you can change the colors. You can change the layout, you can move it to align on left on the right or the center. If you have sub menus, you can configure those sub menus to open on hover or on click. As I mentioned, Joen also mentioned the hamburger menu. You can make it display as a hamburger menu on mobile or all the time or never. There are topography settings, padding settings. That&#8217;s probably the lot. I&#8217;m not sure if I&#8217;m forgetting something here.</p>\n\n\n\n<p>[00:26:27] <strong>Nathan Wrigley:</strong> I think that&#8217;s right, certainly from what I&#8217;m looking at at the moment that it appears that you&#8217;ve covered everything, unless one of the other two of you have got something that we&#8217;ve missed.</p>\n\n\n\n<p>[00:26:36] <strong>Dave Smith:</strong> It is difficult to describe the UI, isn&#8217;t it? I think there&#8217;s a pretty good developer, not developer doc, a user facing doc for the block as well. And that was put together by Anne McCarthy. Again, that goes over a lot of these options. If people want to read that afterwards as well, and that&#8217;s kind of helpful.</p>\n\n\n\n<p>[00:26:49] <strong>Nathan Wrigley:</strong> Joen?</p>\n\n\n\n<p>[00:26:50] <strong>Joen Asmussen:</strong> Yeah, I would just add that it&#8217;s worth noting that these are the user-facing controls where you can configure and tweak and adjust in that way. There are some additional controls that aren&#8217;t yet surfaced to the user. We have this system called global styles, which ultimately is this reflection of properties in the theme dot json file.</p>\n\n\n\n<p>And you can target specific sub blocks and add padding to those, and change these right in the code. The idea being that these properties would be reflected in the UI as well, at least as a rule of thumb. Some of those are on the to-do list. Some of them are already there, like Isabel mentioned fonts, colors, and line height, all that stuff.</p>\n\n\n\n<p>And of course, ultimately we&#8217;re making markup here, and you could style things in CSS if that is your preference, provide some defaults in that way.</p>\n\n\n\n<p>[00:27:45] <strong>Nathan Wrigley:</strong> It might be a good idea to draw some comparisons with current themes. It seems like a lot of theme developers have really made things like menus and navigation and headers and footers make them a real feature of their work, and I can think of some, dot org themes as well as commercially available themes where the menus, the customization options that are there, are truly remarkable, you know, within the customizer, you can change more or less everything. You could have a logo that center aligned and you could have different fonts and hover effects and all of that kind of stuff. And it&#8217;s all available there in a sort of point click interface. I&#8217;m just wondering if there are things that, well any comparisons to be made? Are there any things that you are hoping to achieve in the near future that might bring some parity to those edge cases? Or is it very much going to be that WordPress is sticking with, here it is, it&#8217;s a menu, you can figure out how to do the styling yourself. You can learn a bit of CSS and what have you. I don&#8217;t know if it&#8217;s all going to be point click or if there&#8217;s going to be some sort of technical requirement to make them super individual</p>\n\n\n\n<p>[00:28:47] <strong>Joen Asmussen:</strong> I can take a stab. I think the key feature of the navigation block. I apologize if I&#8217;m repeating myself, is that it is a block, which means you can insert it in patterns as well. A block pattern is a configuration, an already made configuration of a bunch of blocks. You click the blue plus button at the top left corner. You click patterns and you can insert this shortcut to a layout. Twenty Twenty-Two comes with a number of these header patterns pre-made, and they&#8217;re all completely beautiful. So you can browse those and you can insert this header that has maybe a circular logo and a tagline than the navigation below. Or you could find one that has the logo on the left, and the navigation collapsed into the hamburger on the right. And you can just insert one of those. And the entire layout is pre-made and pre inserted, wherever you like. And I think that is one of the key benefits of it being a block, that every single benefit, every single feature we add to the block itself will benefit the navigation block as well in the future. Any global style changes, any new features to fonts, font weights, or paddings, margin, spacing, gap colors, nested changes. All of those will benefit across all of blocks, rather than just for this one piece of software called the navigation block.</p>\n\n\n\n<p>[00:30:18] <strong>Nathan Wrigley:</strong> Yeah, I think you made a really good point at the start and maybe it&#8217;s something that we haven&#8217;t really dwelled on enough, is that it is a block, so it can go anywhere. So, you know, should you wish to have a page full of navigation menus, you could do that. I don&#8217;t know why you would wish to do that, but you could. Whereas in the past that would be probably out of bounds, for the expertise level of most people. They would just be happy with what came along with the theme.</p>\n\n\n\n<p>And there it is right at the top usually, and probably something in the footer. But you could create, I don&#8217;t know, a layout where there were menus in sidebars of different types and menus all over the place. And that&#8217;s the point. It can be surrounded. You can put things in front of it, behind it, above it, below it, whatever you want. And maybe we haven&#8217;t made that point strongly enough.</p>\n\n\n\n<p>[00:31:00] <strong>Dave Smith:</strong> It&#8217;s a really, really good point? And it also comes back to, you know, getting back to your question it&#8217;s like, what can you achieve with a block versus what could you achieve with a classic menus system? And I think if we compare sort of a classic theme experience with a block theme experience. With the classic theme, if you want to style your navigation, your menu, all the control is really requires quite a lot of technical expertise, whether that be CSS styling, or changing the layout in terms of the ordering of things or where the actual navigation is placed. I mean, you might not want it in the header, you might want it below the logo or et cetera. And for that, you would need a developer. Contrast that to block themes, and as Joen says, it&#8217;s a block. So you can put your navigation wherever you like. It&#8217;s really opened up that power. And again, with styling, you&#8217;ve got all the power that the block provides, and that is actually quite a lot.</p>\n\n\n\n<p>And I think that the barrier to entry for customizing your navigation has gone down considerably. Obviously with classic WordPress and all WordPress, you can install plugins and there will always be extenders that create these amazing systems that allow you to modify your menus. But I think there&#8217;s also opportunities for that with the block editor, and I&#8217;m sure that we&#8217;re going to see the extender community building on top of the block and creating really exciting, really, really powerful things. Perhaps sort of mega menu builders and things like this will come.</p>\n\n\n\n<p>I&#8217;m excited to see what happens and what comes down the line. Also if we&#8217;re talking about some limitations of the block at the moment, specifically things that I&#8217;m aware of are the ability to style interaction states. And by that, what I mean is, imagine when you&#8217;re hovering over your navigation. Sometimes you see the style of the item you&#8217;re hovering over change, when you roll over it with your mouse or when you select it, focus it with your keyboard. And that&#8217;s not something you can do currently. You can&#8217;t change the style of that within the editor. So that&#8217;s one thing, and also like spacing and padding control for the menu items themselves. I don&#8217;t believe we can do that at this current time, but they&#8217;re all things that are on the roadmap and they&#8217;re looking to be addressed in future releases of WordPress.</p>\n\n\n\n<p>And of course, there are always going to be certain advanced customization things that are always going to require CSS, and you can still do that. So if you need something really specific, really custom, you can still ask your technical person or you can jump in to learn CSS yourself, and that&#8217;s a great way to do it.</p>\n\n\n\n<p>[00:33:13] <strong>Nathan Wrigley:</strong> Thank you. Isabel?</p>\n\n\n\n<p>[00:33:15] <strong>Isabel Brison:</strong> Yeah. Well in terms of limitations or things that we have on our roadmap, rather like add-ons, I guess. A very interesting challenge will be mega menus, creating more complex drop downs, and that will be a challenge partly for semantic reasons because we had a lot of work in trying to keep a semantic structure for the navigation, with all the different types of blocks that can fit in there.</p>\n\n\n\n<p>And mega menus will present the furthest step in that challenge. Which will be great to work on. And the other thing that I think would be good to see is the ability for extenders to add child locks to the nav. So say someone has, I don&#8217;t know, an e-commerce plugin, there&#8217;s sort of a products block that currently the nav only takes a very limited set of blocks that are hard-coded. And so one of the things that we will work on in the future is to make it possible for other blocks to be added. If a plugin has specific blocks that might suit the nav.</p>\n\n\n\n<p>[00:34:15] <strong>Nathan Wrigley:</strong> Turning attention towards accessibility. Probably reasonably briefly, but nevertheless an important part of any menu structure, the ability for people with different capabilities or different ways that they&#8217;re interacting with the internet. Has a lot of thought gone into that? Was that a particular challenge? Have you endeavored to make this as easy to use for everybody as possible?</p>\n\n\n\n<p>[00:34:37] <strong>Isabel Brison:</strong> Yes. A lot of thought went into them. Well, yeah. a lot of thought went into the front end and that was why I mentioned the semantics earlier. We had to get it right for the structure of the navigation to make sense. When you&#8217;re navigating the page with various assistive technology, In terms of the interface itself for those who are editing a navigation block. Yes, but there&#8217;s always things that we can improve. So we&#8217;ve done a fair bit of work in that sense, but not specific as I think I mentioned earlier, there are not a lot of challenges that are specific to the navigation block in that area. There might be one or another issue, I think there might be a couple of issues, small things such as a button that&#8217;s specific to the block toolbar that&#8217;s not putting focus in the right place when it closes whatever. I mean 99% of accessibility issues that we have flagged for the navigation block that we have opened on our repo are issues that are transversal to other blocks.</p>\n\n\n\n<p>[00:35:38] <strong>Dave Smith:</strong> Yeah, I definitely agree with that. I was putting together the new tracking issue for the navigation block, post 5.9. And if anyone is interested that&#8217;s 3 8 2 7 5 in Github. As part of that, one of the things that we want to focus on, was the accessibility and just put that of front and center from the start. A high priority item as we move forward with future releases, just keeping that like right there. So we&#8217;re not losing sight of that, and it&#8217;s really, really important and we continue to work with the WordPress accessibility to community on it.</p>\n\n\n\n<p>[00:36:07] <strong>Nathan Wrigley:</strong> Joen?</p>\n\n\n\n<p>[00:36:08] <strong>Joen Asmussen:</strong> Yes, I would add also that one of the best features of the navigation block, yet another reason why it took a while to get right. Isabel mentions the semantics, but the thing is when you use the navigation block, what is output all the front end, whether it is sub menus or even just the basic menu, or even the overlay is all fully accessible and you don&#8217;t have to worry about that aspect on its own. For example, by default the menu, you tab through it and menu items open on hover and sort of the classic menu default way for WordPress. But you can change that so that sub menus open on click instead. There&#8217;s even some details around how that little triangle dropdown for sub menus has a separate focus item. So you could focus the parent menu item, go to that or focus the sub menu toggle to open the sub menu. There&#8217;s a great deal of nuance to how you navigate through a menu. And the hamburger opens a proper modal that you have to close with escape and it traps the tab inside until you&#8217;re done.</p>\n\n\n\n<p>So there&#8217;s a great deal of energy already put into making sure that your website will be accessible when you use the navigation block. There&#8217;s always going to be additional work to do. Work is never over, but, there&#8217;s quite a lot of stuff already there which simply will improve and be there for any block theme that uses this block without the theme developer having to implement this accessibility themselves.</p>\n\n\n\n<p>[00:37:49] <strong>Nathan Wrigley:</strong> The three of you, we never really established this at the beginning, is the navigation block, is this your primary focus of your time when you punch the card at the beginning of the day and then knock off at the end of the day? Is navigation where you mostly spend your time?</p>\n\n\n\n<p>[00:38:05] <strong>Isabel Brison:</strong> Well, it has been for me for most of a year, on and off, there were a couple of other projects that I worked on for little bit, but I&#8217;ve been mostly, I can say mostly working on navigation to the best parts of the year.</p>\n\n\n\n<p>[00:38:19] <strong>Dave Smith:</strong> Yeah, same here. I mean I&#8217;m every day, the first thing I&#8217;m doing is catching up with the navigation block. Earlier on in the year, prior to 5.9, I was quite heavily focused on the navigation editor project to which you might come to later. But, certainly all this run up to 5.9 has been very much navigation, navigation, navigation block.</p>\n\n\n\n<p>[00:38:37] <strong>Joen Asmussen:</strong> Yeah, same here. I would add also that, as we mentioned, there are a lot of block editor specific issues that are surfaced due to the navigation block. Issues we encounter, but which need to be fixed for the block interface as a whole. Nathan, you appreciated the persistent list view.</p>\n\n\n\n<p>One of the reasons for that to become this tool, this left sidebar that lets you drag and drop, move, delete blocks right there. That came also from the realization that the nested structure of menus, especially with multiple sub menus, was easier to get an overview of in that interface.</p>\n\n\n\n<p>[00:39:13] <strong>Nathan Wrigley:</strong> It was actually quite a realization to me when I saw it in the list view. I made it so that the pages were listed out and it was quite fascinating to see the list of pages in the menus, in the list view. I confess I hadn&#8217;t expected that. There it was, it was real easy for me to see what my menu structure looked like without having to dig into a further interface. It was really nice.</p>\n\n\n\n<p>[00:39:34] <strong>Dave Smith:</strong> And you can modify it as well, in place, within this list view up and down drag and drop. A lot of work went into</p>\n\n\n\n<p>[00:39:40] <strong>Nathan Wrigley:</strong> Okay. A couple of things just before we round out. Yeah, you mentioned Dave, the navigation editor project, which my understanding is it&#8217;s now stalled. Do you want to just describe a little bit around that? What was that endeavor and why has it been mothballed?</p>\n\n\n\n<p>[00:39:53] <strong>Dave Smith:</strong> I think the first thing to say is that, I definitely don&#8217;t think the project is mothballed, and stalled might even be a step too far. It&#8217;s definitely on a moment of reflection and pause at the moment. it&#8217;s a topic of conversation within the contributor community around navigation.</p>\n\n\n\n<p>One of the other things to say is that the navigation editor is not in 5.9 and there&#8217;s been some confusion around that, but it is not the menu screen remains for classic themes. And the navigation editor is not there. The original project was actually basically to a replace the classic menu screen in WordPress.</p>\n\n\n\n<p>That scope of that project was very ambitious. It&#8217;s easy to say that with hindsight, but it never really managed to make it out of the experimental state, even in the Gutenberg plugin. I think part of the reason for that is that the scope called for the ability to edit both classic and block-based menus within the same interface and save them back to their original format so that you could switch back to a classic theme and still have your menu in place, even though you&#8217;ve edited it in a different interface.</p>\n\n\n\n<p>And that is a big, big challenge. And the main reason for that, even though it was achieved and testament to the people who worked on it, but before me, it was pretty much there when I started working on that. it was very, very difficult for backwards compatibility reasons, and it quickly became clear that the scope was very, very large of what we had to achieve.</p>\n\n\n\n<p>And then they&#8217;d run up to 5.9, there were some, a realignment of the direction on the nav block and specifically the creation of this ability to reuse menus, which required the creation of a custom post type, where the items or the menu were saved too. And that was a big impact on the editor. And basically it was determined that we need to sort of reprioritize the available contributor resources towards the block.</p>\n\n\n\n<p>I&#8217;m glad we did so, because I think it allowed us to really focus down on the block rather than perhaps managed to not land either. But, going forward, I think we need to look really, really carefully at the use cases and the requirements and the scope of this project. The first thing is, is there a use case for a standalone editor for editing menus and WordPress?</p>\n\n\n\n<p>Now the anecdotal feedback I&#8217;ve got so far from 5.9 is that, that seems to be a case for that. Specifically around block-based menus and the system we&#8217;ve just been talking about. There was no way to edit your menu outside of a navigation block itself. And that might sound good because, you know, I said direct editing is good, right? But, the problem is we have no safe space to create and explore and edit our navigations outside of the canvas of the post or the site editor. A good example of why that might be necessary is if you had a e-commerce site, you had your primary navigation, and then on black Friday month, your client comes to you and says, I need to use a different navigation for black Friday. Can you get it ready for me? And at that point, you&#8217;re in a really difficult use case where you can&#8217;t really change your things in your site editor and change your nav because then it would go live immediately. The workflows become pretty, pretty hacky. So there&#8217;s a good case there for an isolated editor to be able to edit these block based menus.</p>\n\n\n\n<p>I will say this is my opinion, this is just a caveat that, but I think it&#8217;s unlikely that we&#8217;ll see the nav editor revived in nt current form and current scope because I&#8217;m not convinced there is a case to save back to the classic menu format at this point. I think we need to be really careful about taking it really slowly. Looking for actual user use cases and doing things in phases, perhaps starting with this focused navigation editor mode. And in fact, that&#8217;s something that Matias Ventura, the lead architect of the Gutenberg project outlined in his sort of what&#8217;s next for the 6.0 release post and this focusing editor mode for navigation would be the first step, and then in the future, perhaps we introduce the ability to import your classic menus, manage them there. But, that needs to be based on actual feedback. I think we should listen to the community about it.</p>\n\n\n\n<p>[00:43:27] <strong>Nathan Wrigley:</strong> Do you know, that&#8217;s really interesting, and it hadn&#8217;t occurred to me that your example of a, let&#8217;s say, black Friday menu, that the fact that it&#8217;s not done in the same interface could potentially cause problems. That&#8217;s really fascinating. Do you think there&#8217;ll be a time where theme developers are only able to use the block. I know that&#8217;s a bit of blue sky thinking and, at some point WordPress has to marshal its resources in, in one way or another. You can&#8217;t support everything forever. Much like we would like to. Is there any discussions around that? Whether the development will sort of stop on the pre 5.9 way of doing menus, or is it always going to be updated in perpetuity?</p>\n\n\n\n<p>[00:44:09] <strong>Dave Smith:</strong> Well, I don&#8217;t know if Joen or Isabel have got any insights into that, but my gut instinct to that would be, I can&#8217;t really imagine a situation where we&#8217;re going to cut off support for the previous menu screen, just because of the backwards compatibility contract that WordPress has with its users.</p>\n\n\n\n<p>But that&#8217;s not to say, will there be continuing level of effort put into that screen as there was previously? Perhaps not because perhaps, you know, the world of WordPress moves forward with blocks, perhaps it doesn&#8217;t. But if it does then, you know, we&#8217;re probably going to see less and less features added to the classic menu screen and more effort put into extending the abilities of the block and any future isolated editor mode.</p>\n\n\n\n<p>I&#8217;d be interested to hear what Joen and Isabel think.</p>\n\n\n\n<p>[00:44:46] <strong>Joen Asmussen:</strong> I can only mainly echo your excellent insights already shared. I think one of the benefits of WordPress and open source also sometimes to its detriment is that it has this giant legacy that it&#8217;s supporting. It&#8217;s worth noting that this existing navigation screen, it still exists. You activate your classic theme and the navigation is there. I imagine so long as there are users that do that, it will be possible in some form or other. That&#8217;s just my personal thoughts based on how WordPress has always worked. I imagine it will be there for a long time.</p>\n\n\n\n<p>[00:45:23] <strong>Nathan Wrigley:</strong> Isabel?</p>\n\n\n\n<p>[00:45:24] <strong>Isabel Brison:</strong> That&#8217;s it really, I mean, things in WordPress tend to linger for a long time because we&#8217;re big on backwards compatibility. And while there are classic themes, the menus interface will continue to exist, because that&#8217;s what classic themes use. There probably won&#8217;t be a lot of new features developed for it. It&#8217;ll just be low key maintained in the background as it were. So I don&#8217;t think it&#8217;s going anywhere anytime soon.</p>\n\n\n\n<p>[00:45:50] <strong>Nathan Wrigley:</strong> For the novice learner of WordPress, I can imagine that fork in the road is going to be, it&#8217;s going to be interesting, shall we say, because there&#8217;s probably a million YouTube demonstrations of how to make menus work in WordPress, and they&#8217;ll be now millions more about how to do it in an alternative way. And so a quick Google search of how do I structure my WordPress menus could well lead people down a very frustrating path I imagine it doesn&#8217;t even look like that. I don&#8217;t understand.</p>\n\n\n\n<p>[00:46:18] <strong>Joen Asmussen:</strong> I think WordPress 5.9 is really an opportunity to try full site editing as it exists and then provide a great deal of feedback. And then WordPress 6.0, could be an interesting evolution and reaction to that feedback. So I would just echo that whatever feedback you have, it&#8217;s something we can act on and learn from.</p>\n\n\n\n<p>[00:46:42] <strong>Dave Smith:</strong> I had a bit of a point about the theme switching process. I&#8217;m not sure we touched on that much, but, there&#8217;ll be I&#8217;d imagine sizeable majority of your users who are on currently on the classic theme, they&#8217;ve probably got a menu in that theme, and they&#8217;re going to be thinking of, so what&#8217;s the process when I come to switch to this block theme, what happens? And as I think Isabel mentioned earlier that, you know, the menus are reusable so they are saved. So the good thing about it is that when you switched to your block theme for 2022, and you go to the editor page and you click on your navigation block, the initial experience is probably going to see a lot of pages there, but what you can do is switch and select a different menu, and you can actually select your classic menu from your classic theme, and use that immediately within the block theme. So there&#8217;s none of this, oh I have to recreate my menu from scratch.</p>\n\n\n\n<p>You know, all of that overhead. All you have to do is just select that menu from under the classic menus section and it will immediately appear. I think that&#8217;s a really powerful thing. And again, if you switch from a block theme to another block theme, the same process. You can select the menu created in theme A and use that in theme B, even though there&#8217;s completely different styling and that&#8217;s really, really powerful,</p>\n\n\n\n<p>Should also mention that if you do import a classic menu then it is a import. It is a copy. And your original classic menus is retained as was. This is perfect if you want to just experiment with full site editing, because what you can do is, you know, spin up a local copy of your site or a staging site. You can switch on to Twenty Twenty-Two, import your classic menu. Have a play around with that, see what you can achieve and then when you&#8217;re finished or if you don&#8217;t like it, you can switch back to your old theme and your classic menu will be still there as was, no changes at all. So that&#8217;s really confidence inspiring, I think these sort of flows allow people to just dip their toe in the water, so to speak.</p>\n\n\n\n<p>[00:48:23] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s a really good point because every interaction that I&#8217;ve had with 5.9 so far has been basically on a vanilla site. I hadn&#8217;t really thought about the consequences of going to a block-based theme on a site which was already in existence with potentially lots and lots of complexity inside the menu. So well made. Thank you. And Isabel.</p>\n\n\n\n<p>[00:48:42] <strong>Isabel Brison:</strong> I&#8217;d just add to what Dave was saying. If you are using a classic theme and you&#8217;re really curious about the navigation block and how it works, you can always make an experiment of adding a navigation block to a regular post because it&#8217;ll work in the post editor and just play around with it and see what you think. And by all means, do please give us feedback.</p>\n\n\n\n<p>[00:49:02] <strong>Nathan Wrigley:</strong> I will make sure that all of the things that we mentioned at the top of the podcast, ways to get in touch are listed as show notes. So please, if you are curious about this, go and have a play WordPress 5.9. See what you think. Play with the navigation block. These good folk will be very, very keen to hear whatever feedback you have, and go and check out the show notes on the podcast episode, and you can get in touch with them and let them know your thoughts. So thank you for joining us today. Dave Smith, Isabel Brison and Joen Asmussen. Thank you very much for joining me today.</p>\n\n\n\n<p>[00:49:33] <strong>Isabel Brison:</strong> Thank you for hosting us.</p>\n\n\n\n<p>[00:49:35] <strong>Dave Smith:</strong> It&#8217;s great to be here.</p>\n</div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Feb 2022 15:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:77:"WPTavern: Yet Another Plugin Dependencies Discussion, Two Proposals This Time";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=129830";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:87:"https://wptavern.com/yet-another-plugin-dependencies-discussion-two-proposals-this-time";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6291:"<p class="has-drop-cap">It has been over nine years since the late Alex Mills opened a ticket on WordPress Trac titled <a href="https://core.trac.wordpress.org/ticket/22316">Plugin Dependencies (Yet Another Plugin Dependencies Ticket)</a>. It is not the oldest of similar feature requests, but it is still open. Most predecessors were closed with the &#8220;wontfix&#8221; label, which is usually the final nail in the coffin of good and bad ideas alike.</p>\n\n\n\n<p>The goal of the ticket is to create a system that allows one plugin to require one or more others to operate. Dependencies are nothing new in the programming world. Composer, the standard PHP package manager, is two weeks shy of turning 10 years old. On the JavaScript end, npm has been around for 12 years, and WordPress has heavily embraced it for core code.</p>\n\n\n\n<p>However, those are developer tools. WordPress was built for users, and resolving plugin dependencies would need to happen from within the user interface.</p>\n\n\n\n<p>Mills wrote in the ticket:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>It&#8217;s been a few years since we looked at plugin dependencies, and this still seems to be a feature people really, really want, especially for shared functionality that isn&#8217;t a plugin in itself. For example, a PHP library that isn&#8217;t popular enough to be in core but is popular enough to be bundled in multiple plugins.</p></blockquote>\n\n\n\n<p>That statement is perhaps even more relevant today. In the past decade, many plugins have grown their own ecosystems of add-on plugins. The responsibility of making sure dependencies are installed has often fallen on the shoulders of end-users. Developers have come up with in-house solutions to ease that burden, and the <a href="https://github.com/TGMPA/TGM-Plugin-Activation">TGM Plugin Activation</a> script has become the <em>de facto</em> standard.</p>\n\n\n\n<p>Relying on dependencies is almost a given in any plugin project, at least playing a part in the average build tools setup. It is probably safe to say that more WordPress plugin developers are comfortable coding in an environment that requires third-party code today than they would have been in WordPress&#8217;s formative years.</p>\n\n\n\n<p>For a platform that has been working hard to modernize itself, resolving plugin dependencies is like traveling in a rocket ship to the Wild West.</p>\n\n\n\n<p>The idea is not without precedent in the WordPress world. While it is a less complex case, WordPress automatically downloads and installs the parent when installing a child theme from the directory.</p>\n\n\n\n<p>Many arguments for a plugin dependency system fall under the add-on scenario. The most obvious use case is WooCommerce and the dozens upon dozens of extensions written for it.</p>\n\n\n\n<p>However, the other scenario that can reach deeper into how developers build on top of WordPress is the inclusion of frameworks and libraries. Right now, plugin authors must bundle third-party code within their projects and make sure it does not get loaded if already bundled within an entirely separate plugin.</p>\n\n\n\n<p>Code reuse is one of the cornerstones of programming. The <a href="https://wptavern.com/the-wordpress-plugin-directory-will-no-longer-accept-frameworks">WordPress plugin directory disallows new frameworks</a> and similar libraries.  However, we could revisit this decision with a dependency system in place.  It could open the possibility of making libraries available as standalone extensions that any other plugin could use.</p>\n\n\n\n<p>For transparency, I have at least a dozen projects that fit under this category, packages sitting around that others could use. So, I at least have <em>some</em> skin in the game, and I am sure many others are in the same boat.</p>\n\n\n\n<p>There are two pull requests on the WordPress GitHub repository for a plugin dependency system. There is also a Google Docs file that <a href="https://docs.google.com/document/d/1Y5URlKW9GE89u7R3-z5o-0i5-9OVZd9HFaILhUE7mLA/edit">outlines both proposals in detail</a>.</p>\n\n\n\n<p>Each asks developers to define dependencies via a plugin header. The following is an example that would require WooCommerce and Gutenberg:</p>\n\n\n\n<pre class="wp-block-code"><code>&lt;?php\n/**\n * Plugin Name: Sample\n * Requires Plugins: woocommerce, gutenberg\n */</code></pre>\n\n\n\n<p>Both of the approaches are similar. From the user viewpoint, they would:</p>\n\n\n\n<ul><li>Show an admin notice that there are dependencies to install.</li><li>Disallow deletion or deactivation of plugins without deleting or deactivating their required plugins.</li><li>Output a message in the plugin card on the manage plugins screen.</li></ul>\n\n\n\n<p><a href="https://github.com/WordPress/wordpress-develop/pull/1547">The first implementation</a> is by Ari Stathopoulos. It creates an &#8220;activation queue&#8221; that would only activate a plugin once users have activated the required plugins. It also allows users to cancel activation requests.</p>\n\n\n\n<img />Notices to activate dependencies.\n\n\n\n<p><a href="https://github.com/WordPress/wordpress-develop/pull/1724">Andy Fragen&#8217;s solution</a> creates a new &#8220;Dependencies&#8221; tab on the plugin management screen. This approach would automatically deactivate any plugin with unmet dependencies and inform the user via an admin notice.</p>\n\n\n\n<p>He has also released the <a href="https://github.com/afragen/plugin-dependencies-tab">Plugin Dependencies Tab</a> project separately on GitHub.</p>\n\n\n\n<img />Plugin dependencies tab.\n\n\n\n<p>There are still some practical concerns with both. Namely, what happens when there is a conflict between supported versions? The current proposals leave it up to the plugins to not break anything on the user&#8217;s end.</p>\n\n\n\n<p>That may be the least confidence-inspiring piece of all of this. However, it is likely the most practical route. Plus, WordPress does not solve version conflicts in its current Wild West system.</p>\n\n\n\n<p>A dependency solution could also be an opportunity for more code modernization. Seeing more developers embracing features like interfaces (contracts) would be welcome. Coding with dependents in mind means thinking through architectural problems differently than when any given project was a standalone plugin.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Feb 2022 02:13: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: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:48:"WPTavern: BP Rewrites Feature Plugin Now in Beta";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=130046";s:7:"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:59:"https://wptavern.com/bp-rewrites-feature-plugin-now-in-beta";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3554:"<p>The ball is moving on a nine-year-old effort to migrate BuddyPress&#8217; custom URI parser to use WordPress&#8217; Rewrite API.  </p>\n\n\n\n<p>BuddyPress currently requires sites to use <a href="https://wordpress.org/support/article/using-permalinks/#mod_rewrite-pretty-permalinks">pretty permalinks</a> in order to be compatible with its URL parser. The plugin analyzes the URL for whatever component you are viewing and performs internal checks to decide what to display there and determine the proper template file. This custom parser has been working well for years but has some drawbacks compared to WordPress&#8217; newer Rewrite API.</p>\n\n\n\n<p>BuddyPress lead developer Boone Gorges summarized the problem in the original <a href="https://buddypress.trac.wordpress.org/ticket/4954">ticket</a>:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>BP&#8217;s custom URI parser (living mostly in&nbsp;<code>bp_core_set_uri_globals()</code>) is slow, error-prone, non-extensible, non-testable, and out of step with WP best practices.</p></blockquote>\n\n\n\n<p>In August of 2021, BuddyPress contributors moved this effort into the <a href="https://github.com/buddypress/bp-rewrites">BP Rewrites</a> feature plugin with the eventual goal of getting it merged into BP Core after wider testing. The first beta was <a href="https://bpdevel.wordpress.com/2022/02/13/bp-rewrites-1-0-0-beta1/">released</a> this week with a call for testing before it gets moved to the WordPress plugin directory.</p>\n\n\n\n<p>BP Rewrites isn&#8217;t just an under-the-hood architectural improvement for BuddyPress, it also has several user-facing benefits: </p>\n\n\n\n<ul><li>BuddyPress URLs customization improved and easier</li><li>Compatibility with plain permalinks</li><li>Improved Compliance with WordPress Standards</li><li>Improved User/Advanded user/Plugin developer/Theme designer BuddyPress experience</li></ul>\n\n\n\n<p>Users who test the plugin will find a URLs customization screen (replacing the BP Pages screen) under the BuddyPress settings where page slugs can be easily changed. This is much more user-friendly than editing the wp-config.php file.</p>\n\n\n\n<img />\n\n\n\n<p>&#8220;When you deactivate the plugin, <code>buddypress</code> post type’s items are switched back to regular pages and you get them back into the corresponding WordPress Administation edit screen,&#8221; BuddyPress core developer Mathieu Viet said. &#8220;Post metas are still there in case you want to activate BP Rewrites back (this can happen when you’re testing another BuddyPress plugin). If you absolutely want to get rid of these post metas, you can delete the BuddyPress pages, create new ones and redo the page mapping from the BuddyPress Pages settings screen.&#8221;</p>\n\n\n\n<p>This isn&#8217;t something you want to test on a production site, as it&#8217;s still uncertain how BP Rewrites will interact with different plugins. Testers can <a href="https://github.com/buddypress/bp-rewrites/issues">report bugs as issues</a> on the plugin&#8217;s GitHub repository.</p>\n\n\n\n<p>&#8220;There’s no secret: the only way to have enough confidence into this backward compatibility mechanism to start thinking of merging BP Rewrites into BuddyPress Core is to test, test, and test again,&#8221; Viet said.</p>\n\n\n\n<p>When discussing BP Rewrites&#8217; progress earlier this year, Viet advised the feature plugin stay as an add-on for at least two major BuddyPress releases. This will give developers the chance to ensure there are fewer plugin conflicts before merging into BuddyPress core.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 15 Feb 2022 22:48: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:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:21:"Matt: Junk Your Jabra";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=55546";s:7:"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:38:"https://ma.tt/2022/02/junk-your-jabra/";s: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:1105:"<p>I usually wouldn&#8217;t do a post about this, but I was so surprised I had to share. I picked up a <a href="https://www.amazon.com/gp/product/B08WK5CZYY/">Jabra Evolve2 30 UC wired headset, with USB-C</a>, because my friend Hugo loves the wireless Jabra and I&#8217;ve been using an older USB-A headset and thought it would be nice to not need an adapter. I also thought for $89 it must be good. The reviews were also really solid (4.3 on Amazon right now).</p>\n\n\n\n<p><strong>Do not</strong> buy this headset. There was a constant buzz/hum in the speaker, people sounded lower quality, and the mic also was lower quality. On the plus side, it was a nice build quality and comfort.</p>\n\n\n\n<p>For <a href="https://www.amazon.com/gp/product/B07P76F99F/?tag=photomatt08-20">$29 cheaper ($60) the Sennheiser SC 135 USB-C</a> had better speaker, way better mic quality, very nice build and comfort. Get that one instead.</p>\n\n\n\n<p>So <a href="https://ma.tt/2020/03/dont-mute-get-a-better-headset/">don&#8217;t mute, get a better headset</a>. <a href="https://krisp.ai/">Krisp.ai</a> is still great, too.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 15 Feb 2022 03:54: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:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:72:"WPTavern: Gutenberg Contributors Explore More Advanced Template Creation";s:7:"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=129991";s:7:"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://wptavern.com/gutenberg-contributors-explore-more-advanced-template-creation";s: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:4519:"<p>Gutenberg design contributors are <a href="https://github.com/WordPress/gutenberg/issues/37407">exploring</a> how the template creation UI can be updated to expand the types of templates that user can create using the Site Editor. In WordPress 5.9 users can edit any template that a theme includes, but template creation is limited to a few basics: </p>\n\n\n\n<ul><li>Front page</li><li>Single</li><li>Page</li><li>Archive</li><li>Search</li><li>404</li><li>Index</li></ul>\n\n\n\n<p>Many of these basic templates are already in use by FSE themes. Users will only see the option to create templates (from this limited list) that their theme hasn&#8217;t already introduced. Opening up template creation to the wider world of WordPress theme templates would enable so much more customization.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>Contributors are exploring adding the ability to create category, author, tag, attachment, taxonomy, date, CPT (custom post types), templates for a specific post or page, and &#8220;<a href="https://github.com/WordPress/gutenberg/issues/36860">general</a>&#8221; templates.</p>\n\n\n\n<p>Automattic designer James Koster shared a short video demonstration of what he imagined the flow for this might look like. </p>\n\n\n\n<p>&#8220;What I felt worked well was separating templates by their specificity,&#8221; Koster said. &#8220;That is to say: templates that serve a static purpose (<code>404</code>, <code>front-page</code>, <code>*-$slug</code> etc) are grouped together, and templates with a dynamic purpose appear beneath.</p>\n\n\n\nVideo Credit: <a href="https://github.com/WordPress/gutenberg/issues/37407#issuecomment-1032512081">James Koster</a>\n\n\n\n<p>&#8220;This arrangement elevates the prominence of creating templates for a specific context – which I think is likely to be quite a popular flow – while still making it very simple to add common templates like <code>page</code>.&#8221;</p>\n\n\n\n<p>He suggested that the &#8220;Advanced&#8221; section at the bottom of the menu could house templates that are less likely to be used, such as taxonomy or date.</p>\n\n\n\n<p>This is isn&#8217;t guaranteed to be the UI that lands for advanced template creation but it&#8217;s one exploration of how it could work.</p>\n\n\n\n<p>WordPress developer Steve Graboski commented on how CPT template creation through the Site Editor would give users more freedom to change the site, while reducing the number of theme files developers need to maintain:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Like several other web developers, I help manage a WP Multisite implementation. If the Site Editor allowed devs like us to make CPT templates, it would make for a profound improvement to our experience with WordPress.</p><p>For starters, we could remove several child themes that exist only to provide our departments with CPT layouts, archives, and search pages. The only files we would need are the plugins that define the CPTs. Who wouldn&#8217;t love a less complicated repo?</p><p>The advantages stretch past the dev team. In theory, we could offer our editors the ability to edit these CPT templates, no coding required. This would enable our non-programming co-workers to change template layouts without relying on our assistance. The editors get more power over their sites, and the developers gain more hours of productivity.</p></blockquote>\n\n\n\n<p>The idea of putting CPT template creation inside the Site Editor prompted participants in the discussion to consider making the creation of the CPTs themselves more user friendly.</p>\n\n\n\n<p>&#8220;I enjoy the idea that core might provide a UI for CPT creation, sometimes I want a CPT, but don&#8217;t want to have to pull out the code editor to do it, especially if it&#8217;s going to have pretty much the same capabilities as a post,&#8221; WordPress developer Aurooba Ahmed said.</p>\n\n\n\n<p>&#8220;Creating templates for <em>existing</em> CPTs feels like table stakes, but also a fairly developer oriented solution because it requires the CPT to be registered in the first place,&#8221; Koster said.</p>\n\n\n\n<p>&#8220;Thinking further along the road&#8230; I wonder if there&#8217;s a world where the Site Editor could enable users to add modules like &#8216;Portfolio&#8217; or &#8216;Testimonials.&#8217; These modules could register the CPT and create all the necessary templates in a single flow. With block patterns and other tools available to us we could potentially make this quite a compelling experience.&#8221; </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 15 Feb 2022 02:20: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:45;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:78:"WPTavern: Clarity Ad Blocker for WordPress Announced, Receives Mixed Reactions";s:7:"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=129980";s:7:"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:88:"https://wptavern.com/clarity-ad-blocker-for-wordpress-announced-receives-mixed-reactions";s: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:8007:"<p class="has-drop-cap">Stanislav Khromov announced <a href="https://wordpress.org/plugins/clarity-ad-blocker/">Clarity</a>, a plugin for hiding obtrusive banners, via <a href="https://twitter.com/khromov/status/1493151526306693122">Twitter</a> and the <a href="https://www.facebook.com/groups/advancedwp/posts/5094252490636924">Advanced WordPress</a> (AWP) Facebook group today. It was first pushed to WordPress.org around a year ago, but the developer seems to be just now publicizing it.</p>\n\n\n\n<p>The <a href="https://wp-clarity.dev/">Clarity website</a> describes its mission as: &#8220;Ads, upsells, and analytics banners have been running rampant in our WordPress dashboards for too long. It&#8217;s time to make them go away, once and for all.&#8221;</p>\n\n\n\n<p>Clarity does not come with a settings screen. Once users active it, it attempts to hide banners and other notifications falling outside of its &#8220;acceptable ads policy,&#8221; which is <a href="https://github.com/khromov/clarity/blob/master/acceptable-ads-policy.md">currently a draft</a> that Khromov has encouraged feedback on. This policy covers plugins that ask for reviews, inform users of discounts, or prompt them to upgrade to a commercial version.</p>\n\n\n\n<p>The plugin&#8217;s goal is to hide those notices unless they are:</p>\n\n\n\n<ul><li>Shown only on an options page that belongs to the plugin or theme and nowhere else.</li><li>Shown only to Administrator role users.</li><li>Not intrusive or distracting.</li><li>Not displayed in the main column, but rather in an &#8220;aside.&#8221;</li></ul>\n\n\n\n<p>The plugin does include a link on the plugins management screen to report unwanted banners. It leads to a <a href="https://github.com/khromov/clarity/issues/new?assignees=khromov&labels=filter-request&template=1-report-notification.md&title=Plugin%2FTheme+name%3A+">pre-filled issued template</a> on Clarity&#8217;s GitHub repository.</p>\n\n\n\n<img />Report unwanted banner link.\n\n\n\n<p>The announcement was well-received by many on AWP, judging by the likes from members. However, several vocalized their opposition to the idea. Some called it &#8220;unethical&#8221; and &#8220;damaging&#8221; to the ecosystem.</p>\n\n\n\n<p>Ads are a fact of life. They generate the necessary revenue for companies to continue maintaining their current products and building new ones. The WordPress industry is no different in that regard. However, these are often small companies where the wrong placement in the admin can mean the difference between creating new jobs and barely scraping by.</p>\n\n\n\n<p>Freemium products are one of the ways that shops provide free features to end-users while also making a commercially-viable solution that keeps their business running. Banners for ads and user ratings are often the most effective methods of making a sale or generating more interest in the project.</p>\n\n\n\n<p>&#8220;By creating an ad blocker &#8211; your selfish disregard to the commercial realities of [open-source] damages a delicate ecosystem,&#8221; <a href="https://www.facebook.com/groups/advancedwp/posts/5094252490636924/?comment_id=5095139490548224&__cft__[0]=AZXnbECB2CcPnlx-pb3V8SA5Po9FYTj8FmUjpTEGWVIkHlskFHD4WV_wSpxMIBK95oHETSrZVtwTVwdAGx4316M6APCJ4ezP7CtaXvl4GFY2VcVWfx8c_QZIVbOh-_yCHxWDKsmMecIInvI1MIeQuqoh&__tn__=R]-R">wrote one developer</a><a href="https://wptavern.com/feed#footnotes-1"><sup>[1]</sup></a> in the AWP thread. &#8220;If you use a free product &#8211; pay for it by tolerating a few nags.&#8221;</p>\n\n\n\n<p>&#8220;The idea of taking someone&#8217;s work product, but bypassing their ads, is at a minimum unethical,&#8221; <a href="https://www.facebook.com/groups/advancedwp/posts/5094252490636924/?comment_id=5095382177190622&__cft__[0]=AZXnbECB2CcPnlx-pb3V8SA5Po9FYTj8FmUjpTEGWVIkHlskFHD4WV_wSpxMIBK95oHETSrZVtwTVwdAGx4316M6APCJ4ezP7CtaXvl4GFY2VcVWfx8c_QZIVbOh-_yCHxWDKsmMecIInvI1MIeQuqoh&__tn__=R]-R">wrote another developer</a>. &#8220;Nobody is forced to capitalize on the fruit of anyone else&#8217;s labor.&#8221;</p>\n\n\n\n<p>Free software means giving users the freedom to change all that. If another developer comes along and blocks the behavior that those users want, it is fair game. Playing in the free-software sandbox means accepting that others can and will change the code you write every now and again. WordPress makes it even easier to do so via its hooks system.</p>\n\n\n\n<p>Clarity is merely one tiny fish swimming in a vast ocean of plugins. If it had over a million active installs, maybe it would be realistically put a dent in some commercial shops&#8217; profits. However, that is not the case. Any claim that it is damaging to the ecosystem is tip-toeing into hyperbole.</p>\n\n\n\n<p>If it did have that many active installs, perhaps it would be a wake-up call for developers, a warning that users want to see change.</p>\n\n\n\n<p>The question is: <em>Do most users need such a plugin?</em></p>\n\n\n\n<p>Maybe not, but it depends. The directory guidelines require that any admin notices &#8212; where most of the &#8220;offending&#8221; ads are located &#8212; <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#11-plugins-should-not-hijack-the-admin-dashboard">must be dismissible</a>. However, the standard is relatively loose in definition. Some plugins show the ad to every user logged into the admin, requiring each to dismiss it. Others refresh themselves on plugin updates, requiring additional action by the user. If a plugin is updated multiple times per week and adds a new admin-wide banner each time, it almost feels like it is skirting the rules, <em>just a little bit</em>.</p>\n\n\n\n<p>Advertisements and other notices can also be problematic on client builds. Freelancers and agencies sometimes get that frantic call when a plugin update displays a new pro upsell message to clients who thought they had already paid what was required for their site. There are some ways to mitigate this, but they are not all 100% fool-proof in every scenario. Clarity would just be another wrench in the ol&#8217; toolbox for tightening up those client sites, creating some extra peace of mind.</p>\n\n\n\n<p>The plugin itself is not &#8220;intelligent.&#8221; It does not learn and grow on its own, evolving as more plugins are created. It requires a manual process of creating a curated list of selectors to target via CSS. The plugin hides banners according to this custom set of definitions.</p>\n\n\n\n<p>As long as third-party developers do not create an <em>ad-block blocker</em> method within their own plugins, Clarity should keep some of the notices at bay. It is unlikely most even knew about this project until its announcement. With it now in the public sphere, I have few doubts that some will override it. It may depend on individual stances on user choice in advertising.</p>\n\n\n\n<p>Clarity provides a method for plugin and theme authors to opt into the blocking of their own advertisements. They only need to check for a PHP constant to do so:</p>\n\n\n\n<pre class="wp-block-code"><code>if ( defined( ''CLARITY_AD_BLOCKER_ENABLED'' ) &amp;&amp; CLARITY_AD_BLOCKER_ENABLED ) {\n        // You should not serve ads or upsells to this user.\n}</code></pre>\n\n\n\n<p>I doubt most would willingly buy into this system. However, I like the idea. The users who go through the trouble of installing and activating an ad-blocking plugin are unlikely the target audience anyway.</p>\n\n\n\n<p>Clarity is a decent option for users who want to find a little calm amidst the noise, but it has its limits.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<blockquote class="wp-embedded-content"><a href="https://wordpress.org/plugins/clarity-ad-blocker/">Clarity &#8211; Ad blocker for WordPress</a></blockquote>\n</div>\n\n\n\n<hr class="wp-block-separator is-style-tavern-separator" />\n\n\n\n<h2 id="footnotes">Footnotes:</h2>\n\n\n\n<p id="footnotes-1">1. Advanced WordPress is a private Facebook group.  Therefore, I did not include the names of the quoted sources in this article.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 15 Feb 2022 01:26:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:18:"Matt: Thirty Eight";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=55514";s:7:"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:35:"https://ma.tt/2022/01/thirty-eight/";s: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:4642:"<p>This is an unusually late birthday post (still backdated to January 11). I woke up on my actual birthday and was not feeling it. I was locked down even more strictly than January 2021 because I was trying to be extra cautious prior to a surgery my Mom had later in the month. I was also on a fairly strict diet and exercise regime after slipping into a weight range I wasn&#8217;t comfortable with.</p>\n\n\n\n<p>So I was feeling extra isolated, had a strange pain in my lower back, and I just felt old all over. I thought of the <a href="https://genius.com/12523">Drake line</a>, &#8220;I&#8217;m really too young to be feeling this old.&#8221; (Maybe <a href="https://genius.com/Garth-brooks-much-too-young-to-feel-this-damn-old-lyrics">originally from Garth Brooks</a>?)</p>\n\n\n\n<p>I meditated with a <a href="https://www.calm.com/">Daily Calm</a> from <a href="https://jeffwarren.org/">Jeff Warren</a> called &#8220;The Boggle,&#8221; which unfortunately I can&#8217;t hotlink but here&#8217;s how it starts: <em>Sometimes we&#8217;re in the boggle, life is throwing everything at us: complicated situations, complicated relationships, we have all these feelings, all these impulses pulling us in different directions, and we have no idea what to do. No idea how to resolve it all. Even no idea what self-care strategy to implement right now. So what&#8217;s interesting about the boggle is that there&#8217;s the challenge of the situation itself, or situations, and there&#8217;s the added challenge of the confusion of it, the scrambling to make sense of everything. So we&#8217;re going to try something different, we&#8217;re going to stop scrambling and accept, even forgive, the boggle. We&#8217;re going to let ourselves be right here, inside any confusion, and take a break from trying to fix any of it. That&#8217;s the itinerary, let&#8217;s go.</em> It hit close to home, and I&#8217;ve ended up returning to that meditation several times since.</p>\n\n\n\n<p>The day really shaped up, though! Friends surprised me with a trip to <a href="https://www.teamlab.art/">a Teamlab exhibit</a> at a museum that was closed on Tuesdays but they got opened up just for us. The museum was magical, but the best part was seeing friends I wasn&#8217;t expecting to, even if masked and relatively distanced. I wore a new <a href="https://ma.tt/files/2022/02/IMG_7081-scaled.jpeg">comfy matching tie die outfit too</a>, because, why not? Ended the day with a small dinner with Mom and three friends.</p>\n\n\n\n<p>I don&#8217;t have any particular wisdom from this birthday except no matter how you feel, take some Advil and keep going.</p>\n\n\n\n<p>This year on the personal side I&#8217;d like to take more silent retreats, get settled at home and out of liminal states, particularly construction projects, and listen to more operas. On the work side I&#8217;d like to set up alternative ecosystems for people tired of the traditional options for social with <a href="https://www.tumblr.com/">Tumblr</a>, listening with <a href="https://www.pocketcasts.com/">Pocket Casts</a>, and writing <a href="https://dayoneapp.com/">with Day One</a>. (Update: A few weeks after my birthday <a href="https://photomatt.tumblr.com/post/675023779369566208/how-the-snowflakes-won">I announced I&#8217;m working on Tumblr full-time</a>.) Finally, I&#8217;d like to do my birthday post on time next year, but I&#8217;m forgiving myself for prioritizing friends and family that day. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f604.png" alt="😄" class="wp-smiley" /></p>\n\n\n\n<p>All birthday posts: <a href="https://ma.tt/2003/01/bday/">19</a>, <a href="https://ma.tt/2004/01/so-im-20/">20</a>, <a href="https://ma.tt/2005/01/hot-barely-legal-matt/">21</a>, <a href="https://ma.tt/2006/01/matt-22/">22</a>, <a href="https://ma.tt/2007/01/twenty-three/">23</a>, <a href="https://ma.tt/2008/01/twenty-four/">24</a>, <a href="https://ma.tt/2009/01/twenty-five/">25</a>, <a href="https://ma.tt/2010/01/twenty-six/">26</a>, <a href="https://ma.tt/2011/01/twenty-seven/">27</a>, <a href="https://ma.tt/2012/01/twenty-eight/">28</a>, <a href="https://ma.tt/2013/01/twenty-nine/">29</a>, <a href="https://ma.tt/2014/01/matt-3-0/">30</a>, <a href="https://ma.tt/2015/01/thirty-one/">31</a>, <a href="https://ma.tt/2016/01/thirty-two/">32</a>, <a href="https://ma.tt/2017/01/thirty-three/">33</a>, <a href="https://ma.tt/2018/01/thirty-four/">34</a>, <a href="https://ma.tt/2019/01/thirty-five/">35</a>, <a href="https://ma.tt/2020/01/thirty-six/">36</a>, <a href="https://ma.tt/2021/01/thirty-seven/">37</a>, <a href="https://ma.tt/2022/01/thirty-eight/">38</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 12 Feb 2022 08:45:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:111:"Gutenberg Times: Gutenberg Developer Hours, from Zero to Hero Series and Adoption paths — Weekend Edition 203";s:7:"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=20426";s:7:"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:117:"https://gutenbergtimes.com/gutenberg-developer-hours-from-zero-to-hero-series-and-adoption-paths-weekend-edition-203/";s: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:24084:"<p>Howdy, </p>\n\n\n\n\n\n<p><br />Among other links, today&#8217;s edition links to three posts about technology adoption, feature adoption, FSE adoption. Josepha Haden Chomphosy, Tammie Lister and Anne McCarthy shine their light on different paths you can take on your journey to explore and conquer the new features,  for contributors, theme developers, site owners or site builders. </p>\n\n\n\n<p>The most approachable parts of designers are <strong>Block Patterns</strong>. For inspiration, visit Tammie Lister&#8217;s, <a href="http://patternspiration.com/">Patternspiration</a> site, the <a href="https://wordpress.org/patterns/">WordPress Pattern Directory</a> or install the free <a href="https://wordpress.org/plugins/extendify/">Extendify plugin</a>. </p>\n\n\n\n<p>In any case, don&#8217;t go it alone. Every week, you can join other WordPress practitioners on various levels on the <a href="https://www.meetup.com/wordpress-social-learning/"><em>Social Learning Spaces</em></a> or in Hallway Hangouts. You find a list of the upcoming events below. </p>\n\n\n\n<p>As always, there is more in this edition from generous people that accompany all of us along our journey. </p>\n\n\n\n<p>Grab your favorite hot or cold beverages and enjoy this Weekend&#8217;s Edition. As always, let me know what you think, or what you need on your block editor journey. </p>\n\n\n\n<p>Yours, 💕<br />Birgit</p>\n\n\n\n<p>PS: &#8220;If you want to go fast, go alone. If you want to go far, go together.&#8221; African Proverb</p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n\n<div class="wp-container-6219cc4890bc2 wp-block-group has-light-background-background-color has-background"><div class="wp-block-group__inner-container">\n<p><strong>Table of contents</strong></p>\n\n\n\n<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#highlights">Highlights</a></li><li><a href="https://gutenbergtimes.com/feed/#building-blocks-and-plugins-for-the-editor">Building blocks and plugins for the editor</a></li><li><a href="https://gutenbergtimes.com/feed/#building-themes-adopting-to-fse">Building themes, adopting to FSE</a></li><li><a href="https://gutenbergtimes.com/feed/#content-creators-and-site-owners-tools">Content Creators and Site Owners Tools</a></li><li><a href="https://gutenbergtimes.com/feed/#wordpress-events">Hallway Hangouts, Webinars, and WordPress Social Learning events.</a></li></ul></div>\n</div></div>\n\n\n\n\n<h2 id="highlights">Highlights</h2>\n\n\n\n<p>Join us again <a href="https://www.meetup.com/wordpress-social-learning/events/283720638/">February 22, 2022 on 11 am ET / 16:00 UTC</a> for another Gutenberg Developer Hours. </p>\n\n\n\n<a href="https://www.meetup.com/wordpress-social-learning/events/283720638/"><img /></a>\n\n\n\n\n<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2022&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test, and Meta team from Jan. 2021 on. Updated by yours truly.  <a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/"><em>The index 2020 is here</em></a></p>\n\n\n\n\n<p><strong>Josepha Haden</strong> <strong>Chomphosy</strong>, Executive Director of the WordPress open-source Project, published <a href="https://make.wordpress.org/project/2022/02/11/a-theory-of-technology-adoption-in-the-wordpress-project/"><strong>A Theory of Technology Adoption in the WordPress&nbsp;Project</strong></a>. </p>\n\n\n\n<p>In the introduction, Chomphosy quoted Calestous Juma <em>&#8220;Many of the dominant technologies that we take for granted have weathered moments of social tension and threats of succession.&#8221; </em></p>\n\n\n\n<p>&#8220;As we head into the iterative part of Gutenberg’s phase 2, there are a few things that we should be aware of that will motivate or inspire our community of users to take a fresh look at the WordPress editor.&nbsp;In my observation, that breaks down into three parts.&#8221; She wrote. </p>\n\n\n\n<ul><li>Apparent usefulness (to the extender) – aka, what does this do for me?</li><li>Apparent ease of use (to the extender and user) – aka, is the difficulty ≤ the current technology?</li><li>Apparent trustworthiness (social proof/social sentiment)&nbsp;–&nbsp;aka, do my trusted friends trust this thing? </li></ul>\n\n\n\n<p>Intrigued? <a href="https://make.wordpress.org/project/2022/02/11/a-theory-of-technology-adoption-in-the-wordpress-project/">Deeper insights in the post.</a>  </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>At WCUS 2021,  <strong>Helen Hou-Sandí</strong> talked about  <a href="https://wordpress.tv/2021/12/23/helen-hou-sandi-a-voice-for-the-new-white-house-administration-with-the-block-editor/">custom blocks development for the new website of White House</a>. You can watch the recording now on WordPress.tv.</p>\n\n\n\n\n<div class="wp-block-embed__wrapper">\n\n</div>Video: <strong>Helen Hou-Sandí</strong> WordCamp US 2021 \n\n\n\n\n<p><strong>10up</strong> recently published more details of the project on the company blog. <strong>&#8220;<a href="https://10up.com/our-work/white-house/">A Voice For A New White House Administration</a>. </strong> Videos enrich the various aspects of the work. Quite a few interesting aspects of the design and build process are noted. For instance:  &#8220;To simplify the content creation experience, 10up removed sidebar options in favor of new blocks for the featured image, category, and date that are displayed in the editor in the same position that they appear on the page.&#8221; </p>\n\n\n\n<p>Take your time to digest the learned lessons and experience reported by one of the leading WordPress agencies. There are quite a few takeaways that might help you navigated the block universe of WordPress. <br /><em>Thank you to <a href="https://mailchi.mp/poststatus/485">Post_Status</a> for surfacing this blog post.</em></p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Matias Ventura</strong>, principal architect of Gutenberg was our guest on the <strong><a href="https://gutenbergtimes.com/podcast/gutenberg-changelog-60-restricting-customization-in-a-full-site-editing-world/">60th episode of the Gutenberg Changelog</a></strong>. Grzegorz (Greg) Ziolkowski and I  discussed with him way to restrict customization in a full-site editing world, the Gutenberg 12.5 release and some changes coming with WordPress 6.0</p>\n\n\n\n\n<div class="wp-container-6219cc4890f95 wp-block-group is-style-default has-light-background-background-color has-background"><div class="wp-block-group__inner-container">\n<p><strong>Subscribe to the&nbsp;<a href="https://gutenbergtimes.com/podcast/">Gutenberg Changelog</a>&nbsp;podcast </strong><br />🎙️&nbsp;<a href="https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe">Spotify</a>&nbsp;|&nbsp;<a href="https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0">Google</a>&nbsp;|&nbsp;<a href="https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475">iTunes</a>&nbsp;|&nbsp;<a href="https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf">PocketCasts</a>&nbsp;|&nbsp;<a href="https://www.stitcher.com/show/gutenberg-changelog">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href="https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast">Pod Bean</a>&nbsp;|&nbsp;<a href="https://castbox.fm/channel/Gutenberg-Changelog-id2173375">CastBox</a>&nbsp;|&nbsp;<a href="https://www.podchaser.com/podcasts/gutenberg-changelog-878239/">Podchaser</a>&nbsp;|&nbsp;<a href="https://gutenbergtimes.com/feed/podcast">RSS Feed</a>&nbsp;</p>\n\n\n\n<img />\n</div></div>\n\n\n\n\n<p>✨ ✨ <strong>Friendly Reminder: </strong><br /><strong>Eleven days left to respond to </strong><a href="https://make.wordpress.org/test/2022/02/02/fse-program-exploration-all-things-media/"><strong>All Things Media</strong> <strong>Call for Testing</strong></a> </p>\n\n\n\n<ul><li><a href="https://make.wordpress.org/test/2022/02/02/fse-program-exploration-all-things-media/">English version</a> by Anne McCarthy</li><li><a href="https://ja.wordpress.org/team/2022/02/04/2637/">Japanese version</a> by Mimi and Akira Tachibana</li><li><a href="https://it.wordpress.org/team/2022/02/07/esplorazione-per-il-programma-fse-tutto-quello-che-fa-media/">Italian version</a> by Piermario Orecchioni </li></ul>\n\n\n\n<p>It&#8217;s a great way to collaborate on ideas on how to integrate the rapidly growing WordPress <a href="https://wordpress.org/photos/">Photo Directory</a> and <a href="https://wordpress.org/openverse/">Openverse</a> into the block editor. </p>\n\n\n\n<h2 id="building-blocks-and-plugins-for-the-editor">Building blocks and plugins for the editor</h2>\n\n\n\n<p>One change in 5.9 to the <a href="https://make.wordpress.org/core/2022/02/09/cover-block-refactor-dev-note/"><strong>Cover block</strong> is now documented in this DevNote</a> by <strong><a href="https://twitter.com/glendaviesnz">Glen Davis</a></strong>. He explains the changes made during refactoring of the Cover block. He also notes that theme and plugin developer were surprised by these changes, as there was no documentation published until now. The most considerable changes was that opacity styling for background color was moved. It broke some sites. </p>\n\n\n\n<p>This has already been fixed, and is scheduled to deploy as part of the WordPress 5.9.1 release. Until then, you can use Davis&#8217; suggested work around or rollback your WordPress 5.9 upgrade with this powerful nifty little plugin <a href="https://wordpress.org/plugins/core-rollback/"><strong>&#8220;Core Rollback&#8221; by Andy Fragen.</strong></a></p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong><a href="https://twitter.com/jonihalabi">Joni Halabi</a></strong> found a way to <a href="https://jhalabi.com/blog/core-dynamic-render-override"><strong>Overriding WP core: Dynamic blocks edition</strong></a>. She shares how she replace the <code>render_callback</code> function for the Core RSS block to render a customized HTML on the front end. </p>\n\n\n\n<p><em>If you have similar needs, you can override a single argument to avoid unregistering a block via <code><a href="https://developer.wordpress.org/reference/hooks/register_block_type_args/3:45">register_block_type_args</a></code> or modify the content generated for the block with <code><a href="https://developer.wordpress.org/reference/hooks/render_block_this-name/">render_block_this-name</a></code></em></p>\n\n\n\n\n<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s main (trunk) branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>\n\n\n\n<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total" /></p>\n\n\n\n\n<h2 id="building-themes-adopting-to-fse">Building themes, adopting to FSE</h2>\n\n\n\n<p>Next week Friday, <strong>Daisy Olsen</strong> and <strong>Sarah Snow</strong> will offer the fifth session in their five-part series: <a href="https://www.meetup.com/wordpress-social-learning/events/283927573/"><strong>Zero to Block Theme Series #5: From Site Editor to Theme</strong></a>. The recordings of the first four parts are available on YouTube: </p>\n\n\n\n<ul><li>Session 1:&nbsp;<a href="https://youtu.be/ntT1GT6Yr3w" target="_blank" rel="noreferrer noopener">Foundations</a></li><li>Session 2:&nbsp;<a href="https://www.youtube.com/watch?v=cjSZOJZspe0" target="_blank" rel="noreferrer noopener">Theme.json</a></li><li>Session 3:&nbsp;<a href="https://www.youtube.com/watch?v=LxIjfkc9O0Q" target="_blank" rel="noreferrer noopener">Theme.json continued &#8211; Styles</a></li><li>Session 4:&nbsp;<a href="https://youtu.be/APsu8Jc570A" target="_blank" rel="noreferrer noopener">Templates and Template Parts</a></li></ul>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Anne McCarthy</strong> published in the series of Core Editor Improvement &#8220;Core Editor Improvement: <a href="https://make.wordpress.org/core/2022/02/09/core-editor-improvement-curated-experiences-with-locking-apis-theme-json/"><strong>Curated experiences with locking APIs &amp; theme.json</strong></a>. She explores <em>&#8220;some practical ways you can perhaps apply these locking options to your individual projects to both provide some guardrails and still allow users to make things their own.&#8221;</em> If you are working on creating an editor experience following the strong standards for publishing and brand design, this post is for you. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Ryan Welcher </strong>posted a short video on <strong><a href="https://www.youtube.com/watch?v=4hNXRdfYx7g">Locking down theme.json</a></strong> and discusses how to control the effect of adding a theme.json file to your classic theme.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<div class="toolbelt-video-wrapper"></div>\n</div>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong><a href="https://twitter.com/jameskoster">James Koster</a></strong> showed in his post <strong><a href="https://jameskoster.design/2022/02/04/expanding-template-creation-options-in-the-site-editor/">Expanding template creation options in the Site Editor</a></strong> and embedded videos early concepts on creating full page prototypes. You can follow along <a href="https://github.com/WordPress/gutenberg/issues/37407">the PR on GitHub</a>. And if you have an idea or opinion, add it there. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>One of the <a href="https://wordpress.org/themes/tags/full-site-editing/">47 Block Themes</a> built for full site editing in the WordPress repository is <strong><a href="https://wordpress.org/themes/miniblock-ooak/">Miniblock OOAK</a> </strong>by <strong>Carolina Nymark</strong>. She describes it as &#8220;One page, all the blocks. If all you need is one fully customizable page, it does not get simpler than this.&#8221; <strong>Justin Tadlock</strong> took it for a spin and posted his review on the WPTavern:  <a href="https://wptavern.com/miniblock-ooak-and-outside-the-box-ideas-in-the-theme-directory"><strong>Miniblock OOAK and Outside-the-Box Ideas in the Theme Directory</strong></a></p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>In her article, <a href="https://extendify.com/gutenberg-full-site-editing-does-not-have-to-be-full/"><strong>Gutenberg Full Site Editing does not have to be full</strong></a>, <strong>Tammie Lister </strong>lays out a path for gradual adoption of the various tools  coming with WordPress 5.9., that starts with stopping to use the term Full-Site Editing. That term hides the fact that it&#8217;s a conglomerate of many pieces for each could stand alone and be integrated separately with existing sites. <em>&#8220;My best advice to anyone looking to start on this journey right now is to start with patterns, move to theme.json, and from there, gradually move through whatever makes sense for you.&#8221;</em> Lister wrote. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Anne McCarthy</strong> suggested a similar path in her post from last fall, that&#8217;s still immensely relevant <a href="https://nomad.blog/2021/09/29/sharing-approaches-for-fse-feature-adoption/"><strong>Sharing Approaches for FSE Feature&nbsp;Adoption</strong></a>. As always, Anne is ahead of us all, so I bring the article back to everyone&#8217;s attention. McCarthy divided her advice for different kind of users, some are for site owners and site builders, others for theme developers. Then she defined four level and explained each one with the matching tools and features, that collectively make out Full-Site Editing. </p>\n\n\n\n<p>If you are struggling to see the forest for the trees, let Lister and McCarthy guide you on the first steps of your journey. Or join us for <strong>Gutenberg Developer Hours</strong> on <strong><a href="https://www.meetup.com/wordpress-social-learning/events/283720638/">February 22, 2022, at 11 am ET / 16:00 UTC</a></strong></p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<h2 id="content-creators-and-site-owners-tools">Content Creators and Site Owners Tools</h2>\n\n\n\n<p>Let&#8217;s celebrate with <strong>Jamie Marsland</strong> the latest updates of WooCommerce Blocks and Storefront block, both premium plugins. They now leverage the new full-site-editing features of WordPress 5.9 and allow  for editing your store&#8217;s templates through the site editor. In this video Marsland demos, how to edit a Single Product page as well as a product category page. </p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<div class="toolbelt-video-wrapper"></div>\n</div>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Sarah Gooding</strong> reported on an addition to the Kadence Blocks collection: <a href="https://wptavern.com/kadence-blocks-2-2-4-adds-lottie-animations-block"><strong>Kadence Blocks 2.2.4&nbsp;Adds Lottie Animations Block</strong></a>.&#8221;Kadence Block’s implementation is in the free version of the plugin and includes block controls for further customizing the animations. Users can adjust playback settings, like autoplay, toggle controls on/off, and change the playback speed and loop settings. The animation’s size, padding, and margins, can all be customized.&#8221; Animations can be a fun tool to add a little whimsy to a site, usually, I find them overdone and quite distracting. So use at your own risk 🙂 </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Nathan Wrigley</strong> host of the <em>WordPress Jukebox </em>podcast had  <strong>Chris Lubkert</strong> and <strong>Rich Tabor </strong>on his show and discussed with them <a href="https://wptavern.com/podcast/13-chris-lubkert-and-rich-tabor-on-building-sites-with-extendify"><strong>Building Sites With Extendify</strong></a>. You can learn more about their vision for a future of page layouts and block patterns in WordPress.  Interestingly enough, Extendify&#8217;s 1400 block patterns and page layouts are all based only on core blocks, coupled with their unique utility design system. </p>\n\n\n\n<p>Rich Tabor also is a contributor on the Gutenberg repository and has been exchanging ideas and solutions with the Gutenberg team since the early days of the block editor in 2017. </p>\n\n\n\n<p><em>Nathan Wrigley has increased the frequency of publishing: After three years without it <a href="https://wptavern.com/feed/podcast">WordPress Jukebox </a>is now a weekly show again! You can subscribe to it on your favorite podcaster and you never miss another show. </em></p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>In his latest video, <a href="https://www.youtube.com/watch?v=OME2hZcUvUE"><strong>Future of WordPress Page Builders is Gutenberg</strong></a>, <strong>Matt Medeiros </strong>monologues about page builders in the era of Full-site Editing in Core. What do you think? </p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<div class="toolbelt-video-wrapper"></div>\n</div>\n\n\n\n<h2 id="wordpress-events">Hallway Hangouts, Webinars, and WordPress Social Learning events.</h2>\n\n\n\n<p>As shared last week, Anne McCarthy has a new FSE Outreach Program Exploration for you. <a href="https://make.wordpress.org/test/2022/02/02/fse-program-exploration-all-things-media/"> All Things Media</a> and <a href="https://wordpress.org/photos/" target="_blank" rel="noreferrer noopener">WordPress Photo directory</a> She invites you to the upcoming Hallway Hangout on <strong>February 16th, 12:30 pm ET / 17:30 pm UTC</strong> to with her and a designer from the Openverse project to chat about the call for testing. The link will be shared in the WPSlack channel <a href="https://wordpress.slack.com/archives/C015GUFFC00">#fse-outreach-experiment.</a> </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>If you can&#8217;t make it, <strong>Courtney Robertson</strong> invites you to the GoDaddy Event &#8220;<a href="https://events.godaddy.com/events/details/godaddy-events-godaddy-pro-online-presents-call-for-testing-wordpress-media/"><strong>Call For Testing WordPress Media&#8221;</strong></a> on February 18th, 2022 at 11 am ET / 16:00 UTC.  </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>On <strong>Feb 23rd 11 am ET / 16:00 UTC</strong> <strong>Hallway Hangout: Navigation Block. </strong>Designers and developers working on the feature will join Anne McCarthy to chat about the new feature. Join the WPSlack <a href="https://wordpress.slack.com/archives/C015GUFFC00">#fse-outreach-experiments</a> channel for details and zoom links. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>February 14, 2022 – 4 pm ET / 21:00 UTC </strong><br /><a href="https://www.meetup.com/wordpress-social-learning/events/283237147/"><strong>Exploring Theme Blocks</strong></a><strong> </strong>with Wes Theron</p>\n\n\n\n<p><strong>February 15, 2022 &#8211; 4:30 pm ET / 21:30 UTC </strong><br /><a href="https://www.meetup.com/wordpress-social-learning/events/283844528/"><strong>Adding Custom CSS to Your Site</strong></a> with Hugh Lashbrooke </p>\n\n\n\n<p><strong>February 16, 2022 1 pm ET / 18:00 UTC </strong><br /><a href="https://www.meetup.com/wordpress-social-learning/events/283827100/"><strong>Beginner&#8217;s Guide to Full Site Editing</strong></a> with Sarah Snow via WordPress Social Learning</p>\n\n\n\n<p><strong>February 18, 2022 1 pm ET / 18:00 UTC </strong><br /><a href="https://www.meetup.com/wordpress-social-learning/events/283927573/"><strong>Zero to Block Theme Series #5: From Site Editor to Theme</strong></a> with Daisy Olsen and Sarah Snow </p>\n\n\n\n<p><strong>February 21, 2022 &#8211; 12 pm (noon) ET / 17:00 UTC</strong><br /><a href="https://www.meetup.com/wordpress-social-learning/events/283644263/"><strong>Hello Blocks! Coding a custom block</strong></a> with Wes Theron and Ryan Welcher. </p>\n\n\n\n<p><strong>February 22, 2022 &#8211; 11 am ET / 16:00 UTC</strong><br /><strong><a href="https://www.meetup.com/wordpress-social-learning/events/283720638/">Gutenberg Developer Hours</a></strong> with Birgit Pauli-Haack and expert panel </p>\n\n\n\n<p><strong>March 1, 2022 5 pm ET / 22:00 UTC</strong> <br /><a href="https://www.meetup.com/wordpress-social-learning/events/283842451/"><strong>Intro to Templates and Template Parts</strong></a> with Wes Theron </p>\n\n\n\n<p><em>Featured Image: <a href="https://wordpress.org/photos/photo/97061fef69/">Jennifer Bourn &#8220;Pile of blue glass chunks in the sun&#8221;</a> found in the WordPress Photo Directory</em></p>\n\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p class="has-text-align-center"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>\n\n\n\n<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email">Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>\n\n\n\n<hr class="wp-block-separator is-style-wide" />";s: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, 12 Feb 2022 03:09:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:58:"WPTavern: WordPress Photo Directory Gets Its Own Make Team";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=129821";s:7:"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://wptavern.com/wordpress-photo-directory-gets-its-own-make-team";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4799:"<img />\n\n\n\n<p>The <a href="https://wordpress.org/photos/">WordPress Photo Directory</a> is taking off, growing to more than 1,400 approved free photos in under two months. After a successful call for testers and volunteer photo moderators, the directory has an enthusiastic team of contributors ready to move the project forward. </p>\n\n\n\n<p>Angela Jin&#8217;s <a href="https://make.wordpress.org/meta/2022/01/13/wordpress-photo-directory-call-for-volunteers/">pitch for photo moderators</a> resonated with a lot of people for a couple reasons &#8211; it outlined an approachable time commitment (1-2 hrs/wk) and didn&#8217;t require any special skills beyond appreciation of photography:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Photo Directory Moderators can expect to spend 1-2 hours in coming weeks learning about the Photo Directory and current moderation tools, and discussing future best practices. To keep the Photo Directory a thriving resource, Moderators are needed for the foreseeable future, perhaps dedicating up to an hour of their time each week.&nbsp;</p></blockquote>\n\n\n\n<p>Nearly two dozen people responded to this call. It was a good strategy for building a wide base of contributors instead of depending on a smaller team that would be required to devote more hours.</p>\n\n\n\n<p>This week Jin formalized the new contributor group, announcing the Photo Directory as <a href="https://make.wordpress.org/meta/2022/02/10/new-wordpress-make-team-the-photo-directory/">a new WordPress Make team</a>. Collaboration is now happening at the new #photos channel in WordPress Slack and the team will begin publishing  at <a href="http://make.wordpress.org/photos">make.wordpress.org/photos</a>. They will be working on two handbooks &#8211; a public one and a private one that will outline processes for moderators handling topics like curation and inappropriate content.</p>\n\n\n\n<p>There has been some confusion about the difference between the WordPress Photo Directory and the Openverse project, which indexes 600 million Creative Commons licensed and public domain image and audio files. Openverse pulls from many different sources, and the WordPress Photo Directory is a new source that will be included with all images licensed under the <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0</a> license. </p>\n\n\n\n<p>Automattic-sponsored Openverse contributor Zack Krida explained the difference between the WordPress Photo Directory and Openverse:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>The&nbsp;<a href="https://wordpress.org/photos/"><strong>WordPress Photo Directory</strong></a><strong>&nbsp;</strong>is both a new curated source of free, high-quality photographs and a new submission tool for Openverse, powered by the WordPress community. Without it, you’d need to use Flickr, Wikimedia Commons, or other sources to submit your work to Openverse.</p></blockquote>\n\n\n\n<p>Another way to contribute to the Photo Directory is by <a href="https://wordpress.org/photos/submit/">submitting photos</a>.  I am quite fond of making steel-cut oats for breakfast, so I decided to test out the submission process with a photograph of my oatmeal. The process is simple and takes less than a minute once you have already selected the image you want submit. Pending photographs are listed in a table after you submit, and the moderation queue for each account is limited to five at this time.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>I was surprised by one of the agreements before sending my photograph: &#8220;Photo must not contain any human faces.&#8221; The guidelines state that submissions cannot contain faces of people at this time for legal reasons. Hopefully, this limitation is being worked out before launch, because the directory needs faces to have the best chance at becoming a world class resource for free images.</p>\n\n\n\n<p>No attribution is required for CC0 photos, but it would be nice to have an easy way to copy attribution info and credit the photographer with a link back to the individual photo listing. This would also be helpful for furthering adoption of the photo directory, with links back coming from around the web. I filed a meta trac <a href="https://meta.trac.wordpress.org/ticket/6097">ticket</a> requesting the feature, as it looks like this is the best way to request an addition to the directory&#8217;s roadmap.</p>\n\n\n\n<p>The Photo Directory has so much momentum right now and offers a  good opportunity to contribute back to the WordPress world without having to know how to code. Meetings have not yet started for the project, but contributors can jump in on the new Slack channel and subscribe to the new <a href="http://make.wordpress.org/photos/">Photo Directory blog</a> on the Make network once it launches.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 12 Feb 2022 02:14:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:49;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:84:"WPTavern: Block, FSE, Hybrid, Universal? What Do We Call These New WordPress Themes?";s:7:"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=129860";s:7:"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://wptavern.com/block-fse-hybrid-universal-what-do-we-call-these-new-wordpress-themes";s: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:7006:"<p class="has-drop-cap">Ellen Bauer, developer and co-owner of ElmaStudio, posed the question on Twitter last week that many have been asking. What do we call these new types of WordPress themes made from blocks? She was not the first to ask. The question also came up via the <a href="https://poststatus.com/">Post Status</a> Slack chat earlier this week.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Naming is still so confusing <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f914.png" alt="🤔" class="wp-smiley" /> Is it block themes, FSE themes, block-based themes or better FSE block themes? I see all of them being used for the same thing, let’s change that asap!!! <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a> <a href="https://twitter.com/hashtag/Community?src=hash&ref_src=twsrc%5Etfw">#Community</a> <a href="https://twitter.com/hashtag/FullSiteEditing?src=hash&ref_src=twsrc%5Etfw">#FullSiteEditing</a> <a href="https://twitter.com/hashtag/FSE?src=hash&ref_src=twsrc%5Etfw">#FSE</a> <a href="https://twitter.com/hashtag/Gutenberg?src=hash&ref_src=twsrc%5Etfw">#Gutenberg</a></p>&mdash; Ellen Bauer (@ellenbauer) <a href="https://twitter.com/ellenbauer/status/1490123705972031489?ref_src=twsrc%5Etfw">February 6, 2022</a></blockquote>\n</div>\n\n\n\n<p>The short answer is that these new themes are &#8220;block themes.&#8221;</p>\n\n\n\n<p>The WordPress Themes Team decided to use this terminology in December 2021. The <a href="https://make.wordpress.org/themes/2021/12/15/themes-team-meeting-notes-december-14-2021/">consensus during their meeting</a> was to clarify the difference between block and classic themes.</p>\n\n\n\n<p>The terminology has also grown organically as the new theming system has emerged. Block themes are themes that are literally made from blocks. The long-term goal should be to simply call them &#8220;themes,&#8221; but the &#8220;block&#8221; prefix will stick with us for a while.</p>\n\n\n\n<p>The long answer is more nuanced. As Anne McCarthy noted in the Post Status discussion, there are four types of themes now:</p>\n\n\n\n<ul><li>Block</li><li>Classic</li><li>Hybrid</li><li>Universal</li></ul>\n\n\n\n<p>Technically, developers can create an entirely custom theming system. That is just how flexible WordPress is, but we will stick to the somewhat more official definitions. There are enough terms for our own little mini dictionary of theming as it is.</p>\n\n\n\n<h2 id="block-themes">Block Themes</h2>\n\n\n\n<img />Editing a block theme via the site editor.\n\n\n\n<p>Block themes have been officially supported since WordPress 5.9&#8217;s release last month. They provide users access to new tools such as the site editor and global styles interfaces. These features have replaced many past settings pages, such as the customizer and widgets screens.</p>\n\n\n\n<p><a href="https://wordpress.org/themes/twentytwentytwo/">Twenty Twenty-Two</a> is the first default to support this new set of tools. There is also a small but growing number of other block themes.</p>\n\n\n\n<p><em>Why do we not call them FSE themes?</em> Full Site Editing is a collection of components and not a single thing. WordPress has released several of these components before version 5.9, such as the template editor, block-based widgets, and <code>theme.json</code> support. In a sense, a classic theme with any level of feature support is also an FSE theme.</p>\n\n\n\n<p>The thing that makes block themes different from classic themes is that they are built from HTML templates made entirely of blocks. This automatically enables the site editor, template editor, global styles interface, and more.</p>\n\n\n\n<h2 id="classic-and-hybrid-themes">Classic and Hybrid Themes</h2>\n\n\n\n<img />Customizing Twenty Twenty, a classic theme.\n\n\n\n<p>I have grouped classic and hybrid themes together because there is no need to differentiate the two.</p>\n\n\n\n<p>Classic WordPress themes are those that we have known and loved all of these years. They feature PHP-based templates in most cases. There are some, like <a href="https://wordpress.org/themes/foxhound/">Foxhound</a>, that are primarily made of JavaScript. However, none have the necessary block HTML templates to qualify as a block theme.</p>\n\n\n\n<p>Hybrid themes are classic themes that have adopted one or more FSE components, such as the template editor or <code>theme.json</code>.</p>\n\n\n\n<p>I do not separate the two theme types because we have never done so before when themes adopt new features. For example, when the nav menus system was first introduced, there was no need to call themes something different based on whether they supported the new menu system. The same can be said for most other features in the past.</p>\n\n\n\n<p>If anything, the official theme directory may need to expand its tags to include additional features as they arise. Filters allow users to search for the things they want from a theme.</p>\n\n\n\n<h2 id="universal-themes">Universal Themes</h2>\n\n\n\n<p>Universal themes work in both a classic and site editor context. Ben Dwyer offered a <a href="https://themeshaper.com/2021/10/06/universal-themes/">more thorough explanation</a> via the Theme Shaper blog last year:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Universal themes are an attempt to bridge the gap between the classic themes and block themes, by adding some layers to a block theme to make it work.</p><p>A Universal theme is a block theme that can use the Full Site Editor but can also be configured in a more classic way. That means that you can use classic WordPress tools, like the Customizer, Menus and Widgets dashboards as well as the Site Editor.</p></blockquote>\n\n\n\n<p>I have not seen much appetite from developers for creating universal themes. I am not sure if any exist, at least not in the official directory.</p>\n\n\n\n<p>It is too early to tell if they will eventually catch on with theme authors. Supporting both classic and modern WordPress tools likely only makes sense for the most popular themes. Their authors may need to rework their codebase, opting into more FSE features and transitioning from a classic/hybrid state to universal support. If the demand is there, some will undoubtedly meet it.</p>\n\n\n\n<p>The support and maintenance burden would be unappealing for most. A clean break from classic is probably the best route for developers building with the latest WordPress features.</p>\n\n\n\n<hr class="wp-block-separator is-style-tavern-separator" />\n\n\n\n<p>Naming things is hard, but it is crucial to have equal footing among participants in discussions. The distinction between classic and block themes will likely be the most useful.</p>\n\n\n\n<p>I doubt the terms matter much for the average WordPress user. They need to know whether a theme supports Feature X or Feature Y. It has been a while since theme tags (filters) were overhauled, and many are outdated.  They might be worth revisiting to ensure that we are meeting user needs today.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 12 Feb 2022 01:49:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:"";}}}}}}}}}}}}}}}}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:"Mon, 28 Feb 2022 10:08:18 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Mon, 28 Feb 2022 10:00:09 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 1";s:16:"content-encoding";s:2:"br";}}s:5:"build";s:14:"20220126143042";}', 'no');
INSERT INTO `wpst_options` VALUES
(6208, '_transient_fusion_fontawesome_en', '.fa,.fab,.fal,.far,.fas{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;display:inline-block;font-style:normal;font-variant:normal;text-rendering:auto;line-height:1}.fa-lg{font-size:1.33333em;line-height:.75em;vertical-align:-.0667em}.fa-xs{font-size:.75em}.fa-sm{font-size:.875em}.fa-1x{font-size:1em}.fa-2x{font-size:2em}.fa-3x{font-size:3em}.fa-4x{font-size:4em}.fa-5x{font-size:5em}.fa-6x{font-size:6em}.fa-7x{font-size:7em}.fa-8x{font-size:8em}.fa-9x{font-size:9em}.fa-10x{font-size:10em}.fa-fw{text-align:center;width:1.25em}.fa-ul{list-style-type:none;margin-left:2.5em;padding-left:0}.fa-ul>li{position:relative}.fa-li{left:-2em;position:absolute;text-align:center;width:2em;line-height:inherit}.fa-border{border:solid .08em #eee;border-radius:.1em;padding:.2em .25em .15em}.fa-pull-left{float:left}.fa-pull-right{float:right}.fa.fa-pull-left,.fab.fa-pull-left,.fal.fa-pull-left,.far.fa-pull-left,.fas.fa-pull-left{margin-right:.3em}.fa.fa-pull-right,.fab.fa-pull-right,.fal.fa-pull-right,.far.fa-pull-right,.fas.fa-pull-right{margin-left:.3em}.fa-spin{-webkit-animation:fa-spin 2s infinite linear;animation:fa-spin 2s infinite linear}.fa-pulse{-webkit-animation:fa-spin 1s infinite steps(8);animation:fa-spin 1s infinite steps(8)}@-webkit-keyframes fa-spin{0%{-webkit-transform:rotate(0);transform:rotate(0)}100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}@keyframes fa-spin{0%{-webkit-transform:rotate(0);transform:rotate(0)}100%{-webkit-transform:rotate(360deg);transform:rotate(360deg)}}.fa-rotate-90{-webkit-transform:rotate(90deg);transform:rotate(90deg)}.fa-rotate-180{-webkit-transform:rotate(180deg);transform:rotate(180deg)}.fa-rotate-270{-webkit-transform:rotate(270deg);transform:rotate(270deg)}.fa-flip-horizontal{-webkit-transform:scale(-1,1);transform:scale(-1,1)}.fa-flip-vertical{-webkit-transform:scale(1,-1);transform:scale(1,-1)}.fa-flip-horizontal.fa-flip-vertical{-webkit-transform:scale(-1,-1);transform:scale(-1,-1)}:root .fa-flip-horizontal,:root .fa-flip-vertical,:root .fa-rotate-180,:root .fa-rotate-270,:root .fa-rotate-90{-webkit-filter:none;filter:none}.fa-stack{display:inline-block;height:2em;line-height:2em;position:relative;vertical-align:middle;width:2.5em}.fa-stack-1x,.fa-stack-2x{left:0;position:absolute;text-align:center;width:100%}.fa-stack-1x{line-height:inherit}.fa-stack-2x{font-size:2em}.fa-inverse{color:#fff}@font-face{font-family:"Font Awesome 5 Brands";font-style:normal;font-weight:normal;src:url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-brands-400.eot);src:url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-brands-400.eot?#iefix) format("embedded-opentype"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-brands-400.woff2) format("woff2"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-brands-400.woff) format("woff"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-brands-400.ttf) format("truetype"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-brands-400.svg#fontawesome) format("svg");font-display: block;}.fab{font-family:"Font Awesome 5 Brands"}@font-face{font-family:"Font Awesome 5 Free";font-style:normal;font-weight:400;src:url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-regular-400.eot);src:url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-regular-400.eot?#iefix) format("embedded-opentype"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-regular-400.woff2) format("woff2"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-regular-400.woff) format("woff"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-regular-400.ttf) format("truetype"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-regular-400.svg#fontawesome) format("svg");font-display: block;}.far{font-family:"Font Awesome 5 Free";font-weight:400;}@font-face{font-family:"Font Awesome 5 Free";font-style:normal;font-weight:900;src:url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-solid-900.eot);src:url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-solid-900.eot?#iefix) format("embedded-opentype"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-solid-900.woff2) format("woff2"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-solid-900.woff) format("woff"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-solid-900.ttf) format("truetype"),url(//staging.redtickeducation.com/wp/wp-content/themes/Avada/includes/lib/assets/fonts/fontawesome/webfonts/fa-solid-900.svg#fontawesome) format("svg");font-display: block;}.fa,.fas{font-family:"Font Awesome 5 Free";font-weight:900}.fa-500px:before{content:"\\f26e"}.fa-accessible-icon:before{content:"\\f368"}.fa-accusoft:before{content:"\\f369"}.fa-acquisitions-incorporated:before{content:"\\f6af"}.fa-ad:before{content:"\\f641"}.fa-address-book:before{content:"\\f2b9"}.fa-address-card:before{content:"\\f2bb"}.fa-adjust:before{content:"\\f042"}.fa-adn:before{content:"\\f170"}.fa-adversal:before{content:"\\f36a"}.fa-affiliatetheme:before{content:"\\f36b"}.fa-air-freshener:before{content:"\\f5d0"}.fa-airbnb:before{content:"\\f834"}.fa-algolia:before{content:"\\f36c"}.fa-align-center:before{content:"\\f037"}.fa-align-justify:before{content:"\\f039"}.fa-align-left:before{content:"\\f036"}.fa-align-right:before{content:"\\f038"}.fa-alipay:before{content:"\\f642"}.fa-allergies:before{content:"\\f461"}.fa-amazon:before{content:"\\f270"}.fa-amazon-pay:before{content:"\\f42c"}.fa-ambulance:before{content:"\\f0f9"}.fa-american-sign-language-interpreting:before{content:"\\f2a3"}.fa-amilia:before{content:"\\f36d"}.fa-anchor:before{content:"\\f13d"}.fa-android:before{content:"\\f17b"}.fa-angellist:before{content:"\\f209"}.fa-angle-double-down:before{content:"\\f103"}.fa-angle-double-left:before{content:"\\f100"}.fa-angle-double-right:before{content:"\\f101"}.fa-angle-double-up:before{content:"\\f102"}.fa-angle-down:before{content:"\\f107"}.fa-angle-left:before{content:"\\f104"}.fa-angle-right:before{content:"\\f105"}.fa-angle-up:before{content:"\\f106"}.fa-angry:before{content:"\\f556"}.fa-angrycreative:before{content:"\\f36e"}.fa-angular:before{content:"\\f420"}.fa-ankh:before{content:"\\f644"}.fa-app-store:before{content:"\\f36f"}.fa-app-store-ios:before{content:"\\f370"}.fa-apper:before{content:"\\f371"}.fa-apple:before{content:"\\f179"}.fa-apple-alt:before{content:"\\f5d1"}.fa-apple-pay:before{content:"\\f415"}.fa-archive:before{content:"\\f187"}.fa-archway:before{content:"\\f557"}.fa-arrow-alt-circle-down:before{content:"\\f358"}.fa-arrow-alt-circle-left:before{content:"\\f359"}.fa-arrow-alt-circle-right:before{content:"\\f35a"}.fa-arrow-alt-circle-up:before{content:"\\f35b"}.fa-arrow-circle-down:before{content:"\\f0ab"}.fa-arrow-circle-left:before{content:"\\f0a8"}.fa-arrow-circle-right:before{content:"\\f0a9"}.fa-arrow-circle-up:before{content:"\\f0aa"}.fa-arrow-down:before{content:"\\f063"}.fa-arrow-left:before{content:"\\f060"}.fa-arrow-right:before{content:"\\f061"}.fa-arrow-up:before{content:"\\f062"}.fa-arrows-alt:before{content:"\\f0b2"}.fa-arrows-alt-h:before{content:"\\f337"}.fa-arrows-alt-v:before{content:"\\f338"}.fa-artstation:before{content:"\\f77a"}.fa-assistive-listening-systems:before{content:"\\f2a2"}.fa-asterisk:before{content:"\\f069"}.fa-asymmetrik:before{content:"\\f372"}.fa-at:before{content:"\\f1fa"}.fa-atlas:before{content:"\\f558"}.fa-atlassian:before{content:"\\f77b"}.fa-atom:before{content:"\\f5d2"}.fa-audible:before{content:"\\f373"}.fa-audio-description:before{content:"\\f29e"}.fa-autoprefixer:before{content:"\\f41c"}.fa-avianex:before{content:"\\f374"}.fa-aviato:before{content:"\\f421"}.fa-award:before{content:"\\f559"}.fa-aws:before{content:"\\f375"}.fa-baby:before{content:"\\f77c"}.fa-baby-carriage:before{content:"\\f77d"}.fa-backspace:before{content:"\\f55a"}.fa-backward:before{content:"\\f04a"}.fa-bacon:before{content:"\\f7e5"}.fa-bacteria:before{content:"\\e059"}.fa-bacterium:before{content:"\\e05a"}.fa-bahai:before{content:"\\f666"}.fa-balance-scale:before{content:"\\f24e"}.fa-balance-scale-left:before{content:"\\f515"}.fa-balance-scale-right:before{content:"\\f516"}.fa-ban:before{content:"\\f05e"}.fa-band-aid:before{content:"\\f462"}.fa-bandcamp:before{content:"\\f2d5"}.fa-barcode:before{content:"\\f02a"}.fa-bars:before{content:"\\f0c9"}.fa-baseball-ball:before{content:"\\f433"}.fa-basketball-ball:before{content:"\\f434"}.fa-bath:before{content:"\\f2cd"}.fa-battery-empty:before{content:"\\f244"}.fa-battery-full:before{content:"\\f240"}.fa-battery-half:before{content:"\\f242"}.fa-battery-quarter:before{content:"\\f243"}.fa-battery-three-quarters:before{content:"\\f241"}.fa-battle-net:before{content:"\\f835"}.fa-bed:before{content:"\\f236"}.fa-beer:before{content:"\\f0fc"}.fa-behance:before{content:"\\f1b4"}.fa-behance-square:before{content:"\\f1b5"}.fa-bell:before{content:"\\f0f3"}.fa-bell-slash:before{content:"\\f1f6"}.fa-bezier-curve:before{content:"\\f55b"}.fa-bible:before{content:"\\f647"}.fa-bicycle:before{content:"\\f206"}.fa-biking:before{content:"\\f84a"}.fa-bimobject:before{content:"\\f378"}.fa-binoculars:before{content:"\\f1e5"}.fa-biohazard:before{content:"\\f780"}.fa-birthday-cake:before{content:"\\f1fd"}.fa-bitbucket:before{content:"\\f171"}.fa-bitcoin:before{content:"\\f379"}.fa-bity:before{content:"\\f37a"}.fa-black-tie:before{content:"\\f27e"}.fa-blackberry:before{content:"\\f37b"}.fa-blender:before{content:"\\f517"}.fa-blender-phone:before{content:"\\f6b6"}.fa-blind:before{content:"\\f29d"}.fa-blog:before{content:"\\f781"}.fa-blogger:before{content:"\\f37c"}.fa-blogger-b:before{content:"\\f37d"}.fa-bluetooth:before{content:"\\f293"}.fa-bluetooth-b:before{content:"\\f294"}.fa-bold:before{content:"\\f032"}.fa-bolt:before{content:"\\f0e7"}.fa-bomb:before{content:"\\f1e2"}.fa-bone:before{content:"\\f5d7"}.fa-bong:before{content:"\\f55c"}.fa-book:before{content:"\\f02d"}.fa-book-dead:before{content:"\\f6b7"}.fa-book-medical:before{content:"\\f7e6"}.fa-book-open:before{content:"\\f518"}.fa-book-reader:before{content:"\\f5da"}.fa-bookmark:before{content:"\\f02e"}.fa-bootstrap:before{content:"\\f836"}.fa-border-all:before{content:"\\f84c"}.fa-border-none:before{content:"\\f850"}.fa-border-style:before{content:"\\f853"}.fa-bowling-ball:before{content:"\\f436"}.fa-box:before{content:"\\f466"}.fa-box-open:before{content:"\\f49e"}.fa-box-tissue:before{content:"\\e05b"}.fa-boxes:before{content:"\\f468"}.fa-braille:before{content:"\\f2a1"}.fa-brain:before{content:"\\f5dc"}.fa-bread-slice:before{content:"\\f7ec"}.fa-briefcase:before{content:"\\f0b1"}.fa-briefcase-medical:before{content:"\\f469"}.fa-broadcast-tower:before{content:"\\f519"}.fa-broom:before{content:"\\f51a"}.fa-brush:before{content:"\\f55d"}.fa-btc:before{content:"\\f15a"}.fa-buffer:before{content:"\\f837"}.fa-bug:before{content:"\\f188"}.fa-building:before{content:"\\f1ad"}.fa-bullhorn:before{content:"\\f0a1"}.fa-bullseye:before{content:"\\f140"}.fa-burn:before{content:"\\f46a"}.fa-buromobelexperte:before{content:"\\f37f"}.fa-bus:before{content:"\\f207"}.fa-bus-alt:before{content:"\\f55e"}.fa-business-time:before{content:"\\f64a"}.fa-buy-n-large:before{content:"\\f8a6"}.fa-buysellads:before{content:"\\f20d"}.fa-calculator:before{content:"\\f1ec"}.fa-calendar:before{content:"\\f133"}.fa-calendar-alt:before{content:"\\f073"}.fa-calendar-check:before{content:"\\f274"}.fa-calendar-day:before{content:"\\f783"}.fa-calendar-minus:before{content:"\\f272"}.fa-calendar-plus:before{content:"\\f271"}.fa-calendar-times:before{content:"\\f273"}.fa-calendar-week:before{content:"\\f784"}.fa-camera:before{content:"\\f030"}.fa-camera-retro:before{content:"\\f083"}.fa-campground:before{content:"\\f6bb"}.fa-canadian-maple-leaf:before{content:"\\f785"}.fa-candy-cane:before{content:"\\f786"}.fa-cannabis:before{content:"\\f55f"}.fa-capsules:before{content:"\\f46b"}.fa-car:before{content:"\\f1b9"}.fa-car-alt:before{content:"\\f5de"}.fa-car-battery:before{content:"\\f5df"}.fa-car-crash:before{content:"\\f5e1"}.fa-car-side:before{content:"\\f5e4"}.fa-caravan:before{content:"\\f8ff"}.fa-caret-down:before{content:"\\f0d7"}.fa-caret-left:before{content:"\\f0d9"}.fa-caret-right:before{content:"\\f0da"}.fa-caret-square-down:before{content:"\\f150"}.fa-caret-square-left:before{content:"\\f191"}.fa-caret-square-right:before{content:"\\f152"}.fa-caret-square-up:before{content:"\\f151"}.fa-caret-up:before{content:"\\f0d8"}.fa-carrot:before{content:"\\f787"}.fa-cart-arrow-down:before{content:"\\f218"}.fa-cart-plus:before{content:"\\f217"}.fa-cash-register:before{content:"\\f788"}.fa-cat:before{content:"\\f6be"}.fa-cc-amazon-pay:before{content:"\\f42d"}.fa-cc-amex:before{content:"\\f1f3"}.fa-cc-apple-pay:before{content:"\\f416"}.fa-cc-diners-club:before{content:"\\f24c"}.fa-cc-discover:before{content:"\\f1f2"}.fa-cc-jcb:before{content:"\\f24b"}.fa-cc-mastercard:before{content:"\\f1f1"}.fa-cc-paypal:before{content:"\\f1f4"}.fa-cc-stripe:before{content:"\\f1f5"}.fa-cc-visa:before{content:"\\f1f0"}.fa-centercode:before{content:"\\f380"}.fa-centos:before{content:"\\f789"}.fa-certificate:before{content:"\\f0a3"}.fa-chair:before{content:"\\f6c0"}.fa-chalkboard:before{content:"\\f51b"}.fa-chalkboard-teacher:before{content:"\\f51c"}.fa-charging-station:before{content:"\\f5e7"}.fa-chart-area:before{content:"\\f1fe"}.fa-chart-bar:before{content:"\\f080"}.fa-chart-line:before{content:"\\f201"}.fa-chart-pie:before{content:"\\f200"}.fa-check:before{content:"\\f00c"}.fa-check-circle:before{content:"\\f058"}.fa-check-double:before{content:"\\f560"}.fa-check-square:before{content:"\\f14a"}.fa-cheese:before{content:"\\f7ef"}.fa-chess:before{content:"\\f439"}.fa-chess-bishop:before{content:"\\f43a"}.fa-chess-board:before{content:"\\f43c"}.fa-chess-king:before{content:"\\f43f"}.fa-chess-knight:before{content:"\\f441"}.fa-chess-pawn:before{content:"\\f443"}.fa-chess-queen:before{content:"\\f445"}.fa-chess-rook:before{content:"\\f447"}.fa-chevron-circle-down:before{content:"\\f13a"}.fa-chevron-circle-left:before{content:"\\f137"}.fa-chevron-circle-right:before{content:"\\f138"}.fa-chevron-circle-up:before{content:"\\f139"}.fa-chevron-down:before{content:"\\f078"}.fa-chevron-left:before{content:"\\f053"}.fa-chevron-right:before{content:"\\f054"}.fa-chevron-up:before{content:"\\f077"}.fa-child:before{content:"\\f1ae"}.fa-chrome:before{content:"\\f268"}.fa-chromecast:before{content:"\\f838"}.fa-church:before{content:"\\f51d"}.fa-circle:before{content:"\\f111"}.fa-circle-notch:before{content:"\\f1ce"}.fa-city:before{content:"\\f64f"}.fa-clinic-medical:before{content:"\\f7f2"}.fa-clipboard:before{content:"\\f328"}.fa-clipboard-check:before{content:"\\f46c"}.fa-clipboard-list:before{content:"\\f46d"}.fa-clock:before{content:"\\f017"}.fa-clone:before{content:"\\f24d"}.fa-closed-captioning:before{content:"\\f20a"}.fa-cloud:before{content:"\\f0c2"}.fa-cloud-download-alt:before{content:"\\f381"}.fa-cloud-meatball:before{content:"\\f73b"}.fa-cloud-moon:before{content:"\\f6c3"}.fa-cloud-moon-rain:before{content:"\\f73c"}.fa-cloud-rain:before{content:"\\f73d"}.fa-cloud-showers-heavy:before{content:"\\f740"}.fa-cloud-sun:before{content:"\\f6c4"}.fa-cloud-sun-rain:before{content:"\\f743"}.fa-cloud-upload-alt:before{content:"\\f382"}.fa-cloudflare:before{content:"\\e07d"}.fa-cloudscale:before{content:"\\f383"}.fa-cloudsmith:before{content:"\\f384"}.fa-cloudversify:before{content:"\\f385"}.fa-cocktail:before{content:"\\f561"}.fa-code:before{content:"\\f121"}.fa-code-branch:before{content:"\\f126"}.fa-codepen:before{content:"\\f1cb"}.fa-codiepie:before{content:"\\f284"}.fa-coffee:before{content:"\\f0f4"}.fa-cog:before{content:"\\f013"}.fa-cogs:before{content:"\\f085"}.fa-coins:before{content:"\\f51e"}.fa-columns:before{content:"\\f0db"}.fa-comment:before{content:"\\f075"}.fa-comment-alt:before{content:"\\f27a"}.fa-comment-dollar:before{content:"\\f651"}.fa-comment-dots:before{content:"\\f4ad"}.fa-comment-medical:before{content:"\\f7f5"}.fa-comment-slash:before{content:"\\f4b3"}.fa-comments:before{content:"\\f086"}.fa-comments-dollar:before{content:"\\f653"}.fa-compact-disc:before{content:"\\f51f"}.fa-compass:before{content:"\\f14e"}.fa-compress:before{content:"\\f066"}.fa-compress-alt:before{content:"\\f422"}.fa-compress-arrows-alt:before{content:"\\f78c"}.fa-concierge-bell:before{content:"\\f562"}.fa-confluence:before{content:"\\f78d"}.fa-connectdevelop:before{content:"\\f20e"}.fa-contao:before{content:"\\f26d"}.fa-cookie:before{content:"\\f563"}.fa-cookie-bite:before{content:"\\f564"}.fa-copy:before{content:"\\f0c5"}.fa-copyright:before{content:"\\f1f9"}.fa-cotton-bureau:before{content:"\\f89e"}.fa-couch:before{content:"\\f4b8"}.fa-cpanel:before{content:"\\f388"}.fa-creative-commons:before{content:"\\f25e"}.fa-creative-commons-by:before{content:"\\f4e7"}.fa-creative-commons-nc:before{content:"\\f4e8"}.fa-creative-commons-nc-eu:before{content:"\\f4e9"}.fa-creative-commons-nc-jp:before{content:"\\f4ea"}.fa-creative-commons-nd:before{content:"\\f4eb"}.fa-creative-commons-pd:before{content:"\\f4ec"}.fa-creative-commons-pd-alt:before{content:"\\f4ed"}.fa-creative-commons-remix:before{content:"\\f4ee"}.fa-creative-commons-sa:before{content:"\\f4ef"}.fa-creative-commons-sampling:before{content:"\\f4f0"}.fa-creative-commons-sampling-plus:before{content:"\\f4f1"}.fa-creative-commons-share:before{content:"\\f4f2"}.fa-creative-commons-zero:before{content:"\\f4f3"}.fa-credit-card:before{content:"\\f09d"}.fa-critical-role:before{content:"\\f6c9"}.fa-crop:before{content:"\\f125"}.fa-crop-alt:before{content:"\\f565"}.fa-cross:before{content:"\\f654"}.fa-crosshairs:before{content:"\\f05b"}.fa-crow:before{content:"\\f520"}.fa-crown:before{content:"\\f521"}.fa-crutch:before{content:"\\f7f7"}.fa-css3:before{content:"\\f13c"}.fa-css3-alt:before{content:"\\f38b"}.fa-cube:before{content:"\\f1b2"}.fa-cubes:before{content:"\\f1b3"}.fa-cut:before{content:"\\f0c4"}.fa-cuttlefish:before{content:"\\f38c"}.fa-d-and-d:before{content:"\\f38d"}.fa-d-and-d-beyond:before{content:"\\f6ca"}.fa-dailymotion:before{content:"\\e052"}.fa-dashcube:before{content:"\\f210"}.fa-database:before{content:"\\f1c0"}.fa-deaf:before{content:"\\f2a4"}.fa-deezer:before{content:"\\e077"}.fa-delicious:before{content:"\\f1a5"}.fa-democrat:before{content:"\\f747"}.fa-deploydog:before{content:"\\f38e"}.fa-deskpro:before{content:"\\f38f"}.fa-desktop:before{content:"\\f108"}.fa-dev:before{content:"\\f6cc"}.fa-deviantart:before{content:"\\f1bd"}.fa-dharmachakra:before{content:"\\f655"}.fa-dhl:before{content:"\\f790"}.fa-diagnoses:before{content:"\\f470"}.fa-diaspora:before{content:"\\f791"}.fa-dice:before{content:"\\f522"}.fa-dice-d20:before{content:"\\f6cf"}.fa-dice-d6:before{content:"\\f6d1"}.fa-dice-five:before{content:"\\f523"}.fa-dice-four:before{content:"\\f524"}.fa-dice-one:before{content:"\\f525"}.fa-dice-six:before{content:"\\f526"}.fa-dice-three:before{content:"\\f527"}.fa-dice-two:before{content:"\\f528"}.fa-digg:before{content:"\\f1a6"}.fa-digital-ocean:before{content:"\\f391"}.fa-digital-tachograph:before{content:"\\f566"}.fa-directions:before{content:"\\f5eb"}.fa-discord:before{content:"\\f392"}.fa-discourse:before{content:"\\f393"}.fa-disease:before{content:"\\f7fa"}.fa-divide:before{content:"\\f529"}.fa-dizzy:before{content:"\\f567"}.fa-dna:before{content:"\\f471"}.fa-dochub:before{content:"\\f394"}.fa-docker:before{content:"\\f395"}.fa-dog:before{content:"\\f6d3"}.fa-dollar-sign:before{content:"\\f155"}.fa-dolly:before{content:"\\f472"}.fa-dolly-flatbed:before{content:"\\f474"}.fa-donate:before{content:"\\f4b9"}.fa-door-closed:before{content:"\\f52a"}.fa-door-open:before{content:"\\f52b"}.fa-dot-circle:before{content:"\\f192"}.fa-dove:before{content:"\\f4ba"}.fa-download:before{content:"\\f019"}.fa-draft2digital:before{content:"\\f396"}.fa-drafting-compass:before{content:"\\f568"}.fa-dragon:before{content:"\\f6d5"}.fa-draw-polygon:before{content:"\\f5ee"}.fa-dribbble:before{content:"\\f17d"}.fa-dribbble-square:before{content:"\\f397"}.fa-dropbox:before{content:"\\f16b"}.fa-drum:before{content:"\\f569"}.fa-drum-steelpan:before{content:"\\f56a"}.fa-drumstick-bite:before{content:"\\f6d7"}.fa-drupal:before{content:"\\f1a9"}.fa-dumbbell:before{content:"\\f44b"}.fa-dumpster:before{content:"\\f793"}.fa-dumpster-fire:before{content:"\\f794"}.fa-dungeon:before{content:"\\f6d9"}.fa-dyalog:before{content:"\\f399"}.fa-earlybirds:before{content:"\\f39a"}.fa-ebay:before{content:"\\f4f4"}.fa-edge:before{content:"\\f282"}.fa-edge-legacy:before{content:"\\e078"}.fa-edit:before{content:"\\f044"}.fa-egg:before{content:"\\f7fb"}.fa-eject:before{content:"\\f052"}.fa-elementor:before{content:"\\f430"}.fa-ellipsis-h:before{content:"\\f141"}.fa-ellipsis-v:before{content:"\\f142"}.fa-ello:before{content:"\\f5f1"}.fa-ember:before{content:"\\f423"}.fa-empire:before{content:"\\f1d1"}.fa-envelope:before{content:"\\f0e0"}.fa-envelope-open:before{content:"\\f2b6"}.fa-envelope-open-text:before{content:"\\f658"}.fa-envelope-square:before{content:"\\f199"}.fa-envira:before{content:"\\f299"}.fa-equals:before{content:"\\f52c"}.fa-eraser:before{content:"\\f12d"}.fa-erlang:before{content:"\\f39d"}.fa-ethereum:before{content:"\\f42e"}.fa-ethernet:before{content:"\\f796"}.fa-etsy:before{content:"\\f2d7"}.fa-euro-sign:before{content:"\\f153"}.fa-evernote:before{content:"\\f839"}.fa-exchange-alt:before{content:"\\f362"}.fa-exclamation:before{content:"\\f12a"}.fa-exclamation-circle:before{content:"\\f06a"}.fa-exclamation-triangle:before{content:"\\f071"}.fa-expand:before{content:"\\f065"}.fa-expand-alt:before{content:"\\f424"}.fa-expand-arrows-alt:before{content:"\\f31e"}.fa-expeditedssl:before{content:"\\f23e"}.fa-external-link-alt:before{content:"\\f35d"}.fa-external-link-square-alt:before{content:"\\f360"}.fa-eye:before{content:"\\f06e"}.fa-eye-dropper:before{content:"\\f1fb"}.fa-eye-slash:before{content:"\\f070"}.fa-facebook:before{content:"\\f09a"}.fa-facebook-f:before{content:"\\f39e"}.fa-facebook-messenger:before{content:"\\f39f"}.fa-facebook-square:before{content:"\\f082"}.fa-fan:before{content:"\\f863"}.fa-fantasy-flight-games:before{content:"\\f6dc"}.fa-fast-backward:before{content:"\\f049"}.fa-fast-forward:before{content:"\\f050"}.fa-faucet:before{content:"\\e005"}.fa-fax:before{content:"\\f1ac"}.fa-feather:before{content:"\\f52d"}.fa-feather-alt:before{content:"\\f56b"}.fa-fedex:before{content:"\\f797"}.fa-fedora:before{content:"\\f798"}.fa-female:before{content:"\\f182"}.fa-fighter-jet:before{content:"\\f0fb"}.fa-figma:before{content:"\\f799"}.fa-file:before{content:"\\f15b"}.fa-file-alt:before{content:"\\f15c"}.fa-file-archive:before{content:"\\f1c6"}.fa-file-audio:before{content:"\\f1c7"}.fa-file-code:before{content:"\\f1c9"}.fa-file-contract:before{content:"\\f56c"}.fa-file-csv:before{content:"\\f6dd"}.fa-file-download:before{content:"\\f56d"}.fa-file-excel:before{content:"\\f1c3"}.fa-file-export:before{content:"\\f56e"}.fa-file-image:before{content:"\\f1c5"}.fa-file-import:before{content:"\\f56f"}.fa-file-invoice:before{content:"\\f570"}.fa-file-invoice-dollar:before{content:"\\f571"}.fa-file-medical:before{content:"\\f477"}.fa-file-medical-alt:before{content:"\\f478"}.fa-file-pdf:before{content:"\\f1c1"}.fa-file-powerpoint:before{content:"\\f1c4"}.fa-file-prescription:before{content:"\\f572"}.fa-file-signature:before{content:"\\f573"}.fa-file-upload:before{content:"\\f574"}.fa-file-video:before{content:"\\f1c8"}.fa-file-word:before{content:"\\f1c2"}.fa-fill:before{content:"\\f575"}.fa-fill-drip:before{content:"\\f576"}.fa-film:before{content:"\\f008"}.fa-filter:before{content:"\\f0b0"}.fa-fingerprint:before{content:"\\f577"}.fa-fire:before{content:"\\f06d"}.fa-fire-alt:before{content:"\\f7e4"}.fa-fire-extinguisher:before{content:"\\f134"}.fa-firefox:before{content:"\\f269"}.fa-firefox-browser:before{content:"\\e007"}.fa-first-aid:before{content:"\\f479"}.fa-first-order:before{content:"\\f2b0"}.fa-first-order-alt:before{content:"\\f50a"}.fa-firstdraft:before{content:"\\f3a1"}.fa-fish:before{content:"\\f578"}.fa-fist-raised:before{content:"\\f6de"}.fa-flag:before{content:"\\f024"}.fa-flag-checkered:before{content:"\\f11e"}.fa-flag-usa:before{content:"\\f74d"}.fa-flask:before{content:"\\f0c3"}.fa-flickr:before{content:"\\f16e"}.fa-flipboard:before{content:"\\f44d"}.fa-flushed:before{content:"\\f579"}.fa-fly:before{content:"\\f417"}.fa-folder:before{content:"\\f07b"}.fa-folder-minus:before{content:"\\f65d"}.fa-folder-open:before{content:"\\f07c"}.fa-folder-plus:before{content:"\\f65e"}.fa-font:before{content:"\\f031"}.fa-font-awesome:before{content:"\\f2b4"}.fa-font-awesome-alt:before{content:"\\f35c"}.fa-font-awesome-flag:before{content:"\\f425"}.fa-fonticons:before{content:"\\f280"}.fa-fonticons-fi:before{content:"\\f3a2"}.fa-football-ball:before{content:"\\f44e"}.fa-fort-awesome:before{content:"\\f286"}.fa-fort-awesome-alt:before{content:"\\f3a3"}.fa-forumbee:before{content:"\\f211"}.fa-forward:before{content:"\\f04e"}.fa-foursquare:before{content:"\\f180"}.fa-free-code-camp:before{content:"\\f2c5"}.fa-freebsd:before{content:"\\f3a4"}.fa-frog:before{content:"\\f52e"}.fa-frown:before{content:"\\f119"}.fa-frown-open:before{content:"\\f57a"}.fa-fulcrum:before{content:"\\f50b"}.fa-funnel-dollar:before{content:"\\f662"}.fa-futbol:before{content:"\\f1e3"}.fa-galactic-republic:before{content:"\\f50c"}.fa-galactic-senate:before{content:"\\f50d"}.fa-gamepad:before{content:"\\f11b"}.fa-gas-pump:before{content:"\\f52f"}.fa-gavel:before{content:"\\f0e3"}.fa-gem:before{content:"\\f3a5"}.fa-genderless:before{content:"\\f22d"}.fa-get-pocket:before{content:"\\f265"}.fa-gg:before{content:"\\f260"}.fa-gg-circle:before{content:"\\f261"}.fa-ghost:before{content:"\\f6e2"}.fa-gift:before{content:"\\f06b"}.fa-gifts:before{content:"\\f79c"}.fa-git:before{content:"\\f1d3"}.fa-git-alt:before{content:"\\f841"}.fa-git-square:before{content:"\\f1d2"}.fa-github:before{content:"\\f09b"}.fa-github-alt:before{content:"\\f113"}.fa-github-square:before{content:"\\f092"}.fa-gitkraken:before{content:"\\f3a6"}.fa-gitlab:before{content:"\\f296"}.fa-gitter:before{content:"\\f426"}.fa-glass-cheers:before{content:"\\f79f"}.fa-glass-martini:before{content:"\\f000"}.fa-glass-martini-alt:before{content:"\\f57b"}.fa-glass-whiskey:before{content:"\\f7a0"}.fa-glasses:before{content:"\\f530"}.fa-glide:before{content:"\\f2a5"}.fa-glide-g:before{content:"\\f2a6"}.fa-globe:before{content:"\\f0ac"}.fa-globe-africa:before{content:"\\f57c"}.fa-globe-americas:before{content:"\\f57d"}.fa-globe-asia:before{content:"\\f57e"}.fa-globe-europe:before{content:"\\f7a2"}.fa-gofore:before{content:"\\f3a7"}.fa-golf-ball:before{content:"\\f450"}.fa-goodreads:before{content:"\\f3a8"}.fa-goodreads-g:before{content:"\\f3a9"}.fa-google:before{content:"\\f1a0"}.fa-google-drive:before{content:"\\f3aa"}.fa-google-pay:before{content:"\\e079"}.fa-google-play:before{content:"\\f3ab"}.fa-google-plus:before{content:"\\f2b3"}.fa-google-plus-g:before{content:"\\f0d5"}.fa-google-plus-square:before{content:"\\f0d4"}.fa-google-wallet:before{content:"\\f1ee"}.fa-gopuram:before{content:"\\f664"}.fa-graduation-cap:before{content:"\\f19d"}.fa-gratipay:before{content:"\\f184"}.fa-grav:before{content:"\\f2d6"}.fa-greater-than:before{content:"\\f531"}.fa-greater-than-equal:before{content:"\\f532"}.fa-grimace:before{content:"\\f57f"}.fa-grin:before{content:"\\f580"}.fa-grin-alt:before{content:"\\f581"}.fa-grin-beam:before{content:"\\f582"}.fa-grin-beam-sweat:before{content:"\\f583"}.fa-grin-hearts:before{content:"\\f584"}.fa-grin-squint:before{content:"\\f585"}.fa-grin-squint-tears:before{content:"\\f586"}.fa-grin-stars:before{content:"\\f587"}.fa-grin-tears:before{content:"\\f588"}.fa-grin-tongue:before{content:"\\f589"}.fa-grin-tongue-squint:before{content:"\\f58a"}.fa-grin-tongue-wink:before{content:"\\f58b"}.fa-grin-wink:before{content:"\\f58c"}.fa-grip-horizontal:before{content:"\\f58d"}.fa-grip-lines:before{content:"\\f7a4"}.fa-grip-lines-vertical:before{content:"\\f7a5"}.fa-grip-vertical:before{content:"\\f58e"}.fa-gripfire:before{content:"\\f3ac"}.fa-grunt:before{content:"\\f3ad"}.fa-guilded:before{content:"\\e07e"}.fa-guitar:before{content:"\\f7a6"}.fa-gulp:before{content:"\\f3ae"}.fa-h-square:before{content:"\\f0fd"}.fa-hacker-news:before{content:"\\f1d4"}.fa-hacker-news-square:before{content:"\\f3af"}.fa-hackerrank:before{content:"\\f5f7"}.fa-hamburger:before{content:"\\f805"}.fa-hammer:before{content:"\\f6e3"}.fa-hamsa:before{content:"\\f665"}.fa-hand-holding:before{content:"\\f4bd"}.fa-hand-holding-heart:before{content:"\\f4be"}.fa-hand-holding-medical:before{content:"\\e05c"}.fa-hand-holding-usd:before{content:"\\f4c0"}.fa-hand-holding-water:before{content:"\\f4c1"}.fa-hand-lizard:before{content:"\\f258"}.fa-hand-middle-finger:before{content:"\\f806"}.fa-hand-paper:before{content:"\\f256"}.fa-hand-peace:before{content:"\\f25b"}.fa-hand-point-down:before{content:"\\f0a7"}.fa-hand-point-left:before{content:"\\f0a5"}.fa-hand-point-right:before{content:"\\f0a4"}.fa-hand-point-up:before{content:"\\f0a6"}.fa-hand-pointer:before{content:"\\f25a"}.fa-hand-rock:before{content:"\\f255"}.fa-hand-scissors:before{content:"\\f257"}.fa-hand-sparkles:before{content:"\\e05d"}.fa-hand-spock:before{content:"\\f259"}.fa-hands:before{content:"\\f4c2"}.fa-hands-helping:before{content:"\\f4c4"}.fa-hands-wash:before{content:"\\e05e"}.fa-handshake:before{content:"\\f2b5"}.fa-handshake-alt-slash:before{content:"\\e05f"}.fa-handshake-slash:before{content:"\\e060"}.fa-hanukiah:before{content:"\\f6e6"}.fa-hard-hat:before{content:"\\f807"}.fa-hashtag:before{content:"\\f292"}.fa-hat-cowboy:before{content:"\\f8c0"}.fa-hat-cowboy-side:before{content:"\\f8c1"}.fa-hat-wizard:before{content:"\\f6e8"}.fa-hdd:before{content:"\\f0a0"}.fa-head-side-cough:before{content:"\\e061"}.fa-head-side-cough-slash:before{content:"\\e062"}.fa-head-side-mask:before{content:"\\e063"}.fa-head-side-virus:before{content:"\\e064"}.fa-heading:before{content:"\\f1dc"}.fa-headphones:before{content:"\\f025"}.fa-headphones-alt:before{content:"\\f58f"}.fa-headset:before{content:"\\f590"}.fa-heart:before{content:"\\f004"}.fa-heart-broken:before{content:"\\f7a9"}.fa-heartbeat:before{content:"\\f21e"}.fa-helicopter:before{content:"\\f533"}.fa-highlighter:before{content:"\\f591"}.fa-hiking:before{content:"\\f6ec"}.fa-hippo:before{content:"\\f6ed"}.fa-hips:before{content:"\\f452"}.fa-hire-a-helper:before{content:"\\f3b0"}.fa-history:before{content:"\\f1da"}.fa-hive:before{content:"\\e07f"}.fa-hockey-puck:before{content:"\\f453"}.fa-holly-berry:before{content:"\\f7aa"}.fa-home:before{content:"\\f015"}.fa-hooli:before{content:"\\f427"}.fa-hornbill:before{content:"\\f592"}.fa-horse:before{content:"\\f6f0"}.fa-horse-head:before{content:"\\f7ab"}.fa-hospital:before{content:"\\f0f8"}.fa-hospital-alt:before{content:"\\f47d"}.fa-hospital-symbol:before{content:"\\f47e"}.fa-hospital-user:before{content:"\\f80d"}.fa-hot-tub:before{content:"\\f593"}.fa-hotdog:before{content:"\\f80f"}.fa-hotel:before{content:"\\f594"}.fa-hotjar:before{content:"\\f3b1"}.fa-hourglass:before{content:"\\f254"}.fa-hourglass-end:before{content:"\\f253"}.fa-hourglass-half:before{content:"\\f252"}.fa-hourglass-start:before{content:"\\f251"}.fa-house-damage:before{content:"\\f6f1"}.fa-house-user:before{content:"\\e065"}.fa-houzz:before{content:"\\f27c"}.fa-hryvnia:before{content:"\\f6f2"}.fa-html5:before{content:"\\f13b"}.fa-hubspot:before{content:"\\f3b2"}.fa-i-cursor:before{content:"\\f246"}.fa-ice-cream:before{content:"\\f810"}.fa-icicles:before{content:"\\f7ad"}.fa-icons:before{content:"\\f86d"}.fa-id-badge:before{content:"\\f2c1"}.fa-id-card:before{content:"\\f2c2"}.fa-id-card-alt:before{content:"\\f47f"}.fa-ideal:before{content:"\\e013"}.fa-igloo:before{content:"\\f7ae"}.fa-image:before{content:"\\f03e"}.fa-images:before{content:"\\f302"}.fa-imdb:before{content:"\\f2d8"}.fa-inbox:before{content:"\\f01c"}.fa-indent:before{content:"\\f03c"}.fa-industry:before{content:"\\f275"}.fa-infinity:before{content:"\\f534"}.fa-info:before{content:"\\f129"}.fa-info-circle:before{content:"\\f05a"}.fa-innosoft:before{content:"\\e080"}.fa-instagram:before{content:"\\f16d"}.fa-instagram-square:before{content:"\\e055"}.fa-instalod:before{content:"\\e081"}.fa-intercom:before{content:"\\f7af"}.fa-internet-explorer:before{content:"\\f26b"}.fa-invision:before{content:"\\f7b0"}.fa-ioxhost:before{content:"\\f208"}.fa-italic:before{content:"\\f033"}.fa-itch-io:before{content:"\\f83a"}.fa-itunes:before{content:"\\f3b4"}.fa-itunes-note:before{content:"\\f3b5"}.fa-java:before{content:"\\f4e4"}.fa-jedi:before{content:"\\f669"}.fa-jedi-order:before{content:"\\f50e"}.fa-jenkins:before{content:"\\f3b6"}.fa-jira:before{content:"\\f7b1"}.fa-joget:before{content:"\\f3b7"}.fa-joint:before{content:"\\f595"}.fa-joomla:before{content:"\\f1aa"}.fa-journal-whills:before{content:"\\f66a"}.fa-js:before{content:"\\f3b8"}.fa-js-square:before{content:"\\f3b9"}.fa-jsfiddle:before{content:"\\f1cc"}.fa-kaaba:before{content:"\\f66b"}.fa-kaggle:before{content:"\\f5fa"}.fa-key:before{content:"\\f084"}.fa-keybase:before{content:"\\f4f5"}.fa-keyboard:before{content:"\\f11c"}.fa-keycdn:before{content:"\\f3ba"}.fa-khanda:before{content:"\\f66d"}.fa-kickstarter:before{content:"\\f3bb"}.fa-kickstarter-k:before{content:"\\f3bc"}.fa-kiss:before{content:"\\f596"}.fa-kiss-beam:before{content:"\\f597"}.fa-kiss-wink-heart:before{content:"\\f598"}.fa-kiwi-bird:before{content:"\\f535"}.fa-korvue:before{content:"\\f42f"}.fa-landmark:before{content:"\\f66f"}.fa-language:before{content:"\\f1ab"}.fa-laptop:before{content:"\\f109"}.fa-laptop-code:before{content:"\\f5fc"}.fa-laptop-house:before{content:"\\e066"}.fa-laptop-medical:before{content:"\\f812"}.fa-laravel:before{content:"\\f3bd"}.fa-lastfm:before{content:"\\f202"}.fa-lastfm-square:before{content:"\\f203"}.fa-laugh:before{content:"\\f599"}.fa-laugh-beam:before{content:"\\f59a"}.fa-laugh-squint:before{content:"\\f59b"}.fa-laugh-wink:before{content:"\\f59c"}.fa-layer-group:before{content:"\\f5fd"}.fa-leaf:before{content:"\\f06c"}.fa-leanpub:before{content:"\\f212"}.fa-lemon:before{content:"\\f094"}.fa-less:before{content:"\\f41d"}.fa-less-than:before{content:"\\f536"}.fa-less-than-equal:before{content:"\\f537"}.fa-level-down-alt:before{content:"\\f3be"}.fa-level-up-alt:before{content:"\\f3bf"}.fa-life-ring:before{content:"\\f1cd"}.fa-lightbulb:before{content:"\\f0eb"}.fa-line:before{content:"\\f3c0"}.fa-link:before{content:"\\f0c1"}.fa-linkedin:before{content:"\\f08c"}.fa-linkedin-in:before{content:"\\f0e1"}.fa-linode:before{content:"\\f2b8"}.fa-linux:before{content:"\\f17c"}.fa-lira-sign:before{content:"\\f195"}.fa-list:before{content:"\\f03a"}.fa-list-alt:before{content:"\\f022"}.fa-list-ol:before{content:"\\f0cb"}.fa-list-ul:before{content:"\\f0ca"}.fa-location-arrow:before{content:"\\f124"}.fa-lock:before{content:"\\f023"}.fa-lock-open:before{content:"\\f3c1"}.fa-long-arrow-alt-down:before{content:"\\f309"}.fa-long-arrow-alt-left:before{content:"\\f30a"}.fa-long-arrow-alt-right:before{content:"\\f30b"}.fa-long-arrow-alt-up:before{content:"\\f30c"}.fa-low-vision:before{content:"\\f2a8"}.fa-luggage-cart:before{content:"\\f59d"}.fa-lungs:before{content:"\\f604"}.fa-lungs-virus:before{content:"\\e067"}.fa-lyft:before{content:"\\f3c3"}.fa-magento:before{content:"\\f3c4"}.fa-magic:before{content:"\\f0d0"}.fa-magnet:before{content:"\\f076"}.fa-mail-bulk:before{content:"\\f674"}.fa-mailchimp:before{content:"\\f59e"}.fa-male:before{content:"\\f183"}.fa-mandalorian:before{content:"\\f50f"}.fa-map:before{content:"\\f279"}.fa-map-marked:before{content:"\\f59f"}.fa-map-marked-alt:before{content:"\\f5a0"}.fa-map-marker:before{content:"\\f041"}.fa-map-marker-alt:before{content:"\\f3c5"}.fa-map-pin:before{content:"\\f276"}.fa-map-signs:before{content:"\\f277"}.fa-markdown:before{content:"\\f60f"}.fa-marker:before{content:"\\f5a1"}.fa-mars:before{content:"\\f222"}.fa-mars-double:before{content:"\\f227"}.fa-mars-stroke:before{content:"\\f229"}.fa-mars-stroke-h:before{content:"\\f22b"}.fa-mars-stroke-v:before{content:"\\f22a"}.fa-mask:before{content:"\\f6fa"}.fa-mastodon:before{content:"\\f4f6"}.fa-maxcdn:before{content:"\\f136"}.fa-mdb:before{content:"\\f8ca"}.fa-medal:before{content:"\\f5a2"}.fa-medapps:before{content:"\\f3c6"}.fa-medium:before{content:"\\f23a"}.fa-medium-m:before{content:"\\f3c7"}.fa-medkit:before{content:"\\f0fa"}.fa-medrt:before{content:"\\f3c8"}.fa-meetup:before{content:"\\f2e0"}.fa-megaport:before{content:"\\f5a3"}.fa-meh:before{content:"\\f11a"}.fa-meh-blank:before{content:"\\f5a4"}.fa-meh-rolling-eyes:before{content:"\\f5a5"}.fa-memory:before{content:"\\f538"}.fa-mendeley:before{content:"\\f7b3"}.fa-menorah:before{content:"\\f676"}.fa-mercury:before{content:"\\f223"}.fa-meteor:before{content:"\\f753"}.fa-microblog:before{content:"\\e01a"}.fa-microchip:before{content:"\\f2db"}.fa-microphone:before{content:"\\f130"}.fa-microphone-alt:before{content:"\\f3c9"}.fa-microphone-alt-slash:before{content:"\\f539"}.fa-microphone-slash:before{content:"\\f131"}.fa-microscope:before{content:"\\f610"}.fa-microsoft:before{content:"\\f3ca"}.fa-minus:before{content:"\\f068"}.fa-minus-circle:before{content:"\\f056"}.fa-minus-square:before{content:"\\f146"}.fa-mitten:before{content:"\\f7b5"}.fa-mix:before{content:"\\f3cb"}.fa-mixcloud:before{content:"\\f289"}.fa-mixer:before{content:"\\e056"}.fa-mizuni:before{content:"\\f3cc"}.fa-mobile:before{content:"\\f10b"}.fa-mobile-alt:before{content:"\\f3cd"}.fa-modx:before{content:"\\f285"}.fa-monero:before{content:"\\f3d0"}.fa-money-bill:before{content:"\\f0d6"}.fa-money-bill-alt:before{content:"\\f3d1"}.fa-money-bill-wave:before{content:"\\f53a"}.fa-money-bill-wave-alt:before{content:"\\f53b"}.fa-money-check:before{content:"\\f53c"}.fa-money-check-alt:before{content:"\\f53d"}.fa-monument:before{content:"\\f5a6"}.fa-moon:before{content:"\\f186"}.fa-mortar-pestle:before{content:"\\f5a7"}.fa-mosque:before{content:"\\f678"}.fa-motorcycle:before{content:"\\f21c"}.fa-mountain:before{content:"\\f6fc"}.fa-mouse:before{content:"\\f8cc"}.fa-mouse-pointer:before{content:"\\f245"}.fa-mug-hot:before{content:"\\f7b6"}.fa-music:before{content:"\\f001"}.fa-napster:before{content:"\\f3d2"}.fa-neos:before{content:"\\f612"}.fa-network-wired:before{content:"\\f6ff"}.fa-neuter:before{content:"\\f22c"}.fa-newspaper:before{content:"\\f1ea"}.fa-nimblr:before{content:"\\f5a8"}.fa-node:before{content:"\\f419"}.fa-node-js:before{content:"\\f3d3"}.fa-not-equal:before{content:"\\f53e"}.fa-notes-medical:before{content:"\\f481"}.fa-npm:before{content:"\\f3d4"}.fa-ns8:before{content:"\\f3d5"}.fa-nutritionix:before{content:"\\f3d6"}.fa-object-group:before{content:"\\f247"}.fa-object-ungroup:before{content:"\\f248"}.fa-octopus-deploy:before{content:"\\e082"}.fa-odnoklassniki:before{content:"\\f263"}.fa-odnoklassniki-square:before{content:"\\f264"}.fa-oil-can:before{content:"\\f613"}.fa-old-republic:before{content:"\\f510"}.fa-om:before{content:"\\f679"}.fa-opencart:before{content:"\\f23d"}.fa-openid:before{content:"\\f19b"}.fa-opera:before{content:"\\f26a"}.fa-optin-monster:before{content:"\\f23c"}.fa-orcid:before{content:"\\f8d2"}.fa-osi:before{content:"\\f41a"}.fa-otter:before{content:"\\f700"}.fa-outdent:before{content:"\\f03b"}.fa-page4:before{content:"\\f3d7"}.fa-pagelines:before{content:"\\f18c"}.fa-pager:before{content:"\\f815"}.fa-paint-brush:before{content:"\\f1fc"}.fa-paint-roller:before{content:"\\f5aa"}.fa-palette:before{content:"\\f53f"}.fa-palfed:before{content:"\\f3d8"}.fa-pallet:before{content:"\\f482"}.fa-paper-plane:before{content:"\\f1d8"}.fa-paperclip:before{content:"\\f0c6"}.fa-parachute-box:before{content:"\\f4cd"}.fa-paragraph:before{content:"\\f1dd"}.fa-parking:before{content:"\\f540"}.fa-passport:before{content:"\\f5ab"}.fa-pastafarianism:before{content:"\\f67b"}.fa-paste:before{content:"\\f0ea"}.fa-patreon:before{content:"\\f3d9"}.fa-pause:before{content:"\\f04c"}.fa-pause-circle:before{content:"\\f28b"}.fa-paw:before{content:"\\f1b0"}.fa-paypal:before{content:"\\f1ed"}.fa-peace:before{content:"\\f67c"}.fa-pen:before{content:"\\f304"}.fa-pen-alt:before{content:"\\f305"}.fa-pen-fancy:before{content:"\\f5ac"}.fa-pen-nib:before{content:"\\f5ad"}.fa-pen-square:before{content:"\\f14b"}.fa-pencil-alt:before{content:"\\f303"}.fa-pencil-ruler:before{content:"\\f5ae"}.fa-penny-arcade:before{content:"\\f704"}.fa-people-arrows:before{content:"\\e068"}.fa-people-carry:before{content:"\\f4ce"}.fa-pepper-hot:before{content:"\\f816"}.fa-perbyte:before{content:"\\e083"}.fa-percent:before{content:"\\f295"}.fa-percentage:before{content:"\\f541"}.fa-periscope:before{content:"\\f3da"}.fa-person-booth:before{content:"\\f756"}.fa-phabricator:before{content:"\\f3db"}.fa-phoenix-framework:before{content:"\\f3dc"}.fa-phoenix-squadron:before{content:"\\f511"}.fa-phone:before{content:"\\f095"}.fa-phone-alt:before{content:"\\f879"}.fa-phone-slash:before{content:"\\f3dd"}.fa-phone-square:before{content:"\\f098"}.fa-phone-square-alt:before{content:"\\f87b"}.fa-phone-volume:before{content:"\\f2a0"}.fa-photo-video:before{content:"\\f87c"}.fa-php:before{content:"\\f457"}.fa-pied-piper:before{content:"\\f2ae"}.fa-pied-piper-alt:before{content:"\\f1a8"}.fa-pied-piper-hat:before{content:"\\f4e5"}.fa-pied-piper-pp:before{content:"\\f1a7"}.fa-pied-piper-square:before{content:"\\e01e"}.fa-piggy-bank:before{content:"\\f4d3"}.fa-pills:before{content:"\\f484"}.fa-pinterest:before{content:"\\f0d2"}.fa-pinterest-p:before{content:"\\f231"}.fa-pinterest-square:before{content:"\\f0d3"}.fa-pizza-slice:before{content:"\\f818"}.fa-place-of-worship:before{content:"\\f67f"}.fa-plane:before{content:"\\f072"}.fa-plane-arrival:before{content:"\\f5af"}.fa-plane-departure:before{content:"\\f5b0"}.fa-plane-slash:before{content:"\\e069"}.fa-play:before{content:"\\f04b"}.fa-play-circle:before{content:"\\f144"}.fa-playstation:before{content:"\\f3df"}.fa-plug:before{content:"\\f1e6"}.fa-plus:before{content:"\\f067"}.fa-plus-circle:before{content:"\\f055"}.fa-plus-square:before{content:"\\f0fe"}.fa-podcast:before{content:"\\f2ce"}.fa-poll:before{content:"\\f681"}.fa-poll-h:before{content:"\\f682"}.fa-poo:before{content:"\\f2fe"}.fa-poo-storm:before{content:"\\f75a"}.fa-poop:before{content:"\\f619"}.fa-portrait:before{content:"\\f3e0"}.fa-pound-sign:before{content:"\\f154"}.fa-power-off:before{content:"\\f011"}.fa-pray:before{content:"\\f683"}.fa-praying-hands:before{content:"\\f684"}.fa-prescription:before{content:"\\f5b1"}.fa-prescription-bottle:before{content:"\\f485"}.fa-prescription-bottle-alt:before{content:"\\f486"}.fa-print:before{content:"\\f02f"}.fa-procedures:before{content:"\\f487"}.fa-product-hunt:before{content:"\\f288"}.fa-project-diagram:before{content:"\\f542"}.fa-pump-medical:before{content:"\\e06a"}.fa-pump-soap:before{content:"\\e06b"}.fa-pushed:before{content:"\\f3e1"}.fa-puzzle-piece:before{content:"\\f12e"}.fa-python:before{content:"\\f3e2"}.fa-qq:before{content:"\\f1d6"}.fa-qrcode:before{content:"\\f029"}.fa-question:before{content:"\\f128"}.fa-question-circle:before{content:"\\f059"}.fa-quidditch:before{content:"\\f458"}.fa-quinscape:before{content:"\\f459"}.fa-quora:before{content:"\\f2c4"}.fa-quote-left:before{content:"\\f10d"}.fa-quote-right:before{content:"\\f10e"}.fa-quran:before{content:"\\f687"}.fa-r-project:before{content:"\\f4f7"}.fa-radiation:before{content:"\\f7b9"}.fa-radiation-alt:before{content:"\\f7ba"}.fa-rainbow:before{content:"\\f75b"}.fa-random:before{content:"\\f074"}.fa-raspberry-pi:before{content:"\\f7bb"}.fa-ravelry:before{content:"\\f2d9"}.fa-react:before{content:"\\f41b"}.fa-reacteurope:before{content:"\\f75d"}.fa-readme:before{content:"\\f4d5"}.fa-rebel:before{content:"\\f1d0"}.fa-receipt:before{content:"\\f543"}.fa-record-vinyl:before{content:"\\f8d9"}.fa-recycle:before{content:"\\f1b8"}.fa-red-river:before{content:"\\f3e3"}.fa-reddit:before{content:"\\f1a1"}.fa-reddit-alien:before{content:"\\f281"}.fa-reddit-square:before{content:"\\f1a2"}.fa-redhat:before{content:"\\f7bc"}.fa-redo:before{content:"\\f01e"}.fa-redo-alt:before{content:"\\f2f9"}.fa-registered:before{content:"\\f25d"}.fa-remove-format:before{content:"\\f87d"}.fa-renren:before{content:"\\f18b"}.fa-reply:before{content:"\\f3e5"}.fa-reply-all:before{content:"\\f122"}.fa-replyd:before{content:"\\f3e6"}.fa-republican:before{content:"\\f75e"}.fa-researchgate:before{content:"\\f4f8"}.fa-resolving:before{content:"\\f3e7"}.fa-restroom:before{content:"\\f7bd"}.fa-retweet:before{content:"\\f079"}.fa-rev:before{content:"\\f5b2"}.fa-ribbon:before{content:"\\f4d6"}.fa-ring:before{content:"\\f70b"}.fa-road:before{content:"\\f018"}.fa-robot:before{content:"\\f544"}.fa-rocket:before{content:"\\f135"}.fa-rocketchat:before{content:"\\f3e8"}.fa-rockrms:before{content:"\\f3e9"}.fa-route:before{content:"\\f4d7"}.fa-rss:before{content:"\\f09e"}.fa-rss-square:before{content:"\\f143"}.fa-ruble-sign:before{content:"\\f158"}.fa-ruler:before{content:"\\f545"}.fa-ruler-combined:before{content:"\\f546"}.fa-ruler-horizontal:before{content:"\\f547"}.fa-ruler-vertical:before{content:"\\f548"}.fa-running:before{content:"\\f70c"}.fa-rupee-sign:before{content:"\\f156"}.fa-rust:before{content:"\\e07a"}.fa-sad-cry:before{content:"\\f5b3"}.fa-sad-tear:before{content:"\\f5b4"}.fa-safari:before{content:"\\f267"}.fa-salesforce:before{content:"\\f83b"}.fa-sass:before{content:"\\f41e"}.fa-satellite:before{content:"\\f7bf"}.fa-satellite-dish:before{content:"\\f7c0"}.fa-save:before{content:"\\f0c7"}.fa-schlix:before{content:"\\f3ea"}.fa-school:before{content:"\\f549"}.fa-screwdriver:before{content:"\\f54a"}.fa-scribd:before{content:"\\f28a"}.fa-scroll:before{content:"\\f70e"}.fa-sd-card:before{content:"\\f7c2"}.fa-search:before{content:"\\f002"}.fa-search-dollar:before{content:"\\f688"}.fa-search-location:before{content:"\\f689"}.fa-search-minus:before{content:"\\f010"}.fa-search-plus:before{content:"\\f00e"}.fa-searchengin:before{content:"\\f3eb"}.fa-seedling:before{content:"\\f4d8"}.fa-sellcast:before{content:"\\f2da"}.fa-sellsy:before{content:"\\f213"}.fa-server:before{content:"\\f233"}.fa-servicestack:before{content:"\\f3ec"}.fa-shapes:before{content:"\\f61f"}.fa-share:before{content:"\\f064"}.fa-share-alt:before{content:"\\f1e0"}.fa-share-alt-square:before{content:"\\f1e1"}.fa-share-square:before{content:"\\f14d"}.fa-shekel-sign:before{content:"\\f20b"}.fa-shield-alt:before{content:"\\f3ed"}.fa-shield-virus:before{content:"\\e06c"}.fa-ship:before{content:"\\f21a"}.fa-shipping-fast:before{content:"\\f48b"}.fa-shirtsinbulk:before{content:"\\f214"}.fa-shoe-prints:before{content:"\\f54b"}.fa-shopify:before{content:"\\e057"}.fa-shopping-bag:before{content:"\\f290"}.fa-shopping-basket:before{content:"\\f291"}.fa-shopping-cart:before{content:"\\f07a"}.fa-shopware:before{content:"\\f5b5"}.fa-shower:before{content:"\\f2cc"}.fa-shuttle-van:before{content:"\\f5b6"}.fa-sign:before{content:"\\f4d9"}.fa-sign-in-alt:before{content:"\\f2f6"}.fa-sign-language:before{content:"\\f2a7"}.fa-sign-out-alt:before{content:"\\f2f5"}.fa-signal:before{content:"\\f012"}.fa-signature:before{content:"\\f5b7"}.fa-sim-card:before{content:"\\f7c4"}.fa-simplybuilt:before{content:"\\f215"}.fa-sink:before{content:"\\e06d"}.fa-sistrix:before{content:"\\f3ee"}.fa-sitemap:before{content:"\\f0e8"}.fa-sith:before{content:"\\f512"}.fa-skating:before{content:"\\f7c5"}.fa-sketch:before{content:"\\f7c6"}.fa-skiing:before{content:"\\f7c9"}.fa-skiing-nordic:before{content:"\\f7ca"}.fa-skull:before{content:"\\f54c"}.fa-skull-crossbones:before{content:"\\f714"}.fa-skyatlas:before{content:"\\f216"}.fa-skype:before{content:"\\f17e"}.fa-slack:before{content:"\\f198"}.fa-slack-hash:before{content:"\\f3ef"}.fa-slash:before{content:"\\f715"}.fa-sleigh:before{content:"\\f7cc"}.fa-sliders-h:before{content:"\\f1de"}.fa-slideshare:before{content:"\\f1e7"}.fa-smile:before{content:"\\f118"}.fa-smile-beam:before{content:"\\f5b8"}.fa-smile-wink:before{content:"\\f4da"}.fa-smog:before{content:"\\f75f"}.fa-smoking:before{content:"\\f48d"}.fa-smoking-ban:before{content:"\\f54d"}.fa-sms:before{content:"\\f7cd"}.fa-snapchat:before{content:"\\f2ab"}.fa-snapchat-ghost:before{content:"\\f2ac"}.fa-snapchat-square:before{content:"\\f2ad"}.fa-snowboarding:before{content:"\\f7ce"}.fa-snowflake:before{content:"\\f2dc"}.fa-snowman:before{content:"\\f7d0"}.fa-snowplow:before{content:"\\f7d2"}.fa-soap:before{content:"\\e06e"}.fa-socks:before{content:"\\f696"}.fa-solar-panel:before{content:"\\f5ba"}.fa-sort:before{content:"\\f0dc"}.fa-sort-alpha-down:before{content:"\\f15d"}.fa-sort-alpha-down-alt:before{content:"\\f881"}.fa-sort-alpha-up:before{content:"\\f15e"}.fa-sort-alpha-up-alt:before{content:"\\f882"}.fa-sort-amount-down:before{content:"\\f160"}.fa-sort-amount-down-alt:before{content:"\\f884"}.fa-sort-amount-up:before{content:"\\f161"}.fa-sort-amount-up-alt:before{content:"\\f885"}.fa-sort-down:before{content:"\\f0dd"}.fa-sort-numeric-down:before{content:"\\f162"}.fa-sort-numeric-down-alt:before{content:"\\f886"}.fa-sort-numeric-up:before{content:"\\f163"}.fa-sort-numeric-up-alt:before{content:"\\f887"}.fa-sort-up:before{content:"\\f0de"}.fa-soundcloud:before{content:"\\f1be"}.fa-sourcetree:before{content:"\\f7d3"}.fa-spa:before{content:"\\f5bb"}.fa-space-shuttle:before{content:"\\f197"}.fa-speakap:before{content:"\\f3f3"}.fa-speaker-deck:before{content:"\\f83c"}.fa-spell-check:before{content:"\\f891"}.fa-spider:before{content:"\\f717"}.fa-spinner:before{content:"\\f110"}.fa-splotch:before{content:"\\f5bc"}.fa-spotify:before{content:"\\f1bc"}.fa-spray-can:before{content:"\\f5bd"}.fa-square:before{content:"\\f0c8"}.fa-square-full:before{content:"\\f45c"}.fa-square-root-alt:before{content:"\\f698"}.fa-squarespace:before{content:"\\f5be"}.fa-stack-exchange:before{content:"\\f18d"}.fa-stack-overflow:before{content:"\\f16c"}.fa-stackpath:before{content:"\\f842"}.fa-stamp:before{content:"\\f5bf"}.fa-star:before{content:"\\f005"}.fa-star-and-crescent:before{content:"\\f699"}.fa-star-half:before{content:"\\f089"}.fa-star-half-alt:before{content:"\\f5c0"}.fa-star-of-david:before{content:"\\f69a"}.fa-star-of-life:before{content:"\\f621"}.fa-staylinked:before{content:"\\f3f5"}.fa-steam:before{content:"\\f1b6"}.fa-steam-square:before{content:"\\f1b7"}.fa-steam-symbol:before{content:"\\f3f6"}.fa-step-backward:before{content:"\\f048"}.fa-step-forward:before{content:"\\f051"}.fa-stethoscope:before{content:"\\f0f1"}.fa-sticker-mule:before{content:"\\f3f7"}.fa-sticky-note:before{content:"\\f249"}.fa-stop:before{content:"\\f04d"}.fa-stop-circle:before{content:"\\f28d"}.fa-stopwatch:before{content:"\\f2f2"}.fa-stopwatch-20:before{content:"\\e06f"}.fa-store:before{content:"\\f54e"}.fa-store-alt:before{content:"\\f54f"}.fa-store-alt-slash:before{content:"\\e070"}.fa-store-slash:before{content:"\\e071"}.fa-strava:before{content:"\\f428"}.fa-stream:before{content:"\\f550"}.fa-street-view:before{content:"\\f21d"}.fa-strikethrough:before{content:"\\f0cc"}.fa-stripe:before{content:"\\f429"}.fa-stripe-s:before{content:"\\f42a"}.fa-stroopwafel:before{content:"\\f551"}.fa-studiovinari:before{content:"\\f3f8"}.fa-stumbleupon:before{content:"\\f1a4"}.fa-stumbleupon-circle:before{content:"\\f1a3"}.fa-subscript:before{content:"\\f12c"}.fa-subway:before{content:"\\f239"}.fa-suitcase:before{content:"\\f0f2"}.fa-suitcase-rolling:before{content:"\\f5c1"}.fa-sun:before{content:"\\f185"}.fa-superpowers:before{content:"\\f2dd"}.fa-superscript:before{content:"\\f12b"}.fa-supple:before{content:"\\f3f9"}.fa-surprise:before{content:"\\f5c2"}.fa-suse:before{content:"\\f7d6"}.fa-swatchbook:before{content:"\\f5c3"}.fa-swift:before{content:"\\f8e1"}.fa-swimmer:before{content:"\\f5c4"}.fa-swimming-pool:before{content:"\\f5c5"}.fa-symfony:before{content:"\\f83d"}.fa-synagogue:before{content:"\\f69b"}.fa-sync:before{content:"\\f021"}.fa-sync-alt:before{content:"\\f2f1"}.fa-syringe:before{content:"\\f48e"}.fa-table:before{content:"\\f0ce"}.fa-table-tennis:before{content:"\\f45d"}.fa-tablet:before{content:"\\f10a"}.fa-tablet-alt:before{content:"\\f3fa"}.fa-tablets:before{content:"\\f490"}.fa-tachometer-alt:before{content:"\\f3fd"}.fa-tag:before{content:"\\f02b"}.fa-tags:before{content:"\\f02c"}.fa-tape:before{content:"\\f4db"}.fa-tasks:before{content:"\\f0ae"}.fa-taxi:before{content:"\\f1ba"}.fa-teamspeak:before{content:"\\f4f9"}.fa-teeth:before{content:"\\f62e"}.fa-teeth-open:before{content:"\\f62f"}.fa-telegram:before{content:"\\f2c6"}.fa-telegram-plane:before{content:"\\f3fe"}.fa-temperature-high:before{content:"\\f769"}.fa-temperature-low:before{content:"\\f76b"}.fa-tencent-weibo:before{content:"\\f1d5"}.fa-tenge:before{content:"\\f7d7"}.fa-terminal:before{content:"\\f120"}.fa-text-height:before{content:"\\f034"}.fa-text-width:before{content:"\\f035"}.fa-th:before{content:"\\f00a"}.fa-th-large:before{content:"\\f009"}.fa-th-list:before{content:"\\f00b"}.fa-the-red-yeti:before{content:"\\f69d"}.fa-theater-masks:before{content:"\\f630"}.fa-themeco:before{content:"\\f5c6"}.fa-themeisle:before{content:"\\f2b2"}.fa-thermometer:before{content:"\\f491"}.fa-thermometer-empty:before{content:"\\f2cb"}.fa-thermometer-full:before{content:"\\f2c7"}.fa-thermometer-half:before{content:"\\f2c9"}.fa-thermometer-quarter:before{content:"\\f2ca"}.fa-thermometer-three-quarters:before{content:"\\f2c8"}.fa-think-peaks:before{content:"\\f731"}.fa-thumbs-down:before{content:"\\f165"}.fa-thumbs-up:before{content:"\\f164"}.fa-thumbtack:before{content:"\\f08d"}.fa-ticket-alt:before{content:"\\f3ff"}.fa-tiktok:before{content:"\\e07b"}.fa-times:before{content:"\\f00d"}.fa-times-circle:before{content:"\\f057"}.fa-tint:before{content:"\\f043"}.fa-tint-slash:before{content:"\\f5c7"}.fa-tired:before{content:"\\f5c8"}.fa-toggle-off:before{content:"\\f204"}.fa-toggle-on:before{content:"\\f205"}.fa-toilet:before{content:"\\f7d8"}.fa-toilet-paper:before{content:"\\f71e"}.fa-toilet-paper-slash:before{content:"\\e072"}.fa-toolbox:before{content:"\\f552"}.fa-tools:before{content:"\\f7d9"}.fa-tooth:before{content:"\\f5c9"}.fa-torah:before{content:"\\f6a0"}.fa-torii-gate:before{content:"\\f6a1"}.fa-tractor:before{content:"\\f722"}.fa-trade-federation:before{content:"\\f513"}.fa-trademark:before{content:"\\f25c"}.fa-traffic-light:before{content:"\\f637"}.fa-trailer:before{content:"\\e041"}.fa-train:before{content:"\\f238"}.fa-tram:before{content:"\\f7da"}.fa-transgender:before{content:"\\f224"}.fa-transgender-alt:before{content:"\\f225"}.fa-trash:before{content:"\\f1f8"}.fa-trash-alt:before{content:"\\f2ed"}.fa-trash-restore:before{content:"\\f829"}.fa-trash-restore-alt:before{content:"\\f82a"}.fa-tree:before{content:"\\f1bb"}.fa-trello:before{content:"\\f181"}.fa-tripadvisor:before{content:"\\f262"}.fa-trophy:before{content:"\\f091"}.fa-truck:before{content:"\\f0d1"}.fa-truck-loading:before{content:"\\f4de"}.fa-truck-monster:before{content:"\\f63b"}.fa-truck-moving:before{content:"\\f4df"}.fa-truck-pickup:before{content:"\\f63c"}.fa-tshirt:before{content:"\\f553"}.fa-tty:before{content:"\\f1e4"}.fa-tumblr:before{content:"\\f173"}.fa-tumblr-square:before{content:"\\f174"}.fa-tv:before{content:"\\f26c"}.fa-twitch:before{content:"\\f1e8"}.fa-twitter:before{content:"\\f099"}.fa-twitter-square:before{content:"\\f081"}.fa-typo3:before{content:"\\f42b"}.fa-uber:before{content:"\\f402"}.fa-ubuntu:before{content:"\\f7df"}.fa-uikit:before{content:"\\f403"}.fa-umbraco:before{content:"\\f8e8"}.fa-umbrella:before{content:"\\f0e9"}.fa-umbrella-beach:before{content:"\\f5ca"}.fa-uncharted:before{content:"\\e084"}.fa-underline:before{content:"\\f0cd"}.fa-undo:before{content:"\\f0e2"}.fa-undo-alt:before{content:"\\f2ea"}.fa-uniregistry:before{content:"\\f404"}.fa-unity:before{content:"\\e049"}.fa-universal-access:before{content:"\\f29a"}.fa-university:before{content:"\\f19c"}.fa-unlink:before{content:"\\f127"}.fa-unlock:before{content:"\\f09c"}.fa-unlock-alt:before{content:"\\f13e"}.fa-unsplash:before{content:"\\e07c"}.fa-untappd:before{content:"\\f405"}.fa-upload:before{content:"\\f093"}.fa-ups:before{content:"\\f7e0"}.fa-usb:before{content:"\\f287"}.fa-user:before{content:"\\f007"}.fa-user-alt:before{content:"\\f406"}.fa-user-alt-slash:before{content:"\\f4fa"}.fa-user-astronaut:before{content:"\\f4fb"}.fa-user-check:before{content:"\\f4fc"}.fa-user-circle:before{content:"\\f2bd"}.fa-user-clock:before{content:"\\f4fd"}.fa-user-cog:before{content:"\\f4fe"}.fa-user-edit:before{content:"\\f4ff"}.fa-user-friends:before{content:"\\f500"}.fa-user-graduate:before{content:"\\f501"}.fa-user-injured:before{content:"\\f728"}.fa-user-lock:before{content:"\\f502"}.fa-user-md:before{content:"\\f0f0"}.fa-user-minus:before{content:"\\f503"}.fa-user-ninja:before{content:"\\f504"}.fa-user-nurse:before{content:"\\f82f"}.fa-user-plus:before{content:"\\f234"}.fa-user-secret:before{content:"\\f21b"}.fa-user-shield:before{content:"\\f505"}.fa-user-slash:before{content:"\\f506"}.fa-user-tag:before{content:"\\f507"}.fa-user-tie:before{content:"\\f508"}.fa-user-times:before{content:"\\f235"}.fa-users:before{content:"\\f0c0"}.fa-users-cog:before{content:"\\f509"}.fa-users-slash:before{content:"\\e073"}.fa-usps:before{content:"\\f7e1"}.fa-ussunnah:before{content:"\\f407"}.fa-utensil-spoon:before{content:"\\f2e5"}.fa-utensils:before{content:"\\f2e7"}.fa-vaadin:before{content:"\\f408"}.fa-vector-square:before{content:"\\f5cb"}.fa-venus:before{content:"\\f221"}.fa-venus-double:before{content:"\\f226"}.fa-venus-mars:before{content:"\\f228"}.fa-vest:before{content:"\\e085"}.fa-vest-patches:before{content:"\\e086"}.fa-viacoin:before{content:"\\f237"}.fa-viadeo:before{content:"\\f2a9"}.fa-viadeo-square:before{content:"\\f2aa"}.fa-vial:before{content:"\\f492"}.fa-vials:before{content:"\\f493"}.fa-viber:before{content:"\\f409"}.fa-video:before{content:"\\f03d"}.fa-video-slash:before{content:"\\f4e2"}.fa-vihara:before{content:"\\f6a7"}.fa-vimeo:before{content:"\\f40a"}.fa-vimeo-square:before{content:"\\f194"}.fa-vimeo-v:before{content:"\\f27d"}.fa-vine:before{content:"\\f1ca"}.fa-virus:before{content:"\\e074"}.fa-virus-slash:before{content:"\\e075"}.fa-viruses:before{content:"\\e076"}.fa-vk:before{content:"\\f189"}.fa-vnv:before{content:"\\f40b"}.fa-voicemail:before{content:"\\f897"}.fa-volleyball-ball:before{content:"\\f45f"}.fa-volume-down:before{content:"\\f027"}.fa-volume-mute:before{content:"\\f6a9"}.fa-volume-off:before{content:"\\f026"}.fa-volume-up:before{content:"\\f028"}.fa-vote-yea:before{content:"\\f772"}.fa-vr-cardboard:before{content:"\\f729"}.fa-vuejs:before{content:"\\f41f"}.fa-walking:before{content:"\\f554"}.fa-wallet:before{content:"\\f555"}.fa-warehouse:before{content:"\\f494"}.fa-watchman-monitoring:before{content:"\\e087"}.fa-water:before{content:"\\f773"}.fa-wave-square:before{content:"\\f83e"}.fa-waze:before{content:"\\f83f"}.fa-weebly:before{content:"\\f5cc"}.fa-weibo:before{content:"\\f18a"}.fa-weight:before{content:"\\f496"}.fa-weight-hanging:before{content:"\\f5cd"}.fa-weixin:before{content:"\\f1d7"}.fa-whatsapp:before{content:"\\f232"}.fa-whatsapp-square:before{content:"\\f40c"}.fa-wheelchair:before{content:"\\f193"}.fa-whmcs:before{content:"\\f40d"}.fa-wifi:before{content:"\\f1eb"}.fa-wikipedia-w:before{content:"\\f266"}.fa-wind:before{content:"\\f72e"}.fa-window-close:before{content:"\\f410"}.fa-window-maximize:before{content:"\\f2d0"}.fa-window-minimize:before{content:"\\f2d1"}.fa-window-restore:before{content:"\\f2d2"}.fa-windows:before{content:"\\f17a"}.fa-wine-bottle:before{content:"\\f72f"}.fa-wine-glass:before{content:"\\f4e3"}.fa-wine-glass-alt:before{content:"\\f5ce"}.fa-wix:before{content:"\\f5cf"}.fa-wizards-of-the-coast:before{content:"\\f730"}.fa-wodu:before{content:"\\e088"}.fa-wolf-pack-battalion:before{content:"\\f514"}.fa-won-sign:before{content:"\\f159"}.fa-wordpress:before{content:"\\f19a"}.fa-wordpress-simple:before{content:"\\f411"}.fa-wpbeginner:before{content:"\\f297"}.fa-wpexplorer:before{content:"\\f2de"}.fa-wpforms:before{content:"\\f298"}.fa-wpressr:before{content:"\\f3e4"}.fa-wrench:before{content:"\\f0ad"}.fa-x-ray:before{content:"\\f497"}.fa-xbox:before{content:"\\f412"}.fa-xing:before{content:"\\f168"}.fa-xing-square:before{content:"\\f169"}.fa-y-combinator:before{content:"\\f23b"}.fa-yahoo:before{content:"\\f19e"}.fa-yammer:before{content:"\\f840"}.fa-yandex:before{content:"\\f413"}.fa-yandex-international:before{content:"\\f414"}.fa-yarn:before{content:"\\f7e3"}.fa-yelp:before{content:"\\f1e9"}.fa-yen-sign:before{content:"\\f157"}.fa-yin-yang:before{content:"\\f6ad"}.fa-yoast:before{content:"\\f2b1"}.fa-youtube:before{content:"\\f167"}.fa-youtube-square:before{content:"\\f431"}.fa-zhihu:before{content:"\\f63f"}', 'yes');
