a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"


";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:61:"
	
	
	
	




















































";s: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:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"WordPress Planet";s:7:"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:28:"http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s: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:47:"WordPress Planet - http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:50:{i:0;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:97:"WPTavern: WordPress Support Team Seeks to Curb Support Requests for Commercial Plugins and Themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=104255";s:7:"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:239:"https://wptavern.com/wordpress-support-team-seeks-to-curb-support-requests-for-commercial-plugins-and-themes?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-support-team-seeks-to-curb-support-requests-for-commercial-plugins-and-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7049:"<img />



<p>WordPress&rsquo; Support Team contributors are <a href="https://make.wordpress.org/support/2020/09/talking-point-handling-support-for-commercial-users-on-the-wordpress-forums/">discussing</a> how they can curb support requests for commercial products on the official WordPress.org forums. Users sometimes seek help for commercial product upgrades on the forums of the free version, not knowing that the moderators&rsquo; official policy is to refer them to the extension&rsquo;s commercial support channel. In other instances, it is not immediately clear whether the issue is with the free version or a paid upgrade that the user has installed. </p>



<p>&ldquo;This has come up a few times the past weeks, mostly in relation to plugins that have a free base product on&nbsp;<a rel="noreferrer noopener" target="_blank" href="http://wordpress.org/">WordPress.org</a>, but sell addons on their own site, and where the line is drawn on who can get supported where,&rdquo; WordPress contributor Marius Jensen said during the team&rsquo;s most recent meeting. &ldquo;Authors are not allowed to support their paid products on&nbsp;<a rel="noreferrer noopener" target="_blank" href="http://wordpress.org/">WordPress.org</a>&nbsp;as is, but where do you draw the line, for example, when a base plugin causes issues with a paid addon, should then support be allowed for the base product on&nbsp;<a rel="noreferrer noopener" target="_blank" href="http://wordpress.org/">WordPress.org</a>, since that&rsquo;s the root issue, or should it be shipped off to the author&rsquo;s own site, since it affects a paying user?&rdquo;</p>



<p>This type of issue is common among products where WordPress.org is the main distribution channel for a popular free theme or plugin. The support relationship between the free and commercial products often intersects in an ambiguous way.</p>



<p>&ldquo;The goal is to ensure that paying customers and free users get the best support they can, from the ones that can give it,&rdquo; Jensen said. Volunteers do not have access to the commercial products, nor is it their job to support them. This is the crux of the matter.</p>



<p>&ldquo;It&rsquo;s an unacceptable misuse of volunteers time to support a product someone else has been paid to support,&rdquo; Jensen said.</p>



<p>Contributors discussed how they can handle different scenarios where it&rsquo;s unclear where the root of the problem is, in order to move the burden away from the support moderators, allowing the extension&rsquo;s author to discern if the problem is with the free version or commercial add-on. Volunteers should not have to familiarize themselves with the minute distinctions between the features that are offered for free or as an upgrade.</p>



<p>On the other side of these support scenarios, where it isn&rsquo;t clear where the problem originates, plugin and theme authors can be inconvenienced when support topics are hastily closed.</p>



<p>&ldquo;It&rsquo;s just that the closing of topics seems counter productive for those (users and devs alike) that get it wrong,&rdquo; plugin developer Arnan de Gans said. &ldquo;Since&nbsp;plugin/theme makers do not have any control over these forums we can&rsquo;t do a thing after topics get closed. Which works against the user experience by creating confusion.&rdquo; He suggested the team consider a grace period where the developer has a day or two to respond.</p>



<p>Ben Meredith, head of support for a freemium&nbsp;plugin, chimed in on the discussion, urging the support team to consider how closing issues can sometimes create a bad user experience:</p>



<blockquote class="wp-block-quote"><p> An issue related to premium products is raised, and summarily closed by forum mods for being about a premium product. This creates a &ldquo;googleable&rdquo; record of the error message/problem that then attracts other visitors. Once the issue has been closed, we get copy-cat issues &ldquo;I am having the same problem (link to closed post)&rdquo; We get those replies in both followup forum posts and internal tickets. To the layperson who has no idea the distinction between &ldquo;WordPress&nbsp;core&nbsp;volunteer&rdquo; and &ldquo;Company I just paid money to,&rdquo; this creates a bad experience all around.</p><p>Premium users are treated like second-class citizens on the forums. They don&rsquo;t know the guidelines, and reached out for help. This may be their first interaction with the WordPress community, and sometimes a well-meaning forum moderator can come across as wrist-slapping the exact people we want to give white-glove service to (they just paid us!).</p></blockquote>



<p>Michelle Frechette, Head of Customer Success at GiveWP, also shared this sentiment regarding the user experience. </p>



<p>&ldquo;Something I&rsquo;m not seeing addressed much here is how alienating it can feel to be corrected by the mods (or even the&nbsp;plugin&nbsp;authors) to be directed from the forums back to the paid support page,&rdquo; she said. </p>



<p>Ben Meredith said that despite sticky posts telling users not to post questions about commercial products, notes in the readme file, website notices, and canned replies, users will inevitably end up posting in the forums anyway. Steering them away to commercial support channels should be done in a way that does not make seeking help on WordPress.org an unwelcoming experience.</p>



<p>&ldquo;I want for the forums to feel as welcoming as a&nbsp;WordCamp,&rdquo; Meredith said.</p>



<p>&ldquo;The current enforcement of the &lsquo;premium plugins can&rsquo;t get support here&rsquo; is not in line with that overarching goal: users using and enjoying WordPress. Currently, premium users (who are potential community members and community leaders!) are getting a first impression of the community that is &lsquo;You&rsquo;re doing it wrong!&rsquo;</p>



<p>&ldquo;I&rsquo;d rather their first impression be &lsquo;Happy to help! heads up, for questions like this in the future, we need you to go here.'&rdquo;</p>



<p>In trying to ease the burden placed on volunteer support forum moderators, it&rsquo;s important to consider how any new policy might also negatively impact developers hosting their plugins and themes on WordPress.org, and what kind of vibe the response gives to users in search of help. There are more suggestions for solutions in the comments on the post, and the discussion is open until&nbsp;<a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200913T0000">Saturday, September 12, 2020, 07:00 PM CDT</a>. The Support Team is seeking to get a wider range of viewpoints from plugin and theme authors before making a final decision on new guidelines for addressing requests for support on commercial products. Make sure to <a href="https://make.wordpress.org/support/2020/09/talking-point-handling-support-for-commercial-users-on-the-wordpress-forums/">jump in on the comments</a> within the next week if you have something to add to the discussion.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 05 Sep 2020 02:03:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:1;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:80:"WPTavern: Gutenberg 8.9 Brings Block-Based Widgets Out of the Experimental Stage";s:7:"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=104238";s:7:"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:205:"https://wptavern.com/gutenberg-8-9-brings-block-based-widgets-out-of-the-experimental-stage?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-8-9-brings-block-based-widgets-out-of-the-experimental-stage";s: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:6765:"<p class="has-drop-cap">On Wednesday, September 2, <a href="https://make.wordpress.org/core/2020/09/03/whats-new-in-gutenberg-2-september/">Gutenberg 8.9 launched</a> with a set of new features, enhancements, and several bug fixes. The development team took the block-based widgets system out of its experimental stage, making it the default experience for all plugin users.</p>



<p>Block-based widgets have taken months upon months of work. The team has surpassed some of my expectations by essentially sticking a square peg into a square hole, granting the power of blocks to the sidebars/widgets system. On the whole, the system works. However, the team still has a lot of work to mold this feature into the shape it needs to be in for the upcoming WordPress 5.6 release in December. It is important that the community at large test, provide feedback, and contribute where possible.</p>



<p>Gutenberg plugin users who have not yet enabled block-based widgets via the experiments screen in past versions will be in for a surprise. The new system will have some of the familiarity of the block editor. However, it is a much different experience than traditional widgets.</p>



<p>The big questions we must answer is whether the feature is currently usable and whether it can be ready for WordPress 5.6.</p>



<h2>New Widgets Screen</h2>



<img />Block-based widgets screen.



<p class="has-drop-cap">Gutenberg completely replaces the old Appearance &gt; Widgets screen in the WordPress admin. The plugin no longer has an option for end-users to disable it, which was expected. The goal is to begin getting users accustomed to building their sidebars with blocks rather than traditional widgets.</p>



<p>For the most part, the new widgets screen handles block-based widgets without issue from a usability perspective. Adding blocks is little different from working with the post-editing screen. It should feel relatively natural for users who are accustomed to the block editor. If anything, the experience seems scaled down in comparison.</p>



<p>Unlike widgets in the past, blocks cannot be collapsed (the sidebars themselves can be). As a long-time WordPress user, this feels uncomfortable. However, it is the sort of uncomfortableness that will simply take some adjustment time.</p>



<p>Core legacy widgets worked well. However, I could not get legacy widgets to work from several third-party plugins. Sometimes, they disappeared from the editor. Then, they would later appear, seemingly at random. Eventually, during testing, I completely broke the page to the point where it did not display anything. Fortunately, I was able to fix it by clearing out a few widget-related rows from the database.</p>



<p>As a developer, I want to simply wipe the slate clean and leave the old widgets system in the dust of history. However, doing so may very well alienate many end-users. For this feature to be successful, we need to carry them along and allow them to easily transition from their current tools to the new system.</p>



<h2>Widget Blocks in the Customizer</h2>



<img />Widget blocks section in the customizer.



<p class="has-drop-cap">While the primary widget blocks screen was generally solid, that was not the case with widget blocks in the customizer. At best, it was sub-par.</p>



<p>We may finally be at that point where I agree with all those earlier complaints of the customizer control panel being too narrow. The most obvious issue was that the block toolbar was too wide for the control panel, hiding pieces of it off-screen. For some blocks, there are buttons that users cannot access.</p>



<p>That is not the end of the issues. Block options are unavailable, so users cannot even add something as basic as an image alt attribute. The core legacy widget blocks are not editable. The &ldquo;more options&rdquo; button popup has a transparent background, making the text unreadable and, for all intents and purposes, not worth attempting a use.</p>



<p>I understand that WordPress is still far from launching widget blocks in the customizer, but the feature was practically unusable. It is still very much in an experimental state and probably should have remained optional for another plugin update or two or three. I cannot recommend using this within any sort of production environment. Stick with the widgets screen in the admin.</p>



<h2>Widgets/Blocks Styling Issues for Theme Authors</h2>



<img />No structured grouping of &ldquo;widget&rdquo; HTML.



<p class="has-drop-cap">One of the largest changes that theme authors need to be aware of is that blocks in sidebars do not have the typical widget HTML wrappers. This could present some issues with styling widgets in the traditional fashion. For example, themes usually register a widget wrapper element and a wrapper for the widget title. This allows theme authors to build consistent styles for each widget. With blocks, this becomes much tougher because the theme author loses that control &mdash; this control is passed to the end-user.</p>



<p>The great part of this system is that users can do some really interesting things and have the flexibility to style their sidebars in any way they want. The bad part is that if a theme author has any sort of intricate styles, such as a boxed widget design, there is no easy way for the end-user to simply drop <em>widgets</em> into place and have them all use that boxed design. There is no standard class name for the theme author to target with CSS, which is what is required for consistently-styled widgets.</p>



<p>This is not necessarily a good or bad thing in and of itself. It is simply different.</p>



<p>With that said, I would have much preferred the Gutenberg development team created a new and separate system from the old sidebars/widgets system. Leave that in place, then build and promote &ldquo;block areas&rdquo; as a new system for theme authors to take advantage of. In the long run, it would allow theme authors to make the transition and even potentially support both systems in their themes. Theme authors are down in the trenches, working with their users on a day-to-day basis. They are in a much better position to handle the transition from old to new.</p>



<p>Theme authors who are not prepared to go <em>all in</em> with block-based widgets in WordPress 5.6 can add the following line of PHP to their theme&rsquo;s setup code to disable the widgets block editor:</p>



<pre class="wp-block-code"><code>remove_theme_support( 'widgets-block-editor' );</code></pre>



<p>Over time, theme authors will want to fully transition to the new system. However, this will provide additional time for them to make any adjustments that may be needed with how widgets are handled.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 04 Sep 2020 17:05:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;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:97:"WPTavern: Sunlit 3.0 for iOS Released, Featuring New Post Editor and Improved Discovery Interface";s:7:"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=103996";s:7:"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:237:"https://wptavern.com/sunlit-3-0-for-ios-released-featuring-new-post-editor-and-improved-discovery-interface?utm_source=rss&utm_medium=rss&utm_campaign=sunlit-3-0-for-ios-released-featuring-new-post-editor-and-improved-discovery-interface";s: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:3794:"<p><a href="https://sunlit.io/">Sunlit</a> 3.0 was released this week and is now <a href="https://apps.apple.com/us/app/sunlit/id1334727769">available in the App Store</a>. The free photoblogging app is a companion app to the <a href="https://micro.blog/">Micro.blog</a> indie microblogging platform. Sunlit has some similarities to Instagram minus the deadweight of ads and algorithms. Users can follow each other, comment on posts, and timeline photos are displayed in chronological order.</p>



<div class="wp-block-image"><img /></div>



<p>&ldquo;The idea is to get more people posting photos to their own blogs, whether that&rsquo;s hosted on Micro.blog,&nbsp;<a rel="noreferrer noopener" href="http://wordpress.com/" target="_blank">WordPress.com</a>, or a self-hosted WordPress,&rdquo; Micro.blog creator Manton Reece said. Publishing to WordPress does not require any extra plugins, because&nbsp;the app uses the built-in XML-RPC support.</p>



<p>Sunlit uses Micro.blog&rsquo;s infrastructure for the social aspect (replies and mentions). Users must be signed into a Micro.blog account (either paid or free) to view the timeline or reply to posts. In the current version, users are required to go to Micro.blog on the web to register first but Reece said his team is aiming to make this more seamless in the future so users can start using all the features in Sunlit right away.</p>



<p>&ldquo;Some people use Micro.blog for their blog exclusively, and some people have a mix of a microblog or photoblog on Micro.blog, as well as a full blog on WordPress,&rdquo; Reece said. </p>



<p>Sunlit also has <a href="https://www.manton.org/2020/08/31/countdown-to-sunlit.html">support for following Tumblr photoblogs</a>. In the app&rsquo;s Discover tab, users can enter a Tumblr subdomain like &ldquo;username.tumblr.com,&rdquo; and then follow the blog even if the user is not on Sunlit. </p>



<div class="wp-block-image"><img /></div>



<p>&ldquo;Micro.blog is based on blogs and IndieWeb standards so that it can integrate well with the rest of the web, not be walled off like a silo,&rdquo; Reece said. &ldquo;One aspect of this is that you can follow many blogs in Micro.blog even if the author of the blog hasn&rsquo;t registered on Micro.blog yet, similar to how you can subscribe to blogs in a feed reader like NetNewsWire or Feedbin.&rdquo;</p>



<p>Sunlit 3.0 has been redesigned with a new Discover interface and a faster, more flexible posting screen. Users can publish a quick photo or even a full blog post with text and photos uploaded to the users&rsquo; blog, along with the HTML layout for the post. This version also includes user search and support for mentions when replying to conversations.</p>



<div class="wp-block-image"><img /></div>



<p>Micro.blog is currently supporting the app&rsquo;s development, and Reese said he has no plans to add any commercial upgrades into Sunlit.</p>



<p>&ldquo;We support Sunlit as part of running Micro.blog,&rdquo; he said. &ldquo;Sunlit makes an existing Micro.blog subscription more useful, so it helps with the overall platform sustainability, even if not everyone using Sunlit is paying for a subscription. We hope that more people will sign up for a paid Micro.blog subscription, but it&rsquo;s not required.&rdquo;</p>



<p>Sunlit does not have an Android app but the teams would like to support Android in the future. The app is open source and <a href="https://github.com/microdotblog/sunlit">available on GitHub</a> under the MIT License.</p>



<p>&ldquo;Because Sunlit for iOS is open source, this [Android support] might be something that comes from the community or it might be something we take the lead on. I personally have much more experience with iOS, so we started there.&rdquo;</p>



<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 03 Sep 2020 23:15:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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:3;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:82:"WPTavern: WordPress Plugin Authors Should Avoid Confusing Users When Naming Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=104091";s:7:"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:209:"https://wptavern.com/wordpress-plugin-authors-should-avoid-confusing-users-when-naming-blocks?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-plugin-authors-should-avoid-confusing-users-when-naming-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7172:"<p class="has-drop-cap">On May 4, the StudioPress development team made a small but significant user-facing change to its Atomic Blocks plugin (now <a href="https://wptavern.com/atomic-blocks-rebranded-to-genesis-blocks-migration-path-to-new-plugin-coming-soon">rebranded to Genesis Blocks</a>). It <a href="https://github.com/studiopress/atomic-blocks/commit/af4a4aa30b05537bc93baa48d932ab9407c8eb7f">removed the &ldquo;AB&rdquo; branding</a> from its block titles. This minor update changed block titles such as AB Accordion and AB Button to Accordion and Button, respectively. On the surface, this change probably seemed of little consequence to the developers on the project. However, for at least one user, it created a massive workload.</p>



<p>Unless users religiously followed the GitHub code commits, they would have missed this update. Stacked with several other code changes for a seemingly unrelated ticket, the team left a message that read, &ldquo;Remove unnecessary &lsquo;AB&rsquo; from block titles.&rdquo;</p>



<p>The change made it into version 2.8.2 of the plugin, which launched a day later.</p>



<p>The problem was that there was no message in the change log that noted this. Users had no indication that the blocks from the plugin were being renamed. Typically, this would not be a big deal since the plugin team had merely dropped the &ldquo;AB&rdquo; prefix from the otherwise unchanged titles. However, what happens when one of those blocks&rsquo; titles matches a core block title?</p>



<p>That was the issue that Marcus Tibesar ran into. The AB Button block suddenly became the Button block. Thinking he was using the core WordPress Button, he made liberal use of it throughout his site. Throw in his decision to drop the plugin after StudioPress rebranded its plugin to Genesis Blocks, it became a bit of a disaster to clean up.</p>



<p>&ldquo;I have been using the Button block for months now only to discover that I&rsquo;m actually using the Atomic Blocks button block!&rdquo; <a href="https://wptavern.com/atomic-blocks-rebranded-to-genesis-blocks-migration-path-to-new-plugin-coming-soon#comment-340105">wrote Tibesar in a comment</a> on the Atomic Blocks rebranding post.</p>



<p>Theoretically, he should have needed to update only any lingering blocks from Atomic Blocks that he had knowingly used. But, he was stuck with blocks that he had unknowingly added to his posts and pages through no fault of his own.</p>



<p>This particular scenario was made worse because WordPress 5.4, released on March 31, introduced a new Buttons (plural) block. The old single Button block was removed from the normal inserter. While not all block-naming issues are so convoluted, it still begs the question: how can plugin authors avoid causing these types of user-experience issues?</p>



<p>It is easy to throw blame toward StudioPress &mdash; and the team could perhaps use a scolding for not being clear about the change when it happened. However, this brings forth a couple of things the greater WordPress community needs to figure out. The first is whether plugin authors need to use a consistent, prefixed naming scheme for their blocks. The second is what can WordPress do to help mitigate issues.</p>



<h2>Prefix All the Things</h2>



<img />Buttons, buttons, and more buttons.



<p class="has-drop-cap">That is the common saying in the WordPress development world, <em>right</em>? Prefixing and namespacing guidelines generally apply to the actual code, which is where conflicts arise. However, there are times when prefixing public-facing text is warranted.</p>



<p>And those times are when plugins utilize a shared space.</p>



<p>The block editor is one such shared space. With more and more block plugins landing in the directory, it is time that plugin authors consider how block-naming schemes affect end-users. The issue is certainly not limited to Atomic/Genesis Blocks. This has been an ongoing trend with several block library plugins. Some do better than others, but it&rsquo;s a toss-up each time a user installs such a plugin.</p>



<p>The easiest route is for plugin authors to simply prefix all custom blocks with their company branding (e.g., AB Button). On the other hand, not every block shares a title with one of the core blocks. For example, a block titled Product Carousel may not need to distinguish itself further from other blocks. It is unlikely that end-users are running multiple eCommerce plugins with blocks that share the same title.</p>



<p>&ldquo;All, repeat all, should have a prefix,&rdquo; said Tibesar.  &ldquo;The prefixes eliminate any confusion as to whether we users are selecting a core block or a third-party block. The most popular plugins appear at the top of the list, and it&rsquo;s confusing from whence they came when prefixes are absent.&rdquo;</p>



<p>At the very least, third-party blocks should have a prefix if their titles match one of the core blocks. End-users should not see two different Cover blocks in the block inserter, for example. Instead, they should see the core Cover and a second, uniquely-titled block. Prefixing is an easy way to do that. But, I could live with anything that does not cause user confusion.</p>



<h2>Locating Instances of Block Usage</h2>



<img />Manage Blocks screen.



<p class="has-drop-cap">In late 2019, the Gutenberg team released the <a href="https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced">first prototype</a> of a potential block management area for the WordPress admin. The Manage Blocks screen from the prototype showcased an area that would allow users to manage every block on their site. One of the more important bits of information on this screen was an &ldquo;Instances&rdquo; count, which displayed the number of times a block was in use. It further linked to a screen with every post that had a particular block.</p>



<p>One of the reasons this feature is important is that it would allow end-users to locate posts that they may want to clean up. Using the Atomic/Genesis Button block as an example, Tibesar could track down all those old uses and make any changes he wanted.</p>



<p>He said he would absolutely welcome this feature in WordPress.  &ldquo;New users are tempted to load up on zillions of block plugins all to be forgotten later.  Also, maintainers would use this tool when cleaning up broken sites. Just being able to see an overview of&nbsp;<em>what</em>&nbsp;blocks were used&nbsp;<em>where</em>, will allow publishers to dial back the number of block plugins installed on their sites, especially when new plugins and technologies emerge.&rdquo;</p>



<p>Because this feature is not in core yet, he had to turn to the <a href="https://wptavern.com/find-my-blocks-plugin-shows-all-blocks-in-use-on-a-wordpress-site">Find My Blocks</a> plugin, which helped him identify 22 posts and pages where he had unknowingly used the Button block from Atomic/Genesis Blocks. In the long term, this is something that needs to be handled directly in WordPress. It is unlikely to be the last time a user needs to clean house and get rid of old blocks.</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 Sep 2020 19:41:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;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:146:"WP Mobile Apps: When I try to add a self-hosted site, I get an “The site at this address is not a WordPress site” error message. What do I do?";s:7:"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:33:"http://apps.wordpress.com/?p=4128";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:160:"https://apps.wordpress.com/2020/09/03/when-i-try-to-add-a-self-hosted-site-i-get-an-the-site-at-this-address-is-not-a-wordpress-site-error-message-what-do-i-do/";s: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:2143:"<p>This error typically means that the WordPress app is not able to connect to your self-hosted site, either because the site URL is incorrect or because something is blocking the app from connecting using XML-RPC. </p>



<p>Here are some troubleshooting steps to try if you see this message:</p>



<ol><li>Ensure that you’ve typed in the URL correctly. </li><li>If the URL is correct, make sure <a href="https://apps.wordpress.com/support/#faq-ios-11">XML-RPC services are enabled on the site</a>. </li><li>Verify that xmlrpc.php is functioning properly by following steps 4-6</li><li>Locate your RSD meta tag by viewing-source on your site. It will look similar to this: </li></ol>



<pre class="wp-block-code"><code>&lt;link title="RSD" href="http://www.mysite.com/xmlrpc.php?rsd" rel="EditURI" type="application/rsd+xml" /&gt;</code></pre>



<ol start="5"><li>Next, follow the link, <a rel="noreferrer noopener" href="http://example.com/xmlrpc.php?rsd" target="_blank">http://example.com/xmlrpc.php?rsd</a>, and make sure it resolved to an XML file. Locate the WordPress API item: <a rel="noreferrer noopener" href="http://example.com/xmlrpc.php" target="_blank">http://example.com/xmlrpc.php</a>. </li><li>Lastly, load that apiLink value into your browser. If everything is setup correctly, you should see this message: “XML-RPC server accepts POST requests only.” </li><li>Go to the <a rel="noreferrer noopener" href="http://validator.w3.org/" target="_blank">W3C Markup Validator</a> and type in the URL of your WordPress site. </li><li>If you get a response such as “… one or more bytes that I cannot interpret as UTF-8,” that is most likely what is causing the app to have trouble with your site. </li><li>Switch your site to the default theme, deactivate any plugins, and try again, to help pin down where the problem is. If everything works, enable your theme and try again. If everything still works, reactivate each plugin one at a time reconnecting each time, until you find the one that is causing the breakage. </li><li>Turn on the Debug Mode to enable the extended log format, and check the log file.</li></ol>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 03 Sep 2020 19:08:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Nick Severson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:50:"WP Mobile Apps: Which devices will this work with?";s:7:"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:33:"http://apps.wordpress.com/?p=4125";s:7:"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://apps.wordpress.com/2020/09/03/which-devices-will-this-work-with/";s: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:89:"<p>The WordPress app works with any device that is running iOS version 11 or greater.</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 Sep 2020 18:51:35 +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:"Nick Severson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:66:"WP Mobile Apps: Which version of WordPress does the app work with?";s:7:"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:33:"http://apps.wordpress.com/?p=4121";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:88:"https://apps.wordpress.com/2020/09/03/which-version-of-wordpress-does-the-app-work-with/";s: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:160:"<p>We make sure the app works with the current and two previous versions of WordPress. Earlier versions are not supported, but most features may still work.</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 Sep 2020 18:49:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Nick Severson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:82:"WPTavern: WordPress 5.5.1 Released with Backfill for Deprecated JavaScript Globals";s:7:"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=104101";s:7:"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:209:"https://wptavern.com/wordpress-5-5-1-released-with-backfill-for-deprecated-javascript-globals?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-5-1-released-with-backfill-for-deprecated-javascript-globals";s: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:4766:"<p><a href="https://wordpress.org/news/2020/09/wordpress-5-5-1-maintenance-release/">WordPress 5.5.1</a> was released yesterday with <a rel="noreferrer noopener" href="https://core.trac.wordpress.org/query?status=closed&milestone=5.5.1&group=status&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority" target="_blank">34 bug fixes, 4 enhancements</a>, and&nbsp;<a rel="noreferrer noopener" href="https://github.com/WordPress/gutenberg/pull/24828" target="_blank">5 bug fixes</a>&nbsp;for the&nbsp;block&nbsp;editor. </p>



<p>Version 5.5 <a href="https://make.wordpress.org/core/2020/08/05/more-support-for-javascript-i18n-in-wordpress-5-5/">removed 19 legacy&nbsp;JavaScript&nbsp;localization objects</a>, in favor of using the new functions and utilities found in the i18n package&nbsp;introduced in WordPress 5.0. One of the most notable changes in this maintenance release is the inclusion of <a href="https://make.wordpress.org/core/2020/09/01/deprecated-javascript-globals/">a backfill for these now deprecated JavaScript globals</a>, which were causing errors with many popular plugins and themes. </p>



<p>&ldquo;If we only count plugins or themes with more than 100k installs or more, some of these already have an incredible impact, which is why we decided to&nbsp;patch&nbsp;this as fast possible.&rdquo; Joost de Valk said in an update compiling a list of <a href="https://docs.google.com/spreadsheets/d/1Vho7hJR4DMRyns38xcUMvVUj8SBov_J8_X4a7zwpmzo/edit?usp=sharing">affected extensions</a>, with the the help of Omar Reiss. </p>



<p>Themes impacted include Astra (1 million+ installs), Storefront (200k+), Hestia (100k+), and dozens more. A small selection of the popular plugins that were impacted include Advanced Custom Fields (1 million+), SiteOrigins Widgets Bundle (1 million+), AMP for WP, (100k+),  WooCommerce Services (1 million+), Ocean Extra (600k+), and Rank Math SEO (400k+). </p>



<p>Theme and plugin developers still need to update their code to use&nbsp;<code>wp.i18n</code> but in the meantime the legacy code will not block JavaScript execution. De Valk said the new plan is to remove this fallback code in two major versions, so developers need to have their code updated by the time WordPress 5.7 rolls around in 2021.&nbsp;</p>



<p>&ldquo;It sounds like a question that also ought to be addressed is how such wide-spread breakage could happen, and how it can be prevented in future,&rdquo; David Anderson commented on the announcement regarding the backfill. &ldquo;What part of the release process ought to have flagged up that this was about to happen, how did that part fail, and how can future similar failures be prevented.&rdquo; Jake Spurlock suggested a retrospective on WordPress 5.5 might be a good idea.</p>



<p>Three weeks after WordPress 5.5 was released, the <a href="https://wordpress.org/plugins/enable-jquery-migrate-helper/">Enable jQuery Migrate Helper</a> has more than 100,000 active installs. The plugin is available as a stopgap for users who experience problems with jQuery after updating to WP 5.5. Although several bumps along the road are expected for users during WordPress&rsquo; process of updating to use the latest version of jQuery, the official support forums were inundated with&nbsp;<a href="https://wordpress.org/search/5.5?in=support_forums">reports of broken sites</a> after 5.5 was released. Many users found out about the plugin after hours of troubleshooting and hunting for a fix. This is another issue that would be helpful to address in a 5.5 retrospective.</p>



<p>This maintenance release also <a href="https://make.wordpress.org/core/2020/08/27/wordpress-environment-types/">removes the ability to alter the list of environment types</a> in the new&nbsp;<code>wp_get_environment_type()</code> function. Contributors decided that introducing new types wasn&rsquo;t the intention of the feature and that it makes it so that theme and plugin developers cannot rely on a set, predictable list of types. They are now limited to production, staging, development, and local, with definitions for each available in the <a href="https://make.wordpress.org/core/2020/08/27/wordpress-environment-types/">announcement</a>.</p>



<p>&ldquo;By limiting the set of environment types in this way, WordPress&nbsp;core, plugins, and themes can change their behavior depending on this setting,&rdquo; Joost de Valk said.</p>



<p>WordPress 5.5.1 also fixes XML sitemaps paginating incorrectly, adds the site environment to debug information, and improves a number of other features that shipped with defects. The <a href="https://wordpress.org/support/wordpress-version/version-5-5-1/">full list of changes</a> is available on the release page.</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 Sep 2020 18:45:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;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:80:"WPTavern: Jetpack 8.9 Adds Donations Block, Newsletter Form, and Social Previews";s:7:"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=104088";s:7:"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:201:"https://wptavern.com/jetpack-8-9-adds-donations-block-newsletter-form-and-social-previews?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-8-9-adds-donations-block-newsletter-form-and-social-previews";s: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:4689:"<p class="has-drop-cap">Jeremey Herve, a Jetpack developer at Automattic, <a href="https://jetpack.com/2020/09/01/jetpack-grow-subscribers-collect-donations/">announced the release of Jetpack 8.9</a> earlier today. The update brings several major features to the plugin&rsquo;s users. Jetpack now sports a new social preview option in the block editor, a newsletter signup form type, and a block for handling donations.</p>



<p>Version 8.9 also adds support for the <a href="https://wordpress.org/plugins/amp/">AMP plugin</a>. Herve noted that Google and Automattic have worked together over the past six months to make this integration happen. He also announced that the team would release an in-depth post on the <a href="https://jetpack.com/blog/">Jetpack blog</a> on how end-users can use the tools available.</p>



<p>Overall, the update seems to be a solid release. I have not run into any issues with the features I make use of thus far.</p>



<h2>Social Network Preview for Posts</h2>



<img />Social Previews popup modal.



<p class="has-drop-cap">The latest version of the plugin adds a new Social Previews tab under the Jetpack sidebar panel in the block editor. It lists a few social icons and a preview button. Clicking the button pops up a modal window that allows users to preview what their post will look like in various places.</p>



<p>Currently, only Google Search, Facebook, and Twitter previews are integrated. However, the announcement post noted that LinkedIn previews are in the works.</p>



<p>Social Previews is not a particularly groundbreaking feature. However, it is a nice value-add for Jetpack users and almost a given in today&rsquo;s climate that is led by social networking sites. The feature is similar to what some SEO plugins, such as <a href="https://yoast.com/wordpress/plugins/seo/social-previews/">Yoast SEO Premium</a>, offer.</p>



<h2>Newsletter Sign-up Form</h2>



<ul><li class="blocks-gallery-item"><img />Select Newsletter Sign-up Form</li><li class="blocks-gallery-item"><img />Form Appears with Necessary Fields</li></ul>



<p class="has-drop-cap">Jetpack 8.9 introduces a Newsletter Sign-up form type via its Form block. When creating a new form, users will see the new option. It works as you might expect, adding a name and email field along with a message that the visitor is granting permission to send emails.</p>



<p>It might not be immediately apparent for some users is that they will need to install and activate the third-party <a href="https://wordpress.org/plugins/creative-mail-by-constant-contact/">Creative Mail</a> plugin for newsletters to work. Jetpack&rsquo;s Newsletter Sign-up merely handles the form. The newsletter aspect requires an account through the <a href="https://www.creativemail.com/plans/">Creativ.eMail website</a>. The free plan allows up to 5,000 emails per month, but you will need to upgrade to a paid tier after that, which will cost at least $4.95 each month.</p>



<p>If this sounds a bit convoluted, it&rsquo;s because it is. Without reading the docs or opening the Newsletter Integration tab in the block options, some users may be wondering how this feature works.</p>



<p>The integration itself works fluidly. Users can install and activate the plugin directly from the block editor. However, they will need to run through the setup and signup steps to begin using email campaigns, such as a newsletter.</p>



<h2>Donations Block</h2>



<img />Donations block and options.



<p class="has-drop-cap">Requiring yet another third-party service is Jetpack&rsquo;s new Donations block. Users will need to be on a <a href="https://jetpack.com/pricing/">paid Jetpack plan</a> to use the block, which allows them to integrate their Stripe account for collecting payments.</p>



<p>The Donations block is a simple affair. With a paid account in place, it is pretty much a plug-and-play system. The block options should be straightforward for the average end-user.</p>



<p>At this point, the Donations block and system may be too limited for some campaigns. This feature seems to more squarely target users who are looking to accept basic donations without all the features that a more mature donation plugin would provide. For anything beyond accepting a few small donations each year, I would lean toward the <a href="https://wordpress.org/plugins/give/">GiveWP plugin</a>. Its team is hyper-focused on making a great donation experience that scales to larger campaigns.</p>



<p>For users who are already using Jetpack and want to start small, it wouldn&rsquo;t hurt to give this block a spin. It is always possible to move up to a dedicated donation plugin down the road.</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 Sep 2020 21:06:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;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:52:"HeroPress: Consistency Gets You Where You’re Going";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=3263";s:7:"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:150:"https://heropress.com/essays/consistency-gets-you-where-youre-going/#utm_source=rss&utm_medium=rss&utm_campaign=consistency-gets-you-where-youre-going";s: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:6947:"<img width="960" height="480" src="https://s20094.pcdn.co/wp-content/uploads/2020/09/imran_sayed.jpg" class="attachment-large size-large wp-post-image" alt="Imran Sayed" /><p>The Tech Industry has given many gifts in my life. It has been an exciting journey so far. So today I decide to pen down my story as a self-taught Software Engineer and share it with the world.</p>
<p>The story of my journey to WordPress really begins about two years ago.</p>
<p>At the time, I was working a comfortable, well-paying job as a Team Lead at Tech Mahindra, one of the largest tech consultancy MNC’s in India. Through the 10 years that I worked at Tech M, I wore different hats &#8212; client representative, mentor, certified trainer &#8212; and collected several performance awards including mobile phones, televisions, a digital camera, microwave oven, a PlayStation and best of all, all-expense paid trip to <a href="https://codeytek.com/portfolio/trip-to-london/">London</a> <img src="https://s.w.org/images/core/emoji/13.0.0/72x72/1f60e.png" alt="?" class="wp-smiley" /></p>
<p>I thought that programming will give me an ability to express my creative skills through code. The idea of how my work and my knowledge can benefit others is thrilling and something that I love.</p>
<p>And the hero of my story is my very own brother, Sayed Taqui. Sayed is an experienced WordPress Developer and a core contributor, who gave me insights into this different world I had no idea about.</p>
<a href="https://s20094.pcdn.co/wp-content/uploads/2020/09/image2.jpg"><img /></a>Sayed Taqui and Imran Sayed
<h2>A new direction</h2>
<p>This did not happen overnight. This was a big risk to change track and move from my job to this new world of WordPress and it actually took me two years to make up my mind.</p>
<p>I started with saving money so I could quit my job and learn new skills. I started with HTML, CSS, JavaScript, PHP and then moved on to WordPress. I also learned to use the tools like Webpack, Babel &amp; Grunt.</p>
<p>My brother Sayed was always around to help me and guided me with some great inputs:</p>
<ul>
<li>learn the basics instead of specific frameworks (vanilla JS before jQuery)</li>
<li>build games to get good at JS. I built my <a href="https://github.com/imranhsayed/shooting-game">first game</a> in JavaScript, and in 2 weeks it was on <a href="https://play.google.com/store/apps/details?id=com.imranhsayed.birdshootinggame&hl=en">PlayStore</a>.</li>
<li>Hack away at the WordPress Core as a way to understand it deeply. He also suggested building a CMS in PHP to mimic WordPress, with CRUD functions, posts, pages and taxonomies, inspired by the WP Core.</li>
</ul>
<p><b>It all pays off!</b><br />
After 7 months of rigorous self-training, I applied for a job in a startup called <a href="https://myrl.tech/">Myrl Tech</a>. Myrl Tech was like a hardcore wrestling ground for me (देसी अखाड़ा), where I learnt to build and deploy applications from scratch.</p>
<p>After years’ worth of experience writing code, learning &amp; applying new technology, giving &amp; receiving training and even being involved with hiring, I got the opportunity to apply to <a href="https://rtcamp.com/">rtCamp</a>, where I currently work.</p>
<p><a href="https://s20094.pcdn.co/wp-content/uploads/2020/09/image4.jpg"><img /></a></p>
<p>rtCamp is a dream job for me. While the perks are great, what I identify most with is their importance on ethics, a friendly culture, and open-source community.</p>
<h2>Giving back</h2>
<p><a href="https://s20094.pcdn.co/wp-content/uploads/2020/09/image3.jpg"><img /></a></p>
<p>During my learning journey, I realized a lot of topics can only be understood by digging into the WP Core. And while many learning resources are available online and on WordPress.org, there are not enough tutorials or blogs available for beginners.</p>
<p>So I made a promise to myself that no matter how busy I get in future I will never forget my origin as a beginner and do what I can to help others. Knowledge is power and I feel it&#8217;s my responsibility to share what I know.</p>
<p>So I’ve started a <a href="https://www.youtube.com/ImranSayedDev">YouTube</a> channel, written tons of blog posts and put together several tutorials through my own open source learning platform. I am proud to have been a speaker at over 6 WordCamps across India. I am also a co-organizer of the local WP meetup group, and have organized 8 meetups last year.</p>
<p>I have also spoken at several international events &#8212; <a href="https://www.crowdcast.io/e/22feb20WPstream/2">Matt’s Popup Livestream</a> on <a href="https://www.slideshare.net/ImranSayed12/fastest-way-of-creating-gutenberg-blocks-with-minimal-javascript-knowledge-popup-livestream-22nd-feb-2020">Gutenberg</a>, <a href="https://wpsessions.com/sessions/wordsesh-apac-2020/">Wordsesh</a> on <a href="https://www.slideshare.net/ImranSayed12/why-progressive-apps-for-wordpress-wordsesh-2020">PWA</a>, <a href="https://javascriptforwp.com/conference/#schedule">JavaScript for WP Conference</a> on <a href="https://www.slideshare.net/ImranSayed12/harness-the-power-of-acf-for-gatsby-and-wordpress">Gatsby</a>, <a href="https://twitter.com/imranhsayed/status/1243498037604827138">WordPress VIP Webinar</a> and many more.</p>
<p>I feel that there are many developers who have amazing knowledge but need a little push since they have never spoken in public. So while all of the above have been high points of my past couple of years, I also enjoy motivating <a href="https://www.meetup.com/Pune-WordPress-Knowledge-Exchange/events/270630113/">new speakers</a> to share what they know.</p>
<p><a href="https://s20094.pcdn.co/wp-content/uploads/2020/09/image1.jpg"><img /></a></p>
<h2>Consistency is what got me here</h2>
<p>Switching career paths has been very fulfilling. Having a supportive brother from the technical field was a blessing, and the skills I gained from the previous role like effective communication, public speaking etc, really helped. However, I’ve had to be patient, consistent and put in the work to make it happen. The advice I’d give to anyone pondering a similar switch is to focus on being consistent.</p>
<p>I also feel that the best way to learn is to teach. Small positive steps ( teaching, helping others etc ) that we take today can make a big difference in a long run, not just in our life, but also the ones that directly or indirectly get influenced by our work.</p>
<p>I encourage you to contribute to open-source, not just code but any way possible. Many of us have the potential to do better than what we are doing already. What’s important is we start and be consistent.</p>
<p>The post <a rel="nofollow" href="https://heropress.com/essays/consistency-gets-you-where-youre-going/">Consistency Gets You Where You&#8217;re Going</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 01 Sep 2020 20:30:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Imran Sayed";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:55:"WordPress.org blog: WordPress 5.5.1 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=8979";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2020/09/wordpress-5-5-1-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8938:"<p>WordPress 5.5.1 is now available!</p>



<p>This maintenance release features&nbsp;<a rel="noreferrer noopener" href="https://core.trac.wordpress.org/query?status=closed&milestone=5.5.1&group=status&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority" target="_blank">34 bug fixes, 5 enhancements</a>, and&nbsp;<a rel="noreferrer noopener" href="https://github.com/WordPress/gutenberg/pull/24828" target="_blank">5 bug fixes</a>&nbsp;for the&nbsp;block&nbsp;editor. These bugs affect WordPress version 5.5, so you’ll want to upgrade.</p>



<p>You can <a href="https://wordpress.org/wordpress-5.5.1.zip">download WordPress 5.5.1 directly</a>, or visit the<strong>&nbsp;Dashboard → Updates</strong> screen&nbsp;and click&nbsp;<strong>Update Now</strong>. If your sites support automatic background updates, they’ve already started the update process.</p>



<p>WordPress 5.5.1 is a short-cycle maintenance release. The next major release will be <a href="https://make.wordpress.org/core/5-6/">version 5.6</a>.</p>



<p>To see a full list of changes, you can browse the&nbsp;<a href="https://core.trac.wordpress.org/query?status=closed&milestone=5.5.1&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">list on Trac</a>, read the <a href="https://make.wordpress.org/core/2020/08/27/wordpress-5-5-1-rc1/">5.5.1 RC1</a> and <a href="https://make.wordpress.org/core/2020/08/31/wordpress-5-5-1-rc2/">5.5.1 RC2</a> posts, or visit the <a href="https://wordpress.org/support/wordpress-version/version-5-5-1/">5.5.1 documentation page</a>.</p>



<h2>Thanks and props!</h2>



<p>The 5.5.1 release was led by <a href="https://profiles.wordpress.org/audrasjb/" class="mention"><span class="mentions-prefix">@</span>audrasjb</a>, <a href="https://profiles.wordpress.org/azhiyadev/" class="mention"><span class="mentions-prefix">@</span>azhiyadev</a>, <a href="https://profiles.wordpress.org/davidbaumwald/" class="mention"><span class="mentions-prefix">@</span>davidbaumwald</a>, <a href="https://profiles.wordpress.org/desrosj/" class="mention"><span class="mentions-prefix">@</span>desrosj</a>, <a href="https://profiles.wordpress.org/johnbillion/" class="mention"><span class="mentions-prefix">@</span>johnbillion</a>, <a href="https://profiles.wordpress.org/planningwrite/" class="mention"><span class="mentions-prefix">@</span>planningwrite</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/" class="mention"><span class="mentions-prefix">@</span>sergeybiryukov</a> and <a href="https://profiles.wordpress.org/whyisjake/" class="mention"><span class="mentions-prefix">@</span>whyisjake</a>.</p>



<p>Thank you to everyone who helped make WordPress 5.5.1 happen:</p>



<a href="https://profiles.wordpress.org/wpamitkumar/">Amit Dudhat</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/rarst/">Andrey &#8220;Rarst&#8221; Savchenko</a>, <a href="https://profiles.wordpress.org/afragen/">Andy Fragen</a>, <a href="https://profiles.wordpress.org/akissz/">Angel Hess</a>, <a href="https://profiles.wordpress.org/avixansa/">avixansa</a>, <a href="https://profiles.wordpress.org/bobbingwide/">bobbingwide</a>, <a href="https://profiles.wordpress.org/brianhogg/">Brian Hogg</a>, <a href="https://profiles.wordpress.org/chunkysteveo/">chunkysteveo</a>, <a href="https://profiles.wordpress.org/claytoncollie/">Clayton Collie</a>, <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a>, <a href="https://profiles.wordpress.org/dlh/">David Herrera</a>, <a href="https://profiles.wordpress.org/dd32/">dd32</a>, <a href="https://profiles.wordpress.org/demetris/">demetris</a>, <a href="https://profiles.wordpress.org/ocean90/">Dominik Schilling</a>, <a href="https://profiles.wordpress.org/dushakov/">dushakov</a>, <a href="https://profiles.wordpress.org/elrae/">Earle Davies</a>, <a href="https://profiles.wordpress.org/nrqsnchz/">Enrique Sánchez</a>, <a href="https://profiles.wordpress.org/fjarrett/">Frankie Jarrett</a>, <a href="https://profiles.wordpress.org/fullofcaffeine/">fullofcaffeine</a>, <a href="https://profiles.wordpress.org/garrett-eclipse/">Garrett Hyder</a>, <a href="https://profiles.wordpress.org/garyj/">Gary Jones</a>, <a href="https://profiles.wordpress.org/gchtr/">gchtr</a>, <a href="https://profiles.wordpress.org/azhiyadev/">Hauwa</a>, <a href="https://profiles.wordpress.org/herregroen/">Herre Groen</a>, <a href="https://profiles.wordpress.org/howdy_mcgee/">Howdy_McGee</a>, <a href="https://profiles.wordpress.org/ipstenu/">Ipstenu (Mika Epstein)</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a>, <a href="https://profiles.wordpress.org/jeremyfelt/">Jeremy Felt</a>, <a href="https://profiles.wordpress.org/jeroenrotty/">Jeroen Rotty</a>, <a href="https://profiles.wordpress.org/joen/">Joen A.</a>, <a href="https://profiles.wordpress.org/johannadevos/">Johanna de Vos</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/psykro/">Jonathan Bossenger</a>, <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/jonathanstegall/">Jonathan Stegall</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/justinahinon/">Justin Ahinon</a>, <a href="https://profiles.wordpress.org/akabarikalpesh/">Kalpesh Akabari</a>, <a href="https://profiles.wordpress.org/khag7/">Kevin Hagerty</a>, <a href="https://profiles.wordpress.org/knutsp/">Knut Sparhell</a>, <a href="https://profiles.wordpress.org/kbjohnson90/">Kyle B. Johnson</a>, <a href="https://profiles.wordpress.org/landau/">landau</a>, <a href="https://profiles.wordpress.org/laxman-prajapati/">Laxman Prajapati</a>, <a href="https://profiles.wordpress.org/gamerz/">Lester Chan</a>, <a href="https://profiles.wordpress.org/mailnew2ster/">mailnew2ster</a>, <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/markjaquith/">Mark Jaquith</a>, <a href="https://profiles.wordpress.org/mapk/">Mark Uraine</a>, <a href="https://profiles.wordpress.org/gothickgothickorguk/">Matt Gibson</a>, <a href="https://profiles.wordpress.org/tw2113/">Michael Beckwith</a>, <a href="https://profiles.wordpress.org/mikeyarce/">Mikey Arce</a>, <a href="https://profiles.wordpress.org/batmoo/">Mohammad Jangda</a>, <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a>, <a href="https://profiles.wordpress.org/nabilmoqbel/">Nabil Moqbel</a>, <a href="https://profiles.wordpress.org/krstarica/">net</a>, <a href="https://profiles.wordpress.org/oakesjosh/">oakesjosh</a>, <a href="https://profiles.wordpress.org/nosolosw/">O André</a>, <a href="https://profiles.wordpress.org/omarreiss/">Omar Reiss</a>, <a href="https://profiles.wordpress.org/ov3rfly/">Ov3rfly</a>, <a href="https://profiles.wordpress.org/paddy/">Paddy</a>, <a href="https://profiles.wordpress.org/casiepa/">Pascal Casier</a>, <a href="https://profiles.wordpress.org/pbiron/">Paul Biron</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/rajeshsingh520/">rajeshsingh520</a>, <a href="https://profiles.wordpress.org/ramiy/">Rami Yushuvaev</a>, <a href="https://profiles.wordpress.org/rebasaurus/">rebasaurus</a>, <a href="https://profiles.wordpress.org/riaanlom/">riaanlom</a>, <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a>, <a href="https://profiles.wordpress.org/kreppar/">Rodrigo Arias</a>, <a href="https://profiles.wordpress.org/rtagliento/">rtagliento</a>, <a href="https://profiles.wordpress.org/salvoaranzulla/">salvoaranzulla</a>, <a href="https://profiles.wordpress.org/sanzeeb3/">Sanjeev Aryal</a>, <a href="https://profiles.wordpress.org/sarahricker/">sarahricker</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/sabernhardt/">Stephen Bernhardt</a>, <a href="https://profiles.wordpress.org/sterndata/">Steven Stern (sterndata)</a>, <a href="https://profiles.wordpress.org/webzunft/">Thomas M</a>, <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</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/twentyzerotwo/">TwentyZeroTwo</a>, <a href="https://profiles.wordpress.org/planningwrite/">Winstina</a>, <a href="https://profiles.wordpress.org/wittich/">wittich</a>, and <a href="https://profiles.wordpress.org/yoavf/">Yoav Farhi</a>.";s: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 Sep 2020 19:13:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"Jb Audras";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;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:81:"Post Status: iThemes has acquired Restrict Content Pro from Sandhills Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=79593";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://poststatus.com/ithemes-has-acquired-restrict-content-pro/";s: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:3361:"<p><a href="https://restrictcontentpro.com/">Restrict Content Pro</a> has been <a href="https://sandhillsdev.com/?p=621">acquired</a> by <a href="https://ithemes.com/">iThemes</a>. Originally built by Pippin Williamson in 2012, RCP was early to the membership space and kept its promise of simplicity and stability throughout its tenure to date.</p>



<p>A couple of years ago, the <a href="https://sandhillsdev.com/">Sandhills Development</a> team put new energy into RCP, and <a href="https://sandhillsdev.com/2020/01/2019-year-in-review/">in 2019</a> the product made nearly $500,000 in revenue. 2020 is set to outpace those numbers. While the sale price is not disclosed, it is a seven-figure deal, likely somewhere between two and four times annual revenue. No members of the Sandhills team are moving over to iThemes and <a href="https://www.liquidweb.com/">Liquid Web</a> (the iThemes parent company), but there is a multi-month transition plan in place.</p>



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

</div>



<p>In our interview, we talked a lot about the process of the deal, the transition expectations, the past and future of the product, and the emotions surrounding the sale — particularly for Pippin.</p>



<p>Strategically, selling RCP enables Sandhills to better focus on their other products and free up several team members' energy. RCP was profitable and fun for them to work on, but they knew it was the right fit with iThemes and were excited to be able to better share the workload on Easy Digital Downloads, AffiliateWP, and their other products. Pippin compared it to hiring multiple full time team members, by simply transitioning what they are working on.</p>



<p>Additionally, the sale enabled them to put some cash in the bank, a comforting thing for a relatively small company in an extraordinarily uncertain time. Sandhills is very much an employee-first company, and this safety net lets them approach the future with confidence.</p>



<p>For iThemes, Matt tells me that the acquisition excites them in part because it gets them on the front-facing part of websites once again. For years now they have focused on the utility side through backups, security, etc. Now they can offer more than peace of mind to their customers by helping them make money.</p>



<p>Restrict Content Pro makes a lot of strategic sense for both Liquid Web and iThemes. Sandhills has always had a great audience, but it is most popular among developers and tinkerers — people ready to get their hands dirty a bit. iThemes opens up a much more user-centric audience, and it expands the base of potential customers through cross-marketing. Liquid Web has put a lot of energy into optimizing for eCommerce, and RCP offers a much more niche eCommerce product for their eCommerce audience that is not selling physical goods.</p>



<p>All around, this deal just makes sense. Thanks to recent energy reviving the product, website, and RCP community, Pippin and his team were able to receive a compelling offer for Restrict Content Pro. Thanks to a well-established marketing plan, and a well-established roadmap for furthering the product's success, iThemes should be able to nicely capitalize on the opportunity.</p>



<p>I'm glad to see a win-win and the opportunity for two companies I admire to take a new step in their respective journeys.</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 Sep 2020 17:06:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:12;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:55:"WordPress.org blog: The Month in WordPress: August 2020";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=8983";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wordpress.org/news/2020/09/the-month-in-wordpress-august-2020/";s: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:9603:"<p>August was special for WordPress lovers, as one of the most anticipated releases, WordPress 5.5, was launched. The month also saw several updates from various contributor teams, including the soft-launch of the Learn WordPress project and updates to Gutenberg. Read on to find out about the latest updates from the WordPress world.</p>



<hr class="wp-block-separator" />



<h2>WordPress 5.5 Launch</h2>



<p>The team launched <a href="https://wordpress.org/news/2020/08/eckstine/">WordPress 5.5</a> on August 11. The major release comes with a host of features like automatic updates for plugins and themes, enabling updates over uploaded ZIP files, a block directory, XML sitemaps, block patterns, inline image editing, and lazy-loading images, to name a few. WordPress 5.5 is now available in 50 languages too! You can update to the latest version directly from your WordPress dashboard or <a href="https://wordpress.org/download/">download</a> it directly from WordPress.org. Subsequent to the 5.5 release, the <a href="https://make.wordpress.org/core/2020/08/27/wordpress-5-5-1-rc1/">5.5.1 release candidate</a> came out on August 28, which will be followed by its official launch of the minor release on September 1.</p>



<p>A record 805 people contributed to WordPress 5.5, hailing from 58 different countries. <a href="https://profiles.wordpress.org/audrasjb/" class="mention"><span class="mentions-prefix">@</span>audrasjb</a> has <a href="https://jeanbaptisteaudras.com/en/2020/08/wordpress-5-5-core-stats-contributions-by-country-company/">compiled many more stats like that</a> and they’re well worth a read!</p>



<p>Want to get involved in building WordPress Core? Follow<a href="https://make.wordpress.org/core/"> the Core team blog</a>, and join the #core channel in <a href="https://make.wordpress.org/chat/">the Making WordPress Slack group</a>.</p>



<h2>Gutenberg 8.7 and 8.8</h2>



<p>The core team launched Gutenberg <a href="https://make.wordpress.org/core/2020/08/05/whats-new-in-gutenberg-august-5/">8.7</a> and <a href="https://make.wordpress.org/core/2020/08/19/whats-new-in-gutenberg-august-19/">8.8</a>. Version 8.7 saw many improvements to the Post Block suite, along with other changes like adding a block example to the Buttons block, consistently autosaving edits, and updating the group block description. Version 8.8 offers updates to Global Styles, the Post Block suite, and Template management. The release significantly improves the back-compatibility of the new Widget Screen, and also includes other important accessibility and mobile improvements to user interfaces like the Toolbar, navigation menus, and Popovers. For full details on the latest versions of these Gutenberg releases, visit these posts about <a href="https://make.wordpress.org/core/2020/08/05/whats-new-in-gutenberg-august-5/">8.7</a> and <a href="https://make.wordpress.org/core/2020/08/19/whats-new-in-gutenberg-august-19/">8.8</a>.</p>



<p>Want to get involved in building Gutenberg? Follow <a href="https://make.wordpress.org/core/">the Core team blog</a>, contribute to <a href="https://github.com/WordPress/gutenberg/">Gutenberg on GitHub</a>, and join the #core-editor channel in <a href="https://make.wordpress.org/chat/">the Making WordPress Slack group</a>.</p>



<h2>Check out the brand new Learn WordPress platform!</h2>



<p><a href="https://learn.wordpress.org/">Learn WordPress</a> is a brand new cross-team initiative led by the <a href="https://make.wordpress.org/community/">WordPress Community team</a>, with support from the <a href="https://make.wordpress.org/training/">training team</a>, the <a href="https://make.wordpress.org/tv/">TV team</a>, and the <a href="https://make.wordpress.org/meta/">meta team</a>. This platform is a learning repository on <a href="https://learn.wordpress.org/">learn.wordpress.org</a>, where WordPress learning content will be made available. Video workshops published on the site will be followed up by supplementary discussion groups based on workshop content. The first of these discussion groups have been scheduled, and you can join an upcoming discussion <a href="https://www.meetup.com/learn-wordpress-discussions/events/">on the dedicated meetup group</a>. The community team invites members to contribute to the project. You can apply to <a href="https://wordcampcentral.survey.fm/learn-wordpress-workshop-application">present a workshop</a>, <a href="https://wordcampcentral.survey.fm/learn-wordpress-reviewer-application">assist with reviewing</a> submitted workshops, and <a href="https://docs.google.com/spreadsheets/d/1A6BYIZAtqk3alBFtJBg-7Q7Y7NBLRnoRFbRTGho2rfI/edit">add ideas for workshops</a> that you would like to see on the site. You can also apply<a href="https://wordcampcentral.survey.fm/learn-wordpress-discussion-group-leader-application"> to be a discussion group leader</a> to organize discussions directly through the <a href="https://learn.wordpress.org">learn.wordpress.org</a> platform. We are also creating a dedicated Learn WordPress working group and have <a href="https://make.wordpress.org/community/2020/08/24/learn-wordpress-working-group-call-for-volunteers/">posted a call for volunteers</a>. Meetup organizers can use <a href="https://learn.wordpress.org/">Learn WordPress</a> content for their meetup events (without applying as a discussion group leader). Simply ask your meetup group to watch one of the workshops in the weeks leading up to your scheduled event, and then host a discussion group for that content as your event.</p>



<p>Want to get involved with the Community team? <a href="https://make.wordpress.org/community/">Follow the Community blog</a>, or join them in the #community-events channel in <a href="https://make.wordpress.org/chat/">the Making WordPress Slack group</a>. To organize a local WordPress community event, <a href="https://make.wordpress.org/community/handbook/virtual-events/welcome/applying-for-a-virtual-event/">visit the handbook page</a>. </p>



<hr class="wp-block-separator" />



<h2>Further Reading:</h2>



<ul><li>As <a href="https://make.wordpress.org/core/2020/03/11/all-women-release-squad/">proposed previously</a>, WordPress 5.6 will have an all-women release squad. The team has <a href="https://make.wordpress.org/core/2020/08/13/wordpress-5-6-release-planning/">started work on the 5.6 release planning</a>.</li><li>The community team has decided to <a href="https://make.wordpress.org/community/2020/08/04/announcement-flagship-events-in-2021/">cancel in-person flagship WordPress events</a> in 2021. While new applications for flagship events in 2021 will not be accepted, organizers of existing flagship events (such as WordCamp US, Europe, and Asia) will have the option to move their event online. </li><li>The core team is working on <a href="https://core.trac.wordpress.org/ticket/37110">updating the jQuery version</a> that comes with WordPress. As the first step, the <a href="https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/">team removed the jQuery Migrate 1.4.1 script </a>from WordPress 5.5. Those who wish to use jQuery migrate for maintaining plugin compatibility can install the <a href="https://wordpress.org/plugins/enable-jquery-migrate-helper/">Enable jQuery Migrate Helper plugin</a>, which has currently reached the 100k installs mark. </li><li>The WordPress documentation team is continuing its discussion on modifying the external linking policy. The conversation is taking place on a <a href="https://docs.google.com/document/d/1i0ipOTmKPShSIMoFuEXnI3gkOOUrPJb9t4HMf30JWC0/edit#heading=h.l0cppyl5zvhs">shared Google doc</a>. Feel free to add comments if you have any thoughts on the topic. </li><li>WordPress will <a href="https://core.trac.wordpress.org/ticket/51043#comment:7">not drop support for PHP 5.6</a>, as initially decided, in order to maintain better version compatibility. The team has additionally come up with a <a href="https://make.wordpress.org/core/2020/08/24/proposal-dropping-support-for-old-php-versions-via-a-fixed-schedule/">proposal to drop support for old PHP versions via a fixed schedule</a>.</li><li>The maiden edition of <a href="https://doaction.org/event/india-2020">do_action India online</a> was held from August 15 to 23. The event, which was held online with collaboration tools, had 94 participants who built fully functional websites for five NGOs from across the country. You can read more about 2020 do_action events <a href="https://wordpressfoundation.org/2020/charity-hackathons-august-2020-report/">on the WordPress Foundation blog</a>.</li><li>The Accessibility team has <a href="https://make.wordpress.org/accessibility/2020/08/25/accessibility-teams-goals-for-wordpress-5-6-and-beyond/">published their goals for WordPress 5.6 and beyond</a> and has started working on them.</li><li><a href="https://minneapolis.wordcamp.org/2020/">WordCamp Minneapolis/St. Paul</a> was held successfully on August 21. The event, which sold over 1400 tickets, had 18 speakers and 12 sponsors.</li><li>The Polyglots team has completed the translation <a href="https://make.wordpress.org/polyglots/2020/08/19/polyglots-handbook-reorganization-update/">handbook structure organization</a>. The handbook now has clear guides for translators, PTEs/GTEs, global mentors, and Plugin/Theme authors.</li></ul>



<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href="https://make.wordpress.org/community/month-in-wordpress-submissions/"><em>submit it here</em></a><em>.</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 Sep 2020 09:32:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Hari Shanker R";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;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:93:"WPTavern: WordSesh EMEA 2020 Kicks Off September 2, Featuring Short Talks and Micro-Tutorials";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=104024";s:7:"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:229:"https://wptavern.com/wordsesh-emea-2020-kicks-off-september-2-featuring-short-talks-and-micro-tutorials?utm_source=rss&utm_medium=rss&utm_campaign=wordsesh-emea-2020-kicks-off-september-2-featuring-short-talks-and-micro-tutorials";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4862:"<p>The second edition of <a href="https://wordsesh.com/">WordSesh EMEA</a> (Europe, Middle East, and Africa) is happening in less than 48 hours on September 2. The virtual event&rsquo;s schedule is tailored to attendees living in the Eastern hemisphere. In its first year running, WordSesh EMEA attracted a solid turnout of close to 1,000 attendees and was the proving ground for future regional WordSesh events. With WordCamp Europe <a href="https://wptavern.com/wordcamp-europe-goes-virtual-for-2021-in-person-conference-to-resume-2022">cancelling in-person events until 2022</a>, WordSesh EMEA is another way to highlight voices in the European WordPress community with a global audience.</p>



<p>&ldquo;There were definitely enough people at the inaugural WordSesh EMEA event that it was clear I needed to do it again, and expand into an APAC event,&rdquo; organizer Brian Richards said. </p>



<p>Richards had WordSesh APAC (Asia/Pacific) on the schedule for the end of March, right when the pandemic was breaking out. WordCamp Asia had just been cancelled the month before, as he was preparing to announce speakers for the WordSesh.</p>



<p>&ldquo;I worked with the WCAsia organizers to invite as many speakers to speak as I could,&rdquo; Richards said. &ldquo;I ended up helping run a Feb 22 pop-up livestream event to host several of them and invited the remainder to join me on a second full day of sessions at WordSesh.&rdquo;</p>



<p>Six months later, many WordCampers have had their fill of online events after months of mandated lockdowns and voluntary quarantining. Any new virtual event announced is immediately in competition with outdoor activities and hobbies that attendees could be engaging in away from the computer. Nevertheless, Richards has seen a threefold increase in signups over the previous year.</p>



<p>&ldquo;There are 3,200 folks registered currently, and we&rsquo;re on track to have 3,500 by the time things kick off on Sept 2nd,&rdquo; he said.</p>



<p>&ldquo;I&rsquo;ve been extremely mindful of virtual event fatigue for this one. This time around, the event is designed to fit inside an 8-hour span, inclusive of breaks, and no single session is longer than 20 minutes (plus Q&amp;A).&rdquo;</p>



<p>Whereas the previous WordSesh events were somewhat novel in that they gave attendees 24 hours of free live streaming WordPress presentations, pandemic era virtual events are evolving to eat up less of attendees&rsquo; free time. Organizers are now opting for scheduling fewer speakers for more manageable sections of time, or requiring them to give more condensed versions of their presentations.</p>



<p>&ldquo;I worked with the speakers to compress their talks into 20 minutes instead of the historical 40 minutes of years past,&rdquo; Richards said. &ldquo;I&rsquo;ve been developing a theory that case studies and micro-tutorials are the most optimal format for a conference talk, though, and I&rsquo;m going to test that idea more thoroughly in future events.&rdquo;</p>



<p>The schedule features 13 sessions on topics ranging from plugin development to client management to marketing with multisite networks. Whether you are a PHP developer learning how to navigate the world of blocks or an event planner seeking resources for the pandemic pivot, there&rsquo;s a session for everyone.</p>



<p>The talks will be a mix of live and pre-recorded, all broadcast live at their set times with speakers joining for Q&amp;A after each session.</p>



<p>&ldquo;Most will be pre-recorded to eliminate any technical risks during the event (e.g. internet outage, power outage, and all the many various life emergencies),&rdquo; Richards said. &ldquo;This also offers a nice bonus of the speaker being able to interact with the chat&nbsp;<em>during</em>&nbsp;their talk.&rdquo; </p>



<p>WordSesh EMEA will introduce a temporary job board, reminiscent of the kind one might find on a whiteboard in the hallway at a traditional WordCamp.</p>



<p>&ldquo;Attendees can share whether they are hiring or looking for work in an entirely free-form format,&rdquo; Richards said. &ldquo;The entire board will be accessible to attendees throughout the live event only. After the event has ended I will capture the final state of the board and share that with everyone who actually attended so they can have a semi-permanent record. I think this is the first time there has ever been anything that only exists for live attendees and nobody else.&rdquo;</p>



<p>Richards will also be delivering virtual swag to attendees&rsquo; inboxes again this year, with substantial discounts to various WordPress shops, hosts, and service providers. If you haven&rsquo;t signed up yet, you are not too late. <a href="https://wordsesh.com/register/">Registration</a> is still open until the last minute, and tickets are free. </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 Sep 2020 04:00:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:94:"WPTavern: One Year After Beta, Elmastudio’s Aino Blocks Plugin Lands in the Plugin Directory";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=104014";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:225:"https://wptavern.com/one-year-after-beta-elmastudios-aino-blocks-plugin-lands-in-the-plugin-directory?utm_source=rss&utm_medium=rss&utm_campaign=one-year-after-beta-elmastudios-aino-blocks-plugin-lands-in-the-plugin-directory";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6853:"<p class="has-drop-cap">One year ago today, Elmastudio <a href="https://www.elmastudio.de/en/beta-release-test-our-aino-free-theme-and-aino-block-collection/">launched a beta version</a> of its <a href="https://wordpress.org/themes/aino/">Aino</a> WordPress theme and <a href="https://wordpress.org/plugins/aino-blocks/">Aino Blocks</a> plugin. While the team pushed the theme live in the theme directory earlier this year, it wasn&rsquo;t until a couple of weeks ago that they officially released their blocks plugin.</p>



<p>Elmastudio&rsquo;s beta launch was one of the first pieces of news I noted when I began writing for the Tavern &mdash; I was already lining up stories a couple of weeks before I <em>officially</em> started. But, the story fell down the list over time. After seeing Aino Blocks land in the plugin directory two weeks ago, I thought it would be interesting to check out what the plugin looked like today.</p>



<p>Aside from a few minor styling issues, the Aino theme is a solid offering for users who are looking for a block-ready theme that provides an open canvas. I am generally a fan of Elmastudio&rsquo;s work with themes. However, most of the blocks from the Aino Blocks plugin are not particularly impressive. At best, they are par for the course for these types of block library plugins. I tend to install them to see if I can find a gem of an idea or two, some missing element that would solve one of the various problems I have. No such luck this time.</p>



<h2>The Plugin&rsquo;s Blocks</h2>



<p class="has-drop-cap">The one block that caught my eye the most was the Grid block. I am still hopeful that core WordPress adopts some sort of <a href="https://wptavern.com/should-the-block-editor-have-a-grid-system">grid layout block</a> or system. Therefore, I test every such block I come across.</p>



<p>The Grid block in the Aino Blocks plugin works well enough for people who have a background in CSS code. The terminology for the block options may be hard to understand for average users. On the whole, it does not feel intuitive enough for me to recommend it over better options.</p>



<img />Using the Grid block.



<p><a href="https://wptavern.com/diving-into-automattics-block-experiments">Layout Grid</a> by Automattic still holds the title for best grid block plugin thus far. Yes, its options can be confusing too, but it does provide dragging capabilities that will autofill those settings for less tech-savvy users. <a href="https://wptavern.com/build-versatile-layouts-with-the-generateblocks-wordpress-plugin">GenerateBlocks</a> also has a powerful Grid block that is far easier to use.</p>



<p>The most complex block and the one that seemingly pushes some boundaries is the Hero block. It is essentially a block that combines content, buttons, and media in a specific layout. The problem is that there may not be a need for the block in every case. It is far better suited as a block pattern, and because the plugin already introduces a custom pattern, there is little reason not to move along the same route with the Hero block.</p>



<p>Within a couple of minutes, I was able to recreate the default Hero block output with core WordPress blocks. The only exception to this was the use of the Badge block included with the Aino Blocks plugin.</p>



<ul><li class="blocks-gallery-item"><img />Aino Hero Block</li><li class="blocks-gallery-item"><img />Core Media &amp; Text Block</li></ul>



<p>To recreate the Hero block, an end-user merely needs to add a Media &amp; Text block. In the content/text panel for the block, they can add the Badge, Heading, Paragraph, and Buttons blocks. After adding an image in the media section, they would have recreated the Hero block. Because of the multiple inner blocks involved in this, it can be a bit complicated for some users. That&rsquo;s where patterns come into play. By using a pattern, the plugin would have:</p>



<ul><li>Used less JavaScript.</li><li>Used less CSS.</li><li>Mostly used core blocks.</li></ul>



<p>Users may be stuck with an unnecessary block in this case. And, if this is their first foray into the world of blocks, they are unlikely to learn that there was a better way.</p>



<p>The one thing the Hero block brings to the table is its custom grid settings. It provides end-users with control over the placement of content and media columns. That is the only thing it has going for it as an individual block, but such a feature might be better as custom block options, such as those provided through <a href="https://wptavern.com/control-block-design-via-the-editorplus-wordpress-plugin">EditorPlus</a>.</p>



<p>Aino Blocks does include a single block pattern. It is called Hero Aino. It is a customized version of the Hero block in pattern form and showcases what users can accomplish with a few adjustments of the block options.</p>



<img />Aino Hero block pattern.



<p>This pattern is the one area where the plugin shines.  It will be interesting to see if the developers continue with more patterns in the future.</p>



<p>The plugin also adds Badge, Card, Author, Testimonial, Buttons, and Arrow Button blocks. The Badge block allows users to add a small bit of text with an inline background. The Arrow Button is essentially a link with an arrow icon next to it. Everything else feels like it has been done before by a plethora of other block collection plugins.</p>



<h2>Final Verdict</h2>



<p class="has-drop-cap">I question whether most of these types of block library plugins are necessary at this point. Few of them feel like they are pushing any limits, raising the bar beyond what has already been done. My fear is that we will continue to see more and more of these collections packaged from every plugin and theme shop to the point where everyone is simply building the same blocks in-house.</p>



<p>This is why the block directory needs to be integrated into core. Instead of downloading an entire collection of blocks for something like a plain ol&rsquo; testimonial block, end-users can simply download a single testimonial block.</p>



<p>Perhaps I am being a bit harsh on Aino Blocks. Maybe it appeared in the plugin directory too late. Bigger plugins have already carved the path that Aino is trekking. I want to see more than <em>yet another block collection by yet another theme/plugin company</em>. I want to be dazzled.</p>



<p>For the most part, the plugin works well. I did not see anything technically wrong with it. I just do not see it appealing to many people outside of Elmastudio&rsquo;s current theme users, not when there are more mature plugins of its type out there.  There is still room to grow.  The company&rsquo;s best bet is to focus on building patterns.  Its first pattern shows some promise.  I am holding out hope for more interesting work to come.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 31 Aug 2020 22:09:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:15;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:50:"WPTavern: WordCamp Austin Opens Call for Musicians";s:7:"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=103599";s:7:"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:145:"https://wptavern.com/wordcamp-austin-opens-call-for-musicians?utm_source=rss&utm_medium=rss&utm_campaign=wordcamp-austin-opens-call-for-musicians";s: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:4365:"<div class="wp-block-image"><img /></div>



<p>WordCamp Austin 2020 is putting out a <a href="https://austin.wordcamp.org/2020/call-for-musicians/">call for musicians</a>, alongside its call for speakers. The event&rsquo;s organizers are rising to the challenge of creating a unique experience for attendees, while working within the constraints of a virtual format. Because the city prides itself on being &ldquo;the live music capital of the world,&rdquo; due to its abundance of music venues, the camp&rsquo;s organizers are inserting a little local Austin flavor into the schedule.</p>



<p>English poet Robert Browning, in his poem <em><a href="https://en.wikisource.org/wiki/Balaustion%27s_Adventure/I">Balaustion&rsquo;s Adventure</a></em>, wrote, <strong>&ldquo;<em>And who hears music, feels his solitude peopled at once.</em>&rdquo; </strong>Music has a way of bringing a human aspect to virtual events where people are sitting alone behind glowing screens, hoping to connect with others during this protracted time of isolation. WordCamp Austin&rsquo;s organizers are aiming to pepper the schedule with a diverse selection of performances for attendees to enjoy. </p>



<p>Musicians from anywhere in the world are invited to send an audition video (or schedule a live audition) for the opportunity to perform 2-5 songs at WordCamp Austin between sessions. Those who are selected will have the choice of performing live (with technical support from the organizers) or submitting pre-recorded performances. Organizers are also accepting auditions from singers, beat-boxers, rappers, and anyone who plays a non-traditional instrument.</p>



<p>&ldquo;We want WC ATX to be put on the map so that it will drive more attraction when we can get back together in person,&rdquo; co-organizer Ben Moore said. &ldquo;Like all other major events, 2020 will be the catalyst for more virtual events. Virtual, in-person, and a hybrid mix of the two will emerge after all of this.&rdquo;</p>



<p>WordCamp Austin organizers are planning to use <a href="https://hubs.mozilla.com/">Hubs Virtual Rooms</a> by Mozilla to create a unique environment for attendees. </p>



<p>&ldquo;I think it will be a lot of fun and allow everyone who is burnt out on Zoom to get something different,&rdquo; co-organizer Cousett Hoover said. &ldquo;We have a lot of dedicated folks but venues in Austin are super expensive which makes it hard to coordinate a WordCamp. This allows us to get more support and with a star group of organizers we can come back even better next year.&rdquo;</p>



<p>WordCamp Austin&rsquo;s use of Hubs Virtual Rooms will be an interesting experiment to follow, as most other virtual WordPress events have opted for Zoom.</p>



<p>&ldquo;One of the more exciting parts of Hubs is the spacial audio feature,&rdquo; Moore said. &ldquo;We hope this can create a more interactive experience for people as opposed to everyone having to hear everything being said. People will be able to &lsquo;walk&rsquo; around, gather in groups, and have smaller conversations without the need for a moderator to designate breakout rooms. We hope to imitate an &lsquo;in-person&rsquo; environment but remain virtual.&rdquo;</p>



<p>WordCamp Austin has been running since 2012, with a few gaps in between when they were not able to make it happen. Most other city-based WordCamps are on hold right now, but Hoover said she sees an opportunity in the present circumstances for newer community members to attend virtually.</p>



<p>&ldquo;I think it is a beautiful opportunity for so many who might otherwise not know about WordCamps or not have one close by to be able to attend,&rdquo; Hoover said. &ldquo;Personally, I work with a lot of Mompreneurs who use WordPress daily for their livelihoods just like many other WordPressers but so many do not know about the incredible community that WordPress has and these events are an opportunity to save on travel and time and still be able to participate a bit.&rdquo;</p>



<p>Organizers are planning two tracks, with 8-10 sessions separated by musical interludes. Applications for WordCamp Austin&rsquo;s musicians are <a href="https://austin.wordcamp.org/2020/call-for-musicians/">due by September 4</a>. The deadline to submit auditions is September 11 and performers will be notified of acceptance by September 15.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 29 Aug 2020 21:39:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;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:88:"WPTavern: Stepping Into a Market With Major Players, Mario Peshev Acquires WP-CRM System";s:7:"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=103830";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:219:"https://wptavern.com/stepping-into-a-market-with-major-players-mario-peshev-acquires-wp-crm-system?utm_source=rss&utm_medium=rss&utm_campaign=stepping-into-a-market-with-major-players-mario-peshev-acquires-wp-crm-system";s: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:5799:"<p class="has-drop-cap">Mario Peshev, the CEO of WordPress agency DevriX, <a href="https://www.prweb.com/releases/renowned_wordpress_core_contributor_mario_peshev_acquires_wp_crm_system_to_drive_business_development_on_worlds_largest_web_platform/prweb17328749.htm">officially announced</a> he had acquired the <a href="https://wordpress.org/plugins/wp-crm-system/">WP-CRM System</a> plugin this week. Formally, his company Premium WP Support is taking the reins for the project. Scott DeLuzio, the creator and previous owner of the plugin, <a href="https://scottdeluzio.com/wp-crm-system-acquired-by-mario-peshev/">published the news</a> on his blog last month.</p>



<p>DeLuzio originally built the plugin in 2015 after dissatisfaction with the solutions available on the market and having no control over the data, which was hosted on third-party services. He made the plugin available through his brand Amplify Plugins. Since then, his company has shifted focus to add-ons for eCommerce plugins in the WordPress space.  Therefore, he decided to sell his CRM project.</p>



<p>Peshev began his career as an engineer with enterprise-grade development. He said he was already familiar with CRMs after having worked with them long before he switched to WordPress development. It shaped the focus of DevriX toward small and medium-sized enterprises (SME) and growing businesses using WordPress as an application framework.</p>



<p>&ldquo;Over the past few years, we&rsquo;ve built a number of integral solutions in-house for our brands &mdash; including our business process management system or our time tracking software,&rdquo; he said. &ldquo;When I stumbled upon a tweet by Scott DeLuzio disclosing the sale of a couple of plugins, I got hooked almost immediately.&rdquo;</p>



<p>Peshev described WP-CRM System as being closely aligned with his company&rsquo;s goal, which is to support WordPress-driven businesses given clear metrics for maximum ROI.</p>



<p>&ldquo;It&rsquo;s powerful, integrates seamlessly with most form plugins (intercepting leads through Contact Form 7 or Gravity Forms), comes with Slack callbacks when leads come in, provides multiple views for different use cases, and gets the job done through a single, yet powerful dashboard,&rdquo; he said. &ldquo;Working with an existing customer base is also a great opportunity to refine the rest of our product offerings and work closely with businesses eager to evolve without having to migrate away from WordPress.&rdquo;</p>



<h2>The Future of WP-CRM System</h2>



<p class="has-drop-cap">For the short term, Peshev said his quality assurance team is doing extensive testing for performance opportunities. It is also testing to see how the plugin can integrate with other popular business plugins. However, the main goal is to push out some usability improvements.</p>



<p>&ldquo;In the long term, we will be expanding into several verticals &mdash; adding industry-specific features that better serve groups of businesses, such as accounting firms, creative studios, and event management companies,&rdquo; he said. &ldquo;The product is customer-led and we rely a lot on existing customers to improve usability even further.&rdquo;</p>



<p>The CRM market is becoming more competitive. Peshev said the contract on this acquisition was already signed by the time Automattic publicly announced its <a href="https://wptavern.com/automattic-acquires-zero-bs-crm-considers-rebranding-it-as-jetpack-crm">acquisition of Zero BS CRM</a> (now <a href="https://wptavern.com/zero-bs-crm-rebrands-and-relaunches-as-jetpack-crm">Jetpack CRM</a>) last year. However, he feels like there is plenty of room for growth for both plugins in the space.</p>



<p>&ldquo;Larger businesses have to scale with certain constraints in mind &mdash; both from a managerial standpoint, and when it comes to responsibility,&rdquo; he said. &ldquo;This is how startups emerge and quickly acquire certain industries or niche markets. Automattic is known to spread across other business segments, such as the hosting or eCommerce ecosystems. I certainly don&rsquo;t believe it sets the right tone, but I&rsquo;m also not concerned about yet another CRM solution entering the space. In this case, it&rsquo;s a mutual effort toward strengthening the position of WordPress in the SME space, bringing more opportunities to matured businesses, and preventing businesses from &lsquo;outgrowing&rsquo; WordPress as a business platform.&rdquo;</p>



<p>The major player in the CRM market is HubSpot, but it pushes users to an app that is hosted off-site, which is the opposite approach of both WP-CRM System and Jetpack CRM.</p>



<p>Peshev said his company used to be a HubSpot agency partner between 2017 and 2019. However, they terminated the partnership because HubSpot&rsquo;s focus was on building an opinionated business ecosystem that was cluttered and incompatible with other solutions. The goal seemed to be to push users toward other CMS-type software that they owned.</p>



<p>&ldquo;WP-CRM System feels native to the WordPress user,&rdquo; said Peshev. &ldquo;With simpler sales cycles, it doesn&rsquo;t feel overwhelming. You don&rsquo;t need to spend forever sifting through options and filling out complex forms. WP-CRM System is designed for growing businesses that used to rely on group chats, emails, and spreadsheets, and can&rsquo;t justify the administrative overhead (or pricing) of the giants in the CRM space. The market is indeed saturated, especially outside of WordPress, and segmentation is the best strategy here: evolving a CRM for a specific segment (WordPress users) and audiences (mostly service businesses) in our case, and developing separate extensions for verticals that reach out more frequently.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 28 Aug 2020 18:23: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:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:17;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:52:"WPTavern: MotoPress Acquires Gutenix WordPress Theme";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=103914";s:7:"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:149:"https://wptavern.com/motopress-acquires-gutenix-wordpress-theme?utm_source=rss&utm_medium=rss&utm_campaign=motopress-acquires-gutenix-wordpress-theme";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2654:"<p>MotoPress, a theme and plugin shop in operation since 2013, has <a href="https://motopress.com/blog/motopress-acquires-gutenix-wordpress-multipurpose-theme/">acquired the Gutenix WordPress theme</a> and its commercial <a href="https://zeguten.zemez.io/">ZeGuten</a> blocks plugin for Gutenberg. The free theme currently has more than 700 active installs after nine months on <a href="https://wordpress.org/themes/gutenix/">WordPress.org</a>.</p>



<p>MotoPress already has a number of successful niche WordPress themes and plugins but Gutenix fills the gap for a multipurpose theme. It was developed to work well with popular page builder plugins, and includes dedicated starter template libraries for Elementor, Brizy, and the block editor. The theme&rsquo;s commercial upgrades bundle the GutenixPro premium plugin, 30+ starter sites, and the ZeGuten plugin.</p>



<img />



<p>MotoPress is more well-known for its <a rel="noreferrer noopener" href="https://motopress.com/products/hotel-booking/" target="_blank">Hotel Booking plugin</a> and its associated add-ons. The company also develops a block collection plugin called&nbsp;<a rel="noreferrer noopener" href="https://wordpress.org/plugins/getwid/" target="_blank">Getwid Gutenberg blocks</a>, which has more than 10,000 active installs and is growing in popularity. Getwid is unique in that the collection is aimed at developers. The plugin comes with a free style kit that includes theme support snippets and CSS classes to accelerate the development process of building custom themes. Its accompanying <a href="https://wordpress.org/themes/getwid-base/">Getwid Base Theme</a> has more than 2,000 active installs.</p>



<p>Even though MotoPress is already developing its own block collection and base theme, the company saw value in acquiring a more multipurpose theme aimed at users of popular page builders.</p>



<p>&rdquo;Such a multipurpose theme is something we always wanted to create &ndash; but have never had the time resource to invest in such a multidimensional and complex thing,&rdquo; MotoPress CEO Alexander Matienko said.</p>



<p>&ldquo;After a fruitful exchange of experiences and visions with the Gutenix creators,I realized one thing. Not only are our companies aligned in our Gutenberg-driven passion, but we both have realistic views on the current WordPress market demands, where Elementor and other builders have been great value for people.&rdquo;</p>



<p>Gutenix is MotoPress&rsquo; first acquisition and the company plans to keep it as a separate product that is independent of <a href="https://motopress.com/membership/">MotoPress Club</a> membership.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 28 Aug 2020 04:34:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;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:75:"WPTavern: Elementor 3.0 Allows Users to Create a Personalized Design System";s:7:"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=103574";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:195:"https://wptavern.com/elementor-3-0-allows-users-to-create-a-personalized-design-system?utm_source=rss&utm_medium=rss&utm_campaign=elementor-3-0-allows-users-to-create-a-personalized-design-system";s: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:5838:"<p class="has-drop-cap">Elementor version 3.0 was <a href="https://elementor.com/blog/elementor-3-new-professional-features/">launched on Tuesday</a>. This release is the first major update to the plugin in over two years and is one of the largest upgrades in its history. The new version focuses on a design system, a new theme builder, and performance improvements. The driving motivation behind this release was to create global design tools, which is a shift from the plugin&rsquo;s roots as a mere page builder.</p>



<p>One of my biggest complaints about <em>builder</em> plugins is that they have often approached design on the individual page level first. However, web design is not about how you can fancy up a page. It is about taking a holistic approach to the overall design of the site. When building single pages, users of such plugins far too often create more work for themselves, much of it better handled on a global scale. One of the cornerstones of development is to not repeat work you have already done. Builder plugins can too easily push those who use them toward such bad habits.</p>



<p>Design should handle the foundational, global features first. Then, drill down to the atomic level when necessary. Builder plugins have almost exclusively gotten this backward in the past.</p>



<p>Elementor 3.0 seeks to solve this problem by introducing its design system and a new theme builder. The latter is part of its pro offering. The design system is essentially a global style creator and is available in both the free and pro versions. This is a welcome addition to the plugin and should create a solution for those foundational elements that the plugin has been missing.</p>



<p>&ldquo;Creating a site with a design system in mind (i.e. style guide, colors, and typography) is how professionals approach building websites,&rdquo; said Ariel Klikstein, the co-founder and CTO of Elementor. &ldquo;For many creators, this is an integral part of building the site as it helps them, their teams, and their clients to align and communicate around a consistent vision.&rdquo;</p>



<p>The Elementor team is coming to terms with the principles that have long guided web designers. The goal is to apply these principles to a user interface, breaking outside the confines of code.</p>



<p>&ldquo;Design system capabilities are among the pillars of building professional websites, as they give the ability to view and control the site elements from a centralized hub and apply sitewide changes to overall colors, typography, and layout,&rdquo; said Klikstein.</p>



<h2>Elementor&rsquo;s Design System</h2>



<img />Editing global colors with Elementor&rsquo;s design system.



<p class="has-drop-cap">Elementor is pitching its new design system as revolutionary. However, such design systems have long existed in the WordPress ecosystem. Theme developers have created similar systems for well over a decade, and they have since capitalized on WordPress&rsquo;s built-in customizer to do it in real time.</p>



<p>The question is whether this new system ups the ante, creating a new baseline in which others must compete.</p>



<p>That will be for users to decide. However, it does offer a plethora of options under its Site Settings menu. It allows end-users to customize colors, typography, and several other elements across the site. Current plugin users will have tools in their hands to do some more amazing things with Elementor, and they will be able to do them in a much more streamlined manner. Ultimately, it should save time and make it possible to update the site over the long term without re-editing old work.</p>



<p>It is not particularly revolutionary, but it is something that should be standard for any sort of visual design system.</p>



<p>&ldquo;While it&rsquo;s true that applying global styles was always possible using custom CSS code and themes, in Elementor V3.0 we made these options truly global,&rdquo; said Klikstein. &ldquo;Today they are independent of a theme, plugin, or widget as part of the element-based web design paradigm. The design system features are integrated into the editor workflow, without the need to use a single line of code. This will let the user implement global colors and fonts across any site element &mdash; be it a button, heading, or background. Then, if the user decides to change the color or a font style, he or she can change it once and apply it wherever it was previously placed in the global setting.&rdquo;</p>



<p><em>To not mislead readers, note that most themes that have implemented such systems have also not required custom CSS or other code.</em></p>



<p>Perhaps the bigger question is whether this new design system will be better than the upcoming <a href="https://make.wordpress.org/design/handbook/focuses/global-styles/">global styles</a> feature in Gutenberg and core WordPress. The aims of the two are similar, but WordPress will undoubtedly launch its feature with a much more limited set of options. WordPress will also need buy-in from theme authors.</p>



<p>Klikstein did not directly respond to the question of how WordPress&rsquo;s global styles feature impacted any decision that went into Elementor&rsquo;s design system feature. However, when cutting through the marketing cruft, he did say, &ldquo;It&rsquo;s great to see that Gutenberg/WordPress is also moving in this direction because we believe this is the best way to create consistent and maintainable websites.&rdquo;  He also said this feature was on the roadmap since the plugin&rsquo;s earlier theme builder concept.</p>



<p>Gutenberg may not be much of a consideration for Elementor&rsquo;s development team. They are clearly carving their own path to success and outpacing others in the race to building websites through a visual interface.</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, 27 Aug 2020 20:35:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;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:93:"WPTavern: Atomic Blocks Rebranded to Genesis Blocks, Migration Path to New Plugin Coming Soon";s:7:"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=103809";s:7:"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:229:"https://wptavern.com/atomic-blocks-rebranded-to-genesis-blocks-migration-path-to-new-plugin-coming-soon?utm_source=rss&utm_medium=rss&utm_campaign=atomic-blocks-rebranded-to-genesis-blocks-migration-path-to-new-plugin-coming-soon";s: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:4941:"<p>StudioPress, which was acquired by WP Engine in 2018, is <a href="https://studiopress.blog/announcing-genesis-blocks/">rebranding</a> its popular <a href="https://wordpress.org/plugins/atomic-blocks/">Atomic Blocks</a> plugin to <a href="https://wordpress.org/plugins/genesis-blocks/">Genesis Blocks</a>. WP Engine also acquired Atomic Blocks in 2018, growing the plugin&rsquo;s user base from 3,000 active installs to more than 60,000 over the past two years. The purpose of rebranding is to more tightly align the block collection with the Genesis brand.</p>



<p>&ldquo;We decided to elevate the Genesis brand to be the parent brand for all of our block and theme products moving forward,&rdquo; WP Engine VP of web strategy David Vogelpohl said. &ldquo;While we could have changed the title of the Atomic Blocks plugin, we wanted the slug to represent the Genesis brand so we decided to create a new plugin to achieve that outcome.&rdquo;</p>



<p>Unfortunately, in order to get the preferred slug for the plugin, WP Engine has to create a new plugin, instead of renaming the existing one. The company is creating a migration tool to move the plugin&rsquo;s 60k users over to  Genesis Blocks.  &nbsp;</p>



<p>&ldquo;Based on initial prototypes, the migration path will be automated for most users of the plugin,&rdquo; Vogelpohl said. &ldquo;We believe that migration technology will be available at the end of our next two-week sprint (starting next week), but we aren&rsquo;t able to commit to a date until more work has been completed.&rdquo;</p>



<p>The new Genesis Blocks plugin will now be explicitly developed in support of StudioPress themes and the <a rel="noreferrer noopener" href="https://studiopress.com/genesis-pro?__hstc=141311597.cfcc56073bf7750c2817e395dcab7eff.1598463759872.1598463759872.1598463759872.1&__hssc=141311597.1.1598463759872&__hsfp=1755708871" target="_blank">Genesis Pro package</a>. This doesn&rsquo;t mean the blocks cannot be used with other themes. Rather, it&rsquo;s more clear to users that the collection is designed to look best with WP Engine&rsquo;s products.</p>



<p>Genesis Blocks contains the same 22 free blocks found in its predecessor but can be upgraded via a Genesis Pro subscription to add more blocks, full page layouts, and pre-built sections. The subscription also includes access to advanced block-level user permissions as well as support for the Genesis Framework and its commercial child themes.</p>



<div class="wp-block-embed__wrapper">
<a href="https://cloudup.com/ci12kCBu6zy"><img src="https://cldup.com/0-CWURP7ZY.gif" alt="Pro" width="1198" height="794" /></a>
</div>



<p>Moving forward, all new features will be added to the new Genesis Blocks plugin, while support for Atomic Blocks gets scaled back to security releases and updates necessary for compatibility with WordPress.</p>



<p>&ldquo;<a href="https://twitter.com/wpdavidv"></a>In time, it will be deprecated, but only after enough users have migrated over,&rdquo; Vogelpohl said. &ldquo;We don&rsquo;t have a date for that yet and any future decisions will be based on the percentage of people who have migrated and the effects of that decision on the users who have not migrated at that time. It&rsquo;s important for us to make decisions that are respectful of the users of any of our products and the sites they manage. We will clearly communicate future plans and dates for deprecation, but for now, users of Atomic Blocks will have plenty of time to migrate. We will continue to update Atomic Blocks for security releases and functionality relative to updates in WordPress until the plugin is officially wound down.&rdquo;</p>



<p>When WP Engine acquired StudioPress and the Genesis Framework, the company said it planned to integrate it tightly into the the WP Engine Digital Experience Platform so it performs better there than anywhere else. It&rsquo;s an interesting trend among WordPress hosting companies, similar to <a href="https://wptavern.com/godaddy-acquires-themebeans-coblocks-block-gallery-and-block-unit-tests">GoDaddy&rsquo;s acquisition of CoBlocks and Themebeans</a>, where the company is gradually refining its product acquisitions to provide its own flavor or &ldquo;experience&rdquo; of WordPress.</p>



<p>WP Engine also plans to rebrand the <a href="https://wordpress.org/plugins/block-lab/">Block Lab</a> plugin as Genesis Custom Blocks. The plugin will also have a similar migration path for its 8,000 active installs. WP Engine&rsquo;s goal with the rebranding effort is to make page building with the block editor more streamlined, as well as an extension of its current product lines.</p>



<p>&ldquo;Genesis Blocks will play a big role in how we deliver value under Full Site Editing in the future, so this is the first step in helping the Genesis community and anyone in WordPress build better sites faster with the block editor,&rdquo; Vogelpohl said.</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, 27 Aug 2020 00:41:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:20;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:85:"WPTavern: WordPress Should Bump PHP Support on a Transparent and Predictable Schedule";s:7:"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=103828";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:215:"https://wptavern.com/wordpress-should-bump-php-support-on-a-transparent-and-predictable-schedule?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-should-bump-php-support-on-a-transparent-and-predictable-schedule";s: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:4504:"<p class="has-drop-cap">Juliette Reinders Folmer <a href="https://make.wordpress.org/core/2020/08/24/proposal-dropping-support-for-old-php-versions-via-a-fixed-schedule/">released a proposal</a> for WordPress to drop old PHP version support on a fixed schedule. She wrote the proposal after Matt Mullenweg, WordPress co-founder and project lead, reached out to discuss solutions. This was after he closed a <a href="https://core.trac.wordpress.org/ticket/51043">Trac ticket</a> last week that sought to <a href="https://wptavern.com/no-minimum-php-version-bump-this-year-wordpress-to-support-php-5-6-for-a-while-longer">drop support for PHP 5.6</a> and bump the minimum version to 7.1 for the next major WordPress release this year.</p>



<p>The proposal lays out a position that many in the WordPress community could get behind. It is a clear-cut, transparent path for the platform&rsquo;s future PHP support.</p>



<p>Folmer essentially put forward two roadmaps in the proposal. The first roadmap decides at what stage WordPress would drop support for a particular PHP version. The platform would remove support for a PHP minor release that is more than five years old each December. This would coincide with whatever major release of WordPress is upcoming. The following schedule lays out the minimum-supported PHP version each year:</p>



<ul><li>December 2020 &ndash; PHP 7.1</li><li>December 2021 &ndash; PHP 7.2</li><li>December 2022 &ndash; PHP 7.3</li><li>December 2023 &ndash; PHP 7.4</li><li>December 2024 &ndash; PHP 8.0</li></ul>



<p>The second part of the proposal creates a rolling schedule for backporting security updates to WordPress. Currently, WordPress releases security updates all the way back to the version 3.7 branch. If adopted, Folmer&rsquo;s recommendation would support only the previous four years of WordPress releases.</p>



<p>Such a change would mean that when WordPress 5.6 is released in December 2020, the WordPress project would be committed to backporting security fixes as far back as WordPress 4.7, released in December 2016.</p>



<p>Folmer also proposes backporting PHP upgrade notices from the site health project to the currently-supported older versions of WordPress. This measure would inform users of PHP version issues before they make the jump to a newer version of WordPress.</p>



<p>The overlap of bumping the minimum PHP support into the future and backporting security fixes gives users a potentially huge window of nine years in which they could stay on whatever version of PHP they are currently on. Nine years may seem like a lifetime on the web with its constantly-changing technology, and it was a point of contention from some people in the comments of the post. However, it is a plan of action, something the WordPress community has not had the pleasure of experiencing with regards to PHP support. Developers will undoubtedly argue over the dates and versions, but that is secondary to actually having a predictable timeline.</p>



<p>A fixed version bump schedule is welcome. It puts everyone from developers to end-users to web hosts on the same page. This level of transparency is necessary if we ever intend to move forward without rehashing the same arguments.</p>



<p>The system of waiting around to see when a specific PHP version&rsquo;s usage stats drop below a certain percentage just muddies things. The result is typically a long-winded argument that does not move the needle. Each side picks its stats. Each side digs its heels in. And each side has plenty of good points to make. Ultimately, everyone wants the same thing &mdash; to move the entire project forward and use up-to-date tools. However, they always disagree on how we get there. Eventually, the minimum PHP version gets bumped and the community gears up for the next round. It leaves us in a constant state of tug of war between those who want quicker advancement and those who do not want to leave users behind.</p>



<p>The truth is that no one is ever completely right in these arguments. There is no roadmap to follow. We have no guiding principle other than &ldquo;this has what&rsquo;s been done before.&rdquo;</p>



<p>WordPress needs to set clear expectations.</p>



<p>This is not just a problem with the minimum PHP version &mdash; many want a more-detailed roadmap for the entire project. However, minimum PHP support is one problematic area that we could have a solution for, and Folmer has carved out a path. We need only follow it.</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, 26 Aug 2020 23:08:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:21;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:33:"HeroPress: Discovering Your Place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=3253";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:118:"https://heropress.com/essays/discovering-your-place/#utm_source=rss&utm_medium=rss&utm_campaign=discovering-your-place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8563:"<img width="960" height="480" src="https://s20094.pcdn.co/wp-content/uploads/2020/08/082120-min.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: I was incredibly lucky to count myself as one of the happy WordPress business stories." /><p>I remember watching a dog I used to have jump without a thought into a river from the edge. I’ve never been someone to do that. I am cautious by nature, considered and ponderous. I plan, ponder, observe, I was always the child that watched and learnt through seeing. My introduction into the WordPress community like so most of my life experiences started with a circling on the edges, a gradual involvement, slowly acclimatising to the waters.</p>
<h3>From DIY roots</h3>
<p>It was the time when everyone was creating their own system from scratch, without asking if they could or should. PHP was fresh, smelt like newly baked cookies, delicious, tasty and often insecurely held together with hope, well-meaning wishes. I was riding the blogging community waves happy and fulfilled, yet frustrated by my own solution that was more a wish than an option. My blogging surf board was more a plank of wood well painted, but really close to breaking. Someone casually mentioned WordPress and after trying it, I was sold. This was pretty early in the life of the system we all enjoy now, but it had enough to show me that this was the way forward.</p>
<p>What truly sold me was how I could customise and theme my site so easily. This really was at that time all I cared about.</p>
<blockquote><p>With so many events like reboots and online refreshes, sites would change their themes more often than socks.</p></blockquote>
<p>I could embrace this with the ease of creating a theme. Style switchers were all the rage, I could change my theme as much as I wanted, with pretty minimal effort and leaving my content alone. It also meant I didn’t have to worry about security, which to be honest I avoided incidents previously out of luck over my code.</p>
<p>Each release saw rapid improvements, bugs were easy to report and whilst I was very much on the edges, I was slowly moving a few more rings deeper into the experience, testing the water as I went. Reporting a bug, asking a question, joining an IRC chat. My contribution circles were increasing as I moved deeper within the project.</p>
<h3>A timeline of sorts</h3>
<p>It would be easy to get stuck on small details in this story, the problem is I want to tell as much of my journey as possible and I’ve been lucky it’s been so long so far. The temptation to expand is heavy, so I’ll try and focus on some points over a timeline.</p>
<p>I am not sure when you say you joined a community, as I noted I sort of circled, dipping my toe in for a while. However, my first self noted contribution would be with the theme team. Working on building the &#8216;core&#8217; of WordPress itself was a hard place to find my start. It was noisy and as I mentioned I needed a quieter on-boarding. Within this space I could work through themes, learn slowly and participate in a smaller group. It was there I stayed for a while, growing my confidence as a contributor.</p>
<h3>Following my passion</h3>
<p>Time moved on and my freelance business grew from an acorn to a flourishing seedling and I made a choice to put my full bet on WordPress. By this time I had discovered not only WordPress, but begun to explore more fully BuddyPress too. It was there I found a place to thrive, grow and for a long time find my contribution space.</p>
<p>Community and specifically enabling people to create, manage and build open source communities, was and always will be a passion of mine. Particularly in this day and age, the potential for empowerment from this type of software can’t be ignored. I count myself lucky to have been able to focus on this for the time I did.</p>
<h3>Growing achievements with help</h3>
<p>My passions were growing along with my business thanks to this project. It was incredible to not only run my own company, but thrive in this space and grow in confidence. I began to travel to WordCamps, speak at them, make connections and then in leaps and bounds grow my business. This continued for a number of years. I was incredibly lucky to count myself as one of the happy WordPress business stories.</p>
<p>I got to focus on communities and as a result got to write a book about BuddyPress theme development.</p>
<blockquote><p>Writing a book was powerful for me as a dyslexic.</p></blockquote>
<p>Whilst not uncommon, for someone who is, writing a book can feel like quite a mountain and you likely are told you won’t achieve that at some point in your life. Never tell anyone they won’t do anything, because there’s a strong possibility given the chance they will, try giving them the opportunity instead.</p>
<p>WordPress has given me some incredible opportunities in life and I count writing a book as one of them. I didn’t do it by myself though, just like I haven’t done anything in this community alone. I got to write through networking, connections, the people I met. Without the community, I wouldn’t have had the business or written the book. Behind every publication is the community, the network that helped create it.</p>
<h3>WordPress has given me options</h3>
<p>One thing this story so far hasn’t covered is the personal side of my life. It’s told you my WordPress journey, yet the tale of any person always has a personal side. Every single commit, every single contribution has a heart, a life behind it. Each contribution has their own ebbs and flows.</p>
<p>Talking about myself isn’t easy because well I have a lot of privilege and right now in this world I know I am so very lucky to work remote, to have the job I do. Being able to be a full time contributor has given me a quality of life and empowerment I daily am grateful for.</p>
<blockquote><p>It meant I could be the sole earner when my partner was too ill to work.</p></blockquote>
<p>It’s allowed us to move to the best location for medical care and support. I am not unique, so many contributors care, support and hold up so many others. It’s not just the contributor behind the contribution, it’s their families, those that depend on them.</p>
<h3>Trying on contribution hats</h3>
<p>If someone asks me where they should contribute, I always suggest they try a number of areas. This is motivated by my own journey. Your place can also change depending on where you are in your contribution adventure, mine did. Just because you enter one area, that doesn’t mean you should stay there. Often the project is enriched by you moving around, spreading your skills and activating. You have to go where you both are the most comfortable and effective, this could be a surprising place to you and others.</p>
<p>A lot of the new contribution hurdles that once existed have been lowered, however for anyone joining it’s never easy. Remembering those first steps every single one of us took is crucial to keep projects alive. Once you forget how hard contribution is, you set yourself up to not have contributions.</p>
<h3>You got this</h3>
<p>If I could time travel there is probably a whole lot I’d do. In relation to my WordPress journey, if I could travel back through the many years to me as I click that first download of WordPress, I’d probably say this quote which I think is attributed to Winnie the Pooh.</p>
<blockquote><p>“You’re braver than you believe, stronger than you seem, and smarter than you think.”</p>
<p><small>― </small><span class="authorOrTitle"><small> A. A. Milne</small><br />
</span></p></blockquote>
<p>It’s so easy for us all to think we aren’t good enough. We can’t contribute. We can’t make a difference. We will never find our place. Nobody will ever want us in their project. I can’t lead. I am not good enough to be a team rep. I can’t speak on stage. I can’t lead a release. I can’t be a committer. A designer can’t write code. Sound familiar? I am sure one of those comments you’ve said to yourself, I’ve said them all to myself.</p>
<p>Maybe in this complicated year, we all should take a moment to be a little gentler, kinder and more compassionate to ourselves. Take a moment to recognise that you can contribute, you can make a difference.. and you do.</p>
<p>The post <a rel="nofollow" href="https://heropress.com/essays/discovering-your-place/">Discovering Your Place</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 26 Aug 2020 09:00: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:13:"Tammie Lister";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:22;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:109:"WPTavern: Privacy-First Gravatar Replacement, Pixel Avatars Module Released for the Toolbelt WordPress Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=103447";s:7:"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:261:"https://wptavern.com/privacy-first-gravatar-replacement-pixel-avatars-module-released-for-the-toolbelt-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=privacy-first-gravatar-replacement-pixel-avatars-module-released-for-the-toolbelt-wordpress-plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5538:"<img />



<p class="has-drop-cap">Ben Gillbanks decided to put an old idea into motion. After the discussion over Gravatar <a href="https://wptavern.com/local-avatars-in-wordpress-yes-please">privacy concerns and local avatars</a> in WordPress reignited a couple of weeks ago, he went to work building <a href="https://www.binarymoon.co.uk/2020/08/pixel-avatars-a-privacy-first-gravatar-replacement/">Pixel Avatars</a>, a generated avatar solution that requires no connection to a third-party service.</p>



<p>Gravatar solves a huge problem. It creates a global avatar so that users need to upload an image to only one site and carry it around the web with them. To use the service, sites must pass email addresses back to Automattic-owned Gravatar.com, such as when a visitor leaves a comment. The typical local avatar solution suffers because it forces users to sign up and upload an image for that specific site. Neither option is ideal for every site owner. And, both options tend to add heavily to the page load speed, depending on the number of avatars loaded.</p>



<p>That is where Pixel Avatars come into play. The script has all the privacy benefits of local avatars while maintaining a light footprint.</p>



<p>&ldquo;Initially, I just liked the idea of making dynamic images that can follow you around the internet,&rdquo; said Gillbanks. &ldquo;I hadn&rsquo;t even considered the privacy implications of using Gravatar &mdash; although in hindsight they are obvious.&rdquo;</p>



<p>He is launching Pixel Avatars as a module in <a href="https://wordpress.org/plugins/wp-toolbelt/">Toolbelt</a>, a WordPress plugin that he <a href="https://wptavern.com/toolbelt-a-new-jetpack-inspired-plugin-with-a-focus-on-speed-and-privacy">launched in 2019</a>. The plugin is a privacy-focused alternative to Jetpack, another project of Automattic that relies on connecting to a third-party server.</p>



<p>&ldquo;The last few years have made a lot of people more aware of privacy online and so I want everything I build to have privacy as a priority,&rdquo; he said.</p>



<p>Gillbanks had not put much thought into the Gravatar vs. local avatar discussion until the WP Tavern coverage of it. <em>It is nice to see that we are least in part responsible for some innovative ideas.</em></p>



<p>&ldquo;It is accepted that using Gravatar is how you add avatars to WordPress sites,&rdquo; he said. &ldquo;However, Gravatar is owned by Automattic and it has the potential for them to generate a lot of data about what sites people view (comment on), and how popular websites are. I have no reason to be suspicious here. I doubt it&rsquo;s being used in this way, but the potential is there and we&rsquo;d have no way of knowing if it was being used for data collection.&rdquo;</p>



<p>He further explained that he believes Gravatar would be better as an optional plugin. &ldquo;Even a bundled plugin would be better than having it on by default,&rdquo; he said. &ldquo;In my opinion, the default should be local avatars with a fallback similar to what I have made for non-registered users (or just a blank image). I&rsquo;ve offered my code to the core privacy team &mdash; my plugin is GPL and the <a href="https://github.com/BinaryMoon/wp-toolbelt/tree/master/modules/avatars">code is on Github</a>, so they are welcome to use it if they wish.&rdquo;</p>



<h2>How the Pixel Avatars Feature Works</h2>



<p class="has-drop-cap">Pixel Avatars are completely local to the site. Using 5kb of JavaScript, which is smaller than a single avatar image on average, the code generates a pixelated avatar. For each user, the plugin creates a hash string using their email address. This method also ensures that the avatar is consistent regardless of what site it is used own.</p>



<p>One of the reasons this is much faster than traditional avatar systems is that the avatars are generated. They are not images that must be loaded, which can be especially problematic when loading a blog post with 100s of comments, each with its own avatar.</p>



<p>&ldquo;If you use external or local avatars then you will still need to load additional image files and no matter how good your content delivery system (server, CDN, third-party avatar service, etc.), this will mean more data transfer, so a slower page load than my Javascript system,&rdquo; said Gillbanks.</p>



<p>From a technical perspective, the script is relatively simple. It short-circuits the core WordPress <code>get_avatar()</code> function and returns an HTML canvas element with a unique data property containing the hash of the user&rsquo;s email address. Once the page is loaded, the JavaScript code generates a unique image for each of the canvases.</p>



<p>&ldquo;Since I am filtering a core function, this will work everywhere that function is used,&rdquo; said Gillbanks. &ldquo;Comments in the admin, the little avatar in the admin bar, and any other pages or blocks that make use of the <code>get_avatar()</code> function. It&rsquo;s not just for comments.&rdquo;</p>



<p>Some site owners may want to use Toolbelt to handle guest commenter&rsquo;s avatars while serving a local avatar for logged-in users. This system could be the best of both worlds &mdash; local avatars for those who have them and not sending any data from site visitors to a third-party site. Gillbanks has tested against 10up&rsquo;s <a href="https://wordpress.org/plugins/simple-local-avatars/">Simple Local Avatars</a> plugin, but it should work with other local avatar plugins.</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, 25 Aug 2020 18:16:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;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:98:"WPTavern: Automattic Tangles with Apple Over Lack of In-App Purchases in the WordPress for iOS App";s:7:"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=103709";s:7:"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:241:"https://wptavern.com/automattic-tangles-with-apple-over-lack-of-in-app-purchases-in-the-wordpress-for-ios-app?utm_source=rss&utm_medium=rss&utm_campaign=automattic-tangles-with-apple-over-lack-of-in-app-purchases-in-the-wordpress-for-ios-app";s: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:8239:"<p>Over the weekend, Matt Mullenweg announced on Twitter that Apple&rsquo;s App Store had blocked Automattic from shipping updates to WordPress&rsquo; official iOS app.  Automattic doesn&rsquo;t sell anything for WordPress.com or Jetpack inside the mobile apps, but the app included external purchasing methods that bypassed Apple&rsquo;s requirement of selling via in-app purchases. </p>



<p>On the surface it seemed Apple was forcing a free app to add in-app purchases solely to extract its 30% cut of the revenue. The problem was if users drilled down deep enough into web help pages, they could <a href="https://twitter.com/mysk_co/status/1296914225718267907">find a window to escape the walled garden</a>. While this seems like an unlikely way that a user would purchase an upgrade, Apple held the app&rsquo;s updates hostage in order to gain full compliance from Automattic.</p>



<p>&ldquo;There are a few convoluted ways you can get to our web app from within previews, documentation, etc.,&rdquo; Mullenweg said in the Twitter conversation. &ldquo;We offered to block based on user agent server-side, but that was not deemed sufficient.&rdquo;</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Update: <a href="https://t.co/aCqKGxE7qL">https://t.co/aCqKGxE7qL</a></p>&mdash; Matt Mullenweg (@photomatt) <a href="https://twitter.com/photomatt/status/1297334622506737664?ref_src=twsrc%5Etfw">August 23, 2020</a></blockquote>
</div>



<p>In a rare congenial response from Apple, the company apologized and reversed course 24 hours later, but not before Automattic had already acquiesced to adding in-app purchases. In a statement provided to <a href="https://www.macrumors.com/2020/08/21/wordpress-ios-app-apple-blocked-updates/">MacRumors</a>, Apple said the issue has been resolved, although it did not specify if this happened weeks ago:</p>



<blockquote class="wp-block-quote"><p><em>We believe the issue with the WordPress app has been resolved. Since the developer removed the display of their service payment options from the app, it is now a&nbsp;free stand-alone app and does not have to offer in-app purchases. We have informed the developer and apologize for any&nbsp;confusion that we have caused.</em></p></blockquote>



<h2>The Official WordPress Apps Need to Be Separate from Automattic&rsquo;s Commercial Interests</h2>



<p>Automattic&rsquo;s control of WordPress&rsquo; official mobile apps has long been a controversial issue in the open source community. Since the company heavily subsidizes the apps&rsquo; development, its agenda for the apps goes completely unrivaled. This is why the official apps contain WordPress.com and Jetpack-specific features that are unnecessary for many self-hosted site owners.</p>



<p>Although the apps are open source, historically, they have <a href="https://wptavern.com/wordpress-for-android-5-7-adds-path-to-upgrade-wordpress-com-plan">rarely received contribution</a> from developers outside Automattic due to the complexity of the code. <a href="https://twitter.com/danroundhill/status/1296941098393190401">This hasn&rsquo;t changed</a>. In 2016, when <a href="https://apps.wordpress.com/2016/08/26/wordpress-for-android-version-5-7/">version 5.7 of the apps came out for iOS</a> and Android, it looked like Automattic was pushing forward on building <a href="https://wptavern.com/wordpress-for-android-5-7-adds-path-to-upgrade-wordpress-com-plan">an upgrade path for WordPress.com plans</a>. At that time, features for self-hosted sites began to lag behind significantly. Automattic mobile engineer Maxime Biais said the commitment to support both was equal.</p>



<p>&ldquo;WordPress.com features are not prioritized over self hosted,&rdquo; he said. &ldquo;When we can implement things for both we do it, but when we can&rsquo;t (like when we don&rsquo;t have the XMLRPC endpoint) we do it for WordPress.com and usually ask Core to do the changes so we can implement the same feature for self-hosted users.&rdquo;</p>



<p>Developing the app for self-hosted users and Automattic&rsquo;s customers at the same time was always a delicate balance. This situation with the App Store underscores the need for the official open source apps to be separate from the control of any commercial entity, but the reality is that these apps would not exist without Automattic. Their continued maintenance is entirely funded by the company. Attracting outside contributions from the broader community has been difficult. Matt Mullenweg said no company has ever submitted contributions for having their products built into the apps, despite invitations and the code bases being open source.</p>



<p>Prior to Apple backing off of its requirement for Automattic to add in-app purchases, the company had presumably exhausted every other option before giving in to Apple&rsquo;s demands. At that point Mullenweg started crowd sourcing ideas from his followers on Twitter to look for a way forward for the community. This seemed to mark a new era for the apps where Mullenweg was willing to consider adding other companies&rsquo; products into the apps alongside his own and then passing the revenue along.</p>



<p>&ldquo;New name: The app has always done a ton of work to support WordPresses hosted anywhere, using the XML-RPC API included in core WP since WP 2.6 was released in 2008,&rdquo; he said. &ldquo;That&rsquo;s why we called it &lsquo;WordPress&rsquo; and not &lsquo;WordPress.com&rsquo; or &lsquo;Jetpack.&rsquo;</p>



<p>&ldquo;I am a big believer in the sanctity of licenses. (Open source relies on licenses and copyright.) We agreed to this license when we signed up for (and stayed in) the app store, so going to follow and abide by the rules. Not looking to skirt it, hence doing what they asked us to.</p>



<p>&ldquo;Allow others IAP: All of the code is open source, if other hosts or plugins wanted to support in-app purchases for their plans we could accept patches and have Automattic pass through the revenue.&rdquo;</p>



<p>The idea of Automattic becoming the arbiter of which companies have access to selling through the official mobile apps introduces even more conflicts of interest into what was already a murky entanglement. This setup would be wholly objectionable to many in the open source community. For the sake of clarity and simplicity, WordPress&rsquo; official mobile apps need to be free from commercial interests.</p>



<p>John James Jacoby suggested Automattic build a new app for its own products if the company wants to add in-app purchases. Mullenweg seemed open to considering the idea.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">We can do that but would probably need to spin up new app under a new developer account, and disable webviews.</p>&mdash; Matt Mullenweg (@photomatt) <a href="https://twitter.com/photomatt/status/1296915015845388288?ref_src=twsrc%5Etfw">August 21, 2020</a></blockquote>
</div>



<p>At the moment, given Apple&rsquo;s apology, the liberation of the mobile apps is no longer a matter of immediate necessity. Mullenweg seems satisfied with the outcome for now, but the original conflicts of interest in the app remain.</p>



<p>&ldquo;I did not expect the previous tweet to get attention outside the WP community,&rdquo; Mullenweg said. &ldquo;My understanding was the previous decision was final, and we had already made many of the arguments people suggested privately over the several weeks the app was locked.</p>



<p>&ldquo;We will continue to be responsive and do our best to be within both the spirit and letter of the app store rules, including closing any webview loopholes that pop up. This also made me appreciate the freedom of the open and independent web.&rdquo;</p>



<p><strong>CORRECTION:</strong> <em>At the time of publishing, this article incorrectly stated that Automattic is the only company whose products are allowed to be built into the official WordPress apps. The previous statement has been removed and updated to reflect the fact that no company has ever tried to submit their products for inclusion in the apps, despite invitations.</em></p>



<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 24 Aug 2020 23:53:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:24;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:67:"WPTavern: New Plugin Displays WordPress Environment Type for Admins";s:7:"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=103676";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:179:"https://wptavern.com/new-plugin-displays-wordpress-environment-type-for-admins?utm_source=rss&utm_medium=rss&utm_campaign=new-plugin-displays-wordpress-environment-type-for-admins";s: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:3118:"<p>One of the minor but useful additions to WordPress 5.5 is the new <code><a href="https://make.wordpress.org/core/2020/07/24/new-wp_get_environment_type-function-in-wordpress-5-5/">wp_get_environment_type()</a></code>&nbsp;function. It makes it possible for plugin and theme authors to do some interesting things based on whether a site is identified as staging, development, production, or some other custom environment type. In discussion on the original trac ticket, Marius Jensen suggested a few ways this function could be useful: </p>



<ul><li>It&rsquo;s a function used for grabbing the current environment, this is to ensure everyone fetches the values the same way (to avoid using different terms and such).</li><li>Outbound emails could be filtered, and if&nbsp;<code>get_environment()</code>&nbsp;isn&rsquo;t set to&nbsp;<code>production</code>&nbsp;then send them to the developer, allowing for legitimate email tests in stage setups without worrying about emails reaching end users.</li><li>API endpoints where you want to use a test endpoint when not in production to prevent data pollution.</li><li>Providing a wp-admin notice for non-production sites so it&rsquo;s much clearer that what you are doing now will/won&rsquo;t affect the site your business relies on.</li></ul>



<p>The new function is already getting put to use in WordPress developer Roy Tanck&rsquo;s new plugin called <a href="https://wordpress.org/plugins/display-environment-type/">Display Environment Type</a>. It adds a prominent red notice to the top of the admin for Production. Custom environment types will be set to blue with a lightbulb icon. (The colors used in the plugin are fixed and not configurable to help avoid confusion across servers.)</p>



<img />



<p>The environment type only displays for admin users. Tankck&rsquo;s plugin also adds the current environment type to WordPress&rsquo; At-a-glance widget:</p>



<img />



<p>This is the first plugin on WordPress.org to make use of the new function, but developers are planning to use in other unique ways.</p>



<p>&ldquo;We are adding our own custom environment vars here at Pantheon so plugin authors have the option of doing this but it would be so nice to have this in core so plugin authors don&rsquo;t need to write host specific code,&rdquo; Pantehon developer advocate John Richards commented on the original ticket for the new function.</p>



<p>WordPress plugin developer Rene Hermenau said he will be implementing this new concept in his <a href="https://wordpress.org/plugins/wp-staging/">WP Staging</a> plugin in the next update. WP Staging, which is currently active on more than 50,000 installs, allows users to quickly create an exact copy of their sites for staging or development purposes. </p>



<p>WordPress.com has also <a href="https://lobby.vip.wordpress.com/2020/08/20/environment-type-support/">added support for environment types</a> in VIP Go, allowing developers to run different code for their sites depending on if it&rsquo;s in production, development, or any other custom environment type configuration.</p>



<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 21 Aug 2020 21:16:26 +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:25;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:76:"WPTavern: WordPress: A Year in Review, New Project to Fill the WordCamp Void";s:7:"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=103672";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:193:"https://wptavern.com/wordpress-a-year-in-review-new-project-to-fill-the-wordcamp-void?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-a-year-in-review-new-project-to-fill-the-wordcamp-void";s: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:6439:"<p class="has-drop-cap">Joe Casabona, a freelance web developer and educator, launched <a href="https://wpyearinreview.com/">WordPress: A Year in Review</a> last week. The project was born out of his passion for helping others and a longing for attending WordCamp US, which <a href="https://wptavern.com/wordcamp-us-2020-canceled-due-to-pandemic-stress-and-online-event-fatigue">has been canceled</a> because of the stress of the pandemic and online event fatigue. He wanted to do something to fill in the void.</p>



<p>His goal is to offer online content that members of the WordPress community may have missed out on in the year. The project will provide learning resources in e-book, print book, video, and audio form. The content will be free, but he is asking community members to chip in and sponsor the project, covering the hard costs of putting it together.</p>



<p>&ldquo;After WordCamp US got canceled, I started thinking about all of the work that went into it and the amazing amount of content that now wouldn&rsquo;t be created,&rdquo; said Casabona of why he decided to begin this project. &ldquo;I am a big WordCamper and go to between 7-10 per year depending on my schedule, so I&rsquo;ve definitely missed that experience. My main hope is that this can fill in some of the missing content from those canceled WordCamps. I know there are other efforts too, like the workshops the WordPress Foundation is hosting.&rdquo;</p>



<h2>What the Project Offers</h2>



<p class="has-drop-cap">The plan for the project is to offer three types of content to the WordPress community for free:</p>



<ul><li>An e-book that reviews how WordPress changed in 2020, including a print edition.</li><li>An interview series with WordCamp speakers.</li><li>A video tutorial series that focuses on new things added to WordPress in 2020.</li></ul>



<p>Casabona plans to run between 15 and 20 interviews with people on a special series via his How I Built It podcast. Instead of a formal talk, he wants to provide interviewees an opportunity to explore their own topics. The <a href="https://howibuilt.it/wcus-2020-interviews/">interview application</a> process is open to those who were scheduled to speak at the canceled WordCamp US through August 31.</p>



<p>&ldquo;The interview series was the first aspect of this project that I thought of,&rdquo; he said. &ldquo;Basically, I will interview people who applied to speak at WCUS 2020 about their talks &mdash; each episode will have 3 interviewees who have the opportunity to talk for about 10 minutes each about their topic. I&rsquo;ll ask them who they are, what their talk was going to be about, and highlight the main points. I&rsquo;m definitely open to ideas depending on who applies and how many people apply.&rdquo;</p>



<p>Currently, Casabona has booked only a few podcast interviews. He said he plans on reaching out to more contributors, depending on how funding goes and the finalized outline for the e-book and videos.</p>



<p>He got the idea for the e-book from <a href="https://www.macstories.net/">MacStories</a>. &ldquo;Every year, Federico Viticci puts out an iOS review in conjunction with the iPhone release, exclusively for his members,&rdquo; he said. &ldquo;I think that&rsquo;s such a great resource and feel something like it would really benefit the WordPress community. Since this is the first one I might have some backstory, but it will mainly be a practical reference for people wondering how the popular CMS changed from January to December &mdash; things they might have missed or overlooked.&rdquo;</p>



<p>If the e-book goes well this year, he will seek to publish it in the following years. The same would hold true for the printed book, which would essentially be the same as the e-book. A print edition would be a nice keepsake for members of the WordPress community. It is something physical, a tangible item that is not made up of bytes stored on a computer, destined for an eventual digital waste bin.</p>



<p>Casabona plans to run 10 video tutorials. He will release one video each week, starting in mid-October, through the end of the year. At the moment, he is planning to run all of the videos himself but may reach out to others who are better-suited for particular topics.</p>



<p>&ldquo;The video series isn&rsquo;t a huge departure from the content I put on my YouTube channel right now,&rdquo; he said. &ldquo;I&rsquo;m targeting mostly users and implementors, but there were some cool developer additions in 5.5.&rdquo;</p>



<h2>Funding and the Future</h2>



<p class="has-drop-cap">The biggest holdup for the project is funding. Casabona has a goal of $3,000 to cover the hard costs, such as transcripts, editing, and out-of-pocket expenses. Those willing to donate can give a custom amount or make a pledge for one of three tiers  with each tier building upon the other:</p>



<ul><li><strong>Support &ndash; $5:</strong> Gets your name in the e-book, progress updates, and behind-the-scenes content.</li><li><strong>Early Access &ndash; $5:</strong> Early draft of the e-book, early access to interviews and videos, and e-book of podcast transcripts.</li><li><strong>IRL! &ndash; $19:</strong> A printed copy of the e-book.</li></ul>



<p>&ldquo;I basically wanted to give the community a chance to pledge and support the project, as well as get a print book if they want it,&rdquo; said Casabona.</p>



<p>He is also asking for <a href="https://wpyearinreview.com/sponsor/">sponsors</a> to help fund the project on top of the initial goal of $3,000, which would only cover the minimum to produce content on his own. &ldquo;Sponsorship will allow me to put more of my time and resources into the project,&rdquo; he said. &ldquo;All of this money is going into production &mdash; the more funding I&rsquo;m able to secure, the more time and resources I can put behind it. For example, this could enable me to hire contributors, editors for each medium, etc.&rdquo;</p>



<p>While it may be a bit early, Casabona is already thinking about the future of the project and has plans if he exceeds his funding goals.</p>



<p>&ldquo;Excess funding will allow me to find and pay more contributors and better position the project for 2021,&rdquo; he said. &ldquo;I&rsquo;d also like to set up a fund to send someone who can&rsquo;t afford it to a WordCamp&hellip;once we start having in-person events again!&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 21 Aug 2020 20:09:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:26;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s: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:134:"WPTavern: WordPress Documentation Team Discusses Modifying External Linking Policy Following Opposition to the Ban on Commercial Links";s:7:"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=103625";s:7:"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:313:"https://wptavern.com/wordpress-documentation-team-discusses-modifying-external-linking-policy-following-opposition-to-the-ban-on-commercial-links?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-documentation-team-discusses-modifying-external-linking-policy-following-opposition-to-the-ban-on-commercial-links";s: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:4311:"<p>Last month the WordPress Documentation Team <a href="https://wptavern.com/wordpress-documentation-team-bans-links-to-commercial-websites">announced a ban</a> on links to commercial websites within the official docs. These include the&nbsp;<a href="https://wordpress.org/support/">HelpHub</a>,&nbsp;<a href="https://developer.wordpress.org/reference/">Code Reference</a>,&nbsp;<a href="https://developer.wordpress.org/plugins/">Plugin</a>&nbsp;and&nbsp;<a href="https://developer.wordpress.org/themes/">Theme</a>&nbsp;Developer Handbooks,&nbsp;<a href="https://developer.wordpress.org/block-editor/">Block Editor Handbook</a>, and&nbsp;the <a href="https://developer.wordpress.org/apis/">Common APIs Handbook</a>. The reason behind the ban was that heavily policing commercial links placed too much responsibility on the documentation team, when they are already working with limited time and resources.</p>



<p>The decision was instantly controversial, igniting a heated discussion in the comments. A blanket ban on links to commercial sites, without a clear outline of what that includes, was confusing. </p>



<p>&ldquo;There isn&rsquo;t clarity what will/won&rsquo;t be allowed, you state that the rules are expected to change in the future (more lax after some trial and error), and end users lose in the end as a result of excluding&nbsp;<em>actually helpful information</em>&nbsp;because it&rsquo;s&nbsp;free but at a domain that has non-free content,&rdquo; Core contributor Clifford Paulick commented on the ban announcement.</p>



<p>The level of opposition seemed to indicate that there may not have been enough discussion up front and that other branches of the WordPress contributor community, including commercial entities who are also contributors, were not considered.</p>



<p>&ldquo;Discussion on [the] external linking policy is going in the way we wanted to avoid,&rdquo; Milana Cap said during the July 13th docs team meeting. &ldquo;I was thinking to explore a different approach.&rdquo; She gave more background on why the team is reconsidering the ban:</p>



<blockquote class="wp-block-quote"><p>The reason we didn&rsquo;t want to allow &lsquo;commercial&rsquo; links is to avoid abuse and make it &lsquo;fair&rsquo; for everyone and not promote any product. We also wanted to save time for our members in a matter of maintenance and sort of automate the process. The further and deeper discussion goes I&rsquo;m realizing this will not be possible. It won&rsquo;t be fair, we won&rsquo;t save time because we&rsquo;ll have to do through discussion every time someone suggest &lsquo;commercial&rsquo; link and I&rsquo;m pretty sure we&rsquo;ll never come to agreement on what&rsquo;s &lsquo;commercial.&rsquo; Personal blogs, services, products.. all of it is mixed now. So my suggestion is to allow them all, make process transparent and set strict rules about the actual &lsquo;content.&rsquo;</p></blockquote>



<p>A Google <a href="https://docs.google.com/document/d/1i0ipOTmKPShSIMoFuEXnI3gkOOUrPJb9t4HMf30JWC0/edit?usp=sharing">document</a> is now home to a collaborative effort on a new policy that Cap says is &ldquo;fundamentally different from&nbsp;previous discussions.&rdquo; The new approach proposes a set of criteria for allowing external links, banning things such as product promotion within the tutorial, affiliate links, paywalls, and tracking. The specific criteria and wording of the new policy are still under active discussion.</p>



<p>Sometimes it pays to speak up, if you have a strong opinion about a decision. Reconsideration of this external linking policy is the direct result of feedback on the initial controversial decision, even after it seemed to be final. This may result in a better solution for all stakeholders involved in this discussion. </p>



<p>Next week the Documentation Team will be hosting a Zoom call to discuss the <a href="https://docs.google.com/document/d/1i0ipOTmKPShSIMoFuEXnI3gkOOUrPJb9t4HMf30JWC0/edit?usp=sharing">proposal</a> they have been collaborating on in Google docs. This meeting is for anyone who is interested, not just Documentation team members. If you want to get in on the discussion, check out the <a href="https://doodle.com/poll/v8yy7auidw3mm6q2">Doodle poll</a> for the proposed dates and times.</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, 20 Aug 2020 23:37: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:27;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:96:"WPTavern: No Minimum PHP Version Bump This Year, WordPress to Support PHP 5.6 for a While Longer";s:7:"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=103611";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:235:"https://wptavern.com/no-minimum-php-version-bump-this-year-wordpress-to-support-php-5-6-for-a-while-longer?utm_source=rss&utm_medium=rss&utm_campaign=no-minimum-php-version-bump-this-year-wordpress-to-support-php-5-6-for-a-while-longer";s: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:6967:"<blockquote class="wp-block-quote"><p>We should be leading the users, not following them.<br />We should be guiding the users, not coddling them.<br />We should carve out the road to the future, not continue to fix a broken road to the past.<br />We should say what we do and do what we say.</p></blockquote>



<p>Juliette Reinders Folmer wrapped up her final thoughts on a <a href="https://core.trac.wordpress.org/ticket/51043">ticket she had opened</a> a mere three days ago. She had opened the ticket in anticipation of movement on WordPress&rsquo;s minimum supported version of PHP. She had opened it after seeing the plan to no longer support PHP 5.6 in the <a href="https://make.wordpress.org/core/2020/08/13/wordpress-5-6-release-planning/">WordPress 5.6 release plans</a> (note that initial release plans are not necessarily set in stone).</p>



<p>There is no denying the symmetry of dropping support for PHP 5.6 with the release of WordPress 5.6. Fate seemed to be calling down, saying that it was time to move past the platform&rsquo;s support of a version that reached End of Life in December 2018. It would be a nice sendoff, a farewell that could usher in a new era of maintaining some semblance of staying up to date with the latest and greatest the programming language has to offer.</p>



<p>But the excitement was cut short. WordPress developers, especially those who have longed for WordPress to be more proactive in updating its PHP requirements, will have to continue pushing for modernization into 2021. It does not look like it will happen this year.</p>



<p>Matt Mullenweg, WordPress co-founder and project lead, <a href="https://core.trac.wordpress.org/ticket/51043#comment:7">closed the ticket</a> a few short hours after its opening. &ldquo;Just so we don&rsquo;t cherry-pick stats to make a point, it&rsquo;s worth noting that the PHP distribution across all WP sites we track is the same as when that post was made in 2018: 85% are 5.6 or above,&rdquo; he wrote. &ldquo;Only about 66% are 7.1 and above.&rdquo;</p>



<p>WordPress has required a minimum of PHP 5.6 since its version 5.2 release. Of the WordPress installs on versions 5.2 through the current 5.5 only 10.69% of those are running PHP 5.6, according to Sergey Biryukov, a core committer for WordPress. This percentage is even lower than when the team flipped the switch to PHP 5.6+.</p>



<p>&ldquo;Given that we&rsquo;re still releasing security updates for WP 3.7 (released almost 7 years ago), it&rsquo;s not like we&rsquo;re leaving PHP 5.6 or 7.0 users without security updates, they just won&rsquo;t have some latest and greatest features of WP 5.6+, which seems fair,&rdquo; <a href="https://make.wordpress.org/core/2020/08/13/wordpress-5-6-release-planning/#comment-39483">he said in the comments</a> on the WordPress 5.6 announcement.</p>



<p>&ldquo;This is <em>obviously</em> a key philosophical decision that should be made by the project lead,&rdquo; <a href="https://twitter.com/nacin/status/1296323839379402752">tweeted</a> lead developer Andrew Nacin. &ldquo;And for what it&rsquo;s worth, our philosophies and standards on this have been consistent for more than a decade. The numbers strongly suggest it&rsquo;s too early to drop PHP 5.6.&rdquo;</p>



<p>While there are certainly arguments to looking at the data in different ways, one of WordPress&rsquo;s guiding philosophies has been making the platform accessible to as many users as possible over the years. This has meant taking a slow, deliberate approach while also reaching out to web hosts and users alike. Dropping support for old versions of PHP has not been nearly as fast as some &mdash; including me &mdash; would like.</p>



<p>The need for updating the minimum version of PHP is not simply about developers wanting to use the newest and shiniest tools. There are practical concerns. PHP 8.0 is slated for release on November 26, 2020. Regardless of WordPress&rsquo;s minimum required version, it must also work with the most up-to-date version of PHP. The wider the range of versions that the platform supports, the harder it is to test.</p>



<p>Such is the case with PHPUnit, a testing framework for PHP applications like WordPress. PHPUnit 8 supports a minimum of PHP 7.2.  Technically, it has syntax that requires PHP 7.1 &mdash; hence, the need for the WordPress version bump.  PHPUnit 9 requires a minimum of 7.3 and is necessary for testing PHP 8.0 compatibility. There is an <a href="https://core.trac.wordpress.org/ticket/46149">open ticket</a> for solving issues with PHPUnit testing where the team is exploring options to support the range of PHP versions.</p>



<p>&ldquo;We also need to work on our messaging around these PHP and core upgrades, so we don&rsquo;t cry wolf and cause these notices to be ignored,&rdquo; continued Mullenweg in his explanation for closing the ticket, pointing to the current site health messaging in WordPress. &ldquo;They do not say what version it is currently on. They do not provide a good way to contact the host. They do not give accurate information about security, as most hosts run backports that patch security on older versions separate from what is officially supported by the core PHP project. These are not free upgrades, and I think the cost vs what we are able to deliver to users, vs the hard caused by leaving so many people behind, needs to be seriously weighed. Right now it feels like we&rsquo;re a bit trigger happy on these requirements, and I&rsquo;d even be open to rolling some back.&rdquo;</p>



<p>WordPress may be joked about in &ldquo;real&rdquo; programming circles. Its reliance on outdated tools may be the punchline from developers who are building sites with the <em>Next Big Thing</em>. However, maybe in spite of or maybe because of the platform&rsquo;s reluctance to quickly drop support for older versions of PHP, it has swallowed up 38% of the web. Any project lead would question meddling too much with its leave-no-users-behind formula that was part of the journey getting here.</p>



<p>It is a tough call for a project lead to make. It is also tough because developers like Folmer have put a ton of work into PHP coding standards tools and do the often thankless job of advocating for pushing WordPress into modern-day coding practices.</p>



<p>WordPress is in a position where it has some leverage. If the software demands an upgraded PHP experience, it can put its massive user base to work by forcing web hosting companies to cater to their needs. Money talks, and if enough users begin looking for greener pastures, perhaps those web hosts will make some adjustments. That is at least the theory that some in the community share. &ldquo;If there are no consequences to user/host (in-)action, why would they ever bother to take action?&rdquo; asked Folmer.</p>



<p>It is also a gamble that the WordPress project does not look to be taking, at least for the version 5.6 release.</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, 20 Aug 2020 20:13:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:28;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:74:"WPTavern: WooCommerce 4.4 Updates Blocks and Centralizes Coupon Management";s:7:"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=103580";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:193:"https://wptavern.com/woocommerce-4-4-updates-blocks-and-centralizes-coupon-management?utm_source=rss&utm_medium=rss&utm_campaign=woocommerce-4-4-updates-blocks-and-centralizes-coupon-management";s: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:3507:"<p class="has-drop-cap">Yesterday, Automattic <a href="https://woocommerce.wordpress.com/2020/08/18/woocommerce-4-4-is-now-available/">dropped version 4.4</a> of its popular WooCommerce plugin. The new release is a minor update with the biggest changes around the plugin&rsquo;s blocks and coupon management in the admin. Two dozen people made 450 contributions to the release.</p>



<p>The WooCommerce team brought several updates to the plugin&rsquo;s blocks. The biggest user-facing change is that the blocks will now use the WooCommerce thumbnail size instead of loading the full-sized image. This change means that images will respect the product image size settings that users can set via the WooCommerce &gt; Product Images section in the customizer. This change will make sites using blocks more performant.</p>



<p>The block editor should be slightly speedier with this update. The team removed front end scripts that were not needed from the post-editing screen.</p>



<p>WooCommerce also updated its flagship theme, Storefront, yesterday. There is nothing in the <a href="https://woocommerce.wordpress.com/2020/08/18/storefront-2-6-0-release-notes/">release notes</a> to suggest that the update corresponds with changes in WooCommerce 4.4, but it is a good idea for users to stay updated regardless.</p>



<h2>Coupon Management Moved to the Marketing Hub in the Admin</h2>



<img />WooCommerce Coupons admin screen.



<p class="has-drop-cap">In WooCommerce 4.1, the team added a new Marketing section in the WordPress admin. When it was initially launched, some users felt like WooCommerce had added a top-level menu item for little more than the purposes of upselling its extensions. The single admin screen also offered links backed to the WooCommerce knowledge base. Many comments on the <a href="https://woocommerce.wordpress.com/2020/03/31/coming-soon-woocommerce-marketing-hub/">launch of the marketing hub</a> asked the team to reconsider making it a top-level menu item, at least until it offered something more than upsells and links back to the WooCommerce website.</p>



<p>Having a centralized marketing location in the WordPress admin makes sense for eCommerce websites though. Creating an online shop is only one part of the process. Successful stores need to have a marketing focus, and WooCommerce is seeking to create an experience that helps more store owners become successful.</p>



<p>While it is a minor change, <a href="https://woocommerce.wordpress.com/2020/07/09/centralized-coupon-management-available-for-testing/">moving the coupons screen</a> to the marketing hub makes sense. For those end-users who make use of coupons, it should very much be a part of their marketing plan.</p>



<p>WooCommerce 4.4 still has the legacy coupons screen beneath the standard WooCommerce menu. However, clicking on the old link will generate an admin notice that migrates users to the new location. The notice provides a button to remove the legacy admin menu item.</p>



<p>Gary Murray, the Product Focus and Lead for WooCommerce, said the team had larger plans beyond the initial marketing hub in the announcement post. Coupons are merely a second stage in the longer-term roadmap. &ldquo;Think automations, campaigns, customer segmentation, coupon management, marketing focused analytics, and reporting,&rdquo; he wrote. While the roadmap for the marketing hub is not public, it will be interesting to see what tools the team adds in future iterations of the plugin.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 19 Aug 2020 21:13: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:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:29;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:72:"WPTavern: Enable jQuery Migrate Helper Plugin Passes 10K Active Installs";s:7:"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=103537";s:7:"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:189:"https://wptavern.com/enable-jquery-migrate-helper-plugin-passes-10k-active-installs?utm_source=rss&utm_medium=rss&utm_campaign=enable-jquery-migrate-helper-plugin-passes-10k-active-installs";s: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:4207:"<p>In just one week since WordPress 5.5 was released, the <a href="https://wordpress.org/plugins/enable-jquery-migrate-helper/">Enable jQuery Migrate Helper</a> plugin has passed 10,000 active installs, as users look for a fix for broken sites. The plugin was developed by the WordPress Core team to mitigate jQuery-related problems users may face after updating to 5.5. WordPress has removed jQuery Migrate 1.4.1, but many themes and plugins are now broken because they use outdated/deprecated jQuery functions that relied on the script. </p>



<p>The official support forums are inundated with <a href="https://wordpress.org/search/5.5?in=support_forums">reports of broken sites</a> after updating to 5.5, as most users who don&rsquo;t follow core development are not aware that jQuery Migrate has been deprecated. Because it&rsquo;s related to jQuery, many of the sites have very visible problems or broken functionality that prevents users from doing things like viewing and editing content. Those who are still using the Classic Editor have been particularly <a href="https://wordpress.org/support/topic/5-5-classic-editor-text-view-add-media-not-working/">hardest hit by the 5.5 update</a>, since older plugins that hook into the old editor are more likely to be using deprecated jQuery functions. </p>



<p>The Enable jQuery Migrate Helper plugin has racked up 34 five-star reviews, as it instantly fixes most users&rsquo; problems:</p>



<blockquote class="wp-block-quote"><p>&ldquo;After updating to 5.5 my hero slider images disappeared and this plugin fixed the problem immediately.&rdquo;</p><p>&ldquo;After updating to WordPress 5.5 my edit a post page and several other things ended up breaking despite having all plugins and my theme updated. This plugin fixed my issue!&rdquo;</p><p>&ldquo;As a newspaper, not being able to see the content of our posts is a pretty big deal. This fixed it. Thank you.&rdquo;</p></blockquote>



<p>The plugin gives users time to figure out which themes or plugins are causing the problems and request the authors of those extensions to update them for compatibility with the latest version of WordPress.</p>



<p>One user, David Halchester, reported a problem with a <a href="https://wordpress.org/support/topic/navigation-menu-vanishes/">vanishing navigation menu</a> to the support forums before discovering the Enable jQuery Migrate Helper plugin. </p>



<p>&ldquo;Voila,&rdquo; Halchester said in his <a href="https://wordpress.org/support/topic/enable-jquery-migrate-helper/">review</a>. &ldquo;It worked like magic. My beautiful custom page is working again. That said &mdash; if WP does not want to lose customers, it needs to make sure its updates are compatible with older sites.</p>



<p>&ldquo;Thank you to the people who created this plug-in. I just saved myself about $300 or more in fees to have someone &lsquo;fix&rsquo; it.&rdquo;</p>



<p>He makes a solid point about the plugin saving users&rsquo; money that might otherwise have gone to developers to fix the problem. For those who discover the plugin as a fix, it only costs them the time and frustration of seeking help from their hosting company or volunteers on the support forums. Others who may not be as persistent will likely have to pay for professional troubleshooting.</p>



<p>Justin Tadlock published a <a href="https://wptavern.com/major-jquery-changes-on-the-way-for-wordpress-5-5-and-beyond">post</a> last week that outlines WordPress&rsquo; three-stage plan for updating jQuery to the latest version.  The plan outlines how a new version of jQuery Migrate will be added in WordPress 5.6 to help users update from jQuery 1.12.4 to 3.5.1 (or later). The tentative plan is to remove the script once more in WordPress 5.7, which is expected in 2021.</p>



<p>In the meantime, the Enable jQuery Migrate Helper plugin functions as a temporary bandaid. Looking ahead towards the prospect of opt-in automatic updates for major Core releases, which is expected to land in WordPress 5.6, it will be important to consider how wide-reaching these breaking changes can be along to path to updating jQuery, especially for those hanging back with the Classic Editor plugin. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 19 Aug 2020 05:11:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:30;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:26:"Matt: Second-Order Effects";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=52013";s:7:"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:43:"https://ma.tt/2020/08/second-order-effects/";s: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:1234:"<p><a href="https://www.theatlantic.com/author/derek-thompson/">Derek Thompson&#8217;s writing for the Atlantic</a> has been some of the most interesting this year. His latest, <a href="https://www.theatlantic.com/ideas/archive/2020/08/just-small-shift-remote-work-could-change-everything/614980/">The Workforce Is About to Change Dramatically</a>, is worth a close read. He gives good arguments for and against how remote working will change real estate, entrepreneurship, and something I&#8217;ve been meaning to write about but he did a much better job, how the <a href="https://www.theatlantic.com/ideas/archive/2019/09/american-migration-patterns-should-terrify-gop/598153/">great migration happening away from superstar cities could reshape politics</a>. </p>



<p>I sincerely hope that all the people <a href="https://www.usa.gov/change-voter-registration">moving to new places are registering to vote in their new home</a>, as I did when I moved from San Francisco back to Houston in 2011. The following year was 2012 and in Harris County (Houston) with 4.263 million people, Obama <a href="https://www.politico.com/2012-election/results/president/texas/">won</a> by <strong>585 votes</strong>. I was one of those votes.</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, 18 Aug 2020 21:15:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;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:66:"WPTavern: WP Rig Starter Theme Project Looking for New Maintainers";s:7:"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=103406";s:7:"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:177:"https://wptavern.com/wp-rig-starter-theme-project-looking-for-new-maintainers?utm_source=rss&utm_medium=rss&utm_campaign=wp-rig-starter-theme-project-looking-for-new-maintainers";s: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:9640:"<img />



<p class="has-drop-cap">A couple of years ago, Morten Rand-Hendriksen launched <a href="https://wptavern.com/wp-rig-a-wordpress-starter-theme-and-build-process-in-one">WP Rig for WordPress</a>. The goal was to bring a modern <a href="https://wprig.io/">starter theme and build process</a> to the theme development community. Now, he and the current team are hoping to find someone new to keep the project moving. Whoever is chosen will gain outright ownership of the project.</p>



<p>Rand-Hendriksen will be hosting a <a href="https://linkedin.zoom.us/meeting/register/tJ0rc-mhqj4rGtbwM7UB7NL7_bOY50qkMIJ9">Zoom meeting</a> on Friday, August 21 at 8 am PST. The meeting is planned to last 30 minutes with a possible additional 30 minutes for a Q&amp;A session. He will update the <a href="https://wprig.io/news/">WP Rig blog</a> with the format and agenda for the meeting this week. Anyone interested in WP Rig&rsquo;s future is free to attend.</p>



<p>&ldquo;The ideal candidate is someone who has the interest, time, and drive to keep the project going,&rdquo; said Rand-Hendriksen. &ldquo;Future owners, maintainers, peers, etc. will be expected to adhere to the established <a href="https://github.com/wprig/docs/blob/master/GOVERNANCE.md">governance model</a>, which outlines roles, responsibilities, powers, and how to &lsquo;climb the ladder&rsquo; if you will.&rdquo;</p>



<p>Before taking the reins, candidates will meet with Rand-Hendriksen and other legacy maintainers of the project. The goal is to sort out the logistics of the handover.</p>



<p>&ldquo;Once the project is handed over to new owners and maintainers, the project becomes their project,&rdquo; said Rand-Hendriksen. &ldquo;That means they can take it in whatever direction they feel is meaningful and valuable for the community. This is a true handover: we, the legacy maintainers, are not imposing our view of what WP Rig should be in the future onto the new owners and maintainers. We will impart our knowledge and vision, and let the next generation of the WP Rig team lay down their own path into the future.&rdquo;</p>



<p>Ideally, the official WordPress Themes Team would take on the WP Rig project or at least its own version of a starter theme. However, the team lacks the resources to make it happen. Some members are interested but no one has the time to contribute to it at the moment, according to Themes Team representative William Patton.</p>



<p>&ldquo;If the TRT wants to adopt the project, they take precedence over all other interested parties,&rdquo; said Rand-Hendriksen. &ldquo;The intent of WP Rig was always to donate the project to the larger WordPress Open Source project, and the TRT would be the ideal group to hand the keys to.&rdquo;</p>



<h2>The Unexplored Future of Full-Site Editing</h2>



<p class="has-drop-cap">Whoever takes on the WP Rig project will be in a position to explore the great unknown of full-site editing. An early version of the feature is expected to land in WordPress 5.6 later this year. This could mean overhauling the project and taking it in an entirely new direction than originally envisioned. It is a tall order and will require someone with the time and ability to keep up with drastic changes in the coming months.</p>



<p>Rand-Hendriksen and the team did some experimental work with <a href="https://github.com/wprig/block-areas">Block Areas</a> and <a href="https://github.com/wprig/wprig-blockade">WP Rig Blockade</a>, a variant of the original WP Rig theme that explored blocks outside of the content area. However, the repositories have seen little work in the last year and a half. Rand-Hendriksen said they got too caught up in releasing version 2.0 of WP Rig to see either of those projects come to fruition.</p>



<p>&ldquo;As the WordPress community starts exploring what <em>blocks everywhere</em> means, it is more important than ever to have this unifying base to start from so everyone is talking the same language and using the same tools,&rdquo; he said. &ldquo;When I had to step away, this was my deepest regret: that I wouldn&rsquo;t be part of shaping this next evolution of the platform and wouldn&rsquo;t be able to help the community develop this unifying baseline.&rdquo;</p>



<p>Rand-Hendriksen believes that full-site editing will only be successful with buy-in from the existing theme development community. Without active participation from these developers, full-site editing could split the community into traditional vs. modern theming.</p>



<p>&ldquo;There is a lot of money at stake, and a lot of developers deeply invested in and financially dependent on the status quo of themes,&rdquo; he said. &ldquo;To bring them on board and explore the future of themes, there needs to be a unified baseline to start from, and this is the opportune time to introduce modern code, tools, and standards. WP Rig can be a catalyst for this project and can also be the foundation on which such a project is built. What is it open source evangelists always say? &lsquo;Decisions are made by those who show up.&rsquo; This is a chance to not just show up but actively guide the community into a collaborative future.&rdquo;</p>



<p>He feels like WP Rig&rsquo;s new owners will be in a position to answer one of the questions looming over the WordPress project: <em>What should full-site editing look like?</em></p>



<h2>Modern Tooling</h2>



<p class="has-drop-cap">WP Rig is far more advanced than the starter themes of yesteryear. However, it is not alone. Of the many starter themes available throughout the WordPress development community, many of them have moved on to include modern build systems and tooling that were not a part of earlier projects such as <a href="https://underscores.me/">Underscores</a> (_s), which is the closest thing to an &ldquo;official&rdquo; starter theme project WordPress has ever seen.</p>



<p>&ldquo;When I first came up with the idea of WP Rig, it was because I&rsquo;d been maintaining a very popular LinkedIn Learning (formerly Lynda.com) course on building themes from scratch using _s for years, and I noticed _s and WP themes, in general, were lagging further and further behind the general trends of web development,&rdquo; said Rand-Hendriksen. &ldquo;WordPress themes are by and large still built as if it&rsquo;s 2012, not 2020, and many of the most important advances of the web dev space are not generally in use in theme development. As the project evolved from my personal experiment to a team, we made a decision to start from scratch and say &lsquo;if someone were to build a theme today, in 2018, with today&rsquo;s tools and best practices, what would that look like?&rsquo; The result is a theme building tool using modern build processes and tooling to make theme development easier. Yes, it looks nothing like the standard starter themes, but like I said, the standard starter themes look like the web in 2012.&rdquo;</p>



<p>There is still some sentiment within the WordPress community that web development is shifting too far from its roots of understanding the basics of HTML, CSS, and entry-level PHP. Have we moved past the point where those simple foundations were enough to build WordPress themes in the modern world?</p>



<p>&ldquo;Is this harder to understand for beginners?&rdquo; asked Rand-Hendriksen. &ldquo;If you start from the assumption that anything other than the good old way of building themes is &lsquo;harder,&rsquo; then yes, absolutely. If you start from the perspective of WordPress themes being many people&rsquo;s first hands-on experience with web development, and WordPress having a responsibility to introduce people to current and forward-thinking web tooling, then I think the answer is no.&rdquo;</p>



<p>Rand-Hendriksen says that WP Rig makes many parts of modern theme development much easier and that the more complex pieces are extensively documented. From performance improvements to modern JavaScript to object-oriented PHP, the theme covers a wide range of practices that old-hat theme developers may need to start coming to grips with, sooner rather than later. &ldquo;For most standard theme development, WP Rig is as easy as with any other dev tool,&rdquo; he said. &ldquo;It is just different from how WordPress themes normally do things. Which from my perspective is not only good but necessary if WordPress themes want to stay current with the rest of the web.&rdquo;</p>



<p>WP Rig also gives theme authors a leg up with accessibility out of the box. Rand-Hendriksen has long been a vocal supporter of pushing for accessibility standards in themes, so it makes sense that the starter that he spearheaded approaches development with accessibility at the forefront.</p>



<p>&ldquo;I&rsquo;ve developed themes for 15+ years and taught theme development for over a decade,&rdquo; said Rand-Hendriksen. &ldquo;One of the major roadblocks for theme development is the lack of an official unified tool to start from. _s served that role for a while, but it is now poorly maintained, sluggish in development, and lagging significantly behind where standards and modern tooling is concerned. WordPress needs something similar to <a href="https://reactjs.org/docs/create-a-new-react-app.html">&lsquo;create react app&rsquo;</a>  has had for a long time. WP Rig was created to serve as a base, or as inspiration, for such a project: provide an official starting theme and build process to give people a unified place to work from and a unified base to contribute back to and improve so the community can lift itself up together.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 18 Aug 2020 19:43:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:32;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:128:"WPTavern: Apple to Enforce 1-Year Limit on SSL/TLS Certificate Lifetimes on September 1, 2020, Mozilla and Google to Follow Suit";s:7:"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=103455";s:7:"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:297:"https://wptavern.com/apple-to-enforce-1-year-limit-on-ssl-tls-certificate-lifetimes-on-september-1-2020-mozilla-and-google-to-follow-suit?utm_source=rss&utm_medium=rss&utm_campaign=apple-to-enforce-1-year-limit-on-ssl-tls-certificate-lifetimes-on-september-1-2020-mozilla-and-google-to-follow-suit";s: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:4866:"<img />image credit: &nbsp;<a href="https://stocksnap.io/author/134">Sylwia Bartyzel</a>



<p>Beginning September 1, 2020, Apple&rsquo;s Safari browser will no longer trust SSL/TLS certificates issued for longer than 398 days, which is the equivalent of one year plus the renewal grace period. Apple cited its &ldquo;ongoing efforts to improve web security&rdquo; in the <a href="https://support.apple.com/en-us/HT211025">announcement</a> earlier this year. The change affects the full lineup of Apple platforms: </p>



<blockquote class="wp-block-quote"><p>This change will affect only TLS server certificates issued from the Root CAs preinstalled with iOS, iPadOS, macOS, watchOS, and tvOS. Additionally, this change will affect only TLS server certificates issued on or after September 1, 2020; any certificates issued prior to that date will not be affected by this change.</p></blockquote>



<p>Apple will begin enforcing the change immediately, which means it will deny connections to TLS servers that don&rsquo;t meet the new requirements. After Apple&rsquo;s announcement, both <a href="https://chromium.googlesource.com/chromium/src/+/ae4d6809912f8171b23f6aa43c6a4e8e627de784">Google</a> and <a href="https://github.com/mozilla/pkipolicy/issues/204">Mozilla</a> contributors moved to propose their own implementations that cap certificate validity at 398 days. </p>



<p>All of the major certificate authorities are falling in line, changing their offerings to conform with the new one year limit. This includes CA market leader <a href="https://www.identrust.com/sites/default/files/resources/IdenTrust_TLS_%20One_%20Year_%20Max_Validity_June_2020_Communication_0_0.pdf">IdenTrust</a>, which accounts for roughly <a href="https://w3techs.com/technologies/history_overview/ssl_certificate">52%</a> of SSL certificates. DigiCert, a CA that captures 20% of the market, <a href="https://www.digicert.com/blog/position-on-1-year-certificates/">published</a> a dry note of compliance, emphasizing the burden it places on certificate users:</p>



<blockquote class="wp-block-quote"><p>Why did Apple unilaterally decide to enforce a shorter certificate lifetime? Their spokesperson said it was to &ldquo;protect users.&rdquo; We know from prior CA/B Forum discussions that longer certificate lifetimes proved to be challenging in replacing certificates, in the case of a major security incident. Apple clearly wants to avoid an ecosystem that cannot quickly respond to major certificate-related threats. Short-lived certificates improve security because they reduce the window of exposure if a TLS certificate is compromised. They also help remediate normal operational churn within organizations by ensuring yearly updates to identity such as company names, addresses and active domains. As with any improvement, shortening of lifetimes should be balanced against the hardship required of certificate users to implement these changes.</p></blockquote>



<p>The idea behind the change is that certificates with shorter life cycles are more secure, as compromised keys would expire on shorter timeframes. The new one-year expiration forces hosts and certificate providers to make automation a high priority. In fact, this is one of the reasons Let&rsquo;s Encrypt&rsquo;s free certificates already have a short <a href="https://letsencrypt.org/2015/11/09/why-90-days.html">90-day life cycle</a>. It was put in place years ago to encourage automation so that shorter lifetimes are no less convenient than longer ones.</p>



<p>Let&rsquo;s Encrypt recommends subscribers renew every sixty days and may even consider recommending shorter lifetimes once automated renewal tools are more widely adopted. This may be happening sooner than anticipated now that Apple&rsquo;s policy is forcing change across the industry.</p>



<p>Many WordPress users make use of Let&rsquo;s Encrypt certificates using a plugin like <a href="https://wordpress.org/plugins/wp-force-ssl/">WP Force SSL &amp; HTTPS Redirect</a> (100k+ active installs), <a href="https://wordpress.org/plugins/ssl-zen/">SSL Zen</a> (20k+ installs) or <a href="https://wordpress.org/plugins/wp-letsencrypt-ssl/">WP Encryption</a> (20k+ installs). Some plugins have automatic renewal built in, but some offer it as part of a commercial upgrade. Others rely on hosts to perform renewals.</p>



<p>Although most website owners will not need to take action, the shorter certificate life cycle may can become a hassle without automated certificate management in place. It may also affect client billing with different options available from hosts and certificate authorities. If you manage websites for clients whose sites previously relied on certificates with longer life cycles, you will want to make sure to have some form of automated certificate management set up when the change goes into effect.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 17 Aug 2020 23:08:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;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:85:"WPTavern: Exploring the First Block Patterns to Land in the WordPress Theme Directory";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=103449";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:215:"https://wptavern.com/exploring-the-first-block-patterns-to-land-in-the-wordpress-theme-directory?utm_source=rss&utm_medium=rss&utm_campaign=exploring-the-first-block-patterns-to-land-in-the-wordpress-theme-directory";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7623:"<p class="has-drop-cap">For months, I have eagerly awaited the official release of <a href="https://wptavern.com/wordpress-5-5-eckstine-introduces-block-directory-block-patterns-and-automatic-updates-for-themes-and-plugins">WordPress 5.5</a>, an update that promised to put the long-awaited block patterns system into the hands of theme designers. I may sound like a broken record at this point, but patterns have the potential to <a href="https://wptavern.com/block-patterns-will-change-everything">revolutionize WordPress theme development</a>, even more so than the upcoming full-site editing.</p>



<p>The feature should drastically change how developers create WordPress themes. If used to its full potential, theme authors can rid themselves of dozens of theme options and drop most of their page templates. They can focus less on programming and more on designing, which is what themes are really all about.</p>



<p>To understand why patterns are so revolutionary, you must understand the underlying issue that it solves for theme authors and, ultimately, end-users. Throughout all of WordPress&rsquo;s theming history, there has been a single overarching issue that has caused untold numbers of issues. This is an issue that has been the root cause of multiple guidelines added to the WordPress.org theme review system.</p>



<p>This single issue can almost exclusively trace its roots back to the big question: how can theme authors build custom homepages and easily allow end-users to recreate them?</p>



<p>Whether it is a slider or columns of info boxes or a call-to-action section, WordPress has never truly provided a solution that theme authors could rely on. To be fair, many developers have built creative and unique systems around the limitations of the platform. However, those systems were specific to a single theme or a set of themes from a single company. There was no standard. There was nothing that would guide theme designers to simply design whatever interesting thing they had in their minds and allow users to simply fill in the content.</p>



<p>While I say that the homepage of the site is the underlying issue here, the problem is really extended to any page on the site. The homepage design is a bit like the theme author&rsquo;s signature. It allows designers to showcase their talents and draw users in. And for over a decade, theme authors have tried a thousand different methods just to get this one page right.</p>



<p>Patterns are so much more. The system does not require that theme authors become PHP ninjas to piece together beautiful designs. It does not limit users to a theme options panel for building their homepage &mdash; they can build out any page on their site with the patterns their themes offer.</p>



<p>The big thing is that it renders the &ldquo;how do I build a custom homepage&rdquo; question moot. Theme authors never need to think about that question again, at least not in the way that they have in previous years. Theming is moving away from building designs on a page level and toward designing individual blocks and sections (patterns). The focus is much more <em>atomic</em>, which provides users with more flexibility and freedom.</p>



<p>Because I could not wait for weeks or months longer to see what theme authors built within this system, I wanted to take a peek at what the current themes in the official theme directory were doing. There was not a lot to look at, but at least some theme authors are willing to be the pioneers in this new era of theming.</p>



<p>Currently, the <a href="https://wordpress.org/themes/tags/block-patterns/">Block Editor Patterns</a> feature filter for the directory is not working. Technically, theme authors are not allowed to add the <code>block-patterns</code> tag to their themes, but there is a <a href="https://github.com/WordPress/theme-check/pull/272">patch available</a> which should fix the issue soon.</p>



<h2>Patterns So Far</h2>



<p class="has-drop-cap">Right now, the theme directory only has three themes with block patterns. It is not much to go on, but it is interesting to see what theme authors are building so far.</p>



<p>UXL Themes recently updated its <a href="https://wordpress.org/themes/cordero/">Cordero</a> theme with several blocks. One of the things I like about how Cordero added its patterns is that it created a custom &ldquo;Cordero&rdquo; block pattern category. Patterns can exist in multiple categories, but having all of the theme&rsquo;s custom patterns consolidated to a single group made discovering them much easier. This is a practice that I would like to see more of going forward.</p>



<p>Cordero&rsquo;s patterns are primarily geared toward the typical business layout. It includes a couple of hero-type patterns, some features/services boxes, and pricing tables.</p>



<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>Cordero theme block patterns.



<p>The <a href="https://wordpress.org/themes/inclusive/">Inclusive</a> theme by Themes Team representative Carolina Nymark has several patterns (it is also a solid theme if you&rsquo;re in the market for a good accessibility-ready option). The most interesting patterns of this theme are its two-column patterns with <em>sidebars</em>. Nymark has essentially created the &ldquo;body&rdquo; of a page with patterns. One adds a sidebar on the left and the other pattern adds it to the right. Both patterns have a main column for adding custom content. The sidebar column is decorated with widget-type blocks by default.</p>



<img />Inclusive theme pattern with sidebar and content columns.



<p>What makes these patterns unique is that they are almost like a stepping stone toward full-site editing &mdash; all that they are missing is a header and footer. Admittedly, I was unprepared for this sort of pattern and expected patterns to be used for smaller sections, but I am a fan of the experimentation in the Inclusive theme.</p>



<p>Nymark has two of the current three themes with block patterns in the directory. Her <a href="https://wordpress.org/themes/deejay/">Deejay</a> theme adds a single pattern, which allows the user to create a DJ profile section on their site. It combines columns, social icons, the latest posts list, a video embed, and more.</p>



<img />Deejay theme profile pattern.



<p>Overall, I like the early exploration of this new feature. It is never easy being the first to try things out, so I applaud the theme authors for paving the way. We&rsquo;re only a week into the WordPress 5.5 release, but I am excited to see more.</p>



<h2>How Well Do Patterns Transfer Between Themes?</h2>



<p class="has-drop-cap">One of the promises of the block system is that it allows users to switch between themes and maintain their content. The idea is that each theme will style all the blocks in such a way that the front end output does not look broken.</p>



<p>While there is merely a small sample size of three themes, I did hit some content styling issues when switching between them.</p>



<p>Generally, the more complex a pattern and whether the pattern employs custom classes decides how well it would transfer from theme to theme. Images could present an interesting problem too if the user decides to not replace a pattern&rsquo;s image with its own. Because the image would exist in the theme folder, if the theme is deactivated and uninstalled, it would no longer exist.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 17 Aug 2020 21:24:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;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:74:"WPTavern: WordPress 5.6 Development Kicks Off with All-Women Release Squad";s:7:"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=103314";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:193:"https://wptavern.com/wordpress-5-6-development-kicks-off-with-all-women-release-squad?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-6-development-kicks-off-with-all-women-release-squad";s: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:4051:"<img />photo credit: <a href="https://stocksnap.io/photo/people-girls-N444PJYUP9">Brodie Vissers</a>



<p>WordPress 5.5 has already been downloaded more than 4 million times after its release earlier this week, and it&rsquo;s time to <a href="https://make.wordpress.org/core/2020/08/13/wordpress-5-6-release-planning/">kick off work on 5.6</a>. Josepha Haden will be leading the release alongside coordinator Dee Teal, with additional leads for Triage (Tonya Mork), Core Tech (Helen Hou-Sand&igrave;), Editor Tech (Isabel Brison), Design (Ellen Bauer and Tammie Lister), and several more women managing documentation, accessibility, marketing, testing, and other important aspects of the release. The full squad includes 46 women so far with a couple of roles left to be decided.</p>



<p>When Josepha Haden officially <a href="https://make.wordpress.org/core/2020/03/11/all-women-release-squad/">proposed</a> the idea of having an all-women release squad, she emphasized that this doesn&rsquo;t mean the release can only include contributions from women. In addition to the general objective of shipping a stable and enhanced version of the WordPress, Haden outlined a few more goals for this historic release:</p>



<blockquote class="wp-block-quote"><p>My hope is that with a release squad comprised entirely of people who identify as women, we&rsquo;ll be able to increase the number women who have that experience and (hopefully) become returning contributors to&nbsp;Core&nbsp;and elsewhere. This doesn&rsquo;t mean the release will only contain contributions from women. And if our current squad training process is any indication, it also doesn&rsquo;t mean that we&rsquo;re asking a squad to show up and do this without support.</p></blockquote>



<p><a href="https://profiles.wordpress.org/francina/">Francesca Marano</a>, who worked as release <a href="https://wptavern.com/a-non-technical-release-leads-journey-to-becoming-a-mentor-for-wordpress-core-development">co-lead for WordPress 5.3</a>, published a post announcing the squad as well as the scope of the release. Two major items are already complete: <a href="https://github.com/WordPress/gutenberg/issues/13204">conversion of the widget-editing areas</a> and removal of support for PHP 5.6.x. The squad plans to deliver an impressive array of new features that are still in development:</p>



<ul><li>Navigation menus&nbsp;block&nbsp;in Core</li><li>Automatic updates for major WordPress Core releases (opt-in)</li><li>New features from the block editor upgrades.</li><li>Widgets-editing and&nbsp;Customizer&nbsp;support in Core</li><li>Default theme, including an FSE compatible version</li><li>PHP 8 support</li><li>Public&nbsp;beta&nbsp;of Full Site Editing</li></ul>



<p>A recent <a href="https://twitter.com/kaydacode/status/1293302599542874177">tweet</a> from a woman who works as an iOS developer at Quicken Loans, asked if there have ever been women in software development working in leadership roles. Although many projects and organizations have women in such roles for many years (as seen in the replies to the tweet), the question demonstrates why representation still matters. WordPress 5.6 is an opportunity to make many more women leaders visible for people who need to see others like themselves in leadership roles.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Lead developer for 38% of the internet let&rsquo;s goooooo who else is out there <a href="https://t.co/bCq8iFdf3I">https://t.co/bCq8iFdf3I</a></p>&mdash; Helen &#20399;-Sand&iacute; (@helenhousandi) <a href="https://twitter.com/helenhousandi/status/1293621808088985602?ref_src=twsrc%5Etfw">August 12, 2020</a></blockquote>
</div>



<p>So far the community has been very <a href="https://twitter.com/SergeyBiryukov/status/1294324969133035522">supportive</a> of the plan for an all-women release squad and is rallying around the idea. WordPress 5.6 is the last release planned for the year and is expected to land on December 8, 2020. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 14 Aug 2020 22:17:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;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:49:"WPTavern: Local Avatars in WordPress? Yes, Please";s:7:"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=103361";s:7:"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:139:"https://wptavern.com/local-avatars-in-wordpress-yes-please?utm_source=rss&utm_medium=rss&utm_campaign=local-avatars-in-wordpress-yes-please";s: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:5442:"<p class="has-drop-cap">It is an age-old question. OK, well, it&rsquo;s really a <a href="https://core.trac.wordpress.org/ticket/16020">10-year-old feature request</a>, but that is <em>age-old</em> in software development years. Should WordPress have a local avatar system?</p>



<p>Let&rsquo;s be honest. Most of us have kind of gritted our teeth and quietly &mdash; and sometimes not so quietly &mdash; lived with the Automattic-owned properties that are integrated directly with the core WordPress software. At least Akismet is a plugin and somewhat detached from the platform. But, avatars, a feature courtesy of Automattic&rsquo;s Gravatar service, is baked deep into the platform. Users must disable avatars completely or opt into another plugin to distance themselves from it.</p>



<p>There are the obvious privacy concerns that some people have around uploading an image to the Gravatar service and creating an account with WordPress.com. Even aside from such concerns, regardless of whether they are warranted, new users who are unfamiliar with local avatar plugins are essentially guided to create an account with a third-party service to have one of the most basic features expected from a CMS.</p>



<p>Not all WordPress installs have access to Gravatar, such as within companies that use intranets. Some countries have the power to effectively block access to the service, as shown by the move China made in 2013 to <a href="https://wptavern.com/china-blocks-gravatar-and-wordpress-com-how-to-adjust-wordpress-settings">block WordPress.com and Gravatar</a>, leaving users to seek out alternatives.</p>



<p>The itch that many want to scratch is to simply remove Automattic-connected services from the core software. Gravatar&rsquo;s inclusion in WordPress has hampered any chance of competing services gaining a foothold. To be fair, at the time of Gravatar&rsquo;s initial inclusion in WordPress, there were few good options. It made sense to leverage a working solution that would get an avatar system rolling. And the notion of a globally-recognized avatar is noble &mdash; one service to control your avatar across the web. However, having that service under the control of a for-profit U.S. company will always be an issue that could potentially hold it back from being the service that the web truly needs. It will certainly always be a contentious issue in the WordPress community. Even those of us who love the software and services that Automattic offers can see the problem.</p>



<p>WordPress should be agnostic about what services it includes out of the box. Gravatar should be a separate plugin, even if it is bundled with core <em>a la</em> Akismet. Local avatars is not an insurmountable feature, and it might just be time to make the change.</p>



<p>While possible to build into core, it is not a simple matter of plugging in an image upload form on the user profile screen. The feature carries its own privacy concerns too. For example, uploading images currently requires certain permissions that would also provide the user with access to the entire media library. There is the question of how to deal with registered vs. non-registered users in such a system along with several other hurdles.</p>



<p>Recent chatter in the 10-year-old ticket and the #core-privacy and #core-media Slack channels have <a href="https://wordpress.slack.com/archives/C9695RJBW/p1593630901357300">reignited the idea of local avatars</a>.  There is also an <a href="https://docs.google.com/spreadsheets/d/172jXhfzVFfKfk8M4NXa3e29GlQhZpAaWSxZCrH07_fo/edit#gid=0">early spreadsheet</a> on local avatar requirements and research.</p>



<p>Much of this discussion is amidst the backdrop of the <a href="https://make.wordpress.org/core/2020/04/01/feature-plugin-proposal-wp-consent-api/">WP Consent API</a> proposal, which seeks to create a standardized method for core, plugins, and themes to obtain consent from users. Presumably, Gravatar usage would tie into this API somehow.</p>



<p>Matt Mullenweg, the co-founder of WordPress and CEO of Automattic, seems open to the discussion. &ldquo;It&rsquo;s exciting to see this older ticket picking up so much steam,&rdquo; he said <a href="https://core.trac.wordpress.org/ticket/16020#comment:120">on the Trac ticket</a>. However, he further pushed for a separate featured plugin that focused on broader privacy concerns.</p>



<p>In many ways, local avatars feel like the early days of the web in which users had to upload a custom avatar to every single website they joined. At times, it could be tedious. Gravatar solved this issue by creating a single service for people to bring their avatars along their journey across the net. However, we have seemingly come full circle in the last few years. With the passage of the European GDPR and other jurisdictions beginning to follow suit with similar privacy laws, it easy to see why there is renewed discussion around Gravatar in core.</p>



<p>We should have local avatars because it is the right thing to do. Provide a basic avatar upload system on the user profile screen. Beyond that, let users choose what they want by installing their preferred plugin without guiding them toward one particular service over another.</p>



<p>If nothing else, I&rsquo;m excited about a wider discussion around local avatars in WordPress and welcome the possibility of such a featured explored via an officially-sanctioned plugin.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 14 Aug 2020 21:58: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:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:64:"WPTavern: Struggles of Remote Work Half a Year Into the Pandemic";s:7:"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=103321";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:173:"https://wptavern.com/struggles-of-remote-work-half-a-year-into-the-pandemic?utm_source=rss&utm_medium=rss&utm_campaign=struggles-of-remote-work-half-a-year-into-the-pandemic";s: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:6007:"<p class="has-drop-cap">This was supposed to be the year that ushered in a revolution in how we work. Remote jobs would become a common practice, spurred on by the global COVID-19 pandemic. A time when everyone would start paying attention to those <em>radical</em> ideas from <a href="https://www.nytimes.com/2020/07/12/business/matt-mullenweg-automattic-corner-office.html">remote work evangelists</a> such as Matt Mullenweg.</p>



<p>The question is whether this pandemic was the catalyst the world needed to reevaluate the workplace.</p>



<p>There is certainly a lot of good we can talk about. No hour-long commutes. Saved money by eating at home instead of takeout from the restaurant across the street. More flexible hours.</p>



<p>As a veteran and evangelist of the remote work movement, I have not dealt with many of the struggles that others have during this stretch. While I have had to adjust to the outside world a bit, for the most part, my day-to-day life has remained the same. I had the knowledge that colleagues, friends, and family were having some growing pains with the new reality. However, I never understood what they were going through.</p>



<p>Last week, I nearly reached my breaking point. It was one of those times where reality decided to check in. The beautiful veneer hanging over a decade of remote work was stripped away. It was a time where I truly understood what others had been going through during this worldwide period of struggle.</p>



<p>One of my housemates tested positive for COVID-19 a week earlier. He had a short battle with a fever a few days before, but that was the scope of sickness within the household. My other two housemates and I tested negative and have been doing fine to this point. As frightening as those few days were (<em>Will my friend be OK? Am I going to get sick?</em>), I was unprepared for what this change meant within our household.</p>



<p>That one little test upended our routines and took its toll on my work life.</p>



<p>It meant two weeks of continual interruptions from people who are not accustomed to being under quarantine. While everyone did their best, it was not an ideal situation. I could hunker down in my own space, but the routine that typically drives my life was shattered. For those of us routine-oriented people, even the smallest interruptions can feel like a freight train chugging by with the sole intent of ruining an otherwise peaceful day.</p>



<p>For most of my professional life, I have worked alone in quiet. I might put on some music or a podcast, mostly as a calming bit of background noise. However, I tend to enjoy being alone with my thoughts and the occasional interruption of a cat jumping in my lap for its daily petting.</p>



<p>The two-week disruption of my life, while unpleasant, was a mere blip in comparison to the struggle that many others have endured and overcome for the past five or six months. However, it has allowed me to become more empathetic when hearing others&rsquo; stories. From disruptions on Zoom meetings of children zipping through the house to the family dog begging for playtime in the middle of the day, work has taken on a new meaning for many. And, this is true for remote workers within the WordPress community.</p>



<p>The pandemic has certainly thrust companies and their employees into remote work. However, I question whether it was the push the world needed to reevaluate the workplace. It is not something that grew organically. It forced people into situations they were unprepared for. Some did not miss a beat. Others are still attempting to <a href="https://wptavern.com/finding-balance-in-these-uncertain-times-remote-work-and-sharing-our-struggles">find balance</a>.</p>



<p>Many of us with years of experience have run into issues. A large portion of the WordPress community works remotely. Some are new to it, and many who have years of experience are learning to cope with changes to their environment.</p>



<p>Mullenweg realizes this is not the best of times, even within an established distributed company such as Automattic.  &ldquo;I believe that if you do distributed work well, you&rsquo;re a lot more productive,&rdquo; he said in <a href="https://www.nytimes.com/2020/07/12/business/matt-mullenweg-automattic-corner-office.html">Corner Office interview</a> for the New York Times.  &ldquo;But the pandemic has affected a lot of people&rsquo;s lives. School is canceled. People are working from home that might not normally work from home. So we definitely have seen a hit to productivity, not to mention the stress, which has been even compounded by the social unrest.&rdquo;</p>



<p>I am still an evangelist for remote work. Outside of potentially teaching schoolchildren once again (perhaps in the far, far away future), I can hardly imagine moving to an office away from home anytime soon. However, I can see how being propelled into an unfamiliar environment will not sit well with some. This experience in remote work may even turn away those who would have otherwise been comfortable had they been given the opportunity outside of the chaos of kids, spouses, housemates, and all the other distractions. That old, familiar cubicle may be enticing at this point.</p>



<p>I am happy that this pandemic will make for some converts to remote work but worry that others have not been given a fair look at the benefits that might exist under normal circumstances.</p>



<p>This post is in part sharing my struggles with remote work and part an open invitation for members of our community to talk about their experiences over the past several months.  This is me checking in with you, our dear readers.  How are you coping today?</p>



<p>For people who are struggling but are not comfortable discussing issues related to remote work openly in the comments, please check out <a href="https://www.bigorangeheart.org/">Big Orange Heart</a>, an organization dedicated to supporting the well-being of remote workers.</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, 13 Aug 2020 22:27:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:64:"WPTavern: Convert Reusable Blocks to Block Patterns with 1-Click";s:7:"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=103302";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:173:"https://wptavern.com/convert-reusable-blocks-to-block-patterns-with-1-click?utm_source=rss&utm_medium=rss&utm_campaign=convert-reusable-blocks-to-block-patterns-with-1-click";s: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:5063:"<p>Now that <a href="https://wptavern.com/wordpress-5-5-eckstine-introduces-block-directory-block-patterns-and-automatic-updates-for-themes-and-plugins">WordPress 5.5</a> has shipped, block patterns are available in core for all users. If you have previously been relying on reusable blocks but prefer the flexibility of block patterns, you may want to convert these. </p>



<p>WordPress core developer Jean-Baptiste Audras has made this possible in the latest update of his <a href="https://wordpress.org/plugins/reusable-blocks-extended/">Reusable Blocks Extended</a> plugin. He posted a video demo of how the plugin converts reusable blocks to block patterns with one click.</p>



<div class="wp-block-embed__wrapper">
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Update! &#128165; My Reusable Blocks Extended <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a> plugin now allows users to convert reusable blocks to block patterns in one click &#10024;<br />Just hit the conversion button and your reusable blocks will be automagically converted &#128526;<br />See the 1min-demo below &#128071;<a href="https://twitter.com/hashtag/WP55?src=hash&ref_src=twsrc%5Etfw">#WP55</a> <a href="https://twitter.com/hashtag/Gutenberg?src=hash&ref_src=twsrc%5Etfw">#Gutenberg</a> <a href="https://t.co/YDBaxnA8Nw">pic.twitter.com/YDBaxnA8Nw</a></p>&mdash; Jb Audras (@AudrasJb) <a href="https://twitter.com/AudrasJb/status/1293673870210338821?ref_src=twsrc%5Etfw">August 12, 2020</a></blockquote>
</div>



<h3>What&rsquo;s the difference between reusable blocks and block patterns?</h3>



<p>Why might you want to convert your reusable blocks to block patterns? For users who are new to the concept, there are a few distinctions between these similar features.</p>



<p>Reusable blocks were designed to be a time-saving feature that allows users to save a block or group of blocks for use on other posts or pages. They can be edited but they have a certain distinction in that they are intended to look the same in all places they are used. Any changes made to a reusable block will apply to all instances of the block wherever it is used.</p>



<p>If a user wanted to make changes to a reusable block specific to one page, the process would involve clicking on the block&rsquo;s properties and selecting &ldquo;convert to regular block,&rdquo; which would ensure that all edits would appear only on that specific instance of the block. It&rsquo;s unlikely that most users would know how to do this without help, so this is one of the drawbacks of reusable blocks.</p>



<p>Block patterns are predefined block layouts that are designed to be changed. Once a pattern is inserted into the content, users can customize with their own text, images, alignments, colors, additional blocks, etc. The options are limitless and any changes made are not saved back to the original pattern. Block patterns provide a flexible starting point that gives users an idea of how blocks can be combined to make attractive layouts.</p>



<h3>User-Created Patterns Are Coming Soon to the Block Pattern Builder Plugin</h3>



<p>At the moment, users can create their own reusable blocks but not their own block patterns. Patterns have to be <a href="https://developer.wordpress.org/block-editor/developers/block-api/block-patterns/">registered with code</a> in order to appear in the pattern library. This is another reason that Audras&rsquo; one-click conversion is quite useful for users who are limited to capabilities offered in the editor&rsquo;s current UI. </p>



<p>The ability to create block patterns inside the editor should be a feature in core. It would enable non-technical users to share their designs and creations in a more flexible format than reusable blocks provide. Until this feature is added to core &ndash; and it isn&rsquo;t a guarantee- there is a plugin for that. </p>



<p>Justin Tadlock&rsquo;s <a href="https://wordpress.org/plugins/block-pattern-builder/">Block Pattern Builder</a> plugin, which is available on WordPress.org, will soon be merging a pull request that <a href="https://github.com/justintadlock/block-pattern-builder/pull/2">adds the option to create block patterns inside the editor</a>. It will work in a similar way to the process of adding reusable blocks. Now that block patterns are available in WordPress 5.5, this feature will be more useful to a wide range of users.</p>



<p>Audras&rsquo; <a href="https://wordpress.org/plugins/reusable-blocks-extended/">Reusable Blocks Extended</a> plugin, like many other amazing utilities for the editor, might be difficult to find unless you already know exactly what to search. Many times users are not even aware of the possibility of converting reusable blocks to patterns.  This might also make a useful core feature but doesn&rsquo;t seem likely to be a high priority at the moment. In the meantime, watch for more plugins to start extending block patterns to do interesting things now that they are available in core WordPress.</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, 13 Aug 2020 22:12:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: JSHint is Now Free Software after Updating License to MIT Expat";s:7:"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=103245";s:7:"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:191:"https://wptavern.com/jshint-is-now-free-software-after-updating-license-to-mit-expat?utm_source=rss&utm_medium=rss&utm_campaign=jshint-is-now-free-software-after-updating-license-to-mit-expat";s: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:4759:"<p>The world of open source tooling has expanded to welcome <a href="https://jshint.com/">JSHint</a>, as the project&rsquo;s maintainers have finally completed the necessary work to adopt the MIT Expat license. Previously, the JavaScript linter&rsquo;s code was partially published under the JSON license, with an additional seemingly innocuous clause that stated: &ldquo;The Software shall be used for Good, not Evil.&rdquo; This clause prevented it from being recognized by FSF as <a href="http://www.gnu.org/licenses/license-list.html">a free software license</a> and similarly was not recognized as <a href="https://opensource.org/licenses/alphabetical">open source</a> by the Open Source Initiative.</p>



<p>In an essay titled <a href="http://mikepennisi.com/blog/2020/jshint-watching-the-ship-sink/">Watching the Ship Sink</a>, JSHint co-maintainer Mike Pennisi describes how the license hurt the project. Despite having captured the distinction of being the most popular JavaScript linter in 2015, the tool has been brutally outpaced during the past five years by its contemporary, ESLint, largely due to the effects of having non-free licensing.</p>



<img />credit: Mike Pennisi



<p>&ldquo;Legally-conscious objectors aren&rsquo;t betraying their own dastardly motivations; they&rsquo;re refusing to enter into an ambiguous contract,&rdquo; Pennisi said. &ldquo;Put differently: they&rsquo;re not saying, &lsquo;I&rsquo;m an evildoer,&rsquo; they&rsquo;re saying, &lsquo;I don&rsquo;t understand what you want.&rsquo; This consideration disqualified JSHint from inclusion in all sorts of contexts.&rdquo;</p>



<p>Licensing concerns prevented developers from the Debian and Fedora GNU/Linux distributions from including JSHint. Pennisi even dips into a bit of WordPress history, when he detailed how programming platforms that &ldquo;repackaged&rdquo; JSHint&nbsp;also reconsidered due to its additional clause.</p>



<p>&ldquo;There was a time when the popular content management system WordPress repackaged JSHint in this way,&rdquo; he said. &ldquo;Once they learned of the JSON license, they replaced JSHint in a matter of weeks.&rdquo; Pennisi referenced a <a href="https://core.trac.wordpress.org/ticket/42850">ticket</a> for WordPress 4.9 wherein JSHint was <a href="https://make.wordpress.org/core/2018/01/24/jshint-removed-from-codemirror-in-4-9-3/">removed from core&rsquo;s implementation of CodeMirror</a>, as well as WordPress&rsquo; build tools. </p>



<p>&ldquo;When a project like JSHint loses users, it also loses contributors,&rdquo; Pennisi said. &ldquo;This slows the addition of new features and the correction of bugs. Timeliness is important for these things, and people perceive delays very negatively. The best example of this comes from JSHint&rsquo;s delayed support for async functions.&rdquo;</p>



<p>JSHint had become what Pennisi described as a &ldquo;bizarrely-encumbered JavaScript linter.&rdquo; Unfortunately, the process of going open source after seven years was not as simple as submitting a pull request for a license change. In a <a href="http://mikepennisi.com/blog/2020/you-may-finally-use-jshint-for-evil/">series of essays</a>, he unfolds the grueling process of requesting permission from all of the project&rsquo;s 200+ contributors, only to end up receiving one refusal and some who weren&rsquo;t available for contact. Ultimately, the JSHint team was forced to rewrite the source code but only for the parts that were contributed by the five people who had not permitted the license change.</p>



<p>At the beginning of August, JSHint updated to use the MIT Expat license in <a href="https://jshint.com/blog/2020-08-02/release-2-12-0/">version 2.12.0</a> and is now GPL-compatible. Pennisi&rsquo;s cautionary tale of what he called &ldquo;the liberation of JSHint&rdquo; is a fascinating read that details the struggle of overcoming the challenges of the project&rsquo;s original license.  The key takeaway from this story is that software creators should strongly consider the ramifications of licensing up front, even if a large community of users seems unimaginable at first. Open source licensing takes a project further than its creator could ever have brought it alone.</p>



<p>&ldquo;For many people, licensing is an esoteric part of software development,&rdquo; Pennisi said. &ldquo;It&rsquo;s a relatable opinion: the legal frameworks are intimidating, and most considerations can be addressed by simply defaulting to well-known free/open-source licenses.</p>



<p>&ldquo;The trouble is that not all software is distributed under well-known free/open-source licenses. My hope is that the particulars of JSHint&rsquo;s decay help folks understand why licensing matters.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 12 Aug 2020 22:47:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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:39;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:68:"WPTavern: Improved Server-Side Rendering of Dynamic WordPress Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=103242";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:181:"https://wptavern.com/improved-server-side-rendering-of-dynamic-wordpress-blocks?utm_source=rss&utm_medium=rss&utm_campaign=improved-server-side-rendering-of-dynamic-wordpress-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4547:"<p class="has-drop-cap">Over the weekend, David Gwyer <a href="https://wpgoplugins.com/an-improved-server-side-render-component-for-dynamic-wordpress-blocks/">announced a custom server-side render component</a> for block plugins. The co-founder of WPGO Plugins primarily built his component to speed up the rendering process for dynamic blocks within his own plugins. However, he has now released this component for other block developers in the WordPress community.</p>



<p>Most blocks are static. Their output remains the same and has no need to change. However, some blocks are dynamic. Their output needs to change based on a variety of reasons, such as the context they are output in or other changes within the WordPress system. For example, the core Latest Posts block is dynamic because the posts that it displays change as new posts are written. If they were output as a static block, the end-user would need to update the block each time a new post was written. Therefore, dynamic blocks come in handy because they are rendered by the server in the editor and on the front end.</p>



<p>The problem with rendering from the server is that it can be slow, especially if the user is making several successive options changes to a particular block. With each change, the block must be re-rendered. The core experience with dynamic blocks has not been ideal.</p>



<p>Gwyer&rsquo;s new component is <a href="https://github.com/dgwyer/server-side-render-x">available via GitHub</a>. The project has little code, and its primary JavaScript file weighs in at just over 4kb (uncompressed). It introduces a new <code>&lt;ServerSideRenderX /&gt;</code> component, which works similarly to WordPress&rsquo;s existing <code><a href="https://developer.wordpress.org/block-editor/packages/packages-server-side-render/">&lt;ServerSideRender /&gt;</a></code>. Block developers should have little trouble switching to this version for a quick test.</p>



<p>He is currently using his component within the <a href="https://wordpress.org/plugins/flexible-faqs/">Flexible FAQs</a> plugin. After running through a few tests, the plugin&rsquo;s dynamic blocks feel much more responsive, almost to the point where there is little difference between it and a JavaScript-rendered static block. </p>



<img /> component works when updating a block." class="wp-image-103253" />Live rendering when updating a dynamic block&rsquo;s options in the editor.



<p>He also has plans to use it within his <a href="https://wordpress.org/plugins/simple-sitemap/">Simple Sitemap</a> plugin and any other future dynamic blocks. That is assuming WordPress does not improve its server-side rendering component in the meantime.</p>



<h2>How the Component Works</h2>



<p class="has-drop-cap">Gwyer&rsquo;s component is a fork of the core <code>&lt;ServerSideRender&gt;</code> component, which he says works well aside from the point where it transitions between render states. His custom component seeks to rectify that issue. &ldquo;The main additions were a new piece of state to track the previous block content to use as placeholder content, and a new component prop to handle the spinner location,&rdquo; he said.</p>



<p>He laid out how both the core and his component works with the core component rendering as follows:</p>



<ol><li>Render block.</li><li>Block attribute(s) updated.</li><li>Replace entire block content with spinner.</li><li>Render new block content.</li></ol>



<p>His new component makes an important change that creates at least a perceived visual speed increase:</p>



<ol><li>Render block.</li><li>Block attribute(s) updated.</li><li>Replace entire block content with placeholder content (current/previous content), plus spinner in the top right corner.</li><li>Render new block content.</li></ol>



<p>&ldquo;Because the block content is essentially left unaltered until the new content is ready to be rendered it looks a lot faster as well as smoother,&rdquo; said Gwyer.</p>



<p>The real question is whether this fork should make its way into the Gutenberg project and eventually merged into WordPress. WordPress developer Ben Gillbanks thinks so and has created a new <a href="https://github.com/WordPress/gutenberg/issues/24519">GitHub ticket</a> with the request.</p>



<p>&ldquo;I&rsquo;d like to see it added to Gutenberg as it&rsquo;s a much better rendering experience for dynamic blocks,&rdquo; said Gwyer. &ldquo;I&rsquo;d happily liaise with the team if they&rsquo;re are interested in including it in core.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 12 Aug 2020 20:49:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;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:102:"WPTavern: A Non-Technical Release Lead’s Journey to Becoming a Mentor for WordPress Core Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=103152";s:7:"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:243:"https://wptavern.com/a-non-technical-release-leads-journey-to-becoming-a-mentor-for-wordpress-core-development?utm_source=rss&utm_medium=rss&utm_campaign=a-non-technical-release-leads-journey-to-becoming-a-mentor-for-wordpress-core-development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:21710:"<p class="has-drop-cap">In the summer of 2019, I was asked to help out with a WordPress release. A few months before, the Core Team representatives reached out to other teams in an effort to increase the diversity of the release teams, and I started seriously considering it. </p>



<p>At the time, I was already heavily involved in the WordPress ecosystem and was in my second year as the WordPress Community and Partnership Manager at SiteGround, but I had no experience whatsoever on how WordPress gets done from a Core point of view. Still, when Josepha Haden, WordPress.org Executive Director, pinged me, I said yes without hesitation. And it proved one of the most challenging and rewarding experiences of my life. Here is how.&nbsp;</p>



<img />Josepha and I walking around Vienna, WCEU 2016 &ndash; Photo by <a href="https://www.flickr.com/photos/lucasartoni/">Luca Sartoni</a>



<h2>An Accidental Contributor: My Path in Tech</h2>



<p>From an early age, I seemed to be predestined to become a developer. My parents are programmers, they started in the sixties, and I got my first personal computer in 1982 when people in Italy didn&rsquo;t really have an idea of what those were.</p>



<p>I followed after their work ethos and I thought that their job was fascinating, making a machine do what you want, but I was drawn to other career options. In fact, I didn&rsquo;t really know what I wanted to do when I grew up, but computers and websites kept being a big part of my personal and professional life.</p>



<p>While back-end programming was never something that interested me, I found myself taking a class on web design in 1999, then signed up for a degree in Arts and Multimedia in 2004.  I finally found WordPress in 2008 and started making a living off of it in 2010.&nbsp;</p>



<p>Soon, I realized my true skill was helping clients who were coming to me with a request for a website to better focus on their &ldquo;why&rdquo; for the website and think about their business and marketing strategy before they hired me. I wrote books on business planning, productivity, and websites.  I also started giving talks at WordCamps and other events to educate freelancers on those topics.&nbsp;</p>



<p>In 2015, I randomly met some people who were involved in the WordPress community, which led me to start contributing too. I didn&rsquo;t have development skills so I never thought I could contribute to OSS, but it turns out that was unnecessary. I met people who pointed me to the many different teams that make WordPress and started being active in Polyglots first and Community later.</p>



<img />My first WordCamp Talk: The Rebirth of the Italian Community, at WordCamp London 2016



<p>I kept working on my business, but the more I contributed to WordPress, the more I wanted to find a way to help thousands of people at a time.  My outreach efforts of giving talks, helping community organizers, and writing content needed to scale.&nbsp;</p>



<p>This is where I met SiteGround.  In the summer of 2017, they were looking for a Community Manager and despite not being one by trade I decided to apply and got the job. Joining the company allowed me to have sponsored time to contribute to WordPress.  It also allowed me to tap into the collective knowledge of my colleagues when I start cooking up new ideas for the project.</p>



<p>So I said yes without hesitation, but the truth is that this yes was almost five years in the making. In addition, I felt that Josepha and SiteGround trusted me to do a good job.  In return, I trusted the WordPress community to help me figure out all the things that I needed to learn.</p>



<h2>How WordPress Gets Done</h2>



<p>The other encouraging factor was that ever since WordPress 5.0, a release was no longer made by one person, as it used to be for years, or a person with a couple of deputies. Now there was a whole team at work, affectionately known as &ldquo;the squad,&rdquo; so there are many hands on deck.</p>



<h3>A Lot of Communication</h3>



<p>During a release cycle, there is a lot of communication.  There are blog posts from different Make teams. At each stage of the release, there are blog posts in the News section of WordPress.org. There is constant chatter in the public Slack channel and there is a private one which is the safety net for the new people that initially might feel intimidated by asking questions in a large public channel.&nbsp;</p>



<h3>The Different Roles in the Release Squad</h3>



<img />WordPress 5.3 had a release squad of 12 people and 654 contributors. WordPress 5.5 threw it out of the park with 805 contributors!



<p>The thing that I love the most about this model for the release is the variety of roles that it includes. There are developers, designers, marketers, technical writers, and project managers. WordPress is not only made of code, and it&rsquo;s great to see all these different skills coming together to contribute to its release.&nbsp;</p>



<p>The role of the Release Coordinator (the one I covered for WordPress 5.3 and 5.4) and of the Triage PM (role that was covered by the excellent David Baumwald for 5.3, 5.4, and 5.5) is to try to keep an eye on all the moving parts. And I say <em>try</em> because it&rsquo;s nearly impossible. This is why there are focus leads for the different parts that are getting worked on.</p>



<p>Matt Mullenweg is the project lead and has been the release lead since WordPress 5.0.  He comes up with the high-level <a href="https://wordpress.org/about/roadmap/">roadmap</a> and the <a href="https://make.wordpress.org/core/2018/12/08/9-priorities-for-2019/">focus projects</a>.&nbsp; But beyond that, he is not involved with the day-to-day life of Core development. In over one year of being involved in Core releases, Matt asked only once to add a <a href="https://make.wordpress.org/core/2020/03/03/fullscreen-mode-enabled-by-default-in-the-editor/#comment-38054">feature</a>.&nbsp;</p>



<p>I am annoyed when people think that everything that happens in WordPress is because Matt wants it that way. It diminishes the role of all the people who care about the project and take it upon themselves to move things forward, to shepherd issues, to champion tickets, and in general to commit to contribute to make WordPress better for everyone, no matter if they do it for one ticket or work on it full time.&nbsp;</p>



<h3>Component Maintainers and Core Committers</h3>



<p>A group of people who are instrumental in shaping a release are the <a href="https://make.wordpress.org/core/2020/02/09/what-does-it-mean-to-be-a-component-maintainer-a-refresher/">component maintainers</a>. They are responsible to look after a certain component that makes up Core and see how tickets in that area are proceeding. They are the ones who can evaluate if a ticket is ready to be merged.</p>



<p>Once a ticket is deemed ready, Core Committers enter the scene. They do a final review of the ticket. They might request some changes, or make the changes themselves while committing. This is the thing that surprised me the most probably. I really didn&rsquo;t think that a commit could take hours, but it definitely can. In the releases I coordinated, I definitely observed not a lot of engagement from maintainers and committers, and this is very demotivating for people working on tickets. Not everything can go into a release, even if the patch is ready, because there aren&rsquo;t enough people to review, give feedback, and ultimately commit. With few resources, you have to make choices and those will not always align with each WordPress user or contributor preferences.&nbsp;</p>



<p>This is probably one of the biggest challenges WordPress will have to tackle moving forward: How can we reactivate people who can give a big help?</p>



<h3>The Release Party</h3>



<img />Photo by <a href="https://www.flickr.com/photos/damndirty/">Florian Ziegler</a>



<p>Despite these issues, things get done and when the release is ready, we celebrate with a party. I don&rsquo;t know who started calling them Release Parties or when they started.  What I know is that for 5.3 and 5.4, I hosted quite a few, and they were all a lot of fun.&nbsp;</p>



<p>On the day of one of the steps of the release (it might be Betas, Release Candidates or General Release) the Core channel gets very active: a lot of people come online to see how the version of WordPress gets released. There are multiple steps and different people involved with different tasks. The release steps are documented in the Core handbook and are followed publicly so everyone can see them all.&nbsp;</p>



<p>The biggest party is the general release day; there is one specific moment which is incredibly powerful. WordPress has a <a href="https://wordpress.org/download/counter/">download counter</a>, so before releasing the new version, the squad takes a screenshot of the previous one, we all say goodbye and welcome the new kid. Despite everything being virtual, this moment is almost tangible and will never cease to move me. We made WordPress, once again.</p>



<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>Screenshots of the WordPress counter seconds before WordPress 5.5 was released and two hours later.



<h2>12 Months as a Core Contributor</h2>



<p>While I was writing this article, it occurred to me that I have been a Core contributor for a year now. I still have my full-time role at SiteGround, which at times I found hard to juggle, so I have to give my team credit for their support.</p>



<p>I still can&rsquo;t write PHP and despise JavaScript deeply, but when I look back, I am incredibly proud of the changes that have happened in the past 12 months. I can not take credit for all of them, but I am happy I was able to be somehow part of them.</p>



<h3>Release Schedule</h3>



<p>One thing that a lot of contributors asked for was a mid-term schedule of releases, to better fit them around their work and personal calendar. Being the new kid can be hard because you don&rsquo;t know the whole history and background of why things are done a certain way, but that is also a perk. You are free to restart conversations.  After discussing it with the squad and other teams, it was clear to me that it was just a matter of &ldquo;who is going to bring this up with Matt&rdquo;. And so I did. A couple of days later a <a href="https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/">tentative release schedule</a> until WordPress 6.0 was published on the Core blog, and we have been using it ever since.</p>



<h3>Bigger Release Squad and Mentorship</h3>



<p>The release squad is also getting bigger with every release.  Many teams are involved in making it and affected by it. It&rsquo;s important for all these teams to be represented in the process. In WordPress 5.5, there are several new roles, and in 5.6 there will be even more: Test, Documentation, Support are all vital components of what makes WordPress great, so having their feedback while the software is in active development is important.</p>



<p>And it&rsquo;s important to have mentors.  This is a major improvement that Josepha introduced in WordPress 5.3. The release squad is not only made of focus leads, but there is a growing group of mentors able to help new contributors learn the ropes. The idea is that those people will eventually become mentors and teach new people. This is another great way to have more and more people involved in Core, with different skills and backgrounds.&nbsp;</p>



<p>And this brings me to the biggest change (and challenge) of all. WordPress 5.6, which is shaping up to be a massive release, will have a <a href="https://wptavern.com/wordpress-names-5-5-release-leads-plans-all-women-release-squad-for-5-6">squad entirely made of women</a> and people who identify as female. Like a lot of things in WordPress, it all started with a <a href="https://twitter.com/JosephaHaden/status/1194431234245447680?s=20">&ldquo;Thinking out loud&rdquo; moment</a> and is now a reality. Work on this release will start very soon, and I am excited to be part of it as a mentor.</p>



<img />Fellow female contributors leading the Polyglots team at WordCamp Torino 2018. Picture by Gianni Vascellari



<h2 class="is-style-default">WordPress Needs Your Help</h2>



<p>I wish I could say it is all unicorns and rainbows, but it&rsquo;s not. The number of people actively involved in making this project a reality is still very small compared to the magnitude of its reach.</p>



<p>I am very much a doer, so I wish people took the time and energy they take into critiquing WordPress and turn it into active contribution time. Yes, sometimes it requires being very stubborn about a ticket and it requires to follow up on it relentlessly, but I still think it&rsquo;s worth it.</p>



<p>Active participation also means leaving constructive feedback in tickets or offering to take notes during dev chat.  That is the curse and the beauty of a massive project.  There is always something to do!</p>



<p>In the last few years, I have also seen an increase in contribution from different kinds of companies. At SiteGround, for example, we mostly contributed to events and the community for years. We sponsored, and we volunteered, we were organizers and speakers. We worked a lot within the Spanish WordPress community to help it develop and grow, and now it&rsquo;s one of the largest in the global community. In the last year, we have increased the hours we dedicate to more technical teams. I am still active in Core as a mentor and as the team representative.  One of our WordPress engineers, Stanimir Stoyanov, is part of the Security team, and one of our JavaScript Engineers, Kiril Zhelyazkov, is now dedicating a couple of days per week to Gutenberg.</p>



<img />My colleague and Core and Security contributor, Stanimir Stoyanov



<p>These topics align with our values, so it was a natural progression for us to become more involved.</p>



<p>Finally, I hope to see people get involved in a proposal I published a few days ago in the Core blog about <a href="https://make.wordpress.org/core/2020/08/07/e2e-end-to-end-testing-in-core-working-group-proposal/">end-to-end tests</a>. Right now there is one, and I&rsquo;m sure we can do better. Again, developers are not the only ones needed. Users are the rarest contributors and probably the ones the project needs the most to finally have some user testing in place. I am not a developer, and I&rsquo;m happy that non-developers can make an impact.&nbsp;</p>



<h2>My Personal Concerns and Hopes for the Future of the Project</h2>



<p>When I started contributing to Core, I started a note on my computer with some observations. Not having 17 years of experience in the project helps me see things without bias, and not being a developer helps me see the project more as a living, breathing body, instead of components or tickets. Allow me to share my concerns, hopes, and dreams for the future.</p>



<h3>Component Maintainers and Core Committers: You Are Needed More Than Ever</h3>



<p>At the time of writing this article, the project has about 60 committers and 60 component maintainers, with a lot of people pulling double, triple, and sometimes sextuple duties. But the reality is that in WordPress 5.4 and 5.5 hundreds of commits were made by Sergey Biryukov. I am incredibly grateful for Sergey&rsquo;s work.  At the same time, I feel like we are inadvertently building a bus factor into Core. The majority of the people with Core Commit access did not commit one ticket. Similarly, I reached out to all the component maintainers to hear about their plans for the upcoming releases and only about 50% of the components replied.</p>



<p>How do we make sure that the people who have the power, and thus the responsibility, to help with committing and shepherding tickets are involved? But also, how do we encourage people to step down and declare themselves inactive so new people can step up?&nbsp;</p>



<p>My career spans over 25 years in different industries, and one thing remains the same: when people see there is someone else filling a role, they will be less motivated and sometimes even intimidated to step up. Scarcity not only drives purchases, it drives new engagement.</p>



<p>The Community Team, for example, <a href="https://make.wordpress.org/community/community-deputies/">maintains a list of deputies and their different statuses</a>. I have been wondering if Core could do something similar so when new people want to step up they can see at a first glance which components are missing maintainers. People who complain about &ldquo;The Core Developers&rdquo; will not see them as a blob, but as individuals who at any point in time might be inactive for a period. When you see that there are actually only a few people actively reviewing and committing, you might be more prone to understand why not every ticket can make it to the finish line.</p>



<h3>Documentation Is the Highest Form of Generosity</h3>



<p>I say this every time I speak about contributing to OSS: documentation is frequently lacking. Oftentimes, what is there is outdated.&nbsp;</p>



<p>How do we make sure that documentation is not an afterthought but is baked into the development process?</p>



<img />Handbook from it.wordpress.org &ndash; How to translate WordPress to Italian. Photo by Gianni Vascellari



<p>There is a lot of work put into writing dev notes for the changes that affect development, but that is not the only documentation that is needed. Some of the processes described in the Core handbooks are outdated, some are missing because they live in experienced contributors&rsquo; minds.</p>



<p>As a big fan of Gutenberg and rich, engaging text, I wish our handbooks would fully leverage the power of the block editor and be more inviting. Right now they are a wall of text and whenever we tell people to look at the handbooks I feel my heart shrinking.</p>



<p>Possible solutions, which I am not sure are technically doable, but a girl can dream: sync with GitHub to solve at least the version control issue. Then recruit, recruit, recruit and work with Documentation, Meta, and Design to provide useful, engaging, readable, easy-to-scan handbooks.</p>



<h3>Keep Track of the Moving Parts and Work as One</h3>



<p>The other thing that I notice often is how teams, focuses, and components work in silos.</p>



<p>This is absolutely not done to be gatekeepers, it&rsquo;s just how every team self-organized over the years.</p>



<p>We need to find a way to have a bird&rsquo;s eye view of what is going into the next release and what are all the moving parts.</p>



<img /><\/span> is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported Licen","focal_length":"23","iso":"3200","shutter_speed":"0.076923076923077","title":"","orientation":"0"}" data-image-title="People-at-Contributor-Day-WordCamp-Europe" data-image-description="" data-medium-file="https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe-300x200.jpg" data-large-file="https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe-500x333.jpg" loading="lazy" width="2000" height="1333" src="https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe.jpg" alt="People sitting at round tables during a contributor day" class="wp-image-103206" srcset="https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe.jpg 2000w, https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe-300x200.jpg 300w, https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe-500x333.jpg 500w, https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe-768x512.jpg 768w, https://wptavern.com/wp-content/uploads/2020/08/People-at-Contributor-Day-WordCamp-Europe-1536x1024.jpg 1536w" sizes="(max-width: 2000px) 100vw, 2000px" />People Making WordPress at Contributor Day, WordCamp Europe 2015 &ndash; Photo by Florian Ziegler



<p>Trac is very granular and you have a number of ready-made reports, you can <a href="https://core.trac.wordpress.org/milestone/5.6">filter by milestones</a> and see how many tickets are in each component, but that is just part of the story.</p>



<p>Yes, I am talking about finding a way to manage the project as a whole and not as bits and bobs.&nbsp;</p>



<h3>Enter GitHub. At Some Point.&nbsp;</h3>



<p>This is not happening anytime soon, but I hope it will eventually happen. Move development <strong>and</strong> project management of WordPress to GitHub, like Gutenberg has been doing.&nbsp;</p>



<p>I know that for many it will be an incentive to contribute to WordPress in a way that is more familiar. It will lower the bar to entrance, which is always welcome. With some handy tutorials, it will allow non-technical people to contribute to documentation, testing, and project management.</p>



<h2>The Future is Bright</h2>



<p>Despite all the issues, or maybe because of them, the future of WordPress is bright.&nbsp;</p>



<p>I have been lurking around multiple teams in these years, and lately I notice more people coming on board, more people being involved in each release, more people stepping up in leadership roles in different teams. I have also noticed an increase in diversity, which is always a welcome change.</p>



<p>Bottom line: WordPress needs all of us to make it happen. I hope to see you on board!</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, 12 Aug 2020 15:04:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Francesca Marano";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: Major jQuery Changes on the Way for WordPress 5.5 and Beyond";s:7:"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=103051";s:7:"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:185:"https://wptavern.com/major-jquery-changes-on-the-way-for-wordpress-5-5-and-beyond?utm_source=rss&utm_medium=rss&utm_campaign=major-jquery-changes-on-the-way-for-wordpress-5-5-and-beyond";s: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:5775:"<img />



<p class="has-drop-cap">With all of the advancements made in JavaScript and newer, shinier frameworks, it is sometimes easy to forget that WordPress still relies on the aging jQuery library. The same holds true for thousands of plugins and themes in the official WordPress directories.</p>



<p>For some, this may feel like a journey back to the mid-2000s, a time when JavaScript very much felt like the Wild West. jQuery solved many issues for a programming language that had not kept up with what developers needed to accomplish.</p>



<p>A ticket created by Aaron Jorbin four years ago to <a href="https://core.trac.wordpress.org/ticket/37110">move WordPress to the latest 3.x branch</a> of jQuery is finally coming to fruition. However, the WordPress development team will need to make this transition in stages, particularly after waiting for so long.</p>



<p>WordPress has fallen behind on keeping jQuery updated. For a platform that routinely suggests that users need to be running the latest and greatest version, it is odd that WordPress itself has not done the same with third-party code that it relies on. WordPress currently bundles jQuery version 1.12.4, a version of the library released in 2016. It is also a version that supports Internet Explorer 6, 7, and 8.</p>



<p>&ldquo;Mostly because for the last couple of years the focus has shifted to other/more modern JavaScript libraries,&rdquo; said WordPress lead developer Andrew Ozz on why the platform has fallen behind. &ldquo;The number of JavaScript developers that contribute to core is limited, and there is a very high demand.&rdquo;</p>



<p>In the long term, he said a future option might be to move the WordPress admin to native (vanilla) JavaScript completely, which is a sentiment shared in the comments on his announcement post to <a href="https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/">update the version of jQuery</a> bundled with WordPress. &ldquo;This would be great,&rdquo; he said, &ldquo;and at the same time, a very large effort.&rdquo;</p>



<p>Far too many themes and plugins rely on this dated version of jQuery to move any faster. While plugins could choose to overwrite core WordPress&rsquo;s bundled version of jQuery with the latest version, themes have had no such option. The official theme directory guidelines require themes to utilize the core-bundled scripts, including jQuery. There is a good reason for this: for the most part, it ensures compatibility with core and third-party plugins.</p>



<p>However, now it is time to move on.</p>



<h2>What Developers and Users Need to Know</h2>



<img />



<p class="has-drop-cap">WordPress has a three-stage plan to bring jQuery up to date. The core team asks that theme and plugin developers begin testing their extensions with the <a href="https://wordpress.org/plugins/wp-jquery-update-test/">Test jQuery Updates</a> plugin. This will help them bring code up to date throughout this transitional period.</p>



<p>The first step in this process will be removing the jQuery Migrate 1.4.1 script from WordPress 5.5, which was <a href="https://wptavern.com/wordpress-5-5-eckstine-introduces-block-directory-block-patterns-and-automatic-updates-for-themes-and-plugins">released earlier today</a>. This version of jQuery Migrate makes older code compatible and helps developers migrate to jQuery 1.9+.</p>



<p>This move will undoubtedly break some plugins and themes. The core team has made the <a href="https://wordpress.org/plugins/enable-jquery-migrate-helper/">Enable jQuery Migrate Helper</a> plugin available for end-users. &ldquo;It is intended to be run in production on sites that experience jQuery-related problems after updating to 5.5,&rdquo; said Ozz. &ldquo;It works by re-enabling jQuery Migrate and by showing the warnings about the use of outdated/deprecated jQuery functions to site admins.&rdquo;</p>



<p>The long-term goal is to get developers to update their extensions. In the meantime, this plugin should ease some of the problems.</p>



<p>Ozz said the biggest thing developers need to do right now is to make sure they are testing their extensions against WordPress 5.5. &ldquo;Ideally, paying more attention to any old jQuery-based scripts and confirming they still work as expected,&rdquo; he continued. &ldquo;In almost all cases, the fixes are trivial.&rdquo;</p>



<p>Beyond WordPress 5.5, things will start to take shape. The tentative plan is to update to the latest version of jQuery and add the latest version of jQuery Migrate as part of the WordPress 5.6 release.</p>



<p>&ldquo;Again, Migrate will be used to help in updating jQuery based scripts, and also as a backward-compatibility &lsquo;fix&rsquo; while plugins and themes get updated,&rdquo; said Ozz. &ldquo;The version of Migrate in WordPress 5.6 will be different, as it will correspond to the latest jQuery version. It will serve the same purpose as when it was added for the first time, but now will help core, plugins, and themes get updated from jQuery 1.12.4 to 3.5.1 (or later).&rdquo;</p>



<p>The third leg of the process will be to once again remove jQuery Migrate from WordPress. This change is tentatively planned for WordPress 5.7, which will not be released until 2021. The end goal is to remove the reliance on Migrate and ship the latest version of jQuery until someday &mdash; perhaps far into the future &mdash; there may no longer be a need for bundling it with WordPress at all.</p>



<p>&ldquo;Following the best practices and the recommendations of the jQuery team, Migrate should be used as a helper tool, not as a permanent backward-compatibility solution,&rdquo; said Ozz. &ldquo;Ideally, WordPress will be able to do this.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 11 Aug 2020 20:29:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:127:"WPTavern: WordPress 5.5 “Eckstine” Introduces Block Directory, Block Patterns, and Automatic Updates for Themes and Plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=103045";s:7:"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:283:"https://wptavern.com/wordpress-5-5-eckstine-introduces-block-directory-block-patterns-and-automatic-updates-for-themes-and-plugins?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-5-eckstine-introduces-block-directory-block-patterns-and-automatic-updates-for-themes-and-plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5681:"<img />



<p><a href="https://wordpress.org/news/2020/08/wordpress-5-5-eckstine/">WordPress 5.5</a> &ldquo;Eckstine&rdquo; landed today, named for American jazz singer Billy Eckstine. This release introduces major improvements for the block editor and the security of WordPress. It was made possible by the contributions of 805 volunteers (with 38% of them being new contributors.) The 5.5 update is a testament to the stability of WordPress during uncertain times, as well as its unstoppable, distributed contributor base, who continue to get things done despite the pandemic&rsquo;s unique challenges.</p>



<p>WordPress continues refining the editing experience with more than 1,500 updates from 10 releases of the Gutenberg plugin included in 5.5. (The plugin is where all the magic is tested prior to landing in WordPress releases, and features are periodically rolled in.) Some of the most notable changes include <a href="https://wptavern.com/matt-mullenweg-and-matias-ventura-demo-new-image-editing-tools-coming-to-gutenberg">inline image editing</a>, device previews, and smoother block movement with better drag-and-drop, block movers, block selection, and block relocation.</p>







<p>Block Patterns are making their debut in WordPress 5.5, with a handful of default patterns already available in the block inserter. This new feature helps users build pages faster by allowing them to instantly place sets of blocks that are already artfully arranged. We have written extensively about why <a href="https://wptavern.com/block-patterns-will-change-everything">block patterns will change everything</a> and it will be exciting to see what developers do with them now that the feature is in core.</p>



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

</div>



<h2>Block Directory Enables Block Discovery and Installation Inside the Editor</h2>



<p>WordPress recently launched a <a href="https://wptavern.com/call-for-block-plugins-the-wordpress-block-directory-is-open-for-business">block directory</a> for single-block plugins and users can now search for and install blocks directly inside the editor. Selected blocks are downloaded seamlessly in the background and automatically activated and placed in the content. The advantage is that users don&rsquo;t have to break their workflows in order to install new functionality. Blocks installed via the editor can also be uninstalled from the plugins page in the admin.</p>



<div class="wp-block-image"><img />Search for and Install Blocks from the Block Directory</div>



<p>Block patterns, combined with the new block directory, will make page building much faster inside the editor by enabling users to quickly spin up layouts and add blocks on the fly.  </p>



<h2>WordPress Security Takes a Giant Leap with Automatic Updates for Themes and Plugins</h2>



<p>Version 5.5 introduces a new UI for enabling auto-updates for themes and plugins. This is an exciting new era for WordPress that brings a higher level of website security while requiring less effort from users. Those who choose to get on the automatic updates train will no longer have to log into their sites and be greeted with a slew of nagging update notices. These updates will happen the same day they are available, so users don&rsquo;t have to check in as often and sites are better protected from plugin and theme vulnerabilities getting exploited.</p>



<img />



<p>WordPress uses wp-cron to fetch updates for plugins and themes twice per day. The feature ships turned off by default in WordPress 5.5, so users will need to visit the theme and plugin pages in the admin to enable automatic updates.  The bulk actions menu dropdown now has options for enabling or disabling auto-updates on all plugins, but users can always enable the updates for select plugins if they have any concerns.</p>



<p>Other notable updates in WordPress 5.5 include the following:</p>



<ul><li><strong>XML Sitemaps</strong>: WordPress now includes <a href="https://wptavern.com/wordpress-5-5-to-include-extensible-core-sitemaps">extensible core sitemaps</a>, and many users will no longer need a plugin for this functionality. This basic implementation was completed in a way that will not impact performance or cause conflicts with other plugins that add sitemaps.</li><li><strong>Lazy Loading Images</strong>: WordPress images will now wait to load until users scroll them into view, speeding up performance, especially on mobile.</li><li><strong>Improved Accessibility</strong>: Metaboxes can now be moved with the keyboard, assistive devices can see status messages in the image editor, copying links in media screens and modal dialogs can now be done with a click of a button, and more.</li><li><strong>Update Themes and Plugins by Uploading ZIP files</strong>: &ndash; Users can now update plugins and themes manually by <a href="https://wptavern.com/after-11-years-users-will-be-able-to-update-themes-and-plugins-via-a-zip-file">uploading a ZIP file</a>, an improvement for scenarios where one does not have server access.</li><li><strong>Final Dashicon Library Update:</strong> The Dashicons project has been <a href="https://wptavern.com/wordpress-dashicons-project-to-discontinue-development-in-favor-of-new-icon-component">discontinued in favor of the new Icon Component</a>. This last update to the library adds 39 block editor icons and 26 other icons. </li></ul>



<p>For a more technical breakdown of some of the changes under the hood, check out the <a href="https://make.wordpress.org/core/tag/5-5+dev-notes/">developer notes</a> and the <a href="https://make.wordpress.org/core/2020/07/30/wordpress-5-5-field-guide/">5.5 field guide</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, 11 Aug 2020 19:13:23 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:48:"WordPress.org blog: WordPress 5.5 “Eckstine”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=8799";s:7:"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:44:"https://wordpress.org/news/2020/08/eckstine/";s: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:69568:"<p>Here it is! Named “Eckstine” in honor of Billy Eckstine, this latest and greatest version of WordPress is available for&nbsp;<a href="https://wordpress.org/download/">download</a> or update in your dashboard.</p>



<img width="632" height="514" src="https://i0.wp.com/wordpress.org/news/files/2020/08/Billy_duotone-1000px_quiche-sans-top.png?resize=632%2C514&ssl=1" alt="" class="wp-image-8930" />



<div class="wp-block-cover has-background-dim"><div class="wp-block-cover__inner-container">
<p class="has-text-align-center has-black-color has-text-color has-background has-large-font-size">Welcome to WordPress 5.5.</p>



<h3 class="has-text-align-center has-black-color has-text-color">In WordPress 5.5, your site gets new power in three major areas: <br />speed, search, and security.</h3>
</div></div>



<div class="wp-block-columns has-white-background-color has-background">
<div class="wp-block-column"></div>



<div class="wp-block-column">
<h2>Speed</h2>



<p><strong>Posts and pages feel faster, thanks to lazy-loaded images.</strong></p>



<p>Images give your story a lot of impact, but they can sometimes make your site seem slow.</p>



<p>In WordPress 5.5, images wait to load until they’re just about to scroll into view. The technical term is ‘lazy loading.’</p>



<p>On mobile, lazy loading can also keep browsers from loading files meant for other devices. That can save your readers money on data — and help preserve battery life.</p>



<h2>Search</h2>



<p><strong>Say hello to your new sitemap.</strong></p>



<p>WordPress sites work well with search engines.</p>



<p>Now, by default, WordPress 5.5 includes an XML sitemap that helps search engines discover your most important pages from the very minute you go live.</p>



<p>So more people will find your site sooner, giving you more time to engage, retain and convert them to subscribers, customers or whatever fits your definition of success.</p>
</div>



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



<div class="wp-block-columns has-background">
<div class="wp-block-column"></div>



<div class="wp-block-column">
<h2>Security</h2>



Now you can choose to update plugins and themes automatically–or pick just a few–from the screens you’ve always used.



<p><strong>Auto-updates for Plugins and Themes</strong></p>



<p>Now you can set plugins and themes to update automatically — or not! — in the WordPress admin. So you always know your site is running the latest code available.</p>



<p>You can also turn auto-updates on or off for each plugin or theme you have installed — all on the same screens you’ve always used.</p>



<p><strong>Update by uploading ZIP files</strong></p>



<p>If updating plugins and themes manually is your thing, now that’s easier too — just upload a ZIP file.</p>
</div>



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



<div class="wp-block-columns has-background">
<div class="wp-block-column"></div>



<div class="wp-block-column">
<h2>Highlights from the block editor</h2>



<p>Once again, the latest WordPress release packs a long list of exciting new features for the block editor. For example:</p>







<div class="wp-block-columns">
<div class="wp-block-column">
<h3>Block patterns</h3>



<p>New block patterns make it simple and fun to create complex, beautiful layouts, using combinations of text and media that you can mix and match to fit your story.</p>



<p>You will also find block patterns in a wide variety of plugins and themes, with more added all the time. Pick any of them from a single place — just click and go!</p>
</div>



<div class="wp-block-column">
<h3>The new block directory</h3>



<p>Now it’s easier than ever to find the block you need. The new block directory is built right into the block editor, so you can install new block types to your site without ever leaving the editor.</p>



<h3>Inline image editing</h3>



<p>Crop, rotate, and zoom your photos right from the image block. If you spend a lot of time on images, this could save you hours!</p>
</div>
</div>







<h3>And so much more.</h3>



<p>The highlights above are a tiny fraction of the new block editor features you’ve just installed. Open the block editor and enjoy!</p>
</div>



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



<div class="wp-block-columns has-white-background-color has-background">
<div class="wp-block-column"></div>



<div class="wp-block-column">
<h2>Accessibility</h2>



<p>Every release adds improvements to the accessible publishing experience, and that remains true for WordPress 5.5.</p>



<p>Now you can copy links in media screens and modal dialogs with a button, instead of trying to highlight a line of text.</p>



<p>You can also move meta boxes with the keyboard, and edit images in WordPress with your assistive device, as it can read you the instructions in the image editor.</p>
</div>



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



<div class="wp-block-columns has-black-color has-text-color has-background">
<div class="wp-block-column"></div>



<div class="wp-block-column">
<h2>For developers</h2>



<p>5.5 also brings a big box of changes just for developers.</p>



<div class="wp-block-columns">
<div class="wp-block-column">
<h3>Server-side registered blocks in the REST API</h3>



<p>The addition of block types endpoints means that JavaScript apps (like the block editor) can retrieve definitions for any blocks registered on the server.</p>



<h3>Defining environments</h3>



<p>WordPress now has a standardized way to define a site’s environment type (staging, production, etc). Retrieve that type with&nbsp;<code>wp_get_environment_type()</code>&nbsp;and execute only the appropriate code.</p>



<h3>Dashicons</h3>



<p>The Dashicons library has received its final update in 5.5. It adds 39 block editor icons along with 26 others.</p>



<h3>Passing data to template files</h3>



<p>The template loading functions (<code>get_header()</code>,&nbsp;<code>get_template_part()</code>, etc.) have a new&nbsp;<code>$args</code>&nbsp;argument. So now you can pass an entire array’s worth of data to those templates.</p>
</div>



<div class="wp-block-column">
<h3>More changes for developers</h3>



<ul><li>The PHPMailer library just got a major update, going from version 5.2.27 to 6.1.6.</li><li>Now get more fine-grained control of&nbsp;<code>redirect_guess_404_permalink()</code>.</li><li>Sites that use PHP’s OPcache will see more reliable cache invalidation, thanks to the new&nbsp;<code>wp_opcache_invalidate()</code>&nbsp;function during updates (including to plugins and themes).</li><li>Custom post types associated with the category taxonomy can now opt-in to supporting the default term.</li><li>Default terms can now be specified for custom taxonomies in&nbsp;<code>register_taxonomy()</code>.</li><li>The REST API now officially supports specifying default metadata values through&nbsp;<code>register_meta()</code>.</li><li>You will find updated versions of these bundled libraries: SimplePie, Twemoji, Masonry, imagesLoaded, getID3, Moment.js, and clipboard.js.</li></ul>
</div>
</div>
</div>



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



<div class="wp-block-columns has-white-background-color has-background">
<div class="wp-block-column"></div>



<div class="wp-block-column">
<h2>The Squad</h2>



<p>Leading this release were&nbsp;<a href="http://ma.tt/">Matt Mullenweg</a>,&nbsp;<a href="https://profiles.wordpress.org/whyisjake">Jake Spurlock,</a> and&nbsp;<a href="https://dream-encode.com/blog/">David Baumwald</a>. Supporting them was this highly enthusiastic release squad:</p>



<ul><li><strong>Editor Tech</strong>: Ella Van Durpe (<a href="https://profiles.wordpress.org/ellatrix/" class="mention"><span class="mentions-prefix">@</span>ellatrix</a>)</li><li><strong>Editor Design</strong>: Michael Arestad (<a href="https://profiles.wordpress.org/michael-arestad/" class="mention"><span class="mentions-prefix">@</span>michael-arestad</a>)</li><li><strong>Core Tech</strong>: Sergey Biryukov (<a href="https://profiles.wordpress.org/sergeybiryukov/" class="mention"><span class="mentions-prefix">@</span>sergeybiryukov</a>)</li><li><strong>Media Tech: </strong>Andrew Ozz (<a href="https://profiles.wordpress.org/azaozz/" class="mention"><span class="mentions-prefix">@</span>azaozz</a>)</li><li><strong>Accessibility Tech</strong>: JB Audras (<a href="https://profiles.wordpress.org/audrasjb/" class="mention"><span class="mentions-prefix">@</span>audrasjb</a>)</li><li><strong>Docs Coordinator</strong>:&nbsp;Justin Ahinon (<a href="https://profiles.wordpress.org/justinahinon/" class="mention"><span class="mentions-prefix">@</span>justinahinon</a>)</li><li><strong>Marketing/Comms Coordinator</strong>: Mary Baum (<a href="https://profiles.wordpress.org/marybaum/" class="mention"><span class="mentions-prefix">@</span>marybaum</a>)</li></ul>



<p>Joining the squad throughout the release cycle were <strong>805 generous volunteer contributors</strong> who collectively worked on over <strong><a href="https://core.trac.wordpress.org/milestone/5.5">523</a> tickets on Trac</strong> and <strong>over 1660 pull requests on GitHub</strong>.</p>



<p>Put on a Billy Eckstine playlist, click that update button (or&nbsp;<a href="https://wordpress.org/download/">download it directly</a>), and check the profiles of the fine folks that helped:</p>


<a href="https://profiles.wordpress.org/a2hosting/">A2 Hosting</a>, <a href="https://profiles.wordpress.org/a4jpcom/">a4jp . com</a>, <a href="https://profiles.wordpress.org/a6software/">a6software</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/abderrahman/">abderrahman</a>, <a href="https://profiles.wordpress.org/webcommsat/">Abha Thakor</a>, <a href="https://profiles.wordpress.org/ibachal/">Achal Jain</a>, <a href="https://profiles.wordpress.org/achbed/">achbed</a>, <a href="https://profiles.wordpress.org/achyuthajoy/">Achyuth Ajoy</a>, <a href="https://profiles.wordpress.org/acosmin/">acosmin</a>, <a href="https://profiles.wordpress.org/acsnaterse/">acsnaterse</a>, <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a>, <a href="https://profiles.wordpress.org/addiestavlo/">Addie</a>, <a href="https://profiles.wordpress.org/addyosmani/">addyosmani</a>, <a href="https://profiles.wordpress.org/adnanlimdi/">adnan.limdi</a>, <a href="https://profiles.wordpress.org/adrian/">adrian</a>, <a href="https://profiles.wordpress.org/airamerica/">airamerica</a>, <a href="https://profiles.wordpress.org/ajayghaghretiya1/">Ajay Ghaghretiya</a>, <a href="https://profiles.wordpress.org/ajitbohra/">Ajit Bohra</a>, <a href="https://profiles.wordpress.org/akbarhusen/">akbarhusen</a>, <a href="https://profiles.wordpress.org/akbarhusen429/">akbarhusen429</a>, <a href="https://profiles.wordpress.org/akhileshsabharwal/">Akhilesh Sabharwal</a>, <a href="https://profiles.wordpress.org/atachibana/">Akira Tachibana</a>, <a href="https://profiles.wordpress.org/schlessera/">Alain Schlesser</a>, <a href="https://profiles.wordpress.org/aljullu/">Albert Juh&#233; Lluveras</a>, <a href="https://profiles.wordpress.org/xknown/">Alex Concha</a>, <a href="https://profiles.wordpress.org/akirk/">Alex Kirk</a>, <a href="https://profiles.wordpress.org/ajlende/">Alex Lende</a>, <a href="https://profiles.wordpress.org/tellyworth/">Alex Shiels</a>, <a href="https://profiles.wordpress.org/alishanvr/">Ali Shan</a>, <a href="https://profiles.wordpress.org/ali11007/">ali11007</a>, <a href="https://profiles.wordpress.org/allendav/">Allen Snook</a>, <a href="https://profiles.wordpress.org/amaschas/">amaschas</a>, <a href="https://profiles.wordpress.org/wpamitkumar/">Amit Dudhat</a>, <a href="https://profiles.wordpress.org/anbumz/">anbumz</a>, <a href="https://profiles.wordpress.org/andfinally/">andfinally</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/andreamiddleton/">Andrea Middleton</a>, <a href="https://profiles.wordpress.org/dontdream/">Andrea Tarantini</a>, <a href="https://profiles.wordpress.org/andraganescu/">Andrei Draganescu</a>, <a href="https://profiles.wordpress.org/aduth/">Andrew Duthie</a>, <a href="https://profiles.wordpress.org/nacin/">Andrew Nacin</a>, <a href="https://profiles.wordpress.org/anevins/">Andrew Nevins</a>, <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/rarst/">Andrey "Rarst" Savchenko</a>, <a href="https://profiles.wordpress.org/nosolosw/">Andrés Maneiro</a>, <a href="https://profiles.wordpress.org/afragen/">Andy Fragen</a>, <a href="https://profiles.wordpress.org/andizer/">Andy Meerwaldt</a>, <a href="https://profiles.wordpress.org/apeatling/">Andy Peatling</a>, <a href="https://profiles.wordpress.org/akissz/">Angel Hess</a>, <a href="https://profiles.wordpress.org/angelasjin/">Angela Jin</a>, <a href="https://profiles.wordpress.org/la-geek/">Angelika Reisiger</a>, <a href="https://profiles.wordpress.org/rilwis/">Anh Tran</a>, <a href="https://profiles.wordpress.org/wpgurudev/">Ankit Gade</a>, <a href="https://profiles.wordpress.org/ankit-k-gupta/">Ankit K Gupta</a>, <a href="https://profiles.wordpress.org/ankitmaru/">Ankit Panchal</a>, <a href="https://profiles.wordpress.org/annezazu/">Anne McCarthy</a>, <a href="https://profiles.wordpress.org/antpb/">Anthony Burchell</a>, <a href="https://profiles.wordpress.org/ahortin/">Anthony Hortin</a>, <a href="https://profiles.wordpress.org/atimmer/">Anton Timmermans</a>, <a href="https://profiles.wordpress.org/antonisme/">Antonis Lilis</a>, <a href="https://profiles.wordpress.org/apedog/">apedog</a>, <a href="https://profiles.wordpress.org/archon810/">archon810</a>, <a href="https://profiles.wordpress.org/argentite/">argentite</a>, <a href="https://profiles.wordpress.org/arpitgshah/">Arpit G Shah</a>, <a href="https://profiles.wordpress.org/passoniate/">Arslan Ahmed</a>, <a href="https://profiles.wordpress.org/asalce/">asalce</a>, <a href="https://profiles.wordpress.org/ashiagr/">ashiagr</a>, <a href="https://profiles.wordpress.org/ashour/">ashour</a>, <a href="https://profiles.wordpress.org/tacitonic/">Atharva Dhekne</a>, <a href="https://profiles.wordpress.org/ajoah/">Aur&#233;lien Joahny</a>, <a href="https://profiles.wordpress.org/aussi/">aussi</a>, <a href="https://profiles.wordpress.org/automaton/">automaton</a>, <a href="https://profiles.wordpress.org/avixansa/">avixansa</a>, <a href="https://profiles.wordpress.org/ayeshrajans/">Ayesh Karunaratne</a>, <a href="https://profiles.wordpress.org/backups/">BackuPs</a>, <a href="https://profiles.wordpress.org/barry/">Barry</a>, <a href="https://profiles.wordpress.org/barryceelen/">Barry Ceelen</a>, <a href="https://profiles.wordpress.org/bartczyz/">Bart Czyz</a>, <a href="https://profiles.wordpress.org/bartekcholewa/">bartekcholewa</a>, <a href="https://profiles.wordpress.org/bartkalisz/">bartkalisz</a>, <a href="https://profiles.wordpress.org/bastho/">Bastien Ho</a>, <a href="https://profiles.wordpress.org/bmartinent/">Bastien Martinent</a>, <a href="https://profiles.wordpress.org/bcworkz/">bcworkz</a>, <a href="https://profiles.wordpress.org/bdbch/">bdbch</a>, <a href="https://profiles.wordpress.org/bdcstr/">bdcstr</a>, <a href="https://profiles.wordpress.org/empireoflight/">Ben Dunkle</a>, <a href="https://profiles.wordpress.org/grapestain/">Bence Szalai</a>, <a href="https://profiles.wordpress.org/bencroskery/">bencroskery</a>, <a href="https://profiles.wordpress.org/benjamingosset/">Benjamin Gosset</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/bettyjj/">BettyJJ</a>, <a href="https://profiles.wordpress.org/bgermann/">bgermann</a>, <a href="https://profiles.wordpress.org/bigcloudmedia/">bigcloudmedia</a>, <a href="https://profiles.wordpress.org/bigdawggi/">bigdawggi</a>, <a href="https://profiles.wordpress.org/billerickson/">Bill Erickson</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/bjornw/">BjornW</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/bbrdaric/">Boris Brdarić</a>, <a href="https://profiles.wordpress.org/ibdz/">Boy Witthaya</a>, <a href="https://profiles.wordpress.org/kraftbj/">Brandon Kraft</a>, <a href="https://profiles.wordpress.org/bpayton/">Brandon Payton</a>, <a href="https://profiles.wordpress.org/brentswisher/">Brent Swisher</a>, <a href="https://profiles.wordpress.org/brianhogg/">Brian Hogg</a>, <a href="https://profiles.wordpress.org/krogsgard/">Brian Krogsgard</a>, <a href="https://profiles.wordpress.org/bruandet/">bruandet</a>, <a href="https://profiles.wordpress.org/bhargavbhandari90/">Bunty</a>, <a href="https://profiles.wordpress.org/burhandodhy/">Burhan Nasir</a>, <a href="https://profiles.wordpress.org/caiocrcosta/">caiocrcosta</a>, <a href="https://profiles.wordpress.org/cvoell/">Cameron Voell</a>, <a href="https://profiles.wordpress.org/cameronamcintyre/">cameronamcintyre</a>, <a href="https://profiles.wordpress.org/carike/">Carike</a>, <a href="https://profiles.wordpress.org/stuffradio/">Carl Wuensche</a>, <a href="https://profiles.wordpress.org/carloslfu/">Carlos Galarza</a>, <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a>, <a href="https://profiles.wordpress.org/sixhours/">Caroline Moore</a>, <a href="https://profiles.wordpress.org/carriganvb/">Carrigan</a>, <a href="https://profiles.wordpress.org/ceyhun/">ceyhun</a>, <a href="https://profiles.wordpress.org/shireling/">Chad</a>, <a href="https://profiles.wordpress.org/cbutlerjr/">Chad Butler</a>, <a href="https://profiles.wordpress.org/mackensen/">Charles Fulton</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/chipsnyder/">Chip Snyder</a>, <a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a>, <a href="https://profiles.wordpress.org/chouby/">Chouby</a>, <a href="https://profiles.wordpress.org/chrisvanpatten/">Chris Van Patten</a>, <a href="https://profiles.wordpress.org/chriscct7/">chriscct7</a>, <a href="https://profiles.wordpress.org/christian1012/">Christian Chung</a>, <a href="https://profiles.wordpress.org/cjbj/">Christian Jongeneel</a>, <a href="https://profiles.wordpress.org/pixelverbieger/">Christian Sabo</a>, <a href="https://profiles.wordpress.org/needle/">Christian Wach</a>, <a href="https://profiles.wordpress.org/christophherr/">Christoph Herr</a>, <a href="https://profiles.wordpress.org/vimes1984/">Christopher Churchill</a>, <a href="https://profiles.wordpress.org/chunkysteveo/">chunkysteveo</a>, <a href="https://profiles.wordpress.org/cklee/">cklee</a>, <a href="https://profiles.wordpress.org/clayray/">clayray</a>, <a href="https://profiles.wordpress.org/claytoncollie/">Clayton Collie</a>, <a href="https://profiles.wordpress.org/cliffpaulick/">Clifford Paulick</a>, <a href="https://profiles.wordpress.org/codeforest/">codeforest</a>, <a href="https://profiles.wordpress.org/commeuneimage/">Commeuneimage</a>, <a href="https://profiles.wordpress.org/copons/">Copons</a>, <a href="https://profiles.wordpress.org/coreymckrill/">Corey McKrill</a>, <a href="https://profiles.wordpress.org/cpasqualini/">cpasqualini</a>, <a href="https://profiles.wordpress.org/cristovaov/">Cristovao Verstraeten</a>, <a href="https://profiles.wordpress.org/littlebigthing/">Csaba (LittleBigThings)</a>, <a href="https://profiles.wordpress.org/curtisbelt/">Curtis Belt</a>, <a href="https://profiles.wordpress.org/clarinetlord/">Cyrus Collier</a>, <a href="https://profiles.wordpress.org/dperonne/">D.PERONNE</a>, <a href="https://profiles.wordpress.org/dsixinetu/">d6</a>, <a href="https://profiles.wordpress.org/danielbachhuber/">Daniel Bachhuber</a>, <a href="https://profiles.wordpress.org/danielhuesken/">Daniel H&#252;sken</a>, <a href="https://profiles.wordpress.org/danieltj/">Daniel James</a>, <a href="https://profiles.wordpress.org/diddledan/">Daniel Llewellyn</a>, <a href="https://profiles.wordpress.org/talldanwp/">Daniel Richards</a>, <a href="https://profiles.wordpress.org/confridin/">Daniel Roch</a>, <a href="https://profiles.wordpress.org/mte90/">Daniele Scasciafratte</a>, <a href="https://profiles.wordpress.org/dboy1988/">Danny</a>, <a href="https://profiles.wordpress.org/darkog/">Darko G.</a>, <a href="https://profiles.wordpress.org/nerrad/">Darren Ethier (nerrad)</a>, <a href="https://profiles.wordpress.org/dmchale/">Dave McHale</a>, <a href="https://profiles.wordpress.org/drw158/">Dave Whitley</a>, <a href="https://profiles.wordpress.org/davidakennedy/">David A. Kennedy</a>, <a href="https://profiles.wordpress.org/davilera/">David Aguilera</a>, <a href="https://profiles.wordpress.org/davidanderson/">David Anderson</a>, <a href="https://profiles.wordpress.org/dartiss/">David Artiss</a>, <a href="https://profiles.wordpress.org/davidbaumwald/">David Baumwald</a>, <a href="https://profiles.wordpress.org/davidbinda/">David Binovec</a>, <a href="https://profiles.wordpress.org/dbrumbaugh10up/">David Brumbaugh</a>, <a href="https://profiles.wordpress.org/desmith/">David E. Smith</a>, <a href="https://profiles.wordpress.org/dlh/">David Herrera</a>, <a href="https://profiles.wordpress.org/dryanpress/">David Ryan</a>, <a href="https://profiles.wordpress.org/dshanske/">David Shanske</a>, <a href="https://profiles.wordpress.org/get_dave/">David Smith</a>, <a href="https://profiles.wordpress.org/davidvee/">davidvee</a>, <a href="https://profiles.wordpress.org/dchymko/">dchymko</a>, <a href="https://profiles.wordpress.org/dkarfa/">Debabrata Karfa</a>, <a href="https://profiles.wordpress.org/deepaklalwani/">Deepak Lalwani</a>, <a href="https://profiles.wordpress.org/dekervit/">dekervit</a>, <a href="https://profiles.wordpress.org/delowardev/">Delowar Hossain</a>, <a href="https://profiles.wordpress.org/demetris/">demetris</a>, <a href="https://profiles.wordpress.org/denisco/">Denis Yanchevskiy</a>, <a href="https://profiles.wordpress.org/derekakelly/">derekakelly</a>, <a href="https://profiles.wordpress.org/pcfreak30/">Derrick Hammer</a>, <a href="https://profiles.wordpress.org/emrikol/">Derrick Tennant</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/dimitrism/">Dimitris Mitsis</a>, <a href="https://profiles.wordpress.org/dingo_d/">dingo-d</a>, <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a>, <a href="https://profiles.wordpress.org/dency/">Dixita Dusara</a>, <a href="https://profiles.wordpress.org/djennez/">djennez</a>, <a href="https://profiles.wordpress.org/dmenard/">dmenard</a>, <a href="https://profiles.wordpress.org/dmethvin/">dmethvin</a>, <a href="https://profiles.wordpress.org/doc987/">doc987</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/dono12/">Dono12</a>, <a href="https://profiles.wordpress.org/doobeedoo/">Doobeedoo</a>, <a href="https://profiles.wordpress.org/dossy/">Dossy Shiobara</a>, <a href="https://profiles.wordpress.org/dpacks/">dpacks</a>, <a href="https://profiles.wordpress.org/dratwas/">dratwas</a>, <a href="https://profiles.wordpress.org/drewapicture/">Drew Jaynes</a>, <a href="https://profiles.wordpress.org/drlightman/">DrLightman</a>, <a href="https://profiles.wordpress.org/drprotocols/">DrProtocols</a>, <a href="https://profiles.wordpress.org/dsifford/">dsifford</a>, <a href="https://profiles.wordpress.org/dudo/">dudo</a>, <a href="https://profiles.wordpress.org/dushakov/">dushakov</a>, <a href="https://profiles.wordpress.org/dustinbolton/">Dustin Bolton</a>, <a href="https://profiles.wordpress.org/dvershinin/">dvershinin</a>, <a href="https://profiles.wordpress.org/cyberhobo/">Dylan Kuhn</a>, <a href="https://profiles.wordpress.org/elrae/">Earle Davies</a>, <a href="https://profiles.wordpress.org/seedsca/">ecotechie</a>, <a href="https://profiles.wordpress.org/eddiemoya/">Eddie Moya</a>, <a href="https://profiles.wordpress.org/eddystile/">Eddy</a>, <a href="https://profiles.wordpress.org/ediamin/">Edi Amin</a>, <a href="https://profiles.wordpress.org/ehtis/">ehtis</a>, <a href="https://profiles.wordpress.org/itsjusteileen/">Eileen Violini</a>, <a href="https://profiles.wordpress.org/ekatherine/">Ekaterina</a>, <a href="https://profiles.wordpress.org/ellatrix/">Ella van Durpe</a>, <a href="https://profiles.wordpress.org/elmastudio/">elmastudio</a>, <a href="https://profiles.wordpress.org/emanuel_blagonic/">Emanuel Blagonic</a>, <a href="https://profiles.wordpress.org/emlebrun/">Emilie LEBRUN</a>, <a href="https://profiles.wordpress.org/manooweb/">Emmanuel Hesry</a>, <a href="https://profiles.wordpress.org/enej/">Enej Bajgoric</a>, <a href="https://profiles.wordpress.org/enricosorcinelli/">Enrico Sorcinelli</a>, <a href="https://profiles.wordpress.org/epiqueras/">Enrique Piqueras</a>, <a href="https://profiles.wordpress.org/nrqsnchz/">Enrique Sánchez</a>, <a href="https://profiles.wordpress.org/shamai/">Eric</a>, <a href="https://profiles.wordpress.org/ericlewis/">Eric Andrew Lewis</a>, <a href="https://profiles.wordpress.org/ebinnion/">Eric Binnion</a>, <a href="https://profiles.wordpress.org/kebbet/">Erik Betshammar</a>, <a href="https://profiles.wordpress.org/folletto/">Erin 'Folletto' Casali</a>, <a href="https://profiles.wordpress.org/esemlabel/">esemlabel</a>, <a href="https://profiles.wordpress.org/esoj/">esoj</a>, <a href="https://profiles.wordpress.org/espiat/">espiat</a>, <a href="https://profiles.wordpress.org/estelaris/">Estela Rueda</a>, <a href="https://profiles.wordpress.org/etoledom/">etoledom</a>, <a href="https://profiles.wordpress.org/etruel/">etruel</a>, <a href="https://profiles.wordpress.org/ev3rywh3re/">Ev3rywh3re</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/gaambo/">Fabian Todt</a>, <a href="https://profiles.wordpress.org/fftfaisal/">Faisal Ahmed</a>, <a href="https://profiles.wordpress.org/flixos90/">Felix Arntz</a>, <a href="https://profiles.wordpress.org/felix-edelmann/">Felix Edelmann</a>, <a href="https://profiles.wordpress.org/ferdiesletering/">ferdiesletering</a>, <a href="https://profiles.wordpress.org/finomeno/">finomeno</a>, <a href="https://profiles.wordpress.org/florianbrinkmann/">Florian Brinkmann</a>, <a href="https://profiles.wordpress.org/mista-flo/">Florian TIAR</a>, <a href="https://profiles.wordpress.org/truchot/">Florian Truchot</a>, <a href="https://profiles.wordpress.org/florianatwhodunit/">florianatwhodunit</a>, <a href="https://profiles.wordpress.org/foliovision/">FolioVision</a>, <a href="https://profiles.wordpress.org/francina/">Francesca Marano</a>, <a href="https://profiles.wordpress.org/francoist/">Francois Thibaud</a>, <a href="https://profiles.wordpress.org/futtta/">Frank Goossens</a>, <a href="https://profiles.wordpress.org/frank-klein/">Frank Klein</a>, <a href="https://profiles.wordpress.org/frankprendergast/">Frank.Prendergast</a>, <a href="https://profiles.wordpress.org/fjarrett/">Frankie Jarrett</a>, <a href="https://profiles.wordpress.org/franzarmas/">Franz Armas</a>, <a href="https://profiles.wordpress.org/fullofcaffeine/">fullofcaffeine</a>, <a href="https://profiles.wordpress.org/mintindeed/">Gabriel Koen</a>, <a href="https://profiles.wordpress.org/gma992/">Gabriel Maldonado</a>, <a href="https://profiles.wordpress.org/gmays/">Gabriel Mays</a>, <a href="https://profiles.wordpress.org/gadgetroid/">gadgetroid</a>, <a href="https://profiles.wordpress.org/galbaras/">Gal Baras</a>, <a href="https://profiles.wordpress.org/garavani/">Garavani</a>, <a href="https://profiles.wordpress.org/garethgillman/">garethgillman</a>, <a href="https://profiles.wordpress.org/garrett-eclipse/">Garrett Hyder</a>, <a href="https://profiles.wordpress.org/garyc40/">Gary Cao</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/gchtr/">gchtr</a>, <a href="https://profiles.wordpress.org/geertdd/">Geert De Deckere</a>, <a href="https://profiles.wordpress.org/geminilabs/">Gemini Labs</a>, <a href="https://profiles.wordpress.org/soulseekah/">Gennady Kovshenin</a>, <a href="https://profiles.wordpress.org/geriux/">geriux</a>, <a href="https://profiles.wordpress.org/giorgio25b/">Giorgio25b</a>, <a href="https://profiles.wordpress.org/gisselfeldt/">gisselfeldt</a>, <a href="https://profiles.wordpress.org/glendaviesnz/">glendaviesnz</a>, <a href="https://profiles.wordpress.org/goldsounds/">goldsounds</a>, <a href="https://profiles.wordpress.org/gh640/">Goto Hayato</a>, <a href="https://profiles.wordpress.org/gkloveweb/">Govind Kumar</a>, <a href="https://profiles.wordpress.org/greglone/">Gr&#233;gory Viguier</a>, <a href="https://profiles.wordpress.org/gradina/">gradina</a>, <a href="https://profiles.wordpress.org/gziolo/">Greg Ziółkowski</a>, <a href="https://profiles.wordpress.org/gregmulhauser/">gregmulhauser</a>, <a href="https://profiles.wordpress.org/grierson/">grierson</a>, <a href="https://profiles.wordpress.org/grzegorzjanoszka/">Grzegorz.Janoszka</a>, <a href="https://profiles.wordpress.org/gsmumbo/">gsmumbo</a>, <a href="https://profiles.wordpress.org/wido/">Guido Scialfa</a>, <a href="https://profiles.wordpress.org/guidobras/">guidobras</a>, <a href="https://profiles.wordpress.org/netsurfer2705/">Gunther Pilz</a>, <a href="https://profiles.wordpress.org/gwwar/">gwwar</a>, <a href="https://profiles.wordpress.org/hvar/">H-var</a>, <a href="https://profiles.wordpress.org/hakre/">hakre</a>, <a href="https://profiles.wordpress.org/halgatewood/">Halacious</a>, <a href="https://profiles.wordpress.org/hankthetank/">hankthetank</a>, <a href="https://profiles.wordpress.org/psdtohtmlguru/">Hapiuc Robert</a>, <a href="https://profiles.wordpress.org/hareesh-pillai/">Hareesh Pillai</a>, <a href="https://profiles.wordpress.org/haukep/">haukep</a>, <a href="https://profiles.wordpress.org/azhiyadev/">Hauwa</a>, <a href="https://profiles.wordpress.org/hazdiego/">Haz</a>, <a href="https://profiles.wordpress.org/h71/">Hector Farahani</a>, <a href="https://profiles.wordpress.org/helen/">Helen Hou-Sandi</a>, <a href="https://profiles.wordpress.org/henrywright/">Henry Wright</a>, <a href="https://profiles.wordpress.org/herregroen/">Herre Groen</a>, <a href="https://profiles.wordpress.org/hlanggo/">hlanggo</a>, <a href="https://profiles.wordpress.org/hommealone/">hommealone</a>, <a href="https://profiles.wordpress.org/ryanshoover/">Hoover</a>, <a href="https://profiles.wordpress.org/howdy_mcgee/">Howdy_McGee</a>, <a href="https://profiles.wordpress.org/hronak/">Hronak Nahar</a>, <a href="https://profiles.wordpress.org/huntlyc/">huntlyc</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/iandstewart/">Ian Stewart</a>, <a href="https://profiles.wordpress.org/ianjvr/">ianjvr</a>, <a href="https://profiles.wordpress.org/ifrins/">ifrins</a>, <a href="https://profiles.wordpress.org/infinum/">infinum</a>, <a href="https://profiles.wordpress.org/ipstenu/">Ipstenu (Mika Epstein)</a>, <a href="https://profiles.wordpress.org/isabel_brison/">Isabel Brison</a>, <a href="https://profiles.wordpress.org/ishitaka/">ishitaka</a>, <a href="https://profiles.wordpress.org/jdgrimes/">J.D. Grimes</a>, <a href="https://profiles.wordpress.org/jackfungi/">jackfungi</a>, <a href="https://profiles.wordpress.org/jacklinkers/">jacklinkers</a>, <a href="https://profiles.wordpress.org/jadonn/">Jadon N</a>, <a href="https://profiles.wordpress.org/jadpm/">jadpm</a>, <a href="https://profiles.wordpress.org/jagirbahesh/">jagirbahesh</a>, <a href="https://profiles.wordpress.org/whyisjake/">Jake Spurlock</a>, <a href="https://profiles.wordpress.org/jameskoster/">James Koster</a>, <a href="https://profiles.wordpress.org/jnylen0/">James Nylen</a>, <a href="https://profiles.wordpress.org/foack/">Jan Koch</a>, <a href="https://profiles.wordpress.org/janr/">Jan Reilink</a>, <a href="https://profiles.wordpress.org/janthiel/">Jan Thiel</a>, <a href="https://profiles.wordpress.org/javidalkaruzi/">Janvo Aldred</a>, <a href="https://profiles.wordpress.org/jarretc/">Jarret</a>, <a href="https://profiles.wordpress.org/jason_the_adams/">Jason Adams</a>, <a href="https://profiles.wordpress.org/strangerstudios/">Jason Coleman</a>, <a href="https://profiles.wordpress.org/boogah/">Jason Cosper</a>, <a href="https://profiles.wordpress.org/coolmann/">Jason Crouse</a>, <a href="https://profiles.wordpress.org/madtownlems/">Jason LeMahieu (MadtownLems)</a>, <a href="https://profiles.wordpress.org/jaz_on/">Jason Rouet</a>, <a href="https://profiles.wordpress.org/jaswsinc/">JasWSInc</a>, <a href="https://profiles.wordpress.org/javiercasares/">Javier Casares</a>, <a href="https://profiles.wordpress.org/shiki/">Jayson Basanes</a>, <a href="https://profiles.wordpress.org/jbinda/">jbinda</a>, <a href="https://profiles.wordpress.org/jbouganim/">jbouganim</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jean-Baptiste Audras</a>, <a href="https://profiles.wordpress.org/jean-david/">Jean-David Daviet</a>, <a href="https://profiles.wordpress.org/jeffr0/">Jeff Chandler</a>, <a href="https://profiles.wordpress.org/jfarthing84/">Jeff Farthing</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/jenmylo/">Jen</a>, <a href="https://profiles.wordpress.org/jenilk/">Jenil Kanani</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/jeremyyip/">Jeremy Yip</a>, <a href="https://profiles.wordpress.org/jeroenrotty/">Jeroen Rotty</a>, <a href="https://profiles.wordpress.org/jeryj/">jeryj</a>, <a href="https://profiles.wordpress.org/jesin/">Jesin A</a>, <a href="https://profiles.wordpress.org/jigneshnakrani/">Jignesh Nakrani</a>, <a href="https://profiles.wordpress.org/jim_panse/">Jim_Panse</a>, <a href="https://profiles.wordpress.org/jipmoors/">Jip Moors</a>, <a href="https://profiles.wordpress.org/jivanpal/">jivanpal</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/joen/">Joen Asmussen</a>, <a href="https://profiles.wordpress.org/johannadevos/">Johanna de Vos</a>, <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a>, <a href="https://profiles.wordpress.org/jdorner/">John Dorner</a>, <a href="https://profiles.wordpress.org/johnjamesjacoby/">John James Jacoby</a>, <a href="https://profiles.wordpress.org/johnpgreen/">John P. Green</a>, <a href="https://profiles.wordpress.org/johnwatkins0/">John Watkins</a>, <a href="https://profiles.wordpress.org/johnnyb/">johnnyb</a>, <a href="https://profiles.wordpress.org/itsjonq/">Jon Quach</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/jrchamp/">Jonathan Champ</a>, <a href="https://profiles.wordpress.org/jchristopher/">Jonathan Christopher</a>, <a href="https://profiles.wordpress.org/desrosj/">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/jonathanstegall/">Jonathan Stegall</a>, <a href="https://profiles.wordpress.org/jonkolbert/">jonkolbert</a>, <a href="https://profiles.wordpress.org/spacedmonkey/">Jonny Harris</a>, <a href="https://profiles.wordpress.org/jonnybot/">jonnybot</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/koke/">Jorge Bernal</a>, <a href="https://profiles.wordpress.org/jorgefilipecosta/">Jorge Costa</a>, <a href="https://profiles.wordpress.org/josephdickson/">Joseph Dickson</a>, <a href="https://profiles.wordpress.org/chanthaboune/">Josepha Haden</a>, <a href="https://profiles.wordpress.org/procifer/">Josh Smith</a>, <a href="https://profiles.wordpress.org/joshuawold/">JoshuaWold</a>, <a href="https://profiles.wordpress.org/joyously/">Joy</a>, <a href="https://profiles.wordpress.org/juanfra/">Juanfra Aldasoro</a>, <a href="https://profiles.wordpress.org/juanlopez4691/">juanlopez4691</a>, <a href="https://profiles.wordpress.org/jules-colle/">Jules Colle</a>, <a href="https://profiles.wordpress.org/julianm/">julianm</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/jgrodel/">Julka Grodel</a>, <a href="https://profiles.wordpress.org/justinahinon/">Justin Ahinon</a>, <a href="https://profiles.wordpress.org/devesine/">Justin de Vesine</a>, <a href="https://profiles.wordpress.org/greenshady/">Justin Tadlock</a>, <a href="https://profiles.wordpress.org/justlevine/">justlevine</a>, <a href="https://profiles.wordpress.org/justnorris/">justnorris</a>, <a href="https://profiles.wordpress.org/kadamwhite/">K. Adam White</a>, <a href="https://profiles.wordpress.org/kaggdesign/">kaggdesign</a>, <a href="https://profiles.wordpress.org/trepmal/">Kailey (trepmal)</a>, <a href="https://profiles.wordpress.org/kaira/">Kaira</a>, <a href="https://profiles.wordpress.org/kaitlin414/">Kaitlin Bolling</a>, <a href="https://profiles.wordpress.org/akabarikalpesh/">Kalpesh Akabari</a>, <a href="https://profiles.wordpress.org/kamataryo/">KamataRyo</a>, <a href="https://profiles.wordpress.org/leprincenoir/">Kantari Samy</a>, <a href="https://profiles.wordpress.org/kasparsd/">Kaspars</a>, <a href="https://profiles.wordpress.org/properlypurple/">Kavya Gokul</a>, <a href="https://profiles.wordpress.org/keesiemeijer/">keesiemeijer</a>, <a href="https://profiles.wordpress.org/ryelle/">Kelly Dwan</a>, <a href="https://profiles.wordpress.org/kennethroberson5556/">kennethroberson5556</a>, <a href="https://profiles.wordpress.org/khag7/">Kevin Hagerty</a>, <a href="https://profiles.wordpress.org/kharisblank/">Kharis Sulistiyono</a>, <a href="https://profiles.wordpress.org/itzmekhokan/">Khokan Sardar</a>, <a href="https://profiles.wordpress.org/kinjaldalwadi/">kinjaldalwadi</a>, <a href="https://profiles.wordpress.org/kirilzh/">Kiril Zhelyazkov</a>, <a href="https://profiles.wordpress.org/kburgoine/">Kirsty Burgoine</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/ixkaito/">Kite</a>, <a href="https://profiles.wordpress.org/kjellr/">Kjell Reigstad</a>, <a href="https://profiles.wordpress.org/knutsp/">Knut Sparhell</a>, <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a>, <a href="https://profiles.wordpress.org/xkon/">Konstantinos Xenos</a>, <a href="https://profiles.wordpress.org/ksoares/">ksoares</a>, <a href="https://profiles.wordpress.org/kthmd/">KT Cheung</a>, <a href="https://profiles.wordpress.org/sainthkh/">Kukhyeon Heo</a>, <a href="https://profiles.wordpress.org/kbjohnson90/">Kyle B. Johnson</a>, <a href="https://profiles.wordpress.org/lalitpendhare/">lalitpendhare</a>, <a href="https://profiles.wordpress.org/landau/">landau</a>, <a href="https://profiles.wordpress.org/laternastudio/">Laterna Studio</a>, <a href="https://profiles.wordpress.org/laurelfulford/">laurelfulford</a>, <a href="https://profiles.wordpress.org/offereins/">Laurens Offereins</a>, <a href="https://profiles.wordpress.org/laxman-prajapati/">Laxman Prajapati</a>, <a href="https://profiles.wordpress.org/gamerz/">Lester Chan</a>, <a href="https://profiles.wordpress.org/levdbas/">Levdbas</a>, <a href="https://profiles.wordpress.org/layotte/">Lew Ayotte</a>, <a href="https://profiles.wordpress.org/lex_robinson/">Lex Robinson</a>, <a href="https://profiles.wordpress.org/linyows/">linyows</a>, <a href="https://profiles.wordpress.org/lipathor/">lipathor</a>, <a href="https://profiles.wordpress.org/lschuyler/">Lisa Schuyler</a>, <a href="https://profiles.wordpress.org/liuhaibin/">liuhaibin</a>, <a href="https://profiles.wordpress.org/ljharb/">ljharb</a>, <a href="https://profiles.wordpress.org/logig/">logig</a>, <a href="https://profiles.wordpress.org/lucasbustamante/">lucasbustamante</a>, <a href="https://profiles.wordpress.org/lwill/">luiswill</a>, <a href="https://profiles.wordpress.org/lukecavanagh/">Luke Cavanagh</a>, <a href="https://profiles.wordpress.org/happiryu/">Luke Walczak</a>, <a href="https://profiles.wordpress.org/lukestramasonder/">lukestramasonder</a>, <a href="https://profiles.wordpress.org/asif2bd/">M Asif Rahman</a>, <a href="https://profiles.wordpress.org/msafi/">M.K. Safi</a>, <a href="https://profiles.wordpress.org/cloudstek/">Maarten de Boer</a>, <a href="https://profiles.wordpress.org/aladin02dz/">Mahfoudh Arous</a>, <a href="https://profiles.wordpress.org/mailnew2ster/">mailnew2ster</a>, <a href="https://profiles.wordpress.org/manojlovic/">manojlovic</a>, <a href="https://profiles.wordpress.org/targz-1/">Manuel Schmalstieg</a>, <a href="https://profiles.wordpress.org/neodjandre/">maraki</a>, <a href="https://profiles.wordpress.org/iworks/">Marcin Pietrzak</a>, <a href="https://profiles.wordpress.org/marcio-zebedeu/">Marcio Zebedeu</a>, <a href="https://profiles.wordpress.org/pereirinha/">Marco Pereirinha</a>, <a href="https://profiles.wordpress.org/marcoz/">MarcoZ</a>, <a href="https://profiles.wordpress.org/netweblogic/">Marcus</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/marekhrabe/">Marek Hrabe</a>, <a href="https://profiles.wordpress.org/mariovalney/">Mario Valney</a>, <a href="https://profiles.wordpress.org/clorith/">Marius Jensen</a>, <a href="https://profiles.wordpress.org/machouinard/">Mark Chouinard</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/mapk/">Mark Uraine</a>, <a href="https://profiles.wordpress.org/markdubois/">markdubois</a>, <a href="https://profiles.wordpress.org/markgoho/">markgoho</a>, <a href="https://profiles.wordpress.org/vindl/">Marko Andrijasevic</a>, <a href="https://profiles.wordpress.org/markoheijnen/">Marko Heijnen</a>, <a href="https://profiles.wordpress.org/markrh/">MarkRH</a>, <a href="https://profiles.wordpress.org/markshep/">markshep</a>, <a href="https://profiles.wordpress.org/markusthiel/">markusthiel</a>, <a href="https://profiles.wordpress.org/martijn-van-der-kooij/">Martijn van der Kooij</a>, <a href="https://profiles.wordpress.org/martychc23/">martychc23</a>, <a href="https://profiles.wordpress.org/marybaum/">Mary Baum</a>, <a href="https://profiles.wordpress.org/matheusfd/">Matheus Martins</a>, <a href="https://profiles.wordpress.org/imath/">Mathieu Viet</a>, <a href="https://profiles.wordpress.org/matveb/">Matias Ventura</a>, <a href="https://profiles.wordpress.org/matjack1/">matjack1</a>, <a href="https://profiles.wordpress.org/webdevmattcrom/">Matt Cromwell</a>, <a href="https://profiles.wordpress.org/gothickgothickorguk/">Matt Gibson</a>, <a href="https://profiles.wordpress.org/matt/">Matt Mullenweg</a>, <a href="https://profiles.wordpress.org/mattrad/">Matt Radford</a>, <a href="https://profiles.wordpress.org/veraxus/">Matt van Andel</a>, <a href="https://profiles.wordpress.org/mattchowning/">mattchowning</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/beatpanda/">Matthew Gerring</a>, <a href="https://profiles.wordpress.org/kittmedia/">Matthias Kittsteiner</a>, <a href="https://profiles.wordpress.org/pfefferle/">Matthias Pfefferle</a>, <a href="https://profiles.wordpress.org/matthieumota/">Matthieu Mota</a>, <a href="https://profiles.wordpress.org/mattyrob/">mattyrob</a>, <a href="https://profiles.wordpress.org/maximeculea/">Maxime Culea</a>, <a href="https://profiles.wordpress.org/maxpertici/">Maxime Pertici</a>, <a href="https://profiles.wordpress.org/maxme/">maxme</a>, <a href="https://profiles.wordpress.org/mayankmajeji/">Mayank Majeji</a>, <a href="https://profiles.wordpress.org/mcshane/">mcshane</a>, <a href="https://profiles.wordpress.org/melchoyce/">Mel Choyce-Dwan</a>, <a href="https://profiles.wordpress.org/menakas/">Menaka S.</a>, <a href="https://profiles.wordpress.org/mensmaximus/">mensmaximus</a>, <a href="https://profiles.wordpress.org/metalandcoffee/">metalandcoffee</a>, <a href="https://profiles.wordpress.org/lilmike/">Michael</a>, <a href="https://profiles.wordpress.org/michael-arestad/">Michael Arestad</a>, <a href="https://profiles.wordpress.org/michaelarestad/">Michael Arestad</a>, <a href="https://profiles.wordpress.org/tw2113/">Michael Beckwith</a>, <a href="https://profiles.wordpress.org/mfields/">Michael Fields</a>, <a href="https://profiles.wordpress.org/mnelson4/">Michael Nelson</a>, <a href="https://profiles.wordpress.org/m_butcher/">Michele Butcher-Jones</a>, <a href="https://profiles.wordpress.org/marktimemedia/">Michelle</a>, <a href="https://profiles.wordpress.org/mcsf/">Miguel Fonseca</a>, <a href="https://profiles.wordpress.org/mihdan/">mihdan</a>, <a href="https://profiles.wordpress.org/miinasikk/">Miina Sikk</a>, <a href="https://profiles.wordpress.org/simison/">Mikael Korpela</a>, <a href="https://profiles.wordpress.org/mikaumoto/">mikaumoto</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/mike-haydon-swo/">Mike Haydon</a>, <a href="https://profiles.wordpress.org/mikeschinkel/">Mike Schinkel [WPLib Box project lead]</a>, <a href="https://profiles.wordpress.org/mikeschroder/">Mike Schroder</a>, <a href="https://profiles.wordpress.org/mikeyarce/">Mikey Arce</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/mislavjuric/">mislavjuric</a>, <a href="https://profiles.wordpress.org/batmoo/">Mohammad Jangda</a>, <a href="https://profiles.wordpress.org/opurockey/">Mohammad Rockeybul Alam</a>, <a href="https://profiles.wordpress.org/mohsinrasool/">Mohsin Rasool</a>, <a href="https://profiles.wordpress.org/monikarao/">Monika Rao</a>, <a href="https://profiles.wordpress.org/gwendydd/">Morgan Kay</a>, <a href="https://profiles.wordpress.org/mor10/">Morten Rand-Hendriksen</a>, <a href="https://profiles.wordpress.org/man4toman/">Morteza Geransayeh</a>, <a href="https://profiles.wordpress.org/mt8biz/">moto hachi ( mt8.biz )</a>, <a href="https://profiles.wordpress.org/mrgrt/">mrgrt</a>, <a href="https://profiles.wordpress.org/mrmist/">mrmist</a>, <a href="https://profiles.wordpress.org/mrtall/">mrTall</a>, <a href="https://profiles.wordpress.org/msaggiorato/">msaggiorato</a>, <a href="https://profiles.wordpress.org/musamamasood/">Muhammad Usama Masood</a>, <a href="https://profiles.wordpress.org/mukesh27/">Mukesh Panchal</a>, <a href="https://profiles.wordpress.org/munyagu/">munyagu</a>, <a href="https://profiles.wordpress.org/nabilmoqbel/">Nabil Moqbel</a>, <a href="https://profiles.wordpress.org/assassinateur/">Nadir Seghir</a>, <a href="https://profiles.wordpress.org/nfmohit/">Nahid Ferdous Mohit</a>, <a href="https://profiles.wordpress.org/nalininonstopnewsuk/">Nalini Thakor</a>, <a href="https://profiles.wordpress.org/nao/">Naoko Takano</a>, <a href="https://profiles.wordpress.org/narwen/">narwen</a>, <a href="https://profiles.wordpress.org/nateinaction/">Nate Gay</a>, <a href="https://profiles.wordpress.org/nathanrice/">Nathan Rice</a>, <a href="https://profiles.wordpress.org/navidos/">Navid</a>, <a href="https://profiles.wordpress.org/neonkowy/">neonkowy</a>, <a href="https://profiles.wordpress.org/krstarica/">net</a>, <a href="https://profiles.wordpress.org/netpassprodsr/">netpassprodsr</a>, <a href="https://profiles.wordpress.org/nextendweb/">Nextendweb</a>, <a href="https://profiles.wordpress.org/calvin_ngan/">Ngan Tengyuen</a>, <a href="https://profiles.wordpress.org/nickdaugherty/">Nick Daugherty</a>, <a href="https://profiles.wordpress.org/nickylimjj/">Nicky Lim</a>, <a href="https://profiles.wordpress.org/vadimnicolai/">nicolad</a>, <a href="https://profiles.wordpress.org/rahe/">Nicolas Juen</a>, <a href="https://profiles.wordpress.org/nicolaskulka/">NicolasKulka</a>, <a href="https://profiles.wordpress.org/jainnidhi/">Nidhi Jain</a>, <a href="https://profiles.wordpress.org/nielsdeblaauw/">Niels de Blaauw</a>, <a href="https://profiles.wordpress.org/nielslange/">Niels Lange</a>, <a href="https://profiles.wordpress.org/nigrosimone/">nigro.simone</a>, <a href="https://profiles.wordpress.org/nikhilbhansi/">Nikhil Bhansi</a>, <a href="https://profiles.wordpress.org/nbachiyski/">Nikolay Bachiyski</a>, <a href="https://profiles.wordpress.org/nilovelez/">Nilo Velez</a>, <a href="https://profiles.wordpress.org/niresh12495/">Niresh</a>, <a href="https://profiles.wordpress.org/nmenescardi/">nmenescardi</a>, <a href="https://profiles.wordpress.org/noahtallen/">Noah Allen</a>, <a href="https://profiles.wordpress.org/ntsekouras/">ntsekouras</a>, <a href="https://profiles.wordpress.org/numidwasnotavailable/">NumidWasNotAvailable</a>, <a href="https://profiles.wordpress.org/oakesjosh/">oakesjosh</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/oglekler/">Olga Gleckler</a>, <a href="https://profiles.wordpress.org/alshakero/">Omar Alshaker</a>, <a href="https://profiles.wordpress.org/omarreiss/">Omar Reiss</a>, <a href="https://profiles.wordpress.org/onokazu/">onokazu</a>, <a href="https://profiles.wordpress.org/optimizingmatters/">Optimizing Matters</a>, <a href="https://profiles.wordpress.org/ov3rfly/">Ov3rfly</a>, <a href="https://profiles.wordpress.org/ovann86/">ovann86</a>, <a href="https://profiles.wordpress.org/overclokk/">overclokk</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/pablohoneyhoney/">Pablo Honey</a>, <a href="https://profiles.wordpress.org/paddy/">Paddy</a>, <a href="https://profiles.wordpress.org/palmiak/">palmiak</a>, <a href="https://profiles.wordpress.org/paresh07/">Paresh Shinde</a>, <a href="https://profiles.wordpress.org/parvand/">Parvand</a>, <a href="https://profiles.wordpress.org/swissspidy/">Pascal Birchler</a>, <a href="https://profiles.wordpress.org/casiepa/">Pascal Casier</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/pdfernhout/">Paul Fernhout</a>, <a href="https://profiles.wordpress.org/djpaul/">Paul Gibbs</a>, <a href="https://profiles.wordpress.org/figureone/">Paul Ryan</a>, <a href="https://profiles.wordpress.org/paulschreiber/">Paul Schreiber</a>, <a href="https://profiles.wordpress.org/paulstonier/">Paul Stonier</a>, <a href="https://profiles.wordpress.org/pschrottky/">Paul Von Schrottky</a>, <a href="https://profiles.wordpress.org/pavelevap/">pavelevap</a>, <a href="https://profiles.wordpress.org/pedromendonca/">Pedro Mendon&#231;a</a>, <a href="https://profiles.wordpress.org/pentatonicfunk/">pentatonicfunk</a>, <a href="https://profiles.wordpress.org/pputzer/">pepe</a>, <a href="https://profiles.wordpress.org/pessoft/">Peter "Pessoft" Kol&#237;nek</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/pderksen/">Phil Derksen</a>, <a href="https://profiles.wordpress.org/johnstonphilip/">Phil Johnston</a>, <a href="https://profiles.wordpress.org/philipmjackson/">Philip Jackson</a>, <a href="https://profiles.wordpress.org/pierlo/">Pierre Gordon</a>, <a href="https://profiles.wordpress.org/pigdog234/">pigdog234</a>, <a href="https://profiles.wordpress.org/pikamander2/">pikamander2</a>, <a href="https://profiles.wordpress.org/pingram3541/">pingram</a>, <a href="https://profiles.wordpress.org/pionect/">Pionect</a>, <a href="https://profiles.wordpress.org/piyushmca/">Piyush Patel</a>, <a href="https://profiles.wordpress.org/pkarjala/">pkarjala</a>, <a href="https://profiles.wordpress.org/pkvillanueva/">pkvillanueva</a>, <a href="https://profiles.wordpress.org/pmbaldha/">Prashant Baldha</a>, <a href="https://profiles.wordpress.org/pratik028/">pratik028</a>, <a href="https://profiles.wordpress.org/pravinparmar2404/">Pravin Parmar</a>, <a href="https://profiles.wordpress.org/presskopp/">Presskopp</a>, <a href="https://profiles.wordpress.org/presslabs/">Presslabs</a>, <a href="https://profiles.wordpress.org/priyankkpatel/">Priyank Patel</a>, <a href="https://profiles.wordpress.org/priyomukul/">Priyo Mukul</a>, <a href="https://profiles.wordpress.org/prografika/">ProGrafika</a>, <a href="https://profiles.wordpress.org/programmin/">programmin</a>, <a href="https://profiles.wordpress.org/puneetsahalot/">Puneet Sahalot</a>, <a href="https://profiles.wordpress.org/pvogel2/">pvogel2</a>, <a href="https://profiles.wordpress.org/r-a-y/">r-a-y</a>, <a href="https://profiles.wordpress.org/raajtram/">Raaj Trambadia</a>, <a href="https://profiles.wordpress.org/larrach/">Rachel Peter</a>, <a href="https://profiles.wordpress.org/raineorshine/">raine</a>, <a href="https://profiles.wordpress.org/rajeshsingh520/">rajeshsingh520</a>, <a href="https://profiles.wordpress.org/superpoincare/">Ramanan</a>, <a href="https://profiles.wordpress.org/ramiy/">Rami Yushuvaev</a>, <a href="https://profiles.wordpress.org/rastaban/">Rastaban</a>, <a href="https://profiles.wordpress.org/ravanh/">RavanH</a>, <a href="https://profiles.wordpress.org/ravatparmar/">Ravat Parmar</a>, <a href="https://profiles.wordpress.org/ravenswd/">ravenswd</a>, <a href="https://profiles.wordpress.org/rawrly/">rawrly</a>, <a href="https://profiles.wordpress.org/rebasaurus/">rebasaurus</a>, <a href="https://profiles.wordpress.org/redsand/">Red Sand Media Group</a>, <a href="https://profiles.wordpress.org/tabrisrp/">Remy Perona</a>, <a href="https://profiles.wordpress.org/remzicavdar/">Remzi Cavdar</a>, <a href="https://profiles.wordpress.org/renathoc/">Renatho</a>, <a href="https://profiles.wordpress.org/renggo888/">renggo888</a>, <a href="https://profiles.wordpress.org/retlehs/">retlehs</a>, <a href="https://profiles.wordpress.org/retrofox/">retrofox</a>, <a href="https://profiles.wordpress.org/riaanlom/">riaanlom</a>, <a href="https://profiles.wordpress.org/youknowriad/">Riad Benguella</a>, <a href="https://profiles.wordpress.org/rianrietveld/">Rian Rietveld</a>, <a href="https://profiles.wordpress.org/riasat/">riasat</a>, <a href="https://profiles.wordpress.org/richtabor/">Rich Tabor</a>, <a href="https://profiles.wordpress.org/ringisha/">Ringisha</a>, <a href="https://profiles.wordpress.org/ritterml/">ritterml</a>, <a href="https://profiles.wordpress.org/rnaby/">Rnaby</a>, <a href="https://profiles.wordpress.org/rcutmore/">Rob Cutmore</a>, <a href="https://profiles.wordpress.org/dhrrob/">Rob Migchels</a>, <a href="https://profiles.wordpress.org/rob006/">rob006</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/robertpeake/">Robert Peake</a>, <a href="https://profiles.wordpress.org/nullbyte/">Robert Windisch</a>, <a href="https://profiles.wordpress.org/kreppar/">Rodrigo Arias</a>, <a href="https://profiles.wordpress.org/ronalfy/">Ronald Huereca</a>, <a href="https://profiles.wordpress.org/costasovo/">Rostislav Woln&#253;</a>, <a href="https://profiles.wordpress.org/roytanck/">Roy Tanck</a>, <a href="https://profiles.wordpress.org/rtagliento/">rtagliento</a>, <a href="https://profiles.wordpress.org/ruxandra/">ruxandra</a>, <a href="https://profiles.wordpress.org/ryan/">Ryan Boren</a>, <a href="https://profiles.wordpress.org/bookdude13/">Ryan Fredlund</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/welcher/">Ryan Welcher</a>, <a href="https://profiles.wordpress.org/ryotasakamoto/">Ryota Sakamoto</a>, <a href="https://profiles.wordpress.org/ryotsun/">ryotsun</a>, <a href="https://profiles.wordpress.org/soean/">S&#246;ren Wrede</a>, <a href="https://profiles.wordpress.org/sorenbronsted/">S&#248;ren Br&#248;nsted</a>, <a href="https://profiles.wordpress.org/sachittandukar/">Sachit Tandukar</a>, <a href="https://profiles.wordpress.org/sagarjadhav/">Sagar Jadhav</a>, <a href="https://profiles.wordpress.org/sajjad67/">Sajjad Hossain Sagor</a>, <a href="https://profiles.wordpress.org/salcode/">Sal Ferrarello</a>, <a href="https://profiles.wordpress.org/salvatoreformisano/">Salvatore Formisano</a>, <a href="https://profiles.wordpress.org/salvoaranzulla/">salvoaranzulla</a>, <a href="https://profiles.wordpress.org/samful/">Sam Fullalove</a>, <a href="https://profiles.wordpress.org/sswebster/">Sam Webster</a>, <a href="https://profiles.wordpress.org/solarissmoke/">Samir Shah</a>, <a href="https://profiles.wordpress.org/otto42/">Samuel Wood (Otto)</a>, <a href="https://profiles.wordpress.org/samueljseay/">samueljseay</a>, <a href="https://profiles.wordpress.org/pacifika/">Sander van Dragt</a>, <a href="https://profiles.wordpress.org/sanzeeb3/">Sanjeev Aryal</a>, <a href="https://profiles.wordpress.org/progremzion/">Sanket Mehta</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/sayedwp/">Sayed Taqui</a>, <a href="https://profiles.wordpress.org/scarolan/">scarolan</a>, <a href="https://profiles.wordpress.org/scholdstrom/">scholdstrom</a>, <a href="https://profiles.wordpress.org/sc0ttkclark/">Scott Kingsley Clark</a>, <a href="https://profiles.wordpress.org/coffee2code/">Scott Reilly</a>, <a href="https://profiles.wordpress.org/scottsmith/">Scott Smith</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/scruffian/">scruffian</a>, <a href="https://profiles.wordpress.org/seanchayes/">Sean Hayes</a>, <a href="https://profiles.wordpress.org/seanpaulrasmussen/">seanpaulrasmussen</a>, <a href="https://profiles.wordpress.org/seayou/">seayou</a>, <a href="https://profiles.wordpress.org/senatorman/">senatorman</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/vjik/">Sergey Predvoditelev</a>, <a href="https://profiles.wordpress.org/sgr33n/">Sergio de Falco</a>, <a href="https://profiles.wordpress.org/sergiomdgomes/">sergiomdgomes</a>, <a href="https://profiles.wordpress.org/functionalrhyme/">Shannon Smith</a>, <a href="https://profiles.wordpress.org/wpshades/">Shantanu Desai</a>, <a href="https://profiles.wordpress.org/shaunandrews/">shaunandrews</a>, <a href="https://profiles.wordpress.org/shooper/">Shawn Hooper</a>, <a href="https://profiles.wordpress.org/shawnz/">shawnz</a>, <a href="https://profiles.wordpress.org/shital-patel/">Shital Marakana</a>, <a href="https://profiles.wordpress.org/shulard/">shulard</a>, <a href="https://profiles.wordpress.org/siliconforks/">siliconforks</a>, <a href="https://profiles.wordpress.org/simonwheatley/">Simon Wheatley</a>, <a href="https://profiles.wordpress.org/simonjanin/">simonjanin</a>, <a href="https://profiles.wordpress.org/sinatrateam/">sinatrateam</a>, <a href="https://profiles.wordpress.org/sjmur/">sjmur</a>, <a href="https://profiles.wordpress.org/skarabeq/">skarabeq</a>, <a href="https://profiles.wordpress.org/skorasaurus/">skorasaurus</a>, <a href="https://profiles.wordpress.org/skoskie/">skoskie</a>, <a href="https://profiles.wordpress.org/slushman/">slushman</a>, <a href="https://profiles.wordpress.org/snapfractalpop/">snapfractalpop</a>, <a href="https://profiles.wordpress.org/seth17/">SpearsMarketing</a>, <a href="https://profiles.wordpress.org/sphakka/">sphakka</a>, <a href="https://profiles.wordpress.org/squarecandy/">squarecandy</a>, <a href="https://profiles.wordpress.org/sreedoap/">sreedoap</a>, <a href="https://profiles.wordpress.org/sstoqnov/">Stanimir Stoyanov</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/sswells/">Steph Wells</a>, <a href="https://profiles.wordpress.org/sabernhardt/">Stephen Bernhardt</a>, <a href="https://profiles.wordpress.org/stephencronin/">Stephen Cronin</a>, <a href="https://profiles.wordpress.org/netweb/">Stephen Edgar</a>, <a href="https://profiles.wordpress.org/dufresnesteven/">Steve Dufresne</a>, <a href="https://profiles.wordpress.org/stevegibson12/">stevegibson12</a>, <a href="https://profiles.wordpress.org/sterndata/">Steven Stern (sterndata)</a>, <a href="https://profiles.wordpress.org/stevenkword/">Steven Word</a>, <a href="https://profiles.wordpress.org/stevenkussmaul/">stevenkussmaul</a>, <a href="https://profiles.wordpress.org/stevenlinx/">stevenlinx</a>, <a href="https://profiles.wordpress.org/stiofansisland/">Stiofan</a>, <a href="https://profiles.wordpress.org/subrataemfluence/">Subrata Sarkar</a>, <a href="https://profiles.wordpress.org/sum1/">SUM1</a>, <a href="https://profiles.wordpress.org/quadthemes/">Sunny</a>, <a href="https://profiles.wordpress.org/sunnyratilal/">Sunny Ratilal</a>, <a href="https://profiles.wordpress.org/sushyant/">Sushyant Zavarzadeh</a>, <a href="https://profiles.wordpress.org/suzylah/">suzylah</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/sergioestevao/">Sérgio Estêvão</a>, <a href="https://profiles.wordpress.org/miyauchi/">Takayuki Miyauchi</a>, <a href="https://profiles.wordpress.org/karmatosed/">Tammie Lister</a>, <a href="https://profiles.wordpress.org/tangrufus/">Tang Rufus</a>, <a href="https://profiles.wordpress.org/utz119/">TeBenachi</a>, <a href="https://profiles.wordpress.org/tessawatkinsllc/">Tessa Watkins LLC</a>, <a href="https://profiles.wordpress.org/wildworks/">Tetsuaki Hamano</a>, <a href="https://profiles.wordpress.org/themiked/">theMikeD</a>, <a href="https://profiles.wordpress.org/theolg/">theolg</a>, <a href="https://profiles.wordpress.org/tweetythierry/">Thierry Muller</a>, <a href="https://profiles.wordpress.org/thimalw/">thimalw</a>, <a href="https://profiles.wordpress.org/webzunft/">Thomas M</a>, <a href="https://profiles.wordpress.org/tfrommen/">Thorsten Frommen</a>, <a href="https://profiles.wordpress.org/thrijith/">Thrijith Thankachan</a>, <a href="https://profiles.wordpress.org/tiagohillebrandt/">Tiago Hillebrandt</a>, <a href="https://profiles.wordpress.org/tillkruess/">Till Kr&#252;ss</a>, <a href="https://profiles.wordpress.org/timothyblynjacobs/">Timothy Jacobs</a>, <a href="https://profiles.wordpress.org/tkama/">Tkama</a>, <a href="https://profiles.wordpress.org/tmdesigned/">tmdesigned</a>, <a href="https://profiles.wordpress.org/tmoore41/">tmoore41</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/tofandel/">Tofandel</a>, <a href="https://profiles.wordpress.org/tomdude/">tomdude</a>, <a href="https://profiles.wordpress.org/tferry/">Tommy Ferry</a>, <a href="https://profiles.wordpress.org/starbuck/">Tony G</a>, <a href="https://profiles.wordpress.org/toro_unit/">Toro_Unit (Hiroshi Urabe)</a>, <a href="https://profiles.wordpress.org/torres126/">torres126</a>, <a href="https://profiles.wordpress.org/zodiac1978/">Torsten Landsiedel</a>, <a href="https://profiles.wordpress.org/toru/">Toru Miki</a>, <a href="https://profiles.wordpress.org/travisnorthcutt/">Travis Northcutt</a>, <a href="https://profiles.wordpress.org/treecutter/">treecutter</a>, <a href="https://profiles.wordpress.org/truongwp/">truongwp</a>, <a href="https://profiles.wordpress.org/tsimmons/">tsimmons</a>, <a href="https://profiles.wordpress.org/dinhtungdu/">Tung Du</a>, <a href="https://profiles.wordpress.org/twentyzerotwo/">TwentyZeroTwo</a>, <a href="https://profiles.wordpress.org/desaiuditd/">Udit Desai</a>, <a href="https://profiles.wordpress.org/grapplerulrich/">Ulrich</a>, <a href="https://profiles.wordpress.org/vagios/">Vagios Vlachos</a>, <a href="https://profiles.wordpress.org/valchovski/">valchovski</a>, <a href="https://profiles.wordpress.org/valentinbora/">Valentin Bora</a>, <a href="https://profiles.wordpress.org/vayu/">Vayu Robins</a>, <a href="https://profiles.wordpress.org/veromary/">veromary</a>, <a href="https://profiles.wordpress.org/szepeviktor/">Viktor Sz&#233;pe</a>, <a href="https://profiles.wordpress.org/vinkla/">vinkla</a>, <a href="https://profiles.wordpress.org/virginienacci/">virginienacci</a>, <a href="https://profiles.wordpress.org/planvova/">Vladimir</a>, <a href="https://profiles.wordpress.org/vabrashev/">Vladislav Abrashev</a>, <a href="https://profiles.wordpress.org/vortfu/">vortfu</a>, <a href="https://profiles.wordpress.org/voyager131/">voyager131</a>, <a href="https://profiles.wordpress.org/vtieu/">vtieu</a>, <a href="https://profiles.wordpress.org/webaware/">webaware</a>, <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</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/planningwrite/">Winstina</a>, <a href="https://profiles.wordpress.org/wittich/">wittich</a>, <a href="https://profiles.wordpress.org/wpdesk/">wpdesk</a>, <a href="https://profiles.wordpress.org/wpdo5ea/">WPDO</a>, <a href="https://profiles.wordpress.org/alexandreb3/">WPMarmite</a>, <a href="https://profiles.wordpress.org/wppinar/">wppinar</a>, <a href="https://profiles.wordpress.org/yahil/">Yahil Madakiya</a>, <a href="https://profiles.wordpress.org/yashrs/">yashrs</a>, <a href="https://profiles.wordpress.org/yoancutillas/">yoancutillas</a>, <a href="https://profiles.wordpress.org/yoavf/">Yoav Farhi</a>, <a href="https://profiles.wordpress.org/yohannp/">yohannp</a>, <a href="https://profiles.wordpress.org/yuhin/">yuhin</a>, <a href="https://profiles.wordpress.org/fierevere/">Yui</a>, <a href="https://profiles.wordpress.org/ysalame/">Yuri Salame</a>, <a href="https://profiles.wordpress.org/yvettesonneveld/">Yvette Sonneveld</a>, <a href="https://profiles.wordpress.org/tollmanz/">Zack Tollman</a>, <a href="https://profiles.wordpress.org/zaheerahmad/">zaheerahmad</a>, <a href="https://profiles.wordpress.org/zakkath/">zakkath</a>, <a href="https://profiles.wordpress.org/zebulan/">Zebulan Stanphill</a>, <a href="https://profiles.wordpress.org/zieladam/">zieladam</a>, and <a href="https://profiles.wordpress.org/chesio/">Česlav Przywara</a>.



<p>&nbsp;</p>



<p>Many thanks to all of the community volunteers who contribute in the&nbsp;<a href="https://wordpress.org/support/">support forums</a>. They answer questions from people across the world, whether they are using WordPress for the first time or since the first release. These releases are more successful for their efforts!</p>



<p>Finally, thanks to all the community translators who worked on WordPress 5.5. Their efforts bring WordPress fully translated to&nbsp;46 languages at release time, with more on the way.</p>



<p>If you want to learn more about volunteering with WordPress, check out&nbsp;<a href="https://make.wordpress.org/">Make WordPress</a>&nbsp;or the&nbsp;<a href="https://make.wordpress.org/core/">core development blog</a>.</p>
</div>



<div class="wp-block-column"></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:"Tue, 11 Aug 2020 19:03:52 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"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: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:66:"WP Mobile Apps: How Do I Connect My WordPress.com or Jetpack Site?";s:7:"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:33:"http://apps.wordpress.com/?p=4037";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:88:"https://apps.wordpress.com/2020/08/11/how-do-i-connect-my-wordpress-com-or-jetpack-site/";s: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:1593:"<p>To access a site hosted with WordPress.com or connected to WordPress.com through the Jetpack plugin, log in with your WordPress.com credentials. After clicking on the <strong>Login button</strong>, select <strong>Continue with WordPress.com. </strong></p>



<p>You can also select the others options to <strong>Continue with Google</strong> or <strong>Continue with Apple</strong> if the email address linked to these services matches the email address of your WordPress.com account. </p>



<p>Next, <em>enter the email address</em> associated with your WordPress.com account and click <strong>next</strong>. From there you can either choose to receive a login link to be sent to your email address or click on the link to &#8220;enter your password instead&#8221; to use your password to log in.  If you select the option to receive a login link, you&#8217;ll be given the option to open Mail where you should have received a new email with a button to click to <strong>&#8216;Log in to the app&#8217;</strong>. This link expires in one hour and when clicked should redirect you to the app where you will see a list of your sites and have the option to either Connect another site or press &#8216;Done&#8217; to start managing your WordPress.com connected sites. </p>



<p>See the login procedure below:</p>



<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 11 Aug 2020 08:16:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Rebecca";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: Astra Theme Suspended and Reinstated, Themes Team Works Toward Delisting Strategy for Guideline Violations";s:7:"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=102960";s:7:"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:275:"https://wptavern.com/astra-theme-suspended-and-reinstated-themes-team-works-toward-delisting-strategy-for-guideline-violations?utm_source=rss&utm_medium=rss&utm_campaign=astra-theme-suspended-and-reinstated-themes-team-works-toward-delisting-strategy-for-guideline-violations";s: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:11208:"<img />



<p class="has-drop-cap">The Themes Team <a href="https://themes.trac.wordpress.org/ticket/87407#comment:3">suspended Astra</a> from the official theme directory just a few short weeks after it became the first non-default WordPress theme to <a href="https://wptavern.com/astra-becomes-the-only-non-default-wordpress-theme-with-1-million-installs">surpass one million active installs</a>. The reason: the theme was breaking the directory&rsquo;s ban on affiliate links. The theme has since been reinstated. However, it has been delisted from the popular themes list.</p>



<p>After the Themes Team handed down an initial five-week suspension, the story continued to unfold through various channels over the weekend and into the start of the new week. Brainstorm Force, the company behind the theme, <a href="https://themes.trac.wordpress.org/ticket/87407#comment:4">argued that it did not violate</a> the affiliate link rule because the theme was simply filtering referral IDs of third-party plugins.  The plugins were technically supplying the links. The company also asked for lenience because this was its first violation.</p>



<p>Since the initial discussion, the Themes Team has reinstated the theme while bumping it off the <a href="https://wordpress.org/themes/">popular themes list</a>. The goal is to make sure existing users still have access to updates while providing a method for dealing with guidelines violations, a method that does not go to the extreme of outright suspension. The team also added an additional week of punishment after finding a sixth affiliate-related violation missed in the initial review.  Astra will now be delisted for a total of six weeks.</p>



<p>Astra is not the first suspension of a popular theme over the years. These high-profile suspensions can lead to the loss of thousands of dollars in revenue if the theme&rsquo;s business model relies on traffic from WordPress.org. In 2017, a <a href="https://wptavern.com/zerif-lite-suspended-from-wordpress-theme-directory-300k-users-left-without-updates">five-month suspension</a> of the Zerif Lite theme left its creators with a <a href="https://wptavern.com/zerif-lite-returns-to-wordpress-org-after-5-month-suspension-and-63-decline-in-revenue">decline of 63% in revenue</a>. Zerif Lite&rsquo;s user count was around one-third of Astra&rsquo;s current total.</p>



<p>While it will take some time to see the results, being delisted will likely cut into Brainstorm Force&rsquo;s revenue. The theme upsells a <em>pro</em> version of their theme. It is a common <em>freemium</em> model that many theme companies employ.</p>



<p>The WordPress.org theme review guidelines <a href="https://make.wordpress.org/themes/handbook/review/required/#selling-credits-and-links">ban affiliate links</a>. More precisely, the guideline is as follows:</p>



<blockquote class="wp-block-quote"><p>Themes are not allowed to have affiliate URLs or links.</p></blockquote>



<p>Technically, Brainstorm Force did not directly output affiliate links via its theme. Instead, the theme injected the company&rsquo;s referral ID into affiliate links for third-party plugins when they were active on a user&rsquo;s site. In and of itself, this type of injection is nothing nefarious. The plugins themselves allow for such filtering of their affiliate links, presumably to entice theme authors to make a few dollars by recommending and integrating with them.</p>



<p>As for the Astra theme, the question is whether it violated the affiliate guideline. When the rule was written, the Themes Team was most likely thinking about direct links within the theme and not a scenario where a theme was injecting a referral ID or filtering an existing link from a plugin.</p>



<p>According to the Themes Team, at least two of the affiliate IDs in Astra were for plugins that the theme recommended but did not actually integrate with or support in any way. In at least once instance, the theme automatically updated a database option for the Monster Insights plugin to add an affiliate ID &mdash; automatically updating any database option without user action is generally not allowed.</p>



<p>Regardless of individual opinions on the Theme Team&rsquo;s complete ban of affiliate links, it is not a cut-and-dry situation of simply allowing or disallowing.</p>



<p>&ldquo;It is also about needing to understand the legal impact of disclosures,&rdquo; said Carolina Nymark, a team representative. &ldquo;It is not something that the team can take responsibility for, nor look away if authors do not follow it.&rdquo;</p>



<h2>Astra&rsquo;s Apology and Response</h2>



<img />



<p class="has-drop-cap">Sujay Pawar, a co-founder of Brainstorm Force, published an <a href="https://wpastra.com/open-letter/">open apology on the Astra blog</a>. However, this apology post created its own controversy within the community. The current post was not the first apology. Pawar changed his original post and removed some of the earlier promises he made to the community.</p>



<p>According to multiple sources within the community and a <a href="https://wpastra.com/open-letter/#comment-62065">comment on the post</a>, he had promised to dedicate 16 hours from one of the company&rsquo;s senior developers to contribute work for the Themes Team. Along with this contribution, he promised to spend 5% of the company&rsquo;s resources toward open source development and to donate to future WordCamps.</p>



<p>&ldquo;These last few days have been very emotional for me and the entire team,&rdquo; said Pawar. &ldquo;I have never been in such a stressful situation in my life. As you can imagine, I wrote many versions of this apology and just wasn&rsquo;t sure what was the best way to do it.&rdquo;</p>



<p>For some people in the community, changing the post&rsquo;s content seemed suspicious. He had changed it around the same time the theme was reinstated on WordPress.org. However, the issue was likely the result of bad timing. Pawar was forthcoming about having written the original post and later removing parts of it.</p>



<p>&ldquo;My initial apology did include the specifics of how we are planning to increase our commitment to WordPress, but after more thought, I felt it wasn&rsquo;t the right place to share that,&rdquo; he said. &ldquo;I don&rsquo;t want our contributions to be overshadowed or tied back to a rule violation. We still plan to honor our commitment, and we will release those details in a dedicated post.&rdquo;</p>



<p>Pawar has no hard feelings for the Themes Team. For him, it has been a high-stress weekend that he will no doubt recover from. He is attempting to rectify the situation the best he can.</p>



<p>&ldquo;I have a lot of respect for all members of Themes Team,&rdquo; he said. &ldquo;They work tirelessly to move the WordPress ecosystem forward. I 100% believe that guidelines must be enforced because it&rsquo;s the only way to ensure that WordPress keeps growing. As one of the most popular theme authors, it&rsquo;s our goal to lead by setting a good example and work together with the TRT to set better standards.&rdquo;</p>



<h2>Long Term: Delisting Themes Instead of Suspending</h2>



<img />



<p class="has-drop-cap">The Themes Team does not have a lot of options when it comes to punitive measures for guideline violations. In a large part, this is the result of limitations of the software in use. The team simply needs better tools.</p>



<p>&ldquo;The punitive measures the team has right now is suspend it or do nothing,&rdquo; said William Patton, a Themes Team representative. &ldquo;There is no in-between, and in a lot of cases, neither of those two options are ideal. From past experience, I have found that asking authors repeatedly for changes is either ineffective or they fix it but the behavior returns after a short time. Suspension has been quite effective in some cases but it is quite a lot of work for the team to manage and maintain lists or time frames of what happened when and to revisit after a given time.&rdquo;</p>



<p>Patton said that the threat of suspension without action is ineffective. However, actually going through with suspending a theme often has implications for end-users. In some cases, there may be an urgent security update that users need to get, but the suspension system does not make that easy to manage.</p>



<p>There is now an <a href="https://meta.trac.wordpress.org/ticket/5362">open meta ticket</a> to offer theme directory administrators the option to delist a theme. In effect, this would keep a theme such as Astra available in the directory if someone knows the direct URL. It would also allow the theme author to provide updates, such as security fixes, to users without direct approval from the Themes Team. However, the theme would not be available through the popular themes list or search.</p>



<p>This offers the team a less drastic option than a full-on suspension and has no negative drawbacks for existing theme users.</p>



<p>Currently, the team found what they described as a &ldquo;hacky&rdquo; method of essentially delisting Astra. Because the popular themes list algorithm uses the theme&rsquo;s publication date to help determine a theme&rsquo;s popularity, the team changed this date for the theme to push it down the popular list. It is not a perfect solution, but it provided a quick middle ground between doing nothing and suspension, at least until a more permanent solution is in place. It also gives them an early chance to test out the effects such a measure would have.</p>



<p>Punitive measures have always been a struggle for the team. On the one hand, they do not like to suspend themes for wrongdoing, regardless of whether such wrongdoing was intentional. On the other, they must attempt to provide a fair playing field for all theme authors. Threats of punishment for guideline violations ring hollow if there is no follow-through. It is not an easy position, and team members can quickly become victims of harassment or unwanted private messages from theme developers and outsiders.</p>



<p>&ldquo;We had several occasions where theme authors would &lsquo;follow us home&rsquo; with blame and different kinds of suggestions,&rdquo; said Nymark.</p>



<p>One of the ways the Themes Team has been dealing with this is by using the relatively anonymous &ldquo;@trtmessenger&rdquo; account when suspending themes. This is the route the team took when handling the Astra theme suspension and followup decisions.</p>



<p>The team has dealt with attacks toward individual members over the years on various decisions it has made. In many cases, the representative who delivered a particular decision, regardless of their personal role in it, bared the brunt of the negative feedback. Far too often, it was a case of shooting the messenger, and the current reps have found a workable solution for this issue.</p>



<p>&ldquo;This is an account that enables messages to be sent without one single person being held accountable for the message,&rdquo; said Patton. &ldquo;It is intended to prevent anyone from getting any negative feedback directly from a decision.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 10 Aug 2020 21:29:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:52:"WPTavern: New WordPress Plugins Disable Unsplash CDN";s:7:"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=102767";s:7:"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:149:"https://wptavern.com/new-wordpress-plugins-disable-unsplash-cdn?utm_source=rss&utm_medium=rss&utm_campaign=new-wordpress-plugins-disable-unsplash-cdn";s: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:9548:"<p>In light of the recent conversations about the Unsplash plugin&rsquo;s CDN, several extensions have popped up this week for disabling it. By default, the plugin serves images from the CDN but saves copies to the WordPress media library in case the plugin is disabled or removed. The plugin does not currently have an option to change this.</p>



<p><a href="https://wordpress.org/plugins/disable-unsplash-cdn/">Disable Unsplash CDN</a> is the first to be published to the WordPress.org directory for changing the plugin&rsquo;s default behavior. There are no options or settings &ndash; activating it turns it on. Xaver Birsak, a prolific WordPress plugin author, created it to help users who may experience slower page speed caused by the Unsplash CDN.</p>



<p>&ldquo;I&rsquo;ve followed the release of the official Unsplash plugin as well the strange one-star rating from Matt Mullenweg which is think is not appropriate,&rdquo; Birsak said. &ldquo;The problem he mentioned was, in addition to the Unsplash license, the fact that images are being served from Unsplash (Imgix) servers. I don&rsquo;t think that this is totally unnecessary from Unsplash as a CDN can serve images much quicker in most cases. For some users this is maybe not the case.&rdquo;</p>



<p>Birsak was referencing Matt Mullenweg&rsquo;s recent <a href="https://wordpress.org/support/topic/i-wouldnt-recommend-using-this/">one-star review</a> of the Unsplash plugin, which drew the ire of many plugin developers whose ability to monetize their products can hinge on getting decent reviews. The review called the plugin &ldquo;sketchy&rdquo; and called into question the practice of making the CDN the default:</p>



<blockquote class="wp-block-quote"><p>It&rsquo;s unclear why they want you to use their CDN and make that the default, it&rsquo;s probably to support their&nbsp;<a href="https://unsplash.com/blog/introducing-unsplash-for-brands/">new advertising business model</a>&nbsp;and get analytics for it. Running a CDN is expensive, and if you&rsquo;re not paying for it then you are the product. I would not be surprised if Unsplash hotlinked images broke at some point in the future.</p><p>If you want a CDN, you should run one for your entire site, not just certain images from a single source &mdash; in fact having multiple CDNs running at the same time could slow down your site because of the additional DNS lookups.</p></blockquote>



<p>Birsak said he checked the plugin and found a simple solution for bypassing the hotlinking, which only requires a few lines of code. </p>



<p>&ldquo;Since it&rsquo;s so easy, and others may find it useful, I released this plugin,&rdquo; Birsak said. &ldquo;Nowadays with GDPR and the invalidation of the Privacy Shield people are more likely to be concerned about sending data to third party services. So disabling the CDN should at least be an option.&rdquo;</p>



<p>WordPress developer <a href="https://tomjn.com/">Tom Nowell</a> also created a quick plugin to disable Unsplash&rsquo;s CDN, which is now <a href="https://gist.github.com/tomjn/a7036d369d6f8082dd1eb256c651696e">available on GitHub</a>.</p>



<p>&ldquo;I don&rsquo;t have qualms with Unsplash themselves but I did miss having the option to choose for myself,&rdquo; Nowell said regarding the plugin&rsquo;s CDN default. &ldquo;Rather than argue to add it, I spent a little time and built the plugin, it&rsquo;s only small so didn&rsquo;t take much time. As for the CDN, it&rsquo;s nice to save bandwidth, though for local development it&rsquo;s always faster to switch it off.&rdquo;</p>



<h2>Unsplash Plugin Will Not Add an Option to Disable the CDN &ndash; Its API Guidelines Require Apps to Use It</h2>



<p>The plugins that disable Unsplash&rsquo;s CDN could immediately become obsolete if Unsplash decided to build in an option into the official plugin to do the same. The company has confirmed the team has no current plans to so. </p>



<p>&ldquo;The CDN is a feature that dynamically serves the right size and format of image, and includes performance optimizations not available via additional plugins like WordPress.com&rsquo;s Jetpack or most CDNs,&rdquo; Unsplash co-founder Luke Chesser said. &ldquo;We do this to improve the performance of the image loading and allow Unsplash contributors to count the number of times their images have been seen.&rdquo;</p>



<p>In addition to sharing this data with contributing photographers, Unsplash advertisers also need this data to continue getting value from the new <a href="https://unsplash.com/blog/introducing-unsplash-for-brands/">Unsplash for Brands</a> business model. </p>



<p>The total monthly cost in 2019 for the company&rsquo;s image hosting with <a rel="noreferrer noopener" href="https://imgix.com/" target="_blank">Imgix</a> was <a href="https://medium.com/unsplash/what-does-unsplash-cost-in-2019-f499620a14d0">$42,408</a>, which means Unsplash spends north of $500k per year to serve optimized images via its CDN. Chesser said the cost of the CDN is &ldquo;very low relative to the number of requests and traffic it can serve,&rdquo; given how optimized and performant the image serving infrastructure is. Last year Unsplash sent petabytes of data through Imgix&rsquo;s CDN for 250 million variations of the library&rsquo;s source images.</p>



<p>&ldquo;We treat brands as contributors as they also share images on Unsplash,&rdquo; Chesser said. &ldquo;We report downloads and views back to them. So yes, the view and download counts do matter to our business from a monetary perspective, but to be clear, if you take away brands, we would still have this requirement as it&rsquo;s central to growing the library and encouraging more contributors.&rdquo;</p>



<p>Providing stats to brands undoubtedly helps pay the bills and keeps the lights on, so it is no wonder the requirement to use the CDN will remain in the WordPress plugin. In fact, this requirement was built into <a href="https://help.unsplash.com/en/articles/2511245-unsplash-api-guidelines">Unsplash&rsquo;s API guidelines</a> in 2018 and applies to all applications accessing the collection:</p>



<p>&ldquo;<em>All API uses must use the hotlinked image URLs returned by the API under the <code>photo.urls</code> &nbsp;properties. This applies to all uses of the image and not just search results. &ldquo;</em></p>



<p>In 2019, Unsplash received more traffic from its API partners than from the company&rsquo;s own website and official apps. Any successful monetization strategy that hinges on advertising will need to deliver those stats and requiring applications use the CDN in order to use the API is one way to do that. </p>



<p>Matt Mullenweg recently <a href="https://twitter.com/photomatt/status/1290739168537001984">asked</a> what these API guidelines mean for existing WordPress plugins, like <a href="https://wordpress.org/plugins/instant-images/">Instant Images</a>, that serve Unsplash images without using the CDN. The plugin has more than 50,000 active installations. </p>



<p>&ldquo;When we released the updated guidelines we applied them proactively to new apps and worked with developers on a case by case basis over a one year period to consider hotlinking and downloads for legacy apps,&rdquo; Chesser said. &ldquo;Instant Images was built before we made the update to the guidelines and so we exempted them long ago, along with&nbsp;a number of other legacy apps.&rdquo;</p>



<p>Instant Images plugin developer Darren Cooney said he will not be adding an option to his plugin for turning on the CDN and declined to comment further on his reasons. </p>



<p>&ldquo;I will say that I think the CDN should be opt-in and it should be more clear what happens on the Unsplash side when the CDN is in use,&rdquo; Cooney said. &ldquo;What is tracked, why it&rsquo;s tracked and what benefit do added views provide the contributors.&rdquo;</p>



<p> When asked whether Unsplash plans to update the plugin to deny API access to sites that have added a plugin to disable the CDN, Chesser said no. WordPress plugins weaponizing themselves against each other is not unheard of, although it is unusual and frowned upon.</p>



<p>&ldquo;We don&rsquo;t do things like that,&rdquo; Chesser said. &ldquo;I think anyone who knows our team and our community will know that we always try to take reasonable actions as we&rsquo;re representing a lot of contributors and a large community. If a user wants to install a plugin to deactivate the CDN but still access the library, they can do that by all means, but we don&rsquo;t want to build, promote, and support that functionality ourselves because it works against our community,&nbsp;our business, and our mission.&rdquo;</p>



<p>The bottom line is Unsplash is a business, and a business needs to make money. Certainly a company doesn&rsquo;t commission a WordPress plugin from a team of the caliber of <a href="https://xwp.co/">XWP</a> without hoping for a return on that kind of investment. The plugin&rsquo;s setup process makes it effortless for users to connect to the Unsplash API, but there isn&rsquo;t any transparency during this process regarding what data users are agreeing to send Unsplash. The plugin needs to be more forthcoming about the data the CDN collects on views and downloads. This would go a long way towards establishing more credibility with skeptics. Those who are wary of the requirement to use the CDN can use a plugin to disable it or install an alternative like Instant Images. </p>



<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 07 Aug 2020 21:45:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s: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: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:111:"WPTavern: Gutenberg 8.7 Adds Minor Changes, Updates Block Pattern Designs, and Continues Full-Site Editing Work";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=102950";s:7:"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:263:"https://wptavern.com/gutenberg-8-7-adds-minor-changes-updates-block-pattern-designs-and-continues-full-site-editing-work?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-8-7-adds-minor-changes-updates-block-pattern-designs-and-continues-full-site-editing-work";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5390:"<p class="has-drop-cap">On Wednesday, the Gutenberg team pushed what was primarily <a href="https://make.wordpress.org/core/2020/08/05/whats-new-in-gutenberg-august-5/">minor enhancements and bug fixes</a> to the WordPress platform&rsquo;s primary project. Everyone is mostly gearing up for the WordPress 5.5 release, so we are not seeing any major features dropping at the moment. However, steady work continues on improving the Gutenberg plugin.</p>



<p>Gutenberg 8.7 contains over 30 bug fixes, in which nearly a third were accessibility-related changes. Around half of the new enhancements focused on updating block patterns.</p>



<p>Users can look forward to several minor enhancements that should improve the editor, such as the Buttons block getting a proper <a href="https://github.com/WordPress/gutenberg/pull/24249">preview in the inserter</a>. The monitoring solution behind auto-saving should also <a href="https://github.com/WordPress/gutenberg/pull/23962">work more consistently</a> with this update.</p>



<p>The biggest user-facing enhancement is the change in <a href="https://github.com/WordPress/gutenberg/pull/24263">dealing with invalid blocks</a>. The latest version of the plugin makes the <em>attempt block recovery</em> option the default. This change hides the <em>resolve</em>, <em>convert to classic</em>, and <em>convert to HTML</em> options under the sub-menu (ellipsis button). This is a nice touch and makes the most sense. Attempting to recover a block should generally be the first step when correcting invalid block output.</p>



<h2>Block Pattern Updates</h2>



<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>Updated block pattern designs.



<p class="has-drop-cap">I can now proceed to eat my earlier words of <a href="https://wptavern.com/decision-time-what-block-patterns-should-ship-with-wordpress-5-5">frustration with block patterns</a>. Or, perhaps I can praise myself in some small way for pushing the Gutenberg team to up their game. I was unhappy with the abysmal designs that were originally going to ship with WordPress 5.5. The team has taken what was looking to be one of the most disappointing first outings for a feature and turned it into something the project can be proud of.</p>



<p>It did not take much. A photo here. A touch of pizazz there. The Don Quixote images and text bring a cohesive theme to the patterns, breathing a touch of life in an otherwise desolate and barren feature.</p>



<p>The &ldquo;large header with a heading&rdquo; pattern <a href="https://github.com/WordPress/gutenberg/pull/24141">dropped the blinding background</a> gradient and replaced it with an image. The &ldquo;quote&rdquo; pattern <a href="https://github.com/WordPress/gutenberg/pull/24140">now has a face</a> instead of an impersonal icon. Even the &ldquo;two images side by side&rdquo; pattern <a href="https://github.com/WordPress/gutenberg/pull/24139">fits in thematically</a>.</p>



<p>If anything, I am not a fan of the long pattern names. &ldquo;Large header with a heading and a button&rdquo; and &ldquo;three columns of text with buttons&rdquo; do not exactly roll off the tongue. Nor do they make it easy to write about them. I do not wish the pain of typing them out on any support volunteers.</p>



<p>At least we are working with a somewhat decent set of patterns going forward, and that is enough to be thankful for at this point. I will now await the first theme author to truly impress me with custom patterns.</p>



<h2>Experimental Features Update</h2>



<img />Site editor beta.



<p class="has-drop-cap">Much of the work for this release centered on the plugin&rsquo;s experimental features. The bulk of it went toward post-related blocks. At this point, these features are so experimental that even experienced developers outside of the inner Gutenberg circle have trouble following the progress. It is nice to see the continual movement in this area. However, from a user viewpoint, it is not even ready for a quick look. Enable at your own risk. Wait until the product is a bit more polished.</p>



<p>I typically enable Gutenberg&rsquo;s experimental features once a month or so. I want to keep up with the progress and not feel out of the loop. Such was the case over the past couple of days as I tinkered a bit more with the full-site editing and demo templates features. I am unsure what I was hoping for. Mostly, I wanted some indication of a bright future &mdash; one that I fully expect to be realized at some point. I wanted to be wowed.</p>



<p>I understand why the <em>wow</em> factor is not there. The feature is far from ready. More than that, I know that, as a developer, you have a vision of the finished product in your head, and as the UI is in flux, others cannot see that vision. It is a step-by-step process that you simply have to continue working through.</p>



<p>I am still of the belief that full-site editing will not be close to a viable feature until 2021. Even with all hands on deck, four months is too small of a window to make anything remotely competitive to existing solutions out there. When full-site editing does land in core WordPress, it needs to do so with a bang, not a whimper.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 07 Aug 2020 21:33:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"
	
	
	
	
	
	
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:88:"WPTavern: Is WP Notify the Silver Bullet WordPress Needs to End Admin Notification Spam?";s:7:"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=102877";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:219:"https://wptavern.com/is-wp-notify-the-silver-bullet-wordpress-needs-to-end-admin-notification-spam?utm_source=rss&utm_medium=rss&utm_campaign=is-wp-notify-the-silver-bullet-wordpress-needs-to-end-admin-notification-spam";s: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:5192:"<p>A short while ago, Justin Tadlock posted an article titled <a rel="noreferrer noopener" href="https://wptavern.com/are-plugin-authors-to-blame-for-the-poor-admin-notices-experience" target="_blank">Are Plugin Authors to Blame for the Poor Admin Notices Experience?</a>. If you haven&rsquo;t already, I recommend reading his article. It describes in detail one question I&rsquo;ve been pondering since I originally posted the <a href="https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/">WP Notify feature project proposal</a> almost a year ago now: Will a new notification system for WordPress solve the notification spam, or just move it elsewhere?</p>



<p>The answer might not be as simple as we think.</p>



<p>I have been building, maintaining, and supporting a number of free, paid, and client plugins for the past five years. During that time I have also been an active contributor &mdash; as much as I possibly can outside of work and my personal life &mdash; to the WordPress open source project. Now that&rsquo;s definitely a drop in the ocean compared to some folks, but whenever I see the mess that can occur when multiple plugins or themes register admin_notices on EVERY SINGLE ADMIN PAGE, it strengthens my resolve in the idea that WordPress needs a centrally managed notification system.&nbsp;</p>



<p>If you read Justin&rsquo;s article, or you are a plugin or theme developer yourself, you know that the notifications system (aka admin notices, a reference to the WordPress <a rel="noreferrer noopener" href="https://developer.wordpress.org/reference/hooks/admin_notices/" target="_blank">hook that prints these notices</a>) in WordPress is limited at best. We need to be honest with ourselves, however, admin notices was not designed to function as a notification system. Admin notices should really only be used to display useful information to the user about state changes in the system. Messages like when a post has been updated or deleted, or a database upgrade is required. Short, useful, and more importantly, relevant.</p>



<p>As developers, we usually look for the root cause of a problem. And in the case of admin notices, the root cause is not the current notification system, or the fact that plugin developers use it for things other than, well, admin notices. The root cause is the fact that there has never existed a mechanism for notifications other than admin notices to be displayed to the user. This means that whenever a plugin developer has needed, or in fact wanted, to communicate with their users, via &ldquo;in app messages,&rdquo; admin notices has been the only way they can do so.</p>



<p>Want to let your users know about a new upgrade? Admin notice. Want to ask them to leave a review? Admin notice. Your premium license is about to expire! Admin notice. Hey, we&rsquo;ve got a new sale on our premium products! Admin notice. It all soon adds up to an almighty mess.</p>



<p>And that&rsquo;s the problem with a project like WP Notify. We&rsquo;ve had admin notices, in its current iteration at least, since 2011. That means we have been using it for all our user facing messages now for nine years at least &ndash; nine years of plugin and theme developers using admin notices to send messages to users.&nbsp;</p>



<p>If you have children, imagine telling your nine year old that the way they have been walking is wrong, and they now need to learn a completely new way of doing it. Good Luck!</p>



<p>So, as much as it pains me to admit it, WP Notify is not the silver bullet that will magically fix the problem at its core. As Matt Mullenweg pointed out in the comments on Justin&rsquo;s article, &ldquo;I don&rsquo;t think a notification center is the solution to this problem. It may be useful for other reasons, but not that one.&rdquo;</p>



<p>However, not having a specific solution for notifications other than those that are necessary, means that developers will keep on doing things the way they have always been. Enforcing new guidelines around the current functionality nine years later is going to be hard, especially since enforcing these guidelines will have to be done by a small group of volunteers, namely the theme and plugin review teams.&nbsp;</p>



<p>By building WP Notify, we create a new and hopefully better way for plugin and theme developers to connect and communicate with their users. At the same time, we provide a tool by which we can more easily enforce any new guidelines. A guideline could be created for example, that unless your message is strictly within the realms of informing the user about state changes in the system, it needs to be displayed in the notifications center, and not as an admin notice.</p>



<p>So no, I don&rsquo;t believe WP Notify will be a silver bullet solution. We&rsquo;re not going to build it, ship it, and suddenly all the notification spam goes away the next day. That kind of change takes time.</p>



<p>But I do believe it&rsquo;s a step in the right direction.</p>



<p>If you agree with me, why not <a href="https://make.wordpress.org/core/tag/feature-notifications/">join our merry band and help us build it</a>.&nbsp;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 07 Aug 2020 14:06:20 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Jonathan Bossenger";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:70:"WPTavern: Automattic Relaunches P2, Self-Hosted Version on the Roadmap";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=102891";s:7:"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:183:"https://wptavern.com/automattic-relaunches-p2-self-hosted-version-on-the-roadmap?utm_source=rss&utm_medium=rss&utm_campaign=automattic-relaunches-p2-self-hosted-version-on-the-roadmap";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4890:"<p>Automattic&rsquo;s relaunch of P2 is <a href="https://wordpress.com/p2/">now in Beta</a>. This is the long-awaited update to the company&rsquo;s internal collaboration software that is also used on WordPress.org and other self-hosted sites via a theme. For years, Automattic, which now counts more than 1,200 employees in 77 countries, has had P2 at the core of its written communication tools. It is used as a complement to Slack and video conferencing, providing a public collaboration space for conversations which might otherwise be hidden away in emails. </p>



<p>The older version of P2 functioned as a dependable workhorse with few changes over the years, but the beta introduces some marked improvements that make it more versatile than before. It is now seamlessly integrated with the block editor and includes a streamlined invitation system for onboarding new team members.</p>



<img />



<p>P2 has a fresh design that has come a long way since its roots as an <a href="https://ma.tt/2009/05/how-p2-changed-automattic/">evolution of the Prologue microblogging theme.</a> Many things about WordPress have changed since P2&rsquo;s first launch 11 years ago but threaded conversations have endured as a useful collaboration format. Mobile support is one of the things that has improved significantly. Users can get notifications via the web, email, and the WordPress mobile apps.</p>



<img />



<p>&ldquo;It works on the WordPress apps perfectly but it&rsquo;s handled as a normal WordPress site, without any P2 specific functionality,&rdquo; Automattic&rsquo;s P2 launch lead Jon Burke said. &ldquo;P2 specific functionality and improvements are on the mobile app product roadmap. The browser version on the other hand has all the particularities that P2 has.&rdquo;</p>



<p>The beta version of P2 is free and each instance comes with 3GB of storage space for images and files. Users can create as many as they like. The product is built on top of WordPress.com&rsquo;s infrastructure but functions as a scaled back version of a blog &ndash; essentially a WordPress for teams. </p>



<p>Pricing for the commercial upgrade has not yet been determined, according to Burke, but the roadmap includes a hefty list of features.</p>



<p>&ldquo;We&rsquo;ll have integrations with third party services, project management features, more storage space, custom URLs, more customization options, etc,&rdquo; Burke said. &ldquo;We plan to introduce multi-site functionality, too, so an organization can create multiple P2s while sharing the same user base, have cross-posting, a common glossary, and other advanced features.&rdquo;</p>



<p>With the diverse myriad of blocks pouring into the WordPress ecosystem, every P2 has the opportunity to be unique, depending on which features it introduces through the editor. Burke said Automattic plans to allow admins to extend their P2 instances with plugins in the enterprise version.</p>



<h2>P2 Set to Roll Out on WordPress.com, Self-Hosted Version Coming &ldquo;Eventually&rdquo; </h2>



<p>P2 is just now entering beta but many fans are already eagerly awaiting a self-hosted version. Burke said it is coming &ldquo;eventually,&rdquo; but the team hasn&rsquo;t yet worked out how it will be structured. The project is not currently available on GitHub.</p>



<p>&ldquo;With this launch version behind us the P2 team will turn to this but don&rsquo;t yet have a time-line,&rdquo; Burke said. &ldquo;The team will need to now define how the backend admin will look.&rdquo; The updated P2 is also coming to power conversations on WordPress.org further down the road.</p>



<p>&ldquo;We don&rsquo;t yet have a target date but it is on the product roadmap,&rdquo; he said. &ldquo;This P2 version has been more than a theme or plugin update &ndash; it&rsquo;s really a product concept- so we can&rsquo;t simply update the WordPress.org P2 theme; it requires additional progress.&rdquo;</p>



<p>P2 seems like it would be a good fit for Automattic&rsquo;s <a href="https://happy.tools/">Happy Tools</a> suite of products for distributed teams. A version of P2 with more features may roll out under this brand once the beta concludes.</p>



<p>&ldquo;Given the sudden global shift to remote work we really wanted to get out a stable product as soon as we could,&rdquo; Burke said. &ldquo;That really made WordPress.com the most expedient pathway to get P2 into peoples&rsquo; hands.</p>



<p>&ldquo;Now that we have launched this version, we will make decisions around where the next releases will live. P2 has been envisioned as being part of the Happy Tools suite. But we are going to learn from the early users on WordPress.com and prioritize the next steps. We know that some users will need a premium version on WordPress.com in order to secure a custom domain and other features so we will update that shortly.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 06 Aug 2020 22:10:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"*data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Sat, 05 Sep 2020 19:14:30 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Sat, 05 Sep 2020 19:00:07 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 1";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20130911040210";}