-- https://www.phpmyadmin.net/
--




--
-- Database: `alex_greenlightkaz`
--

-- --------------------------------------------------------

--
-- Table structure for table `wp_commentmeta`
--

CREATE TABLE `wp_commentmeta` (
  `meta_id` bigint(20) UNSIGNED NOT NULL,
  `comment_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

-- --------------------------------------------------------

--
-- Table structure for table `wp_comments`
--

CREATE TABLE `wp_comments` (
  `comment_ID` bigint(20) UNSIGNED NOT NULL,
  `comment_post_ID` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `comment_author` tinytext NOT NULL,
  `comment_author_email` varchar(100) NOT NULL DEFAULT '',
  `comment_author_url` varchar(200) NOT NULL DEFAULT '',
  `comment_author_IP` varchar(100) NOT NULL DEFAULT '',
  `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_content` text NOT NULL,
  `comment_karma` int(11) NOT NULL DEFAULT '0',
  `comment_approved` varchar(20) NOT NULL DEFAULT '1',
  `comment_agent` varchar(255) NOT NULL DEFAULT '',
  `comment_type` varchar(20) NOT NULL DEFAULT '',
  `comment_parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

-- --------------------------------------------------------

--
-- Table structure for table `wp_links`
--

CREATE TABLE `wp_links` (
  `link_id` bigint(20) UNSIGNED NOT NULL,
  `link_url` varchar(255) NOT NULL DEFAULT '',
  `link_name` varchar(255) NOT NULL DEFAULT '',
  `link_image` varchar(255) NOT NULL DEFAULT '',
  `link_target` varchar(25) NOT NULL DEFAULT '',
  `link_description` varchar(255) NOT NULL DEFAULT '',
  `link_visible` varchar(20) NOT NULL DEFAULT 'Y',
  `link_owner` bigint(20) UNSIGNED NOT NULL DEFAULT '1',
  `link_rating` int(11) NOT NULL DEFAULT '0',
  `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `link_rel` varchar(255) NOT NULL DEFAULT '',
  `link_notes` mediumtext NOT NULL,
  `link_rss` varchar(255) NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

-- --------------------------------------------------------

--
-- Table structure for table `wp_options`
--

CREATE TABLE `wp_options` (
  `option_id` bigint(20) UNSIGNED NOT NULL,
  `option_name` varchar(191) NOT NULL DEFAULT '',
  `option_value` longtext NOT NULL,
  `autoload` varchar(20) NOT NULL DEFAULT 'yes'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;


INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(229, '_transient_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', '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:49:"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:26:"https://wordpress.org/news";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:34:"\n	Thu, 01 Mar 2018 08:41:16 +0000	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:40:"https://wordpress.org/?v=5.0-alpha-42796";s:7:"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:10:{i:0;a:6:{s:4:"data";s:33:"\n		\n		\n		\n		\n				\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:37:"The Month in WordPress: February 2018";s:7:"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/2018/03/the-month-in-wordpress-february-2018/";s: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, 01 Mar 2018 08:41:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:18:"Month in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5613";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:324:"Judging by the flurry of activity across the WordPress project throughout February, it looks like everyone is really getting into the swing of things for 2018. There have been a lot of interesting new developments, so read on to see what the community has been up to for the past month. WordPress 4.9.3 &#38; 4.9.4 [&#8230;]";s: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:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:5936:"<p>Judging by the flurry of activity across the WordPress project throughout February, it looks like everyone is really getting into the swing of things for 2018. There have been a lot of interesting new developments, so read on to see what the community has been up to for the past month.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>WordPress 4.9.3 &amp; 4.9.4</h2>\n\n<p>Early in the month, <a href="https://wordpress.org/news/2018/02/wordpress-4-9-3-maintenance-release/">version 4.9.3 of WordPress was released</a>, including a number of important bug fixes. Unfortunately it introduced a bug that prevented many sites from automatically updating to future releases. To remedy this issue, <a href="https://wordpress.org/news/2018/02/wordpress-4-9-4-maintenance-release/">version 4.9.4 was released</a> the following day requiring many people to manually update their sites.</p>\n\n<p>While this kind of issue is always regrettable, the good thing is that it was fixed quickly, and that not all sites had updated to 4.9.3 yet, which meant they bypassed the bug in that version.</p>\n\n<p>You can find out more technical information about this issue <a href="https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/">on the Core development blog</a>.</p>\n\n<h2>The WordCamp Incubator is Back</h2>\n\n<p>In 2016, the Global Community Team ran an experimental program to help spread WordPress to underserved areas by providing more significant organizing support for their first WordCamp event. This program was dubbed the WordCamp Incubator, and it was so successful in the three cities where it ran that <a href="https://wordpress.org/news/2018/02/wordcamp-incubator-2-0/">the program is back for 2018</a>.</p>\n\n<p>Right now, the Community Team is looking for cities to be a part of this year’s incubator by <a href="https://wordcampcentral.polldaddy.com/s/wordcamp-incubator-program-2018-city-application">taking applications</a>. Additionally, each incubator community will need an experienced WordCamp organizer to assist them as a co-lead organizer for their event — if that sounds interesting to you, then you can <a href="https://wordcampcentral.polldaddy.com/s/wordcamp-incubator-program-2018-co-lead-application">fill in the application form for co-leads</a>.</p>\n\n<p>You can find out further information about the WordCamp Incubator <a href="https://make.wordpress.org/community/2018/02/19/wordcamp-incubator-program-2018-announcement/">on the Community Team blog</a>.</p>\n\n<h2>WordPress Meetup Roundtables scheduled for March</h2>\n\n<p>In order to assist local WordPress meetup organizers with running their meetup groups, some members of the Community Team have organized <a href="https://make.wordpress.org/community/2018/02/23/wordpress-meetup-roundtables-scheduled-for-march/">weekly meetup roundtable discussions through the month of March</a>.</p>\n\n<p>These will be run as video chats at 16:00 UTC every Wednesday this month and will be a great place for meetup organizers to come together and help each other out with practical ideas and advice.</p>\n\n<p>If you are not already in the WordPress meetup program and would like to join, you can find out more information in <a href="https://make.wordpress.org/community/handbook/meetup-organizer/welcome/">the WordPress Meetup Organizer Handbook</a>.</p>\n\n<h2>GDPR Compliance in WordPress Core</h2>\n\n<p>The General Data Protection Regulation (GDPR) is an upcoming regulation that will affect all online services across Europe. In order to prepare for this, a working group has been formed to make sure that WordPress is compliant with the GDPR regulations.</p>\n\n<p>Aside from the fact that this will be a requirement for the project going forward, it will also have an important and significant impact on the privacy and security of WordPress as a whole. The working group has posted <a href="https://make.wordpress.org/core/2018/02/19/proposed-roadmap-tools-for-gdpr-compliance/">their proposed roadmap</a> for this project and it looks very promising.</p>\n\n<p>To get involved in building WordPress Core, jump into the #gdpr-compliance channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>, and follow <a href="https://make.wordpress.org/core/">the Core team blog</a>.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>Further Reading:</h2>\n\n<ul>\n    <li>WPShout published <a href="https://wpshout.com/complete-guide-wordpress-security/">a thorough guide to WordPress security</a>.</li>\n    <li>The Community Team has published interesting statistics from the WordCamp program in <a href="https://make.wordpress.org/community/2018/02/27/wordcamps-in-2016/">2016</a> and <a href="https://make.wordpress.org/community/2018/02/28/wordcamps-in-2017/">2017</a>.</li>\n    <li><a href="https://make.wordpress.org/community/2018/02/15/potential-addition-of-a-new-onboarding-team/">An intriguing proposal has been made</a> for a new ‘Onboarding’ team to be started in the WordPress project.</li>\n    <li>The new editing experience for WordPress, named Gutenberg, continues to be actively developed with <a href="https://make.wordpress.org/core/2018/02/16/whats-new-in-gutenberg-16th-february/">a feature-packed release</a> this past month.</li>\n    <li>The Advanced WordPress Facebook group <a href="https://www.youtube.com/watch?v=4vS_jR5-nIo">held an interview with WordPress co-founder, Matt Mullenweg</a> about the Gutenberg project.</li>\n    <li><a href="https://make.wordpress.org/meta/2018/02/27/two-factor-authentication-on-wp-org/">Two factor authentication is on its way to the WordPress.org network</a> — this will be a great improvement to the overall security of the project.</li>\n</ul>\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5613";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:39:"\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:22:"WordCamp Incubator 2.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:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/news/2018/02/wordcamp-incubator-2-0/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 21 Feb 2018 22:53:20 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:9:"Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:6:"Events";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:8:"WordCamp";s:7:"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=5577";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:343:"WordCamps are informal, community-organized events that are put together by a team of local WordPress users who have a passion for growing their communities. They are born out of active WordPress meetup groups that meet regularly and are able to host an annual WordCamp event. This has worked very well in many communities, with over [&#8230;]";s: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:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2450:"<p><a href="https://central.wordcamp.org/">WordCamps</a> are informal, community-organized events that are put together by a team of local WordPress users who have a passion for growing their communities. They are born out of active WordPress meetup groups that meet regularly and are able to host an annual WordCamp event. This has worked very well in many communities, with over 120 WordCamps being hosted around the world in 2017.<br /></p>\n\n<p>Sometimes though, passionate and enthusiastic community members can’t pull together enough people in their community to make a WordCamp happen. To address this, we introduced <a href="https://wordpress.org/news/2016/02/experiment-wordcamp-incubator/">the WordCamp Incubator program</a> in 2016.<br /></p>\n\n<p>The goal of the incubator program is <strong>to help spread WordPress to underserved areas by providing more significant organizing support for their first WordCamp event.</strong> In 2016, members of <a href="https://make.wordpress.org/community/">the global community team</a> worked with volunteers in three cities — Denpasar, Harare and Medellín — giving direct, hands-on assistance in making local WordCamps possible. All three of these WordCamp incubators <a href="https://make.wordpress.org/community/2017/06/30/wordcamp-incubator-report/">were a great success</a>, so we&#x27;re bringing the incubator program back for 2018.<br /></p>\n\n<p>Where should the next WordCamp incubators be? If you have always wanted a WordCamp in your city but haven’t been able to get a community started, this is a great opportunity. We will be taking applications for the next few weeks, then will get in touch with everyone who applied to discuss the possibilities. We will announce the chosen cities by the end of March.<br /></p>\n\n<p><strong>To apply, </strong><a href="https://wordcampcentral.polldaddy.com/s/wordcamp-incubator-program-2018-city-application"><strong>fill in the application</strong></a><strong> by March 15, 2018.</strong> You don’t need to have any specific information handy, it’s just a form to let us know you’re interested. You can apply to nominate your city even if you don’t want to be the main organizer, but for this to work well we will need local liaisons and volunteers, so please only nominate cities where you live or work so that we have at least one local connection to begin.<br /></p>\n\n<p>We&#x27;re looking forward to hearing from you!<br /></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5577";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:36:"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"WordPress 4.9.4 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:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2018/02/wordpress-4-9-4-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 06 Feb 2018 16:17:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:3:"4.9";s:7:"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=5559";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:350:"WordPress 4.9.4 is now available. This maintenance release fixes a severe bug in 4.9.3, which will cause sites that support automatic background updates to fail to update automatically, and will require action from you (or your host) for it to be updated to 4.9.4. Four years ago with WordPress 3.7 &#8220;Basie&#8221;, we added the ability [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dion Hulse";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1823:"<p>WordPress 4.9.4 is now available.</p>\n<p>This maintenance release fixes a severe bug in 4.9.3, which will cause sites that support automatic background updates to fail to update automatically, and will require action from you (or your host) for it to be updated to 4.9.4.</p>\n<p>Four years ago with <a href="https://wordpress.org/news/2013/10/basie/">WordPress 3.7 &#8220;Basie&#8221;</a>, we added the ability for WordPress to self-update, keeping your website secure and bug-free, even when you weren&#8217;t available to do it yourself. For four years it&#8217;s helped keep millions of installs updated with very few issues over that time. Unfortunately <a href="https://wordpress.org/news/2018/02/wordpress-4-9-3-maintenance-release/">yesterdays 4.9.3 release</a> contained a severe bug which was only discovered after release. The bug will cause WordPress to encounter an error when it attempts to update itself to WordPress 4.9.4, and will require an update to be performed through the WordPress dashboard or hosts update tools.</p>\n<p>WordPress managed hosting companies who install updates automatically for their customers can install the update as normal, and we&#8217;ll be working with other hosts to ensure that as many customers of theirs who can be automatically updated to WordPress 4.9.4 can be.</p>\n<p>For more technical details of the issue, we&#8217;ve <a href="https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/">posted on our Core Development blog</a>. For a full list of changes, consult the <a href="https://core.trac.wordpress.org/query?status=closed&amp;milestone=4.9.4&amp;group=component">list of tickets</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.9.4</a> or visit Dashboard → Updates and click “Update Now.”</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5559";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:33:"\n		\n		\n		\n		\n				\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"WordPress 4.9.3 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:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2018/02/wordpress-4-9-3-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 05 Feb 2018 19:47:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5545";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:372:"WordPress 4.9.3 is now available. This maintenance release fixes 34 bugs in 4.9, including fixes for Customizer changesets, widgets, visual editor, and PHP 7.2 compatibility. For a full list of changes, consult the list of tickets and the changelog. Download WordPress 4.9.3 or visit Dashboard → Updates and click “Update Now.” Sites that support automatic [&#8230;]";s: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:"Sergey Biryukov";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3421:"<p>WordPress 4.9.3 is now available.</p>\n<p>This maintenance release fixes 34 bugs in 4.9, including fixes for Customizer changesets, widgets, visual editor, and PHP 7.2 compatibility. For a full list of changes, consult the <a href="https://core.trac.wordpress.org/query?status=closed&amp;milestone=4.9.3&amp;group=component">list of tickets</a> and the <a href="https://core.trac.wordpress.org/log/branches/4.9?rev=42630&amp;stop_rev=42521">changelog</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.9.3</a> or visit Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.</p>\n<p>Thank you to everyone who contributed to WordPress 4.9.3:</p>\n<p><a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/abdullahramzan/">abdullahramzan</a>, <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/andreiglingeanu/">andreiglingeanu</a>, <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/bpayton/">Brandon Payton</a>, <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a>, <a href="https://profiles.wordpress.org/coleh/">coleh</a>, <a href="https://profiles.wordpress.org/darko-a7/">Darko A7</a>, <a href="https://profiles.wordpress.org/desertsnowman/">David Cramer</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/flixos90/">Felix Arntz</a>, <a href="https://profiles.wordpress.org/frank-klein/">Frank Klein</a>, <a href="https://profiles.wordpress.org/pento/">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a>, <a href="https://profiles.wordpress.org/jbpaul17/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/lizkarkoski/">lizkarkoski</a>, <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/mattyrob/">mattyrob</a>, <a href="https://profiles.wordpress.org/monikarao/">Monika Rao</a>, <a href="https://profiles.wordpress.org/munyagu/">munyagu</a>, <a href="https://profiles.wordpress.org/ndavison/">ndavison</a>, <a href="https://profiles.wordpress.org/nickmomrik/">Nick Momrik</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a>, <a href="https://profiles.wordpress.org/rishishah/">rishishah</a>, <a href="https://profiles.wordpress.org/othellobloke/">Ryan Paul</a>, <a href="https://profiles.wordpress.org/sasiddiqui/">Sami Ahmed Siddiqui</a>, <a href="https://profiles.wordpress.org/sayedwp/">Sayed Taqui</a>, <a href="https://profiles.wordpress.org/seanchayes/">Sean Hayes</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/shooper/">Shawn Hooper</a>, <a href="https://profiles.wordpress.org/netweb/">Stephen Edgar</a>, <a href="https://profiles.wordpress.org/manikmist09/">Sultan Nasir Uddin</a>, <a href="https://profiles.wordpress.org/tigertech/">tigertech</a>, and <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5545";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:33:"\n		\n		\n		\n		\n				\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:36:"The Month in WordPress: January 2018";s:7:"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/2018/02/the-month-in-wordpress-january-2018/";s: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, 02 Feb 2018 08:10: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:8:"category";a:1:{i:0;a:5:{s:4:"data";s:18:"Month in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5541";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:339:"Things got off to a gradual start in 2018 with momentum starting to pick up over the course of the month. There were some notable developments in January, including a new point release and work being done on other important areas of the WordPress project. WordPress 4.9.2 Security and Maintenance Release On January 16, WordPress [&#8230;]";s: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:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3840:"<p>Things got off to a gradual start in 2018 with momentum starting to pick up over the course of the month. There were some notable developments in January, including a new point release and work being done on other important areas of the WordPress project.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>WordPress 4.9.2 Security and Maintenance Release</h2>\n\n<p>On January 16, <a href="https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/">WordPress 4.9.2 was released</a> to fix an important security issue with the media player, as well as a number of other smaller bugs. This release goes a long way to smoothing out the 4.9 release cycle with the next point release, v4.9.3, <a href="https://make.wordpress.org/core/2018/01/31/wordpress-4-9-3-release-pushed-to-february-5th/">due in early February</a>.</p>\n\n<p>To get involved in building WordPress Core, jump into the #core channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>, and follow<a href="https://make.wordpress.org/core/"> the Core team blog</a>.</p>\n\n<h2>Updated Plugin Directory Guidelines</h2>\n\n<p>At the end of 2017, <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/">the guidelines for the Plugin Directory</a> received a significant update to make them clearer and expanded to address certain situations. This does not necessarily make these guidelines complete, but rather more user-friendly and practical; they govern how developers build plugins for the Plugin Directory, so they need to evolve with the global community that the Directory serves.</p>\n\n<p>If you would like to contribute to these guidelines, you can make a pull request to <a href="https://github.com/WordPress/wporg-plugin-guidelines">the GitHub repository</a> or email <a href="mailto:plugins@wordpress.org">plugins@wordpress.org</a>. You can also jump into the #pluginreview channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>Further Reading:</h2>\n\n<ul>\n    <li>Near the end of last year a lot of work was put into improving the standards in the WordPress core codebase and now <a href="https://make.wordpress.org/core/2017/11/30/wordpress-php-now-mostly-conforms-to-wordpress-coding-standards/">the entire platform is at nearly 100% compliance with the WordPress coding standards</a>.</li>\n    <li>Gutenberg, the new editor coming to WordPress core in the next major release, <a href="https://make.wordpress.org/core/2018/01/25/whats-new-in-gutenberg-25th-january/">was updated to v2.1 this month</a> with some great usability and technical improvements.</li>\n    <li>The Global Community Team is <a href="https://make.wordpress.org/community/2018/01/16/2018-goals-for-the-global-community-team-suggestions-time/">taking suggestions for the goals of the Community program in 2018</a>.</li>\n    <li><a href="https://online.wpcampus.org/">WPCampus Online</a>, a digital conference focused on WordPress in higher education, took place on January 30. The videos of the event sessions will be online soon.</li>\n    <li>A WordPress community member <a href="https://wptavern.com/new-toolkit-simplifies-the-process-of-creating-gutenberg-blocks">has released a toolkit</a> to help developers build blocks for Gutenberg.</li>\n    <li>The community team that works to improve the WordPress hosting experience is relatively young, but <a href="https://make.wordpress.org/hosting/2018/01/25/hosting-meeting-notes-january-10-2018/">they have been making some great progress recently</a>.</li>\n</ul>\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5541";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:39:"\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"WordPress 4.9.2 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:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://wordpress.org/news/2018/01/wordpress-4-9-2-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 16 Jan 2018 23:00:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.9";s:7:"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=5376";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:360:"WordPress 4.9.2 is now available. This is a security and maintenance release for all versions since WordPress 3.7﻿. We strongly encourage you to update your sites immediately. An XSS vulnerability was discovered in the Flash fallback files in MediaElement, a library that is included with WordPress. Because the Flash files are no longer needed for [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Ian Dunn";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3946:"<p>WordPress 4.9.2 is now available. This is a <strong>security and maintenance release</strong> for all versions since WordPress 3.7﻿. We strongly encourage you to update your sites immediately.</p>\n\n<p>An XSS vulnerability was discovered in the Flash fallback files in MediaElement, a library that is included with WordPress. Because the Flash files are no longer needed for most use cases, they have been removed from WordPress.</p>\n\n<p>MediaElement has released a new version that contains a fix for the bug, and <a href="https://wordpress.org/plugins/mediaelement-flash-fallbacks/">a WordPress plugin containing the fixed files</a> is available in the plugin repository.</p>\n\n<p>Thank you to the reporters of this issue for practicing <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">responsible security disclosure</a>: <a href="https://opnsec.com">Enguerran Gillier</a> and <a href="https://widiz.com/">Widiz﻿</a>.</p>\n\n<p>21 other bugs were fixed in WordPress 4.9.2. Particularly of note were:</p>\n\n<ul>\n    <li>JavaScript errors that prevented saving posts in Firefox have been fixed.</li>\n    <li>The previous taxonomy-agnostic behavior of <code>get_category_link()</code> and <code>category_description()</code> was restored.</li>\n    <li>Switching themes will now attempt to restore previous widget assignments, even when there are no sidebars to map.<br /></li>\n</ul>\n\n<p>The Codex has <a href="https://codex.wordpress.org/Version_4.9.2">more information about all of the issues fixed in 4.9.2</a>, if you&#x27;d like to learn more.</p>\n\n<p>﻿<a href="https://wordpress.org/download/"></a><a href="https://wordpress.org/download/">Download WordPress 4.9.2</a> or venture over to Dashboard → Updates and click &quot;Update Now.&quot; Sites that support automatic background updates are already beginning to update automatically.</p>\n\n<p>Thank you to everyone who contributed to WordPress 4.9.2:</p>\n\n<p><a href="https://profiles.wordpress.org/0x6f0/">0x6f0</a>, <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</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/blobfolio/">Blobfolio</a>, <a href="https://profiles.wordpress.org/boonebgorges/">Boone Gorges</a>, <a href="https://profiles.wordpress.org/icaleb/">Caleb Burks</a>, <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a>, <a href="https://profiles.wordpress.org/chasewg/">chasewg</a>, <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a>, <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a>, <a href="https://profiles.wordpress.org/hardik-amipara/">Hardik Amipara</a>, <a href="https://profiles.wordpress.org/ionvv/">ionvv</a>, <a href="https://profiles.wordpress.org/jaswrks/">Jason Caldwell</a>, <a href="https://profiles.wordpress.org/jbpaul17/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/jeremyfelt/">Jeremy Felt</a>, <a href="https://profiles.wordpress.org/joemcgill/">Joe McGill</a>, <a href="https://profiles.wordpress.org/johnschulz/">johnschulz</a>, <a href="https://profiles.wordpress.org/juiiee8487/">Juhi Patel</a>, <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a>, <a href="https://profiles.wordpress.org/markjaquith/">Mark Jaquith</a>, <a href="https://profiles.wordpress.org/rabmalin/">Nilambar Sharma</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a>, <a href="https://profiles.wordpress.org/rinkuyadav999/">Rinku Y</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, and <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a>.﻿<strong></strong><br /></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5376";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:33:"\n		\n		\n		\n		\n				\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:37:"The Month in WordPress: December 2017";s:7:"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/2018/01/the-month-in-wordpress-december-2017/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 03 Jan 2018 10: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:8:"category";a:1:{i:0;a:5:{s:4:"data";s:18:"Month in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5424";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:311:"Activity slowed down in December in the WordPress community, particularly in the last two weeks. However, the month started off with a big event and work pushed forward in a number of key areas of the project. Read on to find out more about what transpired in the WordPress community as 2017 came to a [&#8230;]";s: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:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4711:"<p>Activity slowed down in December in the WordPress community, particularly in the last two weeks. However, the month started off with a big event and work pushed forward in a number of key areas of the project. Read on to find out more about what transpired in the WordPress community as 2017 came to a close.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>WordCamp US 2017 Brings the Community Together</h2>\n\n<p>The latest edition of <a href="https://2017.us.wordcamp.org/">WordCamp US</a> took place last month in Nashville on December 1-3. The event brought together over 1,400 WordPress enthusiasts from around the world, fostering a deeper, more engaged global community.</p>\n\n<p>While attending a WordCamp is always a unique experience, you can catch up on <a href="https://wordpress.tv/event/wordcamp-us-2017/">the sessions on WordPress.tv</a> and look through <a href="https://www.facebook.com/pg/WordCampUSA/photos/?tab=albums">the event photos on Facebook</a> to get a feel for how it all happened. Of course, <a href="https://wordpress.tv/2017/12/04/matt-mullenweg-state-of-the-word-2017/">Matt Mullenweg’s State of the Word</a> talk is always one of the highlights at this event.</p>\n\n<p>The next WordCamp US will be held in Nashville again in 2018, but if you would like to see it hosted in your city in 2019 and 2020, then <a href="https://make.wordpress.org/community/2017/12/19/apply-to-host-wordcamp-us-2019-2020/">you have until February 2 to apply</a>.</p>\n\n<h2>WordPress User Survey Data Is Published</h2>\n\n<p>Over the last few years, tens of thousands of WordPress users all over the world have filled out the annual WordPress user survey. The results of that survey are used to improve the WordPress project, but that data has mostly remained private. This has changed now and <a href="https://wordpress.org/news/2017/12/wordpress-user-survey-data-for-2015-2017/">the results from the last three surveys are now publicly available</a> for everyone to analyze.</p>\n\n<p>The data will be useful to anyone involved in WordPress since it provides a detailed look at who uses WordPress and what they do with it — information that can help inform product development decisions across the board.</p>\n\n<h2>New WordPress.org Team for the Tide Project</h2>\n\n<p>As announced at WordCamp US, <a href="https://make.wordpress.org/tide/2017/12/02/new-home/">the Tide project is being brought under the WordPress.org umbrella</a> to be managed and developed by the community.</p>\n\n<p>Tide is a series of automated tests run against every plugin and theme in the directory to help WordPress users make informed decisions about the plugins and themes that they choose to install.</p>\n\n<p>To get involved in developing Tide, jump into the #tide channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>, and follow <a href="https://make.wordpress.org/tide/">the Tide team blog</a>.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>Further Reading:</h2>\n\n<ul>\n    <li>If you’re following the development of Gutenberg, or if you want a primer on where it’s headed, then <a href="https://wordpress.tv/2017/12/10/morten-rand-hendriksen-gutenberg-and-the-wordpress-of-tomorrow/">Morten Rand-Hendriksen’s talk from WordCamp US</a> is a must watch.</li>\n    <li>The annual surveys for WordPress <a href="https://wordpressdotorg.polldaddy.com/s/2017-annual-meetup-member-survey">meetup members</a> and <a href="https://wordpressdotorg.polldaddy.com/s/2017-annual-meetup-organizer-survey">meetup organizers</a> are available for people to fill out — if you’re involved in or attend your local meetup group then be sure to complete those.</li>\n    <li>10up has <a href="https://distributorplugin.com/">a brand new plugin in beta</a> that will assist with powerful and flexible content publishing and syndication across WordPress sites.</li>\n    <li><a href="https://make.wordpress.org/community/2017/12/07/should-we-change-the-default-wordcamp-theme-to-campsite-2017/">The Community Team is exploring a move</a> to make the recently developed CampSite theme the default theme for all new WordCamp websites. This is the theme that was developed and employed for <a href="https://2017.europe.wordcamp.org">WordCamp Europe 2017</a>.</li>\n    <li>The team working on the multisite features of WordPress Core has recently published <a href="https://make.wordpress.org/core/2017/12/19/multisite-roadmap-published/">their planned roadmap for development</a>.</li>\n</ul>\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5424";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:39:"\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:40:"WordPress User Survey Data for 2015-2017";s:7:"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://wordpress.org/news/2017/12/wordpress-user-survey-data-for-2015-2017/";s: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 Dec 2017 21:40:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:7:"General";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:6:"WrapUp";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:6:"survey";s:7:"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=5310";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:321:"For many years, we&#8217;ve invited folks to tell us how they use WordPress by filling out an annual survey. In the past, interesting results from this survey have been shared in the annual State of the Word address. This year, for the first time, the results of the 2017 survey are being published on WordPress [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Andrea Middleton";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:64131:"<p>For many years, we&#8217;ve invited folks to tell us how they use WordPress by filling out an annual survey. In the past, interesting results from this survey have been shared in the annual <a href="https://ma.tt/2017/12/state-of-the-word-2017/">State of the Word</a> address. This year, for the first time, the results of the 2017 survey are being published on WordPress News, along with the results of the 2015 and 2016 survey.</p>\n<p>So that information from the survey doesn&#8217;t reveal anything that respondents might consider private, we do not publish a full export of the raw data. We’d love to make this information as accessible as possible, though, so if you have a suggestion for an OS project or tool we can put the data into that allows people to play with it that still protects individual response privacy, please leave a comment on this post!</p>\n<h4>Major Groups</h4>\n<p>This survey features multiple groups, dividing respondents at the first question:</p>\n<blockquote><p>Which of the following best describes how you use WordPress? (<em>Mandatory</em>)</p></blockquote>\n<p>Those who selected &#8220;I&#8217;m a designer or developer, or I work for a company that designs/develops websites; I use WordPress to build websites and/or blogs for others. (This might include theme development, writing plugins, or other custom work.)&#8221; were served questions from what we&#8217;ll call the &#8220;WordPress Professionals&#8221; group.</p>\n<p>This &#8220;WordPress Professionals&#8221; group is further divided into WordPress Company and WordPress Freelancer/Hobbyist groups, based on how the respondent answered the question, &#8220;Which of the following best describes your involvement with WordPress? (2015) / Do you work for a company, or on your own? (2016-17).&#8221;</p>\n<p>Those who selected &#8220;I own, run, or contribute to a blog or website that is built with WordPress.&#8221; were served questions in what we&#8217;re calling the &#8220;WordPress Users&#8221; group.</p>\n<p>The relevant survey group is noted in each table below. In the case of questions that were served to different groups in 2015 but then served to all respondents in 2016 and 2017, the group responses from 2015 have been consolidated into one set of data for easier comparison between years.</p>\n<h4>Survey results</h4>\n<p><a href="#pro">Jump to answers from WordPress Professionals</a></p>\n<p><a href="#user">Jump to answers from WordPress Users</a></p>\n<p><a href="#all">Jump to answers from All Respondents</a></p>\n<p><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></p>\n<h3>Which of the following best describes how you use WordPress? (Mandatory)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td>Number of responses (since this question was mandatory, the number of responses here is the total number for the survey)</td>\n<td>45,995</td>\n<td></td>\n<td>15,585</td>\n<td></td>\n<td>16,029</td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;m a designer or developer, or I work for a company that designs/develops websites; I use WordPress to build websites and/or blogs for others. (This might include theme development, writing plugins, other custom work.)</td>\n<td>26,662</td>\n<td>58%</td>\n<td>8,838</td>\n<td>57%</td>\n<td>9,099</td>\n<td>57%</td>\n</tr>\n<tr>\n<td>I own, run, or contribute to a blog or website that is built with WordPress.</td>\n<td>16,130</td>\n<td>35%</td>\n<td>5,293</td>\n<td>34%</td>\n<td>5,625</td>\n<td>35%</td>\n</tr>\n<tr>\n<td>Neither of the above.</td>\n<td>3,204</td>\n<td>7%</td>\n<td>1,460</td>\n<td>9%</td>\n<td>1,306</td>\n<td>8%</td>\n</tr>\n</tbody>\n</table>\n<h2 id="pro">WordPress Professionals</h2>\n<h3><strong>Which of the following best describes your involvement with WordPress? (Mandatory, 2015) / Do you work for a company, or on your own? (Mandatory, 2016-17)</strong></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>26,699</td>\n<td></td>\n<td>8,838</td>\n<td></td>\n<td>9,101</td>\n<td></td>\n</tr>\n<tr>\n<td>My primary job is working for a company or organization that uses WordPress.</td>\n<td>9,505</td>\n<td>36%</td>\n<td>3,529</td>\n<td>40%</td>\n<td>3,660</td>\n<td>40%</td>\n</tr>\n<tr>\n<td>My primary job is as a self-employed designer or developer that uses WordPress.</td>\n<td>9,310</td>\n<td>35%</td>\n<td>3,188</td>\n<td>36%</td>\n<td>3,440</td>\n<td>38%</td>\n</tr>\n<tr>\n<td>I earn money from part-time or occasional freelance work involving WordPress.</td>\n<td>5,954</td>\n<td>22%</td>\n<td>1,633</td>\n<td>18%</td>\n<td>1,590</td>\n<td>17%</td>\n</tr>\n<tr>\n<td>Work that I do involving WordPress is just a hobby, I don&#8217;t make money from it.</td>\n<td>1,930</td>\n<td>7%</td>\n<td>491</td>\n<td>6%</td>\n<td>411</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>How does your company or organization work with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,342</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Build/design and/or maintain websites or blogs for other people, companies, or organizations.</td>\n<td>7,772</td>\n<td>27%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Develop or customize themes.</td>\n<td>5,404</td>\n<td>19%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Build/design and/or maintain websites or blogs for my own use.</td>\n<td>4,733</td>\n<td>16%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Host websites for customers.</td>\n<td>4,397</td>\n<td>15%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Develop or distribute plugins.</td>\n<td>3,181</td>\n<td>11%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Provide educational resources to help others to use WordPress.</td>\n<td>1,349</td>\n<td>5%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Sponsor and/or attend WordCamps.</td>\n<td>1,127</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Contribute bug reports and/or patches to WordPress core.</td>\n<td>914</td>\n<td>3%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>182</td>\n<td> 1%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>3,457</td>\n<td></td>\n<td>3,598</td>\n<td></td>\n</tr>\n<tr>\n<td>We make websites for others.</td>\n<td></td>\n<td></td>\n<td>2,695</td>\n<td>24%</td>\n<td>2,722</td>\n<td>23%</td>\n</tr>\n<tr>\n<td>We make websites for ourselves.</td>\n<td></td>\n<td></td>\n<td>2,355</td>\n<td>21%</td>\n<td>2,470</td>\n<td>21%</td>\n</tr>\n<tr>\n<td>We develop or customize themes.</td>\n<td></td>\n<td></td>\n<td>1,866</td>\n<td>16%</td>\n<td>1,910</td>\n<td>16%</td>\n</tr>\n<tr>\n<td>We host websites for others.</td>\n<td></td>\n<td></td>\n<td>1,564</td>\n<td>14%</td>\n<td>1,595</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>We develop or distribute plugins.</td>\n<td></td>\n<td></td>\n<td>1,283</td>\n<td>11%</td>\n<td>1,342</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>We provide educational resources to help others to use WordPress.</td>\n<td></td>\n<td></td>\n<td>581</td>\n<td>5%</td>\n<td>631</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>We sponsor and/or attend WordCamps.</td>\n<td></td>\n<td></td>\n<td>561</td>\n<td>5%</td>\n<td>579</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>We contribute bug reports and/or patches to WordPress core.</td>\n<td></td>\n<td></td>\n<td>444</td>\n<td>4%</td>\n<td>468</td>\n<td>4%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td></td>\n<td></td>\n<td>98</td>\n<td>1%</td>\n<td>96</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<p><strong>How would you describe the business of your typical client(s)? (2015) / How would you describe the business of your typical client/customer? (2016, 2017)</strong></p>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,154</td>\n<td></td>\n<td>3,317</td>\n<td></td>\n<td>3,498</td>\n<td></td>\n</tr>\n<tr>\n<td>Small business</td>\n<td>6,893</td>\n<td>32%</td>\n<td>2,398</td>\n<td>31%</td>\n<td>2,510</td>\n<td>31%</td>\n</tr>\n<tr>\n<td>Large business or Enterprise</td>\n<td>3,635</td>\n<td>17%</td>\n<td>1,361</td>\n<td>18%</td>\n<td>1,447</td>\n<td>18%</td>\n</tr>\n<tr>\n<td>Non-profit</td>\n<td>2,644</td>\n<td>12%</td>\n<td>934</td>\n<td>12%</td>\n<td>992</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>Individual</td>\n<td>2,600</td>\n<td>12%</td>\n<td>888</td>\n<td>12%</td>\n<td>1,022</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>Education</td>\n<td>2,344</td>\n<td>11%</td>\n<td>854</td>\n<td>11%</td>\n<td>966</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>Website development (sub-contracting)</td>\n<td>2,065</td>\n<td>10%</td>\n<td>637</td>\n<td>8%</td>\n<td>677</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>Government</td>\n<td>1,410</td>\n<td>6%</td>\n<td>524</td>\n<td>7%</td>\n<td>552</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>127</td>\n<td>1%</td>\n<td>66</td>\n<td>1%</td>\n<td>64</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<p><strong>How does your company or organization use WordPress when developing websites? (2015) / When making websites, how does your company or organization use WordPress? (2016, 2017)</strong></p>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,078</td>\n<td></td>\n<td>3,369</td>\n<td></td>\n<td>3,552</td>\n<td></td>\n</tr>\n<tr>\n<td>Mostly as a content management system (CMS)</td>\n<td>6,361</td>\n<td>70%</td>\n<td>2,482</td>\n<td>74%</td>\n<td>2,640</td>\n<td>74%</td>\n</tr>\n<tr>\n<td>About half the time as a blogging platform and half the time as a CMS</td>\n<td>1,222</td>\n<td>13%</td>\n<td>370</td>\n<td>11%</td>\n<td>383</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Mostly as a blogging platform</td>\n<td>721</td>\n<td>8%</td>\n<td>137</td>\n<td>4%</td>\n<td>129</td>\n<td>4%</td>\n</tr>\n<tr>\n<td>Mostly as an application framework</td>\n<td>629</td>\n<td>7%</td>\n<td>303</td>\n<td>9%</td>\n<td>303</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>145</td>\n<td>2%</td>\n<td>78</td>\n<td>2%</td>\n<td>97</td>\n<td>3%</td>\n</tr>\n</tbody>\n</table>\n<h3>How much is your average WordPress site customized from the original WordPress installation?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,054</td>\n<td></td>\n<td>3,302</td>\n<td></td>\n<td>3,473</td>\n<td></td>\n</tr>\n<tr>\n<td>A lot of work has been done, the front end is unrecognizable, but the Dashboard still looks like the usual WordPress interface.</td>\n<td>5,651</td>\n<td>62%</td>\n<td>2,025</td>\n<td>61%</td>\n<td>2,105</td>\n<td>61%</td>\n</tr>\n<tr>\n<td>There&#8217;s a different theme and some plugins have been added.</td>\n<td>2,230</td>\n<td>25%</td>\n<td>799</td>\n<td>24%</td>\n<td>905</td>\n<td>26%</td>\n</tr>\n<tr>\n<td>Not at all, it&#8217;s still pretty much the same as the original download.</td>\n<td>756</td>\n<td>8%</td>\n<td>302</td>\n<td>9%</td>\n<td>298</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>You&#8217;d never know this was a WordPress installation, everything (including the admin) has been customized.</td>\n<td>417</td>\n<td>5%</td>\n<td>177</td>\n<td>5%</td>\n<td>165</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>Roughly how many currently active WordPress sites has your company or organization built?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>8,801</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>200 +</td>\n<td>1,074</td>\n<td>12%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>51 &#8211; 200</td>\n<td>1,721</td>\n<td>20%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>21 &#8211; 50</td>\n<td>1,718</td>\n<td>20%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>11 &#8211; 20</td>\n<td>1,284</td>\n<td>15%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>6 &#8211; 10</td>\n<td>1,109</td>\n<td>13%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>2 &#8211; 5</td>\n<td>1,418</td>\n<td>16%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>1</td>\n<td>390</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>0</td>\n<td>87</td>\n<td>1%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>3,358</td>\n<td></td>\n<td>3,540</td>\n<td></td>\n</tr>\n<tr>\n<td>Thousands.</td>\n<td></td>\n<td></td>\n<td>291</td>\n<td>9%</td>\n<td>331</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Hundreds.</td>\n<td></td>\n<td></td>\n<td>770</td>\n<td>23%</td>\n<td>894</td>\n<td>25%</td>\n</tr>\n<tr>\n<td>Fewer than a hundred.</td>\n<td></td>\n<td></td>\n<td>1,144</td>\n<td>34%</td>\n<td>1,177</td>\n<td>33%</td>\n</tr>\n<tr>\n<td>Just a few, but they are really great.</td>\n<td></td>\n<td></td>\n<td>926</td>\n<td>28%</td>\n<td>896</td>\n<td>25%</td>\n</tr>\n<tr>\n<td>Prefer not to answer.</td>\n<td></td>\n<td></td>\n<td>228</td>\n<td>7%</td>\n<td>242</td>\n<td>7%</td>\n</tr>\n</tbody>\n</table>\n<h3>How many person-hours (of your company&#8217;s work) does the typical site take to complete?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,091</td>\n<td></td>\n<td>3,353</td>\n<td></td>\n<td>3,522</td>\n<td></td>\n</tr>\n<tr>\n<td>More than 200</td>\n<td>939</td>\n<td>10%</td>\n<td>309</td>\n<td>9%</td>\n<td>325</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>100 &#8211; 200</td>\n<td>1080</td>\n<td>12%</td>\n<td>329</td>\n<td>10%</td>\n<td>367</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>60 &#8211; 100</td>\n<td>1541</td>\n<td>17%</td>\n<td>527</td>\n<td>16%</td>\n<td>513</td>\n<td>15%</td>\n</tr>\n<tr>\n<td>40 &#8211; 60</td>\n<td>1854</td>\n<td>20%</td>\n<td>583</td>\n<td>17%</td>\n<td>620</td>\n<td>18%</td>\n</tr>\n<tr>\n<td>20 &#8211; 40</td>\n<td>2066</td>\n<td>23%</td>\n<td>691</td>\n<td>21%</td>\n<td>685</td>\n<td>19%</td>\n</tr>\n<tr>\n<td>Fewer than 20</td>\n<td>1611</td>\n<td>18%</td>\n<td>479</td>\n<td>14%</td>\n<td>519</td>\n<td>15%</td>\n</tr>\n<tr>\n<td>Prefer not to answer (2016, 2017)</td>\n<td></td>\n<td></td>\n<td>436</td>\n<td>13%</td>\n<td>493</td>\n<td>14%</td>\n</tr>\n</tbody>\n</table>\n<h3>Roughly what percentage of your company or organization&#8217;s output is based around WordPress (as opposed to other platforms or software)?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>8,950</td>\n<td></td>\n<td>3,345</td>\n<td></td>\n<td>3,503</td>\n<td></td>\n</tr>\n<tr>\n<td>100 %</td>\n<td>1,089</td>\n<td>12%</td>\n<td>438</td>\n<td>13%</td>\n<td>480</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>90 %</td>\n<td>1,043</td>\n<td>12%</td>\n<td>417</td>\n<td>12%</td>\n<td>459</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>80 %</td>\n<td>955</td>\n<td>11%</td>\n<td>367</td>\n<td>11%</td>\n<td>424</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>70 %</td>\n<td>831</td>\n<td>9%</td>\n<td>305</td>\n<td>9%</td>\n<td>344</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>60 %</td>\n<td>534</td>\n<td>6%</td>\n<td>246</td>\n<td>7%</td>\n<td>226</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>50 %</td>\n<td>973</td>\n<td>11%</td>\n<td>335</td>\n<td>10%</td>\n<td>338</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>40 %</td>\n<td>613</td>\n<td>7%</td>\n<td>245</td>\n<td>7%</td>\n<td>202</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>30 %</td>\n<td>877</td>\n<td>10%</td>\n<td>335</td>\n<td>10%</td>\n<td>310</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>20 %</td>\n<td>806</td>\n<td>9%</td>\n<td>242</td>\n<td>7%</td>\n<td>280</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>10 %</td>\n<td>1,039</td>\n<td>12%</td>\n<td>344</td>\n<td>10%</td>\n<td>348</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>0 %</td>\n<td>190</td>\n<td>2%</td>\n<td>72</td>\n<td>2%</td>\n<td>92</td>\n<td>3%</td>\n</tr>\n</tbody>\n</table>\n<h3>In which of the following ways do you work with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>17,009</td>\n<td></td>\n<td>5,221</td>\n<td></td>\n<td>5,425</td>\n<td></td>\n</tr>\n<tr>\n<td>Build/design and/or maintain websites or blogs for other people, companies, or organizations</td>\n<td>15,342</td>\n<td>34%</td>\n<td>4,795</td>\n<td>34%</td>\n<td>5,064</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Develop or customize themes</td>\n<td>10,549</td>\n<td>24%</td>\n<td>2,997</td>\n<td>21%</td>\n<td>3,021</td>\n<td>20%</td>\n</tr>\n<tr>\n<td>Host websites for customers</td>\n<td>8,142</td>\n<td>18%</td>\n<td>2,466</td>\n<td>17%</td>\n<td>2,728</td>\n<td>18%</td>\n</tr>\n<tr>\n<td>Develop or distribute plugins</td>\n<td>4,125</td>\n<td>9%</td>\n<td>1,395</td>\n<td>10%</td>\n<td>1,416</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Provide educational resources to help others to use WordPress</td>\n<td>3,276</td>\n<td>7%</td>\n<td>1,187</td>\n<td>8%</td>\n<td>1,308</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Sponsor and/or attend WordCamps</td>\n<td>1,559</td>\n<td>4%</td>\n<td>648</td>\n<td>5%</td>\n<td>724</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>Contribute bug reports and/or patches to WordPress core</td>\n<td>1,107</td>\n<td>2%</td>\n<td>381</td>\n<td>3%</td>\n<td>393</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>389</td>\n<td>1%</td>\n<td>243</td>\n<td>2%</td>\n<td>299</td>\n<td>2%</td>\n</tr>\n</tbody>\n</table>\n<h3>How would you describe the business of your typical client(s)?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,863</td>\n<td></td>\n<td>5,151</td>\n<td></td>\n<td>5,353</td>\n<td></td>\n</tr>\n<tr>\n<td>Small business</td>\n<td>14,185</td>\n<td>35%</td>\n<td>4,342</td>\n<td>35%</td>\n<td>4,622</td>\n<td>36%</td>\n</tr>\n<tr>\n<td>Individual</td>\n<td>8,513</td>\n<td>21%</td>\n<td>2,581</td>\n<td>21%</td>\n<td>2,583</td>\n<td>20%</td>\n</tr>\n<tr>\n<td>Non-profit</td>\n<td>6,585</td>\n<td>16%</td>\n<td>2,004</td>\n<td>16%</td>\n<td>2,113</td>\n<td>16%</td>\n</tr>\n<tr>\n<td>Website development (sub-contracting)</td>\n<td>4,301</td>\n<td>11%</td>\n<td>1,258</td>\n<td>10%</td>\n<td>1,216</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Education</td>\n<td>3,458</td>\n<td>8%</td>\n<td>1,049</td>\n<td>8%</td>\n<td>1,139</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Large business or Enterprise</td>\n<td>2,391</td>\n<td>6%</td>\n<td>805</td>\n<td>6%</td>\n<td>857</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>Government</td>\n<td>1,150</td>\n<td>3%</td>\n<td>300</td>\n<td>2%</td>\n<td>329</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>173</td>\n<td>0%</td>\n<td>101</td>\n<td>1%</td>\n<td>99</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>How do you use WordPress in your development?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,768</td>\n<td></td>\n<td>5,145</td>\n<td></td>\n<td>5,372</td>\n<td></td>\n</tr>\n<tr>\n<td>Mostly as a content management system (CMS)</td>\n<td>11,754</td>\n<td>70%</td>\n<td>3,641</td>\n<td>71%</td>\n<td>3,959</td>\n<td>74%</td>\n</tr>\n<tr>\n<td>About half the time as a blogging platform and half the time as a CMS</td>\n<td>2,825</td>\n<td>17%</td>\n<td>812</td>\n<td>16%</td>\n<td>721</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>Mostly as an application framework</td>\n<td>1,012</td>\n<td>6%</td>\n<td>343</td>\n<td>7%</td>\n<td>344</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Mostly as a blogging platform</td>\n<td>992</td>\n<td>6%</td>\n<td>246</td>\n<td>5%</td>\n<td>226</td>\n<td>4%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>185</td>\n<td>1%</td>\n<td>105</td>\n<td>2%</td>\n<td>122</td>\n<td>2%</td>\n</tr>\n</tbody>\n</table>\n<h3>How much is your average WordPress site customized from the original WordPress installation?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,699</td>\n<td></td>\n<td>5,131</td>\n<td></td>\n<td>5,317</td>\n<td></td>\n</tr>\n<tr>\n<td>A lot of work has been done, the front end is unrecognizable, but the Dashboard still looks like the usual WordPress interface.</td>\n<td>9,457</td>\n<td>57%</td>\n<td>2,837</td>\n<td>55%</td>\n<td>2,998</td>\n<td>56%</td>\n</tr>\n<tr>\n<td>There&#8217;s a different theme and some plugins have been added.</td>\n<td>5,526</td>\n<td>33%</td>\n<td>1,694</td>\n<td>33%</td>\n<td>1,781</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Not at all, it&#8217;s still pretty much the same as the original download.</td>\n<td>977</td>\n<td>6%</td>\n<td>341</td>\n<td>7%</td>\n<td>310</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>You&#8217;d never know this was a WordPress installation, everything (including the admin) has been customized.</td>\n<td>739</td>\n<td>4%</td>\n<td>261</td>\n<td>5%</td>\n<td>228</td>\n<td>4%</td>\n</tr>\n</tbody>\n</table>\n<h3>How many currently active WordPress sites have you built? (2015) / Roughly how many currently active WordPress sites have you built? (2016, 2017)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,690</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>200 +</td>\n<td>514</td>\n<td>3%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>51 &#8211; 200</td>\n<td>1,728</td>\n<td>10%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>21 &#8211; 50</td>\n<td>3,000</td>\n<td>18%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>11 &#8211; 20</td>\n<td>3,146</td>\n<td>19%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>6 &#8211; 10</td>\n<td>3,405</td>\n<td>20%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>2 &#8211; 5</td>\n<td>3,838</td>\n<td>23%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>1</td>\n<td>698</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>0</td>\n<td>361</td>\n<td>2%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>5,165</td>\n<td></td>\n<td>5367</td>\n<td></td>\n</tr>\n<tr>\n<td>Thousands.</td>\n<td></td>\n<td></td>\n<td>110</td>\n<td>2%</td>\n<td>104</td>\n<td>2%</td>\n</tr>\n<tr>\n<td>Hundreds.</td>\n<td></td>\n<td></td>\n<td>603</td>\n<td>12%</td>\n<td>713</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>Fewer than a hundred.</td>\n<td></td>\n<td></td>\n<td>2,264</td>\n<td>44%</td>\n<td>2,457</td>\n<td>46%</td>\n</tr>\n<tr>\n<td>Just a few, but they are really great.</td>\n<td></td>\n<td></td>\n<td>1,871</td>\n<td>36%</td>\n<td>1,813</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Prefer not to answer.</td>\n<td></td>\n<td></td>\n<td>319</td>\n<td>6%</td>\n<td>280</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>Roughly what percentage of your working time is spent working with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,658</td>\n<td></td>\n<td>5,039</td>\n<td></td>\n<td>5,241</td>\n<td></td>\n</tr>\n<tr>\n<td>100 %</td>\n<td>949</td>\n<td>6%</td>\n<td>459</td>\n<td>9%</td>\n<td>461</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>90 %</td>\n<td>1,300</td>\n<td>8%</td>\n<td>527</td>\n<td>10%</td>\n<td>540</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>80 %</td>\n<td>1,784</td>\n<td>11%</td>\n<td>637</td>\n<td>13%</td>\n<td>711</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>70 %</td>\n<td>1,850</td>\n<td>11%</td>\n<td>608</td>\n<td>12%</td>\n<td>627</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>60 %</td>\n<td>1,313</td>\n<td>8%</td>\n<td>438</td>\n<td>9%</td>\n<td>465</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>50 %</td>\n<td>2,095</td>\n<td>13%</td>\n<td>612</td>\n<td>12%</td>\n<td>639</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>40 %</td>\n<td>1,438</td>\n<td>9%</td>\n<td>391</td>\n<td>8%</td>\n<td>384</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>30 %</td>\n<td>2,076</td>\n<td>12%</td>\n<td>530</td>\n<td>11%</td>\n<td>511</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>20 %</td>\n<td>1,743</td>\n<td>10%</td>\n<td>445</td>\n<td>9%</td>\n<td>429</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>10 %</td>\n<td>1,819</td>\n<td>11%</td>\n<td>342</td>\n<td>7%</td>\n<td>419</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>0 %</td>\n<td>291</td>\n<td>2%</td>\n<td>52</td>\n<td>1%</td>\n<td>55</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>How many hours of your work does the typical site take to complete? (2015) / How many hours of work does your typical WordPress project take to launch? (2016, 2017)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,670</td>\n<td></td>\n<td>5,164</td>\n<td></td>\n<td>5,378</td>\n<td></td>\n</tr>\n<tr>\n<td>More than 200</td>\n<td>503</td>\n<td>3%</td>\n<td>222</td>\n<td>4%</td>\n<td>245</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>100 &#8211; 200</td>\n<td>973</td>\n<td>6%</td>\n<td>386</td>\n<td>7%</td>\n<td>393</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>60 &#8211; 100</td>\n<td>2,277</td>\n<td>14%</td>\n<td>788</td>\n<td>15%</td>\n<td>815</td>\n<td>15%</td>\n</tr>\n<tr>\n<td>40 &#8211; 60</td>\n<td>3,896</td>\n<td>23%</td>\n<td>1,153</td>\n<td>22%</td>\n<td>1,216</td>\n<td>23%</td>\n</tr>\n<tr>\n<td>20 &#8211; 40</td>\n<td>6,068</td>\n<td>36%</td>\n<td>1,487</td>\n<td>29%</td>\n<td>1,582</td>\n<td>29%</td>\n</tr>\n<tr>\n<td>Fewer than 20</td>\n<td>2,953</td>\n<td>18%</td>\n<td>712</td>\n<td>14%</td>\n<td>751</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>418</td>\n<td>8%</td>\n<td>376</td>\n<td>7%</td>\n</tr>\n</tbody>\n</table>\n<h3>Which of the following have you done with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" /> </colgroup>\n</table>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional (Company/Freelancer/Hobbyist)</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>20,687</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I’ve written a theme from scratch.</td>\n<td>11,894</td>\n<td>25%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I’ve written a plugin.</td>\n<td>9,719</td>\n<td>21%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve answered a question in the WordPress forum.</td>\n<td>8,805</td>\n<td>19%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve attended a WordPress meetup.</td>\n<td>4,062</td>\n<td>9%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve submitted a WordPress bug report.</td>\n<td>4,062</td>\n<td>9%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve attended a WordCamp.</td>\n<td>3,571</td>\n<td>8%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve contributed to WordPress documentation.</td>\n<td>1,778</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>1,739</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve contributed a WordPress core patch.</td>\n<td>1,055</td>\n<td>2%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n<h3>What&#8217;s the best thing about WordPress?<a href="#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>22,718</td>\n<td></td>\n<td>7,891</td>\n<td></td>\n<td>8,267</td>\n<td></td>\n</tr>\n<tr>\n<td>Easy/simple/user-friendly</td>\n<td>9,450</td>\n<td>42%</td>\n<td>3,454</td>\n<td>44%</td>\n<td>3,852</td>\n<td>47%</td>\n</tr>\n<tr>\n<td>Customizable/extensible/modular/plugins/themes</td>\n<td>8,601</td>\n<td>38%</td>\n<td>3,116</td>\n<td>39%</td>\n<td>3,555</td>\n<td>43%</td>\n</tr>\n<tr>\n<td>Community/support/documentation/help</td>\n<td>3,806</td>\n<td>17%</td>\n<td>1,211</td>\n<td>15%</td>\n<td>1,340</td>\n<td>16%</td>\n</tr>\n<tr>\n<td>Free/open/open source</td>\n<td>2,291</td>\n<td>10%</td>\n<td>802</td>\n<td>10%</td>\n<td>908</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Popular/ubiquitous</td>\n<td>249</td>\n<td>1%</td>\n<td>86</td>\n<td>1%</td>\n<td>187</td>\n<td>2%</td>\n</tr>\n</tbody>\n</table>\n<h3> What&#8217;s the most frustrating thing about WordPress?<a href="#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>21,144</td>\n<td></td>\n<td>7,294</td>\n<td></td>\n<td>7,691</td>\n<td></td>\n</tr>\n<tr>\n<td>Plugins &amp; themes (abandoned/conflicts/coding standards)</td>\n<td>6,122</td>\n<td>29%</td>\n<td>2,194</td>\n<td>30%</td>\n<td>2,187</td>\n<td>28%</td>\n</tr>\n<tr>\n<td>Security/vulnerabilities/hacks</td>\n<td>2,321</td>\n<td>11%</td>\n<td>712</td>\n<td>10%</td>\n<td>829</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Updates</td>\n<td>1,544</td>\n<td>7%</td>\n<td>422</td>\n<td>6%</td>\n<td>508</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>Nothing/I don&#8217;t know/can&#8217;t think of anything</td>\n<td>1,276</td>\n<td>6%</td>\n<td>344</td>\n<td>5%</td>\n<td>476</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Speed/performance/slow/heavy</td>\n<td>1,196</td>\n<td>6%</td>\n<td>644</td>\n<td>9%</td>\n<td>516</td>\n<td>7%</td>\n</tr>\n</tbody>\n</table>\n<h3>WordPress is as good as, or better than, its main competitors.</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (this question was not asked in the 2015 survey)</td>\n<td></td>\n<td></td>\n<td>8,672</td>\n<td></td>\n<td>9,059</td>\n<td></td>\n</tr>\n<tr>\n<td>Agree</td>\n<td></td>\n<td></td>\n<td>7551</td>\n<td>87%</td>\n<td>7836</td>\n<td>87%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>754</td>\n<td>9%</td>\n<td>795</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Disagree</td>\n<td></td>\n<td></td>\n<td>370</td>\n<td>4%</td>\n<td>428</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h2 id="user">WordPress Users</h2>\n<h3>Which of the following describes how you use WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>15,169</td>\n<td></td>\n<td>5,043</td>\n<td></td>\n<td>5,521</td>\n<td></td>\n</tr>\n<tr>\n<td>My personal blog (or blogs) uses WordPress.</td>\n<td>9,395</td>\n<td>36%</td>\n<td>3,117</td>\n<td>36%</td>\n<td>3,424</td>\n<td>36%</td>\n</tr>\n<tr>\n<td>My company or organization&#8217;s website is built with WordPress software.</td>\n<td>7,480</td>\n<td>29%</td>\n<td>2,519</td>\n<td>29%</td>\n<td>2,841</td>\n<td>30%</td>\n</tr>\n<tr>\n<td>I have a hobby or side project that has a website built with WordPress.</td>\n<td>6,112</td>\n<td>23%</td>\n<td>1,973</td>\n<td>23%</td>\n<td>2,200</td>\n<td>23%</td>\n</tr>\n<tr>\n<td>I write (or otherwise work) for an online publication that uses WordPress.</td>\n<td>2,329</td>\n<td>9%</td>\n<td>806</td>\n<td>9%</td>\n<td>821</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>872</td>\n<td>3%</td>\n<td>234</td>\n<td>3%</td>\n<td>288</td>\n<td>3%</td>\n</tr>\n</tbody>\n</table>\n<h3>Who installed your WordPress website?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>15,055</td>\n<td></td>\n<td>5,020</td>\n<td></td>\n<td>5,523</td>\n<td></td>\n</tr>\n<tr>\n<td>I did.</td>\n<td>11,216</td>\n<td>66%</td>\n<td>3,659</td>\n<td>73%</td>\n<td>4,129</td>\n<td>75%</td>\n</tr>\n<tr>\n<td>My hosting provider</td>\n<td>2,236</td>\n<td>13%</td>\n<td>667</td>\n<td>13%</td>\n<td>767</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>An external company</td>\n<td>909</td>\n<td>5%</td>\n<td>182</td>\n<td>4%</td>\n<td>178</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>An internal web person/team or a colleague</td>\n<td>874</td>\n<td>5%</td>\n<td>178</td>\n<td>4%</td>\n<td>191</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>A friend or family member</td>\n<td>787</td>\n<td>5%</td>\n<td>192</td>\n<td>4%</td>\n<td>172</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>I don&#8217;t know</td>\n<td>502</td>\n<td>3%</td>\n<td>145</td>\n<td>3%</td>\n<td>87</td>\n<td>2%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>345</td>\n<td>2%</td>\n<td>n/a</td>\n<td>n/a</td>\n<td>n/a</td>\n<td>n/a</td>\n</tr>\n</tbody>\n</table>\n<h3>How much has the site been customized from the original WordPress installation?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>14,789</td>\n<td></td>\n<td>4,997</td>\n<td></td>\n<td>5,494</td>\n<td></td>\n</tr>\n<tr>\n<td>There&#8217;s a different theme and some plugins have been added.</td>\n<td>7,465</td>\n<td>50%</td>\n<td>2,337</td>\n<td>47%</td>\n<td>2,660</td>\n<td>48%</td>\n</tr>\n<tr>\n<td>A lot of work has been done, the site itself is unrecognizable from the original theme, but the Dashboard still looks like the usual WordPress interface.</td>\n<td>4,715</td>\n<td>32%</td>\n<td>1,707</td>\n<td>34%</td>\n<td>1,872</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Not at all, it&#8217;s still pretty much the same as it was when I started out.</td>\n<td>1,841</td>\n<td>12%</td>\n<td>635</td>\n<td>13%</td>\n<td>673</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>You&#8217;d never know this was a WordPress installation, everything has been customized.</td>\n<td>768</td>\n<td>5%</td>\n<td>321</td>\n<td>6%</td>\n<td>290</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>What&#8217;s the best thing about WordPress?<a href="#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>14,328</td>\n<td></td>\n<td>4,613</td>\n<td></td>\n<td>5,076</td>\n<td></td>\n</tr>\n<tr>\n<td>Easy/simple/user-friendly</td>\n<td>7,391</td>\n<td>52%</td>\n<td>2,276</td>\n<td>49%</td>\n<td>2,511</td>\n<td>49%</td>\n</tr>\n<tr>\n<td>Customizable/extensible/modular/plugins/themes</td>\n<td>4,219</td>\n<td>29%</td>\n<td>1,569</td>\n<td>34%</td>\n<td>1,632</td>\n<td>32%</td>\n</tr>\n<tr>\n<td>Free/open/open source</td>\n<td>1,586</td>\n<td>11%</td>\n<td>493</td>\n<td>11%</td>\n<td>538</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Community/support/documentation/help</td>\n<td>1,085</td>\n<td>8%</td>\n<td>388</td>\n<td>8%</td>\n<td>458</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Popular/ubiquitous</td>\n<td>223</td>\n<td>2%</td>\n<td>74</td>\n<td>2%</td>\n<td>48</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>What&#8217;s the most frustrating thing about WordPress?<a href="#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>13,681</td>\n<td></td>\n<td>4,287</td>\n<td></td>\n<td>4,758</td>\n<td></td>\n</tr>\n<tr>\n<td>Plugins &amp; themes (abandoned/conflicts/coding standards)</td>\n<td>2,531</td>\n<td>19%</td>\n<td>1,183</td>\n<td>28%</td>\n<td>1,300</td>\n<td>27%</td>\n</tr>\n<tr>\n<td>Customization/design/look/template</td>\n<td>1,273</td>\n<td>9%</td>\n<td>381</td>\n<td>9%</td>\n<td>408</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Code/coding/PHP</td>\n<td>931</td>\n<td>7%</td>\n<td>306</td>\n<td>7%</td>\n<td>277</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Updates</td>\n<td>926</td>\n<td>7%</td>\n<td>209</td>\n<td>5%</td>\n<td>296</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Security/vulnerabilites/hacks</td>\n<td>785</td>\n<td>6%</td>\n<td>255</td>\n<td>6%</td>\n<td>292</td>\n<td>6%</td>\n</tr>\n</tbody>\n</table>\n<h3>WordPress is as good as, or better than, its main competitors.</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>5,026</td>\n<td></td>\n<td>5,498</td>\n<td></td>\n</tr>\n<tr>\n<td>Agree</td>\n<td></td>\n<td></td>\n<td>4,038</td>\n<td>80%</td>\n<td>4,462</td>\n<td>81%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>737</td>\n<td>15%</td>\n<td>782</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>Disagree</td>\n<td></td>\n<td></td>\n<td>254</td>\n<td>5%</td>\n<td>255</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h2 id="all">All Respondents</h2>\n<h3>Can you (truthfully!) say &#8220;I make my living from WordPress&#8221;?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (combination of all three groups from 2015; this question was not broken out by group in 2016-2017)</td>\n<td>42,236</td>\n<td></td>\n<td>14,906</td>\n<td></td>\n<td>15,616</td>\n<td></td>\n</tr>\n<tr>\n<td>Not really, but I do get some or all of my income as a result of working with WordPress.</td>\n<td>16,607</td>\n<td>39%</td>\n<td>5,408</td>\n<td>36%</td>\n<td>5,702</td>\n<td>37%</td>\n</tr>\n<tr>\n<td>Yes.</td>\n<td>9,635</td>\n<td>23%</td>\n<td>4,791</td>\n<td>32%</td>\n<td>5,033</td>\n<td>32%</td>\n</tr>\n<tr>\n<td>No.</td>\n<td>15,995</td>\n<td>38%</td>\n<td>4,713</td>\n<td>32%</td>\n<td>4,882</td>\n<td>31%</td>\n</tr>\n</tbody>\n</table>\n<h3>Which devices do you access WordPress on?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (combination of all three groups from 2015; this question was not broken out by group in 2016-2017)</td>\n<td>42,433</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Web</td>\n<td>40,503</td>\n<td>95%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Android phone</td>\n<td>15,396</td>\n<td>36%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>iPhone</td>\n<td>12,353</td>\n<td>29%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>iPad</td>\n<td>11,748</td>\n<td>28%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Android tablet</td>\n<td>9,223</td>\n<td>22%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Desktop app, like MarsEdit</td>\n<td>6,018</td>\n<td>14%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>1837</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (this question was not broken out by group in 2016-2017)</td>\n<td></td>\n<td></td>\n<td>14,840</td>\n<td></td>\n<td>15,597</td>\n<td></td>\n</tr>\n<tr>\n<td>Web browser on a desktop or laptop</td>\n<td></td>\n<td></td>\n<td>14,160</td>\n<td>54%</td>\n<td>15,052</td>\n<td>55%</td>\n</tr>\n<tr>\n<td>Web browser on a mobile device (tablet or phone)</td>\n<td></td>\n<td></td>\n<td>7,952</td>\n<td>30%</td>\n<td>8,248</td>\n<td>30%</td>\n</tr>\n<tr>\n<td>An app on a mobile device (table or phone)</td>\n<td></td>\n<td></td>\n<td>3,309</td>\n<td>13%</td>\n<td>3,311</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>A desktop app like MarsEdit</td>\n<td></td>\n<td></td>\n<td>517</td>\n<td>2%</td>\n<td>498</td>\n<td>2%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td></td>\n<td></td>\n<td>282</td>\n<td>1%</td>\n<td>240</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>WordPress now updates minor &amp; security releases automatically for you. Check all that apply: (question not asked in 2016, 2017)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (combination of all three groups)</td>\n<td>39,726</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I love auto-updates.</td>\n<td>17,367</td>\n<td>44%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;d like to see auto-updates for plugins.</td>\n<td>12,796</td>\n<td>32%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Initially, I was nervous about auto updates.</td>\n<td>11,868</td>\n<td>30%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Auto updates still make me nervous.</td>\n<td>10,809</td>\n<td>27%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Auto updates don&#8217;t make me nervous now.</td>\n<td>10,708</td>\n<td>27%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;d like to see auto-updates for themes.</td>\n<td>10,449</td>\n<td>26%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;d like to see auto updates for major versions of WordPress.</td>\n<td>10,225</td>\n<td>26%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>This is the first I&#8217;ve heard of auto-updates.</td>\n<td>8,660</td>\n<td>22%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I hate auto-updates.</td>\n<td>3,293</td>\n<td>8%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n<h3>What is your gender?<a href="#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All respondents (This question was not asked in the 2015 survey.)</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>13,953</td>\n<td></td>\n<td>14,680</td>\n<td></td>\n</tr>\n<tr>\n<td>Male</td>\n<td></td>\n<td></td>\n<td>10,978</td>\n<td>78.68%</td>\n<td>11,570</td>\n<td>78.81%</td>\n</tr>\n<tr>\n<td>Female</td>\n<td></td>\n<td></td>\n<td>2,340</td>\n<td>16.77%</td>\n<td>2,511</td>\n<td>21.70%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>601</td>\n<td>4.31%</td>\n<td>562</td>\n<td>3.83%</td>\n</tr>\n<tr>\n<td>Transgender</td>\n<td></td>\n<td></td>\n<td>11</td>\n<td>0.08%</td>\n<td>8</td>\n<td>0.05%</td>\n</tr>\n<tr>\n<td>Nonbinary</td>\n<td></td>\n<td></td>\n<td>8</td>\n<td>0.06%</td>\n<td>17</td>\n<td>0.12%</td>\n</tr>\n<tr>\n<td>Genderqueer</td>\n<td></td>\n<td></td>\n<td>4</td>\n<td>0.03%</td>\n<td>3</td>\n<td>0.02%</td>\n</tr>\n<tr>\n<td>Androgynous</td>\n<td></td>\n<td></td>\n<td>6</td>\n<td>0.04%</td>\n<td>5</td>\n<td>0.03%</td>\n</tr>\n<tr>\n<td>Fluid</td>\n<td></td>\n<td></td>\n<td>3</td>\n<td>0.02%</td>\n<td>4</td>\n<td>0.03%</td>\n</tr>\n<tr>\n<td>Demimale</td>\n<td></td>\n<td></td>\n<td>2</td>\n<td>0.01%</td>\n<td>0</td>\n<td>0</td>\n</tr>\n</tbody>\n</table>\n<h3>Where are you located?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All respondents (This question was not asked in the 2015 survey.)</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>14,562</td>\n<td></td>\n<td>15,343</td>\n<td></td>\n</tr>\n<tr>\n<td>United States</td>\n<td></td>\n<td></td>\n<td>3,770</td>\n<td>25.89%</td>\n<td>4,067</td>\n<td>26.51%</td>\n</tr>\n<tr>\n<td>India</td>\n<td></td>\n<td></td>\n<td>1,456</td>\n<td>10.00%</td>\n<td>1,424</td>\n<td>9.28%</td>\n</tr>\n<tr>\n<td>United Kingdom</td>\n<td></td>\n<td></td>\n<td>810</td>\n<td>5.56%</td>\n<td>900</td>\n<td>5.87%</td>\n</tr>\n<tr>\n<td>Germany</td>\n<td></td>\n<td></td>\n<td>555</td>\n<td>3.81%</td>\n<td>729</td>\n<td>4.75%</td>\n</tr>\n<tr>\n<td>Canada</td>\n<td></td>\n<td></td>\n<td>511</td>\n<td>3.51%</td>\n<td>599</td>\n<td>3.90%</td>\n</tr>\n<tr>\n<td>Australia</td>\n<td></td>\n<td></td>\n<td>389</td>\n<td>2.67%</td>\n<td>460</td>\n<td>3.00%</td>\n</tr>\n<tr>\n<td>Italy</td>\n<td></td>\n<td></td>\n<td>298</td>\n<td>2.05%</td>\n<td>356</td>\n<td>2.32%</td>\n</tr>\n<tr>\n<td>Netherlands</td>\n<td></td>\n<td></td>\n<td>343</td>\n<td>2.36%</td>\n<td>350</td>\n<td>2.28%</td>\n</tr>\n<tr>\n<td>France</td>\n<td></td>\n<td></td>\n<td>232</td>\n<td>1.59%</td>\n<td>283</td>\n<td>1.84%</td>\n</tr>\n<tr>\n<td>Bangladesh</td>\n<td></td>\n<td></td>\n<td>257</td>\n<td>1.76%</td>\n<td>263</td>\n<td>1.71%</td>\n</tr>\n<tr>\n<td>Spain</td>\n<td></td>\n<td></td>\n<td>271</td>\n<td>1.86%</td>\n<td>252</td>\n<td>1.64%</td>\n</tr>\n<tr>\n<td>Brazil</td>\n<td></td>\n<td></td>\n<td>239</td>\n<td>1.64%</td>\n<td>251</td>\n<td>1.64%</td>\n</tr>\n<tr>\n<td>Pakistan</td>\n<td></td>\n<td></td>\n<td>254</td>\n<td>1.74%</td>\n<td>240</td>\n<td>1.56%</td>\n</tr>\n<tr>\n<td>Indonesia</td>\n<td></td>\n<td></td>\n<td>230</td>\n<td>1.58%</td>\n<td>226</td>\n<td>1.47%</td>\n</tr>\n<tr>\n<td>Iran, Islamic Republic of</td>\n<td></td>\n<td></td>\n<td>190</td>\n<td>1.30%</td>\n<td>173</td>\n<td>1.13%</td>\n</tr>\n<tr>\n<td>Sweden</td>\n<td></td>\n<td></td>\n<td>144</td>\n<td>0.99%</td>\n<td>173</td>\n<td>1.13%</td>\n</tr>\n<tr>\n<td>Nigeria</td>\n<td></td>\n<td></td>\n<td>196</td>\n<td>1.35%</td>\n<td>172</td>\n<td>1.12%</td>\n</tr>\n<tr>\n<td>South Africa</td>\n<td></td>\n<td></td>\n<td>193</td>\n<td>1.33%</td>\n<td>172</td>\n<td>1.12%</td>\n</tr>\n<tr>\n<td>Russian Federation</td>\n<td></td>\n<td></td>\n<td>181</td>\n<td>1.24%</td>\n<td>151</td>\n<td>0.98%</td>\n</tr>\n<tr>\n<td>Poland</td>\n<td></td>\n<td></td>\n<td>129</td>\n<td>0.89%</td>\n<td>137</td>\n<td>0.89%</td>\n</tr>\n<tr>\n<td>Romania</td>\n<td></td>\n<td></td>\n<td>144</td>\n<td>0.99%</td>\n<td>132</td>\n<td>0.86%</td>\n</tr>\n<tr>\n<td>Switzerland</td>\n<td></td>\n<td></td>\n<td>122</td>\n<td>0.84%</td>\n<td>130</td>\n<td>0.85%</td>\n</tr>\n<tr>\n<td>Philippines</td>\n<td></td>\n<td></td>\n<td>92</td>\n<td>0.63%</td>\n<td>125</td>\n<td>0.81%</td>\n</tr>\n<tr>\n<td>China</td>\n<td></td>\n<td></td>\n<td>136</td>\n<td>0.93%</td>\n<td>123</td>\n<td>0.80%</td>\n</tr>\n<tr>\n<td>Austria</td>\n<td></td>\n<td></td>\n<td>89</td>\n<td>0.61%</td>\n<td>122</td>\n<td>0.80%</td>\n</tr>\n<tr>\n<td>Ukraine</td>\n<td></td>\n<td></td>\n<td>105</td>\n<td>0.72%</td>\n<td>118</td>\n<td>0.77%</td>\n</tr>\n<tr>\n<td>Denmark</td>\n<td></td>\n<td></td>\n<td>107</td>\n<td>0.73%</td>\n<td>114</td>\n<td>0.74%</td>\n</tr>\n<tr>\n<td>Greece</td>\n<td></td>\n<td></td>\n<td>120</td>\n<td>0.82%</td>\n<td>114</td>\n<td>0.74%</td>\n</tr>\n<tr>\n<td>Portugal</td>\n<td></td>\n<td></td>\n<td>94</td>\n<td>0.65%</td>\n<td>109</td>\n<td>0.71%</td>\n</tr>\n<tr>\n<td>Vietnam</td>\n<td></td>\n<td></td>\n<td>101</td>\n<td>0.69%</td>\n<td>108</td>\n<td>0.70%</td>\n</tr>\n<tr>\n<td>Mexico</td>\n<td></td>\n<td></td>\n<td>94</td>\n<td>0.65%</td>\n<td>105</td>\n<td>0.68%</td>\n</tr>\n<tr>\n<td>Nepal</td>\n<td></td>\n<td></td>\n<td>76</td>\n<td>0.52%</td>\n<td>97</td>\n<td>0.63%</td>\n</tr>\n<tr>\n<td>Ireland</td>\n<td></td>\n<td></td>\n<td>72</td>\n<td>0.49%</td>\n<td>94</td>\n<td>0.61%</td>\n</tr>\n<tr>\n<td>Israel</td>\n<td></td>\n<td></td>\n<td>78</td>\n<td>0.54%</td>\n<td>94</td>\n<td>0.61%</td>\n</tr>\n<tr>\n<td>New Zealand</td>\n<td></td>\n<td></td>\n<td>77</td>\n<td>0.53%</td>\n<td>91</td>\n<td>0.59%</td>\n</tr>\n<tr>\n<td>Finland</td>\n<td></td>\n<td></td>\n<td>63</td>\n<td>0.43%</td>\n<td>90</td>\n<td>0.59%</td>\n</tr>\n<tr>\n<td>Turkey</td>\n<td></td>\n<td></td>\n<td>91</td>\n<td>0.62%</td>\n<td>86</td>\n<td>0.56%</td>\n</tr>\n<tr>\n<td>Malaysia</td>\n<td></td>\n<td></td>\n<td>91</td>\n<td>0.62%</td>\n<td>81</td>\n<td>0.53%</td>\n</tr>\n<tr>\n<td>Belgium</td>\n<td></td>\n<td></td>\n<td>84</td>\n<td>0.58%</td>\n<td>79</td>\n<td>0.51%</td>\n</tr>\n<tr>\n<td>Norway</td>\n<td></td>\n<td></td>\n<td>66</td>\n<td>0.45%</td>\n<td>79</td>\n<td>0.51%</td>\n</tr>\n<tr>\n<td>Argentina</td>\n<td></td>\n<td></td>\n<td>65</td>\n<td>0.45%</td>\n<td>76</td>\n<td>0.50%</td>\n</tr>\n<tr>\n<td>Bulgaria</td>\n<td></td>\n<td></td>\n<td>74</td>\n<td>0.51%</td>\n<td>72</td>\n<td>0.47%</td>\n</tr>\n<tr>\n<td>Japan</td>\n<td></td>\n<td></td>\n<td>61</td>\n<td>0.42%</td>\n<td>68</td>\n<td>0.44%</td>\n</tr>\n<tr>\n<td>Thailand</td>\n<td></td>\n<td></td>\n<td>69</td>\n<td>0.47%</td>\n<td>67</td>\n<td>0.44%</td>\n</tr>\n<tr>\n<td>Czech Republic</td>\n<td></td>\n<td></td>\n<td>76</td>\n<td>0.52%</td>\n<td>66</td>\n<td>0.43%</td>\n</tr>\n<tr>\n<td>Serbia</td>\n<td></td>\n<td></td>\n<td>89</td>\n<td>0.61%</td>\n<td>63</td>\n<td>0.41%</td>\n</tr>\n<tr>\n<td>Kenya</td>\n<td></td>\n<td></td>\n<td>58</td>\n<td>0.40%</td>\n<td>62</td>\n<td>0.40%</td>\n</tr>\n<tr>\n<td>Colombia</td>\n<td></td>\n<td></td>\n<td>39</td>\n<td>0.27%</td>\n<td>59</td>\n<td>0.38%</td>\n</tr>\n<tr>\n<td>Egypt</td>\n<td></td>\n<td></td>\n<td>40</td>\n<td>0.27%</td>\n<td>52</td>\n<td>0.34%</td>\n</tr>\n</tbody>\n</table>\n<h3>What is your age?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2015</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2016</strong></td>\n<td style="text-align: center" colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (This question was not asked in 2015.)</td>\n<td></td>\n<td></td>\n<td>14,944</td>\n<td></td>\n<td>15,636</td>\n<td></td>\n</tr>\n<tr>\n<td>60 and over</td>\n<td></td>\n<td></td>\n<td>1,139</td>\n<td>8%</td>\n<td>1,641</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>50-59</td>\n<td></td>\n<td></td>\n<td>1,537</td>\n<td>10%</td>\n<td>1,996</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>40-49</td>\n<td></td>\n<td></td>\n<td>2,205</td>\n<td>15%</td>\n<td>2,643</td>\n<td>17%</td>\n</tr>\n<tr>\n<td>30-39</td>\n<td></td>\n<td></td>\n<td>3,914</td>\n<td>26%</td>\n<td>3,972</td>\n<td>25%</td>\n</tr>\n<tr>\n<td>20-29</td>\n<td></td>\n<td></td>\n<td>5,013</td>\n<td>34%</td>\n<td>4,444</td>\n<td>28%</td>\n</tr>\n<tr>\n<td>Under 20</td>\n<td></td>\n<td></td>\n<td>1142</td>\n<td>8%</td>\n<td>941</td>\n<td>6%</td>\n</tr>\n</tbody>\n</table>\n<p>Thank you to everyone who made time to fill out the survey &#8212; we&#8217;re so happy you use WordPress, and we&#8217;re very grateful that you&#8217;re willing to share your experiences with us! Thanks also to everyone who spread the word about this survey, and to those of you who read all the way to the bottom of this post. <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n<p><small><a id="text"></a>*Text Field Questions: Each survey included some questions that could be answered only by filling out a text field. In the case of the questions &#8220;What is the best thing about WordPress?&#8221; and &#8220;What is the most frustrating thing about WordPress?&#8221; we listed the five most common responses, aggregated when applicable. In the case of the question “What is your gender?” in the 2016 and 2017 surveys, we aggregated responses as best we could. Responses meant to obscure respondents’ gender entirely are aggregated in “prefer not to answer.”</small></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5310";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:33:"\n		\n		\n		\n		\n				\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:37:"The Month in WordPress: November 2017";s:7:"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/2017/12/the-month-in-wordpress-november-2017/";s: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, 01 Dec 2017 11:00:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:18:"Month in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5290";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:354:"The WordPress project recently released WordPress 4.9, “Tipton” — a new major release named in honor of musician and band leader Billy Tipton. Read on to find out more about this and other interesting news from around the WordPress world in November. WordPress 4.9 “Tipton” On November 16, WordPress 4.9 was released with new features [&#8230;]";s: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:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4197:"<p>The WordPress project recently released WordPress 4.9, “Tipton” — a new major release named in honor of musician and band leader Billy Tipton. Read on to find out more about this and other interesting news from around the WordPress world in November.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>WordPress 4.9 “Tipton”</h2>\n\n<p>On November 16, <a href="https://wordpress.org/news/2017/11/tipton/">WordPress 4.9 was released</a> with new features for publishers and developers alike. Release highlights include design locking, scheduling, and previews in the Customizer, an even more secure and usable code editing experience, a new gallery widget, and text widget improvements.</p>\n\n<p>The follow up security and maintenance, v4.9.1, <a href="https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/">has now been released</a> to tighten up the security of WordPress as a whole.</p>\n\n<p>To get involved in building WordPress Core, jump into the #core channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>, and follow<a href="https://make.wordpress.org/core/"> the Core team blog</a>.</p>\n\n<h2>Apply to Speak At WordCamp Europe 2018</h2>\n\n<p>The next edition of WordCamp Europe takes place in June, 2018. While the organizing team is still in the early stages of planning, <a href="https://2018.europe.wordcamp.org/2017/11/15/are-you-ready-to-speak-at-the-largest-wordpress-event-in-europe/">they are accepting speaker applications</a>.</p>\n\n<p>WordCamp Europe is the largest WordCamp in the world and, along with WordCamp US, one of the flagship events of the WordCamp program — speaking at this event is a great way to give back to the global WordPress community by sharing your knowledge and expertise with thousands of WordPress enthusiasts.</p>\n\n<h2>Diversity Outreach Speaker Training Initiative</h2>\n\n<p>To help WordPress community organizers offer diverse speaker lineups, <a href="https://make.wordpress.org/community/2017/11/13/call-for-volunteers-diversity-outreach-speaker-training/">a new community initiative has kicked off</a> to use existing <a href="https://make.wordpress.org/training/handbook/speaker-training/">speaker training workshops</a> to demystify speaking requirements and help participants gain confidence in their ability to share their WordPress knowledge in a WordCamp session.</p>\n\n<p>The working group behind this initiative will be meeting regularly to discuss and plan how they can help local communities to train speakers for WordCamps and other events.</p>\n\n<p>To get involved in this initiative, you can join the meetings at 5pm UTC every other Wednesday in the #community-team channel of the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>Further Reading:</h2>\n\n<ul>\n    <li><a href="https://2017.us.wordcamp.org/">WordCamp US 2017</a> is happening on December 1-3 in Nashville, with the annual State of the Word talk happening on Saturday afternoon — <a href="https://2017.us.wordcamp.org/live-stream/">the live stream of the entire event is available to view for free</a>.</li>\n    <li><a href="https://xwp.co/tide-a-path-to-better-code-across-the-wordpress-ecosystem/">Tide</a>, a new service from XWP designed to help users make informed plugin choices, is due to launch at WordCamp US.</li>\n    <li>Gutenberg development is continuing rapidly, with <a href="https://make.wordpress.org/core/2017/11/28/whats-new-in-gutenberg-28th-november/">a packed new release</a> and a focus on <a href="https://make.wordpress.org/test/2017/11/22/testing-flow-in-gutenberg/">usability testing</a>.</li>\n    <li>After some discussion among the community, <a href="https://make.wordpress.org/community/2017/11/10/discussion-micro-regional-wordcamps/">a new type of micro-regional WordCamp</a> is going to be introduced into the global WordCamp program.</li>\n</ul>\n\n<p><em></em></p>\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>\n\n<p><em></em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5290";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:36:"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"WordPress 4.9.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:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://wordpress.org/news/2017/11/wordpress-4-9-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 29 Nov 2017 20:33:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5215";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:359:"WordPress 4.9.1 is now available. This is a security and maintenance release for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately. WordPress versions 4.9 and earlier are affected by four security issues which could potentially be exploited as part of a multi-vector attack. As part of the core team&#x27;s [&#8230;]";s: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:"John Blackbourn";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4268:"<p>WordPress 4.9.1 is now available. This is a <strong>security and maintenance release</strong> for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately.</p>\n\n<p>WordPress versions 4.9 and earlier are affected by four security issues which could potentially be exploited as part of a multi-vector attack. As part of the core team&#x27;s ongoing commitment to security hardening, the following fixes have been implemented in 4.9.1:</p>\n\n<ol>\n    <li>Use a properly generated hash for the <code>newbloguser</code> key instead of a determinate substring.</li>\n    <li>Add escaping to the language attributes used on <code>html</code> elements.</li>\n    <li>Ensure the attributes of enclosures are correctly escaped in RSS and Atom feeds.</li>\n    <li>Remove the ability to upload JavaScript files for users who do not have the <code>unfiltered_html</code> capability.</li>\n</ol>\n\n<p>Thank you to the reporters of these issues for practicing <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">responsible security disclosure</a>: <a href="https://twitter.com/0x62626262">Rahul Pratap Singh</a> and John Blackbourn.</p>\n\n<p>Eleven other bugs were fixed in WordPress 4.9.1. Particularly of note were:</p>\n\n<ul>\n    <li>Issues relating to the caching of theme template files.</li>\n    <li>A MediaElement JavaScript error preventing users of certain languages from being able to upload media files.</li>\n    <li>The inability to edit theme and plugin files on Windows based servers.</li>\n</ul>\n\n<p><a href="https://make.wordpress.org/core/2017/11/28/wordpress-4-9-1-scheduled-for-november-29th/">This post has more information about all of the issues fixed in 4.9.1 if you&#x27;d like to learn more</a>.</p>\n\n<p><a href="https://wordpress.org/download/">Download WordPress 4.9.1</a> or venture over to Dashboard → Updates and click &quot;Update Now.&quot; Sites that support automatic background updates are already beginning to update automatically.</p>\n\n<p>Thank you to everyone who contributed to WordPress 4.9.1:</p>\n\n<p><a href="https://profiles.wordpress.org/schlessera/">Alain Schlesser</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/la-geek/">Angelika Reisiger</a>, <a href="https://profiles.wordpress.org/blobfolio/">Blobfolio</a>, <a href="https://profiles.wordpress.org/bobbingwide/">bobbingwide</a>, <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a>, <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a>, <a href="https://profiles.wordpress.org/ocean90/">Dominik Schilling (ocean90)</a>, <a href="https://profiles.wordpress.org/edo888/">edo888</a>, <a href="https://profiles.wordpress.org/erich_k4wp/">Erich Munz</a>, <a href="https://profiles.wordpress.org/flixos90/">Felix Arntz</a>, <a href="https://profiles.wordpress.org/mista-flo/">Florian TIAR</a>, <a href="https://profiles.wordpress.org/pento/">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/ibenic/">Igor Benic</a>, <a href="https://profiles.wordpress.org/jfarthing84/">Jeff Farthing</a>, <a href="https://profiles.wordpress.org/jbpaul17/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/jeremyescott/">jeremyescott</a>, <a href="https://profiles.wordpress.org/joemcgill/">Joe McGill</a>, <a href="https://profiles.wordpress.org/johnbillion/">John Blackbourn</a>, <a href="https://profiles.wordpress.org/johnpgreen/">johnpgreen</a>, <a href="https://profiles.wordpress.org/ryelle/">Kelly Dwan</a>, <a href="https://profiles.wordpress.org/lenasterg/">lenasterg</a>, <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/melchoyce/">Mel Choyce</a>, <a href="https://profiles.wordpress.org/mariovalney/">Mário Valney</a>, <a href="https://profiles.wordpress.org/natacado/">natacado</a>, <a href="https://profiles.wordpress.org/odysseygate/">odyssey</a>, <a href="https://profiles.wordpress.org/precies/">precies</a>, <a href="https://profiles.wordpress.org/stodorovic/">Saša</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, and <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"5215";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:32:"https://wordpress.org/news/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:9:"\n	hourly	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:4:"\n	1	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:4:"site";a:1:{i:0;a:5:{s:4:"data";s:8:"14607090";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Thu, 08 Mar 2018 16:39:59 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:25:"strict-transport-security";s:11:"max-age=360";s:6:"x-olaf";s:3:"⛄";s:13:"last-modified";s:29:"Thu, 01 Mar 2018 08:41:16 GMT";s:4:"link";s:63:"<https://wordpress.org/news/wp-json/>; rel="https://api.w.org/"";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 2";}}s:5:"build";s:14:"20130911010210";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(230, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1520570401', 'no'),
(231, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1520527201', 'no'),
(232, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1520570402', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(233, '_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:60:"WPTavern: WPWeekly Episode 307 – Thirty Percent of the Web";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=78242&preview=true&preview_id=78242";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://wptavern.com/wpweekly-episode-307-thirty-percent-of-the-web";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2423:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I start with a continued discussion of AMP from last week. We cover the big releases of the week including Jetpack, Genesis, Yoast SEO, and Gutenberg. We discuss a new project that aims to determine Gutenberg compatible plugins, debate the terminology used to describe WordPress&#8217; market share, and a new plugin that makes WordPress updates more secure.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://make.wordpress.org/core/2018/03/02/whats-new-in-gutenberg-2nd-march/">Gutenberg 2.3, Now With Nested Blocks</a><br />\n<a href="https://studiopress.blog/genesis-2-6/">Genesis 2.6</a><br />\n<a href="https://yoast.com/yoast-seo-7-0/">Yoast SEO 7.0</a><br />\n<a href="https://jetpack.com/category/releases/">Jetpack 5.9</a><br />\n<a href="https://wptavern.com/4500-plugins-need-your-help-in-determining-gutenberg-compatibility">4,500 Plugins Need Your Help in Determining Gutenberg Compatibility</a><br />\n<a href="https://wptavern.com/new-plugin-makes-wordpress-core-updates-more-secure-by-requiring-cryptographic-signature-verification">New Plugin Makes WordPress Core Updates More Secure by Requiring Cryptographic Signature Verification</a><br />\n<a href="https://wptavern.com/wordpress-now-used-on-30-of-the-top-10-million-sites">WordPress Now Used on 30% of the Top 10 Million Sites</a></p>\n<h2>Picks of the Week:</h2>\n<p>Mel Choyce&#8217;s presentation on <a href="https://wptavern.com/conceptual-ideas-on-how-the-customizer-could-integrate-with-gutenberg">Customizing the Future</a> at LoopConf.</p>\n<p>Felix Arntz&#8217;s presentation on a Global Admin, a <a href="https://www.youtube.com/watch?v=V085zCBdRfc">deep dive into multi-network organization</a> at LoopConf.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, February 14th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #307:</strong><br />\n</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, 08 Mar 2018 03:39:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:22:"Matt: Back to Blogging";s:7:"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=47991";s:7:"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:39:"https://ma.tt/2018/03/back-to-blogging/";s: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:134:"<p>I really enjoyed <a href="http://tomcritchlow.com/2018/02/23/small-b-blogging/">Tom Critchlow&#x27;s post Small b blogging</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, 07 Mar 2018 22:59: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: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: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:79:"WPTavern: Conceptual Ideas on How the Customizer Could Integrate With Gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=78232";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:90:"https://wptavern.com/conceptual-ideas-on-how-the-customizer-could-integrate-with-gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1598:"<p>While the initial focus of Gutenberg is the editor, the second focus is the Customization experience in WordPress. <a href="https://choycedesign.com/">Mel Choyce</a>, Product Designer at Automattic, recently spoke at <a href="https://loopconf.com/">LoopConf</a>, on the <a href="https://loopconf.com/talk/customizing-the-future/">past, present, and future</a> of the customizer.</p>\n<p>Choyce begins the presentation by describing when and how the customizer was added to WordPress. Fun fact, the customizer or what was known as the Theme Customizer at the time, was added to <a href="https://wordpress.org/news/2012/06/green/">WordPress 3.4 &#8220;Green&#8221;</a> in June 2012.</p>\n<p>The session continues with Choyce showcasing new features and enhancements that have been made to the customizer since 2012. Near the 23 minute mark, Choyce shows conceptual images of what the customization experience could be like when implemented with Gutenberg.</p>\n<p>In the experimental images, you can see options to choose page templates or layouts, live previewing changes to blocks, global site styles, and a standard set of user interface patterns. The ideas presented are concepts and likely to change.</p>\n<p>Because the session was recorded with a picture-in-picture, I&#8217;m not able to provide high quality screen captures of the conceptual images. To see those items in detail, I recommend viewing the video in full-screen 1080p. You can full all of the LoopConf sessions for free via <a href="https://www.youtube.com/channel/UCAwOVsWiMdlz6snWRF2HdSQ">their YouTube channel</a>.</p>\n<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 07 Mar 2018 10:17:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:30:"HeroPress: Building A New Life";s:7:"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=2480";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:112:"https://heropress.com/essays/building-a-new-life/#utm_source=rss&utm_medium=rss&utm_campaign=building-a-new-life";s: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:12980:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/03/030718-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: Plan your business around what matters to you/" /><p>This is the story of how I co-founded Barn2 Media with my husband Andy, and scaled it from a startup to one of the UK’s best known WordPress agencies &#8211; all while working part-time.</p>\n<p>I&#8217;ll tell you about the challenges I faced in building a WordPress business that is compatible with a good work-life balance. I&#8217;ll share what I did each time the growing business started to threaten my lifestyle, and how you can do the same.</p>\n<h2>The Beginning</h2>\n<p>I had a traditional full-time job throughout my 20’s. I enjoyed building my career and earning a regular salary, but didn’t like the lack of flexibility that came with it.</p>\n<p>I didn’t like having to arrive at work by a fixed time, or being unable to choose when I worked. As a hard-working person, it felt counter-productive to be forced to work set hours when I may not be at my best.</p>\n<p>My daily commute was anything from 25-50 minutes (which I realise is less than many people). It felt like a waste of time as I could work just as well from home, not to mention the environmental impact of driving so far just to sit in an office. Day-to-day tasks such as ordering items for home delivery became a big deal, as I wasn’t home during the day.</p>\n<p>As a result, I spent most of my 20’s simultaneously building my career in a traditional job, while dreaming about running my own business and working for myself. Andy felt the same about his own job as a senior software developer.</p>\n<blockquote><p>I think that most people want a better lifestyle, but not many actually do anything about it. I thought I was one of those people.</p></blockquote>\n<p>Andy and I would talk endlessly about different business ideas (most of them terrible!) and even experimented with building a few websites that were never launched. However, we didn’t have the drive to make it happen and launch a business in the real world.</p>\n<h2>Starting a Business</h2>\n<p>In late 2009, Andy had finally had enough of his job and we agreed that it was time for him to quit. We decided to start a web design business together. He would work solely on the new business, while I would support it alongside my main job (which I didn&#8217;t hate, even though I didn&#8217;t like the lifestyle).</p>\n<p>We started by building WordPress websites for small local businesses. Andy built the websites and I was responsible for copywriting and marketing. We approached local tradespeople who didn&#8217;t already have a website &#8211; back in 2010, there were still a lot of these! Our first clients were local plumbers, electricians, a washing machine repair shop, etc.</p>\n<p>These early projects were quite low budget. The average hourly rate was quite low because we were still learning and hadn&#8217;t perfected our processes yet. We wasted a lot of time on projects where we had under-quoted but were committed to honoring the agreed price.</p>\n<blockquote><p>We made a lot of mistakes, and learned from them all!</p></blockquote>\n<p>By Year 2, the business was making the equivalent of a fairly low salary for one person. However, we had to work a lot for a relatively small income. This encouraged us to work more hours, and it wasn&#8217;t bringing the lifestyle benefits I was looking for.</p>\n<h2>Lifestyle Tip #1: Learn to Specialize</h2>\n<p>In late 2010, it occurred to me that we were building all our websites in WordPress but not advertising ourself as a WordPress company. I wondered whether people were actually searching for WordPress experts and whether this could be a good way to advertise. That may seem obvious in 2018 now WordPress is the world&#8217;s biggest web platform &#8211; but it was a genuine question back in 2010.</p>\n<p>On a whim, I invested $100 in Google AdWords targeting keywords such as &#8216;WordPress web design&#8217; and &#8216;WordPress developer&#8217;. Amazingly, we were overwhelmed with enquiries and quickly brought in over $4,000 of business &#8211; not a bad return on investment! The work came from medium sized companies who had never used our services before, with higher budgets.</p>\n<blockquote><p>Positioning ourselves as WordPress specialists completely changed the profile of our client base, as well as the budgets we were working with.</p></blockquote>\n<p>This vastly increased our average hourly income, so we were making more money without having to work more hours. Finally, it felt like a proper business with a better work-life balance.</p>\n<h2>Lifestyle Tip #2: Build a (virtual) team</h2>\n<p>The business grew quickly under its new identity as a specialist WordPress agency. By mid-2011, we had more work than we could manage ourselves. I also had a baby and increased my hours on the business while on maternity leave &#8211; eventually not returning to my old job. We still needed to increase the company&#8217;s income, while working towards the lifestyle we wanted.</p>\n<p>We grew the business to the next level by building a virtual team.</p>\n<blockquote><p>I felt quite strongly that I didn&#8217;t want to become a traditional employer with a team of staff, all working together in an office. That would bring me back to the lifestyle I started with!</p></blockquote>\n<p>Instead, I decided to recruit a team of freelancers.</p>\n<p>It took time to find the right freelancers, but the good news is that you can try someone out on a single project with no further commitment. If it doesn&#8217;t work out, then you don&#8217;t have to work with them again. Through trial and error, I built a team of freelancers with different WordPress-related skills. This increased capacity and allowed us to take on more projects without having to work more hours.</p>\n<p>I was still managing all the projects, but could take a step back and wasn&#8217;t directly building the websites. Finally, it felt like a proper WordPress agency.</p>\n<h2>Lifestyle Tip #3: Selling WordPress products</h2>\n<p>By building a distributed team, the business became more and more successful. We were taking on more and more projects, and I was managing all of them. By the time we were running 20 projects at once, I had reached the limits of my capacity and was having to work a lot of hours.</p>\n<p>From 2014-15, I experimented with working with freelance project managers, but had to give up because quality was dropping and our clients were less happy. I realised that with the current business model, I could only continue growing the business by working more and more hours. This wasn&#8217;t what I had been working towards!</p>\n<p>It was time for Andy and I to pursue our other dream: selling WordPress products. We&#8217;d been talking about this since the early days of the business, but the client projects had kept us so busy that we&#8217;d never done anything about it.</p>\n<p>In early 2016, Andy stepped out of the client business and started writing WordPress and WooCommerce plugins to sell. I continued managing client projects for the next 6 months, until the plugins were making enough money to stop taking on new projects and I could spend all my time marketing and supporting the plugins.</p>\n<blockquote><p>Selling WordPress plugins has been very successful because we already knew the market inside out from our years of developing WordPress sites.</p></blockquote>\n<p>We knew where the gaps were and what plugin customers want. We knew where other plugin companies get it wrong, and could learn from their mistakes without making the same mistakes ourselves!</p>\n<p>By launching several plugins, we could listen to what our customers were asking for and build even more. In October 2016, we launched our <a href="https://barn2.co.uk/wordpress-plugins/woocommerce-product-table/">WooCommerce Product Table plugin</a> because so many people asked for a way to list products in a table with add to cart buttons. This immediately became our bestselling plugin and has sold more than all our other plugins combined. Since then, the plugin business has gone from strength to strength.</p>\n<blockquote><p>I have found that selling WordPress products brings a much better work-life balance than providing WordPress services.</p></blockquote>\n<p>We receive (many) plugin support requests every day, but each one takes relatively little time and is less pressured than fixing problems for web design clients. The whole business feels much more relaxed, and I don&#8217;t feel guilty about taking time off.</p>\n<p>Between the two of us, we spend a couple of hours a day on plugin support. We continue improving the plugins, marketing, adding features and building the business on top of that. However, all of this is optional and can easily be done while working part-time.</p>\n<h2>Snow Day! Putting It Into Practice</h2>\n<p>Before we finish, I&#8217;ll tell you about my week. Today is Friday. At 10.30am on Wednesday, I received a text that my daughter&#8217;s school had closed for the rest of the week because of the unusual snow here in the UK.</p>\n<p>The parents with traditional jobs panicked and had to quickly arrange childcare or time-off work. Some of them were stuck in cars on snowed-in roads as they tried to return to the village. No one could get to work the next day. A lot of people lost a lot of money.</p>\n<p>Andy and I simply stopped work, put on our snow gear, walked the 10 minutes to the school, and then went sledging. Since then, we&#8217;ve been sharing the childcare in between responding to plugin support requests (and writing this article!). We&#8217;ve had 37 plugin sales on our website since the school closed, even though we&#8217;ve been working less hours than usual. Now, that&#8217;s what I&#8217;ve been working towards!</p>\n<h2>Conclusion</h2>\n<p>I&#8217;ve worked hard and have been extremely committed to building Barn2 Media. However, this has always been on the condition that it wouldn&#8217;t sacrifice my lifestyle goals.</p>\n<blockquote><p>For me, the ideal business is measured against a combination of financial success and lifestyle benefits. If the founders are working 70 hours a week to keep the money coming in, then it&#8217;s not a successful business!</p></blockquote>\n<p>You can do the same. Design a WordPress business that will give you the lifestyle you want, as well as making money. If you love working with people, build a team and provide WordPress services (WordPress design and development are good for this). If you want to travel, choose work that you can do remotely from different time zones (WordPress products are good for this). Plan your business around what matters to you.</p>\n<p>WordPress is such a huge ecosystem that it comes with many opportunities to build a successful business. With a bit of extra thought and planning, you can build a WordPress business that is successful AND lets you life the lifestyle you&#8217;ve always wanted. That is the true measure of success.</p>\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: Building A New Life" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Building%20A%20New%20Life&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbuilding-a-new-life%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Building A New Life" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fbuilding-a-new-life%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%2Fessays%2Fbuilding-a-new-life%2F&title=Building+A+New+Life" rel="nofollow" target="_blank" title="Share: Building A New Life"></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/essays/building-a-new-life/&media=https://heropress.com/wp-content/uploads/2018/03/030718-150x150.jpg&description=Building A New Life" rel="nofollow" target="_blank" title="Pin: Building A New Life"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/building-a-new-life/" title="Building A New Life"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/building-a-new-life/">Building A New Life</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, 07 Mar 2018 08:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Katie Keith";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:63:"WPTavern: WordPress Now Used on 30% of the Top 10 Million Sites";s:7:"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=78214";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"https://wptavern.com/wordpress-now-used-on-30-of-the-top-10-million-sites";s: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:2379:"<p><a href="https://w3techs.com/">W3Techs</a>, a survey company that monitors usage of various web technologies, <a href="https://w3techs.com/technologies/details/cm-wordpress/all/all">is reporting</a> that WordPress has reached 30% usage or 60.2% market share of all the websites whose content management systems it knows about. This represents a 0.6% increase since February 1st and 13.1% over the last seven years.</p>\n<p>Just five days ago, Matt Mullenweg, co-creator of WordPress, brought attention to the approaching milestone.</p>\n<blockquote class="twitter-tweet">\n<p lang="und" dir="ltr">29.9%&#8230;</p>\n<p>&mdash; Matt Mullenweg (@photomatt) <a href="https://twitter.com/photomatt/status/969378724305973249?ref_src=twsrc%5Etfw">March 2, 2018</a></p></blockquote>\n<p></p>\n<p>When it comes to WordPress&#8217; market share numbers, W3Techs is the most cited source. While some say that <a href="https://thenextweb.com/dd/2018/03/05/30-of-the-web-now-runs-on-wordpress/">WordPress now powers 30% of the web</a>, <a href="https://w3techs.com/technologies">technically</a>, it is used by 30% of the top 10 million sites based on traffic according to <a href="https://www.alexa.com/">Alexa</a>. All sub-domains on WordPress.com and WordPress.org count as one site.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">All the subdomains of <a href="https://t.co/37ETZ4JMFf">https://t.co/37ETZ4JMFf</a> and <a href="https://t.co/YtO6Msd90U">https://t.co/YtO6Msd90U</a> do indeed only count as one site. Sites that are hosted by Automattic under their own domain do count if they have significant traffic on that domain. These are 0.4%, 29.5% are hosted somewhere else.</p>\n<p>&mdash; W3Techs (@W3Techs) <a href="https://twitter.com/W3Techs/status/969523570530451456?ref_src=twsrc%5Etfw">March 2, 2018</a></p></blockquote>\n<p></p>\n<p>The internet is larger than the top 10 million sites. According to <a href="http://www.internetlivestats.com/total-number-of-websites/">Internet live stats</a>, there are close to 2 billion sites on the internet although a majority of them are inactive.</p>\n<p>W3Techs&#8217; numbers show that WordPress&#8217; use is growing on sites that receive a lot of traffic and shows no signs of slowing down as it makes <a href="https://wptavern.com/how-important-is-jetpack-on-wordpress-road-to-50-market-share">its way towards 50%</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, 06 Mar 2018 10:22:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:111:"WPTavern: New Plugin Makes WordPress Core Updates More Secure by Requiring Cryptographic Signature Verification";s:7:"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=78171";s:7:"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:122:"https://wptavern.com/new-plugin-makes-wordpress-core-updates-more-secure-by-requiring-cryptographic-signature-verification";s: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:4278:"<p>In 2016, WordFence <a href="https://www.wordfence.com/blog/2016/11/hacking-27-web-via-wordpress-auto-update/">published their findings</a> of a vulnerability that could have compromised the servers that are used to send out WordPress updates. It turned out to be a complex, obscure vulnerability that ignited a conversation surrounding the security of api.wordpress.org and what could happen if the servers were compromised.</p>\n<p>One idea that was brought forth is to digitally sign WordPress core, theme, and plugin updates. For at least five years, <a href="https://core.trac.wordpress.org/ticket/25052">a trac ticket</a> has laid semi-dormant with this idea in mind.</p>\n<p>Fifteen months ago, Scott Arciszewski, Chief Development Officer for Paragon Initiative Enterprises, who is most widely known for his <a href="https://paragonie.com/blog/2017/02/cryptographically-secure-php-development">cryptography engineering work</a>, <a href="https://web.archive.org/web/20170214062414/https://medium.com/@CiPHPerCoder/stopmullware-on-the-security-of-27-of-the-websites-on-the-internet-298a7e5b6871">published an article</a> that has since been taken down, expressing his strong desire for Matt Mullenweg to make secure cryptographic signatures a priority. Mullenweg responded to his post with <a href="https://medium.com/@photomatt/wordpress-and-update-signing-51501213e1">one of his own</a> stating that although WordPress update signing is important, it&#8217;s not a high priority.</p>\n<p>&#8220;We will at some point; as said above it’s a good idea — can’t hurt, might help,&#8221; Mullenweg responded when asked if WordPress was ever going to do update signing. &#8220;There are, however, some more important security issues in front of it, that impact millions of sites in the real world, so we are prioritizing those issues above a nice-to-have, defense in-depth effort.&#8221;</p>\n<h2>Eric Mann Launches Secure WordPress Updates Plugin</h2>\n<p>While WordPress does not digitally sign updates, Eric Mann, founder of <a href="https://displace.tech/">Displace Technologies, LLC</a>, has <a href="https://ttmm.io/tech/introducing-secure-updates-for-wordpress/">created and released</a> a new plugin that adds code signing to WordPress core updates. It&#8217;s called DGXPCO or <a href="https://wordpress.org/plugins/dgxpco/">Digital Guarantees for eXplicitly Permitted Core Operations</a>. You&#8217;ll find it on the plugin directory by searching for DGXPCO.</p>\n<p>When installed and activated, the plugin integrates with the core updater and requires that any core update must have a valid signature before it can be installed. The signature provides a secondary source of truth that confirms the integrity of the files. The signatures are created using a Ed25519 public/private keypair and <a href="https://github.com/jedisct1/libsodium">Libsodium</a> to sign the files’ contents.</p>\n<p>Mann keeps the private key offline and has published the public key online. The public key will not change and if a core update is signed by a different key, it is a red flag and the update should be avoided. In addition, commits made to the <a href="https://github.com/DisplaceTech/release-hashes">release hashes repository</a> on GitHub are signed with <a href="https://keybase.io/eamann">Mann&#8217;s PGP key</a> to verify that he is the one who added new code.</p>\n<p>Mann admits that the solution is not fool-proof and is working towards improving it. In future versions, the plugin will only notify the user of a WordPress core update if a digital signature is available. Plugins and themes are on the roadmap as well with the ability to opt-in.</p>\n<p>Although he is the only person allowed to digitally sign packages, the model is not sustainable.</p>\n<p>&#8220;As I prove out the update system, I’ll also begin adding sets of public keys that are scoped to specific sets of packages,&#8221; Mann said. &#8220;This will, for example, allow me to whitelist a small number of trusted developers to also sign core packages. It might also empower plugin developers to sign their own releases (but not anyone else’s).&#8221;</p>\n<p>Mann is seeking feedback and is hoping the project provides evidence that something like it can be added to WordPress core.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 03 Mar 2018 00:56:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:75:"Post Status: Marketing and positioning WordPress products — Draft podcast";s:7:"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=44157";s:7:"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://poststatus.com/marketing-positioning-wordpress-products-draft-podcast/";s: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:2776:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.</p>\n<p>This week BK and BR discuss a number of different aspects surrounding marketing and selling WordPress products and services. The conversation flows from selling benefits vs features, to social proof, to marketing and conversion funnels, to understanding and reacting to the problem space, to customer support, and many things in between. Whether you’re already selling products or services, about to sell something, or routinely buy things, there’s likely something for you in this episode.</p>\n<p></p>\n<h3>Links</h3>\n<ul>\n<li>Krogs’ <a href="https://wordpress.tv/2015/12/13/brian-krogsgard-how-to-build-a-compelling-wordpress-product-or-service">WCUS funnel talk</a>: and <a href="https://cdn.poststatus.com/wp-content/uploads/2015/12/krogsgard-wc-us-2015-presentation.pdf">slides</a></li>\n<li><a href="https://wpsessions.com/sessions/understand-price-anchoring/">Price Anchoring session</a> on WPS</li>\n<li><a href="https://poststatus.com/marketing-wordpress-products/">Tips for marketing WordPress products</a></li>\n<li><a href="https://poststatus.com/resources/marketing-success-wordpress-case-study-siteground/">SiteGround’s Publish presentation</a></li>\n<li><a href="https://www.ted.com/talks/barry_schwartz_on_the_paradox_of_choice">TED talk on decision fatigue and the paradox of choice</a> (also good “<a href="https://www.ted.com/talks/dan_gilbert_researches_happiness">Why we make bad decisions</a>”)</li>\n<li><a href="https://stripe.com/atlas/guides/saas-pricing">Stripe Atlas guide to SaaS pricing</a></li>\n</ul>\n<h3>Sponsor: SiteGround</h3>\n<p><a href="https://www.siteground.com/wordpress-hosting.htm/?utm_source=post_status&utm_medium=banner&utm_campaign=ps_ads">SiteGround</a> is engineered for speed, built for security, and crafted for WordPress. They offer feature-rich managed WordPress hosting with premium support, and are officially recommended by WordPress.org. Check out <a href="https://siteground.com/poststatus/?utm_source=post_status&utm_medium=banner&utm_campaign=ps_ads">SiteGround&#8217;s website</a> for a special deal for Post Status listeners, and thanks to SiteGround 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:"Fri, 02 Mar 2018 20:24: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:"Katie Richards";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:77:"WPTavern: 4,500 Plugins Need Your Help in Determining Gutenberg Compatibility";s:7:"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=78194";s:7:"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/4500-plugins-need-your-help-in-determining-gutenberg-compatibility";s: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:2608:"<p>One of the keys to a successful roll out of Gutenberg is plugin compatibility. Without it, users will experience unnecessary frustration and hamper enthusiasm of the new editor. In an effort to figure out what plugins are already compatible with Gutenberg, Daniel Bachhuber <a href="https://make.wordpress.org/core/2018/03/01/introducing-the-gutenberg-plugin-compatibility-database/">has created</a> a <a href="https://plugincompat.danielbachhuber.com/">Gutenberg Plugin Compatibility Database</a>.</p>\n<img />Gutenberg Plugin Compatibility Database\n<p>The database contains 5,000 plugins that represent more than 90% of the total active install count. Plugins are compatible with Gutenberg if they meet the following two requirements.</p>\n<ul>\n<li>A WordPress user can perform the same functional task with Gutenberg active. For instance, if the plugin includes an &#8216;Add Media&#8217; button, it&#8217;s considered Gutenberg-compatible when it has a block registered for the Gutenberg inserter.</li>\n<li>There are no (obvious) errors when the WordPress plugin is active alongside Gutenberg.</li>\n</ul>\n<p>In order to participate in the testing process, you&#8217;ll need to <a href="https://plugincompat.danielbachhuber.com/#account-details/">register an account</a> on the site. Once approved, testers will be able to create a fresh sandboxed WordPress install on the site and test randomly selected plugins. After a manual review is complete, plugins will be marked as <code>is_compatible=yes</code> or <code>is_compatible=no</code>.</p>\n<p>Some plugins are already classified with <code>is_compatible=likely_yes</code> or <code>is_compatible=likely_</code>. As reports are completed, two pie charts that display compatibility results at the bottom of the site update automatically.</p>\n<p>Bachhuber estimates that if each plugin takes about a minute to test, they&#8217;ll need roughly 75 person-hours to get through the remaining 4,500 plugins in the database. This project is a great opportunity for individuals and businesses to contribute back to WordPress via the <a href="https://ma.tt/2014/09/five-for-the-future/">Five for The Future initiative</a>.</p>\n<p>Ideal testers are those who can review dozens of plugins, but even reviewing a few will help the project. If you&#8217;re interested in contributing, check out the project&#8217;s <a href="https://github.com/danielbachhuber/gutenberg-plugin-compatibility#gutenberg-plugin-compatibility">GitHub page</a> to learn what&#8217;s involved in the testing process. Alternatively, visitors can watch the following YouTube video.</p>\n<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Mar 2018 00:57:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:47:"Dev Blog: The Month in WordPress: February 2018";s:7:"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=5613";s:7:"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/2018/03/the-month-in-wordpress-february-2018/";s: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:5935:"<p>Judging by the flurry of activity across the WordPress project throughout February, it looks like everyone is really getting into the swing of things for 2018. There have been a lot of interesting new developments, so read on to see what the community has been up to for the past month.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>WordPress 4.9.3 &amp; 4.9.4</h2>\n\n<p>Early in the month, <a href="https://wordpress.org/news/2018/02/wordpress-4-9-3-maintenance-release/">version 4.9.3 of WordPress was released</a>, including a number of important bug fixes. Unfortunately it introduced a bug that prevented many sites from automatically updating to future releases. To remedy this issue, <a href="https://wordpress.org/news/2018/02/wordpress-4-9-4-maintenance-release/">version 4.9.4 was released</a> the following day requiring many people to manually update their sites.</p>\n\n<p>While this kind of issue is always regrettable, the good thing is that it was fixed quickly, and that not all sites had updated to 4.9.3 yet, which meant they bypassed the bug in that version.</p>\n\n<p>You can find out more technical information about this issue <a href="https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/">on the Core development blog</a>.</p>\n\n<h2>The WordCamp Incubator is Back</h2>\n\n<p>In 2016, the Global Community Team ran an experimental program to help spread WordPress to underserved areas by providing more significant organizing support for their first WordCamp event. This program was dubbed the WordCamp Incubator, and it was so successful in the three cities where it ran that <a href="https://wordpress.org/news/2018/02/wordcamp-incubator-2-0/">the program is back for 2018</a>.</p>\n\n<p>Right now, the Community Team is looking for cities to be a part of this year’s incubator by <a href="https://wordcampcentral.polldaddy.com/s/wordcamp-incubator-program-2018-city-application">taking applications</a>. Additionally, each incubator community will need an experienced WordCamp organizer to assist them as a co-lead organizer for their event — if that sounds interesting to you, then you can <a href="https://wordcampcentral.polldaddy.com/s/wordcamp-incubator-program-2018-co-lead-application">fill in the application form for co-leads</a>.</p>\n\n<p>You can find out further information about the WordCamp Incubator <a href="https://make.wordpress.org/community/2018/02/19/wordcamp-incubator-program-2018-announcement/">on the Community Team blog</a>.</p>\n\n<h2>WordPress Meetup Roundtables scheduled for March</h2>\n\n<p>In order to assist local WordPress meetup organizers with running their meetup groups, some members of the Community Team have organized <a href="https://make.wordpress.org/community/2018/02/23/wordpress-meetup-roundtables-scheduled-for-march/">weekly meetup roundtable discussions through the month of March</a>.</p>\n\n<p>These will be run as video chats at 16:00 UTC every Wednesday this month and will be a great place for meetup organizers to come together and help each other out with practical ideas and advice.</p>\n\n<p>If you are not already in the WordPress meetup program and would like to join, you can find out more information in <a href="https://make.wordpress.org/community/handbook/meetup-organizer/welcome/">the WordPress Meetup Organizer Handbook</a>.</p>\n\n<h2>GDPR Compliance in WordPress Core</h2>\n\n<p>The General Data Protection Regulation (GDPR) is an upcoming regulation that will affect all online services across Europe. In order to prepare for this, a working group has been formed to make sure that WordPress is compliant with the GDPR regulations.</p>\n\n<p>Aside from the fact that this will be a requirement for the project going forward, it will also have an important and significant impact on the privacy and security of WordPress as a whole. The working group has posted <a href="https://make.wordpress.org/core/2018/02/19/proposed-roadmap-tools-for-gdpr-compliance/">their proposed roadmap</a> for this project and it looks very promising.</p>\n\n<p>To get involved in building WordPress Core, jump into the #gdpr-compliance channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>, and follow <a href="https://make.wordpress.org/core/">the Core team blog</a>.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>Further Reading:</h2>\n\n<ul>\n    <li>WPShout published <a href="https://wpshout.com/complete-guide-wordpress-security/">a thorough guide to WordPress security</a>.</li>\n    <li>The Community Team has published interesting statistics from the WordCamp program in <a href="https://make.wordpress.org/community/2018/02/27/wordcamps-in-2016/">2016</a> and <a href="https://make.wordpress.org/community/2018/02/28/wordcamps-in-2017/">2017</a>.</li>\n    <li><a href="https://make.wordpress.org/community/2018/02/15/potential-addition-of-a-new-onboarding-team/">An intriguing proposal has been made</a> for a new ‘Onboarding’ team to be started in the WordPress project.</li>\n    <li>The new editing experience for WordPress, named Gutenberg, continues to be actively developed with <a href="https://make.wordpress.org/core/2018/02/16/whats-new-in-gutenberg-16th-february/">a feature-packed release</a> this past month.</li>\n    <li>The Advanced WordPress Facebook group <a href="https://www.youtube.com/watch?v=4vS_jR5-nIo">held an interview with WordPress co-founder, Matt Mullenweg</a> about the Gutenberg project.</li>\n    <li><a href="https://make.wordpress.org/meta/2018/02/27/two-factor-authentication-on-wp-org/">Two factor authentication is on its way to the WordPress.org network</a> — this will be a great improvement to the overall security of the project.</li>\n</ul>\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</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:"Thu, 01 Mar 2018 08:41:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:83:"WPTavern: WPWeekly Episode 306 – AMP, GDPR, and Brewing Beer At The Boss’ 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:58:"https://wptavern.com?p=78185&preview=true&preview_id=78185";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:85:"https://wptavern.com/wpweekly-episode-306-amp-gdpr-and-brewing-beer-at-the-boss-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:1707:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> joins me live from Hutchinson, KS, to talk about the news of the week. We started off the show discussing the GDPR and the number of things that need to be considered surrounding the right to be forgotten.</p>\n<p>We also have a lengthy conversation about AMP, the open web, and Automattic&#8217;s relationship with Google. Last but not least, we discussed Automattic&#8217;s recent hiring of Kinsey Wilson to be president of the company.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://wptavern.com/matt-cromwell-hosts-matt-mullenweg-in-qa-gutenberg-interview">Matt Cromwell Hosts Matt Mullenweg in Q&amp;A Gutenberg Interview</a><br />\n<a href="https://wptavern.com/new-team-forms-to-facilitate-gdpr-compliance-in-wordpress-core">New Team Forms to Facilitate GDPR Compliance in WordPress Core</a><br />\n<a href="https://www.poynter.org/news/one-time-npr-and-nyt-digital-chief-new-adventure-wordpress">For one-time NPR and NYT digital chief, a new adventure: WordPress</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, March 7th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #306:</strong><br />\n</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, 01 Mar 2018 02:19:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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: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:38:"HeroPress: Changes Coming To HeroPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://heropress.com/?p=2471";s:7:"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:115:"https://heropress.com/changes-coming-heropress/#utm_source=rss&utm_medium=rss&utm_campaign=changes-coming-heropress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4198:"<p>Over the last few months, I’ve been having some deep talks with my <a href="https://twitter.com/mysweetcate">HeroPress partner</a> about what the future of HeroPress looks like. We came up with some changes that feel deeply satisfying. Changes we think should help HeroPress, help readers, and help us as content producers. So here we go.</p>\n<h3>Financial Changes</h3>\n<p>At various times in the past people have told me that the time I spend on HeroPress is worth compensation. When I first started it as a blog, I had no intention of getting money from it. However, being compensated for my time helped ease the burden on my family.</p>\n<blockquote><p>With that in mind, last fall I test-drove a donation page based on interest from some in the community.</p></blockquote>\n<p>It was a good idea, and I’m thankful for the support I received, but for now it’s not the right path.</p>\n<p>So, I’ve pulled the donation page from the site and am no longer accepting site sponsors. You’ll notice I do have a Sponsorship page, but it lists organizations that have made material contributions like hosting, plugins, etc.</p>\n<h3>Content Changes</h3>\n<p>We’ve been publishing every Wednesday for several years now. Over time, readership has climbed quite a bit. That’s great, but it means that many current readers have never seen the earlier content, which remains quite evergreen.</p>\n<blockquote><p>To address this, we’re going to do new HeroPress essays once a month. The other weeks of the month will be replays of earlier essays.</p></blockquote>\n<p>This allows for some breathing room in gathering new contributors and brings back some really great content that shouldn’t be forgotten.</p>\n<p>It also opens up my time to explore the community more. To see if there are new ways that people, particularly on the fringe, can be helped. Sharing stories is useful, but are there other opportunities and needs we’re missing?</p>\n<h3>The Future</h3>\n<p>So HeroPress will continue. I still love doing it. At various times we’ve discussed making it bigger, doing grand things. But not now. For now we’re going to let it grow organically and continue letting it serve its purpose: to give voice to WordPress stories, to make them known, to inspire.</p>\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: Changes Coming To HeroPress" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Changes%20Coming%20To%20HeroPress&via=heropress&url=https%3A%2F%2Fheropress.com%2Fchanges-coming-heropress%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Changes Coming To HeroPress" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fchanges-coming-heropress%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%2Fchanges-coming-heropress%2F&title=Changes+Coming+To+HeroPress" rel="nofollow" target="_blank" title="Share: Changes Coming To HeroPress"></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/changes-coming-heropress/&media=https://heropress.com/wp-content/plugins/rtsocial/images/default-pinterest.png&description=Changes Coming To HeroPress" rel="nofollow" target="_blank" title="Pin: Changes Coming To HeroPress"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/changes-coming-heropress/" title="Changes Coming To HeroPress"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/changes-coming-heropress/">Changes Coming To HeroPress</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, 28 Feb 2018 12:00:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:72:"WPTavern: New Team Forms to Facilitate GDPR Compliance in WordPress Core";s:7:"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=78149";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:83:"https://wptavern.com/new-team-forms-to-facilitate-gdpr-compliance-in-wordpress-core";s: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:6200:"<p>As May 25th, the enforcement date for the <a href="https://www.eugdpr.org/">General Data Protection Regulation</a> (GDPR) draws near, individuals and businesses are scrambling to make sure they&#8217;re compliant. I&#8217;ve read a number of blog posts throughout the WordPress community explaining the GDPR and what needs to be done for compliance and it&#8217;s a tough thing to grasp.</p>\n<p>The EU GDPR was designed to harmonize data privacy laws across Europe, protect and empower European citizens data privacy, and reshape the way organizations across the region approach data privacy. In reading the regulation and various blog posts, the terminology makes it appear that the changes are geared towards large, international businesses that process personal data.</p>\n<p>However, <a href="https://www.smashingmagazine.com/2018/02/gdpr-for-web-developers/">according to Heather Burns</a>, a digital law specialist in Glasgow, Scotland, the GDPR affects sites large and small.</p>\n<blockquote><p>GDPR applies to all businesses, organizations, sectors, situations, and scenarios, regardless of a business’s size, head count, or financial turnover. A small app studio is every bit as beholden to these rules as a large corporation.</p></blockquote>\n<p>Determining if your site needs to be compliant and how to accomplish it can be overwhelming. If you do business in Europe or collect data from European users, you must protect that data in accordance with the GDPR as if you were in Europe. For example, if you operate a blog with a contact form that saves entries to the database from people who live in Europe, you must make your site GDPR compliant.</p>\n<p>There are a lot of aspects to the GDPR and while an excerpt can not fully explain it at a glance, there are a few themes that stick out to me.</p>\n<ul>\n<li>Be upfront and concise about what data is stored, sent, and used on the site or form.</li>\n<li>Give the user a chance to consent without automatically opting them in.</li>\n<li>Collect the least amount of data possible for legitimate business purposes.</li>\n<li>Provide a way for users to download or access their data and remove it.</li>\n</ul>\n<p>Many of these are common sense practices that are not implemented on many sites, WP Tavern included. How often do you visit a <a href="https://wptavern.com/contact-me">site&#8217;s contact form</a> and see an explanation as to why those fields are required, where the data is stored, where it goes, and what is done with it? This is something I&#8217;ll be working on in the next few weeks.</p>\n<h2>Making WordPress Core GDPR Compliant</h2>\n<p>Earlier <a href="https://make.wordpress.org/core/2018/02/13/gdpr-compliance-agenda-february-14/">this month</a>, a number of volunteers gathered to discuss GDPR compliance in WordPress core. The meeting took place in a newly created channel #gdpr-compliance that&#8217;s accessible to anyone with a <a href="https://make.wordpress.org/chat/">SlackHQ account</a>.</p>\n<p>The team created a <a href="https://make.wordpress.org/core/2018/02/19/proposed-roadmap-tools-for-gdpr-compliance/">proposed roadmap</a> to add privacy tools to core. The plan includes the following ideas:</p>\n<ul>\n<li>Add notices for registered users and commenters on what data is collected in core by default and explain why.</li>\n<li>Create guidelines for plugins on how to become GDPR compliant.</li>\n<li>Create and add tools to facilitate compliance and privacy in general.</li>\n<li>Add documentation and help for site owners to learn how to use these tools.</li>\n</ul>\n<p><a href="https://wordpress.slack.com/archives/C9695RJBW/p1519227959000760">Earlier today</a>, <a href="https://make.wordpress.org/core/2018/02/27/gdpr-compliance-chat-recap-february-21st/">the team met</a> and created a <a href="https://github.com/gdpr-compliance/info">GitHub folder</a> that houses the roadmap, knowledge base, trac ticket list, and other items associated with the project. There was also some discussion on whether the interface provided by the <a href="https://www.gdprwp.com/">GDPR for WordPress project</a> is a good foundation for core and plugins to report personal data. The GDPR Compliance Slack channel is also a good place to ask questions and discuss data privacy in general.</p>\n<p>Popular form plugins such as <a href="https://docs.gravityforms.com/wordpress-gravity-forms-and-gdpr-compliance/">GravityForms</a> and <a href="https://ninjaforms.com/gdpr-compliance-wordpress-forms/">NinjaForms</a> have documentation available that explains GDPR compliance and how it applies to their products. For those who use the Contact Form module in Jetpack which <a href="https://github.com/Automattic/jetpack/issues/8430">saves entries to the database by default</a>, you&#8217;ll need to wait for further updates. <a href="https://woocommerce.com/2017/12/gdpr-compliance-woocommerce/">WooCommerce</a> and <a href="https://en.support.wordpress.com/automattic-gdpr/">Automattic</a> have announced that they expect their products will be GDPR compliant by the time it goes into effect later this year.</p>\n<h2>GDPR Resources</h2>\n<p>If you&#8217;re like me, reading about the GDPR and its policies can make your head spin. It&#8217;s important to keep in mind that at the heart of the GDPR are common sense behaviors for handling personal data. If you&#8217;d like to learn more about the GDPR, check out the following resources.</p>\n<ul>\n<li><a href="https://www.smashingmagazine.com/2018/02/gdpr-for-web-developers/">How GDPR Will Change The Way You Develop</a></li>\n<li><a href="https://wordpress.tv/2016/11/01/heather-burns-get-to-grips-with-gdpr/">Heather Burns: Get To Grips With GDPR</a></li>\n<li><a href="https://webdevlaw.uk/data-protection-gdpr/">Data protection (GDPR)</a></li>\n<li><a href="https://wptavern.com/wpweekly-episode-298-gdpr-user-privacy-and-more-with-heather-burns">WPWeekly Episode 298 – GDPR, User Privacy, and More With Heather Burns</a></li>\n<li><a href="https://www.eugdpr.org/gdpr-faqs.html">GDPR FAQs</a></li>\n<li><a href="https://premium.wpmudev.org/blog/gdpr-compliance/">Is Your Website GDPR Compliant? How to Get Ready for the General Data Protection Regulations</a></li>\n</ul>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 27 Feb 2018 23:20:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:75:"WPTavern: Matt Cromwell Hosts Matt Mullenweg in Q&amp;A Gutenberg Interview";s:7:"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=78166";s:7:"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/matt-cromwell-hosts-matt-mullenweg-in-qa-gutenberg-interview";s: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:2903:"<p>Matt Cromwell, Head of Support and Community Outreach for <a href="https://givewp.com/">GiveWP</a> and an administrator for the <a href="https://www.facebook.com/groups/advancedwp/">Advanced WordPress Facebook group</a>, hosted a question and answer session about Gutenberg with Matt Mullenweg earlier today. The interview concludes the <a href="http://www.advancedwp.org/awp-gutenberg-interview-series/">Advanced WordPress Gutenberg interview series</a> that includes, <a href="https://wordpress.tv/2018/02/06/awp-gutenberg-interview-series-with-joost-de-valk/">Joost de Valk</a>, <a href="https://wordpress.tv/2018/02/18/awp-gutenberg-interview-series-with-ahmad-awais/">Ahmad Awais</a>, and <a href="https://youtu.be/ic_du_lsbLE">Tammie Lister</a>.</p>\n<p>Mullenweg began the session by explaining why there is a concerted effort to improve the editor. &#8220;It&#8217;s really almost any user test that you watch,&#8221; he said. &#8220;Both watching people brand new to WordPress and those with years of experience on how they used the editor. It became obvious that we could make something more accessible to new users, but also, a lot more powerful for developers.&#8221;</p>\n<p>With regards to a release date, Mullenweg confirmed that Gutenberg will ship when it&#8217;s ready. Later in the interview, Mullenweg was asked if he could provide a more concrete answer.</p>\n<p>&#8220;For those who want a concrete date, we will have one or two orders of magnitude more users of Gutenberg in April,&#8221; he responded. &#8220;That doesn&#8217;t mean necessarily a 5.0 release, but it does mean that if you&#8217;re planning on aiming for something where a lot of users will be interacting with Gutenberg, aim for April.&#8221;</p>\n<p>While the project&#8217;s name is Gutenberg, some developers have <a href="https://github.com/WordPress/gutenberg/issues/4681">expressed concerns</a> on how the name will be deprecated if at all once it&#8217;s merged into core. There are a number of educational resources, products, and tool kits referencing Gutenberg that could be a source of confusion once it&#8217;s merged into core and referred to as the editor.</p>\n<p>Mullenweg was asked if the Gutenberg name will be deprecated. &#8220;We&#8217;ll see,&#8221; he replied. &#8220;I don&#8217;t think it&#8217;s the most important thing to figure out right now. We&#8217;re tackling some much bigger issues. If the plugin is useful, we&#8217;ll keep it around for beta testing, if not, we&#8217;ll have it turn itself off.&#8221;</p>\n<p>Mullenweg concluded the interview thanking the <a href="https://www.facebook.com/groups/advancedwp/">Advanced WordPress Facebook</a> group for the passion and discussions shared by members. The group has more than 30K members, is free to join, well maintained, and often filled with interesting topics. You can watch the interview in its entirety below.</p>\n<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 26 Feb 2018 23:32:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:67:"Post Status: Observations on a maturing ecosystem — Draft podcast";s:7:"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=43914";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://poststatus.com/observations-maturing-ecosystem-draft-podcast/";s: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:1743:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.</p>\n<p>In this episode, the Brians chat about the steady change that has played out in the WordPress ecosystem throughout the past decade and speculate about what is still to come. One aspect they explore rather deeply is the future trajectory of a website’s purpose and the role WordPress has to play in this transition. Plus, don’t miss their conversation about the new WordPress.com president and Google’s move to hire WordPress talent.</p>\n<p></p>\n<h3>Links</h3>\n<ul>\n<li><a href="https://memos.blog/2018/02/15/kinsey-wilson-named-president-of-wordpress-com/">New WordPress.com President announcement</a></li>\n<li><a href="https://medinathoughts.com/2018/01/29/wordpress-google/">Google&#8217;s WordPress job opportunity</a></li>\n<li><a href="https://micro.blog/">micro.blog</a></li>\n</ul>\n<h3>Sponsor: SearchWP</h3>\n<p>SearchWP makes WordPress search better. Instantly improve your site search without writing a line of code! SearchWP enables custom algorithms, searching custom fields, product data, and much more. Improve your site’s search today with our partner, <a href="https://searchwp.com">SearchWP</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:"Sun, 25 Feb 2018 12:59: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:"Katie Richards";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:77:"WPTavern: WordCamp Orange County Plugin-A-Palooza First Place Prize is $3,000";s:7:"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=78153";s:7:"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-orange-county-plugin-a-palooza-first-place-prize-is-3000";s: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:2009:"<p><a href="https://2018.oc.wordcamp.org/">WordCamp Orange County</a>, CA, 2018 will take place June 9-10. In addition to the regular WordCamp format of speakers sharing their knowledge, there is also a mini-event called Plugin-A-Palooza. This year marks the fourth contest where plugin authors will compete for one of three prizes.</p>\n<ul>\n<li>First Place – <strong>$3,000</strong> cash and 1 Sucuri Business (VIP) license</li>\n<li>Second Place – <strong>$1,500</strong> cash and 1 Sucuri Business (VIP) license</li>\n<li>Third Place – <strong>$500</strong> cash</li>\n</ul>\n<p>Teams will be judged live based on the following criteria:</p>\n<ul>\n<li>Originality</li>\n<li>User Experience/User Interface</li>\n<li>Code Quality</li>\n<li>Presentation of the plugin on WordPress.org.</li>\n</ul>\n<p>Teams can have up to three participants, are required to build their own plugin, and upload it to the WordPress plugin directory by May 18th. Teams will present their plugins to the judges and audience on June 10th.</p>\n<p>Previous winners and plugins include:</p>\n<ul>\n<li>2015 Devin Walker- <a href="https://wordpress.org/plugins/wp-rollback/">WP Rollback</a></li>\n<li>2016 Robert Gillmer &#8211; <a href="https://wordpress.org/plugins/wp-documentor/">WP Documentor</a></li>\n<li>2017 Natalie MacLees &#8211; <a href="https://wordpress.org/plugins/simple-event-listing/">Simple Event Listing</a></li>\n</ul>\n<p>Bridget Willard, WordCamp Orange County organizer, says the event encourages innovation and personal development which are important parts of WordCamps. &#8220;The first plugin that won was WPRollback by WordImpress,&#8221; she said. &#8220;It&#8217;s widely used in the community now. We&#8217;d love to see other camps doing this.&#8221;</p>\n<p>If you&#8217;re interested in participating in Plugin-A-Palooza at WordCamp Orange County this year, you&#8217;ll need to fill out this <a href="https://goo.gl/forms/CpDCsXQRqNI0cil23">entry form</a>. The deadline for submissions is March 5th.</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, 23 Feb 2018 22:46:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:32:"Dev Blog: WordCamp Incubator 2.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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5577";s:7:"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/2018/02/wordcamp-incubator-2-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:2449:"<p><a href="https://central.wordcamp.org/">WordCamps</a> are informal, community-organized events that are put together by a team of local WordPress users who have a passion for growing their communities. They are born out of active WordPress meetup groups that meet regularly and are able to host an annual WordCamp event. This has worked very well in many communities, with over 120 WordCamps being hosted around the world in 2017.<br /></p>\n\n<p>Sometimes though, passionate and enthusiastic community members can’t pull together enough people in their community to make a WordCamp happen. To address this, we introduced <a href="https://wordpress.org/news/2016/02/experiment-wordcamp-incubator/">the WordCamp Incubator program</a> in 2016.<br /></p>\n\n<p>The goal of the incubator program is <strong>to help spread WordPress to underserved areas by providing more significant organizing support for their first WordCamp event.</strong> In 2016, members of <a href="https://make.wordpress.org/community/">the global community team</a> worked with volunteers in three cities — Denpasar, Harare and Medellín — giving direct, hands-on assistance in making local WordCamps possible. All three of these WordCamp incubators <a href="https://make.wordpress.org/community/2017/06/30/wordcamp-incubator-report/">were a great success</a>, so we&#x27;re bringing the incubator program back for 2018.<br /></p>\n\n<p>Where should the next WordCamp incubators be? If you have always wanted a WordCamp in your city but haven’t been able to get a community started, this is a great opportunity. We will be taking applications for the next few weeks, then will get in touch with everyone who applied to discuss the possibilities. We will announce the chosen cities by the end of March.<br /></p>\n\n<p><strong>To apply, </strong><a href="https://wordcampcentral.polldaddy.com/s/wordcamp-incubator-program-2018-city-application"><strong>fill in the application</strong></a><strong> by March 15, 2018.</strong> You don’t need to have any specific information handy, it’s just a form to let us know you’re interested. You can apply to nominate your city even if you don’t want to be the main organizer, but for this to work well we will need local liaisons and volunteers, so please only nominate cities where you live or work so that we have at least one local connection to begin.<br /></p>\n\n<p>We&#x27;re looking forward to hearing from you!<br /></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, 21 Feb 2018 22:53: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: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: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:48:"HeroPress: How To Build A Company With WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2465";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:120:"https://heropress.com/essays/build-company-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=build-company-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:16946:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/02/022118-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: If you keep showing up, you\'d be surprised what happens." />.embed-container { position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; max-width: 100%; } .embed-container iframe, .embed-container object, .embed-container embed { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }\n<div class="embed-container"></div>\n<p>&nbsp;</p>\n<h4>Full text of the above video</h4>\n<p>Hey, y&#8217;all! Thanks for inviting me to come share my story on HeroPress. I&#8217;m so excited to be able to talk a little bit to the HeroPress community.</p>\n<p>So, and I&#8217;m doing a video blog or vlog because this is what I do; I&#8217;m a YouTube person. I create YouTube videos every single Wednesday for what I call WordPress Wednesday to help you improve your online marketing inside of the WordPress world. So I&#8217;m used to doing videos, and I asked if I could do my HeroPress story in this format; and they said go for it, so I&#8217;m excited to talk to you at least in a face-to-face scenario.</p>\n<p>I&#8217;m going to  share a little bit of my story and tell you how WordPress basically became my avenue for becoming a millionaire in just five short years.</p>\n<h3>The Beginning</h3>\n<p>So in 1998, I created my very first ever HTML website. My dad was actually doing websites at the time, and I needed a website for my band because that&#8217;s what I wanted to be is a rockstar; so I learned how to build a website, kind of, under his training and a little bit of self-taught stuff and had a lot of fun doing it that way in 1998.</p>\n<p>And then in 2005, I started hearing about WordPress; but in 2008, as I was freelancing around, a client asked me to build him a website. And they said, &#8220;hey, Kori, can you, can you build me a website, but we absolutely have to have it on WordPress?&#8221; I was like, sure, no problem; straight to Google, &#8220;how do you build a WordPress website&#8221;, you know. And over the weekend I pretty much taught myself how to build out a WordPress website, and I loved it.</p>\n<p>My mind was absolutely blown when I saw the drag and drop options inside of menus to create dropdowns, and a form builder; I was just blown away. So those of you who have struggled in the HTML CSS world, you know the magic or the majesty, if you will even, of WordPress and those environments and how easy it makes it. So when I saw that, I really just thought, oh my goodness, this is a full-circle moment for me.</p>\n<blockquote><p>I really want to use WordPress now from here on forward.</p></blockquote>\n<p>So I reached back out to my dad and said, &#8220;hey, dad, you know, this is a tool that our customers, all of our clients, have been asking us for&#8221;. They&#8217;ve been wanting access to their websites, and we&#8217;ve not been able to give it to them because, in the past, they had to download Dreamweaver, you know, Photoshop and an FTP program; and that was just too much nerd code for them. So we wanted to be able to give them something like this, and WordPress definitely was that solution.</p>\n<p>So he and I worked back and forth for a few years learning, really truly learning, WordPress; and then in 2012, we decided to launch together, my mom, my dad and I, decided to launch WebTegrity in San Antonio, Texas. And it was a very small concept initially; you know, we just me, literally, the three of us, and me and my folks. And then we hired on a subcontractor who is a great graphic designer here in town to try to help us with the creative side of things, and we started to grow our team.</p>\n<h3>Going Big Time</h3>\n<p>So how did we, in five years, build it up in such a way that we were able to sell it for a deal of a million dollars&#8217; worth of shares, which ultimately is a $20 million value deal? How did we do that? I&#8217;m going to give you a little bit of insight on how we were able to accomplish that in such a short time.</p>\n<p>So the very first thing I want you to realize is we did this in a saturated industry in San Antonio, Texas. When I did a search for web developer or web design firms back in 2012, I had over 700 results of different either freelancers or agencies or ad agencies or some solution out there that was either in the general area, or in the nearby area, that provided that service. So how did we, in six years, end up becoming number six in the entire city? We ranked in the top 10; how did we do that?</p>\n<blockquote><p>One of the very first things we did, was we niched ourselves; and, thankfully, WordPress was that solution.</p></blockquote>\n<p>In 2012, there was not an agency directly in San Antonio that was trying to be the go-to place for WordPress; and we purposely started stepping up and saying we are WordPress only, WordPress only, WordPress only. So if you were looking for a different type of CMS solution, we were not the right fit for you. And very, very quickly, we also started teaching it in the city; so we would teach other agencies. We provided on-site training; we provided weekend workshops. All for a price tag, of course; but that was one of our revenue streams. And, again, it set us as the authority in the city for WordPress; so really important that you understand how to niche yourselves and not try to be all things to all people.</p>\n<blockquote><p>The second thing we tried to do was really build a culture.</p></blockquote>\n<p>And you can see, I don&#8217;t work around boring walls. Everything that I do has to have creative juices flowing around me, right. We just want to create a great culture, a great environment. So we had to hire the right people. So that&#8217;s my next tip to you is be very, very careful on who you allow into your culture of your business, who you hire on, and certainly who you bring on as a leader in your culture in your community. So one of the things that we did right away was realize that we can&#8217;t teach passion, so you gotta find people that have a passion to nerd out on stuff like this.</p>\n<p>And you have to find people who have great integrity to just do their best at all times, and you have to find people who love to be creative and love to solve problems for clients, right, who aren&#8217;t just salespeople, right? So if you can find those things, you can teach nerd code all day long; so be sure to just find people with the right hearts to join your community and then train them up the right way, be sure that you just grow and grow and grow your culture in a healthy way, right.</p>\n<blockquote><p>And another thing that we did, so this is another tip, was understand how to really build a revenue stream that was going to be sustainable.</p></blockquote>\n<p>All right, so wrap your heads around this one because this one&#8217;s key. Very early on in our model as we were selling WordPress websites, part of my pitch was, oh, it&#8217;s just five grand and no more after that. It&#8217;s a one-time fee and you&#8217;re done. That&#8217;s a horrible business strategy. We learned very early on, inside of WordPress world, that you have rain or shine, right; so there&#8217;s a lot of clients coming or there are no clients.</p>\n<p>You&#8217;re either slammed working from home even in the evening trying to catch up, or you&#8217;re out on the golf course wondering if you&#8217;re going to get a paycheck next week. It&#8217;s really rain or shine. So how do you create a sustainable model in your business, in your small agency, in your startup; how do you do that, so that when those slow seasons come, you can still pay your team members, you can still keep your lights on?</p>\n<p>Well, we were sitting at a WordCamp; and Jason Cohen from WP Engine was keynoting; and one of the things he said right away is, if you don&#8217;t understand how to create a reoccurring revenue stream in your small agency, you will turn your sign to closed in the next year or two. And he was so right; and it was such a light bulb moment for me that I went back straightaway from that weekend WordCamp up in Austin and I started writing out, okay, how can we create a reoccurring revenue stream? What would that look like inside of our industry?</p>\n<p>And, of course, it was support packages. We didn&#8217;t call them maintenance plans. We certainly didn&#8217;t use retainer, which can have a sense of a negative connotation, right, because of lawyers; sorry! But, still, we didn&#8217;t want to use those words because we&#8217;re already almost creating a, uh, I don&#8217;t think I want to sign up for that type of attitude.</p>\n<p>What we did is we called it support, and very easily, clients were signing up saying, oh, goodness, yes, I need that ongoing support. So use that phrasing, create a model structure where it&#8217;s required, at least for the first 12 months out of the gate as they launch that you are charging them something even as small as $99 a month. And don&#8217;t shortchange yourself on that; put together a great package that you give them that type of value.</p>\n<p>If you were to check out WebTegrity.com, you would see our support plans and what they consist of and the pricing. We&#8217;re very transparent with that. That&#8217;s the way our revenue stream almost doubled our sales in one year and allowed us to keep our lights on when June and July roll around and nobody cares about their websites because they&#8217;re on the beach.</p>\n<blockquote><p>All right, reputation was another huge part of it.</p></blockquote>\n<p>That&#8217;s one of the reasons why we named ourselves WebTegrity, but reputation, understanding that that every client that signs up, whether they&#8217;re a $5,000 website or a $50,000 website gets the same type of boutique-style, white glove, handholding relationship, right? Every single project that you launch, you want to produce the absolute, absolute best. You&#8217;re not shortchanging them; you&#8217;re not, you&#8217;re not wiring something that you hand off to the client and hope to God it doesn&#8217;t break. You really are trying to find the absolute best solution.</p>\n<p>One of the things that also kept us in high standing with our reputation, of course, was offering that training because what we don&#8217;t want to do is keep the veil covered where nobody can see what we&#8217;re doing, right. We really want to be transparent and train our clients the nerd lingo, train the clients what SEO is and what expectations should be. Having that type of open communication really just started to build together a relationship with our clients that they trusted us; and we met their expectation, right. So be sure to hold strongly to your core values for your reputation. Be sure that you&#8217;re asking people to give you great reviews because that&#8217;ll make a difference.</p>\n<blockquote><p>And the last thing I want to talk about is give back.</p></blockquote>\n<p>So at one of the WordCamp US&#8217;s that I went to, Matt himself said, listen, if you&#8217;re making a living with WordPress, you really need to try to figure out how to give back 5% of your time, just 5% of your time a week. How can you do that to give back to the community? Can you start a meet-up group, teach a meetup group; can you facilitate a meetup group where maybe you&#8217;re just the organizer and you never have to speak because you&#8217;re not a fan of speaking?</p>\n<p>Can you organize a WordCamp, volunteer at a WordCamp? Can you write a tutorial and tell people how to do things? Can you teach a workshop; can you make a video?</p>\n<p>And, again, I had a light bulb moment. Of course, I can make videos. So my giveback to the WordPress community is my YouTube channel; every single Wednesday, I&#8217;m creating a video and putting it out there for free to the WordPress world of how to improve your online marketing. That&#8217;s made a huge impact not only, thankfully, inside the WordPress community, but also in my own business model.</p>\n<p>I actually go into WordCamps around the US and people are like, hey, aren&#8217;t you that WordPress girl; don&#8217;t you do videos? It&#8217;s a really cool feeling to be able to give back to the community because I&#8217;ve made my living using WordPress.</p>\n<h3>Understanding</h3>\n<p>So ultimately how did I turn five years into a multi-million dollar buyout? Because we have just recently sold; how did we do that? Ultimately, it was understanding that you have to be able to grow something of value. So as soon as you start your business, you should also be thinking about your exit strategy, right, even in how you name your company.</p>\n<p>If I were to name this Ashton Agency, do you think that I could&#8217;ve just walked away and handed the keys to somebody else named Johnson; it wouldn&#8217;t have worked. Think even about your name; will it stand alone? Can that become a brand that you can hand off and sell as a holistic entity?</p>\n<p>You also want to think about that revenue stream, right, and watch those sales margins. Be sure that your margins are healthy. Don&#8217;t hire until it hurts, until it absolutely hurts. Be sure that you&#8217;re structuring your offerings in such a way that you&#8217;re actually recouping your value. What does that mean? Just understand business better; watch Shark Tank, read more tutorials like this, watch more videos.</p>\n<p>Get a hold of the WordPress community, the core leaders, the speakers that travel around to all the WordCamps. Start following them on Twitter and trying to understand what it is that they&#8217;re training and teaching. There&#8217;s a lot of resources out there for you to gain some ideas from, but ultimately it was me stepping out in the San Antonio community because it was a larger firm here in San Antonio who purchased us.</p>\n<p>So we just kept hammering on the fact that we were the go-to place here in San Antonio for WordPress. We kept training; we kept doing free opportunities, going out and speaking at different events; and people kept seeing us. We kept showing up, so you&#8217;d be surprised what happens. If you keep giving back and you keep showing up to places, you keep establishing yourself as the authority, you keep learning and training and growing your own skill set and growing your team, before you know it, it can happen for you.</p>\n<p>I hope this has been helpful. If you have questions about some of this though, if you&#8217;re trying to grow up your startup, or if you&#8217;re trying to learn how to improve your revenue margins, I&#8217;m always open to a quick twitter conversation or send me an email. I&#8217;d love to connect with you.</p>\n<p>Thanks again for the opportunity to share this on HeroPress.</p>\n<p>Bye, y&#8217;all; catch me over on YouTube. Bye!</p>\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: How To Build A Company With WordPress" class="rtsocial-twitter-button" href="https://twitter.com/share?text=How%20To%20Build%20A%20Company%20With%20WordPress&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbuild-company-wordpress%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: How To Build A Company With WordPress" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fbuild-company-wordpress%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%2Fessays%2Fbuild-company-wordpress%2F&title=How+To+Build+A+Company+With+WordPress" rel="nofollow" target="_blank" title="Share: How To Build A Company With WordPress"></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/essays/build-company-wordpress/&media=https://heropress.com/wp-content/uploads/2018/02/022118-150x150.jpg&description=How To Build A Company With WordPress" rel="nofollow" target="_blank" title="Pin: How To Build A Company With WordPress"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/build-company-wordpress/" title="How To Build A Company With WordPress"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/build-company-wordpress/">How To Build A Company With WordPress</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, 21 Feb 2018 14:00:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Kori Ashton";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:26:"Matt: Commuting Time Saved";s:7:"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=47970";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:43:"https://ma.tt/2018/02/commuting-time-saved/";s: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:344:"<p>On <a href="https://automattic.com/">Automattic&#x27;s</a> internal <a href="https://buddypress.org/">BuddyPress</a>-powered company directory, we allow people to fill out a field saying how far their previous daily commute was. 509 people have filled that out so far, and they are saving 12,324 kilometers of travel every work day. Wow!</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, 19 Feb 2018 18:14:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:71:"Akismet: Version 4.0.3 of the Akismet WordPress Plugin Is Now Available";s:7:"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:"http://blog.akismet.com/?p=1985";s:7:"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:99:"https://blog.akismet.com/2018/02/19/version-4-0-3-of-the-akismet-wordpress-plugin-is-now-available/";s: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:867:"<p>Version 4.0.3 of <a href="http://wordpress.org/plugins/akismet/">the Akismet plugin for WordPress</a> is now available.</p>\n<p>4.0.3 contains a few helpful changes:</p>\n<ul>\n<li>Adds a new scheduled task to clear out old Akismet entries in the <code>wp_commentmeta</code> table that no longer have corresponding comments in <code>wp_comments</code>.  This should help reduce Akismet&#8217;s database usage for some users.</li>\n<li>Adds a new <code>akismet_batch_delete_count</code> action so developers can optionally take action when Akismet comment data is cleaned up.</li>\n</ul>\n<p>To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in <a href="http://wordpress.org/plugins/akismet/">the WordPress plugins directory</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, 19 Feb 2018 15:58: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:10:"Josh Smith";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:68:"Mark Jaquith: Handling old WordPress and PHP versions in your plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:40:"http://markjaquith.wordpress.com/?p=5544";s:7:"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:100:"https://markjaquith.wordpress.com/2018/02/19/handling-old-wordpress-and-php-versions-in-your-plugin/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3563:"<p>New versions of WordPress are released about three times a year, and WordPress itself supports PHP versions all the way back to 5.2.4.</p>\n<p>What does this mean for you as a plugin developer?</p>\n<p>Honestly, many plugin developers spend too much time supporting old versions of WordPress and <strong>really</strong> old versions of PHP.</p>\n<p>It doesn&#8217;t have to be this way. You don&#8217;t need to support every version of WordPress, and you don&#8217;t have to support every version of PHP. Feel free to do this for seemingly selfish reasons. Supporting old versions is hard. You have to &#8220;unlearn&#8221; new WordPress and PHP features and use their older equivalents, or even have code branches that do version/feature checks. It increases your development and testing time. It increases your support burden.</p>\n<p>Economics might force your hand here&#8230; a bit. You can&#8217;t very well, even in 2018, require that everyone be running PHP 7.1 and the latest version of WordPress. But consider the following:</p>\n<p>97% of WordPress installs are running PHP 5.3 or higher. This gives you namespaces, late static binding, closures, Nowdoc, <strong>__DIR</strong><strong>__</strong>, and more.</p>\n<p>88% of WordPress installs are running PHP 5.4 or higher. This gives you short array syntax, traits, function-array dereferencing, guaranteed <strong>&lt;?=</strong> echo syntax availability, <strong>$this</strong> access in closures, and more.</p>\n<p>You get even more things with PHP 5.5 and 5.6 (64% of installs are running 5.6 or higher), but a lot of the syntactic goodness came in 5.3 and 5.4, with very few people running versions less than 5.4. So stop typing <strong>array()</strong>, stop writing named function handlers for simple <strong>array_map()</strong> uses, and start using namespaces to organize and simplify your code.</p>\n<p>Okay, so&#8230; how?</p>\n<p>I recommend that your main plugin file just be a simple bootstrapper, where you define your autoloader, do a few checks, and then call a method that initializes your plugin code. I also recommend that this main plugin file be PHP 5.2 compatible. This should be easy to do (just be careful not to use <strong>__DIR__</strong>).</p>\n<p>In this file, you should check the minimum PHP and WordPress versions that you are going to support. And if the minimums are not reached, have the plugin:</p>\n<ol>\n<li>Not initialize (you don&#8217;t want syntax errors).</li>\n<li>Display an admin notice saying which minimum version was not met.</li>\n<li>Deactivate itself (optional).</li>\n</ol>\n<p>Do not <strong>die()</strong> or <strong>wp_die()</strong>. That&#8217;s &#8220;rude&#8221;, and a bad user experience. Your goal here is for them to update WordPress or ask their host to move them off an ancient version of PHP, so be kind.</p>\n<p>Here is what I use:</p>\n<p><a href="https://gist.github.com/markjaquith/a08623974b37c2cf0207ee2b120b54da">View code on GitHub</a></p>\n<p></p>\n<p><a href="https://twitter.com/markjaquith/status/965605448408813569">Reach out on Twitter</a> and let me know what methods you use to manage PHP and WordPress versions in your plugin!</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s: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, 19 Feb 2018 15:14: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:"Mark Jaquith";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:20;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:85:"Post Status: How WebDevStudios is serving different market segments — Draft podcast";s:7:"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=43724";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:85:"https://poststatus.com/webdevstudios-serving-different-market-segments-draft-podcast/";s: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:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.</p>\n<p>In this episode, Lisa Sabin-Wilson shares about the entangled history of WebDevStudios and eWebscapes and how she and team are targeting every level of the market. WebDevStudios focuses heavily on the upper and enterprise market segments, providing a high degree of attention and support to those clients.</p>\n<p>Sometime in 2017 Lisa did the math on all the lower-end projects that they were referring away and realized that WDS had a prime opportunity to re-introduce her former web studio, eWebscapes, as a way to serve these smaller-scope projects. This rebirth, so to speak, has positioned them to better target local communities, provide staff with more variety of work, and bring simplified processes alongside those they use for larger projects.</p>\n<p></p>\n<h3></h3>\n<h3>Key take-aways</h3>\n<ul>\n<li>Lisa observed a market opportunity and did the math first</li>\n<li>Relaunching started with a solid content strategy</li>\n<li>Simplified processes for managing a project</li>\n<li>Utilized talent already on staff</li>\n<li>Lots of opportunity to target local communities</li>\n<li>Evaluating the success of this strategy after 6 months</li>\n</ul>\n<h3>Links</h3>\n<ul>\n<li><a href="https://webdevstudios.com/">WebDevStudios</a></li>\n<li><a href="https://ewebscapes.com/">eWebscapes</a></li>\n<li><a href="https://jenniferbourn.com/profitable-project-plan/">Profitable Project Plan</a></li>\n<li><a href="https://twitter.com/@lisasabinwilson">Lisa Sabin-Wilson on Twitter</a></li>\n</ul>\n<p><a href="https://webdevstudios.com/about/"><em>Photo Credit</em></a></p>\n<h3>Sponsor: Prospress</h3>\n<p><a href="https://prospress.com/">Prospress</a> makes the WooCommerce Subscriptions plugin, that enables you to turn your online business into a recurring revenue business. Whether you want to ship a box or setup digital subscriptions like I have on Post Status, Prospress has you covered. Check out <a href="https://prospress.com/">Prospress.com</a> for more, and thanks to Prospress 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:"Fri, 16 Feb 2018 22:38:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Katie Richards";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:25:"Matt: No Office Workstyle";s:7:"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=47949";s:7:"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/2018/02/no-office-workstyle/";s: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:3938:"<p>Reed Albergotti has a great article titled <a href="https://www.theinformation.com/articles/latest-amenity-for-startups-no-office">Latest Amenity for Startups: No Office</a>. You can put in your email to read I believe but it&#x27;s behind a paywall otherwise. <a href="https://www.theinformation.com/">The Information</a> is a pretty excellent site that alongside (former Automattician) <a href="https://stratechery.com/">Ben Thompson&#x27;s Stratechery</a> I recommend subscribing to. Here are some quotes from the parts of the article that quote me or talk about <a href="https://automattic.com/">Automattic</a>:</p>\n\n<blockquote class="wp-block-quote">\n    <p>So it’s no coincidence that one of the first companies to operate with a distributed workforce has roots in the open source movement. Automattic, the company behind open source software tools like WordPress, was founded in 2005 and has always allowed its employees to work from anywhere. The company’s 680 employees are based in 63 countries and speak 79 languages. Last year, it closed its San Francisco office, a converted warehouse — because so few employees were using it. It still has a few coworking spaces scattered around the globe.</p>\n    <p>Matt Mullenweg, Automattic’s founder and CEO, said that when the company first started, its employees communicated via IRC, an early form of instant messaging. Now it uses a whole host of software that’s tailor-made for remote work, and as the technology evolves, Automattic adopts what they need.</p>\n    <p>Mr. Mullenweg said Automattic only started having regular meetings, for instance, after it started using Zoom, a video conferencing tool that works even on slow internet connections.</p>\n    <p>He’s become a proponent of office-less companies and shares what he’s learned with other founders who are attempting it. Mr. Mullenweg said he believes the distributed approach has led to employees who are even more loyal to the company and that his employees especially appreciate that they don’t need to spend a chunk of their day on a commute.</p>\n    <p>“Our retention is off the charts,” he said.</p>\n</blockquote>\n\n<p>And:</p>\n\n<blockquote class="wp-block-quote">\n    <p>“Where it goes wrong is if they don’t have a strong network outside of work—they can become isolated and fall into bad habits,” Mr. Mullenweg said. He said he encourages employees to join groups, play sports and have friends outside of work. That kind of thing wouldn’t be a risk at big tech companies, where employees are encouraged to socialize and spend a lot of time with colleagues.</p>\n    <p>But for those who ask him about the negatives, Mr. Mullenweg offers anecdotal proof of a workaround.</p>\n    <p>For example, he said he has 14 employees in Seattle who wanted to beat the isolation by meeting up for work once a week. So they found a local bar that didn’t open until 5 p.m., pooled together the $250 per month co-working stipends that Automattic provides and convinced the bar’s owner to let them rent out the place every Friday.</p>\n</blockquote>\n\n<p>They didn&#x27;t need to pool all their co-working allowance to get the bar, I recall it was pretty cheap! Finally:</p>\n\n<blockquote class="wp-block-quote">\n    <p>For Automattic, flying 700 employees to places like Whistler, British Columbia or Orlando, Florida, has turned into a seven-figure expense.</p>\n    <p>“I used to joke that we save it on office space and blow it on travel. But the reality is that in-person is really important. That’s a worthwhile investment,” Mr. Mullenweg said.It might take a while, but some people are convinced that a distributed workforce is the way of the future.</p>\n    <p>“Facebook is never going to work like this. Google is never going to work like this. But whatever replaces them will look more like a distributed company than a centralized one,” Mr. Mullenweg said.</p>\n</blockquote>";s: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, 16 Feb 2018 18:44:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:29:"Matt: Kinsey Joins Automattic";s:7:"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=47931";s:7:"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:46:"https://ma.tt/2018/02/kinsey-joins-automattic/";s: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:229:"<p>Kinsey Wilson is joining Automattic to run WordPress.com. <a href="https://www.poynter.org/news/one-time-npr-and-nyt-digital-chief-new-adventure-wordpress">Poynter covers the news and has a great interview with Kinsey.</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, 15 Feb 2018 18:56:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:93:"WPTavern: WPWeekly Episode 305 – 10up, JavaScript for WordPress Conference, and Jetpack 5.8";s:7:"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:58:"https://wptavern.com?p=78136&preview=true&preview_id=78136";s:7:"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/wpweekly-episode-305-10up-javascript-for-wordpress-conference-and-jetpack-5-8";s: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:1599:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I discuss the news of the week. We also chat about the Winter Olympics, crypto mining in order to access content on the web, and the joys of taking care of a puppy. Last but not least, we talk about Elasticsearch in Jetpack 5.8 and whether or not improving WordPress&#8217; native search functionality through a service is the way to go.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://wptavern.com/jetpack-5-8-adds-lazy-loading-for-images-module">Jetpack 5.8 Adds Lazy Loading for Images Module</a><br />\n<a href="https://wptavern.com/free-virtual-wordpress-for-javascript-conference-june-29th">Free Virtual WordPress for JavaScript Conference June 29th</a><br />\n<a href="https://wptavern.com/10up-turns-seven">10up Turns Seven</a><br />\n<a href="https://make.wordpress.org/plugins/2018/02/13/not-updated-in-warning/">“Not Updated In …” Warning</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, February 21st 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #305:</strong><br />\n</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, 15 Feb 2018 02:14:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:26:"WPTavern: 10up Turns Seven";s:7:"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=78132";s:7:"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:37:"https://wptavern.com/10up-turns-seven";s: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:2986:"<p><a href="https://10up.com/">10up</a>, a web development agency founded by Jake Goldman in 2011, has turned seven years old. In a <a href="https://10up.com/blog/2018/10up-seven-year-anniversary/">blog post celebrating the occasion</a>, Goldman reviews the previous year and highlights some notable events for the company.</p>\n<p>&#8220;We welcomed more than 30 new clients to our portfolio in another record sales year,&#8221; Goldman said. &#8220;We launched new websites along with web and mobile apps for major brands across verticals as diverse as finance, healthcare, academia, high-tech, big media, consumer packaged goods, food and beverage, and fitness… to name a few.&#8221;</p>\n<p>He also highlighted the company&#8217;s commitment to open source and giving back to WordPress. Throughout the past year, the company has released a number of WordPress plugins and developer tools including, <a href="https://10up.com/blog/2017/distributor-plugin/">Distributor</a>, <a href="https://10up.com/blog/2017/wp-snapshots-share-wordpress-setup/">WP Snapshots</a>, <a href="https://10up.com/blog/2017/wp-docker/">WP Local Docker</a>, <a href="https://10up.com/blog/2018/improving-wordpress-transients/">Async Transients</a>, and more.</p>\n<p>Goldman describes three trends he&#8217;s noticed in the past few years.</p>\n<ol>\n<li>Integrations with innovation happening in other projects and platforms has become increasingly important as the web matures. You see it in React.js and Vue.js emerging as popular front end standards, in the rise of Elasticsearch and NoSQL platforms, with two factor authentication and Google single sign on, with the rise of modern Asset Management Systems.</li>\n<li>For publishers, it’s increasingly becoming about distribution to multiple platforms, more so than<em> just</em> building a website. Google AMP, Facebook Articles, Apple News, Alexa, YouTube channels to name a few.</li>\n<li>If you need any more evidence of WordPress dominance, look no further than how highly in demand top-tier engineering talent is. It’s probably &#8211; literally &#8211; around a factor of 1.5x &#8211; 2x what great engineers were earning 3-4 years ago.</li>\n</ol>\n<p>With seven years of experience under his belt, Goldman offers the following advice for those who are in their first or second year of running an agency or in a leadership position.</p>\n<ol>\n<li> Don’t be quite so hard on yourself &#8211; when you run a business &#8211; when you’re a lease &#8211; there will always be highs and lows &#8211; don’t dwell on the lows.</li>\n<li>Put more emphasis on building systems, routines, and check-ins that offer a better pulse on the collective and individual fulfillment, engagement, and health of the team, rather than relying on transparent upwards communication.</li>\n</ol>\n<p>Congrats to 10up on seven years in business. To learn more about the company and employment opportunities, visit their <a href="https://10up.com/">official site</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, 14 Feb 2018 19:16:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:37:"HeroPress: My WordPress Anniversaries";s:7:"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=2452";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:126:"https://heropress.com/essays/my-wordpress-anniversaries/#utm_source=rss&utm_medium=rss&utm_campaign=my-wordpress-anniversaries";s: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:13243:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/02/021418-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: I feel that I am responsible to be on stage for all the women who haven’t found the courage yet to share their stories." /><p>I never remember dates. I know the birthday of more or less five people. I insist on saying that my son was born on May 11. Incorrect, I was born on May 11, he on May 17. But for some reason, my WordPress dates are permanently etched into my brain. I think it’s because meeting the global WordPress community and helping restart the Italian community are very meaningful moments in my adult life. Please join me in a walk down memory lane <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f642.png" alt="🙂" class="wp-smiley" /></p>\n<h3>May 15, 2015</h3>\n<p>I started building websites with WordPress in 2010: my first website was my own blog, whose only purpose was to publish photos of my son so all the grandparents could enjoy seeing him grow. I enjoyed tinkering around with it, and to my surprise someone wrote asking me to build something similar for them. And they wanted to pay me for it!</p>\n<p>For a few years I worked as an administrative manager during the day and as a web designer at night until I decided to make the jump and become a freelancer.</p>\n<p>I never thought about contributing to WordPress because I wasn’t a back end developer and I didn’t think the project needed people that were not code wizards. Heck, I didn’t even know how WordPress was made or how open source worked exactly!</p>\n<blockquote><p>And then I went to a Freelancers conference in Italy and on May 15 I gave my first talk ever.</p></blockquote>\n<p>Up until that moment I taught small classes, but I never talked in front of more than ten people. I was terrified: in the audience there were more than a hundred people. Some of my friends, but also a lot of seasoned professionals that I respected and admired, and here I was talking about how they should and shouldn’t build a website. I was so nervous, when I grabbed the mic I did such a wide gesture with my arms that the bracelet I was wearing flew through the air to the other side of the room.</p>\n<p>After my talk a guy came to compliment my talk, and I realised that he was one of those people that I respected and admired from afar: <a href="https://twitter.com/lucasartoni">Luca Sartoni</a>, an Automattician whose blog I have been following for a while.</p>\n<p>For the three days of the event we kept chatting about websites, WordPress, entrepreneurship, open source until he convinced me to start a WordPress meetup in my hometown of Torino, Italy. He put me in contact with other people that he knew wanted to do something similar and in less than a month from that conversation we started a meetup. The group now has more than one thousand members, and in March we will celebrate thirty events.</p>\n<h3>November 7, 2015</h3>\n<p>Luca didn’t stop his proselytism in Torino <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f642.png" alt="🙂" class="wp-smiley" /> That same year, WordCamp Europe was held in Seville and at the Polyglots table a revolution was started. A small group of Italians, used to travelling abroad to attend WordCamps, met there and decided that it was time to organise the Italian community.</p>\n<p>The first step was to revive the blog on the Italian WordPress website: it was dormant for seven years and the first thing we did was publish the dates of meetups that were slowly but surely appearing in the whole country. At the beginning of 2015 there were two meetups in Italy, by August there were eight and their number kept growing.</p>\n<p>Now, if you have met Italians, you know we talk a lot. The two Francescos from Apulia, <a href="https://twitter.com/franzvitulli">Franz Vitulli</a> and <a href="https://twitter.com/fra83">Francesco Di Candia</a>, took the second initiative that was crucial to bringing us together: they opened a Slack workspace for the Italians, modeled after the UK workspace. For the whole summer we chatted every single day: about WordPress, about how to grow and manage the community that was forming in front of our eyes, how to communicate, how to contribute.</p>\n<p>And then chatting wasn’t enough, we wanted to meet in person. We wanted to put a face and a voice to the avatars. With the help of <a href="https://twitter.com/rosso">Sara Rosso</a> and <a href="https://twitter.com/miss_jwo">Jenny Wong</a> we carried out a bizarre plan, almost unheard of: a <a href="https://wordpress.tv/2017/12/10/francesca-marano-standalone-contributor-days-help-make-wordpress-with-your-community/">stand alone WordPress Contributor Day</a>. We would meet in Milano for a day to get to know each other and to learn how to Contribute to WordPress.</p>\n<blockquote><p>I like to think that November 7 2015 is the day we became a community: we were not an abstract idea anymore, we were people, meeting in person to make WordPress in Italy.</p></blockquote>\n<p>&nbsp;</p>\n<h3>April 10, 2016</h3>\n<p>The next few months went by in a blur of activities: the meetup organisers in Torino applied to host the first WordCamp in Italy in three years and I lead the organising team, I applied to attend the Community Summit in Philadelphia and I got accepted, I attended the first WordCamp US, my first WordCamp, and volunteered at it. I met a lot of people that helped me become more active and more focused: as a new contributor it’s easy to get overwhelmed by the abundance of amazing projects and tasks you can be part of, but it’s important to keep your focus to be more effective.</p>\n<blockquote><p>After meeting people from all over the world and sharing our experiences I realised the story of the Italian community could be inspiring for other communities and it was worth telling it to a wider audience, so I got completely out of my comfort zone and submitted a talk to WordCamp London.</p></blockquote>\n<p>On April 10th 2016 I gave <a href="https://wordpress.tv/2016/05/30/francesca-marano-rebirth-italian-community/">my first talk at a WordCamp</a> and my first talk in English. I think I didn’t sleep for days before and after the event. It was nerve wracking, but I did it without throwing any bracelet in the air this time.</p>\n<a href="https://heropress.com/wp-content/uploads/2018/02/WCEU2016.jpg"><img class="wp-image-2457 size-large" src="https://heropress.com/wp-content/uploads/2018/02/WCEU2016-1024x684.jpg" alt="" width="960" height="641" /></a>I gave the same talk at WordCamp Europe in 2016 and realised the story was relatable to many communities. Photographer unknown, sorry <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f641.png" alt="🙁" class="wp-smiley" />\n<h3>September 17, 2017</h3>\n<p>Over the following year I kept contributing to WordPress, mostly in the Community team. I participated in the Polyglots activities for a while but then I had to pick and focus my attention. The more I interacted with people from all over the world as a hobby, the more I wanted that to become my job. Although my business as a web designer in Italy was doing good, I felt I wanted to be able to reach more people and find a way to be more involved with the community.<br />\nSo I started looking for a job. I was hesitant at first: all the insecurities I had about myself came back to haunt me. The voice in my head was telling me: you are too old, you don’t have enough technical expertise, you have been contributing for a very short time, English is not your native language, you are a single mom from Italy for crying out loud, who would want to employ you?</p>\n<blockquote><p>Well, it turns out that if you actually look for a job instead of just telling yourself that you really would like a job, chances are you might get one.</p></blockquote>\n<p>Last September I started a new chapter in my career as the <a href="https://www.siteground.com/blog/francesca-marano/">WordPress Community Manager</a> at SiteGround and I couldn’t be happier.</p>\n<p>The past 33 months have completely changed my life, personally and professionally: along the way I learned a number of lessons that I know will stay with me forever.</p>\n<h3>Step Up</h3>\n<p>If you want to achieve something, start today. Just start. Start a meetup, leave a comment to encourage someone else, volunteer to take notes of a meeting, participate in the discussion, bring your own ideas to the table. Be a fire starter, for yourself and for the people around you.</p>\n<h3>Step Back</h3>\n<p>None of the above is about you: the community is bigger than you, you are here to build a path for the future. Once you started something, don’t become too attached, let it go and let other people step up and shine. Mentor them, if they ask and if you can.</p>\n<h3>If you want to go faster go alone, if you want to go further go together</h3>\n<p>I am not a huge fan of motivational quotes, but this one is very dear to my heart and it’s one I have to remind myself quite often. I am a perfectionist and a quick learner: this is ok when you start your own business (and it’s ok only at the beginning, but this is a topic for another article!), but when you are part of a team, you are part of something bigger. It might move slower, but its impact is immensely more powerful than anything you’ll be able to achieve on your own.</p>\n<h3>Representation matters</h3>\n<p>I dislike speaking in public. When I say this people tend to laugh it off because I am good on stage. It doesn’t mean that I like it. I am much more at ease when I am behind the scenes, making things happen.</p>\n<p><img class="aligncenter wp-image-2454 size-full" src="https://heropress.com/wp-content/uploads/2018/02/slack-imgs.jpg" alt="Four women seated on a low wall at a WordPress meetup." width="600" height="400" /></p>\n<blockquote><p>But representation matters: I feel that I am responsible to be on stage for all the women who haven’t found the courage yet to share their stories.</p></blockquote>\n<p>I am responsible for the young ones, so they can see that it’s possible to create a life when you can be both a good, albeit a bit absent mom, and a kick ass professional. I am responsible for the older ones, so they can see that we are represented, that this industry accepts us and recognizes our contributions. I am responsible to show my eleven year old son that women can do whatever they set out to do.</p>\n<h3>Make it better, give it back</h3>\n<p>I wish I came up with this, because it’s an incredibly powerful sentence. <a href="https://heropress.com/essays/make-better-give-back/">John did</a> and I am grateful every day that I get to share my life with him and his wisdom.</p>\n<p>Contributing to open source can be very frustrating: things go slow, sometimes things don’t go at all (there are numerous tickets in the WordPress bug tracker that are five or more years old), sometimes you might disagree with that will be decided, sometimes you might work alongside people that you dislike.</p>\n<p>When this happens, remind yourself that you are working on a brilliant piece of software that is helping the lives and the businesses of millions of people.</p>\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: My WordPress Anniversaries" class="rtsocial-twitter-button" href="https://twitter.com/share?text=My%20WordPress%20Anniversaries&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fmy-wordpress-anniversaries%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: My WordPress Anniversaries" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fmy-wordpress-anniversaries%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%2Fessays%2Fmy-wordpress-anniversaries%2F&title=My+WordPress+Anniversaries" rel="nofollow" target="_blank" title="Share: My WordPress Anniversaries"></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/essays/my-wordpress-anniversaries/&media=https://heropress.com/wp-content/uploads/2018/02/021418-150x150.jpg&description=My WordPress Anniversaries" rel="nofollow" target="_blank" title="Pin: My WordPress Anniversaries"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/my-wordpress-anniversaries/" title="My WordPress Anniversaries"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/my-wordpress-anniversaries/">My WordPress Anniversaries</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, 14 Feb 2018 07:00:49 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Francesca Marano";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:68:"WPTavern: Free Virtual WordPress for JavaScript Conference June 29th";s:7:"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=78116";s:7:"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/free-virtual-wordpress-for-javascript-conference-june-29th";s: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:1714:"<p>Zac Gordon, who <a href="https://wptavern.com/zac-gordon-launches-gutenberg-development-course-includes-more-than-30-videos">launched his Gutenberg development course</a> earlier this year, is organizing a virtual conference called <a href="https://javascriptforwp.com/conference/">JavaScript for WordPress.</a> The conference will take place June 29th and is free to watch.</p>\n<p>&#8220;Making the event free and online was really important for me so we could have as few barriers to entry for folks wanting to learn,&#8221; Gordon said. &#8220;I have a feeling a lot of folks who can&#8217;t tune live will still appreciate having all the talks available on YouTube for free.&#8221;</p>\n<p>So far, 15 speakers have been confirmed with more to be announced soon. The speakers include WordPress core developers, theme and plugin developers, agency owners, and educators. Some of the talks will be from designers allowing user experience and usability to be part of the conversation.</p>\n<p>Gordon says he&#8217;s been wanting to an in-person event for a while but considering the challenges involved, a virtual conference was the next best thing.</p>\n<p>&#8220;I used to run in-person workshops in the Washington DC area, which I miss, and have wanted to do an event for a while,&#8221; he said. &#8220;But doing in-person events is so difficult, so the online format seemed like the best option to go with. I got some good advice from Human Made and WP Campus, who both have experience doing online events, so hopefully everything will go smooth.&#8221;</p>\n<p>To reserve a seat and receive updates, visit the <a href="https://javascriptforwp.com/conference/">JavaScript for WordPress conference site</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, 13 Feb 2018 01:30: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:13:"Jeff Chandler";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:51:"Mark Jaquith: Updating plugins using Git and WP-CLI";s:7:"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:40:"http://markjaquith.wordpress.com/?p=5552";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:83:"https://markjaquith.wordpress.com/2018/02/12/updating-plugins-using-git-and-wp-cli/";s: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:4007:"<p>Now that you know <a href="https://markjaquith.wordpress.com/2018/01/30/simple-wordpress-deploys-using-git/">how I deploy WordPress sites</a> and <a href="https://markjaquith.wordpress.com/2018/02/05/tips-for-configuring-wordpress-environments/">how I configure WordPress environments</a>, what about the maintenance of keeping a WordPress site&#8217;s plugins up-to-date?</p>\n<p>Since I&#8217;m using Git, I cannot use WordPress built-in plugin updater on the live site (and I wouldn&#8217;t want to — if a plugin update goes wrong, my live site could be in trouble!)</p>\n<p>The simple way to update all your plugins from a staging or local development site is to use WP-CLI:</p>\n<pre class="brush: bash; title: ; notranslate">wp plugin update-all\ngit commit -am \'update all plugins\' wp-content/plugins</pre>\n<p>That works. I used to do that.</p>\n<p>I don&#8217;t do that anymore.</p>\n<p>Why? <strong>Granularity</strong>.</p>\n<p>One of the benefits of using version control like Git is that when things go wrong, you can pinpoint when they went wrong, and identify what code caused the issue.</p>\n<p>Git has a great tool called <strong>bisect</strong> that takes a known good state in the past and a current broken state, and then jumps around between revisions, efficiently, asking you to report whether that revision is <strong>good</strong> or <strong>bad</strong>. Then it tells you what revision broke your site.</p>\n<p>If you lump all your plugin updates into one commit, you won&#8217;t get that granularity. You&#8217;ll likely get the <strong>git bisect</strong> result of &#8220;great&#8230; one of EIGHTEEN PLUGINS I updated was the issue&#8221;. That doesn&#8217;t help.</p>\n<p>Here&#8217;s how you do it with granularity:</p>\n<pre class="brush: bash; title: ; notranslate">for plugin in $(wp plugin list --update=available --field=name);\ndo\n    wp plugin update $plugin &amp;&amp;\n    git add -A wp-content/plugins/$plugin &amp;&amp;\n    git commit -m \'update $plugin plugin\'\ndone;</pre>\n<p>This code loops through plugins with updates available, updates each one, and commits it with a message that references the plugin being updated. Great! Now <strong>git bisect</strong> will be able to tell you <strong>which</strong> plugin update broke your site.</p>\n<p>And what if you can only run WP-CLI commands from within a VM, and Git commands from your local machine? For instance, if you&#8217;re using my favorite tool, <a href="https://local.getflywheel.com/">Local by Flywheel</a>, you have to SSH into the site&#8217;s container to issue WP-CLI commands, but from within that container, you might not have Git configured like it is on your host machine.</p>\n<p>So what you can do is break the process into two steps.</p>\n<p>On the VM, run this:</p>\n<pre class="brush: bash; title: ; notranslate">wp plugin list --update=available --field=name &gt; plugins.txt\nwp plugin update-all</pre>\n<p>That grabs a list of plugins with updates and writes them to a file <strong>plugins.txt</strong>, and then updates all the plugins.</p>\n<p>And then on your local machine, run this:</p>\n<pre class="brush: bash; title: ; notranslate">while read plugin;\ndo\n    git add -A wp-content/plugins/$plugin &amp;&amp;\n    git commit -m \'update $plugin plugin\'\ndone; &lt; plugins.txt</pre>\n<p>That slurps in that list of updated plugins and does a distinct <strong>git add</strong> and <strong>git commit</strong> for each.</p>\n<p>When that&#8217;s done, remove <b>plugins.txt</b>.</p>\n<p>All your plugins are quickly updated with WP-CLI, but you get nice granular Git commits and messages.</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s: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, 12 Feb 2018 14:42: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:12:"Mark Jaquith";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:79:"Post Status: WordPress market opportunities: Upmarket edition — Draft podcast";s:7:"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=42360";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:85:"https://poststatus.com/wordpress-market-opportunities-upmarket-edition-draft-podcast/";s: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:2284:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.</p>\n<p>In this episode, Brian and Brian continue their discussion on WordPress market opportunities with a focus on the upper-market and enterprise clients. They take a look at discovery projects, pitching WordPress against competing platforms, and considerations to make before pitching on these high-budget projects. There are plenty of positives and negatives when working on long-term projects that may have a dramatic impact on your company in many ways.</p>\n<p>In addition to these market opportunities, the boys also discuss recent news including iThemes acquisition by Liquid Web, a welcome change to the WordPress.org plugin directory, and an unfortunate and far-reaching bug that shipped with the 4.9.3 release last week.</p>\n<p></p>\n<h3>Links</h3>\n<ul>\n<li><a href="https://poststatus.com/liquid-web-acquired-ithemes/">Liquid Web acquires iThemes</a></li>\n<li><a href="https://generatewp.com/new-policy-changes-wordpress-plugin-directory/">Plugin directory notice changes</a></li>\n<li><a href="https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/">4.9.4 technical details</a></li>\n<li><a href="https://wpsessions.com/sessions/infusing-websites-brand-voice/">Infusing Websites with Brand Voice</a><a href="https://wpsessions.com/teams">WPS Team Training</a></li>\n</ul>\n<h3>Sponsor: WooCommerce</h3>\n<p><a href="https://woocommerce.com/">WooCommerce</a> makes the most customizable eCommerce software on the planet, and it’s the most popular too. You can build just about anything with WooCommerce. <a href="https://woocommerce.com/">Try it today</a>, and thanks to the team at WooCommerce 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:"Fri, 09 Feb 2018 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:"Katie Richards";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:57:"WPTavern: Jetpack 5.8 Adds Lazy Loading for Images Module";s:7:"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=78112";s:7:"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:68:"https://wptavern.com/jetpack-5-8-adds-lazy-loading-for-images-module";s: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:2079:"<p>Jetpack 5.8 <a href="https://jetpack.com/2018/02/06/jetpack-5-8-release/">is available</a> for download and includes a handful of new features for Professional, Premium, and Personal plan users. In <a href="https://wptavern.com/jetpack-5-4-introduces-beta-version-of-new-search-module-powered-by-elasticsearch-for-professional-plan-users">October of last year</a>, Jetpack 5.4 began beta testing a new <a href="https://jetpack.com/support/search/">search module</a> based on <a href="https://www.elastic.co/">Elasticsearch</a>. Jetpack 5.8 concludes the beta and the new search service is available to Professional plan customers.</p>\n<p>The new search module replaces the native search functionality in WordPress and Jetpack developers claim sites with a large amount of content, images, or products will see significant speed improvements and more relevant results. Developers can fine-tune the user experience by using custom queries and template tags. Users can sort results by categories, tags, month/year, post type, or any taxonomy.</p>\n<p>In addition to the Content Delivery Network, users have another method to optimize their sites with a new module named Lazy Load Images. When activated, Jetpack will display a page&#8217;s textual content first. When a user scrolls down the page, Jetpack will request and download images so they appear when that section of the page comes into view. Sites with a large amount of images will benefit most from having this module activated.</p>\n<p>Premium plan customers can now perform security scans on their sites at any time, upload an unlimited amount of videos, and access SEO tools that were once restricted to Business plan customers.</p>\n<p>Other notable improvements include:</p>\n<ul>\n<li>Support for timezone and site language settings</li>\n<li>Improved display of notices</li>\n<li>The GettyImages shortcode now uses the new format required by GettyImages</li>\n</ul>\n<p>To view all of the additions in this release, check out the <a href="https://wordpress.org/plugins/jetpack/#developers">Jetpack 5.8 changelog</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, 09 Feb 2018 07:54:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:15:"Matt: The Laity";s:7:"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=47918";s:7:"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:32:"https://ma.tt/2018/02/the-laity/";s: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:310:"<blockquote class="wp-block-quote">\n    <p>In the last analysis, every profession is a conspiracy against the laity.</p><cite>The Sir Patrick Cullen character in George Bernard Shaw’s play <a href="https://en.m.wikipedia.org/wiki/The_Doctor%27s_Dilemma_(play)">The Doctor’s Dilemma</a></cite></blockquote>";s: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, 08 Feb 2018 21:48:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:86:"WPTavern: WPWeekly Episode 304 – DesktopServer, Life, and Health with Marc Benzakein";s:7:"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:58:"https://wptavern.com?p=78105&preview=true&preview_id=78105";s:7:"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:91:"https://wptavern.com/wpweekly-episode-304-desktopserver-life-and-health-with-marc-benzakein";s: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:1931:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I are joined by <a href="https://twitter.com/MarcBenzak">Marc Benzakein</a>, Operations Manager for ServerPress, LLC. We discussed recent updates to DesktopServer and received a progress report on 4.0. Marc also shared some of the struggles the team encountered throughout 2017.</p>\n<p>We learned what&#8217;s new with <a href="https://wpsitesync.com/">WP SiteSync</a> and what customers can look forward too later this year. We also talked about <a href="https://wordpress.tv/2017/12/08/marc-benzakein-fat-happy-and-fifty/">Marc&#8217;s journey</a> of becoming a healthier person both physically and mentally. He recalls the issues he had to overcome and shares advice on how others can improve their health.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://wptavern.com/woocommerce-3-3-1-released-addresses-template-conflicts">WooCommerce 3.3.1 Released, Addresses Template Conflicts</a><br />\n<a href="https://wptavern.com/wordpress-4-9-4-fixes-critical-auto-update-bug-in-4-9-3">WordPress 4.9.4 Fixes Critical Auto Update Bug in 4.9.3</a><br />\n<a href="https://thehackernews.com/2018/02/wordpress-dos-exploit.html">Unpatched DoS Flaw Could Help Anyone Take Down WordPress Websites</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, February 14th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #304:</strong><br />\n</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, 08 Feb 2018 01:48:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:55:"HeroPress: Becoming a Better Designer Through WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2441";s:7:"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:142:"https://heropress.com/essays/becoming-better-designer-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=becoming-better-designer-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:19189:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/02/020718-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: The connections I\'ve made, the skills I\'ve honed, and the mentorship I\'ve received have all contributed to making me the designer I am today." /><h3>The early years</h3>\n<p>I’ve always been an art kid. One of my first school memories is of drawing a clown and my art teacher being so enamored with it, she hung it up on her door for the whole year.</p>\n<p>The first time in my educational life I didn’t take an art class was my first year of college. By the end of the year, my fingers were itching and I was ready to scream — I had to take art. It didn’t take long for me to declare a Studio Art minor, which eventually became an Arts and Technology minor my senior year.</p>\n<p>I’ve also always been an internet kid. We received our first internet-connected Windows desktop in 1997. I’ll never forget the sound of dial-up as I signed into AOL, day after day for years to come. When my older brother started working for an ISP, we were able to go beyond just using AOL to connect, and I started spending more time exploring websites (rather than just AOL’s apps and chat rooms). I wanted to be like my older brother and learn how to make sites. I taught myself basic HTML by using View Source on existing sites — even back then, I was benefiting from the open web!</p>\n<p>Angelfire was my earliest web canvas. A couple of my friends eventually got into making websites, but I was always a little disdainful of them for using Homestead’s GUI builder, while I was making my sites from scratch. I had a blast making image-rich personal and fan sites with tables and HTML styles. Landing a copy of Photoshop Elements in high school only intensified my enjoyment of web design. I kept that passion up through college, when I found my first design gig.</p>\n<p><a href="https://heropress.com/wp-content/uploads/2018/02/old_web_site.jpg"><img class="size-large wp-image-2442 aligncenter" src="https://heropress.com/wp-content/uploads/2018/02/old_web_site-1024x479.jpg" alt="Old Website, best viewed on AOL" width="960" height="449" /></a></p>\n<h3>Could this be a career?</h3>\n<p>My first year of college got off to a bit of a rough financial start. By the time my financial aid was finalized and I was finally able to pick a work study job, my options were pretty limited. A dance professor needed an assistant to help her with some photocopying and organization tasks, along with helping her build out a print and web portfolio.</p>\n<p>I was honestly a terrible assistant, but I did a pretty good job with the design work. I continued to refine my skills working in the computers labs in subsequent years, and in my Junior year of college (ten years ago!) I landed an internship at a local web design agency. That internship turned into a part-time job, which opened up doors to more local web design opportunities, and soon I was graduating college and pretty well situated into the start of my career.</p>\n<p><a href="https://heropress.com/wp-content/uploads/2018/02/early-site.jpg"><img class="aligncenter size-large wp-image-2443" src="https://heropress.com/wp-content/uploads/2018/02/early-site-1024x666.jpg" alt="Skeumorphic website design that looks like a notepad with pen ink all over it." width="960" height="624" /></a></p>\n<p>It was at these agencies that I started learning how to build WordPress websites. I’d used WordPress a couple times in college and felt comfortable with it, but now I was focusing a lot more on building my skills as a designer and front-end developer. My girlfriend (who was working at the same web agency) and I managed to convince our boss to start letting us create totally custom websites, rather than customizing existing themes, and that opened up a whole new world of design opportunities.</p>\n<h3>My first WordCamp</h3>\n<p>It was around then that my girlfriend, who attended WordCamp NYC the previous year, noticed the conference organizers were <a href="https://2010.nyc.wordcamp.org/volunteer-designer-needed/">looking for some volunteer designers</a> to help create some graphics. She passed along the information, and I got in touch.</p>\n<p>I collaborated with a few other designers to create the WordCamp branding, which was used across the website, t-shirt, signage, and stickers:</p>\n<p><a href="https://heropress.com/wp-content/uploads/2018/02/wcnyc.png"><img class="aligncenter size-full wp-image-2444" src="https://heropress.com/wp-content/uploads/2018/02/wcnyc.png" alt="WCNYC Banner" width="429" height="286" /></a></p>\n<p>It was amazing to see it everywhere at the WordCamp. It felt really special. Though I didn’t get “props” for this, I still consider it my first contribution to WordPress.</p>\n<p>WordCamp NYC was a ton of fun. I met interesting people, learned a lot about WordPress, and started to get a feel for the community. I left with a desire to get more involved. I browsed through WordPress.org, stumbling upon the “Make” section. I was stoked to see that there was a design group. I couldn’t write much code beyond CSS, but I could contribute my design skills. I joined a couple of the core channels on IRC, including the design channel (#wordpress-ui), and observed for while. I watched how the other designers in the project communicated, what they worked on, where they presented their work, etc. By observing before participating, I could learn the social queues and mores of the community. I didn’t want to embarass myself — I wanted to do things the established way based on community standards.</p>\n<p>What I found to be one of the most difficult parts of contributing was adapting to the technology used to build WordPress. I had to learn how to use command line and SVN. Getting set up in SVN and terminal was probably the biggest thing that stopped me from contributing code during my early years.</p>\n<p>But most of all, it came down to conquering fear. Fear that my design skills would be unwanted and unwelcome; fear that other contributors would look down on me or ignore me, or that they’d find me irritating; fear that I just wasn’t good enough to contribute. Some of this fear persists today, albeit greatly reduced.</p>\n<p>There’s a point at which I managed to conquer a little bit of that fear, stop observing, and really start to pitch in. Slowly, I started chiming in and volunteering for design tasks in IRC and the Make Design p2. I ended up doing a lot of small projects on the community side (rather than the core side) at first — some new landing pages and redesigns of sections on WordPress.org, graphics, and design for my own local meetups. I started feeling more and more confident with my contributions.</p>\n<h3>Core Props</h3>\n<p>By this point, I had done some wireframes and mockups for the core WordPress software — I’d even spoken at a WordCamp! — but I hadn’t actually gotten any code committed. Which meant, at this point in time, I didn’t have any “core props.” I was still really intimidated by Trac and SVN. I was a designer, and most design conversations happened in explicitly design space. But I really wanted to get some code committed into core, so I needed to find a CSS bug I felt qualified to fix.</p>\n<p>At WordCamp Philly in 2012, I finally got a chance. Sunday was devoted to contributing to WordPress. There were experienced core contributors present who could teach people how to make a patch, how to submit a ticket, and suggest tickets for people to work on.</p>\n<p>Aaron Jorbin, a core contributor and fellow speaker (and, now a friend), found a CSS issue I could work on: bringing the alternate “blue” color scheme into sync with the default “grey” scheme. He helped me get set up, helped me through saving my changes as a patch, and then helped me submit that patch to Trac. Andy Nacin, another core contributor (and future friend!) subsequently committed that patch, and I received my first core props.</p>\n<p><a href="https://heropress.com/wp-content/uploads/2018/02/first-props2.png"><img class="aligncenter size-large wp-image-2445" src="https://heropress.com/wp-content/uploads/2018/02/first-props2-1024x370.png" alt="Screenshot of ticket giving Mel props" width="960" height="347" /></a></p>\n<p>After creating my first patch, contributing became easier and easier. My confidence grew, and I spent more time participating in IRC, p2s, and Trac discussions. Then, in January of 2013, major design changes started coming to WordPress.</p>\n<h3>My WordPress apprenticeship</h3>\n<p>It started with icons.</p>\n<p>Ben Dunkle, WordPress’s official icon designer, proposed some shiny new icons for the WordPress dashboard. They were “flat” — one color, not a ton of details. The icons were awesome, but they didn’t really fit stylistically with the rest of the admin. The flat styles clashed with WordPress’ heavy use of gradients.</p>\n<p>So, I helped imagine what the admin could look like totally flat. We tried out a couple ideas, got them committed, and refined in code. The stark styles looked really fresh after years of gradients!</p>\n<p>Unfortunately, flattening the admin unearthed a whole lot of other issues. There wasn’t enough time to flesh out the new design before the next version of WordPress launched, so the flat styles got reverted and tabled for another time.</p>\n<p>Pretty soon after, I received an email via my site’s contact form:</p>\n<p><em><strong>Name</strong>: Matt</em><br />\n<em><strong> Comment</strong>: Add me on Skype when you get a chance.</em></p>\n<p>I think my heart stopped when I realized I had been emailed by the co-founder of WordPress, Matt Mullenweg. Matt invited me to come join a group that would take a broader look at redesigning the admin (codenamed “MP6”). It meant a lot for someone as important as Matt to recognize my skills. I spent a lot of my early years as a designer plagued with self-doubt, and suddenly I had someone pointing at me, going “I believe in you!”</p>\n<p>I leapt at the chance.</p>\n<p>Our group worked together on Skype. We quickly scoped the goal of MP6 to only update CSS and a little bit of JS. I helped Ben make some new vector icons, gave feedback and critiqued design proposals, and made some design proposals of my own. It was an intimate group where we all felt free to safely share and critique each other’s work. The mentorship I received from more experienced WordPress designers was invaluable to my growth. Working with these veterans of WordPress really helped me to grow into my fledgling wings.</p>\n<p><a href="https://make.wordpress.org/core/2013/10/23/mp6-3-8-proposal/">WordPress 3.8 shipped with the updated admin interface</a>, and I knew it was time to take my design career to a new level.</p>\n<p><a href="https://heropress.com/wp-content/uploads/2018/02/4-8-credits-smaller.jpg"><img class="aligncenter size-large wp-image-2446" src="https://heropress.com/wp-content/uploads/2018/02/4-8-credits-smaller-1024x895.jpg" alt="WordPress 4.8 Credits" width="960" height="839" /></a></p>\n<h3>Leaving the nest</h3>\n<p>I’d had my eye on Automattic, the makers of WordPress.com, the Jetpack plugin, and many other products, for most of my time contributing to WordPress. A couple of the designers I worked with on MP6 were Automattic designers, and it was an absolute joy to collaborate with them. At this point I’d spent so much of my career as either a lone designer, or in a competitive environment, that having a supportive, collaborative group of people helping me improve my work was a revelation.</p>\n<p>I desperately wanted to work at Automattic.</p>\n<p>While MP6 was in the works, I participated in a three month long design apprenticeship at a local agency. I worked alongside experienced mentors and fellow apprentices to hone my interface and user experience design skills. It was challenging and thrilling and totally complemented the mentorship I was receiving from WordPress folks. Plus, working in a positive environment reinforced my desire to work somewhere similar.</p>\n<p>After the apprenticeship, I finally felt like I had the skills and confidence to apply. I spent a lot of time writing my cover letter, and redesigning my portfolio to use in-depth case studies on a small number of recent projects. I finally sent off my application and crossed my fingers.</p>\n<p>A couple weeks later, I received a reply back asking to schedule an interview. I was terrified, but luckily, Automattic conducts interviews via text, so I was able to hide my fear behind my keyboard and hopefully try to project confidence. (Aside: I also show all my emotions on my face, so online communication is the best.)</p>\n<p>It must have worked, because I was moved on to the next phase of the application, doing a self-contained trial project, which was a whole ton of fun. I was able to put my recently refined research, interviewing, and user testing skills to use. I loved being given a real challenge to tackle. My trial went well, so I was moved along to the final interview with Matt Mullenweg. We spent a couple hours chatting on Skype, and at the end of our conversation I was given an offer. Welcome to Automattic!</p>\n<p>After working so hard on my apprenticeship, and on MP6, joining Automattic felt incredibly validating. The work I put in, the mentorship I received, all of the collaboration, led to this moment. I felt like I had graduated from apprentice and was now embarking on my adventure as a design journeyman. And boy, has it been an adventure!</p>\n<h3><a href="https://heropress.com/wp-content/uploads/2018/02/automattic-2-smaller.jpg"><img class="aligncenter size-large wp-image-2447" src="https://heropress.com/wp-content/uploads/2018/02/automattic-2-smaller-1024x678.jpg" alt="Automattic Group Photo" width="960" height="636" /></a></h3>\n<h3>Design leadership</h3>\n<p>The past four and a half years at Automattic have been fantastic. I have the best coworkers anyone can ask for. I’ve worked with some incredibly talented and empathetic designers, whose guidance and feedback constantly encourage me to improve my skills.</p>\n<p>I’ve continued to contribute to WordPress, slowly gaining more responsibility in the project the longer I stuck around. That’s the secret to becoming an open source leader, I discovered — <strong>decisions are made by the people who show up</strong>.</p>\n<p>In 2016, I was asked to by the Release Design Lead for <a href="https://wordpress.org/news/2016/04/coleman/">WordPress 4.5 “Coleman.”</a> I worked alongside the other release leads to make design-related decisions that impacted the release. This was the first release we experimented with having a Design Lead. I felt like design finally had a seat at the table.</p>\n<p>This continued to be the case last year, when Matt Mullenweg announced core focuses for the year: Editing, Customization, and the API. Both Editing and Customization had designers co-leading their focus. I was named the Customization co-lead. I’d been working on customization and site building on WordPress.com for over a year, so I had relevant experience.</p>\n<p>I worked with my developer co-lead, Weston Ruter, on low-hanging fruit, most of which we released in WordPress 4.8. The release was smaller, focused more on improvements than new features. We made a lot of updates to widgets, which had been long neglected.</p>\n<p>After that, we turned our sights to some more ambitious projects: drafting and scheduling changes in the Customizer, improvements to code editing in the WordPress admin, even more widget updates, and upgrades around the flow of changing themes and building menus for your site. We took a design-first approach to building out these new features, and I think it really shows in the work that we produced during the 4.9 release cycle, which Weston and I co-led.</p>\n<p><a href="https://wordpress.org/news/2017/11/tipton/">WordPress 4.9 “Tipton”</a> launched in November. Since then, I’ve pivoted to work on <a href="https://wordpress.org/gutenberg/">Gutenberg</a>, the new editing experience for WordPress which should be released in 5.0. Once the editing experience wraps up, we’re going to start looking at how we can extend Gutenberg to cover site building and customization. It’s a big, audacious goal that I hope to pursue with caution, humility, and a spirit of adventure.</p>\n<p>I owe WordPress a great deal. The connections I’ve made, the skills I’ve honed, and the mentorship I’ve received have all contributed to making me the designer I am today. I hope to give back for years to come!</p>\n<p><a href="https://heropress.com/wp-content/uploads/2018/02/community-summit-smaller.jpg"><img class="aligncenter size-full wp-image-2448" src="https://heropress.com/wp-content/uploads/2018/02/community-summit-smaller.jpg" alt="Community Summit Group Photo" width="960" height="556" /></a></p>\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: Becoming a Better Designer Through WordPress" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Becoming%20a%20Better%20Designer%20Through%20WordPress&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbecoming-better-designer-wordpress%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Becoming a Better Designer Through WordPress" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fbecoming-better-designer-wordpress%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%2Fessays%2Fbecoming-better-designer-wordpress%2F&title=Becoming+a+Better+Designer+Through+WordPress" rel="nofollow" target="_blank" title="Share: Becoming a Better Designer Through WordPress"></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/essays/becoming-better-designer-wordpress/&media=https://heropress.com/wp-content/uploads/2018/02/020718-150x150.jpg&description=Becoming a Better Designer Through WordPress" rel="nofollow" target="_blank" title="Pin: Becoming a Better Designer Through WordPress"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/becoming-better-designer-wordpress/" title="Becoming a Better Designer Through WordPress"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/becoming-better-designer-wordpress/">Becoming a Better Designer Through WordPress</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, 07 Feb 2018 12:00:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Mel Choyce";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:66:"WPTavern: WooCommerce 3.3.1 Released, Addresses Template Conflicts";s:7:"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=78089";s:7:"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/woocommerce-3-3-1-released-addresses-template-conflicts";s: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:1330:"<p>WooCommerce 3.3.1 <a href="https://woocommerce.wordpress.com/2018/02/06/woocommerce-3-3-1-fix-release-notes/">is available</a> and fixes template conflicts discovered in a handful of WordPress themes that forced the team to <a href="https://wptavern.com/woocommerce-3-3-removed-from-plugin-directory-due-to-theme-conflicts">revert WooCommerce 3.3</a>. The team reviewed handful of the most common themes running WooCommerce and tested them for compatibility with 3.3.1.</p>\n<p><a href="https://github.com/woocommerce/woocommerce/wiki/Template-File-Guidelines-for-Devs-and-Theme-Authors#hook-vs-override---when-to-use-what">WooCommerce developers recommend</a> that theme authors use hooks instead of template overrides to ensure maximum compatibility.</p>\n<p>According to Mike Jolley, WooCommerce lead developer, this release highlighted issues with the template system&#8217;s extensibility and a disconnect between theme authors on external marketplaces. &#8220;We hope to find solutions to these problems in the near future,&#8221; Jolley said.</p>\n<p>WooCommerce 3.3.1 has at least <a href="https://github.com/woocommerce/woocommerce/compare/3.3.0...3.3.1">90 commits</a>. Users are encouraged to create a full-backup of their sites and then browse to Dashboard &gt; Updates to update WooCommerce from within WordPress.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 07 Feb 2018 09:46: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:13:"Jeff Chandler";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:65:"WPTavern: WordPress 4.9.4 Fixes Critical Auto Update Bug in 4.9.3";s:7:"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=78087";s:7:"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/wordpress-4-9-4-fixes-critical-auto-update-bug-in-4-9-3";s: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:1984:"<p>Hours after <a href="https://wptavern.com/wordpress-4-9-3-released-fixes-34-bugs">WordPress 4.9.3 was released</a>, the WordPress development team followed it up <a href="https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/">with 4.9.4</a> to fix a critical bug with the auto update process. The bug generates a fatal PHP error when WordPress attempts to update itself.</p>\n<p>This error requires WordPress site owners and administrators to manually update to WordPress 4.9.4 by visiting your Dashboard and clicking the Update Now button on the Updates page. Alternatively, you can update by uploading the files via SFTP or by using WP-CLI.</p>\n<p>Dion Hulse, WordPress lead developer, says managed hosts that apply updates automatically for their customers will be able to update sites as they normally do. This may explain why some users have reported that sites running 4.9.3 have automatically updated to 4.9.4 without issue.</p>\n<p>The bug stems from an attempt to <a href="https://core.trac.wordpress.org/ticket/43103">reduce the number of API calls</a> made when the auto update cron job is run. Unfortunately, the code committed had unintended consequences. &#8220;It triggers a fatal error as not all of the dependencies of <code>find_core_auto_update()</code> are met,&#8221; Hulse said.</p>\n<p>A postmortem will be published once the team determines how to prevent this mistake from happening in the future. &#8220;We don’t like bugs in WordPress any more than you do, and we’ll be taking steps to both increase automated coverage of our updates and improve tools to aid in the detection of similar bugs before they become an issue in the future,&#8221; Hulse said.</p>\n<p>While WordPress 4.9.3 and 4.9.4 do not include any security fixes, it&#8217;s important to note that in order to receive automatic security updates in the future, sites using the 4.9 branch must be running at least 4.9.4. Older branches are unaffected.</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, 07 Feb 2018 09:19:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:45:"Dev Blog: WordPress 4.9.4 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=5559";s:7:"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/2018/02/wordpress-4-9-4-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:1814:"<p>WordPress 4.9.4 is now available.</p>\n<p>This maintenance release fixes a severe bug in 4.9.3, which will cause sites that support automatic background updates to fail to update automatically, and will require action from you (or your host) for it to be updated to 4.9.4.</p>\n<p>Four years ago with <a href="https://wordpress.org/news/2013/10/basie/">WordPress 3.7 &#8220;Basie&#8221;</a>, we added the ability for WordPress to self-update, keeping your website secure and bug-free, even when you weren&#8217;t available to do it yourself. For four years it&#8217;s helped keep millions of installs updated with very few issues over that time. Unfortunately <a href="https://wordpress.org/news/2018/02/wordpress-4-9-3-maintenance-release/">yesterdays 4.9.3 release</a> contained a severe bug which was only discovered after release. The bug will cause WordPress to encounter an error when it attempts to update itself to WordPress 4.9.4, and will require an update to be performed through the WordPress dashboard or hosts update tools.</p>\n<p>WordPress managed hosting companies who install updates automatically for their customers can install the update as normal, and we&#8217;ll be working with other hosts to ensure that as many customers of theirs who can be automatically updated to WordPress 4.9.4 can be.</p>\n<p>For more technical details of the issue, we&#8217;ve <a href="https://make.wordpress.org/core/2018/02/06/wordpress-4-9-4-release-the-technical-details/">posted on our Core Development blog</a>. For a full list of changes, consult the <a href="https://core.trac.wordpress.org/query?status=closed&milestone=4.9.4&group=component">list of tickets</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.9.4</a> or visit Dashboard → Updates and click “Update Now.”</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, 06 Feb 2018 16:17:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Dion Hulse";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:49:"WPTavern: WordPress 4.9.3 Released, Fixes 34 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=78081";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wptavern.com/wordpress-4-9-3-released-fixes-34-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:681:"<p>WordPress 4.9.3 <a href="https://wordpress.org/news/2018/02/wordpress-4-9-3-maintenance-release/">is available</a> and fixes 34 bugs. Customizer changesets, the visual editor, widgets, and compatibility for PHP 7.2 highlight this release. You can view all of the changes via the <a href="https://core.trac.wordpress.org/log/branches/4.9?rev=42630&stop_rev=42521">changelog</a> or <a href="https://core.trac.wordpress.org/query?status=closed&milestone=4.9.3&group=component">trac tickets</a>. Most sites will update automatically. However, if you want to trigger the update ahead of time or manually update, visit your Dashboard, click the Updates link, and click Update Now.</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, 06 Feb 2018 08:35: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:13:"Jeff Chandler";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:66:"WPTavern: Liquid Web Acquires iThemes in Multi-Million Dollar Deal";s:7:"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=77907";s:7:"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/liquid-web-acquires-ithemes-in-multi-million-dollar-deal";s: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:4149:"<p>Liquid Web, a managed hosting service founded in 1997, <a href="https://www.liquidweb.com/blog/liquid-web-acquires-ithemes/">has acquired</a> <a href="https://ithemes.com/">iThemes</a>. iThemes recently <a href="https://ithemes.com/10-years-in-wordpress/">celebrated its 10th year</a> in business. <a href="https://poststatus.com/liquid-web-acquired-ithemes/">PostStatus reports</a> that it was an all cash deal and sources confirmed to the Tavern that it was a multi-million dollar acquisition.</p>\n<p>iThemes will continue to operate as an independent unit within Liquid Web. Cory Miller will remain as General Manager of iThemes and the company will keep its office and employees in Oklahoma City, OK.</p>\n<p>iThemes was founded in 2008 and is part of a group of WordPress focused companies that started <a href="https://medium.com/@jasonpatricksc/a-brief-history-of-a-wordpress-theme-business-3847e16fcba4">around the same time</a>. The group includes WooThemes, Revolution Themes now known as StudioPress, Press75, WPZoom, and others.</p>\n<p>WooThemes was <a href="https://wptavern.com/automattic-acquires-woocommerce">acquired by Automattic</a>. StudioPress has branched off into content marketing with CopyBlogger and hosting via StudioPress sites. Press75 was acquired by Westwerk in 2014 and WPZoom continues to operate independently.</p>\n<p>iThemes diversified its business a number of times over the years, adding plugins and services to its portfolio. Some of the most notable products include, FlexxTheme, BackupBuddy, Builder, iThemes Sync, and iThemes Security. In 2013, the company branched off into the e-commerce space <a href="https://wptavern.com/ithemes-launches-e-commerce-plugin-exchange">with Exchange</a>. In 2017, <a href="https://ithemes.com/2017/07/13/ithemes-exchange-new-home-exchangewpcom/">Exchange was acquired</a> by AJ Morris allowing the company to focus on iThemes Sales Accelerator, a new product that works exclusively with WooCommerce.</p>\n<p>Considering Liquid Web recently launched <a href="https://www.liquidweb.com/products/managed-woocommerce-hosting/">its managed WooCommerce hosting</a>, iThemes Sales Accelerator should pair nicely with its services.</p>\n<p>This isn&#8217;t the first time a large webhosting company has acquired a WordPress business. In the last two years, GoDaddy has acquired three companies with a presence in the WordPress ecosystem.</p>\n<ul>\n<li><strong>April 2013</strong> EIG Acquires MOJO-Themes</li>\n<li><strong>September 2016</strong> GoDaddy Acquires ManageWP</li>\n<li><strong>December 2016</strong> GoDaddy Acquires WP Curve</li>\n<li><strong>March 2017</strong> GoDaddy Acquires Sucuri</li>\n</ul>\n<h2>After 10 Years, Cory Miller Lets Go</h2>\n<p>Miller founded iThemes 10 years ago and helped navigate it through the ups and downs that come with running a business. Although Miller no longer owns the company he founded, he&#8217;s excited about the next chapter and the opportunities it presents to him and his team.</p>\n<p>&#8220;One of the keys that has contributed greatly to our success over the last 10 years is being willing to adapt and to innovate and to try new things,&#8221; Miller said. &#8220;For instance, If we’d kept focusing solely on WordPress themes, which was our primary business for the early years, we wouldn’t be around today.</p>\n<p>&#8220;As we surveyed the landscape in WordPress, one thing was very obvious to us: hosting is the future. As a bootstrapped company from the beginning, with our DNA as a software company, and seeing where Liquid Web is going, it just made sense for us to join forces.</p>\n<p>&#8220;We view this is as another chapter in our story of our willingness to adapt and try new things so we can keep doing what we do best — Make People’s Lives Awesome. So we&#8217;re tremendously excited about our future with Liquid Web, and what we’re going to be able to do for the WordPress community together.&#8221;</p>\n<p>Miller says they&#8217;re in the middle of the transition process and are working towards tighter integration between iThemes&#8217; products and Liquid Web&#8217;s managed hosting services.</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, 06 Feb 2018 00:33:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:45:"Dev Blog: WordPress 4.9.3 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=5545";s:7:"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/2018/02/wordpress-4-9-3-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:3408:"<p>WordPress 4.9.3 is now available.</p>\n<p>This maintenance release fixes 34 bugs in 4.9, including fixes for Customizer changesets, widgets, visual editor, and PHP 7.2 compatibility. For a full list of changes, consult the <a href="https://core.trac.wordpress.org/query?status=closed&milestone=4.9.3&group=component">list of tickets</a> and the <a href="https://core.trac.wordpress.org/log/branches/4.9?rev=42630&stop_rev=42521">changelog</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.9.3</a> or visit Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.</p>\n<p>Thank you to everyone who contributed to WordPress 4.9.3:</p>\n<p><a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/abdullahramzan/">abdullahramzan</a>, <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/andreiglingeanu/">andreiglingeanu</a>, <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/bpayton/">Brandon Payton</a>, <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a>, <a href="https://profiles.wordpress.org/coleh/">coleh</a>, <a href="https://profiles.wordpress.org/darko-a7/">Darko A7</a>, <a href="https://profiles.wordpress.org/desertsnowman/">David Cramer</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/flixos90/">Felix Arntz</a>, <a href="https://profiles.wordpress.org/frank-klein/">Frank Klein</a>, <a href="https://profiles.wordpress.org/pento/">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a>, <a href="https://profiles.wordpress.org/jbpaul17/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/lizkarkoski/">lizkarkoski</a>, <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/mattyrob/">mattyrob</a>, <a href="https://profiles.wordpress.org/monikarao/">Monika Rao</a>, <a href="https://profiles.wordpress.org/munyagu/">munyagu</a>, <a href="https://profiles.wordpress.org/ndavison/">ndavison</a>, <a href="https://profiles.wordpress.org/nickmomrik/">Nick Momrik</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a>, <a href="https://profiles.wordpress.org/rishishah/">rishishah</a>, <a href="https://profiles.wordpress.org/othellobloke/">Ryan Paul</a>, <a href="https://profiles.wordpress.org/sasiddiqui/">Sami Ahmed Siddiqui</a>, <a href="https://profiles.wordpress.org/sayedwp/">Sayed Taqui</a>, <a href="https://profiles.wordpress.org/seanchayes/">Sean Hayes</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/shooper/">Shawn Hooper</a>, <a href="https://profiles.wordpress.org/netweb/">Stephen Edgar</a>, <a href="https://profiles.wordpress.org/manikmist09/">Sultan Nasir Uddin</a>, <a href="https://profiles.wordpress.org/tigertech/">tigertech</a>, and <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</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, 05 Feb 2018 19:47:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Sergey Biryukov";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:57:"Mark Jaquith: Tips for configuring WordPress environments";s:7:"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:40:"http://markjaquith.wordpress.com/?p=5476";s:7:"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://markjaquith.wordpress.com/2018/02/05/tips-for-configuring-wordpress-environments/";s: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:4626:"<p>Many WordPress hosts will give your site a &#8220;staging&#8221; environment. You can also use tools like <a href="https://local.getflywheel.com/">Local by Flywheel</a>, or <a href="https://www.mamp.info/">MAMP Pro</a> to run a local &#8220;dev&#8221; version of your site. These are great ways of testing code changes, playing with new plugins, or making theme tweaks, without risking breaking your live &#8220;production&#8221; site.</p>\n<p>Here is my advice for working with different WordPress environments.</p>\n<h2>Handling Credentials</h2>\n<p>The live (&#8220;production&#8221;) version of your site should be opt-in. That is, your site&#8217;s Git repo should <strong>not</strong> store production credentials in <strong>wp-config.php</strong>. You don&#8217;t want something to happen like <a href="https://www.reddit.com/r/cscareerquestions/comments/6ez8ag/accidentally_destroyed_production_database_on/">when this developer accidentally connected to the production database</a> and destroyed all the company data on his first day.</p>\n<p>Instead of keeping database credentials in <strong>wp-config.php</strong>, have <strong>wp-config.php</strong> look for a <strong>local-config.php</strong> file. Replace the section that defines the database credentials with something like this:</p>\n<pre class="brush: php; title: ; notranslate">if ( file_exists( __DIR__ . \'/local-config.php\' ) ) {\n    include( __DIR__ . \'/local-config.php\' );\n} else {\n    die( \'local-config.php not found\' );\n}</pre>\n<p>Make sure you add <strong>local-config.php</strong> to your <strong>.gitignore</strong> so that no one commits their local version to the repo.</p>\n<p>On production, you&#8217;ll create a <strong>local-config.php</strong> with production credentials. On staging or development environments, you&#8217;ll create a <strong>local-config.php</strong> with the credentials for those environments.</p>\n<h2>Production is a Choice</h2>\n<p>Right after the section that calls out <strong>local-config.php</strong>, put something like this:</p>\n<pre class="brush: php; title: ; notranslate">if ( ! defined( \'WP_ENVIRONMENT\' ) ) {\n    define( \'WP_ENVIRONMENT\', \'development\' );\n}</pre>\n<p>The idea here is that there will always be a <strong>WP_ENVIRONMENT</strong> constant available to you that tells you what kind of environment your site is being run in. In production, you will put this in <strong>local-config.php</strong> along with the database credentials:</p>\n<pre class="brush: php; title: ; notranslate">define( \'WP_ENVIRONMENT\', \'production\' );</pre>\n<p>Now, in your theme, or your custom plugins, or other code, you can do things like this:</p>\n<pre class="brush: php; title: ; notranslate">if ( \'production\' === WP_ENVIRONMENT ) {\n    add_filter( \'option_gravityformsaddon_gravityformsstripe_settings\', function( $stripe_settings ) {\n        $stripe_settings[\'api_mode\'] = \'live\';\n        return $stripe_settings;\n    });\n} else {\n    add_filter( \'option_gravityformsaddon_gravityformsstripe_settings\', function( $stripe_settings ) {\n        $stripe_settings[\'api_mode\'] = \'test\';\n        return $stripe_settings;\n    });\n}</pre>\n<p>This bit of code is for the Easy Digital Downloads Stripe gateway plugin. It makes sure that on the production environment, the payment gateway is always in <strong>live</strong> mode, and the anywhere else, it is always in <strong>test</strong> mode. This protects against two very bad situations: connecting to live services from a test environment (which could result in customers being charged for test transactions) and connecting to test services from a live environment (which could prevent customers from purchasing products on your site).</p>\n<p>You can also use this pattern to do things like hide Google Analytics on your test sites, or make sure debug plugins are only active on development sites (more on that, in a future post!)</p>\n<p>Don&#8217;t rely on complicated procedures (&#8220;step 34: make sure you go into the Stripe settings and switch the site to test mode on your local test site&#8221;) — make these things explicit in code. Make it impossible to screw it up, and working on your sites will become faster and less stressful.</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s: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, 05 Feb 2018 14:59:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Mark Jaquith";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:40:"Matt: National Magazine Award Nomination";s:7:"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=47900";s:7:"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://ma.tt/2018/02/national-magazine-award-nomination/";s: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:761:"<p>Longreads <a href="http://www.magazine.org/asme/about-asme/pressroom/asme-press-releases/ellies-2018-finalists-announced">was nominated today</a> for its first-ever <a href="https://en.wikipedia.org/wiki/National_Magazine_Awards">National Magazine Award</a>, in the category of columns and commentary, alongside ESPN The Magazine, BuzzFeed News, Pitchfork, and New York magazine. Laurie Penny&#x27;s Longreads columns <a href="https://longreads.com/tag/metoo-and-consent/">explore important questions of consent and female desire</a> that have strongly resonated in our current moment. In addition to this nomination, Penny&#x27;s columns have been translated and republished in Italian and German newspapers, and will be collected in a forthcoming book.</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, 02 Feb 2018 21:37:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:46:"Dev Blog: The Month in WordPress: January 2018";s:7:"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=5541";s:7:"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/2018/02/the-month-in-wordpress-january-2018/";s: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:3839:"<p>Things got off to a gradual start in 2018 with momentum starting to pick up over the course of the month. There were some notable developments in January, including a new point release and work being done on other important areas of the WordPress project.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>WordPress 4.9.2 Security and Maintenance Release</h2>\n\n<p>On January 16, <a href="https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/">WordPress 4.9.2 was released</a> to fix an important security issue with the media player, as well as a number of other smaller bugs. This release goes a long way to smoothing out the 4.9 release cycle with the next point release, v4.9.3, <a href="https://make.wordpress.org/core/2018/01/31/wordpress-4-9-3-release-pushed-to-february-5th/">due in early February</a>.</p>\n\n<p>To get involved in building WordPress Core, jump into the #core channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>, and follow<a href="https://make.wordpress.org/core/"> the Core team blog</a>.</p>\n\n<h2>Updated Plugin Directory Guidelines</h2>\n\n<p>At the end of 2017, <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/">the guidelines for the Plugin Directory</a> received a significant update to make them clearer and expanded to address certain situations. This does not necessarily make these guidelines complete, but rather more user-friendly and practical; they govern how developers build plugins for the Plugin Directory, so they need to evolve with the global community that the Directory serves.</p>\n\n<p>If you would like to contribute to these guidelines, you can make a pull request to <a href="https://github.com/WordPress/wporg-plugin-guidelines">the GitHub repository</a> or email <a href="mailto:plugins@wordpress.org">plugins@wordpress.org</a>. You can also jump into the #pluginreview channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>.</p>\n\n<hr class="wp-block-separator" />\n\n<h2>Further Reading:</h2>\n\n<ul>\n    <li>Near the end of last year a lot of work was put into improving the standards in the WordPress core codebase and now <a href="https://make.wordpress.org/core/2017/11/30/wordpress-php-now-mostly-conforms-to-wordpress-coding-standards/">the entire platform is at nearly 100% compliance with the WordPress coding standards</a>.</li>\n    <li>Gutenberg, the new editor coming to WordPress core in the next major release, <a href="https://make.wordpress.org/core/2018/01/25/whats-new-in-gutenberg-25th-january/">was updated to v2.1 this month</a> with some great usability and technical improvements.</li>\n    <li>The Global Community Team is <a href="https://make.wordpress.org/community/2018/01/16/2018-goals-for-the-global-community-team-suggestions-time/">taking suggestions for the goals of the Community program in 2018</a>.</li>\n    <li><a href="https://online.wpcampus.org/">WPCampus Online</a>, a digital conference focused on WordPress in higher education, took place on January 30. The videos of the event sessions will be online soon.</li>\n    <li>A WordPress community member <a href="https://wptavern.com/new-toolkit-simplifies-the-process-of-creating-gutenberg-blocks">has released a toolkit</a> to help developers build blocks for Gutenberg.</li>\n    <li>The community team that works to improve the WordPress hosting experience is relatively young, but <a href="https://make.wordpress.org/hosting/2018/01/25/hosting-meeting-notes-january-10-2018/">they have been making some great progress recently</a>.</li>\n</ul>\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</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, 02 Feb 2018 08:10: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: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: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:54:"WPTavern: WordPress 4.9.3 Rescheduled for February 5th";s:7:"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=78058";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wptavern.com/wordpress-4-9-3-rescheduled-for-february-5th";s: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:1336:"<p>WordPress 4.9.3 is a maintenance release and was originally scheduled to be available on January 30th. However, due to ongoing tickets and a short time frame to test the <a href="https://make.wordpress.org/core/2018/02/01/wordpress-4-9-3-rc/">release candidate</a>, it has <a href="https://make.wordpress.org/core/2018/01/31/wordpress-4-9-3-release-pushed-to-february-5th/">been pushed back</a> to February 5th.</p>\n<p><a href="https://make.wordpress.org/core/2018/02/01/wordpress-4-9-3-rc/">WordPress 4.9.3 RC 1</a> is available for testing. This release <a href="https://make.wordpress.org/core/2018/01/24/jshint-removed-from-codemirror-in-4-9-3/">removes JSHint from the code editors</a> due to conflicts with the GPL License. If your code relies on JSHint from Core, <a href="https://core.trac.wordpress.org/ticket/42850">developers encourage</a> you to update it to use a copy of JSHint.</p>\n<p>Other changes in 4.9.3 include, avoiding page scrolling when navigating the media modal, a handful of improvements to the customizer, <a href="https://make.wordpress.org/core/2018/01/26/wordpress-4-9-3-beta/">and more</a>. Please test WordPress 4.9.3 on a staging site and if you encounter any bugs, you can report them on the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta section</a> of the support forums.</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, 02 Feb 2018 08:09:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:78:"WPTavern: WooCommerce 3.3 Removed From Plugin Directory Due to Theme Conflicts";s:7:"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=77962";s:7:"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/woocommerce-3-3-removed-from-plugin-directory-due-to-theme-conflicts";s: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:3081:"<p>Earlier this week, WooCommerce 3.3 <a href="https://wptavern.com/woocommerce-3-3-increases-theme-compatibility-auto-regenerates-thumbnails">was released</a> and among the features was increased theme compatibility. However, soon after release, users of third-party themes <a href="https://wordpress.org/support/topic/wc-3-3-issues-with-categories-displaying-in-shop/">reported issues</a> with categories displaying improperly.</p>\n<p>Despite it being a minor release that should be fully backwards compatible with previous releases up to 3.0, WooCommerce has removed 3.3 from the plugin directory and replaced it with 3.2.6.</p>\n<p>According <a href="https://woocommerce.wordpress.com/2018/02/01/woocommerce-3-3-1-status-update/">to a post</a> on the project&#8217;s official blog, WooCommerce 3.3.1 will take the place of 3.3 and will include a fix for the category display issue.</p>\n<blockquote class="wp-block-quote"><p>The issue affected themes with template overrides from 3.2.x which hadn’t been made compatible with 3.3. In general, <a href="https://github.com/woocommerce/woocommerce/wiki/Template-File-Guidelines-for-Devs-and-Theme-Authors#hook-vs-override---when-to-use-what">we recommend that themes use hooks instead of template overrides.</a> Themes such as <a href="https://en-gb.wordpress.org/themes/storefront/">Storefront</a> (which does not use template overrides) were compatible at launch.</p>\n<p><cite>WooCommerce Blog</cite></p></blockquote>\n<p>If you&#8217;ve already updated to WooCommerce 3.3 and your theme is compatible, you don&#8217;t need to make any changes. If your theme is not compatible, WooCommerce recommends checking with your theme&#8217;s author to see if a compatibility fix has been released.</p>\n<p>Users can also wait for the release of 3.3.1, update to the <a href="https://github.com/woocommerce/woocommerce/releases/tag/3.3.1-rc.1">pre-release version</a> of 3.3.1, or use the <a href="https://wordpress.org/plugins/wp-rollback/">WP-Rollback plugin</a> and revert back to 3.2.6. WooCommerce developers suggest only going the WP-Rollback route if you&#8217;re not comfortable installing pre-release software.</p>\n<p>Coen Jacobs, a former member of the WooCommerce development team, commented on Twitter that this was the first time he can remember that a release was reverted.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Fun fact: As far as I recall, there has never been a release of WooCommerce that has been withdrawn before. During my time on the development team we have pushed fix releases on the same day as a big releases, but never was it reverted like this.</p>\n<p>&mdash; Coen Jacobs (@CoenJacobs) <a href="https://twitter.com/CoenJacobs/status/958768816808497152?ref_src=twsrc%5Etfw">January 31, 2018</a></p></blockquote>\n<p></p>\n<p>The development team has tested 3.3.1 with more than 40 different themes and believe it is stable. However, they are exercising caution and thoroughly testing the fixes with more themes. Users can expect to see 3.3.1 officially released the week of February 5th.</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, 02 Feb 2018 07:06: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:13:"Jeff Chandler";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:81:"WPTavern: WPWeekly Episode 303 – Interview With Zac Gordon, Technology Educator";s:7:"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:58:"https://wptavern.com?p=77901&preview=true&preview_id=77901";s:7:"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/wpweekly-episode-303-interview-with-zac-gordon-technology-educator";s: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:1902:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I are joined by <a href="http://zacgordon.com/">Zac Gordon</a>. We discussed a wide range of topics including, balancing freelance work with educating, an overview of Gutenberg from an educator&#8217;s perspective, and potential brand issues if the Gutenberg name <a href="githubhttps://github.com/WordPress/gutenberg/issues/4681">was deprecated</a>. We also talked about some of the difficulties involved with <a href="https://gutenberg.courses/">creating a course</a> around a feature that&#8217;s not yet part of WordPress core.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://ithemes.com/2018/01/31/ithemes-joining-the-liquid-web-family/">iThemes Acquired by LiquidWeb</a><br />\n<a href="https://woocommerce.com/2018/01/whats-new-woocommerce-3-3/">WooCommerce 3.3 Released</a><br />\n<a href="https://wptavern.com/updraftplus-acquires-easy-updates-manager-plugin">Easy Updates Manager Acquired by UpdraftPlus</a></p>\n<h2>Picks of the Week:</h2>\n<p>John James Jacoby suggested <a href="https://www.beamauthentic.com/">Beam Authentic</a>. Beam Authentic is a wearable, connected, smart button that can be programmed to display different images through an app.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, February 7th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #303:</strong><br />\n</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, 01 Feb 2018 02:12:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:100:"WPTavern: Efrain Rivera, A Longtime Community Member, WordCamp Organizer, and Volunteer, Passes Away";s:7:"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=77893";s:7:"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/efrain-rivera-a-longtime-community-member-wordcamp-organizer-and-volunteer-passes-away";s: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:2776:"<p>Efrain Rivera, who helped organize and volunteer at numerous WordCamps in Florida has passed away at the age of 47. The news was shared on Facebook by his sister on January 28th.</p>\n<img />Efrain Rivera and his wife at WordCamp Miami. Photo courtesy of David Bisset\n<p>David Bisset, organizer of WordCamp Miami and a well-known figure in the Florida WordPress community, <a href="http://davidbisset.com/efrain-rivera/">shared his thoughts</a> on Rivera&#8217;s passing.</p>\n<blockquote><p>Efrain wasn’t just a fellow organizer, but also a supporter of the local WordPress meetups. There was no ulterior motive in anything that he did. Never once did he ask for anything – he was just happy to be there and help out. He was 100% about giving back to the WordPress community, but even if the community didn’t exist he would find a way to help out folks.</p>\n<p>Efrain wasn’t just a supporter and volunteer. He was a good friend to have – someone you could speak frankly too.</p></blockquote>\n<p>Rivera is being remembered as a kind, compassionate, and happy person by members of the community.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">I’m so sorry, he was a pleasure volunteering with,  <a href="https://twitter.com/EfrainWp?ref_src=twsrc%5Etfw">@EfrainWp</a> was always happy to help and answer questions.</p>\n<p>&mdash; Rian M. Kinney, Esq. (@TheKinneyFirm) <a href="https://twitter.com/TheKinneyFirm/status/958855848784252928?ref_src=twsrc%5Etfw">February 1, 2018</a></p></blockquote>\n<p></p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">I remember his kindness David. What a great person and sad loss.</p>\n<p>&mdash; Diane Kinney (@dkinney) <a href="https://twitter.com/dkinney/status/958858994843611138?ref_src=twsrc%5Etfw">February 1, 2018</a></p></blockquote>\n<p></p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Efrain was one of happiest, smiliest, caring people I’d ever hung out with at any WordPress event. <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f64f.png" alt="🙏" class="wp-smiley" /> <a href="https://t.co/qW7ChUmjX0">https://t.co/qW7ChUmjX0</a></p>\n<p>&mdash; J ³ (@JJJ) <a href="https://twitter.com/JJJ/status/958448885030182913?ref_src=twsrc%5Etfw">January 30, 2018</a></p></blockquote>\n<p></p>\n<p><a href="https://memorials.serenitymemorialchapels.com/efrain-rivera/3417849/obituary.php">Memorial services are scheduled</a> for Saturday, February 3, 2018 from 4:00 P.M.-9:00 P.M. EST at Serenity Funeral Home and Cremation, 1450 S State Road 7, North Lauderdale, Florida 33068. The service will take place during visitation at 7PM. If you have any memories of meeting or hanging out with Efrain at any of the WordPress events in Florida, please share them in the comments.</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, 01 Feb 2018 01:13: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:13:"Jeff Chandler";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:44:"Post Status: Liquid Web has acquired iThemes";s:7:"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=41738";s:7:"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://poststatus.com/liquid-web-acquired-ithemes/";s: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:5096:"<p><a href="https://www.liquidweb.com/">Liquid Web</a> has acquired <a href="https://ithemes.com/">iThemes</a>, in an all cash deal that includes the entire iThemes team moving over to Liquid Web as an independent unit. Cory Miller &#8212; CEO of iThemes &#8212; will be the Business Manager of the new unit, with iThemes COO Matt Danner as the Director of Technology and Operations for iThemes. The entire team of twenty three people is staying on, and will continue to be headquartered in Oklahoma.</p>\n<p>This is not the first or last time we&#8217;ll see longstanding WordPress companies get rolled into large hosting providers. It&#8217;s a trend that is natural in any ecosystem as it matures, and iThemes was a clear and quality candidate for a host to target. Cory said the culture around Liquid Web, including their &#8220;heroic support,&#8221; but also the quality he sees in their management team, was a key motivator for them to go work with Liquid Web.</p>\n<p>As hosting companies evolve more and more to provide broader services for customers with managed WordPress offerings, there is less room for utility product creators to fill that gap.</p>\n<p>Backups are a fine example: customers may see less need for external backups if they have confidence that their hosting is managing backups properly. Security is another. These have been great products for iThemes, and still are &#8212; but their current markets are more for hosts without a managed experience, and that slice of the pie has been narrowing.</p>\n<p>iThemes has had a partnership with Liquid Web for about a year and a half now, which started by licensing iThemes Sync for Liquid Web&#8217;s WordPress hosting offering. They&#8217;ve slowly been integrating more features into the platform, and the acquisition will allow Liquid Web to further integrate iThemes&#8217; offerings, and allow iThemes to improve some of their product offerings with the backing of Liquid&#8217;s Web&#8217;s hosting infrastructure.</p>\n<p>I spoke to Cory Miller about the move, which is occurring not long after iThemes&#8217; ten year anniversary in business. He said he looks back every year and sees them as chapters in the iThemes story, and this feels just the same. He&#8217;s excited about what the backing from Liquid Web will allow them to do, and most importantly for him, the ability to keep supporting the team they have built over the years.</p>\n<p>Cory tells me he&#8217;s amazed that they&#8217;ve been able to build the company they have built, and neither he nor his business partners would have imagined it ten years ago. All equity holders had their shares purchased by Liquid Web, and Cory and the team will be Liquid Web employees.</p>\n<p>iThemes has iterated on the business many times over the years &#8212; as the name implies. Their theme business slowly dwindled in terms of the overall ratio of sales revenue it provided. BackupBuddy has long been a flagship, and they&#8217;ve found great success the past couple of years since they acquired and iterated on the iThemes Security product. He said that it took them experimenting a great deal &#8212; and like Exchange for eCommerce, and others &#8212; it didn&#8217;t always work out the way they hoped. But because they stayed agile and kept working at it, they&#8217;ve consistently been able to grow and diversify their product line.</p>\n<p>One practical component Liquid Web will be able to provide, as an example, is their data centers to power BackupBuddy and iThemes Stash storage and processing. iThemes has historically used Amazon, which Cory said really adds up and has started to eat into their own margins. Liquid Web will help them not only improve the offering but also to be able to perform those functions more affordably.</p>\n<p>For Liquid Web, this acquisition furthers their goal to integrate WordPress-specific functionality into their suite of WordPress hosting tools. They recently launched WooCommerce hosting on their platform, and the iThemes Sales Accelerator product can now be a core component of that offering. Additionally, the technology iThemes has built with BackupBuddy and Sync will further add to their platform.</p>\n<p>Beyond the technology and products, Liquid Web Vice President of Products and Innovation Chris Lema tells me it&#8217;s about the team:</p>\n<blockquote><p>This adds so much to what we’re doing with managed WordPress and managed WooCommerce, that it just made a lot of sense — both from a product perspective, and even more from a team perspective.</p></blockquote>\n<p>Having spent a lot of time with the management teams for each of these companies, I would agree that the culture fit is a really good one. And for Liquid Web, a company continuing to make its big push into the WordPress market, it is a solid strategic acquisition move that offers product dividends but more importantly adds a great and experienced WordPress team to their company.</p>\n<p><a href="https://ithemes.com/2018/01/31/ithemes-joining-the-liquid-web-family/">Cory shares more</a> about the news on the iThemes blog.</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, 31 Jan 2018 17:12: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: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: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:60:"HeroPress: The Journey: Curiosity, Challenge, Transformation";s:7:"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=2431";s:7:"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:158:"https://heropress.com/essays/journey-curiosity-challenge-transformation/#utm_source=rss&utm_medium=rss&utm_campaign=journey-curiosity-challenge-transformation";s: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:9293:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/01/013118-2-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: My place in the world has transformed." /><p>When I look back on the past five years I’ve been working with WordPress, I feel the real weight of the journey I’ve had to get where I am. Much of it has been filled with challenge of both of the difficult and welcome variety. I’m an optimist and problem-solver to the core, but I sometimes wonder how I got through these past years. One thing is for certain, my involvement with WordPress, the opportunities and community around it, has been a force for so much good, motivation, and satisfaction in my life.</p>\n<h2>The Beginning</h2>\n<p>When I was introduced to WordPress, I was going through one of the most trying times of my adult life. My dad had suddenly passed away just a few years before. We didn’t have the best relationship, but his quirkiness, interest in esoteric things, and passion for food certainly rubbed off on me.</p>\n<p>I was living with roommates, but moved back home to be with my mom. Not too long after, she developed debilitating osteoarthritis in both of her hips. From a physically healthy yet grieving 52-year-old woman to eventually becoming handicap and walker-bound, needless to say, impacted our lives greatly. I became her caretaker, and I also worked retail part-time for the flexible schedule.</p>\n<blockquote><p>I felt emotionally exhausted, uninspired and quite lost with what my next steps would be.</p></blockquote>\n<p>I grew up using the internet fervently as a youth and in my college years. I met new friends, learned new skills, and traveled to new places thanks the endless source of information it provided for my active mind. So when a friend, now my mentor, John Bolyard, approached me to help him in his web marketing and development consultancy using “WordPress” I just said “yes.” It was mysterious, being unknown to me, and intriguing, which is usually a green light in my book!</p>\n<p>I started doing administrative work on a website he helped develop for a national guild. Like many situations, he had finished their website and they would circle back to him for minor updates. I took on the minor updates, started tinkering on my own, and fell in love in the process.</p>\n<p>The accessibility with which one could make changes and produce content dynamically was just mind blowing to me. It was my gateway to web development and now I could make web content with the ability to work with code, if I so chose. It seemed an endless source of learning and knowledge- it was a great fit.</p>\n<h2>Levelling Up</h2>\n<p>That went well and he brought me on a larger project to help the artist, Dorothy Braudy, create her website archive. I was able to blend my affinity for the technical and handy visual memory to help an all around amazing person (she&#8217;s still one of closest people in my life) tell her story through her art. I was thrilled to have the challenge and the privilege to bring her vibrant and prolific work (hundreds of pieces) to the web.</p>\n<p>I also started assisting John with teaching WordPress classes at SCORE, a government organization that helps people develop and sustain small businesses.</p>\n<blockquote><p>We volunteered our time teaching business owners WordPress to help them build their own websites.</p></blockquote>\n<p>It was challenging yet rewarding to see them feel empowered that they could take a hands-on role in making their web presence.</p>\n<p>Nevertheless, I ended up with several clients and that’s how my freelancing career began :). I also started going to meetups. John brought me to my first one in the San Fernando Valley. I was like wait&#8230;this software is cool and people gather to talk about it? I can also learn stuff too?! Get outta town!</p>\n<p>Well, I started attending fairly frequently. Particularly, the meetup in the West Valley lead by Andrew Behla (then at the Topanga Canyon Library). I soaked up info from presentations given by Roy Sivan, Suzette Franck, and Lucy Beer (who is now my teammate). Just to name a few ;).</p>\n<p>After building a consistent client base, I also started working part-time as a project assistant at a boutique museum exhibit development firm. My first project was for the Huntington Library, Art Collections and Botanical Gardens supporting the development of an educational WordPress website for their Junípero Serra exhibition. What were the chances? My skills in WordPress proved helpful for the project and the firm&#8217;s website.</p>\n<h2>Pivoting</h2>\n<p>At this point, I had seen my mom through her first hip replacement and recovery, and she was moving on to her next one. I thought about where I saw myself and also where I could build a sustainable future given the circumstances. I thought WordPress, and so I did a trial as a Happiness Engineer at WordPress.com.</p>\n<p>While I didn&#8217;t get the position, I met some great people and learned exponentially more in that short time than I had on my own. More so, I learned about the users, WordPress’ strengths and weaknesses, and how to fill that gap in an accessible way. I was sad, but also motivated. I took on more client work and just did the thing.</p>\n<p>After three years, it was time to leave the exhibit development firm. It was fascinating, it provided me a design, development and project management vocabulary I had never encountered before. However, I needed a firmer career path and I still thought WordPress. My mom was recovered, I had also just recovered from some health issues, and I knew it was time for a change.</p>\n<p>While doing client work for several months, I also explored options on how I could &#8220;level up.&#8221; Maybe it was my time to dig into web development: should I learn on my own, go to a school?</p>\n<blockquote><p>In my gut, I knew I had to find work that supported my endeavors, so I started applying in the WordPress and tech ecosystem.</p></blockquote>\n<p>I networked, attended workshops, and met some awesome folks in the local tech and WordPress communities. I was also approached about joining the organizer team for WordCamp Los Angeles (WCLAX). I said “yes” (that magic word) and last year we had a great event.</p>\n<p>When we started planning, I had also heard from WP Media, (the company behind the WP Rocket and Imagify plugins), that I was hired for their Customer Support position. We’re a remote crew spread across 8 countries. However, I’ve been lucky enough to spend time with them at WordCamp Europe, WordCamp US, and our annual retreat last year.</p>\n<h2>Transformation</h2>\n<p>My place in the world has transformed. I&#8217;ve traveled to places once out of reach, work every day with some of the most brilliant and kind people in the WordPress space, and grow day by day with new challenges and opportunities. I&#8217;m happy, mom is healthy, and the journey continues…</p>\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: The Journey: Curiosity, Challenge, Transformation" class="rtsocial-twitter-button" href="https://twitter.com/share?text=The%20Journey%3A%20Curiosity%2C%20Challenge%2C%20Transformation&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fjourney-curiosity-challenge-transformation%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: The Journey: Curiosity, Challenge, Transformation" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fjourney-curiosity-challenge-transformation%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%2Fessays%2Fjourney-curiosity-challenge-transformation%2F&title=The+Journey%3A+Curiosity%2C+Challenge%2C+Transformation" rel="nofollow" target="_blank" title="Share: The Journey: Curiosity, Challenge, Transformation"></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/essays/journey-curiosity-challenge-transformation/&media=https://heropress.com/wp-content/uploads/2018/01/013118-2-150x150.jpg&description=The Journey: Curiosity, Challenge, Transformation" rel="nofollow" target="_blank" title="Pin: The Journey: Curiosity, Challenge, Transformation"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/journey-curiosity-challenge-transformation/" title="The Journey: Curiosity, Challenge, Transformation"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/journey-curiosity-challenge-transformation/">The Journey: Curiosity, Challenge, Transformation</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, 31 Jan 2018 11:00:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Renee Johnson";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:84:"WPTavern: WooCommerce 3.3 Increases Theme Compatibility, Auto Regenerates Thumbnails";s:7:"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=77795";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"https://wptavern.com/woocommerce-3-3-increases-theme-compatibility-auto-regenerates-thumbnails";s: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:3108:"<p>WooCommerce 3.3 <a href="https://woocommerce.com/2018/01/whats-new-woocommerce-3-3/">is available</a> and is considered a minor release. Based on the project’s <a href="https://github.com/woocommerce/woocommerce/wiki/Roadmap-and-release-process">new release process</a>, it should be fully backwards compatible with previous releases up to 3.0.</p>\n<p>The orders screen has been redesigned with large buttons that indicate an order’s status. You can also view an order’s details from the order screen without having to edit the order.</p>\n<img class="aligncenter" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2018/01/WC33OrdersScreen.png?w=627&ssl=1" alt="" width="627" height="261" />WooCommerce 3.3 Orders Screen\n<p>For products that are on backorder and have stock management enabled, WooCommerce 3.3 will automatically transition from ‘In stock’ to ‘On backorder’ or ‘Out of stock’ as the inventory decreases. Once inventory is added, the status will switch back to ‘In Stock’.</p>\n<img class="aligncenter" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2018/01/WC33OrderStatus.png?w=627&ssl=1" alt="" width="627" height="328" />WooCommerce 3.3 Order Status Screen\n<p>For full compatibility, users generally needed to use a WordPress theme that specifically supported WooCommerce. In 3.3, improvements have been made so that WooCommerce renders on themes that don’t fully support it, making it compatible with nearly every WordPress theme.</p>\n<p>Users can now set the number of columns and rows for shops with the ability to preview the results live via the Customizer. The columns will resize to fill the entire width of the area and is available on all themes.</p>\n<p>In earlier versions of WooCommerce, shop owners needed to use the <a href="https://wordpress.org/plugins/regenerate-thumbnails/">Regenerate Thumbnails</a> after updating a product’s image as WordPress did not automatically resize the image and generate new thumbnails. WooCommerce 3.3 adds on-the-fly thumbnail regeneration and background thumbnail resizing.</p>\n<p>In addition, users can customize the aspect ratios of product images. The choices are classic square images, custom cropped images, or uncropped images</p>\n<img class="aligncenter" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2018/01/WC33ImageAspectRatio.png?w=627&ssl=1" alt="" width="627" height="402" />WooCommerce 3.3 Image Aspect Ratio Options\n<p>Shop owners can now view logs of product downloads with a couple of built-in filters including, by order, by product, by customer, and by file. You can also search for extensions now from the Extensions administration screen.</p>\n<p>WooCommerce 3.3 includes more features and changes than what’s listed here. For a detailed overview of what’s new in 3.3, <a href="https://github.com/woocommerce/woocommerce/blob/release/3.3/readme.txt">check out the changelog</a>. If you think you’ve discovered a bug, please report it on the <a href="https://github.com/woothemes/woocommerce/issues">project’s GitHub page</a>.</p>\n<p><!-- /wp:core/paragraph --></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, 30 Jan 2018 22:53:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";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:48:"Mark Jaquith: Simple WordPress deploys using Git";s:7:"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:40:"http://markjaquith.wordpress.com/?p=5422";s:7:"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://markjaquith.wordpress.com/2018/01/30/simple-wordpress-deploys-using-git/";s: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:3328:"<p>A few weeks back, Clifton Griffin asked me a question about deploying WordPress sites:</p>\n<div class="embed-twitter">\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr"><a href="https://twitter.com/markjaquith?ref_src=twsrc%5Etfw">@markjaquith</a> Hey Mark, quick question: Do you still use and recommend Capistrano?</p>\n<p>&mdash; Clifton Griffin (@clifgriffin) <a href="https://twitter.com/clifgriffin/status/948373150680707073?ref_src=twsrc%5Etfw">January 3, 2018</a></p></blockquote>\n<p></div>\n<p>I <b>do not</b> use Capistrano for deployments anymore, for one simple reason: it was massive overkill for most of the sites I manage, and maintaining it was not worth the benefit.</p>\n<p>My current deployment system for WordPress sites is simple: I use Git.</p>\n<p>I&#8217;m already using Git for version control of the site&#8217;s code, so using Git for deployments is not that much more work. There are a few ways to do this, but the simplest way is to just make your site root a Git checkout of your site files.</p>\n<p>Then, if your server has read-access to your Git remote, you can run some Git commands to sync everything. Here are your options:</p>\n<ol>\n<li><strong>git pull</strong> — Simple, but might fail if someone naughty has made code modifications on the server.</li>\n<li><strong>git fetch &amp;&amp; git reset &#8211;hard origin/master</strong> — The hard reset method will wipe any local modifications that someone has mistakenly made.</li>\n</ol>\n<p>But wait. Before you implement this, it is very important that you ensure that your server&#8217;s <strong>.git</strong> directory is not readable, as it might be able to leak sensitive information about your site&#8217;s code. How you do this will depend on what web server you&#8217;re running. In Nginx, I do the following:</p>\n<pre class="brush: plain; title: ; notranslate">location ~ /\\.(ht[a-z]+|git|svn) {\ndeny all;\n}</pre>\n<p>In Apache, you could put the following in your <strong>.htaccess</strong> file:</p>\n<pre class="brush: plain; title: ; notranslate">RedirectMatch 404 /\\.git</pre>\n<p>SSHing into your server every time is tedious, so let&#8217;s script that:</p>\n<pre class="brush: bash; title: ; notranslate">#!/bin/bash\nssh example.com \'cd /srv/www/example.com &amp;&amp; git pull\'</pre>\n<p>Save that to <strong>deploy.sh</strong> in your Git repo, run <strong>chmod +x deploy.sh</strong>, and commit it to the repo. Now when you&#8217;re ready to deploy the site, just type <strong>./deploy.sh</strong> and the public site will pull down the latest changes from your main Git remote.</p>\n<p>Bonus points if you make <strong>deploy.sh</strong> take an optional commit hash, so you can also use this tool to roll back to a previous hash, in case a commit goes wrong.</p>\n<p>This method has served me well, for years, and has required no maintenance.</p>\n<p>What methods are you using for WordPress code deploys?</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s: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, 30 Jan 2018 15:31:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Mark Jaquith";s:7:"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:"Thu, 08 Mar 2018 16:40:00 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Thu, 08 Mar 2018 16:30:27 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 2";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20130911010210";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(234, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1520570402', 'no'),
(235, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1520527202', 'no'),
(236, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1520570402', 'no'),
(237, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '<div class="rss-widget"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2018/03/the-month-in-wordpress-february-2018/\'>The Month in WordPress: February 2018</a></li></ul></div><div class="rss-widget"><ul><li><a class=\'rsswidget\' href=\'https://wptavern.com/wpweekly-episode-307-thirty-percent-of-the-web\'>WPTavern: WPWeekly Episode 307 – Thirty Percent of the Web</a></li><li><a class=\'rsswidget\' href=\'https://ma.tt/2018/03/back-to-blogging/\'>Matt: Back to Blogging</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/conceptual-ideas-on-how-the-customizer-could-integrate-with-gutenberg\'>WPTavern: Conceptual Ideas on How the Customizer Could Integrate With Gutenberg</a></li></ul></div>', 'no');

-- --------------------------------------------------------

--
-- Table structure for table `wp_postmeta`
--

CREATE TABLE `wp_postmeta` (
  `meta_id` bigint(20) UNSIGNED NOT NULL,
  `post_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;



-- --------------------------------------------------------

--
-- Table structure for table `wp_termmeta`
--

CREATE TABLE `wp_termmeta` (
  `meta_id` bigint(20) UNSIGNED NOT NULL,
  `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

-- --------------------------------------------------------

--
-- Table structure for table `wp_terms`
--

CREATE TABLE `wp_terms` (
  `term_id` bigint(20) UNSIGNED NOT NULL,
  `name` varchar(200) NOT NULL DEFAULT '',
  `slug` varchar(200) NOT NULL DEFAULT '',
  `term_group` bigint(10) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `wp_terms`
--

INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES
(1, 'Uncategorized', 'uncategorized', 0),
(2, 'Lics', 'lics', 0);

-- --------------------------------------------------------

--
-- Table structure for table `wp_term_relationships`
--

CREATE TABLE `wp_term_relationships` (
  `object_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `term_order` int(11) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `wp_term_relationships`
--

INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES
(9, 2, 0),
(15, 2, 0),
(16, 2, 0),
(17, 2, 0),
(18, 2, 0);

-- --------------------------------------------------------

--
-- Table structure for table `wp_term_taxonomy`
--

CREATE TABLE `wp_term_taxonomy` (
  `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL,
  `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `taxonomy` varchar(32) NOT NULL DEFAULT '',
  `description` longtext NOT NULL,
  `parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `count` bigint(20) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `wp_term_taxonomy`
--

INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES
(1, 1, 'category', '', 0, 0),
(2, 2, 'wplss_logo_showcase_cat', '', 0, 5);

-- --------------------------------------------------------

--
-- Table structure for table `wp_usermeta`
--

CREATE TABLE `wp_usermeta` (
  `umeta_id` bigint(20) UNSIGNED NOT NULL,
  `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `meta_key` varchar(255) DEFAULT NULL,
  `meta_value` longtext
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

--
-- Dumping data for table `wp_usermeta`
--

INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES
(1, 1, 'nickname', 'admin'),
(2, 1, 'first_name', ''),
(3, 1, 'last_name', ''),
(4, 1, 'description', ''),
(5, 1, 'rich_editing', 'true'),
(6, 1, 'comment_shortcuts', 'false'),
(7, 1, 'admin_color', 'fresh'),
(8, 1, 'use_ssl', '0'),
(9, 1, 'show_admin_bar_front', 'true'),
(10, 1, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}'),
(11, 1, 'wp_user_level', '10'),
(12, 1, 'dismissed_wp_pointers', 'text_widget_custom_html'),
(13, 1, 'show_welcome_panel', '1'),
(14, 1, 'session_tokens', 'a:2:{s:64:"c23dc15b1f8d0052b36dcdfb0c1096dd7c7bbaf33fe6433e801ae38cff1a33a9";a:4:{s:10:"expiration";i:1520525911;s:2:"ip";s:9:"127.0.0.1";s:2:"ua";s:114:"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36";s:5:"login";i:1520353111;}s:64:"94d68f11bab91447dc35284abbeee1342867bee184ebc8b3ac6bdcca38111d30";a:4:{s:10:"expiration";i:1520614263;s:2:"ip";s:9:"127.0.0.1";s:2:"ua";s:114:"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36";s:5:"login";i:1520441463;}}'),
(15, 1, 'wp_dashboard_quick_press_last_post_id', '19'),
(16, 1, 'wp_user-settings', 'hidetb=1&libraryContent=browse&editor=tinymce'),
(17, 1, 'wp_user-settings-time', '1520355196'),
(18, 1, 'managenav-menuscolumnshidden', 'a:5:{i:0;s:11:"link-target";i:1;s:11:"css-classes";i:2;s:3:"xfn";i:3;s:11:"description";i:4;s:15:"title-attribute";}'),
(19, 1, 'metaboxhidden_nav-menus', 'a:2:{i:0;s:12:"add-post_tag";i:1;s:15:"add-post_format";}'),
(20, 1, 'community-events-location', 'a:1:{s:2:"ip";s:9:"127.0.0.0";}');

--
-- Indexes for dumped tables
--

--
-- Indexes for table `wp_commentmeta`
--
ALTER TABLE `wp_commentmeta`
  ADD PRIMARY KEY (`meta_id`),
  ADD KEY `comment_id` (`comment_id`),
  ADD KEY `meta_key` (`meta_key`(191));

--
-- Indexes for table `wp_comments`
--
ALTER TABLE `wp_comments`
  ADD PRIMARY KEY (`comment_ID`),
  ADD KEY `comment_post_ID` (`comment_post_ID`),
  ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
  ADD KEY `comment_date_gmt` (`comment_date_gmt`),
  ADD KEY `comment_parent` (`comment_parent`),
  ADD KEY `comment_author_email` (`comment_author_email`(10));

--
-- Indexes for table `wp_links`
--
ALTER TABLE `wp_links`
  ADD PRIMARY KEY (`link_id`),
  ADD KEY `link_visible` (`link_visible`);

--
-- Indexes for table `wp_options`
--
ALTER TABLE `wp_options`
  ADD PRIMARY KEY (`option_id`),
  ADD UNIQUE KEY `option_name` (`option_name`);

--
-- Indexes for table `wp_postmeta`
--
ALTER TABLE `wp_postmeta`
  ADD PRIMARY KEY (`meta_id`),
  ADD KEY `post_id` (`post_id`),
  ADD KEY `meta_key` (`meta_key`(191));

--
-- Indexes for table `wp_termmeta`
--
ALTER TABLE `wp_termmeta`
  ADD PRIMARY KEY (`meta_id`),
  ADD KEY `term_id` (`term_id`),
  ADD KEY `meta_key` (`meta_key`(191));

--
-- Indexes for table `wp_terms`
--
ALTER TABLE `wp_terms`
  ADD PRIMARY KEY (`term_id`),
  ADD KEY `slug` (`slug`(191)),
  ADD KEY `name` (`name`(191));

--
-- Indexes for table `wp_term_relationships`
--
ALTER TABLE `wp_term_relationships`
  ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`),
  ADD KEY `term_taxonomy_id` (`term_taxonomy_id`);

--
-- Indexes for table `wp_term_taxonomy`
--
ALTER TABLE `wp_term_taxonomy`
  ADD PRIMARY KEY (`term_taxonomy_id`),
  ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
  ADD KEY `taxonomy` (`taxonomy`);

--
-- Indexes for table `wp_usermeta`
--
ALTER TABLE `wp_usermeta`
  ADD PRIMARY KEY (`umeta_id`),
  ADD KEY `user_id` (`user_id`),
  ADD KEY `meta_key` (`meta_key`(191));

--
-- AUTO_INCREMENT for dumped tables
--

--
-- AUTO_INCREMENT for table `wp_commentmeta`
--
ALTER TABLE `wp_commentmeta`
  MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `wp_comments`
--
ALTER TABLE `wp_comments`
  MODIFY `comment_ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `wp_links`
--
ALTER TABLE `wp_links`
  MODIFY `link_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `wp_options`
--
ALTER TABLE `wp_options`
  MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=238;
--
-- AUTO_INCREMENT for table `wp_postmeta`
--
ALTER TABLE `wp_postmeta`
  MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=43;
--
-- AUTO_INCREMENT for table `wp_termmeta`
--
ALTER TABLE `wp_termmeta`
  MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `wp_terms`
--
ALTER TABLE `wp_terms`
  MODIFY `term_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `wp_term_taxonomy`
--
ALTER TABLE `wp_term_taxonomy`
  MODIFY `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `wp_usermeta`
--
ALTER TABLE `wp_usermeta`
  MODIFY `umeta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=21;
