-- https://www.phpmyadmin.net/
--
-- Versão do servidor: 5.6.34-log
-- versão do PHP: 7.2.1

START TRANSACTION;



--
-- Database: `feninjer_teste`
--

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

--
-- Estrutura da tabela `wp_commentmeta`
--

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

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

--
-- Estrutura da tabela `wp_comments`
--

CREATE TABLE `wp_comments` (
  `comment_ID` bigint(20) UNSIGNED NOT NULL,
  `comment_post_ID` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `comment_author` tinytext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_520_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_520_ci NOT NULL,
  `comment_karma` int(11) NOT NULL DEFAULT '0',
  `comment_approved` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '1',
  `comment_agent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0',
  `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

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

--
-- Estrutura da tabela `wp_links`
--

CREATE TABLE `wp_links` (
  `link_id` bigint(20) UNSIGNED NOT NULL,
  `link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_visible` varchar(20) COLLATE utf8mb4_unicode_520_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_520_ci NOT NULL DEFAULT '',
  `link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

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

--
-- Estrutura da tabela `wp_options`
--

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


INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(131, '_transient_feed_b85365aa61afaf3d4189819a6f57c4c4', 'a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Blog | Brasil\";s:7:\"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:24:\"https://br.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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s: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:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Dec 2018 22:18: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:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"pt-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:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://wordpress.org/?v=5.0.1-alpha-43972\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:10:{i:0;a:6:{s:4:\"data\";s:36:\"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"WordPress 5.0 “Bebo”\";s:7:\"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://br.wordpress.org/2018/12/06/wordpress-5-0-bebo/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Dec 2018 22:12:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1386\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:340:\"Diga olá para o novo editor Fizemos algumas mudanças grandes no editor. Nosso novo editor baseado em blocos é o primeiro passo em direção a um novo futuro empolgante com uma experiência de edição simplificada em todo o seu site. Você terá mais flexibilidade na forma como o conteúdo é exibido, esteja você criando seu [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:50054:\"\n<h2 style=\"text-align:center\">Diga olá para o novo editor</h2>\n\n\n\n<p>Fizemos algumas mudanças grandes no editor. Nosso novo editor baseado em blocos é o primeiro passo em direção a um novo futuro empolgante com uma experiência de edição simplificada em todo o seu site. Você terá mais flexibilidade na forma como o conteúdo é exibido, esteja você criando seu primeiro site, reformulando seu blog ou escrevendo código para ganhar a vida.<br></p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Gutenberg.jpg?fit=2400%2C1200&amp;ssl=1\" alt=\"\" class=\"wp-image-6331\" /></figure>\n\n\n\n<h2 style=\"text-align:center\">Construindo com blocos</h2>\n\n\n\n<p>O novo editor baseado em blocos não mudará a forma como o conteúdo é exibido para seus visitantes. O que ele fará é inserir qualquer tipo de conteúdo multimídia num piscar de olhos e permitir que você organize o conteúdo como quiser. Cada parte do conteúdo estará em seu próprio bloco, isolado de forma que você possa colocá-lo onde quiser. Se você é do tipo que gosta de HTML e CSS, os blocos não vão atrapalhar. O WordPress está aqui para simplificar o processo, não o resultado.</p>\n\n\n\n<p>Temos vários blocos disponíveis por padrão, e mais são adicionados pela comunidade a cada dia. Aqui estão alguns blocos para te ajudar a iniciar:</p>\n\n\n\n<ul class=\"wp-block-gallery columns-4 is-cropped\"><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Paragraph.jpg\" alt=\"\" data-id=\"1387\" data-link=\"https://br.wordpress.org/?attachment_id=1387\" class=\"wp-image-1387\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Paragraph.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Paragraph-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Paragraph-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Parágrafo</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Heading.jpg\" alt=\"\" data-id=\"1388\" data-link=\"https://br.wordpress.org/?attachment_id=1388\" class=\"wp-image-1388\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Heading.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Heading-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Heading-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Título</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Preformatted.jpg\" alt=\"\" data-id=\"1389\" data-link=\"https://br.wordpress.org/?attachment_id=1389\" class=\"wp-image-1389\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Preformatted.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Preformatted-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Preformatted-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Pré-formatado</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Quote.jpg\" alt=\"\" data-id=\"1390\" data-link=\"https://br.wordpress.org/?attachment_id=1390\" class=\"wp-image-1390\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Quote.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Quote-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Quote-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Citação</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Image.jpg\" alt=\"\" data-id=\"1391\" data-link=\"https://br.wordpress.org/?attachment_id=1391\" class=\"wp-image-1391\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Image.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Image-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Image-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Imagem</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Gallery.jpg\" alt=\"\" data-id=\"1392\" data-link=\"https://br.wordpress.org/?attachment_id=1392\" class=\"wp-image-1392\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Gallery.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Gallery-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Gallery-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Galeria</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Cover-Image.jpg\" alt=\"\" data-id=\"1393\" data-link=\"https://br.wordpress.org/?attachment_id=1393\" class=\"wp-image-1393\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Cover-Image.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Cover-Image-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Cover-Image-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Capa</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Video.jpg\" alt=\"\" data-id=\"1394\" data-link=\"https://br.wordpress.org/?attachment_id=1394\" class=\"wp-image-1394\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Video.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Video-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Video-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Vídeo</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Audio.jpg\" alt=\"\" data-id=\"1395\" data-link=\"https://br.wordpress.org/?attachment_id=1395\" class=\"wp-image-1395\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Audio.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Audio-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Audio-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Áudio</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Column.jpg\" alt=\"\" data-id=\"1396\" data-link=\"https://br.wordpress.org/?attachment_id=1396\" class=\"wp-image-1396\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Column.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Column-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Column-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Colunas</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-File.jpg\" alt=\"\" data-id=\"1397\" data-link=\"https://br.wordpress.org/?attachment_id=1397\" class=\"wp-image-1397\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-File.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-File-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-File-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Arquivo</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Code.jpg\" alt=\"\" data-id=\"1398\" data-link=\"https://br.wordpress.org/?attachment_id=1398\" class=\"wp-image-1398\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Code.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Code-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Code-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Código</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-List.jpg\" alt=\"\" data-id=\"1402\" data-link=\"https://br.wordpress.org/?attachment_id=1402\" class=\"wp-image-1402\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-List.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-List-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-List-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Lista</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Button.jpg\" alt=\"\" data-id=\"1401\" data-link=\"https://br.wordpress.org/?attachment_id=1401\" class=\"wp-image-1401\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Button.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Button-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Button-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Botão</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-Embeds.jpg\" alt=\"\" data-id=\"1400\" data-link=\"https://br.wordpress.org/?attachment_id=1400\" class=\"wp-image-1400\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-Embeds.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-Embeds-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-Embeds-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Mídia incorporada</figcaption></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"https://br.wordpress.org/files/2018/12/Block-Icon-More.jpg\" alt=\"\" data-id=\"1399\" data-link=\"https://br.wordpress.org/?attachment_id=1399\" class=\"wp-image-1399\" srcset=\"https://br.wordpress.org/files/2018/12/Block-Icon-More.jpg 500w, https://br.wordpress.org/files/2018/12/Block-Icon-More-150x150.jpg 150w, https://br.wordpress.org/files/2018/12/Block-Icon-More-300x300.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /><figcaption>Mais</figcaption></figure></li></ul>\n\n\n\n<h2 style=\"text-align:center\">Liberdade para construir, liberdade para escrever</h2>\n\n\n\n<p>Essa nova experiência de edição fornece um tratamento mais consistente de design e conteúdo. Se você estiver criando sites de clientes, poderá criar blocos reutilizáveis. Isso permite que seus clientes adicionem novos conteúdos a qualquer momento, mantendo ao mesmo tempo uma aparência consistente.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2 style=\"text-align:center\">Um novo tema padrão deslumbrante</h2>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2018/12/twenty-nineteen.jpg?fit=2400%2C1600&amp;ssl=1\" alt=\"\" class=\"wp-image-6358\" /></figure>\n\n\n\n<p>Apresentando o Twenty Nineteen, o novo tema padrão que mostra todo o poder do novo editor.</p>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><figure class=\"wp-block-media-text__media\"><img src=\"https://br.wordpress.org/files/2018/12/block-editor-1024x683.jpg\" alt=\"\" class=\"wp-image-1403\" srcset=\"https://br.wordpress.org/files/2018/12/block-editor-1024x683.jpg 1024w, https://br.wordpress.org/files/2018/12/block-editor-300x200.jpg 300w, https://br.wordpress.org/files/2018/12/block-editor-768x512.jpg 768w, https://br.wordpress.org/files/2018/12/block-editor.jpg 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></figure><div class=\"wp-block-media-text__content\">\n<h3>Projetado para o editor de blocos</h3>\n\n\n\n<p>O Twenty Nineteen apresenta estilos personalizados para os blocos disponíveis por padrão na versão 5.0. Ele também usa estilos para o editor em todo o tema. Dessa forma, o que você cria no editor de conteúdo é o que você vê no seu site, fora do Painel.<br></p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><figure class=\"wp-block-media-text__media\"><img src=\"https://br.wordpress.org/files/2018/12/typography.jpg\" alt=\"\" class=\"wp-image-1404\" srcset=\"https://br.wordpress.org/files/2018/12/typography.jpg 900w, https://br.wordpress.org/files/2018/12/typography-1-300x200.jpg 300w, https://br.wordpress.org/files/2018/12/typography-1-768x512.jpg 768w\" sizes=\"(max-width: 900px) 100vw, 900px\" /></figure><div class=\"wp-block-media-text__content\">\n<h3>Simples, layout direcionado para a escrita</h3>\n\n\n\n<p>Com amplo espaço e modernos títulos sem serifa, combinados com o clássico corpo de texto com serifa, o Twenty Nineteen foi construído para ser bonito logo de cara. Ele usa fontes do sistema para aumentar a velocidade de carregamento. Chega de esperar tanto tempo em redes lentas!<br></p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><figure class=\"wp-block-media-text__media\"><img src=\"https://br.wordpress.org/files/2018/12/twenty-nineteen-versatile.gif\" alt=\"\" class=\"wp-image-1405\" /></figure><div class=\"wp-block-media-text__content\">\n<h3>Design versátil para todos os sites</h3>\n\n\n\n<p>O Twenty Nineteen é pensado de forma que você possa usá-lo em vários tipos de sites diferentes. Se você tem um blog de fotografia, um site para seu novo negócio ou caso esteja ajudando uma ONG, o Twenty Nineteen é flexível o suficiente para atender às suas necessidades.<br></p>\n</div></div>\n\n\n\n<div class=\"wp-block-button aligncenter is-style-squared\"><a class=\"wp-block-button__link\" href=\"https://wordpress.org/themes/twentynineteen/\">Experimente o Twenty Nineteen</a></div>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2 style=\"text-align:center\">Alegria para os desenvolvedores</h2>\n\n\n\n<div class=\"wp-block-media-text alignwide\"><figure class=\"wp-block-media-text__media\"><img src=\"https://br.wordpress.org/files/2018/12/Protect.jpg\" alt=\"\" class=\"wp-image-1406\" srcset=\"https://br.wordpress.org/files/2018/12/Protect.jpg 500w, https://br.wordpress.org/files/2018/12/Protect-300x210.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /></figure><div class=\"wp-block-media-text__content\">\n<h3>Proteção</h3>\n\n\n\n<p>Os blocos fornecem uma maneira confortável para os usuários alterarem o conteúdo diretamente, mas ao mesmo tempo garantem que a estrutura do conteúdo não seja facilmente afetada por edições acidentais de código. Isso permite que o desenvolvedor controle o código gerado, mantendo-o polido e semântico, preservado por meio de edições e que não é quebrado facilmente.<br></p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide\"><figure class=\"wp-block-media-text__media\"><img src=\"https://br.wordpress.org/files/2018/12/Compose.jpg\" alt=\"\" class=\"wp-image-1407\" srcset=\"https://br.wordpress.org/files/2018/12/Compose.jpg 500w, https://br.wordpress.org/files/2018/12/Compose-300x210.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /></figure><div class=\"wp-block-media-text__content\">\n<h3>Composição</h3>\n\n\n\n<p>Aproveite uma ampla coleção de APIs e componentes de interface para criar facilmente blocos com controles intuitivos para seus clientes. A utilização desses componentes não apenas acelera o trabalho de desenvolvimento, mas também fornece uma interface mais consistente, utilizável e acessível a todos os usuários.</p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide\"><figure class=\"wp-block-media-text__media\"><img src=\"https://br.wordpress.org/files/2018/12/Create.jpg\" alt=\"\" class=\"wp-image-1408\" srcset=\"https://br.wordpress.org/files/2018/12/Create.jpg 500w, https://br.wordpress.org/files/2018/12/Create-300x210.jpg 300w\" sizes=\"(max-width: 500px) 100vw, 500px\" /></figure><div class=\"wp-block-media-text__content\">\n<h3>Criação</h3>\n\n\n\n<p>O novo paradigma de bloco abre um caminho de exploração e imaginação quando se trata de resolver as necessidades do usuário. Com o fluxo de inserção de bloco unificado, é mais fácil para seus clientes e usuários encontrar e usar blocos para todos os tipos de conteúdo. Os desenvolvedores podem se concentrar em executar sua visão e fornecer experiências de edição ricas, em vez de se preocupar com APIs difíceis.<br></p>\n</div></div>\n\n\n\n<div class=\"wp-block-button aligncenter is-style-squared\"><a class=\"wp-block-button__link\" href=\"https://wordpress.org/gutenberg/handbook/\">Aprenda como começar a usar</a></div>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2 style=\"text-align:center\">Mantenha-se clássico</h2>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Classic.jpg?fit=2400%2C1130&amp;ssl=1\" alt=\"\" class=\"wp-image-6365\" /></figure>\n\n\n\n<p>Prefere continuar com o editor clássico? Sem problemas! O WordPress dará suporte para o plugin do Editor Clássico até 2021.</p>\n\n\n\n<p>O plugin Editor Clássico restaura o editor anterior do WordPress e a tela de edição de posts. Permite que você continue usando plugins que o estendem, que adicionam meta boxes do jeito antigo, ou que dependem do editor anterior de alguma forma. Para instalá-lo, visite sua página de plugins e clique no botão &#8220;Instalar agora&#8221; ao lado do &#8220;Editor Clássico&#8221;. Depois que a instalação do plugin terminar, clique em &#8220;Ativar&#8221; e pronto!</p>\n\n\n\n<p>Observação para usuários de tecnologia assistiva: se tiver problemas de usabilidade com o editor de blocos, recomendamos que continue usando o Editor Clássico.<br></p>\n\n\n\n<div class=\"wp-block-button aligncenter is-style-squared\"><a class=\"wp-block-button__link\" href=\"https://br.wordpress.org/plugins/classic-editor/\">Saber mais sobre o Editor Clássico</a></div>\n\n\n\n<p>O nome desta versão é uma&nbsp;homenagem para o pioneiro do jazz cubano&nbsp;<a href=\"https://en.wikipedia.org/wiki/Bebo_Vald%C3%A9s\">Bebo Valdés</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>O esquadrão</h2>\n\n\n\n<p>Esta versão foi liderada por&nbsp;<a href=\"http://ma.tt/\">Matt Mullenweg</a>, com a coliderança de&nbsp;<a href=\"https://www.allancole.com/\">Allan Cole</a>, <a href=\"http://antpb.com/\">Anthony Burchell</a>, <a href=\"https://pento.net/\">Gary Pendergast</a>, <a href=\"https://josepha.blog/\">Josepha Haden Chomphosy</a>, <a href=\"https://laurel.blog/\">Laurel Fulford</a>, <a href=\"https://yoast.com/about-us/team/omar-reiss/\">Omar Reiss</a>, <a href=\"https://danielbachhuber.com/\">Daniel Bachhuber</a>, <a href=\"https://matiasventura.com/\">Matías Ventura</a>, <a href=\"https://lamda.blog/\">Miguel Fonseca</a>, <a href=\"https://tam.blog/\">Tammie Lister</a>&nbsp;e&nbsp;<a href=\"https://tofumatt.com/\">Matthew Riley MacPherson</a>. Eles receberam a fabulosa ajuda dos colegas a seguir. Foram 423 colaboradores recebendo créditos nesta versão. Coloque um Bebo Valdés para tocar no seu serviço de música favorito e dê uma olhada em alguns de seus perfis:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/jorbin\">Aaron Jorbin</a>, <a href=\"https://profiles.wordpress.org/abdulwahab610\">Abdul Wahab</a>, <a href=\"https://profiles.wordpress.org/abdullahramzan\">Abdullah Ramzan</a>, <a href=\"https://profiles.wordpress.org/abhijitrakas\">abhijitrakas</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/afraithe\">afraithe</a>, <a href=\"https://profiles.wordpress.org/mrahmadawais\">Ahmad Awais</a>, <a href=\"https://profiles.wordpress.org/ahmadawais\">ahmadawais</a>, <a href=\"https://profiles.wordpress.org/airathalitov\">Airat Halitov</a>, <a href=\"https://profiles.wordpress.org/ajitbohra\">Ajit Bohra</a>, <a href=\"https://profiles.wordpress.org/schlessera\">Alain Schlesser</a>, <a href=\"https://profiles.wordpress.org/albertomedina\">albertomedina</a>, <a href=\"https://profiles.wordpress.org/aldavigdis\">aldavigdis</a>, <a href=\"https://profiles.wordpress.org/alexsanford1\">Alex Sanford</a>, <a href=\"https://profiles.wordpress.org/alexis\">alexis</a>, <a href=\"https://profiles.wordpress.org/alexislloyd\">Alexis Lloyd</a>, <a href=\"https://profiles.wordpress.org/arush\">Amanda Rush</a>, <a href=\"https://profiles.wordpress.org/amedina\">amedina</a>, <a href=\"https://profiles.wordpress.org/afercia\">Andrea Fercia</a>, <a href=\"https://profiles.wordpress.org/andreamiddleton\">Andrea Middleton</a>, <a href=\"https://profiles.wordpress.org/euthelup\">Andrei Lupu</a>, <a href=\"https://profiles.wordpress.org/andreiglingeanu\">andreiglingeanu</a>, <a href=\"https://profiles.wordpress.org/aduth\">Andrew Duthie</a>, <a href=\"https://profiles.wordpress.org/sumobi\">Andrew Munro</a>, <a href=\"https://profiles.wordpress.org/anevins\">Andrew Nevins</a>, <a href=\"https://profiles.wordpress.org/azaozz\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/androb\">Andrew Roberts</a>, <a href=\"https://profiles.wordpress.org/andrewtaylor-1\">Andrew Taylor</a>, <a href=\"https://profiles.wordpress.org/andrewserong\">andrewserong</a>, <a href=\"https://profiles.wordpress.org/apeatling\">Andy Peatling</a>, <a href=\"https://profiles.wordpress.org/ameeker\">Angie Meeker</a>, <a href=\"https://profiles.wordpress.org/annaharrison\">Anna Harrison</a>, <a href=\"https://profiles.wordpress.org/atimmer\">Anton Timmermans</a>, <a href=\"https://profiles.wordpress.org/arnaudban\">ArnaudBan</a>, <a href=\"https://profiles.wordpress.org/arshidkv12\">Arshid</a>, <a href=\"https://profiles.wordpress.org/aprakasa\">Arya Prakasa</a>, <a href=\"https://profiles.wordpress.org/artisticasad\">Asad</a>, <a href=\"https://profiles.wordpress.org/mrasharirfan\">Ashar Irfan</a>, <a href=\"https://profiles.wordpress.org/asvinballoo\">asvinballoo</a>, <a href=\"https://profiles.wordpress.org/atanasangelovdev\">Atanas Angelov</a>, <a href=\"https://profiles.wordpress.org/b-07\">Bappi</a>, <a href=\"https://profiles.wordpress.org/bcolumbia\">bcolumbia</a>, <a href=\"https://profiles.wordpress.org/belcherj\">belcherj</a>, <a href=\"https://profiles.wordpress.org/caxco93\">Benjamin Eyzaguirre</a>, <a href=\"https://profiles.wordpress.org/benjamin_zekavica\">Benjamin Zekavica</a>, <a href=\"https://profiles.wordpress.org/benlk\">benlk</a>, <a href=\"https://profiles.wordpress.org/kau-boy\">Bernhard Kau</a>, <a href=\"https://profiles.wordpress.org/bernhard-reiter\">Bernhard Reiter</a>, <a href=\"https://profiles.wordpress.org/betsela\">betsela</a>, <a href=\"https://profiles.wordpress.org/bhargavmehta\">Bhargav Mehta</a>, <a href=\"https://profiles.wordpress.org/birgire\">Birgir Erlendsson (birgire)</a>, <a href=\"https://profiles.wordpress.org/bph\">Birgit Pauli-Haack</a>, <a href=\"https://profiles.wordpress.org/blowery\">blowery</a>, <a href=\"https://profiles.wordpress.org/bobbingwide\">bobbingwide</a>, <a href=\"https://profiles.wordpress.org/boblinthorst\">boblinthorst</a>, <a href=\"https://profiles.wordpress.org/boonebgorges\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/bradyvercher\">Brady Vercher</a>, <a href=\"https://profiles.wordpress.org/kraftbj\">Brandon Kraft</a>, <a href=\"https://profiles.wordpress.org/bpayton\">Brandon Payton</a>, <a href=\"https://profiles.wordpress.org/brentswisher\">Brent Swisher</a>, <a href=\"https://profiles.wordpress.org/technosiren\">Brianna Privett</a>, <a href=\"https://profiles.wordpress.org/briannaorg\">briannaorg</a>, <a href=\"https://profiles.wordpress.org/bronsonquick\">Bronson Quick</a>, <a href=\"https://profiles.wordpress.org/bandonrandon\">Brooke.</a>, <a href=\"https://profiles.wordpress.org/burhandodhy\">Burhan Nasir</a>, <a href=\"https://profiles.wordpress.org/cantothemes\">CantoThemes</a>, <a href=\"https://profiles.wordpress.org/cathibosco\">cathibosco</a>, <a href=\"https://profiles.wordpress.org/chetan200891\">Chetan Prajapati</a>, <a href=\"https://profiles.wordpress.org/chetansatasiya\">chetansatasiya</a>, <a href=\"https://profiles.wordpress.org/ketuchetan\">chetansatasiya</a>, <a href=\"https://profiles.wordpress.org/chouby\">Chouby</a>, <a href=\"https://profiles.wordpress.org/crunnells\">Chris Runnells</a>, <a href=\"https://profiles.wordpress.org/chrisvanpatten\">Chris Van Patten</a>, <a href=\"https://profiles.wordpress.org/chriskmnds\">chriskmnds</a>, <a href=\"https://profiles.wordpress.org/chrisl27\">chrisl27</a>, <a href=\"https://profiles.wordpress.org/pixelverbieger\">Christian Sabo</a>, <a href=\"https://profiles.wordpress.org/christophherr\">Christoph Herr</a>, <a href=\"https://profiles.wordpress.org/circlecube\">circlecube</a>, <a href=\"https://profiles.wordpress.org/claudiosanches\">Claudio Sanches</a>, <a href=\"https://profiles.wordpress.org/coderkevin\">coderkevin</a>, <a href=\"https://profiles.wordpress.org/copons\">Copons</a>, <a href=\"https://profiles.wordpress.org/courtney0burton\">courtney0burton</a>, <a href=\"https://profiles.wordpress.org/littlebigthing\">Csaba (LittleBigThings)</a>, <a href=\"https://profiles.wordpress.org/csabotta\">csabotta</a>, <a href=\"https://profiles.wordpress.org/danieltj\">Daniel James</a>, <a href=\"https://profiles.wordpress.org/talldanwp\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/danielhw\">danielhw</a>, <a href=\"https://profiles.wordpress.org/daniloercoli\">daniloercoli</a>, <a href=\"https://profiles.wordpress.org/dannycooper\">DannyCooper</a>, <a href=\"https://profiles.wordpress.org/nerrad\">Darren Ethier (nerrad)</a>, <a href=\"https://profiles.wordpress.org/davemoran118\">davemoran118</a>, <a href=\"https://profiles.wordpress.org/dcavins\">David Cavins</a>, <a href=\"https://profiles.wordpress.org/dlh\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/davidakennedy\">David Kennedy</a>, <a href=\"https://profiles.wordpress.org/dryanpress\">David Ryan</a>, <a href=\"https://profiles.wordpress.org/davidsword\">David Sword</a>, <a href=\"https://profiles.wordpress.org/folletto\">Davide &#8216;Folletto&#8217; Casali</a>, <a href=\"https://profiles.wordpress.org/davidherrera\">davidherrera</a>, <a href=\"https://profiles.wordpress.org/davisshaver\">Davis</a>, <a href=\"https://profiles.wordpress.org/dciso\">dciso</a>, <a href=\"https://profiles.wordpress.org/dmsnell\">Dennis Snell</a>, <a href=\"https://profiles.wordpress.org/dsmart\">Derek Smart</a>, <a href=\"https://profiles.wordpress.org/designsimply\">designsimply</a>, <a href=\"https://profiles.wordpress.org/dlocc\">Devin Walker</a>, <a href=\"https://profiles.wordpress.org/deviodigital\">Devio Digital</a>, <a href=\"https://profiles.wordpress.org/dfangstrom\">dfangstrom</a>, <a href=\"https://profiles.wordpress.org/dhanendran\">Dhanendran</a>, <a href=\"https://profiles.wordpress.org/diegoliv\">Diego de Oliveira</a>, <a href=\"https://profiles.wordpress.org/diegoreymendez\">diegoreymendez</a>, <a href=\"https://profiles.wordpress.org/dingo_bastard\">dingo-d</a>, <a href=\"https://profiles.wordpress.org/dd32\">Dion Hulse</a>, <a href=\"https://profiles.wordpress.org/dency\">Dixita Dusara</a>, <a href=\"https://profiles.wordpress.org/dixitadusara\">Dixita Gohil</a>, <a href=\"https://profiles.wordpress.org/ocean90\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/donnapep\">Donna Peplinskie</a>, <a href=\"https://profiles.wordpress.org/drewapicture\">Drew Jaynes</a>, <a href=\"https://profiles.wordpress.org/dsawardekar\">dsawardekar</a>, <a href=\"https://profiles.wordpress.org/dsifford\">dsifford</a>, <a href=\"https://profiles.wordpress.org/duanestorey\">Duane Storey</a>, <a href=\"https://profiles.wordpress.org/chopinbach\">Edwin Cromley</a>, <a href=\"https://profiles.wordpress.org/ehg\">ehg</a>, <a href=\"https://profiles.wordpress.org/electricfeet\">ElectricFeet</a>, <a href=\"https://profiles.wordpress.org/eliorivero\">Elio Rivero</a>, <a href=\"https://profiles.wordpress.org/epointal\">Elisabeth Pointal</a>, <a href=\"https://profiles.wordpress.org/iseulde\">Ella Iseulde Van Dorpe</a>, <a href=\"https://profiles.wordpress.org/elrae\">elrae</a>, <a href=\"https://profiles.wordpress.org/enodekciw\">enodekciw</a>, <a href=\"https://profiles.wordpress.org/ephoxjames\">ephoxjames</a>, <a href=\"https://profiles.wordpress.org/ephoxmogran\">ephoxmogran</a>, <a href=\"https://profiles.wordpress.org/sewmyheadon\">Eric Amundson</a>, <a href=\"https://profiles.wordpress.org/ericnmurphy\">ericnmurphy</a>, <a href=\"https://profiles.wordpress.org/etoledom\">etoledom</a>, <a href=\"https://profiles.wordpress.org/fabiankaegy\">fabiankaegy</a>, <a href=\"https://profiles.wordpress.org/fabs_pim\">fabs_pim</a>, <a href=\"https://profiles.wordpress.org/faishal\">faishal</a>, <a href=\"https://profiles.wordpress.org/flixos90\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/floriansimeth\">Florian Simeth</a>, <a href=\"https://profiles.wordpress.org/foobar4u\">foobar4u</a>, <a href=\"https://profiles.wordpress.org/foreverpinetree\">foreverpinetree</a>, <a href=\"https://profiles.wordpress.org/frank-klein\">Frank Klein</a>, <a href=\"https://profiles.wordpress.org/fuyuko\">fuyuko</a>, <a href=\"https://profiles.wordpress.org/gma992\">Gabriel Maldonado</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/garyj\">Gary Jones</a>, <a href=\"https://profiles.wordpress.org/doomwaxer\">Gary Thayer</a>, <a href=\"https://profiles.wordpress.org/garyjones\">garyjones</a>, <a href=\"https://profiles.wordpress.org/soulseekah\">Gennady Kovshenin</a>, <a href=\"https://profiles.wordpress.org/babbardel\">George Olaru</a>, <a href=\"https://profiles.wordpress.org/georgestephanis\">George Stephanis</a>, <a href=\"https://profiles.wordpress.org/georgeh\">georgeh</a>, <a href=\"https://profiles.wordpress.org/gnif\">gnif</a>, <a href=\"https://profiles.wordpress.org/goldsounds\">goldsounds</a>, <a href=\"https://profiles.wordpress.org/grappler\">Grappler</a>, <a href=\"https://profiles.wordpress.org/gziolo\">Grzegorz Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/bordoni\">Gustavo Bordoni</a>, <a href=\"https://profiles.wordpress.org/gwwar\">gwwar</a>, <a href=\"https://profiles.wordpress.org/hardeepasrani\">Hardeep Asrani</a>, <a href=\"https://profiles.wordpress.org/hblackett\">hblackett</a>, <a href=\"https://profiles.wordpress.org/helen\">Helen Hou-Sandi</a>, <a href=\"https://profiles.wordpress.org/luehrsen\">Hendrik Luehrsen</a>, <a href=\"https://profiles.wordpress.org/herbmiller\">herbmiller</a>, <a href=\"https://profiles.wordpress.org/herregroen\">Herre Groen</a>, <a href=\"https://profiles.wordpress.org/hugobaeta\">Hugo Baeta</a>, <a href=\"https://profiles.wordpress.org/hypest\">hypest</a>, <a href=\"https://profiles.wordpress.org/iandunn\">Ian Dunn</a>, <a href=\"https://profiles.wordpress.org/ianstewart\">ianstewart</a>, <a href=\"https://profiles.wordpress.org/ianbelanger\">ibelanger</a>, <a href=\"https://profiles.wordpress.org/icaleb\">iCaleb</a>, <a href=\"https://profiles.wordpress.org/idpokute\">idpokute</a>, <a href=\"https://profiles.wordpress.org/igorsch\">Igor</a>, <a href=\"https://profiles.wordpress.org/imath\">imath</a>, <a href=\"https://profiles.wordpress.org/imonly_ik\">Imran Khalid</a>, <a href=\"https://profiles.wordpress.org/intronic\">intronic</a>, <a href=\"https://profiles.wordpress.org/ipstenu\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/ireneyoast\">Irene Strikkers</a>, <a href=\"https://profiles.wordpress.org/ismailelkorchi\">Ismail El Korchi</a>, <a href=\"https://profiles.wordpress.org/israelshmueli\">israelshmueli</a>, <a href=\"https://profiles.wordpress.org/jdgrimes\">J.D. Grimes</a>, <a href=\"https://profiles.wordpress.org/jd55\">J.D. Grimes</a>, <a href=\"https://profiles.wordpress.org/jakept\">Jacob Peattie</a>, <a href=\"https://profiles.wordpress.org/jagnew\">jagnew</a>, <a href=\"https://profiles.wordpress.org/jahvi\">jahvi</a>, <a href=\"https://profiles.wordpress.org/jnylen0\">James Nylen</a>, <a href=\"https://profiles.wordpress.org/jamestryon\">jamestryon</a>, <a href=\"https://profiles.wordpress.org/jamiehalvorson\">jamiehalvorson</a>, <a href=\"https://profiles.wordpress.org/jdembowski\">Jan Dembowski</a>, <a href=\"https://profiles.wordpress.org/janalwin\">janalwin</a>, <a href=\"https://profiles.wordpress.org/jaswrks\">Jason Caldwell</a>, <a href=\"https://profiles.wordpress.org/octalmage\">Jason Stallings</a>, <a href=\"https://profiles.wordpress.org/yingling017\">Jason Yingling</a>, <a href=\"https://profiles.wordpress.org/vengisss\">Javier Villanueva</a>, <a href=\"https://profiles.wordpress.org/jhoffm34\">Jay Hoffmann</a>, <a href=\"https://profiles.wordpress.org/audrasjb\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/jblz\">Jeff Bowen</a>, <a href=\"https://profiles.wordpress.org/jeffpaul\">Jeffrey Paul</a>, <a href=\"https://profiles.wordpress.org/jeremyfelt\">Jeremy Felt</a>, <a href=\"https://profiles.wordpress.org/jipmoors\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby\">JJJ</a>, <a href=\"https://profiles.wordpress.org/sephsekla\">Joe Bailey-Roberts</a>, <a href=\"https://profiles.wordpress.org/joedolson\">Joe Dolson</a>, <a href=\"https://profiles.wordpress.org/joehoyle\">Joe Hoyle</a>, <a href=\"https://profiles.wordpress.org/joemcgill\">Joe McGill</a>, <a href=\"https://profiles.wordpress.org/joemaller\">joemaller</a>, <a href=\"https://profiles.wordpress.org/joen\">Joen Asmussen</a>, <a href=\"https://profiles.wordpress.org/j-falk\">Johan Falk</a>, <a href=\"https://profiles.wordpress.org/johnbillion\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnny5\">John Godley</a>, <a href=\"https://profiles.wordpress.org/johndyer\">johndyer</a>, <a href=\"https://profiles.wordpress.org/johnpixle\">JohnPixle</a>, <a href=\"https://profiles.wordpress.org/johnwatkins0\">johnwatkins0</a>, <a href=\"https://profiles.wordpress.org/jomurgel\">jomurgel</a>, <a href=\"https://profiles.wordpress.org/desrosj\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/spacedmonkey\">Jonny Harris</a>, <a href=\"https://profiles.wordpress.org/jonsurrell\">jonsurrell</a>, <a href=\"https://profiles.wordpress.org/joostdevalk\">Joost de Valk</a>, <a href=\"https://profiles.wordpress.org/koke\">Jorge Bernal</a>, <a href=\"https://profiles.wordpress.org/jorgefilipecosta\">Jorge Costa</a>, <a href=\"https://profiles.wordpress.org/ieatwebsites\">Jose Fremaint</a>, <a href=\"https://profiles.wordpress.org/shelob9\">Josh Pollock</a>, <a href=\"https://profiles.wordpress.org/jvisick77\">Josh Visick</a>, <a href=\"https://profiles.wordpress.org/joshuawold\">Joshua Wold</a>, <a href=\"https://profiles.wordpress.org/joyously\">Joy</a>, <a href=\"https://profiles.wordpress.org/jrf\">jrf</a>, <a href=\"https://profiles.wordpress.org/jryancard\">jryancard</a>, <a href=\"https://profiles.wordpress.org/jsnajdr\">jsnajdr</a>, <a href=\"https://profiles.wordpress.org/julienmelissas\">JulienMelissas</a>, <a href=\"https://profiles.wordpress.org/kopepasah\">Justin Kopepasah</a>, <a href=\"https://profiles.wordpress.org/kadamwhite\">K.Adam White</a>, <a href=\"https://profiles.wordpress.org/kallehauge\">Kallehauge</a>, <a href=\"https://profiles.wordpress.org/kalpshit\">KalpShit Akabari</a>, <a href=\"https://profiles.wordpress.org/codebykat\">Kat Hagan</a>, <a href=\"https://profiles.wordpress.org/ryelle\">Kelly Dwan</a>, <a href=\"https://profiles.wordpress.org/kevinwhoffman\">Kevin Hoffman</a>, <a href=\"https://profiles.wordpress.org/khleomix\">khleomix</a>, <a href=\"https://profiles.wordpress.org/ixkaito\">Kite</a>, <a href=\"https://profiles.wordpress.org/kjellr\">Kjell Reigstad</a>, <a href=\"https://profiles.wordpress.org/kluny\">kluny</a>, <a href=\"https://profiles.wordpress.org/obenland\">Konstantin Obenland</a>, <a href=\"https://profiles.wordpress.org/xkon\">Konstantinos Xenos</a>, <a href=\"https://profiles.wordpress.org/krutidugade\">krutidugade</a>, <a href=\"https://profiles.wordpress.org/lancewillett\">Lance Willett</a>, <a href=\"https://profiles.wordpress.org/notlaura\">Lara Schenck</a>, <a href=\"https://profiles.wordpress.org/leahkoerper\">leahkoerper</a>, <a href=\"https://profiles.wordpress.org/lloyd\">lloyd</a>, <a href=\"https://profiles.wordpress.org/loicblascos\">Loic</a>, <a href=\"https://profiles.wordpress.org/lucasstark\">Lucas Stark</a>, <a href=\"https://profiles.wordpress.org/lucasrolff\">LucasRolff</a>, <a href=\"https://profiles.wordpress.org/luigipulcini\">luigipulcini</a>, <a href=\"https://profiles.wordpress.org/lukecavanagh\">Luke Cavanagh</a>, <a href=\"https://profiles.wordpress.org/lucaskowalski\">Luke Kowalski</a>, <a href=\"https://profiles.wordpress.org/lukepettway\">Luke Pettway</a>, <a href=\"https://profiles.wordpress.org/luminus\">Luminus</a>, <a href=\"https://profiles.wordpress.org/lynneux\">lynneux</a>, <a href=\"https://profiles.wordpress.org/m-e-h\">m-e-h</a>, <a href=\"https://profiles.wordpress.org/macbookandrew\">macbookandrew</a>, <a href=\"https://profiles.wordpress.org/maedahbatool\">Maedah Batool</a>, <a href=\"https://profiles.wordpress.org/mahdiyazdani\">Mahdi Yazdani</a>, <a href=\"https://profiles.wordpress.org/mahmoudsaeed\">mahmoudsaeed</a>, <a href=\"https://profiles.wordpress.org/travel_girl\">Maja Benke</a>, <a href=\"https://profiles.wordpress.org/mkaz\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/tyxla\">Marin Atanasov</a>, <a href=\"https://profiles.wordpress.org/marina_wp\">marina_wp</a>, <a href=\"https://profiles.wordpress.org/clorith\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/mariusvw\">mariusvw</a>, <a href=\"https://profiles.wordpress.org/markjaquith\">Mark Jaquith</a>, <a href=\"https://profiles.wordpress.org/mapk\">Mark Uraine</a>, <a href=\"https://profiles.wordpress.org/martinlugton\">martinlugton</a>, <a href=\"https://profiles.wordpress.org/mathiu\">mathiu</a>, <a href=\"https://profiles.wordpress.org/webdevmattcrom\">Matt Cromwell</a>, <a href=\"https://profiles.wordpress.org/matt\">Matt Mullenweg</a>, <a href=\"https://profiles.wordpress.org/mattgeri\">MattGeri</a>, <a href=\"https://profiles.wordpress.org/mboynes\">Matthew Boynes</a>, <a href=\"https://profiles.wordpress.org/mattheu\">Matthew Haines-Young</a>, <a href=\"https://profiles.wordpress.org/maurobringolf\">maurobringolf</a>, <a href=\"https://profiles.wordpress.org/maximebj\">Maxime BERNARD-JACQUET</a>, <a href=\"https://profiles.wordpress.org/mayukojpn\">Mayo Moriyama</a>, <a href=\"https://profiles.wordpress.org/meetjey\">meetjey</a>, <a href=\"https://profiles.wordpress.org/melchoyce\">Mel Choyce</a>, <a href=\"https://profiles.wordpress.org/mendezcode\">mendezcode</a>, <a href=\"https://profiles.wordpress.org/woodent\">Micah Wood</a>, <a href=\"https://profiles.wordpress.org/mdawaffe\">Michael Adams (mdawaffe)</a>, <a href=\"https://profiles.wordpress.org/michaelhull\">Michael Hull</a>, <a href=\"https://profiles.wordpress.org/mnelson4\">Michael Nelson</a>, <a href=\"https://profiles.wordpress.org/mizejewski\">Michele Mizejewski</a>, <a href=\"https://profiles.wordpress.org/jbpaul17\">Migrated to @jeffpaul</a>, <a href=\"https://profiles.wordpress.org/stubgo\">Miina Sikk</a>, <a href=\"https://profiles.wordpress.org/simison\">Mikael Korpela</a>, <a href=\"https://profiles.wordpress.org/mihai2u\">Mike Crantea</a>, <a href=\"https://profiles.wordpress.org/mike-haydon-swo\">Mike Haydon</a>, <a href=\"https://profiles.wordpress.org/mikeschroder\">Mike Schroder</a>, <a href=\"https://profiles.wordpress.org/mikehaydon\">mikehaydon</a>, <a href=\"https://profiles.wordpress.org/mikeyarce\">Mikey Arce</a>, <a href=\"https://profiles.wordpress.org/dimadin\">Milan Dinić</a>, <a href=\"https://profiles.wordpress.org/milana_cap\">Milana Cap</a>, <a href=\"https://profiles.wordpress.org/gonzomir\">Milen Petrinski &#8211; Gonzo</a>, <a href=\"https://profiles.wordpress.org/milesdelliott\">milesdelliott</a>, <a href=\"https://profiles.wordpress.org/mimo84\">mimo84</a>, <a href=\"https://profiles.wordpress.org/0mirka00\">mirka</a>, <a href=\"https://profiles.wordpress.org/mitogh\">mitogh</a>, <a href=\"https://profiles.wordpress.org/mmtr86\">mmtr86</a>, <a href=\"https://profiles.wordpress.org/boemedia\">Monique Dubbelman</a>, <a href=\"https://profiles.wordpress.org/mor10\">Morten Rand-Hendriksen</a>, <a href=\"https://profiles.wordpress.org/mostafas1990\">Mostafa Soufi</a>, <a href=\"https://profiles.wordpress.org/motleydev\">motleydev</a>, <a href=\"https://profiles.wordpress.org/mpheasant\">mpheasant</a>, <a href=\"https://profiles.wordpress.org/mrmadhat\">mrmadhat</a>, <a href=\"https://profiles.wordpress.org/mrwweb\">mrwweb</a>, <a href=\"https://profiles.wordpress.org/msdesign21\">msdesign21</a>, <a href=\"https://profiles.wordpress.org/mtias\">mtias</a>, <a href=\"https://profiles.wordpress.org/desideveloper\">Muhammad Irfan</a>, <a href=\"https://profiles.wordpress.org/mukesh27\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/munirkamal\">munirkamal</a>, <a href=\"https://profiles.wordpress.org/mmaumio\">Muntasir Mahmud</a>, <a href=\"https://profiles.wordpress.org/mzorz\">mzorz</a>, <a href=\"https://profiles.wordpress.org/nagayama\">nagayama</a>, <a href=\"https://profiles.wordpress.org/nfmohit\">Nahid F. Mohit</a>, <a href=\"https://profiles.wordpress.org/nao\">Naoko Takano</a>, <a href=\"https://profiles.wordpress.org/napy84\">napy84</a>, <a href=\"https://profiles.wordpress.org/nateconley\">nateconley</a>, <a href=\"https://profiles.wordpress.org/nativeinside\">Native Inside</a>, <a href=\"https://profiles.wordpress.org/greatislander\">Ned Zimmerman</a>, <a href=\"https://profiles.wordpress.org/buzztone\">Neil Murray</a>, <a href=\"https://profiles.wordpress.org/nicbertino\">nic.bertino</a>, <a href=\"https://profiles.wordpress.org/notnownikki\">Nicola Heald</a>, <a href=\"https://profiles.wordpress.org/nielslange\">Niels Lange</a>, <a href=\"https://profiles.wordpress.org/nikschavan\">Nikhil Chavan</a>, <a href=\"https://profiles.wordpress.org/nbachiyski\">Nikolay Bachiyski</a>, <a href=\"https://profiles.wordpress.org/nitrajka\">nitrajka</a>, <a href=\"https://profiles.wordpress.org/njpanderson\">njpanderson</a>, <a href=\"https://profiles.wordpress.org/nosolosw\">nosolosw</a>, <a href=\"https://profiles.wordpress.org/nshki\">nshki</a>, <a href=\"https://profiles.wordpress.org/hideokamoto\">Okamoto Hidetaka</a>, <a href=\"https://profiles.wordpress.org/oskosk\">oskosk</a>, <a href=\"https://profiles.wordpress.org/pareshradadiya-1\">Paresh Radadiya</a>, <a href=\"https://profiles.wordpress.org/swissspidy\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/pbearne\">Paul Bearne</a>, <a href=\"https://profiles.wordpress.org/pauldechov\">Paul Dechov</a>, <a href=\"https://profiles.wordpress.org/paulstonier\">Paul Stonier</a>, <a href=\"https://profiles.wordpress.org/paulwilde\">Paul Wilde</a>, <a href=\"https://profiles.wordpress.org/pedromendonca\">Pedro Mendonça</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/pglewis\">pglewis</a>, <a href=\"https://profiles.wordpress.org/tyrannous\">Philipp Bammes</a>, <a href=\"https://profiles.wordpress.org/piersb\">piersb</a>, <a href=\"https://profiles.wordpress.org/wizzard_\">Pieter Daalder</a>, <a href=\"https://profiles.wordpress.org/pilou69\">pilou69</a>, <a href=\"https://profiles.wordpress.org/delawski\">Piotr Delawski</a>, <a href=\"https://profiles.wordpress.org/poena\">poena</a>, <a href=\"https://profiles.wordpress.org/postphotos\">postphotos</a>, <a href=\"https://profiles.wordpress.org/potbot\">potbot</a>, <a href=\"https://profiles.wordpress.org/prtksxna\">Prateek Saxena</a>, <a href=\"https://profiles.wordpress.org/pratikthink\">pratikthink</a>, <a href=\"https://profiles.wordpress.org/presskopp\">Presskopp</a>, <a href=\"https://profiles.wordpress.org/psealock\">psealock</a>, <a href=\"https://profiles.wordpress.org/ptasker\">ptasker</a>, <a href=\"https://profiles.wordpress.org/rachelmcr\">Rachel</a>, <a href=\"https://profiles.wordpress.org/rachelbaker\">Rachel Baker</a>, <a href=\"https://profiles.wordpress.org/rahmohn\">Rahmohn</a>, <a href=\"https://profiles.wordpress.org/rahmon\">Rahmon</a>, <a href=\"https://profiles.wordpress.org/rahulsprajapati\">Rahul Prajapati</a>, <a href=\"https://profiles.wordpress.org/rakshans1\">rakshans1</a>, <a href=\"https://profiles.wordpress.org/ramonopoly\">ramonopoly</a>, <a href=\"https://profiles.wordpress.org/lamosty\">Rastislav Lamos</a>, <a href=\"https://profiles.wordpress.org/revgeorge\">revgeorge</a>, <a href=\"https://profiles.wordpress.org/youknowriad\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/rianrietveld\">Rian Rietveld</a>, <a href=\"https://profiles.wordpress.org/richsalvucci\">richsalvucci</a>, <a href=\"https://profiles.wordpress.org/riddhiehta02\">Riddhi Mehta</a>, <a href=\"https://profiles.wordpress.org/rileybrook\">Riley Brook</a>, <a href=\"https://profiles.wordpress.org/noisysocks\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/sanchothefat\">Robert O&#8217;Rourke</a>, <a href=\"https://profiles.wordpress.org/robertsky\">robertsky</a>, <a href=\"https://profiles.wordpress.org/_dorsvenabili\">Rocio Valdivia</a>, <a href=\"https://profiles.wordpress.org/rohittm\">Rohit Motwani</a>, <a href=\"https://profiles.wordpress.org/magicroundabout\">Ross Wintle</a>, <a href=\"https://profiles.wordpress.org/rmccue\">Ryan McCue</a>, <a href=\"https://profiles.wordpress.org/welcher\">Ryan Welcher</a>, <a href=\"https://profiles.wordpress.org/ryo511\">ryo511</a>, <a href=\"https://profiles.wordpress.org/sagarprajapati\">Sagar Prajapati</a>, <a href=\"https://profiles.wordpress.org/samikeijonen\">Sami Keijonen</a>, <a href=\"https://profiles.wordpress.org/otto42\">Samuel Wood (Otto)</a>, <a href=\"https://profiles.wordpress.org/smyoon315\">Sang-Min Yoon</a>, <a href=\"https://profiles.wordpress.org/tinkerbelly\">sarah semark</a>, <a href=\"https://profiles.wordpress.org/scottmweaver\">Scott Weaver</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/sergioestevao\">SergioEstevao</a>, <a href=\"https://profiles.wordpress.org/azchughtai\">Shahjehan Ali</a>, <a href=\"https://profiles.wordpress.org/shaileesheth\">Shailee Sheth</a>, <a href=\"https://profiles.wordpress.org/sharaz\">Sharaz Shahid</a>, <a href=\"https://profiles.wordpress.org/giventofly76\">Shaun sc</a>, <a href=\"https://profiles.wordpress.org/shaunandrews\">shaunandrews</a>, <a href=\"https://profiles.wordpress.org/shooper\">Shawn Hooper</a>, <a href=\"https://profiles.wordpress.org/shenkj\">shenkj</a>, <a href=\"https://profiles.wordpress.org/sikander\">sikander</a>, <a href=\"https://profiles.wordpress.org/pross\">Simon Prosser</a>, <a href=\"https://profiles.wordpress.org/siriokun\">siriokun</a>, <a href=\"https://profiles.wordpress.org/sirjonathan\">sirjonathan</a>, <a href=\"https://profiles.wordpress.org/sirreal\">sirreal</a>, <a href=\"https://profiles.wordpress.org/sisanu\">Sisanu</a>, <a href=\"https://profiles.wordpress.org/skorasaurus\">skorasaurus</a>, <a href=\"https://profiles.wordpress.org/butimnoexpert\">Slushman</a>, <a href=\"https://profiles.wordpress.org/ssousa\">Sofia Sousa</a>, <a href=\"https://profiles.wordpress.org/somtijds\">SOMTIJDS</a>, <a href=\"https://profiles.wordpress.org/soean\">Soren Wrede</a>, <a href=\"https://profiles.wordpress.org/spocke\">spocke</a>, <a href=\"https://profiles.wordpress.org/stagger-lee\">Stagger Lee</a>, <a href=\"https://profiles.wordpress.org/sstoqnov\">Stanimir Stoyanov</a>, <a href=\"https://profiles.wordpress.org/netweb\">Stephen Edgar</a>, <a href=\"https://profiles.wordpress.org/stevehenty\">Steve Henty</a>, <a href=\"https://profiles.wordpress.org/charlestonsw\">Store Locator Plus</a>, <a href=\"https://profiles.wordpress.org/strategio\">strategio</a>, <a href=\"https://profiles.wordpress.org/stuartfeldt\">stuartfeldt</a>, <a href=\"https://profiles.wordpress.org/tacrapo\">tacrapo</a>, <a href=\"https://profiles.wordpress.org/tammie_l\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/themeroots\">ThemeRoots</a>, <a href=\"https://profiles.wordpress.org/tfrommen\">Thorsten Frommen</a>, <a href=\"https://profiles.wordpress.org/thrijith\">Thrijith Thankachan</a>, <a href=\"https://profiles.wordpress.org/hedgefield\">Tim Hengeveld</a>, <a href=\"https://profiles.wordpress.org/timgardner\">timgardner</a>, <a href=\"https://profiles.wordpress.org/timmydcrawford\">Timmy Crawford</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/tjnowell\">Tom J Nowell</a>, <a href=\"https://profiles.wordpress.org/tlxo\">Toni Laakso</a>, <a href=\"https://profiles.wordpress.org/tobifjellner\">Tor-Bjorn Fjellner</a>, <a href=\"https://profiles.wordpress.org/toro_unit\">Toro_Unit (Hiroshi Urabe)</a>, <a href=\"https://profiles.wordpress.org/mirucon\">Toshihiro Kanai</a>, <a href=\"https://profiles.wordpress.org/itowhid06\">Towhidul Islam</a>, <a href=\"https://profiles.wordpress.org/travislopes\">Travis Lopes</a>, <a href=\"https://profiles.wordpress.org/truongwp\">truongwp</a>, <a href=\"https://profiles.wordpress.org/tjfunke001\">Tunji Ayoola</a>, <a href=\"https://profiles.wordpress.org/twoelevenjay\">twoelevenjay</a>, <a href=\"https://profiles.wordpress.org/grapplerulrich\">Ulrich</a>, <a href=\"https://profiles.wordpress.org/vindl\">vindl</a>, <a href=\"https://profiles.wordpress.org/vishalkakadiya\">Vishal Kakadiya</a>, <a href=\"https://profiles.wordpress.org/vtrpldn\">Vitor Paladini</a>, <a href=\"https://profiles.wordpress.org/walterebert\">Walter Ebert</a>, <a href=\"https://profiles.wordpress.org/warmarks\">warmarks</a>, <a href=\"https://profiles.wordpress.org/webmandesign\">WebMan Design | Oliver Juhas</a>, <a href=\"https://profiles.wordpress.org/websupporter\">websupporter</a>, <a href=\"https://profiles.wordpress.org/westonruter\">Weston Ruter</a>, <a href=\"https://profiles.wordpress.org/earnjam\">William Earnhardt</a>, <a href=\"https://profiles.wordpress.org/williampatton\">williampatton</a>, <a href=\"https://profiles.wordpress.org/willybahuaud\">Willy Bahuaud</a>, <a href=\"https://profiles.wordpress.org/wpscholar\">wpscholar</a>, <a href=\"https://profiles.wordpress.org/xyfi\">xyfi</a>, <a href=\"https://profiles.wordpress.org/yahil\">Yahil Madakiya</a>, <a href=\"https://profiles.wordpress.org/yingles\">yingles</a>, <a href=\"https://profiles.wordpress.org/yoavf\">Yoav Farhi</a>, <a href=\"https://profiles.wordpress.org/youthkee\">Yusuke Takahashi</a>, <a href=\"https://profiles.wordpress.org/zebulan\">zebulan</a>&nbsp;e&nbsp;<a href=\"https://profiles.wordpress.org/ziyaddin\">Ziyaddin Sadigov</a>.</p>\n\n\n\n<p>Finalmente, nossos agradecimentos a toda a comunidade de tradutores que trabalharam no WordPress 5.0. Seus esforços trazem o WordPress 5.0 completamente traduzido em 37 idiomas logo no lançamento, e tem mais a caminho.</p>\n\n\n\n<p>Se você quer continuar acompanhando ou quer ajudar, leia o&nbsp;<a href=\"https://make.wordpress.org/\">Make WordPress</a> e o nosso <a href=\"https://make.wordpress.org/core/\">blog de desenvolvimento dos arquivos básicos</a>.</p>\n\n\n\n<p>Agradecemos por escolher o WordPress!</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:36:\"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"WordPress 5.0 RC3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://br.wordpress.org/2018/12/04/wordpress-5-0-rc3/\";s: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, 04 Dec 2018 16:00:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1382\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:328:\"O terceiro release candidate (versão candidata, em tradução livre) do WordPress 5.0 já está disponível! O WordPress 5.0 será lançado em 6 de dezembro de 2018. Este é um grande lançamento e precisa da sua ajuda. Se você ainda não testou a versão 5.0, a hora é essa! Para testar o WordPress 5.0 beta, você [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3016:\"\n<p>O terceiro <em>release candidate</em> (versão candidata, em tradução livre) do WordPress 5.0 já está disponível!</p>\n\n\n\n<p><strong>O WordPress 5.0 será lançado em </strong><a href=\"https://make.wordpress.org/core/2018/12/04/new-5-0-target-date/\"><strong>6 de dezembro de 2018</strong></a>. Este é um grande lançamento e precisa da <em>sua</em> ajuda. Se você ainda não testou a versão 5.0, a hora é essa!</p>\n\n\n\n<p>Para testar o WordPress 5.0 beta, você pode usar o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;ou você pode <a href=\"https://wordpress.org/wordpress-5.0-RC3.zip\">baixar o release candidate aqui</a>&nbsp;(zip).</p>\n\n\n\n<p>Para mais detalhes sobre o que esperar do WordPress 5.0, leia <a href=\"https://br.wordpress.org/news/2018/11/wordpress-5-0-release-candidate/\">o post sobre o primeiro release candidate</a>.</p>\n\n\n\n<p>Este release candidate inclui um ajuste para alguns scrips que não eram carregados em instalações em subdiretórios (<a href=\"https://core.trac.wordpress.org/ticket/45469\">#45469</a>) e configurações de locale de usuários não sendo incluídas no editor de blocos (<a href=\"https://core.trac.wordpress.org/ticket/45465\">#45465</a>). O Twenty Nineteen também recebeu pequenos ajustes.</p>\n\n\n\n<h2>Desenvolvedores de plugins e temas</h2>\n\n\n\n<p>Teste seus plugins e temas com o WordPress 5.0 e atualize para 5.0 a versão no campo&nbsp;<em>Tested up to</em>&nbsp;do arquivo readme. Se encontrar problemas de compatibilidade, tenha certeza de publicar no <a href=\"https://wordpress.org/support/forum/alphabeta/\">fórum</a> para que possamos agir antes do lançamento final. Um guia aprofundado com foco nas mudanças para desenvolvedores será publicado em breve no&nbsp;<a href=\"https://make.wordpress.org/core/\">blog de desenvolvimento dos arquivos básicos</a>. Enquanto isso, você pode rever as <a href=\"https://make.wordpress.org/core/tag/5.0+dev-notes/\">notas de desenvolvimento da versão 5.0</a>.</p>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Você lê e escreve bem em inglês?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a>&nbsp;</p>\n\n\n\n<p>Se acha que encontrou um erro, você pode publicá-lo na área <a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta</a> nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro, <a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar <a href=\"https://core.trac.wordpress.org/tickets/major\">uma lista de erros conhecidos</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>WordPress cinco ponto zero<br>vem daqui alguns dias!<br>Vamos comemorar!</em> <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f389.png\" alt=\"🎉\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:36:\"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"WordPress 5.0 RC2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://br.wordpress.org/2018/12/04/wordpress-5-0-rc2/\";s: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, 04 Dec 2018 12:52:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1378\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:375:\"O segundo release candidate (versão candidata, em tradução livre) do WordPress 5.0 já está disponível! Isso é bem importante, significa que estamos cada vez mais próximos do WordPress 5.0. Uma data de lançamento final será anunciada assim que possível, baseada nos comentários sobre este RC. Tudo parece estável e esperamos anunciar essa data em breve. [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3635:\"\n<p>O segundo <em>release candidate</em> (versão candidata, em tradução livre) do WordPress 5.0 já está disponível!</p>\n\n\n\n<p>Isso é bem importante, significa que estamos cada vez mais próximos do WordPress 5.0. Uma data de lançamento final será anunciada assim que possível, baseada nos comentários sobre este RC. Tudo parece estável e esperamos anunciar essa data em breve. Este é um grande lançamento e precisa da <em>sua</em> ajuda. Se você ainda não testou a versão 5.0, a hora é essa! </p>\n\n\n\n<p>Para testar o WordPress 5.0 beta, você pode usar o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;ou você pode <a href=\"https://wordpress.org/wordpress-5.0-RC2.zip\">baixar o release candidate aqui</a>&nbsp;(zip).</p>\n\n\n\n<p>Para mais detalhes sobre o que esperar do WordPress 5.0, leia <a href=\"https://br.wordpress.org/news/2018/11/wordpress-5-0-release-candidate/\">o post sobre o release candidate anterior</a>.</p>\n\n\n\n<h2>Mudanças significativas</h2>\n\n\n\n<ul><li>Paramos de exibir o componente de compatibilidade&nbsp;<em>AdminNotices</em>, porque a sua intenção anterior para retrocompatibilidade estava gerando avisos demais de plugins incompatíveis.</li><li>Uma atualização para que o analisador lide melhor com HTML mal formado, que poderia levar a um loop. Só soubemos que isso aconteceu uma vez em <a href=\"https://gutenstats.blog/\">mais de um milhão de posts</a> feitos com o Gutenberg, mas como isso causou um loop nós consertamos no RC2.</li></ul>\n\n\n\n<h2>Mudanças cosméticas e menores no RC2</h2>\n\n\n\n<ul><li>Acessibilidade: Simplificação nos <em>aria-labels</em> das abas da barra lateral.</li><li>Alteração para somente leitura do campo de URL do link da imagem.</li><li>Internacionalização: Mesclagem de textos similares que eram diferentes apenas por uso de maiúsculas.</li><li>CSS: Melhoria na visualização de estilos de bloco.</li><li>CSS: Ajustes de problemas visuais na disposição do texto do bloco de Botão.</li><li>Ajuste no seletor <em>getSelectedBlockClientId</em>.</li><li>Ajuste no bloco Clássico não exibindo galerias em grade.</li><li>Correção de um problema onde a barra de ferramentas do bloco jogava a imagem para baixo quando estavam selecionados os alinhamentos <em>largura ampla</em> ou <em>completa</em>.</li><li>Estilos específicos para o editor no bloco de Capa foram movidos do style.scss para o editor.scss.</li><li>Ajuste dos modais no navegador Microsoft Edge.</li><li>Ajuste da perda de foco ao iniciar o TinyMCE no Microsoft IE11. Adição de teste para o IE.</li><li>Ajuste na entrada de dados ao montar o TinyMCE no Microsoft IE11.</li><li>Alteração do nome nos @package para WordPress.</li></ul>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Você lê e escreve bem em inglês?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a>&nbsp;</p>\n\n\n\n<p>Se acha que encontrou um erro, você pode publicá-lo na área <a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta</a> nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro, <a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar <a href=\"https://core.trac.wordpress.org/tickets/major\">uma lista de erros conhecidos</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<pre class=\"wp-block-preformatted\"><em>RC bittersweet.<br>We welcome in Gutenberg,<br>Vale Gutenbeard.</em></pre>\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:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:45:\"\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:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://br.wordpress.org/2018/11/23/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:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://br.wordpress.org/2018/11/23/wordpress-5-0-release-candidate/#respond\";s: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 15:36:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1374\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:348:\"O primeiro release candidate (versão candidata, em tradução livre) do WordPress 5.0 já está disponível! Isso é bem importante, porque significa que estamos cada vez mais perto do WordPress 5.0.&#160;A data de lançamento do WordPress 5.0 foi adiada e não será mais no dia 27, para que o RC seja completamente testado. Uma data de [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5936:\"\n<p>O primeiro <em>release candidate</em> (versão candidata, em tradução livre) do WordPress 5.0 já está disponível!</p>\n\n\n\n<p>Isso é bem importante, porque significa que estamos cada vez mais perto do WordPress 5.0.&nbsp;<strong>A data de lançamento do WordPress 5.0 foi adiada e não será mais no dia 27, para que o RC seja completamente testado</strong>. Uma data de lançamento final será anunciada em breve, baseada nos comentários sobre o RC. Este é um grande lançamento e precisa da <em>sua</em> ajuda. Se você ainda não testou a versão 5.0, a hora é essa!&nbsp;</p>\n\n\n\n<p>Para testar o WordPress 5.0 beta, você pode usar o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;ou você pode <a href=\"https://wordpress.org/wordpress-5.0-RC1.zip\">baixar o release candidate aqui</a>&nbsp;(zip).</p>\n\n\n\n<h2>Quais são as novidades do WordPress 5.0?</h2>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/11/Gutenberg-3.png?resize=632%2C316&amp;ssl=1\" alt=\"Captura de tela da interface do novo editor de blocos.\" class=\"wp-image-6271\" /><figcaption>O novo editor de posts baseado em blocos.</figcaption></figure>\n\n\n\n<p>O WordPress 5.0 traz o <a href=\"https://br.wordpress.org/gutenberg/\">novo editor de posts baseado em blocos</a>. O primeiro passo para um futuro emocionante, com uma experiência de edição mais simples em todas as partes do seu site. Você terá mais flexibilidade nas formas como o conteúdo é exibido, esteja você construindo o seu primeiro site, atualizando o seu blog ou seja você programador.</p>\n\n\n\n<p>O editor de blocos está&nbsp;<a href=\"https://gutenstats.blog/\">sendo usado em mais de um milhão de sites</a> e nós acreditamos que ele está pronto para ser usado em todos os sites WordPress. Mesmo assim, entendemos que alguns sites talvez precisem de mais tempo. Se é o seu caso, instale o <a href=\"https://br.wordpress.org/plugins/classic-editor/\">plugin Editor Clássico</a> e você vai continuar usando o editor de posts clássico quando atualizar seu site para o WordPress 5.0.</p>\n\n\n\n<p>O Twenty Nineteen (2019) é o novo tema padrão do WordPress. Ele traz estilos personalizados para os blocos disponíveis por padrão no WP 5.0.&nbsp;O Twenty Nineteen foi pensado de forma que você possa usá-lo em vários tipos de sites diferentes. Se você tem um blog de fotografia, um site para seu novo negócio ou caso esteja ajudando uma ONG, o Twenty Nineteen é flexível o suficiente para atender às suas necessidades.</p>\n\n\n\n<p>O editor de blocos é uma grande mudança, mas isso não é tudo. Também fizemos algumas mudanças menores, incluindo:</p>\n\n\n\n<ul><li>Todos os temas padrão anteriores, do Twenty Ten (2010) até o Twenty Seventeen (2017), foram atualizados para dar suporte ao editor de blocos.</li><li>Você pode melhorar a acessibilidade do conteúdo que você escreve, agora que <a href=\"https://core.trac.wordpress.org/ticket/30421\">rótulos ARIA simples</a>&nbsp;podem ser salvos em posts e páginas.</li><li>O WordPress 5.0 tem oficialmente suporte para versão 7.3 do PHP: se você está usando uma versão anterior, recomendamos que você <a href=\"https://wordpress.org/support/upgrade-php/\">atualize o PHP</a>&nbsp;do seu site.</li><li>Desenvolvedores agora podem adicionar strings traduzíveis diretamente em seus códigos JavaScript, usando os novos <a href=\"https://make.wordpress.org/core/2018/11/09/new-javascript-i18n-support-in-wordpress/\">pacotes de idioma JavaScript</a>.</li></ul>\n\n\n\n<p>Você pode saber mais sobre os ajustes e mudanças desde o Beta 5 <a href=\"https://make.wordpress.org/core/2018/11/20/whats-new-in-gutenberg-20th-november/\">no post de atualização mais recente</a>.</p>\n\n\n\n<p>Para mais detalhes sobre as novidades da versão 50, leia também os posts sobre&nbsp;<a href=\"https://br.wordpress.org/news/2018/10/wordpress-5-0-beta-1/\">Beta 1</a>,&nbsp;<a href=\"https://br.wordpress.org/news/2018/10/wordpress-5-0-beta-2/\">Beta 2</a>,&nbsp;<a href=\"https://br.wordpress.org/news/2018/11/wordpress-5-0-beta-3/\">Beta 3</a>, <a href=\"https://br.wordpress.org/news/2018/11/wordpress-5-0-beta-4/\">Beta 4</a> e&nbsp;<a href=\"https://br.wordpress.org/news/2018/11/wordpress-5-0-beta-5/\">Beta 5</a>.</p>\n\n\n\n<h2>Desenvolvedores de plugins e temas</h2>\n\n\n\n<p>Teste seus plugins e temas com o WordPress 5.0 e atualize&nbsp;a versão no campo&nbsp;<em>Tested up to</em>&nbsp;do arquivo readme&nbsp;para&nbsp;<em>5.0</em>. Se encontrar problemas de compatibilidade, publique no <a href=\"https://wordpress.org/support/forum/alphabeta/\">fórum</a> para que possamos agir antes do lançamento final. Um guia aprofundado com foco nas mudanças para desenvolvedores será publicado em breve no&nbsp;<a href=\"https://make.wordpress.org/core/\">blog de desenvolvimento dos arquivos básicos</a>. Enquanto isso, você pode rever as <a href=\"https://make.wordpress.org/core/tag/5.0+dev-notes/\">notas de desenvolvimento da versão 5.0</a>.</p>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Você lê e escreve bem em inglês?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a>&nbsp;</p>\n\n\n\n<p><strong><em>Se acha que encontrou um erro</em></strong><em>, você pode publicá-lo na&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>área Alpha/Beta</em></a><em>&nbsp;do fórum oficial. Nós vamos adorar ouvir você! Se puder escrever um relatório de um erro que outras pessoas podem reproduzir,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>envie-o para o WordPress Trac (em inglês)</em></a><em>, onde você também pode encontrar&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>uma lista dos erros já conhecidos</em></a><em>.</em></p>\n\n\n\n<p><em>Ruedan los bloques<br>Contando vivos cuentos<br>Que se despiertan</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://br.wordpress.org/2018/11/23/wordpress-5-0-release-candidate/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:36:\"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2018/11/20/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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 20 Nov 2018 11:23:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1369\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:379:\"O WordPress 5.0 Beta 5 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão. Existem duas formas de testar o WordPress 5.0 Beta: com o plugin&#160;WordPress Beta Tester&#160;(você deve usar “bleeding edge nightlies”) ou você [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:5102:\"\n<p>O WordPress 5.0 Beta 5 já está disponível!</p>\n\n\n\n<p><strong>Esta versão ainda está em desenvolvimento,</strong> portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão.</p>\n\n\n\n<p>Existem duas formas de testar o WordPress 5.0 Beta: com o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(você deve usar “bleeding edge nightlies”) ou você pode <a href=\"https://wordpress.org/wordpress-5.0-beta5.zip\">baixar a versão aqui</a>&nbsp;(zip).</p>\n\n\n\n<p><strong>Lembrete: A data de lançamento do WordPress 5.0 mudou</strong>. A nova previsão de lançamento é&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">27 de novembro</a> e precisamos da sua ajuda para que isso aconteça. Aqui estão alguns ajustes importantes que fizemos desde o Beta 4:</p>\n\n\n\n<h2>Editor de blocos</h2>\n\n\n\n<p>O editor de blocos foi atualizado a partir da <a href=\"https://make.wordpress.org/core/2018/11/15/whats-new-in-gutenberg-15th-november-2/\">versão 4.4 do Gutenberg</a> e as maiores mudanças incluem:</p>\n\n\n\n<ul><li>&nbsp;Um <a href=\"https://github.com/WordPress/gutenberg/pull/11874\">painel de links permanentes foi incluído na barra lateral de documento</a> e agora é mais fácil encontrá-lo.</li><li>Os painéis de documento do editor agora podem ser <a href=\"https://github.com/WordPress/gutenberg/pull/11802\">removidos programaticamente</a>.</li><li>O indicador de envio de imagens e galerias foi substituído por uma&nbsp;<a href=\"https://github.com/WordPress/gutenberg/pull/11876\">imagem com um elemento giratório e uma versão esmaecida da imagem</a>.</li><li>Os blocos de edição de texto e código agora <a href=\"https://github.com/WordPress/gutenberg/pull/11750\">ocupam toda a largura do editor</a>.</li><li>A manipulação de imagens foi melhorada. As imagens agora ocupam a quantidade de espaço certa para  <a href=\"https://github.com/WordPress/gutenberg/pull/11846\">temas com editores mais largos</a>, como o Twenty Nineteen.<br></li><li>Estilos de <em>hover</em> agora são <a href=\"https://github.com/WordPress/gutenberg/pull/10333\">devidamente desabilitados em dispositivos móveis</a>.</li><li>O módulo de <em>i18n</em> (internacionalização) foi refatorado, recebendo <a href=\"https://github.com/WordPress/gutenberg/pull/11493\">ganhos significativos de desempenho</a>.</li></ul>\n\n\n\n<p>Além disso, alguns errinhos chatos foram corrigidos:</p>\n\n\n\n<ul><li>Melhor tratamento de <a href=\"https://github.com/WordPress/gutenberg/pull/11590\">links sem um attributo href</a>, que apareciam como <code>undefined</code>.</li><li>Texto em japonês (caracteres com double byte) <a href=\"https://github.com/WordPress/gutenberg/pull/11908\">agora estão disponíveis na lista de blocos</a>.</li><li>Melhor tratamento de codificações diferentes de texto, como emojis, por exemplo, <a href=\"https://github.com/WordPress/gutenberg/pull/11771\">na validação do bloco</a>.</li></ul>\n\n\n\n<p>A lista completa de mudanças está no <a href=\"https://make.wordpress.org/core/2018/11/15/whats-new-in-gutenberg-15th-november-2/\">post de lançamento do Gutenberg 4.4</a>.<br></p>\n\n\n\n<h2>Suporte para PHP 7.3</h2>\n\n\n\n<p>Os últimos erros conhecidos de compatibilidade com o PHP 7.3 foram corrigidos. Você pode saber mais sobre o PHP  7.3 e o WordPress lendo as <a href=\"https://make.wordpress.org/core/2018/10/15/wordpress-and-php-7-3/\">notas de desenvolvimento no blog Make WordPress Core</a>.<br></p>\n\n\n\n<h2>Twenty Nineteen (2019)</h2>\n\n\n\n<p>O esforço para que o Twenty Nineteen esteja pronto na época de lançamento da versão 5.0 continua no <a href=\"https://github.com/WordPress/twentynineteen\">repositório do GitHub</a>. Esta atualização contém <a href=\"https://core.trac.wordpress.org/changeset/43904\">vários ajustes</a>, incluindo:</p>\n\n\n\n<ul><li>Suporte para a classe&nbsp;<code>.button</code>.</li><li>Correção de font-weights para títulos.</li><li>Melhoria no suporte para barra de ferramentas fixas no editor.</li><li>Melhoria no contraste e legibilidade das cores personalizadas usadas durante a seleção de texto.</li><li>Correção do editor para que a área de meta boxes do Gutenberg não se sobreponha ao conteúdo.</li></ul>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Você lê e escreve bem em inglês?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a>&nbsp;</p>\n\n\n\n<p><strong><em>Se acha que encontrou um erro</em></strong><em>, você pode publicá-lo na&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>área Alpha/Beta</em></a><em>&nbsp;do fórum oficial. Nós vamos adorar ouvir você! Se puder escrever um relatório de um erro que outras pessoas podem reproduzir,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>envie-o para o WordPress Trac (em inglês)</em></a><em>, onde você também pode encontrar&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>uma lista dos erros já conhecidos</em></a><em>.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:45:\"\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:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2018/11/13/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:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://br.wordpress.org/2018/11/13/wordpress-5-0-beta-4/#respond\";s: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 12:13: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1363\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:379:\"O WordPress 5.0 Beta 4 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão. Existem duas formas de testar o WordPress 5.0 beta: com o plugin&#160;WordPress Beta Tester&#160;(você deve usar “bleeding edge nightlies”) ou você [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3927:\"\n<p>O WordPress 5.0 Beta 4 já está disponível!</p>\n\n\n\n<p><strong>Esta versão ainda está em desenvolvimento,</strong> portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão.</p>\n\n\n\n<p>Existem duas formas de testar o WordPress 5.0 beta: com o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(você deve usar “bleeding edge nightlies”) ou você pode <a href=\"https://wordpress.org/wordpress-5.0-beta4.zip\">baixar a versão aqui</a>&nbsp;(zip).</p>\n\n\n\n<p><strong>A data de lançamento do WordPress 5.0 mudou</strong>. A nova data é&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">27 de novembro</a> e precisamos da sua ajuda para que isso aconteça. Aqui estão alguns ajustes importantes que fizemos desde o Beta 3:</p>\n\n\n\n<h2>Editor de blocos</h2>\n\n\n\n<p>O editor de blocos foi atualizado a partir da <a href=\"https://make.wordpress.org/core/2018/11/12/whats-new-in-gutenberg-12th-november/\">versão 4.3 do Gutenberg</a> e as maiores mudanças incluem:</p>\n\n\n\n<ul><li>Uma <a href=\"https://github.com/WordPress/gutenberg/pull/7718\">API de Anotações</a>, permitindo que plugins incluam dados contextuais enquanto você escreve.</li><li>Melhoria na consistência da navegação entre blocos feita pelo teclado, assim como ajustes nas diferentes áreas da interface.</li><li>Melhoria na acessibilidade, com marcações e itens para leitura de tela adicionais.</li></ul>\n\n\n\n<p>Além disso, foram corrigidos alguns erros que apareceram na versão beta 3:</p>\n\n\n\n<ul><li>Melhor suporte a plugins que fazem uso mais avançado das meta boxes.</li><li>Suporte a concatenação de scripts.</li><li>Chamadas ajax ocasionalmente causavam erros de PHP.</li></ul>\n\n\n\n<h2>Internacionalização</h2>\n\n\n\n<p>Adicionamos uma API para tradução de strings em arquivos JavaScript dos seus plugins e temas! E como o editor de bloco já está usando essa API, você também já pode começar a usá-la. Leia as <a href=\"https://make.wordpress.org/core/2018/11/09/new-javascript-i18n-support-in-wordpress/\">notas de desenvolvimento</a>&nbsp;para saber mais.</p>\n\n\n\n<h2>Twenty Nineteen (2019)</h2>\n\n\n\n<p>O Twenty Nineteen está sendo trabalhado no seu <a href=\"https://github.com/WordPress/twentynineteen\">repositório do GitHub</a>. Esta atualização contém&nbsp;<a href=\"https://core.trac.wordpress.org/changeset/43892\">vários ajustes</a>, incluindo:</p>\n\n\n\n<ul><li>Menus agora têm suporte apropriado a interações por toque e teclado.</li><li>Um menu de rodapé foi adicionado para links de páginas secundárias.</li><li>Melhoria na compatibilidade com versões anteriores do WordPress.</li></ul>\n\n\n\n<h2>Temas padrão</h2>\n\n\n\n<p>Todos os temas padrão mais antigos, do Twenty Ten até o Twenty Seventeen, tiveram seus estilos no editor de blocos melhorados.</p>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Você lê e escreve bem em inglês?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a>&nbsp;</p>\n\n\n\n<p><strong><em>Se acha que encontrou um erro</em></strong><em>, você pode publicá-lo na&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>área Alpha/Beta</em></a><em>&nbsp;do fórum oficial. Nós vamos adorar ouvir você! Se puder escrever um relatório de um erro que outras pessoas podem reproduzir,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>envie-o para o WordPress Trac (em inglês)</em></a><em>, onde você também pode encontrar&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>uma lista dos erros já conhecidos</em></a><em>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>Internacionali-<br>zação é uma palavra com<br>muitas sílabas.</em></p>\n\n\n\n<p><em>Meta boxes são<br>o estilo de bloco original<br>o velho é o novo de novo.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://br.wordpress.org/2018/11/13/wordpress-5-0-beta-4/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:45:\"\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:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2018/11/05/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:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://br.wordpress.org/2018/11/05/wordpress-5-0-beta-3/#respond\";s: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:09: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1359\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:379:\"O WordPress 5.0 Beta 3 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão. Existem duas formas de testar o WordPress 5.0 beta: com o plugin&#160;WordPress Beta Tester&#160;(você deve usar “bleeding edge nightlies”) ou você [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3417:\"\n<p>O WordPress 5.0 Beta 3 já está disponível!</p>\n\n\n\n<p><strong>Esta versão ainda está em desenvolvimento,</strong> portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão.</p>\n\n\n\n<p>Existem duas formas de testar o WordPress 5.0 beta: com o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(você deve usar “bleeding edge nightlies”) ou você pode <a href=\"https://wordpress.org/wordpress-5.0-beta3.zip\">baixar a versão aqui</a>&nbsp;(zip).</p>\n\n\n\n<p>O lançamento do WordPress 5.0 está previsto para&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">19 de novembro</a> e precisamos da sua ajuda para que isso aconteça. Aqui estão alguns ajustes importantes que fizemos desde o Beta 2:</p>\n\n\n\n<h2>Editor de blocos</h2>\n\n\n\n<p>O editor de blocos foi atualizado para incluir todos os recursos e ajustes da <a href=\"https://make.wordpress.org/core/2018/10/31/whats-new-in-gutenberg-31st-october-2/\">versão 4.2 do Gutenberg</a>. Além disso, existem alguns ajustes e recursos novos, como por exemplo:</p>\n\n\n\n<ul><li>Suporte ao meta box de &#8220;Campos personalizados&#8221;.</li><li>Melhoria na confiabilidade das solicitações à API REST.</li><li>Vários pequenos ajustes e melhorias.</li></ul>\n\n\n\n<h2>Twenty Nineteen (2019)</h2>\n\n\n\n<p>O Twenty Nineteen foi atualizado a partir de seu  <a href=\"https://github.com/WordPress/twentynineteen\">repositório no GitHub</a>. Você vai notar várias novidades nesta versão:</p>\n\n\n\n<ul><li>Adicionado suporte à atualização seletiva de widgets no Personalizar.</li><li>Adicionado suporte às mídias incorporadas responsivas.</li><li>Ajustes para melhorar a leitura e funcionalidades em dispositivos móveis.</li><li>Ajustes em blocos aninhados aparecendo mais largos do que deveriam.</li><li>Correção de erros em versões mais antigas do PHP e no IE11.</li></ul>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Ajude a tradução em Português! <a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a> </p>\n\n\n\n<p>Se você é fluente em inglês e se sente capaz de contribuir com código ou testes, nós temos <a href=\"https://make.wordpress.org/core/2018/11/02/upcoming-5-0-bug-scrubs/\">vários <em>bug scrubs</em></a> agendados para esta semana. Nós adoraríamos envolver o máximo de pessoas possível para termos certeza de que todos os erros informados receberam a devida atenção.</p>\n\n\n\n<p><strong><em>Se acha que encontrou um erro</em></strong><em>, você pode publicá-lo na </em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>área Alpha/Beta</em></a><em> do fórum oficial. Nós vamos adorar ouvir você! Se você puder escrever um relatório de um erro que outras pessoas podem reproduzir, </em><a href=\"https://make.wordpress.org/core/reports/\"><em>envie-o para o WordPress Trac (em inglês)</em></a><em>, onde você também pode encontrar </em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>uma lista dos erros já conhecidos</em></a><em>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>WordPress cinco ponto zero<br>chega daqui a duas semaninhas.<br>Agradecemos a sua ajuda!</em> <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f496.png\" alt=\"💖\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://br.wordpress.org/2018/11/05/wordpress-5-0-beta-3/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:36:\"\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.0 Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2018/11/01/wordpress-5-0-beta-2/\";s: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 12:23:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1355\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:381:\"O WordPress 5.0 Beta 2 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testá-la. Existem duas formas de testar o WordPress 5.0 beta: com o plugin&#160;WordPress Beta Tester&#160;(você deve usar “bleeding edge nightlies”) ou você pode baixar a [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2327:\"\n<p>O WordPress 5.0 Beta 2 já está disponível!</p>\n\n\n\n<p><strong>Esta versão ainda está em desenvolvimento,</strong> portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testá-la.</p>\n\n\n\n<p>Existem duas formas de testar o WordPress 5.0 beta: com o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(você deve usar “bleeding edge nightlies”) ou você pode <a href=\"https://wordpress.org/wordpress-5.0-beta2.zip\">baixar a versão aqui</a>&nbsp;(zip).</p>\n\n\n\n<p>O lançamento do WordPress 5.0 está previsto para&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">19 de novembro</a> e precisamos da sua ajuda para que isso aconteça. Aqui estão alguns ajustes importantes que fizemos desde o Beta 1:</p>\n\n\n\n<h2>Editor de blocos</h2>\n\n\n\n<p>Atualizamos o editor de blocos com a versão mais recente do plugin Gutenberg, que inclui a nova <a href=\"https://github.com/WordPress/gutenberg/pull/10209\">API de Formatos</a>, melhorias nas mídias incorporadas e <a href=\"https://github.com/WordPress/gutenberg/milestone/71\">uma variedade de ajustes</a>.</p>\n\n\n\n<p>Existiam alguns problemas com as meta boxes e elas não estavam aparecendo no editor de blocos, mas isso já foi corrigido.</p>\n\n\n\n<h2>Internacionalização</h2>\n\n\n\n<p>Adicionamos suporte ao <a href=\"https://core.trac.wordpress.org/ticket/45103\">registro e carregamento de tradução de arquivos JavaScript</a>.</p>\n\n\n\n<h2>Twenty Nineteen (2019)</h2>\n\n\n\n<p>O <a href=\"https://github.com/WordPress/twentynineteen\">repositório do Twenty Nineteen</a> está a pleno vapor. Uma série de pequenos erros foram corrigidos e foram feitas algumas adições importantes:</p>\n\n\n\n<ul><li>Agora há uma nova área de widgets no rodapé das páginas.</li><li>Submenus de navegação foram implementados para dispositivos móveis.</li><li>Foram adicionadas opções no Personalizar para alterar as cores do tema e filtros nas imagens destacadas.</li></ul>\n\n\n\n<h2>Todo o resto</h2>\n\n\n\n<p>A API REST teve alguns erros corrigidos e seu desempenho foi aprimorado. A compatibilidade com o PHP 7.3 também foi melhorada.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>Corrigindo os erros:<br>Todos os que você nos contou.<br>E alguns que encontramos também.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:45:\"\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:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.0 Beta 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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2018/10/27/wordpress-5-0-beta-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:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://br.wordpress.org/2018/10/27/wordpress-5-0-beta-1/#respond\";s: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, 27 Oct 2018 09:06: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"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:32:\"https://br.wordpress.org/?p=1352\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:346:\"O WordPress 5.0 Beta 1 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testá-la e, se você já está usando um site de testes, tenha certeza de atualizar o plugin Gutenberg para a versão 4.1. Existem duas formas [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Felipe Elia\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4033:\"\n<p>O WordPress 5.0 Beta 1 já está disponível!</p>\n\n\n\n<p><strong>Esta versão ainda está em desenvolvimento,</strong> portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testá-la e, se você já está usando um site de testes, tenha certeza de atualizar o plugin Gutenberg para a versão 4.1.</p>\n\n\n\n<p>Existem duas formas de testar o WordPress 5.0 beta: com o plugin&nbsp;<a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(você deve usar “bleeding edge nightlies”) ou você pode <a href=\"https://wordpress.org/wordpress-5.0-beta1.zip\">baixar a versão aqui</a>&nbsp;(zip).</p>\n\n\n\n<p>O lançamento do WordPress 5.0 está previsto para&nbsp;<a href=\"https://make.wordpress.org/core/5-0/\">19 de novembro</a> e precisamos da sua ajuda para que isso aconteça. Aqui estão alguns dos itens mais importantes para testar, de modo que possamos encontrar tantos erros quanto possível nas próximas semanas.</p>\n\n\n\n<h2>O editor de blocos</h2>\n\n\n\n<p>O novo editor de blocos Gutenberg agora será o editor de posts padrão!</p>\n\n\n\n<p>O editor de blocos fornece uma experiência de edição moderna e rica em mídias. Você pode criar conteúdos flexíveis e bonitos sem escrever uma linha de código ou você pode mergulhar nas <a href=\"https://wordpress.org/gutenberg/handbook/\">modernas APIs de programação</a> que o editor de blocos fornece.</p>\n\n\n\n<p>Mesmo antes de instalar o WordPress 5.0, você pode <a href=\"https://br.wordpress.org/gutenberg/\">testar o editor de blocos aqui</a>.</p>\n\n\n\n<p>Claro, sabemos que nem todo mundo está preparado para essa mudança ainda. Se esse for o seu caso, você pode instalar o <a href=\"https://br.wordpress.org/plugins/classic-editor/\">plugin Editor Clássico</a> agora, e ele manterá o editor com que você já está familiarizado como padrão, mesmo que você atualize para o WordPress 5.0.</p>\n\n\n\n<h2>Twenty Nineteen (2019)</h2>\n\n\n\n<p>Junto com o novo editor de blocos, temos um novo tema padrão, chamado Twenty Nineteen, que usufrui de todas as vantagens fornecidas pelo editor de blocos.</p>\n\n\n\n<p>Você pode saber mais sobre o Twenty Nineteen neste <a href=\"https://make.wordpress.org/core/2018/10/16/introducing-twenty-nineteen/\">post de apresentação</a> e acompanhar seu desenvolvimento através do <a href=\"https://github.com/WordPress/twentynineteen\">repositório no GitHub</a>.</p>\n\n\n\n<h2>Temas padrão</h2>\n\n\n\n<p>Claro, nós não poderíamos lançar uma nova e linda versão de um tema padrão e deixar todos os nossos temas antigos para trás. Atualizamos todos os temas desde o Twenty Ten, para que eles também fiquem bonitos no novo editor de blocos.</p>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p><a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o Português do Brasil!</a> <strong>Um problema já conhecido</strong>: o autocompletar dos blocos não funciona com nomes que contenham caracteres não-latinos. Adicionar blocos através do sinal de adição funciona e este erro já está corrigido na versão 4.1 do Gutenberg. <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\n\n\n<p><strong><em>Se acha que encontrou um erro</em></strong><em>, você pode publicá-lo na&nbsp;</em><a href=\"https://wordpress.org/support/forum/alphabeta\"><em>área Alpha/Beta</em></a><em>&nbsp;do fórum oficial. Nós vamos adorar ouvir você! Se você está apto a escrever um relatório de um erro que outras pessoas podem reproduzir,&nbsp;</em><a href=\"https://make.wordpress.org/core/reports/\"><em>envie-o para o WordPress Trac (em inglês)</em></a><em>, onde você também pode encontrar&nbsp;</em><a href=\"https://core.trac.wordpress.org/tickets/major\"><em>uma lista dos erros já conhecidos</em></a><em>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>Corrigindo erros pequenos<br>Indo de um por um<br>Você consegue mudar o mundo</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://br.wordpress.org/2018/10/27/wordpress-5-0-beta-1/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:48:\"\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:5:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"O WordCamp São Paulo está chegando!\";s:7:\"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://br.wordpress.org/2018/09/28/o-wordcamp-sao-paulo-esta-chegando/\";s: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:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://br.wordpress.org/2018/09/28/o-wordcamp-sao-paulo-esta-chegando/#respond\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 28 Sep 2018 12:49:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:9:\"WordCamps\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:10:\"são paulo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"WordCampSP\";s:7:\"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://br.wordpress.org/?p=1345\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:194:\"Não marque nada para o dia 13 de Outubro! O evento de WordPress mais tradicional do Brasil, o WordCamp São Paulo, vai acontecer na UNINOVE Vergueira das 8h às 18h e você não pode perder :-)\";s: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:\"Rafael Funchal\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:3274:\"\n<p>Não marque nada para o dia 13 de Outubro! O evento de WordPress mais tradicional do Brasil, o <a href=\"https://2018.saopaulo.wordcamp.org/\">WordCamp São Paulo</a>, vai acontecer na UNINOVE Vergueira das 8h às 18h e você não pode perder <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /></p>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"https://2018.saopaulo.wordcamp.org/\"><img src=\"https://br.wordpress.org/files/2018/09/Poster-WCSP-2018.jpg\" alt=\"WordCamp São Paulo 2018, dia 13 de Outubro na UNINOVE Vergueiro\" class=\"wp-image-1339\" srcset=\"https://br.wordpress.org/files/2018/09/Poster-WCSP-2018.jpg 1920w, https://br.wordpress.org/files/2018/09/Poster-WCSP-2018-300x169.jpg 300w, https://br.wordpress.org/files/2018/09/Poster-WCSP-2018-768x432.jpg 768w, https://br.wordpress.org/files/2018/09/Poster-WCSP-2018-1024x576.jpg 1024w\" sizes=\"(max-width: 1920px) 100vw, 1920px\" /></a></figure>\n\n\n\n<h2>O que é um WordCamp?</h2>\n\n\n\n<p>WordCamps são as conferências internacionais de WordPress organizadas pela comunidade de desenvolvedores, designers e usuários de WordPress ao redor do mundo.</p>\n\n\n\n<p>Os eventos são compostos por palestras, oficinas, troca de ideias e experiências em um ambiente informal. Não possui nenhum fim lucrativo e é organizado por voluntários para a comunidade local. Aceita qualquer tipo de participante, de qualquer área e nível e preza pelo aprendizado, integração e respeito.</p>\n\n\n\n<p>O primeiro WordCamp aconteceu em julho de 2006 nos Estados Unidos e o <a href=\"https://central.wordcamp.org/schedule/past-wordcamps/\">primeiro aqui no nosso país</a> aconteceu no dia 21 de junho de 2009, em São Paulo.</p>\n\n\n\n<h2>WordCamp São Paulo</h2>\n\n\n\n<p>Todo ano, desde 2012, São Paulo tem seu próprio WordCamp e recebe pessoas de todo país. Chegando a 450 participantes em uma das edições, com 24 palestras e 3 workshops, o evento é o lugar perfeito para saber mais sobre o WordPress e conhecer pessoas interessadas na ferramenta.</p>\n\n\n\n<h3>Como participar</h3>\n\n\n\n<p>Temos algumas formas de participar, veja abaixo em qual delas você se encaixa melhor:</p>\n\n\n\n<h4>Ingressos</h4>\n\n\n\n<p>O ingresso tem o valor de R$ 60 (pagamento feito através do PagSeguro)  e dá acesso a toda programação do evento.</p>\n\n\n\n<p>Além de ter acesso às palestras e workshops,  almoço (ou lanche) no local, brindes e a camiseta oficial do evento já estão incluídos no valor.</p>\n\n\n\n<p> O evento é bastante concorrido, então é melhor <a href=\"https://2018.saopaulo.wordcamp.org/ingressos/\">garantir logo o seu lugar</a>.</p>\n\n\n\n<h4>Patrocínio</h4>\n\n\n\n<p>Quer associar a sua marca a um evento tradicional, com visibilidade mundial e com vários patrocinadores internacionais? Veja nosso mídia kit, nossas cotas de patrocínio e preencha nosso <a href=\"https://2018.saopaulo.wordcamp.org/patrocine-o-wordcamp/\">formulário</a>.</p>\n\n\n\n<h4>Espalhando as novidades</h4>\n\n\n\n<p>Você também pode ajudar o evento compartilhando as novidades dele para seus amigos em suas redes. <strong>Não se esqueça de usar a hashtag #WordCampSP</strong> para que sua mensagem seja exibida <a href=\"https://2018.saopaulo.wordcamp.org/compartilhe/\">aqui</a>.</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:36:\"http://wellformedweb.org/CommentAPI/\";a:1:{s:10:\"commentRss\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://br.wordpress.org/2018/09/28/o-wordcamp-sao-paulo-esta-chegando/feed/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:38:\"http://purl.org/rss/1.0/modules/slash/\";a:1:{s:8:\"comments\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:35:\"https://br.wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"hourly\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:1:\"1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s: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:\"Wed, 12 Dec 2018 19:06:34 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 06 Sep 2017 19:17:40 GMT\";s:4:\"link\";s:61:\"<https://br.wordpress.org/wp-json/>; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20130911060210\";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(132, '_transient_timeout_feed_mod_b85365aa61afaf3d4189819a6f57c4c4', '1544684796', 'no'),
(133, '_transient_feed_mod_b85365aa61afaf3d4189819a6f57c4c4', '1544641596', 'no'),
(135, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1544684797', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(136, '_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:82:\"Post Status: Interview with Matt Mullenweg on Gutenberg, WordPress, and the future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=50403\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"https://poststatus.com/matt-mullenweg-on-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:2145:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast\">Google Play</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard.</p>\n<p>In this episode, I am joined by <a href=\"https://ma.tt\">Matt Mullenweg</a>, the co-founder of WordPress and CEO of Automattic.</p>\n<p>Just after releasing WordPress 5.0, and on the heels of WordCamp US, Matt and I review the event, the release, and discuss how he thinks things went, what could have gone better, and what he sees ahead.</p>\n<p>We also dig into WooCommerce, various plans around core development processes, Automattic, and more. I hope you enjoy. </p>\n<p></p>\n<p>And an audio version.</p>\n<p></p>\n<p>Full transcript is coming soon.</p>\n<h3>Episode Links</h3>\n<ul>\n<li><a href=\"https://ma.tt/\">Matt&#8217;s blog</a></li>\n<li><a href=\"https://automattic.com\">Automattic</a></li>\n<li>WordCamp US <a href=\"https://ma.tt/2018/12/state-of-the-word-2018/\">State of the Word</a></li>\n<li>Post Status&#8217;s <a href=\"https://poststatus.com/state-of-the-word-2018/\">coverage of WCUS</a></li>\n<li><a href=\"https://grief.com/the-five-stages-of-grief/\">5 Stages of Grief</a></li>\n</ul>\n<h3>Sponsor: iThemes</h3>\n<p><a href=\"https://ithemes.com/?utm_source=post_status&utm_medium=banner&utm_campaign=ps_ads\">iThemes</a> makes great WordPress plugins, themes and training to help take the guesswork out of building, maintaining and securing WordPress websites. I talk to iThemes CEO Cory Miller during the break to hear about what they are working on, and excited about for the coming year.</p>\n<p>Thanks to <a href=\"https://ithemes.com/?utm_source=post_status&utm_medium=banner&utm_campaign=ps_ads\">iThemes</a> for being a Post Status partner.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Dec 2018 14:45:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Brian Krogsgard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:69:\"WPTavern: State of the Word 2018: WordPress Embraces the Block Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=86291\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"https://wptavern.com/state-of-the-word-2018-wordpress-embraces-the-block-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:13933:\"<a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/12/PIC_20181208_161427272.jpeg?ssl=1\"><img /></a>photo credit: WP Tavern\n<p>WordCamp US kicked off in Nashville over the weekend, following the release of WordPress 5.0. In the first 48 hours, 5.0 had been downloaded more than 2.8 million times. It passed 3 million Saturday night.</p>\n<p>&#8220;There&#8217;s been a lot that&#8217;s been going on, so I&#8217;d like to allow WordPress the chance to re-introduce itself,&#8221; Matt Mullenweg said during the preamble of his <a href=\"https://www.youtube.com/watch?v=aWlfp-1Q19I\" rel=\"noopener\" target=\"_blank\">State of the Word</a> address. He invoked the four freedoms as the project&#8217;s constitution and called the community back to its roots. </p>\n<p>“It&#8217;s the reason we&#8217;re here,” Mullenweg said. “WordPress isn&#8217;t a physical thing; it&#8217;s not a set of code. It&#8217;s kind of an idea.  WordPress is backed by the full faith and credit of every person and company that depends on it.”  </p>\n<p>He reiterated the project’s mission to democratize publishing and recast his vision for advancing the open web.</p>\n<p>&#8220;Like I said a few years ago, we&#8217;re building a web operating system, an operating system for the open, independent web and a platform that others can truly build on,” Mullenweg said.</p>\n<p>WordPress’ 32.5% market share and its commercial ecosystem, which Mullenweg estimates at $10 billion/year,  give the project the resources to make a powerful impact on the future of the web. </p>\n<h3>Mullenweg Builds a Compelling Case for the Block Editor</h3>\n<a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/12/wcus-sotw.jpg?ssl=1\"><img /></a>photo credit: <a href=\"https://twitter.com/WordCampUS/status/1071531659579789313\">WCUS Photography Team</a>\n<p>Mullenweg drove home the necessity of Gutenberg by showing a selection of videos where new users struggled to accomplish simple tasks in the old editor.  Their experiences were accompanied by painful commentary:</p>\n<ul>\n<li>&#8220;This feels like writing a blog back in 2005.”</li>\n<li>&#8220;This was very finnicky; this does not work.”</li>\n<li>&#8220;How would I add a caption? I have no clue.”</li>\n</ul>\n<p>Mullenweg described how he used to effortlessly switch back and forth between the visual and HTML editors prior to WordPress 5.0 but realized that not all users are able to do this.  </p>\n<p>”This has been our editor experience for over a decade now and many of us have learned to deal with it,” he said.</p>\n<p>He followed up with a video demonstrating how much easier these tasks are in the new block editor and identified blocks as the way forward for WordPress.</p>\n<p>Some attendees commented after the fact on how the user testing videos, paired up against an expert using Gutenberg, seemed unbalanced and they would have liked to see videos of new users attempting the same tasks in the new editor. The goal of that segment, however, seemed to be more aimed at communicating the need for Gutenberg and the possibilities it opens up once users have had the chance to grow into it.</p>\n<h3>Mullenweg Urges Attendees to &#8220;Learn Blocks Deeply&#8221;</h3>\n<p>Millions of early adopters have already embraced the block editor during phase 1 of the Gutenberg project, which closed out with 1.2 million active installs and 1.2 million posts written. There have already been 277 WordCamp talks on Gutenberg, 555 meetup events focused on the new editor, and more than 1,000 blog posts discussing it.</p>\n<p>Blocks are taking over the world of WordPress. Version 5.0 shipped with 70 native blocks and there are already more than 100 third-party blocks in existence and 1,000 configurations related to that. </p>\n<p>“Blocks are predictable, tactile, and can be simple like a text block, or as rich as an e-commerce interface,” Mullenweg said. He described them as the new DNA of WordPress, from which users can create anything they can imagine. </p>\n<p>Mullenweg showcased two sites built using the block editor, the <a href=\"https://theindigomill.com/\" rel=\"noopener\" target=\"_blank\">Indigo Mill</a> and <a href=\"https://www.luminasolar.com/\" rel=\"noopener\" target=\"_blank\">Lumina Solar</a>. These beautiful sites open the imagination to what Gutenberg is capable of bringing to websites.</p>\n<p>WordPress.org will be highlighting plugins and themes to push the block ecosystem forward. There are also more than 100 Gutenberg-ready themes available to users on the directory and <a href=\"https://wordpress.org/plugins/browse/blocks/\" rel=\"noopener\" target=\"_blank\">a new Gutenberg block tag that is currently live for plugins</a>. It will also be available for themes soon. </p>\n<p>Mullenweg highlighted tools like the create-guten-block toolkit, Block Lab, and Lazy Blocks that are making it easy for developers to create their own blocks. Block collections and libraries are also emerging. He said one of the priorities for 2019 is to build a WordPress.org directory for discovering blocks and a way to seamlessly install them.</p>\n<p>Building on the homework he gave to WordPress developers in 2015, to “<a href=\"https://wptavern.com/state-of-the-word-2015-javascript-and-api-driven-interfaces-are-the-future-of-wordpress\" rel=\"noopener\" target=\"_blank\">Learn JavaScript Deeply</a>,” Mullenweg urged the community to “Learn Blocks Deeply.”  Blocks provide a host of opportunities to improve the user experience beyond what Gutenberg’s creators could have imagined in the beginning.</p>\n<h3>Gutenberg Phase 2: Navigation Menu Block, Widget blocks, Theme Content Areas</h3>\n<p>Mullenweg announced the next phases for the Gutenberg project. Phase 2 has already begun and focuses on site customization, expanding the block interface to other aspects of content management.  This includes creating a navigation menu block. Reimagining menus is will be challenging, and Mullenweg said they may even get renamed during the process.</p>\n<p>Phase 2 goals also include porting all widgets over to blocks and registering theme content areas in Gutenberg. An early version of phase 2 will be in the Gutenberg plugin so anyone wanting to be part of testing can reactivate it.</p>\n<p>During the Q&#038;A time, one attendee asked a question about how this phase seems to include very little about making layout capabilities more robust. He asked if Mullenweg plans to let those the marketplace handle those layout decision or if core will define a layout language. Mullenweg responded that it may be more prudent to see what others in the ecosystem are doing and cherry pick and adopt the best solutions. He also remarked that it would be exciting if users could switch between different page builders in the future and not lose their content. </p>\n<h3>Gutenberg Phases 3 and 4: Collaboration and Core Support for Multilingual Sites</h3>\n<p>Mullenweg announced that Gutenberg phase 3, targeted for 2020, will focus on collaboration, multi-user editing, and workflows. Phase 4 (2020+) is aimed at developing an official way for WordPress to support multilingual sites. When asked what that will look like from a technical standpoint, given the many existing solutions already available, Mullenweg said he didn’t want to prescribe anything yet, as it’s still in the experimental stage.</p>\n<p>Other major announcements included a highly anticipated bump in the minimum PHP version required for using WordPress. By April 2019, PHP 5.6 will be the minimum PHP version for WordPress, and by December 2019, the requirement will be updated to PHP 7.</p>\n<p>WordPress releases are going to come faster in the future, as Gutenberg development has set a new pace for iteration. Mullenweg said he would like WordPress to get to the point where users are not thinking about what version they are on but instead choose a channel where they can easily run betas or the stable version.</p>\n<h3>Mullenweg Acknowledges Mistakes Made and Lessons Learned in the 5.0 Release Process</h3>\n<p>WordPress 5.0 was one of the longest and most controversial release cycles in the project’s history. Those outside the inner circle of decision-making endured a great deal of uncertainty, as dates were announced and then missed, with secondary dates thrown out in favor of pushing 5.0 out with just three days’ notice. </p>\n<p>“We were scared to announce a new release date after missing our previous one,” Mullenweg said, acknowledging the controversial release date. He said this seemed to create a lot of fear and uncertainty until they announced a new date. The dates seemed to come out of the blue and were stressful for the community. </p>\n<p>Mullenweg highlighted the lessons they learned in the process of releasing 5.0: </p>\n<ul>\n<li>Need the various teams across WordPress working together better</li>\n<li>Need to keep learning JavaScript, even more deeply</li>\n<li>Importance of triage and code freezes</li>\n<li>Always announce release dates</li>\n</ul>\n<p>Mullenweg noted that WordPress 5.0’s beta releases were tested 100 times more than other releases, which he said contributed to Gutenberg becoming more robust before landing in 5.0. However, these positives seemed to be overshadowed by several critical breakdowns in communication that many feel betrayed the community’s trust.</p>\n<p>He noted that people used the plugin review system as a way to vote on Gutenberg and that perhaps the community needs a different medium for expressing those kinds of things. Users did this because they felt it was one of the only feedback mechanisms where they had a voice. Negative reviews piled on in the early days of the plugin’s development but they continued steadily throughout the feature plugin’s journey into core. After 5.0 was released, negative <a href=\"https://wordpress.org/support/plugin/gutenberg/reviews/\" rel=\"noopener\" target=\"_blank\">reviews on the Gutenberg plugin</a> have continued to pour in, and its rating has fallen to 2.2/5 stars.</p>\n<h3>Growing Pains and a Call for Transparency</h3>\n<a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/12/wcus2018.jpg?ssl=1\"><img /></a>photo credit: David Bisset for <a href=\"https://poststatus.com/\">Post Status</a>\n<p>Mullenweg said that Gutenberg development happened entirely in the public eye, surfacing many challenges associated with developing open source software in public. The code was public, but the most important decisions were made behind closed doors. This was compounded by the developer community voicing frustrations during core dev chats and on social media. </p>\n<p>During the Q&#038;A segment, several audience members called for more transparency in the release process, noting that most of the posts and announcements regarding 5.0 came from Automattic employees. Morten Rand-Hendriksen, who has become somewhat of a community firebrand at WordCamp Q&#038;A’s, received applause for his question regarding the use of the word “we” in connection to posts on the make blogs. He pressed Mullenweg for more insight into where these decisions are made. </p>\n<p>Mullenweg said the “we” he meant in regards to 5.0 release dates referred to a private channel where the release leads discussed it. He said with so many people showing up to the dev chats, the discussions became difficult.</p>\n<p>&#8220;I don&#8217;t just go in a cave and come up with these things,&#8221; Mullenweg said. “A lot of people were showing up [to dev chats] who had never contributed to WordPress before and were crowding out the discussion of the core team.” He also said the private conversations were “every bit as feisty as the public one,” except there weren’t any drive-by opinions. </p>\n<p>To those on the outside, these meetings appeared to be secret, as they were never referenced or summarized on the make blogs. This left the developmer community wondering where these decisions were coming from and whether or not they had a voice.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Gutenberg was developed in public, but too many decisions were made in silos and not clearly communicated. This can be improved for 5.1 and beyond <a href=\"https://twitter.com/hashtag/WCUS?src=hash&ref_src=twsrc%5Etfw\">#WCUS</a></p>\n<p>&mdash; K. Adam White (@kadamwhite) <a href=\"https://twitter.com/kadamwhite/status/1071539824358764544?ref_src=twsrc%5Etfw\">December 8, 2018</a></p></blockquote>\n<p></p>\n<p>During the Q&#038;A, Mulllenweg said he listened to vigorous discussion and diverse viewpoints from release leads coming from different companies, while gathering as much information as possible from reading reviews, blog posts, and comments from the community. He described this process as part of the art of trying to make sense of all the different things people are saying and balance that.</p>\n<p>Supporting a BDFL-led project requires a certain amount of trust that the leadership is listening. Over the past several weeks Mullenweg has made a strong effort to <a href=\"https://wptavern.com/mullenweg-ramps-up-communication-ahead-of-wordpress-5-0-release-rc2-now-available\" rel=\"noopener\" target=\"_blank\">keep the channels of communication open</a>.  </p>\n<p>The painful user testing videos Mullenweg shared demonstrated how desperately WordPress needed to grow out of its old editor. It isn’t often that core makes changes that affect nearly every corner of the WordPress ecosystem at the same time. This experience came with its fair share of growing pains. Despite communication missteps during the 5.0 release process, Mullenweg has successfully navigated the project through this rocky transition. Although WordCamp US attendees seemed road weary after 5.0, they were united by a shared desire to move forward and continue working together with the leadership that has kept WordPress on the course of growth and improvement for the past 15 years.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Dec 2018 16:23: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: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:28:\"Matt: State of the Word 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:22:\"https://ma.tt/?p=48685\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"https://ma.tt/2018/12/state-of-the-word-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:1048:\"<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Over the weekend I was in Nashville with over a thousand other WordPress enthusiasts. I met a ton of people, learned a lot, and was able to share the annual State of the Word address with the audience, which is a big summary of what WordPress has been up to and where it&#8217;s going. This year we covered user testing, Gutenberg, 5.0, the future phases of Gutenberg, all the latest and greatest blocks, new minimum PHP requirements, the adoption of 5.0, and some event and community updates. You can also <a href=\"https://www.slideshare.net/photomatt/wordpress-state-of-the-word-2018\">see just the slides</a>. The <a href=\"https://www.youtube.com/watch?v=v2aNNlC8TUE\">Q&amp;A is here in a separate video</a>.</p>\n\n\n\n<p>If you&#8217;d like a text summary and commentary on the speech, <a href=\"https://poststatus.com/state-of-the-word-2018/\">Post Status</a> and <a href=\"https://wptavern.com/state-of-the-word-2018-wordpress-embraces-the-block-editor\">WP Tavern</a> both have good write-ups.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Dec 2018 05:00: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: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: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:55:\"Post Status: Matt Mullenweg’s State of The Word, 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:58:\"https://poststatus.com/?post_type=poststatus_notes&p=49929\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"https://poststatus.com/state-of-the-word-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:8395:\"<p>Matt started by “reintroducing WordPress” and the four freedoms, stressing that “WordPress isn&#8217;t a physical thing or code, it&#8217;s an idea.” Additionally, a “robust commercial ecosystem” supports WordPress, and Matt noted that current estimates indicate WordPress generates about $10 Billion (USD) annually.</p>\n<p>After two years of development and just after WordPress 5.0 officially launched, it&#8217;s not surprising the focus of Matt&#8217;s talk was on Gutenberg. “We&#8217;ve gotten a lot of questions about why we are doing certain things&#8230; why we are working on Gutenberg. And it&#8217;s good to return to users to find that,” Matt acknowledged.</p>\n<h3>Enhancing editor usability</h3>\n<p>A video of new WordPress users testing the classic editor (WordPress 4.9) was shown projected on the big screens over the stage. These clips primarily showed people having difficulties with relatively simple tasks in the editor.</p>\n<p>Matt&#8217;s point was that we&#8217;ve become accustomed to the custom editor&#8217;s quirks, but blocks offer a better experience — from copying and pasting from Microsoft Word and Google Docs into WordPress to quickly creating a responsive website.</p>\n<h3>Community Gutenberg adoption</h3>\n<p>Matt continued with a summary of how Gutenberg has performed in Phase 1 of its release. Before the WordPress 5.0 release, 1.2 million active installs and 1.2 million posts were published, with about 39,000 posts written daily. Phase 1 had 8,684 commits and over 340 contributors. The &#8216;Gutenberg&#8217; tag is already available for plugins in the WordPress repo, and it will be “coming soon” for themes.</p>\n<p>Notably, over 100 Gutenberg themes are already present in the WordPress repo — including the new Twenty Nineteen theme. Matt highlighted two websites — <a href=\"http://theindigomill.com\">The Indigo Mill</a> and <a href=\"http://luminasolar.com\">Lumina Solar</a> — as examples where Gutenberg blocks have been used well to create effective layouts. Matt riffed on the &#8220;Learn JavaScript Deeply&#8221; mantra by repeating &#8220;Learn Blocks Deeply.&#8221; Blocks are the DNA of the new editor. Currently, 70 native blocks and over 100 third-party blocks exist for Gutenberg.</p>\n<h3>Community Gutenberg development</h3>\n<p>He highlighted some of the third party blocks in the wild:</p>\n<ul>\n<li><a href=\"https://yoast.com/yoast-seo-8-0-introducing-the-yoast-seo-gutenberg-sidebar-a-revamped-meta-box/\">Yoast SEO</a></li>\n<li><a href=\"https://github.com/kevinbazira/algori-360-image\">360 Image</a></li>\n<li><a href=\"https://www.ampproject.org/latest/blog/the-official-amp-plugin-for-wordpress/\">Google AMP w/ Gutenberg Integration</a></li>\n<li><a href=\"https://wordpress.org/plugins/dropit/\">Drop It</a></li>\n<li><a href=\"https://wordpress.org/plugins/ecwid-shopping-cart/\">Ecwid Ecommerce Shopping Cart</a></li>\n<li><a href=\"https://woocommerce.com/posts/making-it-easier-to-add-products-to-posts-and-pages-with-the-products-block-for-gutenberg/\">WooCommerce Products Block</a></li>\n<li><a href=\"https://www.bigcommerce.com/wordpress-ecommerce-plugin/\">BigCommerce</a></li>\n<li><a href=\"https://www.wpzoom.com/plugins/new-plugin-released-recipe-card-blocks-for-gutenberg/\">Recipe Card Blocks</a></li>\n<li><a href=\"https://wordpress.org/plugins/tarot/\">Tarot</a></li>\n<li><a href=\"https://twitter.com/dmsnell23/status/1063126946350096389\">Sketch Block</a></li>\n<li><a href=\"https://jetpack.com/support/jetpack-blocks/form-block/\">Jetpack Form Block</a></li>\n<li><a>Guidepost</a></li>\n<li><a href=\"https://sortabrilliant.com/ghostwriter/\">Ghost Writing</a></li>\n<li><a href=\"https://sortabrilliant.com/spoileralert/\">Spoiler Alert</a></li>\n<li><a href=\"https://wordpress.org/plugins/caxton/\">Caxton Shape Divider Block</a></li>\n</ul>\n<p>Matt mentioned several block libraries and frameworks that have appeared:</p>\n<ul>\n<li><a href=\"http://editorblockswp.com\">editorblockswp.com</a></li>\n<li><a href=\"http://gutenberghub.com\">gutenberghub.com</a></li>\n<li><a href=\"http://gutenbergcloud.org\">gutenbergcloud.org</a></li>\n<li><a href=\"https://getblocklab.com\">getblocklab.com</a></li>\n<li><a href=\"https://wordpress.org/plugins/lazy-blocks/\">Lazy Blocks</a></li>\n</ul>\n<h3>Mobile Apps</h3>\n<p>Matt gave the audience an update regarding the WordPress native mobile apps: In the past month, app users published 1.3M posts and uploaded 3.1M photos and videos. Gutenberg will be going into the mobile apps, with a beta release expected in February 2019; I heard February 22nd is the current target date for a beta release.</p>\n<h3>The Next Phases of Gutenberg</h3>\n<p>Matt highlighted the next phases of Gutenberg&#8217;s evolution, which included new information about Phases Three and Four:</p>\n<h4>Phase One</h4>\n<p>Fundamental blocks for writing and editing in the backend editor. These are complete now, although Matt later said that work on the editor would continue.</p>\n<h4>Phase Two</h4>\n<p>Customizing outside of the page/post content will be the next point of emphasis. It may include widgets, menus, and miscellaneous content. Matt notes that menus “will need a bit more experimentation”. &#8220;2019&#8221;.</p>\n<h4>Phase Three</h4>\n<p>Collaboration, multi-user editing in Gutenberg, and workflows. The target for this to phase to be complete is “2020+.”</p>\n<h4>Phase Four</h4>\n<p>&#8220;An official way&#8221; for WordPress to support multilingual sites. Also slated for “2020+.”</p>\n<h3>Other Announcements</h3>\n<p>There were several non-Gutenberg tidbits of note:</p>\n<h4>Auto updates on major versions of WordPress</h4>\n<p>On a list of items to work on in 2019, Matt said he wanted to make it a goal to add optional auto-updates for plugins, themes, and major versions of WordPress.</p>\n<h4>Updated minimum PHP versions</h4>\n<p><a href=\"https://make.wordpress.org/core/2018/12/08/updating-the-minimum-php-version/\">A proposal written</a> by Gary Pendergast makes a case for WordPress to start updating its minimum PHP versions. The proposed plan is to move to PHP 5.6 by April 2019 and to PHP 7.0 by &#8220;as early as&#8221; December 2019. Notably, security support for PHP 5.6 expires in a few days, and the &#8220;end of life&#8221; for PHP 7.0 <a href=\"http://php.net/supported-versions.php\">just passed</a>.</p>\n<p>After Matt mentioned this proposal, it received an enormous amount of applause — far more applause than most of the Gutenberg news that came earlier, and Matt noticed. It is definitely welcome news!</p>\n<h4>WordPress release adoption</h4>\n<p>During the life of the WordPress 4.9 branch, there were over 173 million downloads with 68.4% of all known WordPress installs running 4.9.</p>\n<p>Matt notes that the early adoption numbers for WordPress 5.0 were very similar to WordPress 4.7, which was also a December release back in 2016.</p>\n<h4>Lessons learned in 2018</h4>\n<p>Matt took time to summarize the lessons he learned in 2018, starting with the need for teams to improve how they work together: “There should be no reason for accessibility, testing, and other teams not to be working together since these features should be a feature of everything we develop from the very beginning.” No doubt this came as a response to the concerns about accessibility in Gutenberg that surfaced before WordPress 5.0 was released.</p>\n<h3>Community Update</h3>\n<p>Matt offered some community-related data as well:</p>\n<ul>\n<li><strong>WordCamps:</strong> In 2018 there were 145 WordCamps in 48 countries, with over 45,000 tickets sold. A total of 1,300 organizers (a 33% increase!), 2,651 speakers, and 1,175 sponsors made it all possible.</li>\n<li><strong>Meetups:</strong> This year saw 50% member growth in meetup attendance, with over 687 meetup groups and 5,400 meetup events.</li>\n</ul>\n<p>And with that, he began Q&amp;A.</p>\n<p>You can view the <a href=\"https://www.youtube.com/watch?v=r5b-N2RmxS8\">State of the Word on YouTube</a> in full, and it should become available on WordPress TV very soon.</p>\n<div id=\"attachment_49969\" class=\"wp-caption aligncenter\"><img class=\"wp-image-49969 size-large\" src=\"https://cdn.poststatus.com/wp-content/uploads/2018/12/wcus-2018-sotw-5542-752x439.jpg\" alt=\"\" width=\"752\" height=\"439\" /><p class=\"wp-caption-text\">Photos by <a href=\"https://wpsessions.com\">Brian Richards</a>, for Post Status.</p></div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 10 Dec 2018 15:45: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:\"David Bisset\";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:93:\"WPTavern: AMP Plugin for WordPress Version 1.0 Introduces Gutenberg-Integrated AMP Validation\";s:7:\"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=86248\";s:7:\"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:104:\"https://wptavern.com/amp-plugin-for-wordpress-version-1-0-introduces-gutenberg-integrated-amp-validation\";s: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:2620:\"<p><a href=\"https://amp-wp.org/amp-plugin-1-0-stable-release/\" rel=\"noopener\" target=\"_blank\">Version 1.0</a> of the official AMP plugin for WordPress was released on the eve of WordCamp US, after two years in development by contributors from Automattic, XWP, and Google. This first stable version has a massive <a href=\"https://wordpress.org/plugins/amp/#developers\" rel=\"noopener\" target=\"_blank\">changelog</a> with 30 people credited for their contributions. The plugin is now considered ready for production and is active on more than 300,000 sites.</p>\n<p>Version 1.0 interfaces with the new editor that landed in WordPress 5.0. It will display warnings for AMP-invalid markup on a per-block basis, so users don&#8217;t have to guess what content is generating an issue.</p>\n<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/12/notices-in-blocks-1024x736.png?ssl=1\"><img /></a></p>\n<p>This release also introduces a compatibility tool that offers detailed information on AMP validation errors. It functions like a debugging page where users can see which URLs are generating errors, along with the site component (plugin, theme, or core) where the markup originates.</p>\n<p>Version 1.0 includes granular controls for selecting which templates will be served as AMP. This allows for a more gradual adoption across a site. Users can also opt for Native mode to have the entire site served as AMP.</p>\n<p>The plugin has been updated to support four of WordPress&#8217; default themes, including Twenty Fifteen, Twenty Sixteen, Twenty Seventeen, and Twenty Nineteen. The documentation for <a href=\"https://github.com/xwp/wordpress-develop/pull/307\" rel=\"noopener\" target=\"_blank\">how AMP was added to these bundled themes</a> serves as an example for how theme developers can make their own themes AMP-compatible. </p>\n<p>WordPress users who opt to use AMP on their sites will have a more successful experience with this version, thanks to the improved UI for handling AMP validation errors and the new interface for limiting AMP-support to certain templates.</p>\n<p>The AMP for WordPress project is also sporting a new <a href=\"https://amp-wp.org/\" rel=\"noopener\" target=\"_blank\">website</a> that features a collection of AMP-ready plugins and themes and a showcase of sites using AMP. It also has extensive <a href=\"https://amp-wp.org/documentation/getting-started/\" rel=\"noopener\" target=\"_blank\">documentation</a> for implementors, site owners, and developers. The site provides a central place for news and resources related to the project and its expanding ecosystem of compatible extensions.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Dec 2018 06:51: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: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:90:\"WPTavern: WordPress 5.0 “Bebo” Released, Lays A Foundation for the Platform’s Future\";s:7:\"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=86229\";s:7:\"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/wordpress-5-0-bebo-released-lays-a-foundation-for-the-platforms-future\";s: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:9407:\"<p>In 2016 at WordCamp US in Philadelphia, PA, <a href=\"https://wptavern.com/state-of-the-word-2016-mullenweg-pushes-calypso-as-future-of-wordpress-interface-proposes-major-changes-to-release-cycle\">Matt Mullenweg announced</a> to the world that a new post and page editor would be coming to WordPress. &#8220;The editor does not represent the core of WordPress publishing,&#8221; Mullenweg said.</p>\n\n\n\n<p>His <a href=\"https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/\">vision of the editor</a> was geared towards a more block-based approach that unifies widgets, shortcodes, and other areas of WordPress. Today, that vision has become a reality with the <a href=\"https://wordpress.org/news/2018/12/bebo/\">release of WordPress 5.0</a> featuring <a href=\"https://matiasventura.com/post/gutenberg-or-the-ship-of-theseus/\">project Gutenberg</a>. <br /></p>\n\n\n\n<div class=\"wp-block-image\"><img />The New Editor in WordPress 5.0</div>\n\n\n\n<p>Instead of a large blank canvas, content is broken up into a series of individual blocks that are independent from the content as a whole. For example, you can edit the HTML of one block without it affecting other blocks. </p>\n\n\n\n<p>The editor comes with more than 16 blocks to add content. You can add more blocks by <a href=\"https://wptavern.com/gutenberg-block-library-provides-a-searchable-index-of-individual-blocks\">installing and activating plugins.</a><br /></p>\n\n\n\n<div class=\"wp-block-image\"><img />Some of the Blocks That Are Available in WordPress 5.0</div>\n\n\n\n<p>Each block typically has two areas where you can manipulate its content. The Toolbar, which displays when hovering over a block, and the Inspector located in the right-hand sidebar. The Inspector houses less-often used settings that require more screen space. <br /></p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Between the top toolbar, block toolbar, inspector, block mover, and hidden elements that don&#8217;t appear unless hovered over, there are a lot of user interface buttons. I suggest spending time crafting a test post to get familiar with what each button does. </p>\n\n\n\n<p>To see the new editor in action, check out the following demo video. </p>\n\n\n\nA Short Demo of The New Editor in Action\n\n\n\n<p>If you&#8217;re not ready for the new editor or discover incompatibilities with themes or plugins, you can install the <a href=\"https://wordpress.org/plugins/classic-editor/\">Classic Editor</a> plugin. This plugin will disable the new editor and replace it with the one in WordPress 4.9.8 and below. The WordPress development team <a href=\"https://make.wordpress.org/core/2018/11/07/classic-editor-plugin-support-window/\">has committed</a> to supporting the plugin until December 31st, 2021. </p>\n\n\n\n<p>Those who use assistive technology and experience accessibility issues with the new editor are encouraged to install the Classic Editor plugin until the issues are fixed. <br /></p>\n\n\n\n<h2>Twenty Nineteen: A Fully Compatible Default Theme<br /></h2>\n\n\n\n<p>WordPress 5.0 comes with a new default theme called <a href=\"https://make.wordpress.org/core/2018/10/16/introducing-twenty-nineteen/\">Twenty Nineteen</a> that is fully compatible with the new editor. It includes front-end and back-end styles to provide a What You See Is What You Get experience. It also supports the Wide and Full image alignment options. <br /></p>\n\n\n\n<div class=\"wp-block-image\"><img />Twenty Nineteen Front-End on the Left, Back-End on the Right</div>\n\n\n\n<p>You can see the theme in action on <a href=\"https://ma.tt/\">Matt Mullenweg&#8217;s site</a>.</p>\n\n\n\n<h2>What Happens to Existing Content?<br /></h2>\n\n\n\n<p>Content not created in the new editor is placed into a Classic block. This block mimics the old editor and provides users a choice to migrate it into blocks. However, migrating content into blocks is not required. Most content shouldn&#8217;t be affected by updating to WordPress 5.0. </p>\n\n\n\n<h2>Where to Get Help Using the New Editor</h2>\n\n\n\n<p>For new users, the editor might be an intuitive experience but for many WordPress veterans, it introduces a steep learning curve. After all, the previous editor has existed for more than 10 years. </p>\n\n\n\n<p>At the moment, there is a Gutenberg handbook for <a href=\"https://wordpress.org/gutenberg/handbook/designers-developers/\">Developers</a> and <a href=\"https://wordpress.org/gutenberg/handbook/contributors/\">Contributors</a> but not for Users. Work <a href=\"https://github.com/WordPress/gutenberg/issues/11252\">is underway</a> by the Docs team and other volunteer contributors to put together an initial document to release in 2019. </p>\n\n\n\n<p>Until the official handbook is published, you&#8217;ll need to seek help and education elsewhere.</p>\n\n\n\n<h3>WordPress 5.0 Essential Training</h3>\n\n\n\n<p>Morten Rand-Hendriksen, an educator for LinkedIn Learning has published <a href=\"https://www.linkedin.com/learning/wordpress-5-essential-training/?trk=insiders_23476852_learning\">a course</a> that walks users through the new editor. It&#8217;s available to view for free for the next three weeks. </p>\n\n\n\n<h3>Gutenberg Times<br /></h3>\n\n\n\n<p>Birgit Pauli-Haack has been keeping tabs on Gutenberg&#8217;s development for more than a year. <a href=\"https://gutenbergtimes.com\">Gutenberg Times</a> contains relevant information about the editor for <a href=\"https://gutenbergtimes.com/category/for-users/\">users</a> and <a href=\"https://gutenbergtimes.com/category/for-developers/\">developers</a>. </p>\n\n\n\n<h3>WordPress Support Forums<br /></h3>\n\n\n\n<p>Volunteers are standing by ready to answer your questions. If you think you&#8217;ve discovered a bug, incompatibility, or are experiencing trouble with the new editor, please post it in the <a href=\"https://wordpress.org/support/forum/how-to-and-troubleshooting/\">support forums</a>. </p>\n\n\n\n<h3>WordPress 5.0 Field Guide</h3>\n\n\n\n<p>The <a href=\"https://make.wordpress.org/core/2018/12/06/wordpress-5-0-field-guide/\">WordPress 5.0 field guide</a> provides important links and information for developers and users related to this release. <br /></p>\n\n\n\n<h2>WordPress 5.0 Is the Beginning of A New Journey</h2>\n\n\n\n<p>While WordPress 5.0 introduces a new editor, it also lays the foundation for what&#8217;s to come. The first phase of project Gutenberg was the editor. The second phase is the Customizer with a focus on full-site layouts. The third and fourth phases will be shared and discussed by Mullenweg at this year&#8217;s WordCamp US.</p>\n\n\n\n<p>The new editor is part of a long process to reinvent WordPress. Matías Ventura, Co-lead of the Gutenberg project succinctly explains why the need for Gutenberg exists. <br /></p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>WordPress has always been about the user experience, and that needs to continue to evolve under newer demands. Gutenberg is an attempt at fundamentally addressing those needs, based on the idea of content blocks. 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><p>How can such a vision happen without dismantling, rebuilding, fragmenting, or breaking the WordPress ship that for over a decade has been carrying the thoughts, joys, and livelihoods of millions of people and more than a quarter of the web?</p><p>The ship, like Theseus’, needs to continue sailing while we upgrade the materials that make it. It needs to adapt to welcome new people, those that find it too rough to climb on board, too slippery a surface, too unwelcoming a sight, while retaining its essence of liberty. This is not an easy challenge—not in the slightest. </p><p>Indeed, <a href=\"https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/\">we called it Gutenberg for a reason</a>, for both its challenges and opportunities, for what it can represent in terms of continuity and change. It is an ambitious project and it needs the whole WordPress community to succeed.</p><cite><a href=\"https://matiasventura.com/post/gutenberg-or-the-ship-of-theseus/\">Matías Ventura, Co-lead of the Gutenberg project.<br /></a></cite></blockquote>\n\n\n\n<p>As the new editor <a href=\"https://wordpress.org/download/counter/\">makes its way</a> across the world, it will be interesting to see what the reactions are from users who experience it for the first time. It will also be interesting to see what the <a href=\"https://twitter.com/photomatt/status/1069327043618320385\">developer community builds</a> that takes the editor to new heights. </p>\n\n\n\n<p>WordPress 5.0 is the <a href=\"https://www.linkedin.com/pulse/gutenberg-morten-rand-hendriksen\">beginning of a new journey</a> for the project. One that will have bumpy roads, new discoveries, and plenty of opportunities to learn. So saddle up and keep your hands and arms inside the vehicle until it makes a complete stop. <br /></p>\n\n\n\n<p>WordPress 5.0 is named after <a href=\"https://en.wikipedia.org/wiki/Bebo_Vald%C3%A9s\">Bebo Valdés</a> who was a Cuban pianist, bandleader, composer and arranger. The release was led by Matt Mullenweg with Allan Cole, Anthony Burchell, Gary Pendergast, Josepha Haden Chomphosy, Laurel Fulford, Omar Reiss, Daniel Bachhuber, Matías Ventura, Miguel Fonseca, Tammie Lister, Matthew Riley MacPherson as co-leads. At least 423 people contributed to the release. <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, 06 Dec 2018 21:38: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:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"Dev Blog: WordPress 5.0 “Bebo”\";s:7:\"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=6328\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/news/2018/12/bebo/\";s: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:42239:\"<h2>Say Hello to the New Editor</h2>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>We’ve made some big upgrades to the editor. Our new block-based editor 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<div class=\"wp-block-image\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Gutenberg.jpg?fit=2400%2C1200&ssl=1\" alt=\"\" class=\"wp-image-6331\" /></div>\n\n\n\n<h2>Building with Blocks</h2>\n\n\n\n<p>The new block-based editor won’t change the way any of your content looks to your visitors. What it will do is let you insert any type of multimedia in a snap and rearrange to your heart’s content. Each piece of content will be in its own block; a distinct wrapper for easy maneuvering. If you’re more of an HTML and CSS sort of person, then the blocks won’t stand in your way. WordPress is here to simplify the process, not the outcome.</p>\n\n\n\n\n\n\n\n<p>We have tons of blocks available by default, and more get added by the community every day. Here are a few of the blocks to help you get started:</p>\n\n\n\n<ul class=\"wp-block-gallery columns-4 is-cropped\"><li class=\"blocks-gallery-item\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Paragraph.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6340\" />Paragraph</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Heading.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6341\" />Heading</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Preformatted.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6342\" />Preformatted</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Quote.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6343\" />Quote</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Image.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6344\" />Image</li><li class=\"blocks-gallery-item\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Gallery.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6345\" />Gallery</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Cover-Image.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6346\" />Cover</li><li class=\"blocks-gallery-item\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Video.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6347\" />Video</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Audio.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6348\" />Audio</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Column.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6349\" />Columns</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-File.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6350\" />File</li><li class=\"blocks-gallery-item\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Code.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6351\" />Code</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-List.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6352\" />List</li><li class=\"blocks-gallery-item\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Button.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6353\" />Button</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-Embeds.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6354\" />Embeds</li><li class=\"blocks-gallery-item\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Block-Icon-More.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6355\" />More</li></ul>\n\n\n\n<h2>Freedom to Build, Freedom to Write</h2>\n\n\n\n<p>This new editing experience provides a more consistent treatment of design as well as content. If you’re building client sites, you can create reusable blocks. This lets your clients add new content anytime, while still maintaining a consistent look and feel.</p>\n\n\n\n\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>A Stunning New Default Theme</h2>\n\n\n\n<div class=\"wp-block-image\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2018/12/twenty-nineteen.jpg?fit=2400%2C1600&ssl=1\" alt=\"\" class=\"wp-image-6358\" /></div>\n\n\n\n<p>Introducing Twenty Nineteen, a new default theme that shows off the power of the new editor.</p>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2018/12/block-editor-1024x683.jpg?resize=632%2C422&ssl=1\" alt=\"\" class=\"wp-image-6359\" /><div class=\"wp-block-media-text__content\">\n<h3 id=\"mce_9\">Designed for the block editor</h3>\n\n\n\n<p>Twenty Nineteen features custom styles for the blocks available by default in 5.0. It makes extensive use of editor styles throughout the theme. That way, what you create in your content editor is what you see on the front of your site.<br /></p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/typography.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6427\" /><div class=\"wp-block-media-text__content\">\n<h3 id=\"mce_18\">Simple, type-driven layout</h3>\n\n\n\n<p>Featuring ample whitespace, and modern sans-serif headlines paired with classic serif body text, Twenty Nineteen is built to be beautiful on the go. It uses system fonts to increase loading speed. No more long waits on slow networks!</p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2018/12/twenty-nineteen-versatile.gif?w=632&ssl=1\" alt=\"\" class=\"wp-image-6361\" /><div class=\"wp-block-media-text__content\">\n<h3 id=\"mce_24\">Versatile design for all sites</h3>\n\n\n\n<p>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</div></div>\n\n\n\n<div class=\"wp-block-button aligncenter\"><a class=\"wp-block-button__link has-text-color\" href=\"https://wordpress.org/themes/twentynineteen/\">Give Twenty Nineteen a try</a></div>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Developer Happiness</h2>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Protect.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6362\" /><div class=\"wp-block-media-text__content\">\n<h3 id=\"mce_34\">Protect</h3>\n\n\n\n<p>Blocks provide a comfortable way for users to change content directly, while also ensuring the content structure cannot be easily disturbed by accidental code edits. This allows the developer to control the output, building polished and semantic markup that is preserved through edits and not easily broken.</p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2018/12/Compose.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6363\" /><div class=\"wp-block-media-text__content\">\n<h3 id=\"mce_39\">Compose</h3>\n\n\n\n<p>Take advantage of a wide collection of APIs and interface components to easily create blocks with intuitive controls for your clients. Utilizing these components not only speeds up development work but also provide a more consistent, usable, and accessible interface to all users.</p>\n</div></div>\n\n\n\n<div class=\"wp-block-media-text alignwide is-stacked-on-mobile\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Create.jpg?w=632&ssl=1\" alt=\"\" class=\"wp-image-6364\" /><div class=\"wp-block-media-text__content\">\n<h3 id=\"mce_45\">Create</h3>\n\n\n\n<p>The new block paradigm opens up a path of exploration and imagination when it comes to solving user needs. With the unified block insertion flow, it’s easier for your clients and customers to find and use blocks for all types of content. Developers can focus on executing their vision and providing rich editing experiences, rather than fussing with difficult APIs.</p>\n</div></div>\n\n\n\n<div class=\"wp-block-button aligncenter\"><a class=\"wp-block-button__link has-text-color\" href=\"https://wordpress.org/gutenberg/handbook/\">Learn how to get started</a></div>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Keep it Classic</h2>\n\n\n\n<div class=\"wp-block-image\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2018/12/Classic.jpg?fit=2400%2C1130&ssl=1\" alt=\"\" class=\"wp-image-6365\" /></div>\n\n\n\n<p>Prefer to stick with the familiar Classic Editor? No problem! Support for the Classic Editor plugin will remain in WordPress through 2021.</p>\n\n\n\n<p>The Classic Editor plugin restores the previous WordPress editor and the Edit Post screen. It lets you keep using plugins that extend it, add old-style meta boxes, or otherwise depend on the previous editor. To install, visit your plugins page and click the “Install Now” button next to “Classic Editor”. After the plugin finishes installing, click “Activate”. That’s it!</p>\n\n\n\n<p>Note to users of assistive technology: if you experience usability issues with the block editor, we recommend you continue to use the Classic Editor.</p>\n\n\n\n<div class=\"wp-block-button aligncenter\"><a class=\"wp-block-button__link has-text-color\" href=\"https://wordpress.org/plugins/classic-editor/\">Check out the Classic Editor</a></div>\n\n\n\n<p>This release is named in homage to the pioneering Cuban jazz musician <a href=\"https://en.wikipedia.org/wiki/Bebo_Vald%C3%A9s\">Bebo Valdés</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>The Squad</h2>\n\n\n\n<p>This release was led by <a href=\"http://ma.tt/\">Matt Mullenweg</a>, along with co-leads <a href=\"https://www.allancole.com/\">Allan Cole</a>, <a href=\"http://antpb.com/\">Anthony Burchell</a>, <a href=\"https://pento.net/\">Gary Pendergast</a>, <a href=\"https://josepha.blog/\">Josepha Haden Chomphosy</a>, <a href=\"https://laurel.blog/\">Laurel Fulford</a>, <a href=\"https://yoast.com/about-us/team/omar-reiss/\">Omar Reiss</a>, <a href=\"https://danielbachhuber.com/\">Daniel Bachhuber</a>, <a href=\"https://matiasventura.com/\">Matías Ventura</a>, <a href=\"https://lamda.blog/\">Miguel Fonseca</a>, <a href=\"https://tam.blog/\">Tammie Lister</a>, <a href=\"https://tofumatt.com/\">Matthew Riley MacPherson</a>. They were ably assisted by the following fabulous folks. There were 423 contributors with props in this release. Pull up some Bebo Valdés on your music service of choice, and check out some of their profiles:</p>\n\n\n<a href=\"https://profiles.wordpress.org/jorbin\">Aaron Jorbin</a>, <a href=\"https://profiles.wordpress.org/abdulwahab610\">Abdul Wahab</a>, <a href=\"https://profiles.wordpress.org/abdullahramzan\">Abdullah Ramzan</a>, <a href=\"https://profiles.wordpress.org/abhijitrakas\">abhijitrakas</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/afraithe\">afraithe</a>, <a href=\"https://profiles.wordpress.org/mrahmadawais\">Ahmad Awais</a>, <a href=\"https://profiles.wordpress.org/ahmadawais\">ahmadawais</a>, <a href=\"https://profiles.wordpress.org/airathalitov\">Airat Halitov</a>, <a href=\"https://profiles.wordpress.org/ajitbohra\">Ajit Bohra</a>, <a href=\"https://profiles.wordpress.org/schlessera\">Alain Schlesser</a>, <a href=\"https://profiles.wordpress.org/albertomedina\">albertomedina</a>, <a href=\"https://profiles.wordpress.org/aldavigdis\">aldavigdis</a>, <a href=\"https://profiles.wordpress.org/alexsanford1\">Alex Sanford</a>, <a href=\"https://profiles.wordpress.org/alexis\">alexis</a>, <a href=\"https://profiles.wordpress.org/alexislloyd\">Alexis Lloyd</a>, <a href=\"https://profiles.wordpress.org/arush\">Amanda Rush</a>, <a href=\"https://profiles.wordpress.org/amedina\">amedina</a>, <a href=\"https://profiles.wordpress.org/afercia\">Andrea Fercia</a>, <a href=\"https://profiles.wordpress.org/andreamiddleton\">Andrea Middleton</a>, <a href=\"https://profiles.wordpress.org/euthelup\">Andrei Lupu</a>, <a href=\"https://profiles.wordpress.org/andreiglingeanu\">andreiglingeanu</a>, <a href=\"https://profiles.wordpress.org/aduth\">Andrew Duthie</a>, <a href=\"https://profiles.wordpress.org/sumobi\">Andrew Munro</a>, <a href=\"https://profiles.wordpress.org/anevins\">Andrew Nevins</a>, <a href=\"https://profiles.wordpress.org/azaozz\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/androb\">Andrew Roberts</a>, <a href=\"https://profiles.wordpress.org/andrewtaylor-1\">Andrew Taylor</a>, <a href=\"https://profiles.wordpress.org/andrewserong\">andrewserong</a>, <a href=\"https://profiles.wordpress.org/apeatling\">Andy Peatling</a>, <a href=\"https://profiles.wordpress.org/ameeker\">Angie Meeker</a>, <a href=\"https://profiles.wordpress.org/annaharrison\">Anna Harrison</a>, <a href=\"https://profiles.wordpress.org/atimmer\">Anton Timmermans</a>, <a href=\"https://profiles.wordpress.org/arnaudban\">ArnaudBan</a>, <a href=\"https://profiles.wordpress.org/arshidkv12\">Arshid</a>, <a href=\"https://profiles.wordpress.org/aprakasa\">Arya Prakasa</a>, <a href=\"https://profiles.wordpress.org/artisticasad\">Asad</a>, <a href=\"https://profiles.wordpress.org/mrasharirfan\">Ashar Irfan</a>, <a href=\"https://profiles.wordpress.org/asvinballoo\">asvinballoo</a>, <a href=\"https://profiles.wordpress.org/atanasangelovdev\">Atanas Angelov</a>, <a href=\"https://profiles.wordpress.org/b-07\">Bappi</a>, <a href=\"https://profiles.wordpress.org/bcolumbia\">bcolumbia</a>, <a href=\"https://profiles.wordpress.org/belcherj\">belcherj</a>, <a href=\"https://profiles.wordpress.org/caxco93\">Benjamin Eyzaguirre</a>, <a href=\"https://profiles.wordpress.org/benjamin_zekavica\">Benjamin Zekavica</a>, <a href=\"https://profiles.wordpress.org/benlk\">benlk</a>, <a href=\"https://profiles.wordpress.org/kau-boy\">Bernhard Kau</a>, <a href=\"https://profiles.wordpress.org/bernhard-reiter\">Bernhard Reiter</a>, <a href=\"https://profiles.wordpress.org/betsela\">betsela</a>, <a href=\"https://profiles.wordpress.org/bhargavmehta\">Bhargav Mehta</a>, <a href=\"https://profiles.wordpress.org/birgire\">Birgir Erlendsson (birgire)</a>, <a href=\"https://profiles.wordpress.org/bph\">Birgit Pauli-Haack</a>, <a href=\"https://profiles.wordpress.org/blowery\">blowery</a>, <a href=\"https://profiles.wordpress.org/bobbingwide\">bobbingwide</a>, <a href=\"https://profiles.wordpress.org/boblinthorst\">boblinthorst</a>, <a href=\"https://profiles.wordpress.org/boonebgorges\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/bradyvercher\">Brady Vercher</a>, <a href=\"https://profiles.wordpress.org/kraftbj\">Brandon Kraft</a>, <a href=\"https://profiles.wordpress.org/bpayton\">Brandon Payton</a>, <a href=\"https://profiles.wordpress.org/brentswisher\">Brent Swisher</a>, <a href=\"https://profiles.wordpress.org/technosiren\">Brianna Privett</a>, <a href=\"https://profiles.wordpress.org/briannaorg\">briannaorg</a>, <a href=\"https://profiles.wordpress.org/bronsonquick\">Bronson Quick</a>, <a href=\"https://profiles.wordpress.org/bandonrandon\">Brooke.</a>, <a href=\"https://profiles.wordpress.org/burhandodhy\">Burhan Nasir</a>, <a href=\"https://profiles.wordpress.org/cantothemes\">CantoThemes</a>, <a href=\"https://profiles.wordpress.org/cathibosco\">cathibosco</a>, <a href=\"https://profiles.wordpress.org/chetan200891\">Chetan Prajapati</a>, <a href=\"https://profiles.wordpress.org/chetansatasiya\">chetansatasiya</a>, <a href=\"https://profiles.wordpress.org/ketuchetan\">chetansatasiya</a>, <a href=\"https://profiles.wordpress.org/chouby\">Chouby</a>, <a href=\"https://profiles.wordpress.org/crunnells\">Chris Runnells</a>, <a href=\"https://profiles.wordpress.org/chrisvanpatten\">Chris Van Patten</a>, <a href=\"https://profiles.wordpress.org/chriskmnds\">chriskmnds</a>, <a href=\"https://profiles.wordpress.org/chrisl27\">chrisl27</a>, <a href=\"https://profiles.wordpress.org/pixelverbieger\">Christian Sabo</a>, <a href=\"https://profiles.wordpress.org/christophherr\">Christoph Herr</a>, <a href=\"https://profiles.wordpress.org/circlecube\">circlecube</a>, <a href=\"https://profiles.wordpress.org/claudiosanches\">Claudio Sanches</a>, <a href=\"https://profiles.wordpress.org/coderkevin\">coderkevin</a>, <a href=\"https://profiles.wordpress.org/copons\">Copons</a>, <a href=\"https://profiles.wordpress.org/courtney0burton\">courtney0burton</a>, <a href=\"https://profiles.wordpress.org/littlebigthing\">Csaba (LittleBigThings)</a>, <a href=\"https://profiles.wordpress.org/csabotta\">csabotta</a>, <a href=\"https://profiles.wordpress.org/danieltj\">Daniel James</a>, <a href=\"https://profiles.wordpress.org/talldanwp\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/danielhw\">danielhw</a>, <a href=\"https://profiles.wordpress.org/daniloercoli\">daniloercoli</a>, <a href=\"https://profiles.wordpress.org/dannycooper\">DannyCooper</a>, <a href=\"https://profiles.wordpress.org/nerrad\">Darren Ethier (nerrad)</a>, <a href=\"https://profiles.wordpress.org/davemoran118\">davemoran118</a>, <a href=\"https://profiles.wordpress.org/dcavins\">David Cavins</a>, <a href=\"https://profiles.wordpress.org/dlh\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/davidakennedy\">David Kennedy</a>, <a href=\"https://profiles.wordpress.org/dryanpress\">David Ryan</a>, <a href=\"https://profiles.wordpress.org/davidsword\">David Sword</a>, <a href=\"https://profiles.wordpress.org/folletto\">Davide \'Folletto\' Casali</a>, <a href=\"https://profiles.wordpress.org/davidherrera\">davidherrera</a>, <a href=\"https://profiles.wordpress.org/davisshaver\">Davis</a>, <a href=\"https://profiles.wordpress.org/dciso\">dciso</a>, <a href=\"https://profiles.wordpress.org/dmsnell\">Dennis Snell</a>, <a href=\"https://profiles.wordpress.org/dsmart\">Derek Smart</a>, <a href=\"https://profiles.wordpress.org/designsimply\">designsimply</a>, <a href=\"https://profiles.wordpress.org/dlocc\">Devin Walker</a>, <a href=\"https://profiles.wordpress.org/deviodigital\">Devio Digital</a>, <a href=\"https://profiles.wordpress.org/dfangstrom\">dfangstrom</a>, <a href=\"https://profiles.wordpress.org/dhanendran\">Dhanendran</a>, <a href=\"https://profiles.wordpress.org/diegoliv\">Diego de Oliveira</a>, <a href=\"https://profiles.wordpress.org/diegoreymendez\">diegoreymendez</a>, <a href=\"https://profiles.wordpress.org/dingo_bastard\">dingo-d</a>, <a href=\"https://profiles.wordpress.org/dd32\">Dion Hulse</a>, <a href=\"https://profiles.wordpress.org/dency\">Dixita Dusara</a>, <a href=\"https://profiles.wordpress.org/dixitadusara\">Dixita Gohil</a>, <a href=\"https://profiles.wordpress.org/ocean90\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/donnapep\">Donna Peplinskie</a>, <a href=\"https://profiles.wordpress.org/drewapicture\">Drew Jaynes</a>, <a href=\"https://profiles.wordpress.org/dsawardekar\">dsawardekar</a>, <a href=\"https://profiles.wordpress.org/dsifford\">dsifford</a>, <a href=\"https://profiles.wordpress.org/duanestorey\">Duane Storey</a>, <a href=\"https://profiles.wordpress.org/chopinbach\">Edwin Cromley</a>, <a href=\"https://profiles.wordpress.org/ehg\">ehg</a>, <a href=\"https://profiles.wordpress.org/electricfeet\">ElectricFeet</a>, <a href=\"https://profiles.wordpress.org/eliorivero\">Elio Rivero</a>, <a href=\"https://profiles.wordpress.org/epointal\">Elisabeth Pointal</a>, <a href=\"https://profiles.wordpress.org/iseulde\">Ella Iseulde Van Dorpe</a>, <a href=\"https://profiles.wordpress.org/elrae\">elrae</a>, <a href=\"https://profiles.wordpress.org/enodekciw\">enodekciw</a>, <a href=\"https://profiles.wordpress.org/ephoxjames\">ephoxjames</a>, <a href=\"https://profiles.wordpress.org/ephoxmogran\">ephoxmogran</a>, <a href=\"https://profiles.wordpress.org/sewmyheadon\">Eric Amundson</a>, <a href=\"https://profiles.wordpress.org/ericnmurphy\">ericnmurphy</a>, <a href=\"https://profiles.wordpress.org/etoledom\">etoledom</a>, <a href=\"https://profiles.wordpress.org/fabiankaegy\">fabiankaegy</a>, <a href=\"https://profiles.wordpress.org/fabs_pim\">fabs_pim</a>, <a href=\"https://profiles.wordpress.org/faishal\">faishal</a>, <a href=\"https://profiles.wordpress.org/flixos90\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/floriansimeth\">Florian Simeth</a>, <a href=\"https://profiles.wordpress.org/foobar4u\">foobar4u</a>, <a href=\"https://profiles.wordpress.org/foreverpinetree\">foreverpinetree</a>, <a href=\"https://profiles.wordpress.org/frank-klein\">Frank Klein</a>, <a href=\"https://profiles.wordpress.org/fuyuko\">fuyuko</a>, <a href=\"https://profiles.wordpress.org/gma992\">Gabriel Maldonado</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/garyj\">Gary Jones</a>, <a href=\"https://profiles.wordpress.org/doomwaxer\">Gary Thayer</a>, <a href=\"https://profiles.wordpress.org/garyjones\">garyjones</a>, <a href=\"https://profiles.wordpress.org/soulseekah\">Gennady Kovshenin</a>, <a href=\"https://profiles.wordpress.org/babbardel\">George Olaru</a>, <a href=\"https://profiles.wordpress.org/georgestephanis\">George Stephanis</a>, <a href=\"https://profiles.wordpress.org/georgeh\">georgeh</a>, <a href=\"https://profiles.wordpress.org/gnif\">gnif</a>, <a href=\"https://profiles.wordpress.org/goldsounds\">goldsounds</a>, <a href=\"https://profiles.wordpress.org/grappler\">Grappler</a>, <a href=\"https://profiles.wordpress.org/gziolo\">Grzegorz Ziółkowski</a>, <a href=\"https://profiles.wordpress.org/bordoni\">Gustavo Bordoni</a>, <a href=\"https://profiles.wordpress.org/gwwar\">gwwar</a>, <a href=\"https://profiles.wordpress.org/hardeepasrani\">Hardeep Asrani</a>, <a href=\"https://profiles.wordpress.org/hblackett\">hblackett</a>, <a href=\"https://profiles.wordpress.org/helen\">Helen Hou-Sandi</a>, <a href=\"https://profiles.wordpress.org/luehrsen\">Hendrik Luehrsen</a>, <a href=\"https://profiles.wordpress.org/herbmiller\">herbmiller</a>, <a href=\"https://profiles.wordpress.org/herregroen\">Herre Groen</a>, <a href=\"https://profiles.wordpress.org/hugobaeta\">Hugo Baeta</a>, <a href=\"https://profiles.wordpress.org/hypest\">hypest</a>, <a href=\"https://profiles.wordpress.org/iandunn\">Ian Dunn</a>, <a href=\"https://profiles.wordpress.org/ianstewart\">ianstewart</a>, <a href=\"https://profiles.wordpress.org/ianbelanger\">ibelanger</a>, <a href=\"https://profiles.wordpress.org/icaleb\">iCaleb</a>, <a href=\"https://profiles.wordpress.org/idpokute\">idpokute</a>, <a href=\"https://profiles.wordpress.org/igorsch\">Igor</a>, <a href=\"https://profiles.wordpress.org/imath\">imath</a>, <a href=\"https://profiles.wordpress.org/imonly_ik\">Imran Khalid</a>, <a href=\"https://profiles.wordpress.org/intronic\">intronic</a>, <a href=\"https://profiles.wordpress.org/ipstenu\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/ireneyoast\">Irene Strikkers</a>, <a href=\"https://profiles.wordpress.org/ismailelkorchi\">Ismail El Korchi</a>, <a href=\"https://profiles.wordpress.org/israelshmueli\">israelshmueli</a>, <a href=\"https://profiles.wordpress.org/jdgrimes\">J.D. Grimes</a>, <a href=\"https://profiles.wordpress.org/jd55\">J.D. Grimes</a>, <a href=\"https://profiles.wordpress.org/jakept\">Jacob Peattie</a>, <a href=\"https://profiles.wordpress.org/jagnew\">jagnew</a>, <a href=\"https://profiles.wordpress.org/jahvi\">jahvi</a>, <a href=\"https://profiles.wordpress.org/jnylen0\">James Nylen</a>, <a href=\"https://profiles.wordpress.org/jamestryon\">jamestryon</a>, <a href=\"https://profiles.wordpress.org/jamiehalvorson\">jamiehalvorson</a>, <a href=\"https://profiles.wordpress.org/jdembowski\">Jan Dembowski</a>, <a href=\"https://profiles.wordpress.org/janalwin\">janalwin</a>, <a href=\"https://profiles.wordpress.org/jaswrks\">Jason Caldwell</a>, <a href=\"https://profiles.wordpress.org/octalmage\">Jason Stallings</a>, <a href=\"https://profiles.wordpress.org/yingling017\">Jason Yingling</a>, <a href=\"https://profiles.wordpress.org/vengisss\">Javier Villanueva</a>, <a href=\"https://profiles.wordpress.org/jhoffm34\">Jay Hoffmann</a>, <a href=\"https://profiles.wordpress.org/audrasjb\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/jblz\">Jeff Bowen</a>, <a href=\"https://profiles.wordpress.org/jeffpaul\">Jeffrey Paul</a>, <a href=\"https://profiles.wordpress.org/jeremyfelt\">Jeremy Felt</a>, <a href=\"https://profiles.wordpress.org/jipmoors\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby\">JJJ</a>, <a href=\"https://profiles.wordpress.org/sephsekla\">Joe Bailey-Roberts</a>, <a href=\"https://profiles.wordpress.org/joedolson\">Joe Dolson</a>, <a href=\"https://profiles.wordpress.org/joehoyle\">Joe Hoyle</a>, <a href=\"https://profiles.wordpress.org/joemcgill\">Joe McGill</a>, <a href=\"https://profiles.wordpress.org/joemaller\">joemaller</a>, <a href=\"https://profiles.wordpress.org/joen\">Joen Asmussen</a>, <a href=\"https://profiles.wordpress.org/j-falk\">Johan Falk</a>, <a href=\"https://profiles.wordpress.org/johnbillion\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnny5\">John Godley</a>, <a href=\"https://profiles.wordpress.org/johndyer\">johndyer</a>, <a href=\"https://profiles.wordpress.org/johnpixle\">JohnPixle</a>, <a href=\"https://profiles.wordpress.org/johnwatkins0\">johnwatkins0</a>, <a href=\"https://profiles.wordpress.org/jomurgel\">jomurgel</a>, <a href=\"https://profiles.wordpress.org/desrosj\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/spacedmonkey\">Jonny Harris</a>, <a href=\"https://profiles.wordpress.org/jonsurrell\">jonsurrell</a>, <a href=\"https://profiles.wordpress.org/joostdevalk\">Joost de Valk</a>, <a href=\"https://profiles.wordpress.org/koke\">Jorge Bernal</a>, <a href=\"https://profiles.wordpress.org/jorgefilipecosta\">Jorge Costa</a>, <a href=\"https://profiles.wordpress.org/ieatwebsites\">Jose Fremaint</a>, <a href=\"https://profiles.wordpress.org/shelob9\">Josh Pollock</a>, <a href=\"https://profiles.wordpress.org/jvisick77\">Josh Visick</a>, <a href=\"https://profiles.wordpress.org/joshuawold\">Joshua Wold</a>, <a href=\"https://profiles.wordpress.org/joyously\">Joy</a>, <a href=\"https://profiles.wordpress.org/jrf\">jrf</a>, <a href=\"https://profiles.wordpress.org/jryancard\">jryancard</a>, <a href=\"https://profiles.wordpress.org/jsnajdr\">jsnajdr</a>, <a href=\"https://profiles.wordpress.org/julienmelissas\">JulienMelissas</a>, <a href=\"https://profiles.wordpress.org/kopepasah\">Justin Kopepasah</a>, <a href=\"https://profiles.wordpress.org/kadamwhite\">K.Adam White</a>, <a href=\"https://profiles.wordpress.org/kallehauge\">Kallehauge</a>, <a href=\"https://profiles.wordpress.org/kalpshit\">KalpShit Akabari</a>, <a href=\"https://profiles.wordpress.org/codebykat\">Kat Hagan</a>, <a href=\"https://profiles.wordpress.org/ryelle\">Kelly Dwan</a>, <a href=\"https://profiles.wordpress.org/kevinwhoffman\">Kevin Hoffman</a>, <a href=\"https://profiles.wordpress.org/khleomix\">khleomix</a>, <a href=\"https://profiles.wordpress.org/ixkaito\">Kite</a>, <a href=\"https://profiles.wordpress.org/kjellr\">Kjell Reigstad</a>, <a href=\"https://profiles.wordpress.org/kluny\">kluny</a>, <a href=\"https://profiles.wordpress.org/obenland\">Konstantin Obenland</a>, <a href=\"https://profiles.wordpress.org/xkon\">Konstantinos Xenos</a>, <a href=\"https://profiles.wordpress.org/krutidugade\">krutidugade</a>, <a href=\"https://profiles.wordpress.org/lancewillett\">Lance Willett</a>, <a href=\"https://profiles.wordpress.org/notlaura\">Lara Schenck</a>, <a href=\"https://profiles.wordpress.org/leahkoerper\">leahkoerper</a>, <a href=\"https://profiles.wordpress.org/lloyd\">lloyd</a>, <a href=\"https://profiles.wordpress.org/loicblascos\">Loic</a>, <a href=\"https://profiles.wordpress.org/lucasstark\">Lucas Stark</a>, <a href=\"https://profiles.wordpress.org/lucasrolff\">LucasRolff</a>, <a href=\"https://profiles.wordpress.org/luigipulcini\">luigipulcini</a>, <a href=\"https://profiles.wordpress.org/lukecavanagh\">Luke Cavanagh</a>, <a href=\"https://profiles.wordpress.org/lucaskowalski\">Luke Kowalski</a>, <a href=\"https://profiles.wordpress.org/lukepettway\">Luke Pettway</a>, <a href=\"https://profiles.wordpress.org/luminus\">Luminus</a>, <a href=\"https://profiles.wordpress.org/lynneux\">lynneux</a>, <a href=\"https://profiles.wordpress.org/m-e-h\">m-e-h</a>, <a href=\"https://profiles.wordpress.org/macbookandrew\">macbookandrew</a>, <a href=\"https://profiles.wordpress.org/maedahbatool\">Maedah Batool</a>, <a href=\"https://profiles.wordpress.org/mahdiyazdani\">Mahdi Yazdani</a>, <a href=\"https://profiles.wordpress.org/mahmoudsaeed\">mahmoudsaeed</a>, <a href=\"https://profiles.wordpress.org/travel_girl\">Maja Benke</a>, <a href=\"https://profiles.wordpress.org/mkaz\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/tyxla\">Marin Atanasov</a>, <a href=\"https://profiles.wordpress.org/marina_wp\">marina_wp</a>, <a href=\"https://profiles.wordpress.org/clorith\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/mariusvw\">mariusvw</a>, <a href=\"https://profiles.wordpress.org/markjaquith\">Mark Jaquith</a>, <a href=\"https://profiles.wordpress.org/mapk\">Mark Uraine</a>, <a href=\"https://profiles.wordpress.org/martinlugton\">martinlugton</a>, <a href=\"https://profiles.wordpress.org/mathiu\">mathiu</a>, <a href=\"https://profiles.wordpress.org/webdevmattcrom\">Matt Cromwell</a>, <a href=\"https://profiles.wordpress.org/matt\">Matt Mullenweg</a>, <a href=\"https://profiles.wordpress.org/mattgeri\">MattGeri</a>, <a href=\"https://profiles.wordpress.org/mboynes\">Matthew Boynes</a>, <a href=\"https://profiles.wordpress.org/mattheu\">Matthew Haines-Young</a>, <a href=\"https://profiles.wordpress.org/maurobringolf\">maurobringolf</a>, <a href=\"https://profiles.wordpress.org/maximebj\">Maxime BERNARD-JACQUET</a>, <a href=\"https://profiles.wordpress.org/mayukojpn\">Mayo Moriyama</a>, <a href=\"https://profiles.wordpress.org/meetjey\">meetjey</a>, <a href=\"https://profiles.wordpress.org/melchoyce\">Mel Choyce</a>, <a href=\"https://profiles.wordpress.org/mendezcode\">mendezcode</a>, <a href=\"https://profiles.wordpress.org/woodent\">Micah Wood</a>, <a href=\"https://profiles.wordpress.org/mdawaffe\">Michael Adams (mdawaffe)</a>, <a href=\"https://profiles.wordpress.org/michaelhull\">Michael Hull</a>, <a href=\"https://profiles.wordpress.org/mnelson4\">Michael Nelson</a>, <a href=\"https://profiles.wordpress.org/mizejewski\">Michele Mizejewski</a>, <a href=\"https://profiles.wordpress.org/jbpaul17\">Migrated to @jeffpaul</a>, <a href=\"https://profiles.wordpress.org/stubgo\">Miina Sikk</a>, <a href=\"https://profiles.wordpress.org/simison\">Mikael Korpela</a>, <a href=\"https://profiles.wordpress.org/mihai2u\">Mike Crantea</a>, <a href=\"https://profiles.wordpress.org/mike-haydon-swo\">Mike Haydon</a>, <a href=\"https://profiles.wordpress.org/mikeschroder\">Mike Schroder</a>, <a href=\"https://profiles.wordpress.org/mikehaydon\">mikehaydon</a>, <a href=\"https://profiles.wordpress.org/mikeyarce\">Mikey Arce</a>, <a href=\"https://profiles.wordpress.org/dimadin\">Milan Dinić</a>, <a href=\"https://profiles.wordpress.org/milana_cap\">Milana Cap</a>, <a href=\"https://profiles.wordpress.org/gonzomir\">Milen Petrinski - Gonzo</a>, <a href=\"https://profiles.wordpress.org/milesdelliott\">milesdelliott</a>, <a href=\"https://profiles.wordpress.org/mimo84\">mimo84</a>, <a href=\"https://profiles.wordpress.org/0mirka00\">mirka</a>, <a href=\"https://profiles.wordpress.org/mitogh\">mitogh</a>, <a href=\"https://profiles.wordpress.org/mmtr86\">mmtr86</a>, <a href=\"https://profiles.wordpress.org/boemedia\">Monique Dubbelman</a>, <a href=\"https://profiles.wordpress.org/mor10\">Morten Rand-Hendriksen</a>, <a href=\"https://profiles.wordpress.org/mostafas1990\">Mostafa Soufi</a>, <a href=\"https://profiles.wordpress.org/motleydev\">motleydev</a>, <a href=\"https://profiles.wordpress.org/mpheasant\">mpheasant</a>, <a href=\"https://profiles.wordpress.org/mrmadhat\">mrmadhat</a>, <a href=\"https://profiles.wordpress.org/mrwweb\">mrwweb</a>, <a href=\"https://profiles.wordpress.org/msdesign21\">msdesign21</a>, <a href=\"https://profiles.wordpress.org/mtias\">mtias</a>, <a href=\"https://profiles.wordpress.org/desideveloper\">Muhammad Irfan</a>, <a href=\"https://profiles.wordpress.org/mukesh27\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/munirkamal\">munirkamal</a>, <a href=\"https://profiles.wordpress.org/mmaumio\">Muntasir Mahmud</a>, <a href=\"https://profiles.wordpress.org/mzorz\">mzorz</a>, <a href=\"https://profiles.wordpress.org/nagayama\">nagayama</a>, <a href=\"https://profiles.wordpress.org/nfmohit\">Nahid F. Mohit</a>, <a href=\"https://profiles.wordpress.org/nao\">Naoko Takano</a>, <a href=\"https://profiles.wordpress.org/napy84\">napy84</a>, <a href=\"https://profiles.wordpress.org/nateconley\">nateconley</a>, <a href=\"https://profiles.wordpress.org/nativeinside\">Native Inside</a>, <a href=\"https://profiles.wordpress.org/greatislander\">Ned Zimmerman</a>, <a href=\"https://profiles.wordpress.org/buzztone\">Neil Murray</a>, <a href=\"https://profiles.wordpress.org/nicbertino\">nic.bertino</a>, <a href=\"https://profiles.wordpress.org/notnownikki\">Nicola Heald</a>, <a href=\"https://profiles.wordpress.org/nielslange\">Niels Lange</a>, <a href=\"https://profiles.wordpress.org/nikschavan\">Nikhil Chavan</a>, <a href=\"https://profiles.wordpress.org/nbachiyski\">Nikolay Bachiyski</a>, <a href=\"https://profiles.wordpress.org/nitrajka\">nitrajka</a>, <a href=\"https://profiles.wordpress.org/njpanderson\">njpanderson</a>, <a href=\"https://profiles.wordpress.org/nosolosw\">nosolosw</a>, <a href=\"https://profiles.wordpress.org/nshki\">nshki</a>, <a href=\"https://profiles.wordpress.org/hideokamoto\">Okamoto Hidetaka</a>, <a href=\"https://profiles.wordpress.org/oskosk\">oskosk</a>, <a href=\"https://profiles.wordpress.org/pareshradadiya-1\">Paresh Radadiya</a>, <a href=\"https://profiles.wordpress.org/swissspidy\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/pbearne\">Paul Bearne</a>, <a href=\"https://profiles.wordpress.org/pauldechov\">Paul Dechov</a>, <a href=\"https://profiles.wordpress.org/paulstonier\">Paul Stonier</a>, <a href=\"https://profiles.wordpress.org/paulwilde\">Paul Wilde</a>, <a href=\"https://profiles.wordpress.org/pedromendonca\">Pedro Mendon&#231;a</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/pglewis\">pglewis</a>, <a href=\"https://profiles.wordpress.org/tyrannous\">Philipp Bammes</a>, <a href=\"https://profiles.wordpress.org/piersb\">piersb</a>, <a href=\"https://profiles.wordpress.org/wizzard_\">Pieter Daalder</a>, <a href=\"https://profiles.wordpress.org/pilou69\">pilou69</a>, <a href=\"https://profiles.wordpress.org/delawski\">Piotr Delawski</a>, <a href=\"https://profiles.wordpress.org/poena\">poena</a>, <a href=\"https://profiles.wordpress.org/postphotos\">postphotos</a>, <a href=\"https://profiles.wordpress.org/potbot\">potbot</a>, <a href=\"https://profiles.wordpress.org/prtksxna\">Prateek Saxena</a>, <a href=\"https://profiles.wordpress.org/pratikthink\">pratikthink</a>, <a href=\"https://profiles.wordpress.org/presskopp\">Presskopp</a>, <a href=\"https://profiles.wordpress.org/psealock\">psealock</a>, <a href=\"https://profiles.wordpress.org/ptasker\">ptasker</a>, <a href=\"https://profiles.wordpress.org/rachelmcr\">Rachel</a>, <a href=\"https://profiles.wordpress.org/rachelbaker\">Rachel Baker</a>, <a href=\"https://profiles.wordpress.org/rahmohn\">Rahmohn</a>, <a href=\"https://profiles.wordpress.org/rahmon\">Rahmon</a>, <a href=\"https://profiles.wordpress.org/rahulsprajapati\">Rahul Prajapati</a>, <a href=\"https://profiles.wordpress.org/rakshans1\">rakshans1</a>, <a href=\"https://profiles.wordpress.org/ramonopoly\">ramonopoly</a>, <a href=\"https://profiles.wordpress.org/lamosty\">Rastislav Lamos</a>, <a href=\"https://profiles.wordpress.org/revgeorge\">revgeorge</a>, <a href=\"https://profiles.wordpress.org/youknowriad\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/rianrietveld\">Rian Rietveld</a>, <a href=\"https://profiles.wordpress.org/richsalvucci\">richsalvucci</a>, <a href=\"https://profiles.wordpress.org/riddhiehta02\">Riddhi Mehta</a>, <a href=\"https://profiles.wordpress.org/rileybrook\">Riley Brook</a>, <a href=\"https://profiles.wordpress.org/noisysocks\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/sanchothefat\">Robert O\'Rourke</a>, <a href=\"https://profiles.wordpress.org/robertsky\">robertsky</a>, <a href=\"https://profiles.wordpress.org/_dorsvenabili\">Rocio Valdivia</a>, <a href=\"https://profiles.wordpress.org/rohittm\">Rohit Motwani</a>, <a href=\"https://profiles.wordpress.org/magicroundabout\">Ross Wintle</a>, <a href=\"https://profiles.wordpress.org/rmccue\">Ryan McCue</a>, <a href=\"https://profiles.wordpress.org/welcher\">Ryan Welcher</a>, <a href=\"https://profiles.wordpress.org/ryo511\">ryo511</a>, <a href=\"https://profiles.wordpress.org/sagarprajapati\">Sagar Prajapati</a>, <a href=\"https://profiles.wordpress.org/samikeijonen\">Sami Keijonen</a>, <a href=\"https://profiles.wordpress.org/otto42\">Samuel Wood (Otto)</a>, <a href=\"https://profiles.wordpress.org/smyoon315\">Sang-Min Yoon</a>, <a href=\"https://profiles.wordpress.org/tinkerbelly\">sarah semark</a>, <a href=\"https://profiles.wordpress.org/scottmweaver\">Scott Weaver</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/sergioestevao\">SergioEstevao</a>, <a href=\"https://profiles.wordpress.org/azchughtai\">Shahjehan Ali</a>, <a href=\"https://profiles.wordpress.org/shaileesheth\">Shailee Sheth</a>, <a href=\"https://profiles.wordpress.org/sharaz\">Sharaz Shahid</a>, <a href=\"https://profiles.wordpress.org/giventofly76\">Shaun sc</a>, <a href=\"https://profiles.wordpress.org/shaunandrews\">shaunandrews</a>, <a href=\"https://profiles.wordpress.org/shooper\">Shawn Hooper</a>, <a href=\"https://profiles.wordpress.org/shenkj\">shenkj</a>, <a href=\"https://profiles.wordpress.org/sikander\">sikander</a>, <a href=\"https://profiles.wordpress.org/pross\">Simon Prosser</a>, <a href=\"https://profiles.wordpress.org/siriokun\">siriokun</a>, <a href=\"https://profiles.wordpress.org/sirjonathan\">sirjonathan</a>, <a href=\"https://profiles.wordpress.org/sirreal\">sirreal</a>, <a href=\"https://profiles.wordpress.org/sisanu\">Sisanu</a>, <a href=\"https://profiles.wordpress.org/skorasaurus\">skorasaurus</a>, <a href=\"https://profiles.wordpress.org/butimnoexpert\">Slushman</a>, <a href=\"https://profiles.wordpress.org/ssousa\">Sofia Sousa</a>, <a href=\"https://profiles.wordpress.org/somtijds\">SOMTIJDS</a>, <a href=\"https://profiles.wordpress.org/soean\">Soren Wrede</a>, <a href=\"https://profiles.wordpress.org/spocke\">spocke</a>, <a href=\"https://profiles.wordpress.org/stagger-lee\">Stagger Lee</a>, <a href=\"https://profiles.wordpress.org/sstoqnov\">Stanimir Stoyanov</a>, <a href=\"https://profiles.wordpress.org/netweb\">Stephen Edgar</a>, <a href=\"https://profiles.wordpress.org/stevehenty\">Steve Henty</a>, <a href=\"https://profiles.wordpress.org/charlestonsw\">Store Locator Plus</a>, <a href=\"https://profiles.wordpress.org/strategio\">strategio</a>, <a href=\"https://profiles.wordpress.org/stuartfeldt\">stuartfeldt</a>, <a href=\"https://profiles.wordpress.org/tacrapo\">tacrapo</a>, <a href=\"https://profiles.wordpress.org/tammie_l\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/themeroots\">ThemeRoots</a>, <a href=\"https://profiles.wordpress.org/tfrommen\">Thorsten Frommen</a>, <a href=\"https://profiles.wordpress.org/thrijith\">Thrijith Thankachan</a>, <a href=\"https://profiles.wordpress.org/hedgefield\">Tim Hengeveld</a>, <a href=\"https://profiles.wordpress.org/timgardner\">timgardner</a>, <a href=\"https://profiles.wordpress.org/timmydcrawford\">Timmy Crawford</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/tjnowell\">Tom J Nowell</a>, <a href=\"https://profiles.wordpress.org/tlxo\">Toni Laakso</a>, <a href=\"https://profiles.wordpress.org/tobifjellner\">Tor-Bjorn Fjellner</a>, <a href=\"https://profiles.wordpress.org/toro_unit\">Toro_Unit (Hiroshi Urabe)</a>, <a href=\"https://profiles.wordpress.org/mirucon\">Toshihiro Kanai</a>, <a href=\"https://profiles.wordpress.org/itowhid06\">Towhidul Islam</a>, <a href=\"https://profiles.wordpress.org/travislopes\">Travis Lopes</a>, <a href=\"https://profiles.wordpress.org/truongwp\">truongwp</a>, <a href=\"https://profiles.wordpress.org/tjfunke001\">Tunji Ayoola</a>, <a href=\"https://profiles.wordpress.org/twoelevenjay\">twoelevenjay</a>, <a href=\"https://profiles.wordpress.org/grapplerulrich\">Ulrich</a>, <a href=\"https://profiles.wordpress.org/vindl\">vindl</a>, <a href=\"https://profiles.wordpress.org/vishalkakadiya\">Vishal Kakadiya</a>, <a href=\"https://profiles.wordpress.org/vtrpldn\">Vitor Paladini</a>, <a href=\"https://profiles.wordpress.org/walterebert\">Walter Ebert</a>, <a href=\"https://profiles.wordpress.org/warmarks\">warmarks</a>, <a href=\"https://profiles.wordpress.org/webmandesign\">WebMan Design &#124; Oliver Juhas</a>, <a href=\"https://profiles.wordpress.org/websupporter\">websupporter</a>, <a href=\"https://profiles.wordpress.org/westonruter\">Weston Ruter</a>, <a href=\"https://profiles.wordpress.org/earnjam\">William Earnhardt</a>, <a href=\"https://profiles.wordpress.org/williampatton\">williampatton</a>, <a href=\"https://profiles.wordpress.org/willybahuaud\">Willy Bahuaud</a>, <a href=\"https://profiles.wordpress.org/wpscholar\">wpscholar</a>, <a href=\"https://profiles.wordpress.org/xyfi\">xyfi</a>, <a href=\"https://profiles.wordpress.org/yahil\">Yahil Madakiya</a>, <a href=\"https://profiles.wordpress.org/yingles\">yingles</a>, <a href=\"https://profiles.wordpress.org/yoavf\">Yoav Farhi</a>, <a href=\"https://profiles.wordpress.org/youthkee\">Yusuke Takahashi</a>, <a href=\"https://profiles.wordpress.org/zebulan\">zebulan</a>, and <a href=\"https://profiles.wordpress.org/ziyaddin\">Ziyaddin Sadigov</a>.\n\n\n\n<p>Finally, thanks to all the community translators who worked on WordPress 5.0. Their efforts bring WordPress 5.0 fully translated to 37 languages at release time, with more on the way.</p>\n\n\n\n<p>If you want to follow along or help out, check out <a href=\"https://make.wordpress.org/\">Make WordPress</a> and our <a href=\"https://make.wordpress.org/core/\">core development blog</a>.</p>\n\n\n\n<p>Thanks for choosing WordPress!</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Dec 2018 19:28:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"Post Status: WordPress 5.0 marks a new era for the world’s most popular CMS\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=49548\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"https://poststatus.com/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:5170:\"<p>WordPress 5.0, &#8220;<a href=\"https://wordpress.org/news/2018/12/bebo/\">Bebo</a>,&#8221; is a shift of the highest order for the platform. Block-based editing, under the name of &#8220;Gutenberg,&#8221; is an entirely new way to publish content. It adds a world of flexibility when writing, and it opens the gates for transforming much of the broader WordPress experience moving forward.</p>\n<p></p>\n<p>TinyMCE has been the core of the WordPress writing experience for, well, forever. Users will be able to continue using TinyMCE with the <a href=\"https://wordpress.org/plugins/classic-editor/\">Classic Editor</a> plugin, which will be especially useful for those web applications with significant amounts of structured content that will take time and reprogramming to fit the new editing experience.</p>\n<p>The need for a new editor has been a wide-held concern in the WordPress community for a long time. Gutenberg has been more than two years in the making, and it involved dozens of full-time or near full-time contributors at times. Automattic, the company behind WordPress.com and other popular WordPress products, has invested a great deal in Gutenberg&#8217;s development, as have many other companies and individuals — but the bulk of development and decision-making has been by Automattic employees.</p>\n<p>There have been critiques that the process for decision making has been too closed off and rushed toward the end of the development cycle for the purpose of delivery by WordCamp US despite ongoing concerns, particularly around accessibility.</p>\n<p>5.0 had to ship eventually, and the process has been a long one. It was a complete shift from the traditional development cycles, which <a href=\"https://poststatus.com/interview-matt-mullenweg-new-wordpress-release-cycle/\">I discussed with Matt Mullenweg</a> at WordCamp US two years ago.</p>\n<p>I have personally held the view that now is as good a time as any to release 5.0, though the exact timing is a burden on folks traveling to WCUS, particularly considering that it was just a few days notice; it is putting a kink in the plans of many.</p>\n<p>Timing aside, Gutenberg is, I believe, an important step and a big test for WordPress. It is imperative that the platform evolves to be both more powerful and easier to use — an enormously difficult dual challenge that I have advocated as an important feat to accomplish for several years now.</p>\n<p>WordPress is the easiest full-featured content management system to use. But it is more difficult than many alternative publishing platforms — particularly hosted ones. Drastic changes, like Gutenberg, are necessary to continue being a preferred platform for end users. Being easy to use and customize got WordPress to the dominant position it is in today, and I believe it is extremely important to continue in that trajectory to maintain that position.</p>\n<p>At the same time, as WordPress is being used in ever more advanced applications, developers need powerful, scalable solutions. WordPress has made great strides over the years to accommodate this use case, from various APIs to assist in new data structure creation, to the REST API. Gutenberg offers much promise to continue this trend, as it is quite extendable and also flexible for deployment on the web, in native apps, and on both front-ends and backends.</p>\n<p>I believe 5.0 is a huge step forward for the platform. The journey is not without its issues, and there is much work to do, but WordPress needed and continues to need big changes and advancements to maintain its position at the top of the content management food chain.</p>\n<p>People are using WordPress for all sorts of things, whether traditional publishing, eCommerce, application frameworks, and much more. I’m excited to see what Gutenberg brings to further these applications. Strictly as an editor, it’s far from perfect, but it’s an important step in the right direction.</p>\n<h2>Get familiar with WordPress 5.0</h2>\n<p>Here are some links to places to learn more about the new editing experience and WordPress 5.0.</p>\n<ul>\n<li><a href=\"https://wordpress.org/news/2018/12/bebo/\">WordPress 5.0 release post</a></li>\n<li><a href=\"https://wordpress.org/gutenberg/handbook/\">Gutenberg designer and developer handbook</a></li>\n<li><a href=\"https://wordpress.org/gutenberg/\">WordPress.org/Gutenberg</a> teaser, where you can use it live.</li>\n<li><a href=\"https://make.wordpress.org/core/2018/12/06/wordpress-5-0-field-guide/\">WordPress 5.0 Field Guide</a></li>\n<li>Gutenberg <a href=\"https://github.com/WordPress/gutenberg\">on GitHub</a> (This will be deprecated but offers a nice history.)</li>\n<li><a href=\"https://make.wordpress.org/core/2018/12/06/the-rest-api-in-wordpress-5-0/\">Changes to the REST API</a></li>\n<li><a href=\"https://make.wordpress.org/core/2018/12/06/media-5-0-guide/\">Media in 5.0</a></li>\n<li>The <a href=\"https://make.wordpress.org/core/2018/10/16/introducing-twenty-nineteen/\">Twenty Nineteen</a> default theme and Gutenberg support <a href=\"https://make.wordpress.org/core/2018/12/06/block-editor-support-in-existing-default-themes/\">in other default themes</a>.</li>\n</ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Dec 2018 17:31:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Brian Krogsgard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:60:\"WPTavern: WPWeekly Episode 340 – Twas the Night Before 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:58:\"https://wptavern.com?p=86219&preview=true&preview_id=86219\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/wpweekly-episode-340-twas-the-night-before-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:1802:\"<p>In this episode, <a href=\"http://jjj.me\">John James Jacoby</a> and I are joined by Matt Mullenweg, co-creator of the WordPress project. We discussed a number of topics that have been making the rounds across the community such as:</p>\n<ul>\n<li>The WordPress 5.0 release strategy and how it will evolve once it&#8217;s released.</li>\n<li>Whether or not Gutenberg is ready and what ready means.</li>\n<li>Having Automatticians in project leadership roles and what roles WordPress core contributors can or will have going forward.</li>\n<li>ClassicPress, Publicious, and other forks.</li>\n<li>Gutenberg and Accessibility.</li>\n<li>Communication, feedback mechanisms, and trying to make sure everybody can participate in the conversation.</li>\n</ul>\n<p>We also talked about the long-term vision of Gutenberg. Near the end of the interview, Matt described some of the innovative things he&#8217;s seen built with the new editor.</p>\n<p>To round out the show, we sent shoutouts to Alex Mills who <a href=\"https://alex.blog/2018/11/30/my-cancer-just-wont-give-up/\">recently discovered</a> that he will need to battle through leukemia again.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Thursday, December 13th 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 #340:</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, 06 Dec 2018 03:32:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:48:\"BuddyPress: BuddyPress 4.1.0 maintenance release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=282488\";s:7:\"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/12/buddypress-4-1-0-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:332:\"<p>Immediately available is BuddyPress 4.1.0. This maintenance release fixes 3 bugs related to last week&#8217;s 4.0.0 release, and is a recommended upgrade for all BuddyPress installations.</p>\n<p>For complete details on the release, visit the <a href=\"https://codex.buddypress.org/releases/version-4-1-0/\">4.1.0 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:\"Wed, 05 Dec 2018 16:18:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"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: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:52:\"Matt: Interview on Gutenberg and Future of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=48667\";s:7:\"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://ma.tt/2018/12/interview-on-gutenberg-and-future-of-wordpress/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:863:\"<p>Yesterday I was able to have a great conversation with Adam from WP Crafter, a popular Youtube channel with over five million views. Adam said it was his first interview but you can&#8217;t tell, we had an excellent conversation that covered Gutenberg, the 5.0 release, why WordPress has done well so far, and what&#8217;s coming in the future. If you&#8217;d like more context than text or tweets can give for what&#8217;s happening in WordPress today, check it out.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Of course Friday and Saturday are <a href=\"https://2018.us.wordcamp.org\">WordCamp US</a>, which returns to Nashville this year. Everything will be live-streamed for free, including my State of the Word presentation on Saturday, you just need to <a href=\"https://2018.us.wordcamp.org/tickets/\">pick up a free streaming ticket</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, 05 Dec 2018 14:16: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:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:11;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: WordPress 5.0 Targeted for December 6, Prompting Widespread Outcry Ahead of WordCamp US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=86065\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://wptavern.com/wordpress-5-0-targeted-for-december-6-prompting-widespread-outcry-ahead-of-wordcamp-us\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7290:\"<p>During last week&#8217;s core dev chat, Matt Mullenweg urged developers to consider WordPress 5.0 as &#8220;coming as soon as possible.&#8221; Nevertheless, his decision to set Thursday, December 6, for the <a href=\"https://make.wordpress.org/core/2018/12/04/new-5-0-target-date/\" rel=\"noopener\" target=\"_blank\">new release date</a> has taken many by surprise. </p>\n<p>Official feedback channels and social media erupted with largely negative feedback on the decision, as the new release date has 5.0 landing the day before WordCamp US begins. This is a travel day for many attending the conference. It also means both of the planned follow-up releases will be expected during the upcoming weeks when many have scheduled time off for major world holidays.</p>\n<p>Yoast CEO Joost de Valk, one of the most vocal critics of the 5.0 timelime, <a href=\"https://twitter.com/yoast/status/1069880401055895553\" rel=\"noopener\" target=\"_blank\">posted a public message of dissent</a> that resonated with many on Twitter:</p>\n<blockquote><p>We vehemently disagree with the decision to release WordPress 5.0 on December 6th, and think it&#8217;s irresponsible and disrespectful towards the community. </p>\n<p>However, we&#8217;re now going to try and support the community as well as possible and we hope to show everyone that Gutenberg is indeed a huge step forward.</p></blockquote>\n<p>Although Gutenberg as a project has strong support from many large companies in the WordPress ecosystem, much of the current uproar is rooted in a communication published in early October that indicated <a href=\"https://make.wordpress.org/core/2018/10/03/proposed-wordpress-5-0-scope-and-schedule/\" rel=\"noopener\" target=\"_blank\">5.0 would be pushed to January</a> if it missed the first set of planned release dates:</p>\n<blockquote><p>We know there is a chance that 5.0 will need additional time, so these dates can slip by up to 8 days if needed. If additional time beyond that is required, we will instead aim for the following dates:</p>\n<p>Secondary RC 1: January 8, 2019</p>\n<p>Secondary Release: January 22, 2019</p>\n<p>Should we need to switch to the secondary dates, this will be communicated as soon as we’re aware.</p></blockquote>\n<p>Companies made plans based on this schedule, but after those dates passed Mullenweg was unwilling to commit to honoring the previous communication. The plan from the outset may have been to &#8220;play it by ear&#8221; and incorporate new information as it became available, but the developer community had been counting on the published deadlines to be definitive.</p>\n<p>&#8220;This decision was made in disregard to earlier specific timelines and promises, and does not take the realities on the ground into account,&#8221; Morten Rand-Hendricksen <a href=\"https://twitter.com/mor10/status/1070013237205204992?s=19\" rel=\"noopener\" target=\"_blank\">said</a>. &#8220;I agree with @yoast it is both irresponsible and disrespectful.&#8221;</p>\n<p>Although reactions on Twitter run the gamut from unbridled optimism to full on outrage, many of those commenting on the schedule have fallen into resignation, convinced that community feedback never really mattered when it came to scheduling the release.</p>\n<p>Mullenweg&#8217;s rationale behind announcing the release date with three days notice is that Gutenberg and/or the Classic Editor are already active on more than 1.3 million sites. Users do not have to upgrade to WordPress 5.0 until they are ready. If they opt for the Classic Editor, the editing experience &#8220;will be indistinguishable from 4.9.8.&#8221; </p>\n<p>Users who are informed enough to make this choice will be well-prepared when they see that 5.0 update in their dashboards. However, one of the chief concerns is that millions of WordPress users will update without testing. Plugin developers are scrambling to ship compatibility updates and support staff will need to be on hand to help users navigate any incompatibilities or bugs in the new editing experience. Hundreds of WordPress professionals will be traveling to WordCamp US when 5.0 is expected to ship, which poses challenges for supporting users who experience problems with the update.</p>\n<p>&#8220;I do not think the attendees of WCUS are more important than much larger portion of the WordPress community who does not (and cannot) attend, and there are numerous ways to deal with 5.0 before or after the 6th if that particular day is inconvenient for someone, regardless of the reason,&#8221; Mullenweg <a href=\"https://make.wordpress.org/core/2018/12/04/new-5-0-target-date/#comment-34686\" rel=\"noopener\" target=\"_blank\">said</a> in response to comments regarding the date conflicting with travel plans.</p>\n<p>The release date <a href=\"https://make.wordpress.org/core/2018/12/04/new-5-0-target-date/\" rel=\"noopener\" target=\"_blank\">announcement</a> has well over 100 comments from frustrated contributors and developers expressing concerns, and Mullenweg has been responsive in the comments. He has recently <a href=\"https://wptavern.com/mullenweg-ramps-up-communication-ahead-of-wordpress-5-0-release-rc2-now-available\" rel=\"noopener\" target=\"_blank\">ramped up communication</a> ahead of the release, regularly attending core dev chats, adding dedicated office hours to connect with the community one-on-one, and answering some of the most pressing Gutenberg questions on his blog in a lengthy but inspiring <a href=\"https://ma.tt/2018/11/a-gutenberg-faq/\" rel=\"noopener\" target=\"_blank\">FAQ post</a>. </p>\n<p>Despite these communication efforts, contributors who are not employed by Automattic have said they feel this release has been plagued by a lack of transparency regarding decision-making. Many WordPress core committers, core contributors, and former release leads have <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\">pushed back</a> on releasing before January to no avail. Their concerns and disappointments during the process hang like a dark cloud over what should be an exciting time for the future of WordPress.</p>\n<p>&#8220;No matter how bad the process around WordPress 5.0 might have been, finally setting a release date was the only right step following the RCs,&#8221; WordPress core developer Dominik Schilling <a href=\"https://twitter.com/ocean90/status/1069874387870978048\" rel=\"noopener\" target=\"_blank\">said</a>. &#8220;Let&#8217;s see if it&#8217;s also the beginning for doing it better to get back on releases which everyone will love.&#8221;</p>\n<p><a href=\"https://gemservers.com/\" rel=\"noopener\" target=\"_blank\">John Teague</a>, who runs an 11-person operation, managing 210 enterprise hosting clients, summarized how many are feeling ahead of WordPress 5.0 shipping out this week.</p>\n<p>&#8220;I so want to be supportive of this release,&#8221; Teague said. &#8220;But between the top down, heavily Automattic managed process, poor release communication, super short RC2, RC3, punting on accessibility, and now this two-day notice to 5.0 release &#8211; it reminds me of an old Air Force saying when instructors sent barely trained pilots up for their first solo:  </p>\n<p>&#8216;Send em up and let God grade em.\'&#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, 05 Dec 2018 07:37: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: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:49:\"HeroPress: WordPress made me walk 700km to Berlin\";s:7:\"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=2658\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:150:\"https://heropress.com/essays/wordpress-made-me-walk-700km-to-berlin/#utm_source=rss&utm_medium=rss&utm_campaign=wordpress-made-me-walk-700km-to-berlin\";s: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:9479:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2018/12/120518-1024x512.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: Nothing happens in your comfort zone. Go beyond and find the magic.\" /><p>Since the year 2000 I was employed at a big IT hardware/software/services firm. After about 9 years I was not feeling quite happy about how things went. Let’s say that the plans the company had with me did not really line up with the monthly reward. So, I quit and started my own company, <a href=\"https://nostromo.nl/\">nostromo.nl</a> in June 2009 (<a href=\"https://twitter.com/mbootsman/status/2090725144\">Tweetproof</a>). The goal was to serve customers by designing/developing and maintaining websites.</p>\n<h3>A new beginning</h3>\n<p>Now the challenge begins. Where do I start, who do I call? “Hello, do you need a new website? I just started my company and I can help you”. Why would I be the right person to help this company with their new website? The first thing I learned was to be sure of myself. I know what I can do and the customer needs help, probably because they are not so skillful in building websites.</p>\n<p>After a month I was talking with a potential customer, my first one (!), and I got the quotation signed. I was going to build my own CMS, and I soon realized (the hard way) that was not the way to go. I had to do a CMS comparison and WordPress won.</p>\n<h3>Here comes WordPress</h3>\n<p>The ease of use and the extensive documentation for developers convinced me. After having built numerous websites, and offering maintenance services to customers, I wanted  to know who the people were that built WordPress. Why? Well, because I was using free software and I was making money with it. That didn’t feel right, I wanted to give something back.</p>\n<p>Browsing support forums and IRC (that&#8217;s something like Slack, but without the GIFs) I quickly became aware of the WordPress community and felt I wanted to get to know these great people.</p>\n<h3>WordCamp &#8211; how it changed me</h3>\n<p>It was 2010 when I learned about a thing called WordCamp in The Netherlands. The entrance ticket was cheap and I could attend talks by inspiring people. On November 6th 2010, I was waiting in line at the registration desk. It was my turn, and someone from behind the desk said; “Hey, nostromo!”. It was <a href=\"https://twitter.com/remkusdevries\">Remkus de Vries</a>, he recognized me from my avatar on Twitter and those two words made me feel welcome immediately. This moment I remember very vividly and it marks the point where my enthusiasm for the WordPress community was sparked to life.</p>\n<h3>I volunteer &#8211; a lot</h3>\n<p>Giving back to the community got defined. Translating, helping out in the Dutch official WordPress support forum, organizing meetups/WordCamps (The Netherlands, the first WordCamp Europe, and WordCamp Rotterdam) and helping others join and be active in the WordPress community. These were some of the things I did, and yes, I had to push the brake on voluntary jobs sometimes, because I also needed to be productive and profitable in my business. Since that first WordCamp I have met amazing, inspiring and skillful people (in random order). I haven’t met new people, I met new friends.</p>\n<h3>Volunteering &#8211; taking it to the next level</h3>\n<p>It was June 4th 2018 when I got a weird idea. Yeah, that sometimes happens. Impulsive as I am, I tweeted it:</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">I&#039;m thinking about walking to the next <a href=\"https://twitter.com/hashtag/WCEU?src=hash&ref_src=twsrc%5Etfw\">#WCEU</a>. Needs some planning of course, and funding / sponsoring. Will launch a separate website after this years edition.</p>\n<p>&mdash; <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f6b6-1f3fc-200d-2642-fe0f.png\" alt=\"🚶🏼‍♂️\" class=\"wp-smiley\" /> Marcel Bootsman (@mbootsman) <a href=\"https://twitter.com/mbootsman/status/1003666255994376192?ref_src=twsrc%5Etfw\">June 4, 2018</a></p></blockquote>\n<p></p>\n<p>Little did I know, there was a body part that had a big objection. While planning to go to Belgrade for WordCamp Europe 2018 this happened:</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Good morning. Going to see doctor later, I have a sore knee and walking is merely possible. Great timing, body&#8230; <a href=\"https://twitter.com/hashtag/WCEU?src=hash&ref_src=twsrc%5Etfw\">#WCEU</a></p>\n<p>&mdash; <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f6b6-1f3fc-200d-2642-fe0f.png\" alt=\"🚶🏼‍♂️\" class=\"wp-smiley\" /> Marcel Bootsman (@mbootsman) <a href=\"https://twitter.com/mbootsman/status/1006400794617352192?ref_src=twsrc%5Etfw\">June 12, 2018</a></p></blockquote>\n<p></p>\n<p>And yes, I had to cancel our trip (my wife was going to join) and ended up laying in bed for about a week with an inflamed knee. I received antibiotics from the doctor and gladly the pain and inflammation disappeared. That aside, at the end of WCEU 2018 it was announced that WCEU 2019 was going to be in Berlin. I was happy, since that’s really close (about 700 km) to where I live.</p>\n<p>Currently I am training, I’ve planned my route and I am looking for places to sleep in Germany. Please see this website <a href=\"http://walktowc.eu\">walktowc.eu</a> for more information. Since this hike is probably going to gain some attention in the community, I had another idea. Why not use this as a means to raise money, for a good cause. Walking 700 km in about 30 days is a challenge, and if I can get enough attention, raising money might work out. Now I just had to find a good cause to raise money for&#8230;</p>\n<h3>Raising funds for DonateWC</h3>\n<p>I have known <a href=\"https://twitter.com/motherofcode\">Ines van Essen</a> for a few years now and in September 2017 she started a thing called <a href=\"https://donatewc.org/\">DonateWC</a>. After a successful initial funding campaign they sent their first recipient to <a href=\"https://donatewc.org/sponsorship-recipients/were-sending-a-speaker-to-wordcamp-cape-town/\">WordCamp Capetown</a> in October 2017. Seeing this made me believe this is another sign of how friendly and supporting the WordPress community is, to make sure that people are able to attend WordCamps, while they do not have the financial means to do so. The community supports community members, and that’s the reason why I chose DonateWC as the cause I’m going to raise funds for. And as a side effect also raise awareness of the existence of DonateWC.</p>\n<h3>My message to you</h3>\n<p>Don’t feel obliged to do things you don’t like.</p>\n<p>Do things you like.</p>\n<p>Start volunteering.</p>\n<p>Build your network.</p>\n<p>Enjoy the community.</p>\n<p>Step (or walk) out of your comfort zone.</p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Nothing happens in your comfort zone. Go beyond and find the magic. <a href=\"https://t.co/Rm4zDtT5JL\">pic.twitter.com/Rm4zDtT5JL</a></p>\n<p>&mdash; <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f6b6-1f3fc-200d-2642-fe0f.png\" alt=\"🚶🏼‍♂️\" class=\"wp-smiley\" /> Marcel Bootsman (@mbootsman) <a href=\"https://twitter.com/mbootsman/status/971276691447386120?ref_src=twsrc%5Etfw\">March 7, 2018</a></p></blockquote>\n<p></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: WordPress made me walk 700km to Berlin\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=WordPress%20made%20me%20walk%20700km%20to%20Berlin&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fwordpress-made-me-walk-700km-to-berlin%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: WordPress made me walk 700km to Berlin\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fwordpress-made-me-walk-700km-to-berlin%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%2Fwordpress-made-me-walk-700km-to-berlin%2F&title=WordPress+made+me+walk+700km+to+Berlin\" rel=\"nofollow\" target=\"_blank\" title=\"Share: WordPress made me walk 700km to Berlin\"></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/wordpress-made-me-walk-700km-to-berlin/&media=https://heropress.com/wp-content/uploads/2018/12/120518-150x150.jpg&description=WordPress made me walk 700km to Berlin\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: WordPress made me walk 700km to Berlin\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/essays/wordpress-made-me-walk-700km-to-berlin/\" title=\"WordPress made me walk 700km to Berlin\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/wordpress-made-me-walk-700km-to-berlin/\">WordPress made me walk 700km to Berlin</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, 05 Dec 2018 07:00:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Marcel Bootsman\";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:27:\"Dev Blog: WordPress 5.0 RC3\";s:7:\"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=6322\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2018/12/wordpress-5-0-rc3/\";s: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:2755:\"<p>The third release candidate for WordPress 5.0 is now available!</p>\n\n\n\n<p><strong>WordPress 5.0 will be released on </strong><a href=\"https://make.wordpress.org/core/2018/12/04/new-5-0-target-date/\"><strong>December 6, 2018</strong></a>. This is a big release and needs&nbsp;<em>your</em>&nbsp;help—if you haven’t tried 5.0 yet, now is the time!</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-RC3.zip\">download the release candidate here</a>&nbsp;(zip).</p>\n\n\n\n<p>For details about what to expect in WordPress 5.0, please see the&nbsp;<a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-release-candidate/\">first release candidate post</a>.</p>\n\n\n\n<p>This release candidate includes a fix for some scripts not loading on subdirectory installs (<a href=\"https://core.trac.wordpress.org/ticket/45469\">#45469</a>), and user locale settings not being loaded in the block editor (<a href=\"https://core.trac.wordpress.org/ticket/45465\">#45465</a>). Twenty Nineteen has also had a couple of minor tweaks.</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&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a>&nbsp;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>If you think you’ve found a bug, you can post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a>&nbsp;in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;<a href=\"https://make.wordpress.org/core/reports/\">file one on WordPress Trac</a>, where you can also find&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">a list of known bugs</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>WordPress Five Point Oh<br />Is just a few days away!<br />Nearly party time!</em> <img src=\"https://s.w.org/images/core/emoji/11/72x72/1f389.png\" alt=\"🎉\" class=\"wp-smiley\" /></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Dec 2018 07:07:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"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: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:87:\"WPTavern: New Block Gallery Plugin Offers a Suite of Photo Gallery Blocks for 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=85195\";s:7:\"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/new-block-gallery-plugin-offers-a-suite-of-photo-gallery-blocks-for-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:3116:\"<p>The new Gutenberg editor has basic support for galleries with a few nice features, such as the ability to set the number of columns and automatically crop thumbnails for a more uniform appearance. If you need more control over your galleries, Rich Tabor&#8217;s <a href=\"https://wordpress.org/plugins/block-gallery/\" rel=\"noopener\" target=\"_blank\">Block Gallery</a> plugin is currently the best option made specifically for use with Gutenberg and WordPress 5.0+. It offers a suite of photo gallery blocks with minimal, tasteful styling that fits unobtrusively into virtually any site design. </p>\n<p>Block Gallery currently offers three different blocks, including masonry, fullscreen stacked, and a carousel slider. Each block has its own settings that offer more customization for the specific gallery type.</p>\n<p><a href=\"https://i2.wp.com/wptavern.com/wp-content/uploads/2018/10/Screen-Shot-2018-12-03-at-3.19.46-PM.png?ssl=1\"><img /></a></p>\n<p>The plugin also makes use of Gutenberg&#8217;s block transform utility to allow users to seamlessly transform galleries from one style to another with one click, as demonstrated in the video below.</p>\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>A demo of the new <a href=\"https://wordpress.org/plugins/block-gallery/\">Block Gallery WordPress Plugin</a>\n<p>&#8220;I built the Block Gallery plugin originally as a proving ground for exploring how my portfolio WordPress themes at ThemeBeans will interface with Gutenberg,&#8221; <a href=\"https://themebeans.com/\" rel=\"noopener\" target=\"_blank\">ThemeBeans</a> founder Rich Tabor said. &#8220;I do not particularly like the idea of disabling the block editor on portfolio custom post types, so I wanted to find a clever way for folks to use different sorts of galleries to showcase their art, illustrations, photos, etc. Block Gallery was born out of that exploration.&#8221;  </p>\n<p>Tabor said that although the core gallery block is much more robust than the classic editor’s gallery system, he wanted to give users more flexibility in how they display media. His favorite feature of the project is the ability to morph gallery blocks into different types.</p>\n<p>&#8220;That means every image, settings, display option, and color selection are each migrated instantly — if a user swaps out a selected gallery for a different type,&#8221; Tabor said. &#8220;For instance, folks can morph from a masonry gallery to a carousel slider in a single click, without having to re-upload/assign images or select any options. It’s all done behind the scenes, automagically.&#8221;</p>\n<p>Tabor&#8217;s Block Gallery plugin is a major leap forward for galleries in terms of usability. It offers a beautiful implementation of features that would have been difficult to imagine before the block editor. <a href=\"https://wordpress.org/plugins/block-gallery/\" rel=\"noopener\" target=\"_blank\">Block Gallery</a> currently has more than 400 active installs after a little more than month in the official directory. Watch for that number to jump as more people begin using the new editor when WordPress 5.0 is released. </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, 03 Dec 2018 22:29: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: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:47:\"Dev Blog: The Month in WordPress: November 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=6318\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2018/12/the-month-in-wordpress-november-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:6607:\"<p>WordPress 5.0 is almost ready for release, including an all-new content editing experience. Volunteers all across the project are gearing up for the launch and making sure everything is ready. Read on to find out what&#8217;s been happening and how you can get involved.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.0 Close to Launch</h2>\n\n\n\n<p>The release date for WordPress 5.0 has not yet been set, but the second release candidate (RC) <a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-rc2/\">is now available</a>. The final release date will be determined based on feedback and testing of this RC. The Core development team has been posting <a href=\"https://make.wordpress.org/core/2018/12/03/5-0-gutenberg-status-update-dec-3/\">daily updates</a> on the progress of their work on v5.0, with the number of open issues for this release decreasing every day.<br /></p>\n\n\n\n<p>The primary feature of this release is <a href=\"https://wordpress.org/gutenberg/\">the new editor</a> that will become the default WordPress experience going forward. A number of people have been seeking more direct feedback from the release leads about the progress of this release, which <a href=\"https://profiles.wordpress.org/matt/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>matt</a> has facilitated by hosting <a href=\"https://make.wordpress.org/core/2018/11/29/gutenberg-5-0-listening-office-hours/\">one-to-one discussions</a> with anyone in the community who wanted to talk with him about it. He has also published <a href=\"https://ma.tt/2018/11/a-gutenberg-faq/\">an extended FAQ</a> covering many of the questions people have been asking.<br /></p>\n\n\n\n<p>Alongside the development of the new editor, the Mobile team has been working hard to bring the WordPress mobile apps up to speed. They plan to make a beta version available <a href=\"https://make.wordpress.org/mobile/2018/11/15/gutenberg-in-the-apps-what-to-expect/\">in February 2019</a>.<br /></p>\n\n\n\n<p>Want to get involved in developing WordPress Core in 5.0 and beyond? Follow <a href=\"https://make.wordpress.org/core\">the Core team blog</a> and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>New WordPress Support Platform Goes Live</h2>\n\n\n\n<p>WordPress user documentation has long been hosted on the <a href=\"https://codex.wordpress.org/\">WordPress Codex</a>, but for the past couple of years an ambitious project has been underway to move that content to a freshly-built WordPress-based platform. This project, named “HelpHub,” is now live and <a href=\"https://wordpress.org/support/\">the official home of WordPress Support</a>.<br /></p>\n\n\n\n<p>There is still plenty of content that needs to be migrated from the Codex to HelpHub, but the initial move is done and the platform is ready to have all WordPress’ user documentation moved across. HelpHub will be the first place for support, encouraging users to find solutions for themselves before posting in the <a href=\"https://wordpress.org/support/forums/\">forums</a>.<br /></p>\n\n\n\n<p>Want to get involved in populating HelpHub with content, or with its future development? Follow <a href=\"https://make.wordpress.org/docs/\">the Documentation team blog</a> and join the #docs channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Spanish WordPress Community Pushes Translations Forward</h2>\n\n\n\n<p>The WordPress community in Spain has been hard at work making sure as much of the WordPress project as possible is available in Spanish. <a href=\"https://es.wordpress.org/2018/11/07/logros-equipo-traducciones-wordpress-espana/\">They have recently translated more of the project than ever</a> — including WordPress Core, WordPress.org, the mobile apps and the top 120 plugins in the Directory.<br /></p>\n\n\n\n<p>This achievement has largely been possible due to the fact that <a href=\"https://make.wordpress.org/polyglots/teams/?locale=es_ES\">the Spanish translation team</a> has over 2,500 individuals contributing to it, making it the largest translation team across the whole project. <br /></p>\n\n\n\n<p>Want to get involved in translating WordPress into your local language? You can <a href=\"https://translate.wordpress.org/\">jump straight into translations</a>, follow <a href=\"https://make.wordpress.org/polyglots/\">the Polyglots team blog</a> and join the #polyglots channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li>All volunteer teams have checked in with their <a href=\"https://wordpress.org/news/2018/11/quarterly-updates-q3-2018/\">latest quarterly updates</a>.</li><li>The WordPress Support Team <a href=\"https://make.wordpress.org/support/2018/11/new-volunteer-orientation-for-wp-support-contributors-dec-9/\">is hosting an orientation</a> for new Support volunteers on December 9.</li><li><a href=\"https://2018.us.wordcamp.org/tickets/\">Tickets are now available</a> to watch the WordCamp US livestream for free.</li><li>WordPress Core <a href=\"https://core.trac.wordpress.org/ticket/45287\">has switched to a WP-CLI command</a> for generating localization files.</li><li>WordPress Coding Standards v1.2.0 <a href=\"https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/releases/tag/1.2.0\">has been released</a> with some really useful improvements.</li><li>The first ever <a href=\"https://2019.nordic.wordcamp.org/\">WordCamp Nordic</a> is taking place on March 7-8, 2019 with ticket sales now open.</li><li>The WordCamp Incubator program is going very well this year — <a href=\"https://make.wordpress.org/community/2018/11/27/wordcamp-incubator-2018-update-thread-november-edition/\">you can see the latest updates here</a>.</li><li>The Mobile Team is looking for testers for the upcoming v11.3 release of the WordPress mobile apps on <a href=\"https://make.wordpress.org/mobile/2018/11/21/call-for-testing-wordpress-for-android-11-3/\">Android</a> and <a href=\"https://make.wordpress.org/mobile/2018/11/21/call-for-testing-wordpress-for-ios-11-3/\">iOS</a>.</li><li>The WordCamp Europe team is looking for local communities to <a href=\"https://2019.europe.wordcamp.org/2018/11/29/call-for-host-city/\">apply to be the host city</a> for the 2020 event.</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:\"Mon, 03 Dec 2018 17:43:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:16;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"WPTavern: WordCamp Europe Opens the Call for Host City 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=86110\";s:7:\"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-europe-opens-the-call-for-host-city-2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2379:\"<p><a href=\"https://i1.wp.com/wptavern.com/wp-content/uploads/2018/11/wordcamp-eurpoe-2019.png?ssl=1\"><img /></a></p>\n<p>WordCamp Europe has opened the <a href=\"https://2019.europe.wordcamp.org/2018/11/29/call-for-host-city/\" rel=\"noopener\" target=\"_blank\">call for a host city for 2020</a>. Previous editions of the event have been held in Leiden, Sofia, Seville, Vienna, Paris, and Belgrade, and the next on deck is Berlin in 2019. Organizers are always working ahead for an event this size. In fact, the team plans together for the better part of a year before attendees arrive for the three-day event. The upcoming WCEU is currently being planned by a team of 66 organizers from 15 countries. </p>\n<p>Teams applying to host WordCamp Europe are required to have organized at least one or more successful WordCamps in a European city, with at least one recent one held in 2017 or 2018. The core organizing team will work with all applicants in the open to help them prepare the best applications possible, as detailed in the announcement:  </p>\n<blockquote><p>To guarantee total transparency during the process, all applicants receive the same help in the appropriate public channel of the WCEU Slack workspace. No question is considered or answered in a private message.</p></blockquote>\n<p>Three weekends in June 2020 are available to applicants as potential dates. Teams interested to apply are encouraged to begin filling out the <a href=\"https://docs.google.com/forms/d/e/1FAIpQLSfPd5InsSfaGXA1zRu_PJ435AGXXPlUYMuCqCBkEOKRNSrd7w/viewform\" rel=\"noopener\" target=\"_blank\">7-page survey</a> (which can be started and completed as information becomes available). It includes questions about the local community, previous WordCamps, possible venue(s), cost of living in the city, and other data that will be important to the selection committee. </p>\n<p>A preliminary online AMA session will be held December 13, 2018, to assist teams in answering questions about the application process. The deadline to apply to host the event is February 28, 2019. Applicants will receive a decision by March 15, 2019, and the final selection will be announced during the closing remarks in Berlin next June. Check out the call for host cities <a href=\"https://2019.europe.wordcamp.org/2018/11/29/call-for-host-city/\" rel=\"noopener\" target=\"_blank\">announcement</a> for more information.</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, 03 Dec 2018 16:45:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:92:\"WPTavern: Mullenweg Ramps Up Communication Ahead of WordPress 5.0 Release, RC2 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=86090\";s:7:\"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/mullenweg-ramps-up-communication-ahead-of-wordpress-5-0-release-rc2-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:5209:\"<p><a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-rc2/\" rel=\"noopener\" target=\"_blank\">WordPress 5.0 RC2</a> was released today with 15 notable updates, including improvements to block preview styling, browser-specific bug fixes, and other changes. RC2 was released simultaneously with <a href=\"https://make.wordpress.org/core/2018/11/30/whats-new-in-gutenberg-30th-november/\" rel=\"noopener\" target=\"_blank\">Gutenberg version 4.6</a>. </p>\n<p>The official release date for WordPress 5.0 has not yet been announced, because it depends on feedback from RC2 testing. Contributors&#8217; uneasiness with not having an official release date seemed to reach a critical tipping point during this week&#8217;s WordPress dev chat, as many participants pressured Matt Mullenweg, who is leading the release, to give more information on when they can expect 5.0. </p>\n<p>&#8220;It is very important that we have a release date to aim for,&#8221; ACF founder Elliot Condon said. &#8220;I’m finding the current &#8216;waiting game&#8217; quite stressful, and I suspect a few other developers will share the same feeling.&#8221;</p>\n<p>Tensions were high as contributors cited various reasons for wanting a date, including companies needing support staff on hand, upcoming holidays, documentation planning, and the importance of user trust.</p>\n<p>&#8220;We&#8217;re determining the release date based on the open issues,&#8221; Mullenweg said. &#8220;Please consider it as coming as soon as possible, when everything is resolved.&#8221;</p>\n<p>&#8220;I hope it&#8217;s clear we&#8217;re trying to get this out as soon as possible, but don&#8217;t yet have enough data to announce an official date. As mentioned last week we have done a number of December releases in the past, and may this time, but don&#8217;t have enough data to announce a new date yet.&#8221;</p>\n<p>Mullenweg also urged dev chat attendees to keep in mind that any site administrators can install the Classic Editor plugin to keep the current editing experience, regardless of the 5.0 release date. He said the date will be announced via a P2 post, not during a dev chat.</p>\n<p>&#8220;If you want to know what to plan on, please don&#8217;t hold anything back based on expected dates, please test or deploy the RCs, that&#8217;s what they&#8217;re for,&#8221; Mullenweg said. </p>\n<p>In the meantime, Mullenweg is spending the weekend taking questions from the community during <a href=\"https://make.wordpress.org/core/2018/11/29/gutenberg-5-0-listening-office-hours/\" rel=\"noopener\" target=\"_blank\">24 office hours slots</a>. He also published a lengthy post titled &#8220;<a href=\"https://ma.tt/2018/11/a-gutenberg-faq/\" rel=\"noopener\" target=\"_blank\">WordPress 5.0: A Gutenberg FAQ</a>,&#8221; which reaffirms WordPress&#8217; mission in the context of Gutenberg. It answers questions like &#8220;Why do we need Gutenberg at all?&#8221; and &#8220;Why blocks?&#8221;</p>\n<p>&#8220;I knew we would be taking a big leap,&#8221; Mullenweg said. &#8220;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.&#8221;</p>\n<p>The stats Mullenweg cited about previously having 9 major WordPress releases in December (34% of all releases in the last decade) indicate that a December release may still be on the table. His post addresses the perceived urgency behind getting Gutenberg out the door and into the hands of users. In evaluating WordPress 5.0&#8217;s readiness, he said it&#8217;s important to differentiate between the code being ready and the community being ready.</p>\n<p>&#8220;In the recent debate over Gutenberg readiness, I think it’s important to understand the difference between Gutenberg being ready code-wise (it is now), and whether the entire community is ready for Gutenberg,&#8221; Mullenweg said.</p>\n<p>&#8220;It will take some time — we’ve had 15 years to polish and perfect core, after all — but the global WordPress community has some of the world’s most talented contributors and we can make it as good as we want to make it.&#8221;</p>\n<p>The post also offers a preview of where Gutenberg is going in the next site customization phase and how it will change the way users build their sites.</p>\n<p>&#8220;The Editor is just the start,&#8221; he said. &#8220;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.&#8221;</p>\n<p>Mullenweg said he plans to talk more about the next phases following site customization during the State of the Word address at WordCamp US. If you have questions about Gutenberg and where it&#8217;s headed, the comments are open on his <a href=\"https://ma.tt/2018/11/a-gutenberg-faq/\" rel=\"noopener\" target=\"_blank\">post</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 01 Dec 2018 03:15: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: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:67:\"WPTavern: Let Us Know If You’re Hosting a WordCamp US Watch Party\";s:7:\"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=86150\";s:7:\"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:75:\"https://wptavern.com/let-us-know-if-youre-hosting-a-wordcamp-us-watch-party\";s: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:505:\"<p>WordCamp US is next weekend and if you&#8217;re unable to attend, you can watch from home via the <a href=\"https://wptavern.com/wordcamp-us-2018-livestream-tickets-now-available\">free livestream</a>. However, some WordPress meetup groups host watch parties. These parties generally include food, beverages, and a large projection screen. </p>\n\n\n\n<p>If you&#8217;re hosting one of these parties, please let us know about it in the comments. Tell us the location and what attendees can expect. <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:\"Sat, 01 Dec 2018 01:11:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:27:\"Dev Blog: WordPress 5.0 RC2\";s:7:\"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=6287\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2018/11/wordpress-5-0-rc2/\";s: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:3298:\"<p>The second 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. A final release date will be announced soon, based on feedback from this release candidate. Things are appearing very stable and we hope to announce a date soon. This is a big release and needs <em>your</em> help—if you haven’t tried 5.0 yet, now is the time! </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-RC2.zip\">download the release candidate here</a>&nbsp;(zip).</p>\n\n\n\n<p>For details about what to expect in WordPress 5.0, please see the <a href=\"https://wordpress.org/news/2018/11/wordpress-5-0-release-candidate/\">previous release candidate post</a>.</p>\n\n\n\n<h2>Significant changes</h2>\n\n\n\n<ul><li>We stopped rendering&nbsp;<em>AdminNotices</em>&nbsp;compatibility component, as this previous attempt at backward compatibility was bringing in numerous incompatible banners and notices from plugins.</li><li>An update to the parser to better deal with malformed HTML that could cause a loop. We&#8217;re only aware of this in the wild being triggered once in the <a href=\"https://gutenstats.blog/\">over a million posts</a> made with Gutenberg, but it caused a loop so we wanted to fix for RC2.</li></ul>\n\n\n\n<h2>Cosmetic and minor changes in RC2</h2>\n\n\n\n<ul><li>Accessibility: Simplify sidebar tabs&nbsp;aria-labels.</li><li>Make the&nbsp;Image&nbsp;Link URL field readonly.</li><li>Internationalization: Merge&nbsp;similar text strings that differed only in capitalization.</li><li>CSS: Improve block preview&nbsp;styling.</li><li>CSS: Fix&nbsp;visual issues&nbsp;with&nbsp;Button&nbsp;block text wrap.</li><li>Fix&nbsp;getSelectedBlockClientId selector.</li><li>Fix&nbsp;Classic&nbsp;block&nbsp;not showing galleries on a grid.</li><li>Fix an issue where the block toolbar&nbsp;would cause an image to jump&nbsp;downwards when the&nbsp;<em>wide</em>&nbsp;or&nbsp;<em>full</em>&nbsp;alignments were activated.</li><li>Move editor specific styles&nbsp;from style.scss to editor.scss in&nbsp;Cover&nbsp;block.</li><li>Fix modals&nbsp;in Microsoft Edge browser.</li><li>Fix Microsoft IE11 focus loss&nbsp;after TinyMCE init.&nbsp;Add&nbsp;IE check.</li><li>Fix Microsoft IE11 input when mounting TinyMCE.</li><li>Change @package names&nbsp;to WordPress.</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>If you think you’ve found a bug, you can post to the <a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, <a href=\"https://make.wordpress.org/core/reports/\">file one on WordPress Trac</a>, where you can also find <a href=\"https://core.trac.wordpress.org/tickets/major\">a list of known bugs</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<pre class=\"wp-block-verse\"><em>RC bittersweet.<br />We welcome in Gutenberg,<br />Vale Gutenbeard.</em></pre>\";s: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 23:16: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: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: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: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: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: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:18327:\"<p><em>Update: </em><a href=\"https://wordpress.org/news/2018/12/bebo/\"><em>On December 6th we released WordPress 5.0</em></a><em>. It was definitely the most controversial release in a while, but the usage and adoption metrics are looking similar to previous releases. I&#8217;m looking forward to continuing to iterate on the new block editor!</em></p>\n\n\n\n<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: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: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: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: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: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: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: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: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: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: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:1360:\"<p><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></p>\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: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: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: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: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: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: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: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: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: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: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:9944:\"<p><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></p>\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: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: 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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: 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: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: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: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: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: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: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: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: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: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: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: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: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:\"\";}}}}}}}}}}}}}}}}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:\"Wed, 12 Dec 2018 19:06:36 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Wed, 12 Dec 2018 18:45:29 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20130911060210\";}', 'no');
