--
-- Host: localhost    Database: comtechl_wp782
-- ------------------------------------------------------


--
-- Table structure for table `wpib_commentmeta`
--

CREATE TABLE `wpib_commentmeta` (
  `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `comment_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `meta_value` longtext COLLATE utf8mb4_unicode_ci,
  PRIMARY KEY (`meta_id`),
  KEY `comment_id` (`comment_id`),
  KEY `meta_key` (`meta_key`(191))
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpib_commentmeta`
--


--
-- Table structure for table `wpib_comments`
--

CREATE TABLE `wpib_comments` (
  `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0',
  `comment_author` tinytext COLLATE utf8mb4_unicode_ci NOT NULL,
  `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_ci 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 COLLATE utf8mb4_unicode_ci NOT NULL,
  `comment_karma` int(11) NOT NULL DEFAULT '0',
  `comment_approved` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '1',
  `comment_agent` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `comment_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0',
  `user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`comment_ID`),
  KEY `comment_post_ID` (`comment_post_ID`),
  KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
  KEY `comment_date_gmt` (`comment_date_gmt`),
  KEY `comment_parent` (`comment_parent`),
  KEY `comment_author_email` (`comment_author_email`(10))
) ENGINE=MyISAM AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpib_comments`
--


--
-- Table structure for table `wpib_layerslider`
--

CREATE TABLE `wpib_layerslider` (
  `id` int(10) NOT NULL AUTO_INCREMENT,
  `author` int(10) NOT NULL DEFAULT '0',
  `name` varchar(100) COLLATE utf8mb4_unicode_520_ci DEFAULT '',
  `slug` varchar(100) COLLATE utf8mb4_unicode_520_ci DEFAULT '',
  `data` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `date_c` int(10) NOT NULL,
  `date_m` int(10) NOT NULL,
  `schedule_start` int(10) NOT NULL DEFAULT '0',
  `schedule_end` int(10) NOT NULL DEFAULT '0',
  `flag_hidden` tinyint(1) NOT NULL DEFAULT '0',
  `flag_deleted` tinyint(1) NOT NULL DEFAULT '0',
  `flag_popup` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wpib_layerslider`
--


--
-- Table structure for table `wpib_layerslider_revisions`
--

CREATE TABLE `wpib_layerslider_revisions` (
  `id` int(10) NOT NULL AUTO_INCREMENT,
  `slider_id` int(10) NOT NULL,
  `author` int(10) NOT NULL DEFAULT '0',
  `data` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `date_c` int(10) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wpib_layerslider_revisions`
--


--
-- Table structure for table `wpib_links`
--

CREATE TABLE `wpib_links` (
  `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci 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) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_notes` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  PRIMARY KEY (`link_id`),
  KEY `link_visible` (`link_visible`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpib_links`
--


--
-- Table structure for table `wpib_loginizer_logs`
--

CREATE TABLE `wpib_loginizer_logs` (
  `username` varchar(255) NOT NULL DEFAULT '',
  `time` int(10) NOT NULL DEFAULT '0',
  `count` int(10) NOT NULL DEFAULT '0',
  `lockout` int(10) NOT NULL DEFAULT '0',
  `ip` varchar(255) NOT NULL DEFAULT '',
  `url` varchar(255) NOT NULL DEFAULT '',
  UNIQUE KEY `ip` (`ip`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `wpib_loginizer_logs`
--

INSERT INTO `wpib_loginizer_logs` VALUES ('swamitra.s@cisplinc.com',1543553676,3,1,'103.227.96.30','https://www.comtechl.nwpro2.fcomet.com/wp-login.php');

--
-- Table structure for table `wpib_options`
--

CREATE TABLE `wpib_options` (
  `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `option_name` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes',
  PRIMARY KEY (`option_id`),
  UNIQUE KEY `option_name` (`option_name`)
) ENGINE=MyISAM AUTO_INCREMENT=4435 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

--
-- Dumping data for table `wpib_options`
--


INSERT INTO `wpib_options` VALUES (4415,'_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:90:\"WPTavern: Gutenberg Times to Host Live Q&amp;A with Gutenberg Leads on Friday, November 30\";s:7:\"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=85908\";s:7:\"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:95:\"https://wptavern.com/gutenberg-times-to-host-live-qa-with-gutenberg-leads-on-friday-november-30\";s: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:1224:\"<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/11/creating-gutenberg-q-and-a.jpg?ssl=1\"><img /></a></p>\n<p>Birgit Pauli-Haack, curator of the <a href=\"https://gutenbergtimes.com/\" rel=\"noopener\" target=\"_blank\">Gutenberg Times</a> website, is hosting a Q&#038;A session with Gutenberg&#8217;s phase 1 design and development leads on Friday, November 30, at 2pm ET (19:00 UTC). Matias Ventura, Tammie Lister, and Joen Asmussen will join Pauli-Haack to discuss their journey &#8220;Creating Gutenberg&#8221; over the past two years.</p>\n<p>If you have any pressing questions about Gutenberg&#8217;s architecture, design, or the future of the project, this event is a good opportunity to speak to members of the team who have been building it full-time. The Q&#038;A is free to watch but attendees who want to participate with questions will need to <a href=\"https://zoom.us/webinar/register/6915430666443/WN_d_ejr1e0T0Se1YpyoU0Ojg\" rel=\"noopener\" target=\"_blank\">register</a>. There are 100 seats available. Pauli-Haack will also be live-streaming the session to the <a href=\"https://www.youtube.com/channel/UCSD3LG2kSHdr7llRSHaylxw\" rel=\"noopener\" target=\"_blank\">Gutenberg Times YouTube channel</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, 30 Nov 2018 00:48:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"Matt: WordPress 5.0: A Gutenberg FAQ\";s:7:\"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=48628\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"https://ma.tt/2018/11/a-gutenberg-faq/\";s: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:17970:\"<p>We are nearing the release date for WordPress 5.0 and Gutenberg, one of the most important and exciting projects I’ve worked on in my <a href=\"https://ma.tt/2018/05/wordpress-at-15/\">15 years</a> with this community. <br /></p>\n\n\n\n<p>I knew we would be taking a big leap. But it’s a leap we need to take, and I think the end result is going to open up many new opportunities for everyone in the ecosystem, and for those being introduced to WordPress for the first time. It brings us closer to our mission of democratizing publishing for everyone.<br /></p>\n\n\n\n<p>I recently visited WordCamp Portland to talk about Gutenberg and WordPress 5.0, which will also include the new default theme <a href=\"https://make.wordpress.org/core/2018/10/16/introducing-twenty-nineteen/\">Twenty Nineteen</a>, which you’re seeing me test out on this very site. There were some great questions and testimonials about Gutenberg, so I’d urge you to watch the <a href=\"https://wordpress.tv/2018/11/08/matt-mullenweg-qa-at-wordcamp-portland-2018/\">full video</a> and <a href=\"https://wptavern.com/matt-mullenweg-addresses-controversies-surrounding-gutenberg-at-wordcamp-portland-qa\">read the WP Tavern recap</a>. I&#8217;ve also visited meetups, responded to review threads, kept an eye on support, and I&#8217;m in the middle of <a href=\"https://make.wordpress.org/core/2018/11/29/gutenberg-5-0-listening-office-hours/\">office hours with the core community</a>.<br /></p>\n\n\n\n<p>As we head toward the release date and <a href=\"https://2018.us.wordcamp.org/\">WordCamp US</a>, I&#8217;ve put many questions and answers into a Gutenberg FAQ below. For those who have other questions, I will be checking the comments here. <br /></p>\n\n\n\n<p>It’s an exciting time, and I’m thrilled to be working with y’all on this project. </p>\n\n\n\n<img />Not the ship of Theseus\n\n\n\n<h2>What is Gutenberg? </h2>\n\n\n\n<p>Gutenberg, for those who aren&#8217;t actively following along, is a brand new Editor for WordPress &#8212; contributors have been working on it since January 2017 and it&#8217;s one of the most significant changes to WordPress in years. It&#8217;s built on the idea of using &#8220;blocks&#8221; to write and design posts and pages. <br /></p>\n\n\n\n<p>This will serve as the foundation for future improvements to WordPress, including blocks as a way not just to design posts and pages, but also entire sites. <br /></p>\n\n\n\n<p>The overall goal is to simplify the first-time user experience of WordPress &#8212; for those who are writing, editing, publishing, and designing web pages. The editing experience is intended to give users a better visual representation of what their post or page will look like when they hit publish. As I wrote in <a href=\"https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/\">my post last year</a>, &#8220;Users will finally be able to build the sites they see in their imaginations.&#8221; <br /></p>\n\n\n\n<p>Matías Ventura, team lead for Gutenberg, <a href=\"https://matiasventura.com/post/gutenberg-or-the-ship-of-theseus/\">wrote an excellent post</a> about the vision for Gutenberg, saying, “It’s an attempt to improve how users interact with their content in a fundamentally visual way, while at the same time giving developers the tools to create more fulfilling experiences for the people they are helping.”</p>\n\n\n\n<h2>Why do we need Gutenberg at all? </h2>\n\n\n\n<p>For many of us already in the WordPress community, it can be easy to forget the learning curve that exists for people being introduced to WordPress for the first time. Customizing themes, adding shortcodes, editing widgets and menus &#8212; there’s an entire language that one must learn behind the scenes in order to make a site or a post look like you want it to look. <br /></p>\n\n\n\n<p>Over the past several years, JavaScript-based applications have created opportunities to simplify the user experience in consumer apps and software. Users’ expectations have changed, and the bar has been raised for simplicity. It is my deep belief that WordPress must evolve to improve and simplify its own user experience for first-time users. <br /></p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">What can you do in 137 lines in <a href=\"https://twitter.com/hashtag/Gutenberg?src=hash&ref_src=twsrc%5Etfw\">#Gutenberg</a>? <a href=\"https://t.co/zLINZGMXMe\">pic.twitter.com/zLINZGMXMe</a></p>&mdash; Dennis Snell (@dmsnell23) <a href=\"https://twitter.com/dmsnell23/status/1063126946350096389?ref_src=twsrc%5Etfw\">November 15, 2018</a></blockquote>\n</div>\n\n\n\n<h2>Why blocks? </h2>\n\n\n\n<p>The idea with blocks was to create a new common language across WordPress, a new way to connect users to plugins, and replace a number of older content types &#8212; things like shortcodes and widgets &#8212; that one had to be well-versed in the idiosyncrasies of WordPress to understand. <br /></p>\n\n\n\n<p>The block paradigm is not a new one &#8212; in fact many great plugins have already shown the promise of blocks with page design in WordPress. Elementor, one of the pioneers in this space, has now introduced <a href=\"https://elementor.com/blog/blocks-for-gutenberg/\">a new collection of Gutenberg blocks</a> to showcase what’s possible: <br /></p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<h2>Why change the Editor? </h2>\n\n\n\n<p>The Editor is where most of the action happens in WordPress’s daily use, and it was a place where we could polish and perfect the block experience in a contained environment. <br /></p>\n\n\n\n<p>Additionally, the classic Editor was built primarily for text &#8212; articles have become increasingly multimedia, with social media embeds, maps, contact forms, photo collages, videos, and GIFs. It was time for a design paradigm that allowed us to move past the messy patchwork of shortcodes and text. <br /></p>\n\n\n\n<p>The Editor is just the start. In upcoming phases blocks will become a fundamental part of entire site templates and designs. It’s currently a struggle to use the Customizer and figure out how to edit sections like menus, headers, and footers. With blocks, people will be able to edit and manipulate everything on their site without having to understand where WordPress hides everything behind the scenes. <br /></p>\n\n\n\n<h2>What does Automattic get out of this? </h2>\n\n\n\n<p>There have been posts recently asking questions about Automattic’s involvement in Gutenberg compared to other contributors and companies. There is no secret conspiracy here &#8212; as project lead I was able to enlist the help of dozens of my colleagues to contribute to this project, and I knew that a project of this size would require it. Automattic aims to have 5% of its people dedicated to WordPress community projects, which at its current size would be about 42 people full-time. The company is a bit behind that now (~35 full-time), and the company is growing a lot next year, so look for 10-15 additional people working on core and community projects.&nbsp;<br /></p>\n\n\n\n<p>In the end, Gutenberg is similar to many other open source projects &#8212; Automattic will benefit from it, but so will everyone else in the WordPress community (and even <a href=\"https://drupalgutenberg.org/\">the Drupal community</a>). It’s available for everyone under the GPL. If the goal was purely to benefit Automattic it would have been faster, easier, and created an advantage for Automattic to have Gutenberg just on WP.com. That wasn&#8217;t, and isn&#8217;t, the point.</p>\n\n\n\n<h2>Is Gutenberg ready? </h2>\n\n\n\n<p>Absolutely. Our original goal with Gutenberg was to get it on 100,000 sites to begin testing &#8212; it’s now already on <a href=\"https://gutenstats.blog/\">more than 1 million sites</a>, and it’s the fastest-growing plugin in WordPress history. There is a lot of user demand.<br /></p>\n\n\n\n<p>The goal was to both test Gutenberg on as many sites as possible before the 5.0 release, and also to encourage plugin developers to make sure their plugins and services will be ready. With everyone pitching in, we can make this the most <em>anti-climactic</em> release in WordPress history. &nbsp;<br /></p>\n\n\n\n<p>In the recent debate over Gutenberg readiness, I think it&#8217;s important to understand the difference between Gutenberg being ready code-wise (it is now), and whether the entire community is ready for Gutenberg.<br /></p>\n\n\n\n<p>It will take some time &#8212; we&#8217;ve had 15 years to polish and perfect core, after all &#8212; but the global WordPress community has some of the world&#8217;s most talented contributors and we can make it as good as we want to make it. <br /></p>\n\n\n\n<p>There is also a new opportunity to dramatically expand the WordPress contributor community to include more designers and JavaScript engineers. With JavaScript apps there are also new opportunities for designing documentation and support right on the page, so that help arrives right where you need it. <br /></p>\n\n\n\n<p>Someone described Gutenberg to me as “WordPress in 3D.” I like the sound of that. Blocks are like layers you can zoom in and out of. The question now is: What are we going to build with this new dimension? </p>\n\n\n\n<h2>Do I have to switch to Gutenberg when WordPress 5.0 is released? </h2>\n\n\n\n<p>Not at all. When it’s released, you get to choose what happens. You can install the <a href=\"https://wordpress.org/plugins/classic-editor/\">Classic Editor plugin</a> today and when 5.0 is released, nothing will change. We&#8217;ve commited to supporting and updating Classic Editor until 2022. If you’d like to <a href=\"https://wordpress.org/plugins/gutenberg/\">install Gutenberg early</a>, you can do that now too. The Classic Editor plugin has been available for 13 months now, and Gutenberg has been available for 18 months. Both have been heavily promoted since August 2018, and more than 1.3 million .org sites have opted-in already to either experience, so nothing will change for them when they update to 5.0.</p>\n\n\n\n<h2>How can I make sure I’m ready? </h2>\n\n\n\n<p>Before updating to 5.0, try out the <a href=\"https://wordpress.org/plugins/gutenberg/\">Gutenberg plugin</a> with your site to ensure it works with your existing plugins, and also to get comfortable with the new experience. Developers across the entire ecosystem are working hard to update their plugins, but your mileage and plugins may vary. And you can always use the Classic Editor to address any gaps.<br /></p>\n\n\n\n<p>As with every new thing, things might feel strange and new for a bit, but I’m confident once you start using it you’ll get comfy quickly and you won’t want to go back.</p>\n\n\n\n<p>The release candidate of 5.0 is stable and fine to develop against and test.</p>\n\n\n\n<h2>When will 5.0 be released?</h2>\n\n\n\n<p>We have had a stable RC1, which stands for first release candidate, and about to do our second one. There is only currently one known blocker and it&#8217;s cosmetic. The stability and open issues in the release candidates thus far makes me optimistic we can release soon, but as before the primary driver will be the stability and quality of the underlying software. We made the mistake prior of announcing dates when lots of code was still changing, and had to delay because of regressions and bugs. Now that things aren&#8217;t changing, we&#8217;re approaching a time we can commit to a date soon.</p>\n\n\n\n<h2>Is it terrible to do a release in December?</h2>\n\n\n\n<p>Some people think so, some don&#8217;t. There have been <a href=\"https://wordpress.org/about/roadmap/\">9 major WordPress releases</a> in previous Decembers. December releases actually comprise 34% of our major releases in the past decade.</p>\n\n\n\n<h2>Can I set it up so only certain users get to use Gutenberg? </h2>\n\n\n\n<p>Yes, and soon. We’re going to be doing another update to the Classic Editor before the 5.0 release to give it a bit more fine-grained user control &#8212; we’ve heard requests for options that allow certain users or certain roles and post types to have Gutenberg while others have Classic Editor. </p>\n\n\n\n<h2>What happens after 5.0? </h2>\n\n\n\n<p>We’ve been doing a release of Gutenberg every two weeks, and 5.0 isn’t going to stop that. We’ll do minor release to 5.0 (5.0.1, 5.0.2) fortnightly, with occasional breaks, so if there’s feedback that comes in, we can address it quickly. Many of the previous bugs in updates were from juggling between updates in the plugin and core, now that Gutenberg is in core it&#8217;s much easier and safer to incrementally update.</p>\n\n\n\n<h2>What about Gutenberg and accessibility? </h2>\n\n\n\n<p>We’ve had some important discussions about accessibility over the past few weeks and I am grateful for those who have helped raise these questions in the community. <br /></p>\n\n\n\n<p>Accessibility has been core to WordPress from the very beginning. It’s part of why we started – the adoption of web standards and accessibility.<br /></p>\n\n\n\n<p>But where I think we fell down was with project management &#8212; specifically, we had a team of volunteers that felt like they were disconnected from the rapid development that was happening with Gutenberg. We need to improve that. In the future I don’t know if it makes sense to have accessibility as a separate kind of process from the core development. It needs to be integrated at every single stage. <br /></p>\n\n\n\n<p>Still, we’ve accomplished a lot, as Matías <a href=\"https://make.wordpress.org/core/2018/10/18/regarding-accessibility-in-gutenberg/\">has written about</a>. There have been more than 200 closed issues related to accessibility since the very beginning. <br /></p>\n\n\n\n<p>We’re also taking the opportunity to fix some things that have had poor accessibility in WordPress from the beginning. <a href=\"https://codemirror.net/6/\">CodeMirror</a>, which is a code editor for templates, is not accessible, so we have some parts of WordPress that we really need to work on to make better. <br /></p>\n\n\n\n<p>Speaking of which, CodeMirror was seeking funding for their next version &#8212; Automattic has now <a href=\"https://codemirror.net/6/\">sponsored that funding</a> and in return it will be made available under the GPL, and that the next version of CodeMirror will be fully accessible. <br /></p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Great news ? Due to a substantial donation from <a href=\"https://twitter.com/automattic?ref_src=twsrc%5Etfw\">@automattic</a> our crowdfunding goal has been reached, and CodeMirror 6 is definitely happening!</p>&mdash; CodeMirror (@codemirror) <a href=\"https://twitter.com/codemirror/status/1054759532990218242?ref_src=twsrc%5Etfw\">October 23, 2018</a></blockquote>\n</div>\n\n\n\n<p>Finally, Automattic will be funding an accessibility study of WordPress, Gutenberg, and an evaluation of best practices across the web, to ensure WordPress is fully accessible and setting new standards for the web overall. </p>\n\n\n\n<h2>After WordPress 5.0, is the Gutenberg name going to stick around?</h2>\n\n\n\n<p>Sometimes code names can take on a life of their own. I think Gutenberg is still what we’ll call this project &#8212; it’s <a href=\"https://github.com/WordPress/gutenberg\">called that on GitHub</a>, and you’re also seeing it <a href=\"https://drupalgutenberg.org/\">adopted by other CMSes beyond WordPress</a> &#8212; but for those outside the community I can see it simply being known as “the new WordPress editor.” </p>\n\n\n\n<h2>With the adoption of React for Gutenberg, what do you see as the future for React and WordPress? </h2>\n\n\n\n<p>In 2015 I said <a href=\"https://wordpress.tv/2015/12/07/matt-mullenweg-state-of-the-word-2015/\">“Learn JavaScript deeply”</a> &#8212; then in 2016 we brought the <a href=\"https://developer.wordpress.org/rest-api/\">REST API</a> into Core. Gutenberg is the first major feature built entirely on the REST API, so if you are learning things today, learn JavaScript, and I can imagine a future wp-admin that’s 100% JavaScript talking to APIs. I’m excited to see that happen. <br /></p>\n\n\n\n<p>Now, switching to a pure JavaScript interface could break some backward compatibility, but a nice thing about Gutenberg is that it provides an avenue for all plugins to work through &#8212; it gives them a way to plug in to that. It can eliminate the need for what’s currently done in custom admin screens. &nbsp;<br /></p>\n\n\n\n<p>The other beautiful thing is that because Gutenberg essentially allows for translation into many different formats &#8212; it can publish to your web page, it can publish your RSS feed, AMP, it can publish blocks that can be translated into email for newsletters &#8212; there’s so much in the structured nature of Gutenberg and the semantic HTML that it creates and the grammar that’s used to parse it, can enable for other applications. <br /></p>\n\n\n\n<p>It becomes a little bit like a <em>lingua franca</em> that even crosses CMSes. There’s now these new cross-CMS Gutenberg blocks that will be possible. It’s not just WordPress anymore &#8212; it might be a JavaScript block that was written for Drupal that you install on your WordPress site. How would that have ever happened before? That’s why we took two years off &#8212; it’s why we’ve had everyone in the world working on this thing. It’s because we want it to be #WorthIt. <br /></p>\n\n\n\n<p>And WordPress 5.0 is just the starting line. We want to get it to that place where it’s not just better than what we have today, but a world-class, web-defining experience. It’s what we want to create and what everyone deserves. </p>\n\n\n\n<h2>Was this post published with Gutenberg?</h2>\n\n\n\n<p>Of course. <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f604.png\" alt=\"😄\" class=\"wp-smiley\" /> No bugs, but I do see lots of areas we can continue to improve and I&#8217;m excited to get to work on future iterations.</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, 29 Nov 2018 23:56:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:72:\"WPTavern: WPCampus Seeks to Raise $30K for Gutenberg Accessibility Audit\";s:7:\"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=86032\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/wpcampus-seeks-to-raise-30k-for-gutenberg-accessibility-audit\";s: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:4364:\"<p>WPCampus is <a href=\"https://wpcampus.org/2018/11/fundraising-for-wpcampus-gutenberg-accessibility-audit/\" rel=\"noopener\" target=\"_blank\">seeking funding</a> to conduct an accessibility audit of WordPress&#8217; Gutenberg editor. The non-profit organization is dedicated to helping web professionals, educators, and others who work with WordPress in higher education. Educational institutions often have stricter legal obligations that require software to be WCAG 2.0 level AA compliant and many European institutions set the bar even higher at WCAG 2.1.</p>\n<p><a href=\"https://wptavern.com/wpcampus-is-pursuing-an-independent-accessibility-audit-of-gutenberg\" rel=\"noopener\" target=\"_blank\">WPCampus moved to spearhead an audit</a> after Automattic decided to forego Matt MacPherson&#8217;s <a href=\"https://wptavern.com/gutenberg-accessibility-audit-postponed-indefinitely\" rel=\"noopener\" target=\"_blank\">proposal</a> for Gutenberg to undergo an accessibility audit. Results of the audit will help WPCampus determine any potential legal risk for institutions upgrading to WordPress 5.0 and will also identify specific challenges that Gutenberg introduces for assistive technology users and others with accessibility needs.</p>\n<p>&#8220;A professional accessibility audit is a large expense for a small nonprofit like WPCampus,&#8221; WPCampus director Rachel Cherry said. &#8220;Accessibility is important to all of us in the WordPress community. We’re asking for your help to fund the audit and ensure this important research is completed.&#8221;</p>\n<p>WPCampus is still evaluating proposals from vendors and will announce its selection soon, along with an updated timeline for completing the audit. The organization has set its funding goal at $30,000, an amount that falls in the mid-range of the proposals the selection committee has received. If the campaign raises more than the amount required, WPCampus plans to designate the funds for other accessibility-related efforts, such as future audits and live captioning at conferences.</p>\n<p>Two days after launching the campaign, WPCampus has received $3,692 (12%) towards its funding goal. The organization plans to share the results of the audit and any supporting documents on its website.</p>\n<p>The comments published on the donations page demonstrate how strongly supporters feel about getting an audit and using that information to make Gutenberg a tool that anyone can use. The topic of accessibility is close to the heart for many donating to the campaign.</p>\n<p>&#8220;When I was navigating stores with three small children, stores which helped me with automatic doors, wide aisles, and shopping carts for a crowd often made the decision for me as to whether I could shop at all,&#8221; WordPress developer <a href=\"https://robincornett.com/\" rel=\"noopener\" target=\"_blank\">Robin Cornett</a> said. &#8220;As we create content and build tools for the internet, we should be doing all we can to ensure the best online experience we can for everyone.&#8221;</p>\n<p>WordPress co-founder <a href=\"https://mikelittle.org/\" rel=\"noopener\" target=\"_blank\">Mike Little</a> also donated to the campaign, with comments on how important accessibility is to fulfilling the project&#8217;s mission.</p>\n<p>&#8220;As the platform that democratizes publishing, we can&#8217;t allow new features in WordPress to take that away from users with accessibility needs,&#8221; Little said.</p>\n<p>&#8220;Accessibility matters to everyone — injured, encumbered, distracted, disabled, everyone,&#8221; WordPress consultant <a href=\"http://adrianroselli.com\" rel=\"noopener\" target=\"_blank\">Adrian Roselli</a> said. Accessibility in WordPress matters to my clients because some of their people require it in order to use the tool and therefore stay gainfully employed.&#8221;</p>\n<p>The audit proposed months ago has evolved to become a community effort funded by passionate supporters working in various capacities throughout the WordPress ecosystem. If WPCampus is successful in funding its campaign, this particular approach has the benefit of making it a more cooperative effort with more people invested in the process than if it were funded by a single company. WPCampus aims to release the audit report to the community by January 17, 2019 but the dates will depend on the arrangement with the vendor. </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, 29 Nov 2018 22:03:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\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:92:\"WPTavern: Drupal 8.7 to Introduce Layout Builder, Contributors Face Accessibility Challenges\";s:7:\"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=85572\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"https://wptavern.com/drupal-8-7-to-introduce-layout-builder-contributors-face-accessibility-challenges\";s: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:6649:\"<p>WordPress 5.0 will soon replace the editor with the new Gutenberg editor as part of a multi-phase project to improve the experience of authoring rich content. Phase 2 will shift focus to tackle site customization, bringing more complex layout and page builder capabilities to Gutenberg.</p>\n<p>As this phase kicks off soon, it&#8217;s valuable to see what other platforms are doing on this front. Drupal has traditionally appealed to a more technical audience, and probably wouldn&#8217;t count Squarespace, Wix, and Tumblr among their competitors, but the project is getting more friendly towards site builders and content editors. Drupal has brought improvements to its usability, media, and layout experiences over the past few years in support of users who have demanded a more modern, simplified admin UI. The project is currently testing a visual design tool for building layouts.</p>\n<p>Two weeks ago, Drupal founder and project lead Dries Buytaert <a href=\"https://dri.es/why-drupal-layout-builder-is-so-unique-and-powerful\" rel=\"noopener noreferrer\" target=\"_blank\">previewed the new Layout Builder</a>, an experimental feature that is stabilizing and expected to land in Drupal 8.7 in May 2019. Layout Builder offers layouts for templated content, customizations to templated layouts, and custom pages. These uses are especially important when building sites with large amounts of content that occasionally require template overrides and one-off landing pages.</p>\n<p>Buytaert described how Layout Builder approaches the creation of one-off dynamic pages, which he said is similar to the capabilities found in services such as Squarespace and projects like Gutenberg for WordPress and Drupal: </p>\n<blockquote><p>A content author can start with a blank page, design a layout, and start adding blocks. These blocks can contain videos, maps, text, a hero image, or custom-built widgets (e.g. a Drupal View showing a list of the ten most popular gift baskets). Blocks can expose configuration options to the content author. For instance, a hero block with an image and text may offer a setting to align the text left, right, or center. These settings can be configured directly from a sidebar.</p></blockquote>\n<p>Buytaert&#8217;s demo video shows the Layout Builder in action. Its capabilities are similar to many of WordPress&#8217; third-party page builders, such as <a href=\"https://elementor.com/theme-builder/\" rel=\"noopener noreferrer\" target=\"_blank\">Elementor</a> and <a href=\"https://www.wpbeaverbuilder.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Beaver Builder</a>.</p>\n<p></p>\n<h3>Layout Builder Poses Accessibility Challenges</h3>\n<p>Layout Builder is anchored on one of Drupal&#8217;s stronger features &#8211; the ability to create structured content, but it faces some of the same accessibility challenges that WordPress&#8217; Gutenberg editor has encountered. </p>\n<p>In his post introducing Layout Builder, Buytaert made some pointed remarks about Drupal&#8217;s commitment to accessibility:</p>\n<blockquote><p>Accessibility is one of Drupal&#8217;s core tenets, and building software that everyone can use is part of our core values and principles. A key part of bringing Layout Builder functionality to a &#8220;stable&#8221; state for production use will be ensuring that it passes our accessibility gate (Level AA conformance with WCAG and ATAG). This holds for both the authoring tool itself, as well as the markup that it generates. We take our commitment to accessibility seriously.</p></blockquote>\n<p>Some contributors are not as optimistic about Drupal being able to fulfill these bold claims in time to ship the feature in 8.7.0. Andrew Macpherson, one of the accessibility topic maintainers for Drupal 8 core, has <a href=\"https://www.drupal.org/project/drupal/issues/3007978#comment-12853731\" rel=\"noopener\" target=\"_blank\">proposed Layout Builder offer an alternative UI</a> that users can access without the visual preview UI.</p>\n<p>&#8220;Dries&#8217; blog post about layout builder yesterday says we&#8217;re on track to mark this as stable for D8.7.0,&#8221; Macpherson said. &#8220;I&#8217;m not at all optimistic about that, because as yet there is no feasible plan for how it can be made accessible.</p>\n<p>&#8220;A minimum viable product for Layout Builder accessibility would be at least one method which works, for each user task, for each input/output method. I don&#8217;t think we can say we have found a feasible approach. We&#8217;re in deeply experimental territory here &#8211; there isn&#8217;t a well-established, reliable pattern we can just copy to make the current layout builder accessible. Essentially, we&#8217;re making stuff up in a hurry, for a novel UI, with limited opportunity for design validation. There&#8217;s no guarantee that users are going to understand it, or find it easy to use. That&#8217;s why I&#8217;m not optimistic about it getting past the accessibility gate in time for D8.7.0.&#8221;</p>\n<p>Macpherson said that WCAG strongly advises against providing alternate versions but allows for them in instances where the main version cannot be made accessible.</p>\n<p>&#8220;I think we are effectively in this situation now, although we are still exploring ideas,&#8221; he said. </p>\n<p>Macpherson also recommended they continue striving to make the drag-and-drop, visual-preview layout builder UI accessible at the same time. He referenced emerging <a href=\"https://inclusivedesignprinciples.org/#offer-choice\" rel=\"noopener\" target=\"_blank\">principles of Inclusive Design</a> for application developers, which recommend &#8220;offering choice,&#8221; giving users different ways of completing tasks, especially those that may be complex or non-standard.</p>\n<p>&#8220;Eventually, I&#8217;d like to see BOTH layout builder UIs being accessible, and offer genuinely useful choices for everyone,&#8221; Macpherson said. &#8220;But let&#8217;s take the time to do it well, instead of hastily bolting on fixes for one type of interaction method at a time, in a rush to ship a single layout builder UI. &#8221;</p>\n<p>Macpherson&#8217;s proposal is still under consideration, but it provides an interesting perspective on similar challenges WordPress contributors are facing with Gutenberg. Modernizing UIs to make the site building experience more accessible for those who don&#8217;t know how to code has to be balanced with considerations for those who may not be able see very well or use a mouse. Drupal contributors are exploring providing an alternative accessible UI as a solution to empower more users to take advantage of the new Layout Builder.</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, 29 Nov 2018 04:31:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:106:\"WPTavern: WPWeekly Episode 339 – Interview With Pippin Williamson, Founder of Sandhills Development, LLC\";s:7:\"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=86062&preview=true&preview_id=86062\";s:7:\"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:111:\"https://wptavern.com/wpweekly-episode-339-interview-with-pippin-williamson-founder-of-sandhills-development-llc\";s: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:1455:\"<p>In this episode, <a href=\"http://jjj.me\">John James Jacoby</a> and I are joined by <a href=\"http://pippin.com/\">Pippin Williamson</a>, founder of <a href=\"http://sandhillsdev.com/\">Sandhills Development</a>, LLC. Pippin describes what he&#8217;s learned going through the process of opening a brick and mortar business.</p>\n<p>He also describes the emotional process of firing employees, making business decisions as a team, and how he wants to create a life-long company where employees stick around for decades.</p>\n<p>Near the end of the episode, Pippin expresses his opinions on Gutenberg the product and Gutenberg the process. You might be surprised by what he has to say.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"https://pippinsplugins.com/2017-in-review/\">2017 in review</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, December 5th 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 #339:</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:\"Wed, 28 Nov 2018 19:54:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:65:\"WPTavern: SyntaxHighlighter Evolved Plugin Adds Gutenberg Support\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=85968\";s:7:\"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/syntaxhighlighter-evolved-plugin-adds-gutenberg-support\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4743:\"<p>WordPress 5.0 will ship with a code block in the new editor but it doesn&#8217;t include syntax highlighting. The code is currently wrapped in pre tags. During the earlier days of Gutenberg&#8217;s development, the HTML block had syntax highlighting but the team was not satisfied with its implementation and decided to pull it until they could <a href=\"https://github.com/WordPress/gutenberg/issues/10423\" rel=\"noopener\" target=\"_blank\">provide more consistent behavior across blocks</a>. </p>\n<p>For now, users will have to depend on a plugin to get syntax highlighting. <a href=\"https://wordpress.org/plugins/syntaxhighlighter/\" rel=\"noopener\" target=\"_blank\">SyntaxHighlighter Evolved</a> is one of the first plugins of its kind to add Gutenberg support via its own block. </p>\n<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-28-at-10.08.36-AM.png?ssl=1\"><img /></a></p>\n<p>The plugin currently adds syntax highlighting to source code on the frontend only. Nevertheless, it&#8217;s a great use case for Gutenberg, as the plugin previously required you to remember how to structure the shortcode in a particular way in order to use it. </p>\n<p>Ian Dunn <a href=\"https://github.com/Viper007Bond/syntaxhighlighter/pull/78\" rel=\"noopener\" target=\"_blank\">contributed the Gutenberg support</a> for SyntaxHighlighter Evolved. In the PR for this feature, Dunn said he wanted to give existing users a way to continue using the plugin after WordPress 5.0 is released:</p>\n<blockquote><p>\nThe syntax highlighting only works on the front end, due to the nature of SyntaxHighlighter. Details are documented in the edit() function&#8217;s docblock.</p>\n<p>Because of that, this isn&#8217;t the ideal syntax highlighting block[1], but this provides a way for existing users to continue using the plugin without having to migrate old posts to a different plugin.</p>\n<p>Another limitation is that this PR only supports the language attribute of the shortcode, because I ran out of time/energy. This lays the groundwork, though, so the rest of them can easily be added in a future iteration.</p></blockquote>\n<p>SyntaxHighlighter Evolved is active on more than 40,000 installations and is also used on WordPress.com, so this update to the plugin should help those who rely on it to be able to use the new Gutenberg editor without having to switch back to the old editor when they need to add code to their content.</p>\n<p>There is still some debate about the best way to provide syntax highlighting in Gutenberg. Another implementation called <a href=\"https://github.com/mkaz/code-syntax-block\" rel=\"noopener\" target=\"_blank\">Code Syntax Block</a> by Marcus Kazmierczak, extends Gutenberg&#8217;s existing code block to offer syntax highlighting, instead of creating a new block for it. It also uses <a href=\"http://prismjs.com/\" rel=\"noopener\" target=\"_blank\">PrismJS syntax highlighter</a>.</p>\n<p><a href=\"https://github.com/cedaro/shiny-code\" rel=\"noopener\" target=\"_blank\">Shiny Code</a> is another approach that adds a new block for code and provides a preview inside the Gutenberg editor. </p>\n<p><a href=\"https://cloudup.com/cAjq1AKskL8\"><img src=\"https://i1.wp.com/cldup.com/2MLWW0oXx3.gif?resize=627%2C308&ssl=1\" alt=\"Shiny code\" width=\"627\" height=\"308\" /></a></p>\n<p>In the official plugin directory, the <a href=\"https://wordpress.org/plugins/enlighter/\" rel=\"noopener\" target=\"_blank\">Enlighter</a> plugin, which has 10,000 active installs, offers experimental support for Gutenberg that is being <a href=\"https://github.com/EnlighterJS/Plugin.Gutenberg\" rel=\"noopener\" target=\"_blank\">actively developed on GitHub</a>. <a href=\"https://wordpress.org/plugins/kebo-code/\" rel=\"noopener\" target=\"_blank\">Kebo Code</a>, a relatively new plugin with fewer than 10 installs, was created to offer syntax highlighting for Gutenberg and currently supports 121 languages and two themes. Users will have to switch to the frontend to see the code rendered with the theme selected. </p>\n<p>SyntaxHighlighter Evolved does not yet provide a way for highlighting existing code blocks or transforming a core code block to use the plugin&#8217;s syntax highlighting. Converting all existing code blocks might take some time for those who have been using it extensively. Alex Mills, the plugin&#8217;s author, said he is considering all of these issues and welcomes patches on the <a href=\"https://github.com/Viper007Bond/syntaxhighlighter\" rel=\"noopener\" target=\"_blank\">GitHub repository for the plugin</a>. Plugin authors may change their approaches over time, depending on where Gutenberg goes in the future, so users will want to evaluate available plugins periodically to see which ones suit their needs.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 28 Nov 2018 17:10:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:59:\"WPTavern: WordCamp US 2018 Livestream Tickets 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:29:\"https://wptavern.com/?p=85848\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wptavern.com/wordcamp-us-2018-livestream-tickets-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:1353:\"<a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2016/11/nashville.jpg?ssl=1\"><img /></a>photo credit: Viv Lynch <a href=\"http://www.flickr.com/photos/68894626@N00/30070498810\">Westward</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nc-nd/2.0/\">(license)</a>\n<p>The countdown has started for <a href=\"https://2018.us.wordcamp.org\" rel=\"noopener\" target=\"_blank\">WordCamp US 2018</a> in Nashville. The event is just 10 days away. If you cannot attend, watching via the livestream is the next best option. Anyone can join the livestream for free, but viewers will need to <a href=\"https://2018.us.wordcamp.org/tickets/\" rel=\"noopener\" target=\"_blank\">sign up for a ticket</a> on the event website. </p>\n<p>This year&#8217;s <a href=\"https://2018.us.wordcamp.org/schedule/\" rel=\"noopener\" target=\"_blank\">schedule</a> includes sessions in two tracks: Banjo and Guitar. Matt Mullenweg&#8217;s annual <a href=\"https://2018.us.wordcamp.org/2018/11/27/state-of-the-word-2018/\" rel=\"noopener\" target=\"_blank\">State of the Word</a> address is scheduled for Saturday, December 8, at 4:00 p.m. CST. Livestream ticket holders can tune in to any of the sessions and may also want to participate in the conversations on Twitter using the <a href=\"https://twitter.com/hashtag/WCUS?src=hash\" rel=\"noopener\" target=\"_blank\">#WCUS hashtag</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, 27 Nov 2018 22:09: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:41:\"BuddyPress: BuddyPress 4.0.0 “Pequod”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=282222\";s:7:\"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:55:\"https://buddypress.org/2018/11/buddypress-4-0-0-pequod/\";s: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:5882:\"<p>BuddyPress 4.0.0 &#8220;Pequod&#8221; is now available!</p>\n<h3>A focus on data privacy and control</h3>\n<p>BuddyPress boasts a proud history of letting community members and managers control their data, independent of third-party, commercial entities. In this spirit, as well as the spirit of recent regulations like the EU&#8217;s General Data Protection Regulation (GDPR), Expanding on some of the tools introduced by WordPress in version 4.9.8, BuddyPress 4.0 introduces a suite of tools allowing users and site admins to manage member data and privacy.</p>\n<div id=\"attachment_282223\" class=\"wp-caption alignnone\"><a href=\"https://buddypress.org/wp-content/uploads/1/2018/11/data-export.png\"><img class=\"size-full wp-image-282223\" src=\"https://buddypress.org/wp-content/uploads/1/2018/11/data-export.png\" alt=\"Screenshot of \" /></a><p class=\"wp-caption-text\">Giving your users greater control over their data</p></div>\n<p>The new &#8220;Export Data&#8221; Settings panel lets users request an export of all BuddyPress data they&#8217;ve created. BuddyPress integrates seamlessly with the data export functionality introduced in WordPress 4.9.8, and BP data is included in exports that are initiated either from the Export Data panel or via WP&#8217;s Tools &gt; Export Personal Data interface.</p>\n<p>BuddyPress 4.0 also integrates with WordPress 4.9.8&#8217;s Privacy Policy tools. When you create or update your Privacy Policy, BP will suggest text that&#8217;s specifically tailored to the kinds of social data generated on a BuddyPress site. And will prompt registering users to agree to the Privacy Policy, if your theme supports it.</p>\n<p>We&#8217;ve also done a complete review of BuddyPress&#8217;s cookie behavior, and dramatically reduced the number of cookies needed to browse a BP-powered site &#8211; especially for logged-out users. We&#8217;re confident that this change will help site owners comply with local privacy regulations.</p>\n<h3>Nouveau and other improvements</h3>\n<p>The BuddyPress team has been hard at work improving the Nouveau template pack introduced in BuddyPress 4.0. We&#8217;ve improved accessibility, extensibility, and responsiveness on mobile devices.</p>\n<p>BuddyPress 4.0 also contains a number of internal improvements that improve compatibility with various version of PHP, fix formatting and content issues when sending emails, and address some backward-compatibility concerns.</p>\n<h3>Mille grazie</h3>\n<p>As usual, this BuddyPress release is only possible thanks to the contributions of the community. Special thanks to the following folks who contributed code and testing to the release: <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha (xknown)</a>, <a href=\"https://profiles.wordpress.org/ankit-k-gupta/\">Ankit K Gupta (ankit-k-gupta)</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone B Gorges (boonebgorges)</a>, <a href=\"https://profiles.wordpress.org/sbrajesh/\">Brajesh Singh (sbrajesh)</a>, <a href=\"https://profiles.wordpress.org/brianbws/\">Brian Cruikshank (brianbws)</a>, <a href=\"https://profiles.wordpress.org/needle/\">Christian Wach (needle)</a>, <a href=\"https://profiles.wordpress.org/cyberwani/\">Dinesh Kesarwani (cyberwani)</a>, <a href=\"https://profiles.wordpress.org/dipesh.kakadipa/\">dipeshkakadiya</a>, <a href=\"https://profiles.wordpress.org/drywallbmb/\">drywallbmb</a>, <a href=\"https://profiles.wordpress.org/dullowl/\">dullowl</a>, <a href=\"https://profiles.wordpress.org/eric01/\">Eric (eric01)</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse/\">Garrett Hyder (garrett-eclipse)</a>, <a href=\"https://profiles.wordpress.org/harshall/\">Harshal Limaye (harshall)</a>, <a href=\"https://profiles.wordpress.org/hnla/\">Hugo (hnla)</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby (johnjamesjacoby)</a>, <a href=\"https://profiles.wordpress.org/marcella1981/\">Marcella (marcella1981)</a>, <a href=\"https://profiles.wordpress.org/imath/\">Mathieu Viet (imath)</a>, <a href=\"https://profiles.wordpress.org/mercime/\">mercime</a>, <a href=\"https://profiles.wordpress.org/MorgunovVit/\">MorgunovVit</a>, <a href=\"https://profiles.wordpress.org/n0barcode/\">n0barcode</a>, <a href=\"https://profiles.wordpress.org/pareshradadiya/\">paresh.radadiya (pareshradadiya)</a>, <a href=\"https://profiles.wordpress.org/DJPaul/\">Paul Gibbs (DJPaul)</a>, <a href=\"https://profiles.wordpress.org/pooja1210/\">Pooja N Muchandikar (pooja1210)</a>, <a href=\"https://profiles.wordpress.org/r-a-y/\">r-a-y</a>, <a href=\"https://profiles.wordpress.org/espellcaste/\">Renato Alves (espellcaste)</a>, <a href=\"https://profiles.wordpress.org/RT77/\">RT77</a>, <a href=\"https://profiles.wordpress.org/cyclic/\">Ryan Williams (cyclic)</a>, <a href=\"https://profiles.wordpress.org/elhardoum/\">Samuel Elh (elhardoum)</a>, <a href=\"https://profiles.wordpress.org/shubh14/\">shubh14</a>, <a href=\"https://profiles.wordpress.org/spdustin/\">spdustin</a>, <a href=\"https://profiles.wordpress.org/suvikki/\">suvikki</a>, <a href=\"https://profiles.wordpress.org/netweb/\">Stephen Edgar (netweb)</a>, <a href=\"https://profiles.wordpress.org/thejimmy/\">thejimmy</a>, <a href=\"https://profiles.wordpress.org/vapvarun/\">vapvarun</a>, <a href=\"https://profiles.wordpress.org/wbcomdesigns/\">Wbcom Designs (wbcomdesigns)</a>, <a href=\"https://profiles.wordpress.org/yahil/\">Yahil Madakiya (yahil)</a></p>\n<p>This version of BuddyPress is code-named &#8220;Pequod&#8221; after the famous <a href=\"https://pequodspizza.com/\">Pequod&#8217;s Pizza</a> in Chicago, where the crust really is caramelized, and the dish really is deep. Buon gusto!</p>\n<h3>Keep on truckin&#8217;</h3>\n<p>Questions or comments about the release? Visit the <a href=\"https://buddypress.org/support/\">buddypress.org support forums</a>, or open a ticket on <a href=\"https://buddypress.trac.wordpress.org\">our bugtracker</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, 27 Nov 2018 19:57:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Boone Gorges\";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:90:\"WPTavern: Jetpack 6.8 Adds Gutenberg Blocks for Payment Buttons, Forms, Maps, and Markdown\";s:7:\"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=85576\";s:7:\"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/jetpack-6-8-adds-gutenberg-blocks-for-payment-buttons-forms-maps-and-markdown\";s: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:3613:\"<p><a href=\"https://jetpack.com/2018/11/27/jetpack-6-8-building-jetpack-for-the-new-wordpress-editor/\" rel=\"noopener\" target=\"_blank\">Jetpack 6.8</a> was released today, introducing the plugin&#8217;s first set of blocks for Gutenberg. The necessary infrastructure was added in version 6.6 and all existing features that touch the editor are in the process of being ported over to blocks. This release includes blocks for payment buttons, forms, maps, and markdown.</p>\n<p>The Contact Form module is one of the plugin&#8217;s most popular features and one that users often enable on new websites. This block removes a major barrier to implementing a form on WordPress sites &#8211; new users will have no need to try to understand the concept of shortcodes in order to collect feedback on their sites. Creating a new form essentially works like adding blocks inside of blocks:</p>\n<p><a href=\"https://cloudup.com/cNVMNF2ZGd8\"><img src=\"https://i2.wp.com/cldup.com/LZmv0Xj_Iq.gif?resize=627%2C568&ssl=1\" alt=\"Form\" width=\"627\" height=\"568\" /></a></p>\n<p>The <a href=\"https://jetpack.com/support/jetpack-blocks/simple-payments-block/\" rel=\"noopener\" target=\"_blank\">Simple Payments button block</a> is slightly different in that it already has the form fields set up so the user can fill them out for whatever they are selling. This block is available for users on the Jetpack Premium or Professional plan.</p>\n<p>The <a href=\"https://jetpack.com/support/jetpack-blocks/map-block/\" rel=\"noopener\" target=\"_blank\">map block</a> makes it easy for users to embed an interactive map within the content of posts or pages. After <a href=\"https://www.mapbox.com/signup/\" rel=\"noopener\" target=\"_blank\">signing up for a free Mapbox Access Token</a>, users can select a location directly inside the new editor and preview it live with different map theme options and a color-picker for the marker.</p>\n<p><a href=\"https://cloudup.com/cUFrJDi-tqy\"><img src=\"https://i2.wp.com/cldup.com/NL4okuVN0s.gif?resize=627%2C338&ssl=1\" alt=\"Map\" width=\"627\" height=\"338\" /></a></p>\n<p>Some of those who have tested Gutenberg may not be a fan of its current writing interface, but after you see some of these blocks in action for things like maps and payment buttons, it&#8217;s clear that this is a superior interface for these content types. Modernizing the interface for content that previously relied on shortcodes is where Gutenberg truly excels right now.</p>\n<p>Development on the Gutenberg plugin has been so active that it makes sense that the Jetpack team waited until WordPress 5.0 RC to release any blocks. Jetpack users can take advantage of them now if they have Gutenberg installed, or wait until 5.0 is officially released. The Jetpack team is also working on a number of other blocks for existing features. You can <a href=\"https://github.com/Automattic/jetpack/labels/Gutenberg\" rel=\"noopener\" target=\"_blank\">follow the progress</a> on upcoming blocks at Jetpack&#8217;s GitHub repository and log issues with blocks that have already been released.</p>\n<p>Jetpack 6.8 also restores the Publicize module to the pre-publish sidebar, so users can continue automatically sharing posts after WordPress 5.0 is released. This version ensures compatibility with Jetpack&#8217;s widgets for those using the Twenty Nineteen theme. Check out the <a href=\"https://wp.me/p1moTy-cee\" rel=\"noopener\" target=\"_blank\">release post</a> to see more blocks in action and the <a href=\"https://wordpress.org/plugins/jetpack/#developers\" rel=\"noopener\" target=\"_blank\">changelog</a> for a full list of all the enhancements and bug fixes.</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, 27 Nov 2018 17:52:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:79:\"WPTavern: WordPress 5.0 RC 1 Released, Gutenberg Passes 1 Million Installations\";s:7:\"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=85923\";s:7:\"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/wordpress-5-0-rc-1-released-gutenberg-passes-1-million-installations\";s: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:5988:\"<p><a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-release-candidate/\" rel=\"noopener\" target=\"_blank\">WordPress 5.0 RC 1</a> was released over the weekend after a string of five betas that began in late October. According to the <a href=\"https://gutenstats.blog/\" rel=\"noopener\" target=\"_blank\">Gutenberg stats page</a>, more than 1.1 million sites have the Gutenberg plugin installed and users have written more than 980,000 posts using the new editor. These numbers are conservative estimates, as the numbers only include WordPress.com sites and sites running Jetpack.</p>\n<p>Most of the changes included in the RC were outlined in the <a href=\"https://make.wordpress.org/core/2018/11/20/whats-new-in-gutenberg-20th-november/\" rel=\"noopener\" target=\"_blank\">Gutenberg 4.5</a> release post last week. An update published today shows 12 PRs waiting for review in the 4.6 milestone, 14 open issues in the 5.0.0 milestone, and more than 150 issues open in 5.0.1 and subsequent releases. <a href=\"https://make.wordpress.org/core/tag/5.0+dev-notes/\" rel=\"noopener\" target=\"_blank\">Dev notes for 5.0</a> have been published and tagged on the make.wordpress.org/core blog.</p>\n<p>WordPress 5.0&#8217;s official release date was set for November 27 but after further evaluation the date has been <a href=\"https://make.wordpress.org/core/2018/11/21/5-0-gutenberg-status-update-nov-21/\" rel=\"noopener\" target=\"_blank\">pushed back</a>. Last week WordPress core core committers, contributors, and former release leads made strong, last-minute <a href=\"https://wptavern.com/wordpress-5-0-rc-expected-on-u-s-thanksgiving-holiday-despite-last-minute-pushback-from-contributors\" rel=\"noopener\" target=\"_blank\">appeals</a> to hold off RC and defer the release to January. Development is moving forward desipite the pushback. A new release date has not yet been announced. The current plan is to monitor feedback on the RC and the team will make a decision from there.</p>\n<h3>Mullenweg Responds to Critics on Twitter, Reiterates Vision for Gutenberg</h3>\n<p>Over the weekend, Matt Mullenweg responded to critics on Twitter who voiced concerns about his leadership and communication throughout WordPress 5.0&#8217;s development. One particular post titled &#8220;<a href=\"https://cameronjonesweb.com.au/blog/lets-take-a-very-serious-look-at-gutenberg/\" rel=\"noopener\" target=\"_blank\">Let’s Take A Very Serious Look At Gutenberg</a>,&#8221; written by WordPress developer Cameron Jones, sparked conversation. In response to Cliff Seal, who urged Mullenweg to &#8220;re-cast the vision of WordPress in a way that accounts for the apparent urgency of this effort,&#8221; Mullenweg <a href=\"https://twitter.com/photomatt/status/1066397086206304256\" rel=\"noopener\" target=\"_blank\">responded</a>:</p>\n<blockquote><p>\nMany people who try to start publishing with WordPress fail; those who don&#8217;t struggle with shortcodes, embeds, widgets; those who can toggle to code view to do basic tasks in the editor, and for clients set up elaborate meta-field and CPT based schemes to avoid catastrophe.</p>\n<p>Gutenberg aims to solve these problems, improve the WP experience for all its users, and open up independent, open source, beautiful publishing on the web to a class of users that couldn&#8217;t publish with WordPress before.</p>\n<p>It may seem rushed to people unused to this pace of development and improvement in the WordPress world. However this has been a pace sustained for almost two years now, and we still look slow compared to some modern software. Speed of iteration is enabled by the new tech stack.</p>\n<p>It bothers me at a deep, moral level to hold back a user experience that will significantly upgrade the publishing ability and success of tens or hundreds of millions of users. It hasn&#8217;t been ready (for core) yet, so it&#8217;s not released. I hope it will be soon! </p>\n<p>This may all look very quaint in retrospect, when we look back three or five years from now. It&#8217;s a tough transition but the foundation Gutenberg enables will be worth it.</p></blockquote>\n<p>Matt Medeiros, another vocal critic of Mullenweg&#8217;s leadership on WordPress 5.0, <a href=\"https://www.youtube.com/watch?v=W1Rhr9Y54ck\" rel=\"noopener\" target=\"_blank\">recorded a video</a>, expounding on his concerns about transparency and the rushed pace. He summarized the frustrations that inspired him to make the video.</p>\n<p>&#8220;While I agree WordPress needs innovation to reach new users that desperately require freedom over their content, especially within the context of today&#8217;s social networks, I don&#8217;t agree and am also discouraged by Matt not sharing the product vision with the community,&#8221; Medeiros said. &#8220;It&#8217;s polarizing to build software under the guise of openness with a mission to democratize publishing, but not give the same people volunteering to &#8216;Five for the Future&#8217; a voice for the future. </p>\n<p>&#8220;Lack of communication, not Gutenberg or the team developing it, has lead to the current divide and we&#8217;re left asking &#8212; why? WordPress has always had a branding problem and this continues to muddy the lines between open source project and WordPress the &#8216;product.\'&#8221;</p>\n<p>The 5.0 release is heading into the home stretch but Gutenberg has several phases ahead with many more years of development. Mullenweg&#8217;s responses on Twitter over the weekend indicate he is interested in keeping the lines of communication open throughout the process. He said he plans to dedicate more time to responding directly to feedback.</p>\n<p>&#8220;One thing will try: I’m going to open up some listening office hours in the next week so people can talk directly,&#8221; Mullenweg <a href=\"https://twitter.com/photomatt/status/1065981341496471555\" rel=\"noopener\" target=\"_blank\">said</a>. &#8220;I want everyone to be and feel heard, as they have been since the beginning of this process in 2016.&#8221;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 27 Nov 2018 01:54:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:10;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"Dev Blog: WordPress 5.0 Release Candidate\";s:7:\"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=6257\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2018/11/wordpress-5-0-release-candidate/\";s: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:5355:\"<p>The first release candidate for WordPress 5.0 is now available!</p>\n\n\n\n<p>This is an important milestone, as we near the release of WordPress 5.0.&nbsp;<strong>The WordPress 5.0 release date has shifted from the 27th to give more time for the RC to be fully tested</strong>. A final release date will be announced soon, based on feedback on the RC. This is a big release and needs <em>your</em> help—if you haven’t tried 5.0 yet, now is the time!&nbsp;</p>\n\n\n\n<p>To test WordPress 5.0, you can use the&nbsp;<a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;plugin or you can&nbsp;<a href=\"https://wordpress.org/wordpress-5.0-RC1.zip\">download the release candidate here</a>&nbsp;(zip).</p>\n\n\n\n<h2>What&#8217;s in WordPress 5.0?</h2>\n\n\n\n<img src=\"https://i1.wp.com/wordpress.org/news/files/2018/11/Gutenberg-3.png?resize=632%2C316&ssl=1\" alt=\"Screenshot of the new block editor interface.\" class=\"wp-image-6271\" />The new block-based post editor.\n\n\n\n<p>WordPress 5.0 introduces the <a href=\"https://wordpress.org/gutenberg/\">new block-based post editor</a>. This is the first step toward an exciting new future with a streamlined editing experience across your site. You’ll have more flexibility with how content is displayed, whether you are building your first site, revamping your blog, or write code for a living.</p>\n\n\n\n<p>The block editor is&nbsp;<a href=\"https://gutenstats.blog/\">used on over a million sites</a>, we think it&#8217;s ready to be used on all WordPress sites. We do understand that some sites might need some extra time, though. If that&#8217;s you, please install the <a href=\"https://wordpress.org/plugins/classic-editor/\">Classic Editor plugin</a>, you&#8217;ll continue to use the classic post editor when you upgrade to WordPress 5.0.</p>\n\n\n\n<p>Twenty Nineteen is WordPress&#8217; new default theme, it&nbsp;features custom styles for the blocks available by default in 5.0.&nbsp;Twenty Nineteen is designed to work for a wide variety of use cases. Whether you’re running a photo blog, launching a new business, or supporting a non-profit, Twenty Nineteen is flexible enough to fit your needs.</p>\n\n\n\n<p>The block editor is a big change, but that&#8217;s not all. We&#8217;ve made some smaller changes as well,&nbsp; including:</p>\n\n\n\n<ul><li>All of the previous default themes, from Twenty Ten through to Twenty Seventeen, have been updated to support the block editor.</li><li>You can improve the accessibility of the content you write, now that <a href=\"https://core.trac.wordpress.org/ticket/30421\">simple ARIA labels</a>&nbsp;can be saved in posts and pages.</li><li>WordPress 5.0 officially supports the upcoming PHP 7.3 release: if you&#8217;re using an older version, we encourage you to <a href=\"https://wordpress.org/support/upgrade-php/\">upgrade PHP</a>&nbsp;on your site.</li><li>Developers can now add translatable strings directly to your JavaScript code, using the new <a href=\"https://make.wordpress.org/core/2018/11/09/new-javascript-i18n-support-in-wordpress/\">JavaScript language packs</a>.</li></ul>\n\n\n\n<p>You can read more about the fixes and changes since  Beta 5 <a href=\"https://make.wordpress.org/core/2018/11/20/whats-new-in-gutenberg-20th-november/\">in the last update post</a>.</p>\n\n\n\n<p>For more details about what’s new in version 5.0, check out the&nbsp;<a href=\"https://wordpress.org/news/2018/10/wordpress-5-0-beta-1/\">Beta 1</a>,&nbsp;<a href=\"https://wordpress.org/news/2018/10/wordpress-5-0-beta-2/\">Beta 2</a>,&nbsp;<a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-3/\">Beta 3</a>, <a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-4/\">Beta 4</a> and&nbsp;<a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-5/\">Beta 5</a>&nbsp;blog posts.</p>\n\n\n\n<h2>Plugin and Theme Developers</h2>\n\n\n\n<p>Please test your plugins and themes against WordPress 5.0 and update the&nbsp;<em>Tested up to</em>&nbsp;version in the readme to 5.0. If you find compatibility problems, please be sure to post to the <a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a> so we can figure those out before the final release. An in-depth field guide to developer-focused changes is coming soon on the&nbsp;<a href=\"https://make.wordpress.org/core/\">core development blog</a>. In the meantime, you can review the&nbsp;<a href=\"https://make.wordpress.org/core/tag/5.0+dev-notes/\">developer notes for 5.0</a>.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a>&nbsp;</p>\n\n\n\n<p><strong><em>If you think you’ve found a bug</em></strong><em>, you can post to the&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>Alpha/Beta area</em></a><em>&nbsp;in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>file one on WordPress Trac</em></a><em>, where you can also find&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>a list of known bugs</em></a><em>.</em></p>\n\n\n\n<p class=\"has-background has-medium-font-size\"><em>Ruedan los bloques<br />Contando vivos cuentos<br />Que se despiertan</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, 23 Nov 2018 09:46:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matias Ventura\";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:112:\"WPTavern: WordPress 5.0 RC Expected on U.S. Thanksgiving Holiday, despite Last-Minute Pushback from Contributors\";s:7:\"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=85784\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/wordpress-5-0-rc-expected-on-u-s-thanksgiving-holiday-despite-last-minute-pushback-from-contributors\";s: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:9937:\"<a href=\"https://i0.wp.com/wptavern.com/wp-content/uploads/2017/10/ship-bottle.jpg?ssl=1\"><img /></a>photo credit: KaylaKandzorra <a href=\"http://www.flickr.com/photos/48077358@N02/4952091078\">i miss you grampa.</a> &#8211; <a href=\"https://creativecommons.org/licenses/by/2.0/\">(license)</a>\n<p>WordPress core committers, core contributors, and former release leads made strong, last-minute <a href=\"https://make.wordpress.org/core/2018/11/19/5-0-gutenberg-status-update-nov-19/\" rel=\"noopener noreferrer\" target=\"_blank\">appeals</a> on Monday for the 5.0 release to be deferred to January. RC was expected Monday but those urging its delay cited the large number of open issues on the milestone and the fact that many confirmed bugs are being aggressively punted to followup releases.  </p>\n<p>&#8220;I do not see how we can seriously ship a release candidate today,&#8221; Joe McGill said. &#8220;In doing so, we are either saying we’re ok with shipping a major version of WordPress with this many known issues, or that the term &#8216;release candidate&#8217; does not actually have meaning. I would suggest that we revise the schedule to push back RC for at least 4 weeks so we have a reasonable deadline and, in the mean time, continue releasing betas.&#8221;</p>\n<p>Nearly every contributor involved in the discussion was enthusiastic about Gutenberg but urged release lead Matt Mullenweg to allow for four weeks of RC and code freeze to give the community to prepare. </p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">&#8211; Building site with Gutenberg<br />&#8211; Find bug, go to GH to file an issue <br />&#8211; Find the ticket already exists.<br />&#8211; Bug has already been punted to \"5.0.x Follow Ups\"<br />&#8211; Find all the other *known* bugs planned for 5.0 launch</p>\n<p>:(<a href=\"https://t.co/EiXR8tgHnz\">https://t.co/EiXR8tgHnz</a></p>\n<p>&mdash; Bill Erickson (@BillErickson) <a href=\"https://twitter.com/BillErickson/status/1064619368045252608?ref_src=twsrc%5Etfw\">November 19, 2018</a></p></blockquote>\n<p></p>\n<p>Contributors said they don&#8217;t understand the rush to get 5.0. Several noted that Gutenberg seems to be measured by a different rod of success than previous releases where headline features were held to a different standard in regards to shipping known bugs. </p>\n<p>&#8220;We’re fast approaching a million (Jetpack tracked) posts made through the editor, with the non-tracked number probably a multiple of that,&#8221; Mullenweg said in response to contributors&#8217; concerns. &#8220;There’s been an explosion of plugins building on top of Gutenberg and some things like the work ACF and Block Lab have done that seem really transformational for WordPress. For those whom the editor is not a good fit they can opt in at any point, including post-5.0, to Classic and continue using WP exactly as they had before until at least 2022 and likely beyond.&#8221; </p>\n<p>Mullenweg identified a few questions he sees as &#8220;good measures of success for Gutenberg:&#8221;</p>\n<ul>\n<li>Are people, when given the choice, choosing to use it over the old editor?</li>\n<li>Can they create things they weren’t able to create before?</li>\n<li>Are new-to-WP users more successful (active, happy with what they create) than pre-Gutenberg?</li>\n<li>Are interesting things being built on top of it?</li>\n</ul>\n<p>Interesting plugins are being built on top of Gutenberg but they are breaking with every release of the plugin. Gutenberg 4.5 was released yesterday, matching the first 5.0 RC feature set. It includes a large number of changes and bug fixes that have gone relatively untested by the community at large. Most notably, 4.5 introduced a regression that caused a <a href=\"https://github.com/WordPress/gutenberg/issues/12148\" rel=\"noopener noreferrer\" target=\"_blank\">white screen of death when trying to load custom post types</a> in the classic editor, forcing a 4.5.1 release earlier in the day. Every release introduces changes that cause plugins to break, requiring immediate updates from plugin developers.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Our new <a href=\"https://twitter.com/hashtag/gutenberg?src=hash&ref_src=twsrc%5Etfw\">#gutenberg</a> development cycle<br />1) New version of GB is released<br />2) We cross our fingers<br />3) Find out GB breaks stuff<br />4) Fix GB issues<br />5) Issue release<br />6) New version of GB released<br />repeat process <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f613.png\" alt=\"😓\" class=\"wp-smiley\" /></p>\n<p>&mdash; pootlepress (@pootlepress) <a href=\"https://twitter.com/pootlepress/status/1065146009964212225?ref_src=twsrc%5Etfw\">November 21, 2018</a></p></blockquote>\n<p></p>\n<p>Gutenberg technical lead Matias Ventura posted an <a href=\"https://make.wordpress.org/core/2018/11/21/5-0-gutenberg-status-update-nov-21/\" rel=\"noopener noreferrer\" target=\"_blank\">update</a> today, confirming that WordPress 5.0 will miss the planned November 27 release date but did not offer a secondary date.</p>\n<p>&#8220;The date for 5.0 release is under consideration, given it’s not plausible for it to be the on 27th,&#8221; Ventura said. </p>\n<h3>WordPress 5.0 Will Ship &#8220;When It&#8217;s Ready,&#8221; Contributors are Focusing on Getting Release Candidate out ASAP</h3>\n<p>When the second set of November dates for release were missed, many assumed WordPress 5.0 would fall back to the secondary dates in January, but that has not yet been confirmed. The previous <a href=\"https://make.wordpress.org/core/2018/10/03/proposed-wordpress-5-0-scope-and-schedule/\" rel=\"noopener noreferrer\" target=\"_blank\">scope and schedule Gary Pendergast outlined</a> said the November dates could slip by up to eight days if necessary and that if additional time was required, they would aim for the January dates:</p>\n<p>Secondary RC 1: January 8, 2019</p>\n<p>Secondary Release: January 22, 2019 </p>\n<p>During the regularly scheduled core developers&#8217; chat today, the discussion regarding WordPress 5.0&#8217;s release date became heated, as contributors continued to push for a January release. Pendergast suggested that December might have a viable date, to which Yoast CEO Joost de Valk responded, &#8220;I’m going to raise hell if we do December.&#8221;</p>\n<p>WordPress plugin developers and agencies are trying to plan for upcoming holidays and want to have staff available when the release lands. Many of those who attended the meeting were hoping to receive confirmation on the release being pushed back to January.</p>\n<p>&#8220;Please also consider the plugin shops that are rearranging their priorities to have blocks ready for 5.0, only to have had to fix them several times in the last few weeks,&#8221; Kevin Hoffman said. &#8220;The success of 5.0 depends just as much on third-party support as it does core.&#8221; </p>\n<p>&#8220;There&#8217;s agreement on that from all sides, that the amount of code churn and missed earlier deadlines means that the 27th is untenable,&#8221; Mullenweg said. &#8220;RC is still possible soon, but please don&#8217;t assume that implies a final release date until we see how that goes and pick one. I hope that it shows that we are willing to change decisions based on new information, it&#8217;s not about being &#8216;right&#8217; or sticking to previous plans blindly.&#8221;</p>\n<p>This statement indicates Mullenweg may be considering dates that were not included in the original schedule, as he later said,&#8221;If y&#8217;all can take the data without freaking out about what it means for the release date, there have been 8 major releases in December, it&#8217;s actually been 34% of our last 23 major releases.&#8221;</p>\n<p>Several contributors agreed that getting an RC out ASAP would finally force a longer code freeze for Gutenberg&#8217;s UI, API, documentation, and features. This would give the community more time to prepare. </p>\n<p>&#8220;As part of the development team for almost two years now, I’d love for us to draw the RC line soon for the sake of everyone’s fatigue,&#8221; Matias Ventura said. &#8220;And think it’s ready to be drawn. I am concerned with letting us do &#8216;one more little thing&#8217; and pushing the stability line further down, in an almost endless process.&#8221; </p>\n<p>Contributors are now wrapping up the last few tickets and the plan is to get the release candidate out tomorrow during the U.S. Thanksgiving holiday. Given WordPress&#8217; global contributor base, releasing on the holiday shouldn&#8217;t be an issue. The team is also still investigating the possibility of bundling the Classic Editor plugin with updates for existing WordPress sites.</p>\n<p>&#8220;Our focus right now is on a great RC,&#8221; Mullenweg said. Throughout Gutenberg&#8217;s development Mullenweg has said WordPress 5.0 would ship &#8220;when it&#8217;s ready.&#8221; No release date will be announced until the team has had time to evaluate the release candidate.</p>\n<p>&#8220;It is true that the primary thing is whether it&#8217;s ready, and it&#8217;s not currently ready,&#8221; Mullenweg said.</p>\n<p>In 1928, John A. Shedd published a little book called “Salt from My Attic.&#8221; It included a saying that U.S. Navy Rear Admiral Grace Hopper said was influential in her life: &#8220;A ship in harbor is safe, but that is not what ships are built for.&#8221; </p>\n<p>Shipping a major overhaul of WordPress&#8217; editor has brought a fair share of uncertainty and frustration to contributors and the community that depends on the software. After mission-critical issues have been resolved, it seems to become a cycle of fixing and breaking things that could continue indefinitely. Although the holiday timing isn&#8217;t ideal, if Gutenberg stalls much longer it&#8217;s going to be burning daylight. At some point the ship just needs to push away from the port and see how it sails.</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, 22 Nov 2018 03:17:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:58:\"WPTavern: ExpressionEngine Goes Open Source after 16 Years\";s:7:\"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=85816\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wptavern.com/expressionengine-goes-open-source-after-16-years\";s: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:6180:\"<p>In a post titled &#8220;<a href=\"https://expressionengine.com/blog/open-source-has-won\" rel=\"noopener noreferrer\" target=\"_blank\">Open Source Has Won</a>,&#8221; EllisLab founder Rick Ellis explained why ExpressionEngine is <a href=\"https://expressionengine.com/blog/expressionengine-is-now-free\" rel=\"noopener noreferrer\" target=\"_blank\">going open source</a> after 16 years. The content management system is an evolution of the pMachine blogging software first released in early 2002. EllisLab previously required a license fee to use the full version of ExpressionEngine, which is built on object-oriented PHP and uses MySQL for storage.</p>\n<p>&#8220;Although open source was a viable licensing model when we launched our first CMS back in 2002, it was not apparent then just how dominant open source would become on the web,&#8221; Ellis said. &#8220;It wasn’t until Eric Raymond wrote The Cathedral &#038; The Bazaar that open source would even begin to enter the general public’s consciousness. Since then we’ve watched the open source market grow rapidly and continuously.</p>\n<p>&#8220;Today, over 90% of the CMS market is open source. In fact, it’s nearly the de-facto license model for all-things web. Stunningly, the market is expected to triple in revenue within the next five to ten years, and it’s estimated that over 70% of businesses worldwide rely on open-source software. To say that the internet is open source would not be an exaggeration. It’s that dominant.&#8221;</p>\n<p>Ellis said he had wanted to migrate to an open source license for a long time but had not yet found &#8220;the right strategic and financial partner to enable the full vision of what we hope to achieve.&#8221; The first part of EllisLab&#8217;s business plan is to build a successful services model and then branch out from there.</p>\n<p>Prior to licensing ExpressionEngine under the <a href=\"https://expressionengine.com/license\" rel=\"noopener noreferrer\" target=\"_blank\">Apache License, Version 2.0</a>, EllisLab&#8217;s <a href=\"https://web.archive.org/web/20180627183126/https://expressionengine.com/license\" rel=\"noopener noreferrer\" target=\"_blank\">commercial license</a> imposed severe restrictions on what users could do with the software. Users were not permitted to do any of the following:</p>\n<ul>\n<li>Use the Core License (free) for any client or contract work.</li>\n<li>Use the Software as the basis of a hosted blogging service, or to provide hosting services to others.</li>\n<li>Reproduce, distribute, or transfer the Software, or portions thereof, to any third party.</li>\n<li>Modify, tamper with, bypass, or in any way impede license registration routines in the Software.</li>\n<li>Sell, rent, lease, assign, or sublet the Software or portions thereof, including sites in your multi-site license.</li>\n<li>Grant rights to any other person.</li>\n<li>Use the Software in violation of any U.S. or international law or regulation.</li>\n</ul>\n<p>Additional stipulations encouraged users not to share code by keeping their repositories private, and to make sure they were paying for commercial licenses if they were being paid for their work. </p>\n<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-20-at-1.35.18-PM.png?ssl=1\"><img /></a></p>\n<p>There was simply no way ExpressionEngine could capture any significant amount of market share with this kind of restrictive licensing and its usage has steadily declined over the years. It is currently used by <a href=\"https://w3techs.com/technologies/details/cm-expressionengine/all/all\" rel=\"noopener noreferrer\" target=\"_blank\">0.3% of all the websites</a> whose content management system w3techs can detect. By this or any other measure of market share, ExpressionEngine stands as a sobering monument to the importance of giving a project a license that empowers its community to continue adding wood to the fire.</p>\n<p>&#8220;The community is mostly gone at this point and I don&#8217;t even think its related to them charging for the software but they just stopped responding people and helping them in their forums,&#8221; reddit user @netzvolk <a href=\"https://www.reddit.com/r/PHP/comments/9ylq4i/expressionengine_is_now_open_source/ea2g130/\" rel=\"noopener noreferrer\" target=\"_blank\">commented</a> on the news.</p>\n<p>&#8220;I have paid EE multiple times in the past but considered NOT paying anymore because third party developers are gone, the community members are gone, the tutorials and books are gone&#8230;.EE 2 was the best version so far. Moving to yearly releases also caused more harm than good in terms of building a stable ecosystem around the product.&#8221;</p>\n<p>ExpressionEngine&#8217;s new open source licensing is a major win for its remaining users. How much further down the road would the software be if the decision was made years ago? There&#8217;s no way to know, but moving forward users will have more input and influence over the future of the software. </p>\n<p>&#8220;I suspect open sourcing EE is an approach to get that community and developers back,&#8221; @netzvolk <a href=\"https://www.reddit.com/r/PHP/comments/9ylq4i/expressionengine_is_now_open_source/ea2n7ce/\" rel=\"noopener noreferrer\" target=\"_blank\">said</a>. &#8220;EllisLab can still make money with consulting, support and add-ons.</p>\n<p>&#8220;But all those suffer if nobody is using the product anymore. This is more about expanding reach to stay afloat than anything else because some of their past bad decisions are what created alternatives like <a href=\"https://craftcms.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Craft</a>. EllisLab turned an amazing product into a forgotten one in just a few years. I hope this means some change, and maybe, maybe one day the old developers and hard core EE community members come back.&#8221;</p>\n<p>Users can only speculate on why EllisLab is making this move after 16 years of keeping its software locked down under restrictive licensing, but Ellis makes it clear in his post that the market decided long ago.</p>\n<p>&#8220;Open source has won,&#8221; Ellis said. &#8220;It’s not even a contest anymore.&#8221;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 20 Nov 2018 21:21: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:71:\"WPTavern: Figma Partners with WordPress to Improve Design Collaboration\";s:7:\"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=85769\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/figma-partners-with-wordpress-to-improve-design-collaboration\";s: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:3679:\"<p><a href=\"https://i0.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-19-at-8.43.27-PM.png?ssl=1\"><img /></a></p>\n<p><a href=\"https://www.figma.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Figma</a>, an online collaborative interface design tool, has donated an organizational membership to the WordPress project. The browser-based application helps designers and developers collaborate more efficiently and is used by organizations like Microsoft, Slack, and Uber. It provides design tools, prototyping, previews, and real-time feedback, all in the same place, and is often described as the &#8220;Google Docs for designing apps.&#8221;</p>\n<p>Figma aims to match the way designers work today in collaborative roles, with features like shared component libraries, versioning, live device preview, and Sketch import. It was created to offer &#8220;one single source of truth for design files.&#8221;</p>\n<p>&#8220;Where we may have used multiple tools in order to support all the parts of the design process, Figma incorporates many of the core features of other tools all in one product for a more efficient and powerful workflow,&#8221; Alexis Lloyd, Head of Design Innovation at Automattic, said in the <a href=\"https://make.wordpress.org/design/2018/11/19/figma-for-wordpress/\" rel=\"noopener noreferrer\" target=\"_blank\">announcement</a> on the make.wordpress design blog. &#8220;I’m excited about the possibilities for how Figma can make the WordPress design process more collaborative, robust, and efficient.&#8221;</p>\n<p>Figma launched in 2016 but has quickly gained popularity due to its seamless developer handoff exports and cross-platform compatibility. Many teams inside the WordPress community are already big fans of using Figma. 10up has been using the tool as part of the company&#8217;s design process. The <a href=\"https://10up.com/blog/2018/wordpress-wireframes-sketch/\" rel=\"noopener noreferrer\" target=\"_blank\">SketchPress</a> library that 10up created, a collection of WordPress admin interfaces, symbols, and icons, is in the process of being converted into a shared team library for Figma so that WordPress contributors can take advantage of it.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">We\'ve been using Figma at <a href=\"https://twitter.com/10up?ref_src=twsrc%5Etfw\">@10up</a> to improve collaboration across our team &amp; clients. Excited to see <a href=\"https://twitter.com/figmadesign?ref_src=twsrc%5Etfw\">@figmadesign</a> partnering w/ <a href=\"https://twitter.com/WordPress?ref_src=twsrc%5Etfw\">@WordPress</a> to make design more collaborative. Big thanks to <a href=\"https://twitter.com/apollo_ux?ref_src=twsrc%5Etfw\">@apollo_ux</a> for adapting <a href=\"https://twitter.com/hashtag/SketchPress?src=hash&ref_src=twsrc%5Etfw\">#SketchPress</a> to Figma as well! <a href=\"https://t.co/Lq2Poqexjj\">https://t.co/Lq2Poqexjj</a></p>\n<p>&mdash; Chris Wallace (@chriswallace) <a href=\"https://twitter.com/chriswallace/status/1064618129370873858?ref_src=twsrc%5Etfw\">November 19, 2018</a></p></blockquote>\n<p></p>\n<p>If you have held back on getting involved in designing for the WordPress project because of archaic collaboration tools, working with Figma may improve your contribution experience. Designers can get access to the WordPress.org Figma team by signing in with a WordPress.org Slack account using the <a href=\"https://www.figma.com/slack/642003996626140596/invite\" rel=\"noopener noreferrer\" target=\"_blank\">invitation link</a>. New users can upgrade their default &#8220;view&#8221; capabilities and get access to edit files by requesting permission in WordPress&#8217; #design Slack channel. </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, 20 Nov 2018 02:53:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:78:\"WPTavern: New Block Lab Plugin Makes it Easy to Create Custom Gutenberg Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=85659\";s:7:\"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/new-block-lab-plugin-makes-it-easy-to-create-custom-gutenberg-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5435:\"<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-19-at-10.25.08-AM.png?ssl=1\"><img /></a></p>\n<p><a href=\"https://getblocklab.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Block Lab</a> is a new tool that provides an admin interface and a templating system for creating custom Gutenberg blocks. Rob Stinson, Luke Carbis, and Rheinard Korf, all employees at <a href=\"https://xwp.co/\" rel=\"noopener noreferrer\" target=\"_blank\">XWP</a>, kicked off the project in their own time with the goal of removing the relatively steep barrier to block creation. The plugin is <a href=\"https://wordpress.org/plugins/block-lab/\" rel=\"noopener noreferrer\" target=\"_blank\">now available on WordPress.org</a> and Stinson said their target audience is WordPress developers ranging from junior to experienced.</p>\n<p>The Block Lab admin screen lets users select an icon for the custom block, enter keywords, and choose from a variety of input fields. </p>\n<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/11/block-lab-admin.png?ssl=1\"><img /></a></p>\n<p>Rendering the custom blocks in the editor and on the frontend requires simple PHP functions that most WordPress developers are probably already familiar with. Here&#8217;s an example for a testimonial block from the <a href=\"https://github.com/getblocklab/block-lab/wiki/Displaying-custom-blocks\" rel=\"noopener noreferrer\" target=\"_blank\">plugin&#8217;s documentation</a>:</p>\n<pre class=\"brush: php; light: true; title: ; notranslate\">\n&lt;img src=\"&lt;?php block_field( \'profile-picture\' ); ?&gt;\" alt=\"&lt;?php block_field( \'author-name\' ); ?&gt;\" /&gt;\n&lt;h3&gt;&lt;?php block_field( \'author-name\' ); ?&gt;&lt;/h3&gt;\n&lt;p&gt;&lt;?php block_field( \'testimonial\' ); ?&gt;&lt;/p&gt;\n</pre>\n<p>The plugin makes it possible to build custom blocks in a matter of minutes, as demonstrated in the video below.</p>\n<p></p>\n<h3>Block Lab Puts Block Creation Inside the WordPress Admin</h3>\n<p>Block Lab differs from existing block creation tools in that it aims to provide a Gutenberg-first solution directly inside the WordPress admin. With the exception of the template creation, developers are not required to write any code when using it to create blocks.</p>\n<p>&#8220;Ahmad’s <a href=\"https://github.com/ahmadawais/create-guten-block\" rel=\"noopener noreferrer\" target=\"_blank\">create-gluten-block</a> is an excellent solution, but is more focused on streamlining block creation from the ground floor,&#8221; Stinson said. &#8220;As I understand, it’s a development framework. Block Lab is about letting the developer kick off from the 10th floor and does this by offering a super simple WP Admin and traditional templating  experience.&#8221;</p>\n<p>Stinson said <a href=\"https://wptavern.com/acf-5-8-beta-1-introduces-blocks-feature-release-slated-for-november\" rel=\"noopener noreferrer\" target=\"_blank\">ACF&#8217;s solution</a> was one of the inspirations for his team but that Block Lab tackles block creation from a different angle. </p>\n<p>&#8220;ACF is amazing as well &#8211; easily one of our all time favorite plugins and one that has inspired us,&#8221; Stinson said. &#8220;Block Lab is a Gutenberg-first solution. Where ACF is a meta data first solution. They both arrive at similar destinations but get there by very different means, both technically and as far as UX goes.&#8221;</p>\n<p>Developers and users who adopt Block Labs should be aware that if the plugin is deactivated, the custom blocks they created will also be deactivated. They are stored in the database and the templates are stored in the theme or child theme. Switching themes means users will lose the blocks as well.</p>\n<p>&#8220;Adding templates to a stand-alone plugin is the most effective way around this,&#8221; Stinson said. &#8220;Either way though, the templating is simple enough that copying template folders/files from one theme to another is pretty easy. I did this exact thing yesterday in about 5 minutes.&#8221;</p>\n<p>Data portability isn&#8217;t a guarantee for users right now, but Stinson said his team has some ideas about how they can reduce barriers even further to include an in-admin templating experience. </p>\n<p>Block Lab&#8217;s creators have plans to offer commercial extensions eventually, but at this stage they are focusing on solving the problem for users in the free plugin.</p>\n<p>&#8220;Once we better understand what folks are needing, we’ll find a way of gracefully offering premium stuff,&#8221; Stinson said.  </p>\n<p>There are still many unknowns about how the larger community of WordPress users will react to the upcoming 5.0 release, but Stinson is convinced that Gutenberg will have a positive impact on the plugin ecosystem and users&#8217; experiences with extensions.</p>\n<p>&#8220;Gutenberg is going to, ultimately, change things for the better in the plugin ecosystem,&#8221; he said. &#8220;There is no doubt it’s going to be bumpy for the first little while, but the net effect is that WordPress will have a better editing experience in general and one that gives plugin developers a stronger baseline for extending the editing experience. Even as we explore what we can do with Block Lab we’re discovering really cool things that we would never have thought of unless we just started using it. I think this will be the larger experience by most people in the WordPress community.&#8221;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 19 Nov 2018 21:41:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:94:\"WPTavern: Gutenberg is Coming to WordPress’ Mobile Apps, Beta Version Expected February 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=85696\";s:7:\"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:101:\"https://wptavern.com/gutenberg-is-coming-to-wordpress-mobile-apps-beta-version-expected-february-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3582:\"<p>The team working on integrating Gutenberg into WordPress&#8217; mobile apps is making progress, but users will not have access to the new editor in the apps until early 2019. Jorge Bernal, a mobile engineer at Automattic, <a href=\"https://make.wordpress.org/mobile/2018/11/15/gutenberg-in-the-apps-what-to-expect/\" rel=\"noopener noreferrer\" target=\"_blank\">posted an update</a> yesterday, highlighting current capabilities:</p>\n<blockquote><p>Gutenberg Mobile [is] working inside the apps and the first post published with it, the writing flow has improved so it’s starting to feel more like an editor and less like a collection of isolated blocks, we have a working toolbar in place, you can now select images from your media library.</p></blockquote>\n<p>If you are using one of the mobile apps and you attempt to edit a post that was created with Gutenberg, you will see a warning like the one below:</p>\n<p><a href=\"https://i0.wp.com/wptavern.com/wp-content/uploads/2018/11/Screenshot_20181116-170549.png?ssl=1\"><img /></a></p>\n<p>This doesn&#8217;t mean users cannot edit content in the mobile apps, but there will be inconsistencies while Gutenberg support is still in progress. </p>\n<p>I created some posts with Gutenberg and then went to edit them in the Android app. During my tests of switching back to the Gutenberg editor after saving some changes in the mobile app, I found that Gutenberg included the content but not the formatting options I had selected in the app. I received a warning about unexpected or invalid content. </p>\n<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-16-at-5.08.13-PM.png?ssl=1\"><img /></a></p>\n<p>The mobile apps team expects to ship an <a href=\"https://github.com/wordpress-mobile/gutenberg-mobile/milestone/4\" rel=\"noopener noreferrer\" target=\"_blank\">alpha release</a> to testers at the end of 2018, with basic capabilities like adding a heading, paragraph, and images from the media library:</p>\n<blockquote><p>We will have an alpha release at the end of the year that will showcase the editing flow with some selected basic blocks. We will have a basic integration with the apps, enough to be able to experience Gutenberg (via secret opt-in or special builds), but won’t be showing this to users. Being able to use early versions of Gutenberg directly in the apps will make it easier to gather feedback and do user testing.</p></blockquote>\n<p>A beta with support for the most common types of content is tentatively planned for February 2019. The team is aiming to make writing a post using Gutenberg Mobile as pleasant as it currently is with Aztec.</p>\n<p>&#8220;As Gutenberg rolls out to users on the web, we might see a good amount of users hitting problems trying to edit Gutenberg posts on Aztec,&#8221; Bernal said. &#8220;We have done (and keep doing) a lot of work to try to make that as good as possible, but there are limits to how compatible we can make the existing editor. We want to reduce the gap between Gutenberg launching and having a version in the apps, so we’re adjusting scope a bit to ship in February.&#8221;</p>\n<p>It will be interesting to see how Gutenberg support is presented in the apps. I imagine it will be challenging to improve upon the mobile apps&#8217; current editing experience, which is already fairly intuitive and streamlined. </p>\n<p>Users can follow along with the process and give feedback on the <a href=\"https://github.com/wordpress-mobile/gutenberg-mobile\" rel=\"noopener noreferrer\" target=\"_blank\">Gutenberg Mobile</a> GitHub repo.</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 Nov 2018 23:52:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WPTavern: How WordPress Has Changed People’s Lives\";s:7:\"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=85710\";s:7:\"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:60:\"https://wptavern.com/how-wordpress-has-changed-peoples-lives\";s: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:4877:\"<p>It&#8217;s Friday and we could probably all use a little more positivity in our lives, especially on social media. Morten Rand-Hendriksen recently <a href=\"https://twitter.com/mor10/status/1062839649498845186\">asked his followers</a> on Twitter how WordPress has changed their lives. Here are a couple of the responses that stood out to me.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>As a beginner web designer, who was struggling to find a job/work, WordPress opened the door to web development and enabled me  to offer clients control over their websites. That was nearly 10 years ago and I’ve been building with WP ever since. </p><cite><a href=\"https://twitter.com/keithdevon/status/1062978809090228225\">Keith Devon</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I graduated in 2008 right into the thick of the recession. No jobs, nothing &#8211; the only way I could put food on the table and pay rent was to build WordPress sites for people. This led to my entire career in UX design, and my life would be very very different without WordPress.</p><cite><a href=\"https://twitter.com/scotsullivan/status/1063158394809393152\">Scott Sullivan</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Here&#8217;s one you won&#8217;t expect. I was in an agency job I hated. I had an interview with Automattic and failed. Devastated, it forced me to look at what I really wanted. I now have my own consultancy.</p><cite><a href=\"https://twitter.com/mrwiblog/status/1062976260182368257\">Chris Taylor</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I&#8217;d been working in the social field for more than 30 years. In 2015 I had to change and decided to work in the digital world. I casually met the Turin Meetup community and joined them. Then I started to contribute to the Polyglots team. Now, I&#8217;m one of the Italian GTE</p><cite><a href=\"https://twitter.com/lausacco/status/1063076968051232768\">Laurasacco</a></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I&#8217;d been working for a hosting company and noticed how many of our users were enjoying it. Decided to go to WordCamp in 2008. The software was great, but the community was what really drew me in. I&#8217;ve been using WordPress in my career ever since then.</p><cite><a href=\"https://twitter.com/supernovia/status/1062926352511160320\">Ms. Velda</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Made a WP website for a friend, then another, then someone who paid me&#8230; Today is 6 years and 120 clients later.<br /></p><cite><a href=\"https://twitter.com/Sara11D/status/1063032808669614080\">Sara Dunn</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>#<strong>WCSEA</strong> and specifically <a href=\"https://twitter.com/adspedia\">@<strong>adspedia</strong></a> reminded me that WordPress is about the inspiring people I meet at so many occasions. Beautiful minds &amp; souls who inspired me to build a new and better life 2 years ago. It’s way more than software and individual ego.</p><cite><a href=\"https://twitter.com/CaroleOlinger/status/1062991590199832576\">Carole Olinger</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I started by own consultancy doing WordPress for nonprofits straight out of college. Somehow, I&#8217;m still here and still loving it almost a decade later. Meetups and WordCamps (<a href=\"https://twitter.com/hashtag/wcsea?src=hash\">#<strong>wcsea</strong></a>!) were so crucial to my learning, developing as a speaker, and networking.</p><cite><a href=\"https://twitter.com/MRWweb/status/1062858131988828160\">Mark Root-Wiley</a><br /></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I started working with <a href=\"https://twitter.com/hashtag/WordPress?src=hash\">#<strong>WordPress</strong></a> in 2012 after my business was sold out from under me by a ‘partner&#8217;. I ended up losing everything. Developing WordPress sites contributed to getting my Family out of debt, back on our feet. <a href=\"https://twitter.com/mor10\">@<strong>Mor10</strong></a> you&#8217;ve been an inspiration along the way&#8230;</p><cite><a href=\"https://twitter.com/d8m18n/status/1063203958485803009\">Damian Saunders</a><br /></cite></blockquote>\n\n\n\n<p>There&#8217;s always a lot happening in the WordPress ecosystem and every once in awhile, it&#8217;s nice to step back to see how this software, which is used by millions of people across the world, is impacting  lives.<br /></p>\n\n\n\n<p>I highly encourage you to read <a href=\"https://twitter.com/mor10/status/1062839649498845186\">the thread</a> in its entirety.  If you&#8217;d like to read similar, more in-depth content, check out <a href=\"https://heropress.com/\">HeroPress</a>. HeroPress publishes inspirational essays from members of the community once a month. <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:\"Fri, 16 Nov 2018 22:25: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: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:77:\"WPTavern: WordPress 5.0 Beta 5 Adds Permalink Editing to the Document Sidebar\";s:7:\"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=85671\";s:7:\"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:97:\"https://wptavern.com/wordpress-5-0-beta-5-released-adds-permalink-editing-to-the-document-sidebar\";s: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:2257:\"<div class=\"wp-block-image\"><img />Permalink Panel</div>\n\n\n\n\nWordPress 5.0 Beta 5 <a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-5/\">is available</a> for testing and includes all of the block editor changes that are in <a href=\"https://make.wordpress.org/core/2018/11/15/whats-new-in-gutenberg-15th-november-2/\">Gutenberg 4.4</a>. One of the major changes in this release is the addition of a Permalink panel that is in the Document sidebar. \n\n\n\nThe <a href=\"https://github.com/WordPress/gutenberg/pull/11874\">panel was added</a> based on user feedback  that the UI for editing the permalink is difficult to discover and buggy. This method of editing the permalink does not replace the existing method of clicking the title block. \n\n\n\nIn beta 5, developers can now <a href=\"https://github.com/WordPress/gutenberg/pull/11802\">remove panels</a> from the document sidebar. However, if you want to add panels to the sidebar, there is <a href=\"https://github.com/WordPress/gutenberg/pull/11802#issuecomment-439370494\">currently no way</a> to do it.\n\n\n\nHandling images has <a href=\"https://github.com/WordPress/gutenberg/pull/11846\">been improved</a> in beta 5 as images now take up the right amount of space in themes with wider editors. <a href=\"https://github.com/WordPress/gutenberg/pull/10333\">Hover styles</a> for mobile devices are disabled and the i18n module <a href=\"https://github.com/WordPress/gutenberg/pull/11493\">was refactored</a> to take advantage of performance improvements. \n\n\n\nIf WordPress 5.0 is released before the end of the year, it will include <a href=\"https://make.wordpress.org/core/2018/10/15/wordpress-and-php-7-3/\">PHP 7.3 compatibility fixes</a>. If 5.0 is delayed until next year, these compatibility fixes <a href=\"https://wptavern.com/wordpress-4-9-9-release-may-shift-focus-to-php-7-3-compatibility-gutenberg-merge-proposal-timeline-tbd\">will be released</a> in a minor WordPress update before the end of this year.\n\n\n\nWordPress 5.0 RC 1 is scheduled to be released on Monday, November 19th, with 5.0 final scheduled to be released November 27th. If you think you&#8217;ve discovered a bug, please report it in the  <a href=\"https://wordpress.org/support/forum/alphabeta/\">Alpha/Beta support forums</a>. <br />\";s: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 Nov 2018 20:51:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:95:\"WPTavern: WordPress Accessibility Team to Host Hackathon with Deque Systems at WordCamp US 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:29:\"https://wptavern.com/?p=85636\";s:7:\"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:106:\"https://wptavern.com/wordpress-accessibility-team-to-host-hackathon-with-deque-systems-at-wordcamp-us-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:4651:\"<p>WordPress&#8217; Accessibility team will be <a href=\"https://make.wordpress.org/accessibility/2018/11/15/hackathon-automated-accessibility-testing-with-deque-on-the-wcus-contributor-day/\" rel=\"noopener noreferrer\" target=\"_blank\">hosting a hackathon at Contributor Day</a> on Sunday, December 9, at WordCamp US in Nashville. The team will be joined by lead developers from <a href=\"https://www.deque.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Deque Systems</a>, a widely respected accessibility firm in the industry, with the goal of setting up automated accessibility testing for WordPress core.</p>\n<p>The event has been in planning since JSconf EU 2018 in June when <a href=\"https://twitter.com/miss_jwo\" rel=\"noopener noreferrer\" target=\"_blank\">Jenny Wong</a> met with <a href=\"https://twitter.com/caitlinthefirst\" rel=\"noopener noreferrer\" target=\"_blank\">Caitlin Cashin</a> from Deque. They discussed how Deque could help WordPress with their accessibility expertise at WordCamp US. Rian Rietveld worked with Aaron Campbell, who is organizing the WCUS contributor day, to put the hackathon in motion.</p>\n<p>Deque&#8217;s site is built on WordPress and the company specializes in helping teams get hooked up with automation tools. The company created <a href=\"https://www.deque.com/axe/\" rel=\"noopener noreferrer\" target=\"_blank\">aXe</a>, an open source library and testing engine that can be customized to integrate with all modern browsers and testing frameworks. Deque <a href=\"https://wptavern.com/axe-an-open-source-javascript-library-for-automating-accessibility-testing\" rel=\"noopener noreferrer\" target=\"_blank\">open sourced aXe in 2015</a> and the team was invited to contribute the library to the <a href=\"http://www.w3.org/WAI/ER/2015/draft-charter-3\" rel=\"noopener noreferrer\" target=\"_blank\">W3C WAI Evaluation and Repair Tools Working Group</a>, when the group worked to develop a normative set of rules for evaluating WCAG 2.0 conformance.</p>\n<p>Deque is volunteering their lead developers to help WordPress make improvements to its development workflow. The company has hosted similar hackathons in the past.</p>\n<p>&#8220;By focusing primarily on projects with broad adoption, accessibility fixes have potential to trickle down to every website or web application including that library,&#8221; Deque Developer Advocate Marcy Sutton said after the <a href=\"https://www.deque.com/blog/highlights-takeaways-2nd-annual-axe-hackathon/\" rel=\"noopener noreferrer\" target=\"_blank\">2017 aXe hackathon in San Diego</a>. &#8220;Ultimately, this kind of work will have the most impact on the lives of people with disabilities, as it contributes to the creation of a more accessible workplace environment. A more accessible web also means a better user experience for everyone, part of the reason why digital accessibility is so important.&#8221;</p>\n<p>In order for the hackathon at WordCamp US to be successful, Deque will need to connect to contributors who can collaborate on setting up automated testing.</p>\n<p>&#8220;From the WordPress side we would like to invite core developers to join in and help find solutions to set this up,&#8221; Accessibility Team rep Jean-Baptiste Audras said. He and contributor Rachel Cherry will be representing the accessibility team during the hackathon and they need help from core committers who know their way around the automated testing system in WordPress core. Audras also said the team will need help from Gutenberg contributors.</p>\n<p>&#8220;The tools can/will provide automated tests for the block editor since it&#8217;s based on testing the DOM (Document Object Model) of each admin screen generated by WordPress,&#8221; he said. &#8220;But we have to build it together with the people involved in Gutenberg to see how we can handle it the best way.&#8221;</p>\n<p>Audras said the Gutenberg phase 2 release leads have already been in touch with the accessibility team and communication across teams is improving.</p>\n<p>&#8220;If we find a technical solution, there should ideally not be technical problems to implement it,&#8221; Audras said. &#8220;As usual, it will be a question of priority and communication. I am confident that Gutenberg developers will be interested to add some automated checks to the Gutenberg stack.&#8221;</p>\n<p>Audras said he doesn&#8217;t know when the automated tests for accessibility will be operational but he believes they will be very helpful in the future, especially in cases where new releases are being put out quickly. Anyone interested to contribute to the effort can get in touch on WordPress Slack&#8217;s #accessibility channel.</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 Nov 2018 15:39:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:48:\"BuddyPress: BuddyPress 4.0.0 Release Candidate 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=281885\";s:7:\"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://buddypress.org/2018/11/buddypress-4-0-0-release-candidate-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1216:\"<p>BP 4.0.0 Release Candidate 1 is now available. This package contains the code that we think we&#8217;ll ship as BuddyPress 4.0.0 later in November. If you build BuddyPress plugins or themes, you&#8217;re encouraged to give the RC a thorough look in a test environment.</p>\n<p>Important changes in 4.0.0 include:</p>\n<ul>\n<li>BuddyPress data exporters (for WP 4.9.6+), including a new &#8216;Export Data&#8217; Settings subtab, where users can request an export from the front end</li>\n<li>Integration into the WordPress privacy policy system (for WP 4.9.6+)</li>\n<li>Improvements to Nouveau and other BP interfaces on mobile devices</li>\n<li>Bug fixes for emails, Nouveau, BP&#8217;s nav tools</li>\n<li>Improved compatibility with WP 4.9.x and 5.0</li>\n</ul>\n<p>See the <a href=\"https://buddypress.trac.wordpress.org/query?group=status&milestone=4.0\">4.0.0 milestone</a> for more info.</p>\n<p>Download the 4.0.0 release candidate from wordpress.org: <a href=\"https://downloads.wordpress.org/plugin/buddypress.4.0.0-RC1.zip\">https://downloads.wordpress.org/plugin/buddypress.4.0.0-RC1.zip</a>. As always, remember that this is pre-release software, and we don&#8217;t recommend running it on a production site.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 16 Nov 2018 03:05: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:12:\"Boone Gorges\";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:30:\"Dev Blog: WordPress 5.0 Beta 5\";s:7:\"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=6250\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-5/\";s: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:4742:\"<p>WordPress 5.0 Beta 5 is now available!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.</p>\n\n\n\n<p>There are two ways to test this WordPress 5.0 Beta: try the&nbsp;<a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;plugin (you’ll want “bleeding edge nightlies”), or you can&nbsp;<a href=\"https://wordpress.org/wordpress-5.0-beta5.zip\">download the beta here</a>&nbsp;(zip).</p>\n\n\n\n<p><strong>Reminder: the WordPress 5.0 release date has changed</strong>. It is now scheduled for release on&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">November 27</a>, and we need your help to get there. Here are some of the big issues that we’ve fixed since Beta 4:</p>\n\n\n\n<h2>Block Editor</h2>\n\n\n\n<p>The block editor has been updated to match the <a href=\"https://make.wordpress.org/core/2018/11/15/whats-new-in-gutenberg-15th-november-2/\">Gutenberg 4.4 release</a>, the major changes  include:</p>\n\n\n\n<ul><li>&nbsp;A <a href=\"https://github.com/WordPress/gutenberg/pull/11874\">permalink panel has been added to the document sidebar</a> to make it easier to find.</li><li>Editor document panels can now be <a href=\"https://github.com/WordPress/gutenberg/pull/11802\">programmatically removed</a>.</li><li>The uploading indicator for images and galleries has been replaced with a&nbsp;<a href=\"https://github.com/WordPress/gutenberg/pull/11876\">spinner and faded out image</a>.</li><li>The text and code editing blocks will now <a href=\"https://github.com/WordPress/gutenberg/pull/11750\">use the full width of the editor</a>.</li><li>Image handling has been improved. Images now  take up the right amount of space for <a href=\"https://github.com/WordPress/gutenberg/pull/11846\">themes with wider editors</a> (like Twenty Nineteen).<br /></li><li>Hover styles are now <a href=\"https://github.com/WordPress/gutenberg/pull/10333\">correctly disabled for mobile devices</a>.</li><li>The i18n module has been refactored to benefit from <a href=\"https://github.com/WordPress/gutenberg/pull/11493\">significant performance gains</a>.</li></ul>\n\n\n\n<p>Additionally, there have been some pesky bugs fixed:</p>\n\n\n\n<ul><li>Better handling for <a href=\"https://github.com/WordPress/gutenberg/pull/11590\">links without an href</a> attribute, which were showing as <code>undefined</code>.</li><li>Japanese text (double byte characters) are <a href=\"https://github.com/WordPress/gutenberg/pull/11908\">now usable in the list block</a>.</li><li>Better handling for different text encodings (e.g. emoji) within a block <a href=\"https://github.com/WordPress/gutenberg/pull/11771\">in block validation</a>.</li></ul>\n\n\n\n<p>A full list of changes can be found in the <a href=\"https://make.wordpress.org/core/2018/11/15/whats-new-in-gutenberg-15th-november-2/\">Gutenberg 4.4 release post</a>.<br /></p>\n\n\n\n<h2>PHP 7.3 Support</h2>\n\n\n\n<p>The final known PHP 7.3 compatibility issue has been fixed. You can brush up on what you need to know about PHP 7.3 and WordPress by checking out the <a href=\"https://make.wordpress.org/core/2018/10/15/wordpress-and-php-7-3/\">developer note on the Make WordPress Core blog</a>.<br /></p>\n\n\n\n<h2>Twenty Nineteen</h2>\n\n\n\n<p>Work on making Twenty Nineteen ready for prime time continues on its <a href=\"https://github.com/WordPress/twentynineteen\">GitHub repository</a>. This update includes <a href=\"https://core.trac.wordpress.org/changeset/43904\">a host of tweaks and bug fixes</a>, including:</p>\n\n\n\n<ul><li>Add <code>.button</code> class support.</li><li>Fix editor font-weights for headings.</li><li>Improve support for sticky toolbars in the editor.</li><li>Improve text-selection custom colors for better contrast and legibility.</li><li>Fix editor to prevent Gutenberg&#8217;s meta boxes area from overlapping the content.</li></ul>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a>&nbsp;</p>\n\n\n\n<p><strong><em>If you think you’ve found a bug</em></strong><em>, you can post to the&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>Alpha/Beta area</em></a><em>&nbsp;in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>file one on WordPress Trac</em></a><em>, where you can also find&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>a list of known bugs</em></a><em>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\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, 16 Nov 2018 01:09: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:19:\"Jonathan Desrosiers\";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:135:\"WPTavern: Full Gutenberg Compatibility Coming Soon to Automattic’s Free Themes on WordPress.org, Including Storefront for WooCommerce\";s:7:\"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=85613\";s:7:\"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://wptavern.com/full-gutenberg-compatibility-coming-soon-to-automattics-free-themes-on-wordpress-org-including-storefront-for-woocommerce\";s: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:3720:\"<p>If your site is hosted on <a href=\"http://WordPress.com\" rel=\"noopener noreferrer\" target=\"_blank\">WordPress.com</a> and you are trying out the new Gutenberg editor, there are currently <a href=\"https://github.com/Automattic/themes\" rel=\"noopener noreferrer\" target=\"_blank\">24 themes with full Gutenberg support</a> available and more on the way. In response to questions about how to find Gutenberg themes on WordPress.com, <a href=\"https://themeshaper.com/\" rel=\"noopener noreferrer\" target=\"_blank\">Automattic&#8217;s Theme Team</a> has <a href=\"https://twitter.com/MRWweb/status/1062491404373356544\" rel=\"noopener noreferrer\" target=\"_blank\">given an update</a> about the status of the .com themes, as well as the company&#8217;s free themes on WordPress.org.</p>\n<p>There is currently no way to search for Gutenberg-ready themes on WordPress.com themes because there is no filter set up for this. However, the team said users should not any experience any issues with themes breaking with the new editor:</p>\n<blockquote><p>All existing themes should still work with Gutenberg. At worst styles in the editor might not exactly match styles on the site itself, and styling for individual blocks might cause conflicts if the theme treats that type of content in a specific way. But that is true of all WordPress themes, not just the ones on WordPress.com.</p></blockquote>\n<p>Users can activate any theme they want with Gutenberg. The new editor is not going to break any themes, but a theme does need to <a href=\"https://wordpress.org/gutenberg/handbook/extensibility/theme-support/\" rel=\"noopener noreferrer\" target=\"_blank\">add support</a> for users to take advantage of specific features like wide alignments and block color palettes. Gutenberg-ready themes also include editor styles to ensure a consistent editing experience between frontend and backend.</p>\n<p>Automattic is also working to bring some of those updates from its current set of Gutenberg-ready themes to its free themes hosted on WordPress.org. The company has <a href=\"https://wordpress.org/themes/author/automattic/\" rel=\"noopener noreferrer\" target=\"_blank\">109 themes</a> in the directory, which have cumulatively been downloaded more than <a href=\"http://wptally.com/?wpusername=automattic\" rel=\"noopener noreferrer\" target=\"_blank\">17 million times</a>. The majority of its more popular themes fall into the business category, such as <a href=\"https://wordpress.org/themes/dara/\" rel=\"noopener noreferrer\" target=\"_blank\">Dara</a> (10K active installs), <a href=\"https://wordpress.org/themes/argent/\" rel=\"noopener noreferrer\" target=\"_blank\">Argent</a> (10K), <a href=\"https://wordpress.org/themes/edin/\" rel=\"noopener noreferrer\" target=\"_blank\">Edin</a> (6K), and <a href=\"https://wordpress.org/themes/karuna/\" rel=\"noopener noreferrer\" target=\"_blank\">Karuna (5K)</a>. Several of these themes are already Gutenberg-ready with the code <a href=\"https://github.com/Automattic/themes\" rel=\"noopener noreferrer\" target=\"_blank\">available on GitHub</a>.</p>\n<p><a href=\"https://wordpress.org/themes/storefront/\" rel=\"noopener noreferrer\" target=\"_blank\">Storefront</a> is by far Automattic&#8217;s most popular free theme on WordPress.org with 200,000+ installs and is well on its way towards being ready to support Gutenberg&#8217;s new features. Development towards this goal is <a href=\"https://github.com/woocommerce/storefront/tree/feature/gutenberg\" rel=\"noopener noreferrer\" target=\"_blank\">happening on GitHub</a>. Users can run beta versions of the Storefront theme ahead of time using the <a href=\"https://github.com/seb86/Storefront-Beta-Tester\" rel=\"noopener noreferrer\" target=\"_blank\">Storefront Beta Tester</a> plugin.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 16 Nov 2018 00:27:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:78:\"WPTavern: WPWeekly Episode 338 – Inflation, WordPress Release Dates, WP GDPR\";s:7:\"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=85642&preview=true&preview_id=85642\";s:7:\"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/wpweekly-episode-338-inflation-wordpress-release-dates-wp-gdpr\";s: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:1871:\"<p>In this episode, <a href=\"http://jjj.me\">John James Jacoby</a> and I discuss the news of the week. We talk about the delayed release of WordPress 5.0 and which day would be a suitable release date. We share our opinions on Matt&#8217;s answers from his Q&amp;A appearance at WordCamp in Portland, Oregon. We also talk about the changes in WordPress core development, Automatticians in leadership roles, and last, but not least, WordCamp budgeting.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"https://wptavern.com/wordpress-5-0-release-date-update-to-november-27\">WordPress 5.0 Release Date Update to November 27</a></p>\n<p><a href=\"https://wptavern.com/matt-mullenweg-addresses-controversies-surrounding-gutenberg-at-wordcamp-portland-qa\">Matt Mullenweg Addresses Controversies Surrounding Gutenberg at WordCamp Portland Q&amp;A</a></p>\n<p><a href=\"https://wptavern.com/wp-gdpr-compliance-plugin-patches-privilege-escalation-vulnerability\">WP GDPR Compliance Plugin Patches Privilege Escalation Vulnerability</a></p>\n<p><a href=\"https://wptavern.com/maximum-ticket-prices-for-wordcamps-will-increase-to-25-per-day-in-2019\">Maximum Ticket Prices for WordCamps Will Increase to $25 per Day in 2019</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, November 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 #338:</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 Nov 2018 17:23: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:\"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: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:80:\"WPTavern: NextGEN Gallery Plugin to Add Gutenberg Support Ahead of WordPress 5.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:29:\"https://wptavern.com/?p=85609\";s:7:\"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/nextgen-gallery-plugin-to-add-gutenberg-support-ahead-of-wordpress-5-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:4139:\"<p>If you&#8217;re a <a href=\"https://wordpress.org/plugins/nextgen-gallery/\" rel=\"noopener noreferrer\" target=\"_blank\">NextGEN Gallery plugin</a> user and have been wondering about Gutenberg compatibility, Imagely CEO Erick Danzer announced today that the plugin will ship a gallery block in a release planed for next week. The plugin is currently used on nearly a million WordPress sites (900,000+ active installs). NextGEN Gallery&#8217;s Gutenberg block has been in <a href=\"https://www.imagely.com/gutenberg-block/\" rel=\"noopener noreferrer\" target=\"_blank\">beta testing since May</a> and the plugin will support users who update to use the new editor as well as those who stick with the Classic Editor plugin.</p>\n<p>In a post titled &#8220;<a href=\"https://www.imagely.com/defer-gutenberg/\" rel=\"noopener noreferrer\" target=\"_blank\">A Plea to Defer the Release of Gutenberg</a>,&#8221; Danzer outlined his concerns with the timeline for WordPress 5.0. His thoughts echo many other prominent members of the development community who have written their own <a href=\"https://wptavern.com/calls-to-delay-wordpress-5-0-increase-developers-cite-usability-concerns-and-numerous-bugs-in-gutenberg\" rel=\"noopener noreferrer\" target=\"_blank\">calls to delay the release</a>. He cites feedback on WordPress.org and urges the Gutenberg team not to discount the validity of these reviews:</p>\n<blockquote><p>Some people have been dismissive of those reviews and questioned whether they are a legitimate reflection of user experiences with Gutenberg. The reviews often lack detail and can be quite harsh.</p>\n<p>But that’s the experience of ALL plugin developers on the WordPress repository. Gutenberg is being reviewed in precisely the same way as every other plugin on the repository. If any other major plugin maintained a 2.3 star rating and refused to accept the feedback as legitimate, it would not be a major plugin for long.</p>\n<p>Even without detail, reviews on the repository represent a fair reflection of overall user feelings about a plugin. In the case of Gutenberg, it is clear the plugin is not ‘wowing’ potential users.</p></blockquote>\n<p>Danzer also referenced a release the NextGEN Gallery team shipped in 2013 that included &#8220;major and breaking changes&#8221; that had been &#8220;tested aggressively but in limited ways.&#8221; This release broke an estimated 10 percent of the plugin&#8217;s installations as well as compatibility with many extensions. It has had a lasting impact on NextGEN&#8217;s reputation for the past five years. Danzer said he fears WordPress may be headed in the same direction, except at a much larger scale.</p>\n<p>As a postscript to his plea, Danzer assured users reading his post that NextGEN Gallery will have support for Gutenberg in time for the WordPress 5.0 release:</p>\n<blockquote><p>Despite the concerns expressed in this post, I want to assure NextGEN Gallery users that we&#8217;ll be ready regardless of the final release decision for Gutenberg. We&#8217;ll be officially  in the next week. We&#8217;ve tested and ensured that your existing galleries will work when you update. We&#8217;ve developed our block so that if you add galleries via Gutenberg, they will continue to work if you roll back or install the classic editor. And we&#8217;ll have all hands on deck to deal with any issues that arise when Gutenberg is released.</p></blockquote>\n<p>NextGEN Gallery&#8217;s Gutenberg support includes a block that launches a modal where users can select a gallery to insert. Unless it has significantly changed from the <a href=\"https://www.youtube.com/watch?v=ZCazFfYz49s\" rel=\"noopener noreferrer\" target=\"_blank\">beta preview video</a> published, the gallery block doesn&#8217;t seem to offer a preview of the gallery inside the Gutenberg editor once it has been selected and placed within the content. Users who want to test the beta version of Gutenberg support in the plugin can download the latest from the <a href=\"https://www.imagely.com/wordpress-gallery-plugin/nextgen-gallery/beta/\" rel=\"noopener noreferrer\" target=\"_blank\">NextGEN Gallery beta page</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 Nov 2018 23:54:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:60:\"WPTavern: Drupal Gutenberg Showcased at DrupalCamp Oslo 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:29:\"https://wptavern.com/?p=85542\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wptavern.com/drupal-gutenberg-showcased-at-drupalcamp-oslo-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:4727:\"<p>Gutenberg appreciation is running high across the CMS pond in the Drupal world. DrupalCamp Oslo 2018, Norway&#8217;s biggest national camp to date, was held over the weekend. The event featured two sessions on Gutenberg &#8211; one for site builders and one for block developers. <a href=\"https://www.frontkom.no/\" rel=\"noopener noreferrer\" target=\"_blank\">Frontkom</a>, the team behind <a href=\"https://drupalgutenberg.org/\" rel=\"noopener noreferrer\" target=\"_blank\">Drupal Gutenberg</a>, took home two <a href=\"https://splashawards.org/\" rel=\"noopener noreferrer\" target=\"_blank\">Splash Awards</a> for &#8220;Best Module&#8221; and &#8220;Best Integration&#8221; for 2018.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">The Splash Awards for Best integration and Best module was awarded to Drupal Gutenberg this weekend @ <a href=\"https://twitter.com/hashtag/dcoslo?src=hash&ref_src=twsrc%5Etfw\">#dcoslo</a>! Big smile from <a href=\"https://twitter.com/perandre?ref_src=twsrc%5Etfw\">@perandre</a> on behalf of the <a href=\"https://twitter.com/frontkom?ref_src=twsrc%5Etfw\">@frontkom</a> team. <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f3c6.png\" alt=\"🏆\" class=\"wp-smiley\" /><img src=\"https://s.w.org/images/core/emoji/11/72x72/1f3c6.png\" alt=\"🏆\" class=\"wp-smiley\" /> <a href=\"https://t.co/Sx0NLv3rWY\">pic.twitter.com/Sx0NLv3rWY</a></p>\n<p>&mdash; drupalgutenberg (@drupalgutenberg) <a href=\"https://twitter.com/drupalgutenberg/status/1061973657470337024?ref_src=twsrc%5Etfw\">November 12, 2018</a></p></blockquote>\n<p></p>\n<p>The <a href=\"https://wptavern.com/gutenberg-cloud-plugin-for-wordpress-is-now-in-beta\" rel=\"noopener noreferrer\" target=\"_blank\">Cloud Blocks plugin for WordPress</a> was released in beta two weeks ago to begin testing the Gutenberg Cloud API, which enables blocks to be shared across CMS&#8217;s. The Drupal version of this connector plugin was introduced at DrupalCamp Oslo. Frontkom&#8217;s Per André Rønsen and Thor Andre Gretland hosted a session called &#8220;Build your pages build with Drupal Gutenberg&#8221; where they gave attendees a look at Gutenberg Cloud for D8. It runs as submodule of Drupal Gutenberg.</p>\n<p><a href=\"https://cloudup.com/c5wZ7ylbkvN\"><img src=\"https://i2.wp.com/cldup.com/9giVOkXdC3.gif?resize=627%2C407&ssl=1\" alt=\"Drupal pagebuilder gutenberg\" width=\"627\" height=\"407\" /></a></p>\n<h3>Changes Coming to Gutenberg Cloud: All Blocks Will Undergo Code Review before Publishing</h3>\n<p>One of the speakers at the event was a member of the Drupal.org security team. Rønsen said after their session they had good participation during the Q&amp;A time.</p>\n<p>&#8220;There was some push back on Gutenberg Cloud for letting any developer add new blocks,&#8221; Rønsen said. &#8220;We explained that this is only during beta phase, and that we do code review of new blocks coming in. However, this led to the decision of switching to white listing instead. Starting next week, block authors will need to email us and ask for code review before we accept the blocks. This will go hand in hand with an upcoming browser on gutenbergcloud.org  – meaning each block will get it&#8217;s own little landing page online. We think this will be useful for people to see how Gutenberg Cloud can be useful for their site.&#8221;</p>\n<p>Overall, the Frontkom team saw a positive reception to Gutenberg Cloud at DrupalCamp Oslo and they are working to incorporate some of the valuable feedback they received.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Totally impressed by <a href=\"https://twitter.com/drupalgutenberg?ref_src=twsrc%5Etfw\">@drupalgutenberg</a> demo at <a href=\"https://twitter.com/hashtag/dcoslo?src=hash&ref_src=twsrc%5Etfw\">#dcoslo</a>. Good work <a href=\"https://twitter.com/frontkomtech?ref_src=twsrc%5Etfw\">@frontkomtech</a> <a href=\"https://twitter.com/hashtag/drupalgutenberg?src=hash&ref_src=twsrc%5Etfw\">#drupalgutenberg</a> <a href=\"https://twitter.com/hashtag/drupalnorge?src=hash&ref_src=twsrc%5Etfw\">#drupalnorge</a> <a href=\"https://t.co/qXbX8mXhnp\">pic.twitter.com/qXbX8mXhnp</a></p>\n<p>&mdash; Baddy Sonja Breidert (@baddysonja) <a href=\"https://twitter.com/baddysonja/status/1060881025813934085?ref_src=twsrc%5Etfw\">November 9, 2018</a></p></blockquote>\n<p></p>\n<p>&#8220;The interest was amazing,&#8221; Rønsen said. &#8220;This week, we&#8217;ve been in contact with two big dev teams who wants to help out getting the Drupal module a stable release.&#8221;</p>\n<p>The session for site builders was not filmed but there is an unofficial video from the developer day where Frontkom&#8217;s Marco Fernandes and Frank Gjertsen gave a technical session on how to build custom blocks.</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, 14 Nov 2018 19:56: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: Maximum Ticket Prices for WordCamps Will Increase to $25 per Day in 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=85570\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"https://wptavern.com/maximum-ticket-prices-for-wordcamps-will-increase-to-25-per-day-in-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4485:\"<p>For the last seven years, the maximum amount of money WordCamp organizers could charge for ticket prices was $20 per day. In 2019, this <a href=\"https://make.wordpress.org/community/2018/11/12/increase-in-wordcamp-maximum-ticket-price-for-2019/\">will increase</a> to $25 per day.</p>\n<p>The new amount accounts for inflation and provides breathing room for organizers. According to the Bureau of Labor Statistics <a href=\"https://data.bls.gov/cgi-bin/cpicalc.pl?cost1=20.00&year1=200601&year2=201808\">inflation calculator</a>, $20 in January of 2006 is equal to $25.51 in October of 2018.</p>\n<p>Organizers don&#8217;t have to charge this amount and are encouraged to keep the ticket price as low as possible. The increase is also part of a delicate balancing act between not being a financial burden and getting 80% or more of attendees to show up.</p>\n<p>&#8220;The ticket price does not reflect on the value of the event,&#8221; Andrea Middleton, Community organizer said.</p>\n<p>&#8220;In an ideal world, all WordCamp tickets would be free just like WordPress is free but to avoid organizing a conference for 500 registrants and only having 50 people show up on the day of the event, we <a href=\"https://make.wordpress.org/community/handbook/wordcamp-organizer/planning-details/selling-tickets/#the-reasons-behind-pricing-tickets-as-low-as-possible\">charge as little as we possibly can</a> for tickets, but just enough that people will show up for the event if they’re sleepy that morning or got a last-minute invitation to a pool party or something.&#8221;</p>\n<p>When the <a href=\"https://make.wordpress.org/community/2018/09/17/proposal-to-increase-the-maximum-ticket-price-for-wordcamps/\">proposal </a>to increase the maximum ticket price was published in September, many commenters approved of the increase with <a href=\"https://make.wordpress.org/community/2018/09/17/proposal-to-increase-the-maximum-ticket-price-for-wordcamps/#comment-25918\">some suggesting</a> an even higher amount to account for inflation for the next few years. <a href=\"https://make.wordpress.org/community/2018/09/17/proposal-to-increase-the-maximum-ticket-price-for-wordcamps/#comment-25885\">Ian Dunn questioned</a> whether or not budget shortfalls were due to organizing teams spending money on extra things.</p>\n<p>&#8220;Beyond that, though, I’m curious why camps are having more trouble today than they were 5 or even 10 years ago?&#8221; Dunn said.</p>\n<p>&#8220;Is it harder to get sponsorships? It seems like the opposite is true, especially given how much the global sponsorship program covers.</p>\n<p>&#8220;Based on experiences in my local community, I suspect that the primary reason for budget shortfalls is that the organizing team is choosing to do extra things, beyond what’s necessary to meet the goals of a WordCamp. For example, holding after-parties at trendy venues, expensive speaker gifts, professional A/V (which I’ve advocated for in the past, but not at the cost of higher ticket prices), etc.&#8221;</p>\n<p>It is interesting to ponder how much money WordCamps could save globally by eliminating the materialistic aspects of the event such as t-shirts, speaker gifts, lanyards, badges, signs, etc.</p>\n<p>At there core, WordCamps are about gathering the local community together in a physical location to share knowledge. Not every WordPress event needs to mimic WordCamp US or WordCamp Europe, two of the largest events in the world.</p>\n<p>Although the WordPress Community team tracks data such as how much each WordCamp charges for ticket prices, the information is not readily available. This is because of the large volume of data that would need to be calculated and displayed. It would be interesting to see an info-graphic of this data where you can compare the average ticket price for WordCamps per country.</p>\n<p>Hugh Lashbrooke, a WordPress Community team contributor who has access to the data says that, &#8220;globally the majority of camps have lower prices.&#8221;</p>\n<p>WordCamp organizers are highly encouraged to <a href=\"https://make.wordpress.org/community/handbook/wordcamp-organizer/first-steps/web-presence/using-camptix-event-ticketing-plugin/#tracking-attendance\">keep track</a> of attendance as the data is used to help make better informed decisions. The team will review the no-show rates at WordCamps at the end of 2019 to determine if the price increase had any effect. If not, the team may increase the price again for 2020.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 14 Nov 2018 19:25: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: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:92:\"WPTavern: Google Developers Demo AMP Stories Integration with Gutenberg at Chrome Dev Summit\";s:7:\"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=85548\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://wptavern.com/google-developers-demo-amp-stories-integration-with-gutenberg-at-chrome-dev-summit\";s: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:2929:\"<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-13-at-1.18.48-PM.png?ssl=1\"><img /></a></p>\n<p>Alberto Medina and Weston Ruter gave a presentation on Progressive Content Management Systems yesterday at <a href=\"https://developer.chrome.com/devsummit/\" rel=\"noopener noreferrer\" target=\"_blank\">Chrome Dev Summit 2018</a> in San Francisco. Medina is a developer advocate at Google and Ruter recently transitioned into a new role as a Developer Programs Engineer after eight years at XWP.</p>\n<p>Medina began the session with a quick overview of the increasingly complex CMS space, which is growing, according to figures he cited from w3techs: 54% of sites are built with some kind of CMS (11% YoY growth). Many CMS&#8217;s face common challenges when it comes to integrating modern web technologies into their platforms, such as large code bases, legacy code, and technical debt.</p>\n<p>In addressing the challenges that WordPress faces, Google is looking to make an impact on a large swath of the web. Medina outlined the two-part approach Google is using with the WordPress ecosystem. This includes AMP integration via the AMP plugin for WordPress. It&#8217;s currently at <a href=\"https://make.xwp.co/2018/11/05/amp-plugin-release-v1-0-rc2/\" rel=\"noopener noreferrer\" target=\"_blank\">version 1.0 RC2</a> and the stable version is scheduled for release at the end of this month.</p>\n<p>The second part of the approach is integration of modern web capabilities and APIs in core, so that things like service workers and background sync are supported natively in a way that the entire ecosystem can take advantage of them. Google has invested resources to get these features added to core.</p>\n<p>Ruter demonstrated a single page application built in WordPress using a standard theme as the basis and the AMP plugin as a foundation. Medina said the team plans to continue expanding this work integrating AMP content into WordPress, specifically in the context of Gutenberg. He gave a quick demo of how they are working to help content creators easily take advantage of features like <a href=\"https://www.ampproject.org/stories/\" rel=\"noopener noreferrer\" target=\"_blank\">AMP stories</a> via a Gutenberg integration.</p>\n<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/11/Screen-Shot-2018-11-13-at-2.08.41-PM.png?ssl=1\"><img /></a></p>\n<p>Medina said AMP stories are formed by components and work well with Gutenberg, since everything in the new editor corresponds to a block.</p>\n<p>&#8220;We want powerful components like these to become available across all CMS&#8217;s,&#8221; Medina said. &#8220;The CMS space is moving steadily along the progressive web road.&#8221;</p>\n<p>Check out the video below to learn more about Google&#8217;s experience integrating modern web capabilities and progressive technologies into the WordPress platform and ecosystem.</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, 14 Nov 2018 00:27: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:27;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"Dev Blog: WordPress 5.0 Beta 4\";s:7:\"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=6241\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-4/\";s: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:3706:\"<p>WordPress 5.0 Beta 4 is now available!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.</p>\n\n\n\n<p>There are two ways to test the WordPress 5.0 Beta: try the&nbsp;<a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;plugin (you’ll want “bleeding edge nightlies”), or you can&nbsp;<a href=\"https://wordpress.org/wordpress-5.0-beta4.zip\">download the beta here</a>&nbsp;(zip).</p>\n\n\n\n<p><strong>The WordPress 5.0 release date has changed</strong>, it is now scheduled for release on&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">November 27</a>, and we need your help to get there. Here are some of the big issues that we’ve fixed since Beta 3:</p>\n\n\n\n<h2>Block Editor</h2>\n\n\n\n<p>The block editor has been updated to match the <a href=\"https://make.wordpress.org/core/2018/11/12/whats-new-in-gutenberg-12th-november/\">Gutenberg 4.3 release</a>, the major changes  include:</p>\n\n\n\n<ul><li>An <a href=\"https://github.com/WordPress/gutenberg/pull/7718\">Annotations API</a>, allowing plugins to add  contextual data as you write.</li><li>More consistent keyboard navigation between blocks, as well as back-and-forth between different areas of the interface.</li><li>Improved accessibility, with additional  labelling and speech announcements.</li></ul>\n\n\n\n<p>Additionally, there have been some bugs fixed that popped up in beta 3:</p>\n\n\n\n<ul><li>Better support for plugins that have more advanced meta box usage.</li><li>Script concatenation is now supported.</li><li>Ajax calls could occasionally cause PHP errors.</li></ul>\n\n\n\n<h2>Internationalisation</h2>\n\n\n\n<p>We&#8217;ve added an API for translating your plugin and theme strings in JavaScript files! The block editor is now using this, and you can start using it, too. Check out the <a href=\"https://make.wordpress.org/core/2018/11/09/new-javascript-i18n-support-in-wordpress/\">developer note</a>&nbsp;to get started.</p>\n\n\n\n<h2>Twenty Nineteen</h2>\n\n\n\n<p>Twenty Nineteen is being polished over on its <a href=\"https://github.com/WordPress/twentynineteen\">GitHub repository</a>. This update includes <a href=\"https://core.trac.wordpress.org/changeset/43892\">a host of tweaks and bug fixes</a>, including:</p>\n\n\n\n<ul><li>Menus now  properly support keyboard and touch interactions.</li><li>A footer menu has been added for secondary page links.</li><li>Improved backwards compatibility with older versions of WordPress.</li></ul>\n\n\n\n<h2>Default Themes</h2>\n\n\n\n<p>All of the older default themes—from Twenty Ten through to Twenty Seventeen—have polished  styling in the block editor.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a>&nbsp;</p>\n\n\n\n<p><strong><em>If you think you’ve found a bug</em></strong><em>, you can post to the&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>Alpha/Beta area</em></a><em>&nbsp;in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>file one on WordPress Trac</em></a><em>, where you can also find&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>a list of known bugs</em></a><em>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>International-<br />isation is a word with<br />many syllables.</em></p>\n\n\n\n<p><em>Meta boxes are<br />the original style block.<br />Old is new again.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 13 Nov 2018 01:27: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:15:\"Gary Pendergast\";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:87:\"WPTavern: WordCamp Nordic Tickets Now on Sale, Sponsorship Packages Sold Out in Minutes\";s:7:\"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=85193\";s:7:\"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:97:\"https://wptavern.com/wordcamp-nordic-tickets-now-on-sale-sponsorship-packages-sold-out-in-minutes\";s: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:2086:\"<p><a href=\"https://2019.nordic.wordcamp.org/tickets/\" rel=\"noopener noreferrer\" target=\"_blank\">Tickets</a> for the first ever <a href=\"https://wptavern.com/wordcamp-nordic-2019-to-be-held-in-helsinki-march-7-8\" rel=\"noopener noreferrer\" target=\"_blank\">WordCamp Nordic</a> went on sale today and 100 seats sold within 20 minutes. The event is scheduled to be held in Helsinki, Finland, March 7-8, 2019. There are currently 97 regular tickets and 59 micro-sponsor tickets remaining in the first batch, but more will be released in another round.</p>\n<p>If there was any question about whether this new regional WordCamp would gain support, the record-setting buy up of all the <a href=\"https://2019.nordic.wordcamp.org/call-for-sponsors/\" rel=\"noopener noreferrer\" target=\"_blank\">sponsor packages</a> has put them to rest. All of the Gold packages (3000 €) were purchased within one minute. Silver packages (1500 €) and Bronze packages (750 €) were all purchased within four minutes and 35 minutes, respectively.</p>\n<p>&#8220;Sponsor packages tend to go in a few hours whenever there’s a WordCamp in Finland, largely thanks to our communications team and the fact that most companies involved with WordPress follow the conversations on our local Slack/Twitter where these things get announced,&#8221; co-organizer Niko Pettersen said. &#8220;But this must have been a record even for us. WordCamp Nordic seems to be drawing a lot of interest.&#8221;</p>\n<p>The <a href=\"https://2019.nordic.wordcamp.org/call-for-speakers/\" rel=\"noopener noreferrer\" target=\"_blank\">call for speakers</a> opened on November 7 and submissions close January 7, 2019. All of the sessions will be held in English and the camp is planning to have two tracks. Those interested to speak may apply for a long talk (40 minutes) or a lightning talk (15 minutes). Selections will be made by mid-January and speakers will be announced in February. Follow <a href=\"https://twitter.com/WordCampNordic\" rel=\"noopener noreferrer\" target=\"_blank\">@WordCampNordic</a> for all the latest news from the event.</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 Nov 2018 00:30: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:78:\"WPTavern: WP GDPR Compliance Plugin Patches Privilege Escalation Vulnerability\";s:7:\"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=85459\";s:7:\"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/wp-gdpr-compliance-plugin-patches-privilege-escalation-vulnerability\";s: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:5052:\"<p>At the end of last week, a plugin called <a href=\"https://wordpress.org/plugins/wp-gdpr-compliance/\" rel=\"noopener noreferrer\" target=\"_blank\">WP GDPR Compliance</a> sent out a security update for a privilege escalation vulnerability that was reported to the WordPress Plugin Directory team on November 6. The plugin was temporarily removed and then reinstated after the issues were patched within 24 hours by its creators, <a href=\"https://www.van-ons.nl/\" rel=\"noopener noreferrer\" target=\"_blank\">Van Ons</a>, a WordPress development shop based in Amsterdam.</p>\n<p>The changelog for the most recent release states that previous versions are vulnerable to SQL injection due to &#8220;wrong handling of possible user input in combination with unsafe unserialization.&#8221; The fixes are in version 1.4.3, which includes the following:</p>\n<ul>\n<li>Security fix: Removed base64_decode() function</li>\n<li>Security fix: Correctly escape input in $wpdb->prepare() function</li>\n<li>Security fix: Only allow modifying WordPress options used by the plugin and by the user capabilities</li>\n</ul>\n<p>Van Ons said they requested the Plugin Directory team do a forced update but they said it was not an option in this case.</p>\n<p><a href=\"https://wordpress.org/plugins/wp-gdpr-compliance/\" rel=\"noopener noreferrer\" target=\"_blank\">WP GDPR Compliance</a> has more than 100,000 active installs. According to Wordfence, the vulnerability is being actively exploited in the wild and many users are reporting new administrator accounts being created on their affected sites. The <a href=\"https://www.wordfence.com/blog/2018/11/privilege-escalation-flaw-in-wp-gdpr-compliance-plugin-exploited-in-the-wild/\">Wordfence blog</a> has a breakdown of how attackers are taking advantage of these sites:</p>\n<blockquote><p>We’ve already begun seeing cases of live sites infected through this attack vector. In these cases, the ability to update arbitrary options values is being used to install new administrator accounts onto the impacted sites.</p>\n<p>By leveraging this flaw to set the users_can_register option to 1, and changing the default_role of new users to “administrator”, attackers can simply fill out the form at /wp-login.php?action=register and immediately access a privileged account. From this point, they can change these options back to normal and install a malicious plugin or theme containing a web shell or other malware to further infect the victim site.</p></blockquote>\n<p>Wordfence has seen multiple malicious administrator accounts present on sites that have been compromised, with variations of the username t2trollherten. Several WP GDPR Compliance plugin users have commented on the Wordfence post saying they were victims of the exploit, having found new admin users with a backdoor and file injections added.</p>\n<p>The plugin has its own <a href=\"https://www.wpgdprc.com/\" rel=\"noopener noreferrer\" target=\"_blank\">website</a> where the vulnerability was announced. Its creators recommend that anyone who didn&#8217;t update right away on November 7, 2018, should look for changes in their databases. The most obvious symptom of attack is likely to be new users with administrator privileges. Any unrecognized users should be deleted. They also recommend restoring a complete backup of the site before November 6 and then updating to version 1.4.3 right away.</p>\n<p>The WP GDPR Compliance plugin lets users add a GDPR checkbox to Contact Form 7, Gravity Forms, WooCommerce, and WordPress comments. It allows visitors and customers to opt into allowing the site to handle their personal data for a defined purpose. It also allows visitors to request data stored in the website&#8217;s database through a Data Request page that allows them to request data to be deleted.</p>\n<p>While the name of the plugin includes the word &#8220;compliance,&#8221; users should note that the plugin details includes a disclaimer:</p>\n<p>&#8220;ACTIVATING THIS PLUGIN DOES NOT GUARANTEE YOU FULLY COMPLY WITH GDPR. PLEASE CONTACT A GDPR CONSULTANT OR LAW FIRM TO ASSESS NECESSARY MEASURES.&#8221;</p>\n<p>A relatively new amendment to <a href=\"https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#9-developers-and-their-plugins-must-not-do-anything-illegal-dishonest-or-morally-offensive\" rel=\"noopener noreferrer\" target=\"_blank\">section 9 of the plugin development guidelines</a> restricts plugin authors from implying that a plugin can create, provide, automate, or guarantee legal compliance. Heather Burns, a member of WordPress Privacy team, worked together with Mika Epstein last April to <a href=\"https://make.wordpress.org/plugins/2018/04/12/legal-compliance-added-to-guidelines/\" rel=\"noopener noreferrer\" target=\"_blank\">put this change into effect</a>. This guideline is especially important for users to remember when a plugin author uses GDPR Compliance in the name of the plugin. It isn&#8217;t a guarantee of compliance, just a useful tool as part of larger plan to protect users&#8217; privacy.</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, 12 Nov 2018 20:20:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:69:\"Akismet: Version 4.1 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=2031\";s:7:\"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:97:\"https://blog.akismet.com/2018/11/12/version-4-1-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:826:\"<p>Version 4.1 of <a href=\"http://wordpress.org/plugins/akismet/\">the Akismet plugin for WordPress</a> is now available and contains the following changes:</p>\n\n<ul><li>We added a WP-CLI method for retrieving Akismet stats: <code>wp akismet stats</code><br /></li><li>Akismet now hooks into the  new &#8220;Personal Data Eraser&#8221; functionality from WordPress 4.9.6 to ensure that any personal data stored by Akismet is erased when requested.<br /></li><li>We&#8217;ve updated the plugin to more quickly clear outdated alert messages.</li></ul>\n\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, 12 Nov 2018 19:51:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Christopher Finke\";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:99:\"WPTavern: Matt Mullenweg Addresses Controversies Surrounding Gutenberg at WordCamp Portland Q&amp;A\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=85433\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"https://wptavern.com/matt-mullenweg-addresses-controversies-surrounding-gutenberg-at-wordcamp-portland-qa\";s: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:8531:\"<p>Matt Mullenweg joined attendees at WordCamp Portland, OR, for a Q&amp;A session last weekend and the recording is now <a href=\"https://wordpress.tv/2018/11/08/matt-mullenweg-qa-at-wordcamp-portland-2018/\" rel=\"noopener noreferrer\" target=\"_blank\">available on WordPress.tv</a>.</p>\n<p>The first question came from a user who tried Gutenberg and turned it off because of a plugin conflict. She asked if users will have to use Gutenberg when 5.0 is released. Mullenweg said one of the reasons Gutenberg has been tested so early is to give plugin developers time to get their products compatible. He also said that it has been the fastest growing plugin in WordPress&#8217; history, with more than 600,000 installations since it was first made available.</p>\n<p>In response to her question he said users will have the option to use the Classic Editor and that the team is considering updating it to include per-user controls and the possibility to turn it on/off for different post types.</p>\n<p>Subsequent questions went deeper into recent controversies surrounding Gutenberg, which Mullenweg addressed more in depth.</p>\n<p>&#8220;The tough part of any open source project &#8211; there&#8217;s kind of a crucible of open source development which can sometimes be more adversarial and sometimes even acrimonious,&#8221; he said. &#8220;Working within the same company, you can kind of assume everyone is rowing in the same direction. In a wide open source ecosystem, some people might actually want the opposite of what you&#8217;re doing, because it might be in their own economic self-interest, or for any number of reasons.</p>\n<p>&#8220;I liken it much more to being a mayor of a city than being a CEO of a company. I&#8217;ve done WordPress now for 15 years so I&#8217;m pretty used to it. It might seem kind of controversial if you&#8217;re just coming in, but this is not the most controversial thing we have ever brought into WordPress. The last time we had a big fork of WordPress was actually when we brought in WYSIWYG the first time. Maybe there&#8217;s something about messing with the editor that sets people off.&#8221;</p>\n<p>Mullenweg commented on how polarizing Twitter can be as a medium and how that can impact conversations in negatives ways. He said people tend to read the worst into things that have been said and that has been a new challenge during this particular time in WordPress&#8217; history. WordPress tweets are sprinkled into timelines along with politics and current events in a way that can cause people to react differently than if the discussion was held in a trac ticket, for example.</p>\n<p>One attendee asked, &#8220;With Gutenberg there&#8217;s a lot of uncertainty. Where do you see the tipping point where you see people become more favorable to Gutenberg than the Classic Editor?&#8221;</p>\n<p>&#8220;Part of getting these two plugins, Gutenberg and Classic Editor, out early, was that it could remove uncertainty for people,&#8221; Mullenweg said. &#8220;Months before they were released you could kind of choose your path. The hope is that the 5.0 release day is the most anti-climactic thing ever. Because we have over a million sites that have either chosen to not use Gutenberg, which is totally ok, or have already opted in and have been getting these sometimes weekly updates. We have hosts that have been actually been pre-installing, pre-activating Gutenberg with all of their sites.&#8221;</p>\n<p>Mullenweg said hosts that have pre-installed Gutenberg have not reported a higher than normal support load and that it has basically been &#8220;a non-event.&#8221; It&#8217;s the users who are updating to 5.0 after many years of using WordPress who will have the most to learn.</p>\n<p>&#8220;Gutenberg does by some measures five or ten measures more than what you could really accomplish in the classic editor,&#8221; Mullenweg said. &#8220;That also means there&#8217;s more buttons, there&#8217;s more blocks. That is part of the idea &#8211; to open up people&#8217;s flexibility and creativity to do things they would either need code or a crazy theme to do in the past. And now we&#8217;re going to open that up to do WordPress&#8217; mission, which is to democratize publishing and make it accessible to everyone.&#8221;</p>\n<p>Gutenberg&#8217;s current state of accessibility has been a hot topic lately and one attendee asked for his thoughts about the recent discussions. Mullenweg said there is room for improvement in how this aspect of the project was handled and that WordPress can work better across teams in the future:</p>\n<blockquote><p>Accessibility has been core to WordPress from the very beginning. It&#8217;s part of why we started &#8211; adoption of web standards and accessibility things. We&#8217;ve been a member of the web standards project for many many years. We did kind of have some project management fails in this process where we had a team of volunteers that felt like they were disconnected from the rapid development that was happening with Gutenberg. Definitely there were some things we could do better there. In the future I think that we need &#8211; I don&#8217;t know if it makes sense to have separate accessibility as a separate kind of process from the core development. It really needs to be integrated at every single stage. We did do a lot, as Matias did a big long post on it. We&#8217;ve done a ton of keyboard accessibility stuff, there&#8217;s ARIA elements on everything. One of their feedbacks was that we did it wrong, but we did it the best that we knew how to and it&#8217;s been in there for awhile. There&#8217;s been over 200 closed issues from really the very beginning. We also took the opportunity to fix some things that had been poorly accessible in WordPress from the beginning. It&#8217;s not that WordPress is perfectly accessible and all WCAG AA and it&#8217;s reverting. It&#8217;s actually that huge swaths of WP are inaccessible &#8211; they just might not be considered core paths from the current accessibility team but I consider them core.</p></blockquote>\n<p>In response to a question about the future of React in WordPress, Mullenweg went more in depth on the vision he had when he urged the WordPress community to <a href=\"https://wptavern.com/state-of-the-word-2015-javascript-and-api-driven-interfaces-are-the-future-of-wordpress\">learn JavaScript deeply in 2015</a>. At that time he said &#8220;it is the future of the web.&#8221; He described how each block can be a launching point for something else &#8211; via a modal, such as updating settings, doing advanced things with an e-commerce store, zooming in and out of those screens from the editor. This was perhaps the most inspirational part of the Q&amp;A where the potential of Gutenberg shines as bright as it did in the early demos.</p>\n<p>&#8220;The other beautiful thing is that because Gutenberg essentially allows for translation into many different formats,&#8221; Mullenweg said. &#8220;It can publish to your web page, your RSS feed, AMP, blocks can be translated into email for newsletters, there&#8217;s so much that the structured nature of Gutenberg and the semantic HTML it creates and the grammar that&#8217;s used to parse it, can enable for other applications. It becomes a little bit like a lingua franca that perhaps even crosses CMS&#8217;s. There&#8217;s now these new cross-CMS Gutenberg blocks will be possible. It&#8217;s not just WordPress anymore. It may be a JavaScript block that was written for Drupal that you install on your WordPress site. I mean, hot diggity! How would that have ever happened before? That&#8217;s why we took two years off; it&#8217;s why we&#8217;ve had everyone in the world working on this thing.&#8221;</p>\n<p>JavaScript is what makes this cross-platform collaboration possible and it&#8217;s already evident in the work the Drupal Gutenberg contributors are doing, as well as the platform-agnostic Gutenberg Cloud project. When Gutenberg is released in 5.0, it will enable more for WordPress and the web than we can predict right now.</p>\n<p>&#8220;This is not the finish line,&#8221; Mullenweg said. &#8220;5.0 is almost like the starting point. Expect just as much time invested into Gutenberg after the 5.0 release as before &#8211; to get it to that place where we don&#8217;t think it&#8217;s just better than what we have today but it&#8217;s actually like a world-class web-defining experience, which is what we want to create and what you all deserve.&#8221;</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:\"Sat, 10 Nov 2018 15:30:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}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:58:\"WPTavern: WordPress 5.0 Release Date Update to November 27\";s:7:\"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=85475\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wptavern.com/wordpress-5-0-release-date-update-to-november-27\";s: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:2548:\"<p>The WordPress 5.0 release date has been pushed back to November 27. The <a href=\"https://make.wordpress.org/core/2018/10/03/proposed-wordpress-5-0-scope-and-schedule/\" rel=\"noopener noreferrer\" target=\"_blank\">previous schedule</a> outlined the possibility of a slip date where the first target date could slip by up to eight days if necessary.</p>\n<p>&#8220;As discussed during the Core devchat this week, the initial November 19th target date is looking a bit too soon for a release date,&#8221; Gutenberg technical lead Matias Ventura said in today&#8217;s announcement on the <a href=\"https://make.wordpress.org/core/2018/11/09/update-on-5-0-release-schedule/\" rel=\"noopener noreferrer\" target=\"_blank\">make.wordpress.org/core</a> blog. &#8220;After listening to a lot of feedback — as well as looking at current issues, ongoing pull requests, and general progress — we’re going to take an extra week to make sure everything is fully dialed in and the release date is now targeted for November 27th.&#8221;</p>\n<p>Ventura outlined a new plan where beta 4 and beta 5 releases will coincide with Gutenberg 4.3 and 4.4 releases. RC1 is expected to be released November 19. He said contributors will be posting daily high level updates on the current status of the release, including things like open pull requests to be reviewed and outstanding bugs, to the #core-editor channel.</p>\n<p>The announcement also includes a short video demonstration of Gutenberg fully integrated with the new default Twenty Nineteen theme.</p>\n<p></p>\n<p>Given the recent <a href=\"https://wptavern.com/calls-to-delay-wordpress-5-0-increase-developers-cite-usability-concerns-and-numerous-bugs-in-gutenberg\" rel=\"noopener noreferrer\" target=\"_blank\">pushback on the timeline</a> from prominent WordPress developers and business owners, the updated November 27 timeline may still not offer enough time to resolve the issues remaining and allow the ecosystem to prepare training materials that accurately reflect late stage UI changes.</p>\n<p>At a spontaneous Q&amp;A session at WordCamp Portland this weekend, Matt Mullenweg said WordPress 5.0 was branched from 4.9.8 so this release has been tightly wound to the previous one to allow for a more seamless transition.</p>\n<p>The next targeted release day falls on the Tuesday after Cyber Monday, which should be a relief to anyone running a WordPress-powered e-commerce site. If WordPress misses the updated November 27 release date, it will be pushed back to the secondary target date of January 22, 2019.</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 Nov 2018 20:06:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"WPTavern: WPWeekly Episode 337 – Gutenberg User Experiences, Release Timelines, and the Classic Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=85470&preview=true&preview_id=85470\";s:7:\"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:109:\"https://wptavern.com/wpweekly-episode-337-gutenberg-user-experiences-release-timelines-and-the-classic-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2142:\"<p>In this episode, <a href=\"http://jjj.me\">John James Jacoby</a> and I break down what&#8217;s happening with Gutenberg. We discuss our trials and tribulations with the editor, the release timeline, and calls from members of the community to delay WordPress 5.0 until January. We also share details on how long the Classic Editor plugin will be supported. Last but not least, we talk about the possible release strategy of shipping point releases every two weeks after WordPress 5.0 is released.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"https://wptavern.com/how-to-add-an-image-to-a-paragraph-block-in-gutenberg\">How to Add an Image to A Paragraph Block in Gutenberg</a></p>\n<p><a href=\"https://wptavern.com/adding-aligned-images-to-paragraphs-in-gutenberg-is-not-as-tough-as-i-thought\">Adding Aligned Images to Paragraphs in Gutenberg Is Not as Tough as I Thought</a></p>\n<p><a href=\"https://wptavern.com/wordpress-5-0-beta-3-released-rc-1-expected-november-12\">WordPress 5.0 Beta 3 Released, RC 1 Expected November 12</a></p>\n<p><a href=\"https://joost.blog/wordpress-5-0-needs-a-different-timeline/\">WordPress 5.0 needs a different timeline    </a></p>\n<p><a href=\"https://mrwweb.com/wordpress-5-0-is-not-ready/\">WordPress 5.0 is Not Ready</a></p>\n<p><a href=\"https://wptavern.com/classic-editor-plugin-may-be-included-with-5-0-updates-support-window-set-to-end-in-2021\">Classic Editor Plugin May Be Included with 5.0 Updates, Support Window Set to End in 2021</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, November 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 #337:</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:\"Fri, 09 Nov 2018 17:21: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:\"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:47:\"Matt: Gutenberg in Portland Oregon and Podcasts\";s:7:\"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=48589\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://ma.tt/2018/11/gutenberg-in-portland-oregon-and-podcasts/\";s: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:1192:\"<p>I&#8217;ve had the opportunity to talk about Gutenberg at two great venues recently. The first was at WordCamp Portland which graciously allowed me to join for a Q&amp;A at the end of the event. The questions were great and covered a lot of the latest and greatest about Gutenberg and WordPress 5.0:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Last week I also joined <a href=\"https://wpbuilds.com/2018/11/08/episode-101-matt-mullenweg-why-gutenberg-and-why-now/\">Episode 101 of the WP Builds podcast</a>, where as Nathan put it: &#8220;We talk about Gutenberg, why Matt thinks that we need it, and why we need it now. We go on to chat about how it’s divided the WordPress community, especially from the perspective of users with accessibility needs.&#8221;</p>\n\n\n\n<p>They may be out of seats already, but <a href=\"https://www.meetup.com/Southern-Maine-WordPress-Meetup/events/256212528/\">I&#8217;ll be on the other coast to do a small meetup in Portland, Maine</a> this week. As we lead up to release and <a href=\"https://2018.us.wordcamp.org/\">WordCamp US</a> I&#8217;m really enjoying the opportunity to hear from WordPress users of all levels all over the country.</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 Nov 2018 04:45:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:114:\"WPTavern: Calls to Delay WordPress 5.0 Increase, Developers Cite Usability Concerns and Numerous Bugs in 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=85371\";s:7:\"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:124:\"https://wptavern.com/calls-to-delay-wordpress-5-0-increase-developers-cite-usability-concerns-and-numerous-bugs-in-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:9585:\"<p>Developers and business owners are waiting anxiously in the wings, as Gutenberg is 11 days away from its debut in WordPress 5.0. There is still a chance that the release could be delayed to the secondary date (January 22, 2019), but the decision has not yet been announced.</p>\n<p>&#8220;I am lukewarm on the 19th, but not because of the number of open issues (which isn&#8217;t a good measure or target) — more that we&#8217;ve been a day or two behind a few times now,&#8221; 5.0 release lead Matt Mullenweg said during yesterday&#8217;s dev chat. He said that reports &#8220;from the field&#8221; continue to be good and companies that have already installed and activated the plugin haven&#8217;t reported a higher than normal support burden.</p>\n<p>&#8220;My concern can be summed up as this,&#8221; Aaron Jorbin said. &#8220;There are approximately 400 issues that need either code or a decision to punt. Assuming five minutes per issue, that means there are about 33 hours worth of bug scrubs that need to take place between now and RC.&#8221;</p>\n<p>&#8220;I don’t think we can make a decision on moving the date in the next 45 minutes,&#8221; Gary Pendergast said in response to concerns raised at the meeting. &#8220;I do think it’s fair to say that the Gutenberg and 5.0 leadership teams are hearing all the feedback, and are actively looking whether the timeline is still correct.&#8221;</p>\n<p>Mullenweg said open issues are not a good measure of whether the release is on target but the numerous bugs the community is encountering has precipitated a flurry of posts advocating for the release to be delayed.</p>\n<p>In a post titled &#8220;<a href=\"https://joost.blog/wordpress-5-0-needs-a-different-timeline/\" rel=\"noopener noreferrer\" target=\"_blank\">WordPress 5.0 needs a different timeline</a>,&#8221; Joost de Valk, author of <a href=\"https://wordpress.org/plugins/wordpress-seo/\" rel=\"noopener noreferrer\" target=\"_blank\">Yoast SEO</a>, cites accessibility concerns and the stability of the project as reasons for a delay. de Valk identifies himself a strong supporter of Gutenberg and his team has already built compatibility and <a href=\"https://wptavern.com/yoast-seo-8-2-adds-how-to-and-faq-gutenberg-blocks-with-structured-data\" rel=\"noopener noreferrer\" target=\"_blank\">Gutenberg-first features</a> into their plugin, which has more than 5 million active installs.</p>\n<p>&#8220;It’s arguably one of the biggest leaps forward in WordPress’ editing experience and its developer experience in this decade,&#8221; de Valk said. &#8220;It’s also not done yet, and if we keep striving for its planned November 19th release date, we are setting ourselves up for failure.&#8221;</p>\n<p>de Valk gave two reasons for why he believes the November 19th timeline to be untenable:</p>\n<blockquote><p>There are some <a href=\"https://make.wordpress.org/accessibility/2018/10/29/report-on-the-accessibility-status-of-gutenberg/\" rel=\"noopener noreferrer\" target=\"_blank\">severe accessibility concerns</a>. While these aren’t new and a few people are working hard on them, I actually think we can get a better handle on fixing them if we push the release back. Right now it looks to me as though keyboard accessibility has regressed in the last few releases of Gutenberg.</p>\n<p>The most important reason: the overall stability of the project isn’t where it needs to be yet. There are so many open issues for the 5.0 milestone that even fixing all the blockers before we’d get to Release Candidate stage next week is going to prove impossible. We have, at time of writing <a href=\"https://github.com/wordpress/gutenberg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+no%3Amilestone+label%3A%22%5BType%5D+Bug%22+-label%3A%22future%22+\" rel=\"noopener noreferrer\" target=\"_blank\">212 untriaged bugs</a> and <a href=\"https://github.com/wordpress/gutenberg/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22WordPress+5.0%22\" rel=\"noopener noreferrer\" target=\"_blank\">165 issues on the WordPress 5.0 milestone</a>.</p></blockquote>\n<p>WordPress developer Mark Root-Wiley published a post the same day titled &#8220;<a href=\"https://mrwweb.com/wordpress-5-0-is-not-ready/\" rel=\"noopener noreferrer\" target=\"_blank\">WordPress 5.0 is Not Ready</a>.&#8221; He outlined why he believes the release needs to be delayed and suggested the project pursue more auditing and quality assurance testing before shipping it out.</p>\n<p>&#8220;WordPress 5.0 can and should be a positive change to WordPress, but if it is released in late November as planned, it won’t be,&#8221; Root-Wiley said. &#8220;There are simply too many bugs in the editor, and the experience is not polished enough. This is because the rate of development has prevented systematic quality assurance (QA) and user testing. Both types of testing are required to ensure the editor is ready and to increase the community’s confidence in the update.&#8221;</p>\n<p>Root-Wiley describes a buggy experience when attempting to write blog posts with the new editor, which echoes many others&#8217; <a href=\"https://jjj.blog/2018/10/wordpress-5-0-beta-1/\" rel=\"noopener noreferrer\" target=\"_blank\">recent</a> <a href=\"https://twitter.com/mor10/status/1060255182552854528\" rel=\"noopener noreferrer\" target=\"_blank\">experiences</a>.</p>\n<p>&#8220;I’m doing my best to give feedback, but it’s exhausting and there are so many little bugs that I struggle to isolate and replicate the one I’m reporting without running into another,&#8221; Root-Wiley said. &#8220;How is it possible for me to find so many bugs without trying from just writing 1.5 blog posts?&#8221;</p>\n<p>Root-Wiley also suggested removing what he deemed to be unnecessary features in order to streamline the editing experience and focus on the fundamentals. These features include the tables block, paragraph background colors, spotlight and fullscreen mode, dropcaps, verse block, among others.</p>\n<p>&#8220;The pace of development has been blistering,&#8221; Root-Wiley said. &#8220;That speed has been great for developing a lot of features and iterating on those features quickly, but it hasn’t allowed for sufficient testing. What’s needed now is more time for people to find and report bugs with the editor features in their proposed final state.&#8221;</p>\n<p>Gutenberg criticism is often characterized as coming from people who are resistant to change, but these strong messages about delaying the release come from developers who believe the new editor is the future and have heavily invested in contributing to its success.</p>\n<p>Both de Valk and Root-Wiley&#8217;s posts seem to have resonated with many who have had similar experiences with the editor. Other core developers and committers have also publicly lent their voices to the call to delay the release.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">My thoughts are very much aligned here. I\'m super excited for the release &#8212; I think it\'s crucial for WordPress\' success. But I don\'t think it, nor the ecosystem, are quite ready following the shortened release cycle. <a href=\"https://t.co/R0nZt0mk41\">https://t.co/R0nZt0mk41</a></p>\n<p>&mdash; Mike Schroder (@GetSource) <a href=\"https://twitter.com/GetSource/status/1060238359660912640?ref_src=twsrc%5Etfw\">November 7, 2018</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">This: <a href=\"https://t.co/wpcQ02qcTw\">https://t.co/wpcQ02qcTw</a>  They are missing almost every milestone on their release schedule, leaving me 1 week to test with RC before Thanksgiving, and plugin/theme authors no time to develop/test with stabler code. It should just come out with their backup January date.</p>\n<p>&mdash; Lisa Woodruff (@lisa_m_woodruff) <a href=\"https://twitter.com/lisa_m_woodruff/status/1060533833899171841?ref_src=twsrc%5Etfw\">November 8, 2018</a></p></blockquote>\n<p></p>\n<p>Opinions on Gutenberg&#8217;s readiness vary wildly depending on the person&#8217;s perspective and involvement in the project. Those who are working on it full-time have not publicly offered opinions indicating that it might not be ready for the November 19 timeline.</p>\n<p>&#8220;The 5.0 milestone is in a very manageable place, but if the volume becomes more worrying in the next couple days or it becomes clear milestones won’t be made, we’ll revise as needed,&#8221; Gutenberg technical lead Matias Ventura Ventura said during yesterday&#8217;s dev chat. He confirmed that the fast pace of development will continue.</p>\n<p>Regardless of when 5.0 is released, users can count on getting minor releases every two weeks to address bugs and issues that pop up after Gutenberg is in the hands of millions more users.</p>\n<p>&#8220;Hopefully as people get used to the more regular cadence they can plan around it, much like they used to complain a ton about, but then got used to, 3 major releases a year,&#8221; Mullenweg said during the dev chat.</p>\n<p>In 2016, Mullenweg began describing how WordPress could become &#8220;the operating system of the web,&#8221; with open APIs that others can build on. While that idea encompasses a lot more than just release schedules, WordPress seems to be moving in the direction of shipping updates that come more frequently and eventually more invisibly in the background, similar to how users update their browsers. Releasing Gutenberg in its current state, with frequent updates following, could prove to be a major testing ground to see if greater world of WordPress users are ready to embrace this new era of rapid iteration.</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 Nov 2018 00:03:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:87:\"WPTavern: Adding Aligned Images to Paragraphs in Gutenberg Is Not as Tough as I Thought\";s:7:\"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=85417\";s:7:\"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/adding-aligned-images-to-paragraphs-in-gutenberg-is-not-as-tough-as-i-thought\";s: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:4126:\"Last week, I published <a href=\"https://wptavern.com/how-to-add-an-image-to-a-paragraph-block-in-gutenberg\">an article</a> that describes the process I went through in Gutenberg to try to add an aligned image to a paragraph block. I concluded that performing the task in the Classic Editor was easier than in Gutenberg.\n\n\n\nIn response to the article, William Earnhardt <a href=\"https://wearnhardt.com/2018/11/the-gutenberg-complexity-fallacy/\">compared the process</a> and showed how it can be accomplished in two steps in Gutenberg.\n\n\n\n\n<ol><li>Drag an image into editor where you want it to go. </li><li>Click align right. </li></ol>\n\n\n\n\nDragging and dropping images into WordPress is not something I do. It&#8217;s not how I write. His method is simpler but I prefer to work within the interface. His second suggestion of accomplishing the task is the method I&#8217;ll use from now on.\n\n\n\n\n<ol><li>Click the block inserter above the paragraph you want to insert the image before.</li><li>Select the image block.</li><li>Drag the image onto the block.</li><li>Click align right.</li></ol>\n\n\n\n\nIn the last few months of using Gutenberg, I&#8217;ve become accustomed to adding new blocks by pressing enter at the end of a paragraph block or by clicking the plus sign to the left of a block. I haven&#8217;t used the plus sign between blocks but it makes sense and indeed, it&#8217;s quicker to accomplish the task.\n\n\n\nAccording to Earnhardt, there are even more ways to complete the task in Gutenberg. This brings up an important question, how many different ways and user interfaces should there be to accomplish a task? If you don&#8217;t do it a certain way, are you <a href=\"https://developer.wordpress.org/reference/functions/_doing_it_wrong/\">doing_it_wrong</a>?\n\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n\nTake for example, adding captions to images. In Gutenberg, there are at least two opportunities to add a caption. The first is the attachment details screen after uploading or selecting an image from the media library.\n\n\n\nThe second is the Image block user interface. When using the Image block interface, my cursor gets stuck in the caption area and I need to click outside of the block in order to continue. If I use the attachment details screen, it automatically puts the caption text into the image block, bypassing the hurdle. Which interface am I supposed to use and which method is considered doing_it_wrong?<br />\n\n\n\n\n<div class=\"wp-block-image\"><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/11/2018-11-08_00-56-29-1.gif?ssl=1\"><img /></a>Adding a Caption via the Image Block Interface</div>\n\n\n\n\n\n<h2>I&#8217;m Willing to Learn</h2>\n\n\n\n\nI understand the long vision of Gutenberg and what it means for the future of WordPress. For the past several months, I&#8217;ve used the plugin and interface exclusively to craft content.\n\n\n\nI&#8217;ve been learning things along the way and trying to readjust my workflows but the question I keep coming back to when doing things in Gutenberg is why?\n\n\n\nWhy is this button hidden? Why are there three differently located buttons to add blocks when it would be nice to memorize one? Why does this do that and vice versa? Where is all of the research and usability testing that explains the why behind so many of the interactions and flows? Am I just a moron or is it the interface that guides me in the wrong direction?\n\n\n\nMany of my experiences in using Gutenberg this past year have been <a href=\"https://mrwweb.com/wordpress-5-0-is-not-ready/\">echoed by Mark Root-Wiley</a>. He does a great job of saying what I&#8217;ve been feeling and thinking for a long time.\n\n\n\nWhen I and thousands of others watched Matías Ventura‏ perform a <a href=\"https://www.youtube.com/watch?v=XOY3ZUO6P0k&feature=youtu.be\">live demo</a> of Gutenberg at the 2017 State of Word, people were blown away. But this is someone who has been creating Gutenberg from the core and is proficient in all that it offers. Is this the level of Gutenberg proficiency I and others need in order to get things done? Probably not, but at times, it sure feels that way. <br />\";s: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 Nov 2018 07:37:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:99:\"WPTavern: Classic Editor Plugin May Be Included with 5.0 Updates, Support Window Set to End in 2021\";s:7:\"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=85387\";s:7:\"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:109:\"https://wptavern.com/classic-editor-plugin-may-be-included-with-5-0-updates-support-window-set-to-end-in-2021\";s: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:6806:\"<p>Gary Pendergast <a href=\"https://make.wordpress.org/core/2018/11/07/classic-editor-plugin-support-window/\" rel=\"noopener noreferrer\" target=\"_blank\">announced</a> this morning that the <a href=\"https://wordpress.org/plugins/classic-editor/\" rel=\"noopener noreferrer\" target=\"_blank\">Classic Editor</a> plugin will be officially supported until December 31, 2021. The plugin eases the transition for sites where plugins or themes are not yet compatible with Gutenberg and gives users the opportunity to preserve their existing workflows.</p>\n<p>&#8220;Since the Classic Editor plugin is central in this transition, we are considering including it with upgrades to WordPress 5.0,&#8221; Pendergast said. &#8220;New WordPress installs would still add it manually, and we’ve included it in the Featured Plugins list to increase visibility. If you have thoughts on this idea, please leave a comment.&#8221;</p>\n<p>Pendergast clarified that &#8220;officially supported&#8221; means that the plugin &#8220;will be guaranteed to work as expected in the most recent major release of WordPress, and the major release before it.&#8221; He also said the project will evaluate the continuing maintenance of the plugin in 2021 and may possibly extend the date.</p>\n<p>The post has already received quite a bit of feedback and generally positive reactions to the prospect of including the Classic Editor along with 5.0 updates for existing sites.</p>\n<p>WordPress Core Committer Pascal Birchler asked for a clarification on what &#8220;we&#8221; referred to in Pendergast&#8217;s post, and Pendergast clarified that he is speaking on behalf of the WordPress project. Other commenters pressed for more information, as the announcement was delivered as something that had already been decided and the conversation surrounding the decision was not public.</p>\n<p>&#8220;I’m grateful for the communication on a hard date for support of the classic editor,&#8221; Darren Ethier commented on the post. &#8220;It helps many people depending on WordPress for their livelihood to make plans surrounding things depending on it. But for volunteers who &#8216;show up&#8217; at meetings and in contributing, the process for arriving at these kinds of decisions in an open source project is very opaque and seems to be increasingly so.&#8221;</p>\n<p>This announcement highlights a trend in recent decision making for the project where decisions on important items appear to have been made behind closed doors without community input. Matthew MacPherson&#8217;s <a href=\"https://wptavern.com/gutenberg-accessibility-audit-postponed-indefinitely\" rel=\"noopener noreferrer\" target=\"_blank\">proposal for an independent accessibility audit</a>, which had broad support from the community, was shut down in a similar way. MacPherson was named WordPress 5.0&#8217;s accessibility lead but didn&#8217;t seem to be fully vested with the power to lead that aspect of the release in the community&#8217;s best interests. I asked MacPherson if he could further clarify how the decision to forego the audit was reached, as it seemed even a surprise to him in the GitHub issue thread. He said he had &#8220;no comment&#8221; on how the decision came about.</p>\n<p>WPCampus is now <a href=\"https://wptavern.com/wpcampus-is-pursuing-an-independent-accessibility-audit-of-gutenberg\" rel=\"noopener noreferrer\" target=\"_blank\">pursuing an accessibility audit</a> in order to better serve its community of more than 800 web professionals, educators, and others who work with WordPress in higher education.</p>\n<p>&#8220;We&#8217;re receiving a lot of interest and I&#8217;m holding meetings with potential vendors to answer their questions,&#8221; WPCampus director Rachel Cherry said. &#8220;We&#8217;ve received a lot of messages from individuals and organizations wanting to contribute financially.&#8221;</p>\n<p>The <a href=\"https://wptavern.com/wordpress-accessibility-team-delivers-sobering-assessment-of-gutenberg-we-have-to-draw-a-line\" rel=\"noopener noreferrer\" target=\"_blank\">recent report from the accessibility team</a> demonstrates critical issues that prevent the team from recommending Gutenberg to users of assistive technology. These issues also have a major impact on those using WordPress for higher education, as the law requires them to meet certain standards. Several in this particular industry commented on Pendergast&#8217;s post to advocate for shipping the Classic Editor plugin with new installs as well.</p>\n<p>&#8220;Many organizations who use WordPress are required by law to provide accessible software under Section 508,&#8221; Rachel Cherry said. &#8220;Until such a time when the accessibility of Gutenberg has been improved, and Section 508 compliance is clear, these organizations will require use of the Classic Editor.</p>\n<p>&#8220;Not to mention the users who will be dependent upon the Classic Editor to have an accessible publishing experience.</p>\n<p>&#8220;Please consider bundling Classic Editor with all versions of core, new and updated, going forward so that every end user has the easy and inclusive option of using it from day one.&#8221;</p>\n<p>Elaine Shannon, another WordPress user who works in academia, also commented on the Pendergast&#8217;s post to recommend having the Classic Editor bundled with new versions of WordPress, due to many education sites running on multisite installations.</p>\n<p>&#8220;Some institutions are on managed hosts, where they’ll receive 5.0 without initiating the update themselves,&#8221; Shannon said. &#8220;Others are managed by on-campus IT services, where one campus admin will push the update and affect thousands of users. In many cases, these are MultiSites where end users – the ones who need the choice of whether to use Gutenberg or Classic Editor – do not have the ability to add a plugin. So regardless of whether these users are in a brand-new shiny install or just an updated existing one, many users are going to need to fall back to the Classic Editor, and if it’s not bundled with Core there will be some folks left having to contact their administrator.&#8221;</p>\n<p>Pendergast&#8217;s post said the WordPress project is considering including the plugin with upgrades to 5.0 but did not identify where or when that decision will be made. However, users who depend on the plugin now have a clear idea of how long it will be supported.</p>\n<p>&#8220;As for the EOL on Classic Editor support, that’s probably more clarity than [the core team] has ever really given on a feature-to-plugin transition and I’m in favor of having that hard date,&#8221; WordPress core developer Drew Jaynes said. &#8220;It sets the right tone that the plugin is not intended as a long-term solution, rather a stopgap with a definitive EOL.&#8221;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 07 Nov 2018 20:13:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\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: Nidhi Jain Is Awarded the Kim Parsell Travel Scholarship\";s:7:\"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=85390\";s:7:\"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/nidhi-jain-is-awarded-the-kim-parsell-travel-scholarship\";s: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:1553:\"In 2015, the WordPress Foundation <a href=\"https://wptavern.com/the-wordpress-foundation-creates-a-traveling-scholarship-in-memory-of-kim-parsell\">created a travel scholarship</a> in memory of <a href=\"https://wptavern.com/kim-parsell-affectionately-known-as-wpmom-passes-away\">Kim Parsell</a>. The <a href=\"https://2018.us.wordcamp.org/kim-parsell-memorial-scholarship-2018/\">scholarship</a> covers travel expenses, lodging, and a ticket to the event. This year&#8217;s recipient is <a href=\"https://twitter.com/jainnidhi03\">Nidhi Jain</a> from Udaipur, Rajasthan, India. \n\n\n\nJain is a volunteer organizer for WordCamp Udaipur, a WordPress developer, contributor, and a seasoned traveler. <br />\n\n\n\n&#8220;Being selected for the Kim Parsell Memorial Scholarship is an honor, achievement and a proud moment for me,&#8221; Jain told the WordCamp US organizing team when asked what it means to be selected.  \n\n\n\n&#8220;I will try my best to make the most out of it and give back to the community in all possible ways. Since I have been a WordCamp volunteer and organizer in the last few years, I am excited to see and learn from WordCamp US. I am sure, I will have a lot of sweet memories and wonderful learnings to take back home.&#8221;\n\n\n\nPrevious winners include Elizabeth Shilling in 2016 and Bianca Welds in 2017. If you&#8217;re not familiar with who Kim Parsell is, I recommend reading <a href=\"https://heropress.com/essays/family-well-loved/\">this essay</a> which provides some context as to why the scholarship was created in her memory. <br />\";s: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 Nov 2018 13:59: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: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:30:\"HeroPress: Accidental Activist\";s:7:\"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=2648\";s:7:\"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/accidental-activist/#utm_source=rss&utm_medium=rss&utm_campaign=accidental-activist\";s: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:12230:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2019/11/110618-1024x512.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: Imagine a world where more kinds of people are speaking up. That\'s a world I\'m excited to see.\" /><p>I never meant to become an activist. I swear. It was an accident.</p>\n<p>And yet here I am, celebrating my one year anniversary of leading the Diversity Outreach Speaker Training working group in the WordPress Community team. We are causing waves in the number of women and other underrepresented groups who are stepping up to become speakers at WordPress Meetups, WordCamps, and events. Pretty cool, right?</p>\n<p>How did this happen?</p>\n<p>Let’s start this story with how I got into WordPress. Back in 2011, I was looking for a practicum placement for the New Media Design and Web Development college program I was in in Vancouver, BC. We had touched on WordPress only briefly in class. I was curious about it, so I got a Practicum placement working on a higher education website that was built in WordPress. (It was in BuddyPress, even! Ooh. Aah.) As a thank you, my practicum advisor bought me a ticket to WordCamp Vancouver 2011: Developer’s Edition. That event was the start of my love affair with WordPress and I began taking on freelancing gigs. I’ve been a WordPress solopreneur for most of the time since.</p>\n<p>The following year my practicum advisor, who had become a client, was creating the first ever BuddyCamp for BuddyPress. He asked me to be on his organizing team. (Side note: I was especially excited to moderate a panel with Matt Mullenweg and other big names on it!) I was noticed and I was invited to be on the core organizing team for the next year’s WordCamp Vancouver by the lead organizer. I was thrilled. It was quite an honour!</p>\n<p>This is where the real story begins… after an important disclaimer.</p>\n<blockquote><p>Disclaimer: For simplicity in this story, I’ll be using the terms women and men, though in reality gender is not a simple binary and is actually a wide spectrum of different identities.</p></blockquote>\n<h3>The Real Beginning</h3>\n<p>There were three of us—myself and two men—and it was our first time any of us were organizing a WordCamp. We were having dinner in one of our apartments and we had 40 speaker applications spread out before us. The plan was to pick 14 to speak. It was hard. They were all really good.</p>\n<p>The lead organizer grabbed 6 out of the 7 that came from the women and said, &#8220;Well, we are accepting all of these.&#8221;</p>\n<p>At this point I didn’t know that not many women were applying to speak at tech conferences at the time.</p>\n<blockquote><p>So I was the one saying, &#8220;Wait, wait. Who cares what gender they are? Let’s go through them and pick based on the topics that would fit the conference’s flow.&#8221;</p></blockquote>\n<p>They both said that the 6 of the women’s pitches were really good, fit with the flow, and frankly, we needed to accept as many as we could or we’d get called out. (This is embarrassing to say now, but that was the conversation back in 2013.)</p>\n<p>Here’s how it went down:</p>\n<p>After we accepted the six, two of the women dropped out for family emergencies. (Guess how many men dropped out for family emergencies?) Also we had added a third speakers’ track. Now there were only 4 women out of 28 speakers. Only 1 in 7. That is 14%, my friends. That is not great.</p>\n<p>So not great, in fact, that we did get called out. People did talk about it, question us about it, and even wrote blog posts about it.</p>\n<h3>More Experience</h3>\n<p>So when later that year I went to WordCamp San Francisco—the biggest WordCamp at the time (before there was a WordCamp US)—I took the opportunity to chat with other organizers at a WordCamp organizer brunch.</p>\n<blockquote><p>I found out that many of the organizers had trouble getting enough women presenters.</p></blockquote>\n<p>I was surprised to find that we actually had a high number of women applicants in comparison to others, as many of them had zero! They were asking me how we got such a high number. They all said they would happily accept more if only more would apply.</p>\n<p>So then I needed to know, why was this happening? Why weren’t we getting more women applicants? I started researching, reading, and talking to people.</p>\n<p>Though this issue is complex, one thing that came up over and over was that when we would ask the question, &#8220;Hey, will you speak at my conference?&#8221; we would get two answers:</p>\n<ul>\n<li>&#8220;What would I talk about?&#8221;</li>\n<li>&#8220;I’m not an expert on anything. I don’t know enough about anything to give a talk on it.&#8221;</li>\n</ul>\n<p>That’s when the idea happened.</p>\n<h3>The Idea</h3>\n<p>As it goes, the idea happened while I was at a feminist blanket-fort slumber party. Yes, you heard right. And as one does at all feminist blanket-fort slumber parties, we talked about feminist issues.</p>\n<p>When I brought up my issue about the responses we were getting, one of the ladies said, &#8220;Why don’t you get them in a room and have them brainstorm topics?&#8221;</p>\n<blockquote><p>And that was it. That set me on the path.</p></blockquote>\n<p>I became the lead of a small group creating a workshop in Vancouver. In one of the exercises, we invited the participants to brainstorm ideas and show them that they have literally a hundred ideas. (Then the biggest problem becomes picking one. <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" /> )</p>\n<p>In our first iteration, we covered:</p>\n<ul>\n<li>Why it matters that women (<em>added later: diverse groups</em>) are in the front of the room</li>\n<li>The myths of what it takes to be the speaker at the front of the room (aka beating impostor syndrome)</li>\n<li>Different speaking formats, especially story-telling</li>\n<li>Finding and refining a topic</li>\n<li>Tips to becoming a better speaker</li>\n<li>Practising leveling up speaking in front of the group throughout the afternoon</li>\n</ul>\n<p>Other cities across North America got wind of our workshop and started running it as well, and they added their own material.</p>\n<p>Our own participants wanted more support, so the next year we added material created from the other cities as well as generated more of our own:</p>\n<ul>\n<li>Coming up with a great title</li>\n<li>Writing a pitch that is more likely to get accepted</li>\n<li>Writing a bio</li>\n<li>Creating an outline</li>\n<li>Creating better slides</li>\n</ul>\n<p>We did it! In 2014—in only one year since we started—we had 50% women speakers and 3 times the number of women applicants! Not only that, but it was a Developer’s Edition. It&#8217;s more challenging it is to find women developers in general, let alone those who will step up to speak.</p>\n<h3>Building On</h3>\n<p>Impressive as that is, the reason I am truly passionate about this work is because of what happened next:</p>\n<ul>\n<li>Some of the women who did our workshop and started publicly speaking stepped up to be leaders in our community and created new things for us. For example, a couple of them created a new Meetup track with a User focus.</li>\n<li>A handful of others became WordCamp organizers. One year Vancouver had an almost all-female organizing team – 5 out of 6!</li>\n<li>It also influenced local businesses. One local business owner loved what one of the women speakers said so much that he hired her immediately. She was the first woman developer on the team, and soon after she became the Senior Developer.</li>\n</ul>\n<p>It is results like these that ignited my passion. I’ve now seen time and again what happens when different kinds of folks speak in the front of the room. More kinds of people feel welcome in the community. The speakers and the new community members bring new ideas and new passions that help to make the technology we are creating more inclusive as well as generate new ideas that benefit everyone.</p>\n<p>This workshop has been so successful, with typical results of 40-60% women speakers at WordCamps, that the WordPress Community Team asked me to promote it and train it for women and all diverse groups around the world. We created the Diversity Outreach Speaker Training working group. I started creating and leading it in late 2017.</p>\n<blockquote><p>Thanks to our group, our workshop has been run in 17 cities so far this year, 32 have been trained to run it, and 53 have expressed interest in 24 countries. Incredible!</p></blockquote>\n<p>I love this work so much that I’m now looking at how to do this for a living. I’m proud of how the human diversity represented on the stage adds value not only to the brand but also in the long-term will lead to the creation of a better product. I’m inspired by seeing the communities change as a result of the new voices and new ideas at the WordPress events.</p>\n<p><strong>&#8220;Jill’s leadership in the development and growth of the Diversity Outreach Speaker Training initiative has had a positive, measurable impact on WordPress community events worldwide. When WordPress events are more diverse, the WordPress project gets more diverse — which makes WordPress better for more people.&#8221;</strong></p>\n<p><em>&#8211; Andrea Middleton, Community organizer on the WordPress open source project</em></p>\n<p>I’m exploring sponsorships, giving conference and corporate trainings, and looking at other options so that I can be an Accidental Activist full-time and make a bigger impact. Imagine a world where more kinds of people are speaking up. That’s a world I’m excited to see.</p>\n<h3>Resources:</h3>\n<p>Workshop: <a href=\"http://diversespeakers.info/\">http://diversespeakers.info/</a></p>\n<p>More info and please let us know if you use it or would like help using it: <a href=\"https://tiny.cc/wpwomenspeak\">https://tiny.cc/wpwomenspeak</a></p>\n<p>Diversity Outreach Speaker Training Team—Join us! <a href=\"https://make.wordpress.org/community/2017/11/13/call-for-volunteers-diversity-outreach-speaker-training/\">https://make.wordpress.org/community/2017/11/13/call-for-volunteers-diversity-outreach-speaker-training/</a></p>\n<p>How to build a diverse speaker roster: Coming soon. Contact Jill for it.</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: Accidental Activist\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=Accidental%20Activist&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Faccidental-activist%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: Accidental Activist\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Faccidental-activist%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%2Faccidental-activist%2F&title=Accidental+Activist\" rel=\"nofollow\" target=\"_blank\" title=\"Share: Accidental Activist\"></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/accidental-activist/&media=https://heropress.com/wp-content/uploads/2019/11/110618-150x150.jpg&description=Accidental Activist\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: Accidental Activist\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/essays/accidental-activist/\" title=\"Accidental Activist\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/accidental-activist/\">Accidental Activist</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 Nov 2018 12: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Jill Binder\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}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:114:\"WPTavern: Authors of Popular WordPress.org Themes Rolling Out Gutenberg Compatibility Updates Ahead of 5.0 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:29:\"https://wptavern.com/?p=85247\";s:7:\"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:125:\"https://wptavern.com/authors-of-popular-wordpress-org-themes-rolling-out-gutenberg-compatibility-updates-ahead-of-5-0-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:5506:\"<p><a href=\"https://wordpress.org/themes/astra/\" rel=\"noopener noreferrer\" target=\"_blank\">Astra</a>, a free theme that has steadily been growing in popularity, is now <a href=\"https://wpastra.com/gutenberg-compatible/\" rel=\"noopener noreferrer\" target=\"_blank\">fully compatible with Gutenberg</a>. The theme was first released in May 2017 and has more than 100,000 active installations. It was downloaded approximately 2,000 &#8211; 4,500 times per day over the past month and currently maintains a 5-star average rating on WordPress.org after 844 reviews.</p>\n<p>Astra&#8217;s creators advertise the theme as fast, lightweight (less than 50KB on frontend), and compatible with many page builders. These features have been key to its rapid growth. Last week they announced full Gutenberg compatibility, which means sites built with Astra will be able to take advantage of all the new features in the editor when 5.0 is released.  </p>\n<p>Astra&#8217;s Gutenberg compatibility update includes front-end styles displayed in the editor and support for the full-width alignment option. The width of the content in the editor matches that of the frontend, and the same is true for the typography, colors, and background.</p>\n<p><a href=\"https://i0.wp.com/wptavern.com/wp-content/uploads/2018/11/gutenberg-full-width.gif?ssl=1\"><img /></a></p>\n<p>The theme also ensures that the default Gutenberg blocks, i.e. quotes and galleries, will inherit Astra customizer styles to match the rest of the site. </p>\n<p>Astra&#8217;s creators support the theme by offering commercial <a href=\"https://wpastra.com/pricing/\" rel=\"noopener noreferrer\" target=\"_blank\">packages</a> that include additional features and plugins, <a href=\"https://wpastra.com/ready-websites/\" rel=\"noopener noreferrer\" target=\"_blank\">starter sites</a>, add-ons for page builders, and support. They plan to offer additional Gutenberg features in commercial add-ons. Astra&#8217;s Ultimate Addons product will introduce custom blocks, such as Section, Heading, Info Box, Post Grid, Google Map, Table, Social Share, Menu, Buttons, along with pre-made starter templates.</p>\n<p>After two months of weekend work, Anders Norén reported that <a href=\"https://wordpress.org/themes/author/anlino/\" rel=\"noopener noreferrer\" target=\"_blank\">all 18 of his free themes on WordPress.org</a> have been <a href=\"http://www.andersnoren.se/the-gutenberg-update/\" rel=\"noopener noreferrer\" target=\"_blank\">updated to be compatible with Gutenberg</a>. Norén&#8217;s popular minimalist style themes have a cumulative rating of 4.97 out of 5 stars and have been downloaded more than <a href=\"http://wptally.com/?wpusername=anlino\" rel=\"noopener noreferrer\" target=\"_blank\">2.2 million times</a>. They are active on an estimated 100,000 WordPress installations.</p>\n<p>&#8220;There are no custom blocks or other fancy stuff to be found in the updates, but if you’re running one of my themes, you should be able to update to WordPress 5.0 and start using Gutenberg without any hitches, in the editor or on the front-end,&#8221; Norén said. &#8220;If you plan to keep using the classic editor, things should look mostly the same after you install the update.&#8221;</p>\n<p>The Gutenberg compatibility update for Norén&#8217;s themes includes editor styles, with layout, typography and colors matching the theme, styles for core blocks and new alignment options, and custom font sizes and color palette in the editor. Norén also took the opportunity to do an overall code cleanup and add improvements for older versions of PHP, accessibility and localization improvements, and bug fixes, amounting to 17,525 lines of code added or modified.</p>\n<p>&#8220;The past couple of weekends have been grueling, but knowing that my themes will be ready for WordPress 5.0 – whether it hits the November 20th release date or not – was worth it,&#8221; Norén said.</p>\n<p>Themeisle has updated <a href=\"https://wordpress.org/themes/hestia/\" rel=\"noopener noreferrer\" target=\"_blank\">Hestia</a> with Gutenberg compatibility in the theme&#8217;s <a href=\"https://themeisle.com/blog/hestia-2-0/\" rel=\"noopener noreferrer\" target=\"_blank\">2.0 release</a>. The popular Material Design WordPress theme is the company&#8217;s flagship product and is installed on more than 100,000 WordPress sites. The company is planning to release a brand new theme that will be fully Gutenberg compatible. They have not yet announced if <a href=\"https://wordpress.org/themes/zerif-lite/\" rel=\"noopener noreferrer\" target=\"_blank\">Zerif Lite</a> (100,000+ installs) will be updated for the new editor.</p>\n<p>Six weeks ago, <a href=\"https://wordpress.org/themes/search/Gutenberg/\" rel=\"noopener noreferrer\" target=\"_blank\">searching the WordPress.org Theme Directory for “Gutenberg”</a> produced 26 results where compatibility is mentioned in the theme descriptions. That number has jumped to 53. Support for the new editor seems to have happened much faster in the commercial theme space where <a href=\"https://themeforest.net/category/wordpress?term=Gutenberg\" rel=\"noopener noreferrer\" target=\"_blank\">searching for Gutenberg on Envato</a> already turns up hundreds of results before the editor has even landed in core. Authors of free themes on WordPress.org don&#8217;t always have the same motivation. Those who support popular themes are more likely to have their themes compatible by the time WordPress 5.0 arrives, especially if the free theme is connected to a paid product.</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 Nov 2018 04:34: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:66:\"WPTavern: WordPress 5.0 Beta 3 Released, RC 1 Expected November 12\";s:7:\"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=85224\";s:7:\"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-5-0-beta-3-released-rc-1-expected-november-12\";s: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:6909:\"<p><a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-3/\" rel=\"noopener noreferrer\" target=\"_blank\">WordPress 5.0 Beta 3</a> was released this morning. This beta incorporates all the changes from <a href=\"https://make.wordpress.org/core/2018/10/31/whats-new-in-gutenberg-31st-october-2/\" rel=\"noopener noreferrer\" target=\"_blank\">Gutenberg 4.2 RC1</a>, which was released last week. It fixes a bug with the display of the custom fields meta box and also improves REST API requests.</p>\n<p>Gutenberg has undergone a few UI tweaks and introduces a <a href=\"https://github.com/WordPress/gutenberg/pull/10209\" rel=\"noopener noreferrer\" target=\"_blank\">Formatting API</a> for adding new RichText components. The inserter between blocks was updated to provide a more consistent experience that matches the other “add block” buttons. Version 4.2 also adds support for displaying icons in new block categories to better organize groups of blocks. The example pictured in the release post shows the Jetpack icon. The Jetpack team has been <a href=\"https://wptavern.com/jetpack-6-6-improves-site-verification-tools-asset-cdn-module-now-in-beta-gutenberg-blocks-coming-soon\" rel=\"noopener noreferrer\" target=\"_blank\">working on a number of blocks for existing features</a> and is expected to release those soon.</p>\n<p><a href=\"https://i0.wp.com/wptavern.com/wp-content/uploads/2018/11/block-categories.png?ssl=1\"><img /></a></p>\n<p>WordPress 5.0 Beta 3 brings in updates from Twenty Nineteen&#8217;s GitHub repository, including support for selective refresh widgets in the customizer, support for responsive embeds, and tweaks to improve the experience on mobile devices.</p>\n<h3>Updates to WordPress 5.0 Schedule: More Beta Releases and a Shortened RC Period</h3>\n<p>WordPress 5.0 is now two weeks away from its <a href=\"https://make.wordpress.org/core/5-0/\" rel=\"noopener noreferrer\" target=\"_blank\">projected release date</a> of November 19. Last week Gary Pendergast announced some <a href=\"https://make.wordpress.org/core/2018/10/31/wordpress-5-0-schedule-updates/\" rel=\"noopener noreferrer\" target=\"_blank\">updates to the 5.0 release schedule</a> that build in extra time for betas. After pushing out Beta 3 Pendergast said he expects to release Beta 4 later this week. He also offered an explanation for why RC1 is scheduled for release on November 12, allowing for just one week of last-minute testing following RC.</p>\n<p>&#8220;The block editor has been available for over a year,&#8221; Pendergast said. &#8220;It’s already had a longer testing period, with 30 times the number of sites using it, than any previous WordPress release. The primary purpose of the beta and release candidate periods is to ensure that it’s been correctly merged into Core.&#8221;</p>\n<p>Initial feedback on the schedule changes indicate that some user would appreciate a longer RC period, since the code being tested has changed so often. </p>\n<p>&#8220;The API freeze just happened in version 4.2, so saying the editor has been available for over a year in anywhere near its current state doesn’t make sense for a 7-day RC period on such a major change,&#8221; WordPress trainer and developer Brian Hogg <a href=\"https://make.wordpress.org/core/2018/10/31/wordpress-5-0-schedule-updates/#comment-34292\" rel=\"noopener noreferrer\" target=\"_blank\">said</a>.</p>\n<p>&#8220;As an example, just in the last version or two the hover-over menu to remove a block has been taken out and tucked away at the top menu (which was available as shown in <a href=\"https://youtu.be/yjqW_IS6Q7w?t=80\" rel=\"noopener noreferrer\" target=\"_blank\">https://youtu.be/yjqW_IS6Q7w?t=80</a>), with little time for anyone to provide usability feedback on changes like this.&#8221;</p>\n<p>Those who are creating training materials and videos have been waiting for a bit of a reprieve in Gutenberg development to make sure their materials are accurate and ready for 5.0.</p>\n<p>&#8220;Knowing it’s an RC means we can assume a level of &#8216;this is how it will be&#8217; that just isn’t necessarily with pre-RC versions,&#8221; Modern Tribe developer George Gecewicz <a href=\"https://make.wordpress.org/core/2018/10/31/wordpress-5-0-schedule-updates/#comment-34278\" rel=\"noopener noreferrer\" target=\"_blank\">commented</a> on the post. &#8220;That relative certainty is useful for testing aggressively, finalizing design/UI stuff, and revealing post-merge bugs.&#8221;</p>\n<p>Gutenberg 4.1 was supposed to be the &#8220;<a href=\"https://github.com/WordPress/gutenberg/milestone/66\" rel=\"noopener noreferrer\" target=\"_blank\">UI freeze</a>&#8221; milestone, but that hasn&#8217;t happened yet with several changes introduced in 4.2. </p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">The \"freeze\" in \"UI freeze\" doesn\'t mean you can thaw it and change it willy nilly. Some of us rely on such landmarks to do our work.</p>\n<p>&mdash; Morten Rand-Hendriksen (@mor10) <a href=\"https://twitter.com/mor10/status/1059269623944642560?ref_src=twsrc%5Etfw\">November 5, 2018</a></p></blockquote>\n<p></p>\n<p>There should be short window of time before 5.0 is released where training materials can be finalized. However, the Gutenberg team plans to continue on from there with its same pace of development.</p>\n<p>&#8220;Over the past six months, there has been a release every two weeks,&#8221; Pendergast said. &#8220;We’ll plan to continue that over the first few WordPress 5.0.x releases, to ensure that bug fixes are available as quickly as possible. How soon should we expect WordPress 5.0.1? Approximately two weeks after WordPress 5.0, unless we see bug reports that indicate a need for a faster release.&#8221;</p>\n<p>WordPress 5.0 is on schedule for its original release date, but there is still a possibility for the the release to be delayed. Matt Mullenweg, <a href=\"https://wptavern.com/wordpress-accessibility-team-delivers-sobering-assessment-of-gutenberg-we-have-to-draw-a-line#comment-266997\" rel=\"noopener noreferrer\" target=\"_blank\">commenting</a> on responses to the accessibility team&#8217;s assessment of Gutenberg, said that delaying the release has &#8220;definitely been considered&#8221; and that it may still happen. His response also indicates that WordPress users can expect the pace of core development to continue along the path Gutenberg has carved. </p>\n<p>&#8220;Despite some differences that still need be resolved, there’s general consensus that the long-term way to create the best WP experience for all types of users is not something you can tack on with 5-6 weeks at the end, but will be the result of continuing the continuous iteration we’ve had with the 42 public releases of Gutenberg so far,&#8221; Mullenweg said. &#8220;It means we can get improvements into the hands of users within weeks following a release, not months (or years) as was the old model with WordPress.&#8221;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 05 Nov 2018 18:39: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:30:\"Dev Blog: WordPress 5.0 Beta 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:34:\"https://wordpress.org/news/?p=6236\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2018/11/wordpress-5-0-beta-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:3164:\"<p>WordPress 5.0 Beta 3 is now available!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.</p>\n\n\n\n<p>There are two ways to test the WordPress 5.0 Beta: try the&nbsp;<a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;plugin (you’ll want “bleeding edge nightlies”), or you can&nbsp;<a href=\"https://wordpress.org/wordpress-5.0-beta3.zip\">download the beta here</a>&nbsp;(zip).</p>\n\n\n\n<p>WordPress 5.0 is slated for release on&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">November 19</a>, and we need your help to get there. Here are some of the big issues that we&#8217;ve fixed since Beta 2:</p>\n\n\n\n<h2>Block Editor</h2>\n\n\n\n<p>The block editor has been updated to include all of the features and bug fixes from the upcoming <a href=\"https://make.wordpress.org/core/2018/10/31/whats-new-in-gutenberg-31st-october-2/\">Gutenberg 4.2 release</a>. Additionally, there are some newer bug fixes and features, such as:</p>\n\n\n\n<ul><li>Adding support for the &#8220;Custom Fields&#8221; meta box.</li><li>Improving the reliability of REST API requests.</li><li>A myriad of minor tweaks and improvements.</li></ul>\n\n\n\n<h2>Twenty Nineteen</h2>\n\n\n\n<p>Twenty Nineteen has been updated from its <a href=\"https://github.com/WordPress/twentynineteen\">GitHub repository</a>, this version is full of new goodies to check out:</p>\n\n\n\n<ul><li>Adds support for Selective Refresh Widgets in the Customiser.</li><li>Adds support for Responsive Embeds.</li><li>Tweaks to improve readability and functionality on mobile devices.</li><li>Fixes nested blocks appearing wider than they should be.</li><li>Fixes some errors in older PHP versions, and in IE11.</li></ul>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English? <a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a> </p>\n\n\n\n<p>If you&#8217;re able to contribute with coding or testing changes, we have <a href=\"https://make.wordpress.org/core/2018/11/02/upcoming-5-0-bug-scrubs/\">a multitude of bug scrubs</a> scheduled this week, we&#8217;d love to have as many people as we can ensuring all bugs reported get the attention they deserve.</p>\n\n\n\n<p><strong><em>If you think you’ve found a bug</em></strong><em>, you can post to the&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>Alpha/Beta area</em></a><em>&nbsp;in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>file one on WordPress Trac</em></a><em>, where you can also find&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>a list of known bugs</em></a><em>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>WordPress Five Point Oh<br />is just two short weeks away.<br />Thank you for helping!</em> <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f496.png\" alt=\"💖\" class=\"wp-smiley\" /><em><br /></em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 05 Nov 2018 00:20: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:15:\"Gary Pendergast\";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:80:\"WPTavern: GitHub Rolls Out More Small Improvements as Part of Project Paper Cuts\";s:7:\"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=85245\";s:7:\"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/github-rolls-out-more-small-improvements-as-part-of-project-paper-cuts\";s: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:4625:\"<p>In August, GitHub <a href=\"https://blog.github.com/2018-08-28-announcing-paper-cuts/\" rel=\"noopener noreferrer\" target=\"_blank\">announced</a> Project Paper Cuts, an effort aimed at bringing small improvements to the developer and project maintainer experiences. These are fixes for issues that don&#8217;t generally fall within larger initiatives. Some of the first improvements that have already been implemented include the following:</p>\n<ul>\n<li>Unselect markers when copying and pasting the contents of a diff</li>\n<li>Edit a repository’s README from the repository root</li>\n<li>Access your repositories straight from the profile dropdown</li>\n<li>Highlight permalinked comments</li>\n<li>Remove files from a pull request with a button</li>\n<li>Branch names in merge notification emails</li>\n<li>Create new pull requests from your repository’s Pull Requests Page</li>\n<li>Add a teammate from the team discussions page</li>\n<li>Collapse all diffs in a pull request at once</li>\n<li>Copy the URL of a comment</li>\n</ul>\n<p>One of the latest improvements allows repository admins to transfer an issue that has been misfiled to another repository where it belongs. At the moment it only works within the same GitHub organization account. Initial <a href=\"https://twitter.com/asmeurer/status/1057741387108560897\" rel=\"noopener noreferrer\" target=\"_blank\">feedback</a> from users indicates many would appreciate this feature require push permissions, instead of admin permissions, as there are likely more users who can help in the bug tracker with moving issues, setting labels, and closing bugs.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Issue filed in the wrong repo? </p>\n<p>We know your pain! And now we\'ve got a fix. </p>\n<p>Repo admins can transfer issues to wherever they belong. <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f3d8.png\" alt=\"🏘\" class=\"wp-smiley\" /> <a href=\"https://t.co/rPwNng7ZOl\">pic.twitter.com/rPwNng7ZOl</a></p>\n<p>&mdash; GitHub (@github) <a href=\"https://twitter.com/github/status/1057678791764467712?ref_src=twsrc%5Etfw\">October 31, 2018</a></p></blockquote>\n<p></p>\n<p>The &#8220;<a href=\"https://blog.github.com/2018-11-01-suggested-changes-update/\" rel=\"noopener noreferrer\" target=\"_blank\">suggested changes</a>&#8221; feature GitHub introduced in beta two weeks ago seems to have been adopted fairly quickly by users. Suggested Changes lets users suggest a change to code in a pull request. These changes can be accepted by the author or assignees with one click and then committed.</p>\n<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/11/suggested-changes.png?ssl=1\"><img /></a></p>\n<p>GitHub reports more than 10 percent of all reviewers suggested at least one change. They have received 100,000 suggestions and estimate that 4% of all review commits created have included a suggestion. Based on feedback so far, GitHub put the following improvements on the roadmap for the Suggested Changes feature: </p>\n<ul>\n<li>The ability to suggest changes to multiple lines at once</li>\n<li>The ability to accept multiple changes in a single commit</li>\n</ul>\n<p>Project Paper Cuts is borrowing heavily from <a href=\"https://github.com/sindresorhus/refined-github/\" rel=\"noopener noreferrer\" target=\"_blank\">Refined GitHub</a>, a browser extension that simplifies the GitHub interface and adds useful features. </p>\n<p>&#8220;Full-time open source developer <a href=\"https://github.com/sindresorhus/\" rel=\"noopener noreferrer\" target=\"_blank\">Sindre Sorhus</a> has built a great browser extension that builds on and improves the GitHub experience, along with a fantastic community that has come together to discuss workflows and build their favorite features,&#8221; GitHub product manager Luke Hefson said. &#8220;Project Paper Cuts has taken inspiration from a lot of Refined GitHub’s additions, and we’re building some of the most-loved features right into GitHub itself.&#8221;</p>\n<p>GitHub is aiming to be more open and transparent with user feedback after the <a href=\"https://wptavern.com/open-source-project-maintainers-confront-github-with-open-letter-on-issue-management\" rel=\"noopener noreferrer\" target=\"_blank\">2016 fiasco with disgruntled open source project maintainers</a>. These fixes for small annoyances add up in the grand scheme of things to improve project workflow for millions of developers and project maintainers. The improvements are shipping out regularly and are all outlined in <a href=\"https://blog.github.com/changelog/\" rel=\"noopener noreferrer\" target=\"_blank\">GitHub&#8217;s public 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, 02 Nov 2018 18:58:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:92:\"WPTavern: WPWeekly Episode 336 – Interview With Andrew Roberts, CEO and Co-founder of Tiny\";s:7:\"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=85267&preview=true&preview_id=85267\";s:7:\"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-336-interview-with-andrew-roberts-ceo-and-co-founder-of-tiny\";s: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:2772:\"<p>In this episode, <a href=\"http://jjj.me\">John James Jacoby</a> and I are joined by <a href=\"https://twitter.com/andrew_roberts?lang=en\">Andrew Roberts</a>, CEO and Co-founder of <a href=\"https://www.tiny.cloud/\">Tiny</a>. Tiny is the company behind the popular open source library <a href=\"https://www.tiny.cloud/features/\">TinyMCE</a>. Roberts shares his entrepreneurial journey, what the company plans on doing with its recent <a href=\"https://wptavern.com/tiny-raises-4m-in-series-a-funding-publishes-gutenberg-faq\">round of funding</a>, and the relationship between TinyMCE and Gutenberg.</p>\n<p>Here is an excerpt from the show on what Roberts thinks about Gutenberg.</p>\n<blockquote><p>I think that ultimately Gutenberg will be more innovative than just incrementally changing from the old editor experience toward block-based editing.</p>\n<p>I think you know Matt&#8217;s probably had a tough year with some of the criticisms around Gutenberg but I admire his courage and leadership because if he hadn&#8217;t put his brand equity on the line, if he hadn&#8217;t invested his goodwill in doing this, this would never be launching in a month from now.</p>\n<p>There may be a painful year or two but in the grand scheme of things this will turn out for the better. It&#8217;s taken a lot of courage and bravery for him to do that. He&#8217;s taken a lot of shots in the back, but you know that&#8217;s why he gets paid the big bucks as they say.</p></blockquote>\n<h2>Stories Discussed:</h2>\n<p><a href=\"https://jjj.blog/2018/10/wordpress-5-0-beta-1/\">WordPress 5.0 Beta 1</a><br />\n<a href=\"https://wptavern.com/wordpress-accessibility-team-delivers-sobering-assessment-of-gutenberg-we-have-to-draw-a-line\">WordPress Accessibility Team Delivers Sobering Assessment of Gutenberg: “We have to draw a line.”</a><br />\n<a href=\"https://wptavern.com/woocommerce-3-5-introduces-rest-api-v3-improves-transactional-emails\">WooCommerce 3.5 Introduces REST API v3, Improves Transactional Emails</a><br />\n<a href=\"https://wptavern.com/wp-engine-acquires-array-themes\">WP Engine Acquires Array Themes</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, November 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 #336:</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:\"Fri, 02 Nov 2018 13:25: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: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:63:\"WPTavern: How to Add an Image to A Paragraph Block in 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=85201\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/how-to-add-an-image-to-a-paragraph-block-in-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:2393:\"<p>WordPress 5.0 is on the horizon and with it comes a number of opportunities to explain how to get things done in the new editor. <br /></p>\n\n\n\n<h2>Testing Scenario<br /></h2>\n\n\n\n<p>A user has written three paragraphs and decides to add an image to the second paragraph. This user wants the image to be aligned to the right. </p>\n\n\n\n<h2>Accomplishing the Task in the Classic Editor</h2>\n\n\n\n<p>The classic editor is essentially one big block. Adding media to a paragraph is as quick as placing the mouse cursor at the beginning of a paragraph, clicking the add new media button, selecting or uploading an image, and choosing its alignment. </p>\n\n\n\n<h2 id=\"mce_6\">Accomplishing the Task in Gutenberg</h2>\n\n\n\n<p>In Gutenberg, each paragraph is a block and each block has its own toolbar. This is important because after writing three paragraphs, you can&#8217;t click on an add media button. Instead, you need to create an image block. </p>\n\n\n\n<p>Once you&#8217;ve selected an image, you need to move the image block above the paragraph block where you want to insert it. At first, you might try to drag and drop the image into the paragraph but that doesn&#8217;t work. You need to use the up and down arrows or drag the block into position. </p>\n\n\n\n<p>Once the image block is in the correct location, click the align right icon. The image will be inserted into the right side of the paragraph block. </p>\n\n\n\n<img />A Right Aligned Image Inside of A Paragraph Block\n\n\n\n<p>If you want to move the image to a different paragraph block, you&#8217;ll need to click the Align center button which turns the image back into its own block and repeat the process described above. </p>\n\n\n\n<h2>Adding Images to Paragraphs in the Classic Editor Is Easier<br /></h2>\n\n\n\n<p>The task I described above is one I think millions of users will have trouble completing when WordPress 5.0 is released. In the Classic editor, the writing flow doesn&#8217;t feel disjointed when you want to add images or embed content into posts. </p>\n\n\n\n<p>In Gutenberg, everything is a block which in many cases, causes the flow to be disrupted as you need to figure out what block you need, how to manipulate it, where to move it, find where the options are, etc. </p>\n\n\n\n<p>The process of adding images to paragraphs will likely improve after WordPress 5.0 is released but until then, the Classic editor wins this use case. </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 Nov 2018 11:35: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: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:79:\"WPTavern: Google’s reCAPTCHA v3 Promises a “Frictionless User Experience”\";s:7:\"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=85145\";s:7:\"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/googles-recaptcha-v3-promises-a-frictionless-user-experience\";s: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:3218:\"<p>Google <a href=\"https://webmasters.googleblog.com/2018/10/introducing-recaptcha-v3-new-way-to.html\" rel=\"noopener noreferrer\" target=\"_blank\">introduced reCAPTCHA v3</a> this week, which promises a new &#8220;frictionless user experience.&#8221; Earlier versions of the API stopped bots but also drew the ire of internet users across the globe. Users were regularly inconvenienced with distorted text challenges, street sign puzzles, click requirements, and other actions to prove their humanity. </p>\n<p>v3 offers a marked improvement by detecting bots in the background and returning a score that tells the admin if the interaction is suspicious. It scores traffic with its <a href=\"https://patents.google.com/patent/US20110054961A1/en\">Adaptive Risk Analysis Engine</a> instead of forcing human users to perform interactive challenges. The score can be used three different ways:</p>\n<ul>\n<li>Set a threshold that determines when a user is let through or when further verification needs to be done, i.e. two-factor authentication or phone verification.</li>\n<li>Combine the score with your own signals that reCAPTCHA can’t access, such as user profiles or transaction histories.</li>\n<li>Use the reCAPTCHA score as one of the signals to train your machine learning model to fight abuse.</li>\n</ul>\n<p>v3 give site owners more options to customize the thresholds and actions for different types of traffic. The video below explains how it works and the <a href=\"https://developers.google.com/recaptcha/docs/v3\" rel=\"noopener noreferrer\" target=\"_blank\">developer docs</a> have more information on frontend integration and score interpretation.</p>\n<p></p>\n<p>Site owners can view their traffic in the <a href=\"https://www.google.com/recaptcha/admin\" rel=\"noopener noreferrer\" target=\"_blank\">reCAPTCHA admin console</a>. It also displays a list of all of your sites and what version of the API they are using.</p>\n<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/10/Screen-Shot-2018-11-01-at-5.08.11-PM.png?ssl=1\"><img /></a></p>\n<p>The admin console also has a form for registering new sites:</p>\n<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/10/Screen-Shot-2018-11-01-at-5.09.18-PM.png?ssl=1\"><img /></a></p>\n<p>The WordPress Plugin Directory has <a href=\"https://wordpress.org/plugins/search/reCAPTCHA/\" rel=\"noopener noreferrer\" target=\"_blank\">dozens of standalone plugins and contact forms</a> that make use of reCAPTCHA in some way. Sites that are already set up to use v2 or the Invisible CAPTCHA, will not automatically update to use v3. There&#8217;s a different signup and implementation process that the site owner has to perform before having it integrated on the site.</p>\n<p>WordPress plugin developers who offer reCAPTCHA will have to decide if they want to update existing plugins to use v3 or package a v3 offering in a new plugin. The reCAPTCHA v1 API was shut down earlier this year in March. Google&#8217;s <a href=\"https://github.com/google/recaptcha/\" rel=\"noopener noreferrer\" target=\"_blank\">reCAPTCHA PHP client library on GitHub</a> is still actively encouraging use of both v2 and v3. A date has not been announced for v2 to be deprecated. </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 Nov 2018 00:09:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:37:\"Dev Blog: Quarterly Updates | Q3 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=6206\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://wordpress.org/news/2018/11/quarterly-updates-q3-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:14624:\"<p><em>To keep everyone aware of big projects and efforts across WordPress contributor teams, I&#8217;ve reached out to each team&#8217;s <a href=\"https://make.wordpress.org/updates/team-reps/\">listed representatives</a>. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I&#8217;ve included a link to each team&#8217;s site in the headings.</em></p>\n\n\n<h2><a href=\"https://make.wordpress.org/accessibility/\">Accessibility</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/joedolson/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>joedolson</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>audrasjb</a>, <a href=\"https://profiles.wordpress.org/arush/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>arush</a></li>\n<li><strong>Priority</strong>: Work on authoring a manual for assistive technology users on Gutenberg, led by Claire Brotherton (<a href=\"https://profiles.wordpress.org/abrightclearweb/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>abrightclearweb</a>). Continue to work on improving the overall user experience in Gutenberg. Update and organize the WP A11y handbook.</li>\n<li><strong>Struggle</strong>: Lack of developers and accessibility experts to help test and code the milestone issues. Still over 100 outstanding issues, and developing the Gutenberg AT manual helps expose additional issues. The announcement of an accessibility focus on 4.9.9 derailed our planning for Gutenberg in September with minimal productivity, as that goal was quickly withdrawn from the schedule.</li>\n<li><strong>Big Win</strong>: Getting focus constraint implemented in popovers and similar components in Gutenberg.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/cli/\">CLI</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: @danielbachhuber, <a href=\"https://profiles.wordpress.org/schlessera/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>schlessera</a></li>\n<li><strong>Priority</strong>: Current priority is v2.1.0 of WP-CLI, to polish the major refactoring v2.0.0 introduced. You can <a href=\"https://make.wordpress.org/cli/good-first-issues/\">join in or follow progress</a> on their site.</li>\n<li><strong>Struggle</strong>: Getting enough contributors to make peer-review possible/manageable.</li>\n<li><strong>Big Win</strong>: The major refactoring of v2 was mostly without any negative impacts on existing installs. It provided substantial improvements to maintainability including: faster and more reliable testing, more straight-forward changes to individual packages, and simpler contributor on-boarding.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/community/\">Community</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/francina/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>francina</a>, <a href=\"https://profiles.wordpress.org/hlashbrooke/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>hlashbrooke</a></li>\n<li><strong>Priority</strong>: Supporting contributors of all levels via: monthly <a href=\"https://make.wordpress.org/community/2018/10/08/announcement-monthly-chat-for-wordcamp-organisers/\">WordCamp Organizers chat</a>, better onboarding with a translated <a href=\"https://make.wordpress.org/community/2017/08/11/global-community-team-welcome-pack/\">welcome pack</a>, and Contribution Drive documentation.</li>\n<li><strong>Struggle</strong>: Fewer contributors than usual.</li>\n<li><strong>Big Win</strong>: <a href=\"https://make.wordpress.org/community/2018/09/21/meetup-application-vetting-sprint-26-27-september/\">Meetup Vetting Sprint</a>! </li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/core/\">Core</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/jeffpaul/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>jeffpaul</a></li>\n<li><strong>Priority</strong>: Continued preparation for the 5.0 release cycle and Gutenberg.</li>\n<li><strong>Struggle</strong>: Identifying tasks for first time contributors, as well as for new-to-JS contributors.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/design/\">Design</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/melchoyce/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>melchoyce</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>karmatosed</a>, <a href=\"https://profiles.wordpress.org/boemedia/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>boemedia</a>, <a href=\"https://profiles.wordpress.org/joshuawold/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>joshuawold</a>, <a href=\"https://profiles.wordpress.org/mizejewski/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>mizejewski</a></li>\n<li><strong>Priority</strong>: Preparing for WordPress 5.0 and continuing to work on better onboarding practices.</li>\n<li><strong>Struggle</strong>: Identifying tasks for contributor days, especially for small- to medium-sized tasks that can be fit into a single day.</li>\n<li><strong>Big Win</strong>: Regular contributions are starting to build up.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/docs/\">Documentation</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/kenshino/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>kenshino</a></li>\n<li><strong>Priority</strong>: Getting HelpHub out before WordPress 5.0&#8217;s launch to make sure Gutenberg User Docs have a permanent position to reside</li>\n<li><strong>Struggle</strong>: Getting the documentation from HelpHub into WordPress.org/support is more manual than initially anticipated.</li>\n<li><strong>Big Win</strong>: Had a good discussion with the Gutenberg team about their docs and how WordPress.org expects documentation to be distributed (via DevHub, Make and HelpHub). Getting past the code blocks to release HelpHub (soon)</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/hosting/\">Hosting</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/mikeschroder/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>mikeschroder</a>, <a href=\"https://profiles.wordpress.org/jadonn/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>jadonn</a></li>\n<li><strong>Priority</strong>: Helping Gutenberg land well at hosts for users in 5.0.</li>\n<li><strong>Struggle</strong>: Short time frame with few resources to accomplish priority items.</li>\n<li><strong>Big Win</strong>: Preparing Try Gutenberg support guide for hosts during the rollout and good reception from users following it.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/marketing/\">Marketing</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/bridgetwillard/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>bridgetwillard</a></li>\n<li><strong>Priority</strong>: Continuing to write and publish case studies from the community.</li>\n<li><strong>Big Win</strong>: Onboarding guide is going well and is currently being <a href=\"https://translate.wordpress.org/projects/meta/get-involved\">translated</a>.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/meta/\">Meta</a> (WordPress.org Site)</h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/tellyworth/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>tellyworth</a>, <a href=\"https://profiles.wordpress.org/coffee2code/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>coffee2code</a></li>\n<li><strong>Priority</strong>: Support for other teams in the lead up to, and the follow-up of, the release of WP 5.0. ETA is the WP 5.0 release date (Nov 19) and thereafter, unless it gets bumped to next quarter.</li>\n<li><strong>Struggle</strong>: Maintaining momentum on tickets (still).</li>\n<li><strong>Big Win</strong>: Launch of front-end demo of Gutenberg on https://wordpress.org/gutenberg/</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/mobile/\">Mobile</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/elibud/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>elibud</a></li>\n<li><strong>Priority</strong>: Have an alpha version of Gutenberg in the WordPress apps, ETA end of year 2018.</li>\n<li><strong>Struggle</strong>: Unfamiliar tech stack and the goal of reusing as much of Gutenberg-web&#8217;s code as possible.</li>\n<li><strong>Big Win</strong>: Running mobile tests on web&#8217;s PRs.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/plugins/\">Plugins</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/ipstenu/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>ipstenu</a></li>\n<li><strong>Priority</strong>: Cleaning up &#8216;inactive&#8217; users, which was supposed to be complete but some work preparing for 5.0 was necessary.</li>\n<li><strong>Struggles</strong>: Devnotes are lacking for the upcoming release which slows progress.</li>\n<li><strong>Big Win</strong>: No backlog even though a lot were out!</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/polyglots/\">Polyglots</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/petya/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>petya</a>, <a href=\"https://profiles.wordpress.org/ocean90/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>ocean90</a>, <a href=\"https://profiles.wordpress.org/nao/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>nao</a>, <a href=\"https://profiles.wordpress.org/chantalc/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chantalc</a>, <a href=\"https://profiles.wordpress.org/deconf/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>deconf</a>, <a href=\"https://profiles.wordpress.org/casiepa/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>casiepa</a></li>\n<li><strong>Priority</strong>: Help re-activating inactive locale teams.</li>\n<li><strong>Struggle</strong>: Many GTEs are having a hard time keeping up with incoming translation <a href=\"https://make.wordpress.org/polyglots/?resolved=unresolved&tags=editor-requests\">validation and PTE requests</a>.</li>\n<li><strong>Big Win</strong>: Made some progress in locale research and reassigning new GTEs.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/support/\">Support</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/clorith/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>clorith</a></li>\n<li><strong>Priority:</strong> Preparing for the upcoming 5.0 release</li>\n<li><strong>Struggle</strong>: Finding a good balance between how much we want to help people and how much we are able to help people. Also, contributor recruitment (always a crowd favorite!)</li>\n<li><strong>Big Win</strong>: How well the team, on a global level, has managed to maintain a good flow of user engagement through support.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/themes/\">Theme Review</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/acosmin/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>acosmin</a>, <a href=\"https://profiles.wordpress.org/rabmalin/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>rabmalin</a>, <a href=\"https://profiles.wordpress.org/thinkupthemes/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>thinkupthemes</a>, <a href=\"https://profiles.wordpress.org/williampatton/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>williampatton</a></li>\n<li><strong>Priority</strong>: Implementing the Theme Sniffer plugin on WordPress.org which is one step forward towards automation. ETA early 2019</li>\n<li><strong>Struggle</strong>: Not having so many contributors/reviewers.</li>\n<li><strong>Big Win</strong>: Implementing <a href=\"https://make.wordpress.org/themes/2018/10/25/new-requirements/\">multiple requirements</a> into our review flow, like screenshots and readme.txt requirements.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<p><!-- /wp:list --><!-- wp:heading --></p>\n<h2><a href=\"https://make.wordpress.org/training/\">Training</a></h2>\n<p><!-- /wp:heading --><!-- wp:list --></p>\n<ul>\n<li><strong>Contacted</strong>: <a href=\"https://profiles.wordpress.org/bethsoderberg/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>bethsoderberg</a>, <a href=\"https://profiles.wordpress.org/juliek/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>juliek</a></li>\n<li><strong>Priority:</strong> Getting the learn.wordpress.org site designed, developed, and being able to publish lesson plans to it.</li>\n<li><strong>Struggle:</strong> Getting contributors onboard and continually contributing. Part of that is related to the learn.wordpress.org site. People like to see their contributions.</li>\n<li><strong>Big Win</strong>: We have our new workflow and tools in place. We are also streamlining that process to help things go from idea to publication more quickly.</li>\n</ul>\n<p><!-- /wp:list --><!-- wp:paragraph --></p>\n<p><em>Interested in updates from the last quarter? You can find those here: <a href=\"https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/\">https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/</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 Nov 2018 16:46: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:46:\"Dev Blog: The Month in WordPress: October 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=6230\";s:7:\"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/11/the-month-in-wordpress-october-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:8136:\"<p>Teams across the WordPress project are working hard to make sure everything is ready for the upcoming release of WordPress 5.0. Find out what’s going on and how you can get involved.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>The Plan for WordPress 5.0</h2>\n\n\n\n<p>Early this month, <a href=\"https://make.wordpress.org/core/2018/10/03/proposed-wordpress-5-0-scope-and-schedule/\">the planned release schedule was announced</a> for WordPress 5.0, which was <a href=\"https://make.wordpress.org/core/2018/10/31/wordpress-5-0-schedule-updates/\">updated</a> a few weeks later. WordPress 5.0 is a highly anticipated release, as it’s the official &nbsp;launch of Gutenberg &#8212; the new block editor for WordPress Core. For more detail, check out this <a href=\"https://make.wordpress.org/core/2018/10/12/granular-timeline/\">&nbsp;granular timeline</a>.<br /></p>\n\n\n\n<p>Along with the planned release schedule, <a href=\"https://profiles.wordpress.org/matt/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>matt</a>, who is heading up this release, <a href=\"https://make.wordpress.org/core/2018/10/03/a-plan-for-5-0/\">announced leads for critical focuses on the project</a>, including <a href=\"https://profiles.wordpress.org/matveb/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>matveb</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>karmatosed</a>, <a href=\"https://profiles.wordpress.org/laurelfulford/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>laurelfulford</a>, <a href=\"https://profiles.wordpress.org/allancole/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>allancole</a>, <a href=\"https://profiles.wordpress.org/lonelyvegan/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>lonelyvegan</a>, <a href=\"https://profiles.wordpress.org/omarreiss/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>omarreiss</a>, <a href=\"https://profiles.wordpress.org/antpb/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>antpb</a>, <a href=\"https://profiles.wordpress.org/pento/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>pento</a>, <a href=\"https://profiles.wordpress.org/chanthaboune/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chanthaboune</a>, <a href=\"https://profiles.wordpress.org/danielbachhuber/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>danielbachhuber</a>, and <a href=\"https://profiles.wordpress.org/mcsf/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>mcsf</a>.<br /></p>\n\n\n\n<p><a href=\"https://wordpress.org/news/2018/10/wordpress-5-0-beta-2/\">WordPress 5.0 is currently in its second beta phase</a> and will soon move to the release candidate status. Help test this release right now by installing the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester plugin</a> on your site.<br /></p>\n\n\n\n<p>Want to get involved in building WordPress Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>. You can also help out by <a href=\"https://make.wordpress.org/test/\">testing</a> or <a href=\"https://make.wordpress.org/polyglots/2018/10/24/wordpress-5-0-gutenberg-and-twenty-nineteen/\">translating</a> the release into a local language.</p>\n\n\n\n<h2>New Editor for WordPress Core</h2>\n\n\n\n<p>Active development continues on <a href=\"https://wordpress.org/gutenberg\">Gutenberg</a>, the new editing experience for WordPress Core. <a href=\"https://make.wordpress.org/core/2018/10/31/whats-new-in-gutenberg-31st-october-2/\">The latest release</a> is feature complete, meaning that all further development on it will be to improve existing features and fix outstanding bugs.<br /></p>\n\n\n\n<p>Some have raised concerns about Gutenberg’s accessibility, prompting the development team <a href=\"https://make.wordpress.org/core/2018/10/18/regarding-accessibility-in-gutenberg/\">to detail some areas</a> in which the new editor is accessible. To help improve things further, the team has made <a href=\"https://make.wordpress.org/core/2018/10/19/call-for-testers-community-gutenberg-accessibility-tests/\">a public call for accessibility testers</a> to assist.<br /></p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/tag/gutenberg\">the Gutenberg tag</a> on the Core team blog and join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>. Read <a href=\"https://make.wordpress.org/test/2018/10/19/gutenberg-needs-testing-areas/\">this guide</a> to find areas where you can have the most impact.</p>\n\n\n\n<h2>Migrating HelpHub to WordPress.org</h2>\n\n\n\n<p>HelpHub is an ongoing project to move all of WordPress’ user documentation from the <a href=\"https://codex.wordpress.org/\">Codex</a> to the <a href=\"https://wordpress.org/support/\">WordPress Support portal</a>.<br /></p>\n\n\n\n<p>HelpHub has been developed on <a href=\"https://wp-helphub.com/\">a separate staging server</a> and it’s now time to migrate the new documentation to its home on WordPress.org. The plan is to have everything moved over &nbsp;before WordPress 5.0 is released, so that all the new documentation will be available on the new platform from the start.<br /></p>\n\n\n\n<p>The HelpHub team has published <a href=\"https://make.wordpress.org/docs/2018/11/01/call-for-volunteers-helphub-migration/\">a call for volunteers</a> to help with the migration. If you would like to get involved, join the #docs channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>, and contact <a href=\"https://profiles.wordpress.org/atachibana/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>atachibana</a> to get started.</p>\n\n\n\n<h2>A New Default Theme for WordPress</h2>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2018/10/16/introducing-twenty-nineteen/\">A brand new default theme &#8212; Twenty Nineteen &#8212; has been announced</a>&nbsp;with development being led by <a href=\"https://profiles.wordpress.org/allancole/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>allancole</a>. The theme is packaged with WordPress 5.0, so it will be following the same release schedule as Core.<br /></p>\n\n\n\n<p>The new theme is designed to integrate seamlessly with Gutenberg and showcase how you can build a theme alongside the new block editor and take advantage of the creative freedom that it offers.<br /></p>\n\n\n\n<p>Want to help build Twenty Nineteen? Join in on <a href=\"https://github.com/WordPress/twentynineteen\">the theme’s GitHub repo</a> and join the #core-themes channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.<br /></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li>The Support team are putting together more formal <a href=\"https://github.com/Clorith/wporg-support-guidelines\">Support Guidelines</a> for the WordPress Support Forums.</li><li>The group focused on privacy tools in Core <a href=\"https://make.wordpress.org/core/2018/10/11/whats-new-in-core-privacy/\">has released some details</a> on the work they have been doing recently, with a roadmap for their plans over the next few months.</li><li>The Core team <a href=\"https://make.wordpress.org/core/2018/10/15/wordpress-and-php-7-3/\">released an update</a> about how WordPress will be compatible with PHP 7.3.</li><li>The Theme Review Team have published <a href=\"https://make.wordpress.org/themes/2018/10/25/new-requirements/\">some new requirements</a> regarding child themes, readme files and trusted authors in the Theme Directory.</li><li>The WordCamp Europe team <a href=\"https://make.wordpress.org/community/2018/10/23/progressive-web-app-for-wordcamps/\">are working on a PWA service</a> for all WordCamp websites.</li></ul>\n\n\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em><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:\"Thu, 01 Nov 2018 08:40:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:61:\"WPTavern: Gutenberg Cloud Plugin for WordPress is Now in Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=85115\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wptavern.com/gutenberg-cloud-plugin-for-wordpress-is-now-in-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5938:\"<p><a href=\"https://www.frontkom.no/\" rel=\"noopener noreferrer\" target=\"_blank\">Frontkom</a>, the team behind the <a href=\"https://gutenbergcloud.org/\" rel=\"noopener noreferrer\" target=\"_blank\">Gutenberg Cloud</a> project, has published the beta version of its WordPress plugin to the official repository. <a href=\"https://wordpress.org/plugins/cloud-blocks/\" rel=\"noopener noreferrer\" target=\"_blank\">Cloud Blocks</a> serves as a connector, allowing WordPress users to browse and install open source blocks from Gutenberg Cloud. The blocks are hosted on NPM and their assets are served from CloudFlare using <a href=\"https://unpkg.com\" rel=\"noopener noreferrer\" target=\"_blank\">unpkg.com</a>.</p>\n<p><a href=\"https://i0.wp.com/wptavern.com/wp-content/uploads/2018/10/gutenberg-cloud-wp-plugin.gif?ssl=1\"><img /></a></p>\n<p>Gutenberg Cloud&#8217;s online library of blocks is CMS agnostic, offering blocks for both Drupal and WordPress sites, and more CMSs in the future. The service advertises three key benefits for developers who host blocks on Gutenberg Cloud:</p>\n<ul>\n<li>Wider adoption: Your blocks can be used outside of WP</li>\n<li>Discoverability: Your blocks will pop up in the Cloud Blocks UI</li>\n<li>Faster development: No plugin/SVN needed, just publish to NPM</li>\n</ul>\n<p>Frontkom is actively recruiting WordPress developers to add blocks to the cloud to test the process. Documentation for <a href=\"https://github.com/front/cloud-blocks/blob/master/docs/migrate-block.md\" rel=\"noopener noreferrer\" target=\"_blank\">migrating blocks from a plugin</a> is available on GitHub. Frontkom has also produced a new <a href=\"https://github.com/front/create-cloud-block\" rel=\"noopener noreferrer\" target=\"_blank\">boilerplate generator for building Gutenberg Cloud blocks</a>.</p>\n<p>Users should note that the team is still ironing out the experience for developers adding blocks to the cloud, so the plugin isn&#8217;t yet ready for general use. It&#8217;s currently under active development. </p>\n<h3>WordPress Developers Say Gutenberg Cloud May Not be the Best Way to Release Blocks but Platform has Potential</h3>\n<p>I contacted some WordPress developers who have tested sending their blocks to Gutenberg Cloud to get their initial reactions to the platform. </p>\n<p>&#8220;The idea that folks will be able to install blocks a la carte is interesting,&#8221; <a href=\"https://coblocks.com/\" rel=\"noopener noreferrer\" target=\"_blank\">CoBlocks</a> author and ThemeBeans founder Rich Tabor said. &#8220;It’s pretty much as easy as installing plugins.&#8221;</p>\n<p>Tabor experimented with migrating his Block Gallery blocks and said the process was not difficult but he foresees difficulties in maintaining blocks across parent plugins and Gutenberg Cloud.</p>\n<p>&#8220;As a developer, I’m still not entirely convinced Gutenberg Cloud is the best way to release blocks, aside from relatively simple blocks,&#8221; Tabor said. &#8220;I personally lean towards building suites of blocks that share a relative purpose, instead of one plugin (or one Cloud Block instance) per block. For one, it cuts down on maintenance quite a bit, as custom components can be shared between blocks. And there’s much better discoverability on getting relative blocks in the hands of users — if they’re grouped together.&#8221;</p>\n<p>Block collections have been criticized for making it difficult to search for and discover individual blocks, but Tabor makes some good arguments for improving block discoverability by grouping together features users often need. That is the whole point of successful plugins like Jetpack, but this type of packaging also lends itself to criticism about bloat.</p>\n<p>&#8220;It’s a similar conundrum when we look at grouped/not grouped shortcode plugins,&#8221; Tabor said. &#8220;I suppose the main difference is that the nature of blocks is much more complicated than that of shortcodes. History seems to repeat itself.&#8221;</p>\n<p>Tabor said he is considering distributing a few of his free blocks through Gutenberg Cloud but he hasn&#8217;t fully decided yet.</p>\n<p>WordPress core contributor, <a href=\"https://joshpress.net/\" rel=\"noopener noreferrer\" target=\"_blank\">Josh Pollock</a>, who has worked extensively with React and Gutenberg, also tested the Gutenberg Cloud platform. He said he thinks it has a lot of potential for developers who write blocks that are mainly JavaScript already.</p>\n<p>&#8220;I could see how an agency that builds WordPress sites could save a lot of time and hassle building out a block library,&#8221; Pollock said. &#8220;As a plugin developer with a lot of little ideas, the pain and time of setting up a block and block environment, which no one has gotten right yet, makes me very excited about this.&#8221;</p>\n<p>Pollock also reported a positive experience with the <a href=\"https://github.com/front/create-cloud-block\" rel=\"noopener noreferrer\" target=\"_blank\">create-cloud-block</a> generator.</p>\n<p>&#8220;The code that create-cloud-block generates is well-written, but not too opinionated,&#8221; Pollock said. &#8220;The developer experience is both really cool &#8212; you preview your block in a functional Gutenberg-powered editor with no WordPress site attached &#8212; and a little frustrating as there is no live reload yet. I know they are just getting started and the tool doesn&#8217;t lock you into any structure, which is great. I&#8217;ll be keeping my eye on this project.&#8221;</p>\n<p>Frontkom CTO Per André Rønsen said his team will continue testing the cloud internally until they get more developer feedback on the corresponding WordPress plugin. For Drupal users, Gutenberg Cloud will be shipped as a submodule of Gutenberg, which means all sites that install Gutenberg will also get the Cloud module. It can, however, be disabled. Rønsen said his team plans to showcase Gutenberg Cloud for D8 at DrupalCamp Oslo in November.</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 Oct 2018 23:12:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 30 Nov 2018 04:46:51 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Fri, 30 Nov 2018 04:30:28 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:\"20130911093210\";}','no'),(1120,'qode_sidebars','a:2:{i:0;s:19:\"Content Bottom Area\";i:1;s:12:\"News Sidebar\";}','yes');

--
