


<p>[00:06:54] <strong>Matt Cromwell:</strong> I think you are much more fair than I.</p>



<p>[00:06:56] <strong>Nathan Wrigley:</strong> Okay, that&#8217;s very kind of you. The long and the short of Alex&#8217;s piece is that he believes that by the year 2022, we&#8217;ve got to a point where, if you are going to be releasing a plugin, a free plugin, into the WordPress space, he believes that it&#8217;s now no longer effective to do that on wordpress.org. The article is probably about a 10 or 15 minute read, and as always with Alex&#8217;s pieces, there&#8217;s lots and lots of data and so on to back it up. But essentially he believes it&#8217;s ineffective for a variety of reasons.</p>



<p>One of them is that the marketplace seems to be dominated, in his view, by some giant incumbents. We&#8217;ve all seen those plugins before. If you&#8217;ve tried to add a new plugin through the WordPress repository, you&#8217;ll probably know the plugins that we&#8217;re talking about. They always rise to the top. And that&#8217;s largely because, Alex thinks, because of the install base that they&#8217;ve already got. Once they&#8217;ve got over a certain amount, the hump of a 100,000, 500,000 or 1,000,000 installs, then it becomes more likely that they&#8217;re going to be surfaced.</p>



<p>There&#8217;s also the idea that, in the recent past, especially since 2016, he makes the point, it&#8217;s much more difficult for new plugins to breach that number. So getting past a hundred thousand and so on is more difficult, which is compounding the problem.</p>



<p>And then if you add on to that, the fact that the search functionality within the WordPress repository also doesn&#8217;t give the opportunity for new plugins to be discovered. If you go there and you search for particular keywords, his contention would be that it&#8217;s much more likely that the ones with the greater install base are going to be surfaced first. In other words, it&#8217;s a bit of a, an echo chamber, I suppose, in a sense is what he&#8217;s saying.</p>



<p>Given all of that, he contends that you would be better off spending your time, and I guess for time you could read money as well, elsewhere. It might be better to have social campaigns or Google ads or some other channel of distribution, outside of wordpress.org, and so your endeavors would be better served elsewhere.</p>



<p>Alex I hope that I&#8217;ve summed that up correctly. If I&#8217;ve not, pleased do get in touch and let me know where I&#8217;ve mistaken things and I will gladly amend the show notes as such. But that, broadly speaking, is Alex&#8217;s contention. And, a day or so later compelled you to write a rebuttal. Just tell us what your thoughts are.</p>



<p>[00:09:26] <strong>Matt Cromwell:</strong> Yeah. Generally speaking I gave some good caveats in my piece that Alex does know what he&#8217;s talking about, and he has a lot of data to back up his conclusions, and I still believe that strongly um, he has reasons for saying what he says. What compelled me to write a rebuttal were essentially a couple claims that I felt were potentially not as helpful for the WordPress ecosystem.</p>



<p>In particular, one thing I think that&#8217;s important of what he&#8217;s saying is that, he says essentially that if you&#8217;re serious about your business and you want to build plugins then you should do premium only, and not a freemium model. Like basically do not build a free plugin, build a premium only plugin. And I really do believe that is damaging to the WordPress ecosystem overall.</p>



<p>If we start to see an influx of premium only offerings it can be really harder for the common user because, we all know it doesn&#8217;t take one plugin to build your website. It often takes a dozen, or several dozen plugins to build your website. And if you have to go, and be purchasing them across the web all over the place, it suddenly makes WordPress not as optimal to deal with.</p>



<p>So that&#8217;s one of the big downsides of his argument that makes me say, ah, I think this needs a lot more context and I think it needs somebody to say, no, the freemium model still works. And then I spend the rest of the article really talking about how I do see that the freemium model does still work and specifically that .org, while the active install count is significant, it&#8217;s not the only factor, and it is still possible for newer plugins to get adoption on wordpress.org. It just takes some savvy for sure. It&#8217;s not as easy as it used to be. I&#8217;ll give him that for sure. It&#8217;s not a situation anymore where if you build it, they will come. So yeah, the long and the short of it.</p>



<p>[00:11:18] <strong>Nathan Wrigley:</strong> So, one of your contentions is that it&#8217;s damaging to the WordPress ecosystem, if in effect there was only paid for plugins and everything that you wished to have on your website was a paid for plugin. I&#8217;m guessing that over the years you&#8217;ve built websites in which you have utilized free plugins? And some of them may be broad in scope, but some of them may just achieve a couple of smaller things.</p>



<p>And, there&#8217;s something to be said about that, isn&#8217;t there? I guess there is something about the community and about the ecosystem, about the expectations of what you are getting into when you install WordPress, which has this free model to it. I guess that&#8217;s an important component of the community and it would in a sense be a shame if the only things that you could have were paid for.</p>



<p>I remember the day, probably going back about 15 or so years ago, when I was looking around for different models for CMSs that I was going to begin using, and there were a variety of them. And there was Drupal and there was Joomla. But if memory serves, there was one called Expression Engine. I could have got the name wrong there. And it seemed to have a very low install base.</p>



<p>And my perception of that was that was because it took that model, it had the model of, you had to pay for not only the CMS but I think all of the different component parts that you could bolt onto the top of it, AKA plugins, and perhaps that was something that stifled its growth. And if we look back at WordPress, perhaps the free plugin model is one of the big factors of its success?</p>



<p>[00:12:47] <strong>Matt Cromwell:</strong> For sure. Absolutely. I mean, for us with GiveWP and I think many people could think, whenever I say GiveWP, you can also think similarly of WooCommerce, quite honestly. It&#8217;s really important to us that GiveWP is free, because a lot of non, all non-profits basically start from zero in many ways. And they are always very conscious about their expenses. And they&#8217;re in the fundraising space. There are so many dozens and dozens of paid fundraising platforms and they are oftentimes very expensive. So having a free option for folks to be able to start fundraising with, and do it successfully and effectively is really important.</p>



<p>And I say similar to WooCommerce because it is similar, like a lot of small businesses start from zero, and they can&#8217;t afford to be paying for a whole bunch of different plugins, just in order to sell their stuff online. I do worry a little bit on the WooCommerce side that their plugin ecosystem has gotten so large that sometimes it feels like it&#8217;s harder to start a shop with just WooCommerce free. And I wish they might put a little bit more features into the free plugin. But that&#8217;s a whole nother podcast.</p>



<p>[00:13:59] <strong>Nathan Wrigley:</strong> Okay. Let&#8217;s take a couple of different pieces of the wordpress.org repo. One of the first things that Alex talks about is the opportunity is quite low according to his data for converting people over. So let&#8217;s say in the case of GiveWP, he doesn&#8217;t cite GiveWP, let&#8217;s be clear. He talks about other different plugins and you can verify that by looking at the article. His contention is that really the conversion rate from the free plugin, if people install your free plugin, it&#8217;s somewhere between one and 3% of those people will be interested enough to go and explore and look for your, your website or whatever channel it is that you&#8217;ve got for getting the paid version.</p>



<p>So, between one and 3% of your users, and therefore that&#8217;s seems like a fairly small figure. And so the cost in terms of the support that you&#8217;d have to give on .org, and also the fact that you&#8217;re having to update it and maintain two different versions with different features. If it&#8217;s only one or two or 3% that are converting, that does seem to be relatively small, but your experience is clearly different.</p>



<p>[00:15:04] <strong>Matt Cromwell:</strong> Yeah, for sure. Now Alex definitely when he was trying to say which plugins have the benefit of being preferred on the plugin directory search. I do think that he would put Give in the category of kind of an elite plugin. Because he did say plugins with a hundred thousand installs or more that have been there for a long time have this elite status, and it&#8217;s hard to compete with them. And we do have over a hundred thousand installs. We&#8217;ve been there for seven years now. So I think he doesn&#8217;t put us in the same category. But nevertheless, I can say authoritatively that we are converting closer to 28% of our install count to paid customers.</p>



<p>I also gave some data on a newer plugin called Orderable that I&#8217;m also involved with on the Stellar side that just launched last summer. And honestly, it&#8217;s a low estimation honestly. If I really look at everyone who&#8217;s paid for anything with Orderable, it is closer to the 30%. But right now, in terms of active customers, it&#8217;s around 18%. So it&#8217;s converting much higher than one to 2%, or one to 3%. But even if you take that one to 3%, and you think about these large plugins like Elementor or whatnot that have 5 million active installs that&#8217;s 50,000 customers. And that&#8217;s significant regardless.</p>



<p>[00:16:21] <strong>Nathan Wrigley:</strong> Yeah, I wonder what could account for the difference there, because Alex is one, two or 3% which may very well be the case in certain given niches, or given the data that he was talking about. I wonder how we account for the big ocean really between your 28, 30%, whatever it may be, and that much smaller percentage? Perhaps it&#8217;s something to do with the nature of the plugin itself, what it&#8217;s doing, what problem it&#8217;s trying to solve, and whether it&#8217;s more desirable. I don&#8217;t really know. It&#8217;s interesting.</p>



<p>[00:16:52] <strong>Matt Cromwell:</strong> Yeah, it is interesting and I, I do want to get some data from Alex on the specific freemium plugins that he&#8217;s worked on, on that, in that way. I do believe that Vova at Freemius probably has additional data that he might share about this subject as well. I believe that on average plugins that use Freemius convert higher than that 3% as well.</p>



<p>And that one I think is another significant data point to keep in mind. But I know from, I, I know Alex and I adore him, he&#8217;s great. And if I&#8217;m thinking the most optimistically about his perspective, I think it&#8217;s more that he would really expect conversion rates to be at least 5% or higher because that&#8217;s what he can get with organic results. That&#8217;s what he can get with CPC ads most likely. He just knows marketing from a larger perspective and really is expecting a lot more. So, if I&#8217;m trying to be generous that&#8217;s what I would think.</p>



<p>[00:17:44] <strong>Nathan Wrigley:</strong> I wonder if there is something in that, maybe your company Give, in this case that we&#8217;re talking about is unusually effective. So your 27%, 28%, whatever it may be is not the normal. Which is obviously very good for the way that you&#8217;ve done marketing and way that you&#8217;ve pitched yourself into the repo.</p>



<p>I&#8217;m curious, and it may be something that you don&#8217;t know the answer to, what would have been the rate? Given the install base that you&#8217;ve got. So you mentioned that there&#8217;s over a hundred thousand and you may not wish to share the numbers, which is fine. What percentage would have been effective to you? In other words, if it had have been at one or 2%, could you have made the plugin viable or did it need to creep into the 10 and 15% kind of area?</p>



<p>[00:18:30] <strong>Matt Cromwell:</strong> Mm-hmm. Well, we did have other plugins at the time, freemium plugins. And truth be told, I was not analyzing their conversion rates very specifically at that time. We had a bunch of business reviews plugins. We had a really fun plugin called Maps Builder that had a free and a pro version. And my guess would be that the conversion rates at that time for those plugins were probably also a lot lower than the 27%.</p>



<p>But they were viable. So I would just be guessing, I don&#8217;t want to just guess, but I do feel like they would probably be in the single digits in terms of conversion numbers. And at the end of the day, yeah, we did retire those for the most part. The business reviews ones are still out there, but we&#8217;ve made a premium product to kind of replace those. And it&#8217;s because of the success of GiveWP. So even if I look at our own plugins that we&#8217;ve built, we did make choices to sunset products because they weren&#8217;t converting as well. So it&#8217;s not as if I don&#8217;t hear Alex, on his side of things because I have some of that same experience. I just don&#8217;t think the conclusion is that means that .org is not viable. I do think it&#8217;s more of a product fit type of conversation, a marketing conversation, and things like that.</p>



<p>[00:19:38] <strong>Nathan Wrigley:</strong> Just taking a bit of an aside here for a moment. Everything that goes into the .org repository is by nature, it&#8217;s free. You can download it and anybody can access it at any time. I&#8217;m curious, you may have opinions on this, you may not. If you have a commercial variant of the plugin, so you&#8217;ve got two sides of the coin. You&#8217;ve got the free .org side, and the paid for, wherever you may put that, but you&#8217;ve got a paid for version somewhere else. What is the true intent of the free version? Because I could look at it cynically and say, okay, the free version is basically a channel for trying to sweep people towards the paid version.</p>



<p>And then with a less cynical hat, I could be, it&#8217;s offering the kind of functionality that we can support for free. In other words, we&#8217;re doing an altruistic thing, for the community for free, completely for free, with no expectation. Maybe it&#8217;s one side or the other, or maybe it&#8217;s a little bit of both. You&#8217;re being altruistic. You&#8217;re giving away certain set of features and range of options with the hope that some of them will come across. But no expectation, you know, it&#8217;s fine if you want to use the free version forever. As a plugin developer who&#8217;s been in the game for a long time, I wonder which side of the fence you sit on, or perhaps you literally do sit on the fence there.</p>



<p>[00:20:54] <strong>Matt Cromwell:</strong> Yeah, I mean the way that things like this work is essentially that at a certain stage, once you start to get enough users, it&#8217;s going to incur costs, just to have users. So specifically when you&#8217;re doing a plugin, like GiveWP or like WooCommerce that is so foundational to the functionality of a website and so important to that website, it&#8217;s going to start to incur costs. And that is human costs. That&#8217;s in the form of technical support for the most part. And account services. Because the users are going to need support. They&#8217;re gonna want support. And in order to fund that support, we do have to have some sort of funding in one way or another.</p>



<p>So doing the free plugin specifically is in order to serve that niche, in order to serve that functionality with the intention then that we&#8217;re gonna need to fund this in one way or another, and we&#8217;re gonna do that with premium features essentially. But it, it&#8217;s always been our strong conviction that the free plugin needs to be very full featured. That you need to be able to do effective fundraising with it out of the box. Or else folks don&#8217;t know what they&#8217;re getting into when they go to pay for something. So essentially it&#8217;s not just a funnel, which in some ways I think that&#8217;s a little bit of the take that Alex is leaning on, is that is looking at .org as one of your marketing funnels.</p>



<p>Which it is, of course. But it also represents your best foot forward of what your product is supposed to be, and what it&#8217;s supposed to offer. And in business there&#8217;s very often this idea of try before you buy, or there&#8217;s a free trial type of thing. With plugins we can&#8217;t do try before you buy really, and you can&#8217;t do free trials really, so your best option is to provide a free product that then leads to paid products. Am I answering your question?</p>



<p>[00:22:41] <strong>Nathan Wrigley:</strong> Yeah. That&#8217;s good. I know it&#8217;s a difficult tight rope to walk that one because, there isn&#8217;t really a correct answer, is there? It clearly has to be a little bit of a marketing channel. You are offering something in the hope of sweeping up a few of them. But equally, you are offering something in the hope that they&#8217;ll enjoy it and experience it and in many cases the functionality that&#8217;s there is sufficient. But should you wish more functionality, here&#8217;s the option.</p>



<p>It&#8217;s an interesting thing as well that in the community, the whole promotional piece on the .org side is, I think, widely viewed with disdain. That is to say it doesn&#8217;t take much for a plugin author to completely derail their plugin if they abuse the UI that they&#8217;ve got for their plugin. I&#8217;m thinking here of examples in the past where companies have taken the opportunity to fill up portions of the screen with advertising for the paid version and so on.</p>



<p>So, we can see that the community really do feel quite strongly about this. From the plugin side, obviously, the author&#8217;s side, you wish to promote your own products because you want to stay in business. From the user&#8217;s side, there seems to be a groundswell of people who think that the repository version needs to be completely without any upsell features. It&#8217;s just, if it&#8217;s good enough, we&#8217;ll figure that out for ourselves and we&#8217;ll go and discover it for ourselves.</p>



<p>In terms of discovery, let&#8217;s just move back to the piece that you wrote. One of the contentions that Alex has was that being discovered inside of the repository is increasingly difficult. The big incumbents of which you&#8217;ve described GiveWP perhaps is one of them, but we know the names of all the other ones. They dominate the search because of their active install counts, and Alex maintains that that&#8217;s a very important metric. In other words, if you go into the repository and begin a search, it&#8217;s quite likely that the results will skew towards the larger active install count plugins. Therefore, it&#8217;s going to be difficult to break through the ceiling of that, no matter how unique and brilliant your plugin is, just because it&#8217;s difficult to launch something and it takes a lot of time. You have, specifically on that point, your rebuttal is interesting. What did you say there?</p>



<p>[00:24:52] <strong>Matt Cromwell:</strong> Yeah, the active install count is a factor, and the plugin directory has gotten larger. But the active install count is one factor of many of the way in which the plugin search works. And luckily when you&#8217;re working with a open source platform like WordPress, all of the code that creates that search is open source as well.</p>



<p>So folks can take a look at it and see exactly the way that the algorithm works, in complete contrast to Google, for example, where it&#8217;s a big black box and nobody really knows how it works exactly. But .org is actually pretty straightforward and relatively simple. But there are a lot of metrics that they take into account when they create that search. And honestly the title of the plugin is actually one of the more significant ones.</p>



<p>Now that being said, if you are, if in your title of your plugin you wanna say something like Wrigley page builder. Page builder is a very flooded field. Things like Elementor and Beaver Builder and others do have a lot more installs already and they&#8217;re going to show up higher if they also have page builder in their title than Wrigley will.</p>



<p>But that doesn&#8217;t mean that you aren&#8217;t found or aren&#8217;t discovered. You might not be first. You might not be second, but you still have a really good chance of being on page one. Because there&#8217;s really not that many page builders on .org currently. So there&#8217;s still a lot of room overall. That&#8217;s kind of my biggest contention, is simply that the way the search works is more complicated than just simply the active install count. It&#8217;s also these specific tags that you use. It&#8217;s also the way in which you describe the type of functionality you have. Whether or not you have good support is even a factor. Like answering all of your .org tickets and things like that. Those all factor in. How recently you&#8217;ve updated the plugin factors in. There&#8217;s a lot of factors involved.</p>



<p>[00:26:38] <strong>Nathan Wrigley:</strong> So you specifically mentioned the following things, which are thrown into the mix when you do a search. So it would be the title of the plugin, the excerpt, the description, the tags, the slug author name, contributor names, last time it was updated, compatibility with core versions, number of active installs, percentage of support tickets resolved, which is really an interesting one, and the average star rating as well.</p>



<p>So there are quite a few things in there. I guess in a sense, having that knowledge could lead you to be quite sophisticated in gaming that system, and it&#8217;s no different really than something like Google where people spend, I would imagine very large amounts of money in some cases, really manicuring their SEO, but without that insight.</p>



<p>And they may succeed one day, they may succeed another day. The point being, they still need to jump through hoops. It&#8217;s not You go over to Google and suddenly you are a winner. You would still have to spend large amounts of time and money organically to break through the surface against, say, for example, other page builders. I presume the problem would be equal over there than it would be on .org.</p>



<p>[00:27:49] <strong>Matt Cromwell:</strong> Yeah, absolutely. And in this way I think what Alex is speaking to a bit is that, in the past with the plugin directory, it really was easier. It really was a lot easier to simply launch your plugin on .org and you would get found in the WP admin relatively easily. And those days are definitely not there anymore. It&#8217;s not quite as easy as it used to be at all. But I don&#8217;t believe that it means that .org is now no longer viable as a distribution option, or even as a marketing or business option.</p>



<p>[00:28:21] <strong>Nathan Wrigley:</strong> Do you believe that the search algorithm in .org, despite the fact that it&#8217;s going through these whole slew of different things, and I&#8217;m guessing that if you read the code, you can see how the waiting would be and so on and so forth. But, do you believe that the search functionality does need a tweak?</p>



<p>Are there other metrics which you would like to see thrown in? Or, indeed just different areas of the UI which may give a small but potentially important boost to newcomers, in a way that perhaps the current search wouldn&#8217;t? And, I think Alex mentions something like rising stars as an option. The idea that plugins, which are new, potentially, they&#8217;ve gone from zero to 50 in a matter of days. That&#8217;s, on WordPress, that&#8217;s a big leap if you go from nothing to 50 or a hundred in a short period of time, that&#8217;s really quite something. And so maybe there&#8217;s parts of the UI where compliments of that nature could improve visibility.</p>



<p>[00:29:14] <strong>Matt Cromwell:</strong> Absolutely, there&#8217;s always room for improvement when it comes to search algorithms, because they are highly complex systems, and they are so significant. In some ways though, I think, just even if the search algorithm itself didn&#8217;t change, but we were able to add things like categorization, being able to navigate down the directory through categories first and then search. That might be a big advantage right away.</p>



<p>Especially if one of those categories was, new. Something that was recently launched. There&#8217;s actually a really fun free plugin, I think it&#8217;s just called New Plugins, I&#8217;ll have to look it up. I&#8217;ll send you the link. But you can install this plugin in your website, and what it does is it adds, when you go to plugins, add new, there&#8217;s tabs in there that says featured and things like that. It&#8217;ll add a new tab, and it&#8217;ll just show you the newest plugins on the directory. And I think that&#8217;s really cool and I&#8217;d love to see that on .org directly.</p>



<p>[00:30:09] <strong>Nathan Wrigley:</strong> Yeah, that&#8217;s really interesting. You also point out that the, gaming is the wrong word, but you make the point that it is still possible given the way that the search is carried out and the results that are shown, that, as an example, some of your competitors, they seem to have optimized with use of their plugin name or the other things that we mentioned, you know, excerpts and description, tags and so on. They&#8217;ve managed to vault over you in the .org search results, because they&#8217;ve optimized for words, which are well, really important to you, but you haven&#8217;t specifically optimized for those.</p>



<p>So for example, nobody could deny that your plugin GiveWP is to do with fundraising, and yet fundraise as a particular word, you are outcompeted on the marketplace there. And also crowdfunding, which again would be an important part of what it is that you do. Both of those words, you quickly discovered you were not winning, and in some cases you didn&#8217;t even appear in the search results on the first page, despite the fact that GiveWP is really, that is inside your wheelhouse without a doubt.</p>



<p>And so there is opportunity, I guess it&#8217;s more of a sort of long tail search. You&#8217;ve just got to find what those opportunities are. Unfortunately, I guess we don&#8217;t have the sort of metrics that we have with things like Google Ads and so on and so forth, where you can see what people have been searching for over, over a period of time, in a particular geography, given different demographics and so on. You just have to do the grunt work of figuring all this stuff out.</p>



<p>[00:31:35] <strong>Matt Cromwell:</strong> Yeah. One other point related to that, that I pointed out is that your presence on .org isn&#8217;t only about the .org plugin search. It&#8217;s also about Google search because those pages all get found on Google as well. And so because we do have insights from search console and Google Ads and things like that, that does influence the terms that we want to be found with as well.</p>



<p>So it&#8217;s not only about figuring out how .org prioritizes plugins, but also what is going to get found on Google as well, because it&#8217;s really hard for any WordPress plugin to beat the domain authority of wordpress.org. If you build a plugin they most likely are going to be on the first page of Google before you are.</p>



<p>[00:32:17] <strong>Nathan Wrigley:</strong> So the contention there is that the .org repo is kind of doing double duty. It&#8217;s obviously offering your plugin up, should it be found, to people trying to add a new plugin. But also Google itself is scraping the.org repo and surfacing in its own search results. So if people are looking for the same kind of thing over on Google, they may very well be pointed towards your .org page. Have I summarised that correctly?</p>



<p>[00:32:43] <strong>Matt Cromwell:</strong> Yep, absolutely. In this way .org is just a marketplace in many ways. It&#8217;s a public marketplace for folks to find free plugins.</p>



<p>[00:32:50] <strong>Nathan Wrigley:</strong> I do wonder if the algorithm which is running behind Google, obviously complex and probably, took billions of dollars over time to be put together and is very sophisticated. But it&#8217;s not quite such a blunt instrument, is it? It&#8217;s not just taking data from a series of tags and descriptions and metatags and so on. There&#8217;s a lot going on. So for example, if I search for fundraise, Google is probably clever enough to figure out hang on a minute, fundraise is a sort of synonym for crowdfunding. It&#8217;s a synonym for donations and so on. So, we&#8217;ll highlight those results as well. So in, in many ways, it&#8217;s a little bit more sophisticated, and maybe the .org search could have some of that goodness thrown into it in the future. Albeit not with the same budget that Google clearly has.</p>



<p>[00:33:36] <strong>Matt Cromwell:</strong> Yeah, absolutely. That&#8217;s also a real reason why if you do have a free plugin on .org, it&#8217;s really good to make sure that you have folks who actually link to that plugin on .org. Not only linking to your website itself but to your free plugin on .org. Because then Google will pick up, oh, when folks are looking for fundraise plugin, they actually are looking for this Give thing, that might not rank as well on .org, but it is gonna rank great on Google, because Google does figure that out.</p>



<p>[00:34:04] <strong>Nathan Wrigley:</strong> We haven&#8217;t really strayed into this subject, but I&#8217;m wondering if you&#8217;ve had any experience with alternative marketplaces. The only one that really comes into my mind is Envato. Where for many years they&#8217;ve had a kind of rival plugin marketplace. I really haven&#8217;t been looking at how successful that&#8217;s been going, many years since I last visited it. But the option for plugin developers to sort of, corral together and have a completely different space. But it feels to me that in the end, potentially you just end up with the same problem, but in a third party marketplace.</p>



<p>[00:34:36] <strong>Matt Cromwell:</strong> Yeah, and that third party marketplace has very strong priorities around the way it wants to be paid, and the types of products it wants to be highlighting. They are far more opinionated about the way all of the products there are found and discovered. And it is really for the, the bottom line of Envato.</p>



<p>And I think, honestly, that&#8217;s one thing that&#8217;s a bit of an untapped conversation is the significance of having what is essentially a marketplace being owned by a non-profit organization, like the WP Foundation. I do think that&#8217;s a significant conversation and the more folks need to be having and recognize that we&#8217;re not just really all fighting for attention from a LLC or some giant corporation. We&#8217;re really trying to contribute together on a public project that should be primarily influenced by a non-profit organization instead.</p>



<p>[00:35:29] <strong>Nathan Wrigley:</strong> I guess the long and the short of this episode would be, from your perspective, is the Word Press repository perfect? No. Is it useful? Yes. And that perhaps is enough for now. Could it be improved? Another yes, but for now that seems to be, at least for you and your experience, good enough</p>



<p>[00:35:47] <strong>Matt Cromwell:</strong> Absolutely. I think it&#8217;s viable. I think it can be very helpful and beneficial. It doesn&#8217;t have to be your, it shouldn&#8217;t be your only tactic. But it also shouldn&#8217;t be easily ignored either.</p>



<p>[00:35:58] <strong>Nathan Wrigley:</strong> So just to round off the conversation, one final question. How do you view your efforts on the WordPress repository as against all of the other things that you do outside of WordPress. So for example, Google and so on? You may have data to hand, you may not, I don&#8217;t know. But I&#8217;m just wondering if, one is equal to another or if the .org side definitely comes in second place, or perhaps it is the primary channel of your sales funnel.</p>



<p>[00:36:23] <strong>Matt Cromwell:</strong> Because there are different types of freemium models, that answer will be different based on the product owner and the route that they chose. If it&#8217;s a free plugin with a pro version, meaning you have to uninstall the free one in order to install the pro one, their priorities are probably gonna be very different.</p>



<p>But in our case, similar to Woo Commerce, it&#8217;s a core free plugin, and any of the paid add-ons require the free version to be installed. And because of that setup that we have, and WooCommerce has as well, the free plugin is foundational to everything we do. We&#8217;re always improving the free plugin in order for it to be more powerful, more streamlined, and for it to be able to enable us to do more things in the pro add-ons as well.</p>



<p>So being able to really parse it between priorities, it&#8217;s almost impossible. Because for us, the free plugin really encompasses the whole ecosystem of what Give actually does and means for us as a business, and as a product for the users.</p>



<p>[00:37:21] <strong>Nathan Wrigley:</strong> I&#8217;m sure that this will be something which resonates with a lot of people. I don&#8217;t really know which side of the fence the audience will be sitting on, but no doubt there will be some commentary. There&#8217;ll be people wishing to explain their reasoning behind this, one way or another. Please feel free to go to the post on WP Tavern, and leave us some comments there. But for now, thank you so much Matt Cromwell for explaining your position about the WordPress.org repo. I appreciate it.</p>



<p>[00:37:47] <strong>Matt Cromwell:</strong> Absolutely. Thank you so much.</p>
</div>



<p>On the podcast today we have <a href="https://twitter.com/learnwithmattc">Matt Cromwell</a>.</p>



<p>Matt is Senior Director of Operations and Marketing at <a href="https://twitter.com/learnwithmattc">StellarWP</a>, where he provides marketing and business insights and coaching to burgeoning WordPress product owners. He’s also one of the founders of <a href="https://givewp.com/">GiveWP</a>, a donations plugin which uses the freemium model, having a free version on the WordPress.org repository as well as a paid premium offering.</p>



<p>The WordPress.org repository is where you find yourself when you click the ‘add new’ button in the WP admin. It’s a place where plugin developers can, if they follow the guidelines, host their plugins. It provides a direct line of access to all WordPress websites, and is therefore a convenient, free place to host your plugin. In return, the plugins in the repository must be freely available by the plugin authors.</p>



<p>In the past few weeks, the repository has been in the news. Some statistics were unexpectedly removed, and this has led to conversation about the governance of the repository, as well as questions about whether the repository is still a worthwhile place to offer your free plugins, if you have a premium tier.</p>



<p>Alex Denning wrote a post entitled “<a href="https://getellipsis.com/blog/org-is-ineffective-plugin-distribution">WordPress.org is ineffective for plugin distribution in 2022</a>”, in which he lays out his thoughts as to why he no longer recommends the WordPress repository. The battle against already successful plugins, low conversation rates and the difficulty in gaining visibility are amongst the arguments that he puts forward.</p>



<p>Shortly after Alex’s post was published, Matt Cromwell posted a rebuttal entitled “<a href="https://www.mattcromwell.com/the-case-for-the-wordpress-plugin-freemium-model/">The Case for the WordPress Freemium Model</a>”, and this is the basis of the podcast today.</p>



<p>We talk about Matt’s history in WordPress as a premium plugin owner, and how his experience leads him to conclude differently; that the WordPress repository can be successful, given the right expectations and approach. He’s found using the repository to be an effective channel to drive the plugin’s premium tier, as well as a way of offering a useful free donation tool to the community.</p>



<p>It’s a fascinating chat and is sure to interest anyone thinking about starting a freemium plugin.</p>



<h2>Useful links.</h2>



<p><a href="https://getellipsis.com/blog/org-is-ineffective-plugin-distribution">WordPress.org is ineffective for plugin distribution in 2022</a></p>



<p><a href="https://www.mattcromwell.com/the-case-for-the-wordpress-plugin-freemium-model/">The case for the WordPress freemium model</a></p>



<p><a href="https://givewp.com/">GiveWP</a></p>



<p><a href="https://orderable.com/">Orderable</a></p>



<p><a href="https://stellarwp.com/">StellarWP</a></p>



<p><a href="https://wordpress.org/plugins/cubecolour-new-plugins/">Cubecolour New Plugins</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 03 Nov 2022 08:49:23 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:54:"Post Status: WordPress 6.1 • Raghavendra Satish Peri";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=142548";s:7:"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://poststatus.com/wordpress-6-1-raghavendra-satish-peri/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:15427:"<h2 id="h-this-week-at-wordpress-org-october-31-2022">This Week at WordPress.org (October 31, 2022)</h2>


<div class="has-background has-theme-palette-8-background-color wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">#WordPress 6.1 was released on November 1. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2728.png" alt="✨" class="wp-smiley" /> Check out all the updated and revised support articles. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4d6.png" alt="📖" class="wp-smiley" /> Learn about #accessibility and contributor Raghavendra Satish Peri from the WordPress India community. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ee-1f1f3.png" alt="🇮🇳" class="wp-smiley" /> </p></div>


<div class="wp-block-spacer"></div>



<div id="kt-info-box_68609b-a8" class="wp-block-kadence-infobox"><div class="kt-blocks-info-box-link-wrap kt-blocks-info-box-media-align-left kt-info-halign-left"><div class="kt-blocks-info-box-media-container"><div class="kt-blocks-info-box-media kt-info-media-animate-none"><div class="kadence-info-box-icon-container kt-info-icon-animate-none"><div class="kadence-info-box-icon-inner-container"><span class="kt-info-svg-icon kt-info-svg-icon-fe_arrowUpCircle"></span></div></div></div></div><div class="kt-infobox-textcontent"><h2 class="kt-blocks-info-box-title"><a href="https://make.wordpress.org/core/2022/08/10/proposal-stop-merging-experimental-apis-from-gutenberg-to-wordpress-core/">WordPress 6.1 </a>&#8220;Misha&#8221;</h2><p class="kt-blocks-info-box-text"><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2b06.png" alt="⬆" class="wp-smiley" /> <a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1 “Misha”</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/23ea.png" alt="⏪" class="wp-smiley" /> <a href="https://make.wordpress.org/hosting/2022/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f1ee-1f1f3.png" alt="🇮🇳" class="wp-smiley" /> <a href="https://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/">Raghavendra Satish Peri</a><br /><br /><img src="https://s.w.org/images/core/emoji/14.0.0/72x72/267b.png" alt="♻" class="wp-smiley" /> <a href="https://make.wordpress.org/project/2022/11/01/sustainability-channel-what-should-we-do/">Call for Comments — What Does Sustainability Mean to You?</a></p></div></div></div>



<h2 id="h-news">News<a href="https://wordpress.org/news/2022/10/wordpress-6-1-release-candidate-3/"></a></h2>



<ul>
<li><a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1 “Misha”</a></li>



<li><a href="https://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/">People of WordPress: Raghavendra Satish Peri</a></li>



<li><a href="https://wordpress.org/news/2022/10/episode-42-something-spooky-this-way-comes/">WP Briefing: Episode 42: Something Spooky This Way Comes</a></li>
</ul>



<div class="wp-block-kadence-spacer aligncenter kt-block-spacer-_121b9e-cb"><div class="kt-block-spacer kt-block-spacer-halign-center"><hr class="kt-divider" /></div></div>



<div class="is-layout-flex wp-container-35 wp-block-columns">
<div class="is-layout-flow wp-block-column">
<h2 id="h-community">Community</h2>



<ul>
<li><a href="https://make.wordpress.org/community/2022/11/02/recap-of-the-diverse-speaker-training-group-wpdiversity-amer-emea-on-october-26-2022/">Recap of the Diverse Speaker Training group (#WPDiversity) AMER/EMEA on October 26, 2022</a></li>



<li><a href="https://make.wordpress.org/community/2022/10/27/deputy-training-4-wordcamp-process-flow-recap/">Deputy Training #4: WordCamp Process Flow Recap</a></li>
</ul>



<h2 id="h-core"><a href="https://make.wordpress.org/core">Core</a> </h2>



<ul>
<li><a href="https://make.wordpress.org/core/2022/11/01/a-week-in-core-october-31-2022/">A Week in Core – October 31, 2022</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/31/wordpress-6-1-release-candidate-6-rc6-now-available-for-testing/">WordPress 6.1 Release Candidate 6 (RC6) Now Available for Testing</a></li>



<li><a href="https://make.wordpress.org/core/2022/10/31/postponed-to-wp-6-2-escaping-table-and-field-names-with-wpdbprepare/">Postponed to WP 6.2: Escaping Table and Field names with <code>wpdb::prepare()</code></a></li>



<li><a href="https://make.wordpress.org/core/2022/10/28/core-editor-improvement-advancing-the-writing-experience/">Core Editor Improvement: Advancing the writing experience</a></li>
</ul>



<h3 id="h-meetings">Meetings</h3>



<ul>
<li><a href="https://make.wordpress.org/core/2022/11/02/dev-chat-agenda-november-2-2022/">Dev Chat agenda, November 2, 2022</a></li>



<li><a href="https://make.wordpress.org/core/2022/11/01/editor-chat-agenda-2-november-2022/">Editor Chat Agenda: 2 November 2022</a></li>
</ul>



<h2 id="h-documentation"><a href="https://make.wordpress.org/docs">Documentation</a></h2>



<ul>
<li><a href="https://make.wordpress.org/docs/2022/11/02/summary-of-docs-team-meeting-november-1-2022/">Summary of Docs Team Meeting November 1, 2022</a></li>



<li><a href="https://make.wordpress.org/docs/2022/10/28/the-documentation-team-contributor-day-summary/">The Documentation team Contributor Day summary</a></li>
</ul>



<h3 id="h-support-articles"><br />Support Articles</h3>



<ul>
<li><a href="https://wordpress.org/support/article/colors-settings-overview/">Colors Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/layout-settings-overview/">Layout Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/typography-settings-overview/">Typography Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/twenty-twenty-three/">Twenty Twenty-Three</a></li>



<li><a href="https://wordpress.org/support/article/twenty-twenty-three-changelog/">Twenty Twenty-Three Changelog</a></li>



<li><a href="https://wordpress.org/support/article/border-settings-overview/">Border Settings Overview</a></li>



<li><a href="https://wordpress.org/support/article/post-author-biography-block/">Post Author Biography Block</a></li>



<li><a href="https://wordpress.org/support/article/comment-template-block/">Comment Template Block</a></li>



<li><a href="https://wordpress.org/support/article/comment-edit-link-block/">Comment Edit Link Block</a></li>



<li><a href="https://wordpress.org/support/article/comment-reply-link-block/">Comment Reply Link Block</a></li>
</ul>



<h2 id="h-hosting"><a href="https://make.wordpress.org/hosting">Hosting</a></h2>



<ul>
<li><a href="https://make.wordpress.org/hosting/2022/10/19/call-for-action-testing-rollback-feature/">Call For Action – Testing Rollback Feature</a></li>
</ul>



<h2 id="h-marketing"><a href="https://make.wordpress.org/marketing">Marketing</a></h2>



<ul>
<li><a href="https://make.wordpress.org/marketing/2022/11/02/agenda-wordpress-global-marketing-team-meeting-november-2-2022/">Agenda: WordPress global Marketing Team meeting, November 2, 2022</a></li>



<li><a href="https://make.wordpress.org/marketing/2022/11/01/notes-global-marketing-team-meeting-october-26-2022/">Notes: Global Marketing Team meeting, October 26, 2022</a></li>
</ul>



<h2 id="h-meta"><a href="https://make.wordpress.org/meta">Meta</a></h2>



<ul>
<li><a href="https://make.wordpress.org/meta/2022/10/21/wordpress-org-redesign-update/">WordPress.org Redesign Update</a></li>



<li><a href="https://make.wordpress.org/meta/2022/10/20/displaying-style-variations-for-supporting-themes/">Displaying Style Variations for Supporting Themes</a></li>
</ul>



<h2 id="h-mobile"><a href="https://make.wordpress.org/mobile">Mobile</a></h2>



<ul>
<li><a href="https://make.wordpress.org/mobile/2022/11/01/call-for-testing-wordpress-for-android-21-1/">Call for Testing: WordPress for Android 21.1</a></li>



<li><a href="https://make.wordpress.org/mobile/2022/11/01/call-for-testing-wordpress-for-ios-21-1/">Call for Testing: WordPress for iOS 21.1</a></li>



<li><a href="https://make.wordpress.org/updates/2022/11/02/mobile-team-update-november-2nd-2/">Mobile Team Update – November 2nd</a></li>
</ul>
</div>



<div class="is-layout-flow wp-block-column">
<h2 id="h-performance"><a href="https://make.wordpress.org/performance/">Performance</a></h2>



<ul>
<li><a href="https://make.wordpress.org/core/2022/11/01/performance-team-meeting-summary-1-november-2022/">Performance Chat Summary: 1 November 2022</a></li>
</ul>



<h2 id="h-plugins"><a href="https://make.wordpress.org/plugins">Plugins</a></h2>



<ul>
<li><a href="https://make.wordpress.org/updates/2022/10/31/plugin-review-team-31-oct-2022-%F0%9F%91%BB/">Plugin Review Team: 31 Oct 2022&nbsp;</a></li>
</ul>



<h2 id="h-polyglots">Polyglots</h2>



<ul>
<li><a href="https://make.wordpress.org/polyglots/2022/11/02/agenda-weekly-polyglots-chat-nov-2-2022-700-utc/">Agenda: Weekly Polyglots Chat – Nov. 2, 2022 (7:00 UTC)</a></li>
</ul>



<h2 id="h-project"><a href="https://make.wordpress.org/project">Project</a></h2>



<ul>
<li><a href="https://make.wordpress.org/project/2022/11/01/sustainability-channel-what-should-we-do/">Now we have a sustainability channel in Making WordPress Slack, what should we do?</a></li>
</ul>



<h2><a href="https://make.wordpress.org/support">Support</a></h2>



<ul>
<li><a href="https://make.wordpress.org/updates/2022/10/27/support-team-meeting-updates-for-october-27/">Support Team Meeting Updates for October 27</a></li>
</ul>



<h2 id="h-test"><a href="https://make.wordpress.org/test">Test</a></h2>



<ul>
<li><a href="https://make.wordpress.org/test/2022/10/26/hallway-hangout-discussion-on-wrapping-phase-2-26-oct/">Hallway Hangout: Discussion on wrapping Phase 2 (26 Oct)</a></li>



<li><a href="https://make.wordpress.org/updates/2022/10/31/test-team-update-31-october-2022/">Test Team Update: 31 October 2022</a></li>
</ul>



<h2 id="h-themes"><a href="https://make.wordpress.org/themes">Themes</a></h2>



<ul>
<li><a href="https://make.wordpress.org/updates/2022/11/01/themes-team-update-november-01-2022/">Themes team update November 01, 2022</a></li>
</ul>



<h2 id="h-training"><a href="https://make.wordpress.org/training">Training</a></h2>



<ul>
<li><a href="https://learn.wordpress.org/individual-learner-survey/">How did you learn WordPress?</a></li>



<li><a href="https://make.wordpress.org/training/2022/11/01/summary-update-courses-currently-in-development-1-november-2022/">Summary Update: Courses Currently in Development or Published (1 November 2022)</a></li>



<li><a href="https://make.wordpress.org/training/2022/10/31/meeting-agenda-for-november-1-2022/">Meeting Agenda for November 1, 2022</a></li>
</ul>



<h3 id="h-tutorials">Tutorials</h3>



<ul>
<li><a href="https://learn.wordpress.org/tutorial/using-block-template-parts-in-classic-themes/">Using Block Template Parts in Classic Themes</a></li>



<li><a href="https://learn.wordpress.org/tutorial/a-beginners-guide-to-the-wordpress-template-hierarchy/">A Beginners Guide to the WordPress Template Hierarchy</a></li>



<li><a href="https://learn.wordpress.org/tutorial/tools-import-and-export/">Tools: Import and Export</a></li>
</ul>



<h3 id="h-online-workshops">Online Workshops</h3>



<ul>
<li><a href="https://learn.wordpress.org/?meeting=the-creative-side-of-blocks-vol-3">The Creative Side of Blocks, Vol. 3</a></li>



<li><a href="https://learn.wordpress.org/?meeting=padding-margin-and-block-spacing">Padding, Margin and Block Spacing</a></li>



<li><a href="https://learn.wordpress.org/?meeting=lets-code-internationalisation-in-block-themes">Let’s code! Internationalisation in Block Themes</a></li>



<li><a href="https://learn.wordpress.org/?meeting=wordpress-development-live-stream-internationalisation">WordPress development live stream: Internationalisation</a></li>
</ul>



<h3 id="h-courses">Courses</h3>



<ul>
<li><a href="https://learn.wordpress.org/course/a-developers-guide-to-block-themes-part-1/">A Developers Guide to Block Themes – Part 1</a></li>
</ul>



<h2 id="h-wptv">WPTV</h2>



<ul>
<li><a href="https://meta.trac.wordpress.org/ticket/1430">WordPress TV videos now auto-published to Youtube</a></li>



<li><a href="https://wordpress.tv/category/year/2022/">Latest WordPress TV videos</a></li>
</ul>
</div>
</div>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2 id="h-related-news">Related News:</h2>



<ul>
<li><a href="https://tc39.es/#proposals">ECMAScript Proposals</a></li>
</ul>



<p class="has-theme-palette-7-background-color has-background">Thanks for reading our WP dot .org roundup! Each week we are highlighting the news and discussions coming from the good folks making WordPress possible. If you or your company create products or services that use WordPress, you need to be engaged with them and their work. Be sure to share this resource with your product and project managers. <br /><br /><strong>Are you interested in giving back and contributing your time and skills to WordPress.org?</strong> <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://wordpress.org/support/article/contributing-to-wordpress/">Start Here ›</a><br /><br /><strong>Get our weekly WordPress community news digest</strong> — Post Status' <a href="https://poststatus.com/news/week-in-review/">Week in Review</a> — covering the WP/Woo news plus significant writing and podcasts. It's also available in <a href="https://poststatus.com/newsletter">our newsletter</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f48c.png" alt="💌" class="wp-smiley" /></p>



<div class="wp-block-spacer"></div>



<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">
<p class="has-text-align-left has-normal-font-size" id="h-get-ready-for-remote-work">You — and <a href="https://poststatus.com/#Agency">your whole team</a> can <a href="https://poststatus.com/#choose-membership">Join Post Status</a> too!</p>



<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/14.0.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/14.0.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/14.0.0/72x72/1f426.png" alt="🐦" class="wp-smiley" /> and <a href="https://www.linkedin.com/company/post-status-llc/">LinkedIn</a>. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f4bc.png" alt="💼" class="wp-smiley" /></p>
</div></div>



<div class="wp-block-spacer"></div>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 03 Nov 2022 02:53:31 +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:43;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:45:"Post Status: The WordPress Enterprise Paradox";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://poststatus.com/?p=142360";s:7:"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://poststatus.com/the-wordpress-enterprise-paradox/";s: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:13115:"<div class="is-layout-flow wp-block-group eplus-wrapper has-theme-palette-2-color has-theme-palette-8-background-color has-text-color has-background"><div class="wp-block-group__inner-container"><div class="wp-block-post-excerpt"><p class="wp-block-post-excerpt__excerpt">&#8220;WordPress as a platform is putting us on the enterprise path. But what got us here is what makes us irrelevant,&#8221; says Magne Ilsaas, CEO and Founding Partner of Dekode. Magne wants to start an overdue conversation about three big risks — and opportunities — for WordPress agencies: 1) A lack of spaces for professional conversations and knowledge-sharing, including professional events, meetups,  and mastermind groups catering to enterprise WordPress. 2) Successful agencies that use WordPress extensively with little or no community involvement whose work would benefit from enterprise WordPress peer networks. 3) An over-emphasis in WordPress agencies on short-term engineering solutions to the exclusion of long-term business solutions. What's often left out is design, user experience, and most of all the capacity to play a strategic advisory role in partnership with clients.  </p></div>


<div class="wp-block-spacer eplus-wrapper"></div>



<p class="yoast-reading-time__wrapper"><span class="yoast-reading-time__icon"></span><span class="yoast-reading-time__spacer"></span><span class="yoast-reading-time__descriptive-text">Estimated reading time:  </span><span class="yoast-reading-time__reading-time">4</span><span class="yoast-reading-time__time-unit"> minutes</span></p>
</div></div>



<p class="has-drop-cap">As more and more enterprises move onto WordPress and digital becomes the backbone of modern business, we need to become more than developers and designers. We are now business advisors, thinking on behalf of the companies we work for.</p>



<p>Agencies focusing on open source and WordPress are in a pretty good spot these days. Demand for WordPress development has never been higher, and we continue to see bigger companies building their websites on WordPress.&nbsp;</p>



<blockquote><p>Most clients know WordPress may not be the best choice, but they are starting to understand that “best choice” isn’t relevant.&nbsp;</p></blockquote>



<p>At Dekode we are focusing on enterprise clients, and it's really fun when large, interesting projects come our way — because of WordPress. It is a real contrast to how it used to be when most of our client meetings were spent explaining why WordPress is a good choice. Now it's rarely discussed at all. Most clients that come our way have already decided that WordPress is the right choice for them. Even big public tenders call out for WordPress.</p>



<p>Most of them know it's not necessarily the best choice, but they are starting to understand that “best choice” isn’t relevant.&nbsp;</p>



<p>If a client in 2017 set out to choose a CMS and had the slightest idea of what they were doing, they would have a shortlist of three to five CMSs to choose from. The truth is that any of them would have been a good choice, and any of them could be bent into shape to suit the client’s needs.</p>



<div class="is-layout-constrained wp-block-group has-theme-palette-8-background-color has-background"><div class="wp-block-group__inner-container">
<h2 id="h-the-paradox"><strong>The Paradox</strong>:</h2>



<p><strong>WordPress as a platform is putting us on the enterprise path.&nbsp;</strong></p>



<p><strong>But what got us here is what makes us irrelevant.</strong></p>
</div></div>



<h2 id="h-can-we-overcome-success">Can We <strong>Overcome Success</strong>?</h2>



<p>With the traction WordPress has gained over the last 15 years, we see that more and more enterprise companies are opening their eyes to what we can do with WordPress, but too often it’s for the wrong reasons.&nbsp;</p>



<p>For large parts of the WordPress industry, plugins, themes, and soon-to-be <em>Gutenblocks</em> are the fuel that keeps the WordPress snowball rolling. SMBs spinning up WordPress websites on the fly.&nbsp; The platform is really great at this because it's so easy and flexible. It's a Swiss Army Knife on steroids, able to adapt to anyone's needs.&nbsp;</p>



<blockquote><p>Some of the best WordPress projects are done by agencies that don’t really care about WordPress or the WordPress community. </p></blockquote>



<p>But here is the paradox: this success is holding us back now because the thousands of plugins and DIY articles and solutions generally aren’t meant or relevant for the enterprise market. This means that a lot of enterprise companies are building patchwork WordPress installations that may or may not scale, be secure, or actually work as a modern digital tool for solving business needs.&nbsp; As we build more and more functionality and options, we are strolling farther and farther away from the enterprise playing field.</p>



<p>Some of the best WordPress projects are done by agencies that don’t really care about WordPress or the WordPress community. Why? Because they use WordPress for what it is. A tool that gets the job done, cheaply and effectively. But as the web gets more and more complex, some of these agencies don't have the people with the necessary skills, and we are seeing more high-profile enterprise clients with low-quality WordPress websites.</p>



<p>So we are putting ourselves in a pretty bad position at the moment.&nbsp;</p>



<p>With the rising demand for WordPress experts, everything should be great. But the fact is that there are too many high-profile websites out there with really poor-quality work under the hood. And the reputation WordPress has as an alternative for enterprise will deteriorate as these solutions fall apart piece by piece.</p>



<blockquote><p>Do we actually solve someone's business goal or a user's need? Mileage varies — a lot.</p></blockquote>



<p>Even though we are busy discussing our tool and what it can and cannot do, some WordPress enterprise projects actually do end up with a skillful WordPress agency. But all too often, the decision of what CMS to build on is made after a lot of the important strategic decisions are made—or even after the design is done.</p>



<p>Too often other agencies are helping clients with strategic decision-making, design and communication, user testing,&nbsp; conversion optimization, and digital marketing.</p>



<p>When competing platforms can offer a full spectrum of expertise, it really doesn't matter how good we are as developers. If the solutions we help create don't deliver on basic user needs and business goals, where is the value to the client? But too often we are not in a position to affect quality and business impact. Most of the time we are missing the show by collectively taking ourselves <em>off</em> the playing field.</p>



<h2 id="h-is-wordpress-enterprise-ready"><strong>Is WordPress enterprise ready?</strong></h2>



<p>From a technical perspective, the answer is obviously yes.&nbsp;</p>



<p>From a <em>people</em> perspective, the answer is much less clear: yes and no.</p>



<p>For the enterprise, WordPress is still a pretty risky move. But not because there aren't agencies that can deliver high-quality code, security, and scalability. It's amazing what the best developers can spin up on WordPress, but that doesn't really matter if everyone but the developers understands how they are (or aren’t) delivering a positive user experience and solving the client's business problems.&nbsp;</p>



<blockquote><p>Imagine a way of doing business that is not about redesign loops and short-term decisions but a way to create sustainable digital platforms and deliver long-term value to our clients.</p></blockquote>



<p>Today when we get a project brief, there are no technical reasons why you shouldn't choose WordPress. Subjectively speaking, it's probably the best CMS out there, for many reasons.&nbsp;</p>



<p>But that doesn't mean that it is the right choice for an enterprise business.</p>



<p>There are plenty of examples of enterprise websites that run on WordPress. Technically many of them are flawless, and some even look good, but do they actually solve someone's business goal or a user's need? Mileage varies — a lot.</p>



<h2 id="h-the-secret-sauce"><strong>The Secret Sauce</strong></h2>



<p>Digital is becoming the foundation of modern businesses, and in order to stay relevant, it is not enough to be only designers and developers anymore. We need to develop our skills further and become business designers and long-term digital partners for our clients.</p>



<p>The best solutions can be made when we take our WordPress knowledge and developer skills and use them to create sustainable platforms and design systems that align with business strategy, user needs, and digital marketing.</p>



<p>We need to hold ourselves accountable to a long-term perspective for the decisions we make and the solutions we create. To stay relevant, we need to understand success is the value we deliver — on top of the technology.&nbsp;&nbsp;</p>



<p>There are plenty of WordCamps, seminars, podcasts, blogs, tutorials, and meetups out there.&nbsp;</p>



<blockquote><p>To stay relevant, we need to understand success is the value we deliver — on top of the technology.&nbsp;&nbsp;</p></blockquote>



<p>But what they all have in common is that they are aimed at the mass market side of WordPress where price tags are low and scale is everything. This is fantastic, and it will keep the WordPress snowball rolling.</p>



<p>But why is there no arena for professional conversations around WordPress Enterprise?</p>



<p>Why is there no knowledge sharing about creating value on top of the tools we create?</p>



<p>What if we did business the same way we've built WordPress? What if we leverage our biggest asset, which is not WordPress the tool. It’s WordPress, the community, the culture, the openness, and the inclusiveness. What if we create our own way of integrating our open-source mindset into how we conduct our businesses?</p>



<blockquote><p>We need a WordPress mindset, a WordPress way of doing business, that enables value creation for everyone involved.</p></blockquote>



<p>Imagine a way of doing business that is not about redesign loops and short-term decisions but a way to create sustainable digital platforms and deliver long-term value to our clients.</p>



<p>In my opinion, there are enough strong forces in play to keep WordPress as a platform enterprise-ready and relevant. But I’m not sure that matters without a better understanding and focus on how we can deliver value on top of the tools we create.&nbsp;</p>



<p>My wish is for WordPress to be known as more than the most cost-effective, enterprise-ready technology. I want it to be known for a WordPress mindset, a WordPress way of doing business, that enables value creation for everyone involved.&nbsp;</p>



<div class="wp-block-spacer"></div>



<div class="is-layout-constrained wp-block-group has-theme-palette-7-background-color has-background"><div class="wp-block-group__inner-container">
<h2>Help make it happen! Join <a href="https://poststatus.slack.com/archives/C02TNBDAXLL"><span>#agency-owners</span></a> in Post Status Slack.</h2>



<p>Leave a <a href="https://poststatus.com/planet/feed/#comments">comment</a>, get in touch, or jump into <a href="https://poststatus.slack.com/">Post Status Slack</a> if this is a conversation you'd like to contribute to.</p>
</div></div>



<div class="wp-block-spacer"></div>



<div class="wp-block-media-text is-stacked-on-mobile has-background" id="author"><a href="https://dekode.no/"><img width="752" height="752" src="https://cdn.poststatus.com/wp-content/uploads/2022/11/ab58aa31afffd4af6284f4244b9f61a8-752x752.webp" alt="Magne Ilsaas" class="not-transparent wp-image-142508 size-medium" /></a><div class="wp-block-media-text__content">
<p><strong>Magne Ilsaas</strong> is the founder and manager of <strong><a href="https://dekode.no">Dekode</a></strong>, Norway`s biggest WordPress agency. He works on bridging the gap between design and engineering in order to create the best and most cost-efficient WordPress projects. When he`s not working, you`ll find him skiing or fishing in Lofoten.</p>



<ul class="is-horizontal is-content-justification-center is-layout-flex wp-container-40 wp-block-social-links alignright has-small-icon-size is-style-default"><li class="wp-social-link wp-social-link-twitter wp-block-social-link"><a href="https://twitter.com/dekodeno/" class="wp-block-social-link-anchor"><span class="wp-block-social-link-label screen-reader-text">Twitter</span></a></li>

<li class="wp-social-link wp-social-link-linkedin wp-block-social-link"><a href="https://www.linkedin.com/in/magne-ilsaas-4968b75/" class="wp-block-social-link-anchor"><span class="wp-block-social-link-label screen-reader-text">LinkedIn</span></a></li></ul>
</div></div>



<p></p>
<p>This article was published at Post Status — the community for WordPress professionals.</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, 02 Nov 2022 23:24:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Magne Ilsaas";s: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:"
	
	
	
	
	
	
";s: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:61:"WPTavern: WP All Import Is Moving Away from Lifetime Licenses";s:7:"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=139123";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:72:"https://wptavern.com/wp-all-import-is-moving-away-from-lifetime-licenses";s: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:4078:"<p>WP All Import <a href="https://www.wpallimport.com/your-last-chance-to-buy-unlimited-lifetime-licenses/">announced</a> it will soon change its business model to annual licenses. The product, which includes free and commercial versions, allows users to import/export XML, CSV, or Excel data and integrates with more than a dozen popular plugins. Since its founding in 2011, WP All Import has been sold with unlimited, lifetime licenses. The product has more than 12,000 customers.</p>



<p>In a statement published this week, WP All Import explained that the company went with lifetime licenses from the beginning because most commercial plugins were sold this way when they started in 2011 and customers began to expect it. </p>



<p>Some companies have had a rocky transition out of providing lifetime licenses, as the community saw with <a href="https://wptavern.com/delicious-brains-acquires-advanced-custom-fields-plugin">Delicious Brains&#8217; acquisition of ACF</a> in June 2021. Although they assured existing customers that they would honor their lifetime licenses, a few months later on Black Friday, Delicious Brains began <a href="https://wptavern.com/acf-solicits-lifetime-license-holders-for-contributions-urging-them-to-purchase-annual-subscriptions">urging them to purchase annual subscriptions</a>. For many companies transitioning away from old pricing strategies, lifetime license holders become dead weight, requiring support without putting revenue back into the company. WP All Import has found success with offering lifetime licenses for 11 years, but the company is making sure its new customers will be paying every year:</p>



<blockquote class="wp-block-quote">
<p>We are not making this change because because lifetime licenses are inherently unsustainable or support costs are spiraling out of control.</p>



<p>WP All Import is a profitable business, support costs generally follow revenue up and down, and lifetime licenses for WordPress plugins are absolutely a sustainable business model.</p>



<p><strong>We are moving to annual licenses simply because we will make more money.</strong></p>



<p>&#8220;While lifetime licenses work, annual licenses are absolutely more profitable over the long term. This is why you see almost every piece of software on earth now being sold with one.&#8221;</p>
</blockquote>



<p>WP All Import is one of the few remaining companies that is still using a lifetime license pricing strategy. The company noted that over the past ten years, the budgets for WordPress projects have grown along with the quality of their software. </p>



<p>Generally, the response to the news has been positive. Some are considering purchasing lifetime licenses before they are no longer offered. One customer said he appreciated the honest communication but bristled at the notion that &#8220;people just expect to have to renew their software licenses.&#8221; </p>



<p>&#8220;No,&#8221; developer Patrick van Kouteren said. &#8220;It is being forced upon consumers because it generates more revenue for the business selling it.&#8221;</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Well, that's honest from WP All Import. But followed by a bullshit statement: "people just expect to have to renew". No. It is being forced upon consumers because it generates more revenue for the business selling it. <a href="https://t.co/U1p0qy4JJt">pic.twitter.com/U1p0qy4JJt</a></p>&mdash; Patrick van Kouteren (@pvankouteren) <a href="https://twitter.com/pvankouteren/status/1587721931696050182?ref_src=twsrc%5Etfw">November 2, 2022</a></blockquote>
</div>



<p>WP All Import assured existing customers that it will continue to honor their lifetime licenses and offer the same level of support. If the company releases new products in the future, lifetime license holders will be eligible to purchase annual licenses for these products at discounted rates. WP All Import said the company will be making these changes &#8220;sometime later this year or next year.&#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:"Wed, 02 Nov 2022 22:07: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:45;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:116:"WPTavern: WordPress 6.1 Introduces New Default Theme and Fluid Typography, Expands Design Tools and Template Options";s:7:"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=139076";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:126:"https://wptavern.com/wordpress-6-1-introduces-new-default-theme-and-fluid-typography-expands-design-tools-and-template-options";s: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:5422:"<p><a href="https://wordpress.org/news/2022/11/misha/">WordPress 6.1 &#8220;Misha&#8221;</a> was released today, named for Soviet-Norwegian jazz pianist <a href="https://en.wikipedia.org/wiki/Mikhail_Alperin">Mikhail “Misha” Alperin</a>, who was born in Ukraine in 1956. A founding member of the first Moldavian jazz quartet, and later the <a href="https://en.wikipedia.org/wiki/Moscow_Art_Trio">Moscow Art Trio</a>, Alperin became known for his distinct and bewitching blend of jazz and folk music.</p>



<p>This release is the culmination of a months-long effort to <a href="https://github.com/WordPress/gutenberg/issues/43241">improve the design tooling consistency</a> of WordPress&#8217; core blocks. That means blocks that were missing things like typography, color, and border support have been updated wherever possible to match the support included in other blocks. Design tools and their controls are also now more consistently presented, so users can intuitively know what to expect when customizing their blocks.</p>



<img />image credit: WordPress 6.1 About page



<p>WordPress 6.1 <a href="https://make.wordpress.org/core/2022/07/21/core-editor-improvement-deeper-customization-with-more-template-options/">expands the templates options</a> available for site editing. Theme authors and users can now create page-specific templates, custom post type and post-specific templates, user-selectable custom templates for all post types, and taxonomy-specific templates for categories or tags.</p>



<p>With all the new block design and template editing capabilities, WordPress 6.1 has added more sophisticated content-locking capabilities. Block-locking can now be applied to all inner blocks in one click. This applies to containing blocks like Group, Cover, and Column blocks.</p>



<img />image credit: WordPress 6.1 About Page



<p>Menu management has also gotten a big update in 6.1, with menu controls relocated to their own place in the block settings. The navigation block now offers new fallback options in case the block isn&#8217;t pre-populated with inner blocks. If the navigation menu is empty, the fallback behavior is to display a list of available pages using the Page List block. If there are multiple block menus, the fallback is to display the most recently created block menu. This ensures that users aren&#8217;t stuck and can more easily understand where their menus will show up.</p>



<h3>New Twenty Twenty-Three Default Theme with 10 Style Variations</h3>



<p>One of the most anticipated parts of this release is the new <a href="https://wordpress.org/themes/twentytwentythree/">Twenty Twenty-Three</a> (TT3) default theme. This is a new kind of default theme that bundles a curated set of style variations, instead of creating a new theme from scratch. It uses a stripped-back version of Twenty Twenty-Two as the base for a theme that features <a href="https://wptavern.com/wordpress-announces-10-style-variation-selections-for-twenty-twenty-three-theme">10 community-contributed style variations</a>.</p>



<img />image credit: WordPress 6.1 About page



<p>The theme is accessibility-ready and puts the spotlight on all of the design tools available in the latest release. It is basically a blank slate for further customization, with both rich and minimalist color palettes and multiple typography options. It will be exciting to see what the world of WordPress users builds with the new theme.</p>



<img />



<p>Fluid typography makes its debut in 6.1. This feature is for theme authors but benefits users and site visitors alike. It allows authors to define font sizes that will smoothly scale between smaller and larger viewports, adapting in a fluid way to varying widths. </p>



<p>The best part of the new fluid typography feature is that it can easily be turned on by setting <code>typography.fluid</code> to be <code>true</code> in theme.json and adding <code>fluid</code> to each of the <code>settings.typography.fontSizes</code> with <code>min</code> and <code>max</code> values. If you want to see an example of fluid typography in action, look no further than the new Twenty Twenty-Three theme.</p>







<p>Other notable new features and updates in 6.1 include the following: </p>



<ul>
<li>List and Quote blocks now support inner blocks</li>



<li>Improved layout and visualization of document settings</li>



<li>Support for starter patterns for any post type</li>



<li>Filter Themes Directory for block themes in the admin</li>



<li>Improved block placeholders that show customization options</li>



<li>New system for persisting user preferences across browsers and devices</li>



<li>Block-based Template Parts now available in Classic Themes</li>



<li>Query Loop block extended to support custom queries</li>



<li>Set preset values for padding, margin and block gap</li>
</ul>



<p>WordPress 6.1 includes more than 60 <a href="https://make.wordpress.org/core/2022/10/11/wordpress-6-1-accessibility-improvements/">accessibility improvements</a> and 25 tickets dedicated to <a href="https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress-6-1/">performance</a>. This release is the result of the tireless efforts of more than 800 contributors from 60+ countries. For a quick visual tour, check out the official WordPress 6.1 promo video:</p>



<div class="wp-block-embed__wrapper">

</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, 02 Nov 2022 02:30:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:45:"WordPress.org blog: WordPress 6.1 “Misha”";s:7:"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=13798";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/news/2022/11/misha/";s: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:78897:"<img width="1024" height="683" src="https://i0.wp.com/wordpress.org/news/files/2022/11/inline-image-inline.png?resize=1024%2C683&ssl=1" alt="" class="wp-image-13872" />



<h1>Welcome to “Misha”</h1>



<p>Say hello to WordPress 6.1, “Misha,” inspired by the life and work of jazz pianist <a href="https://en.wikipedia.org/wiki/Mikhail_Alperin">Mikhail “Misha” Alperin</a>. Ukrainian-born Misha introduced the work of jazz ensembles globally and is celebrated as a founding member of the <a href="https://en.wikipedia.org/wiki/Moscow_Art_Trio">Moscow Art Trio</a>.<br /><br />“Misha” further refines the site-building experience. Inside WordPress 6.1 you’ll interact with enhancements that continue to make site creation more intuitive while pushing your creative boundaries further than ever. Don’t forget to enjoy some of Misha’s <a href="https://www.youtube.com/channel/UCuh5oEm_jJ_jTcv8DmbLi2Q">jazz piano</a> as you take in all WordPress 6.1 has to offer.</p>



<p><span>The third major release of 2022 is here. </span><a href="https://wordpress.org/wordpress-6.1.zip"><span>Download it now</span></a><span>! As of the time of this release, WordPress powers </span><a href="https://w3techs.com/technologies/overview/content_management">43%</a><span> of websites worldwide.</span></p>



<p><span>Site owners and administrators should upgrade today to take full advantage of the many stability, performance, and usability enhancements. Furthermore, WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.</span></p>



<blockquote class="wp-block-quote">
<p>This release includes features that many in the WordPress Community have been most excited about since the start of this project. Additional enhancements and improvements to the editor give site owners more control and easier customization while offering a more cohesive experience to users. A lot of writing-focused improvements are included in the release, because if you’re giving voices to the voiceless you’ve got to focus on folks writing the copy. </p>



<p>Some of my favorite enhancements are the refined ability to select partial paragraphs in a block; settings to keep list view open by default; and the keyboard shortcut to add internal links expanded to all blocks.</p>
<cite>Josepha Haden Chomphosy, Executive Director</cite></blockquote>



<div class="wp-block-buttons is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="https://wordpress.org/wordpress-6.1.zip">Download WordPress 6.1</a></div>
</div>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2>What’s Inside</h2>



<h3>Twenty Twenty-Three:<br />A fresh default theme with 10 distinct style variations</h3>



<p>After introducing foundational elements for block themes and style variations in releases 5.9 and 6.0, WordPress site builders welcome a new default theme, Twenty Twenty-Three, that is powered by <a href="https://make.wordpress.org/design/2022/09/07/tt3-default-theme-announcing-style-variation-selections/">10 different styles</a> and tagged as&nbsp; “<a href="https://make.wordpress.org/themes/handbook/review/accessibility/">Accessibility Ready</a>.” These intentionally unique styles ensure users can apply a different look and feel to their site with a single click—all within a single theme.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Style-Variation-News-1.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13843" />



<h3>New templates for an improved creator experience</h3>



<p>New and more refined templates now give site builders more control over the creation of their sites. In this suite of new templates, find a custom template for posts &amp; pages in the Site Editor. Create and edit template parts like headers and footers more quickly with a new search-and-replace tool and easily view your new site.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Templates-News.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13818" />



<h3>Design tools for more consistency and control</h3>



<p>Thoughtful upgrades to the controls for design elements and blocks make laying out and building your new site a more consistent, complete, and intuitive experience.</p>




<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Design-Tools-News.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13819" />




<h3>Manage menus with ease</h3>



<p>New fallback options in the navigation block mean you can edit the menu that’s open; no searching needed. Plus, the controls for choosing and working on menus have their own place in the block settings. The mobile menu system also gets an upgrade with new features, including different icon options, to make the menu yours.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Navigation-1.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13844" />



<h3>Cleaner layouts and document settings visualization</h3>



<p>View and manage post and page settings with a better-organized display improving the use of features like template picker and scheduler.</p>



<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Document-settings-News-1.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13838" />



<h3>One-click lock setting for all inner blocks</h3>



<p>When locking blocks, a new toggle lets you apply your lock settings to all the blocks in a containing block like the group, cover, and column blocks.</p>




<img width="1024" height="601" src="https://i0.wp.com/wordpress.org/news/files/2022/11/Lock-News.png?resize=1024%2C601&ssl=1" alt="" class="wp-image-13824" />




<h3>Improved block placeholders</h3>



<p>Various blocks have improved placeholders that reflect customization options to help you design your site and its content. For example, the Image block placeholder displays custom borders and duotone filters even before selecting an image.</p>



<h3>Compose richer lists and quotes with inner blocks</h3>



<p>The List and Quote blocks now support inner blocks, allowing for more flexible and rich compositions like adding headings inside your Quote blocks.</p>



<h3>More responsive text with fluid typography</h3>



<p>For developers working with block themes and/or <code>theme.json</code>, <a href="https://make.wordpress.org/core/2022/08/04/whats-new-in-gutenberg-13-8-3-august/#fluid-typography-support">fluid typography</a> lets you define font sizes that adapt for easy reading in any screen size.</p>



<h3>Add starter patterns to any post type</h3>



<p>In WordPress 6.0, site builders could add suggested patterns so that when creating a new page, you did not have to start blank. In 6.1, site builders can continue to opt-in to this feature for not only pages but for any post type. </p>



<h3>Find block themes faster</h3>



<p>The Themes Directory has a filter for block themes, and a pattern preview gives a better sense of what the theme might look like while exploring different themes and patterns.</p>



<h3>Keep your Site Editor settings for later</h3>



<p>Site Editor settings are now <a href="https://make.wordpress.org/core/2022/10/10/changes-to-block-editor-preferences-in-wordpress-6-1/">persistent for each user</a>. This means your settings will now be consistent across browsers and devices.</p>



<h3>A streamlined style system</h3>



<p>The CSS rules for margin, padding, typography, colors, and borders within the <a href="https://make.wordpress.org/core/2022/10/10/block-styles-generation-style-engine/">styles engine</a> are now all in one place, reducing time spent on layout-specific tasks and helps to generate semantic class names.</p>



<h3>Updated interface options and features</h3>



<p>Updates include <a href="https://make.wordpress.org/core/2022/10/10/styling-elements-in-block-themes/">styling elements</a> like buttons, citations, and links globally; controlling hover, active, and focus states for links using theme.json (not available to control in the interface yet); and customizing outline support for blocks and elements, among other features.</p>



<h3>Continued evolution of layout options</h3>



<p>The default content dimensions provided by themes can now be overridden in the Styles Sidebar, giving site builders better control over full-width content. Developers have <a href="https://make.wordpress.org/core/2022/10/10/updated-editor-layout-support-in-6-1-after-refactor/">fine-grained control over these controls</a>.</p>



<h3>Block Template parts in classic themes</h3>



<p><a href="https://make.wordpress.org/core/2022/10/04/block-based-template-parts-in-traditional-themes/">Block template parts can now be defined in classic themes</a> by adding the appropriate HTML files `parts` directory at the root of the theme.</p>



<h3>Expanded support for Query Loop blocks</h3>



<p><a href="https://make.wordpress.org/core/2022/10/10/extending-the-query-loop-block/">New filters</a> let Query Block variations support custom queries for more powerful variations and advanced hierarchical post types filtering options.</p>



<h3>Filters for all your styles</h3>



<p><a href="https://make.wordpress.org/core/2022/10/10/filters-for-theme-json-data/">Leverage filters</a> in the Styles sidebar to control settings at all four levels of your site—core, theme, user, or block, from less to more specific.</p>



<h3>Spacing presets for faster, consistent design</h3>



<p>Save time and avoid hard-coding values into a theme with <a href="https://make.wordpress.org/core/2022/10/07/introduction-of-presets-across-padding-margin-and-block-gap/">preset margin and padding values for multiple blocks.</a></p>



<h3>Content-only editing support for container blocks</h3>



<p>Thanks to content-only editing settings, layouts can be locked within container blocks. In a content-only block, its children are invisible to the List View and entirely uneditable. So you control the layout while your writers can focus on the content. Combine it with block-locking options for even more advanced control over your blocks.</p>



<h3>Other notes of interest</h3>



<ul>
<li>6.1 includes a new time-to-read feature showing content authors the approximate time-to-read values for pages, posts, and custom post types.</li>



<li>The site tagline is empty by default in new sites but can be modified in General Settings.</li>



<li>A new modal design offers a background blur effect, making it easier to focus on the task at hand.</li>
</ul>



<h2>Enhancing WordPress 6.1 Accessibility</h2>



<p>Accessibility is an integral part of the WordPress mission of fostering an inclusive community and supporting users of all types around the world. With this in mind, WordPress 6.1 includes nearly 60 updates specifically focused on enhancing the accessibility of the platform. <a href="https://make.wordpress.org/core/2022/10/11/wordpress-6-1-accessibility-improvements/">Read these updates</a> to learn more about the continual initiatives aimed at improving accessibility.</p>



<h2>Improved Performance in WordPress 6.1</h2>



<p>WordPress 6.1 resolves more than 25 tickets dedicated to enhancing performance with improvements for every type of site. A full breakdown can be found in the <a href="https://make.wordpress.org/core/2022/10/11/performance-field-guide-for-wordpress-6-1/">Performance Field Guide</a>.</p>



<h2>Learn More About WordPress 6.1</h2>



<p>See WordPress 6.1 in action! Watch a <a href="https://www.youtube.com/watch?v=1w9oywSa6Hw">brief overview video</a> highlighting some of the major features debuting in WordPress 6.1.</p>



<div class="wp-block-embed__wrapper">

</div>



<p><br /></p>



<p>Explore <a href="https://learn.wordpress.org/">learn.wordpress.org</a> for brief how-to videos and lots more on new features in WordPress. Or join a live <a href="https://learn.wordpress.org/social-learning/">interactive online </a>workshop on a specific WordPress topic.</p>



<p>Developers can explore the <a href="https://make.wordpress.org/core/2022/10/12/wordpress-6-1-field-guide/">WordPress 6.1 Field Guide</a>, complete with detailed developer notes to help you build with and extend WordPress. Read the <a href="https://wordpress.org/support/wordpress-version/version-6-1">WordPress</a><a href="https://wordpress.org/support/wordpress-version/version-6-1/"> 6.1 Release Notes</a> for more information on the included enhancements and issues fixed, installation information, developer notes and resources, release contributors, and the list of file changes in this release.</p>



<h2>The WordPress 6.1 Release Squad</h2>



<p><span>The group listed below tirelessly supported the release, from conception to ship date, and beyond:</span></p>



<p><span>Release Lead: </span><a href="https://profiles.wordpress.org/matt/"><span>Matt Mullenweg</span></a><span>&nbsp;</span><br /><span>Release Coordinators: </span><a href="https://profiles.wordpress.org/priethor/"><span>Héctor Prieto</span></a><span> and </span><a href="https://profiles.wordpress.org/desrosj/"><span>Jonathan Desrosiers</span></a><span>&nbsp;</span><br /><span>Core Tech Co-Leads: </span><a href="https://profiles.wordpress.org/mikeschroder/"><span>Mike Schroder</span></a><span>, </span><a href="https://profiles.wordpress.org/davidbaumwald/"><span>David Baumwald</span></a><span>, and </span><a href="https://profiles.wordpress.org/jeffpaul/"><span>Jeff Paul</span></a><br /><span>Editor Tech Co-Leads: </span><a href="https://profiles.wordpress.org/czapla/"><span>Michal Czaplinski</span></a><span>, </span><a href="https://profiles.wordpress.org/bernhard-reiter/"><span>Bernie Reiter</span></a><span>, and </span><a href="https://profiles.wordpress.org/cbravobernal/"><span>Carlos Bravo</span></a><br /><span>Core Triage Co-Leads: </span><a href="https://profiles.wordpress.org/audrasjb/"><span>JB Audras</span></a><span> and </span><a href="https://profiles.wordpress.org/chaion07/"><span>Ahmed Chaion</span></a><br /><span>Editor Triage Co-Leads: </span><a href="https://profiles.wordpress.org/ndiego/"><span>Nick Diego</span></a> <span>and </span><a href="https://profiles.wordpress.org/annezazu/"><span>Anne McCarthy</span></a><br /><span>Documentation Co-Leads: </span><a href="https://profiles.wordpress.org/bph/"><span>Birgit Pauli-Haack</span></a><span>, </span><a href="https://profiles.wordpress.org/milana_cap/"><span>Milana Cap</span></a><span>, and </span><a href="https://profiles.wordpress.org/femkreations/"><span>Femy Praseeth</span></a><br /><span>Marketing &amp; Communications Co-Leads:</span> <a href="https://profiles.wordpress.org/jpantani/"><span>Jonathan Pantani</span></a> <span>and </span><a href="https://profiles.wordpress.org/dansoschin/"><span>Dan Soschin</span></a><br /><span>Test Lead: </span><a href="https://profiles.wordpress.org/ironprogrammer/"><span>Brian Alexander</span></a><br /><span>Design Lead: </span><a href="https://profiles.wordpress.org/richtabor/"><span>Rich Tabor</span></a><br /><span>Default Theme Co-Leads: </span><a href="https://profiles.wordpress.org/beafialho/"><span>Beatriz Fialho</span></a><span> &amp; </span><a href="https://profiles.wordpress.org/mikachan/"><span>Sarah Norris</span></a></p>



<blockquote class="wp-block-quote">
<p>Thank you to all the contributors who dedicated time and energy to bring the best WordPress experience to everyone.</p>
<cite>Josepha Haden Chomphosy</cite></blockquote>



<p></p>



<pre class="wp-block-code"><code class=""><p class="is-style-wporg-props-long alignfull"><a href="https://profiles.wordpress.org/10upsimon/">10upsimon</a> · <a href="https://profiles.wordpress.org/1naveengiri/">1naveengiri</a> · <a href="https://profiles.wordpress.org/aaroncampbell/">Aaron D. Campbell</a> · <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a> · <a href="https://profiles.wordpress.org/aaronrobertshaw/">Aaron Robertshaw</a> · <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a> · <a href="https://profiles.wordpress.org/hurayraiit/">Abu Hurayra</a> · <a href="https://profiles.wordpress.org/bosconiandynamics/">Adam Bosco</a> · <a href="https://profiles.wordpress.org/adampickering/">Adam Pickering</a> · <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a> · <a href="https://profiles.wordpress.org/admwgn/">Adam Wiltgen</a> · <a href="https://profiles.wordpress.org/zieladam/">Adam Zielinski</a> · <a href="https://profiles.wordpress.org/addiestavlo/">Addie</a> · <a href="https://profiles.wordpress.org/oztaser/">Adil &#214;ztaşer</a> · <a href="https://profiles.wordpress.org/aduth/">aduth</a> · <a href="https://profiles.wordpress.org/aezazshekh/">Aezaz Shekh</a> · <a href="https://profiles.wordpress.org/afrid1719/">afrid1719</a> · <a href="https://profiles.wordpress.org/chaion07/">Ahmed Chaion</a> · <a href="https://profiles.wordpress.org/engahmeds3ed/">Ahmed Saeed</a> · <a href="https://profiles.wordpress.org/seakashdiu/">Akash Mia</a> · <a href="https://profiles.wordpress.org/wildworks/">Aki Hamano</a> · <a href="https://profiles.wordpress.org/kamig478/">Akram ul haq</a> · <a href="https://profiles.wordpress.org/akshitsethi/">Akshit Sethi</a> · <a href="https://profiles.wordpress.org/schlessera/">Alain Schlesser</a> · <a href="https://profiles.wordpress.org/alamgircsebd/">alamgircsebd</a> · <a href="https://profiles.wordpress.org/alanp57/">AlanP57</a> · <a href="https://profiles.wordpress.org/alansyue/">alansyue</a> · <a href="https://profiles.wordpress.org/aljullu/">Albert Juh&#233; Lluveras</a> · <a href="https://profiles.wordpress.org/alberuni-azad/">Alberuni Azad.</a> · <a href="https://profiles.wordpress.org/elpanda13gmailcom/">Alejandro J. Sanchez P.</a> · <a href="https://profiles.wordpress.org/zutigrm/">Aleksej</a> · <a href="https://profiles.wordpress.org/xknown/">Alex Concha</a> · <a href="https://profiles.wordpress.org/ajlende/">Alex Lende</a> · <a href="https://profiles.wordpress.org/viper007bond/">Alex Mills</a> · <a href="https://profiles.wordpress.org/acoulombe/">Alexis Coulombe</a> · <a href="https://profiles.wordpress.org/alexstine/">alexstine</a> · <a href="https://profiles.wordpress.org/allancole/">allancole</a> · <a href="https://profiles.wordpress.org/allisonplus/">allisonplus</a> · <a href="https://profiles.wordpress.org/mrfoxtalbot/">Alvaro G&#243;mez</a> · <a href="https://profiles.wordpress.org/amirkamizi/">amirkamizi</a> · <a href="https://profiles.wordpress.org/amjadr360/">Amjad Ali</a> · <a href="https://profiles.wordpress.org/anantajitjg/">Anantajit JG</a> · <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a> · <a href="https://profiles.wordpress.org/deksar/">Andreas</a> · <a href="https://profiles.wordpress.org/andraganescu/">Andrei Draganescu</a> · <a href="https://profiles.wordpress.org/_smartik_/">Andrei Surdu</a> · <a href="https://profiles.wordpress.org/nacin/">Andrew Nacin</a> · <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a> · <a href="https://profiles.wordpress.org/andrewserong/">Andrew Serong</a> · <a href="https://profiles.wordpress.org/eatingrules/">Andrew Wilder</a> · <a href="https://profiles.wordpress.org/andrewnz/">AndrewNZ</a> · <a href="https://profiles.wordpress.org/rarst/">Andrey "Rarst" Savchenko</a> · <a href="https://profiles.wordpress.org/andrija/">Andrija Naglic</a> · <a href="https://profiles.wordpress.org/oandregal/">André</a> · <a href="https://profiles.wordpress.org/afragen/">Andy Fragen</a> · <a href="https://profiles.wordpress.org/andykeith/">Andy Keith</a> · <a href="https://profiles.wordpress.org/aniketpatel/">Aniket Patel</a> · <a href="https://profiles.wordpress.org/anitanenova/">anitanenova</a> · <a href="https://profiles.wordpress.org/ankit-k-gupta/">Ankit K Gupta</a> · <a href="https://profiles.wordpress.org/annabansaghi/">Anna Bansaghi</a> · <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a> · <a href="https://profiles.wordpress.org/alaca/">Ante Laca</a> · <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a> · <a href="https://profiles.wordpress.org/antonvlasenko/">Anton Vlasenko</a> · <a href="https://profiles.wordpress.org/apedog/">apedog</a> · <a href="https://profiles.wordpress.org/apokalyptik/">apokalyptik</a> · <a href="https://profiles.wordpress.org/arrasel403/">AR Rasel</a> · <a href="https://profiles.wordpress.org/arcangelini/">arcangelini</a> · <a href="https://profiles.wordpress.org/archon810/">archon810</a> · <a href="https://profiles.wordpress.org/aristath/">Ari Stathopoulos</a> · <a href="https://profiles.wordpress.org/yellyc/">Ariel Chinn</a> · <a href="https://profiles.wordpress.org/xylocone/">Arjun Singh</a> · <a href="https://profiles.wordpress.org/armondal/">Arnab Mondal</a> · <a href="https://profiles.wordpress.org/passoniate/">Arslan Kalwar</a> · <a href="https://profiles.wordpress.org/arturgrabo/">Artur Grabowski</a> · <a href="https://profiles.wordpress.org/ideag/">Arunas Liuiza</a> · <a href="https://profiles.wordpress.org/aspexi/">Aspexi</a> · <a href="https://profiles.wordpress.org/aurooba/">Aurooba Ahmed</a> · <a href="https://profiles.wordpress.org/filosofo/">Austin Matzko</a> · <a href="https://profiles.wordpress.org/ayeshrajans/">Ayesh Karunaratne</a> · <a href="https://profiles.wordpress.org/azurseisme/">azurseisme</a> · <a href="https://profiles.wordpress.org/baned/">BaneD</a> · <a href="https://profiles.wordpress.org/barneydavey/">barneydavey</a> · <a href="https://profiles.wordpress.org/bbobnis/">Bartosz Bobnis</a> · <a href="https://profiles.wordpress.org/beafialho/">Beatriz Fialho</a> · <a href="https://profiles.wordpress.org/scruffian/">Ben Dwyer</a> · <a href="https://profiles.wordpress.org/bengreeley/">Ben Greeley</a> · <a href="https://profiles.wordpress.org/utz119/">Benachi</a> · <a href="https://profiles.wordpress.org/benjgrolleau/">Benjamin Grolleau</a> · <a href="https://profiles.wordpress.org/benoitchantre/">Benoit Chantre</a> · <a href="https://profiles.wordpress.org/bernhard reiter/">Bernhard Reiter</a> · <a href="https://profiles.wordpress.org/bernhard-reiter/">Bernie Reiter</a> · <a href="https://profiles.wordpress.org/mxbclang/">Bethany Chobanian Lang</a> · <a href="https://profiles.wordpress.org/albatross10/">Bhavik Kalpesh</a> · <a href="https://profiles.wordpress.org/bhrugesh12/">Bhrugesh Bavishi</a> · <a href="https://profiles.wordpress.org/birgire/">Birgir Erlendsson (birgire)</a> · <a href="https://profiles.wordpress.org/bph/">Birgit Pauli-Haack</a> · <a href="https://profiles.wordpress.org/bjorn2404/">bjorn2404</a> · <a href="https://profiles.wordpress.org/boblindner/">Bob</a> · <a href="https://profiles.wordpress.org/bobbingwide/">bobbingwide</a> · <a href="https://profiles.wordpress.org/gitlost/">bonger</a> · <a href="https://profiles.wordpress.org/boonebgorges/">Boone Gorges</a> · <a href="https://profiles.wordpress.org/bjorsch/">Brad Jorsch</a> · <a href="https://profiles.wordpress.org/kraftbj/">Brandon Kraft</a> · <a href="https://profiles.wordpress.org/ironprogrammer/">Brian Alexander</a> · <a href="https://profiles.wordpress.org/bgardner/">Brian Gardner</a> · <a href="https://profiles.wordpress.org/cantuaria/">Bruno Cantuaria</a> · <a href="https://profiles.wordpress.org/ribaricplusplus/">Bruno Ribaric</a> · <a href="https://profiles.wordpress.org/burgiuk/">burgiuk</a> · <a href="https://profiles.wordpress.org/burhandodhy/">Burhan Nasir</a> · <a href="https://profiles.wordpress.org/bwbama/">bwbama</a> · <a href="https://profiles.wordpress.org/cadlec/">cadlec</a> · <a href="https://profiles.wordpress.org/cagsmith/">cagsmith</a> · <a href="https://profiles.wordpress.org/cbravobernal/">Carlos Bravo</a> · <a href="https://profiles.wordpress.org/carlosgprim/">Carlos Garcia Prim</a> · <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a> · <a href="https://profiles.wordpress.org/cavalierlife/">cavalierlife</a> · <a href="https://profiles.wordpress.org/cdbessig/">cdbessig</a> · <a href="https://profiles.wordpress.org/shireling/">Chad Chadbourne</a> · <a href="https://profiles.wordpress.org/nhuja/">Chandra M</a> · <a href="https://profiles.wordpress.org/critterverse/">Channing Ritter</a> · <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a> · <a href="https://profiles.wordpress.org/chintan1896/">Chintan hingrajiya</a> · <a href="https://profiles.wordpress.org/cbringmann/">Chloe Bringmann</a> · <a href="https://profiles.wordpress.org/chouby/">Chouby</a> · <a href="https://profiles.wordpress.org/chrisbudd1/">Chris Budd</a> · <a href="https://profiles.wordpress.org/chrishardie/">Chris Hardie</a> · <a href="https://profiles.wordpress.org/czarate/">Chris Zarate</a> · <a href="https://profiles.wordpress.org/chriscct7/">chriscct7</a> · <a href="https://profiles.wordpress.org/chrisguitarguy/">chrisguitarguy</a> · <a href="https://profiles.wordpress.org/cwbudde/">Christian-W. Budde</a> · <a href="https://profiles.wordpress.org/christinavoudouris/">Christina Voudouris</a> · <a href="https://profiles.wordpress.org/apermo/">Christoph Daum</a> · <a href="https://profiles.wordpress.org/cfinke/">Christopher Finke</a> · <a href="https://profiles.wordpress.org/ryno267/">Chuck Reynolds</a> · <a href="https://profiles.wordpress.org/chynnabenton/">chynnabenton</a> · <a href="https://profiles.wordpress.org/ckanderson22/">ckanderson22</a> · <a href="https://profiles.wordpress.org/claytoncollie/">Clayton Collie</a> · <a href="https://profiles.wordpress.org/design_dolphin/">CodePoet</a> · <a href="https://profiles.wordpress.org/codesdnc/">codesdnc</a> · <a href="https://profiles.wordpress.org/codewhy/">codewhy</a> · <a href="https://profiles.wordpress.org/costdev/">Colin Stewart</a> · <a href="https://profiles.wordpress.org/colonelphantom/">colonelphantom</a> · <a href="https://profiles.wordpress.org/cbirdsong/">Cory Birdsong</a> · <a href="https://profiles.wordpress.org/courane01/">Courtney Robertson</a> · <a href="https://profiles.wordpress.org/craigfrancis/">craigfrancis</a> · <a href="https://profiles.wordpress.org/crazycoders/">crazycoders</a> · <a href="https://profiles.wordpress.org/mitogh/">Crisoforo Gaspar</a> · <a href="https://profiles.wordpress.org/cu121/">Cupid Chakma</a> · <a href="https://profiles.wordpress.org/curdin/">Curdin Krummenacher</a> · <a href="https://profiles.wordpress.org/cyrillbolliger/">cyrillbolliger</a> · <a href="https://profiles.wordpress.org/dxd5001/">Daijiro Miyazawa</a> · <a href="https://profiles.wordpress.org/dainemawer/">dainemawer</a> · <a href="https://profiles.wordpress.org/daisyo/">Daisy Olsen</a> · <a href="https://profiles.wordpress.org/daledupreez/">Dale du Preez</a> · <a href="https://profiles.wordpress.org/colorful-tones/">Damon Cook</a> · <a href="https://profiles.wordpress.org/damonganto/">damonganto</a> · <a href="https://profiles.wordpress.org/danfarrow/">Dan Farrow</a> · <a href="https://profiles.wordpress.org/dansoschin/">Dan Soschin</a> · <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</a> · <a href="https://profiles.wordpress.org/danieliser/">Daniel Iser</a> · <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a> · <a href="https://profiles.wordpress.org/schutzsmith/">Daniel Schutzsmith</a> · <a href="https://profiles.wordpress.org/mte90/">Daniele Scasciafratte</a> · <a href="https://profiles.wordpress.org/darerodz/">darerodz</a> · <a href="https://profiles.wordpress.org/dariak/">Daria</a> · <a href="https://profiles.wordpress.org/dkotter/">Darin Kotter</a> · <a href="https://profiles.wordpress.org/darkog/">Darko G.</a> · <a href="https://profiles.wordpress.org/darkskipper/">darkskipper</a> · <a href="https://profiles.wordpress.org/uofaberdeendarren/">Darren Coutts</a> · <a href="https://profiles.wordpress.org/htdat/">Dat Hoang</a> · <a href="https://profiles.wordpress.org/datainterlock/">datainterlock</a> · <a href="https://profiles.wordpress.org/dhilditch/">Dave Hilditch</a> · <a href="https://profiles.wordpress.org/dave1010/">dave1010</a> · <a href="https://profiles.wordpress.org/davidanderson/">David Anderson</a> · <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a> · <a href="https://profiles.wordpress.org/davidbinda/">David Biňovec</a> · <a href="https://profiles.wordpress.org/dcowgill/">David C</a> · <a href="https://profiles.wordpress.org/dpcalhoun/">David Calhoun</a> · <a href="https://profiles.wordpress.org/desmith/">David E. Smith</a> · <a href="https://profiles.wordpress.org/dg12345/">David Goring</a> · <a href="https://profiles.wordpress.org/dgwyer/">David Gwyer</a> · <a href="https://profiles.wordpress.org/dlh/">David Herrera</a> · <a href="https://profiles.wordpress.org/daviedr/">David Rozando</a> · <a href="https://profiles.wordpress.org/get_dave/">David Smith</a> · <a href="https://profiles.wordpress.org/davidvongries/">David Vongries</a> · <a href="https://profiles.wordpress.org/daxelrod/">daxelrod</a> · <a href="https://profiles.wordpress.org/daymobrew/">daymobrew</a> · <a href="https://profiles.wordpress.org/dsas/">Dean Sas</a> · <a href="https://profiles.wordpress.org/deepakvijayan/">Deepak Vijayan</a> · <a href="https://profiles.wordpress.org/denis-de-bernardy/">Denis de Bernardy</a> · <a href="https://profiles.wordpress.org/dingo_d/">Denis Žoljom</a> · <a href="https://profiles.wordpress.org/denishua/">denishua</a> · <a href="https://profiles.wordpress.org/dennisatyoast/">Dennis Claassen</a> · <a href="https://profiles.wordpress.org/dmsnell/">Dennis Snell</a> · <a href="https://profiles.wordpress.org/derekblank/">derekblank</a> · <a href="https://profiles.wordpress.org/pcfreak30/">Derrick Hammer</a> · <a href="https://profiles.wordpress.org/dharm1025/">Dharmesh Patel</a> · <a href="https://profiles.wordpress.org/dhl/">dhl</a> · <a href="https://profiles.wordpress.org/dianeco/">Diane Co</a> · <a href="https://profiles.wordpress.org/dilipbheda/">Dilip Bheda</a> · <a href="https://profiles.wordpress.org/dingdang/">dingdang</a> · <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a> · <a href="https://profiles.wordpress.org/dipakparmar443/">Dipak Parmar</a> · <a href="https://profiles.wordpress.org/divyeshgodhani/">divyeshgodhani</a> · <a href="https://profiles.wordpress.org/ocean90/">Dominik Schilling</a> · <a href="https://profiles.wordpress.org/donmhico/">donmhico</a> · <a href="https://profiles.wordpress.org/dougwollison/">Doug Wollison</a> · <a href="https://profiles.wordpress.org/dougal/">Dougal Campbell</a> · <a href="https://profiles.wordpress.org/drewapicture/">Drew Jaynes</a> · <a href="https://profiles.wordpress.org/drivingralle/">Drivingralle</a> · <a href="https://profiles.wordpress.org/drzraf/">drzraf</a> · <a href="https://profiles.wordpress.org/dwainm/">Dwain Maralack</a> · <a href="https://profiles.wordpress.org/kucrut/">Dzikri Aziz</a> · <a href="https://profiles.wordpress.org/dovyp/">Dōvy Paukstys</a> · <a href="https://profiles.wordpress.org/eclev91/">eclev91</a> · <a href="https://profiles.wordpress.org/chopinbach/">Edwin Cromley</a> · <a href="https://profiles.wordpress.org/eedee/">eedee</a> · <a href="https://profiles.wordpress.org/ehtis/">Ehtisham S.</a> · <a href="https://profiles.wordpress.org/eliezerspp/">Eliezer Pe&#241;a</a> · <a href="https://profiles.wordpress.org/ellatrix/">Ella van Durpe</a> · <a href="https://profiles.wordpress.org/clarkeemily/">Emily Clarke</a> · <a href="https://profiles.wordpress.org/manooweb/">Emmanuel Hesry</a> · <a href="https://profiles.wordpress.org/lopo/">Enrico Battocchi</a> · <a href="https://profiles.wordpress.org/ethitter/">Erick Hitter</a> · <a href="https://profiles.wordpress.org/codekraft/">Erik</a> · <a href="https://profiles.wordpress.org/kebbet/">Erik Betshammar</a> · <a href="https://profiles.wordpress.org/estelaris/">estelaris</a> · <a href="https://profiles.wordpress.org/manuilov/">Eugene M</a> · <a href="https://profiles.wordpress.org/madpixels/">eugene.manuilov</a> · <a href="https://profiles.wordpress.org/eugenemanuilov/">Eugene.Manuilov</a> · <a href="https://profiles.wordpress.org/eherman24/">Evan Herman</a> · <a href="https://profiles.wordpress.org/aaemnnosttv/">Evan Mattson</a> · <a href="https://profiles.wordpress.org/circlecube/">Evan Mullins</a> · <a href="https://profiles.wordpress.org/fabiankaegy/">Fabian K&#228;gy</a> · <a href="https://profiles.wordpress.org/faisal03/">Faisal Alvi</a> · <a href="https://profiles.wordpress.org/faison/">Faison</a> · <a href="https://profiles.wordpress.org/felipeelia/">Felipe Elia</a> · <a href="https://profiles.wordpress.org/flixos90/">Felix Arntz</a> · <a href="https://profiles.wordpress.org/fellyph/">Fellyph Cintra</a> · <a href="https://profiles.wordpress.org/femkreations/">Femy Praseeth</a> · <a href="https://profiles.wordpress.org/florianbrinkmann/">Florian Brinkmann</a> · <a href="https://profiles.wordpress.org/fpodhorsky/">fpodhorsky</a> · <a href="https://profiles.wordpress.org/fcoveram/">Francisco</a> · <a href="https://profiles.wordpress.org/franz00/">franzaurus</a> · <a href="https://profiles.wordpress.org/fuadragib/">Fuad Ragib</a> · <a href="https://profiles.wordpress.org/furi3r/">furi3r</a> · <a href="https://profiles.wordpress.org/gabri3lmarques/">gabri3lmarques</a> · <a href="https://profiles.wordpress.org/gdetassigny/">Gabriel de Tassigny</a> · <a href="https://profiles.wordpress.org/gabertronic/">Gabriel Rose</a> · <a href="https://profiles.wordpress.org/gamecreature/">gamecreature</a> · <a href="https://profiles.wordpress.org/garrett-eclipse/">Garrett Hyder</a> · <a href="https://profiles.wordpress.org/voldemortensen/">Garth Mortensen</a> · <a href="https://profiles.wordpress.org/garyj/">Gary Jones</a> · <a href="https://profiles.wordpress.org/pento/">Gary Pendergast</a> · <a href="https://profiles.wordpress.org/garymatthews919/">garymatthews919</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/georgestephanis/">George Stephanis</a> · <a href="https://profiles.wordpress.org/geriux/">Gerardo Pacheco</a> · <a href="https://profiles.wordpress.org/gigitux/">gigitux</a> · <a href="https://profiles.wordpress.org/giox069/">giox069</a> · <a href="https://profiles.wordpress.org/gisgeo/">gisgeo</a> · <a href="https://profiles.wordpress.org/giuseppemazzapica/">giuseppemazzapica</a> · <a href="https://profiles.wordpress.org/glendaviesnz/">Glen Davies</a> · <a href="https://profiles.wordpress.org/goldenapples/">goldenapples</a> · <a href="https://profiles.wordpress.org/greglone/">Gr&#233;gory Viguier</a> · <a href="https://profiles.wordpress.org/graham73may/">graham73may</a> · <a href="https://profiles.wordpress.org/grantmkin/">Grant M. Kinney</a> · <a href="https://profiles.wordpress.org/gziolo/">Greg Ziółkowski</a> · <a href="https://profiles.wordpress.org/greg24/">greg24</a> · <a href="https://profiles.wordpress.org/gregorlove/">gRegor Morrill</a> · <a href="https://profiles.wordpress.org/gunterer/">gunterer</a> · <a href="https://profiles.wordpress.org/bordoni/">Gustavo Bordoni</a> · <a href="https://profiles.wordpress.org/gvgvgvijayan/">gvgvgvijayan</a> · <a href="https://profiles.wordpress.org/h2ham/">h2ham (Hiromu Hasegawa)</a> · <a href="https://profiles.wordpress.org/hakanca/">hakanca</a> · <a href="https://profiles.wordpress.org/hakre/">hakre</a> · <a href="https://profiles.wordpress.org/hansjovisyoast/">Hans-Christiaan Braun</a> · <a href="https://profiles.wordpress.org/thakkarhardik/">Hardik Thakkar</a> · <a href="https://profiles.wordpress.org/haritpanchal/">Harit Panchal</a> · <a href="https://profiles.wordpress.org/harshvaishnav/">harshvaishnav</a> · <a href="https://profiles.wordpress.org/hasanuzzamanshamim/">Hasanuzzaman</a> · <a href="https://profiles.wordpress.org/azhiyadev/">Hauwa Abashiya</a> · <a href="https://profiles.wordpress.org/helen/">Helen Hou-Sandi</a> · <a href="https://profiles.wordpress.org/iamarinoh/">Henrique Iamarino</a> · <a href="https://profiles.wordpress.org/henrywright/">Henry Wright</a> · <a href="https://profiles.wordpress.org/here/">here</a> · <a href="https://profiles.wordpress.org/herregroen/">Herre Groen</a> · <a href="https://profiles.wordpress.org/hilayt24/">Hilay Trivedi</a> · <a href="https://profiles.wordpress.org/hiren1094/">hiren sanja</a> · <a href="https://profiles.wordpress.org/hiyascout/">hiyascout</a> · <a href="https://profiles.wordpress.org/howdy_mcgee/">Howdy_McGee</a> · <a href="https://profiles.wordpress.org/hugodevos/">hugodevos</a> · <a href="https://profiles.wordpress.org/huubl/">huubl</a> · <a href="https://profiles.wordpress.org/hztyfoon/">hztyfoon</a> · <a href="https://profiles.wordpress.org/priethor/">Héctor Prieto</a> · <a href="https://profiles.wordpress.org/ianbelanger/">Ian Belanger</a> · <a href="https://profiles.wordpress.org/iandunn/">Ian Dunn</a> · <a href="https://profiles.wordpress.org/iansvo/">iansvo</a> · <a href="https://profiles.wordpress.org/icaspar/">iCaspar</a> · <a href="https://profiles.wordpress.org/igmoweb/">Ignacio Cruz Moreno</a> · <a href="https://profiles.wordpress.org/igorsch/">Igor</a> · <a href="https://profiles.wordpress.org/igrigorik/">igrigorik</a> · <a href="https://profiles.wordpress.org/ilovecats7/">ilovecats7</a> · <a href="https://profiles.wordpress.org/ilunabar/">ilunabar</a> · <a href="https://profiles.wordpress.org/imadarshakshat/">imadarshakshat</a> · <a href="https://profiles.wordpress.org/innovext/">Innovext</a> · <a href="https://profiles.wordpress.org/ipajen/">ipajen</a> · <a href="https://profiles.wordpress.org/ipstenu/">Ipstenu (Mika Epstein)</a> · <a href="https://profiles.wordpress.org/irecinius/">irecinius</a> · <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a> · <a href="https://profiles.wordpress.org/iulia-cazan/">Iulia Cazan</a> · <a href="https://profiles.wordpress.org/ivanjeronimo/">ivanjeronimo</a> · <a href="https://profiles.wordpress.org/iviweb/">iviweb</a> · <a href="https://profiles.wordpress.org/jdgrimes/">J.D. Grimes</a> · <a href="https://profiles.wordpress.org/primetimejas/">Jacob Schweitzer</a> · <a href="https://profiles.wordpress.org/jakariaistauk/">Jakaria Istauk</a> · <a href="https://profiles.wordpress.org/outrankjames/">James</a> · <a href="https://profiles.wordpress.org/jameskoster/">James Koster</a> · <a href="https://profiles.wordpress.org/jamesckemp/">jamesckemp</a> · <a href="https://profiles.wordpress.org/jamieburchell/">jamieburchell</a> · <a href="https://profiles.wordpress.org/janthiel/">Jan Thiel</a> · <a href="https://profiles.wordpress.org/jarretc/">Jarret</a> · <a href="https://profiles.wordpress.org/jsnjohnston/">Jason Johnston</a> · <a href="https://profiles.wordpress.org/trapsta/">Jasper Kinoti</a> · <a href="https://profiles.wordpress.org/javiarce/">Javier Arce</a> · <a href="https://profiles.wordpress.org/carazo/">Javier Carazo</a> · <a href="https://profiles.wordpress.org/javiercasares/">Javier Casares</a> · <a href="https://profiles.wordpress.org/grandeljay/">Jay Trees</a> · <a href="https://profiles.wordpress.org/jchambo/">jchambo</a> · <a href="https://profiles.wordpress.org/audrasjb/">Jean-Baptiste Audras</a> · <a href="https://profiles.wordpress.org/jeawhanlee/">jeawhanlee</a> · <a href="https://profiles.wordpress.org/jffng/">Jeff Ong</a> · <a href="https://profiles.wordpress.org/jeffpaul/">Jeff Paul</a> · <a href="https://profiles.wordpress.org/juberstine/">Jeff Uberstine</a> · <a href="https://profiles.wordpress.org/jeremyfelt/">Jeremy Felt</a> · <a href="https://profiles.wordpress.org/jeherve/">Jeremy Herve</a> · <a href="https://profiles.wordpress.org/jeroenreumkens/">JeroenReumkens</a> · <a href="https://profiles.wordpress.org/luminuu/">Jessica Lyschik</a> · <a href="https://profiles.wordpress.org/jhart35/">jhart35</a> · <a href="https://profiles.wordpress.org/jhnstn/">jhnstn</a> · <a href="https://profiles.wordpress.org/jigar-bhanushali/">jigar bhanushali</a> · <a href="https://profiles.wordpress.org/jnz31/">jnz31</a> · <a href="https://profiles.wordpress.org/joedolson/">Joe Dolson</a> · <a href="https://profiles.wordpress.org/joehoyle/">Joe Hoyle</a> · <a href="https://profiles.wordpress.org/joemcgill/">Joe McGill</a> · <a href="https://profiles.wordpress.org/joelhardi/">joelhardi</a> · <a href="https://profiles.wordpress.org/joelmadigan/">joelmadigan</a> · <a href="https://profiles.wordpress.org/joen/">Joen Asmussen</a> · <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a> · <a href="https://profiles.wordpress.org/johnjamesjacoby/">John James Jacoby</a> · <a href="https://profiles.wordpress.org/johnregan3/">John Regan</a> · <a href="https://profiles.wordpress.org/johnwatkins0/">John Watkins</a> · <a href="https://profiles.wordpress.org/johnmark8080/">johnmark8080</a> · <a href="https://profiles.wordpress.org/jb510/">Jon Brown</a> · <a href="https://profiles.wordpress.org/jonsurrell/">Jon Surrell</a> · <a href="https://profiles.wordpress.org/psykro/">Jonathan Bossenger</a> · <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a> · <a href="https://profiles.wordpress.org/jpantani/">Jonathan Pantani</a> · <a href="https://profiles.wordpress.org/jonmackintosh/">jonmackintosh</a> · <a href="https://profiles.wordpress.org/spacedmonkey/">Jonny Harris</a> · <a href="https://profiles.wordpress.org/jonny-s/">jonny-s</a> · <a href="https://profiles.wordpress.org/jonoaldersonwp/">Jono Alderson</a> · <a href="https://profiles.wordpress.org/joostdevalk/">Joost de Valk</a> · <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a> · <a href="https://profiles.wordpress.org/josvelasco/">Jos Velasco</a> · <a href="https://profiles.wordpress.org/joegrainger/">Joseph Grainger</a> · <a href="https://profiles.wordpress.org/jostnes/">Josepha Dambul</a> · <a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden</a> · <a href="https://profiles.wordpress.org/jhabdas/">Josh Habdas</a> · <a href="https://profiles.wordpress.org/joshuaabenazer/">Joshua Abenazer</a> · <a href="https://profiles.wordpress.org/joyously/">Joy</a> · <a href="https://profiles.wordpress.org/jrbeilke/">jrbeilke</a> · <a href="https://profiles.wordpress.org/jsh4/">jsh4</a> · <a href="https://profiles.wordpress.org/jsnajdr/">jsnajdr</a> · <a href="https://profiles.wordpress.org/juhise/">Juhi Saxena</a> · <a href="https://profiles.wordpress.org/juliemoynat/">Julie Moynat</a> · <a href="https://profiles.wordpress.org/jrf/">Juliette Reinders Folmer</a> · <a href="https://profiles.wordpress.org/juliobox/">Julio Potier</a> · <a href="https://profiles.wordpress.org/just0nequestion/">just0nequestion</a> · <a href="https://profiles.wordpress.org/justinahinon/">Justin Ahinon</a> · <a href="https://profiles.wordpress.org/justinsainton/">Justin Sainton</a> · <a href="https://profiles.wordpress.org/greenshady/">Justin Tadlock</a> · <a href="https://profiles.wordpress.org/welenofsky/">Justin Welenofsky</a> · <a href="https://profiles.wordpress.org/jyolsna/">jyolsna</a> · <a href="https://profiles.wordpress.org/kadamwhite/">K. Adam White</a> · <a href="https://profiles.wordpress.org/kacper3355/">kacper3355</a> · <a href="https://profiles.wordpress.org/kafleg/">KafleG</a> · <a href="https://profiles.wordpress.org/kevin940726/">Kai Hao</a> · <a href="https://profiles.wordpress.org/kajalgohel/">Kajal Gohel</a> · <a href="https://profiles.wordpress.org/akabarikalpesh/">Kalpesh Akabari</a> · <a href="https://profiles.wordpress.org/kapilpaul/">Kapil Paul</a> · <a href="https://profiles.wordpress.org/karinclimber/">Kari Anderson</a> · <a href="https://profiles.wordpress.org/karlgroves/">karlgroves</a> · <a href="https://profiles.wordpress.org/karlijnbk/">Karlijn Bok</a> · <a href="https://profiles.wordpress.org/kasparsd/">Kaspars</a> · <a href="https://profiles.wordpress.org/zoonini/">Kathryn Presner</a> · <a href="https://profiles.wordpress.org/kbrownkd/">kbrownkd</a> · <a href="https://profiles.wordpress.org/kkoppenhaver/">Keanan Koppenhaver</a> · <a href="https://profiles.wordpress.org/ryelle/">Kelly Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/kellychoffman/">Kelly Hoffman</a> · <a href="https://profiles.wordpress.org/kevinb/">Kevin Behrens</a> · <a href="https://profiles.wordpress.org/khag7/">Kevin Hagerty</a> · <a href="https://profiles.wordpress.org/khoipro/">Khoi Pro</a> · <a href="https://profiles.wordpress.org/khokansardar/">Khokan Sardar</a> · <a href="https://profiles.wordpress.org/killua99/">killua99</a> · <a href="https://profiles.wordpress.org/kishanjasani/">Kishan Jasani</a> · <a href="https://profiles.wordpress.org/kitchin/">kitchin</a> · <a href="https://profiles.wordpress.org/kjellr/">Kjell Reigstad</a> · <a href="https://profiles.wordpress.org/kkmuffme/">kkmuffme</a> · <a href="https://profiles.wordpress.org/blackawxs/">klewis</a> · <a href="https://profiles.wordpress.org/knutsp/">Knut Sparhell</a> · <a href="https://profiles.wordpress.org/vdwijngaert/">Koen Van den Wijngaert</a> · <a href="https://profiles.wordpress.org/konradyoast/">Konrad.K</a> · <a href="https://profiles.wordpress.org/kovshenin/">Konstantin Kovshenin</a> · <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a> · <a href="https://profiles.wordpress.org/konyoldeath/">konyoldeath</a> · <a href="https://profiles.wordpress.org/kanlukasz/">Kris Kelvin</a> · <a href="https://profiles.wordpress.org/krishaweb/">KrishaWeb</a> · <a href="https://profiles.wordpress.org/krupalpanchal/">Krupal Panchal</a> · <a href="https://profiles.wordpress.org/kmadhak/">Kunal Madhak</a> · <a href="https://profiles.wordpress.org/kurtpayne/">Kurt Payne</a> · <a href="https://profiles.wordpress.org/kwillmorth/">kwillmorth</a> · <a href="https://profiles.wordpress.org/kbjohnson90/">Kyle B. Johnson</a> · <a href="https://profiles.wordpress.org/devnel/">Kyle Nel</a> · <a href="https://profiles.wordpress.org/larsmqller/">larsmqller</a> · <a href="https://profiles.wordpress.org/laurelfulford/">laurelfulford</a> · <a href="https://profiles.wordpress.org/laurlittle/">Lauren Stein</a> · <a href="https://profiles.wordpress.org/laurent22777/">laurent22777</a> · <a href="https://profiles.wordpress.org/lazam786/">lazam786</a> · <a href="https://profiles.wordpress.org/leewillis77/">Lee Willis</a> · <a href="https://profiles.wordpress.org/leemon/">leemon</a> · <a href="https://profiles.wordpress.org/0mirka00/">Lena Morita</a> · <a href="https://profiles.wordpress.org/leonidasmilossis/">Leo Milo</a> · <a href="https://profiles.wordpress.org/leogermani/">leogermani</a> · <a href="https://profiles.wordpress.org/rudlinkon/">Linkon Miyan</a> · <a href="https://profiles.wordpress.org/linsoftware/">Linnea Huxford</a> · <a href="https://profiles.wordpress.org/lonnylot/">lonnylot</a> · <a href="https://profiles.wordpress.org/thelovekesh/">Lovekesh Kumar</a> · <a href="https://profiles.wordpress.org/lovor/">Lovro Hrust</a> · <a href="https://profiles.wordpress.org/lozula/">lozula</a> · <a href="https://profiles.wordpress.org/lucasbustamante/">Lucas Bustamante</a> · <a href="https://profiles.wordpress.org/lucilastancato/">lucilastancato</a> · <a href="https://profiles.wordpress.org/luigipulcini/">luigipulcini</a> · <a href="https://profiles.wordpress.org/zaguiini/">Luis Felipe Zaguini</a> · <a href="https://profiles.wordpress.org/luisherranz/">luisherranz</a> · <a href="https://profiles.wordpress.org/infolu/">Luiz Ara&#250;jo</a> · <a href="https://profiles.wordpress.org/mitweka/">Lukas Niebler</a> · <a href="https://profiles.wordpress.org/lukecavanagh/">Luke Cavanagh</a> · <a href="https://profiles.wordpress.org/msnewas/">M S Newaz</a> · <a href="https://profiles.wordpress.org/maartenj/">Maarten</a> · <a href="https://profiles.wordpress.org/mashikag/">Maciej</a> · <a href="https://profiles.wordpress.org/maciejmackowiak/">maciejmackowiak</a> · <a href="https://profiles.wordpress.org/madhudollu/">Madhu Dollu</a> · <a href="https://profiles.wordpress.org/mrdollu/">Madhu Dollu</a> · <a href="https://profiles.wordpress.org/onemaggie/">Maggie Cabrera</a> · <a href="https://profiles.wordpress.org/maahrokh/">Mahrokh</a> · <a href="https://profiles.wordpress.org/maksimkuzmin/">maksimkuzmin</a> · <a href="https://profiles.wordpress.org/malthert/">malthert</a> · <a href="https://profiles.wordpress.org/manfcarlo/">manfcarlo</a> · <a href="https://profiles.wordpress.org/manishsongirkar36/">Manish Songirkar</a> · <a href="https://profiles.wordpress.org/manzoorwanijk/">Manzoor Wani</a> · <a href="https://profiles.wordpress.org/manzurahammed/">Manzur Ahammed</a> · <a href="https://profiles.wordpress.org/marcyoast/">Marc</a> · <a href="https://profiles.wordpress.org/fullofcaffeine/">Marcelo de Moraes Serpa</a> · <a href="https://profiles.wordpress.org/mciampini/">Marco Ciampini</a> · <a href="https://profiles.wordpress.org/mkaz/">Marcus Kazmierczak</a> · <a href="https://profiles.wordpress.org/marekdedic/">Marek Dědič</a> · <a href="https://profiles.wordpress.org/nuryko/">Marianna</a> · <a href="https://profiles.wordpress.org/chaton666/">Marie Comet</a> · <a href="https://profiles.wordpress.org/tyxla/">Marin Atanasov</a> · <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a> · <a href="https://profiles.wordpress.org/markbiek/">Mark Biek</a> · <a href="https://profiles.wordpress.org/markhowellsmead/">Mark Howells-Mead</a> · <a href="https://profiles.wordpress.org/markjaquith/">Mark Jaquith</a> · <a href="https://profiles.wordpress.org/markparnell/">Mark Parnell</a> · <a href="https://profiles.wordpress.org/markoheijnen/">Marko Heijnen</a> · <a href="https://profiles.wordpress.org/flootr/">Markus</a> · <a href="https://profiles.wordpress.org/mkox/">Markus Kosmal</a> · <a href="https://profiles.wordpress.org/mhkuu/">Martijn van der Klis</a> · <a href="https://profiles.wordpress.org/hinjiriyo/">Martin Stehle</a> · <a href="https://profiles.wordpress.org/martinkrcho/">martin.krcho</a> · <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a> · <a href="https://profiles.wordpress.org/mashukushibiki/">Mashu</a> · <a href="https://profiles.wordpress.org/masteradhoc/">masteradhoc</a> · <a href="https://profiles.wordpress.org/msurdi/">Mat&#237;as Emanuel Surdi</a> · <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a> · <a href="https://profiles.wordpress.org/mmaattiiaass/">matiasbenedetto</a> · <a href="https://profiles.wordpress.org/mattchowning/">Matt Chowning</a> · <a href="https://profiles.wordpress.org/mattkeys/">Matt Keys</a> · <a href="https://profiles.wordpress.org/matt/">Matt Mullenweg</a> · <a href="https://profiles.wordpress.org/mattwondra/">Matt Wondra</a> · <a href="https://profiles.wordpress.org/mboynes/">Matthew Boynes</a> · <a href="https://profiles.wordpress.org/mattheweppelsheimer/">Matthew Eppelsheimer</a> · <a href="https://profiles.wordpress.org/matthiaspabst/">Matthias Pabst</a> · <a href="https://profiles.wordpress.org/matthiasreinholz/">Matthias Reinholz</a> · <a href="https://profiles.wordpress.org/mattyrob/">mattyrob</a> · <a href="https://profiles.wordpress.org/azouamauriac/">Mauriac AZOUA</a> · <a href="https://profiles.wordpress.org/maximej/">Maxime J.</a> · <a href="https://profiles.wordpress.org/maximemeganck/">Maxime Meganck</a> · <a href="https://profiles.wordpress.org/mayankmajeji/">Mayank Majeji</a> · <a href="https://profiles.wordpress.org/maythamalsudany/">maythamalsudany</a> · <a href="https://profiles.wordpress.org/mayuge/">Mayuge</a> · <a href="https://profiles.wordpress.org/mcliwanow/">mcliwanow</a> · <a href="https://profiles.wordpress.org/rakibwordpress/">Md Rakib Hossain</a> · <a href="https://profiles.wordpress.org/russel07/">Md. Russel Hussain</a> · <a href="https://profiles.wordpress.org/mdrago/">mdrago</a> · <a href="https://profiles.wordpress.org/mehedi890/">Mehedi Foysal</a> · <a href="https://profiles.wordpress.org/meher/">Meher Bala</a> · <a href="https://profiles.wordpress.org/mehulkaklotar/">Mehul Kaklotar</a> · <a href="https://profiles.wordpress.org/melchoyce/">Mel Choyce-Dwan</a> · <a href="https://profiles.wordpress.org/meloniq/">meloniq</a> · <a href="https://profiles.wordpress.org/merkys/">Merkys Maliukevičius</a> · <a href="https://profiles.wordpress.org/meysamnorouzi/">meysam norouzi</a> · <a href="https://profiles.wordpress.org/mfgmicha/">Micha Krapp</a> · <a href="https://profiles.wordpress.org/michaelbourne/">Michael Bourne</a> · <a href="https://profiles.wordpress.org/mburridge/">Michael Burridge</a> · <a href="https://profiles.wordpress.org/czapla/">Michal Czaplinski</a> · <a href="https://profiles.wordpress.org/miguelaxcar/">Miguel Axcar</a> · <a href="https://profiles.wordpress.org/mcsf/">Miguel Fonseca</a> · <a href="https://profiles.wordpress.org/mihaidumitrascu/">Mihai Dumitrascu</a> · <a href="https://profiles.wordpress.org/mihai2u/">Mike Crantea</a> · <a href="https://profiles.wordpress.org/mdgl/">Mike Glendinning</a> · <a href="https://profiles.wordpress.org/mikehansenme/">Mike Hansen</a> · <a href="https://profiles.wordpress.org/mikejolley/">Mike Jolley (a11n)</a> · <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a> · <a href="https://profiles.wordpress.org/mikemanzo/">mikemanzo</a> · <a href="https://profiles.wordpress.org/milana_cap/">Milana Cap</a> · <a href="https://profiles.wordpress.org/milindmore22/">Milind More</a> · <a href="https://profiles.wordpress.org/mimitips/">mimi</a> · <a href="https://profiles.wordpress.org/multidots1896/">Minal Diwan</a> · <a href="https://profiles.wordpress.org/presents111/">miya</a> · <a href="https://profiles.wordpress.org/mlajo/">Mladen</a> · <a href="https://profiles.wordpress.org/batmoo/">Mohammad Jangda</a> · <a href="https://profiles.wordpress.org/mjkhajeh/">MohammadJafar Khajeh</a> · <a href="https://profiles.wordpress.org/mohitdadhich10/">Mohit Dadhich</a> · <a href="https://profiles.wordpress.org/boemedia/">Monique Dubbelman</a> · <a href="https://profiles.wordpress.org/mt8biz/">moto hachi</a> · <a href="https://profiles.wordpress.org/mreishus/">mreishus</a> · <a href="https://profiles.wordpress.org/mrobit/">mrobit</a> · <a href="https://profiles.wordpress.org/msolution/">msolution</a> · <a href="https://profiles.wordpress.org/mtias/">mtias</a> · <a href="https://profiles.wordpress.org/wparslan/">Muhammad Arslan</a> · <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a> · <a href="https://profiles.wordpress.org/mmaumio/">Muntasir Mahmud</a> · <a href="https://profiles.wordpress.org/amustaque97/">Mustaque Ahmed</a> · <a href="https://profiles.wordpress.org/mvraghavan/">mvraghavan</a> · <a href="https://profiles.wordpress.org/mw108/">mw108</a> · <a href="https://profiles.wordpress.org/mweichert/">mweichert</a> · <a href="https://profiles.wordpress.org/n8finch/">n8finch</a> · <a href="https://profiles.wordpress.org/tushar284/">Nahid Hasan</a> · <a href="https://profiles.wordpress.org/nalininonstopnewsuk/">Nalini Thakor</a> · <a href="https://profiles.wordpress.org/namithjawahar/">Namith Jawahar</a> · <a href="https://profiles.wordpress.org/nareshbheda/">Naresh Bheda</a> · <a href="https://profiles.wordpress.org/nateallen/">Nate Allen</a> · <a href="https://profiles.wordpress.org/nhadsall/">Nathan</a> · <a href="https://profiles.wordpress.org/nathanatmoz/">Nathan Johnson</a> · <a href="https://profiles.wordpress.org/navigatrum/">navigatrum</a> · <a href="https://profiles.wordpress.org/neffff/">neffff</a> · <a href="https://profiles.wordpress.org/nendeb55/">nendeb</a> · <a href="https://profiles.wordpress.org/neychok/">Neycho Kalaydzhiev</a> · <a href="https://profiles.wordpress.org/eidolonnight/">Nicholas Garofalo</a> · <a href="https://profiles.wordpress.org/ndiego/">Nick Diego</a> · <a href="https://profiles.wordpress.org/celloexpressions/">Nick Halsey</a> · <a href="https://profiles.wordpress.org/nico23/">Nico</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/nikkigagency/">nikkigagency</a> · <a href="https://profiles.wordpress.org/im_niloy/">Niloy</a> · <a href="https://profiles.wordpress.org/ninos-ego/">Ninos</a> · <a href="https://profiles.wordpress.org/nithi22/">Nithin John</a> · <a href="https://profiles.wordpress.org/nithins53/">Nithin SreeRaj</a> · <a href="https://profiles.wordpress.org/nlpro/">nlpro</a> · <a href="https://profiles.wordpress.org/noahtallen/">Noah Allen</a> · <a href="https://profiles.wordpress.org/noplanman/">noplanman</a> · <a href="https://profiles.wordpress.org/nouarah/">nouarah</a> · <a href="https://profiles.wordpress.org/numidwasnotavailable/">NumidWasNotAvailable</a> · <a href="https://profiles.wordpress.org/nunomorgadinho/">nunomorgadinho</a> · <a href="https://profiles.wordpress.org/zikubd/">Nurul Umbhiya</a> · <a href="https://profiles.wordpress.org/nuvopoint/">nuvoPoint</a> · <a href="https://profiles.wordpress.org/nvartolomei/">nvartolomei</a> · <a href="https://profiles.wordpress.org/oakesjosh/">oakesjosh</a> · <a href="https://profiles.wordpress.org/obayedmamur/">Obayed Mamur</a> · <a href="https://profiles.wordpress.org/obliviousharmony/">obliviousharmony</a> · <a href="https://profiles.wordpress.org/ockham/">ockham</a> · <a href="https://profiles.wordpress.org/oguzkocer/">oguzkocer</a> · <a href="https://profiles.wordpress.org/oglekler/">Olga Gleckler</a> · <a href="https://profiles.wordpress.org/oliverstapelfeldt/">Oliver Stapelfeldt</a> · <a href="https://profiles.wordpress.org/olliejones/">OllieJones</a> · <a href="https://profiles.wordpress.org/oneearth27/">oneearth27</a> · <a href="https://profiles.wordpress.org/onnimonni/">Onni Hakala</a> · <a href="https://profiles.wordpress.org/opr18/">opr18</a> · <a href="https://profiles.wordpress.org/ovidiul/">ovidiul</a> · <a href="https://profiles.wordpress.org/p_enrique/">p_enrique</a> · <a href="https://profiles.wordpress.org/paaljoachim/">Paal Joachim Romdahl</a> · <a href="https://profiles.wordpress.org/poliuk/">Pablo Postigo</a> · <a href="https://profiles.wordpress.org/pablohoney/">PabloHoney</a> · <a href="https://profiles.wordpress.org/palmiak/">palmiak</a> · <a href="https://profiles.wordpress.org/pls78/">Paolo L. Scala</a> · <a href="https://profiles.wordpress.org/paragoninitiativeenterprises/">Paragon Initiative Enterprises</a> · <a href="https://profiles.wordpress.org/xparham/">Parham Ghaffarian</a> · <a href="https://profiles.wordpress.org/swissspidy/">Pascal Birchler</a> · <a href="https://profiles.wordpress.org/patrickgroot/">Patrick Groot</a> · <a href="https://profiles.wordpress.org/pbearne/">Paul Bearne</a> · <a href="https://profiles.wordpress.org/pbiron/">Paul Biron</a> · <a href="https://profiles.wordpress.org/paulkevan/">Paul Kevan</a> · <a href="https://profiles.wordpress.org/figureone/">Paul Ryan</a> · <a href="https://profiles.wordpress.org/paulohcruz/">Paulo Cruz</a> · <a href="https://profiles.wordpress.org/paulopmt1/">Paulo Trentin</a> · <a href="https://profiles.wordpress.org/pavanpatil1/">Pavan Patil</a> · <a href="https://profiles.wordpress.org/pavelschoffer/">pavelschoffer</a> · <a href="https://profiles.wordpress.org/pbking/">pbking</a> · <a href="https://profiles.wordpress.org/pedromendonca/">Pedro Mendon&#231;a</a> · <a href="https://profiles.wordpress.org/westi/">Peter Westwood</a> · <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a> · <a href="https://profiles.wordpress.org/petitphp/">petitphp</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/phillsav/">Phill</a> · <a href="https://profiles.wordpress.org/strategio/">Pierre Sylvestre</a> · <a href="https://profiles.wordpress.org/nekojonez/">Pieterjan Deneys</a> · <a href="https://profiles.wordpress.org/boniu91/">Piotrek Boniu</a> · <a href="https://profiles.wordpress.org/mordauk/">Pippin Williamson</a> · <a href="https://profiles.wordpress.org/pkolenbr/">pkolenbr</a> · <a href="https://profiles.wordpress.org/webtechpooja/">Pooja Derashri</a> · <a href="https://profiles.wordpress.org/pooja1210/">Pooja N Muchandikar</a> · <a href="https://profiles.wordpress.org/praful2111/">Praful Patel</a> · <a href="https://profiles.wordpress.org/pratiweb/">Pratiksha</a> · <a href="https://profiles.wordpress.org/nikeo/">presscustomizr</a> · <a href="https://profiles.wordpress.org/presskopp/">Presskopp</a> · <a href="https://profiles.wordpress.org/presstoke/">presstoke</a> · <a href="https://profiles.wordpress.org/priyomukul/">Priyo Mukul</a> · <a href="https://profiles.wordpress.org/prokium/">prokium</a> · <a href="https://profiles.wordpress.org/pypwalters/">pypwalters</a> · <a href="https://profiles.wordpress.org/itsjonq/">Q</a> · <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a> · <a href="https://profiles.wordpress.org/larrach/">Rachel Peter</a> · <a href="https://profiles.wordpress.org/raduiason/">raduiason</a> · <a href="https://profiles.wordpress.org/rafiahmedd/">Rafi Ahmed</a> · <a href="https://profiles.wordpress.org/tan007/">Rahi Prajapati</a> · <a href="https://profiles.wordpress.org/rajanpanchal2028/">Rajan Panchal</a> · <a href="https://profiles.wordpress.org/rajeshraval786/">Rajesh Raval</a> · <a href="https://profiles.wordpress.org/ralucastn/">ralucastn</a> · <a href="https://profiles.wordpress.org/superpoincare/">Ramanan</a> · <a href="https://profiles.wordpress.org/rahmohn/">Ramon Ahnert</a> · <a href="https://profiles.wordpress.org/rcorrales/">Ramon Corrales</a> · <a href="https://profiles.wordpress.org/ramon-fincken/">ramon fincken</a> · <a href="https://profiles.wordpress.org/ramonopoly/">Ramon James</a> · <a href="https://profiles.wordpress.org/randhirexpresstech/">Randhir Jha</a> · <a href="https://profiles.wordpress.org/ravipatel/">Ravikumar Patel</a> · <a href="https://profiles.wordpress.org/rcanepa/">rcanepa</a> · <a href="https://profiles.wordpress.org/rebasaurus/">rebasaurus</a> · <a href="https://profiles.wordpress.org/rehanali/">Rehan Ali</a> · <a href="https://profiles.wordpress.org/tabrisrp/">Remy Perona</a> · <a href="https://profiles.wordpress.org/renathoc/">Renatho (a11n)</a> · <a href="https://profiles.wordpress.org/renegeuze/">renegeuze</a> · <a href="https://profiles.wordpress.org/laboiteare/">Reuhno</a> · <a href="https://profiles.wordpress.org/rflw/">rflw</a> · <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a> · <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a> · <a href="https://profiles.wordpress.org/rinatkhaziev/">Rinat</a> · <a href="https://profiles.wordpress.org/rinkychowdhury9/">Rinky Chowdhury</a> · <a href="https://profiles.wordpress.org/rishishah/">Rishi Shah</a> · <a href="https://profiles.wordpress.org/rjasdfiii/">rjasdfiii</a> · <a href="https://profiles.wordpress.org/rkaiser0324/">rkaiser0324</a> · <a href="https://profiles.wordpress.org/noisysocks/">Robert Anderson</a> · <a href="https://profiles.wordpress.org/miqrogroove/">Robert Chapin</a> · <a href="https://profiles.wordpress.org/robertghetau/">robertght</a> · <a href="https://profiles.wordpress.org/robinwpdeveloper/">Robin</a> · <a href="https://profiles.wordpress.org/robmiller/">robmiller</a> · <a href="https://profiles.wordpress.org/rodricus/">rodricus</a> · <a href="https://profiles.wordpress.org/rodrigosevero/">rodrigosevero</a> · <a href="https://profiles.wordpress.org/ravanh/">Rolf Allard van Hagen</a> · <a href="https://profiles.wordpress.org/rolfsiebers/">Rolf Siebers</a> · <a href="https://profiles.wordpress.org/rollybueno/">rollybueno</a> · <a href="https://profiles.wordpress.org/rherault/">Romain Herault</a> · <a href="https://profiles.wordpress.org/romulodl/">romulodl</a> · <a href="https://profiles.wordpress.org/ross_ritchey/">ross_ritchey</a> · <a href="https://profiles.wordpress.org/lev0/">Roy</a> · <a href="https://profiles.wordpress.org/geekstreetwp/">Russell Aaron</a> · <a href="https://profiles.wordpress.org/ryan/">Ryan Boren</a> · <a href="https://profiles.wordpress.org/ryankienstra/">Ryan Kienstra</a> · <a href="https://profiles.wordpress.org/rmccue/">Ryan McCue</a> · <a href="https://profiles.wordpress.org/ryanmurphy/">Ryan Murphy</a> · <a href="https://profiles.wordpress.org/welcher/">Ryan Welcher</a> · <a href="https://profiles.wordpress.org/sebastienserre/">S&#233;bastien SERRE</a> · <a href="https://profiles.wordpress.org/sergiomdgomes/">S&#233;rgio Gomes</a> · <a href="https://profiles.wordpress.org/soean/">S&#246;ren Wrede</a> · <a href="https://profiles.wordpress.org/sabbirmc/">Sabbir Ahmed</a> · <a href="https://profiles.wordpress.org/sajjad67/">Sajjad Hossain Sagor</a> · <a href="https://profiles.wordpress.org/saggre/">Sakri Koskimies</a> · <a href="https://profiles.wordpress.org/samikeijonen/">Sami Keijonen</a> · <a href="https://profiles.wordpress.org/viralsampat/">Sampat Viral</a> · <a href="https://profiles.wordpress.org/otto42/">Samuel Wood (Otto)</a> · <a href="https://profiles.wordpress.org/sandipmondal/">Sandip Mondal - a11n</a> · <a href="https://profiles.wordpress.org/sandrasanzdev/">Sandra Sanz</a> · <a href="https://profiles.wordpress.org/santosguillamot/">santosguillamot</a> · <a href="https://profiles.wordpress.org/mikachan/">Sarah Norris</a> · <a href="https://profiles.wordpress.org/sarahricker/">sarahricker</a> · <a href="https://profiles.wordpress.org/sathyapulse/">Sathiyamoorthy V</a> · <a href="https://profiles.wordpress.org/isaumya/">Saumya Majumder</a> · <a href="https://profiles.wordpress.org/xconsau/">Saurabh Sharma</a> · <a href="https://profiles.wordpress.org/scofennellgmailcom/">Scott Fennell</a> · <a href="https://profiles.wordpress.org/sc0ttkclark/">Scott Kingsley Clark</a> · <a href="https://profiles.wordpress.org/gmagicscott/">Scott Lesovic</a> · <a href="https://profiles.wordpress.org/wonderboymusic/">Scott Taylor</a> · <a href="https://profiles.wordpress.org/scribu/">scribu</a> · <a href="https://profiles.wordpress.org/sean212/">Sean Fisher</a> · <a href="https://profiles.wordpress.org/sebastianpisula/">Sebastian Pisula</a> · <a href="https://profiles.wordpress.org/monolithon/">seieric</a> · <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a> · <a href="https://profiles.wordpress.org/seedsca/">Sergio Scabuzzo</a> · <a href="https://profiles.wordpress.org/seriouslysenpai/">seriouslysenpai</a> · <a href="https://profiles.wordpress.org/sethta/">Seth Alling</a> · <a href="https://profiles.wordpress.org/shanjidah/">shangidah afroz</a> · <a href="https://profiles.wordpress.org/enchiridion/">Shannon Little</a> · <a href="https://profiles.wordpress.org/sharjeelkhanvmi/">Sharjeel Khan</a> · <a href="https://profiles.wordpress.org/shoaibkarimali/">Shoaib Ali</a> · <a href="https://profiles.wordpress.org/shraboni/">Shraboni</a> · <a href="https://profiles.wordpress.org/shreyasikhar26/">Shreyas Ikhar</a> · <a href="https://profiles.wordpress.org/shuvo586/">shuvo586</a> · <a href="https://profiles.wordpress.org/rsiddharth/">siddharth ravikumar</a> · <a href="https://profiles.wordpress.org/nomnom99/">Siddharth Thevaril</a> · <a href="https://profiles.wordpress.org/siobhyb/">Siobhan</a> · <a href="https://profiles.wordpress.org/sirzooro/">sirzooro</a> · <a href="https://profiles.wordpress.org/slaffik/">Slava Abakumov</a> · <a href="https://profiles.wordpress.org/slobodanmanic/">Slobodan Manic</a> · <a href="https://profiles.wordpress.org/smit08/">Smit Rathod</a> · <a href="https://profiles.wordpress.org/sobatkras/">sobatkras</a> · <a href="https://profiles.wordpress.org/khromov/">Stanislav Khromov</a> · <a href="https://profiles.wordpress.org/steelwagstaff/">SteelWagstaff</a> · <a href="https://profiles.wordpress.org/ste_95/">Stefano</a> · <a href="https://profiles.wordpress.org/ryokuhi/">Stefano Minoia</a> · <a href="https://profiles.wordpress.org/hypest/">Stefanos Togoulidis</a> · <a href="https://profiles.wordpress.org/stentibbing/">stentibbing</a> · <a href="https://profiles.wordpress.org/sabernhardt/">Stephen Bernhardt</a> · <a href="https://profiles.wordpress.org/netweb/">Stephen Edgar</a> · <a href="https://profiles.wordpress.org/camwynsp/">Stephen Page</a> · <a href="https://profiles.wordpress.org/sterlo/">Sterling Hamilton</a> · <a href="https://profiles.wordpress.org/stevenlinx/">Steven Lin</a> · <a href="https://profiles.wordpress.org/steveo2000/">steveo2000</a> · <a href="https://profiles.wordpress.org/studiolxv/">studiolxv</a> · <a href="https://profiles.wordpress.org/subrataemfluence/">Subrata Sarkar</a> · <a href="https://profiles.wordpress.org/sumitbagthariya16/">Sumit Bagthariya</a> · <a href="https://profiles.wordpress.org/sumitsingh/">Sumit Singh</a> · <a href="https://profiles.wordpress.org/5um17/">Sumit Singh</a> · <a href="https://profiles.wordpress.org/csesumonpro/">Sumon Sarker</a> · <a href="https://profiles.wordpress.org/sunil25393/">SunilPrajapati</a> · <a href="https://profiles.wordpress.org/sunyatasattva/">sunyatasattva</a> · <a href="https://profiles.wordpress.org/cybr/">Sybre Waaijer</a> · <a href="https://profiles.wordpress.org/synchro/">Synchro</a> · <a href="https://profiles.wordpress.org/system909/">system909</a> · <a href="https://profiles.wordpress.org/tahmidulkarim/">Tahmid ul Karim</a> · <a href="https://profiles.wordpress.org/inc2734/">Takashi Kitajima</a> · <a href="https://profiles.wordpress.org/karmatosed/">Tammie Lister</a> · <a href="https://profiles.wordpress.org/devtanbir/">Tanbir Ahmod</a> · <a href="https://profiles.wordpress.org/tanvirul/">Tanvirul Haque</a> · <a href="https://profiles.wordpress.org/taskotr/">Taras Dashkevych</a> · <a href="https://profiles.wordpress.org/targz/">targz</a> · <a href="https://profiles.wordpress.org/tlovett1/">Taylor Lovett</a> · <a href="https://profiles.wordpress.org/tazotodua/">tazotodua</a> · <a href="https://profiles.wordpress.org/tbember/">tbember</a> · <a href="https://profiles.wordpress.org/tykoted/">Teddy Patriarca</a> · <a href="https://profiles.wordpress.org/tellyworth/">Tellyworth</a> · <a href="https://profiles.wordpress.org/edent/">Terence Eden</a> · <a href="https://profiles.wordpress.org/tharsheblows/">tharsheblows</a> · <a href="https://profiles.wordpress.org/iamjaydip/">thejaydip</a> · <a href="https://profiles.wordpress.org/tweetythierry/">Thierry Muller</a> · <a href="https://profiles.wordpress.org/thijso/">Thijs</a> · <a href="https://profiles.wordpress.org/griffinjt/">Thomas Griffin</a> · <a href="https://profiles.wordpress.org/hyperbrand/">Thorsten Schraut</a> · <a href="https://profiles.wordpress.org/threadi/">threadi</a> · <a href="https://profiles.wordpress.org/baxbridge/">Tiffany Bridge</a> · <a href="https://profiles.wordpress.org/tillkruess/">Till Kr&#252;ss</a> · <a href="https://profiles.wordpress.org/sippis/">Timi Wahalahti</a> · <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a> · <a href="https://profiles.wordpress.org/tmooredev/">Titus Moore</a> · <a href="https://profiles.wordpress.org/tobiasbg/">TobiasBg</a> · <a href="https://profiles.wordpress.org/tobifjellner/">tobifjellner (Tor-Bjorn Fjellner)</a> · <a href="https://profiles.wordpress.org/tomjdv/">Tom de Visser</a> · <a href="https://profiles.wordpress.org/tjnowell/">Tom J Nowell</a> · <a href="https://profiles.wordpress.org/tj692/">Tom Janssen</a> · <a href="https://profiles.wordpress.org/tommusrhodus/">Tom Rhodes</a> · <a href="https://profiles.wordpress.org/tomasztunik/">Tomasz Tunik</a> · <a href="https://profiles.wordpress.org/tomepajk/">tomepajk</a> · <a href="https://profiles.wordpress.org/shimotomoki/">Tomoki Shimomura</a> · <a href="https://profiles.wordpress.org/skithund/">Toni Viemer&#246;</a> · <a href="https://profiles.wordpress.org/tonylocalword/">tony.localword</a> · <a href="https://profiles.wordpress.org/hellofromtonya/">Tonya Mork</a> · <a href="https://profiles.wordpress.org/toro_unit/">Toro_Unit (Hiroshi Urabe)</a> · <a href="https://profiles.wordpress.org/zodiac1978/">Torsten Landsiedel</a> · <a href="https://profiles.wordpress.org/transl8or/">transl8or</a> · <a href="https://profiles.wordpress.org/wpsmith/">Travis Smith</a> · <a href="https://profiles.wordpress.org/tremidkhar/">Tremi Dkhar</a> · <a href="https://profiles.wordpress.org/trevorpfromsandee/">TrevorPolischuk</a> · <a href="https://profiles.wordpress.org/nathannoom/">Trinadin</a> · <a href="https://profiles.wordpress.org/dinhtungdu/">Tung Du</a> · <a href="https://profiles.wordpress.org/turtlepod/">turtlepod</a> · <a href="https://profiles.wordpress.org/ugyensupport/">Ugyen Dorji</a> · <a href="https://profiles.wordpress.org/grapplerulrich/">Ulrich</a> · <a href="https://profiles.wordpress.org/umesh84/">Umesh Gupta</a> · <a href="https://profiles.wordpress.org/upadalavipul/">upadalavipul</a> · <a href="https://profiles.wordpress.org/utsavmadaan823/">utsavmadaan823</a> · <a href="https://profiles.wordpress.org/eboxnet/">Vagelis</a> · <a href="https://profiles.wordpress.org/evildon/">varma</a> · <a href="https://profiles.wordpress.org/vasartam/">vasartam</a> · <a href="https://profiles.wordpress.org/vdankbaar/">vdankbaar</a> · <a href="https://profiles.wordpress.org/velochicdunord/">Velochicdunord</a> · <a href="https://profiles.wordpress.org/vcanales/">Vicente Canales</a> · <a href="https://profiles.wordpress.org/vikasprogrammer/">vikasprogrammer</a> · <a href="https://profiles.wordpress.org/virgar/">Virginie Garnier</a> · <a href="https://profiles.wordpress.org/vishalkakadiya/">Vishal Kakadiya</a> · <a href="https://profiles.wordpress.org/vortfu/">vortfu</a> · <a href="https://profiles.wordpress.org/vtad/">vtad</a> · <a href="https://profiles.wordpress.org/elten/">wang</a> · <a href="https://profiles.wordpress.org/webbeetle/">webbeetle</a> · <a href="https://profiles.wordpress.org/webmandesign/">WebMan Design &#124; Oliver Juhas</a> · <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a> · <a href="https://profiles.wordpress.org/whaze/">whaze</a> · <a href="https://profiles.wordpress.org/whissi/">Whissi</a> · <a href="https://profiles.wordpress.org/earnjam/">William Earnhardt</a> · <a href="https://profiles.wordpress.org/williampatton/">williampatton</a> · <a href="https://profiles.wordpress.org/withinboredom/">withinboredom</a> · <a href="https://profiles.wordpress.org/woji29911/">woji29911</a> · <a href="https://profiles.wordpress.org/yahil/">Yahil Madakiya</a> · <a href="https://profiles.wordpress.org/yannielsen/">Yan Knudtskov</a> · <a href="https://profiles.wordpress.org/collet/">Yann</a> · <a href="https://profiles.wordpress.org/yoavf/">Yoav Farhi</a> · <a href="https://profiles.wordpress.org/byohann6/">Yohann Billard</a> · <a href="https://profiles.wordpress.org/fierevere/">Yui</a> · <a href="https://profiles.wordpress.org/omaeyusuke/">yuu</a> · <a href="https://profiles.wordpress.org/zaerl/">zaerl</a> · <a href="https://profiles.wordpress.org/zebulan/">Zebulan Stanphill</a> · <a href="https://profiles.wordpress.org/zenaulislam/">Zenaul Islam</a> · <a href="https://profiles.wordpress.org/ziposc/">ziposc</a> · <a href="https://profiles.wordpress.org/chesio/">Česlav Przywara</a> · <a href="https://profiles.wordpress.org/shenyanzhi/">沈唁</a></p><br /></code></pre>



<p>WordPress 6.1 would not have been possible without the contributions of more than 800 people in over 60 countries. Their asynchronous coordination to deliver hundreds of enhancements and fixes into a stable release is a testament to the power and capability of the WordPress community.</p>



<p>By release day, 71 locales had translated 90-percent or more of WordPress 6.1 into their language. Community translators continue after a release ensuring more translations are on their way. Thank you to everyone who helps to make WordPress available in over 200 languages.</p>



<p>Many thanks to all of the community volunteers who contribute to the <a href="https://wordpress.org/support/">support forums</a> by answering questions from WordPress users around the world.</p>



<p>If contributing to WordPress appeals to you, it’s easy to learn more and get involved. Discover the different teams that come together to <a href="https://make.wordpress.org/">Make WordPress</a> and explore the product roadmap on the <a href="https://make.wordpress.org/core/">core development blog</a>.</p>



<h2>The WordPress Mission &amp; You</h2>



<p>WordPress is software designed for everyone, emphasizing accessibility, performance, security, and ease of use. The project believes great software should work with minimum setup, so you can focus on sharing your story, product, or services freely. The basic WordPress software is simple and predictable so you can easily get started. It also offers powerful features for growth and success.</p>



<p>WordPress believes in democratizing publishing and <a href="https://opensource.org/osd-annotated">the freedoms that come with open source</a>. Supporting this idea is a large community of people collaborating on and contributing to this project. The WordPress community is welcoming and inclusive. Our contributors’ passion drives the success of WordPress which, in turn, helps you reach your goals.</p>



<p><a href="https://wordpress.org/about/">Learn more about WordPress</a> and how you can join our community to help shape the future of the world’s most popular website platform.</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<h2>Haiku Fun for 6.1</h2>



<p>Another release,<br />Mark it down as completed.<br />Breathe, relax, and cheers!</p>



<hr class="wp-block-separator has-alpha-channel-opacity" />



<p><em>This announcement was updated on Tue Nov 8 at 9:00 p.m. UTC to clarify some features in 6.1.</em></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, 01 Nov 2022 18:38: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:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:54:"Do The Woo Community: Around the Woo Builder Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"https://dothewoo.io/?p=73400";s:7:"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://dothewoo.io/around-the-woo-builder-community/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:389:"<p>Discovering what people are doing and thinking in the WooCommerce Builder Community and what you can learn from their insights.</p>
<p>&gt;&gt; The post <a rel="nofollow" href="https://dothewoo.io/around-the-woo-builder-community/">Around the Woo Builder Community</a> appeared first on <a rel="nofollow" href="https://dothewoo.io">Do the Woo - a WooCommerce Builder Community</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:"Tue, 01 Nov 2022 10:03:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"BobWP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:83:"WPTavern: New Missing Menu Items Plugin Adds Site Building Links to WordPress Admin";s:7:"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=139048";s:7:"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:94:"https://wptavern.com/new-missing-menu-items-plugin-adds-site-building-links-to-wordpress-admin";s: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:2904:"<p>If you are going all in on building sites with the new full-site editing (FSE) experience, then you may have noticed a lack of menu items that will deliver you directly to the tools you need to use. </p>



<p>It may be because the Site Editor is still in beta, or because WordPress leadership may still be <a href="https://wptavern.com/wordpress-contributors-consider-renaming-full-site-editing">discussing whether to rename FSE</a>. Perhaps it&#8217;s better that users don&#8217;t blindly stumble into FSE templates from the main admin menu, but some of these site building features are buried away with no quick access. </p>



<p>For example, you are three clicks deep before arriving at Template Parts. Managing reusable blocks is also a tucked away on a separate screen that can be accessed through the post editor but sends you to a new page. </p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">If you're using the block editor, and reusable blocks<br /><br />Do yourself a favor cut and paste this at the end of your website: <br /><br />/wp-admin/edit.php?post_type=wp_block<br /><br />Then bookmark it.</p>&mdash; Ben LayerWP &amp; WPDeals.email (@benswrite) <a href="https://twitter.com/benswrite/status/1585257042406957058?ref_src=twsrc%5Etfw">October 26, 2022</a></blockquote>
</div>



<p>When LayerWP founder Ben Townsend brought attention to this in a tweet, Roy Sivan responded with a link to a new free plugin that creates quicker access to these menus.</p>



<p><a href="https://wordpress.org/plugins/missing-menu-items/">Missing Menu Items</a> expands the admin menu with links to reusable blocks, navigation menus, templates, and template parts, so they are all one click away. It adds them to the Appearance menu under the Editor (beta) link:</p>



<img />



<p>If you are regularly working with Reusable blocks or editing navigation and templates, this plugin will save you some time and help you zip around the editor faster.  </p>



<img />



<p>Missing Menu Items was made by <a href="https://easilyamusedinc.com/">Easily Amused</a>, the creators of <a href="https://blockstyles.com/">Block Styles</a>, a commercial plugin that lets users further customize core blocks with unique styles and boasts “fully responsive block-level design control.&#8221; The team will be adding more useful menu links and admin improvements in future releases. Users can <a href="https://blockstyles.com/contact/">contact</a> the development team with menu item requests and they will consider them. </p>



<p><a href="https://wordpress.org/plugins/missing-menu-items">Missing Menu Items</a> is available on WordPress.org. Direct support is available for those who have purchased a <a href="https://blockstyles.com/">BlockStyles</a> membership, and community support can be found in the plugin&#8217;s forums on the directory.</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, 01 Nov 2022 03:15:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:49;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:64:"WordPress.org blog: People of WordPress: Raghavendra Satish Peri";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=13705";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:79:"https://wordpress.org/news/2022/10/people-of-wordpress-raghavendra-satish-peri/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:12327:"<p><strong>This month, in the run up to WordPress Accessibility Day, we feature Raghavendra Satish Peri, a blogger turned digital entrepreneur based in India, who specializes</strong> <strong>in web accessibility and digital marketing</strong>.</p>



<p><strong>The People of WordPress series shares inspiring stories of how people&#8217;s lives can change for the better through WordPress and its global network of contributors.</strong></p>



<img width="1014" height="627" src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-featured-img.jpg?resize=1014%2C627&ssl=1" alt="Raghavendra speaking at a Blogger event, 2015." class="wp-image-13701" />Raghavendra speaking at a blogger event, 2015



<h2>Expressing myself through WordPress</h2>



<p>Raghavendra Satish Peri says WordPress is more than a way to succeed online. It&#8217;s a community that has always answered his questions and helped him learn, and has enabled his voice to be heard across the world.</p>



<p>These are motivating benefits for Raghavendra, who has a vision impairment that introduces challenges to many of the things he wants to do. The WordPress community has helped him make some of his dreams come true. After chatting with others at WordPress events, about his wish to go trekking and running, he found he was later contacted by people in the community went with him to do just that.</p>



<img width="534" height="748" src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-3.jpg?resize=534%2C748&ssl=1" alt="Raghavendra training for a marathon in 2013." class="wp-image-13702" />Raghavendra training for a marathon in 2013



<p>He also found WordPress events a way to raise the importance of accessibility issues, share tips, and connect local communities so they can collaborate on items both within and outside WordPress.</p>



<h2>Life growing up with an enabling family</h2>



<p>A key asset for Raghavendra has been the support of his family as he coped with his progressive blindness. His sister took charge of teaching him important social and life skills, so he could navigate his country&#8217;s rigorous education system.</p>



<p>Those were the early days of technology everywhere, and nobody much was thinking about using it in education and day-to-day life.</p>



<p>When Raghavendra got his first computer, in 2004, it was a revelation. His sister taught him to use the internet efficiently, and he taught himself a few basics of programming. Soon he was spending 10 to 12 hours a day exploring the online world and learning about the web.</p>



<h2>Discovering WordPress and blogging</h2>



<p>In 2006, he learned basic web design and began to sell website templates. His growing interest in search engines and content led him to WordPress. As the years progressed, his eyesight deteriorated. He had to relearn his skills and acquire new ones to compensate. When he could no longer see the computer screen, he learnt to use screen readers.&nbsp;</p>



<p>At that point there was a gap: he had the same business skills, but he couldn&#8217;t apply them as effectively until he got comfortable with using screen readers.&nbsp;</p>



<img width="800" height="534" src="https://i0.wp.com/wordpress.org/news/files/2022/10/4.jpg?resize=800%2C534&ssl=1" alt="Raghavendra speaking at an event in Bangalore, India in 2014. Photo Credit: Two Feet To Fly - fLaShBuLbZz Photography" class="wp-image-13790" />Raghavendra speaking at an event in Bengalaru, India in 2014



<p>To help achieve that, Raghavendra moved to Bengalaru, where he got a full education in screen-reader technology and took a job as a consultant in digital accessibility.</p>



<p>He recalls learning from that time that, in his words: “Some things are important, but one needs to let them go so that more important things can take the new space.”</p>



<p>During his stay in Bengaluru, he stumbled on the idea of blogging and audiobooks. On his 23rd birthday, he had two firsts: registering a domain and publishing a blog post. At first he wrote about things happening in his daily life, which initially got low responses. But when he started attending blogging and tech meetups, he received encouragement from fellow bloggers who complimented him on his writing style. </p>



<p>Using WordPress to publish his story, Raghavendra found a love for writing and this made him want to learn and understand WordPress much better.</p>



<blockquote class="wp-block-quote">
<h2>“Writing freed my mind and soul from the pain and sorrow; it takes a person into a Zen state where one can understand their soul once they see their own thoughts on paper.”</h2>
<cite>Raghavendra Satish Peri</cite></blockquote>



<p>There were still some ongoing challenges arising from his difficulties with seeing. For example, Raghavendra found coding was made more complicated. But he took it slowly, and he improved steadily.&nbsp;</p>



<p>He started as many WordPressers do, installing themes and plugins, and making minor changes to the code. Ultimately, he moved all of his sites to WordPress, and as he learned more about WordPress, he could help his friends and family more with their projects.</p>



<p>After just a few years, Raghavendra had the skills and the confidence to build just about anything in WordPress, progressing from simple to complex websites.</p>



<p>Today Raghavendra is a successful entrepreneur. He sees his life as full of promise. WordPress still helps him grow every day, professionally and personally.</p>



<blockquote class="wp-block-quote">
<p>“There is always hope for tomorrow! Do not look for the light at the end of the tunnel, embrace the darkness, listen to the quietness, and feel the airflow. You will know that light is ahead even before you see it.&#8221;&nbsp;</p>
<cite>Raghavendra Satish Peri</cite></blockquote>



<h2>Contribute to accessibility and WordPress</h2>



<p>Another thing Raghavendra has in common with many WordPressers is his enthusiasm and involvement in the community. As he has learnt more about the software, he felt he needed to be involved with improving accessibility too. He started to help organize local meetups and conferences and encourages others to give time and skills to contribute too.&nbsp;</p>



<img width="704" height="500" src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-5.jpg?resize=704%2C500&ssl=1" alt="2016, Raghavendra on stage speaking at WordCamp Mumbai" class="wp-image-13699" />2016, Raghavendra speaking at WordCamp Mumbai



<p>He follows software development closely, especially where WordPress meets accessibility.</p>



<p>In 2020, on learning about a global WordPress Accessibility event, he applied and became a speaker. His topic was <a href="https://youtu.be/bvgLjWCRfrQ">Gutenberg Accessibility, A Screen Reader User&#8217;s Perspective</a>. His interest continued as a result of this event, and he wanted to be part of growing its audience and impact, initially through joining its dedicated channel on Slack. Eventually, he joined the organizing team for future events.</p>



<p>Helping run WordPress events brought together all of Raghavendra&#8217;s existing skills. It taught him a lot about what it takes to make an event truly inclusive, from captions and sign language to media players and more.&nbsp;</p>



<p>As his involvement has grown, Raghavendra has found it has become easier to source and use resources that make events and presentations more accessible. But knows there&#8217;s always more that can be learnt in this area, and encourages others to use understanding from events like the Accessibility Days in their conferences.</p>



<p>Join the global WordPress Accessibility Day 2022 online on November 2-3, 2022.&nbsp;It&#8217;s <a href="https://wpaccessibility.day/">free to register</a>!</p>



<a href="https://wpaccessibility.day/" target="_blank" rel="noreferrer noopener"><img width="568" height="173" src="https://i0.wp.com/wordpress.org/news/files/2022/10/wp-accessibility-day-22.png?resize=568%2C173&ssl=1" alt="WordPress Accessibility Day 2022 logo in purple and turquoise" class="wp-image-13783" /></a>



<h2><br />Sharing learning on accessibility can be a motivator </h2>



<p>In 2021, Raghavendra underwent his most challenging event to date, when he had a kidney transplant. To motivate himself, he started a website that focuses on accessibility and inclusive design. This prompted him to start an accessibility community to help fill the gaps in accessibility knowledge. Today, it is one of India’s largest online accessibility communities, educating developers and designers and training people with disabilities to build a career in accessibility testing.</p>



<img src="https://i0.wp.com/wordpress.org/news/files/2022/10/raghavendra-6.jpg?resize=680%2C790&ssl=1" alt="Portrait photo of Raghavendra post his organ transplant, 2021." class="wp-image-13698" width="680" height="790" />Raghavendra after his organ transplant in 2021



<p>Raghavendra is also a keen user of the WordPress Gutenberg editor and builds all his websites using it. Though content creation and editing can still pose him difficulties, he finds the front end of the Gutenberg blocks very accessible. He believes in participating in the software to make it a better experience for all.</p>



<blockquote class="wp-block-quote">
<p>&#8220;I decided to live my life to the fullest and make my mark on the world. This thought keeps me motivated.&#8221;</p>
<cite>Raghavendra Satish Peri</cite></blockquote>



<p>After a successful transplant, he lives a disciplined life with a few restrictions. He continues to enjoy working in-depth in disability, accessibility, and inclusion spaces. Raghavendra hopes others will join with him and the thousands of other people who collaborate to make a difference.</p>



<h2>Share the stories</h2>



<p>Help share these stories of open source contributors and continue to grow the community. Meet more WordPressers in the <a href="https://wordpress.org/news/category/newsletter/interviews/">People of WordPress series</a>.</p>



<p>Thank you to Raghavendra Satish Peri (<a href="https://profiles.wordpress.org/tarkham/" class="mention"><span class="mentions-prefix">@</span>tarkham</a>) for sharing his experiences for this latest edition.</p>



<h2>Contributors</h2>



<p>Thanks to Meher Bala (<a href="https://profiles.wordpress.org/meher/" class="mention"><span class="mentions-prefix">@</span>meher</a>), Abha Thakor (<a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</a>) and Surendra Thakor (<a href="https://profiles.wordpress.org/sthakor/" class="mention"><span class="mentions-prefix">@</span>sthakor</a>) for interviews and writing this feature, to Mary Baum (<a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a>), Chloe Bringmann (<a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a>), and Larissa Murillo (<a href="https://profiles.wordpress.org/lmurillom/" class="mention"><span class="mentions-prefix">@</span>lmurillom</a>) for reviews.</p>



<p>The <em>People of WordPress</em> series thanks Josepha Haden (<a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a>) and Topher DeRosia (<a href="https://profiles.wordpress.org/topher1kenobe/" class="mention"><span class="mentions-prefix">@</span>topher1kenobe</a>) for their support.</p>



<div class="wp-block-media-text is-stacked-on-mobile is-vertically-aligned-center"><img width="180" height="135" src="https://i0.wp.com/wordpress.org/news/files/2020/03/heropress_logo_180.png?resize=180%2C135&ssl=1" alt="HeroPress logo" class="wp-image-8409 size-full" /><div class="wp-block-media-text__content">
<p class="has-small-font-size"><em>This People of WordPress feature is inspired by an essay originally published on </em><a href="https://heropress.com/"><em>HeroPress.com</em></a><em>, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. </em>#HeroPress </p>
</div></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 31 Oct 2022 19:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Meher Bala";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"*data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Thu, 17 Nov 2022 09:57:03 GMT";s:12:"content-type";s:8:"text/xml";s:13:"last-modified";s:29:"Thu, 17 Nov 2022 09:45:33 GMT";s:4:"vary";s:15:"Accept-Encoding";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:16:"content-encoding";s:4:"gzip";s:4:"x-nc";s:9:"HIT ord 1";}}s:5:"build";s:14:"20221117095344";}