(94297,'_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:61:\"\n	\n	\n	\n	\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a: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:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WPTavern: What Should an Author Bio Block Look Like?\";s:7:\"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:29:\"https://wptavern.com/?p=96070\";s:7:\"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:62:\"https://wptavern.com/what-should-an-author-bio-block-look-like\";s: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:6173:\"<img />Two author bio block mock-ups compared.\n\n\n\n<p>Joshua Wold, co-representative for the WordPress design team, <a href=\"https://make.wordpress.org/design/2019/12/23/author-card-block-exploration/\">shared an early exploration</a> of an author card block.  Community members explored several ideas at the design table during the contributor day at WordCamp US 2019.  In the post, Wold followed up on the original sketches from that melding of design minds.</p>\n\n\n\n<p>The original idea for the author block was a <a href=\"https://github.com/WordPress/gutenberg/issues/1844\">GitHub ticket</a> created in July 2017, but it was far ahead of its time.  The Gutenberg project needed to focus on the basics and more common blocks for post content at that point.  Now is the time to shift gears and begin work on these more complex blocks that will likely be a large part of the full-site editing phase of the project.</p>\n\n\n\n<p>Currently, there are several proposed components to the author block:</p>\n\n\n\n<ul><li>Image/Avatar</li><li>Name</li><li>Description/Biography</li><li>Website Link</li><li>Social Network Links</li><li>Recommended Posts</li></ul>\n\n\n\n<p>I am on the fence about a recommended posts option as part of the block.  If they were recommended posts written by that author, it could be an interesting concept to explore.  However, version 1 of the block should focus on the most common elements, which the other components in the list cover.</p>\n\n\n\n<p>Wold asked four key questions about the future of the block.  The following are my responses to each.</p>\n\n\n\n<h2>What Is the Value of the Block and How Will It Be Used?</h2>\n\n\n\n<p>Coming from the theme world, what surprises me is that WordPress has never standardized on this feature at this point.  Author bio sections are commonplace in theme development.  Core should have standardized this feature years ago.  We have a standard search form, comment list, featured image, and more.  Many of the features that WordPress has standardized over the years were born out of theme designers carving the path forward, and author bios are no different.</p>\n\n\n\n<p>It has long made sense for an author bio template tag to exist.  However, we are living in a block world.  The concept has merely shifted.</p>\n\n\n\n<p>We do not need an author bio block today.  We will need it tomorrow.  As we shift closer and closer to full-site editing, we need to be building, iterating, and testing these types of blocks in preparation for the point of no return.  This block, along with similar blocks, should drop in core at the same time the switch is flipped on full-site editing.</p>\n\n\n\n<p>The primary use case will be for end-users to edit their theme&rsquo;s block templates to stick the author bio at the end of their single post views.  However, such a block need not be limited to that scenario.  Users could create a &ldquo;team&rdquo; or &ldquo;authors&rdquo; page on their site.  Some may want to drop these into columns or create some sort of gallery of author bios.</p>\n\n\n\n<p>I could see taking this even further and naming it a &ldquo;user bio&rdquo; block.  Use cases do not have to be centered around the concept of an author.</p>\n\n\n\n<h2>Where Should the Author Data Come From?</h2>\n\n\n\n<p>The primary, or at least initial, source of data should come from user data and metadata stored in the database.  It does not make sense to duplicate efforts by retyping content within the block if it already exists.</p>\n\n\n\n<p>One big question will be around social icons.  If these are a part of the block, there is no current source to pull the URLs from.  If automatically generating the data, WordPress will need to add social media contact methods to the user profile screen in the admin.  That can be a slippery slope when deciding which social networks to include.  However, core WordPress could stick to three or four major networks and provide a filter hook for plugin authors to utilize along with a standard for how additional fields are handled.</p>\n\n\n\n<p>There is also the possibility that this block could simply be a pre-defined pattern of existing, smaller blocks that pulled in data like a user biography, user social icons, and user avatar.  Then, the site owner could move other blocks in and out as they saw fit.</p>\n\n\n\n<h2>What Block Design Options Should Be Available?</h2>\n\n\n\n<p>The obvious design options are the standard text color, background color, and font size options.  <a href=\"https://github.com/WordPress/gutenberg/issues/16848\">Border design options</a> would be a bonus, but that goes beyond the scope of this specific block.</p>\n\n\n\n<p>The standard alignment options would be welcome, particularly center, wide, and full.  An alignment option for the avatar image to shift it left or right could also be useful.  It could work similarly to the existing Media &amp; Text core block.</p>\n\n\n\n<p>I would not go overboard with design options.  Let theme authors create custom block styles for users to choose from.  That is the theme author&rsquo;s job.</p>\n\n\n\n<h2>What Additional Features Should the Block Handle?</h2>\n\n\n\n<p>Outside of an avatar and biography, a social icon list is the most necessary feature.  It is almost ubiquitous with author bio boxes.</p>\n\n\n\n<p>What I would like to see is an author/user &ldquo;gallery&rdquo; block that builds upon this initial idea.  At the moment, I am already imagining the painful user experience of creating a team page and putting individual user bio blocks into columns.  Then, I am further imagining having to update that page and potentially move columns around.  As an end-user, there are times when I want to micro-manage certain aspects of my site.  This would not be one of them.  Just give me a simple block to list user bios in some sort of columnized format.</p>\n\n\n\n<p>Such a block could provide an avenue for many types of options.  Maybe an option to list authors of a certain post type.  Perhaps an option to list users by role.  Or, let me list the top users by post count.</p>\n\n\n\n<p>This idea may be pushing over into plugin territory.  However, in terms of what I would want to do with my sites, this would be high on the list.</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, 27 Dec 2019 20:00: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:1;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Joseph: 2020 Style\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"https://blog.josephscott.org/?p=17917\";s:7:\"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:51:\"https://blog.josephscott.org/2019/12/27/2020-style/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:951:\"<p>With the year 2020 fast approaching, I thought it would be a good time to change up the style on <a href=\"https://blog.josephscott.org/\">blog.josephscott.org</a>.  To that end, I&#8217;m trying out the <a href=\"https://wordpress.org/themes/twentytwenty/\">Twenty Twenty WordPress theme</a>.</p>\n<a href=\"https://blog.josephscott.org/wp-content/uploads/2019/12/screenshot-blog-josephscott-org.png\"><img src=\"https://blog.josephscott.org/wp-content/uploads/2019/12/screenshot-blog-josephscott-org-450x1024.png\" alt=\"\" width=\"450\" height=\"1024\" class=\"size-large wp-image-17932\" /></a>blog.josephscott.org\n<p>One of the things I&#8217;m really happy to see in the Twenty Twenty theme is the use of <a href=\"https://github.com/WordPress/twentytwenty/pull/163\">vanilla JavaScript, without jQuery</a>.  I&#8217;m hopeful that more WordPress themes will follow that pattern ( jQuery has been great, but if you don&#8217;t need it, don&#8217;t use 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:\"Fri, 27 Dec 2019 18:02: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:11:\"josephscott\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"WPTavern: Rank Math SEO Plugin Adds WordPress Block Editor Support\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=95921\";s:7:\"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:77:\"https://wptavern.com/rank-math-seo-plugin-adds-wordpress-block-editor-support\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5310:\"<p>The team behind the <a href=\"https://wordpress.org/plugins/seo-by-rank-math/\">Rank Math SEO plugin</a> released an update that includes full support for the block editor on December 18.  The update includes around two dozen features, improvements, and fixes.  The biggest feature update was the inclusion of a new plugin sidebar for the block editor.</p>\n\n\n\n<p>Some of the new features include a filter for unlimited focus keywords, an email notification each time the plugin is automatically updated, and a warning when using the review Schema type.  It also improved compatibility with the Elementor plugin&rsquo;s sitemap module and added Advanced Custom Fields integration to the sidebar.  A full list of features is available in the plugin&rsquo;s <a href=\"https://rankmath.com/changelog/\">public change log</a>.</p>\n\n\n\n<p>The team has a <a href=\"https://s.rankmath.com/demo\">public demo available</a> for end-users to test the plugin without having to install it on their sites.</p>\n\n\n\n<p>Bhanu Ahluwalia, co-founder and CMO at Rank Math, said that everyone on the team had been experimenting with the Gutenberg plugin since the first beta was released.  &ldquo;We had some experience with Gutenberg, but working on Rank Math has taught us so many things and helped us on so many levels,&rdquo; he said.</p>\n\n\n\n<p>It was not always a smooth journey.  Ahluwalia said the team wanted to keep the plugin lightweight and not sacrifice speed with new technologies.  &ldquo;We had to learn React, Webpack, ES6, etc.,&rdquo; he said.  &ldquo;In essence, we had to re-learn patterns, practices, and pitfalls of Gutenberg, and we had to do it all with little-to-no documentation available. We had to dive deep into the code and get ourselves familiar with every line of code to ensure nothing interfered with the existing functions of our plugin.&rdquo;</p>\n\n\n\n<h2>Testing the Block Editor Sidebar</h2>\n\n\n\n<img />Rank Math sidebar as seen in the block editor.\n\n\n\n<p>Immediately upon activating the update, I noted the Rank Math button at the top right of the editor.  Admittedly, I was not happy with the space the button took up or its difference in design when compared to other plugin sidebar buttons.  Instead of a simple icon, the button includes both an icon and an SEO score.  As more and more plugins and themes begin adding sidebars of their own, this space could become cluttered quickly.  I would like to see this scaled back to simply be an icon and not take up precious screen real estate.</p>\n\n\n\n<p>The plugin manages to pack a ton of options and information into a tight spot.  Once viewing the plugin sidebar, it presents four sub-tabs (General, Advanced, Schema, and Social), each with custom panels or sections.  While I am not generally a fan of complex SEO plugins and prefer solutions such as <a href=\"https://wptavern.com/slim-seo-keeps-options-simple-and-handles-the-legwork-of-seo\">Slim SEO</a>, the plugin handles the interface gracefully.</p>\n\n\n\n<p>In comparison to the old meta boxes, the interface is a huge step up.  The meta box system used in previous versions of the plugin or with the current Classic editor is cumbersome at best.  The team had to get more creative to pull off a solution for the sidebar, which forced them to tighten up the interface.</p>\n\n\n\n<p>Not all users were happy with the <a href=\"https://wordpress.org/support/topic/sidebar-really/\">narrow space</a> provided by the new sidebar.  The Rank Math team was ahead of the game and included a <a href=\"https://rankmath.com/kb/filters-hooks-api-developer/#disable-gutenberg-sidebar\">filter hook to disable</a> this feature.  Disabling will return the old-style meta box at the bottom of the post-editing area.</p>\n\n\n\n<p>&ldquo;Supporting both the Classic Editor and Gutenberg at once with a single plugin is hectic to say the least,&rdquo; said Ahluwalia. &ldquo;We would rather put our energy into a single editing experience, but seeing how WordPress is evolving after Gutenberg, we have to double our efforts to offer a consistent user experience.&rdquo;</p>\n\n\n\n<p>At the moment, the team plans to continue supporting the classic editor until at least 2022.  &ldquo;Depending on the user feedback and the acceptance of the Classic editor, we can continue to support it even further,&rdquo; said Ahluwalia.</p>\n\n\n\n<p>The Rank Math also team shared a video of block editor support on Twitter:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">&#127881; Here\'s a sneak preview of Rank Math\'s upcoming major update which adds <a href=\"https://twitter.com/hashtag/Gutenberg?src=hash&ref_src=twsrc%5Etfw\">#Gutenberg</a> support &ndash; now it\'s even easier for people using the latest version of <a href=\"https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw\">#WordPress</a> to use Rank Math <a href=\"https://twitter.com/hashtag/SEO?src=hash&ref_src=twsrc%5Etfw\">#SEO</a> &#128285;<br /><br />Want to take the Beta for a spin now? Join us on Facebook<a href=\"https://t.co/Ykfhj2d5Z1\">https://t.co/Ykfhj2d5Z1</a> <a href=\"https://t.co/E1ItpD0b4B\">pic.twitter.com/E1ItpD0b4B</a></p>&mdash; Rank Math SEO (@rankmathseo) <a href=\"https://twitter.com/rankmathseo/status/1198226289129189376?ref_src=twsrc%5Etfw\">November 23, 2019</a></blockquote>\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 23 Dec 2019 19:53:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:3;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"BuddyPress: BuddyPress 5.1.1 Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=309527\";s:7:\"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:48:\"https://buddypress.org/2019/12/buddypress-5-1-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1122:\"<p><a href=\"https://downloads.wordpress.org/plugin/buddypress.5.1.1.zip\">BuddyPress 5.1.1</a> is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.</p>\n\n\n\n<p>The 5.1.1 release addresses one security issue:</p>\n\n\n\n<ul><li>A denied of service was fixed that could allow a logged in user to remove another user&#8217;s avatar and also any empty folder. Discovered by <a href=\"https://hackerone.com/nomnom\">nomnom</a>.</li></ul>\n\n\n\n<p>Thi vulnerability was reported privately to the BuddyPress team, in accordance with&nbsp;<a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">WordPress’s security policies</a>. Our thanks to the reporter for practicing coordinated disclosure.</p>\n\n\n\n<p>For complete details, visit the&nbsp;<a href=\"https://codex.buddypress.org/releases/version-5-1-1/\">5.1.1 changelog</a>.</p>\n\n\n\n<p>Update to BuddyPress 5.1.1 today in your WordPress Dashboard, or by&nbsp;<a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</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:\"Mon, 23 Dec 2019 09:45:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"WPTavern: Version 1 Prototype of the WordPress Admin Block Directory Announced\";s:7:\"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:29:\"https://wptavern.com/?p=95946\";s:7:\"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:89:\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\";s: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:7139:\"<p>Mel Choyce-Dwan shared the first version of the <a href=\"https://make.wordpress.org/design/2019/12/19/block-directory-in-wp-admin-v1/\">WordPress admin block directory prototype</a> the design team has been working on.  The goal is to bring the block directory to the admin in WordPress 5.5, which is currently <a href=\"https://wptavern.com/progress-on-wordpress-2019-projects-sets-2020-roadmap\">set for August 2020 on the roadmap</a>.  The post also outlines reusable components that can be used in other areas of the admin in the long term.</p>\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-wp-admin?node-id=1460%3A277&viewport=366%2C373%2C0.25&scaling=min-zoom\">Figma prototype</a> is available for those who want to give it a test run.  It is important to remember that this is an early version and many things can change by the time the block directory lands in WordPress.</p>\n\n\n\n<p>The prototype was built after feedback from the <a href=\"https://make.wordpress.org/design/2019/07/11/block-directory-in-wp-admin-concepts/\">first round of concepts shared</a> in July on the Make Design blog.</p>\n\n\n\n<p>For this admin project to be successful, WordPress plugin developers will need to start submitting blocks to the <a href=\"https://wordpress.org/plugins/browse/block/\">block directory</a> on WordPress.org.  At the moment, there are only 10 blocks listed.  Getting in early will give block authors an edge on the competition.  The block directory has a few <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">additional guidelines</a> beyond normal plugins that authors should review.</p>\n\n\n\n<h2>About Blocks Screen</h2>\n\n\n\n<img />About Blocks admin screen.\n\n\n\n<p>The About Blocks screen is the primary blocks admin screen.  It appears to be an informational page with resources for users to learn more about using blocks on their sites.  It also has links to development resources for designing and building blocks.  </p>\n\n\n\n<p>Making this information directly available, especially to users, would be a smart decision if it makes it into the final design.  As we move toward an entirely new way to build websites with WordPress, it is important to provide learning tools to users.  This seemed to be one of the missing components when the block editor first launched in core.  If done right, it could ease the burden on new users and old users who are transitioning to the new editor.</p>\n\n\n\n<p>The above screenshot also shows the new admin screen header proposal.  The page title is followed by a short description of what the screen is about.  Followed the intro are action links on the left and meta-type links on the right.  I am a fan of the generous use of whitespace and extra information.</p>\n\n\n\n<h2>Add Blocks Screen</h2>\n\n\n\n<img />Add Blocks screen.\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A2958&viewport=366%2C373%2C0.25&scaling=min-zoom\">add blocks screen</a> is similar to the current new plugin screen in the WordPress admin.  The primary &ldquo;Featured&rdquo; tab (the tab opened when first visiting the screen) is broken down into various sections, such as &ldquo;Blocks We Love&rdquo; and &ldquo;Popular Tags.&rdquo;</p>\n\n\n\n<p>One of the more interesting sections of this page is the &ldquo;Top Authors&rdquo; list.  This concept would be a great way to give recognition to block authors who are building useful blocks for the community.</p>\n\n\n\n<p>There is also a &ldquo;Recent Blocks&rdquo; section near the bottom of the page.  I would rather see a top tab for that.  It feels a bit buried in the current design.  New plugin and theme authors already struggle to break into popular lists.  Recently-added blocks should be higher up the page or have a dedicated tab/page to showcase them a bit more.</p>\n\n\n\n<h2>Installed Blocks Screen</h2>\n\n\n\n<img />Installed Blocks screen.\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A2958&viewport=366%2C373%2C0.25&scaling=min-zoom\">block installation screen</a> is similar to the existing installed plugins screen in core and lists all of the blocks that are installed.  There are also active and inactive tabs.  Improvements here are primarily around list table design.  On the whole, they are minor adjustments, but the look of the tables is much nicer.  <em>Can we have this in core, across the board, now?</em></p>\n\n\n\n<p>A new element is the &ldquo;Instances&rdquo; column, which lists the number of times a block has been used on the site.  By clicking the number, you are taken to a new screen that lists the posts the block has been used in.  It also displays the instances for each post.  This would be a useful feature for deciding whether to deactivate or remove a block.</p>\n\n\n\n<p>Side note to this:  I have worked on numerous projects in the past where I was doing cleanup and attempting to figure out if a plugin, especially those with shortcodes, were in use on the site.  Showing the instances count for blocks is brilliant.</p>\n\n\n\n<h2>Manage Blocks Screen</h2>\n\n\n\n<img />Manage Blocks screen.\n\n\n\n<p>Plugins such as <a href=\"https://wordpress.org/plugins/block-options/\">EditorsKit</a> have had built-in block management for a while.  However, this feature feels like it should be in core WordPress.  There are numerous core blocks that some users will likely never use.  Having the ability to hide them from the block inserter will reduce clutter and make it easier to find the blocks they need.</p>\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A14224&viewport=366%2C373%2C0.25&scaling=min-zoom\">block management screen</a> will allow users to activate or deactivate any specific block on their website.  Like the block installation screen, it also displays the number of instances a block is in use.</p>\n\n\n\n<h2>Reusable Blocks Screen</h2>\n\n\n\n<img />Reusable Blocks screen.\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A15861&viewport=366%2C373%2C0.25&scaling=min-zoom\">reusable blocks screen</a> is already available in WordPress.  It does not currently have an admin menu link, so it is not easily discoverable.  You can view it by going to the <code>yoursite.com/wp-admin/edit.php?post_type=wp_block</code> URL or clicking the &ldquo;Manage All Reusable Blocks&rdquo; link under the &ldquo;Reusable&rdquo; tab in the block inserter.</p>\n\n\n\n<p>This screen allows users to manage blocks that are stored for reuse within multiple posts.  Like the installation and management screens, the prototype displays an instances column for tracking how often the block has been used.</p>\n\n\n\n<p>Users can import and export reusable blocks.  It will be interesting to see if more WordPress users start sharing their block creations with others once this screen has better exposure or if it will be something people simply use to copy blocks from site to site.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 20 Dec 2019 21:09:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:5;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"WPTavern: WordPress 5.3.2 Addresses a Handful of Bugs\";s:7:\"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:29:\"https://wptavern.com/?p=95927\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wptavern.com/wordpress-5-3-2-addresses-a-handful-of-bugs\";s: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:2810:\"<p>On December 18, less than a week since <a href=\"https://wptavern.com/wordpress-5-3-1-includes-security-and-bug-fixes-accessibility-enhancements-and-twenty-twenty-changes\">WordPress 5.3.1 security update</a> shipped to the masses, the core team dropped a <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\">version 5.3.2 maintenance release</a>.  No security issues were named in this update.  Instead, 5.3.2 addresses a couple of high-priority bugs along with a few other issues.</p>\n\n\n\n<p>Users with automatic updates enabled should already be updated to the latest version or will receive an update soon.  Other users should update as soon as they are able, especially if their installation is affected by any of the following issues.</p>\n\n\n\n<p>The first high-priority fix addressed an issue with modified post objects that have an invalid date.  The fix ensures that the <code>get_feed_build_date()</code> function handles this scenario.  The documentation was updated to clarify the function will return <code>false</code> on failure.  This change also led to a comparison-check fix in the test tools when inserting a post with a future or published status.</p>\n\n\n\n<p>The second major bug fixed in 5.3.2 was an edge case where unique file names could clash.  On case-sensitive systems, the <code>wp_unique_filename()</code> function failed to rename some files when the uploaded file matched an existing file with an uppercase file extension.  The fix addresses a fatal error in those cases.</p>\n\n\n\n<p>Developers tackled another issue with the <code>wp_unique_filename()</code> function.  When a destination directory for an uploaded file was unreadable, WordPress was throwing PHP warnings.  The fix includes only running the final filename-collision test for files that are saved to the user&rsquo;s <code>/uploads</code> directory.</p>\n\n\n\n<p>Building off the accessibility work in the previous release, buttons with the <code>.active</code> class are now properly styled in the non-default admin color schemes.  On some screens, particularly the Permalinks admin screen, active buttons had white text on a light gray background, making them unreadable.</p>\n\n\n\n<p>Users who wish to do so, can <a href=\"https://wordpress.org/support/wordpress-version/version-5-3-2/\">view the full release documentation</a> from WordPress.</p>\n\n\n\n<p>With the widespread usage of automatic updates, it would be nice to see more of these quicker releases during the development cycle.  Maybe weekly releases are a bit much.  However, shipping a few extra minor releases between major upgrades would be a good opportunity to knock out some of the 6,500 Trac tickets on <a href=\"https://wptavern.com/progress-on-wordpress-2019-projects-sets-2020-roadmap\">WordPress&rsquo; 2020 roadmap</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 20 Dec 2019 00:19: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: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:6;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"WordPress.org blog: WordPress 5.3.2 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=8275\";s:7:\"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/2019/12/wordpress-5-3-2-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:2828:\"<p>WordPress 5.3.2 is now available!</p>\n\n\n\n<p>This maintenance release features 5 fixes and enhancements.</p>\n\n\n\n<p>WordPress 5.3.2 is a short-cycle maintenance release. The next major release will be&nbsp;version 5.4.</p>\n\n\n\n<p>You can download WordPress 5.3.2 by clicking the button at the top of this page, or visit your<strong>&nbsp;Dashboard → Updates</strong>&nbsp;and click&nbsp;<strong>Update Now</strong>.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h2>Maintenance updates</h2>\n\n\n\n<p>Shortly after&nbsp;<a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">WordPress 5.3.1 was released</a>, a couple of high severity Trac tickets were opened. The Core team scheduled this quick maintenance release to resolve these issues.</p>\n\n\n\n<p>Main issues addressed in 5.3.2:</p>\n\n\n\n<ul><li>Date/Time: Ensure that&nbsp;<code>get_feed_build_date()</code>&nbsp;correctly handles a modified post object with invalid date.</li><li>Uploads: Fix file name collision in&nbsp;<code>wp_unique_filename()</code>&nbsp;when uploading a file with upper case extension on non case-sensitive file systems.</li><li>Media: Fix PHP warnings in&nbsp;<code>wp_unique_filename()</code>&nbsp;when the destination directory is unreadable.</li><li>Administration: Fix the colors in all color schemes for buttons with the&nbsp;<code>.active</code>&nbsp;class.</li><li>Posts, Post Types: In&nbsp;<code>wp_insert_post()</code>, when checking the post date to set&nbsp;<code>future</code>&nbsp;or&nbsp;<code>publish</code>&nbsp;status, use a proper delta comparison.</li></ul>\n\n\n\n<p>For more information,&nbsp;<a href=\"https://core.trac.wordpress.org/query?status=closed&type=!task+(blessed)&resolution=fixed&milestone=5.3.2&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority\">browse the full list of changes on Trac</a>&nbsp;or check out the&nbsp;<a href=\"https://wordpress.org/support/wordpress-version/version-5-3-2/\">version 5.3.2 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks!</h2>\n\n\n\n<p>Thank you to everyone who contributed to WordPress 5.3.2:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey &#8220;Rarst&#8221; Savchenko</a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion hulse</a>, <a href=\"https://profiles.wordpress.org/eden159/\">eden159</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Dwan</a>, <a href=\"https://profiles.wordpress.org/pbiron/\">Paul Biron</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</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, 18 Dec 2019 22:42: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: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:7;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: One-Time vs. Recurring Payments for WordPress Products\";s:7:\"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:29:\"https://wptavern.com/?p=95900\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/one-time-vs-recurring-payments-for-wordpress-products\";s: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:6248:\"<p>Jeff Starr posed the question at Digging into WordPress: <a href=\"https://digwp.com/2019/12/pricing-model-better/\">Which Pricing Model Do You Prefer: One-Time or Recurring?</a></p>\n\n\n\n<p>It is not the first time the question has been asked in the WordPress community and will not be the last.  It is important that we keep coming back to it from time to time.</p>\n\n\n\n<p>In the early days of the commercial WordPress ecosystem, many shops sold products for a one-time fee.  This was particularly true during the 2007-2010 years, which were what many dub the &ldquo;WordPress themes heyday,&rdquo; a period in which theme shops raked in tons of cash due to lack of competition.</p>\n\n\n\n<p>As the market became more saturated, many businesses saw the writing on the wall.  One-time fees for commercial themes or plugins did not make for a sustainable business model.  Of course, some companies pushed forward with that model.  They were either large enough to capitalize on an influx of new customers every year or they continued to push out new products for existing customers to buy.</p>\n\n\n\n<p>Today, most theme and plugin shops utilize a recurring business model.  Many of those shops also set up automatic renewals.  From a business perspective, companies need to keep existing customers while bringing in new buyers to continue maintaining, supporting, and building new features for the current product catalog.  Companies also need growth to build new products.  A recurring fee helps ease the burden of supporting and maintaining the existing products.</p>\n\n\n\n<p>Pippin Williamson <a href=\"https://pippinsplugins.com/automatic-license-renewals-twenty-months-later/\">saw massive revenue growth</a> over 20 months after turning on automatic renewals across his company&rsquo;s various products.  Other companies have seen similar increases with the same model.</p>\n\n\n\n<p>As a former business owner, I <em>dumb-lucked</em> my way into yearly, recurring payments.  When I first launched a theme shop in 2008, that was the model I went with.  I did not know a single thing about running a business except that money exchanged hands.  I was in my early 20s and accustomed to living off minimum wage, digging change from the couch to buy a value meal, and finding creative ways &mdash; short of dumpster diving &mdash; to scrape by.  Anything better than that was a success for me.  Recurring payments just made sense, especially because I was vastly undercutting my competitors in price.  That one decision helped sustain my business for many years.  In hindsight, I would not have had the little success I had with a single-payment model because I never brought in enough new customers.</p>\n\n\n\n<p>Having worked on the business end of WordPress for over a decade and being a member of the community for even longer, it is easy for me to say most companies should use a recurring business model.</p>\n\n\n\n<p>However, as a software customer in general, I have not always maintained that mindset.  There are many pieces of software that I loathe paying for each year.  This was particularly true before running a business that dealt with software.  There is a part of me that feels some shame for disliking the recurring model with non-WordPress software.  Those businesses need to pay their employees and afford to continue making the product better.</p>\n\n\n\n<p>On the other hand, there is always that part of me that simply wants to pay for something once and always have access to it.  Perhaps I am a product of my culture.  Software is unlike other art forms where Version 1.0 is the finished product.  Customers do not always see the work that goes on to maintain, support, and continue building a product.  That is certainly true when I look at non-WordPress software.</p>\n\n\n\n<p>For WordPress products, I am always more than happy to pay a recurring fee because I have been on the other side.  I also get to talk with others every day who are trying to run their own companies.  That human variable in the equation changes how I view software in the WordPress ecosystem in a way that is much harder with other software.</p>\n\n\n\n<h2>A Middle Ground</h2>\n\n\n\n<p>Starr pointed out a middle-of-the-road option that few WordPress companies take but is often the model used for other software products.  Major releases of software carry an upgrade fee while minor and patch releases are included with the initial purchase.  Often, major software releases have years in between.  Customers may not feel like they are constantly having to pay for updates in this system.  Major upgrades also mean feature upgrades.  Features are what sell the product to the average end-user.</p>\n\n\n\n<p><a href=\"https://www.literatureandlatte.com/scrivener/overview\">Scrivener</a>, a writing program for authors, uses this model.  Instead of having to pay yearly, I can upgrade to the new, shiny version when it drops with loads of features.  As a customer, I feel like I am getting something tangible when forking over the cash for an update.</p>\n\n\n\n<p>Perhaps I am happy to continue paying for software that helps me pursue my lifelong dream of becoming a novelist.  Perhaps the company simply knows how to sell to its customer base.  Either way, it is one piece of software that I have never complained about renewing.</p>\n\n\n\n<h2>What is the Best Option?</h2>\n\n\n\n<p>To answer the question posed by Starr, I will always prefer a one-time fee as a customer simply because it is in my nature to want to pay the least amount I can for anything.  However, I would prefer most WordPress businesses to go with whatever model is most sustainable for their specific business.  We are all in this boat together, and I wish growth for the ecosystem.</p>\n\n\n\n<p>One of the missing pieces with many WordPress plugin and theme shops is that they need to find creative ways to sell the customer on coming back.  Support and maintenance can be eye-catching for agencies and freelancers, but they are not always selling points for the average consumer after that initial purchase.</p>\n\n\n\n<p>Right now, there is a sense of complacency as WordPress-related businesses have stuck with similar recurring options over the last several years.  It might be time for someone to shake things up.</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, 18 Dec 2019 20:37: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:8;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: Bluehost Launches Premium WordPress Theme Marketplace to Customers\";s:7:\"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:29:\"https://wptavern.com/?p=95726\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/bluehost-launches-premium-wordpress-theme-marketplace-to-customers\";s: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:5675:\"<img />Screenshot of the Bluehost Marketplace from the customer dashboard.\n\n\n\n<p>In November, web hosting provider Bluehost <a href=\"https://www.bluehost.com/blog/bluehost-news/introducing-wordpress-themes-to-the-bluehost-marketplace-12981/\">launched a WordPress plugin and theme marketplace</a>.  The company integrated with <a href=\"https://www.mojomarketplace.com/\">MOJO Marketplace</a> to provide access to WordPress products via its customer dashboard.  Currently, the marketplace is open to third-party theme developers.  Plugin authors will have to wait, but they will eventually be able to sell their plugins through the Bluehost Marketplace.</p>\n\n\n\n<p>By integrating with MOJO Marketplace, much of the existing infrastructure and products are already in place.  Bluehost can simply offer the products to its customers through a custom-built interface and provide MOJO sellers with another avenue for distribution.</p>\n\n\n\n<p>The idea behind the marketplace is for Bluehost&rsquo;s customers to be able to build their websites without ever leaving their control panel.  &ldquo;Ultimately, we are trying to save customers time and energy from having to hunt for these things themselves and instead work within the dashboard to find the themes and plugins that are best fit for their site,&rdquo; said Suhaib Zaheer, general manager for Bluehost.</p>\n\n\n\n<p>&ldquo;Our native marketplace also provides our customers with the ability to automatically install the themes and plugins they have purchased, reducing the amount of time and number of steps required to get their site appearance and functionality up and running,&rdquo; he said.</p>\n\n\n\n<p>The Bluehost Marketplace currently has over 900 themes and 18 WooCommerce plugins for customers to choose from.  The themes are all viewable via the <a href=\"https://www.mojomarketplace.com/themes/wordpress\">WordPress themes page</a> on the MOJO website.  All themes uploaded by sellers go through a manual review process by the Bluehost Marketplace team before approval.  This includes basic items like design quality, functionality, installation, and documentation.</p>\n\n\n\n<p>There is also a &ldquo;Bluehost Certified&rdquo; filter available to users who want to use themes that have been further tested for quality control.  &ldquo;We conduct additional reviews to certify themes for our Bluehost Certified category on a quarterly basis,&rdquo; said Zaheer .</p>\n\n\n\n<p>There appear to be 85 themes that are Bluehost Certified based on a screenshot acquired of the marketplace.  However, that number is not verified.  The MOJO Marketplace page does not appear to have a filter to view these, but it is available to users of Bluehost&rsquo;s hosting service.</p>\n\n\n\n<h2>Selling on the Bluehost Marketplace</h2>\n\n\n\n<p>Theme developers who want to sell themes via Bluehost can apply through <a href=\"https://mojosupport.zendesk.com/hc/en-us/categories/200823136-Sellers\">MOJO Marketplace</a>.  Authors should note that they would like to be Bluehost Certified.  </p>\n\n\n\n<p>Theme sellers who want to get certification must meet the <a href=\"https://my.bluehost.com/hosting/help/certified-wordpress-themes\">Bluehost Certified guidelines</a>.  Some are fairly normal and would be expected in today&rsquo;s market such as responsiveness, browser compatibility, fast load times, and active support from the author.</p>\n\n\n\n<p>Others are a bit of a head-scratcher.  </p>\n\n\n\n<p>Certification requires that themes support page builders.  It&rsquo;s unclear which page builders need to be supported and what level of support is necessary.  Ideally, this would be the other way around.  Page builders should be built in such a way that they do not need theme-specific support.</p>\n\n\n\n<p>Demo content is required.  It is not clear if the requirements simply mean to provide an installable XML file with demo content or for the theme to output demo content in the absence of user content.  Based on the description, it seems like the latter.  If so, I would not want any part of that as a potential theme author.  I could see requiring the use of the WordPress starter content feature in this case but nothing more.</p>\n\n\n\n<p>The requirements also list &ldquo;plugins supported&rdquo; with no additional description.  <em>Good luck to theme authors figuring out exactly what that means.</em></p>\n\n\n\n<p>Bluehost needs to make its Bluehost Certified page more detailed to be attractive to potential theme authors.  There are far too many unanswered questions.</p>\n\n\n\n<p><a href=\"https://mojosupport.zendesk.com/hc/en-us/articles/115001076306-Commission-Rates\">Commission rates</a> are the same rates as other themes on the MOJO Marketplace.  Themes sold exclusively through the marketplace earn between 50% and 70% based on the number of sales.  Non-exclusive theme commissions are at a flat rate of 50%.  Both exclusive and non-exclusive authors can distribute their themes through the Bluehost Marketplace.</p>\n\n\n\n<p>&ldquo;Theme sellers are welcome to set the price of their item,&rdquo; said Zaheer.  &ldquo;However, we recommend they stay within $49-$69 range. If the review team does not feel the price is uniform with other themes in the same category, they will request a price change in order to be sold on the Marketplace.&rdquo;</p>\n\n\n\n<p>The pricing recommendation seems to be a bit on the low end, but it is consistent with the theme industry&rsquo;s race to the bottom.  Quality theme work should be at least double.</p>\n\n\n\n<p>Fortunately for theme authors, pricing is based on yearly renewals.  They are required to offer technical assistance within 24-48 hours while a user&rsquo;s yearly support license is up to date.</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, 17 Dec 2019 20:40:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"WordPress.org blog: State of the Word: the story of the slides\";s:7:\"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=8233\";s:7:\"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:77:\"https://wordpress.org/news/2019/12/state-of-the-word-the-story-of-the-slides/\";s: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:8021:\"<p>During the State of the Word at WordCamp US 2019, Matt Mullenweg shared that Gutenberg was used to create his slides and the presentation was powered by the Slides plugin. Using WordPress to power a slide deck isn’t an obvious choice, so we wanted to showcase the process and give some tips for making slide layouts using Gutenberg.</p>\n\n\n\n<p><em>This post is co-written by Ella and <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie</a>, who (along with <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel</a>, <a href=\"https://profiles.wordpress.org/mapk/\">Mark</a>, <a href=\"https://profiles.wordpress.org/nrqsnchz/\">Enrique</a>, <a href=\"https://profiles.wordpress.org/itsjonq/\">Q</a></em> <em>and a cast of supporters) helped create this year’s State of the Word slide deck.</em></p>\n\n\n\n<h2>How it Started</h2>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/ellatrix/\">Ella Van Durpe</a> was selected to speak at <a href=\"https://www.youtube.com/watch?v=ZNWNhUPrqB4\">JSConf</a> and ReactEurope and wanted slides for her presentation.&nbsp;</p>\n\n\n\n<p>In the past, she’d used Reveal.js to create slides and enjoyed the freedom to create anything using HTML, CSS and JavaScript. These languages were comfortable, familiar, and also can be published on the web in their native format.&nbsp;</p>\n\n\n\n<p>For these new presentations, she wanted to use Reveal.js again but didn’t feel like writing all the HTML by hand. Creating blocks of content visually, without having to actually write any code, which can be published natively to the web, is exactly what Gutenberg was built for.</p>\n\n\n\n<p>The plugin was prototyped quickly, with hardcoded styles on the slides and zero options. At the end of each presentation, Ella shared a brief demo of the Gutenberg-based slides and the audience was amazed.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">.<a href=\"https://twitter.com/ellatrx?ref_src=twsrc%5Etfw\">@ellatrx</a> any chance you might open source this? <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f642.png\" alt=\"?\" class=\"wp-smiley\" /> <a href=\"https://t.co/6hygMpBqUA\">https://t.co/6hygMpBqUA</a></p>&mdash; Pascal Birchler (@swissspidy) <a href=\"https://twitter.com/swissspidy/status/1131573525612048385?ref_src=twsrc%5Etfw\">May 23, 2019</a></blockquote>\n</div>\n\n\n\n<p>As WordCamp US approached, Ella suggested that her plugin be used for State of the Word. Since it was such a hit with her audience members, it seemed like this would be a great chance to share it with the WordPress community as a whole.</p>\n\n\n\n<span id=\"more-8233\"></span>\n\n\n\n<h2>How it Works</h2>\n\n\n\n<h3>Technical information</h3>\n\n\n\n<p>The plugin registers a custom post type called “presentation” and a new “slide” block. The slide block is a sort of enhanced “Group” block, which is restricted to the root of the post, but you can put any other block inside it. As a result, you have a post filled with only slides at the root and slides filled with content. This maps perfectly to the Reveal.js markup, which requires content in HTML section elements.</p>\n\n\n\n<p>Since these slides each have their own design, the theme styles are disabled and styling is set from each slide. A custom presentation template is provided by the plugin to render the custom post on the front-end.</p>\n\n\n\n<p>Then Ella added options to style the slides. For example, she added options to control the slide background and font, at both the document level and individual slide level. She also added Reveal.js options, which allow you to change the transition style and speed. Lastly, she added a custom CSS field to allow style overwrites.</p>\n\n\n\n<p>For the State of the Word, she also added speaker notes and a speaker view.</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/image.png?fit=632%2C363&ssl=1\" alt=\"\" class=\"wp-image-8271\" />\n\n\n\n<h3>How it&#8217;s Designed</h3>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/01.png?fit=632%2C515&ssl=1\" alt=\"\" class=\"wp-image-8262\" />\n\n\n\n<p>The inspiration for the slide designs came from Blue Note album covers (which were also the inspiration for the <a href=\"https://www.slideshare.net/photomatt/state-of-the-word-2011/\">2011 State of the Word slides</a>). These album covers inspired the recent “About” page in WordPress core and the starter content for the new Twenty Twenty theme. This style consists of strong, geometric shapes and simple forms with clean lines. Photography and bold typography are at the heart of this look.</p>\n\n\n\n<img src=\"https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?fit=632%2C541&ssl=1\" alt=\"\" class=\"wp-image-8267\" />\n\n\n\n<p>Various color palettes and font pairings were explored before selecting the best combination for the presentation.</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/03.png?fit=632%2C407&ssl=1\" alt=\"\" class=\"wp-image-8259\" />\n\n\n\n<p>A strong photographic element was needed for the slides. Past WordCamps are a great source of photos, so we dug through years of photo galleries to find just the right shots. With colors, fonts, and photos, we laid the foundation to build the deck.</p>\n\n\n\n<h2>Tips for Making Gutenberg Slides</h2>\n\n\n\n<h3>Tip One: columns are your friends</h3>\n\n\n\n<p>If you want slides with a precise layout, use columns. As you can see here, we used a 3 column layout to center content within a slide:</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/3.png?w=632&ssl=1\" alt=\"\" class=\"wp-image-8260\" />\n\n\n\n<h3>Tip Two: spacer blocks are useful</h3>\n\n\n\n<p>Want to really unlock the power of columns? Combine them with the spacer block! We used spacer blocks to position content over background images, like in this slide:</p>\n\n\n\n<img src=\"https://i2.wp.com/wordpress.org/news/files/2019/12/6.png?w=632&ssl=1\" alt=\"\" class=\"wp-image-8264\" />\n\n\n\n<h3>Tip Three: test on large screens</h3>\n\n\n\n<p>It’s important to preview and test your slides as you go. Make sure to design for the size and aspect ratio of the projector you’ll be using and do a visual check in presentation mode from time to time.</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/notes.png?fit=632%2C405&ssl=1\" alt=\"\" class=\"wp-image-8269\" />\n\n\n\n<h3>Tip Four: check your videos</h3>\n\n\n\n<p>A good demo video is integral to showcase new features. Joen Asmussen has a great post on <a href=\"https://automattic.design/2019/11/12/good-ui-demo-videos/\">creating effective demo videos</a>.</p>\n\n\n\n<h2>Lessons learned</h2>\n\n\n\n<blockquote class=\"wp-block-quote\"><p><em>I’d love to make the art directed compositions easier to create. </em></p><cite><em>Mel Choyce-Dwan</em></cite></blockquote>\n\n\n\n<p>As Gutenberg evolves, one big improvement is that art direction will get easier. Even with the improvements this year, creating some layouts in Gutenberg was trickier than expected. For the more complicated compositions, we relied on SVGs. Eventually, the need for hacks will dissolve away, and a new world of exciting possibilities will open for everyone.</p>\n\n\n\n<p>Browsers offered one of our biggest learnings in this presentation, more than they would if you use Keynote or Powerpoint, for example (tools most of us have used). Often, we found that what we created in the editor varied a when viewed full-screen. We were able to mitigate this by updating the plugin to use a fixed size, instead of using the entire browser window.</p>\n\n\n\n<h2>Wrapping it up</h2>\n\n\n\n<p>If you would like to check out the State of the Word, you can watch the <a href=\"https://wordpress.tv/2019/11/03/2019-state-of-the-word/\">video</a> and read all about it in a <a href=\"https://ma.tt/2019/11/state-of-the-word-2019/\">post</a>.</p>\n\n\n\n<p>The Slides plugin is not only available on the plugin repo, but you can also get the code from <a href=\"https://github.com/WordPress/slides\">GitHub</a> and <a href=\"https://translate.wordpress.org/projects/wp-plugins/slide/\">help translate</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, 17 Dec 2019 19:27:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Ella van Durpe\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"Matt: Comments and Collatz Conundrum\";s:7:\"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=50619\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://ma.tt/2019/12/comments-and-collatz-conundrum/\";s: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:1480:\"<p>Over the summer <a href=\"https://terrytao.wordpress.com/\">Terence Tao</a>, a <a href=\"https://en.wikipedia.org/wiki/Fields_Medal\">Fields Medal</a>-winning mathematician considered one of the best of his generation, got an anonymous comment <a href=\"https://terrytao.wordpress.com/2011/08/25/the-collatz-conjecture-littlewood-offord-theory-and-powers-of-2-and-3/\">on his WordPress blog post from 2011 exploring the Collatz conjecture</a> — one of the most persistent problems in math — suggesting he explore the problem for &#8220;almost all&#8221; numbers. Terence has been a regular WP.com blogger since 2007 and he and his commenters make <a href=\"https://en.support.wordpress.com/latex/\">extensive use of our LaTeX feature to express and embed equations</a>. </p>\n\n\n\n<p>That anonymous comment <a href=\"https://www.quantamagazine.org/mathematician-terence-tao-and-the-collatz-conjecture-20191211/\">led him to an important breakthrough on the Collatz Conundrum, as Quanta Magazine reports</a>. If you want great comments, you as the author have to participate in them and Terence is incredibly active in engaging with the commenters on his site.</p>\n\n\n\n<p>I&#8217;ve always said that comments are the best part of blogging, but this is a particularly cool example. <a href=\"https://terrytao.wordpress.com/2019/09/10/almost-all-collatz-orbits-attain-almost-bounded-values/\">Here&#8217;s Terence&#8217;s latest post on it</a>, with an excellent comment thread following.</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, 16 Dec 2019 21:46:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:11;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"WPTavern: Slim SEO Keeps Options Simple and Handles the Legwork of SEO\";s:7:\"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:29:\"https://wptavern.com/?p=95857\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/slim-seo-keeps-options-simple-and-handles-the-legwork-of-seo\";s: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:7627:\"<p>I have been running a blog of some kind since the Spring of 2003.  In a few short months, it will be my 17th <em>blog-aversary</em>.  The most important lesson I have learned over the years is to not do more work than is necessary to publish a blog post.</p>\n\n\n\n<p>There was a time when I fiddled with custom field boxes to fine-tune every aspect of a blog post, such as meta keywords, descriptions, titles, and much more.  However, worrying over every bit of metadata about a post became more work than actually writing the blog post itself.  It was killing my creative process.</p>\n\n\n\n<p>I have tried numerous SEO plugins and even built such a plugin myself once.  Eventually, I would always come back to simply automating most of the process for whatever project I was working on.</p>\n\n\n\n<p>Some SEO purists may balk at the idea.  They might argue that everything must be fine-tuned for the best results in search engines.  I could not say.  Worrying about ranking seems to be a never-ending, uphill battle.  In my experience, no particular plugin has ever given me an edge in comparison to another.  Results were always similar regardless of whether I fixated on every detail that options-filled SEO plugins offered or let an automated system generate the bits and pieces I needed.</p>\n\n\n\n<p>I decided to give the <a href=\"https://wordpress.org/plugins/slim-seo/\">Slim SEO plugin</a> a try.  It promised to handle the dirty work and ticked most of the boxes in terms of what I was looking for in an SEO plugin.</p>\n\n\n\n<p>Slim SEO is a plugin built by eLightUp, the company behind the <a href=\"https://wordpress.org/plugins/meta-box/\">Meta Box</a> framework and <a href=\"https://wordpress.org/themes/author/gretathemes/\">GretaThemes</a>.  Given their history of building quality extensions for WordPress, their SEO plugin made sense for a test run.</p>\n\n\n\n<p>The plugin beautifully handles the basics that you would expect from an SEO plugin.  It automatically handles meta tags, including Open Graph Tags for social media.  It generates a sitemap of your public posts and pages.  It outputs structured data via JSON-LD with no work on the user&rsquo;s part.</p>\n\n\n\n<p><strong>TL;DR:</strong> For users who are looking for a simple SEO solution with little legwork, Slim SEO is a solid option.  For users who want to tinker with every aspect of their SEO, look elsewhere.</p>\n\n\n\n<h2>A Slim User Interface</h2>\n\n\n\n<p>As a user, the things I tire of quickly the most are complex options screens.  <em>Just give me the basics.</em>  That is exactly what Slim SEO does.  It has a single options screen titled &ldquo;SEO&rdquo; under the default &ldquo;Settings&rdquo; menu in the admin.  Currently, the only options are for inputting header and footer scripts from various services, such as Google Tag Manager or Google Analytics.</p>\n\n\n\n<p>On the post-editing screen, the plugin provides a simple meta box for customizing the meta title and description.  Users can also opt to hide the post from search engines and change the Facebook and Twitter images for the post.  And, that&rsquo;s it.</p>\n\n\n\n<img />Per-post SEO options meta box.\n\n\n\n<p>Each of these options can be skipped if you prefer to let the plugin handle them automatically.</p>\n\n\n\n<p>Suffice it to say, I am a fan of the slimmed-down interface.  The plugin has no SEO scores, keyword rankings, or 20 different options to worry about.  It does not show a preview of what the post might look like in a search engine.  The options available are items that I <em>may</em> want to configure from time to time, so it&rsquo;s nice to have the ability to do so when needed.</p>\n\n\n\n<h2>The Downsides of the Plugin</h2>\n\n\n\n<p>Slimmed-down does not always equate to being better.  You make sacrifices by allowing the plugin to make decisions that may not always be the best for your site.  Keep these in mind when deciding whether to use the plugin.</p>\n\n\n\n<h3>Automatic Redirects</h3>\n\n\n\n<p>One of the biggest downsides of automated systems is that I sometimes want things to be handled differently by the plugin.  The plugin&rsquo;s automatic redirect feature is a good example of that issue.  Out of the box, the plugin will redirect all attachment page views to the media file.  It also redirects visitors to author archive pages to the home page if the author has not written any posts or on single-author sites.</p>\n\n\n\n<p>These auto-redirects may be desirable for some end-users, but they are not something I want.  The problem is there is no clear way to disable this feature, even via code.</p>\n\n\n\n<h3>Header Cleanup</h3>\n\n\n\n<p>The plugin also has a &ldquo;cleanup&rdquo; feature that automatically removes the RSD link, Windows Live Writer manifest link, WordPress version number, and post shortlink from the <code>&lt;head&gt;</code> area on the front end.  It may be desirable to remove those items, but their removal would be more appropriate in a cleanup WordPress type of plugin rather than a plugin focused on SEO.</p>\n\n\n\n<h3>Automatic Image Alt Attributes</h3>\n\n\n\n<p>Slim SEO automatically adds the <code>alt</code> attribute to post thumbnails and when inserting images into the editor.  The problem is that it uses the attachment title.  This could make accessibility worse than simply leaving the alt attribute empty.  If your attachment title is something like <code>DS_IMG9453.jpg</code>, it does not accurately describe an image.</p>\n\n\n\n<h3>Breadcrumbs</h3>\n\n\n\n<p>The plugin has a shortcode for outputting breadcrumbs.  It must either be manually added to a shortcode-aware area or within a theme template.</p>\n\n\n\n<p>The breadcrumbs functionality provides a baseline experience. It doesn&rsquo;t handle every scenario or even close to every scenario.  The feature will not get you far with highly-complex setups.   However, it would work OK for the average install. </p>\n\n\n\n<p>That&rsquo;s par for the course with SEO plugins &mdash; mediocre breadcrumbs at best.  Frankly, SEO plugins should drop breadcrumbs from the feature list and let fully-fledged breadcrumb plugins do their thing.  Users should use opt for a plugin that specifically focuses on being a breadcrumb plugin.  Authors who build those tend to have more experience handling edge cases.</p>\n\n\n\n<h2>How Does the Code Stack Up?</h2>\n\n\n\n<p>From a programming perspective, the code is clean and clear.  It is 90% to the point where it should be.  The missing 10% is that there are no references to many of the objects the plugin creates.  This is not an issue limited to this plugin and is more common than it should be.</p>\n\n\n\n<p>This issue makes it next to impossible to remove actions and filters from hooks.  For end-users, this does not matter.  For developers, it is not a frustration-free exercise to manipulate how the plugin works.  This could easily be solved in numerous ways, such as using a container, service locator, static single instance, singleton, or even a global.  Whether some of those methods should be deployed is beyond the scope of this review.  Nevertheless, <em>some</em> reference to the plugin&rsquo;s objects would help.</p>\n\n\n\n<p>Addressing this issue would come in handy disabling those auto-redirects.</p>\n\n\n\n<h2>The Final Verdict</h2>\n\n\n\n<p>Aside from a handful of admittedly trivial gripes, I would use this plugin in lieu of SEO plugins with more options.  Years of running multiple sites has taught me to grab for the simplest solutions so that I can get back to doing the things I enjoy doing.</p>\n\n\n\n<p>If you prefer to micro-manage every aspect of your SEO, there are plenty of existing options out there.  Slim SEO will not fit your needs.</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, 16 Dec 2019 20:48:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:12;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: Inserting Special Characters Into the Block Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=95833\";s:7:\"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://wptavern.com/inserting-special-characters-into-the-block-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3696:\"<p>For users of the Classic WordPress editor who often needed to insert special characters into their posts, life was once simple.  Click the &ldquo;&Omega;&rdquo; button in the editor to open a modal with a list of characters not found on a standard keyboard.  The user then only needed to click on the character they wanted to insert and go about the business of writing their post.</p>\n\n\n\n<p>For users who made the move to the block editor and were accustomed to inserting special characters at the click of a button, life became more complicated.  The answer to their woes was to first insert a Classic block and use its special character inserter, which kind of defeats the purpose of using the new and shiny block editor.  Another option was to use the special character app/program packaged with their computer, which assumes all users know the keyboard shortcut for it or how to run the program.</p>\n\n\n\n<p>By many accounts, this would be considered a <em>standard</em> feature for any text editor.  When WordPress is at a stage of trying to sell a new editor, it should be prepared to include features that users of the old editor consider standard.  The lack of a special-character inserter could have been written off as an oversight if people were not asking for it.</p>\n\n\n\n<ul><li><a href=\"https://github.com/WordPress/gutenberg/issues/1678\">Reimplement Character Map</a></li><li><a href=\"https://github.com/WordPress/gutenberg/issues/7162\">Just a Few More Text/Paragraph Formatting Choices?</a></li><li><a href=\"https://github.com/WordPress/gutenberg/issues/8782\">Add Special Character Menu</a></li><li><a href=\"https://github.com/WordPress/gutenberg/issues/8817\">Where Are the Special Characters?</a></li></ul>\n\n\n\n<p>People <em>were</em> asking for it.</p>\n\n\n\n<p>Fortunately, the requests caught the attention of the 10up team.  In September this year, they <a href=\"https://10up.com/blog/2019/insert-special-characters-wordpress-plugin/\">released the first version</a> of their <a href=\"https://wordpress.org/plugins/insert-special-characters/\">Insert Special Characters</a> plugin.  It has since gone through a couple of updates and works well across browsers.</p>\n\n\n\n<p>The plugin is simple and does its job much better than the previous Classic editor inserter.  Instead of just handling the basics, the team went above and beyond what was necessary to launch the plugin.</p>\n\n\n\n<p>The plugin adds a new sub-menu item to the text toolbar titled &ldquo;&Omega; Special Characters.&rdquo;</p>\n\n\n\n<img />&ldquo;Special Characters&rdquo; rich text menu item.\n\n\n\n<p>After clicking the link to insert a special character, a modal box appears on the screen.  The box provides hundreds of special characters to choose from.  It sorts them under Miscellaneous, Math, Latin, and Arrow categories while providing a search filter to narrow down the list.  The box can also be reached by typing <code>ctrl</code>/<code>cmd</code> + <code>o</code> on the keyboard.</p>\n\n\n\n<img />Special characters insertion modal box.\n\n\n\n<p>Like many modals, the box pops up in a weird position from time to time, depending on where the insertion point is on the screen. Outside of that, I found no major problems with the plugin.</p>\n\n\n\n<p>The plugin also <a href=\"https://github.com/10up/insert-special-characters/blob/1.0.2/README.md#extending\">provides a hook</a> for other developers to manipulate the tabs and available characters in the modal.</p>\n\n\n\n<p>This does beg the question of whether the feature should be implemented in the core block editor now.  If the core team puts it in at this point, one would hope they would make it competitive with the plugin.  Anything less would be a letdown.</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, 13 Dec 2019 20:46:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"WPTavern: WordPress 5.3.1 Includes Security and Bug Fixes, Accessibility Enhancements, and Twenty Twenty Changes\";s:7:\"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:29:\"https://wptavern.com/?p=95815\";s:7:\"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:121:\"https://wptavern.com/wordpress-5-3-1-includes-security-and-bug-fixes-accessibility-enhancements-and-twenty-twenty-changes\";s: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:4204:\"<p><a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">WordPress 5.3.1 was released today</a> with 46 bug fixes and enhancements.  Changes include several accessibility improvements and four security vulnerability fixes.  The update includes multiple changes to the default Twenty Twenty theme.</p>\n\n\n\n<p>Version 5.3.1 is a security and maintenance release.  All users are encouraged to update as soon as possible.  For those with auto-updates enabled, updates are currently rolling out.  All major branches of WordPress from version 3.7 through 5.3 received the new security fixes.</p>\n\n\n\n<p>The following security issues were addressed:</p>\n\n\n\n<ul><li>Users without the correct permission (capability) could make a post sticky via the REST API.</li><li>An issue where cross-site scripting (XSS) could be stored in links.</li><li>Hardening the <code>wp_kses_bad_protocol()</code> function so that it is aware of the named colon attribute.</li><li>A stored XSS vulnerability using block editor content.</li></ul>\n\n\n\n<p>Most of the release focused on maintenance.  Form fields and buttons now have the same height, which should result in a more consistent admin UI.  This has long been an issue, but the accessibility changes in WordPress 5.3 highlighted the problem.</p>\n\n\n\n<p>A bug with how permalinks were generated with the new Date/Time changes in WordPress 5.3 has been fixed.  This left some sites using date-based URLs with incorrect post permalinks.</p>\n\n\n\n<p>Other changes include removing support for the CollegeHumor oEmbed provider (the site is no longer available), updating the <code>sodium_compat</code> library, and making sure admin verification emails use the user&rsquo;s locale instead of the site&rsquo;s locale.  For a full overview of all changes, visit the <a href=\"https://wordpress.org/support/wordpress-version/version-5-3-1/\">WordPress 5.3.1 release page</a>.</p>\n\n\n\n<h2>Accessibility Improvements</h2>\n\n\n\n<img />&ldquo;Coffee&rdquo; color scheme with new button colors.\n\n\n\n<p>Some of the biggest accessibility changes fixed issues with the <a href=\"https://make.wordpress.org/core/2019/12/10/alternate-color-schemes-changes-in-wordpress-5-3-1/\">alternate admin color schemes</a> available in WordPress.  The accessibility improvements to buttons in WordPress 5.3 did not get carried over to most of the alternate schemes.  Or, rather, those alternate color schemes were not taken into account when the changes went into effect.  This left secondary button elements practically unreadable in some cases, which made accessibility worse.</p>\n\n\n\n<p>Version 5.3.1 creates a unified design for secondary buttons for every color scheme.  It also makes sure that the <code>:active</code> state for buttons are consistent.</p>\n\n\n\n<p>Other improvements to accessibility include adding underlines to links on the Dashboard screen that were not clearly links by context, properly disabling nav menu forms when they should not be in use, and adding hover effects for links on the &ldquo;About&rdquo; admin screens.</p>\n\n\n\n<h2>Twenty Twenty Changes</h2>\n\n\n\n<img />Author bio option in the customizer.\n\n\n\n<p>The Twenty Twenty theme launched with JavaScript-based, smooth-scroll behavior for anchor links.  This feature did not work correctly in all cases.  It also broke anchor links to individual comments when paginated comments were enabled on a site.  </p>\n\n\n\n<p>Version 1.1 of Twenty Twenty <a href=\"https://make.wordpress.org/core/2019/12/08/twenty-twenty-animated-scroll-changes-in-wordpress-5-3-1/\">includes CSS-based, smooth-scroll behavior</a>.  This greatly simplifies the code by using native behavior.  It also works based on the user&rsquo;s reduced motion setting for their browser, which enhances accessibility for the theme.</p>\n\n\n\n<p>The theme update comes packaged with a new option for showing or hiding the post author bio.  The setting is available under the &ldquo;Theme Options&rdquo; section in the customizer.  It is enabled by default and will show the author bio section at the end of every post across the site.</p>\n\n\n\n<p>The Twenty Twenty update also includes several bug fixes, most of which were trivial issues.</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, 13 Dec 2019 00:58:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:14;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"WordPress.org blog: WordPress 5.3.1 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8203\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:12695:\"<p>WordPress 5.3.1 is now available!</p>\n\n\n\n<p>This security and maintenance release features 46 fixes and enhancements. Plus, it adds a number of security fixes—see the list below.</p>\n\n\n\n<p>WordPress 5.3.1 is a short-cycle maintenance release. The next major release will be version 5.4.</p>\n\n\n\n<p>You can download WordPress 5.3.1 by clicking the button at the top of this page, or visit your<strong>&nbsp;Dashboard → Updates</strong>&nbsp;and click&nbsp;<strong>Update Now</strong>.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h2>Security updates</h2>\n\n\n\n<p>Four security issues affect WordPress versions 5.3 and earlier; version 5.3.1 fixes them, so you’ll want to upgrade. If you haven’t yet updated to 5.3, there are also updated versions of 5.2 and earlier that fix the security issues.</p>\n\n\n\n<ul><li>Props to <a href=\"https://danielbachhuber.com/\">Daniel Bachhuber</a> for finding an issue where an unprivileged user could make a post sticky via the REST API.</li><li>Props to <a href=\"https://blog.ripstech.com/authors/simon-scannell\">Simon Scannell of RIPS Technologies</a> for finding and disclosing an issue where cross-site scripting (XSS) could be stored in well-crafted links.</li><li>Props to the <a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://wordpress.org/\">WordPress.org</a> Security Team for hardening <code>wp_kses_bad_protocol()</code> to ensure that it is aware of the named colon attribute.</li><li>Props to <a href=\"https://twitter.com/ducnt_\">Nguyen The Duc</a> for discovering a stored XSS vulnerability using block editor content.</li></ul>\n\n\n\n<h2>Maintenance updates</h2>\n\n\n\n<p>Here are a few of the highlights:</p>\n\n\n\n<ul><li>Administration: improvements to admin form controls height and alignment standardization (see related <a href=\"https://make.wordpress.org/core/2019/12/11/admin-form-controls-height-and-alignment-standardization-in-wordpress-5-3-1/\">dev note</a>), dashboard widget links accessibility and alternate color scheme readability issues (see related <a href=\"https://make.wordpress.org/core/2019/12/10/alternate-color-schemes-changes-in-wordpress-5-3-1/\">dev note</a>).</li><li>Block editor: fix Edge scrolling issues and intermittent JavaScript issues.</li><li>Bundled themes: add customizer option to show/hide author bio, replace JS based smooth scroll with CSS (see related <a href=\"https://make.wordpress.org/core/2019/12/08/twenty-twenty-animated-scroll-changes-in-wordpress-5-3-1/\">dev note</a>) and fix Instagram embed CSS.</li><li>Date/time: improve non-GMT dates calculation, fix date format output in specific languages and make&nbsp;<code>get_permalink()</code>&nbsp;more resilient against PHP timezone changes.</li><li>Embeds: remove CollegeHumor oEmbed provider as the service doesn&#8217;t exist anymore.</li><li>External libraries: update <code>sodium_compat</code>.</li><li>Site health: allow the remind interval for the admin email verification to be filtered.</li><li>Uploads: avoid thumbnails overwriting other uploads when filename matches, and exclude PNG images from scaling after upload.</li><li>Users: ensure administration email verification uses the user&#8217;s locale instead of the site locale.</li></ul>\n\n\n\n<p>For more information, <a href=\"https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=5.3.1&order=priority\">browse the full list of changes on Trac</a> or check out the&nbsp;<a href=\"https://wordpress.org/support/wordpress-version/version-5-3-1/\">version 5.3.1 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks!</h2>\n\n\n\n<p>In addition to the security researchers mentioned above, thank you to everyone who contributed to WordPress 5.3.1:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/123host/\">123host</a>, <a href=\"https://profiles.wordpress.org/acosmin/\">acosmin</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/aljullu/\">Albert Juhé Lluveras</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/viper007bond/\">Alex Mills</a>, <a href=\"https://profiles.wordpress.org/anantajitjg/\">Anantajit JG</a>, <a href=\"https://profiles.wordpress.org/anlino/\">Anders Norén</a>, <a href=\"https://profiles.wordpress.org/andraganescu/\">andraganescu</a>, <a href=\"https://profiles.wordpress.org/afercia/\">Andrea Fercia</a>, <a href=\"https://profiles.wordpress.org/aduth/\">Andrew Duthie</a>, <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey &#8220;Rarst&#8221; Savchenko</a>, <a href=\"https://profiles.wordpress.org/aravindajith/\">aravindajith</a>, <a href=\"https://profiles.wordpress.org/archon810/\">archon810</a>, <a href=\"https://profiles.wordpress.org/ate-up-with-motor/\">Ate Up With Motor</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/birgire/\">Birgir Erlendsson (birgire)</a>, <a href=\"https://profiles.wordpress.org/boga86/\">Boga86</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/poena/\">Carolina Nymark</a>, <a href=\"https://profiles.wordpress.org/chetan200891/\">Chetan Prajapati</a>, <a href=\"https://profiles.wordpress.org/littlebigthing/\">Csaba (LittleBigThings)</a>, <a href=\"https://profiles.wordpress.org/xendo/\">Dademaru</a>, <a href=\"https://profiles.wordpress.org/danielbachhuber/\">Daniel Bachhuber</a>, <a href=\"https://profiles.wordpress.org/mte90/\">Daniele Scasciafratte</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">David Baumwald</a>, <a href=\"https://profiles.wordpress.org/dlh/\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion hulse</a>, <a href=\"https://profiles.wordpress.org/ehtis/\">ehtis</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/epiqueras/\">epiqueras</a>, <a href=\"https://profiles.wordpress.org/fabifott/\">Fabian</a>, <a href=\"https://profiles.wordpress.org/flixos90/\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/flaviozavan/\">flaviozavan</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse/\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/hometowntrailers/\">Glenn</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Grzegorz (Greg) Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/grzegorzjanoszka/\">Grzegorz.Janoszka</a>, <a href=\"https://profiles.wordpress.org/hareesh-pillai/\">Hareesh Pillai</a>, <a href=\"https://profiles.wordpress.org/ianbelanger/\">Ian Belanger</a>, <a href=\"https://profiles.wordpress.org/ispreview/\">ispreview</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/macmanx/\">James Huff</a>, <a href=\"https://profiles.wordpress.org/jameskoster/\">James Koster</a>, <a href=\"https://profiles.wordpress.org/jarretc/\">Jarret</a>, <a href=\"https://profiles.wordpress.org/studiotwee/\">Jasper van der Meer</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/jeichorn/\">jeichorn</a>, <a href=\"https://profiles.wordpress.org/jeremyclarke/\">Jer Clarke</a>, <a href=\"https://profiles.wordpress.org/jeremyfelt/\">Jeremy Felt</a>, <a href=\"https://profiles.wordpress.org/jipmoors/\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/joehoyle/\">Joe Hoyle</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/spacedmonkey/\">Jonny Harris</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/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/justdaiv/\">justdaiv</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Dwan</a>, <a href=\"https://profiles.wordpress.org/kharisblank/\">Kharis Sulistiyono</a>, <a href=\"https://profiles.wordpress.org/ixkaito/\">Kite</a>, <a href=\"https://profiles.wordpress.org/kyliesabra/\">kyliesabra</a>, <a href=\"https://profiles.wordpress.org/lisota/\">lisota</a>, <a href=\"https://profiles.wordpress.org/lukaswaudentio/\">lukaswaudentio</a>, <a href=\"https://profiles.wordpress.org/maciejmackowiak/\">Maciej Mackowiak</a>, <a href=\"https://profiles.wordpress.org/marcelo2605/\">marcelo2605</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/mat-lipe/\">Mat Lipe</a>, <a href=\"https://profiles.wordpress.org/mayanksonawat/\">mayanksonawat</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/michael-arestad/\">Michael Arestad</a>, <a href=\"https://profiles.wordpress.org/miette49/\">miette49</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/mauteri/\">Mike Auteri</a>, <a href=\"https://profiles.wordpress.org/msaari/\">Mikko Saari</a>, <a href=\"https://profiles.wordpress.org/gdragon/\">Milan Petrovic</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/nextscripts/\">NextScripts</a>, <a href=\"https://profiles.wordpress.org/nickdaugherty/\">Nick Daugherty</a>, <a href=\"https://profiles.wordpress.org/nielslange/\">Niels Lange</a>, <a href=\"https://profiles.wordpress.org/noyle/\">noyle</a>, <a href=\"https://profiles.wordpress.org/ov3rfly/\">Ov3rfly</a>, <a href=\"https://profiles.wordpress.org/paragoninitiativeenterprises/\">Paragon Initiative Enterprises</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/larrach/\">Rachel Peter</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/quicoto/\">Ricard Torres</a>, <a href=\"https://profiles.wordpress.org/murgroland/\">Roland Murg</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/samuelfernandez/\">SamuelFernandez</a>, <a href=\"https://profiles.wordpress.org/sathyapulse/\">sathyapulse</a>, <a href=\"https://profiles.wordpress.org/wonderboymusic/\">Scott Taylor</a>, <a href=\"https://profiles.wordpress.org/scvleon/\">scvleon</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/sergiomdgomes/\">sergiomdgomes</a>, <a href=\"https://profiles.wordpress.org/sgr33n/\">SGr33n</a>, <a href=\"https://profiles.wordpress.org/simonjanin/\">simonjanin</a>, <a href=\"https://profiles.wordpress.org/smerriman/\">smerriman</a>, <a href=\"https://profiles.wordpress.org/steevithak/\">steevithak</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\">Stephen Bernhardt</a>, <a href=\"https://profiles.wordpress.org/netweb/\">Stephen Edgar</a>, <a href=\"https://profiles.wordpress.org/dufresnesteven/\">Steve Dufresne</a>, <a href=\"https://profiles.wordpress.org/subratamal/\">Subrata Mal</a>, <a href=\"https://profiles.wordpress.org/manikmist09/\">Sultan Nasir Uddin</a>, <a href=\"https://profiles.wordpress.org/cybr/\">Sybre Waaijer</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/tanvirul/\">Tanvirul Haque</a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>, <a href=\"https://profiles.wordpress.org/timon33/\">timon33</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/spaceshipone/\">Timothée Brosille</a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/dinhtungdu/\">Tung Du</a>, <a href=\"https://profiles.wordpress.org/veminom/\">Veminom</a>, <a href=\"https://profiles.wordpress.org/vortfu/\">vortfu</a>, <a href=\"https://profiles.wordpress.org/waleedt93/\">waleedt93</a>, <a href=\"https://profiles.wordpress.org/williampatton/\">williampatton</a>, <a href=\"https://profiles.wordpress.org/wpgurudev/\">wpgurudev</a>, and <a href=\"https://profiles.wordpress.org/tollmanz/\">Zack Tollman</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 13 Dec 2019 00:07: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: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:15;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:118:\"WPTavern: Gutenberg 7.1 Includes Welcome Modal, Improves Multi-Block Selection, and Adds Drag-and-Drop Featured Images\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=95796\";s:7:\"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:127:\"https://wptavern.com/gutenberg-7-1-includes-welcome-modal-improves-multi-block-selection-and-adds-drag-and-drop-featured-images\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7146:\"<p class=\"has-drop-cap\">The past two weeks have been blazing fast for <a href=\"https://make.wordpress.org/core/2019/12/11/whats-new-in-gutenberg-11-december/\">Gutenberg plugin development</a>.  A total of 161 pull requests (patches) were merged into version 7.1 of the plugin.  Over 20 bugs were squashed while the team added several enhancements, which include better multi-block selection, a new welcome modal, and drag-and-drop featured images.</p>\n\n\n\n<p>The team refactored several areas of the codebase to prepare for future changes and make it possible to use new hooks.  API changes include a new <a href=\"https://github.com/WordPress/gutenberg/pull/17926\">custom select control</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/18609\">text highlight</a>, and <a href=\"https://github.com/WordPress/gutenberg/pull/17603\">custom gradient picker</a> components for developers to use in their plugins.</p>\n\n\n\n<p>The release also featured a toolbar button for switching between &ldquo;edit&rdquo; and &ldquo;select&rdquo; mode.  The select mode allows you to select blocks without opening the editing controls unless you click again within a block, which switches you back to editing mode.  The only noticeable difference is that the editing controls do not appear while in select mode.  <em>Wondering when I will ever use this feature&hellip;</em></p>\n\n\n\n<h2>Welcome Guide Modal</h2>\n\n\n\n<img />New welcome guide modal for first-time users.\n\n\n\n<p>The new version of the plugin includes a <a href=\"https://github.com/WordPress/gutenberg/pull/18041\">pop-up welcome modal</a> for first-time users.  There are currently three panels with short introductions to what blocks are, how to use them, and getting to know the block library.  </p>\n\n\n\n<p>Ideally, the modal will link out to more extensive documentation in a future iteration.  Right now, the information provided does not go into much detail.  It feels like a message to say, &ldquo;Hey, check out this shiny new thing.&rdquo;  However, there needs to be more substance for it to be helpful for first-timers.</p>\n\n\n\n<h2>Improved Multi-block Selection</h2>\n\n\n\n<img />Selecting multiple blocks at once.\n\n\n\n<p>The block editor now incorporates a nicer <a href=\"https://github.com/WordPress/gutenberg/pull/16835\">native multi-block selection</a> process.  The first aspect of this change is to use the native selection color, which improves accessibility.  It also uses native selection behavior when selecting multiple blocks.</p>\n\n\n\n<p>The second part is important because it paves the way toward partial block selection in a future release.  Currently, when selecting text across multiple blocks, the editor extends this out to select all text from the selected blocks.  In the future, it should be possible to select only part of the text across multiple blocks.  This would be consistent with normal text-based editors where users can select the last sentence from one paragraph and the first from the next, for example.</p>\n\n\n\n<p><a href=\"https://github.com/WordPress/gutenberg/pull/18746\">Selecting multiple blocks and pasting</a> new content works correctly in 7.1.  In the past, the rich text component handled pasting.  This resulted in the blocks being split and the pasted content inserted between the split.  The block editor now handles the pasting process.  This allows users to completely replace multiple selected blocks with a paste.</p>\n\n\n\n<h2>Drag-and-Drop Featured Images</h2>\n\n\n\n<img />Dragging a featured image from the desktop.\n\n\n\n<p>Instead of clicking the featured image box to open the media modal, users can now save themselves a click.  Just like dragging and dropping an image into the editor, the featured image box now accepts any image file dropped into it.</p>\n\n\n\n<h2>Table Captions</h2>\n\n\n\n<img />Adding a caption to the table block.\n\n\n\n<p>For those who have long waited for a true table <code>&lt;caption&gt;</code> implementation, keep on waiting.</p>\n\n\n\n<p>A <a href=\"https://github.com/WordPress/gutenberg/issues/11589\">year-old ticket</a> that was opened for a table caption feature was closed with a solution matching that of other blocks with captions (e.g., image, gallery).  The <a href=\"https://github.com/WordPress/gutenberg/pull/15554\">pull request</a> featured a lengthy discussion over the technical limitations of how to best handle the feature.  Ultimately, the decision was to wrap tables in a <code>&lt;figure&gt;</code> element and add the caption via the <code>&lt;figcaption&gt;</code> tag.</p>\n\n\n\n<p>While this may work for some who need to add a caption or summary below a table, it is not currently helping users who need captions in their normal spot at the top of a table.</p>\n\n\n\n<p>In the long run, users who need to roll out advanced tables will likely need a table block plugin anyway.  The Gutenberg and core WordPress implementation is limiting for anything beyond the most basic table output.  Real captions would have been a nice touch though.</p>\n\n\n\n<h2>Alignment for the Navigation Block</h2>\n\n\n\n<img />Aligning navigation block items.\n\n\n\n<p>The Navigation block, which moved out of the experimental stage in version 7.0, has a <a href=\"https://github.com/WordPress/gutenberg/pull/18909\">new option for justifying</a> the list items to the left, right, or center.  This will be an important feature for full-site editing in the long term because users will want to set their nav menu perfectly.</p>\n\n\n\n<p>This block will likely be in flux for a while.  There are still major questions about how navigation will work on mobile, especially as we inch closer to full-site editing.  <em>Will core play a role in making mobile menus?  Will themes be left to their own devices?  Will themes offer multiple options based on screen size?</em></p>\n\n\n\n<h2>Moving Ahead with Templates and Full-Site Editing</h2>\n\n\n\n<p>Coming off the heels of a somewhat controversial <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">documentation proposal for block-based themes</a>, version 7.1 includes a new demo block template named <code>index.html</code>.  It is a fallback template in cases where no templates are available.  This is an early, experimental step toward making full-site editing a reality.  </p>\n\n\n\n<p>Theme developers who want to start looking at what block templates <em>could</em> look like, should <a href=\"https://github.com/WordPress/gutenberg/blob/v7.1.0/lib/demo-block-templates/index.html\">view the demo index.html template</a>.</p>\n\n\n\n<p>Unfortunately, the release ZIP file available through the official plugin repository does not include the <code>index.html</code> template.  It was excluded because of a <a href=\"https://github.com/WordPress/gutenberg/issues/19066\">bug in the build process</a>.  However, it may be packaged in a version 7.1.1 minor release.  The file is correctly included for developers who clone from the Git repository.</p>\n\n\n\n<p>The second step of this process was the addition of a Template Part block.  The idea for this block is that it would be a placeholder to add to templates, which would output a template part on the front end.</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, 11 Dec 2019 21:21:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"bbPress: bbPress 2.6.3 is out!\";s:7:\"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:29:\"https://bbpress.org/?p=206794\";s:7:\"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:54:\"https://bbpress.org/blog/2019/12/bbpress-2-6-3-is-out/\";s: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:967:\"<p>bbPress 2.6.3 fixes <a href=\"https://bbpress.trac.wordpress.org/query?status=closed&group=resolution&milestone=2.6.3\">9 issues</a> reported by community members:</p>\n\n\n\n<ul><li>Fixes a few typos and grammatical errors</li><li>Bumps required WordPress versions to 5.3.0 (bbPress always only officially supports the latest WordPress version)</li><li>Fixes the Forums widget displaying in the wrong order</li><li>Fixes a JavaScript error with hierarchical replies</li></ul>\n\n\n\n<p class=\"has-text-color has-background has-very-dark-gray-color has-very-light-gray-background-color\">We&#8217;re continuing to work on improving bbPress 2.6 while also deciding what exactly will make it into 2.7.</p>\n\n\n\n<p class=\"has-text-color has-background has-very-dark-gray-color\">Expect for the next minor release (bbPress 2.6.4) to be released sometime before Christmas 2019. <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f41d.png\" alt=\"?\" class=\"wp-smiley\" /></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 10 Dec 2019 20:52: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:17:\"John James Jacoby\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Creator of EditorsKit Launches Community Block-Sharing 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:29:\"https://wptavern.com/?p=95775\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/creator-of-editorskit-launches-community-block-sharing-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:4340:\"<img />\n\n\n\n<p>Jeffrey Carandang, the creator behind the EditorsKit WordPress plugin, <a href=\"https://shareablock.com/introducing-shareablock-share-and-download-free-gutenberg-block-template-designs/\">launched a new community site</a> for sharing block designs and templates today.  The ShareABlock website allows visitors to download block files directly from the site and import them into the block editor.  Users can also sign up to share custom block designs and full-blown block templates.  All downloads are available for free.</p>\n\n\n\n<p>At the moment, there are 18 block designs available for download.  There are two primary types of downloads:  block patterns and block templates. </p>\n\n\n\n<p><a href=\"https://shareablock.com/blocks/category/block-patterns/\">Patterns</a> are smaller groupings of blocks to create a specific section for a page.  These include designs such as various hero sections, pricing lists, and a call-to-action section. </p>\n\n\n\n<p><a href=\"https://shareablock.com/blocks/category/templates/\">Templates</a> work the same way as patterns.  However, they are larger sets of blocks designed to create an entire page.  For example, one template allows users to import a full gallery portfolio page.  Another creates an editable resume layout.</p>\n\n\n\n<p>Other than Carandang, two other contributors have shared block designs.  This number should rise as more people sign up and decide to share their creations.  The <a href=\"https://shareablock.com/how-to-submit-design-on-share-a-block/\">registration process</a> is open to anyone who wants to join.  However, each contribution is subject to a review for quality assurance.</p>\n\n\n\n<p>&ldquo;One of my primary goals in creating [EditorsKit] is to help users get a little more comfortable with using the new WordPress Gutenberg block editor,&rdquo; described Carandang in the announcement post for ShareABlock.  &ldquo;The goal is to help users create Gutenberg blocks easily. With drag and drop import, layout and designs will be available in an instant.&rdquo;</p>\n\n\n\n<p>Carandang feels confident that pre-configured block designs will help users learn how to use the block editor to create richer content.  &ldquo;Even if it&rsquo;s just a little help to make them comfortable with Gutenberg, it means a lot,&rdquo; he wrote.</p>\n\n\n\n<p>He said the feedback from users has been positive thus far.</p>\n\n\n\n<img />Importing the Fullscreen Profile Card block pattern.\n\n\n\n<p>Block designs downloaded from ShareABlock require the <a href=\"https://wordpress.org/plugins/block-options/\">EditorsKit plugin</a>, which is available for free in the WordPress plugin directory.  This requirement is because WordPress does not currently have a native importer built into the block editor.  In the future, this may change and the requirement could be lifted.</p>\n\n\n\n<p>Version 1.7 of EditorsKit introduced the <a href=\"https://wptavern.com/editorskit-1-6-and-1-7-add-tools-for-writers-drag-and-drop-block-export-import\">ability to import blocks</a> by dragging and dropping a block <code>.json</code> file into the editor.  The blocks available via ShareABlock work using this feature.  After downloading a <code>.json</code> file from the site, users merely need to drag it into the editor.  Users can also use the &ldquo;Import&rdquo; block available from EditorsKit to do the same.</p>\n\n\n\n<h2>Block Patterns and the Future</h2>\n\n\n\n<p>&ldquo;The plan is to provide integration with Block Patterns, which is what the core devs are currently working on,&rdquo; said Carandang.  &ldquo;With this integration, the import process will be much easier.&rdquo;</p>\n\n\n\n<p>Block patterns are a planned feature that is under <a href=\"https://github.com/WordPress/gutenberg/issues/17335\">active development</a> in the Gutenberg plugin and will eventually make its way into core WordPress. Patterns are predefined sets of blocks.  They will allow users to quickly create more advanced layouts while also teaching what specific blocks do.  The idea is to have a set of patterns with common layouts that people see around the web.  </p>\n\n\n\n<p>Carandang said he is actively checking the progress of the Block Patterns feature.  He is eager to see the feature to come to fruition, which carries with it the possibility of more widespread use of the blocks available from his new community.</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, 10 Dec 2019 19:51:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:18;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"BuddyPress: BuddyPress 5.1.0 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=309343\";s:7:\"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:48:\"https://buddypress.org/2019/12/buddypress-5-1-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1258:\"<p>Immediately available is <a href=\"https://downloads.wordpress.org/plugin/buddypress.5.1.0.zip\">BuddyPress 5.1.0</a>. This maintenance release fixes 8 bugs related to the 5.0.0 release, and is a recommended upgrade for all BuddyPress installations.</p>\n\n\n\n<p>For details on the changes, please read the <a href=\"https://codex.buddypress.org/releases/version-5-1-0/\">5.1.0 release notes</a>.</p>\n\n\n\n<p>Update to BuddyPress 5.1.0 today in your WordPress Dashboard, or by&nbsp;<a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</a>.</p>\n\n\n\n<h2>Many thanks to 5.1.0 contributors <span class=\"dashicons dashicons-heart\"></span></h2>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/szepeviktor/\">szepe.viktor</a>, <a href=\"https://profiles.wordpress.org/jarretc/\">JarretC</a>, <a href=\"https://profiles.wordpress.org/espellcaste/\">Renato Alves (espellcaste)</a>, <a href=\"https://profiles.wordpress.org/dcavins/\">David Cavins (dcavins)</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone Gorges (boonebgorges)</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby (johnjamesjacoby)</a> &amp; <a href=\"https://profiles.wordpress.org/imath/\">Mathieu Viet (imath)</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:\"Mon, 09 Dec 2019 21:45:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:19;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"WPTavern: Progress on WordPress’ 2019 Projects Sets 2020 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:29:\"https://wptavern.com/?p=95761\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/progress-on-wordpress-2019-projects-sets-2020-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:8566:\"<p>Josepha Haden, Executive Director of WordPress, published an <a href=\"https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/\">update of WordPress&rsquo; goals in 2019</a>.  The focus for WordPress over the past year has been on nine primary projects.  Of the nine projects, WordPress only managed to ship two in 2019.  This means that the focus in 2020 will be much the same as the community continues building on the progress it has made toward the existing projects.</p>\n\n\n\n<p>Currently, there are three <a href=\"https://wordpress.org/about/roadmap/\">planned major releases</a> for WordPress in 2020:</p>\n\n\n\n<ul><li>Version 5.4 &ndash; March 2020</li><li>Version 5.5 &ndash; August 2020</li><li>Version 5.6 &ndash; December 2020</li></ul>\n\n\n\n<p>Each of those dates are subject to change.  We should also get more specific dates as each release draws near.  The various projects for 2020 should land in each release.</p>\n\n\n\n<p>Matt Mullenweg, co-founder of WordPress, initially laid out the 2019 plans in his <a href=\"https://wptavern.com/state-of-the-word-2018-wordpress-embraces-the-block-editor\">2018 State of the Word</a> address and <a href=\"https://make.wordpress.org/core/2018/12/08/9-priorities-for-2019/\">listed the projects</a> on the Make Core blog.  The big takeaway is that 2019 was supposed to be the year that we got closer to full-site customization (Phase 2 of the Gutenberg project).  While developers have made huge strides in making that a reality, much of the project is still in its infancy.</p>\n\n\n\n<h2>Projects That Shipped in 2019</h2>\n\n\n\n<p>All existing core WordPress widgets now exist as blocks.  Rather than being limited to placing widgets where the theme decides, users can now put widgets in posts, pages, or any other content area via the block editor.  As the project continues to move toward full-site editing, users will eventually have the ability to place these widgets and other blocks nearly anywhere.</p>\n\n\n\n<p>The site health project was merged into core.  It features a screen that provides information about the site&rsquo;s health to site owners.  It also has a fatal-error detection script that emails site owners when plugin and theme issues are found.</p>\n\n\n\n<h2>Projects to Expect in 2020</h2>\n\n\n\n<p>Most of the remaining projects that did not quite make the cut for release in 2019 have still made progress during the year.  The following is a breakdown of what projects to expect in the coming year.</p>\n\n\n\n<h3>Navigation Menu Block</h3>\n\n\n\n<img />Navigation block in the block editor.\n\n\n\n<p>Currently, the navigation block&rsquo;s target is to ship with WordPress 5.4.  This is a likely reality because it is now out of the experimental stage and is available for beta testing in <a href=\"https://wptavern.com/gutenberg-7-0-launches-stable-navigation-block-post-blocks-and-template-parts\">Gutenberg 7.0</a>.  The development team worked on this block for several releases and now have something stable enough for user testing.</p>\n\n\n\n<p>This block is a major piece of the site-customization puzzle.  In the long term, users will need an easy-to-use block for handling navigation menus across their site.</p>\n\n\n\n<h3>Custom Block-Aware Content Areas for Themes</h3>\n\n\n\n<p>Phase 1 of the Gutenberg project brought the block editor to post content.  A large part of Phase 2 is <a href=\"https://github.com/WordPress/gutenberg/issues/13489\">breaking outside of post content</a> and allowing users to add blocks in more areas.  It is unclear exactly what that will look like in the long run.  Themes should be able to register additional block-aware areas.</p>\n\n\n\n<p>The target release for this feature is set to WordPress 5.5, but it is too early to guess whether that is a realistic target.  It is a tough issue to solve because it will need to coincide with decisions on <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">theme block templates</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/18029\">saving multiple entities</a>, and <a href=\"https://github.com/WordPress/gutenberg/issues/13113\">full-site customization</a> in general.  It is not a feature that can be rushed because it will have far-reaching consequences to how WordPress works for years into the future.</p>\n\n\n\n<h3>Widget Areas to Support Blocks</h3>\n\n\n\n<img />Experimental widget areas feature in Gutenberg.\n\n\n\n<p>The current plan is to allow widget areas (sidebars) to support blocks alongside widgets.  The Gutenberg plugin has an experimental widget areas option for enabling an early version of this feature, which has a target release of WordPress 5.5.</p>\n\n\n\n<p>There are two aspects to making this feature a reality.  The first is making it work on the <a href=\"https://github.com/WordPress/gutenberg/issues/13204\">widgets admin screen</a>.  The second is making it work in the <a href=\"https://github.com/WordPress/gutenberg/issues/13205\">customizer</a>, an area where users can also manage widgets.</p>\n\n\n\n<p>At the moment, it feels like the sidebar concept should be deprecated.  The experimental feature works by allowing users to add blocks to a sidebar, which are converted into one big &ldquo;block area&rdquo; widget on output.  If WordPress is &ldquo;all in&rdquo; on the block paradigm, energy would be better spent focusing on allowing themes to build custom block areas and letting the official Sidebar API die a slow death.  Mixing an old concept with a new one feels clunky at best.  It&rsquo;s time to move on and soft-deprecate sidebars and widgets until most themes no longer support them.</p>\n\n\n\n<h3>Block Directory Search and Install</h3>\n\n\n\n<img />Experimental block directory search in Gutenberg plugin.\n\n\n\n<p>Eventually, all WordPress users will be able to search for a block via the block inserter.  If the block exists, they can insert it into the block area.  If not, the inserter will allow users to discover new blocks from the <a href=\"https://wordpress.org/plugins/browse/block/\">block directory</a>.  The installation, activation, and insertion of the new block should be seamless.</p>\n\n\n\n<p>The target release for this feature is set for WordPress 5.5, which should be possible (if not earlier) based on how well the feature currently works in the Gutenberg plugin.  It is not perfect yet and has broken more than a few of my posts when working with installed blocks.  There are still <a href=\"https://github.com/WordPress/gutenberg/issues/17440\">several open issues</a> that need to be addressed.</p>\n\n\n\n<p>Plugin authors who are looking to get ahead of the game can submit block plugins by following the <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">block plugin guidelines</a>.</p>\n\n\n\n<h3>Automatic Plugin, Theme, and Major Core Updates</h3>\n\n\n\n<p>After years of extensive testing and using automatic updates for minor WordPress releases, it feels like we should already have auto-updates on everything at this point.  Having to keep up with plugin and theme updates can be a pain for some site owners.  With enough plugins, it is not out of the realm of possibility to have one or more plugins to update daily.</p>\n\n\n\n<p>Some hosting solutions and Jetpack have mitigated this issue for many users by offering automatic plugin updates, but this is a long overdue core feature that should be a high priority.  No target release was given for auto-updates on themes/plugins or major core releases.  Let&rsquo;s hope the feature does not get put on the back burner for another year.</p>\n\n\n\n<h3>Tackling Over 6,500 Trac Issues</h3>\n\n\n\n<p>With the Gutenberg plugin getting much of the attention these days, it is easy to forget that there are <a href=\"https://core.trac.wordpress.org/\">thousands of tickets</a> awaiting patches, reviews, and decisions on Trac.  I have long been a champion of using one major release of WordPress to simply fix existing bugs while adding no new features.</p>\n\n\n\n<p>Jonathan Desrosiers has written an <a href=\"https://jonathandesrosiers.com/2019/06/wordpress-triage-team-3-month-reflection/\">extensive post</a> that covers much of the work the Triage Team has done earlier this year.</p>\n\n\n\n<p>Triaging is not something that ever truly reaches a conclusion.  It is an ongoing process that must continue throughout the life of a project.  People who are interested in being involved with the Triage Team can find more information on the <a href=\"https://make.wordpress.org/core/2019/03/01/introducing-the-wordpress-triage-team/\">Triage Team announcement post</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 09 Dec 2019 21:25:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:11:\"\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"HeroPress: Video from DoSummitGood\";s:7:\"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:29:\"https://heropress.com/?p=3027\";s:7:\"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:113:\"https://heropress.com/video-from-dosummitgood/#utm_source=rss&utm_medium=rss&utm_campaign=video-from-dosummitgood\";s: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:2637:\"<img width=\"960\" height=\"503\" src=\"https://s20094.pcdn.co/wp-content/uploads/2019/12/DoSummitGood-mountain_optimised-1024x536.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"\" />\n<p>I recently took part in DoSummitGood, an online conference for people and organizations working to Do Good in the WordPress community.</p>\n\n\n\n<p>The organizers managed to get recordings of all the talks on YouTube the very next day, which is pretty impressive.</p>\n\n\n\n<p>In this talk I tell a lot more about what was going on in my personal life while spinning up HeroPress, so I recommend checking it out even if you&#8217;ve already heard the story.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"jetpack-video-wrapper\"></div>\n</div>\n<div class=\"rtsocial-container rtsocial-container-align-right rtsocial-horizontal\"><div class=\"rtsocial-twitter-horizontal\"><div class=\"rtsocial-twitter-horizontal-button\"><a title=\"Tweet: Video from DoSummitGood\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=Video%20from%20DoSummitGood&via=heropress&url=https%3A%2F%2Fheropress.com%2Fvideo-from-dosummitgood%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: Video from DoSummitGood\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fvideo-from-dosummitgood%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-linkedin-horizontal\"><div class=\"rtsocial-linkedin-horizontal-button\"><a class=\"rtsocial-linkedin-button\" href=\"https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fvideo-from-dosummitgood%2F&title=Video+from+DoSummitGood\" rel=\"nofollow\" target=\"_blank\" title=\"Share: Video from DoSummitGood\"></a></div></div><div class=\"rtsocial-pinterest-horizontal\"><div class=\"rtsocial-pinterest-horizontal-button\"><a class=\"rtsocial-pinterest-button\" href=\"https://pinterest.com/pin/create/button/?url=https://heropress.com/video-from-dosummitgood/&media=https://heropress.com/wp-content/uploads/2019/12/DoSummitGood-mountain_optimised-150x150.jpg&description=Video from DoSummitGood\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: Video from DoSummitGood\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/video-from-dosummitgood/\" title=\"Video from DoSummitGood\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/video-from-dosummitgood/\">Video from DoSummitGood</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:\"Mon, 09 Dec 2019 16: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:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WordPress.org blog: People of WordPress: Jill Binder\";s:7:\"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=8192\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/12/people-of-wordpress-jill-binder/\";s: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:10930:\"<p><em>You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.</em></p>\n\n\n\n<h2><strong>Meet Jill Binder</strong></h2>\n\n\n\n<p>Jill Binder never meant to become an activist. She insists it was an accident.</p>\n\n\n\n<p>Despite that, Jill has led the Diversity Outreach Speaker Training working group in the WordPress Community team since 2017. This group is dedicated to increasing the number of women and other underrepresented groups who are stepping up to become speakers at WordPress Meetups, WordCamps, and events.&nbsp;</p>\n\n\n\n<h2><strong>Jill’s back story</strong></h2>\n\n\n\n<h3><strong>Internship</strong></h3>\n\n\n\n<p>Jill’s WordPress story begins in 2011, in Vancouver, Canada.&nbsp;Jill secured an internship for her college program, working on a higher education website that was built in WordPress.&nbsp;As a thank you, her practicum advisor bought Jill a ticket to WordCamp Vancouver 2011: Developer’s Edition. After that Jill began freelancing&nbsp; with WordPress as a Solopreneur.&nbsp;</p>\n\n\n\n<h3><strong>First steps in the WordPress community</strong></h3>\n\n\n\n<p>The following year her internship advisor, who had become a client, was creating the first ever BuddyCamp for BuddyPress. He asked Jill to be on his organizing team. At that event she also moderated a panel that had Matt Mullenweg on it. Then, Jill was invited to be on the core organizing team for WordCamp Vancouver.</p>\n\n\n\n<p>Part of this role meant reviewing and selecting speakers. From 40 speaker applications that could be a fit the team had to pick only 14 to speak.</p>\n\n\n\n<h2><strong>The diversity challenge when selecting speakers</strong></h2>\n\n\n\n<p>For anyone who has organized a conference, you know that speaker selection is hard. Of the 40 applications, 7 were from women, and the lead organizer selected 6 of those to be included in the speaker line up.</p>\n\n\n\n<p>At this point Jill wasn’t aware that very few women apply to speak at tech conferences and suggested selection should be made on the best fit for the conference. The team shared that not only did they feel the pitches were good and fit the conference, but they also needed to be accepted or the Organizers would be criticized for a lack of diversity.</p>\n\n\n\n<p>Selecting women for fear of criticism is embarrassing to admit, but that’s how people felt in 2013.</p>\n\n\n\n<p>By the time the event happened, though, the number of women speakers dropped to 4. And with an additional track being added, the number of speakers overall was up to 28. Only 1 speaker in 7 was a woman (or 14%) and attendees did ask questions and even blogged about the lack of representation.</p>\n\n\n\n<h2><strong>What keeps women from applying?</strong></h2>\n\n\n\n<p>Later that year at&nbsp; WordCamp San Francisco—the biggest WordCamp at the time (before there was a WordCamp US)—Jill took the opportunity to chat with other organizers about her experience. She found out that many organizers had trouble getting enough women to present.</p>\n\n\n\n<p>Surprisingly Vancouver had a high number of women applicants in comparison to others, and the consensus was more would be accepted&nbsp; if only more would apply.</p>\n\n\n\n<p>Jill decided that she&nbsp; needed to know why this was happening? Why weren’t there more women applying? She started researching, reading, and talking to people.</p>\n\n\n\n<p>Though this issue is complex, two things came up over and over:</p>\n\n\n\n<ul><li>“What would I talk about?”</li><li>“I’m not an expert on anything. I don’t know enough about anything to give a talk on it.”</li></ul>\n\n\n\n<h2><strong>A first workshop with encouraging results</strong></h2>\n\n\n\n<p>Then Jill had an idea. She brought up the issue at an event and someone suggested that they should get women together in a room and brainstorm speaker topics.</p>\n\n\n\n<p>So Jill became the lead of a small group creating a workshop in Vancouver: the talented Vanessa Chu, Kate Moore Hermes, and Mandi Wise. In one of the exercises that they created, participants were invited to brainstorm ideas—this proved that they had literally a hundred topic ideas and the biggest problem then became picking just one!</p>\n\n\n\n<p>In the first workshop, they focussed on:</p>\n\n\n\n<ul><li>Why it matters that women (<em>added later: diverse groups</em>) are in the front of the room</li><li>The myths of what it takes to be the speaker at the front of the room (aka beating impostor syndrome)</li><li>Different presentation formats, especially story-telling</li><li>Finding and refining a topic</li><li>Tips to become a better speaker</li><li>Leveling up by speaking in front of the group throughout the afternoon</li></ul>\n\n\n\n<img src=\"https://i2.wp.com/wordpress.org/news/files/2019/12/image-2.png?w=632&ssl=1\" alt=\"women gathering to discussion presentation topics\" class=\"wp-image-8195\" />Vancouver Workshop 2014\n\n\n\n<h2><strong>Leading to workshops across North America and then the world</strong></h2>\n\n\n\n<p>Other cities across North America heard about the workshop and started hosting them, adding their own material.</p>\n\n\n\n<p>Many women who initially joined her workshop wanted help getting even better at public speaking. So Jill&#8217;s Vancouver team added in some material created from the other cities and a bit more of their own. Such as:</p>\n\n\n\n<ul><li>Coming up with a great title</li><li>Writing a pitch that is more likely to get accepted</li><li>Writing a bio</li><li>Creating an outline</li></ul>\n\n\n\n<p>At WordCamp Vancouver 2014—only one year since Jill started—there were 50% women speakers and 3 times the number of women applicants! Not only that, but this WordCamp was a Developer’s Edition, where it’s more challenging to find women developers in general, let alone those who will step up to speak.</p>\n\n\n\n<h3><strong>More work is needed!</strong></h3>\n\n\n\n<p>Impressive as those results were, the reason Jill is so passionate about this work is because of what happened next:</p>\n\n\n\n<ul><li>Some of the women who attended the workshop stepped up to be leaders in the community and created new content for other women.</li><li>A handful of others became WordCamp organizers. One year Vancouver had an almost all-female organizing team – 5 out of 6!</li><li>It also influenced local businesses. One local business owner loved what one of the women speakers said so much that he hired her immediately. She was the first woman developer on the team, and soon after she became the Senior Developer.</li></ul>\n\n\n\n<h2><strong>Diversity touches on many levels</strong></h2>\n\n\n\n<p>Jill has seen time and again what happens when different people speak at the front of the room. More people feel welcome in the community. The speakers and the new community members bring new ideas and new passions that help to make the technology we are creating more inclusive. And together we generate new ideas that benefit everyone.</p>\n\n\n\n<p>This workshop was so successful, with typical results of going from 10% to 40-60% women speakers at WordCamps, that the WordPress Global Community Team asked Jill to promote it and train it for women and all diverse groups around the world. In late 2017, Jill started leading the Diverse Speaker Training group (<a href=\"https://make.wordpress.org/community/tag/wpdiversity/\">#wpdiversity</a>).</p>\n\n\n\n<p>Dozens of community members across the world have now been trained to lead the workshop. With now dozens of workshops worldwide, for WordPress and other open source software projects as well, there is an increase in speaker diversity.&nbsp;</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?fit=632%2C474&ssl=1\" alt=\"Diverse Speaker Training group \" class=\"wp-image-8196\" />WordCamp US 2019\n\n\n\n<p>As a result of the success, Jill is now sponsored to continue the program. The first sponsor is Automattic. She’s proud of how the diversity represented on the stage adds value not only to the brand but also in the long-term will lead to the creation of a better product. She’s inspired by seeing the communities change as a result of the new voices and new ideas at the WordPress events.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p><em>Jill’s leadership in the development and growth of the Diversity Outreach Speaker Training initiative has had a positive, measurable impact on WordPress community events worldwide. When WordPress events are more diverse, the WordPress project gets more diverse — which makes WordPress better for more people.”</em></p><cite><em> Andrea Middleton, Community organizer on the WordPress open source project</em></cite></blockquote>\n\n\n\n<h3><strong>Resources:</strong></h3>\n\n\n\n<ul><li>The Workshop: <a href=\"http://diversespeakers.info/\">http://diversespeakers.info/</a></li><li>More information: <a href=\"https://tiny.cc/wpdiversity\">https://tiny.cc/wpdiversity</a></li><li><a href=\"https://make.wordpress.org/community/handbook/wordcamp-organizer/planning-details/speakers/building-a-diverse-speaker-roster/\">How to build a diverse speaker roster</a></li><li><a href=\"https://make.wordpress.org/community/2017/11/13/call-for-volunteers-diversity-outreach-speaker-training/\">Diversity Outreach Speaker Training Team</a></li></ul>\n\n\n\n<h2><strong>Contributors</strong></h2>\n\n\n\n<p>Alison Rothwell (<a href=\"https://profiles.wordpress.org/wpfiddlybits/\">@wpfiddlybits</a>), Yvette Sonneveld (<a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld</a>), Josepha Haden (<a href=\"https://profiles.wordpress.org/chanthaboune/\">@chanthaboune</a>), Topher DeRosia (<a href=\"https://profiles.wordpress.org/topher1kenobe/\">@topher1kenobe</a>)</p>\n\n\n\n<div class=\"wp-block-image\"><img src=\"https://lh6.googleusercontent.com/fq6qus5qmviDZaznrQnW-4wcbSs6NSrqeqEEGnPjgi2WJrVevNm4Em4KsP-VVH_0kMgWuNtW7mm_V9-hKtrrJFohRi6KrUXAoLHjrymChCltMr9fuh4dBIu_0SqNPts0MZgcvh_W\" alt=\"\" width=\"153\" height=\"115\" /></div>\n\n\n\n<p><em>This post is based on an article originally published on HeroPress.com, a community initiative created by </em><a href=\"https://profiles.wordpress.org/topher1kenobe/\"><em>Topher DeRosia</em></a><em>. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.</em></p>\n\n\n\n<p></p>\n\n\n\n<p><em>Meet more WordPress community members over at </em><a href=\"https://heropress.com/\"><em>HeroPress.com</em></a><em>!</em></p>\n\n\n\n<p><em><strong>Correction: December 7, 2019</strong><br />The original article mentioned the team Jill lead, but did not mention the team members who joined her. Those have been added. Apologies to Vanessa, Kate, and Mandi. <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f642.png\" alt=\"?\" class=\"wp-smiley\" /> </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:\"Fri, 06 Dec 2019 23:27: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:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"WPTavern: Zero BS CRM 3.0 Improves UI, Changes Database Structure, and Becomes More Extendable\";s:7:\"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:29:\"https://wptavern.com/?p=95739\";s:7:\"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:103:\"https://wptavern.com/zero-bs-crm-3-0-improves-ui-changes-database-structure-and-becomes-more-extendable\";s: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:6294:\"<img />\n\n\n\n<p>The team behind Zero BS CRM <a href=\"https://zerobscrm.com/road-to-v3/\">launched version 3.0</a> of their WordPress plugin today.  This is the first major release since the plugin was <a href=\"https://wptavern.com/automattic-acquires-zero-bs-crm-considers-rebranding-it-as-jetpack-crm\">acquired by Automattic in August</a>.  The updated plugin uses custom database tables, opens the plugin for more extensions, and has a more consistent UI than previous versions.</p>\n\n\n\n<p>CRM is an acronym for &ldquo;customer relationship management.&rdquo;  CRM systems allow businesses to manage their customer relationships through an interface.  How CRM systems work can vary greatly, depending on the software used.  In general, the goal is to help manage contacts, sales, and productivity.</p>\n\n\n\n<p>Zero BS CRM was co-created by Mike Stott and Woody Hayday.  Despite a low number of plugin users (around 1,000 at acquisition), Automattic acquired the plugin based on the strength of the product.  Currently, Stott and Hayday are the primary developers on the plugin and maintain more than 30 commercial extensions for it.</p>\n\n\n\n<p>Many CRM solutions are SaaS products, such as Salesforce CRM and HubSpot CRM.  &ldquo;The main benefit of ZBS CRM over online SaaS type solutions is it sits in your WP admin dashboard, and you own your own data,&rdquo; said Stott.</p>\n\n\n\n<p>Version 3.0 of the plugin improves in several key areas.  One major change is the switch to custom database tables rather than pigeon-holing everything into a custom post type.  This change should speed up accessing data such as contacts and transactions in large databases.</p>\n\n\n\n<p>Users should benefit from a much improved and consistent UI from previous versions.  Zero BS CRM does not strictly follow the core WordPress admin UI.  &ldquo;When looking at ZBS CRM and how to tie in all our menu items into the WordPress UI &ndash; it wasn&rsquo;t easy,&rdquo; said Stott.  &ldquo;We settled on using a UI framework with our own top menu, and a natural follow-on for that was to draw our list views using that same UI and button systems. Whether we move this back or not depends on feedback from our users &mdash; we get a lot of positive feedback on how easy it is to navigate around and wouldn&rsquo;t want to change something that&rsquo;s been getting good feedback.&rdquo;</p>\n\n\n\n<img />Contact management screen in the Zero BS CRM plugin.\n\n\n\n<p>Moving to custom tables over custom post types has also helped improve elements of the UI.  Stott said a huge advantage is not having third-party plugins accidentally adding themselves to the plugin&rsquo;s admin pages, such as having unnecessary SEO options on contact records.</p>\n\n\n\n<p>Another big change in 3.0 was building out a more extendable foundation for the plugin.  This will open up custom CRM objects in the future.  For example, plugin users could manage resources such as &ldquo;properties&rdquo; or &ldquo;campuses&rdquo; along with customer contact data.  This update creates more potential for industry-specific extensions.</p>\n\n\n\n<p>&ldquo;It really opens the door for more extendibility in the future,&rdquo; said Stott, &ldquo;and through an improved API in 2020 will allow for us to do more work across platforms and open up our CRM tools to more people.&rdquo;</p>\n\n\n\n<p>The Zero BS CRM plugin remains free and is <a href=\"https://wordpress.org/plugins/zero-bs-crm/\">available in the WordPress plugin repository</a>.  The primary source of income comes from its extension bundles, which are priced monthly and billed yearly.  The website currently offers freelancer ($11/month), entrepreneur ($17/month), and elite ($30/month) pricing options.  It also has a reseller plan available.</p>\n\n\n\n<h2>The Move to Automattic</h2>\n\n\n\n<p>When the plugin was first acquired, there was an initial idea to rebrand as &ldquo;Jetpack CRM.&rdquo;  However, they have maintained the Zero BS CRM branding with an acronym instead of the direct expletive for &ldquo;BS.&rdquo;  A rebrand may still be on the table in 2020 or beyond.</p>\n\n\n\n<p>&ldquo;We&rsquo;ve been gathering user feedback and sentiment following the minor changes to ZBS CRM and the initial reactions if we were to rename as Jetpack CRM,&rdquo; said Stott.  &ldquo;Since the shorter name, there&rsquo;s been less objection or negative feelings, which puts less pressure on a big rebrand project, but it&rsquo;s certainly something we&rsquo;ll be coming back to.&rdquo;</p>\n\n\n\n<p>Stott said the primary focus since the acquisition has been less on branding and more on delivering 3.0 to the existing customer base.</p>\n\n\n\n<p>The acquisition by Automattic has helped with how their two-person team works.  &ldquo;The main thing is being able to lean on the amazing team and people throughout Automattic,&rdquo; said Stott.  &ldquo;In the past, we&rsquo;d only have Woody and my input, now we can reach out to experts in design, marketing, plus much more, and bounce our ideas around a vast pool of experience.&rdquo;</p>\n\n\n\n<p>He explained that the additional support resources of Automattic&rsquo;s Happiness Engineers means that he and his partner can focus more on engineering and growing the product and team.</p>\n\n\n\n<p>The acquisition of Zero BS CRM came during a busy year for Automattic.  With major moves such as <a href=\"https://wptavern.com/automattic-acquires-tumblr-plans-to-rebuild-the-backend-powered-by-wordpress\">acquiring Tumblr</a> and the <a href=\"https://wptavern.com/automattic-raises-300m-in-series-d-investment-round-valuation-jumps-to-3-billion\">Salesforce investment</a>, this small plugin has mostly flown under the radar in comparison.  Stott and Hayday have big plans for 2020.  They would like to grow the engineering team and explore bringing their tools to more WordPress.com users.</p>\n\n\n\n<p>The plugin&rsquo;s growth has remained stable since the acquisition, according to Stott.  &ldquo;The announcement brought us some additional customers who saw the backing from Automattic as strong advocacy for the plugin over other solutions in the WordPress space, so they made the decision to join us,&rdquo; he said.  The plugin has doubled its active install count and now serves over 2,000 users.  The team expects to continue growing in the coming months.</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, 06 Dec 2019 20:43:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:23;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WPTavern: Gutenberg: One Year Later\";s:7:\"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:29:\"https://wptavern.com/?p=95698\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"https://wptavern.com/gutenberg-one-year-later\";s: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:9610:\"<p>As we quickly head into the final weeks of 2019, we also pass the first anniversary of WordPress 5.0 and, subsequently, Gutenberg coming headlong into our lives. </p>\n\n\n\n<p>Love it or hate it, Gutenberg is here to stay.  If you had asked my thoughts on it last December, I would have probably sided with a large portion of other WordPress users.</p>\n\n\n\n<p><em>What are you doing?</em></p>\n\n\n\n<p><em>WordPress is fine, leave it alone!</em></p>\n\n\n\n<p><em>Stop forcing me to use this!</em></p>\n\n\n\n<p>Here we are, twelve months later, and you know what? I LOVE IT.  And, I am not alone.</p>\n\n\n\n<p>When it comes to writing content, I cannot <em>imagine</em> using the Classic Editor anymore. Sure, for a few paragraphs, the Classic Editor is fine.  However, when you need to make a 4,000+ word post, Gutenberg and the new block system make things a lot easier.</p>\n\n\n\n<p>Yes, the UI is a struggle for someone brand new to WordPress.  We have all heard the &ldquo;<em>Wait, I thought you said this was like Word?</em>&rdquo; line.  A good onboarding process would tackle that going forward.  For the rest of us, if you have not adopted Gutenberg yet, you should take another look at it.</p>\n\n\n\n<h2>The Need for a New Editor</h2>\n\n\n\n<p>Let&rsquo;s be honest.  The Classic Editor was great for short posts, a couple of headlines and paragraphs, job done.  But, how often were you going into the Text tab to remove an extra line break, fix a shortcode, or cut and paste a section to somewhere else in the post?&nbsp; At best, it was a struggle.  Often, it was excruciating to get your post <em>just right</em> before publishing.</p>\n\n\n\n<p>Not only will I <em>not</em> miss this, but I am pleased that new users will not be exposed to it anymore either.</p>\n\n\n\n<img />Classic Editor &ndash; Text tab in action\n\n\n\n<p>When I first heard of Gutenberg &mdash; before it was released in WordPress 5.0 &mdash; I installed the plugin and was immediately confused and slightly bewildered at the options. I wondered how I would edit in the future. </p>\n\n\n\n<p>I, among many others, probably gave out the same noises as when Facebook and Twitter reveal a huge overhaul of their UI, agreeing with everyone that things would never be the same again. <em>This was a mistake. </em>Of course, I was both right and wrong at the same time.  I just didn&rsquo;t know it.  Editing would not be the same again.  Instead, it would be a lot better (with some adjustment).</p>\n\n\n\n<p>I also know that many people will not agree with me and do not like the way Gutenberg looks or behaves to this day. But, if you give it some time and understand how it can make your life easier, it will do just that.</p>\n\n\n\n<p>First, take the time to work out the difference between Blocks and Document. On the left you have all the blocks for your post or page, inserting them in merrily as you go. On the right, the Document panel controls everything else, handily changing when you need to fine-tune a block.</p>\n\n\n\n<img />Gutenberg block editor in action\n\n\n\n<p>One of the most common complaints I have read is people struggling with the toolbar that appears as you hover over each block. There is a simple solution to this, and when it is enabled, the majority of people suddenly start to love it! Make sure you set the view to &ldquo;Top Toolbar&rdquo; in the Gutenberg options. Now you have a distraction and clutter-free editing environment to work with.</p>\n\n\n\n<h2>Gutenberg vs. Page Builders</h2>\n\n\n\n<p>Gutenberg is not a page builder, and it is a common argument thrown out by people on why they refuse to use it. They are right, it is not a replacement for the likes of Elementor or Beaver Builder.  If you remove the comparison to page builders from your mind, you will find adapting to it is much easier.</p>\n\n\n\n<p>My peers and I regularly chat about Gutenberg and agree it is already great for writing.  The post creation process is a breath of fresh air.  Others have great stories from their clients about being able to produce content and edit it with ease, and the number of editor-related support requests is down, which can only be a good thing.</p>\n\n\n\n<p>However, many of us would not use it for designing pages. Instead, we still prefer to use one of the many page builders for that complete control.</p>\n\n\n\n<p>Gutenberg Phase 2 will allow editing of the site to areas outside of the main content (e.g., headers, footers, sidebars) and will creep further into the page builder category, which means we will have a strange blend of Gutenberg and page builders living side by side on many sites soon.</p>\n\n\n\n<p>Will it remove the complete need for themes? Who knows? I suspect we will have people further divided into opposing camps going forward, but what a great opportunity for us to collectively work on for a better overall experience in the end.</p>\n\n\n\n<h2>By the Numbers</h2>\n\n\n\n<p>Let us take a quick look at Gutenberg and its penetration to date.</p>\n\n\n\n<p>Currently, 63.8% of all WordPress installs are running 5.x onward according to WordPress.org, which means Gutenberg is available natively on nearly two-thirds of all WordPress installs.</p>\n\n\n\n<p>But, it is not all red roses when it comes to adoption. </p>\n\n\n\n<p>The Classic Editor plugin has over 5 million active installs (and a rather biased 723 five-star reviews, such as &ldquo;Keep this forever&rdquo; and &ldquo;Never going to give it up!&rdquo;). It is also currently in the top five of the most popular plugins. </p>\n\n\n\n<p>Is this the backlash against Gutenberg or incompatibility with older themes forcing users to use the Classic Editor for now? At a guess, a good majority is probably the latter combined with some diehards. </p>\n\n\n\n<p>But, look at the graph below from the <a rel=\"noreferrer noopener\" class=\"ek-link\" href=\"https://wordpress.org/plugins/classic-editor/\" target=\"_blank\">Classic Editor plugin page</a>.</p>\n\n\n\n<img />\n\n\n\n<p>Growth is declining. That is not a movement of people who continue to install Classic Editor on new installs and refuse to adapt.</p>\n\n\n\n<p>Classic Editor adoption will likely continue falling, and perhaps the original date of it being supported until 2022 isn&rsquo;t that far-fetched after all (note: they have said they will continue to support it longer if needed).</p>\n\n\n\n<p>On the flip-side, the Gutenberg plugin has 200,000 active installs and a whopping two-thirds of reviews (2,003) are a paltry one star. However, many are merely unhelpful complaints (e.g., &ldquo;This is junk&rdquo; and &ldquo;Destroy it&rdquo;).  They do not tell the true story to novices.</p>\n\n\n\n<p>As you can see from the graph below for the Gutenberg plugin, active install growth is up and continues to climb.  It is not at the same pace as the decline with the Classic Editor, but that is probably because it is bundled with WordPress now.</p>\n\n\n\n<img />\n\n\n\n<p>One thing people seem to forget is Gutenberg is a plugin in and of itself.  It is updated frequently, whereas the majority of users only see changes to it when there is a WordPress core update.</p>\n\n\n\n<p>If you can see past the fields of one-star reviews and install the plugin, you will be rewarded with more frequent updates to the experience. </p>\n\n\n\n<p>For example, version 7.0 recently added in the Navigation block as stable, allowing users to quickly create a menu of links. Don&rsquo;t get me wrong; this does require theme integration for it to work, but you can get a better idea of where it is heading on a more frequent basis this way (7.0 is expected to ship with WordPress 5.4 in March/April 2020).</p>\n\n\n\n<h2>Block Party</h2>\n\n\n\n<p>Compatibility with Gutenberg continues at a quick pace.  With over 21 pages of block-enabled plugins available on WordPress.org, pretty much all the popular plugins have solutions in place.  A fair amount of plugin updates these days are also adding new and enhanced blocks as standard.</p>\n\n\n\n<p>If those are not enough for you, we also now have a new breed of block-specific plugins. There is a growing trend of plugins devoted to purely enhancing the style and number of blocks you can add to your site.</p>\n\n\n\n<p>Popular Gutenberg-focused plugins such as <a class=\"ek-link\" href=\"https://wpstackable.com\">Stackable</a> and <a class=\"ek-link\" href=\"https://editorskit.com\">EditorsKit</a> add further styling and editing abilities, bringing you another step closer to full-page design and enhancing your content.</p>\n\n\n\n<img />EditorsKit &ndash; a purely Gutenberg plugin.\n\n\n\n<p>Because no one knows how far Gutenberg will go and which toes it will step on, block plugins may have a fight on their hands in the future.  At the pace they are being released and updated, it is a good sign of a committed global collective who not only believe in the future of blocks but is excited about it too.</p>\n\n\n\n<h2>What Does the Future Hold?</h2>\n\n\n\n<p>Gutenberg is here to stay, and I don&rsquo;t think any of us have ever denied that. It is probably not an issue for anyone who started using WordPress for the first time this year.</p>\n\n\n\n<p>Thankfully, for those already deeply embedded in WordPress, things are getting easier (and I would say more enjoyable) with the growth of the new Gutenberg-specific plugins.</p>\n\n\n\n<p>With the advent of platforms such as Wix and Squarespace, it was obvious that WordPress needed <em>something</em> to make it more user-friendly and Gutenberg is a solid attempt at that. It is still a bit rough around the edges, but the days we look back nostalgically at the Classic Editor are likely numbered.</p>\n\n\n\n<p>How will it look at the end of 2020? Will you still be using the Classic Editor?</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, 05 Dec 2019 17:49: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:12:\"Chris Hughes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"WPTavern: Initial Documentation for Block-Based WordPress Themes Proposed\";s:7:\"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:29:\"https://wptavern.com/?p=95687\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\";s: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:7198:\"<p class=\"has-drop-cap\">In a pull request on the Gutenberg repository yesterday, Riad Benguella <a href=\"https://github.com/WordPress/gutenberg/pull/18890\">created an initial document</a> that outlines how block-based WordPress themes might work.  While the document is merely a starting point for the conversation, it is a set of ideas that will likely forever reshape the WordPress landscape.  It is paradigm-shifting.</p>\n\n\n\n<p>For the first time, theme authors can glimpse what their future holds.  Since the inception of Gutenberg, many have asked for more technical details.  Particularly, they wanted to know whether themes would be reduced to a stylesheet or a stylesheet and a few PHP files.  <em>What would themes look like architecturally?  Would themes exist at all?</em></p>\n\n\n\n<p>The document, while open for changes, makes a strong case about the structure of themes going forward.  It is clear that much forethought has gone into the proposal.  It matches the direction of the experimental site-editing feature in Gutenberg that has already been set in motion.  Even though it is subject to change, there seems to be a finality to the overarching idea.  The writing has long been on the wall.  Now everyone can see the wall.  The missing piece is figuring out how to bring the idea to fruition.</p>\n\n\n\n<h2>What is Full Site Editing?</h2>\n\n\n\n<p>Before understanding how themes of the future might work, you must first understand the direction that Gutenberg is headed.  The end goal for Gutenberg, and eventually WordPress, is for users to have the ability to customize every aspect of their site via the block system.  Currently, the block system primarily handles editing post content.</p>\n\n\n\n<p>To move to full-site editing, every piece of dynamic data about a site must be a block.  For example, a site title block must exist as a placeholder for the site title.  Users should be able to place it anywhere they desire to output the title, such as in the header.</p>\n\n\n\n<p>This has left theme authors with a reasonable question:  If users can move these blocks anywhere, where do themes fit into the picture?</p>\n\n\n\n<p>It is easy to see how themes would become little more than a stylesheet that styles every WordPress block while also handling other necessary styles like typography and vertical rhythm.  Even then, it makes one wonder if themes, at least in how we have come to know them, are necessary at all.</p>\n\n\n\n<h2>The Proposed Theme Structure</h2>\n\n\n\n<p>The proposed structure does not look much different from current WordPress themes.  The big difference is that theme templates would become &ldquo;block templates&rdquo; and &ldquo;block template parts.&rdquo;  These templates would be HTML files rather than PHP files.</p>\n\n\n\n<p>The following is where the structure currently stands.</p>\n\n\n\n<pre class=\"wp-block-code\"><code>theme\n|__ style.css\n|__ functions.php\n|__ block-templates\n    |__ index.html\n    |__ single.html\n    |__ archive.html\n    |__ ...\n|__ block-template-parts\n    |__ header.html\n    |__ footer.html\n    |__ sidebar.html\n    |__ ...</code></pre>\n\n\n\n<p>From a templating perspective, it appears relatively <em>normal</em> for a WordPress theme.  The files simply have a different type and are organized in specific folders.</p>\n\n\n\n<p>However, the difference is how the HTML templates would work.  They would essentially become placeholders for blocks.  Users would also have the ability to edit or completely overwrite individual templates via the WordPress admin.  Because templates are made up of blocks, no code would be necessary on the user&rsquo;s part.  They could simply point and click to insert or remove blocks with their mouse.  </p>\n\n\n\n<p>In other words, block templates within themes would be unique starting points for users to build their sites.</p>\n\n\n\n<p>There are two noteworthy items about the proposed system:  themes are still themes and end-users can become theme builders.</p>\n\n\n\n<h3>The Essence of a Theme Remains the Same</h3>\n\n\n\n<p>When you cut through everything else, WordPress themes have always been HTML and CSS.  The PHP aspect of theming basically mixes PHP function calls (i.e., template tags) within some structured HTML markup.  If you look at most themes going through the official WordPress theme directory, you will find that the underlying markup is mostly the same.</p>\n\n\n\n<p>In the block template system, this idea doesn&rsquo;t change.  If anything, it could simplify the role of theme author by creating a set of standard elements (blocks) that themes output.  If done right, it also creates a standard for class names so that styles can easily be shared across themes and all sorts of similar goodies.</p>\n\n\n\n<h3>Anyone Can Build a Theme</h3>\n\n\n\n<p>The initial outline explains the potential of exporting themes:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Ultimately, any WordPress user with the correct capabilities (example: administrator WordPress role) will be able to access these templates in the WordPress admin, edit them in dedicated views and potentially export the templates as a theme.</p></blockquote>\n\n\n\n<p>This is where the proposed system could revolutionize website building.  Those without the coding skills to create a WordPress theme today could have the tools to contribute something back tomorrow.</p>\n\n\n\n<p>The idea aligns perfectly with the open-source ethos of WordPress.  By giving everyone the ability to export their customizations, it provides an avenue for contributing that we have never had before for non-coders.  <em>A free directory of customized themes created by and for the community, anyone?</em></p>\n\n\n\n<h2>The Design Side of the Equation</h2>\n\n\n\n<p>Block templates are merely the HTML.  Themes will need to stand apart with their CSS.  However, there must be standardization to pull this off.</p>\n\n\n\n<p>Designers will need to shift to a block-based approach when it comes to design.  Some may already be familiar with various &ldquo;component-based&rdquo; systems, which would work much the same way.  Rather than designing from the top-down, theme authors would approach design on a more atomic level by designing each block.</p>\n\n\n\n<p>There are also many unanswered questions about how styles will eventually work.  Currently, there is an open ticket for <a href=\"https://github.com/WordPress/gutenberg/issues/9534\">discussing a style system for blocks</a>.  Much of the discussion is around how to integrate a design system with themes.</p>\n\n\n\n<h2>Join the Discussion</h2>\n\n\n\n<p>It is important to point out that nothing about this proposal is set in stone.  It is a high-level outline of what the future of themes could hold.  However, now is time for input from the community, especially theme authors who may have felt a bit out of the loop in the past.  Now is the time to make your voice heard and to contribute ideas to the discussion.</p>\n\n\n\n<p>The WordPress theme review team also has an <a href=\"https://make.wordpress.org/themes/2019/12/04/questions-about-the-future-of-themes/\">open discussion on the future of themes</a> that goes along with this proposal and whether themes should start taking advantage of experimental Gutenberg features.</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, 04 Dec 2019 20:56:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Black Friday Banner Gone Wrong: Advertising in Free 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:29:\"https://wptavern.com/?p=95661\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wptavern.com/black-friday-banner-gone-wrong-advertising-in-free-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:6514:\"<img />Screenshot of the Yoast Black Friday Ad\n\n\n\n<p>On November 28, millions of people awoke to a Black Friday ad on nearly every page of their WordPress admin, courtesy of the <a href=\"https://wordpress.org/plugins/wordpress-seo/\">Yoast SEO plugin</a>.  That day also coincided with the U.S. Thanksgiving holiday, so it left freelancers and agencies scrambling to address a banner on their clients&rsquo; sites on a day they likely planned to spend with family.  The ad was not limited to users with administrative permissions either, so some site owners were troubled to find users with low-level permissions could see the ad in the WordPress admin.</p>\n\n\n\n<p>The initial code for the banner was <a href=\"https://github.com/Yoast/wordpress-seo/commit/bf13569fa7a25aacac72e8b92c577adcafa9ccc6#diff-9ac66dbc3ac65e9898209f08c006799c\">added on October 25</a>, which made its way into version 12.4 of the Yoast SEO plugin.  The code for the banner ad limited its output between November 28 and December 3 (Cyber Monday).</p>\n\n\n\n<p>After blowback from users, the Yoast team published an updated version of the plugin without the banner.  However, the initial damage was done.  Users began immediately <a href=\"https://wordpress.org/support/plugin/wordpress-seo/reviews/?filter=1\">leaving poor reviews</a> for the plugin.  The 1-star reviews are still coming in, putting the number over 100 in the span of five days.</p>\n\n\n\n<p>&ldquo;That BlackFridayBanner was not the best idea,&rdquo; wrote Marieke van de Rakt, CEO of Yoast, <a href=\"https://twitter.com/MariekeRakt/status/1200077958700044290\">on Twitter</a>. &ldquo;We&rsquo;re truly sorry for the annoyance and difficulties it may have caused. We did not think this through properly. If you want, you can update to a new version of our plugin without that banner.&rdquo;</p>\n\n\n\n<p>The initial decision to place the ad was about growth for Yoast&rsquo;s premium products.  The company has not grown as fast as expected over the past year explained van de Rakt.  They had also seen other plugins use those types of ads, which was a part of the decision to run it.</p>\n\n\n\n<p>&ldquo;Let&rsquo;s be clear,&rdquo; said van de Rakt.  &ldquo;This was a mistake. We just didn&rsquo;t think this one through. It was incredibly stupid. So I can talk about why we made a decision, but I don&rsquo;t want that to be the explanation. The explanation is that we made a mistake.&rdquo;</p>\n\n\n\n<p>The ad was an animated banner, and some users complained that it was difficult to dismiss.  All notices in plugins available through the WordPress plugin directory must be dismissible.  &ldquo;That was a technical mistake,&rdquo; said van de Rakt of the issues with clicking the &ldquo;x&rdquo; icon for dismissal.</p>\n\n\n\n<p>While the team had seen other plugins run similar ads in the past, van de Rakt explained that they didn&rsquo;t take into account how large of a user base Yoast SEO has in comparison to those plugins.  &ldquo;For so many users, we were the first plugin that done this,&rdquo; she said.  &ldquo;They never saw this before in their backend. And they freak out. This was a complete error of judgment.&rdquo;</p>\n\n\n\n<p>Yoast plans to talk more with its plugin&rsquo;s users.  Currently, the team is looking into creating a user-testing panel to prevent similar situations in the future.</p>\n\n\n\n<p>&ldquo;In hindsight, and that&rsquo;s what I feel most bad about, the banner did not fit our values,&rdquo; said van de Rakt.  &ldquo;These kinds of banners are not &lsquo;Yoast.&rsquo; Perhaps, if we state more explicitly what we as Yoast find important and what fits Yoast and what doesn&rsquo;t, a mistake like this will be made less quickly.&rdquo;</p>\n\n\n\n<h2>Making Money with Freemium Products</h2>\n\n\n\n<p>Yoast is a large company within the WordPress space.  It employs 90 people in its primary office in Wijchen, the Netherlands.  It also has an additional 20 employees around the world.  Running a successful business means paying everyone, contributing back to WordPress with its five-for-the-future work, and running charitable programs such as the Yoast Diversity Fund.</p>\n\n\n\n<p>Currently, the Yoast SEO plugin has over 5 million active installs.  According to van de Rakt, only around 2% of the plugin&rsquo;s users also use the company&rsquo;s premium products.  Such a large plugin needs continuous funding to support and maintain.</p>\n\n\n\n<p>Advertising a product or service in an internet culture that is seemingly averse to ads is not always easy.  &ldquo;It&rsquo;s rather hard to find ways to reach our audience, and we also have some principles on how (not) to do that,&rdquo; said van de Rakt.  &ldquo;We like to advertise in a straight-forward way. Tell people what they&rsquo;re buying. Ads are very annoying, but at least they are clear in what they&rsquo;re doing.&rdquo;</p>\n\n\n\n<p>One issue that plugin companies run into is the lack of an official premium marketplace for WordPress.  Currently, companies have to resort to in-admin advertising or similar tactics to push users on an upsell.  Most of Yoast&rsquo;s premium products are sold through banners on the plugin&rsquo;s pages in the WordPress admin.  Such practices do not always go over well with users, particularly when they are using a free product.  One wrong step and it could spell disaster for future growth.  Yoast is large enough to bounce back, but smaller companies may struggle more.</p>\n\n\n\n<p>It is a tough balancing act between providing a valuable free product and making enough of a return to run a successful company.  The Yoast team does not want to lock their popular SEO plugin completely behind a paywall.  &ldquo;Our mission is SEO for everyone,&rdquo; said van de Rakt.  &ldquo;We believe that every idea should have a fair chance in the search results. That means that also without any funds, people should be able to have a good working SEO plugin. Our free plugin is really important to us.&rdquo;</p>\n\n\n\n<p>&ldquo;I had a really bad weekend,&rdquo; said van de Rakt.  &ldquo;I am a people pleaser and I was terribly sad by what happened. But, the discussion about how to handle this is a good one.&rdquo;</p>\n\n\n\n<p>Perhaps some good will come of this incident if there is an open dialogue.  &ldquo;These kinds of things sometimes lead to different &lsquo;rule-sets&rsquo; or policies within WordPress,&rdquo; said van de Rakt.  &ldquo;Might even mean that there will be different and better ways for premium plugins to market their products.&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, 03 Dec 2019 20:53:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"BuddyPress: ​​Contributing to BuddyPress just got easier :)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=309282\";s:7:\"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:52:\"https://buddypress.org/2019/12/bp-beta-tester-1-0-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1940:\"<p>Yesterday morning we’ve deployed the first stable version of the BP Beta Tester plugin on the WordPress.org plugins directory.​​</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"wp-embedded-content\"><a href=\"https://wordpress.org/plugins/bp-beta-tester/\">BP Beta Tester</a></blockquote>\n</div>\n\n\n\n<p>This plugin’s goal is to make it easier to beta test our pre-releases. You just need to install and activate the plugin to be ready to try our beta and release candidate versions once we’ve announced them on this blog.​​<br />​<br />Beta testing BuddyPress is very important to make sure it behaves the right way for you and for the community. Although we, the BuddyPress Development Team, are regularly testing it, it’s very challenging to test every possible configuration of WordPress and BuddyPress. That’s why we absolutely need your help during these pre-release stages.​​</p>\n\n\n\n<p>Making this plugin available was one of the means we thought about during our post 5.0.0 release development meeting to have more BuddyPress contributors.​​<br />​<br />Beta testing is actually a good way to start contributing, to anticipate and fix potential issues before you have the bad surprise to meet them once you&#8217;re upgrading to a new stable version of the plugin.​​</p>\n\n\n\n<p><strong>NB:</strong> to beta test BuddyPress, we strongly advise you to have a local copy of your live site or a staging site : it’s always safer than doing it on a production site.​​</p>\n\n\n\n<p>During our next pre-release stages, when you will find something is going wrong during your beta tests, please think of warning us about it submitting a ticket on our <a href=\"https://buddypress.trac.wordpress.org/newticket\">Development Tracker</a> or posting a new topic in our <a href=\"https://buddypress.org/support/\">support forums</a>.​​</p>\n\n\n\n<p>Thanks in advance for your time and help &lt;3</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, 03 Dec 2019 12:27:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Mathieu Viet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: Gutenberg 7.0 Launches Stable Navigation Block, Post Blocks, and Template Parts\";s:7:\"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:29:\"https://wptavern.com/?p=95640\";s:7:\"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:98:\"https://wptavern.com/gutenberg-7-0-launches-stable-navigation-block-post-blocks-and-template-parts\";s: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:7072:\"<p>On November 27, <a href=\"https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/\">Gutenberg 7.0 landed</a> with several features, enhancements, and bug fixes.  Most notably, the navigation block is now a stable feature.  Theme authors can also start using block template parts and testing the post title and content blocks.</p>\n\n\n\n<p>The update addressed several bugs with the block editor.  It also introduced new developer features such as the <a href=\"https://github.com/WordPress/gutenberg/pull/17963\">card component</a> and the ability to <a href=\"https://github.com/WordPress/gutenberg/pull/17376\">internationalize strings with safe HTML</a>.</p>\n\n\n\n<p>Gradient classes are now <a href=\"https://github.com/WordPress/gutenberg/pull/18590\">used for the cover block</a>.  Classes are a nicer solution than the inline styles used in earlier iterations.  Note that gradients are still an experimental feature.</p>\n\n\n\n<p>For developers, there is a new <a href=\"https://github.com/WordPress/gutenberg/tree/master/docs/designers-developers/developers/backward-compatibility\">backward-compatibility document</a> that outlines how the project preserves compatibility in its public APIs. This should be useful for all developers working on the project in the future.</p>\n\n\n\n<h2>Navigation Block Now Stable</h2>\n\n\n\n<img />Creating a nav menu with the navigation block.\n\n\n\n<p>The navigation block is now a stable feature and no longer considered experimental.  The interface is much improved over earlier implementations.  For quickly building a menu of links, it does the job.  Users can manually type a link or search for an existing link for the site.</p>\n\n\n\n<p>A user interface for nav menus in the block editor is no easy beast to tame.  The Gutenberg team managed to fit in the most common features without making it feel confusing.  For users, theme integration may be limited until their themes are updated with full support.  The default Gutenberg design may not be ideal or work at all in the context of the active theme.</p>\n\n\n\n<p>The navigation block also comes with both light and dark block styles.  Theme authors can design these how they prefer, add additional styles, or remove the styles altogether.  More than likely, theme authors will begin adding several variations to their themes as a selling point in the long run.</p>\n\n\n\n<p>The Gutenberg team dropped the background color option from the navigation block. Instead, users are encouraged to place it within a group block and add a background to the group. It is possible to change the link text color directly within the navigation block.</p>\n\n\n\n<p>Currently, there is no parity between normal nav menu HTML classes and navigation block classes.  This could result in bulkier theme CSS, at least in the transition between how themes currently work and  the full site-editing era.  Inconsistent classes is an issue that should be handled with a <a href=\"https://wptavern.com/themes-of-the-future-a-design-framework-and-a-master-theme\">design framework</a>.</p>\n\n\n\n<h2>Post Title and Content Blocks Added</h2>\n\n\n\n<img />Customized post title block output.\n\n\n\n<p>As part of the experimental site-editing feature, Gutenberg has introduced the <a href=\"https://github.com/WordPress/gutenberg/pull/18461\">post title and post content blocks</a>.  These blocks act as placeholders and will output either the title or content.  Both blocks are foundational elements for true full-site editing.  Eventually, users will no longer be as limited to how their posts are output on the screen.</p>\n\n\n\n<p>Currently, the post title block simply outputs the post title inside of <code>&lt;h1&gt;</code> tags. There are no classes for customizing the design. The other missing element at this point is the post byline or meta area that often accompanies the title.  In the long run, Gutenberg needs to have a method of handling post header and footer areas.</p>\n\n\n\n<p>The custom post header feature has plagued theme authors for years, long before Gutenberg was around.  There are dozens or more implementations in the wild.  Some of them work with the block editor.  Others use custom post meta or the featured image.  However, users are often left with sub-par implementations that don&rsquo;t always work in the context of a specific post.</p>\n\n\n\n<p>One of the features I have wanted to implement within Gutenberg is the &ldquo;hero&rdquo; image with text set over the top.  By using the built-in cover block and the post title block, I was able to accomplish this.  However, it was still missing the post byline.  Therefore, I put together a quick filter to output the post byline when the post title block is in use.</p>\n\n\n\n<p><em>Any theme author who wants to test it out can modify the following code. I would not recommend this in production since this is an experimental feature, but it is good to start thinking ahead about possibilities.</em></p>\n\n\n<pre class=\"brush: php; auto-links: false; gutter: false; title: ; wrap-lines: false; notranslate\">\nadd_filter( \'pre_render_block\', function( $block_content, $block ) {\n\n    if ( \'core/post-title\' === $block[\'blockName\'] ) {\n\n        $post = gutenberg_get_post_from_context();\n\n        if ( ! $post ) {\n            return $block_content;\n        }\n\n        if ( \'post\' === $post-&gt;post_type ) {\n\n            $block_content = \'&lt;h1 class=\"entry__title\"&gt;\' . get_the_title( $post ) . \'&lt;/h1&gt;\';\n\n            $block_content .= sprintf(\n                \'&lt;div class=\"entry__byline\"&gt;%s &amp;middot; %s &amp;middot; %s&lt;/div&gt;\',\n                get_the_author(),\n                get_the_date(),\n                get_the_term_list( $post-&gt;ID, \'category\' )\n            );\n        }\n      }\n\n    return $block_content;\n\n}, 10, 2 );\n</pre>\n\n\n<h2>Block Template Parts for Themes</h2>\n\n\n\n<p>Gutenberg 6.9 <a href=\"https://wptavern.com/gutenberg-6-9-introduces-image-titles-block-patterns-and-new-theme-features\">introduced block templates</a> that resolve from a theme&rsquo;s <code>/block-templates</code> folder as part of the site-building experiment.  Version 7.0 takes that a step farther and introduces a <a href=\"https://github.com/WordPress/gutenberg/pull/18339\">block template parts system</a>, which resolves from a theme&rsquo;s <code>/block-template-parts</code> directory.</p>\n\n\n\n<p>This new system allows top-level templates to house smaller, reusable template parts.  This is a rather standard method of template-part handling that has become a part of the normal theme-building experience.</p>\n\n\n\n<p>It will be interesting to see how this works in the long run.  WordPress&rsquo; current template part system for theme authors (i.e., <code>get_template_part()</code>) is a bare-bones implementation with little flexibility for handling features like hierarchy and passing data.  Thus far, the new feature seems to be a melding of blocks and old templating ideas, but it is too early in the process to see where it goes or whether theme authors will have to make customizations to bend the system to their will.</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, 02 Dec 2019 19:22:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WordPress.org blog: The Month in WordPress: November 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8156\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2019/12/the-month-in-wordpress-november-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8071:\"<p>November has been a big month in the WordPress community. New releases, big events, and a push for more contributors have characterized the work being done across the project — read on to find out more!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>The release of WordPress 5.3 “Kirk”</h2>\n\n\n\n<p><a href=\"https://wordpress.org/news/2019/11/kirk/\">WordPress 5.3 was released</a> on November 12, and is <a href=\"https://wordpress.org/download/\">available for download</a> or update in your dashboard! Named “Kirk,” after jazz multi-instrumentalist Rahsaan Roland Kirk, 5.3 enhances the block editor with <a href=\"https://make.wordpress.org/core/2019/09/24/new-block-apis-in-wordpress-5-3/\">new APIs</a> and <a href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">theme-related features</a>, adds more intuitive interactions, and improves accessibility in a number of areas — including <a href=\"https://make.wordpress.org/core/2019/10/18/noteworthy-admin-css-changes-in-wordpress-5-3/\">CSS in the dashboard</a>, the <a href=\"https://make.wordpress.org/core/2019/10/14/improvements-in-media-component-accessibility-in-wordpress-5-3/\">media manager</a>, <a href=\"https://make.wordpress.org/core/2019/09/23/core-widgets-new-aria-current-attribute-in-wordpress-5-3/\">core widgets</a>, and <a href=\"https://core.trac.wordpress.org/query?focuses=~accessibility&milestone=5.3&group=component&max=500&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=id\">dozens of other areas</a>.</p>\n\n\n\n<p>You can read the full details of all the included enhancements in the <a href=\"https://make.wordpress.org/core/2019/10/17/wordpress-5-3-field-guide/\">5.3 Field Guide</a>.</p>\n\n\n\n<p>Along with 5.3 came <a href=\"https://wordpress.org/themes/twentytwenty/\">the new Twenty Twenty theme</a>, which gives users more design flexibility and integrates with the block editor. For more information about the improvements to the block editor, expanded design flexibility, the Twenty Twenty theme, and to see the huge list of amazing contributors who made this release possible, read <a href=\"https://wordpress.org/news/2019/11/kirk/\">the full announcement</a>.</p>\n\n\n\n<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>. You can also <a href=\"https://make.wordpress.org/core/2019/11/15/5-3-retrospective-call-for-feedback/\">provide feedback</a> on the 5.3 release process.</p>\n\n\n\n<h2>At Last! bbPress 2.6!</h2>\n\n\n\n<p><a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6/\">bbPress 2.6 was released</a> on November 12 after a little over six years in development. This new release includes per-forum moderation, new platforms to import from, and an extensible engagements API. You can read more about all of this in <a href=\"https://codex.bbpress.org/\">the bbPress codex</a>.</p>\n\n\n\n<p><a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6-1-is-out/\">Version 2.6.1</a> and <a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6-2-is-out/\">2.6.2</a> quickly followed, both of which fixed a number of bugs that required immediate attention.</p>\n\n\n\n<p>Want to get involved in building bbPress? Follow <a href=\"https://bbpress.org/blog/\">the bbPress blog</a> and join the #bbpress channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>State of the Word</h2>\n\n\n\n<p><a href=\"https://2019.us.wordcamp.org/\">WordCamp US 2019</a> was held in St. Louis, MO this year on November 1-3. At the event, <a href=\"https://profiles.wordpress.org/matt/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>matt</a> gave his annual State of the Word address, during which he shared what had been accomplished in the past year, announced what is coming next, and shared several ways to get involved.</p>\n\n\n\n<p>You can watch <a href=\"https://www.youtube.com/watch?v=LezbkeV059Q&t=21s\">the State of the Word</a> as well as <a href=\"https://www.youtube.com/watch?v=fFsVbAo8HwI\">the Q&amp;A session at the end</a>, and <a href=\"https://ma.tt/2019/11/state-of-the-word-2019/\">read Matt’s recap</a> of the address. If you didn’t make it to St. Louis, you can still <a href=\"https://www.youtube.com/playlist?list=PL1pJFUVKQ7ETHl165LvLVXfB3yBZEzV-q\">watch all the sessions</a> at your leisure.</p>\n\n\n\n<h2>Five for the Future</h2>\n\n\n\n<p>During the State of the Word, Matt announced that there is now <a href=\"https://wordpress.org/five-for-the-future/\">a dedicated landing page for Five for the Future</a>, which features the people and organizations that commit at least it 5% of their resources to the WordPress open source project. There are many ways to contribute to WordPress, such as core development, marketing, translation, training, and community organizing, among many other important paths to contribution.</p>\n\n\n\n<p>Five for the Future welcomes individuals and organizations, and highlights all the incredible ways we build WordPress together. For more information, visit <a href=\"https://wordpress.org/five-for-the-future/\">the Five for the Future page</a>.<br /></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li>After releasing WordPress 5.3, the Core team announced <a href=\"https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/\">a tentative release schedule</a> for 2020 and 2021.</li><li>The Core team has announced <a href=\"https://make.wordpress.org/core/2019/11/28/new-css-focus-in-core/\">a new CSS focus</a> to complement the existing ones for PHP and JavaScript — this focus comes with dedicated tags, targeted work, and a new #core-css Slack channel.</li><li>Version 2.2 of the WordPress Coding Standards <a href=\"https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/2.2.0\">has been released</a> — this new release is ready for WordPress 5.3, includes five brand new sniffs, and plenty of new command-line documentation.</li><li>The latest update to the Theme Review Coding Standards, <a href=\"https://github.com/WPTRT/WPThemeReview/releases/tag/0.2.1\">v0.2.1</a>, is compatible with v2.2 of the WordPress Coding Standards, and helps authors to build more standards-compatible themes.</li><li><a href=\"https://2019.us.wordcamp.org/2019/11/11/wordcamp-us-2020/\">The WordCamp US team has announced</a> the dates for next year’s event in St. Louis, MO — WordCamp US 2020 will be held on October 27-29. This will be the first time that the event will be held during the week and not on a weekend. The team has also announced a Call for Organizers. If you are interested in joining the team, <a href=\"https://2020.us.wordcamp.org/2019/11/21/join-the-wcus-2020-organizing-team/\">learn more</a>.&nbsp;</li><li>The WP Notify project, which is building a unified notification system for WordPress Core, <a href=\"https://make.wordpress.org/core/2019/11/29/wp-notify-hiatus-till-january-2020/\">is on hiatus</a> until January 2020.</li><li>A working group on the Community Team <a href=\"https://make.wordpress.org/community/2019/11/25/handbook-update-how-to-improve-the-diversity-of-your-wordpress-events/\">has updated their Handbook</a> to help organizers create more diverse events.</li><li>The WP-CLI team <a href=\"https://make.wordpress.org/cli/2019/11/12/wp-cli-v2-4-0-release-notes/\">released v2.4.0</a> of the WordPress command-line tool. This release includes support for WordPress 5.3 and PHP 7.4.</li><li>Gutenberg development continues rapidly with <a href=\"https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/\">the latest 7.0 release</a> including an early version of the navigation menus block, among other enhancements and fixes.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it 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:\"Mon, 02 Dec 2019 08:38:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"Matt: Powering Your House\";s:7:\"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=50550\";s:7:\"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:42:\"https://ma.tt/2019/11/powering-your-house/\";s: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:263:\"<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>I enjoyed this fun video from xkcd&#8217;s Randall Munroe on different ways you could power your home, illustrated. <a href=\"https://xkcd.com/how-to/\">Check out his book How To for more in the same vein</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 30 Nov 2019 22:33: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: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:30;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"WPTavern: WP&amp;UP to Hold #DoSummitGood Online Event for Giving Tuesday\";s:7:\"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:29:\"https://wptavern.com/?p=95585\";s:7:\"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:78:\"https://wptavern.com/wpup-to-hold-dosummitgood-online-event-for-giving-tuesday\";s: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:4922:\"<img />\n\n\n\n<p>On Giving Tuesday, December 3, WP&amp;UP is holding an online event called <a href=\"https://wpandup.org/go/dosummitgood\">#DoSummitGood</a> that features speakers from various &ldquo;for good&rdquo; WordPress organizations.  The event will have nine sessions from 13 speakers.  It begins at <a href=\"http://www.timebie.com/std/utc.php?q=13\">13:00 UTC</a>.</p>\n\n\n\n<p>Giving Tuesday is a global movement meant to inspire generosity.  The celebration has run each year since 2012 on the Tuesday following the U.S. Thanksgiving holiday.  The idea is to inspire people to do good, not for just one day of the year, but each day of their lives.</p>\n\n\n\n<p>A WordPress-focused event on Giving Tuesday sounds like a perfect match.  Given the nature of open source and the charitable work of many of the people and companies in the space, it makes sense to hold a specific event for the holiday.   &ldquo;This is the first #DoSummitGood and there has already been a discussion about making this an annual event for Giving Tuesday,&rdquo; said Dan Maby, CEO and a Trustee of WP&amp;UP.</p>\n\n\n\n<p>WP&amp;UP is a registered charity organization with a mission to support and promote positive mental health within the WordPress community.  Its <a href=\"https://wpandup.org/health-hubs/\">Health Hubs</a> cover topics like business, skills, physical, and mental health.  The organization also provides support and counseling services.</p>\n\n\n\n<p>The idea for the #DoSummitGood event was born from a WP&amp;UP <a href=\"https://wpandup.org/2019/10/join-our-open-discussion-town-hall-ama-on-wednesday-9th-october/\">Town Hall</a> in October.  &ldquo;Our focus is on collaboration and our Town Halls are an opportunity for members of the public to get involved and help brainstorm ideas for the community, as well as get to know more about what WP&amp;UP does,&rdquo; said Maby.</p>\n\n\n\n<p>The primary event will run via <a href=\"https://www.crowdcast.io/e/dosummitgood/register\">Crowdcast</a>.  By registering for the event, attendees will gain access to the Hallway Track to meet with other attendees online.  They will also have the ability to ask questions directly to the speakers.  Registration is free but will close once it reaches a specific number of signups.  &ldquo;WP&amp;UP is paying for the technical solution to deliver the event,&rdquo; said Maby.  &ldquo;As a registered charity we have to be responsible for expenditure, and so limiting the number of seats for this first event is one way we can do that.&rdquo;</p>\n\n\n\n<p>For those who do not register and attend via Crowdcast, they can still watch and participate in the event through various social platforms:</p>\n\n\n\n<ul><li><a href=\"https://twitter.com/WPandUP\">Twitter</a></li><li><a href=\"https://www.facebook.com/WPandUP/\">Facebook</a></li><li><a href=\"https://www.youtube.com/wpandup\">YouTube</a></li><li><a href=\"https://www.twitch.tv/wpandup\">Twitch</a></li></ul>\n\n\n\n<p>Each of the sessions will feature various international speakers who will give a talk on their area of expertise.  The sessions will follow a specific format and run for one hour.  For the first 10 minutes of each session, the individual speaker or group will talk about the &ldquo;for good&rdquo; entity they represent.  They will follow up with a 35-minute talk on their subject.  Afterward, the speaker and attendees will participate in an open Q&amp;A session.</p>\n\n\n\n<p>The #DoSummitGood event is designed to give back.  &ldquo;Throughout the event, a donation form will be shared,&rdquo; said Maby.  &ldquo;All money raised through this form will be distributed between the various non-profits that feature in the event.&rdquo;</p>\n\n\n\n<p>Cory Miller, a Trustee at WP&amp;UP, will kick off the event with a session titled &ldquo;The Iceberg of Life: How I Manage the Ups and Downs.&rdquo;  Miller has been open about mental health within the WordPress community and his struggles for several years.  He has previously written on the topic of <a href=\"https://corymiller.com/the-iceberg-of-life/\">The Iceberg of Life</a>, which is worth reading if you are looking to get an early look into what his session may be about.</p>\n\n\n\n<p>Marieke van de Rakt will follow up with a talk about improving a site&rsquo;s SEO.  She is representing Yoast and its <a href=\"https://wptavern.com/yoast-launches-fund-to-increase-speaker-diversity-at-tech-conferences\">diversity fund program</a>, which helps to remove the financial burdens that cause minorities or underrepresented groups to speak at conferences.</p>\n\n\n\n<p>The nine sessions have a diverse group of speakers from various organizations that are currently providing support for charities, minorities, and other groups that need help.  The topics include turning passion into a profession,  bringing more diversity to speaking roles at conferences, and more.  Two of the sessions will be round-table events with multiple speakers.</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, 27 Nov 2019 19:26:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"Matt: Distributed Podcast: Clark Valberg, Lydia X. Z. Brown, Stephen Wolfram, and the Grand Meetup\";s:7:\"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=50496\";s:7:\"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:50:\"https://ma.tt/2019/11/distributed-podcast-updates/\";s: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:9149:\"<p>If y&#8217;all haven&#8217;t caught up recently with my podcast <a href=\"https://distributed.blog/\">Distributed</a>, this is a perfect moment to do so—the past several weeks have been full of insights from folks like InVision CEO Clark Valberg, attorney and advocate Lydia X. Z. Brown, Stephen Wolfram, and some of my own Automattic colleagues in-person at our Grand Meetup. </p>\n\n\n\n<p>You can subscribe at <a href=\"https://podcasts.apple.com/us/podcast/distributed-with-matt-mullenweg/id1463243282\">Apple Podcasts</a>, <a href=\"https://podcasts.google.com/?feed=aHR0cHM6Ly9kaXN0cmlidXRlZC5ibG9nL2NhdGVnb3J5L3BvZGNhc3QvZmVlZC8%3D\">Google</a>, <a href=\"https://overcast.fm/itunes1463243282/distributed-with-matt-mullenweg\">Overcast</a>, <a href=\"https://open.spotify.com/show/59bljZU7v9cJTXKvlfnFN8?si=Iv4hgJMFRCCx4SpmXlLArg\">Spotify</a>, or wherever you like to listen.&nbsp;</p>\n\n\n\n<span id=\"more-50496\"></span>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/11/26/the-importance-of-irl-in-a-world-of-screens/\">The Importance of IRL in a World of Screens (Automattic Grand Meetup)</a></h2>\n\n\n\n<p>&#8220;When you work in a distributed company, every time that you interact with your colleagues via text… you are taking out of your social bank account with them. So when you get people together, that’s when you have the opportunity to see each other face-to-face, and remind everybody that you’re all human beings. And fill that social capital back up because it’s so hard to communicate via text.&#8221;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/11/14/clark-valberg-invision/\">Building the Tools That Bring the Screen to Life (Clark Valberg, InVision)&nbsp;</a></h2>\n\n\n\n<p>&#8220;We needed it as a talent hack, as a talent arbitrage. Hire the best people wherever they happen to be, figure everything out later, hire them quickly, get them in the ship as early as possible and start seeing results. How can I just hire the best people no matter where they are?&#8221;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/10/31/making-work-accessible-wherever-it-happens/\">Making Work Accessible, Wherever It Happens (Lydia X. Z. Brown)</a></h2>\n\n\n\n<p>&#8220;I have believed from a very young age that every single one of us has a moral obligation to use whatever resources we have — time, money, knowledge, skills, emotional energy, access to physical resources — however that might be defined — that we each have a moral obligation to use those resources in service of justice, and fighting against injustice and oppression and violence in all of its forms, structural and individual, subtle and overt.&#8221;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/10/17/inside-toptals-distributed-screening-process/\">Inside Toptal&#8217;s Distributed Screening Process (Taso Du Val)&nbsp;</a></h2>\n\n\n\n<p>&#8220;I was going into an office but not seeing anyone or interacting with anyone except myself. So it almost was this zombie-like walk to the office every morning where I’m going to the office because I go to work, but I don’t see anyone who I work with. [laughs] And so I actually started waking up and just working on my computer at home. And then I said to myself, &#8216;Well, why am I even working from home?\'&#8221;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/10/03/turning-ideas-into-real-things/\">The Machine That Turns Ideas Into Real Things (Stephen Wolfram)&nbsp;</a></h2>\n\n\n\n<p>“You can do things that are very commercial, but a little bit intellectually boring. And it tends to be the case that you’re doing a lot of rinse-and-repeat stuff if you want to grow purely commercially, so to speak. Or, you can do things that are wonderful intellectually, but the world doesn’t happen to value them and you can’t make commercial sense that way. And I’ve tried to navigate something in between those two where it’s where I’m really intellectually interested and where it’s commercially successful enough to sustain the process for a long time.”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/09/19/welcome-to-the-chaos/\">Welcome to the Chaos (Sonal Gupta, Automattic)</a></h2>\n\n\n\n<p>“I like to trust people and give them autonomy. But I keep in touch with them very regularly and I think it becomes clear pretty quickly if somebody is not doing work. We look at performance, and we look at communication at a distributed company. Communication is oxygen.”&nbsp;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/09/05/managing-distributed-teams/\">Observe, Don’t Surveil: Managing Distributed Teams with Respect (Scott Berkun)</a></h2>\n\n\n\n<p>“To work at a remote company demanded great communication skills, and everyone had them. It was one of the great initial delights. Every corporation has the same platitudes for the importance of clear communication, yet utterly fails to practice it. There was little jargon at Automattic. No ‘deprioritized action items’ or ‘catalyzing of crossfunctional objectives.’ People wrote plainly, without pretense and with great charm.”&nbsp;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/08/22/build-distributed-engineering-teams/\">How to Build and Strengthen Distributed Engineering Teams (Cate Huston, Automattic)</a></h2>\n\n\n\n<p>“A senior engineer makes the whole team better, but we don’t want to be prescriptive about how people made the team better. That was up to them. There were options, but that was the expectation for everyone on the team. You come in, you’re an experienced engineer, we expect you to be making the whole team better in some way, and what that looks like is up to you.”&nbsp;</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/08/08/stay-connected-in-a-distributed-world/\">How to Stay Connected in a Distributed World (Leo Widrich)</a>&nbsp;</h2>\n\n\n\n<p>“I started to feel like I was hitting a wall. This thing that I always dreamt of, to have a profitable company, to be financially secure, to have a team… I felt that having that success, having some of that financial security — it left me unfulfilled in a lot of other areas. — in the sense of deep lasting connection and also a lack of emotional resilience to deal with the ups and downs that startup life comes with.”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/07/25/helping-creativity-happen-from-a-distance/\">Helping Creativity Happen from a Distance (John Maeda)&nbsp;</a></h2>\n\n\n\n<p>“My point is blogging is good for you. It’s mental health, it’s expression, it’s sharing your process with the world. And when you relate to the world, your standard of quality floats to that value of the world. It’s a market economy of ideas and by putting ourselves out there, you become relevant.”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/07/11/engineering-with-empathy/\">Engineering with Empathy (Han Yuan, Upwork)&nbsp;</a></h2>\n\n\n\n<p>“We really want to encourage empathy in general. And so a key part of empathy is being able to try to see the other person’s point of view. And in an organization as distributed as ours where people come from all around the world, we view it as an essential ingredient to developing deep and meaningful collaboration.”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/07/11/how-to-do-hr-in-a-blended-company/\">How to Do HR in a Blended Company (Zoe Harte, Upwork)&nbsp;</a></h2>\n\n\n\n<p>“That means saying, ‘Okay, our entire organization will connect this many times a year in this many ways. There will be an all-department meeting once a month, once a quarter — whatever is appropriate — and that we will cover these three priorities and in broad progress and how it’s impacting the business overall.’ And then the expectation would be that the smaller subsets of teams are meeting in this way.”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/07/02/on-building-automattic/\">On Building Automattic (Me)</a></h2>\n\n\n\n<p>“Our distributed roots did not come from some grand vision, but instead emerged from cold realities. Colocation (being in the same place, at the same time) is expensive!”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/06/13/is-remote-work-bs/\">Is Remote Work Bulls&#8212;t? (Arianna Simpson)</a></h2>\n\n\n\n<p>“I think having people come and interrupt you every 25 seconds, as is often the case in open floor plans, is definitely not the most productive situation. So the model I’ve seen work well, or the model I lean towards, is having an office where people are working from, but having private offices or spaces where people can plug in their headphones and just do work alone while still being in the same place as, hopefully, all of their colleagues.”</p>\n\n\n\n<h2><a href=\"https://distributed.blog/2019/05/30/could-vr-replace-the-office/\">For Years, VR Promised to Replace the Office. Could It Really Happen Now? (John Vechey, Pluto VR)</a></h2>\n\n\n\n<p>“The technology forces you to be present — in a way flatscreens do not — so that you gain authentic experiences, as authentic as in real life. People remember VR experiences not as a memory of something they saw but as something that happened to them.”</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Nov 2019 03:53: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: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:32;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"WPTavern: WordPress Black Friday Sales Roundup\";s:7:\"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:29:\"https://wptavern.com/?p=95552\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://wptavern.com/wordpress-black-friday-sales-roundup\";s: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:11633:\"<div class=\"wp-block-cover alignfull has-background-dim-80 has-gray-900-background-color has-background-dim has-parallax bg-gray-900\"><div class=\"wp-block-cover__inner-container\">\n<h1 class=\"text-white\">WordPress Black Friday Sales Roundup</h1>\n\n\n\n<p class=\"has-medium-font-size font-secondary text-base\"><a href=\"https://wptavern.com/author/justintadlock\">Justin Tadlock</a>&nbsp;<span class=\"sep mx-2\">&middot;</span>&nbsp;November 26, 2019&nbsp;<span class=\"sep mx-2\">&middot;</span>&nbsp;<a href=\"https://wptavern.com/category/news\">News</a></p>\n</div></div>\n\n\n\n<p>&lsquo;Tis the largest shopping season of the year.  While you are gearing up for a big weekend of finding that perfect gift for your family and friends, you might take a moment to consider giving your website a little something for the holiday.</p>\n\n\n\n<p>The following is our roundup of WordPress hosting, services, and plugins that are on sale this week and next.</p>\n\n\n\n<h2>Hosting and Domain Deals</h2>\n\n\n\n<p>If you are in the market for a new host or have been sitting on a new domain name to purchase, now might be the time to start looking around to see if you can snag a good price.</p>\n\n\n\n<h3>BlueHost</h3>\n\n\n\n<p>BlueHost is running a weeklong event, which began on November 25.  The web host is offering 60% off WordPress, 50% off VPS, and 40% off WordPress Pro hosting. The offer includes a free domain for the first year.</p>\n\n\n\n<p><a href=\"https://www.bluehost.com/\">Visit BlueHost&rsquo;s site &rarr;</a></p>\n\n\n\n<h3>DreamHost</h3>\n\n\n\n<p>DreamHost is cutting their prices on new domain registrations from November 25 through December 3, which ranges from a low $0.79 for <code>.xyz</code> to $6.99 for <code>.com</code> registrations. Beginning on Friday, November 29, they are offering deals on their Shared Unlimited hosting for 1-year ($5.95/month) and 3-year ($4.95/month) paid plans.</p>\n\n\n\n<p><a href=\"http://dreamhost.com/\">Visit DreamHost&rsquo;s site &rarr;</a></p>\n\n\n\n<h2>WordPress Services</h2>\n\n\n\n<p>A couple of WordPress companies are offering markdowns on their services rather than products this shopping season.</p>\n\n\n\n<h3>WPScan</h3>\n\n\n\n<p>WPScan, an online WordPress vulnerability scanner, is giving a 20% discount for the first three months on any of their paid plans.  Use the coupon code <code>BLACKFRIDAY20</code> at checkout.</p>\n\n\n\n<p><a href=\"http://wpscan.io\">Visit WPScan&rsquo;s site &rarr;</a></p>\n\n\n\n<h3>WPDandy</h3>\n\n\n\n<p>WPDandy offers WordPress maintenance, management, and support, which includes backup and security services.  The team is currently running 50% off each plan available.  The Black Friday deal is currently open, but there is no mention of when it ends.</p>\n\n\n\n<p><a href=\"https://wpdandy.com/black-friday-2019\">See WPDandy&rsquo;s sale &rarr;</a></p>\n\n\n\n<h2>Plugins</h2>\n\n\n\n<p>If you have had your eye on a particular plugin but have yet to pull the trigger, now may be a good chance to grab it.  The following is a roundup of several plugins and plugin bundles.  Some are currently on sale.  Others will begin on Black Friday.  Most sales will last several days.</p>\n\n\n\n<h3>Saturday Drive</h3>\n\n\n\n<p>Saturday Drive, the company behind <a href=\"https://ninjaforms.com/\">Ninja Forms</a> and <a href=\"https://calderaforms.com/\">Caldera Forms</a>, has the most interesting Black Friday deal.  Users have a chance of getting between 40% and 100% off either plugin by using the spinner at checkout.  The company is also donating 10% of all sales to Operation Smile.  The promotion runs between November 29 and December 3.</p>\n\n\n\n<p>Read more about Saturday Drive&rsquo;s <a href=\"https://saturdaydrive.com/save-it-forward/\">Save it Forward event &rarr;</a></p>\n\n\n\n<h3>iThemes</h3>\n\n\n\n<p>iThemes has a large selection of products, including its popular BackupBuddy and iThemes Security Pro plugins.  The site is cutting prices 50% off any new plugin, combo pack, hosting, theme, Stash, or annual Sync plan from November 23 &ndash; December 2.</p>\n\n\n\n<p><a href=\"https://ithemes.com/coupon/black-friday-cyber-monday-sale/\">See iTheme&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>GiveWP</h3>\n\n\n\n<p>GiveWP is a donations plugin that allows visitors to contribute to your cause directly from your website. They are running a 50%-off special for the next week.  However, the sale is limited to the first 500 customers.  This would be a good time to snag the plugin if you plan on collecting donations for Giving Tuesday next week.</p>\n\n\n\n<p><a href=\"https://givewp.com/lps/black-friday/\">See GiveWP&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>Pootlepress</h3>\n\n\n\n<p>Pootlepress, a WordPress plugin and theme shop, is slashing 40% off their WooBuilder Blocks and Storefront Blocks plugins, which integrate WooCommerce and Gutenberg.  The sale begins on November 29 and ends on December 4.</p>\n\n\n\n<p><a href=\"https://www.pootlepress.com/\">Visit Pootlepress&rsquo; site &rarr;</a></p>\n\n\n\n<h3>Starfish Reviews</h3>\n\n\n\n<p>Starfish Reviews, a plugin designed to help businesses get more reviews on Google, Facebook, and other platforms, is currently on sale for 83% off. The lifetime deal ends on November 30.</p>\n\n\n\n<p><a href=\"https://starfish.reviews/2019-bfcm-ltd/\">See Starfish Review&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>ProjectHuddle</h3>\n\n\n\n<p>ProjectHuddle is a WordPress feedback plugin for use by agencies and freelancers to communicate with their clients. It allows clients to provide comments on mockups and more.  Each pricing plan has been cut by 40%.  The sale began on November 25 and runs through December 2.</p>\n\n\n\n<p><a href=\"https://projecthuddle.com/friday\">See ProjectHuddle&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>Paid Memberships Pro</h3>\n\n\n\n<p>Paid Memberships Pro is a WordPress community and memberships plugin that works with several payment gateways and integrates with community plugins such as bbPress and BuddyPress.  The website is cutting $100 from its Plus plan and $200 from its Unlimited plan, both of which locks in a lifetime renewal rate.  The offer runs from November 29 through December 2.  Use the <code>blackfriday</code> discount code at checkout.</p>\n\n\n\n<p><a href=\"https://www.paidmembershipspro.com/press/resources/\">See Paid Memberships Pro&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>Dev4Press</h3>\n\n\n\n<p>Dev4Press is a plugin shop that has a range of plugins, including bbPress tools, security, ratings, and more.  Customers can grab 25% off using the <code>BLACKCYBER</code> coupon code at checkout.  The discount can be applied to all plugins, add-ons, and club memberships.  The sale runs from November 27 through December 3.  </p>\n\n\n\n<p><a href=\"https://www.dev4press.com/promotion/2019/black-friday-cyber-monday-2019/\">See Dev4Press&rsquo; sale &rarr;</a></p>\n\n\n\n<h3>SiteOrigin</h3>\n\n\n\n<p>SiteOrigin is slashing 50% off their premium product bundle on Black Friday, November 29, which includes over 20 add-ons for their theme and plugin products.  Use the <code>NOVEMBER30</code> coupon code at checkout for the discount.  On Giving Tuesday, November 3, the team will provide email support to all users, which is typically only available on paid plans.</p>\n\n\n\n<p><a href=\"https://siteorigin.com/downloads/premium/\">Visit SiteOrigin&rsquo;s Premium page &rarr;</a></p>\n\n\n\n<h3>Stackable</h3>\n\n\n\n<p>Stackable, a premium blocks collection plugin, kicked off its version 2 launch on November 25.  The site is currently holding a flash sale that ends on November 27.  Use the discount code <code>LTD30</code> to grab 30% off.  After the flash sale, they will continue with a 20% discount for all annual plans when using the <code>LAUNCH20</code> discount code. This deal ends on December 9.  The website is also offering limited-time lifetime purchases during the event.</p>\n\n\n\n<p><a href=\"https://wpstackable.com/\">Visit Stackable&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>Hookturn</h3>\n\n\n\n<p>Hookturn, a company that specializes in add-on plugins for Advanced Custom Fields, is currently offering 40% off their ACF Theme Code Pro, ACF Custom Database Tables, and Advanced Forms Pro plugins.  The sale runs until December 3.</p>\n\n\n\n<p><a href=\"https://hookturn.io\">Visit Hookturn&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>SearchWP</h3>\n\n\n\n<p>SearchWP is an advanced search form plugin that offers a more robust search of content for WordPress.  The company&rsquo;s sale this year begins on Friday, November 29, and lasts until Tuesday, December 3.  The site is offering a 30%-50% discount on new plugin licenses and 40% off upgrades for existing customers at checkout.</p>\n\n\n\n<p><a href=\"https://searchwp.com/\">Visit SearchWP&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>OrganizeWP</h3>\n\n\n\n<p>OrganizeWP, a drag-and-drop plugin that allows users to manage their WordPress admin, will be on sale for 50% off support and update licenses.  The runs November 29 through December 3.  Discounts are automatically applied at checkout.</p>\n\n\n\n<p><a href=\"https://organizewp.com/\">Visit OrganizeWP&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>Gravity PDF</h3>\n\n\n\n<p>Gravity PDF, a plugin for automatically creating PDF documents for Gravity Forms, is currently holding a sale for 40% off their access passes.  The sale will end on Monday, December 2.</p>\n\n\n\n<p><a href=\"https://gravitypdf.com/l/2019-black-friday-and-cyber-monday-sale/\">See Gravity PDF&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>Meta Box</h3>\n\n\n\n<p>Meta Box, a custom fields plugin for developers, is offering 60% off their lifetime bundle, which brings the price from $499 down to $199.  The sales event lasts from November 26 through December 6.</p>\n\n\n\n<p><a href=\"https://metabox.io/black-friday/\">See Meta Box&rsquo;s sale &rarr;</a></p>\n\n\n\n<h3>WisdmLabs</h3>\n\n\n\n<p>WisdmLabs, a shop with various WooCommerce and LearnDash add-ons, will begin offering 30% discount on all products and bundles available through their site on November 28 and last through December 2.  Use the <code>BFCM30</code> coupon code at checkout.</p>\n\n\n\n<p><a href=\"https://wisdmlabs.com/premium-wordpress-plugins/\">See WisdmLabs&rsquo; sale &rarr;</a></p>\n\n\n\n<h3>MailOptin</h3>\n\n\n\n<p>MailOptin is an email opt-in form plugin that allows website visitors to sign up for an email subscription.  The site is offering a 25% discount for customers who use the <code>BCFM2019</code> coupon code from November 29 through December 3.</p>\n\n\n\n<p><a href=\"https://mailoptin.io\">Visit MailOptin&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>Social Rocket</h3>\n\n\n\n<p>Social Rocket, a social sharing plugin for WordPress that works with all the major social networks, is currently on sale for 33% off using the <code>BFCM2019</code> coupon code.  The discount is available through December 2.</p>\n\n\n\n<p><a href=\"https://wpsocialrocket.com/\">Visit Social Rocket&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>Charitable</h3>\n\n\n\n<p>Charitable is a fundraising plugin for WordPress that allows visitors to donate directly on users&rsquo; sites.  The website is offering 30% off its pro and agency payment options from November 29 through December 3.  Use the <code>PRO30BF19</code> code at checkout for the discount.</p>\n\n\n\n<p><a href=\"https://www.wpcharitable.com/\">Visit Charitable&rsquo;s website &rarr;</a></p>\n\n\n\n<h3>Sandhills Development</h3>\n\n\n\n<p>Sandhills Development is offering 25% off with the <code>BFCM2019</code> coupon code on all its products, which includes Easy Digital Downloads, AffiliateWP, Restrict Content Pro, Sugar Calendar, and WP Simple Pay.  The sale runs from November 29 through December 6.  They are also offering lifetime bundle deals and over $3,000 in prizes.</p>\n\n\n\n<p><a href=\"https://sandhillsdev.com/2019/11/sandhills-sale-event-2019/\">See Sandhills Development&rsquo;s sale &rarr;</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, 26 Nov 2019 21:29: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"WPTavern: WP Tavern’s New Design: No More Wood Grain\";s:7:\"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:29:\"https://wptavern.com/?p=95513\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://wptavern.com/wp-taverns-new-design-no-more-wood-grain\";s: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:4871:\"<img />Screenshot of the new homepage design.\n\n\n\n<p>If you are viewing WP Tavern from your browser today, you might be a bit shocked.  Things are different &mdash; much different.  If you are reading this post via email or a feed reader, hop on over to the live site to take a look.</p>\n\n\n\n<p>Welcome to the new design!</p>\n\n\n\n<p>When I accepted the job to write for WP Tavern, some of you asked if I would be handling anything with the design and development aspects of the site.  Today, you have your answer.  I was tasked with overhauling our dated design and getting something fresh up.</p>\n\n\n\n<p>From the moment I logged in and started peeking behind the curtain, the task seemed almost insurmountable.  WP Tavern has had nearly 5,000 posts over 12 years.  It has content mixed and matched with plugins that have not been used in years.  Being perfectly honest, I was unsure what some plugins did for a long while.  However, I have gotten to know the site and its inner-workings over the past couple of months, and the new design has taken shape around some of that.</p>\n\n\n\n<p>Rather than taking the time to do a complete overhaul of everything, which is sorely needed, our team decided the best course of action was to get a new theme up and iterate.</p>\n\n\n\n<p>The first step of the design process was to remove the wood-grain background.  There is likely some nostalgia attached to that for some of our readers (some of you may have grown accustomed to it over the last 12 years), but it is the one thing we universally agreed to drop.</p>\n\n\n\n<p>The second step was to move to a sidebar-less design.  Our team at the Tavern decided that nearly everything in the previous design&rsquo;s sidebar offered few benefits to our readers.  It was a distraction that took away from the content.</p>\n\n\n\n<p>The next step of the design process was to add complete compatibility with the block editor (Gutenberg).  With no sidebar, this will open the door for us to do more interesting things with media and other elements over the long term.</p>\n\n\n\n<p>Overall, the goal was to make the reading process nicer for all of you who visit the site.  I hope that we have accomplished that.</p>\n\n\n\n<h2>The Future Design of the Site</h2>\n\n\n\n<p>This is version 1.0 of the new design.  A large part of the process was laying the groundwork in a way that it would be easy to make changes going forward.</p>\n\n\n\n<p>There are still some missing elements that will be re-added soon.  Primarily, the site needs a search form in the header/navigation area.  Redesigning the email subscription form and moving it to a different location is high on the list.</p>\n\n\n\n<p>The site should load faster than before. However, there is still a lot of cleanup to do with plugins over the long haul. Page loads should be even snappier as we continue to iterate.</p>\n\n\n\n<p>I also hope we can add a custom logo and other Tavern-<em>esque</em> elements that bring more personality to the site as we move along in this ongoing process.</p>\n\n\n\n<p>However, this is the point where you, the WP Tavern audience, get to join the conversation.  Before pushing too far with additional changes, it is important to get your feedback about what you want to see in the coming days, weeks, and months.  Ultimately, the goal is to serve you WordPress news and information in the best way possible.</p>\n\n\n\n<p>Feedback is certainly welcome.  If there is a missing element you want to see return, post it in the comments.  If there is something you would like to see added, don&rsquo;t be shy about letting us know.</p>\n\n\n\n<p>The <a href=\"https://wptavern.com/contact-me\">contact form</a> is also always open for private feedback or for letting us know about a problem with the site.</p>\n\n\n\n<h2>What Is Under the Hood?</h2>\n\n\n\n<p>To get the theme up and running, I reused a ton of code from my previous theme-related work before joining WP Tavern. It made sense to use a build system I already knew from top to bottom and not reinvent the wheel.</p>\n\n\n\n<p>The CSS system is a customized and stripped-down version of <a href=\"https://tailwindcss.com/\">Tailwind CSS</a>.  Tailwind is a utility-first CSS framework.  For most of my professional career, I have shied away from utility-based frameworks.  However, Tailwind is a well-designed framework with a smart naming scheme that strikes a balance between readability and practicality.  It is one of the few that has clicked with me.  WordPress also uses several utility classes, especially with the block editor.  The two systems made sense together.</p>\n\n\n\n<p>WordPress front-end output and some plugins (I&rsquo;m looking at you, Jetpack) do not make it easy to take a full utility-class approach.  Everything else was addressed on a case-by-case basis.</p>\n\n\n\n<p>If any WordPress developers want to know more about the technical aspects, I am happy to answer questions.</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, 25 Nov 2019 20:32:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"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:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"bbPress: bbPress 2.6.2 is out!\";s:7:\"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:29:\"https://bbpress.org/?p=206111\";s:7:\"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:54:\"https://bbpress.org/blog/2019/11/bbpress-2-6-2-is-out/\";s: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:1342:\"<p>bbPress 2.6.2 fixes <a href=\"https://bbpress.trac.wordpress.org/query?status=closed&group=resolution&milestone=2.6.2\">5 more small bugs</a> that were reported by community members in our support forums:</p>\n\n\n\n<ul><li>Hierarchical replies in threaded discussion topics were broken for sites that were enabling the visual editor, so we unbroke it.</li><li>Sites with custom <code>bbpress.css</code> files were not having their custom styling applied in some cases. We fixed at least one case that we could find. Let us know if this is still not working correctly for you.</li><li>BuddyPress Notifications stopped working completely, but that wasn&#8217;t on purpose so we made them work completely again.</li><li>The &#8220;Edit&#8221; part of a URL pattern was not customizable inside of Forum Settings. Now it is!</li><li>One of the repair tools had a typo in it, so we untypo&#8217;ed it.</li></ul>\n\n\n\n<p>Thanks to everyone in the forums for being persistent and helping us identify all these annoyances. </p>\n\n\n\n<p>We&#8217;re going to continue minor releases as bugs get reported and fixed. The team is committed to making sure your forums are running as smoothly as can be, so don&#8217;t be surprised if you see 2.6.3 soon too! <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f41d.png\" alt=\"?\" class=\"wp-smiley\" /></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Nov 2019 18: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:17:\"John James Jacoby\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"WPTavern: Optimizing Code in a World That Doesn’t Want to Optimize\";s:7:\"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:29:\"https://wptavern.com/?p=95433\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://wptavern.com/optimizing-code-in-a-world-that-doesnt-want-to-optimize\";s: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:6757:\"<p><em>Premature optimization is the root of all evil.</em></p>\n\n\n\n<p>It is a common saying among developers.  It makes sense.  Optimizing prematurely can mean redoing work down the line, and time is the developer&rsquo;s most finite resource.  It can mean spending that precious time optimizing for scenarios that do not yet exist for a product&rsquo;s users.  It can mean writing code that is harder to understand with unclear performance gains.</p>\n\n\n\n<p>While participating with the WordPress theme review team about a year ago, I came across that nugget of advice once again.  <em>Premature optimization is the root of all evil.</em>  The reply was to a theme author who was looking to decrease the number and weight of scripts their theme needed to load.  On one hand, the theme author could load a 1.29 kb script with no dependencies to get the job done.  The other option was to use the jQuery-dependent script included in core WordPress for a total of 105 kb because &ldquo;most&rdquo; WordPress sites are loading jQuery anyway.</p>\n\n\n\n<p>For me, the answer was simple.  Use the smaller script unless the core script was already loaded on the front end.  I did not think of it in terms of <em>premature optimization</em>.  I thought of it as plain old, run-of-the-mill, everyday optimization.</p>\n\n\n\n<p>Developers should not confuse <em>premature optimization</em> with the concept of making smart design decisions early in the process.  Nor should they wait until the final stage of development to start optimizing, a time when the focus is on getting a product out to end-users.  That is a sign of a poor product design process.</p>\n\n\n\n<p>Over the past year, that conversation stuck with me.  It helped me become more cognizant of a terrifying trend, not just in the WordPress developer community, but with web development in general.  Far too often, developers are so far removed from normal users and the technology those users rely on that optimization is little more than an afterthought.  Instead, it should always be at the forefront of any developer&rsquo;s mind.</p>\n\n\n\n<p>The overreliance on this misused quote has helped push the trend of measuring page weight in megabytes instead of kilobytes.  It is too often used as a catchall justification for not doing any optimization in the development phase while making up for it with file compression and caching in production.</p>\n\n\n\n<p>Part of writing quality code is optimizing that code during every stage of the development process.  It is about making hard decisions to cut unnecessary things as the software comes together.  Caching should be a last resort after everything else has been cleaned up.</p>\n\n\n\n<p>Premature optimization is more about attempting to optimize when there are no clear gains or working on micro-optimizations that alter the software&rsquo;s design for little-to-no benefit.  It does not mean overlooking obvious performance boosts during development.</p>\n\n\n\n<h2>Not Everyone is on Gigabit Internet</h2>\n\n\n\n<p>Most developers I know are on super-fast internet connections, often with 1 Gbps download speeds and unlimited data.  In that situation, it is easy to forget that large chunks of the world are still on slow connections with data caps.</p>\n\n\n\n<p>Some may even associate slow connections with third-world countries where millions of people are on 2G cell phone technology.  However, there are large swaths of the United States and other developed countries that have no direct cable or DSL lines, which are commonly available in cities and suburbs.</p>\n\n\n\n<p>This disconnect is directly evident when other developers have initiated chats with me.  In the past couple of years, it has been increasingly common for them to ask for a video chat.  It is not even questioned whether such a thing is possible (video chats are unreliable at best for me).  The ability to video chat at any time is taken for granted.</p>\n\n\n\n<p>There are two internet service options in the area that I live in:  satellite or dial-up.  Even the local telephone company refuses to offer DSL in this area because of infrastructural costs with decades-old phone lines.  Because of the prohibitive costs of satellite internet access, which typically comes with data limits, many are stuck with dial-up.  Cell phone companies are changing the game to a degree, assuming service is reliable, but there are downfalls with going that route, which can include data or hotspot limitations.</p>\n\n\n\n<p>For such a technologically-advanced country, many of its people are barely catching up to where others were a decade ago.</p>\n\n\n\n<p>While I am fortunate enough to choose where I live and have nothing holding me back from moving, most do not have that option.  They are stuck with the best they can afford.  Even in rural areas, the internet is an inescapable part of daily life, and developers are not making it easy for these people.</p>\n\n\n\n<p>While this is anecdotal, it is the stark reality of rural life in pockets of the US.</p>\n\n\n\n<p>The upside of living in the backwoods of Alabama is that it has changed my perspective as a developer.  It has meant that I needed to question every code decision for every plugin and theme I built.  With data caps, I needed to make sure that I was not using too many resources.  </p>\n\n\n\n<p>More than anything, having a data cap changed how I used the internet.  I now run an ad-blocker.  I have an extension to kill videos from auto-loading.  I disable JavaScript on heavy sites that I need to use.  Some sites seem interesting, but I never return to them because they are resource hogs.</p>\n\n\n\n<p>When you live in a place where every byte matters, you tend to avoid wasting them.</p>\n\n\n\n<p>While not always successful, since my transition to small-town life, I have attempted to build applications in a way that served people who are not privileged enough to have blazing-fast internet access.</p>\n\n\n\n<p>Pointing this out is about making sure developers are aware that optimization matters.  It matters at every stage of the development process.  It matters because these people with slow connections and data caps also need to buy products, use services, read content, and do all the other things that people do on the web.</p>\n\n\n\n<p>If you are a developer who is thinking about adding that slider, swiping mechanism for mobile, or some other slick gadget, think about those of who must wait for that feature to load.  Check that its dependencies are not loading too many extra resources.  Do some research to see if you can locate a lighter-weight implementation.  But, first, ask yourself if it is necessary.</p>\n\n\n\n<p>The themes and plugins that WordPress developers build should never be the bottleneck for a website.  We can do better.</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, 21 Nov 2019 21:31: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:36;a:6:{s:4:\"data\";s:11:\"\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"HeroPress: Five Years Since The Dream Began\";s:7:\"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:29:\"https://heropress.com/?p=3019\";s:7:\"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:131:\"https://heropress.com/five-years-since-the-dream-began/#utm_source=rss&utm_medium=rss&utm_campaign=five-years-since-the-dream-began\";s: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:3140:\"<p>Exactly five years ago today I woke up to an email from Dave Rosen telling me my life was about to change.  He didn&#8217;t know yet what we&#8217;d build, but he offered me the chance to build something.</p>\n\n\n\n<p>From that seed we crafted HeroPress. It was a battle, filled with uncertainty, and at times tears, but I can say without hesitation that HeroPress has changed my life, and the life of my family, for the better.</p>\n\n\n\n<p>Never, ever did I expect to become friends with so many people from so many places. HeroPress has changed the way I look at the world, and the people in it. It&#8217;s influenced my job opportunities. It&#8217;s opened doors for me to places that I didn&#8217;t know existed.</p>\n\n\n\n<p>As always, I want to say thank you.  Thank you to Dave for planting the seed.  Thank you to all the contributors over the years, building something great.  Thank you to people willing to retweet for me every week. Thank you to all the people who&#8217;ve trusted me with their stories.</p>\n\n\n\n<p>Here&#8217;s hoping for another five years!</p>\n\n\n\n<img />Dave Rosen and I doing the X-Team X.\n<div class=\"rtsocial-container rtsocial-container-align-right rtsocial-horizontal\"><div class=\"rtsocial-twitter-horizontal\"><div class=\"rtsocial-twitter-horizontal-button\"><a title=\"Tweet: Five Years Since The Dream Began\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=Five%20Years%20Since%20The%20Dream%20Began&via=heropress&url=https%3A%2F%2Fheropress.com%2Ffive-years-since-the-dream-began%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: Five Years Since The Dream Began\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Ffive-years-since-the-dream-began%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-linkedin-horizontal\"><div class=\"rtsocial-linkedin-horizontal-button\"><a class=\"rtsocial-linkedin-button\" href=\"https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Ffive-years-since-the-dream-began%2F&title=Five+Years+Since+The+Dream+Began\" rel=\"nofollow\" target=\"_blank\" title=\"Share: Five Years Since The Dream Began\"></a></div></div><div class=\"rtsocial-pinterest-horizontal\"><div class=\"rtsocial-pinterest-horizontal-button\"><a class=\"rtsocial-pinterest-button\" href=\"https://pinterest.com/pin/create/button/?url=https://heropress.com/five-years-since-the-dream-began/&media=https://heropress.com/wp-content/plugins/rtsocial/images/default-pinterest.png&description=Five Years Since The Dream Began\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: Five Years Since The Dream Began\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/five-years-since-the-dream-began/\" title=\"Five Years Since The Dream Began\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/five-years-since-the-dream-began/\">Five Years Since The Dream Began</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:\"Thu, 21 Nov 2019 15:21: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:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WPTavern: WP Agency Summit Kicks Off December 6\";s:7:\"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:29:\"https://wptavern.com/?p=95420\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com/wp-agency-summit-kicks-off-december-6\";s: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:4819:\"<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p><a href=\"https://wpagencysummit.com/\">WP Agency Summit</a>, a virtual event for WordPress agencies, will kick off December 6, 2019, and last through December 16.  The event will feature daily sessions by over 30 WordPress professionals that are designed to help agencies grow their business.  Each session will be free to view, but there will be a price tag attached after the event closes.</p>\n\n\n\n<p>Jan Koch, owner WP Mastery, is running the event.  WP Agency Summit is for profit, but Koch expressed a desire to give something back to the community that has helped him over the years.  &ldquo;I want this event to deliver value to the WP community, because I myself have received free support countless times from Facebook groups, forums, etc.,&rdquo; he said.  &ldquo;That&rsquo;s why the event is free to watch online while it&rsquo;s running.&rdquo;</p>\n\n\n\n<p>The event is primarily aimed at WordPress agencies, but others may find value in it.  &ldquo;This event is also interesting for WordPress freelancers and digital agencies who occasionally use WordPress,&rdquo; said Koch.  &ldquo;However, being a WordPress agency owner myself, I wanted to ensure that business owners like myself and those in similar situations get the most value from the event.&rdquo;</p>\n\n\n\n<p>Video sessions will be available to view for 48 hours at no cost.  For those who sign up for a free pass, they can upgrade to lifetime access for $127. That lifetime access will go up to $197 during the event and $497 afterward.</p>\n\n\n\n<p>Potential buyers may want to opt for the free option before deciding whether future access to the sessions and bonus materials are worth plunking down the cash.  For an agency, the cost is minimal either way.  However, for a solo freelancer, the $497 price is high enough to warrant caution.  Most will want to check out the material first.</p>\n\n\n\n<p>Each of the video sessions is prerecorded and edited rather than shot live.  Koch is using Vimeo Pro to host the videos.  There will be a live hangout to begin the event.  Attendees and speakers will also get a Facebook group invite for asking questions and engaging with each other.</p>\n\n\n\n<p>Cloudways, Siteground, and MainWP are sponsoring the event, which helps cover some of the up-front costs.  Outside of that, Koch is handling the remainder of those costs out of his pocket but is hopeful for a positive return through the sale of lifetime access to the materials.</p>\n\n\n\n<p>Koch first ran a virtual summit called &ldquo;The WP Summit&rdquo; in 2015, which was a more broad event based on various WordPress topics.  That event had over 2,000 registrations.  &ldquo;As you can imagine, just talking about topics related to WP resulted in a very wide-spread speaker lineup, so there weren&rsquo;t any clear takeaways,&rdquo; said Koch.</p>\n\n\n\n<p>The idea for WP Agency Summit has been in Koch&rsquo;s mind since 2018.  It wasn&rsquo;t until some conversations with others at WordCamp Europe (WCEU) in 2019 that it started coming together.  &ldquo;After WCEU, I invested in a virtual training for summits and hired a mentor to properly set up the WP Agency Summit,&rdquo; he said.  &ldquo;My goal is to run 4 events like this in 2020, so this summit is serving as &lsquo;crash test dummy&rsquo; and foundation at the same time.&rdquo;</p>\n\n\n\n<h2>The Speaker Lineup</h2>\n\n\n\n<p>There are over 30 speakers signed on for the event.  Kim Doyal, a content marketer formerly known as &ldquo;The WordPress Chick,&rdquo; will teach agencies how to write copy that attracts higher-paying clients.  Ahmad Awais, core WordPress contributor, will teach how to save time writing code in the VS Code editor.</p>\n\n\n\n<p>Most sessions will focus on how agencies can grow their business with topics related to recurring revenue, marketing, and working with clients.  Each day of the event will feature three or four sessions.</p>\n\n\n\n<p>WP Agency Summit is hosting a diverse male lineup of over 20 speakers from Europe, Asia, Australia, Africa, and the US.  However, there are only four sessions lead by women within the industry.  &ldquo;I recognize this as a problem with my event,&rdquo; said Koch.  &ldquo;The reason I have so much more male than female speakers is quite simple, the current speaker line-up is purely based on connections I had when I started planning for the event. It was a relatively short amount of time for me, so I wasn&rsquo;t able to build relationships with more female WP experts beforehand.&rdquo;</p>\n\n\n\n<p>Koch assures that he will have a more balanced ratio for upcoming summits in 2020 and beyond.  &ldquo;Even in this prelaunch phase, I already got in touch with many outstanding women in the WP community which would make perfect speakers for the next events,&rdquo; he 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:\"Wed, 20 Nov 2019 19:50:08 +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:38;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:110:\"HeroPress: Building A WordPress Business In Iran – ساختن یک زندگی وردپرسی در ایران\";s:7:\"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=3012\";s:7:\"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:148:\"https://heropress.com/essays/building-a-wordpress-business-in-iran/#utm_source=rss&utm_medium=rss&utm_campaign=building-a-wordpress-business-in-iran\";s: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:19728:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2019/11/112019-min-1024x512.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull quote: Over the years, WordPress transformed my personal and profesional life. In Persian: در طی این سالها، وردپرس زندگی شخصی و حرفه‌ای من را تغییر داد.\" /><div class=\"c-message__content c-message__content--feature_sonic_inputs\">\n<div class=\"c-message__message_blocks c-message__message_blocks--rich_text\">\n<div class=\"p-block_kit_renderer p-block_kit_renderer--absorb_margin\">\n<div class=\"p-block_kit_renderer__block_wrapper p-block_kit_renderer__block_wrapper--first\">\n<div class=\"p-rich_text_block\" dir=\"auto\">\n<div class=\"p-rich_text_section\"><a href=\"https://heropress.com/feed/#fas\">این مقاله به زبان فارسی نیز در دسترس است.</a></div>\n</div>\n</div>\n</div>\n</div>\n</div>\n<p>I purchased my first computer set when I was 19 years old, but several years before that, at the age of 15, I took a computer and MS-DOS training course and without having a computer, by merely practicing on paper, I managed to get the perfect score on the final exam.</p>\n<p>It was during those years that internet gradually entered our town. Well, don’t be shocked. Internet was introduced to our small town pretty late and we got acquainted with this technological phenomenon very late. However, internet instantly found its place in my daily routine and I was fascinated by it.  After surfing the internet for a year, I was little by little encouraged to find out what a website is and how it works. Thus, I familiarized myself with the first programming language, that is, HTML and began learning it and given my enthusiasm, I mastered it in less than 10 days.</p>\n<p>I was increasingly attracted to the internet and the issues pertinent to it, and soon enough I was drawn to various internet technologies. In less than a year, I was able to learn PHP, CSS, and HTML and relying on my limited knowledge, I began testing different systems and scripts.</p>\n<h3>Introduction to Blogging</h3>\n<p>During those same years, I worked with various blog systems, one of which was B2 system. A little while later, while conducting tests, doing installations, and having fun, I encountered a system which was quite similar to B2. I installed it. Then, I entered its various parts.  I found its management system, templates and codes quite appealing and easy to work with. Thus, I began translating it into Persian for my personal purposes, and in less than a week, I turned most of its various parts into Persian and they were ready to be used. Yet, due to certain reasons, I failed to install this system on my host or test it online. But I kept the system on my computer and I worked with it and enjoyed it. Yes, that system was one of the first versions of WordPress.</p>\n<p>Prior to working with WordPress, I had worked with various systems and scripts, and I was primarily accustomed to Joomla. However, simplicity, convenience, and interesting environment of WordPress drew me towards this system and I kept working with it.</p>\n<p>I was by nature shy and reticent; therefore, I was not that active in any groups or forums –this was the case in my personal life as well as on the web. Consequently, during the first few years of my activity in the field of WordPress, I hardly ever participated in WordPress forums or local groups.</p>\n<h3>Getting Involved</h3>\n<p>However, one of my friends who was active in the field of Persian WordPress, invited me to collaborate with one of the Persian WordPress support forums and this was a new beginning for me in the area of localization of WordPress.</p>\n<p>My keen interest in working with WordPress as well as helping others work and become more familiar with it made me spend a lot of time daily in the Persian WordPress forum. Nevertheless, due to the shortcomings and needs of the Persian WordPress community, we also created another support website. Following the creation of this new website, many users were attracted to it and gradually we got a lot of feedback from the Persian WordPress community. So, we became further involved with the Persian WordPress community and the scope of our activities expanded.</p>\n<p>It was during these years that I got my first formal job offer in the field of WordPress and I launched the first WordPress website for a client and received money in return for my services.  This experience highly motivated me and helped me envision my future as a WordPress developer. Meanwhile, with the help of some of my friends, I started a small web design and development company which was supposed to focus on coding and programming electronic components, but my keen enthusiasm for web development drew the entire team to focus on web design and development. Due to my numerous activities in the field of WordPress and my growing recognition as a WordPress activist, over the course of a few years, virtually all of our company activities centered on WordPress as the main basis of our work, and now we are one of the active supporters of WordPress in Iran.</p>\n<h3>Transformations</h3>\n<p>Over the years, WordPress transformed my personal and professional life. My personal life was changed in the respect that from a shy, quiet and inactive guy, I turned into an energetic, active person interested in discussions and participation in social events. Along the way, I also met great and influential people, including my future spouse.</p>\n<p>We organized various gatherings and meetups in the field of WordPress. We held WordPress seminars. We set up various public forums and groups to enhance the impact of WordPress and educate newcomers, and thus, many changes occurred in my overall mood and personality.</p>\n<p>Besides, prior to the general change of direction in our company towards web and especially WordPress, our revenues were low and the company had a very slow growth; yet following our change of direction and basing the structure of the company on WordPress, our annual growth rate increased dramatically and there was a considerable increase in the size of the company, number of the personnel, and payments.</p>\n<p>I should also mention that I am a graduate of textile engineering. However, my field of study has nothing to do with my career interests. Since from a very young age I dreamt of working in the field of computer science, even studying an irrelevant major did not stop me from pursuing my old dream and while studying textile engineering, I worked in the field of computer science and in my own company.</p>\n<p>Now, 16 years after my first encounter with WordPress, it has pervaded every aspect of my life and has changed me personally, mentally, and professionally and has influenced my choice of career and business. And I am really glad that on that day I became familiar with WordPress and started working with it and am still involved with it up to this day, because not only my life changed as a result, but also I managed to educate so many people and help them transform their lives in a way that WordPress played a major role in their lives and contributed to their further success.</p>\n<h1 id=\"fas\">ساختن یک زندگی وردپرسی در ایران</h1>\n<p>من اولین کامپیوتر خود را وقتی ۱۹ ساله بودم خریدم ولی چندین سال قبل از آن  در سن 15 سالگی به کلاس آموزش کامپیوتر و دوره آموزشی کار با DOS رفتم  و بدون داشتن کامپیوتر و با تمرین روی کاغذ توانستم نمره کامل رو در آزمون نهایی کسب کنم.</p>\n<p>در همان سالها بود که اینترنت کم کم وارد شهر ما شد، بله تعجب نکنید درشهرکوچک ما اینترنت خیلی دیر وارد شد و ما خیلی دیر با این پدیده آشنا شدیم اما اینترنت به سرعت جای خود را در کارهای روزمره من باز کرد و من شیفته آن شدم بعد از یک سال کار کردن با اینترنت من کم کم ترغیب شدم که بفهمم سایت چیست و چگونه کار میکند و با اولین زبان یعنی HTML آشنا شدم و شروع به یادگیری آن کردم و با اشتیاق فراوانی که داشتم آن را در کمتر از ۱۰ روز یاد گرفتم.</p>\n<p>من هر روز بیشتر جذب اینترنت و موضوعات مرتبط با آن می شدم و به سرعت به سوی تکنولوژی های مختلف اینترنتی کشیده شدم. یک سال هم طول نکشید که توانستم HTML / CSS / PHP را یاد بگیرم و با همون دانش اندک، شروع به تست سیستم و اسکریپتهای مختلف کردم.</p>\n<h3>مقدمه‌ای برای شروع</h3>\n<p>در همان سال‌ها من با سیستم‌های وبلاگی مختلفی کار کردم که یکی از آن‌ها سیستم b2 بود. کمی بعدتر در همین تستها و نصب‌ها و بازیگوشی ها  با سیستمی مواجه شدم که بسیار شبیه b2 بود. آن را نصب کردم سپس وارد بخش‌های مختلف آن شدم، سیستم مدیریت، بخش قالب و کدهای آن و بسیار برایم ساده و جالب و جذاب به نظر رسید و به همین دلیل شروع به فارسی کردن آن برای کارهای شخصی خود کردم و کمتر از یک هفته بخش‌های مختلف آن را تا حدود زیادی فارسی و آماده استفاده کرده بودم. اما به دلایل خاصی موفق نشدم که آن را بر روی هاست خود نصب و به صورت آنلاین تست کنم. ولی آن سیستم را بر روی کامپیوتر خود نگه داشتم و با آن کار می کردم و لذت می بردم. بله آن سیستم یکی از اولین نسخه های وردپرس بود.</p>\n<p>من قبل از کار با وردپرس با سیستم ها و اسکریپت های مختلفی کار کرده بودم و بیشترین اسکریپتی که با آن انس گرفته بودم جوملا بود اما سادگی و روانی و محیط جذاب مدیریت وردپرس باعث شد که من به سمت وردپرس کشیده شوم و کار با آن را ادامه دهم.</p>\n<p>من ذاتا آدم کم حرف و خجالتی بودم و به همین دلیل خیلی در گروه ها و انجمن های خاصی فعالیت نمی‌کردم و این هم شامل وب و هم شامل زندگی عادی من میشد به همین دلیل تا چند سال اولیه فعالیت من در وردپرس، خیلی در انجمنهای تخصصی و یا گروه های محلی آن  فعالیتی نداشتم.</p>\n<h3>شروع مشارکت</h3>\n<p>تا اینکه یکی از دوستان من که از فعالان وردپرس در زبان فارسی بود من را دعوت به همکاری در یکی از انجمن های پشتیبانی وردپرس به زبان فارسی کرد و این شروعی دوباره برای من در زمینه محلی سازی وردپرس بود.</p>\n<p>علاقه زیاد من به کار با وردپرس و همچنین کمک به دیگران برای کار و آشنایی بیشتر با وردپرس باعث شد که من روزانه زمان زیادی را در انجمن وردپرس فارسی صرف کنم. اما با توجه به کمبود ها و نیازهایی که جامعه فارسی داشت ما یک سایت پشتیبانی دیگر را نیز ایجاد کردیم با ایجاد سایت جدید کاربران زیادی جذب ما شدند و کم کم ما بازخوردهای زیادی را از جامعه فارسی گرفتیم به همین دلیل بیشتر درگیر جامعه فارسی وردپرس شدیم و دامنه فعالیت های ما نیز گسترش پیدا کرد.</p>\n<h3>دگرگونی</h3>\n<p>در همین سال‌ها اولین پیشنهاد کاری رسمی من در زمینه وردپرس رسید و من اولین سایت خود را برای یک مشتری با وردپرس برپا کردم و در قبال آن مبلغی را دریافت کردم که این موضوع باعث شد انگیزه زیادی در من شکل بگیرد و مسیر حرکتی آینده خود را در وردپرس ببینم. همزمان، با کمک چند نفر از دوستان خود یک شرکت طراحی و برنامه نویسی کوچک را تاسیس کردیم که روند آن قرار بود بر کدنویسی و برنامه نویسی برای قطعات الکترونیکی باشد اما اشتیاق فراوان من به طراحی وب باعث شد که نظر کلیه جمع نیز به سمت کدنویسی و طراحی وب کشیده شود. با توجه به فعالیت‌های زیاد من در وردپرس و بیشتر شناخته شدن من به عنوان یک فعال وردپرسی، در طی یک بازه زمانی چند ساله، کلیه فعالیت های شرکت ما نیز به سمت وردپرس کشیده شد و مبنای اصلی کارهای ما وردپرس شد و هم اکنون ما یکی از حامیان فعال وردپرس در ایران هستیم.</p>\n<p>طی سالیان مختلف وردپرس زندگی شخصی و کاری من را تغییر داد. زندگی شخصی من را از این جهت تغییر داد که از یک آدم خجالتی و کم حرف و کم فعالیت به یک آدم فعال، پر انرژی و علاقمند به بحث و گفتگو و حضور در اجتماعات تبدیل شوم. در این مسیر با افراد بزرگ و تاثیرگذار منجمله با همسر آینده خود نیز آشنا شدم.</p>\n<p>اجتماعات و میتاپهای مختلفی را در زمینه وردپرس راه اندازی نمودیم. سمینار های وردپرسی برگزار کردیم. انجمن ها و گروه‌های مردمی مختلفی را در جهت افزایش نفوذ وردپرس و آموزش آن به افراد تازه کار راه اندازی کردیم و به همین دلیل تغییرات زیادی در روحیه و خلقیات و شخصیت کلی من ایجاد شد.</p>\n<p>همچنین تا قبل از تغییر روند کلی شرکت ما به سمت وب و علی‌الخصوص وردپرس، شرکت درآمد خاصی نداشت و بسیار کند رشد می کرد اما پس از تغییر رویه و راه اندازی بستر اصلی شرکت بر روی وردپرس روند سالانه ما به شدت رشد کرد و هم از نظر اندازه و هم تعداد کارکنان و هم از نظر سطح دستمزد و حقوق پیشرفت چشمگیری در شرکت ایجاد شد.</p>\n<p>این را هم اضافه کنم که من فارغ التحصیل در رشته مهندی نساجی هستم. اما رشته تحصیلی من با رشته و علاقمندی کا ی من کاملا از هم جدا و نامرتبط هستند. چون من از جوانی آرزو و شوق کار کردن در زمینه کامپیوتر را داشتم و حتی تحصیل در رشته ای نامرتبط هم سبب نشد که دست از آرزوی قدیمی خود بردارم  و حتی همزمان با تحصیل در رشته نساجی، در زمینه کامپیوتر و در شرکت خود مشغول به کار بودم.</p>\n<p>حالا ۱۶ سال از اولین برخورد و کار من با وردپرس می‌گذرد و وردپرس تقریباً در همه زمینه های مختلف زندگی من نفوذ کرده و باعث تغییر من در زمینه شخصی، روحی و کاری و کسب و کار  من شده است و از این بابت بسیار خوشحال هستم که آن روز توانستم با وردپرس آشنا شده و شروع به کار کنم و تا به امروز نیز درگیر آن باشم.</p>\n<p>زیرا علاوه بر اینکه زندگی من تغییر کرد، توانستم افراد زیادی را نیز آموزش داده و به آنها کمک کنم تا زندگی‌ آنها نیز تغییر کند و وردپرس شاکله زندگی آنها را تشکیل داده و باعث موفقیت بیشتر آنها شود.</p>\n<p>&nbsp;</p>\n<div class=\"rtsocial-container rtsocial-container-align-right rtsocial-horizontal\">\n<div class=\"rtsocial-twitter-horizontal\">\n<div class=\"rtsocial-twitter-horizontal-button\"><a title=\"Tweet: Building A WordPress Business In Iran &#8211; ساختن یک زندگی وردپرسی در ایران\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=Building%20A%20WordPress%20Business%20In%20Iran%20%2D%20%D8%B3%D8%A7%D8%AE%D8%AA%D9%86%20%DB%8C%DA%A9%20%D8%B2%D9%86%D8%AF%DA%AF%DB%8C%20%D9%88%D8%B1%D8%AF%D9%BE%D8%B1%D8%B3%DB%8C%20%D8%AF%D8%B1%20%D8%A7%DB%8C%D8%B1%D8%A7%D9%86&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbuilding-a-wordpress-business-in-iran%2F\" rel=\"nofollow\" target=\"_blank\"></a></div>\n</div>\n<div class=\"rtsocial-fb-horizontal fb-light\">\n<div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: Building A WordPress Business In Iran &#8211; ساختن یک زندگی وردپرسی در ایران\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fbuilding-a-wordpress-business-in-iran%2F\" rel=\"nofollow\" target=\"_blank\"></a></div>\n</div>\n<div class=\"rtsocial-linkedin-horizontal\">\n<div class=\"rtsocial-linkedin-horizontal-button\"><a class=\"rtsocial-linkedin-button\" href=\"https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbuilding-a-wordpress-business-in-iran%2F&title=Building+A+WordPress+Business+In+Iran+%26%238211%3B+%D8%B3%D8%A7%D8%AE%D8%AA%D9%86+%DB%8C%DA%A9+%D8%B2%D9%86%D8%AF%DA%AF%DB%8C+%D9%88%D8%B1%D8%AF%D9%BE%D8%B1%D8%B3%DB%8C+%D8%AF%D8%B1+%D8%A7%DB%8C%D8%B1%D8%A7%D9%86\" rel=\"nofollow\" target=\"_blank\" title=\"Share: Building A WordPress Business In Iran &#8211; ساختن یک زندگی وردپرسی در ایران\"></a></div>\n</div>\n<div class=\"rtsocial-pinterest-horizontal\">\n<div class=\"rtsocial-pinterest-horizontal-button\"><a class=\"rtsocial-pinterest-button\" href=\"https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/building-a-wordpress-business-in-iran/&media=https://heropress.com/wp-content/uploads/2019/11/112019-min-150x150.jpg&description=Building A WordPress Business In Iran - ساختن یک زندگی وردپرسی در ایران\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: Building A WordPress Business In Iran &#8211; ساختن یک زندگی وردپرسی در ایران\"></a></div>\n</div>\n<p><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/essays/building-a-wordpress-business-in-iran/\" title=\"Building A WordPress Business In Iran &#8211; ساختن یک زندگی وردپرسی در ایران\"></a></div>\n<p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/building-a-wordpress-business-in-iran/\">Building A WordPress Business In Iran &#8211; ساختن یک زندگی وردپرسی در ایران</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, 20 Nov 2019 04:30:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Morteza Geransayeh\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: 10up Releases GitHub Actions for Simplifying WordPress Plugin Deployment\";s:7:\"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:29:\"https://wptavern.com/?p=95388\";s:7:\"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:93:\"https://wptavern.com/10up-releases-github-actions-for-simplifying-wordpress-plugin-deployment\";s: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:6671:\"<p>10up announced the <a href=\"https://10up.com/blog/2019/wordpress-github-actions-streamline-plugin-deployment/\">public availability of two GitHub Actions</a> geared toward WordPress plugin developers yesterday.  The first Action allows developers to deploy plugin updates directly to the WordPress.org plugin directory by tagging a release on GitHub.  The second Action handles readme file and asset updates. </p>\n\n\n\n<p>On November 14, GitHub <a href=\"https://github.blog/2019-11-14-powering-community-led-innovation-with-github-actions/\">announced the public launch</a> of their GitHub Actions feature.  GitHub Actions are a way for developers to automate workflows from their Git repositories.  Actions can also be shared with others, reused across projects, and forked like any other public repository.</p>\n\n\n\n<p>Currently, there are over 1,300 GitHub Actions with more being added every day.  At least <a href=\"https://github.com/marketplace?utf8=%E2%9C%93&type=actions&query=wordpress\">nine of the current Actions</a> are related to WordPress, including an Action to <a href=\"https://wptavern.com/rtcamp-releases-github-actions-for-automated-code-review-deploying-wordpress-and-slack-notifications\">deploy WordPress by rtCamp</a>, but there will certainly be more to come in the future.</p>\n\n\n\n<p>With GitHub Actions out of beta, it opens the door for companies like 10up to share their custom workflows and for others to build upon them.  It will also be interesting to see what Actions other developers within the WordPress ecosystem release.</p>\n\n\n\n<p>The 10up team initially <a href=\"https://10up.com/blog/2019/introducing-github-actions-for-wordpress-plugins/\">launched their custom Actions</a> for WordPress in March 2019, which was during GitHub Actions beta period.  &ldquo;Everybody has been very positive,&rdquo; said Helen Hou-Sand&iacute;, director of open source initiatives at 10up and WordPress lead developer.  &ldquo;We&rsquo;ve had a number of people report bugs, request enhancements, and contribute code and documentation. That&rsquo;s been a really great measure of adoption and attention for me &mdash; having people give thoughtful critical feedback and help us improve this tool for everybody.&rdquo;</p>\n\n\n\n<p>Hou-Sand&iacute; is interested in seeing other ideas for adding workflows or potentially new Actions from the community.  &ldquo;An example of something we&rsquo;ve just started doing without writing a whole new Action is generating hook documentation and deploying that to GitHub Pages, which eliminates the need to generate locally, commit manually, and decide on where to host things,&rdquo; she said.</p>\n\n\n\n<p>&ldquo;Development was actually smoother than I anticipated,&rdquo; said Hou-Sand&iacute; of creating and testing the team&rsquo;s GitHub Actions.  &ldquo;Maybe because I spent a fairly long time planning and obsessing over potential issues and chose to use Bash.&rdquo;  For testing, she was able to use an inactive plugin repo on WordPress.org.  &ldquo;I&rsquo;m sure I could have come up with a method to test completely locally, but being able to use actual environments without repercussions was helpful.&rdquo;</p>\n\n\n\n<p>The 10up team has already been deploying plugin updates with the Actions.  Hou-Sand&iacute; said that she does not think about this in terms of saving time, even though the team is already tagging releases via GitHub.  </p>\n\n\n\n<p>&ldquo;What it&rsquo;s really done for us is, along with well-documented release processes, made it so that anybody can jump in and get a plugin updated or released without worrying about modifying commit permissions or their personal knowledge of SVN,&rdquo; she said.  &ldquo;This makes it much easier to get releases out especially when it&rsquo;s an urgent bugfix.&rdquo;</p>\n\n\n\n<h2>Deploying and Updating WordPress Plugins</h2>\n\n\n\n<p>Both of the GitHub Actions created by 10up help ease the pain of deploying plugin updates to the official WordPress plugin directory.  They are designed to streamline plugin release management and simplify the process of getting code out to end-users.</p>\n\n\n\n<p>WordPress plugin authors must use Subversion (SVN) to commit and tag plugin releases in the directory.  Often, this is an issue because Git is the most-used version control system.  Some developers have no experience with SVN, and the number of developers unfamiliar with it will likely only grow as Git continues to gain popularity.  Even with those who do understand SVN, switching between version control systems can hinder workflows, particularly with larger teams.</p>\n\n\n\n<p>With so many WordPress plugin developers using Git, it makes sense to use tools that are a part of their daily workflow rather than jumping into a system only used during releases.  That is where both of these GitHub Actions developed by 10up can help.  </p>\n\n\n\n<p>Adding Actions to a repository is a fairly straightforward process.  All repositories have a new &ldquo;Actions&rdquo; tab.  Developers can create new workflows directly from the Actions page for their repository.  When adding a new workflow, it is simply a matter of copying and pasting a particular Action&rsquo;s code snippet.</p>\n\n\n\n<div class=\"wp-block-image\"><img />Adding a custom GitHub workflow.</div>\n\n\n\n<p>The <a href=\"https://github.com/marketplace/actions/wordpress-plugin-deploy\">WordPress Plugin Deploy</a> Action is for deploying plugin updates directly to the WordPress plugin directory.  When developers tag a release on GitHub, it will automatically commit the update to the WordPress.org SVN repository.  The Action respects <code>.distignore</code> and <code>.gitattributes</code> for ignoring files that should not be distributed to users.  It also allows developers to add their plugin assets to a <code>.wordpress-org</code> folder, which will be committed to the top-level <code>assets</code> directory.</p>\n\n\n\n<p><a href=\"https://github.com/marketplace/actions/wordpress-plugin-readme-assets-update\">WordPress.org Plugin Readme/Assets Update</a> is a separate Action that allows developers to commit changes to their plugin&rsquo;s readme or assets.  It is useful when plugin authors need to update their plugin&rsquo;s <code>Tested up to</code> version number or update screenshots, banners, and icons.  This Action watches for changes on a specified branch.</p>\n\n\n\n<p>Both Actions require developers to set up secret values for their WordPress SVN username and password.  Secrets are encrypted data that can be set via a repository&rsquo;s &ldquo;Settings &gt; Secrets&rdquo; screen.  The SVN username and password are required so that GitHub can deploy commits to WordPress.org.</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, 19 Nov 2019 23:00: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: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:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"WordPress.org blog: WordPress 5.2.4 Update\";s:7:\"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=7787\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2019/11/wordpress-5-2-4-update/\";s: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:1100:\"<p>Late-breaking news on the<a href=\"https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/\"> 5.2.4 short-cycle security release </a>that landed October 14. When we released the news post, I inadvertently missed giving props to Simon Scannell of <a href=\"https://blog.ripstech.com/\">RIPS Technologies</a> for finding and disclosing an issue where path traversal can lead to remote code execution. </p>\n\n\n\n<p>Simon has done a <a href=\"https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/\">great</a> <a href=\"https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/\">deal</a> of <a href=\"https://wordpress.org/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/\">work</a> on the WordPress project, and failing to mention his contributions is a huge oversight on our end.</p>\n\n\n\n<p>Thank you to all of the reporters for <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">privately disclosing</a> vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.</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, 19 Nov 2019 04:47: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:\"Jake Spurlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"WPTavern: Gutenberg 6.9 Introduces Image Titles, Block Patterns, and New Theme Features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=95365\";s:7:\"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:96:\"https://wptavern.com/gutenberg-6-9-introduces-image-titles-block-patterns-and-new-theme-features\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5671:\"<p>On November 13, the Gutenberg team <a href=\"https://make.wordpress.org/core/2019/11/13/whats-new-in-gutenberg-13-november/\">launched version 6.9</a> with several features, most of which were aimed at developers.  Users can now add custom image title attributes.  Plugin developers can start diving into the new Block Patterns API.  Plus, theme authors can begin tinkering with the experimental gradient presets and block templates features.</p>\n\n\n\n<p>Gutenberg 6.9 fixed numerous bugs, including an annoying <a href=\"https://github.com/WordPress/gutenberg/issues/16429\">invalid content error</a> when selecting a color for the pullquote block.  The update included several enhancements and changes to the underlying codebase.</p>\n\n\n\n<p>Much of the work in version 6.9 went toward experimental features, including the navigation block.  At this point, the nav block still needs a ton of work for practical use.  The interface is still a bit clunky.  Undoubtedly, this is one of the toughest user experience challenges to solve and will take time before it is ready for widespread usage.  Right now, it is about continually iterating upon the work from previous versions.</p>\n\n\n\n<h2>Image Title Attribute Field</h2>\n\n\n\n<div class=\"wp-block-image\"><img />Editing the image title field in Gutenberg.</div>\n\n\n\n<p>The ability to add image titles is perhaps the biggest user-facing feature added in Gutenberg 6.9.  The <a href=\"https://github.com/WordPress/gutenberg/issues/11054\">original ticket</a> for adding the feature has been simmering for over a year.</p>\n\n\n\n<p>The Gutenberg team added the title field under the &ldquo;Advanced&rdquo; tab when editing an image block. This was a smart decision because image titles are often used incorrectly to describe an image, which is the job of the &ldquo;Alt Text&rdquo; field located under the &ldquo;Image Settings&rdquo; tab.  Image titles are also generally unnecessary.  When used, they should describe the role of the image on the page.</p>\n\n\n\n<h2>Initial Block Patterns API Merged</h2>\n\n\n\n<div class=\"wp-block-image\"><img />Choosing a column layout in the block editor.</div>\n\n\n\n<p>The Block Patterns API is a developer feature primarily for creating initial setup states for complex blocks.  For example, the columns block has several common patterns that users may want to choose. By providing those patterns when first inserting a block, the user does not have to go through the routine of configuring all of the settings for it.</p>\n\n\n\n<p>The idea is to cut back on the complexities of configuring some blocks so that users can more quickly get to the point of adding their custom content and getting their desired results.</p>\n\n\n\n<p>The first step toward the Block Patterns API was <a href=\"https://github.com/WordPress/gutenberg/pull/18270\">merged into Gutenberg 6.9</a>, but it is still in the experimental stage at this point.</p>\n\n\n\n<h2>Block Gradient Presets</h2>\n\n\n\n<div class=\"wp-block-image\"><img />Adding a gradient background to a button in Gutenberg.</div>\n\n\n\n<p>Gutenberg introduced gradient backgrounds in <a href=\"https://wptavern.com/gutenberg-6-7-introduces-storybook-and-gradient-backgrounds\">version 6.7</a> for the button block. The feature launched with a set of gradients that did not match users&rsquo; themes, which meant the feature was little more than a fun experiment.</p>\n\n\n\n<p>In version 6.9, developers can register custom gradients that are less of an eyesore by using colors that fit into the theme&rsquo;s color palette.</p>\n\n\n\n<p>Currently, <a href=\"https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-gradient-presets\">block gradient presets</a> are marked as an experimental feature and use the <code>__experimental-editor-gradient-presets</code> theme support flag.  Now is a good time for theme authors to begin exploring this feature so they can be ready when the experimental flag is removed.</p>\n\n\n\n<h2>Block Templates for Themes</h2>\n\n\n\n<p>For theme authors, block templates were the most exciting aspect of Gutenberg&rsquo;s potential when it first launched.  Throughout all of WordPress&rsquo; history, creating custom page templates, particularly front page templates, has been an exercise in frustration.  Theme authors have always had great ideas about what their themes&rsquo; front pages should look like.  In a way, it is an author&rsquo;s signature on a theme project.  It is often what sets one theme apart from another.</p>\n\n\n\n<p>However, creating an interface that allows users to change what is traditionally a blog post list to something more ornate and complex is not an easy thing to do.  Hundreds, perhaps thousands, of varying implementations are currently in the wild, each with their take on how to create a custom front page.</p>\n\n\n\n<p>Enter Gutenberg.  Theme authors, regardless of whether they love or hate it, usually see the potential of a block-based editor in terms of laying out a front page.  The idea of having complete control over where specific blocks sit and how they appear on the front end is an alluring one, especially if there is a standardized experience for users to figure out how to plug their content into the blocks.</p>\n\n\n\n<p>Gutenberg 6.9 <a href=\"https://github.com/WordPress/gutenberg/pull/18247\">laid the groundwork</a> toward this reality by resolving block templates from a theme&rsquo;s <code>/block-templates</code> folder.</p>\n\n\n\n<p>At this point, theme block templates are still in the experimental stage as part of the <a href=\"https://github.com/WordPress/gutenberg/issues/17512\">full site editing feature</a>.  From a theme development perspective, this could be revolutionary.</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, 18 Nov 2019 19:03:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"Post Status: Scott Bolinger on WordPress, JAMstack, and the future of the independent developer\";s:7:\"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=71326\";s:7:\"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:42:\"https://poststatus.com/wordpress-jamstack/\";s: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:1790:\"<p>In this episode, Scott and I dig into his experience as an indie developer within the WordPress landscape.</p>\n\n\n\n<p>Scott has long used JavaScript as a core technology with AppPresser. I think he\'s on the forefront of thinking about and using technologies that are new to WordPress but out in full force in other ecosystems. </p>\n\n\n\n<p>Scott is really into <a href=\"https://jamstack.org/\">JAMstack</a> (JavaScript, APIs, Markup). He\'s working on <a href=\"https://staticfuse.com/\">Static Fuse</a> now, which helps connect WordPress to <a href=\"https://www.gatsbyjs.org/\">Gatsby</a>. Gatsby has a <em>lot</em> of attention in web tech right now.</p>\n\n\n\n<p>We also dig pretty deeply into the challenges and opportunities facing independent developers, and the interest levels in WordPress from the indie dev crowd. It\'s an interesting episode, and I learned a lot from Scott. I hope you do too. Enjoy our conversation!</p>\n\n\n\n\n\n\n\n<h3>Other links from the show</h3>\n\n\n\n<ul><li><a href=\"https://graphql.org/\">GraphQL</a> and <a href=\"https://www.wpgraphql.com/\">WPGraphQL</a></li><li><a href=\"https://scottbolinger.com/\">Scott\'s website</a></li><li><a href=\"https://theproductbusiness.com/podcast/\">The Product Business podcast</a></li><li>Zac Gordon\'s <a href=\"https://javascriptforwp.com/product-category/courses/\">JavascriptforWP</a> courses</li></ul>\n\n\n\n<h3>Sponsor: Sandhills Development</h3>\n\n\n\n<p><a href=\"http://sandhillsdev.com/\">Sandhills Development</a>&nbsp;makes a suite of excellent plugins to power your WordPress website. Whether you need to sell digital downloads, restrict content, create an affiliate program, or manage an events calendar, they’ve got you covered. Thanks to&nbsp;<a href=\"http://sandhillsdev.com/\">Sandhills</a>&nbsp;for being a Post Status partner.</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, 16 Nov 2019 16:36: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: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:43;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"WPTavern: 24 WordPress Snippets ’til Christmas, Submissions Open for 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=95346\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/24-wordpress-snippets-til-christmas-submissions-open-for-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5943:\"<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>After a multi-year hiatus, Elliott Richmond has relaunched his WordPress advent calendar and is looking for volunteers.  The <a href=\"https://advent.elliottrichmond.co.uk/\">WP Snippets &rsquo;til Christmas</a> site will host 24 days of WordPress code snippets starting on December 1 and lasting until December 24.  With each passing day, a new code snippet will be revealed.</p>\n\n\n\n<p>Advent calendars are special types of calendars used to count down the days until Christmas.  They are often a part of religious celebrations but can be used for other purposes such as family traditions and games.  For Richmond&rsquo;s advent calendar, it is a way to contribute something back to the WordPress community.</p>\n\n\n\n<p>Richmond opened the site for developers to make contributions to the 24-day event.  &ldquo;I&rsquo;ve been in touch with the original contributors in the hope that they&rsquo;ll submit again and registration is also open to anyone else who wishes to contribute,&rdquo; he said.  &ldquo;Otherwise, it will just be the Elliott Richmond show.&rdquo;  </p>\n\n\n\n<p>He would rather have community submissions than attempting to write all 24 code snippets alone.  Jeff Starr, Zac Gordon, and Tom McFarlin, all prominent developers in the WordPress community, have already signed on to submit code.  <em>Author&rsquo;s note: I am also considering joining because it sounds like fun.</em></p>\n\n\n\n<p>Anyone who wants to receive updates each day of the event can register for free on the <a href=\"https://advent.elliottrichmond.co.uk/\">WP Snippets &rsquo;til Christmas</a> website.  The same signup form is available for contributors.</p>\n\n\n\n<p>There are no limitations on the types of code snippets that contributors can submit, only that they should be related to WordPress.  Richmond says he has some ideas such as a WP-CLI script and a deployment tool for use on the command line.  However, code snippets can be something as simple as sticking a basic function into a theme to more complex scripts.</p>\n\n\n\n<p>&ldquo;I come from a frontend world and I&rsquo;m a self-taught PHP developer,&rdquo; said Richmond.  &ldquo;I&rsquo;m evolving constantly and always eager to learn new things. I think WordPress is similar, it&rsquo;s always evolving and inspiring innovation. If you put any limitations on things they rapidly become stagnated.&rdquo;</p>\n\n\n\n<p>The code snippets are not aimed at any type of WordPress user in particular.  &ldquo;I think it&rsquo;s really useful to see bite-size code snippets to help those in the community who are taking that next step into development,&rdquo; said Richmond.  &ldquo;To those more seasoned developers, I think it&rsquo;s always useful to see how other developers approach things.&rdquo;</p>\n\n\n\n<p>Each code snippet will have an open comments section similar to a traditional blog.  This will allow others to say thanks for sharing or to jump-start a conversation.</p>\n\n\n\n<h2>The Road Back to the Advent Calendar</h2>\n\n\n\n<p>Richmond has been a WordPress user and developer since the launch of the platform.  He is the director of <a href=\"https://squareone.software/\">Square One Software</a>, a software development company that specializes in WordPress development.</p>\n\n\n\n<p>He <a href=\"https://wptavern.com/wordpress-snippets-til-christmas-submissions-opened-for-2013\">last ran the advent calendar</a> in 2013.  After the success of the first year in 2012, he decided to put it together for a second round.  He wanted to keep it going beyond the first two years, but work and other commitments took priority.</p>\n\n\n\n<p>In the years since, Richmond met other local WordPress enthusiasts at WordCamp London.  He now helps host the local meetup in Cheltenham, UK.  With the help of the community, he organized four teams of local project managers, designers, developers, and content writers for a <a href=\"https://doaction.org/event/cheltenham-2019/\">local do_action event</a>.  &ldquo;I&rsquo;m still an enthusiastic proponent of giving back to the community and actively encourage others in our local community to share their experience and knowledge,&rdquo; said Richmond.</p>\n\n\n\n<p><a href=\"https://doaction.org/\">do_action</a> events are charity hackathons that use WordPress to help provide local charity organizations an online presence.</p>\n\n\n\n<p>&ldquo;Every single team and team member did an amazing job on the day for four local non-profit charities, putting together a functional WordPress website for each charity while I personally gave a charity representative some hands-on training,&rdquo; said Richmond.  &ldquo;Taking away some of the overhead of creating a website for the charities allows them to concentrate on what they do best, which is raising money for their own community.&rdquo;</p>\n\n\n\n<p>Richmond described needing to find something to do next while still riding the buzz from the event.  That is when he decided to relaunch the WP Snippets &rsquo;til Christmas event.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p>Because it is the season, Richmond crowned &ldquo;It&rsquo;s a Wonderful Life&rdquo; as the greatest Christmas movie.</p>\n\n\n\n<p>&ldquo;I love classics and this one is a true classic, pretty apt in the current move to make people aware of mental health,&rdquo; said Richmond.  &ldquo;The movie starts with depression and pending suicide when a guardian angel is bestowed to the main character George Bailey. George is shown how many lives he&rsquo;s impacted on in his own local community and how things would have been if he didn&rsquo;t exist, a real heartwarming feel-good reflection on the things that we take for granted in our own existence.&rdquo;</p>\n\n\n\n<p>With this upcoming holiday season, considering taking the time to give back to both your local community and the WordPress community.  One great way to do that is to contribute a code snippet to WP Snippets &rsquo;til Christmas.</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, 15 Nov 2019 21:10:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"bbPress: bbPress 2.6.1 is out!\";s:7:\"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:29:\"https://bbpress.org/?p=205662\";s:7:\"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:54:\"https://bbpress.org/blog/2019/11/bbpress-2-6-1-is-out/\";s: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:2442:\"<p>It seems like only <a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6/\">yesterday that 2.6.0</a> was released, and depending on where you live that might actually be true! <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f5d3.png\" alt=\"?\" class=\"wp-smiley\" /></p>\n\n\n\n<p>bbPress 2.6.1 fixes a few small (but very annoying bugs) that warranted some immediate attention:</p>\n\n\n\n<ul><li><a href=\"https://bbpress.trac.wordpress.org/ticket/3232\">One</a> was causing subforums not to be listed underneath their parents anymore.</li><li><a href=\"https://bbpress.trac.wordpress.org/ticket/3281\">Another</a> was causing styling issues for a few of the themes that come bundled with WordPress itself.</li><li><a href=\"https://bbpress.trac.wordpress.org/ticket/3280\">The last one</a> was causing issues with posting content within WordPress Admin, because of incompatibility with a few plugins that were interacting with the REST API in admin area pages in fun ways that we hadn&#8217;t anticipated yet.</li></ul>\n\n\n\n<p>Thanks to the quick reporting of <a href=\"https://bbpress.org/forums/profile/stevehammatt/\">stevehammatt</a> and <a href=\"https://bbpress.org/forums/profile/pdvwp/\">pdvwp</a>, we were able to identify all of these problems and get them into bbPress 2.6.1 right away. You both rock! <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f44f.png\" alt=\"?\" class=\"wp-smiley\" /></p>\n\n\n\n<p class=\"has-text-color has-background has-very-dark-gray-color has-very-light-gray-background-color\">One bug still remains that we could use your help with, that is affecting sites that have a custom <code>bbpress.css</code> file in their theme. If you need to fix this ASAP, you can rename it to <code>bbpress.min.css</code> temporarily. If you&#8217;re able to chime into <a href=\"https://bbpress.org/forums/topic/child-css/\">this topic in the forums</a>, that would be super helpful!</p>\n\n\n\n<p>If you have a few moments, the great Justin Tadlock from WPTavern <a href=\"https://wptavern.com/bbpress-2-6-released-after-6-years-includes-per-forum-moderation-and-engagements-api\">asked me a few questions about bbPress 2.6</a>, so consider giving it a read.</p>\n\n\n\n<p>Lastly, thank you everyone for the positive comments and responses to seeing bbPress 2.6 finally happen. It made my day, and I really appreciate it. <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f49a.png\" alt=\"?\" class=\"wp-smiley\" /></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Nov 2019 23:48: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:17:\"John James Jacoby\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"WPTavern: bbPress 2.6 Released After 6 Years, Includes Per-Forum Moderation and Engagements API\";s:7:\"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:29:\"https://wptavern.com/?p=95336\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"https://wptavern.com/bbpress-2-6-released-after-6-years-includes-per-forum-moderation-and-engagements-api\";s: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:7007:\"<p>On Tuesday, John James Jacoby announced that bbPress 2.6 was available to the public after a six-year wait in a post titled <a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6/\">bbPress 2.6 &mdash; Better Great Than Never</a>.  The announcement landed with a whimper as it was overshadowed by the release of WordPress 5.3 on the same day.</p>\n\n\n\n<p><a href=\"https://wordpress.org/plugins/bbpress/\">bbPress</a> is an official WordPress project for powering forums.  It was <a href=\"https://bbpress.org/blog/2004/12/soft-launch/\">initially launched</a> on December 28, 2004, by Matt Mullenweg as a standalone project.  During the first iteration&rsquo;s heyday, it was popular within the WordPress community as a simple forum solution.  In 2011, <a href=\"https://bbpress.org/blog/2011/09/bbpress-2-0-now-available/\">bbPress 2.0 relaunched</a> as a WordPress plugin with Jacoby as the lead developer.</p>\n\n\n\n<p>The bbPress team is primarily comprised of four part-time contributors with nearly no volunteers available for user testing.  Stephen Edgar, Brandon Allen, and Sergey Biryukov were the primary developers other than Jacoby behind version 2.6.</p>\n\n\n\n<p>&ldquo;Jennifer M. Dodd deserves a mention for her contributions to 2.6 early on; she&rsquo;s largely moved on but is wonderful,&rdquo; said Jacoby.  &ldquo;Behind the scenes in the meta and forums teams are Samuel &lsquo;Otto&rsquo; Wood, Dion Hulse, Mika Epstein, Marius Jensen, and countless others who provide feedback and feature requests upstream based on how WordPress.org uses bbPress.&rdquo;</p>\n\n\n\n<p>Contributors resolved 420 open tickets with 1,737 code commits over the multi-year span it took for version 2.6 to drop.  The new version ships with hundreds of bug fixes and improvements.  Its features include per-forum moderation, new platforms to import forum content from, and an Engagements API.</p>\n\n\n\n<p>The new Engagements API connects user IDs to the various types of content in bbPress, such as forums, topics, replies, and topic tags.  This works as a sort of relationship system between users and any content they interact with on the forums.  In previous versions of bbPress, all of this data was saved in the user metadata table.</p>\n\n\n\n<p>Per-forum moderation is a key feature for forums, but it has been one of the missing elements in bbPress.  The new feature takes advantage of the Engagements API to connect user IDs to forum IDs.  In turn, this allows site owners to create moderators for individual forums.  This feature works in contrast to the existing &ldquo;moderator&rdquo; role in bbPress, which provides users global moderation powers.</p>\n\n\n\n<h2>Why the 6-Year Wait?</h2>\n\n\n\n<p>You could be forgiven for wondering if bbPress was all but dead.  The last minor release happened in 2017 when the team dropped version 2.5.14.  The same year, bbPress 2.6 was <a href=\"https://wptavern.com/bbpress-2-6-beta-3-likely-as-team-focuses-on-solid-data-migration-path\">headed toward a third beta</a> and even had a <a href=\"https://bbpress.org/forums/topic/bbpress-2-6-beta/\">few release candidates</a>.</p>\n\n\n\n<p>&ldquo;There was not very much feedback on the 2.6 beta or RC, and I had just transitioned into my role at Sandhills Development,&rdquo; said Jacoby. &ldquo;I decided it was better to concentrate on doing a good job where I could make a direct impact on people&rsquo;s lives, rather than have no idea if I was doing a good job at all with bbPress.&rdquo;</p>\n\n\n\n<p>Jacoby did not want to release a potentially buggy version 2.6 and take on the support burden at the time.  Doing so would have interfered with his responsibilities at his new job.  &ldquo;Younger me would have tried to do both, and failed at both,&rdquo; said Jacoby.</p>\n\n\n\n<p><em>Why such a long wait between releases?</em>  Most likely, it was for the same reason the <a href=\"https://twitter.com/bbPress/status/1194327563407122432\">Twitter announcement</a> got fewer than a couple of dozen likes and even fewer retweets.  There is not much community engagement with the project.  On the flip side, the bbPress team has not been active on social media or the project&rsquo;s official blog in the past two years.  </p>\n\n\n\n<p>Despite the lack of community engagement, bbPress is currently installed on over 300,000 sites.  It runs the forums at WordPress.org, WordPress.com, CSS-Tricks, and other large communities.  However, there is not much help sent back to the bbPress project from most places.</p>\n\n\n\n<p>&ldquo;On WordPress.org, bbPress is just one piece of a very complex puzzle, and everything is mostly in maintenance mode all the time,&rdquo; said Jacoby.  &ldquo;The forums team focuses on the needs of the forums and the meta team helps maintain the code itself, but WordPress has made it easier and more rewarding to contribute to; so contributors graduate up to WordPress core and rarely look back.&rdquo;</p>\n\n\n\n<p>The idea behind switching bbPress 2.x to a WordPress plugin from its standalone roots was that it would be simpler for the larger WordPress community to pitch in.  Jacoby said that contributions have improved since the pre-plugin era, but it has not helped enough.  &ldquo;There&rsquo;s more attention and accolades with WordPress and Gutenberg than there are with the bb&rsquo;s or GlotPress,&rdquo; he said.</p>\n\n\n\n<p>One of bbPress&rsquo; biggest problems is the lack of resources.  There is no commercial element to the plugin and no major companies are funding anyone to work on the project full time.</p>\n\n\n\n<p>&ldquo;For an open-source project to be sustainable long-term, it needs to have an economy behind it,&rdquo; said Jacoby.  &ldquo;Without an economy, what&rsquo;s the real goal? Market share? Building better forum software? Those are not enough by itself when people need to make a living, and when less work with WooCommerce can help you earn a better living.&rdquo;</p>\n\n\n\n<h2>The Future of Forums</h2>\n\n\n\n<p>Six years between major releases is a lifetime in technological years, plenty enough time for another company to claim the WordPress forum market share.  However, bbPress managed to keep its crown as the most-used WordPress forum plugin during the wait.  It does beg the question of whether companies or developers see a future for forums.</p>\n\n\n\n<p>With so many alternative options for user engagement, are forums a dying breed of software?</p>\n\n\n\n<p>&ldquo;If forums are dying, it&rsquo;s a slow death, according to the numbers anyway,&rdquo; said Jacoby.  &ldquo;Chat apps like Slack and Discord (or Twitch and YouTube) are where people do forum-type stuff these days. Moderating your own community takes dedication and work, and if you&rsquo;re going to do work, why not build an audience someplace else instead?&rdquo;</p>\n\n\n\n<p>Jacoby has hope for the future, however.  &ldquo;I can imagine a bunch of reasons why forums seem unattractive,&rdquo; he said, &ldquo;but to me they are still what everyone circles back around to, just like having their own blogs!&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, 14 Nov 2019 20: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: WordCamp US 2020 Date and Location Announced, New Weekday 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:29:\"https://wptavern.com/?p=95327\";s:7:\"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:86:\"https://wptavern.com/wordcamp-us-2020-date-and-location-announced-new-weekday-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:3394:\"<p>Mark your calendars, folks.  WordCamp US 2020 will start on a&hellip;<em>Tuesday</em>.</p>\n\n\n\n<p>On November 11, the WordCamp US team announced that next year&rsquo;s event will happen during the middle of the week, from October 27 through October 29.  This is a change from the usual three-day weekend event.  The time frame puts the event&rsquo;s days on Tuesday, Wednesday, and Thursday.  The yearly conference will remain in St. Louis, Missouri, in 2020.</p>\n\n\n\n<p>Those planning ahead can sign up for updates via the new <a href=\"https://2020.us.wordcamp.org/\">WordCamp US 2020 site</a>.</p>\n\n\n\n<p>Thus far, the switch away from a weekend has been met with generally positive <a href=\"https://twitter.com/WordCampUS/status/1193910076244996096\">responses via Twitter</a> and Slack. However, some people fear the schedule will not allow them to attend.  </p>\n\n\n\n<p>The WordCamp US Twitter account cited date availability, Halloween, and giving the weekend back to attendees as the reason behind the change.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Number of reasons from date availability, letting folks get home for Halloween, and letting folks have a their weekend back on an out-of-town event</p>&mdash; WordCamp US (@WordCampUS) <a href=\"https://twitter.com/WordCampUS/status/1193912839725101056?ref_src=twsrc%5Etfw\">November 11, 2019</a></blockquote>\n</div>\n\n\n\n<p>For professionals in the WordPress space, this move will likely be a welcome change.  They are often able to get extra time off from work, sometimes paid leave, to attend the event.  The company they work for may even be funding their travel.  For them, attending a WordCamp is a part of their work.  </p>\n\n\n\n<p>The unfortunate side effect of attending a WordCamp over the weekend is that some attendees usually have to wake up for work on Monday morning after traveling back home on Sunday.  Many are essentially working two weeks straight without any downtime.  This helps pile on the problem of developer burnout.  Rest days, time with friends and family, and getting away from code-related things is a part of a healthy work-life balance.</p>\n\n\n\n<p>Moving the event to the middle of the week should allow professionals to better maintain that balance.</p>\n\n\n\n<p>On the other hand, some attendees may find it harder to attend during the week.  This is particularly true for WordCamp-goers who do not work with WordPress professionally.  They may not be able to get the time off work.</p>\n\n\n\n<p>As a general rule, Americans tend to have little paid leave they can take advantage of throughout the year.  The average worker in the private sector only gets <a href=\"https://www.cnbc.com/2018/07/05/heres-how-many-paid-vacation-days-the-typical-american-worker-gets-.html\">10 paid vacation days</a> per year after one year of employment.  Those numbers rise the longer an employee sticks with a single company.  The US does not guarantee paid leave for workers.</p>\n\n\n\n<p>Without support from their employer, some people may have to choose between using their paid time off to attend and keeping those days in reserve for family vacation or holidays.</p>\n\n\n\n<p>Unlike local WordCamps, the US conference is more of an industry event that sees professionals from across the US and the world.  The move to a weekday schedule should be a nice change for many.</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, 13 Nov 2019 21:27:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"WPTavern: WordPress 5.3 “Kirk” Released, Brings New Default Theme, Editor Improvements, and UI Tweaks\";s:7:\"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:29:\"https://wptavern.com/?p=95290\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://wptavern.com/wordpress-5-3-kirk-released-brings-new-default-theme-editor-improvements-and-ui-tweaks\";s: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:7770:\"<div class=\"wp-block-image\"><img />Rahsaan Roland Kirk<br />Credit:  <a href=\"https://www.flickr.com/photos/heiner1947/4485444348/in/photostream/\">Heinrich Klaffs</a> CC BY-SA 2.0</div>\n\n\n\n<p><a href=\"https://wordpress.org/news/2019/11/kirk/\">WordPress 5.3 &ldquo;Kirk,&rdquo;</a> named in honor American jazz musician Rahsaan Roland Kirk, is now available for download.  The update includes a new default theme named Twenty Twenty, user interface improvements aimed at accessibility, and new block editor features.</p>\n\n\n\n<p>This release saw contributions from 645 volunteers, which is the largest contributor group ever for a WordPress release.</p>\n\n\n\n<p>The release was led by <a href=\"https://ma.tt\">Matt Mullenweg</a>, <a href=\"https://profiles.wordpress.org/francina/\">Francesca Marano</a>, and <a href=\"https://profiles.wordpress.org/davidbaumwald\">David Baumwald</a>.  They were joined by the following contributors in supporting roles in getting version 5.3 released.</p>\n\n\n\n<ul><li>Editor Tech Lead &ndash; <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a></li><li>Editor Design Lead &ndash; <a href=\"https://profiles.wordpress.org/mapk/\">Mark Uraine</a></li><li>Core Tech Lead &ndash; <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a></li><li>Default Theme Design Lead &ndash; <a href=\"https://profiles.wordpress.org/anlino/\">Anders Nor&eacute;n</a></li><li>Default Theme Wrangler &ndash; <a href=\"https://profiles.wordpress.org/ianbelanger/\">Ian Belanger</a></li><li>Docs Coordinator &ndash; <a href=\"https://profiles.wordpress.org/justinahinon/\">Justin Ahinon</a></li><li>Accessibility Lead &ndash; <a href=\"https://profiles.wordpress.org/audrasjb/\">JB Audras</a></li><li>Marketing Lead &ndash; <a href=\"https://profiles.wordpress.org/mikerbg/\">Mike Reid</a></li><li>Media Focus Lead &ndash; <a href=\"https://profiles.wordpress.org/mikeschroder/\">Mike Schroder</a></li></ul>\n\n\n\n<p>WordPress 5.2 had 84 million downloads before WordPress 5.3&rsquo;s release.</p>\n\n\n\n<p>The PHP native JSON extension is now required for any site running WordPress 5.3 or later.  This should not be an issue for the majority of users because the extension has been bundled with PHP by default since 2006.  WordPress will output an error and cancel the update procedure if it detects the extension is missing.  Users who are unable to update will need to contact their web hosts to have the extension enabled.</p>\n\n\n\n<h2>Twenty Twenty: New Default Theme</h2>\n\n\n\n<div class=\"wp-block-image\"><img />Screenshot of the Twenty Twenty WordPress theme.</div>\n\n\n\n<p>WordPress is getting a fresh coat of paint.  Anders Nor&eacute;n led the design team for the new <a href=\"https://wptavern.com/twenty-twenty-bundled-in-core-beta-features-overview\">Twenty Twenty</a> theme, which was a <a href=\"https://wptavern.com/first-look-at-twenty-twenty-new-wordpress-default-theme-based-on-chaplain\">fork of his original Chaplin theme</a>.</p>\n\n\n\n<p>The Twenty Twenty theme is completely geared toward creating content with the block editor with its bold and opinionated styling.  It comes with a cover page template and has a custom color system designed to keep the site&rsquo;s color contrast accessible.</p>\n\n\n\n<h2>Block Editor Features and Improvements</h2>\n\n\n\n<div class=\"wp-block-image\"><img />Nesting any block inside the Cover block.</div>\n\n\n\n<p>WordPress 5.3 includes features from the versions 5.4 &ndash; 6.5 of the Gutenberg plugin along with bug fixes and performance improvements from versions 6.6 and 6.7.  For users who have not been running the plugin, they should see faster loading times and quicker responses from keystrokes.</p>\n\n\n\n<p>WP Tavern has covered every major release of the Gutenberg plugin that will be bundled in WordPress 5.3, except Gutenberg 5.6.  Catch up on any features you missed with the following articles.</p>\n\n\n\n<ul><li><a href=\"https://wptavern.com/gutenberg-5-5-adds-new-group-block-for-nesting-child-blocks\">Gutenberg 5.5 Adds New Group Block for Nesting Child Blocks</a></li><li><a href=\"https://wptavern.com/gutenberg-5-7-adds-new-block-appender-for-group-and-columns-blocks\">Gutenberg 5.7 Adds New Block Appender for Group and Columns Blocks</a></li><li><a href=\"https://wptavern.com/gutenberg-5-8-released-with-prototype-of-new-block-based-widgets-screen\">Gutenberg 5.8 Released with Prototype of New Block-based Widgets Screen</a></li><li><a href=\"https://wptavern.com/gutenberg-5-9-brings-major-improvements-to-block-grouping-introduces-snackbar-notices\">Gutenberg 5.9 Brings Major Improvements to Block Grouping, Introduces Snackbar Notices</a></li><li><a href=\"https://wptavern.com/gutenberg-6-0-adds-layout-picker-to-columns-block\">Gutenberg 6.0 Adds Layout Picker to Columns Block </a></li><li><a href=\"https://wptavern.com/gutenberg-6-1-introduces-animation-to-block-moving-actions-adds-block-based-widgets-screen-experiments\">Gutenberg 6.1 Introduces Animation to Block Moving Actions, Adds Block-Based Widgets Screen Experiments</a></li><li><a href=\"https://wptavern.com/gutenberg-6-2-adds-nesting-capabilities-to-cover-media-text-blocks\">Gutenberg 6.2 Adds Nesting Capabilities to Cover, Media &amp; Text Blocks</a></li><li><a href=\"https://wptavern.com/gutenberg-6-3-improves-accessibility-with-new-navigation-and-edit-modes\">Gutenberg 6.3 Improves Accessibility with New Navigation and Edit Modes</a></li><li><a href=\"https://wptavern.com/gutenberg-6-4-adds-new-typewriter-experience-cover-block-resizing-and-block-inserter-help-panel\">Gutenberg 6.4 Adds New Typewriter Experience, Cover Block Resizing, and Block Inserter Help Panel</a></li><li><a href=\"https://wptavern.com/gutenberg-6-5-adds-experimental-block-directory-search-to-inserter-and-new-social-links-block\">Gutenberg 6.5 Adds Experimental Block Directory Search to Inserter and New Social Links Block</a></li></ul>\n\n\n\n<h2>Other Core Features</h2>\n\n\n\n<p>Work toward <a href=\"https://wptavern.com/wordpress-5-3-improves-large-image-handling\">large image handling</a> went into the update.  Instead of checking file sizes, images larger than 2,560 pixels are scaled down and used as the &ldquo;full&rdquo; image size.  This change makes large images web ready and will significantly decrease file sizes for many users who upload images without optimizing them beforehand.  This is common with mobile phone uploads.  </p>\n\n\n\n<p>For those who prefer to maintain the original sizes of image uploads, which is sometimes the case with photography sites, grab the <a href=\"https://wordpress.org/plugins/disable-big-image-threshold/\">Disable &ldquo;BIG Image&rdquo; Threshold</a> plugin.</p>\n\n\n\n<p>The site health screen introduced in WordPress 5.2 has some user experience improvements, such as tweaking how the grading indicator works for clarity.  WordPress site owners will also need to <a href=\"https://wptavern.com/wordpress-5-3-to-introduce-new-admin-email-verification-screen\">verify their admin email</a> every six months.  This feature is to help make sure site recovery emails are being sent to the right place when an error occurs.  It also lays the groundwork for future features that may build upon it.</p>\n\n\n\n<h2>Developer Changes</h2>\n\n\n\n<p>Developers should read the full <a href=\"https://make.wordpress.org/core/2019/10/17/wordpress-5-3-field-guide/\">WordPress 5.3 field guide</a> to make sure none of the changes affect their plugins or themes. Some of the changes include the following.</p>\n\n\n\n<ul><li>Full support for PHP 7.4.</li><li>Improved date/time handling.</li><li>Robots meta tag now used for discouraging search engines from listing a site.</li><li>New meta key comparison operators added.</li><li>Integers are no longer allowed for nav menu slugs.</li><li><code>wp_die()</code> now allows custom HTML.</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, 12 Nov 2019 22:12:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"WordPress.org blog: WordPress 5.3 “Kirk”\";s:7:\"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=7684\";s:7:\"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:40:\"https://wordpress.org/news/2019/11/kirk/\";s: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:60337:\"<div class=\"wp-block-image\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2019/11/5.3-album-cover.png?resize=632%2C632&ssl=1\" alt=\"Album cover for WordPress 5.3 Kirk, showcasing a duotone red/cream Rahsaan Roland Kirk playing the saxophone on a red background.\" class=\"wp-image-7710\" /></div>\n\n\n\n<p class=\"has-text-color has-background\">Introducing our most refined user experience with the improved block editor in WordPress 5.3! Named “Kirk” in honour of jazz multi-instrumentalist Rahsaan Roland Kirk, the latest and greatest version of WordPress is available for <a href=\"https://wordpress.org/download/\">download</a> or update in your dashboard.</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/11/divider.png?resize=632%2C159&ssl=1\" alt=\"\" class=\"wp-image-7721\" />\n\n\n\n<p><strong>5.3 expands and refines the block editor</strong> with more intuitive <strong>interactions</strong> and improved <strong>accessibility</strong>. New features in the editor increase design freedoms, provide additional layout options and style variations to allow designers more control over the look of a site.</p>\n\n\n\n<p>This release also introduces the <strong>Twenty Twenty theme</strong> giving the user more design flexibility and integration with the block editor. Creating beautiful web pages and advanced layouts has never been easier.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Block Editor Improvements</h2>\n\n\n\n\n\n\n\n<p>This enhancement-focused update introduces over 150 new features and usability improvements, including improved large image support for uploading non-optimized, high-resolution pictures taken from your smartphone or other high-quality cameras. Combined with larger default image sizes, pictures always look their best.</p>\n\n\n\n<p>Accessibility improvements include the integration of block editor styles in the admin interface. These improved styles fix many accessibility issues: color contrast on form fields and buttons, consistency between editor and admin interfaces, new snackbar notices, standardizing to the default WordPress color scheme, and the introduction of Motion to make interacting with your blocks feel swift and natural. </p>\n\n\n\n<p>For people who use a keyboard to navigate the dashboard, the block editor now has a Navigation mode. This lets you jump from block to block without tabbing through every part of the block controls.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Expanded Design Flexibility</h2>\n\n\n\n\n\n\n\n<p>WordPress 5.3 adds even more robust tools for creating amazing designs.</p>\n\n\n\n<ul><li>The new Group block lets you easily divide your page into colorful sections.</li><li>The Columns block now supports fixed column widths.</li><li>The new predefined layouts make it a cinch to arrange content into advanced designs.</li><li>Heading blocks now offer controls for text and background color.</li><li>Additional style options allow you to set your preferred style for any block that supports this feature.</li></ul>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Introducing Twenty Twenty</h2>\n\n\n\n<div class=\"wp-block-image\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/11/twentytwenty-desktop.png?resize=632%2C626&ssl=1\" alt=\"A desktop preview of the Twenty Twenty theme, showing both the front-end and the editor view.\" class=\"wp-image-7686\" /></div>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile is-vertically-aligned-top\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2019/11/twentytwenty-mobile.png?w=632&ssl=1\" alt=\"A mobile image of the Twenty Twenty  theme, over a decorative backgorund of brown-grey bars.\" class=\"wp-image-7714\" /><div class=\"wp-block-media-text__content\">\n<p>As the block editor celebrates its first birthday, we are proud that Twenty Twenty is designed with flexibility at its core. Show off your services or products with a combination of columns, groups, and media blocks. Set your content to wide or full alignment for dynamic and engaging layouts. Or let your thoughts be the star with a centered content column!</p>\n\n\n\n<p class=\"has-normal-font-size\">As befits a theme called Twenty Twenty, clarity and readability is also a big focus. The theme includes the typeface&nbsp;<a href=\"https://rsms.me/inter/\">Inter</a>, designed by Rasmus Andersson. Inter comes in a Variable Font version, a first for default themes, which keeps load times short by containing all weights and styles of Inter in just two font files.</p>\n</div></div>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Improvements for Everyone</h2>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2019/11/Rotate.png?w=632&ssl=1\" alt=\"An icon showing an arrow rotating a square.\" class=\"wp-image-7731\" /><div class=\"wp-block-media-text__content\">\n<h3>Automatic Image Rotation</h3>\n\n\n\n<p>Your images will be correctly rotated upon upload according to the embedded orientation data. This feature was first proposed nine years ago and made possible through the perseverance of many dedicated contributors.</p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2019/11/Health.png?w=632&ssl=1\" alt=\"A plus in a square, indicating health.\" class=\"wp-image-7732\" /><div class=\"wp-block-media-text__content\">\n<h3>Improved Site Health Checks</h3>\n\n\n\n<p>The improvements introduced in 5.3 make it even easier to identify issues. Expanded recommendations highlight areas that may need troubleshooting on your site from the Health Check screen.</p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2019/11/Email.png?w=632&ssl=1\" alt=\"A email icon.\" class=\"wp-image-7733\" /><div class=\"wp-block-media-text__content\">\n<h3>Admin Email Verification</h3>\n\n\n\n<p>You’ll now be periodically asked to confirm that your admin email address is up to date when you log in as an administrator. This reduces the chance of getting locked out of your site if you change your email address.</p>\n</div></div>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>For Developers</h2>\n\n\n\n<div class=\"wp-block-columns\">\n<div class=\"wp-block-column\">\n<h3>Date/Time Component Fixes</h3>\n\n\n\n<p>Developers can now work with&nbsp;<a href=\"https://make.wordpress.org/core/2019/09/23/date-time-improvements-wp-5-3/\">dates and timezones</a>&nbsp;in a more reliable way. Date and time functionality has received a number of new API functions for unified timezone retrieval and PHP interoperability, as well as many bug fixes.</p>\n</div>\n\n\n\n<div class=\"wp-block-column\">\n<h3>PHP 7.4 Compatibility</h3>\n\n\n\n<p>WordPress 5.3 aims to fully support PHP 7.4. This release contains&nbsp;<a href=\"https://make.wordpress.org/core/2019/10/11/wordpress-and-php-7-4/\">multiple changes</a>&nbsp;to remove deprecated functionality and ensure compatibility. WordPress continues to encourage all users to run the latest and greatest versions of PHP.</p>\n</div>\n</div>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/11/divider.png?resize=632%2C159&ssl=1\" alt=\"\" class=\"wp-image-7721\" />\n\n\n\n<h2>The Squad</h2>\n\n\n\n<p>This release was led by&nbsp;<a href=\"http://ma.tt/\">Matt Mullenweg</a>,&nbsp;<a href=\"https://profiles.wordpress.org/francina\">Francesca Marano</a>, and <a href=\"https://dream-encode.com/blog/\">David Baumwald</a>. They were enthusiastically supported by a large release squad:</p>\n\n\n\n<ul><li><strong>Editor Tech</strong>: Riad Benguella (<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://profiles.wordpress.org/youknowriad/\"><strong>@youknowriad</strong></a>)</li><li><strong>Editor Design</strong>: Mark Uraine (<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://profiles.wordpress.org/mapk/\"><strong>@mapk</strong></a>)</li><li><strong>Core Tech</strong>: Andrew Ozz (<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://profiles.wordpress.org/azaozz/\"><strong>@azaozz</strong></a>)</li><li><strong>Docs Coordinator</strong>:&nbsp;Justin Ahinon (<a href=\"https://profiles.wordpress.org/justinahinon/\"><strong>@justinahinon</strong></a>)</li><li><strong>Marketing/Release Comms</strong>:&nbsp;Mike Reid (<a href=\"https://profiles.wordpress.org/mikerbg/\"><strong>@mikerbg</strong></a>)</li><li><strong>Media/Uploader</strong>:&nbsp;Mike Schroder (<a href=\"https://profiles.wordpress.org/mikeschroder/\"><strong>@mikeschroder</strong></a>)</li><li><strong>Accessibility</strong>:&nbsp;JB Audras (<a href=\"https://profiles.wordpress.org/audrasjb/\"><strong>@audrasjb</strong></a>)</li><li><strong>Default Theme</strong> <strong>Wrangler</strong>: Ian Belanger (<a href=\"https://profiles.wordpress.org/ianbelanger/\"><strong>@ianbelanger</strong></a>)</li><li><strong>Default Theme Designer</strong>: Anders Norén (<a href=\"https://profiles.wordpress.org/anlino/\"><strong>@anlino</strong></a>)</li></ul>\n\n\n\n<p>The squad was joined throughout the twelve week release cycle by 645 generous volunteer contributors (our largest group of contributors to date) who collectively fixed 658 bugs.</p>\n\n\n\n<p>Put on a Rahsaan Roland Kirk playlist, click that update button (or <a href=\"https://wordpress.org/download/\">download it directly</a>), and check the profiles of the fine folks that helped:</p>\n\n\n<a href=\"https://profiles.wordpress.org/123host/\">123host</a>, <a href=\"https://profiles.wordpress.org/1994rstefan/\">1994rstefan</a>, <a href=\"https://profiles.wordpress.org/5hel2l2y/\">5hel2l2y</a>, <a href=\"https://profiles.wordpress.org/irsdl/\">@irsdl</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/aksdvp/\">Aashish S</a>, <a href=\"https://profiles.wordpress.org/abhijitrakas/\">Abhijit Rakas</a>, <a href=\"https://profiles.wordpress.org/abrightclearweb/\">abrightclearweb</a>, <a href=\"https://profiles.wordpress.org/acalfieri/\">acalfieri</a>, <a href=\"https://profiles.wordpress.org/acosmin/\">acosmin</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/adamsoucie/\">Adam Soucie</a>, <a href=\"https://profiles.wordpress.org/adhitya03/\">Adhitya Rachman</a>, <a href=\"https://profiles.wordpress.org/mrahmadawais/\">Ahmad Awais</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/atachibana/\">Akira Tachibana</a>, <a href=\"https://profiles.wordpress.org/aljullu/\">Albert Juh&#233; Lluveras</a>, <a href=\"https://profiles.wordpress.org/albertomake/\">albertomake</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/xavortm/\">Alex Dimitrov</a>, <a href=\"https://profiles.wordpress.org/ajlende/\">Alex Lende</a>, <a href=\"https://profiles.wordpress.org/alexclassroom/\">Alex Lion</a>, <a href=\"https://profiles.wordpress.org/viper007bond/\">Alex Mills</a>, <a href=\"https://profiles.wordpress.org/alexsanford1/\">Alex Sanford</a>, <a href=\"https://profiles.wordpress.org/xyfi/\">Alexander Botteram</a>, <a href=\"https://profiles.wordpress.org/xel1045/\">Alexandre D\'Eschambeault</a>, <a href=\"https://profiles.wordpress.org/alexvorn2/\">Alexandru Vornicescu</a>, <a href=\"https://profiles.wordpress.org/alexeyskr/\">alexeyskr</a>, <a href=\"https://profiles.wordpress.org/alextran/\">alextran</a>, <a href=\"https://profiles.wordpress.org/ayubi/\">Ali Ayubi</a>, <a href=\"https://profiles.wordpress.org/allancole/\">allancole</a>, <a href=\"https://profiles.wordpress.org/allendav/\">Allen Snook</a>, <a href=\"https://profiles.wordpress.org/alvarogois/\">Alvaro Gois dos Santos</a>, <a href=\"https://profiles.wordpress.org/arush/\">Amanda Rush</a>, <a href=\"https://profiles.wordpress.org/amolv/\">Amol Vhankalas</a>, <a href=\"https://profiles.wordpress.org/anantajitjg/\">Anantajit JG</a>, <a href=\"https://profiles.wordpress.org/anlino/\">Anders Norén</a>, <a href=\"https://profiles.wordpress.org/afercia/\">Andrea Fercia</a>, <a href=\"https://profiles.wordpress.org/andg/\">Andrea Gandino</a>, <a href=\"https://profiles.wordpress.org/agengineering/\">Andrea Grillo</a>, <a href=\"https://profiles.wordpress.org/andreamiddleton/\">Andrea Middleton</a>, <a href=\"https://profiles.wordpress.org/abrain/\">Andreas Brain</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/andrewtaylor-1/\">Andrew Taylor</a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey 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/angelagibson/\">Angela Gibson</a>, <a href=\"https://profiles.wordpress.org/rilwis/\">Anh Tran</a>, <a href=\"https://profiles.wordpress.org/anischarolia/\">anischarolia</a>, <a href=\"https://profiles.wordpress.org/ahdeubzer/\">Anja Deubzer</a>, <a href=\"https://profiles.wordpress.org/antpb/\">Anthony Burchell</a>, <a href=\"https://profiles.wordpress.org/atimmer/\">Anton Timmermans</a>, <a href=\"https://profiles.wordpress.org/apermo/\">Apermo</a>, <a href=\"https://profiles.wordpress.org/arafat/\">Arafat Rahman</a>, <a href=\"https://profiles.wordpress.org/aravindajith/\">Aravind Ajith</a>, <a href=\"https://profiles.wordpress.org/archon810/\">archon810</a>, <a href=\"https://profiles.wordpress.org/arena/\">arena</a>, <a href=\"https://profiles.wordpress.org/aristath/\">Ari Stathopoulos</a>, <a href=\"https://profiles.wordpress.org/arunsathiya/\">Arun Sathiya</a>, <a href=\"https://profiles.wordpress.org/artisticasad/\">Asad Shahbaz</a>, <a href=\"https://profiles.wordpress.org/asadkn/\">asadkn</a>, <a href=\"https://profiles.wordpress.org/mrasharirfan/\">Ashar Irfan</a>, <a href=\"https://profiles.wordpress.org/ashwinpc/\">ashwinpc</a>, <a href=\"https://profiles.wordpress.org/wpboss/\">Aslam Shekh</a>, <a href=\"https://profiles.wordpress.org/ate-up-with-motor/\">Ate Up With Motor</a>, <a href=\"https://profiles.wordpress.org/atlasmahesh/\">atlasmahesh</a>, <a href=\"https://profiles.wordpress.org/au87/\">au87</a>, <a href=\"https://profiles.wordpress.org/aubreypwd/\">Aubrey Portwood</a>, <a href=\"https://profiles.wordpress.org/augustuswm/\">augustuswm</a>, <a href=\"https://profiles.wordpress.org/aurooba/\">Aurooba Ahmed</a>, <a href=\"https://profiles.wordpress.org/avinapatel/\">Avina Patel</a>, <a href=\"https://profiles.wordpress.org/aksl95/\">Axel DUCORON</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/backermann1978/\">backermann1978</a>, <a href=\"https://profiles.wordpress.org/b-07/\">Bappi</a>, <a href=\"https://profiles.wordpress.org/toszcze/\">Bartosz Romanowski</a>, <a href=\"https://profiles.wordpress.org/pixolin/\">Bego Mario Garde</a>, <a href=\"https://profiles.wordpress.org/bfintal/\">Benjamin Intal</a>, <a href=\"https://profiles.wordpress.org/benjamin_zekavica/\">Benjamin Zekavica</a>, <a href=\"https://profiles.wordpress.org/bennemann/\">bennemann</a>, <a href=\"https://profiles.wordpress.org/bgermann/\">bgermann</a>, <a href=\"https://profiles.wordpress.org/bhaktirajdev/\">Bhaktii Rajdev</a>, <a href=\"https://profiles.wordpress.org/bibliofille/\">bibliofille</a>, <a href=\"https://profiles.wordpress.org/biranit/\">Biranit</a>, <a href=\"https://profiles.wordpress.org/birgire/\">Birgir Erlendsson</a>, <a href=\"https://profiles.wordpress.org/bitcomplex/\">bitcomplex</a>, <a href=\"https://profiles.wordpress.org/bjornw/\">BjornW</a>, <a href=\"https://profiles.wordpress.org/boblinthorst/\">boblinthorst</a>, <a href=\"https://profiles.wordpress.org/boga86/\">Boga86</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/bor0/\">Boro Sitnikovski</a>, <a href=\"https://profiles.wordpress.org/crazyjaco/\">Bradley Jacobs</a>, <a href=\"https://profiles.wordpress.org/bradleyt/\">Bradley Taylor</a>, <a href=\"https://profiles.wordpress.org/kraftbj/\">Brandon Kraft</a>, <a href=\"https://profiles.wordpress.org/brentswisher/\">Brent Swisher</a>, <a href=\"https://profiles.wordpress.org/bronsonquick/\">Bronson Quick</a>, <a href=\"https://profiles.wordpress.org/bsetiawan88/\">bsetiawan88</a>, <a href=\"https://profiles.wordpress.org/burhandodhy/\">Burhan Nasir</a>, <a href=\"https://profiles.wordpress.org/cbravobernal/\">Carlos Bravo</a>, <a href=\"https://profiles.wordpress.org/poena/\">Carolina Nymark</a>, <a href=\"https://profiles.wordpress.org/cdog/\">Catalin Dogaru</a>, <a href=\"https://profiles.wordpress.org/cathibosco1/\">Cathi Bosco</a>, <a href=\"https://profiles.wordpress.org/chandrapatel/\">Chandra Patel</a>, <a href=\"https://profiles.wordpress.org/caercam/\">Charlie Merland</a>, <a href=\"https://profiles.wordpress.org/chetan200891/\">Chetan Prajapati</a>, <a href=\"https://profiles.wordpress.org/ketuchetan/\">Chetan Satasiya</a>, <a href=\"https://profiles.wordpress.org/blogginglife/\">Chico</a>, <a href=\"https://profiles.wordpress.org/chintan1896/\">Chintan hingrajiya</a>, <a href=\"https://profiles.wordpress.org/chrico/\">ChriCo</a>, <a href=\"https://profiles.wordpress.org/aprea/\">Chris Aprea</a>, <a href=\"https://profiles.wordpress.org/chrisvanpatten/\">Chris Van Patten</a>, <a href=\"https://profiles.wordpress.org/christian1012/\">Christian Chung</a>, <a href=\"https://profiles.wordpress.org/needle/\">Christian Wach</a>, <a href=\"https://profiles.wordpress.org/lovememore/\">christianoliff</a>, <a href=\"https://profiles.wordpress.org/christophherr/\">Christoph Herr</a>, <a href=\"https://profiles.wordpress.org/cleancoded/\">cleancoded</a>, <a href=\"https://profiles.wordpress.org/cmagrin/\">cmagrin</a>, <a href=\"https://profiles.wordpress.org/compilenix/\">CompileNix</a>, <a href=\"https://profiles.wordpress.org/salzano/\">Corey Salzano</a>, <a href=\"https://profiles.wordpress.org/courtney0burton/\">courtney0burton</a>, <a href=\"https://profiles.wordpress.org/cristianozanca/\">Cristiano Zanca</a>, <a href=\"https://profiles.wordpress.org/littlebigthing/\">Csaba (LittleBigThings)</a>, <a href=\"https://profiles.wordpress.org/dswebsme/\">D.S. Webster</a>, <a href=\"https://profiles.wordpress.org/xendo/\">Dademaru</a>, <a href=\"https://profiles.wordpress.org/daleharrison/\">daleharrison</a>, <a href=\"https://profiles.wordpress.org/danmicamediacom/\">Dan Foley</a>, <a href=\"https://profiles.wordpress.org/goodevilgenius/\">Dan Jones</a>, <a href=\"https://profiles.wordpress.org/danbuk/\">DanBUK</a>, <a href=\"https://profiles.wordpress.org/danielbachhuber/\">Daniel Bachhuber</a>, <a href=\"https://profiles.wordpress.org/redsweater/\">Daniel Jalkut (Red Sweater)</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/mte90/\">Daniele Scasciafratte</a>, <a href=\"https://profiles.wordpress.org/danieliser/\">danieliser</a>, <a href=\"https://profiles.wordpress.org/daniloercoli/\">daniloercoli</a>, <a href=\"https://profiles.wordpress.org/dvankooten/\">Danny van Kooten</a>, <a href=\"https://profiles.wordpress.org/nerrad/\">Darren Ethier</a>, <a href=\"https://profiles.wordpress.org/darthhexx/\">darthhexx</a>, <a href=\"https://profiles.wordpress.org/deapness/\">Dave Parker</a>, <a href=\"https://profiles.wordpress.org/get_dave/\">Dave Smith</a>, <a href=\"https://profiles.wordpress.org/drw158/\">Dave Whitley</a>, <a href=\"https://profiles.wordpress.org/davetgreen/\">davetgreen</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/david.binda/\">David Binovec</a>, <a href=\"https://profiles.wordpress.org/davidbinda/\">David Binovec</a>, <a href=\"https://profiles.wordpress.org/daveshine/\">David Decker</a>, <a href=\"https://profiles.wordpress.org/dlh/\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/daviedr/\">David Rozando</a>, <a href=\"https://profiles.wordpress.org/dshanske/\">David Shanske</a>, <a href=\"https://profiles.wordpress.org/daxelrod/\">daxelrod</a>, <a href=\"https://profiles.wordpress.org/dkarfa/\">Debabrata Karfa</a>, <a href=\"https://profiles.wordpress.org/dennis_f/\">Deni</a>, <a href=\"https://profiles.wordpress.org/dehisok/\">Denis Cherniavsky</a>, <a href=\"https://profiles.wordpress.org/denisco/\">Denis Yanchevskiy</a>, <a href=\"https://profiles.wordpress.org/wpdennis/\">Dennis</a>, <a href=\"https://profiles.wordpress.org/dionysous/\">Dennis Hipp</a>, <a href=\"https://profiles.wordpress.org/dmsnell/\">Dennis Snell</a>, <a href=\"https://profiles.wordpress.org/dsifford/\">Derek Sifford</a>, <a href=\"https://profiles.wordpress.org/derweili/\">derweili</a>, <a href=\"https://profiles.wordpress.org/dfangstrom/\">dfangstrom</a>, <a href=\"https://profiles.wordpress.org/dharmin16/\">Dharmin Shah</a>, <a href=\"https://profiles.wordpress.org/dhavalkasvala/\">Dhaval kasavala</a>, <a href=\"https://profiles.wordpress.org/dhuyvetter/\">dhuyvetter</a>, <a href=\"https://profiles.wordpress.org/dianeco/\">Diane Co</a>, <a href=\"https://profiles.wordpress.org/diedeexterkate/\">DiedeExterkate</a>, <a href=\"https://profiles.wordpress.org/diego-la-monica/\">Diego La Monica</a>, <a href=\"https://profiles.wordpress.org/digitalapps/\">digitalapps</a>, <a href=\"https://profiles.wordpress.org/dilipbheda/\">Dilip Bheda</a>, <a href=\"https://profiles.wordpress.org/odminstudios/\">Dima</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/ocean90/\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/drewapicture/\">Drew Jaynes</a>, <a href=\"https://profiles.wordpress.org/dukex/\">Dukex</a>, <a href=\"https://profiles.wordpress.org/dushanthi/\">dushanthi</a>, <a href=\"https://profiles.wordpress.org/seedsca/\">ecotechie</a>, <a href=\"https://profiles.wordpress.org/eden159/\">eden159</a>, <a href=\"https://profiles.wordpress.org/ediamin/\">Edi Amin</a>, <a href=\"https://profiles.wordpress.org/etoledom/\">Eduardo Toledo</a>, <a href=\"https://profiles.wordpress.org/ehtis/\">ehtis</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/iseulde/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/elliotcondon/\">Elliot Condon</a>, <a href=\"https://profiles.wordpress.org/codex-m/\">Emerson Maningo</a>, <a href=\"https://profiles.wordpress.org/edocev/\">Emil Dotsev</a>, <a href=\"https://profiles.wordpress.org/emiluzelac/\">Emil Uzelac</a>, <a href=\"https://profiles.wordpress.org/epiqueras/\">Enrique Piqueras</a>, <a href=\"https://profiles.wordpress.org/nrqsnchz/\">Enrique S&#225;nchez</a>, <a href=\"https://profiles.wordpress.org/erikkroes/\">erikkroes</a>, <a href=\"https://profiles.wordpress.org/estelaris/\">estelaris</a>, <a href=\"https://profiles.wordpress.org/evalarumbe/\">evalarumbe</a>, <a href=\"https://profiles.wordpress.org/faazshift/\">faazshift</a>, <a href=\"https://profiles.wordpress.org/fabifott/\">Fabian</a>, <a href=\"https://profiles.wordpress.org/fabiankaegy/\">Fabian K&#228;gy</a>, <a href=\"https://profiles.wordpress.org/fblaser/\">fblaser</a>, <a href=\"https://profiles.wordpress.org/felipeelia/\">Felipe Elia</a>, <a href=\"https://profiles.wordpress.org/flixos90/\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/fencer04/\">Fencer04</a>, <a href=\"https://profiles.wordpress.org/flaviozavan/\">flaviozavan</a>, <a href=\"https://profiles.wordpress.org/flipkeijzer/\">flipkeijzer</a>, <a href=\"https://profiles.wordpress.org/mista-flo/\">Florian TIAR</a>, <a href=\"https://profiles.wordpress.org/foysalremon/\">Foysal Remon</a>, <a href=\"https://profiles.wordpress.org/galbaras/\">Gal Baras</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse/\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/voldemortensen/\">Garth Mortensen</a>, <a href=\"https://profiles.wordpress.org/garyj/\">Gary Jones</a>, <a href=\"https://profiles.wordpress.org/pento/\">Gary Pendergast</a>, <a href=\"https://profiles.wordpress.org/guddu1315/\">Gaurang Dabhi</a>, <a href=\"https://profiles.wordpress.org/gchtr/\">gchtr</a>, <a href=\"https://profiles.wordpress.org/soulseekah/\">Gennady Kovshenin</a>, <a href=\"https://profiles.wordpress.org/loyaltymanufaktur/\">Gesundheit Bewegt GmbH</a>, <a href=\"https://profiles.wordpress.org/sachyya-sachet/\">ghoul</a>, <a href=\"https://profiles.wordpress.org/girlieworks/\">girlieworks</a>, <a href=\"https://profiles.wordpress.org/glauberglauber/\">glauberglauber</a>, <a href=\"https://profiles.wordpress.org/hometowntrailers/\">Glenn</a>, <a href=\"https://profiles.wordpress.org/gravityview/\">GravityView</a>, <a href=\"https://profiles.wordpress.org/gregsullivan/\">gregsullivan</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Grzegorz Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/grzegorzjanoszka/\">Grzegorz.Janoszka</a>, <a href=\"https://profiles.wordpress.org/gwwar/\">gwwar</a>, <a href=\"https://profiles.wordpress.org/hardeepasrani/\">Hardeep Asrani</a>, <a href=\"https://profiles.wordpress.org/thakkarhardik/\">Hardik Thakkar</a>, <a href=\"https://profiles.wordpress.org/hareesh-pillai/\">Hareesh Pillai</a>, <a href=\"https://profiles.wordpress.org/hareesh pillai/\">Hareesh Pillai</a>, <a href=\"https://profiles.wordpress.org/harryfear/\">harryfear</a>, <a href=\"https://profiles.wordpress.org/harshbarach/\">harshbarach</a>, <a href=\"https://profiles.wordpress.org/haszari/\">haszari</a>, <a href=\"https://profiles.wordpress.org/hesyifei/\">He Yifei</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/herbmiller/\">herbmiller</a>, <a href=\"https://profiles.wordpress.org/herregroen/\">herregroen</a>, <a href=\"https://profiles.wordpress.org/hirofumi2012/\">hirofumi2012</a>, <a href=\"https://profiles.wordpress.org/hkandulla/\">HKandulla</a>, <a href=\"https://profiles.wordpress.org/howdy_mcgee/\">Howdy_McGee</a>, <a href=\"https://profiles.wordpress.org/hoythan/\">hoythan</a>, <a href=\"https://profiles.wordpress.org/hlashbrooke/\">Hugh Lashbrooke</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/ianmjones/\">ianmjones</a>, <a href=\"https://profiles.wordpress.org/zinigor/\">Igor Zinovyev</a>, <a href=\"https://profiles.wordpress.org/gsayed786/\">Imran Sayed</a>, <a href=\"https://profiles.wordpress.org/intimez/\">intimez</a>, <a href=\"https://profiles.wordpress.org/ipstenu/\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/iqbalbary/\">iqbalbary</a>, <a href=\"https://profiles.wordpress.org/ireneyoast/\">Irene Strikkers</a>, <a href=\"https://profiles.wordpress.org/isabel_brison/\">Isabel Brison</a>, <a href=\"https://profiles.wordpress.org/ismailelkorchi/\">Ismail El Korchi</a>, <a href=\"https://profiles.wordpress.org/ispreview/\">ispreview</a>, <a href=\"https://profiles.wordpress.org/jdgrimes/\">J.D. Grimes</a>, <a href=\"https://profiles.wordpress.org/jagirbaheshwp/\">jagirbaheshwp</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/jalpa1984/\">Jalpa Panchal</a>, <a href=\"https://profiles.wordpress.org/macmanx/\">James Huff</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/jameslnewell/\">jameslnewell</a>, <a href=\"https://profiles.wordpress.org/janak007/\">janak Kaneriya</a>, <a href=\"https://profiles.wordpress.org/jankimoradiya/\">Janki Moradiya</a>, <a href=\"https://profiles.wordpress.org/janwoostendorp/\">janw.oostendorp</a>, <a href=\"https://profiles.wordpress.org/jared_smith/\">jared_smith</a>, <a href=\"https://profiles.wordpress.org/jarocks/\">jarocks</a>, <a href=\"https://profiles.wordpress.org/jarretc/\">Jarret</a>, <a href=\"https://profiles.wordpress.org/studiotwee/\">Jasper van der Meer</a>, <a href=\"https://profiles.wordpress.org/javeweb/\">jave.web</a>, <a href=\"https://profiles.wordpress.org/javorszky/\">javorszky</a>, <a href=\"https://profiles.wordpress.org/jayswadas/\">Jay Swadas</a>, <a href=\"https://profiles.wordpress.org/iamjaydip/\">Jaydip</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jean-Baptiste Audras</a>, <a href=\"https://profiles.wordpress.org/jfarthing84/\">Jeff Farthing</a>, <a href=\"https://profiles.wordpress.org/jeffpaul/\">Jeff Paul</a>, <a href=\"https://profiles.wordpress.org/jeichorn/\">jeichorn</a>, <a href=\"https://profiles.wordpress.org/jenblogs4u/\">Jen Miller</a>, <a href=\"https://profiles.wordpress.org/jenkoian/\">jenkoian</a>, <a href=\"https://profiles.wordpress.org/jeremyclarke/\">Jer Clarke</a>, <a href=\"https://profiles.wordpress.org/jeremyfelt/\">Jeremy Felt</a>, <a href=\"https://profiles.wordpress.org/engelen/\">Jesper van Engelen</a>, <a href=\"https://profiles.wordpress.org/luminuu/\">Jessica Lyschik</a>, <a href=\"https://profiles.wordpress.org/jffng/\">jffng</a>, <a href=\"https://profiles.wordpress.org/jikamens/\">jikamens</a>, <a href=\"https://profiles.wordpress.org/jipmoors/\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/jitendrabanjara1991/\">jitendrabanjara1991</a>, <a href=\"https://profiles.wordpress.org/jkitchen/\">jkitchen</a>, <a href=\"https://profiles.wordpress.org/jmmathc/\">jmmathc</a>, <a href=\"https://profiles.wordpress.org/joakimsilfverberg/\">joakimsilfverberg</a>, <a href=\"https://profiles.wordpress.org/jobthomas/\">Job</a>, <a href=\"https://profiles.wordpress.org/jodamo5/\">jodamo5</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/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby</a>, <a href=\"https://profiles.wordpress.org/johnregan3/\">John Regan</a>, <a href=\"https://profiles.wordpress.org/jojotjebaby/\">jojotjebaby</a>, <a href=\"https://profiles.wordpress.org/jrchamp/\">Jonathan Champ</a>, <a href=\"https://profiles.wordpress.org/jond/\">Jonathan Davis</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/jg-visual/\">Jonathan Goldford</a>, <a href=\"https://profiles.wordpress.org/spacedmonkey/\">Jonny Harris</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/josephscott/\">Joseph Scott</a>, <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a>, <a href=\"https://profiles.wordpress.org/shelob9/\">Josh Pollock</a>, <a href=\"https://profiles.wordpress.org/joshuanoyce/\">Joshua Noyce</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/jsnajdr/\">jsnajdr</a>, <a href=\"https://profiles.wordpress.org/juanfra/\">Juanfra Aldasoro</a>, <a href=\"https://profiles.wordpress.org/juiiee8487/\">Juhi Patel</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/junktrunk/\">junktrunk</a>, <a href=\"https://profiles.wordpress.org/justdaiv/\">justdaiv</a>, <a href=\"https://profiles.wordpress.org/justinahinon/\">Justin Ahinon</a>, <a href=\"https://profiles.wordpress.org/greenshady/\">Justin Tadlock</a>, <a href=\"https://profiles.wordpress.org/kadamwhite/\">K. Adam White</a>, <a href=\"https://profiles.wordpress.org/kafleg/\">kafleg</a>, <a href=\"https://profiles.wordpress.org/trepmal/\">Kailey (trepmal)</a>, <a href=\"https://profiles.wordpress.org/kakshak/\">Kakshak Kalaria</a>, <a href=\"https://profiles.wordpress.org/kamrankhorsandi/\">Kamran Khorsandi</a>, <a href=\"https://profiles.wordpress.org/leprincenoir/\">Kantari Samy</a>, <a href=\"https://profiles.wordpress.org/karlgroves/\">karlgroves</a>, <a href=\"https://profiles.wordpress.org/katielgc/\">katielgc</a>, <a href=\"https://profiles.wordpress.org/kbrownkd/\">kbrownkd</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Dwan</a>, <a href=\"https://profiles.wordpress.org/kellychoffman/\">Kelly Hoffman</a>, <a href=\"https://profiles.wordpress.org/kerfred/\">Kerfred</a>, <a href=\"https://profiles.wordpress.org/kingkero/\">kero</a>, <a href=\"https://profiles.wordpress.org/ketanumretiya030/\">Ketan Umretiya</a>, <a href=\"https://profiles.wordpress.org/kevinkovadia/\">kevIN kovaDIA</a>, <a href=\"https://profiles.wordpress.org/kharisblank/\">Kharis Sulistiyono</a>, <a href=\"https://profiles.wordpress.org/killerbishop/\">killerbishop</a>, <a href=\"https://profiles.wordpress.org/killua99/\">killua99</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/kokers/\">kokers</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/kuus/\">kuus</a>, <a href=\"https://profiles.wordpress.org/kyliesabra/\">kyliesabra</a>, <a href=\"https://profiles.wordpress.org/laurelfulford/\">laurelfulford</a>, <a href=\"https://profiles.wordpress.org/lbenicio/\">lbenicio</a>, <a href=\"https://profiles.wordpress.org/leogermani/\">leogermani</a>, <a href=\"https://profiles.wordpress.org/leonblade/\">leonblade</a>, <a href=\"https://profiles.wordpress.org/lessbloat/\">lessbloat</a>, <a href=\"https://profiles.wordpress.org/lisota/\">lisota</a>, <a href=\"https://profiles.wordpress.org/lllor/\">lllor</a>, <a href=\"https://profiles.wordpress.org/lordlod/\">lordlod</a>, <a href=\"https://profiles.wordpress.org/loreleiaurora/\">LoreleiAurora</a>, <a href=\"https://profiles.wordpress.org/luan-ramos/\">Luan Ramos</a>, <a href=\"https://profiles.wordpress.org/luciano-croce/\">luciano-croce</a>, <a href=\"https://profiles.wordpress.org/luigipulcini/\">luigipulcini</a>, <a href=\"https://profiles.wordpress.org/luisherranz/\">luisherranz</a>, <a href=\"https://profiles.wordpress.org/lukaswaudentio/\">lukaswaudentio</a>, <a href=\"https://profiles.wordpress.org/wpfed/\">Luke</a>, <a href=\"https://profiles.wordpress.org/lukecarbis/\">Luke Carbis</a>, <a href=\"https://profiles.wordpress.org/lukecavanagh/\">Luke Cavanagh</a>, <a href=\"https://profiles.wordpress.org/m1tk00/\">m1tk00</a>, <a href=\"https://profiles.wordpress.org/maartenleenders/\">maartenleenders</a>, <a href=\"https://profiles.wordpress.org/palmiak/\">Maciej Palmowski</a>, <a href=\"https://profiles.wordpress.org/maciejmackowiak/\">maciejmackowiak</a>, <a href=\"https://profiles.wordpress.org/mahesh901122/\">Mahesh Waghmare</a>, <a href=\"https://profiles.wordpress.org/majemedia/\">Maje Media LLC</a>, <a href=\"https://profiles.wordpress.org/malthert/\">malthert</a>, <a href=\"https://profiles.wordpress.org/manooweb/\">manooweb</a>, <a href=\"https://profiles.wordpress.org/manuelaugustin/\">Manuel Augustin</a>, <a href=\"https://profiles.wordpress.org/manzoorwanijk/\">Manzoor Wani</a>, <a href=\"https://profiles.wordpress.org/marcelo2605/\">marcelo2605</a>, <a href=\"https://profiles.wordpress.org/marcguay/\">MarcGuay</a>, <a href=\"https://profiles.wordpress.org/iworks/\">Marcin Pietrzak</a>, <a href=\"https://profiles.wordpress.org/marcomartins/\">Marco Martins</a>, <a href=\"https://profiles.wordpress.org/marcosalexandre/\">MarcosAlexandre</a>, <a href=\"https://profiles.wordpress.org/mkaz/\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/marekhrabe/\">Marek Hrabe</a>, <a href=\"https://profiles.wordpress.org/chaton666/\">Marie Comet</a>, <a href=\"https://profiles.wordpress.org/maguiar/\">Mario Aguiar</a>, <a href=\"https://profiles.wordpress.org/nofearinc/\">Mario Peshev</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius Jensen</a>, <a href=\"https://profiles.wordpress.org/mdwolinski/\">Mark D Wolinski</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/markoheijnen/\">Marko Heijnen</a>, <a href=\"https://profiles.wordpress.org/mspatovaliyski/\">Martin Spatovaliyski</a>, <a href=\"https://profiles.wordpress.org/splitti/\">Martin Splitt</a>, <a href=\"https://profiles.wordpress.org/m-e-h/\">Marty Helmick</a>, <a href=\"https://profiles.wordpress.org/marybaum/\">Mary Baum</a>, <a href=\"https://profiles.wordpress.org/masummdar/\">masummdar</a>, <a href=\"https://profiles.wordpress.org/matstars/\">Mat Gargano</a>, <a href=\"https://profiles.wordpress.org/mat-lipe/\">Mat Lipe</a>, <a href=\"https://profiles.wordpress.org/iceable/\">Mathieu Sarrasin</a>, <a href=\"https://profiles.wordpress.org/imath/\">Mathieu Viet</a>, <a href=\"https://profiles.wordpress.org/mattchowning/\">Matt Chowning</a>, <a href=\"https://profiles.wordpress.org/mboynes/\">Matthew Boynes</a>, <a href=\"https://profiles.wordpress.org/mattheu/\">Matthew Haines-Young</a>, <a href=\"https://profiles.wordpress.org/matthiasthiel/\">matthias.thiel</a>, <a href=\"https://profiles.wordpress.org/mattyrob/\">mattyrob</a>, <a href=\"https://profiles.wordpress.org/matveb/\">Matías Ventura</a>, <a href=\"https://profiles.wordpress.org/maximeculea/\">Maxime Culea</a>, <a href=\"https://profiles.wordpress.org/maximejobin/\">Maxime Jobin</a>, <a href=\"https://profiles.wordpress.org/maxme/\">maxme</a>, <a href=\"https://profiles.wordpress.org/mayanksonawat/\">mayanksonawat</a>, <a href=\"https://profiles.wordpress.org/mchavezi/\">mchavezi</a>, <a href=\"https://profiles.wordpress.org/immeet94/\">Meet Makadia</a>, <a href=\"https://profiles.wordpress.org/mehidi258/\">Mehidi Hassan</a>, <a href=\"https://profiles.wordpress.org/mehulkaklotar/\">Mehul Kaklotar</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce</a>, <a href=\"https://profiles.wordpress.org/melinedo/\">Melin Edomwonyi</a>, <a href=\"https://profiles.wordpress.org/meloniq/\">meloniq</a>, <a href=\"https://profiles.wordpress.org/michael-arestad/\">Michael Arestad</a>, <a href=\"https://profiles.wordpress.org/mbabker/\">Michael Babker</a>, <a href=\"https://profiles.wordpress.org/mnelson4/\">Michael Nelson</a>, <a href=\"https://profiles.wordpress.org/donmhico/\">Michael Panaga</a>, <a href=\"https://profiles.wordpress.org/michelweimerskirch/\">michel.weimerskirch</a>, <a href=\"https://profiles.wordpress.org/michielatyoast/\">Michiel Heijmans</a>, <a href=\"https://profiles.wordpress.org/miette49/\">miette49</a>, <a href=\"https://profiles.wordpress.org/mcsf/\">Miguel Fonseca</a>, <a href=\"https://profiles.wordpress.org/miguelvieira/\">miguelvieira</a>, <a href=\"https://profiles.wordpress.org/mihaiiceyro/\">mihaiiceyro</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/mauteri/\">Mike Auteri</a>, <a href=\"https://profiles.wordpress.org/mdgl/\">Mike Glendinning</a>, <a href=\"https://profiles.wordpress.org/mikehansenme/\">Mike Hansen</a>, <a href=\"https://profiles.wordpress.org/mikejolley/\">Mike Jolley</a>, <a href=\"https://profiles.wordpress.org/mikerbg/\">Mike Reid</a>, <a href=\"https://profiles.wordpress.org/mikeschroder/\">Mike Schroder</a>, <a href=\"https://profiles.wordpress.org/mikengarrett/\">MikeNGarrett</a>, <a href=\"https://profiles.wordpress.org/msaari/\">Mikko Saari</a>, <a href=\"https://profiles.wordpress.org/dimadin/\">Milan Dinić</a>, <a href=\"https://profiles.wordpress.org/gdragon/\">Milan Petrovic</a>, <a href=\"https://profiles.wordpress.org/mobeen-abdullah/\">Mobeen Abdullah</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/boemedia/\">Monique Dubbelman</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/mppfeiffer/\">mppfeiffer</a>, <a href=\"https://profiles.wordpress.org/mrmadhat/\">mrmadhat</a>, <a href=\"https://profiles.wordpress.org/msaggiorato/\">msaggiorato</a>, <a href=\"https://profiles.wordpress.org/mtias/\">mtias</a>, <a href=\"https://profiles.wordpress.org/phpdocs/\">Muhammad Afzal</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/mzorz/\">mzorz</a>, <a href=\"https://profiles.wordpress.org/nadir/\">nadir</a>, <a href=\"https://profiles.wordpress.org/nfmohit/\">Nahid Ferdous Mohit</a>, <a href=\"https://profiles.wordpress.org/naveenkharwar/\">Naveen Kharwar</a>, <a href=\"https://profiles.wordpress.org/nayana123/\">Nayana Maradia</a>, <a href=\"https://profiles.wordpress.org/greatislander/\">Ned Zimmerman</a>, <a href=\"https://profiles.wordpress.org/neelpatel7295/\">Neel Patel</a>, <a href=\"https://profiles.wordpress.org/nextendweb/\">Nextendweb</a>, <a href=\"https://profiles.wordpress.org/nextscripts/\">NextScripts</a>, <a href=\"https://profiles.wordpress.org/niallkennedy/\">Niall Kennedy</a>, <a href=\"https://profiles.wordpress.org/nickdaugherty/\">Nick Daugherty</a>, <a href=\"https://profiles.wordpress.org/celloexpressions/\">Nick Halsey</a>, <a href=\"https://profiles.wordpress.org/nickylimjj/\">Nicky Lim</a>, <a href=\"https://profiles.wordpress.org/nicolad/\">nicolad</a>, <a href=\"https://profiles.wordpress.org/rahe/\">Nicolas Juen</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/nikschavan/\">Nikhil Chavan</a>, <a href=\"https://profiles.wordpress.org/nikolastoqnow/\">nikolastoqnow</a>, <a href=\"https://profiles.wordpress.org/niq1982/\">Niku Hietanen</a>, <a href=\"https://profiles.wordpress.org/rabmalin/\">Nilambar Sharma</a>, <a href=\"https://profiles.wordpress.org/nishitlangaliya/\">Nishit Langaliya</a>, <a href=\"https://profiles.wordpress.org/kailanitish90/\">Nitish Kaila</a>, <a href=\"https://profiles.wordpress.org/nmenescardi/\">nmenescardi</a>, <a href=\"https://profiles.wordpress.org/noahtallen/\">noahtallen</a>, <a href=\"https://profiles.wordpress.org/notnownikki/\">notnownikki</a>, <a href=\"https://profiles.wordpress.org/noyle/\">noyle</a>, <a href=\"https://profiles.wordpress.org/hideokamoto/\">Okamoto Hidetaka</a>, <a href=\"https://profiles.wordpress.org/lindstromer/\">Olaf Lindstr&#246;m</a>, <a href=\"https://profiles.wordpress.org/moonomo/\">Omaar Osmaan</a>, <a href=\"https://profiles.wordpress.org/omarreiss/\">Omar Reiss</a>, <a href=\"https://profiles.wordpress.org/onlanka/\">onlanka</a>, <a href=\"https://profiles.wordpress.org/ov3rfly/\">Ov3rfly</a>, <a href=\"https://profiles.wordpress.org/oxyc/\">oxyc</a>, <a href=\"https://profiles.wordpress.org/ozmatflc/\">ozmatflc</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/paragoninitiativeenterprises/\">Paragon Initiative Enterprises</a>, <a href=\"https://profiles.wordpress.org/paresh07/\">Paresh Shinde</a>, <a href=\"https://profiles.wordpress.org/hardipparmar/\">Parmar Hardip</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/patilvikasj/\">patilvikasj</a>, <a href=\"https://profiles.wordpress.org/patrelentlesstechnologycom/\">Patrick Baldwin</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/paulschreiber/\">Paul Schreiber</a>, <a href=\"https://profiles.wordpress.org/bassgang/\">Paul Vincent Beigang</a>, <a href=\"https://profiles.wordpress.org/pedromendonca/\">Pedro Mendon&#231;a</a>, <a href=\"https://profiles.wordpress.org/pputzer/\">pepe</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/phillipjohn/\">PhillipJohn</a>, <a href=\"https://profiles.wordpress.org/pierlo/\">Pierre Gordon</a>, <a href=\"https://profiles.wordpress.org/pikamander2/\">pikamander2</a>, <a href=\"https://profiles.wordpress.org/decrecementofeliz/\">Pilar Mera</a>, <a href=\"https://profiles.wordpress.org/wppinar/\">Pinar Olguc</a>, <a href=\"https://profiles.wordpress.org/powerbuoy/\">powerbuoy</a>, <a href=\"https://profiles.wordpress.org/promz/\">Pramod Jodhani</a>, <a href=\"https://profiles.wordpress.org/pratikthink/\">Pratik</a>, <a href=\"https://profiles.wordpress.org/pratikkry/\">Pratik K. Yadav</a>, <a href=\"https://profiles.wordpress.org/freewebmentor/\">Prem Tiwari</a>, <a href=\"https://profiles.wordpress.org/presskopp/\">Presskopp</a>, <a href=\"https://profiles.wordpress.org/priyankkpatel/\">Priyank Patel</a>, <a href=\"https://profiles.wordpress.org/quantumstate/\">Quantumstate</a>, <a href=\"https://profiles.wordpress.org/raajtram/\">Raaj Trambadia</a>, <a href=\"https://profiles.wordpress.org/raamdev/\">Raam Dev</a>, <a href=\"https://profiles.wordpress.org/raboodesign/\">raboodesign</a>, <a href=\"https://profiles.wordpress.org/larrach/\">Rachel Peter</a>, <a href=\"https://profiles.wordpress.org/rahulvaza/\">Rahul Vaza</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/ramon-fincken/\">ramon fincken</a>, <a href=\"https://profiles.wordpress.org/rclations/\">RC Lations</a>, <a href=\"https://profiles.wordpress.org/rebasaurus/\">rebasaurus</a>, <a href=\"https://profiles.wordpress.org/reikodd/\">ReikoDD</a>, <a href=\"https://profiles.wordpress.org/remcotolsma/\">Remco Tolsma</a>, <a href=\"https://profiles.wordpress.org/retrofox/\">retrofox</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/quicoto/\">Ricard Torres</a>, <a href=\"https://profiles.wordpress.org/rockfire/\">Richard Korthuis</a>, <a href=\"https://profiles.wordpress.org/riddhiehta02/\">Riddhi Mehta</a>, <a href=\"https://profiles.wordpress.org/rbrishabh/\">Rishabh Budhiraja</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/robi-bobi/\">Robert Ivanov</a>, <a href=\"https://profiles.wordpress.org/rogueresearch/\">rogueresearch</a>, <a href=\"https://profiles.wordpress.org/rconde/\">Roi Conde</a>, <a href=\"https://profiles.wordpress.org/murgroland/\">Roland Murg</a>, <a href=\"https://profiles.wordpress.org/ronakganatra/\">Ronak Ganatra</a>, <a href=\"https://profiles.wordpress.org/raubvogel/\">Ronny Harbich</a>, <a href=\"https://profiles.wordpress.org/karthost/\">Roy Randolph</a>, <a href=\"https://profiles.wordpress.org/roytanck/\">Roy Tanck</a>, <a href=\"https://profiles.wordpress.org/ryan/\">Ryan Boren</a>, <a href=\"https://profiles.wordpress.org/ryankienstra/\">Ryan Kienstra</a>, <a href=\"https://profiles.wordpress.org/rmccue/\">Ryan McCue</a>, <a href=\"https://profiles.wordpress.org/welcher/\">Ryan Welcher</a>, <a href=\"https://profiles.wordpress.org/sebastienserre/\">S&#233;bastien SERRE</a>, <a href=\"https://profiles.wordpress.org/samgordondev/\">samgordondev</a>, <a href=\"https://profiles.wordpress.org/sasiddiqui/\">Sami Ahmed Siddiqui</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/samuelfernandez/\">SamuelFernandez</a>, <a href=\"https://profiles.wordpress.org/progremzion/\">Sanket Mehta</a>, <a href=\"https://profiles.wordpress.org/tinkerbelly/\">sarah semark</a>, <a href=\"https://profiles.wordpress.org/sarathar/\">Sarath AR</a>, <a href=\"https://profiles.wordpress.org/saskak/\">saskak</a>, <a href=\"https://profiles.wordpress.org/sathyapulse/\">sathyapulse</a>, <a href=\"https://profiles.wordpress.org/sbardian/\">sbardian</a>, <a href=\"https://profiles.wordpress.org/coffee2code/\">Scott Reilly</a>, <a href=\"https://profiles.wordpress.org/wonderboymusic/\">Scott Taylor</a>, <a href=\"https://profiles.wordpress.org/scvleon/\">scvleon</a>, <a href=\"https://profiles.wordpress.org/sebastianpisula/\">Sebastian Pisula</a>, <a href=\"https://profiles.wordpress.org/assassinateur/\">Seghir Nadir</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/sergiomdgomes/\">sergiomdgomes</a>, <a href=\"https://profiles.wordpress.org/seuser/\">seuser</a>, <a href=\"https://profiles.wordpress.org/sgastard/\">sgastard</a>, <a href=\"https://profiles.wordpress.org/sgr33n/\">SGr33n</a>, <a href=\"https://profiles.wordpress.org/shadyvb/\">Shady Sharaf</a>, <a href=\"https://profiles.wordpress.org/shamim51/\">Shamim Hasan</a>, <a href=\"https://profiles.wordpress.org/sharaz/\">Sharaz Shahid</a>, <a href=\"https://profiles.wordpress.org/shashank3105/\">Shashank Panchal</a>, <a href=\"https://profiles.wordpress.org/shawfactor/\">shawfactor</a>, <a href=\"https://profiles.wordpress.org/shital-patel/\">Shital Marakana</a>, <a href=\"https://profiles.wordpress.org/siliconforks/\">siliconforks</a>, <a href=\"https://profiles.wordpress.org/simonjanin/\">simonjanin</a>, <a href=\"https://profiles.wordpress.org/simono/\">simono</a>, <a href=\"https://profiles.wordpress.org/sinatrateam/\">sinatrateam</a>, <a href=\"https://profiles.wordpress.org/sirreal/\">sirreal</a>, <a href=\"https://profiles.wordpress.org/sixes/\">Sixes</a>, <a href=\"https://profiles.wordpress.org/slaffik/\">Slava Abakumov</a>, <a href=\"https://profiles.wordpress.org/slobodanmanic/\">Slobodan Manic</a>, <a href=\"https://profiles.wordpress.org/smerriman/\">smerriman</a>, <a href=\"https://profiles.wordpress.org/snapfractalpop/\">snapfractalpop</a>, <a href=\"https://profiles.wordpress.org/socalchristina/\">socalchristina</a>, <a href=\"https://profiles.wordpress.org/soean/\">Soren Wrede</a>, <a href=\"https://profiles.wordpress.org/spectacula/\">Spectacula</a>, <a href=\"https://profiles.wordpress.org/spenserhale/\">spenserhale</a>, <a href=\"https://profiles.wordpress.org/spuds10/\">spuds10</a>, <a href=\"https://profiles.wordpress.org/sstoqnov/\">Stanimir Stoyanov</a>, <a href=\"https://profiles.wordpress.org/steevithak/\">steevithak</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/sabernhardt/\">Stephen Bernhardt</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/stevenkword/\">Steven Word</a>, <a href=\"https://profiles.wordpress.org/studyboi/\">studyboi</a>, <a href=\"https://profiles.wordpress.org/subratamal/\">Subrata Mal</a>, <a href=\"https://profiles.wordpress.org/subrataemfluence/\">Subrata Sarkar</a>, <a href=\"https://profiles.wordpress.org/sudhiryadav/\">Sudhir Yadav</a>, <a href=\"https://profiles.wordpress.org/manikmist09/\">Sultan Nasir Uddin</a>, <a href=\"https://profiles.wordpress.org/tha_sun/\">sun</a>, <a href=\"https://profiles.wordpress.org/codesue/\">Suzen Fylke</a>, <a href=\"https://profiles.wordpress.org/svanhal/\">svanhal</a>, <a href=\"https://profiles.wordpress.org/patilswapnilv/\">Swapnil V. Patil</a>, <a href=\"https://profiles.wordpress.org/swapnild/\">swapnild</a>, <a href=\"https://profiles.wordpress.org/cybr/\">Sybre Waaijer</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/nevma/\">Takis Bouyouris</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/tanvirul/\">Tanvirul Haque</a>, <a href=\"https://profiles.wordpress.org/tazotodua/\">tazotodua</a>, <a href=\"https://profiles.wordpress.org/technote0space/\">technote</a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>, <a href=\"https://profiles.wordpress.org/tessak22/\">Tessa Kriesel</a>, <a href=\"https://profiles.wordpress.org/themes-1/\">them.es</a>, <a href=\"https://profiles.wordpress.org/themezly/\">Themezly</a>, <a href=\"https://profiles.wordpress.org/thulshof/\">Thijs Hulshof</a>, <a href=\"https://profiles.wordpress.org/kraftner/\">Thomas Kr&#228;ftner</a>, <a href=\"https://profiles.wordpress.org/thomaswm/\">thomaswm</a>, <a href=\"https://profiles.wordpress.org/tdh/\">Thord D. Hedengren</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/tigertech/\">tigertech</a>, <a href=\"https://profiles.wordpress.org/n7studios/\">Tim Carr</a>, <a href=\"https://profiles.wordpress.org/timhavinga/\">Tim Havinga</a>, <a href=\"https://profiles.wordpress.org/hedgefield/\">Tim Hengeveld</a>, <a href=\"https://profiles.wordpress.org/timon33/\">timon33</a>, <a href=\"https://profiles.wordpress.org/spaceshipone/\">Timoth&#233;e Brosille</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/timph/\">timph</a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/tmdesigned/\">tmdesigned</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/toddhalfpenny/\">toddhalfpenny</a>, <a href=\"https://profiles.wordpress.org/tosho/\">Todor Gaidarov</a>, <a href=\"https://profiles.wordpress.org/tjnowell/\">Tom J Nowell</a>, <a href=\"https://profiles.wordpress.org/tferry/\">Tommy Ferry</a>, <a href=\"https://profiles.wordpress.org/skithund/\">Toni Viemer&#246;</a>, <a href=\"https://profiles.wordpress.org/tonybogdanov/\">tonybogdanov</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/itowhid06/\">Towhidul Islam</a>, <a href=\"https://profiles.wordpress.org/trasweb/\">trasweb</a>, <a href=\"https://profiles.wordpress.org/travisnorthcutt/\">Travis Northcutt</a>, <a href=\"https://profiles.wordpress.org/travisseitler/\">travisseitler</a>, <a href=\"https://profiles.wordpress.org/triplejumper12/\">triplejumper12</a>, <a href=\"https://profiles.wordpress.org/truchot/\">truchot</a>, <a href=\"https://profiles.wordpress.org/truongwp/\">truongwp</a>, <a href=\"https://profiles.wordpress.org/dekervit/\">Tugdual de Kerviler</a>, <a href=\"https://profiles.wordpress.org/dinhtungdu/\">Tung Du</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/utsav72640/\">Utsav tilava</a>, <a href=\"https://profiles.wordpress.org/vaishalipanchal/\">Vaishali Panchal</a>, <a href=\"https://profiles.wordpress.org/vbaimas/\">vbaimas</a>, <a href=\"https://profiles.wordpress.org/veminom/\">Veminom</a>, <a href=\"https://profiles.wordpress.org/venutius/\">Venutius</a>, <a href=\"https://profiles.wordpress.org/fesovik/\">Viktor Veljanovski</a>, <a href=\"https://profiles.wordpress.org/vishalkakadiya/\">Vishal Kakadiya</a>, <a href=\"https://profiles.wordpress.org/vishitshah/\">Vishit Shah</a>, <a href=\"https://profiles.wordpress.org/vladlu/\">vladlu</a>, <a href=\"https://profiles.wordpress.org/vladwtz/\">Vladut Ilie</a>, <a href=\"https://profiles.wordpress.org/vortfu/\">vortfu</a>, <a href=\"https://profiles.wordpress.org/svovaf/\">Vova Feldman</a>, <a href=\"https://profiles.wordpress.org/vrimill/\">vrimill</a>, <a href=\"https://profiles.wordpress.org/w3rkjana/\">w3rkjana</a>, <a href=\"https://profiles.wordpress.org/waleedt93/\">waleedt93</a>, <a href=\"https://profiles.wordpress.org/webcommsat/\">webcommsat AbhaNonStopNewsUK</a>, <a href=\"https://profiles.wordpress.org/webdados/\">Webdados (Marco Almeida)</a>, <a href=\"https://profiles.wordpress.org/webmandesign/\">WebMan Design &#124; Oliver Juhas</a>, <a href=\"https://profiles.wordpress.org/westonruter/\">Weston Ruter</a>, <a href=\"https://profiles.wordpress.org/earnjam/\">William Earnhardt</a>, <a href=\"https://profiles.wordpress.org/wpdavis/\">William P. Davis</a>, <a href=\"https://profiles.wordpress.org/williampatton/\">William Patton</a>, <a href=\"https://profiles.wordpress.org/withinboredom/\">withinboredom</a>, <a href=\"https://profiles.wordpress.org/worldweb/\">worldweb</a>, <a href=\"https://profiles.wordpress.org/wpgurudev/\">wpgurudev</a>, <a href=\"https://profiles.wordpress.org/yanngarcia/\">yanngarcia</a>, <a href=\"https://profiles.wordpress.org/collet/\">Yannicki</a>, <a href=\"https://profiles.wordpress.org/yarnboy/\">yarnboy</a>, <a href=\"https://profiles.wordpress.org/yashar_hv/\">yashar_hv</a>, <a href=\"https://profiles.wordpress.org/yoavf/\">Yoav Farhi</a>, <a href=\"https://profiles.wordpress.org/yodiyo/\">yodiyo</a>, <a href=\"https://profiles.wordpress.org/fierevere/\">Yui</a>, <a href=\"https://profiles.wordpress.org/yvettesonneveld/\">Yvette Sonneveld</a>, <a href=\"https://profiles.wordpress.org/zaantar/\">zaantar</a>, <a href=\"https://profiles.wordpress.org/tollmanz/\">Zack Tollman</a>, <a href=\"https://profiles.wordpress.org/zalak151291/\">zalak151291</a>, <a href=\"https://profiles.wordpress.org/zebulan/\">Zebulan Stanphill</a>, <a href=\"https://profiles.wordpress.org/chesio/\">Česlav Przywara</a>, <a href=\"https://profiles.wordpress.org/airathalitov/\">АЙРАТ ХАЛИТОВ <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f525.png\" alt=\"?\" class=\"wp-smiley\" /></a>, and <a href=\"https://profiles.wordpress.org/ounziw/\">水野史土</a>.\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<p>Many thanks to all of the community volunteers who contribute in the <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>\n\n\n\n<p>Finally, thanks to all the community translators who worked on WordPress 5.3. Their efforts bring WordPress fully translated to 47 languages at release time, with more on the way.</p>\n\n\n\n<p>If you want 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>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p class=\"has-text-align-center has-medium-font-size\">Thanks for choosing WordPress!</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2019/11/image.png?fit=632%2C414&ssl=1\" alt=\"\" class=\"wp-image-7755\" />\";s: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, 12 Nov 2019 21:38: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: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:49;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"WPTavern: Recurring Payments Feature Launches for WordPress.com and Jetpack Users\";s:7:\"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:29:\"https://wptavern.com/?p=95300\";s:7:\"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:92:\"https://wptavern.com/recurring-payments-feature-launches-for-wordpress-com-and-jetpack-users\";s: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:3978:\"<p>WordPress.com <a href=\"https://en.blog.wordpress.com/2019/11/12/recurring-payments/\">launched a new recurring payments feature</a> its users today.  The payments system will allow bloggers to earn money for their content directly from any page on their site.  The feature is also available for self-hosted WordPress users who have the Jetpack plugin installed.</p>\n\n\n\n<p>The recurring payments system works alongside <a href=\"https://stripe.com\">Stripe</a>, so users must have a connected account to receive payments.  Stripe currently serves over 30 countries around the world.  WordPress.com&rsquo;s documentation maintains an up-to-date <a href=\"https://en.support.wordpress.com/recurring-payments-button/#stripe-supported-countries\">list of countries</a> currently allowed to use the payment gateway.</p>\n\n\n\n<p>The new feature doesn&rsquo;t come for free.  Recurring payments access is only available to users on a premium WordPress.com plan.  Plus, on top of the 2.9% + $0.30 for each payment that Stripe collects, WordPress.com has a <a href=\"https://en.support.wordpress.com/recurring-payments-button/#related-fees\">tiered fee table</a> based on the user&rsquo;s plan.</p>\n\n\n\n<ul><li>WordPress.com eCommerce &ndash; No fee</li><li>WordPress.com Business &ndash; 2% per sale</li><li>WordPress.com Premium &ndash; 4% per sale</li><li>WordPress.com Personal &ndash; 8% per sale</li></ul>\n\n\n\n<p>At the lowest tier, users will see nearly 11% of sales go toward WordPress.com and Stripe fees.  If accepting large volumes of payments, it will make sense for most users to upgrade to a higher plan to offset the fees.  The tiers seem reasonably priced because the infrastructure is completely handled by WordPress.com.  </p>\n\n\n\n<p>Self-hosted users can bypass the WordPress.com fees with a multitude of existing payment plugins.  They will have to decide whether the tools and support provided by WordPress.com is enough of a value-add to go for their service.</p>\n\n\n\n<p>The Jetpack team first <a href=\"https://wptavern.com/jetpack-opens-signup-for-membership-block-beta\">opened a limited beta test</a> for this new feature on May 18, 2019.  At the time, the feature was referred to as a &ldquo;membership block.&rdquo;  The announcement post says that users can &ldquo;offer ongoing subscriptions, site memberships, monthly donations, and more.&rdquo;</p>\n\n\n\n<p>However, members-based content seems to be limited in comparison to other fully-featured membership plugins and would require extra manual work to limit access to a site&rsquo;s premium content.  The WordPress.com recommendation is to <a href=\"https://en.support.wordpress.com/recurring-payments-button/#limit-access-to-content\">password-protect posts</a> and email out the password to subscribers or set up a newsletter.</p>\n\n\n\n<p>This is far from a true membership system, but it could be enough for the average blogger who wants to make a few dollars on the side.  The groundwork is there for a more powerful membership system in the future if the WordPress.com and Jetpack teams want to pursue it.  The market is still ripe for innovation in the membership space.</p>\n\n\n\n<h2>Recurring Payments Block</h2>\n\n\n\n<div class=\"wp-block-image\"><img />Jetpack recurring payments editor block</div>\n\n\n\n<p>The new recurring payments feature requires at least Jetpack version 7.4.  The feature comes in the form of a block for the block editor (Gutenberg) and is located under the &ldquo;Jetpack&rdquo; tab when inserting a new block.</p>\n\n\n\n<p>The block has four fields that can be customized:</p>\n\n\n\n<ul><li>Currency</li><li>Price</li><li>Description</li><li>Renewal Interval &ndash; limited to monthly and yearly renewals</li></ul>\n\n\n\n<p>There is no limit on the number of different payment blocks users can add.  Users can create a new payment plan by adding a new block.  Previous options are backed up and will appear when inserting the block for users who need to output an existing plan on a new post or 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:\"Tue, 12 Nov 2019 19:45:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 30 Dec 2019 05:09:42 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Mon, 30 Dec 2019 05:00:09 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20130911133210\";}','no');
