-- Softaculous SQL Dump
-- http://www.softaculous.com
--




--
-- Database: `a1design_wp293`
--

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

--
-- Table structure for table `wpo1_commentmeta`
--

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

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

--
-- Table structure for table `wpo1_comments`
--

CREATE TABLE `wpo1_comments` (
  `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0',
  `comment_author` tinytext COLLATE utf8mb4_unicode_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',
  `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0',
  `user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`comment_ID`),
  KEY `comment_post_ID` (`comment_post_ID`),
  KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
  KEY `comment_date_gmt` (`comment_date_gmt`),
  KEY `comment_parent` (`comment_parent`),
  KEY `comment_author_email` (`comment_author_email`(10))
) ENGINE=InnoDB  DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wpo1_comments`
--

INSERT INTO `wpo1_comments` VALUES
(1, 1, 'A WordPress Commenter', 'wapuu@wordpress.example', 'https://wordpress.org/', '', '2021-06-29 17:11:40', '2021-06-29 17:11:40', 'Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from <a href="https://gravatar.com">Gravatar</a>.', 0, '0', '', 'comment', 0, 0);

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

--
-- Table structure for table `wpo1_links`
--

CREATE TABLE `wpo1_links` (
  `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `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 '',
  PRIMARY KEY (`link_id`),
  KEY `link_visible` (`link_visible`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

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

--
-- Table structure for table `wpo1_options`
--

CREATE TABLE `wpo1_options` (
  `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `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',
  PRIMARY KEY (`option_id`),
  UNIQUE KEY `option_name` (`option_name`),
  KEY `autoload` (`autoload`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;


INSERT INTO `wpo1_options` VALUES
(292, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1625109571', 'no'),
(293, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1625066371', 'no'),
(336, 'category_children', 'a:0:{}', 'yes'),
(456, 'recently_activated', 'a:0:{}', 'yes'),
(462, '_site_transient_update_plugins', 'O:8:"stdClass":5:{s:12:"last_checked";i:1625075173;s:7:"checked";a:3:{s:19:"akismet/akismet.php";s:5:"4.1.9";s:51:"all-in-one-wp-migration/all-in-one-wp-migration.php";s:4:"7.44";s:9:"hello.php";s:5:"1.7.2";}s:8:"response";a:0:{}s:12:"translations";a:0:{}s:9:"no_update";a:3:{s:19:"akismet/akismet.php";O:8:"stdClass":9:{s:2:"id";s:21:"w.org/plugins/akismet";s:4:"slug";s:7:"akismet";s:6:"plugin";s:19:"akismet/akismet.php";s:11:"new_version";s:5:"4.1.9";s:3:"url";s:38:"https://wordpress.org/plugins/akismet/";s:7:"package";s:56:"https://downloads.wordpress.org/plugin/akismet.4.1.9.zip";s:5:"icons";a:2:{s:2:"2x";s:59:"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272";s:2:"1x";s:59:"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272";}s:7:"banners";a:1:{s:2:"1x";s:61:"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904";}s:11:"banners_rtl";a:0:{}}s:51:"all-in-one-wp-migration/all-in-one-wp-migration.php";O:8:"stdClass":9:{s:2:"id";s:37:"w.org/plugins/all-in-one-wp-migration";s:4:"slug";s:23:"all-in-one-wp-migration";s:6:"plugin";s:51:"all-in-one-wp-migration/all-in-one-wp-migration.php";s:11:"new_version";s:4:"7.44";s:3:"url";s:54:"https://wordpress.org/plugins/all-in-one-wp-migration/";s:7:"package";s:71:"https://downloads.wordpress.org/plugin/all-in-one-wp-migration.7.44.zip";s:5:"icons";a:2:{s:2:"2x";s:76:"https://ps.w.org/all-in-one-wp-migration/assets/icon-256x256.png?rev=2458334";s:2:"1x";s:76:"https://ps.w.org/all-in-one-wp-migration/assets/icon-128x128.png?rev=2458334";}s:7:"banners";a:2:{s:2:"2x";s:79:"https://ps.w.org/all-in-one-wp-migration/assets/banner-1544x500.jpg?rev=2538919";s:2:"1x";s:78:"https://ps.w.org/all-in-one-wp-migration/assets/banner-772x250.png?rev=2538919";}s:11:"banners_rtl";a:0:{}}s:9:"hello.php";O:8:"stdClass":9:{s:2:"id";s:25:"w.org/plugins/hello-dolly";s:4:"slug";s:11:"hello-dolly";s:6:"plugin";s:9:"hello.php";s:11:"new_version";s:5:"1.7.2";s:3:"url";s:42:"https://wordpress.org/plugins/hello-dolly/";s:7:"package";s:60:"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip";s:5:"icons";a:2:{s:2:"2x";s:64:"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855";s:2:"1x";s:64:"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855";}s:7:"banners";a:1:{s:2:"1x";s:66:"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855";}s:11:"banners_rtl";a:0:{}}}}', 'no'),
(463, 'ai1wm_secret_key', 'Bh2Tc7aR4VxB', 'yes'),
(464, 'ai1wm_status', 'a:2:{s:4:"type";s:8:"download";s:7:"message";s:352:"<a href="https://yueding.a1design.com.hk/wp-content/ai1wm-backups/yueding.a1design.com.hk-20210630-010730-ah6i3u.wpress" class="ai1wm-button-green ai1wm-emphasize ai1wm-button-download" title="yueding.a1design.com.hk" download="yueding.a1design.com.hk-20210630-010730-ah6i3u.wpress"><span>Download yueding.a1design.com.hk</span><em>Size: 27 MB</em></a>";}', 'yes'),
(541, '_site_transient_ai1wm_last_check_for_updates', '1625075172', 'no'),
(542, 'ai1wm_updater', 'a:0:{}', 'yes'),
(548, '_site_transient_timeout_community-events-fe2656db21032b703129e44e916ac562', '1625084147', 'no'),
(549, '_site_transient_community-events-fe2656db21032b703129e44e916ac562', 'a:4:{s:9:"sandboxed";b:0;s:5:"error";N;s:8:"location";a:1:{s:2:"ip";s:11:"49.131.83.0";}s:6:"events";a:2:{i:0;a:10:{s:4:"type";s:6:"meetup";s:5:"title";s:45:"Discussion Group: Introduction to Open-Source";s:3:"url";s:68:"https://www.meetup.com/learn-wordpress-discussions/events/279064366/";s:6:"meetup";s:27:"Learn WordPress Discussions";s:10:"meetup_url";s:51:"https://www.meetup.com/learn-wordpress-discussions/";s:4:"date";s:19:"2021-06-30 02:00:00";s:8:"end_date";s:19:"2021-06-30 03:00:00";s:20:"start_unix_timestamp";i:1625043600;s:18:"end_unix_timestamp";i:1625047200;s:8:"location";a:4:{s:8:"location";s:6:"Online";s:7:"country";s:2:"US";s:8:"latitude";d:37.7799987792970028976924368180334568023681640625;s:9:"longitude";d:-122.419998168950002082056016661226749420166015625;}}i:1;a:10:{s:4:"type";s:6:"meetup";s:5:"title";s:118:"WordPress Meetup #54: 區塊編輯器【Block Editor】基礎應用和相關 SEO 結構化資料 (Cantonese 廣東話)";s:3:"url";s:67:"https://www.meetup.com/Hong-Kong-WordPress-Meetup/events/279081463/";s:6:"meetup";s:26:"Hong Kong WordPress Meetup";s:10:"meetup_url";s:50:"https://www.meetup.com/Hong-Kong-WordPress-Meetup/";s:4:"date";s:19:"2021-07-20 11:00:00";s:8:"end_date";s:19:"2021-07-20 12:00:00";s:20:"start_unix_timestamp";i:1626750000;s:18:"end_unix_timestamp";i:1626753600;s:8:"location";a:4:{s:8:"location";s:6:"Online";s:7:"country";s:2:"HK";s:8:"latitude";d:22.2700004577639987246584496460855007171630859375;s:9:"longitude";d:114.139999389650000694018672220408916473388671875;}}}}', 'no'),
(550, '_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3', '1625084149', 'no'),
(551, '_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:27:"News –  – 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:"link";a:1:{i:0;a:5:{s:4:"data";s:26:"https://wordpress.org/news";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 30 Jun 2021 03:47: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:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:40:"https://wordpress.org/?v=5.9-alpha-51272";s:7:"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:63:"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 5.8 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:67:"https://wordpress.org/news/2021/06/wordpress-5-8-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 30 Jun 2021 03:47: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:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"5.8";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10873";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:364:"The first release candidate for WordPress 5.8 is now available! 🎉 Please join us in celebrating this very important milestone in the community&#8217;s progress towards the final release of WordPress 5.8! “Release Candidate” means the new version is ready for release, but with thousands of plugins and themes and differences in how the millions of [&#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:12:"Jeffrey Paul";s: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:4776:"\n<p>The first release candidate for <a href="https://make.wordpress.org/core/5-8/">WordPress 5.8</a> is now available! <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f389.png" alt="🎉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n\n\n\n<p>Please join us in celebrating this very important milestone in the community&#8217;s progress towards the final release of WordPress 5.8!</p>\n\n\n\n<p>“Release Candidate” means the new version is ready for release, but with thousands of plugins and themes and differences in how the millions of people use WordPress, it is possible something was missed.  WordPress 5.8 is slated for release&nbsp;on&nbsp;<strong>July 20, 2021</strong>, but <em>your</em>&nbsp;help is needed to get there—if you have not tried 5.8 yet,&nbsp;<strong>now is the time</strong>!</p>\n\n\n\n<p>You can test the WordPress 5.8 release candidate in three ways:</p>\n\n\n\n<ul><li>Install and activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (select the <code>Bleeding edge</code> channel and then <code>Beta/RC Only</code> stream)</li><li>Directly download the release candidate version <a href="https://wordpress.org/wordpress-5.8-RC1.zip">(zip)</a></li><li>Using WP-CLI to test: <code>wp core update --version=5.8-RC1</code></li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta releases and gave feedback.  Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>What is in WordPress 5.8?</h2>\n\n\n\n<p>The second release of 2021 continues to progress on the block editor towards the promised future of full site editing with these updates:</p>\n\n\n\n<ul><li>Manage Widgets with Blocks</li><li>Display Posts with New Blocks and Patterns</li><li>Edit Post Templates</li><li>Overview of the Page Structure</li><li>Suggested Patterns for Blocks</li><li>Style and Colorize Images</li><li><code>theme.json</code></li><li>Dropping support for IE11</li><li>Adding support for WebP</li><li>Adding Additional Block Supports</li><li><a href="https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/">Version 10.7</a> of the Gutenberg plugin</li></ul>\n\n\n\n<p>WordPress 5.8 also has lots of refinements to enhance the developer experience.  To learn more, subscribe to the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> and pay special attention to the <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">developer notes tag</a> for updates on those and other changes that could affect your products.</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.8 and update the&nbsp;<em>Tested up to</em>&nbsp;version in the <code>readme</code> file to 5.8.  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 those can be figured out before the final release.</p>\n\n\n\n<p>The WordPress 5.8 Field Guide, due to be published very shortly, will give you a deeper dive into the major changes.</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; This release also marks the&nbsp;<a href="https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze">hard string freeze</a>&nbsp;point of the 5.8 release schedule.</p>\n\n\n\n<p><em><strong>If you think you have found a bug</strong>, you can post to the&nbsp;<a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a>&nbsp;in the support forums. We would love to hear from you!  If you are comfortable writing a reproducible bug report,&nbsp;<a href="https://core.trac.wordpress.org/newticket">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>.</em></p>\n\n\n\n<p class="has-text-align-right"><strong><em>Props to <a href=''https://profiles.wordpress.org/audrasjb/'' class=''mention''><span class=''mentions-prefix''>@</span>audrasjb</a>, <a href=''https://profiles.wordpress.org/cbringmann/'' class=''mention''><span class=''mentions-prefix''>@</span>cbringmann</a>, <a href=''https://profiles.wordpress.org/webcommsat/'' class=''mention''><span class=''mentions-prefix''>@</span>webcommsat</a>, and <a href=''https://profiles.wordpress.org/pbiron/'' class=''mention''><span class=''mentions-prefix''>@</span>pbiron</a> for copy suggestions and final review.</em></strong></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>We are almost there,<br>WordPress 5.8 comes next month.<br>We need your help: test!</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10873";s: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:63:"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 5.8 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:56:"https://wordpress.org/news/2021/06/wordpress-5-8-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 25 Jun 2021 17:14: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:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"5.8";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10855";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:331:"WordPress 5.8 Beta 4 is now available for testing! This software is still in development,&#160;so it is not recommended to run this version on a production site. Consider setting up a test site to play with it. You can test the WordPress 5.8 Beta 4 in three ways: Install/activate the WordPress Beta Tester plugin (select [&#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:12:"Jeffrey Paul";s: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:4104:"\n<p>WordPress 5.8 Beta 4 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it is not recommended to run this version on a production site. Consider setting up a test site to play with it.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 4 in three ways:</p>\n\n\n\n<ul><li>Install/activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the&nbsp;<code>Bleeding edge</code>&nbsp;channel and the&nbsp;<code>Beta/RC Only</code> stream).</li><li>Direct download the beta version here (<a href="https://wordpress.org/wordpress-5.8-beta4.zip">zip</a>).</li><li>Using WP-CLI to test: <code>wp core update --version=5.8-beta4</code></li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021. That’s less than <strong>four weeks away</strong>, so we need your help to make sure the final release is as good as it can be.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-3/" data-type="post">Beta 3</a>, <a href="https://core.trac.wordpress.org/query?status=closed&amp;changetime=06%2F24%2F2021..06%2F26%2F2021&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">18</a> bugs have been fixed. Most tickets focused on polishing existing default themes, fixing bugs in the new block Widget screen, and squashing Editor bugs collected during beta.</p>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<p>Watch the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a> in the coming weeks, which will break down these and other changes in greater detail.</p>\n\n\n\n<p>So far, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&amp;changetime=..06%2F25%2F2021&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">254 tickets in WordPress 5.8</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&amp;status=reopened&amp;changetime=..06%2F25%2F2021&amp;type=enhancement&amp;type=feature+request&amp;milestone=5.8&amp;group=component&amp;col=id&amp;col=summary&amp;col=type&amp;col=status&amp;col=milestone&amp;col=changetime&amp;col=owner&amp;col=priority&amp;col=keywords&amp;order=changetime">91 new features and enhancements</a>, and more bug fixes are on the way.</p>\n\n\n\n<p><strong>Do some testing!</strong></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">Testing for bugs</a> is a vital part of polishing the release during the beta stage and a great way to contribute. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2728.png" alt="✨" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n\n\n\n<p>If you think you’ve found a bug, please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta</a> area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible <a href="https://make.wordpress.org/core/reports/">bug report</a>, file one on <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href=''https://profiles.wordpress.org/desrosj/'' class=''mention''><span class=''mentions-prefix''>@</span>desrosj</a> <a href=''https://profiles.wordpress.org/clorith/'' class=''mention''><span class=''mentions-prefix''>@</span>clorith</a> for reviews and <a href=''https://profiles.wordpress.org/chanthaboune/'' class=''mention''><span class=''mentions-prefix''>@</span>chanthaboune</a> for final edits!</em></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>Releasing software<br>Is complex when open source<br>Yet WordPressers do</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10855";s: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:60:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 5.8 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:56:"https://wordpress.org/news/2021/06/wordpress-5-8-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 23 Jun 2021 02:36:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10843";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:331:"WordPress 5.8 Beta 3 is now available for testing! This software is still in development,&#160;so it is not recommended to run this version on a production site. Consider setting up a test site to play with it. You can test the WordPress 5.8 Beta 3 in three ways: Install/activate the WordPress Beta Tester plugin (select [&#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:7:"Josepha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:5777:"\n<p>WordPress 5.8 Beta 3 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it is not recommended to run this version on a production site. Consider setting up a test site to play with it.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 3 in three ways:</p>\n\n\n\n<ul><li>Install/activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the&nbsp;<code>Bleeding edge</code>&nbsp;channel and the&nbsp;<code>Beta/RC Only</code> stream).</li><li>Direct download the beta version here (<a href="https://wordpress.org/wordpress-5.8-beta3.zip">zip</a>).</li><li>Using WP-CLI to test: <code>wp core update --version=5.8-beta3</code></li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021. That’s just <strong>four weeks away</strong>, so we need your help to make the final release is as good as it can be.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-2/" data-type="post">Beta 2</a>, <a href="https://core.trac.wordpress.org/query?status=closed&amp;changetime=06%2F16%2F2021..06%2F23%2F2021&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">38</a> bugs have been fixed. Here is a summary of some of the included changes:</p>\n\n\n\n<ul><li>Block Editor: Move caching to endpoint for unique responses. (<a href="https://core.trac.wordpress.org/ticket/53435">#53435</a>)</li><li>Bundled Themes: Improve display of blocks in widget areas. (<a href="https://core.trac.wordpress.org/ticket/53422">#53422</a>)</li><li>Coding Standards: Bring some consistency to HTML formatting in <code>wp-admin/comment.php</code>. (<a href="https://core.trac.wordpress.org/ticket/52627">#52627</a>)</li><li>Editor: Include Cover block in the list of block types registered using metadata files. (<a href="https://core.trac.wordpress.org/ticket/53440">#53440</a>)</li><li>Editor: Include Cover block in the list of block types registered using metadata files. (<a href="https://core.trac.wordpress.org/ticket/53440">#53440</a>)</li><li>Media: Add new functions to return the previous/next attachment links. (<a href="https://core.trac.wordpress.org/ticket/45708">#45708</a>)</li><li>Media: Improve upload page media item layout on smaller screens. (<a href="https://core.trac.wordpress.org/ticket/51754">#51754</a>)</li><li>Media: Update total attachment count when media added or removed. (<a href="https://core.trac.wordpress.org/ticket/53171">#53171</a>)</li><li>REST API: Decode single and double quote entities in widget names and descriptions. (<a href="https://core.trac.wordpress.org/ticket/53407">#53407</a>)</li><li>Twenty Nineteen: Update margins on full- and wide-aligned blocks in the editor. (<a href="https://core.trac.wordpress.org/ticket/53428">#53428</a>)</li><li>Widgets: Add editor styles to the widgets block editor. (<a href="https://core.trac.wordpress.org/ticket/53344">#53344</a>)</li></ul>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<p>Watch the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a> in the coming weeks, which will break down these and other changes in greater detail.</p>\n\n\n\n<p>So far, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&amp;changetime=..06%2F23%2F2021&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">254 tickets in WordPress 5.8</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&amp;status=reopened&amp;changetime=..06%2F23%2F2021&amp;type=enhancement&amp;type=feature+request&amp;milestone=5.8&amp;group=component&amp;col=id&amp;col=summary&amp;col=type&amp;col=status&amp;col=milestone&amp;col=changetime&amp;col=owner&amp;col=priority&amp;col=keywords&amp;order=changetime">91 new features and enhancements</a>, and more bug fixes are on the way.</p>\n\n\n\n<p><strong>Do some testing!</strong></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">Testing for bugs</a> is a vital part of polishing the release during the beta stage and a great way to contribute. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2728.png" alt="✨" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n\n\n\n<p>If you think you’ve found a bug, please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta</a> area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible <a href="https://make.wordpress.org/core/reports/">bug report</a>, file one on <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href=''https://profiles.wordpress.org/jeffpaul/'' class=''mention''><span class=''mentions-prefix''>@</span>jeffpaul</a> <a href=''https://profiles.wordpress.org/desrosj/'' class=''mention''><span class=''mentions-prefix''>@</span>desrosj</a> <a href=''https://profiles.wordpress.org/hellofromtonya/'' class=''mention''><span class=''mentions-prefix''>@</span>hellofromtonya</a> <a href=''https://profiles.wordpress.org/pbiron/'' class=''mention''><span class=''mentions-prefix''>@</span>pbiron</a> for reviews and final edits!</em></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>Esperanza first.<br>Want to know the next jazzer?<br>Then please test beta.</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10843";s: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:55:"\n		\n		\n		\n		\n		\n				\n\n					\n										\n					\n		\n		\n\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:55:"WP Briefing: Episode 11: WordCamp Europe 2021 in Review";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://wordpress.org/news/2021/06/episode-11-wordcamp-europe-2021-in-review/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 21 Jun 2021 12:33:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/news/?post_type=podcast&p=10837";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:364:"In this episode, Josepha Haden Chomphosy does a mini deep dive into WordCamp Europe 2021, specifically the conversation between the project’s co-founder, Matt Mullenweg, and Brian Krogsgard formerly of PostStatus. Tune in to hear her take and for this episode’s small list of big things. Have a question you&#8217;d like answered? You can submit them [&#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:9:"enclosure";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:60:"https://wordpress.org/news/files/2021/06/WP-Briefing-011.mp3";s:6:"length";s:1:"0";s:4:"type";s:0:"";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Chloe Bringmann";s: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:10500:"\n<p>In this episode, Josepha Haden Chomphosy does a mini deep dive into WordCamp Europe 2021, specifically the conversation between the project’s co-founder, Matt Mullenweg, and Brian Krogsgard formerly of PostStatus. Tune in to hear her take and for this episode’s small list of big things.</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href="mailto:wpbriefing@wordpress.org">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<p>Editor:<a href="https://profiles.wordpress.org/dustinhartzler/"> Dustin Hartzler</a></p>\n\n\n\n<p>Logo:<a href="https://profiles.wordpress.org/beafialho/"> Beatriz Fialho</a></p>\n\n\n\n<p>Production:<a href="https://profiles.wordpress.org/mkaz/"> </a><a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a></p>\n\n\n\n<p>Song: Fearless First by Kevin MacLeod</p>\n\n\n\n<h2>References </h2>\n\n\n\n<p><a href="https://wordpress.org/news/2021/06/gutenberg-highlights/">Gutenberg Highlights&nbsp;</a></p>\n\n\n\n<p><a href="https://www.youtube.com/watch?v=o-IvKy3322k&amp;t=12428s">Matt Mullenweg in conversation with Brian Krogsgard&nbsp;</a></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/5-8/">5.8 Development Cycle</a></p>\n\n\n\n<p><a href="https://japan.wordcamp.org/2021/">WordCamp Japan</a></p>\n\n\n\n<p><a href="https://europe.wordcamp.org/2021/a-recap-on-wceu-2021/">A recap on WCEU 2021</a></p>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id="more-10837"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy 00:10</strong></p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insights into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 00:40</strong></p>\n\n\n\n<p>A couple of weeks ago, we hosted WordCamp Europe and had the double pleasure of a demo that showed us a bit about the future of WordPress and an interview that looked back while also looking a bit forward. If you haven&#8217;t seen the demo, it was beautiful. And I&#8217;ve included a link to it in the show notes. And if you haven&#8217;t heard the interview, there were a few specific moments that I&#8217;d like to take the time to delve into a little more. Brian Krogsgard, in his conversation with Matt Mullenweg, brought up three really interesting points. I mean, he brought up a lot of interesting points, but there were three that I would particularly like to look into today. The first was about balance. The second was about cohesion. And the third was about those we leave behind.&nbsp;&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 01:24</strong></p>\n\n\n\n<p>So first is this question of balance. Brian brought this up in the context of the overall economic health of the WordPress ecosystem. And in that particular moment, he talked about companies that are coming together, companies that are merging. And in Matt&#8217;s answer, the part that I found the most interesting was when he said, &#8220;the point at which there is the most commercial opportunity is also the point at which there is the most opportunity for short-termism. He went on to talk about the importance of long-term thinking and collective thinking about what makes us, and us here means probably the WordPress project, more vibrant and vital in 10 or 20 or 30 years. One of the things that he specifically called out in that answer was the responsibility of larger companies in the ecosystem. For instance, like Automattic, to commit fully to giving back, there are many ways now that companies can give back to WordPress so that we all replenish the Commons. They can pay for volunteer contributors&#8217; time; they can create and sponsor entire teams through the Five for the Future program. They can contribute time through our outreach program. And they can even contribute to WordPress&#8217;s ability to own our own voice by engaging their audience&#8217;s awareness of what&#8217;s next in WordPress, or whatever. And I know this balance, this particular balance of paid contributors or sponsored contributors, compared to our volunteer contributors or self-sponsored contributors; I know that this balance is one that people keep an eagle eye on. I am consistently on a tight rope to appropriately balanced those voices. But as with so many things where balance is key, keeping an eye on the middle or the long-distance can really help us get it right.&nbsp;&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 03:23</strong></p>\n\n\n\n<p>The second question was one of cohesion and specifically cohesion over the competition. Brian asked how, if people feel disadvantaged, you can foster a feeling of cohesion rather than competition? And Matt&#8217;s first answer was that competition is great. Specifically, he said that competition is great as long as you consider where your collaboration fits into the mission. And he also spent some time exploring how competitors in the ecosystem can still work from a community-first mindset. I personally cannot agree enough about some of the benefits of collaboration alongside your competitors. I remind sponsored contributors from time to time, and I think it&#8217;s true for any contributor that you are an employee of your company first and a contributor to WordPress second. However, once you step into contribution time, your main concern is the users of WordPress, or new contributors, or the health of the WordPress ecosystem as a whole or the WordPress project. So you get all this subject matter expertise from competitive forces, collaborating in a very us versus the problem way. And when you do that, you&#8217;re always going to find a great solution. It may not be as fast as you want it to build things out in the open in public. And so sometimes we get it wrong and have to come back and fix it but still, given time, we&#8217;re going to come out with the best solution because we have so many skilled people working on this.&nbsp;&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 05:01</strong></p>\n\n\n\n<p>And then the third question that I wanted to really touch on is the question of those we leave behind. Brian asked Matt if he thought mid-sized agencies and mid-sized consultants were being squeezed out with the block editor. Matt&#8217;s high-level answer was no, and I tend to agree with him. It&#8217;s not all mid-sized anything any more than it&#8217;s all small-sized anything. His answer continued to look at what stands to change for users with the block editor and who really can stand to benefit. It made me think back to my WordPress 5.0 listening tour. We launched WordPress 5.0, which was, in case anyone forgets, the first release with the block editor in it. I took a six-month-long tour to anywhere that WordPressers were so I could hear their main worries, what Brian is saying in there, and what Matt is saying to really came up all the time in those conversations. And basically, it was that this update takes all the power away from people who are building websites. And in these conversations, and Matt and Brian&#8217;s conversation, it was really focused on our freelancers and consultants. But at the same time, all of them heard that this update gives power back to all of the people who could build websites.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 06:28</strong></p>\n\n\n\n<p>I could not shake the feeling at the time. And honestly, I can&#8217;t shake it now that no high-end consultants, or freelancers, or any other developer or site creator sit around just longing for maintenance work. After six months of talking to people, I didn&#8217;t hear anyone say, &#8220;you know, I just love making the same author card over and over and over.&#8221; Or, &#8220;updated the footer every week, this month. And that&#8217;s why I got into this business.&#8221; And more than the feeling that there just wasn&#8217;t anyone who just loved maintenance, I got a feeling that there were real problems that needed to be solved for these clients and that they wanted to solve them. And that they also would gladly trade updating footers for the much more interesting work of creating modern and stylish business hubs based on WordPress for the clients who trust them so much. All of that, I guess, is to say that, yes, the block editor does give power back to our clients again, but not at the expense of those who have to build the sites in the first place. I think it stands to restore everyone&#8217;s sense of agency more than we truly realize. So that&#8217;s my deep dive on WordCamp Europe; I included links to the demo and the talk below, just in case you haven&#8217;t seen them yet. And you want to get a little bit of insight into the full context of the conversations that I just did a bit of a deep dive into.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 08:15</strong></p>\n\n\n\n<p>And now it&#8217;s time for our smallest of big things. All right, I have three things for you today. Number one, tomorrow, we package WordPress 5.8 beta three. If you&#8217;ve never had a chance to stop by the core channel in slack for the past packaging process, I really encourage you to stop by; we call them release parties. It&#8217;s a bunch of people who stand around and help get it done. So you can also see how it gets done. And if you&#8217;re feeling brave, you can even try your hand at testing out one of the packages as soon as it&#8217;s ready. The second thing is that a week from tomorrow, we reach our first release candidate milestone. So if you have meant to submit any bugs or patches or if you&#8217;ve been procrastinating on documentation, or dev notes, right now is the time so that we can have a chance to get everything into the release by the time we reach the release candidate milestone on the 29th. And the third thing is that we are currently right in the middle of WordCamp Japan. That is a great opportunity to meet some contributors and maybe even get started with contributions yourself. So stop by if you haven&#8217;t had a chance to check it out already. I will leave a link in the show notes. And that, my friends, is your small list of big things. </p>\n\n\n\n<p>Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host, Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10837";s: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:60:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 5.8 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:56:"https://wordpress.org/news/2021/06/wordpress-5-8-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:"Tue, 15 Jun 2021 18:34: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:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10808";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:344:"WordPress 5.8 Beta 2 is now available for testing! This software is still in development,&#160;so it’s not recommended to run this version on a production site. Consider setting up a test site to play with it. You can test the WordPress 5.8 Beta 2 in two ways: Install/activate the WordPress Beta Tester plugin (select the Bleeding [&#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: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:"";}}}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:6174:"\n<p>WordPress 5.8 Beta 2 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it’s not recommended to run this version on a production site. Consider setting up a test site to play with it.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 2 in two ways:</p>\n\n\n\n<ul><li>Install/activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the <code>Bleeding edge</code> channel and the <code>Beta/RC Only</code> stream)</li><li>Direct download the beta version here (<a href="https://wordpress.org/wordpress-5.8-beta2.zip">zip</a>).</li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021. That’s just <strong>five weeks away</strong>, so your help is vital to ensure that the final release is as good as it can be.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/" data-type="post" data-id="10733">Beta 1</a>, <a href="https://core.trac.wordpress.org/query?status=closed&amp;changetime=06%2F09%2F2021..06%2F15%2F2021&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">26</a> bugs have been fixed. Here is a summary of some of the included changes:</p>\n\n\n\n<ul><li>Block Editor: Remove bundled block patterns and support the patterns directory. (<a href="https://core.trac.wordpress.org/ticket/53246">#53246</a>)</li><li>Block Editor: Add a type property to allow Core to identify the source of the editor styles. (<a href="https://core.trac.wordpress.org/ticket/53175">#53175</a>)</li><li>Build/Test Tools: Adds some tests for Quick Draft section in Dashboard. (<a href="https://core.trac.wordpress.org/ticket/52905">#52905</a>)</li><li>Build/Test Tools: Replaced <code>@babel/polyfill</code> with <code>core-js/stable</code>. (<a href="https://core.trac.wordpress.org/ticket/52941">#52941</a>)</li><li>Coding Standards: Further update the code for bulk menu items deletion to better follow WordPress coding standards. (<a href="https://core.trac.wordpress.org/ticket/21603">#21603</a>)</li><li>External Libraries: Update Underscore to version 1.13.1. (<a href="https://core.trac.wordpress.org/ticket/45785">#45785</a>)</li><li>General: A number of block editor, template mode and widget screen related fixes. (<a href="https://core.trac.wordpress.org/changeset/51149">#51149</a>)</li><li>Login and Registration: Improve the unknown username error message. (<a href="https://core.trac.wordpress.org/ticket/52915">#52915</a>)</li><li>Media: Restore AJAX response data shape in media library. (<a href="https://core.trac.wordpress.org/ticket/50105">#50105</a>)</li><li>Site Health: Display a list of file formats supported by the GD library. (<a href="https://core.trac.wordpress.org/ticket/53022">#53022</a>)</li><li><span style="color: initial;, sans-serif">Twemoji: It&#8217;s the new one! (</span><a href="https://core.trac.wordpress.org/ticket/52852">#52852</a>)</li></ul>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<p>Watch the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a> in the coming weeks, which will break down these and other changes in greater detail.</p>\n\n\n\n<p>So far, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&amp;changetime=..06%2F15%2F2021&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">214 tickets in WordPress 5.8</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&amp;status=reopened&amp;changetime=..06%2F15%2F2021&amp;type=enhancement&amp;type=feature+request&amp;milestone=5.8&amp;group=component&amp;col=id&amp;col=summary&amp;col=type&amp;col=status&amp;col=milestone&amp;col=changetime&amp;col=owner&amp;col=priority&amp;col=keywords&amp;order=changetime">87 new features and enhancements</a>, and more bug fixes are on the way.</p>\n\n\n\n<p><strong>Do some testing!</strong></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">Testing for bugs</a> is a vital part of polishing the release during the beta stage and a great way to contribute. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2728.png" alt="✨" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n\n\n\n<p>If you think you’ve found a bug, please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta</a> area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible <a href="https://make.wordpress.org/core/reports/">bug report</a>, file one on <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href=''https://profiles.wordpress.org/chanthaboune/'' class=''mention''><span class=''mentions-prefix''>@</span>chanthaboune</a> for revision, <a href=''https://profiles.wordpress.org/webcommsat/'' class=''mention''><span class=''mentions-prefix''>@</span>webcommsat</a>, <a href=''https://profiles.wordpress.org/youknowriad/'' class=''mention''><span class=''mentions-prefix''>@</span>youknowriad</a>, <a href=''https://profiles.wordpress.org/jorbin/'' class=''mention''><span class=''mentions-prefix''>@</span>jorbin</a>, <a href=''https://profiles.wordpress.org/felipeelia/'' class=''mention''><span class=''mentions-prefix''>@</span>felipeelia</a> , and <a href=''https://profiles.wordpress.org/jeffpaul/'' class=''mention''><span class=''mentions-prefix''>@</span>jeffpaul</a> for proofreading, and <a href=''https://profiles.wordpress.org/cbringmann/'' class=''mention''><span class=''mentions-prefix''>@</span>cbringmann</a> for final edits!</em></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>Install won’t you please<br>WordPress 5-8 Beta 2?<br>We need your help: test!</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10808";s: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:60:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"Gutenberg Highlights";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2021/06/gutenberg-highlights/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 11 Jun 2021 11:03:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Features";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"WordCamp";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10779";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:"During WordCamp Europe this past Wednesday Matt and I gathered to discuss the latest developments of Gutenberg and to share a video with some of the current and upcoming highlights. The video is wonderfully narrated by @beafialho and it was a great opportunity to celebrate all the incredible work that contributors are doing around the [&#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: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:"";}}}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:1386:"\n<p>During <a href="https://europe.wordcamp.org/2021/">WordCamp Europe</a> this past Wednesday Matt and I gathered to discuss the latest developments of Gutenberg and to share a video with some of the current and upcoming highlights. The video is wonderfully narrated by <a href=''https://profiles.wordpress.org/beafialho/'' class=''mention''><span class=''mentions-prefix''>@</span>beafialho</a> and it was a great opportunity to celebrate all the incredible work that contributors are doing around the globe to improve the editing and customization experience of WordPress. For those that weren&#8217;t able to attend live it&#8217;s now available for watching online.</p>\n\n\n\n<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-4-3 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">\n<iframe class=''youtube-player'' width=''632'' height=''356'' src=''https://www.youtube.com/embed/a1Sf7PxfmLQ?version=3&#038;rel=1&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;fs=1&#038;hl=en-US&#038;autohide=2&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;'' sandbox=''allow-scripts allow-same-origin allow-popups allow-presentation''></iframe>\n</div></figure>\n\n\n\n<p>Matt also opened a thread for questions <a href="https://ma.tt/2021/06/wceu-open-thread/">on his blog</a>, so be sure to chime in there if you have any!</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10779";s: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:63:"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 5.8 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:56:"https://wordpress.org/news/2021/06/wordpress-5-8-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 09 Jun 2021 02:47: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:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"5.8";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10733";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:50:"WordPress 5.8 Beta 1 is now available for testing!";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Jeffrey Paul";s: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:10110:"\n<p>WordPress 5.8 Beta 1 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it is not recommended to run this version on a production site. Instead, we recommend that you run this on a test site to play with the new version.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 1 in two ways:</p>\n\n\n\n<ul><li>Install and activate the&nbsp;<a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a>&nbsp;plugin (select the “Bleeding edge” channel and &#8220;Beta/RC Only&#8221; stream).</li><li>Direct download the <a href="https://wordpress.org/wordpress-5.8-beta1.zip">beta version here&nbsp;(zip)</a>.</li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021.  This is just&nbsp;<strong>six weeks away</strong>, so your help is vital to ensure this release is tested properly and as good as it can be.</p>\n\n\n\n<p>Keep your eyes on the&nbsp;<a href="https://make.wordpress.org/core/">Make WordPress Core blog</a>&nbsp;for&nbsp;<a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a>&nbsp;in the coming weeks, breaking down these and other changes in greater detail.</p>\n\n\n\n<p>So what&#8217;s new in this 5.8?  Let&#8217;s start with some highlights.</p>\n\n\n\n<h2>Highlights</h2>\n\n\n\n<h3>Powerful Blocks</h3>\n\n\n\n<ul><li>Discover several new blocks and expressive tools, including blocks for&nbsp;<em>Page Lists</em>,&nbsp;<em>Site Title</em>,&nbsp;<em>Logo</em>, and&nbsp;<em>Tagline</em>. A powerful&nbsp;<em>Query Loop</em>&nbsp;block offers multiple ways for displaying lists of posts and comes with new block patterns that take advantage of its flexibility and creative possibilities.</li><li>Interacting with nested blocks has been made easier with a permanent toolbar button for selecting a parent. Block outlines are shown when hovering or focusing on the different block type buttons. Block handles are now also present for drag and drop when in “select” mode.</li><li>Introduces the&nbsp;<strong>List View</strong>, a panel that can be toggled and helps navigate complex blocks and patterns.</li><li>Reusable blocks have an improved creation flow and support for history revisions. </li><li>A cool new duotone block adds images effects which can be used in media blocks or supported in third-party blocks. Color presets can also be customized by the theme.</li></ul>\n\n\n\n<h3>Handpicked Patterns</h3>\n\n\n\n<p>Patterns can now also be recommended and selected during block setup, offering powerful new flows. Pattern transformations are also possible and allow converting a block or a collection of blocks into different patterns.</p>\n\n\n\n<p>New collection of Patterns and an initial integration with the upcoming Pattern Directory on WordPress.org.</p>\n\n\n\n<h3>Better Tools</h3>\n\n\n\n<ul><li><span style="color: initial;, sans-serif">New template editor that allows creating new custom templates for a page using blocks.</span></li><li>Themes can now control and configure styling with a theme.json file, including layout configuration, block supports, color palettes, and more.</li><li>New design tools and enhancements to existing blocks, including more color, typography, and spacing options, drag and drop for Cover backgrounds, additions to block transformation options, ability to embed PDFs within the File block, and more.</li><li>Includes improvements to how the editor is rendered to more accurately resemble the frontend.</li></ul>\n\n\n\n<h3>Internet Explorer 11</h3>\n\n\n\n<p>Support for Internet Explorer 11 is ending in WordPress this year. In this release, most of those changes are being merged so use the Beta and RC periods to test!</p>\n\n\n\n<h3>Blocks in Widgets Area</h3>\n\n\n\n<ul><li>You can now use any block in your theme’s widget areas using the all new Widgets screen and updated Customizer.</li><li>Existing third party widgets continue to work via the <a href="https://developer.wordpress.org/block-editor/how-to-guides/widgets/legacy-widget-block/">Legacy Widget block</a>.</li><li>Not quite ready for a full switch? To ease the transition, users can use the <a href="https://wordpress.org/plugins/classic-widgets/">Classic Widgets plugin</a> and themes can call <a href="https://developer.wordpress.org/block-editor/how-to-guides/widgets/opting-out/">remove_theme_support( &#8216;widgets-block-editor&#8217; )</a>.</li></ul>\n\n\n\n<p><em>Looking for a change and can&#8217;t find it? There are more improvements listed after the break.</em></p>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<h3>Do some testing!</h3>\n\n\n\n<p>Testing for bugs is an important part of polishing the release during the beta stage and a great way to contribute.</p>\n\n\n\n<p>If you think you’ve found a bug, please post to the&nbsp;<a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta area</a>&nbsp;in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;<a href="https://core.trac.wordpress.org/newticket">file one on WordPress Trac</a>. That’s also where you can find a list of&nbsp;<a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p>Thanks for joining us, and happy testing!</p>\n\n\n\n<p class="has-text-align-left"><em><span><i>Props to </i></span><a href=''https://profiles.wordpress.org/audrasjb/'' class=''mention''><span class=''mentions-prefix''>@</span>audrasjb</a>, <a href=''https://profiles.wordpress.org/cbringmann/'' class=''mention''><span class=''mentions-prefix''>@</span>cbringmann</a>, <a href=''https://profiles.wordpress.org/youknowriad/'' class=''mention''><span class=''mentions-prefix''>@</span>youknowriad</a>, <a href=''https://profiles.wordpress.org/annezazu/'' class=''mention''><span class=''mentions-prefix''>@</span>annezazu</a>, <a href=''https://profiles.wordpress.org/matveb/'' class=''mention''><span class=''mentions-prefix''>@</span>matveb</a>, and <a href=''https://profiles.wordpress.org/desrosj/'' class=''mention''><span class=''mentions-prefix''>@</span>desrosj</a><span><i> for </i>editing/proof reading</span> this post, and <a href=''https://profiles.wordpress.org/chanthaboune/'' class=''mention''><span class=''mentions-prefix''>@</span>chanthaboune</a> for final review.</em></p>\n\n\n\n<hr class="wp-block-separator is-style-default" />\n\n\n\n<p><em>Full Site Editing<br>Coming at the end of year<br>But first, Beta 1</em></p>\n\n\n\n<span id="more-10733"></span>\n\n\n\n<h2><strong>Improvements in this Release</strong></h2>\n\n\n\n<ul><li>Improvements to Reusable blocks, Cover block, Table block, List View, Rich text placeholder, Template Editing Mode, Block Inserter, and Top Toolbar</li><li>Query loop block that uses a query/filter to create a flexible post list based on templates. Best used with patterns.</li><li>Parity refinement between editor and frontend, Standardization to block toolbars organization</li><li>Block widgets in the Customizer</li><li>Introducing the Global Styles and Global Settings APIs: control the editor settings and available customization tools and style blocks using a theme.json file.Template editor opens inside an iframe to more accurately resemble the front end.</li><li>Ability to transform Media and Text into Columns</li><li>Embedded PDFs within File block</li><li>Spacing options for Social Links and Buttons, Spacer block width adjustments</li><li>Twemoji has been updated to version 13.1, bringing you many new Emoji.</li><li>Editor performance improvements</li><li>Hide writing prompt from subsequent empty paragraphs</li><li>More descriptive publishing UI</li><li>Added capability to set the default format for image sub-sizes as well as WebP support</li><li>Added widgets block editor to widgets.php and customize.php</li><li>Added block patterns to default themes</li><li>Added ability to mark a plugin as unmanaged</li><li>Enable revisions for the reusable block custom post type</li><li>Enqueue script and style assets only for blocks present on the page</li><li>Abstracted block editor configuration by deprecating existing filters and introducing replacements that are context-aware</li><li>New sidebars, widget, and widget-types REST API endpoints</li><li>Added support for modifying the term relation when querying posts in the REST API</li><li>Site Health now supports custom sub-menus and pages</li><li>Themes now display the number of available theme updates in the admin menu</li><li>Speed up cached <code>get_pages()</code> calls</li><li>Underscore updates from 1.8.3 to 1.9.1</li></ul>\n\n\n\n<p>To see all of the features for Gutenberg release in detail check out these posts: <a href="https://make.wordpress.org/core/2021/02/17/whats-new-in-gutenberg-10-0-february/">10.0</a>, <a href="https://make.wordpress.org/core/2021/03/02/whats-new-in-gutenberg-10-1-3-march/">10.1</a>, <a href="https://make.wordpress.org/core/2021/03/17/whats-new-in-gutenberg-10-2-17-march/">10.2</a>, <a href="https://make.wordpress.org/core/2021/04/02/whats-new-in-gutenberg-10-3-31-march/">10.3</a>, <a href="https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/">10.4</a>, <a href="https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/">10.5</a>, <a href="https://make.wordpress.org/core/2021/05/14/whats-new-in-gutenberg-10-6-12-may/">10.6</a>, and <a href="https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/">10.7</a>. In addition to those changes, contributors have fixed&nbsp;<a href="https://core.trac.wordpress.org/query?status=closed&amp;milestone=5.8&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority">215 tickets in WordPress 5.8</a>, including&nbsp;<a href="https://core.trac.wordpress.org/query?status=closed&amp;status=reopened&amp;type=enhancement&amp;type=feature+request&amp;milestone=5.8&amp;col=id&amp;col=summary&amp;col=type&amp;col=status&amp;col=milestone&amp;col=owner&amp;col=priority&amp;col=changetime&amp;col=keywords&amp;order=changetime">88 new features and enhancements</a>, with more bug fixes on the way.</p>\n\n\n\n<p></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10733";s: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:55:"\n		\n		\n		\n		\n		\n				\n\n					\n										\n					\n		\n		\n\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"WP Briefing: Episode 10: Finding the Good In Disagreement";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wordpress.org/news/2021/06/episode-10-finding-the-good-in-disagreement/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 07 Jun 2021 12:22: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/news/?post_type=podcast&p=10424";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:408:"To Agree, disagree, and everything in-between. In this episode, Josepha talks about forming opinions and decision-making in the WordPress project. Have a question you&#8217;d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits Editor: Dustin Hartzler Logo: Beatriz Fialho Production: Chloé Bringmann Song: Fearless First by Kevin MacLeod [&#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:9:"enclosure";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:60:"https://wordpress.org/news/files/2021/06/WP-Briefing-010.mp3";s:6:"length";s:1:"0";s:4:"type";s:0:"";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Chloe Bringmann";s: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:12068:"\n<p>To Agree, disagree, and everything in-between. In this episode, Josepha talks about forming opinions and decision-making in the WordPress project.</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href="mailto:wpbriefing@wordpress.org">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<p>Editor:<a href="https://profiles.wordpress.org/dustinhartzler/"> Dustin Hartzler</a></p>\n\n\n\n<p>Logo:<a href="https://profiles.wordpress.org/beafialho/"> Beatriz Fialho</a></p>\n\n\n\n<p>Production:<a href="https://profiles.wordpress.org/mkaz/"> </a><a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a></p>\n\n\n\n<p>Song: Fearless First by Kevin MacLeod</p>\n\n\n\n<h2>References</h2>\n\n\n\n<p><a href="https://www.oprah.com/spirit/suzy-welchs-rule-of-10-10-10-decision-making-guide/all">10/10/10 Rule</a></p>\n\n\n\n<p><a href="https://en.wikipedia.org/wiki/Time_management#The_Eisenhower_Method">The Eisenhower Matrix&nbsp;</a></p>\n\n\n\n<p><a href="https://en.wikipedia.org/wiki/Minimax">The Maximin Strategy&nbsp;</a></p>\n\n\n\n<p><a href="https://europe.wordcamp.org/2021/">WordCamp Europe</a></p>\n\n\n\n<p><a href="https://japan.wordcamp.org/2021/">WordCamp Japan</a></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/5-8/">WordPress 5.8 Development Cycle</a></p>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id="more-10424"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:10</p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of some of the ideas behind the WordPress open source project and the community around it, as well as get a small list of big things coming up in the next two weeks. I&#8217;m your host, Joseph Haden Chomphosy. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>00:40</p>\n\n\n\n<p>For anyone who has ever organized something, whether it&#8217;s a social event, a school project, or an annual family gathering, you know that there are many different opinions. The more opinions you have, the more likely people don&#8217;t see eye to eye. And before you know it, you&#8217;ve got some disagreements. Some things make disagreements worse, like imbalance of information, lack of showing your work, and sometimes just “too many cooks in the kitchen,” to use a regional phrase. Frankly, sometimes it seems like the second you have more than one cook in your kitchen, you&#8217;re going to get some disagreements. But I think that&#8217;s a healthy thing. WordPress is huge. And there are huge numbers of people contributing to WordPress or any other open source project you want to name. So there&#8217;s a lot of stuff available to disagree about. If we never saw anyone pointing out an area that wasn&#8217;t quite right, there would probably be something wrong. If you, like me, think that a healthy tension of collaborative disagreement can be useful when approached thoughtfully, then this quick start guide is for you.&nbsp;</p>\n\n\n\n<p>Step one, prepare to host a discussion. This is, by the way, just the hardest step out there. You have to take a little time to figure out what problem you&#8217;re solving with the solution you&#8217;re suggesting, any goals that it relates to, and then figure out what the bare minimum best outcome would be and what the wildest dreams magic wand waving outcome would be. And you have to be honest with yourself.&nbsp;</p>\n\n\n\n<p>Step two, host the discussion. The venue will be different for different discussions, but you see a lot of these on team blogs or within the actual tickets where work is being done. Wherever you&#8217;re hosting it, state the problem, state your idea for the solution and ask for what you missed. If you&#8217;re hosting a discussion in person, like in a town hall format, this can be hard. And generally, hosting discussions in an in-person or voice call or zoom call kind of way is hard. So if you have an opportunity to start doing this in text first and level your way up to in person, that&#8217;s my recommendation.&nbsp;</p>\n\n\n\n<p>Step three is to summarize the discussion and post a decision if possible. So organizing a big discussion into main points is a really good practice for the people you&#8217;re summarizing it for and yourself. It helps you to confirm your understanding, and it also gives you the chance to pair other solutions with the problem and goals you outlined in step one. If a different solution solves the same problem but with less time or effort, it&#8217;s worth taking a second look with less time or effort. There’s something that I say to WordPress contributors frequently, and that is there are a lot of yeses. There are a lot of right ways to do things and only a few clear wrong ways to do things. So be open-minded about whether or not someone else&#8217;s right way to do things could still achieve the goals you&#8217;re trying to accomplish with your solution. A note on step three where I said, “and post the decision if possible.” Sometimes you&#8217;re the person to make that decision, but sometimes you are not the person who can give something the green light, and so you&#8217;re preparing a recommendation. Whether you&#8217;re making a decision or a recommendation, sometimes you may experience a little decision-making paralysis. I know I do. So here are a few of the tools that I use.</p>\n\n\n\n<p>If you&#8217;re avoiding the decision, use the 10/10/10 rule; it can help you figure out if you&#8217;re stuck on a short-term problem. If there are too many good choices, use the Eisenhower Matrix that can help you to prioritize objectively. If there are too many bad choices, use the Maximin strategy. It can help you to identify how to minimize any potential negative impacts.&nbsp;</p>\n\n\n\n<p>Okay, so you&#8217;ve considered your position. You’ve discussed everything. You summarized the big points. Maybe you also worked your way through to a recommendation or a decision. What about everyone who disagreed with the decision? Or have you made a recommendation, and it wasn&#8217;t accepted? How do you deal with that? That&#8217;s where “disagree and commit” shows up. This phrase was made popular by the folks over at Amazon, I think. But it first showed up, I believe at Sun Microsystems as this phrase, “agreeing, commit, disagree and commit or get out of the way.”</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>05:34</p>\n\n\n\n<p>Disagree and commit as a concept works pretty well when everyone agrees on the vision and the goals, but not necessarily how to get to those goals. We&#8217;ve had moments in recent history where folks we&#8217;re not able to agree, we’re not able to commit, and so then left the project. I hate when that happens. I want people to thrive in this community for the entire length of their careers. But I also understand that situation shows up in the top five learnings of open source when you no longer have interest in the project and handed it off to a competent successor. So there it is &#8211; disagreements in open source in WordPress.&nbsp;</p>\n\n\n\n<p>As with so many of the things I discuss on this podcast, this is incredibly complex and nuanced in practice. Taking an argument, distilling facts from feelings, and adjusting frames of reference until the solution is well informed and risk-balanced. That is a skill set unto itself. But one that increases the health of any organization. I’ll share that list of references and general materials in the show notes, including a link explaining each of those decision-making tools that I shared. I&#8217;m also going to include the contributor training module on decision-making in the WordPress project. It&#8217;s got excellent information. It&#8217;s part of a series of modules that I asked team reps to take and sponsored contributors. I don&#8217;t require it from anyone, but I do hope that it is useful for you. Also, speaking of useful for you, if you are just here for leadership insights, I included some hot takes after the outro music for you. It&#8217;s like an Easter egg, but I just told you about it.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>07:33</p>\n\n\n\n<p>And that brings us to our small list of big things! First off, WordCamp Europe is happening this we; I hope that everybody has an opportunity to attend. If you still haven&#8217;t gotten your tickets, they are free, and I think there are still a few left. I will include a link in the show notes as well. There&#8217;s going to be a little demo with Matt Mullenweg and Matias Ventura on the WordPress 5.8 release that&#8217;s coming up. And then kind of a retrospective discussion between Matt and Brian Krogsgard. I encourage you to join; I think it&#8217;s going to be very interesting.&nbsp;</p>\n\n\n\n<p>There&#8217;s also WordCamp, Japan coming up June 20 through 26th. I mentioned it last time &#8211;&nbsp; it has a big section of contributing and contribution time. So if you&#8217;re looking to get started, some projects are laid out, and I encourage you to take a look at that as well.&nbsp;</p>\n\n\n\n<p>The new thing on this list, and I don&#8217;t know how new It is, in general, I hope it&#8217;s not too new to you, is that WordPress 5.8 release is reaching its beta one milestone on June 8th, so right in the middle of WordCamp Europe. I encourage every single theme developer, plugin developer that we have, agency owners that we have to really take a look at this release and dig into testing it. It&#8217;s a gigantic release. And I have so many questions about what will work and will not work once we get it into a broader testing area. We&#8217;ve been doing a lot of testing in the outreach program. But it&#8217;s always helpful to get people who are using WordPress daily in their jobs to really give a good solid test to the beta product to the beta package. And put it all through its paces for us.&nbsp;</p>\n\n\n\n<p>So, that my friends, is your small list of big things. Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy&nbsp; </strong>10:09</p>\n\n\n\n<p>Hey there, you must be here because I told you about this totally not hidden easter egg about my hot takes on organizational health; I have three for you. And if you&#8217;ve ever worked with me, none of this will surprise you. But if you haven&#8217;t worked with me, hopefully, it kind of gives you some idea about how I approach all of this a bit differently. So, number one, critical feedback is the sign of a healthy organization. And I will never be dissuaded from that opinion. A complete lack of dissent doesn&#8217;t look like “alignment.” To me, that looks like fear. And it goes against the open source idea that many eyes make all bugs shallow.&nbsp;</p>\n\n\n\n<p>Tip number two, a bit of tension is good, a bit of disagreement is good. The same thing that I say about women in tech, we&#8217;re not all the same. And if we were, then we wouldn&#8217;t need to collaborate anyway. But diversity, whether that&#8217;s the diversity of thought or of a person or of experience, just doesn&#8217;t happen without some misunderstandings. It&#8217;s how we choose to grow through those misunderstandings that make all the difference for the type of organization we are.&nbsp;</p>\n\n\n\n<p>And hot take number three, changing your mind isn&#8217;t flip-flopping or hypocritical. I think that&#8217;s a sign of growth and willingness to hear others. I like to think of my embarrassment at past bad decisions &#8211; as the sore muscles of a learning brain. And I, again, probably won&#8217;t be dissuaded from that opinion. Although, you know, if I&#8217;m sticking true to changing your mind some flip-flopping or hypocritical, maybe I will, but you can always try to, to give me the counter-argument for that, and we&#8217;ll see how it goes. Thank you for joining me for my little public easter egg.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10424";s: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:66:"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:36:"People of WordPress: Tijana Andrejic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2021/06/people-of-wordpress-tijana-andrejic/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 07 Jun 2021 12:01:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:4:{i:0;a:5:{s:4:"data";s:9:"heropress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:10:"Interviews";s: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:16:"ContributorStory";s: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:5:{s:4:"data";s:9:"HeroPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10427";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:178:"This month to coincide with WordCamp Europe, we feature Tijana Andrejic from Belgrade, Serbia, about her journey from fitness trainer to the opportunities in the WordPress world.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:28:"webcommsat AbhaNonStopNewsUK";s: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:14291:"\n<p><strong>WordPress is open source software, maintained by a global network of contributors. There are many examples of how WordPress has changed people’s lives for the better. In this monthly series, we share some of the amazing stories.</strong></p>\n\n\n\n<p>This month to coincide with WordCamp Europe, we feature Tijana Andrejic from Belgrade, Serbia, about her journey from fitness trainer to the WordPress world, with the freelance and corporate opportunities it introduced. </p>\n\n\n\n<figure class="wp-block-image size-large"><img loading="lazy" width="632" height="387" src="https://i0.wp.com/wordpress.org/news/files/2021/06/2021-07-Tijana-Andrejic_Featured-Img_1.jpg?resize=632%2C387&#038;ssl=1" alt="Tijana - portrait picture" class="wp-image-10713" srcset="https://i0.wp.com/wordpress.org/news/files/2021/06/2021-07-Tijana-Andrejic_Featured-Img_1.jpg?w=1024&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/06/2021-07-Tijana-Andrejic_Featured-Img_1.jpg?resize=300%2C184&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/06/2021-07-Tijana-Andrejic_Featured-Img_1.jpg?resize=768%2C470&amp;ssl=1 768w" sizes="(max-width: 632px) 100vw, 632px" data-recalc-dims="1" /></figure>\n\n\n\n<p>As a professional manager with a college degree in Organizational Science and a certified fitness instructor, Tijana is nothing if not driven and goal-oriented.&nbsp;</p>\n\n\n\n<p>Following her time as a fitness trainer, Tijana moved to work in IT around 2016. She first explored content creation and design before focusing on SEO and becoming an independent specialist.&nbsp;&nbsp;</p>\n\n\n\n<p>Tijana was hired as a Customer Happiness Engineer for a hosting company, where she discovered the benefits of having a team. She realized that having close working relationships with colleagues is helpful for business success and accelerates personal growth.</p>\n\n\n\n<p>Tijana hopes that by sharing her story, she can help others who are either starting their career or are moving roles. She describes the opportunities she discovered in the WordPress community as ‘a huge epiphany’, especially in the world of freelancing.</p>\n\n\n\n<p>She highlights <strong>5 things that helped her to start a new freelancing career</strong>. Let’s dive into them.</p>\n\n\n\n<h2>What motivates me?</h2>\n\n\n\n<p>“Why am I doing this?” is the first question that Tijana asks herself before starting anything new. This self-review and honesty, she feels, allows her to determine her priorities. She also benchmarks options around her motivations of wanting a flexible schedule and to grow professionally.&nbsp;</p>\n\n\n\n<p>She lists the reasons to make a particular choice, like being a freelancer, to help her choose the right job, pathway, or identify alternatives.&nbsp;</p>\n\n\n\n<p>She recommends that others can take a similar approach. If freelancing is still the best solution after examining all their goals and motivations, Tijana believes a good next step would be to learn WordPress-related skills.</p>\n\n\n\n<figure class="wp-block-image"><img src="https://lh6.googleusercontent.com/cdHeIL-H_mE6QFCUxUT-gfKS2GzizRHtn4iCENoaWOimC82BfModRJh44QbhvHPW0GNVP5eUPhgxQteDRbA_9EUzpssTXMGWje1hUuKyrfXUgGhCnvXQdraaUQiaGBjFr73dNYxr" alt="WordCamp Europe 2019 group picture" /></figure>\n\n\n\n<h2>Develop WordPress related skills</h2>\n\n\n\n<p>The next question you may ask: “Why WordPress?”</p>\n\n\n\n<p>WordPress is used by more than 40% of websites in some form and offers various roles, many of which are not developer-specific. Tijana highlights a few:&nbsp;</p>\n\n\n\n<ul><li>web developer (coding websites, themes, and plugins)</li><li>web implementor (creating websites from existing themes without coding)</li><li>web designer (designing website mock-ups, editing images, or creating online infographics)</li><li>client support professional (helping people with their websites)</li><li>website maintenance (WordPress, themes, and plugins are maintained and backed up regularly)</li><li>WordPress trainer (helping clients with how to use the platform or teaching other web professionals)</li><li>content writer</li><li>accessibility specialist (making sure standards are met and suggesting solutions for accessibility barriers)</li><li>SEO consultant (improving search outcomes and understanding)</li><li>statistics consultant, especially for web shops</li><li>WordPress assistant (adding new content and editing existing posts)</li><li>website migration specialist (moving websites from one server to another)</li><li>web security specialist</li></ul>\n\n\n\n<figure class="wp-block-image"><img src="https://lh4.googleusercontent.com/16XExYT_P4R4PX3orOaWbueDfkBIA6PFQ-CuYEXdeN9AvUIuIF33aIjT1DpdnFCqhrijWv1f68OR2Qh14xGT9REHGJ-MqK-OxJ9XcrhZ3IkcW8DBI7nVAtvFcCnCHL0woka_FV6t" alt="WCBGD group picture" /></figure>\n\n\n\n<p>Tijana emphasized: “Another reason why WordPress is great for freelancers is the strong community that exists around this content management system (CMS).&#8221; WordCamps and Meetups are a way to get useful information and meet people from a large and very diverse community and get answers to many questions straight away.&nbsp;</p>\n\n\n\n<p>In the past year, these events have been primarily online. However, the contributors who run them continue to make an effort to provide an experience as close to in-person events as possible. The biggest advantage to online events is that we can attend events from across the world, even if sometimes during these difficult times, it is difficult to get enough time to deeply into this new experience. Since Tijana’s first Meetup, she has attended many WordPress community events and volunteered as a speaker.</p>\n\n\n\n<h2>Plan in advance</h2>\n\n\n\n<p>Becoming a freelancer takes time. For Tijana, success came with proper planning and following her plan to ‘acquire or improve relevant skills that will make you stand out in the freelance market.’ She strongly believes that learning and growing as a professional opens more business opportunities.&nbsp;</p>\n\n\n\n<p>If you are considering a freelance career, she advises improving relevant skills or developing new skills related to your hobbies as ‘there is nothing better than doing what you love.’ In cases where no previous experience and knowledge can be used, she suggests choosing ‘a job that has a shorter learning curve and builds your knowledge around that.’</p>\n\n\n\n<p>Tijana started as a content creator and learned to become an SEO expert. However, she highlights many alternative paths, including starting as a web implementer and moving to train as a developer.&nbsp;</p>\n\n\n\n<p>She suggests to others: “It would be a good idea to analyze the market before you jump into the learning process.” She also recommends people check the latest trends and consider the future of the skills they are developing.</p>\n\n\n\n<p>Visit the new <a href="https://learn.wordpress.org/">Learn WordPress.org</a> to see what topics are of interest to you. In this newly established resource, the WordPress community aggregates workshops to support those who want to start and improve their skills, provides lesson plans for professional WordPress trainers and helps you create personal learning to develop key skills. There is also material on helping you be part of and organize events for your local community.</p>\n\n\n\n<p>Tijana highlights that there are many places for freelancers to find clients. For example, the WordPress Community has a place where companies and individual site owners publish their job advertisements&nbsp; &#8211; <a href="https://jobs.wordpress.net/">Jobs.WordPress.net</a>.</p>\n\n\n\n<h2>Hurray, it’s time to get a first freelancing job</h2>\n\n\n\n<p>As a pragmatic person, Tijana recommends: “Save money before quitting your job to become a full-time freelancer. Alternatively, try freelancing for a few hours per week to see if you like it. Although some people do benefit when taking a risk, think twice before you take any irreversible actions.”&nbsp;</p>\n\n\n\n<p>She shared some possible next steps:&nbsp;</p>\n\n\n\n<ul><li>use a freelancing platform</li><li>triple-check your resume</li><li>professionally present yourself</li><li>fill up your portfolio with examples</li><li>use video material</li></ul>\n\n\n\n<p>“By using video material, your clients will not see you like a list of skills and previous experiences, but as a real person that has these skills and experiences and that provides a certain service for them.”</p>\n\n\n\n<p>She adds: “Have a detailed strategy when choosing your first employer. Choose your first employer wisely, very wisely. I can’t emphasize enough how important this is”.</p>\n\n\n\n<p>When Tijana took her first freelancing job, she considered the following:</p>\n\n\n\n<ul><li>how was the employer rated by other freelancers who worked for him previously</li><li>how does the employer rate other freelancers</li><li>how much money had they already spent on the platform</li><li>the number of open positions for a specific job and the number of freelancers that have already applied&nbsp;</li></ul>\n\n\n\n<p>“The first job is not all about the money. Don’t get greedy on your first job. If you get good recommendations, your second job can pay two to three times more. And your third job can go up to five times more. That was my experience.”</p>\n\n\n\n<h2>Take responsibility as a freelancer</h2>\n\n\n\n<p>Tijana reminds us: “Freedom often comes with responsibility; individual responsibility is key when it comes to freelancing.”</p>\n\n\n\n<p>She advises others not to take a job if you can not make a deadline and have someone reliable who can help you.&nbsp;</p>\n\n\n\n<p>Missing deadlines will cost your client money and affect the review the client will be willing to leave about your job, and this can have a big impact on your future opportunities or freelance jobs.</p>\n\n\n\n<p>She adds: “This can start a downward spiral for your career. However, we are all humans, and unpredictable things can happen. If for some reason you are not able to complete your work in a timely manner, let your client know immediately so they can have enough time to hire someone else”.</p>\n\n\n\n<p>Tijana emphasizes the importance of making expectations clear before accepting a job, both what the client is expecting and what you can expect from the client.&nbsp;</p>\n\n\n\n<p>Lastly, she points out that if you are working from home, your friends and family should treat you the way they would if you were in an office. She advises: “Let them know about your working schedule.”</p>\n\n\n\n<p>She hopes that these basic guidelines will be useful in launching freelance careers, as they did her, even though there is no universal recipe for all.</p>\n\n\n\n<p>Tijana highlights: “It’s just important to stay focused on your goals and to be open to new opportunities.” Freelancing wasn’t the only way she could have fulfilled her goals, but it was an important part of her path, and it helped her be confident in her abilities to make the next big step in her life.</p>\n\n\n\n<p>As a freelancer, she was missing close relationships with colleagues and teamwork, which she has now found in her current firm. Her colleagues describe her as a: “walking-talking bundle of superpowers: sports medicine and fitness professional, SEO expert, blogger, designer and a kitty foster mum”.</p>\n\n\n\n<figure class="wp-block-image"><img src="https://lh4.googleusercontent.com/PIGT9R6FmtEHsNBvWzyViW5htRAm156asTOsohOGOUwfsWjW1TuDhUI9yuZnjIe-1eFHfFUWPULPtw82P3YYXHa0bsY_jA5keelmDHfSkTdd3xUsVZTmG9KvdE8XTojvU3LxYCsi" alt="Conference reception" /></figure>\n\n\n\n<p>If you are considering starting your career as a freelancer, take the courses offered at <a href="https://learn.wordpress.org/">learn.wordpress.org,</a> reach out to companies that you would be interested in working with, and remember that there are a whole host of opportunities in the WordPress project.</p>\n\n\n\n<p><a href="https://make.wordpress.org/">The WordPress.org Teams</a> &#8211; what they do, when and where they meet</p>\n\n\n\n<p><a href="https://learn.wordpress.org/">Learn WordPress resource</a> &#8211; free to use to expand your knowledge and skills of using the platform and learning about the community around it.</p>\n\n\n\n<p>The 3-day <a href="https://europe.wordcamp.org/2021/">WordCamp Europe 2021</a> online event begins on 7 June 2021. You can discover more about being a contributor in its live sessions and <a href="https://europe.wordcamp.org/2021/contribute-to-wordpress/">section on ways to contribute to WordPress</a>.</p>\n\n\n\n<h2>Contributors</h2>\n\n\n\n<p>Thanks to Olga Gleckler (<a href=''https://profiles.wordpress.org/oglekler/'' class=''mention''><span class=''mentions-prefix''>@</span>oglekler</a>), Abha Thakor (<a href="https://profiles.wordpress.org/webcommsat/">@webcommsat</a>), Chloé Bringmann (<a href=''https://profiles.wordpress.org/cbringmann/'' class=''mention''><span class=''mentions-prefix''>@</span>cbringmann</a>), Surendra Thakor (<a href=''https://profiles.wordpress.org/sthakor/'' class=''mention''><span class=''mentions-prefix''>@</span>sthakor</a>), and Meher Bala (<a href=''https://profiles.wordpress.org/meher/'' class=''mention''><span class=''mentions-prefix''>@</span>meher</a>) for working on this story. Josepha Haden (<a href="https://profiles.wordpress.org/chanthaboune/">@chanthaboune</a>) and also to Topher DeRosia (<a href="https://profiles.wordpress.org/topher1kenobe/">@topher1kenobe</a>) who created HeroPress. Thank you to Tijana Andrejic (<a href=''https://profiles.wordpress.org/andtijana/'' class=''mention''><span class=''mentions-prefix''>@</span>andtijana</a>) for sharing her #ContributorStory</p>\n\n\n\n<figure class="wp-block-image"><img src="https://lh4.googleusercontent.com/FEZ2FQJ0vQ311YoPfh6ny15NXh8saTLH_RjyDO4pUOuEGBTa-Czk63PGoWL04FawKviRfNx0QXePx-goK04X12ry1BR_WXh-kVPIfsEeItPAX6reN5fHS96q6-8dUI506ZO38Z0G" alt="HeroPress logo" /></figure>\n\n\n\n<p><em>This post is based on an article originally published on HeroPress.com. It highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.</em></p>\n\n\n\n<p><em>Meet more WordPress community members in our <a href="https://wordpress.org/news/category/heropress/">People of WordPress series</a>.</em></p>\n\n\n\n<p><em>#ContributorStory #HeroPress</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10427";s: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:60:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:40:"A New Design is Coming to WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wordpress.org/news/2021/06/a-new-design-is-coming-to-wordpress-news/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 03 Jun 2021 20:47: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:8:"category";a:2:{i:0;a:5:{s:4:"data";s:7:"General";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:7:"Updates";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10418";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:324:"After many years of a tidy, white-space filled design on WordPress.org/news it&#8217;s time to bring new life to the way we present our content. So much has changed since this site was first created: the people who read it, the type and variety of what is published, even the way WordPress works has changed. Which [&#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:7:"Josepha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:1591:"\n<p>After many years of a tidy, white-space filled design on WordPress.org/news it&#8217;s time to bring new life to the way we present our content. So much has changed since this site was first created: the people who read it, the type and variety of what is published, even the way WordPress works has changed.</p>\n\n\n\n<p>Which means it makes sense to change our theme. </p>\n\n\n\n<p>Earlier this year, Matt requested a new design from Beatriz Fialho (who also created the State of the Word slides for 2020). The design keeps a clean, white-space friendly format while incorporating a more jazzy, playful feeling with a refreshed color palette. </p>\n\n\n\n<figure class="wp-block-image size-large"><img loading="lazy" width="632" height="449" src="https://i0.wp.com/wordpress.org/news/files/2021/06/25-1024x728-1.png?resize=632%2C449&#038;ssl=1" alt="" class="wp-image-10420" srcset="https://i0.wp.com/wordpress.org/news/files/2021/06/25-1024x728-1.png?w=1024&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2021/06/25-1024x728-1.png?resize=300%2C213&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2021/06/25-1024x728-1.png?resize=768%2C546&amp;ssl=1 768w" sizes="(max-width: 632px) 100vw, 632px" data-recalc-dims="1" /></figure>\n\n\n\n<p>More detail on this modern exploration have been posted on <a href="https://make.wordpress.org/design/2021/06/03/redesign-of-wordpress-org-news/">make.wordpress.org/design</a>. I encourage you to stop by and read more about the thoughts behind the coming updates; and keep an eye out for the new look here and across WordPress.org!</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:5:"10418";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:32:"https://wordpress.org/news/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:9:"\n	hourly	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:4:"\n	1	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:4:"site";a:1:{i:0;a:5:{s:4:"data";s:8:"14607090";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 30 Jun 2021 08:15:50 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:25:"strict-transport-security";s:11:"max-age=360";s:6:"x-olaf";s:3:"⛄";s:13:"last-modified";s:29:"Wed, 30 Jun 2021 03:47:48 GMT";s:4:"link";s:63:"<https://wordpress.org/news/wp-json/>; rel="https://api.w.org/"";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 1";}}s:5:"build";s:14:"20201016145008";}', 'no');
INSERT INTO `wpo1_options` VALUES
(552, '_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1625084149', 'no'),
(553, '_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1625040949', 'no'),
(554, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1625084151', 'no'),
(555, '_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:54:"WPTavern: WP Engine Makes Local Pro Free for All Users";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119329";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:153:"https://wptavern.com/wp-engine-makes-local-pro-free-for-all-users?utm_source=rss&utm_medium=rss&utm_campaign=wp-engine-makes-local-pro-free-for-all-users";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3025:"<p>WP Engine <a href="https://wpengine.com/blog/wp-engine-supercharges-wordpress-development-local-pro-free-for-everyone/?utm_medium=organicsocial&utm_source=twitter">announced</a> today that Local Pro, the commercial upgrade for its local WordPress development product, is now free for all users. Beginning with <a href="https://localwp.com/releases/">version 6.0</a>, all features that formerly required a paid subscription are now available with a free Local account. These include Live Links Pro, Instant Reload, Link Checker, and MagicSync. </p>\n\n\n\n<p>&ldquo;We believe Local Pro features benefit a broader WordPress developer community and we want to deliver the full value of Local to more developers than ever,&rdquo; WP Engine Senior Vice President Seth Halpern said. &ldquo;We want to empower the freedom to create on WordPress by making all Local features available for free.&rdquo;</p>\n\n\n\n<p>WP Engine&rsquo;s recently published research&nbsp;estimates the&nbsp;<a href="https://wpengine.com/wordpress-economy/">WordPress economy at $596.7B</a>. The company may be in a better position to gain customers for its hosting products if they make Local completely free, as the tool was designed to seamlessly connect with WP Engine and Flywheel&rsquo;s hosting. It is currently used by more than 300,000 developers. Over the years Local has gained popularity due to how easy it makes setting up WordPress development and testing environments. </p>\n\n\n\n<p>Version 6.0 also introduces Local&rsquo;s new <a href="https://localwp.com/cloud-backups/">Cloud Backups add-on</a>, which will allow users to backup to Google Drive or Dropbox. Cloud backups can be restored from the Tools tab. The 6.0 release post details a few features that have been moved to new locations in the interface:</p>\n\n\n\n<ul><li><a href="https://localwp.com/help-docs/connect/magic-sync/">MagicSync</a>&nbsp;is now a global preference, and the default push/pull experience can be toggled in the Preferences menu.&nbsp;</li><li>Live Links Pro, now&nbsp;<a href="https://localwp.com/live-links/">Live Links</a>, will be accessible for all users by connecting your Local account.</li><li><a href="https://localwp.com/help-docs/local-features/link-checker/">Link Checker</a>&nbsp;and&nbsp;<a href="https://localwp.com/help-docs/local-features/instant-reload/">Instant Reload</a>&nbsp;have been moved to the Local Add-ons Library.&nbsp;</li><li>Xdebug Add-ons have moved from the Utilities tab into the Tools tab within Local.</li></ul>\n\n\n\n<p>Existing Local Pro subscribers will have access to priority support until September 1, 2021. After that time, dedicated ticket support will be discontinued in favor of directing users to the <a rel="noreferrer noopener" href="https://localwp.com/community/" target="_blank">community forums</a>&nbsp;and&nbsp;<a rel="noreferrer noopener" href="http://localwp.com/help-docs/" target="_blank">help docs</a>. WP Engine is offering customers full or prorated refunds, which will be sent out before July 31, 2021.</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, 30 Jun 2021 04:28:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"WordPress.org blog: WordPress 5.8 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:35:"https://wordpress.org/news/?p=10873";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2021/06/wordpress-5-8-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:4740:"<p>The first release candidate for <a href="https://make.wordpress.org/core/5-8/">WordPress 5.8</a> is now available! <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/1f389.png" alt="🎉" class="wp-smiley" /></p>\n\n\n\n<p>Please join us in celebrating this very important milestone in the community&#8217;s progress towards the final release of WordPress 5.8!</p>\n\n\n\n<p>“Release Candidate” means the new version is ready for release, but with thousands of plugins and themes and differences in how the millions of people use WordPress, it is possible something was missed.  WordPress 5.8 is slated for release&nbsp;on&nbsp;<strong>July 20, 2021</strong>, but <em>your</em>&nbsp;help is needed to get there—if you have not tried 5.8 yet,&nbsp;<strong>now is the time</strong>!</p>\n\n\n\n<p>You can test the WordPress 5.8 release candidate in three ways:</p>\n\n\n\n<ul><li>Install and activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (select the <code>Bleeding edge</code> channel and then <code>Beta/RC Only</code> stream)</li><li>Directly download the release candidate version <a href="https://wordpress.org/wordpress-5.8-RC1.zip">(zip)</a></li><li>Using WP-CLI to test: <code>wp core update --version=5.8-RC1</code></li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta releases and gave feedback.  Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>What is in WordPress 5.8?</h2>\n\n\n\n<p>The second release of 2021 continues to progress on the block editor towards the promised future of full site editing with these updates:</p>\n\n\n\n<ul><li>Manage Widgets with Blocks</li><li>Display Posts with New Blocks and Patterns</li><li>Edit Post Templates</li><li>Overview of the Page Structure</li><li>Suggested Patterns for Blocks</li><li>Style and Colorize Images</li><li><code>theme.json</code></li><li>Dropping support for IE11</li><li>Adding support for WebP</li><li>Adding Additional Block Supports</li><li><a href="https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/">Version 10.7</a> of the Gutenberg plugin</li></ul>\n\n\n\n<p>WordPress 5.8 also has lots of refinements to enhance the developer experience.  To learn more, subscribe to the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> and pay special attention to the <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">developer notes tag</a> for updates on those and other changes that could affect your products.</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.8 and update the&nbsp;<em>Tested up to</em>&nbsp;version in the <code>readme</code> file to 5.8.  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 those can be figured out before the final release.</p>\n\n\n\n<p>The WordPress 5.8 Field Guide, due to be published very shortly, will give you a deeper dive into the major changes.</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; This release also marks the&nbsp;<a href="https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze">hard string freeze</a>&nbsp;point of the 5.8 release schedule.</p>\n\n\n\n<p><em><strong>If you think you have found a bug</strong>, you can post to the&nbsp;<a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a>&nbsp;in the support forums. We would love to hear from you!  If you are comfortable writing a reproducible bug report,&nbsp;<a href="https://core.trac.wordpress.org/newticket">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>.</em></p>\n\n\n\n<p class="has-text-align-right"><strong><em>Props to <a href="https://profiles.wordpress.org/audrasjb/" class="mention"><span class="mentions-prefix">@</span>audrasjb</a>, <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a>, <a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</a>, and <a href="https://profiles.wordpress.org/pbiron/" class="mention"><span class="mentions-prefix">@</span>pbiron</a> for copy suggestions and final review.</em></strong></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>We are almost there,<br />WordPress 5.8 comes next month.<br />We need your help: test!</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:"Wed, 30 Jun 2021 03:47: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:12:"Jeffrey Paul";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:79:"WPTavern: Add Editor-Only Notes via the Markdown Comment Block WordPress Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119331";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:203:"https://wptavern.com/add-editor-only-notes-via-the-markdown-comment-block-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=add-editor-only-notes-via-the-markdown-comment-block-wordpress-plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3843:"<p class="has-drop-cap">Rich Tabor, the Senior Product Manager of WordPress Experience at GoDaddy, <a href="https://twitter.com/richard_tabor/status/1408460733055184897">tweeted that he had an idea</a> for a new block at the end of last week. Shortly after, the <a href="https://wordpress.org/plugins/markdown-comment-block/">Markdown Comment Block</a> plugin appeared on WordPress.org.</p>\n\n\n\n<p>The plugin is a one-off block. It allows users to enter notes directly into the post editor that will not appear on the front end of the site. Tabor said he came up with the idea when working on an article for building single-block plugins.</p>\n\n\n\n<p>There are few things I love more than simple plugins with a tight focus, performing a single function. Markdown Comment Block lands in this category.</p>\n\n\n\n<p>The plugin creates a new block that works nearly the same as a typical Paragraph block:</p>\n\n\n\n<img />Adding inline comments to a post.\n\n\n\n<p>Users can change the text color, but they will not have access to the typical Rich Text controls. Those should be unnecessary anyway.</p>\n\n\n\n<p>As someone who does long-form writing almost exclusively in Markdown, the block&rsquo;s use of the double percent-sign syntax for comments intrigued me. Technically, the Markdown spec does not support any sort of special characters for them. It handles HTML comments. However, those appear in the source code on the front end when the document is rendered. I have only seen the <code>%%</code> mark to denote comments in the <a href="https://www.inspire-writer.com/">Inspire Writer</a> app for Windows. Tabor said he had seen the same in <a href="https://ulysses.app/">Ulysses</a>. The feature also exists in the <a href="https://useiceberg.com/">Iceberg editor</a> for WordPress, which Tabor created alongside Jeffrey Carandang.</p>\n\n\n\n<p>The plugin also introduces the <code>%%</code> keyboard shortcut. Typing it directly in the editor will create a new Markdown Comment block.</p>\n\n\n\n<p>My primary use case for the plugin would be leaving notes for my later self. However, it could also be handy in users&rsquo; publishing flows. The block adds a &ldquo;Resolve&rdquo; button to the toolbar. Clicking it deletes the comment.</p>\n\n\n\n<img />Clicking the &ldquo;Resolve&rdquo; button will delete the block.\n\n\n\n<p>The block itself will not likely offer a robust enough feature set for complex workflows. However, pairing it with a plugin like <a href="https://wptavern.com/upgrade-your-publishing-flow-with-the-post-descriptions-wordpress-plugin">Post Descriptions</a> could round out the experience for larger teams of writers and copyeditors.</p>\n\n\n\n<p>The Post Descriptions plugin allows users to add notes on the post level. These notes appear on the post-management screen, letting other team members know when to check an article. However, it may be hard to provide the full context of what issues need to be resolved before publishing. Markdown Comment Block adds an inline comments system, letting team members pass in-text notes.</p>\n\n\n\n<p>Theme developers should appreciate that the block uses CSS custom properties too, which makes it easy to overwrite its default style rules.  In moments, I was able to make it match my theme:</p>\n\n\n\n<img />Custom color, font, and line-height styles.\n\n\n\n<p>The <code>--markdown-comment-font-size</code>, <code>--markdown-comment-line-height</code>, and <code>--markdown-comment-color</code> variables are available for theme developers who want to add in support.</p>\n\n\n\n<p>The one complaint I had about the block is its title: &ldquo;Comment.&rdquo; It is easy to confuse it with the six other comment-related blocks already in the WordPress block list. And, there will only be more in upcoming versions. Giving it a title of &ldquo;Markdown Comment&rdquo; would better distinguish it from others.</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, 30 Jun 2021 00:15: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:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:113:"WPTavern: BuddyPress 9.0 Scheduled for Short Development Cycle to Ship Block-Based Widgets Ahead of WordPress 5.8";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119255";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:271:"https://wptavern.com/buddypress-9-0-scheduled-for-short-development-cycle-to-ship-block-based-widgets-ahead-of-wordpress-5-8?utm_source=rss&utm_medium=rss&utm_campaign=buddypress-9-0-scheduled-for-short-development-cycle-to-ship-block-based-widgets-ahead-of-wordpress-5-8";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3801:"<p><a href="https://buddypress.org/2021/06/buddypress-8-0-0-alfano/">BuddyPress 8.0</a> was just released earlier this month on June 6, but the core development team is gearing up for a <a href="https://bpdevel.wordpress.com/2021/06/24/bp-dev-chat-summary-june-23-2021/">short development cycle for 9.0</a>. The release will be specifically targeted at getting BuddyPress core widgets ready for WordPress 5.8&rsquo;s new block widgets experience. Contributors are aiming to hit the following timeline to ship 9.0 before the next major WordPress release:</p>\n\n\n\n<ul><li>Beta: July 8.</li><li>RC: July 12.</li><li>Final:&nbsp;<strong>July 16</strong></li></ul>\n\n\n\n<p>BuddyPress entered the world of blocks with the release of version 6.0 in May 2020, allowing users to insert a specific Member or Group into content. Version 7.0, released six months later, introduced blocks for featuring a list of members, a list of groups, and the ability to embed a public activity post. Over the next few weeks, BuddyPress contributors will continue the process of <a href="https://github.com/buddypress/bp-blocks/issues/37">migrating the rest of the BuddyPress component widgets to blocks</a>. These include the following:</p>\n\n\n\n<ul><li><strong>Blogs Recent Posts Widget</strong>: A list of recently published posts from across the network</li><li><strong>BP Core Login Widget</strong>: Shows a Log In form to logged-out visitors, and a Log Out link to those who are logged in</li><li><strong>BP Core Friends Widget</strong>: A dynamic list of recently active, popular, and newest Friends of the displayed member. Widget is only shown when viewing a member profile</li><li><strong>BP Groups Widget</strong>: A dynamic list of recently active, popular, newest, or alphabetical groups</li><li><strong>BP Core Members Widget</strong>: A dynamic list of recently active, popular, and newest members</li><li><strong>BP Core Recently Active Widget</strong>: Profile photos of recently active members</li><li><strong>BP Core Who&rsquo;s Online Widget</strong>: Profile photos of online users</li><li><strong>BP Messages Sitewide Notices Widget</strong>: Display Sitewide Notices posted by the site administrator</li></ul>\n\n\n\n<p><strong>BP Nouveau widgets:</strong></p>\n\n\n\n<ul><li><strong>BP Latest Activities</strong>: Display the latest updates of your community having the types of your choice</li><li><strong>BP Nouveau Navigation Widget</strong>: Displays BuddyPress primary nav in the sidebar of the site. (Must be used as the first widget of the sidebar and only once.)</li></ul>\n\n\n\n<p>In addition to building a block for every BuddyPress widget, contributors are aiming to make it possible to <a href="https://buddypress.trac.wordpress.org/ticket/8496">transform existing BP widgets into their corresponding BP block</a>.</p>\n\n\n\n<p>With the new block widgets screen imminently landing in WordPress, BuddyPress has to make this move forward to keep pace with the progress of the block editor&rsquo;s march beyond use in the content editor. Otherwise, BuddyPress users would need to <a href="https://wptavern.com/classic-widgets-plugin-disables-wordpress-5-8s-upcoming-block-based-widgets-system">disable block widgets with the Classic Widgets plugin</a> in order to maintain access to BuddyPress core widgets.</p>\n\n\n\n<p>Contributors are also working on creating a new Follow component, a frequently requested feature which would use the now abandoned <a href="https://github.com/r-a-y/buddypress-followers">BuddyPress Follow</a> plugin as inspiration. The feature will work similar to Twitter following or the Facebook follow button that allows users to see public activity posts for those they are following. The Follow component is being built as a plugin first and will ship with 9.0 if it is ready in time.</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, 29 Jun 2021 01:07: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: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:58:"WPTavern: Diving Into WordPress 5.8’s New Widgets Screen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119259";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:155:"https://wptavern.com/diving-into-wordpress-5-8s-new-widgets-screen?utm_source=rss&utm_medium=rss&utm_campaign=diving-into-wordpress-5-8s-new-widgets-screen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6657:"<p class="has-drop-cap">It has been a while since I have touched widgets. Once the site editor landed in the Gutenberg plugin, I almost exclusively dropped the old sidebar paradigm and moved to block templates. Reactivating old themes and jumping into the widgets screen felt like time-traveling into a bygone era.</p>\n\n\n\n<p>After months of being deeply embedded within block themes, it is hard to imagine moving back to the sidebar widgets system that most WordPress users are still using today.</p>\n\n\n\n<p><a href="https://wptavern.com/wordpress-5-8-beta-1-released-new-blocks-new-widgets-screen-and-pattern-directory-on-deck">WordPress 5.8 is slated to ship</a> with a small taste of bringing blocks outside of the content editor. However, it can feel like a surface-level refresh of a dying system, one that does not always work.</p>\n\n\n\n<p>Block-based widgets are part of the transitional phase between classic WordPress and the future, which centers on a complete site editor. Once the bulk of themes are built atop blocks, the need for widgets will wane. The site editor and block themes do not support the old sidebar system. Instead, users will be able to place blocks anywhere.</p>\n\n\n\n<p>Last October, I asked the question: <a href="https://wptavern.com/are-block-based-widgets-ready-to-land-in-wordpress-5-6">Are Block-Based Widgets Ready To Land in WordPress 5.6?</a> At the time, the widgets screen was expected to launch with the final release of 2020. However, the development team pulled back on the feature&rsquo;s inclusion, primarily because the customizer implementation was sub-par.</p>\n\n\n\n<p>Asking the same question of WordPress 5.8, my answer is mostly the same. It is time to ship the current feature and prepare for a future without widgets. There are so many components that are far more exciting around the corner. The primary user-experience issues will linger around until users have moved on to block themes.</p>\n\n\n\n<p>I have long been in the camp of starting from a clean slate for block themes, letting widgets die out. However, the path WordPress has chosen is to create this stepping stone for users who may be on traditional themes for a while. It provides an opportunity to use blocks outside of the editor, which may be a leap forward for many.</p>\n\n\n\n<p>With the vast number of libraries, one-off blocks, and support from plugin authors, users have a wealth of block choices at their fingertips. Right now, if there is no equivalent widget, those users can only ever use those blocks in their content. Within a block-widget system, that limitation does not exist.</p>\n\n\n\n<p>It also lifts some burdens from developers. Those who want to shed some of their old code and go all-in on blocks can begin considering deprecating or retiring widgets.</p>\n\n\n\n<p>Transitioning to the new Widgets screen should feel simple to users familiar with the WordPress content editor. Inserting blocks is the same. The difference is that each sidebar has its own container.</p>\n\n\n\n<img />Widgets screen with a Gallery block in the Footer sidebar.\n\n\n\n<p>The range of blocks within core WordPress could also let users drop some of their widgets-based plugins. One of the most popular types of widgets over the years has been for handling post lists. There are dozens of such plugins and an untold number of themes that include one. Coupled with WordPress 5.8&rsquo;s Query Loop block, users can now recreate many of those widgets themselves.</p>\n\n\n\n<img />Custom post list using the Query Loop block.\n\n\n\n<p>Much of this depends on the theme&rsquo;s design support of blocks and whether it will accommodate anything other than traditional widgets.</p>\n\n\n\n<p>Customizer support for block widgets is lightyears ahead of where it was just a few short months ago. However, it feels awkward at best. There is a deep feeling of not belonging. While it was a remarkable programming feat to make the two features work together, the user experiences are nearly a decade apart.</p>\n\n\n\n<img />Editing a Heading block in the customizer.\n\n\n\n<p>Despite the customizer providing a live preview, the Widgets screen in the WordPress admin gives the necessary workspace. Trying to squeeze the block editor into the tiny customize controls panel was never going to be an ideal experience, and it still is not. It gets the job done, but I recommend the traditional widgets screen for fewer headaches.</p>\n\n\n\n<h2>Problems Remain</h2>\n\n\n\n<p class="has-drop-cap">In the eight months since I first dived into the block-based widgets, the system has been overhauled. However, the potential issues I brought up remain. Just dropping blocks into a sidebar can have mixed results. For example, compare a Legacy Widget to Heading and Latest Comments blocks in the footer sidebar of the popular OceanWP theme:</p>\n\n\n\n<img />Mismatched headings and colors.\n\n\n\n<p>The issue is that WordPress treats every block as a widget. Traditionally, widgets have had both a title and content. Blocks have no such concept. A Heading followed by something like a Paragraph, Latest Comments, or another block has no special meaning in the block system. They are all treated separately.</p>\n\n\n\n<p>This issue is in full view when adding blocks to the default Twenty Twenty-One WordPress theme:</p>\n\n\n\n<img />Block treated as widget in Twenty Twenty-One footer sidebar.\n\n\n\n<p>Notice the Heading and Latest Comments blocks are columnized because they are seen as separate widgets.</p>\n\n\n\n<p>To address this, users must add multiple blocks into a Group block if they want them treated as a single &ldquo;widget.&rdquo; It is a simple matter, but it could still be a usability hurdle for some.</p>\n\n\n\n<p>Even with a fix in place, there is no guarantee that blocks will appear as the widgets the theme author intended.</p>\n\n\n\n<p>I long ago gave up on the hope that there would be better handling for block widgets. The <a href="https://wptavern.com/classic-widgets-plugin-disables-wordpress-5-8s-upcoming-block-based-widgets-system">Classic Widgets plugin</a> is available for those who need it, and <a href="https://developer.wordpress.org/block-editor/how-to-guides/widgets/opting-out/#using-remove_theme_support">theme authors can opt-out</a>. These are necessary tools for an experience that can range from downright awesome to utterly broken.</p>\n\n\n\n<p>Bringing blocks outside of the content editor for traditional theme users is probably necessary for the transition, but the current site editor experience already feels much smoother than block widgets. The long-term focus should be on moving away from the dated concept of widgets and into a WordPress front-end 100% built on blocks.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 28 Jun 2021 23:52:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:96:"Gutenberg Times: Theme.json Resources, Block Patterns and WordPress 5.8 – Weekend Edition #175";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=18320";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://gutenbergtimes.com/theme-json-resources-block-patterns-and-wordpress-5-8-weekend-edition-175/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:13004:"<p>Howdy, </p>\n\n\n\n<p>We enjoy cooling off at the community pool after our lunch walks. It&#8217;s the simple things, right? </p>\n\n\n\n<p>I learned so much in this week&#8217;s Live Q &amp; A! You might too. Jeff prepared a insightful demo of the basics. Thank you to all those watching and asking great questions! It was a pleasure and honor to have Daisy Olson, Tammie Lister and Jeff Ong on the show. <a href="https://gutenbergtimes.com/theme-json-for-wordpress-theme-authors-demo-and-live-q-a-w-daisy-olson-tammie-lister-and-jeff-ong/">The recording is available here.</a> So are the links to the shared resources and the transcript. </p>\n\n\n\n<p>What else happened this week in WordPress? Amazingly plenty. Get yourself your favorite beverage and start reading and watching. </p>\n\n\n\n\n\n<p>Yours, 💕<br />Birgit</p>\n\n\n\n\n\n<h2>Release week at WordPress</h2>\n\n\n\n<p>WordPress is such a fantastic open-source project. I admire the team and the people in it so much! </p>\n\n\n\n<p>The <a href="https://wordpress.slack.com/archives/C01VACX5E2W">public Slack channel of the release squad</a> helped me understand more of the complexities behind making software that is used by many millions of people all over the world. If you ever get a chance to spend a few minutes scrolling through the discussions on slack, on trac or GitHub, do it. Meet the people, who bring the work of hundreds of contributors over the finish line. Meet the contributors. </p>\n\n\n\n<p><a href="https://make.wordpress.org/core/5-8/">WordPress 5.8 Beta 4</a> is out and ready for your testing. WordPress 5.8 RC 1 is scheduled for June 29th, 2021. That comes with a hard string freeze, and the Polyglot teams get into high gear with translations. It&#8217;s also the deadline for DevNotes of the more significant changes coming  with this release. </p>\n\n\n\n<p><a href="https://make.wordpress.org/core/2021/06/24/whats-new-in-gutenberg-10-9-23-june/">Gutenberg 10.9 and 10.9.1</a> were released. Some bug fixes will be ported back to be included in the WordPress 5.8. Grzegorz Ziolkowski and I recorded the Gutenberg Changelog #46 yesterday, and it will be published on Monday. Our editor, Sandy, is on a well-deserved break over the weekend.  <a href="https://wptavern.com/gutenberg-10-9-renames-the-query-block-adds-collapsible-list-view-items-and-rolls-out-rich-url-previews"><strong>Justin Tadlock </strong>took 10.9 </a>for a spin at the WPTavern. </p>\n\n\n\n<p>&#8212; <a href="https://gutenbergtimes.com/podcast/changelog-46-devnotes-for-wordpress-5-8/">Gutenberg Changelog #46 is now available</a> &#8212; 6/27</p>\n\n\n\n\n<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2021&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly.  <a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/">The index 2020 is here</a></p>\n\n\n\n\n<h2>Theme.json Resources</h2>\n\n\n\n<p>You can read an&nbsp;<a href="https://make.wordpress.org/core/2021/06/25/introducing-theme-json-in-wordpress-5-8/"><strong>Introducing theme.json in WordPress 5.8</strong></a>&nbsp;by&nbsp;<strong><a href="https://twitter.com/nosolosw">Andre Maneiro</a></strong>&nbsp;on the Core Make blog.</p>\n\n\n\n<p>You can read up on the details specifications in the Block Editor Handbook:&nbsp;<strong><a href="https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/">Global Settings &amp; Styles (theme.json)</a>.</strong></p>\n\n\n\n<p>Another fantastic way to get your feet wet is to heed the&nbsp;<a href="https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/"><strong>Call for Testing #8</strong></a>&nbsp;out of the FSE outreach program. <strong>Anne McCarthy</strong> has some interesting tasks for you. <a href="https://wptavern.com/fse-outreach-round-8-a-developer-centric-call-for-testing-theme-json-configuration"><strong>Justin Tadlock </strong></a> has more for you on the <em>WordPress Tavern</em> </p>\n\n\n\n<p><strong>Tammie Lister</strong>&nbsp;started a new project <a href="https://ephemeralthemes.com/">&#8220;Ephemeral Themes&#8221;</a> and shared her thoughts on theme.json and why she is excited again for theme development.&nbsp;<a href="https://ephemeralthemes.com/2021/06/20/theme-json-inspires/"><strong>Theme.json inspires</strong></a></p>\n\n\n\n<p>The Gutenberg team is in ongoing discussion about various topics. Two were raised during the <a href="https://gutenbergtimes.com/theme-json-for-wordpress-theme-authors-demo-and-live-q-a-w-daisy-olson-tammie-lister-and-jeff-ong/">Live Q &amp; A</a>. Both could use your opinion and ideas.</p>\n\n\n\n<ul><li><a href="https://github.com/WordPress/gutenberg/issues/29568">Default Colors, Theme Colors, and Custom Colors</a></li><li><a href="https://github.com/WordPress/gutenberg/issues/20244">Responsive Global Styles as a work in progress</a></li></ul>\n\n\n\n<p>A good way to get started and see the configuration in action is to study the themes available in the&nbsp;<a href="https://github.com/WordPress/theme-experiments/"><strong>Theme Experiments repository</strong></a>&nbsp;on GitHub.</p>\n\n\n\n<h2>Full Site Editing </h2>\n\n\n\n<p>Another theme by <strong>Ana Segota,</strong>  built for the Site editor will come to the WordPress directory. Justin Tadlock took it for a spin. <a href="https://wptavern.com/clove-a-showcase-of-block-patterns-by-anariel-design"><strong>Clove: A Showcase of Block Patterns by Anariel Design</strong></a>.</p>\n\n\n\n<p><strong>Anne McCarthy </strong>published <a href="https://make.wordpress.org/test/2021/06/24/fse-program-polished-portfolios-summary/"><strong>FSE Program Polished Portfolios Summary</strong></a> with the updated feedback from a great group of participants. </p>\n\n\n\n<p>On her personal blog, <strong>Anne McCarthy</strong> also published <a href="https://nomad.blog/2021/06/11/on-future-outreach-program-models-in-the-wordpress-community/"><strong>On Future Outreach Program Models in the WordPress Community</strong></a>. She shared some of her learn lessons on running the FSE outreach program and what needs to happen to make this a permanent contributor activity within WordPress. </p>\n\n\n\n<p>Here is the <a href="https://make.wordpress.org/test/2021/06/09/upcoming-fse-outreach-program-schedule-june-july/">Upcoming FSE Outreach Program Schedule</a></p>\n\n\n\n<p><a href="https://twitter.com/scruffian"><strong>Ben Dwyer</strong> </a>on ThemeShaper posted <strong><a href="https://themeshaper.com/2021/06/23/universal-themes-some-ideas/">Some Ideas for Universal Themes</a>.</strong> He wrote: &#8220;A universal theme would work in both editing modes.&nbsp; A user should be able to build a site in classic mode and switch to FSE mode when the Site Editor is more mature or when they are ready to try all the extra tools that Full Site Editing will bring. Changes to a theme in classic mode should be reflected when I enable the Site Editor.&#8221; and goes into more details on how that could work. At Automattic, they experiment with the <a href="https://github.com/Automattic/themes/tree/trunk/quadrat">Quadrat theme</a>. </p>\n\n\n\n\n<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s main (trunk) branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>\n\n\n\n<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge" /></p>\n\n\n\n<p></p>\n\n\n\n\n<h2>Block Patterns</h2>\n\n\n\n<p>About 80 Patterns have been published in the Pattern Directory on WordPress.org, <strong>Kjell Reigstad</strong> reported in his <strong><a href="https://make.wordpress.org/design/2021/06/23/update-initial-patterns-for-the-patterns-directory/">Update: Initial Patterns for the Patterns Directory</a> </strong>over the last two weeks, Kjell, Mel Choyce and Beatriz Fialho were fielding community submissions and working with the designers. There are wonderful and useful patterns, you can use for your site.</p>\n\n\n\n<p>The discussion about <strong>Block Patterns</strong> on the WordPress Tavern has readers ruminating about <strong><a href="https://wptavern.com/wordpress-theme-lock-in-silos-and-the-block-system">Theme Lock-In, Silos, and the Block System</a>.</strong> In a Post Status discussion, <strong>Tammie Lister </strong>thought the opposite is true. &#8220;it&#8217;s going to be easier, not harder, to switch with the newer set up.&#8221; And then she continues: &#8220;Try swapping between themes now. It&#8217;s not a picnic. It&#8217;s often a sad rained on picnic with soggy sandwiches of sadness, even with the best hope.&#8221; 🌧️ I might steal that metaphor from Tammie 💕</p>\n\n\n\n<p>Speaking of Block Patterns, the design team also brought Block Patterns to all WordPress Twenty themes, all the way back to Twenty-Ten. They will be released with WordPress 5.8. <strong>Milana Cap</strong> published about these <strong><a href="https://make.wordpress.org/core/2021/06/21/bundled-themes-changes-in-wordpress-5-8/">Bundled themes changes in WordPress 5.8</a>.</strong> They are a great inspiration for designer on what can be possible with Block Patterns now. Justin Tadlock at the WordPress Tavern also <a href="https://wptavern.com/a-throwback-to-the-past-refreshing-old-twenty-wordpress-themes-with-block-patterns">took the new patterns out for a spin.</a></p>\n\n\n\n<p>In <strong><a href="https://themeshaper.com/2021/06/25/theme-patterns-for-the-site-editor/">Theme patterns for the Site&nbsp;Editor</a> </strong> <strong>Kjell Reigstad</strong> show off a new UI to handle the display of different patterns for a header. It is an expansion of the block pattern display for Query Loop for various Post list layouts. He also shared his code and a short tutorial. Kjell also used the Quadrat theme from the Automattic repository </p>\n\n\n\n\nHeader Patterns in Quadrat Theme / Automattic\n\n\n\n\n<h2>Block Development and Plugins</h2>\n\n\n\n<p>For block builders, the Core-editor team published two DevNotes this week. </p>\n\n\n\n<p><strong><a href="https://make.wordpress.org/core/2021/06/23/block-api-enhancements-in-wordpress-5-8/">Block API Enhancements in WordPress 5.8</a> </strong>by <strong>Grzegorz Ziolkowski</strong>, encouraging plugins developers to using the block.json metadata file. He lists under the benefits: </p>\n\n\n\n<ul><li>code sharing between JavaScript and PHP and other languages, </li><li>optimized enqueuing of assets on the frontend to support performance increases.</li><li>Allows listing of the block on the Block Type REST API endpoint </li><li>It&#8217;s a requirement for blocks to be included in the WordPress Plugin Directory  </li></ul>\n\n\n\n<p><a href="https://make.wordpress.org/core/2021/06/25/block-supports-api-updates-for-wordpress-5-8/"><strong>Block supports API updates for WordPress 5.8</strong></a>&nbsp; by <strong>Daisy Olsen</strong>, which outlines and additional support options for color, duotone, fontSize, lineHeight, spacing options for blocks and themes. </p>\n\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p class="has-text-align-center"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>\n\n\n\n<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email">Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n\n<p>Featured Image: <a target="_blank" rel="noreferrer noopener" href="https://commons.wikimedia.org/w/index.php?curid=6068229">&#8220;File:Lego Color Bricks.jpg&#8221;</a>&nbsp;by&nbsp;<a href="https://www.flickr.com/people/13403905@N03" target="_blank" rel="noreferrer noopener">Alan Chia</a>&nbsp;is licensed under&nbsp;<a href="https://creativecommons.org/licenses/by-sa/2.0?ref=ccsearch&atype=rich" target="_blank" rel="noreferrer noopener">CC BY-SA 2.0</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, 26 Jun 2021 19:18:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Birgit Pauli-Haack";s: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:127:"Gutenberg Times: Theme.json for WordPress Theme Authors – demo and  Live Q &amp; A w/ Daisy Olson, Tammie Lister and Jeff Ong";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=18324";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:125:"https://gutenbergtimes.com/theme-json-for-wordpress-theme-authors-demo-and-live-q-a-w-daisy-olson-tammie-lister-and-jeff-ong/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:56956:"<p>On June 24th, we hosted Gutenberg Times Live Q &amp; A on the topic  <strong>&#8220;Theme.json for Theme Authors &#8211; Getting started with theme development for Full-site Editing&#8221;</strong> It was a great pleasure and privilege to have <a href="https://twitter.com/DaisyOlsen">Daisy Olson</a>, developer advocate at Automattic, <a href="https://twitter.com/karmatosed">Tammie Lister</a>, design lead at Extendify and <a href="https://twitter.com/jffng">Jeff Ong</a>, code wrangler at Automattic on the show. </p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<div class="toolbelt-video-wrapper"></div>\n</div>\n\n\n\n<p>Jeff Ong prepared <a href="https://youtu.be/dBwhHKKblhU?t=831">a demo</a> for us, and then attendees had some interesting questions our panelists answered. You can read the transcript below.</p>\n\n\n\n<p>WordPress 5.8 will come with the infrastructure and foundation to control the block editor and theme settings via the configuration file theme.json. JSON is a universal data format that is readable to PHP and JavaScript alike.</p>\n\n\n\n<blockquote class="wp-block-quote is-style-large"><p>Themes no longer have to pretend that they&#8217;re plugins.</p><cite>Tammie Lister</cite></blockquote>\n\n\n\n<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#0-resources-about-theme-json-and-themes-for-full-site-editing">Resources about theme.json and themes for Full-site editing</a></li><li><a href="https://gutenbergtimes.com/feed/#1-themes-for-full-site-editing-in-the-word-press-org-repository">Themes for Full-site Editing in the WordPress.org repository</a></li><li><a href="https://gutenbergtimes.com/feed/#2-strong-what-will-change-most-for-the-theme-developers-when-building-themes-for-full-site-editing-strong">What will change most for the theme developers when building themes for full-site editing?</a></li><li><a href="https://gutenbergtimes.com/feed/#3-demo-configuring-the-block-editor-with-theme-json-file">Demo: Configuring the block editor with theme.json file</a></li><li><a href="https://gutenbergtimes.com/feed/#3-meta-charset-utf-8-why-do-we-want-to-rewrite-css-in-json">Why do we want to rewrite CSS in JSON</a></li><li><a href="https://gutenbergtimes.com/feed/#4-what-happens-when-you-update-the-color-palette-will-saved-blocks-have-the-new-colors">What happens when you update the color palette? Will saved blocks have the new colors?</a></li></ul></div>\n\n\n\n<h2 id="0-resources-about-theme-json-and-themes-for-full-site-editing">Resources about theme.json and themes for Full-site editing</h2>\n\n\n\n<p>During the show, we mentioned a few places where you can dive in and learn more about theme.json.</p>\n\n\n\n<p>You can read an <a href="https://make.wordpress.org/core/2021/06/25/introducing-theme-json-in-wordpress-5-8/"><strong>Introducing theme.json in WordPress 5.8</strong></a> by <strong>Andre Maneiro</strong> on the Core Make blog. </p>\n\n\n\n<p>You can read up on the details specifications in the Block Editor Handbook: <strong><a href="https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/">Global Settings &amp; Styles (theme.json)</a>. </strong></p>\n\n\n\n<p>A good way to get started and see the configuration in action is to study the themes available in the <a href="https://github.com/WordPress/theme-experiments/"><strong>Theme Experiments repository</strong></a> on GitHub. </p>\n\n\n\n<p>Another fantastic way to get your feet wet is to heed the <a href="https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/"><strong>Call for Testing #8</strong></a> out of the FSE outreach program. Anne McCarthy has some interesting tasks for you. </p>\n\n\n\n<p><strong>Tammie Lister</strong> started a new blog and shared her thoughts on theme.json and why she is excited again for theme development. <a href="https://ephemeralthemes.com/2021/06/20/theme-json-inspires/"><strong>Theme.json inspires</strong></a></p>\n\n\n\n<p>The Gutenberg team is in ongoing discussion about various topics. Two were raised during the Live Q &amp; A. Both could use your opinion and ideas. </p>\n\n\n\n<ul><li><a href="https://github.com/WordPress/gutenberg/issues/29568">Default Colors, Theme Colors, and Custom Colors</a></li><li><a href="https://github.com/WordPress/gutenberg/issues/20244">Responsive Global Styles as a work in progress</a></li></ul>\n\n\n\n<h2 id="1-themes-for-full-site-editing-in-the-word-press-org-repository">Themes for Full-site Editing in the WordPress.org repository</h2>\n\n\n\n<ul><li><a href="https://wordpress.org/themes/blockbase/">Block Base</a> by Automattic</li><li><a href="https://wordpress.org/themes/naledi/">Naledi </a>by Anariel Design</li><li><a href="https://wordpress.org/themes/tt1-blocks/">TT1 Blocks</a> by WordPress contributors, the FSE sibling of the Twenty-Twenty-One Theme</li><li><a href="https://wordpress.org/themes/block-based-bosco/">Block-Based Bosco</a> by Fränk Klein</li><li><a href="https://wordpress.org/themes/armando/">Armando</a> by Carolyn Newmark</li><li><a href="https://wordpress.org/themes/q/">Q </a>by Ari Stathopoulos</li><li><a href="https://wordpress.org/themes/hansen/">Hansen</a> by Uxl Themes</li></ul>\n\n\n\n<p class="has-larger-font-size" id="transcript"><strong>Transcript</strong></p>\n\n\n\n<p class="has-text-align-center" id="transcript"><em><span class="has-inline-color has-accent-color">This transcript is still a work in progress</span></em><strong><span class="has-inline-color has-accent-color"> </span></strong>&#8211; Birgit</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Well, and then we can start the webinar here. The webinar is now live and welcome to our 28th Gutenberg live Q and A on this June 24th. My name is Birgit Pauli-Haack and I am your host for today&#8217;s discussion. Thank you all for watching, and it&#8217;s great to have you. And while you all come in, use the chat window to tell us where you are and where you&#8217;re watching from.&nbsp;</p>\n\n\n\n<p>And today we will discuss a new way to configure themes, that is black themes, with global styles and settings file theme.json. And it will enable theme developers to centralize all the block-based settings, color palettes, font sizes, and other block-based customizations. This way you will also control which of the other block features the theme supports or does not support.&nbsp;</p>\n\n\n\n<p>So that&#8217;s my simple mind&#8217;s description of the new features and I&#8217;m so thrilled to have three experts on the show to go beyond this simple explanation and help theme developers to get started. I&#8217;m extremely honored to have Daisy Olsen, developer advocate at Automatic and WordPress contributor. Hey, good to have you. Also Jeff Ong, code wrangler at Automatic.</p>\n\n\n\n<p><em>Jeff Ong: </em>Hello.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Thanks for being here. And at last but not at least Tammie Lister, design lead at Extendify.</p>\n\n\n\n<p><em>Tammie Lister:</em> Hello.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> We&#8217;ll do some proper introduction in less than a minute. I just have a few housekeeping notes. So after the introduction, we&#8217;ll have a first round robin question and then we see a demo. Jeff was working really hard on it and I think he was the only one repairing hard for this live Q and A. And then we&#8217;ll discuss the different angles and how they get started. And then, of course, answer your question.</p>\n\n\n\n<p>Speaking of questions, how do you pose your questions? There&#8217;s a Q and A on the bottom of the screen, a kind of icon. You click on that and write your question. And for those watching on YouTube use the chat window next to the video player. And so saying hi. Hi, Victor. From Buenos Aires in Argentina. Awesome. Thank you for being here. All right. When you do comments and questions, so please be kind even if you disagree.&nbsp;</p>\n\n\n\n<p>This is a family endeavor. All right. Well, I&#8217;m thrilled you all agreed dear panelists to come on the show and I get an hour to talk with you about your work. So, Daisy, tell us a little bit about you, where are you&#8217;re located and what is it that you do as developer advocate on the purpose project and at Automatic?</p>\n\n\n\n<p><em>Daisy Olsen: </em>Yeah. I&#8217;m Daisy Olsen and I live in New Hampshire in the United States. It&#8217;s a beautiful day here right now unlike some parts of this country that are really hot. We got the cool weather over here this week. So as a developer advocate, I talk about WordPress a lot.</p>\n\n\n\n<p>I get out and do workshops, teach classes, write documentation and just stay involved and close to the projects development so that I know what&#8217;s going on theoretically and can share that out particularly with plugin and theme developers as well as agencies and freelancers and things like that.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Awesome. So glad you&#8217;re here. Thank you. So, Tammie, thank you for coming back to the show. It&#8217;s been over three years. The last time you were on the show was just after Gutenberg was merged into Core and you were one of the three leads with Matias Ventura and Joen Asmussen. </p>\n\n\n\n<p>And you shared a lot about the journey of Gutenberg and the philosophy behind it. So I will put the link to the show into the show notes for you who have been coming later to Gutenberg. But this year you joined the WordPress product company Extendify. So what do you do there?</p>\n\n\n\n<p><em>Tammie Lister:</em> First of all, has it been three years? That goodness. Time flies. So in Extendify I focus on design. So our solutions extend the editor. And then the aim is to make it even more usable for people&#8217;s purpose that they want to use it for. And I&#8217;m really, really excited about that.</p>\n\n\n\n<p>So it means that people can have the best experience from the content they&#8217;re creating, to the layout, the patterns, the styles, whatever that the editor enables, that&#8217;s really what I&#8217;m focusing on. So it&#8217;s a interesting new challenge to do. And you have blew my brain with that time span. You really have. That&#8217;s awesome.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Well, it&#8217;s also over three years that Gutenberg times us. So I&#8217;ve been part of that journey so for so long.</p>\n\n\n\n<p><em>Tammie Lister:</em> Congrats.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Nothing really held my attention for so long. And normally I get really bored. Well, I&#8217;m also really happy that Extendify took over <a href="https://wordpress.org/plugins/editorplus/">Editor Plus</a> from Munir Kumal and the <a href="https://wordpress.org/plugins/block-options/">EditorsKit</a> from Jeffrey Carandang. So, those have a more sustainable way now to access because both Munir and Jeffrey seem to have&#8230; Munir joined you, but Jeffrey moved on to be a consultant at , I think, 10up.</p>\n\n\n\n<p><em>Tammie Lister:</em> It&#8217;s so really exciting.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. I imagine. So thank you also to Jeff Ong for joining us today as well. You&#8217;re a code wrangler in Automatic and what have you been working on lately except for the demo. I know about that.</p>\n\n\n\n<p><em>Jeff Ong</em>: Well, first, thank you for having me and hosting this. Awesome to be here. I feel very honored to be with three on-time contributors. So super cool. At Automattic, I&#8217;ve been working on theme development, pretty solely focused on that for the last year. And my background is not in WordPress. </p>\n\n\n\n<p>So it&#8217;s kind of been an interesting journey to transition and learn about the ecosystem and really coming at a transitory time figuring out how do we kind of move into this new block-based paradigm? How do we make themes that work with the block editor really well and can hopefully unlock more creativity for just really great design. And I can tell you what sites again. Well, making new themes and figuring out how to do that with the latest version of Gutenberg, which turns out every day.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> So the viewers follow Jeff Ong, he&#8217;s going to teach you how to do things with the Block Editor. And we will soon see a little demo of that. It&#8217;s what Daisy said, &#8220;What you did in five minutes, I taught a course on that in three hours.&#8221; So it&#8217;s going to be a little fast paced today.&nbsp;</p>\n\n\n\n<h2 id="2-strong-what-will-change-most-for-the-theme-developers-when-building-themes-for-full-site-editing-strong">What will change most for the theme developers when building themes for full-site editing?</h2>\n\n\n\n<p>But before we head into media&#8217;s raised, I would like to ask each of you, so what do you think will change most for the theme developers when building themes? These are for agency building custom themes for the clients or for theme shops rolling out new themes to sell. Do you want to start, Tammie?</p>\n\n\n\n<p><em>Tammie Lister:</em> Yeah. That&#8217;s interesting because I think perhaps it&#8217;s a change if you wanted to be a change. Because lots of this is an opt-in, as is the way. WordPress, the best way to opt-in. I go back to a lot of times that this is a freeing of things and I think it brings an opportunity that has pros and cons, ups and downs with opportunities.</p>\n\n\n\n<p>But plug-ins themes no longer have to pretend that they&#8217;re plugins and they no longer have to be everything and have to be things that they weren&#8217;t intended to be in the first. So I think that that is a challenge in itself because there&#8217;s a certain way that you maybe thought you had to do things and now you don&#8217;t have to work around things. We often have to work around things in WordPress.&nbsp;</p>\n\n\n\n<p>And if you don&#8217;t have to work around it, it can feel a little bit peculiar, but once you realize you don&#8217;t have to do that, it&#8217;s actually really awesome. But you have to realize you don&#8217;t have to and that WordPress was getting in the way. I also think as a result there&#8217;s going to be a space for more creativity, and this can also be really to challenging because maybe you were limited to what you could do creativity wise because of just the confinements of the space and the confinements of what you could do before.&nbsp;</p>\n\n\n\n<p>And it&#8217;s going to open things again to a lot more people. And a lot more people who maybe didn&#8217;t have access to a theme developer with experience who knew the exact ins and outs of it. So I think that&#8217;s a challenge because new people in this space, new creativity. But honestly I think it&#8217;s a good thing. It&#8217;s just if you want to and you&#8217;re open to it and you can kind of explore those new ways, but I don&#8217;t think it&#8217;s a change that you have to make. I think that&#8217;s the thing.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Awesome. Thank you. Daisy, what do you think?</p>\n\n\n\n<p><em>Daisy Olsen: </em>So I think I would agree with Tammie that the barrier of entry for a new theme designer. And I think that&#8217;s one of the key things is it&#8217;s bringing the design back to theming. Theming over time became very functional. We had a lot of theme companies that were trying to make their themes as flexible, powerful and feature-ful as possible to reach a wide variety of people.</p>\n\n\n\n<p>And I think that we can see some opportunity for vertically oriented designs coming out where you have a theme that is geared towards a restaurant or geared towards, I don&#8217;t know, a salon or a certain kind of a business or even a personal site.</p>\n\n\n\n<p>And I think that there&#8217;s a lot of opportunity to be able to have a lot of variety out there in the marketplace so that when someone asks you inevitable question, because this was probably the most common question when I was working for a thing company is which theme is best for this?&nbsp;</p>\n\n\n\n<p>I&#8217;m doing this kind of a site, which themes should I use. And it could make it so, well, here are five that are really geared towards what you&#8217;re trying to do instead of, oh, you can use any of them. You just have to do all this work to get it to look bright.</p>\n\n\n\n<p>Birgit Pauli-Haack: Yeah. That&#8217;s a good point. Thank you. Jeff?.</p>\n\n\n\n<p><em>Jeff Ong:</em> Definitely, from a design perspective, it&#8217;s super exciting. I want to highlight maybe a little bit more from the development side. This seems like the biggest opportunity or clearest opportunity to ensure that your theme is integrated with the editor. That the things that you&#8217;re doing with the editor and your ability to customize it to control what presets and options are available there to the users of the theme, this is the theme [inaudible 00:12:27].</p>\n\n\n\n<p>It&#8217;s a unifying kind of idea and single point of truth. Talking about theme.json and even just this whole concept of how do we bring the experience together. I think we have an opportunity to do that and that&#8217;s going to change even in some small level. Even if your theme.json cloud just as a few settings. You can take it slow like Tammie was saying. Incorporate parts of it because to me you have this new contract now that can really unify things and bring things together from a lot of disparate parts and pieces.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Lots to think about. And I agree with all of you. I had this pleasure last year that I took over themes from agencies and they were so powerful and all the things that normally a plug-in will do, custom post types and rigid and all that. It&#8217;s all in one place and we won&#8217;t be able to change a theme at all. </p>\n\n\n\n<p>So now this is definitely going to make life a lot easier for site owners as well So lots to think about and listening to you is quite inspiring to kind of think, oh, well how many direction can my brain go now? But, Jeff, are you ready for your demo? I think it would be helpful for all the people here on the call to see what it&#8217;s all about and how it kind of gets started.</p>\n\n\n\n<p><em>Jeff Ong:</em> Yes. We have 10 minutes roughly. Yes. Can you see my screen? </p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> We can see your screen. Yes.</p>\n\n\n\n<h2 id="3-demo-configuring-the-block-editor-with-theme-json-file">Demo: Configuring the block editor with theme.json file</h2>\n\n\n\n<p><a href="https://www.youtube.com/watch?v=dBwhHKKblhU&t=18s">14.02</a></p>\n\n\n\n<p>Jeff Ong: So we have a blank theme here and I just want to kind of go over some, not going to cover everything, but some of the key parts of that theme.json introduces and show how that impacts a blank theme and also the editor. So hopping over to my code editor. I have my theme.JSON here. This is a really basic, simple theme and nothing going on yet.&nbsp;</p>\n\n\n\n<p>In here I&#8217;m going to go ahead and the first thing I want to talk about are the settings of your theme.JSON. Settings are kind of what control or give you the ability to configure the editor and what kind of customization options are present to a user and the theme. The only thing I have right now is the layout, which we&#8217;ll get to in a second. But let&#8217;s say I want to add some color options here.</p>\n\n\n\n<p>Previously it would be done in the functions PHP. I have kind of a few sheets over here. Sorry. I need to hide these meeting control. I&#8217;m going to copy a color palette from this. I&#8217;m going to set a palette that&#8217;s going to become available to me in my theme. I go to edit the same post. In here I see my cornso, my orange, red, and color blue that&#8217;s become available to me.&nbsp;</p>\n\n\n\n<p>What&#8217;s pretty interesting about this is before you would have had to kind of go into functions at this whole palette and then also define the class name, something like this to actually apply those styles. Let&#8217;s say I want this heading to be orange, update it. Show it here. I get all this cool stuff for free. This class was generated for me by Gutenberg using this preset and that I have defined meeting controls defined here in my palette options.&nbsp;</p>\n\n\n\n<p>Another cool thing or interesting about the possibility here is within the same configuration. Let&#8217;s say I&#8217;m the theme designer. I have the option right now to change the color to kind of anything I want. The powerful thing about theme.json at this time is it can actually turn something like this off. I actually don&#8217;t want people or my users to be able to change anything, change the color palette.</p>\n\n\n\n<p>But let&#8217;s go ahead and reset this back here. Turned off custom colors within theme.json. And then back here you&#8217;ll see that option has disappeared. So inaccessible color combinations or just color combinations that you don&#8217;t want to be available. You can turn that off. This is just one of the options that are available. Color is just one of the options that you can customize.</p>\n\n\n\n<p>You can also take a look at something like typography. I think I can find some font sizes here. Refresh. I can see now that those presets were available, are now available to me. I can do the same thing again here too. Say I don&#8217;t actually want people to be able to change all sides here. As a designer I know it&#8217;s best and I don&#8217;t want people putting in random font sizes.&nbsp;</p>\n\n\n\n<p>So disable that and now only my presets are available too. Oh, by the way, this content is just kind of some standard block-based content. Again, I&#8217;m getting all of this kind of for free or for free in a way by just applying some preset values here. Well, I think the next thing that I wanted to cover is going into the last thing. I&#8217;ll cover it within the settings because you can actually change these per block.&nbsp;</p>\n\n\n\n<p>Remember we were looking at color before. I could add a color key to the paragraph block and actually say, just kidding. I want to allow you to be able to change the color of paragraph blocks. Just the paragraph blocks. I can open up the whole thing. So within here now I can see, oh, I can actually change just for paragraph blocks. I go up to my heading. This custom color is not available. This color option is not available.&nbsp;</p>\n\n\n\n<p>If you want to I could also supply a custom palette. I&#8217;m not going to do that, but could say if you wanted a specific palette that&#8217;s just applied for paragraph blocks. That would be how you do it. So I think that&#8217;s it for settings. I&#8217;m going to go ahead and collapse this now and move on to the styles key of our theme.json. And now within here I can start to define some files.&nbsp;</p>\n\n\n\n<p>Remember our colors from up here from the palette. I can go ahead and because I know that WordPress is generating CSS variables based on these palettes, I can go ahead and start to use those within the styles application of the style section of my theme.json. So with the preset color, put orange red. See what else do. These are going to apply at the top level. So this is going to apply to everything.</p>\n\n\n\n<p>Say I only wanted, for instance, my headings to be&#8230; Let&#8217;s make this. Do the same thing in here and say, ah, I just want, actually, let&#8217;s just make my paragraph colors black. So, again, what I&#8217;ve done here is I&#8217;ve set my global kind of text color to this orange red was preset, which was provided by WordPress and generated here to the entire text. And then actually I can go in and target specific block, set the settings for that as well.&nbsp;</p>\n\n\n\n<p>I think we are close. I just want to show, well, if you&#8217;re editing this, something that&#8217;s also probably going to happen and mess this up. It should throw some kind of an error here yet. Notice there when decoding theme.json. So that&#8217;ll let you know there&#8217;s something going on because it&#8217;s pretty easy tip something up here.&nbsp;</p>\n\n\n\n<p>And I think that&#8217;s just a small note is we&#8217;ll likely encounter that if you&#8217;re configuring keys and nested objects trying to figure out how each of those apply. You pause here for a second. I guess the last thing I want to cover too is the concept of elements. So within here, any h2 that I have is going to be applied a specific style here. So I have the same because [inaudible 00:24:24] can appear outside of blocks or links, for example.</p>\n\n\n\n<p>These are restricted to a specific set at the moment. So let&#8217;s just say text. So, again, because this is not actually rendered as a pocket and an element and that can appear anywhere. That&#8217;s something that I can target with this kind of top level elements select here. Everything else here you can target with the name of the block.&nbsp;</p>\n\n\n\n<p>That is most of what I wanted to cover pretty fast, but again all of the settings that you can find here or that I&#8217;m going over, there&#8217;s way more than just color. There&#8217;s spacing, typography and all of that can be found in documentation that Birgit, I think she shared it here. So that I want to open it up. And I guess there are questions. If there are specific parts that anyone would want to go into in a little more detail. Happy to do that.</p>\n\n\n\n<p><em>Daisy Olsen: </em>Thank you, Jeff. </p>\n\n\n\n<p><em>Birgit Pauli-Haack: </em>Thank you, Jeff. This was awesome. Do you want to just say something?</p>\n\n\n\n<p><em>Daisy Olsen: </em>Yeah. I just wanted to say that maybe we could just talk about layout real quick because I think that&#8217;s going to be a big one for 5.8.</p>\n\n\n\n<p><em>Jeff Ong:</em> Yeah. And I kind of skipped over. It was the first thing that was in here. Yes. Layout key is a way for you to quickly define the default, the width of your content within WordPress or within here. So if you see here, if I don&#8217;t define this layout, a lot of my content is just going to be full width by default. </p>\n\n\n\n<p>You can supply two values here. Content size, it&#8217;s just going to be the default width. You can also define, I think it&#8217;s, what is it? Wide size. Wide width. Nothing happened there because I hadn&#8217;t provided it. Maybe there&#8217;s a better way to show that with cover block.&nbsp;</p>\n\n\n\n<p>Birgit Pauli-Haack: Nice. I like it.&nbsp;</p>\n\n\n\n<p><em>Jeff Ong:</em> Pretty cool. You can, I mean, alignment coming together and within a unified system reliably layout content with starting here is pretty powerful stuff I&#8217;d say.</p>\n\n\n\n<p><em>Birgit Pauli-Haack: </em>Yeah. Awesome. So I shared in the chat window, if you haven&#8217;t seen it, the documentation link where you can read up about the theme.json as a whole. When you say, Daisy, that that&#8217;s the layout will be important for 5.8, which part of it would be, where does it come into play?</p>\n\n\n\n<p><em>Daisy Olsen:</em> So with 5.8 with the custom template functionality that&#8217;s coming where you can basically create a custom template for an entire page or a post that would cover your header as well as your content. If you need to have these setting set for the width, especially the content size for it but preferably also wide so that your site knows how wide it should be. </p>\n\n\n\n<p>Otherwise you get kind of the facts that Jeff showed where it was the full width of the page. It didn&#8217;t have anything to contain it down to the width that you want. So for any theme that wants to use the template editor would benefit from having a theme.json file that even if it only has the one thing in it, it would be good way to take advantage of it.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. It&#8217;s an excellent tip. Thank you, Daisy. You heard it here first. So we already got some questions in our Q and A, but I just wanted to have one question for Jeff before. That&#8217;s my prerogative as a host, I get the first question. So if I understood it correctly, so until now, theme.json comes into play I had to create many different places or touch many different places to make a color palette work.</p>\n\n\n\n<p>So, I had to put it in my functions.php and then I also have to put it in my style sheet. Is [inaudible 00:30:04] that I don&#8217;t have to do this anymore, or do I still have to put it into my style sheet, or is it automatically created with when I put the color palette in the theme.json?</p>\n\n\n\n<p><em>Jeff Ong:</em> It is wonderful question. It is automatically created. This is all that that style sheet looks like since this is one of the big very exciting aspects of a theme.json. It&#8217;s that it&#8217;s managing this for you. And then also I think more down the line by providing colors and styles in this way. And then also by applying the styles here you can guarantee that those blocks are going to integrate properly.</p>\n\n\n\n<p>It&#8217;s like the styles for those blocks are going to be more closely tied and actually in how the block is implemented. So no more writing styles that are overwriting that we&#8217;re having to target specific nested blocks. And so there&#8217;s tons of complications to this and there&#8217;s a lot more room to mature and develop, but I think that&#8217;s one of the parts I&#8217;m most excited about. To your point, there&#8217;s one place now where I can define my palette and show how it should be applied. I don&#8217;t have to go into two different places to do it.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> All right. Well, let&#8217;s go to the questions. Victor Kane, from the beginning of the show has already put them in and he&#8217;s particular interested in finding out about the workflow using them theme.json. So one is the best editing alternative for VS Code formatting, and then the second one was the possibility for exporting interactive selections to clipboard and code. I&#8217;m not quite sure I understand the question. Maybe you understand it, Jeff Daisy, Tammie.</p>\n\n\n\n<p><em>Tammie Lister:</em> Personally. So I think this is a personal choice. I&#8217;m going to start with an answer and then go to&#8230; I use VS Code, so I may not be able to give the right answer there. I would be curious to know what you don&#8217;t want in VS Code, and I think that that&#8217;s the thing. This opens up personal&#8230; I&#8217;m going to be really bad at reading the response in chat whilst talking. So I&#8217;m going to be a little bit pertinent and kind of speak first. I&#8217;m sorry, I&#8217;ll get back to it.</p>\n\n\n\n<p>It&#8217;s your personal choice how you write and then you can kind of go back to it. So the thing that I did, this was my workflow, it has been my workflow so far, and I think this is the thing, we&#8217;re all finding our own new workflows with these new toys that we&#8217;re playing with. So what I&#8217;ve been doing is I&#8217;ve been using theme.json.&nbsp;</p>\n\n\n\n<p>I&#8217;ve actually been setting up variables using SAS that have been then pulling in root variables into my theme.json so that I can pull them through. That&#8217;s a weird way to do it. That&#8217;s strange, but the reason being, it means I can reuse and keep things separately. But I&#8217;m sure that everybody on this call has their own little workflows that they are kind of working from.</p>\n\n\n\n<p><em>Daisy Olsen:</em> My approach to that was actually the opposite that I was using my theme.json to set all of my variables so that I didn&#8217;t need SAS, which I think for those that never quite got their head wrapped around preprocessed CSS, it might be a way to simplify things for those that prefer it that way.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Awesome. </p>\n\n\n\n<p><em>Tammie Lister: </em>I think it&#8217;s what you&#8217;re cozy with, right? And I think that&#8217;s the thing. This can adapt to what was your cozy blanket of coding, and you don&#8217;t have to lose that yet, I think.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> All right. So Victor commented on that. If I get the results, I want interactively with the global settings panel on the right-hand side of the editor, can I export that to a theme.json format?</p>\n\n\n\n<p><em>Daisy Olsen: </em>The answer is not right now. I think there&#8217;s discussion in the teams about maybe building it, but it hasn&#8217;t been the highest priority because everything needs to work first before we start working on an exporter. But there are other parts of that can be exported in that full site editing experience that can be exported. So I think it would be a natural progression to add the ability to do a theme.json export.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yes. Definitely there will be.</p>\n\n\n\n<p><em>Tammie Lister:</em> From the very beginning, there were designs in global style. Sorry. The reason I know is that was one thing I did partake on. There was exporting. So I have a feeling if we all wanted to play some little happy bets, there will be exploiting at some point.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. But if we all bet on the same thing, it&#8217;s not really bet, right? Victor, as always, you&#8217;re a little bit ahead of the time. So and from Jan Horna, from the Czech Republic, it&#8217;s very hot by now there. </p>\n\n\n\n<p>He has two questions as a theme developer, one, is the theme.json supposed to include all the styling, formatting definitions and replaced the CSS style? And I think we&#8217;d take it one at a time. So we talked a little bit about it from my question, but would it replace? You could still do all those styling in the style sheets as you want, right?</p>\n\n\n\n<p><em>Daisy Olsen:</em> And I think there are some things that will remain in other styling, but you could use the variables that you set or the properties that you set in your theme.json in your CSS. So they can work together. But I don&#8217;t think that theme.json, at least right now, will not completely replace an entire site&#8217;s design, especially if you have a very complex design.</p>\n\n\n\n<h2 id="3-meta-charset-utf-8-why-do-we-want-to-rewrite-css-in-json">Why do we want to rewrite CSS in JSON</h2>\n\n\n\n<p><em>Jeff Ong:</em> Yeah. And this was one of my first questions and honestly, skepticism early on of the proposal around this, is CSS is great. Why do we want to rewrite CSS in JSON. And then it slowly, I mean, other people are obviously smarter than me understood this quickly. It&#8217;s not about rewriting all of CSS. There&#8217;s definitely going to be aspects of your site, especially if you have taking, like you&#8217;re saying, more complicated designs that will remain in CSS. </p>\n\n\n\n<p>But this is about creating, I think, more of the foundational elements and understanding how the blocks will interact with your styles and having that single point of contact, I think is most important. So I think for me, at least it&#8217;s more about the foundational elements that are going to be placed and managed this way than replacing your entirety of your styles. Because this great.&nbsp;</p>\n\n\n\n<p>Things like animations and transformation, and this is all really powerful stuff that I don&#8217;t imagine, really, at least in the super near future, having a big part of theme.json. To the question about, will you be able to save an export a theme.json from global styles? I think this is a really important thing to keep in mind is what I just showed you is kind of unnatural. I don&#8217;t imagine a future necessarily where theme developers are writing raw JSON.</p>\n\n\n\n<p>It&#8217;s really, there&#8217;s not a great experience for it. It&#8217;s a configuration file. And so the more, to points that have already been raised, it&#8217;s about we&#8217;re in this phase now because we need to kind of identify and get it to work, and then we can kind of build an ecosystem around what would a really cool UI look like to generate one of these files? Is it native directly to global styles? How do we start to imagine those interfaces so the theme developers or theme designers can really get to the core of this experience too?</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> All right. Well, thank you. Good point. You wanted to say something.</p>\n\n\n\n<p><em>Tammie Lister: </em>Yeah. I was just going to say over time, CSS has gained so much. So I didn&#8217;t know about anyone else, but I had a block.css file that was getting bigger and bigger of supporting blocks and doing things. And something I&#8217;ve noticed that I can do is throw that file away, and I couldn&#8217;t be happier because what I can do now is lean into these defaults. I&#8217;m still going to have some lines of CSS, the output by whatever, a preprocessor, whatever, my happy little whatever. </p>\n\n\n\n<p>Because everyone has got their own way and we should have our own way of doing it. But it&#8217;s a foundation, and it means that we&#8217;re not having to work around the editor or find different ways of doing it. I set up naturally a hack file for the editor out of habit. I haven&#8217;t filled it with anything yet in the latest theme I&#8217;ve been working on.&nbsp;</p>\n\n\n\n<p>I&#8217;m delighted if I never fill that up with anything on the next theme, because it means that the new way we&#8217;re doing things hasn&#8217;t had me to work around that. I can just use the foundation and create a really awesome experience on top of it. And that&#8217;s what we should be doing. We should be working with the editor, not having to work around it, or using not important like it was going out of fashion to go over control of it. It was this awkward middle ground we were working in trying to make things fit that paradigm.&nbsp;</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> And I think that fits right into the next question from Jan Horna again, and he says so as a block theme developer, should I focus from a strategic point of view on theme.json block styles, or block patterns. In other words, how do I differentiate? It&#8217;s kind of a high-level question there.</p>\n\n\n\n<p>D<em>aisy Olsen: </em>I would say all of the above. They&#8217;re all important things. And your block styles are part of theme.json, I would say. But block patterns are really a powerful partner to the theme.json, that you can create building blocks for a site where you&#8217;ve got some really amazing very specific designed elements that could be used for different things on a site. So if you&#8217;re creating a commercial application that&#8217;s going to go out to a wide audience, they can be more generic. </p>\n\n\n\n<p>But if you have a client and you&#8217;re working as a freelancer or in an agency where you have a site that needs to have access to these things that they&#8217;re going to use more than once, patterns are a fantastic way to do that, where most of the work is done for them. They don&#8217;t have to reconfigure everything from the ground up every time they want to create something similar to what they&#8217;ve done before.</p>\n\n\n\n<h2 id="4-what-happens-when-you-update-the-color-palette-will-saved-blocks-have-the-new-colors">What happens when you update the color palette? Will saved blocks have the new colors?</h2>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Thank you. And Spencer McCormick in the chat had a question. So what happens when you update the color palette or similar, for example, if you have a primary and secondary colors, when you update and change the palette colors, will saved blocks have the new colors? That&#8217;s an interesting question. Thank you, Spenser.</p>\n\n\n\n<p><em>Daisy Olsen:</em> I can answer that to some extent. If you think of your palette as named colors, if you give the different hex code to the same name, it should apply to the site. But if you give it a new name, then that&#8217;s a new element, and it won&#8217;t apply to anything that already had an old name attached to it.</p>\n\n\n\n<p><em>Jeff Ong:</em> There is a hefty discussion related to this question on the naming of colors in the way that Gutenberg wants to supply a default palette or a default set of named colors so that you could reliably&#8230; What we&#8217;re seeing I think is that I think patterns have been wanting to rely on specific colors across kind of, so you can guarantee oh, when corn flour shows up it&#8217;s always going to be corn flour. </p>\n\n\n\n<p>It&#8217;s always going to be available. There&#8217;s a lot of complication and nuance around it. But if, I think today, to answer your question, like Daisy is saying, today, if I were to supply a value or a named value here and then change it or take it out of my palette, then that would break the experience or it would no longer be applied to that.</p>\n\n\n\n<p>And that&#8217;s part of the challenge, how do we reliably solve for that? How do we give theme office the tools to figure that out. But now if they set a custom color, if you set a custom color on an element or a block, then that will remain because it&#8217;s a specific X value, but the class names will go away though, if they&#8217;re supplied by the theme.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> So great discussions. And I&#8217;m probably going to share, and if it&#8217;s one issue where that discuss the theme team every week kind of shares all the things that are discussed and that need input from the community or other theme developers on their make blog. </p>\n\n\n\n<p>So that is definitely a place to go to chime in and we&#8217;ll find all the discussions that are happening. And then chime in in the ones that you find important and that you are worried about. So Tim Bowen has the question, how does the theme.json handle responsive sizes for font sizes especially. Responsive sizes.</p>\n\n\n\n<p><em>Daisy Olsen: </em>By default, I&#8217;m not sure.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> You&#8217;ve stomped the panelists. Yes, we did it.</p>\n\n\n\n<p><em>Tammie Lister:</em> I mean, you can use not just pixel values for your fonts, so-</p>\n\n\n\n<p><em>Daisy Olsen:</em> That&#8217;s what I was going to say. </p>\n\n\n\n<p>Tammie Lister: &#8230; that helps. And I think it&#8217;s a work in progress. So things like responsive and breakpoints. But the now answer is you don&#8217;t have to just use pixels. And Jeff just gave a great leak.</p>\n\n\n\n<p>Je<em>ff Ong: </em>I just dropped the issue in that has not seen a lot of activity around it, but the idea of media. So the first part of your question on font sizes, there are ways of calculating this where they&#8217;re not pixel values tied to specific viewports. You could supply a calculated value, for example, in your small&#8230; that is based on a viewport size. </p>\n\n\n\n<p>So it&#8217;s kind of a paradigm shift or design paradigm shift of getting away from you must be 12 pixels under below 600 pixel viewport width, to more of are we okay with kind of a fluid typography kind of system? That being said, there are instances where you need media queries, and that is not currently&#8230; I don&#8217;t know how actively that&#8217;s being worked on right now. But a wonderful thing open to contributors.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> So Patty has a comment and a question after that, Patty O&#8217;Hara, I most often develop custom themes for clients and hand them off for the clients to update the content. And playing around with new tools, I&#8217;m excited to start using them, but don&#8217;t want to give access to global standards to anyone with admin access. Will the granularity of permissions changes so that I can block access to changing fonts and colors from within the admin?</p>\n\n\n\n<p><em>Tammie Lister:</em> I think this amazing thing happens in where also Jeff showed some of the control you can do. So in the demo, there was some control that you can do. But my process is a history of configurability and being able to do that be it in code, or be it in a plugin. But I honestly think we need to be a little bit cautious. This is my personal opinion here, and we need to maybe embrace allowing people to do styling. </p>\n\n\n\n<p>You can set boundaries, you can set branding boundaries, you can set pallets, you can set topography. But we need to move away a little bit from having such pixel fixated control in that sense and think about safely within boundaries, expression of these tools. And that people can create really amazing things, and you can maintain branding that way, and it can empower someone.&nbsp;</p>\n\n\n\n<p>These themes are becoming style guides, and that&#8217;s something that is known in the corporate world and used within that space as well. It&#8217;s a term, but it&#8217;s kind of democratizing design in that sense in giving people all these tools to play with, and I think it&#8217;s a huge change in the way that we&#8217;ve done things, but I think it&#8217;s really, really important and really, really empowering to the people that are using our themes.</p>\n\n\n\n<p><em>Birgit Pauli-Haack: </em>That&#8217;s a good advocacy for set it free. Thank you.</p>\n\n\n\n<p><em>Tammie Lister:</em> But you&#8217;re allowed to have boundaries. I think you can set it free, but be comfortable about some boundaries. I think sometimes when we say set it free, it can be scary because we don&#8217;t say you&#8217;re allowed to have some boundaries, but with pallets and with these style guides, that&#8217;s what you&#8217;re saying. You&#8217;re saying I&#8217;m making these good decisions for you and you can choose from this platform of good decisions. And that&#8217;s kind of awesome. I think,</p>\n\n\n\n<p><em>Birgit Pauli-Haack: </em>Yeah. I like the plea for block patterns that Daisy just a couple of minutes had that block patterns also give you the possibility or the option to actually provide different facets of how a section can be organized or styled within the style design system that you build with the block add on. </p>\n\n\n\n<p>And so I think that there is a lot of creativity that will come from that as well. So Tim Bowen is brave and contemplating, is it safe to use the theme.json now for a project launching in August? Would we just activate the Gutenberg plugin and add JSON file? Or is there more to it? I would love to move away from our functions in Editor.js method probably as soon as possible. So what would we say to Tim?</p>\n\n\n\n<p><em>Daisy Olsen:</em> The theme is not a block theme, as in it doesn&#8217;t use HTML templates, then I probably wouldn&#8217;t put the Gutenberg plugin on a production website, unless you are ready to deal with unexpected things happening. But placing your theme.json file in your classic theme on the 5.8 beta or release candidate that will be coming, I would start testing there and see if the things that you&#8217;re putting in your theme.json file work with 5.8 on a classic theme. That&#8217;d be my suggestion.</p>\n\n\n\n<p><em>Tammie Lister:</em> I think if it&#8217;s launching in August, that means 5.8 should be out. She tries to check her mental calendar. So I think tests. I, personally, am okay. I would consider it if it was going into a site, but I would also want to know how many users were using it, what their levels was, what they were doing, what they were going to create, and how they were going to do it. So it&#8217;s a&#8230; this is not legal advice. I feel that there should be [inaudible 00:50:36] advice that I can be. </p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Don&#8217;t try this at home. </p>\n\n\n\n<p><em>Tammie Lister:</em> But by then, 5.8 should be out.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Yeah. 5.8 comes out July 20th, that&#8217;s at least the schedule for that. So we ran out of questions right now one the Q and A sessions here. Well, you&#8217;re welcome, Tim. Good luck with that, and let us know. Is there more to the setting it up besides just activating the plugin or adding the JSON file. Well, back to kind of using it and editing. </p>\n\n\n\n<p>When there are already themes available in the theme repository that use the full set up for full site editing and use all the template parts and templates with the blocks, and header blocks, and photo blocks, and all that. But I&#8217;m not quite sure of that yet. Be careful about the using the Gutenberg plugin in production. It always has a few hiccups there.</p>\n\n\n\n<p>So it wasn&#8217;t the first time ever that I retreated to the last version when I had one and had to wait till one, two, or three point releases to come out. So I&#8217;m hesitant to say do it in production. Test it as much as possible. So I have a lot of things on my screen, but not the right thing. Here, so it is. Oh, Ryan, we are pretty good time wise. </p>\n\n\n\n<p>So, I don&#8217;t have an additional&#8230; So, when we say how to get started, what was the first thing most difficult part for you for learning, or was there a mind shift until it clicked? Just to kind of get away from a fear of learning something new, and was there something when you go back ages on the theme.json thing.</p>\n\n\n\n<p><strong><em>Tammie Lister: </em></strong>So for me, it was realizing it wasn&#8217;t as hard as I maybe mentally thought it was. It was just the same with learning anything. You always think it&#8217;s going to be super hard, or at least with me, I read like dev doc and I&#8217;m like&#8230; My brain makes that noise. And then I just letting my theme be lighter. Letting it take the weight of that, giving up control, which as someone that&#8217;s maybe a bit of an old themer, giving up control of things, that&#8217;s an interesting process to go through. </p>\n\n\n\n<p>But it&#8217;s really important embracing those foundations. And when you do, there&#8217;s that mind shift of creating in the editor. That was the moment that&#8230; And I&#8217;m still going through the process. I think it&#8217;s a process, and it&#8217;s a process as these tools are evolving. We&#8217;re talking about be gentle, they&#8217;re in production. These tools are still evolving and working.&nbsp;</p>\n\n\n\n<p>If you are using these tools now before it&#8217;s released, then you&#8217;re going to hit bugs and report them. But that&#8217;s the thing. This theme.json also&#8230; the moment I kind of, the Jenga box, the blocks fell in my brain was I stopped seeing it as global stars. And I knew it wasn&#8217;t just global stars, but I felt it wasn&#8217;t just global stars and this felt like it could be the backbone of my theme, and it felt like it wasn&#8217;t everything in my theme, but it felt like it could be the backbone, is the best way I can describe it.&nbsp;</p>\n\n\n\n<p>And I could hang my theme from it. And we&#8217;ve hung our theme from functions.php wrongly, I think. So it was just that change from PHP to doing it all in the editor and creating and seeing that JSON. It just was free, and it&#8217;s more in line with how things are made outside WordPress, which I think is delightful.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Any comments from you that you want to add, Daisy?</p>\n\n\n\n<p><em>Daisy Olsen: </em>So when I first started working with a theme.json file, I found that I had to&#8230; So there&#8217;s a whole section called styles, and I had to realign my thinking about what that meant, because what it&#8217;s saying is there are style settings in your blocks or for your site level depending on how it&#8217;s being applied, and what you&#8217;re doing is configuring the defaults for it. </p>\n\n\n\n<p>So if I think of the theme.json file as a default file, then it helped me frame it so that I&#8217;m not necessarily replacing my CSS depending on&#8230; I mean, I&#8217;m letting theme.json do the heavy lifting, kind of like Tammie said, but then I can take it further if I feel like I need to, or I want to. So I like thinking of it as a configuration file or a defaults file.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> That&#8217;s a good point. Jeff, do you have any stories how I came about?</p>\n\n\n\n<p>Jeff Ong: It&#8217;s been really helpful to pair on it with people, to work on a theme with someone. I think if my team at Automattic. It&#8217;s a very culture of collaboration, and if you have the opportunity to say, &#8220;I&#8217;m having trouble with this. Would you want to work on this?&#8221; With someone like that, because this definitely can be a head bashing kind of why is this not being applied? </p>\n\n\n\n<p>I literally just wrote color green. Why is it not green? It can be so frustrating dealing with that. So to have someone just to look at your code and be like &#8220;Oh, you missed a comma or actually you need an extra key there&#8221; is really, really helpful for something like this.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Oh yeah. So well, I think we&#8217;re coming to the end of our show. This has been very interesting and inspiring. So thank you all so much. And for those who want to dive into at a guided kind of testing session, Anne McCarthy, who, as you might know, runs the Full Site Editing Outreach program, she&#8217;s about to post the eighth call for testing, and it will all be about the theme.json file.</p>\n\n\n\n<p>So as soon as it&#8217;s out, I will share a link in the show notes. And of course, also if you subscribed to our Gutenberg Times newsletter, you will definitely be informed about that. So at this point, I only have two more questions for our panelists. So do you have any announcements that you couldn&#8217;t get out before and you want the people to keep in mind? And if people want to get in touch with you, what would be the best way. Tammie, you want to start?</p>\n\n\n\n<p><em>Tammie Lister:</em> Yeah. So I&#8217;m comatose in all the things. I&#8217;m pretty easy to find in a good way. And I love chatting to people. So please do. I think my thing to say would be remember all of what happening now you can help shape. Just because we&#8217;ve sat here talking about it doesn&#8217;t mean we know anything more than you? It just means we&#8217;ve poked it and we&#8217;ve played around with the code. </p>\n\n\n\n<p>So do that. Start exploring it. And it&#8217;s a lot more accessible than it ever was. It&#8217;s starting to be more accessible. There&#8217;s more documentation than there ever was coming out. And if you care about what happens with themes or you ever cared about what happens to themes, and maybe you could have that reignited, start to join the conversation. And I guess my final point would be, I think my hope is to see this experimentation come back to themes.&nbsp;</p>\n\n\n\n<p>I think we forgot about that a little bit and we need to have some fun again in these. We used to have so much fun in WordPress themes, and I look forward to not just themes to have a purpose, but just themes that are art, themes that are just wacky experiments, and start enjoying theming and make some art. I&#8217;m really excited to see what things people create and use them just for one day even. That&#8217;d be amazing.</p>\n\n\n\n<p><em>Birgit Pauli-Haack</em>: Yeah. So Jeff, anything you want to have people keep in mind, and how to get in contact with you.</p>\n\n\n\n<p><em>Jeff Ong:</em> Yeah. Contact at J-F-F-N-G. And I guess keeping in mind, I&#8217;m just building on the last thing Tammie said, perhaps find a way to have fun with it and get curious about it, and try it. There&#8217;s really to me, a fundamental tendance of learning about something or you just have, how do I get curious about this thing? How do I play with it and have fun? And that&#8217;s going to be the most important thing to keep in at the center.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Thank you, Jeff, and thank you so much for the audio work on the demo. Daisy.</p>\n\n\n\n<p><em>Daisy Olsen:</em> I&#8217;m Daisy Olsen on most things, Olsen with an E, and I would say that as far as what you can do as the next step if you&#8217;re interested in learning more about this, is go to&#8230; I&#8217;m pretty sure that Birgit has a link to this somewhere, the <a href="https://github.com/WordPress/theme-experiments/">theme experiments repository on GitHub</a> in the WordPress space has things that other people have done or are working on. </p>\n\n\n\n<p>So I love to see examples of something in action to help me learn more about it and to see what other people have done. So I would say go check out something.json files in there and see what people have come up with.</p>\n\n\n\n<p><em>Birgit Pauli-Haack:</em> Awesome. Thank you so much. So big thank you to Daisy, Jeff, and Tammie to come today and make your time. A big thank you also for the viewers with all your great questions. I think we got a great array of it. And if you have more questions, you can always send them to me via email to <a href="mailto:pauli@gutenbergtimes.com">pauli@gutenbergtimes.com</a>, and I&#8217;ll get you the answers.</p>\n\n\n\n<p>And the recording of the show will be available in a few minutes on our YouTube channel. And I&#8217;ll share all the links then also in the video description. And within a few days, we will have also a transcript that we will publish on the Gutenbergtimes.com. So be well, good-bye, and good luck. That was fun. Thank you.</p>\n\n\n\n<p>Jeff Ong: Thank you, everyone.</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, 26 Jun 2021 17:23:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:18:"Birgit Pauli-Haack";s: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:46:"WPTavern: Major Revamp Coming to GitHub Issues";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119005";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:137:"https://wptavern.com/major-revamp-coming-to-github-issues?utm_source=rss&utm_medium=rss&utm_campaign=major-revamp-coming-to-github-issues";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2872:"<p>This week GitHub unveiled new features that will be included in a total revamp of <a rel="noreferrer noopener" href="http://github.com/features/issues" target="_blank">GitHub Issues</a>, including project tables that are similar to spreadsheets, custom fields, a keyboard driven command palette, improved task lists, and issue forms. The new project table view is an alternative to project boards, allowing users to filter, sort, and group issues and pull requests. Project managers can customize the table with custom fields and saved views.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>GitHub is also making it easier to manage issues that include subtasks. Users can now add lists and the issue will automatically track the status with a progress indicator.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p><a href="https://github.blog/changelog/2021-06-23-issues-forms-beta-for-public-repositories/">Issues forms are now in beta</a> for public repositories. Many open source projects currently use Markdown issue templates and encourage contributors to provide more details by removing the placeholder text and replacing it with their own. Maintainers can now set up YAML configured forms with required fields and instructions to better guide the process.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<a href="https://cloudup.com/cxWiOL85R4T"><img src="https://cldup.com/Uh6zy46mrI.gif" alt="Issue forms" width="2010" height="1005" /></a>\n</div>\n\n\n\n<p>The revamped Issues feature is being updated to provide a bridge between the planning tools and the problems the tools were created to solve. Mario Rodriguez, Head of Product for GitHub&nbsp;Enterprise, explained why they are evolving GitHub Issues in the beta <a href="https://github.blog/2021-06-23-introducing-new-github-issues/">announcement</a>:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>As teams and projects grow, the way you work evolves. Tools that hard-code a specific methodology are too rigid and complex to flex to whatever the moment demands. Often, we find ourselves creating a spreadsheet or pulling out a notepad, just to have the freedom to think. But then our planning is disconnected from where the work happens and quickly goes stale.</p></blockquote>\n\n\n\n<p>The WordPress project hasn&rsquo;t yet moved away from Trac but most of Gutenberg development happens on GitHub. It&rsquo;s also the most popular repository hosting site for WordPress theme and plugin authors. Contributors to these projects may soon see some of these features in action for personal accounts and organizations that opt into the beta.</p>\n\n\n\n<p>The new <a href="http://github.com/features/issues">GitHub Issues</a> is expected to be out of beta later this year. GitHub plans to bundle it for free, along with the new project planning capabilities, with its Free, Pro, Team, and Enterprise plans.</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, 26 Jun 2021 03:49: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: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:94:"WPTavern: FSE Outreach Round #8: A Developer-Centric Call for Testing Theme JSON Configuration";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118998";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:229:"https://wptavern.com/fse-outreach-round-8-a-developer-centric-call-for-testing-theme-json-configuration?utm_source=rss&utm_medium=rss&utm_campaign=fse-outreach-round-8-a-developer-centric-call-for-testing-theme-json-configuration";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7807:"<p class="has-drop-cap">Round #8 of the Full Site Editing (FSE) Outreach Program began yesterday. Instead of the user-centric call for testing features from the UI, program lead Anne McCarthy <a href="https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/">asks that volunteers dive into code</a>. The new adventure is all about testing <code>theme.json</code> files.</p>\n\n\n\n<p>The twist is likely to limit the pool of usual volunteers. However, it could open it up to an audience that may have been sitting on the sideline for the previous tests: theme developers.</p>\n\n\n\n<p>Before jumping headfirst <a href="https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/">theme JSON files</a>, we should probably all get on the same page.</p>\n\n\n\n<p>I have been calling <code>theme.json</code> the tipping point between the old WordPress and the new WordPress. When version 5.0 of the core platform launched in late 2018, it was a revolutionary step forward, but not on the surface. A new editor is just a new editor. Some will love it; others will hate it.  And, it was more often clunky than not.  For the most part, WordPress was still WordPress.</p>\n\n\n\n<p>The core software was due for an upending. Newer technologies were not only democratizing publishing in their own ways, but they were also bringing that same concept to design.</p>\n\n\n\n<p>The introduction of blocks was merely foundational. The new editor was an imperfect tool, often feeling like the proverbial round peg being shoved into a square hole.</p>\n\n\n\n<p>The only way to live out the early vision of the Gutenberg project was to continue bridging the gap between what the user sees in the admin and what gets output on the front end. That is what the <code>theme.json</code> file is all about. It is a translator that allows users, themes, and WordPress to all speak the same language.</p>\n\n\n\n<p><em>What does this mean exactly?</em></p>\n\n\n\n<p>From a user&rsquo;s viewpoint, they see all sorts of controls for changing their blocks. Color, font size, alignment, and other options are tools that allow them to customize their content.</p>\n\n\n\n<img />Customizing a profile card for my cat using block options.\n\n\n\n<p>There are severe limitations with what is possible in the current system. Theme authors can register a handful of options. Outside of that, the theme and block systems can feel like they are pitted against each other for control.</p>\n\n\n\n<p>That is where the <code>theme.json</code> file comes in. It allows themes and WordPress to get on the same page, creating a standardized system that improves the user experience.</p>\n\n\n\n<p>This file that lives a theme&rsquo;s root folder hands over the power to configure dozens of presets (e.g., color and font options), custom CSS properties, and default styles for blocks and HTML elements.</p>\n\n\n\n<p>It also gives themers the power to enable or disable specific features. For example, developers can turn off the ability for users to set a custom font size but provide access to their perfect scale of choices that fit into the design&rsquo;s vertical rhythm.</p>\n\n\n\n<p>However, it will move beyond the simple configuration of blocks in the content editor. When the global styles system launches alongside the site editor in the future, users will customize many of the presets and overwrite the default block styles. Because everyone is speaking that same language, fewer conflicts arise.</p>\n\n\n\n<p>As designer Tammie Lister pointed out in her piece for Ephermeral Themes, <a href="https://ephemeralthemes.com/2021/06/20/theme-json-inspires/">Theme.json inspires</a>, themes have been stuck. The software, the community, has put too much responsibility on the shoulders of themers over the years. They have had to innovate and build the systems that should have been coming from WordPress. Not only did the core platform need to be turned on its head, but the design system deserved an overhaul.</p>\n\n\n\n<p>&ldquo;I am very aware that saying &lsquo;first major theme process to core&rsquo; in years is quite a statement,&rdquo; wrote Lister. &ldquo;Theme.json to me is that though. I don&rsquo;t say this ignoring iterations and improvements, WordPress is a project flowing with the energy of those. However, themes were on life support stuck in a land when the rest of front end development was moving on. It wasn&rsquo;t for some trying to change that, mostly when they did the time wasn&rsquo;t right and as it didn&rsquo;t come from core it was always a harder change.&rdquo;</p>\n\n\n\n<p>It is time for a new front-end design era. But, first, we must test.</p>\n\n\n\n<h2>Testing Theme JSON</h2>\n\n\n\n<img />Real-world theme.json file.\n\n\n\n<p class="has-drop-cap">The more I journeyed into this call for testing, the more I realized it did not feel right for me. Over the past couple of months, I have already been in the thick of working from the <code>theme.json</code> file. I know most of the little quirks and see the gaps. The tricks for working with it feel second nature to me.</p>\n\n\n\n<p>I have performed all of the beginner and intermediate steps dozens upon dozens of times. I have already filed tickets for any issues I have run into. Or, someone else has already beat me to the punch.</p>\n\n\n\n<p>Those stages of this testing round need fresh eyes. The best feedback will be from theme authors who will be viewing the problems through a different pair of lenses.  If you are in this group, there is no time like the present to test and provide feedback.</p>\n\n\n\n<p>The advanced stage calls for recreating a classic theme using <code>theme.json</code>. It is best to stick with something simple. Otherwise, you could be looking at a weeks-long experiment. McCarthy recommends Twenty Twenty or Storefront. I have already been performing this song and dance too. My test project was an old theme that I gutted and turned into a block theme.</p>\n\n\n\n<p>There is one overarching issue that I keep coming back to. It is that theme authors must work from a JSON file at all.</p>\n\n\n\n<p>I understand the &ldquo;why&rdquo; behind using JSON. It is a universal format that we can pass around from JavaScript to PHP. Third-party APIs can understand it.</p>\n\n\n\n<p>However, I am currently sitting on top of 900+ lines of code in my <code>theme.json</code>. I have heard from a couple of other theme authors who have been doing deep work with similar numbers. I expect it to only grow.</p>\n\n\n\n<p>&ldquo;Number of lines&rdquo; is not necessarily some metric where a specific total is a dividing point between &ldquo;good&rdquo; or &ldquo;bad.&rdquo; The problem is that comments are not allowed in JSON files. One of the cornerstones of sound development is documenting code. Skipping out on documentation of a few dozen lines is not so bad. However, when you speed past 900, things can get out of hand.</p>\n\n\n\n<p>Plus, at a certain point, you start wanting to split pieces into their own groups. This much code is begging for better organization.</p>\n\n\n\n<p>The thing that is currently missing is a PHP layer for theme authors to use. Remember, JSON is a universal format. It is easy to convert PHP to JSON and vice-versa. Building in this layer for theme authors would accomplish two things:</p>\n\n\n\n<ol><li>They can organize what will likely be 1,000s of lines of code.</li><li>It will be easier to transition to the new system.</li></ol>\n\n\n\n<p>The latter point is likely the most salient. PHP has been the language of theming since the theming has been around. Developers know it and are comfortable using it, and WordPress should meet them in the middle. If we are closing gaps, this is the one that needs filling before more configuration possibilities are added and <code>theme.json</code> files balloon into unwieldy, 5,000-line behemoths.</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, 26 Jun 2021 03:30:07 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:40:"WordPress.org blog: WordPress 5.8 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:35:"https://wordpress.org/news/?p=10855";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2021/06/wordpress-5-8-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:3891:"<p>WordPress 5.8 Beta 4 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it is not recommended to run this version on a production site. Consider setting up a test site to play with it.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 4 in three ways:</p>\n\n\n\n<ul><li>Install/activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the&nbsp;<code>Bleeding edge</code>&nbsp;channel and the&nbsp;<code>Beta/RC Only</code> stream).</li><li>Direct download the beta version here (<a href="https://wordpress.org/wordpress-5.8-beta4.zip">zip</a>).</li><li>Using WP-CLI to test: <code>wp core update --version=5.8-beta4</code></li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021. That’s less than <strong>four weeks away</strong>, so we need your help to make sure the final release is as good as it can be.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-3/">Beta 3</a>, <a href="https://core.trac.wordpress.org/query?status=closed&changetime=06%2F24%2F2021..06%2F26%2F2021&milestone=5.8&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">18</a> bugs have been fixed. Most tickets focused on polishing existing default themes, fixing bugs in the new block Widget screen, and squashing Editor bugs collected during beta.</p>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<p>Watch the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a> in the coming weeks, which will break down these and other changes in greater detail.</p>\n\n\n\n<p>So far, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&changetime=..06%2F25%2F2021&milestone=5.8&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">254 tickets in WordPress 5.8</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&status=reopened&changetime=..06%2F25%2F2021&type=enhancement&type=feature+request&milestone=5.8&group=component&col=id&col=summary&col=type&col=status&col=milestone&col=changetime&col=owner&col=priority&col=keywords&order=changetime">91 new features and enhancements</a>, and more bug fixes are on the way.</p>\n\n\n\n<p><strong>Do some testing!</strong></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">Testing for bugs</a> is a vital part of polishing the release during the beta stage and a great way to contribute. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2728.png" alt="✨" class="wp-smiley" /></p>\n\n\n\n<p>If you think you’ve found a bug, please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta</a> area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible <a href="https://make.wordpress.org/core/reports/">bug report</a>, file one on <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href="https://profiles.wordpress.org/desrosj/" class="mention"><span class="mentions-prefix">@</span>desrosj</a> <a href="https://profiles.wordpress.org/clorith/" class="mention"><span class="mentions-prefix">@</span>clorith</a> for reviews and <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a> for final edits!</em></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>Releasing software<br />Is complex when open source<br />Yet WordPressers do</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, 25 Jun 2021 17:14: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:12:"Jeffrey Paul";s: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:115:"WPTavern: Gutenberg 10.9 Renames the Query Block, Adds Collapsible List View Items, and Rolls Out Rich URL Previews";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119015";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:271:"https://wptavern.com/gutenberg-10-9-renames-the-query-block-adds-collapsible-list-view-items-and-rolls-out-rich-url-previews?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-10-9-renames-the-query-block-adds-collapsible-list-view-items-and-rolls-out-rich-url-previews";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6463:"<p class="has-drop-cap">Yesterday, <a href="https://make.wordpress.org/core/2021/06/24/whats-new-in-gutenberg-10-9-23-june/">Gutenberg 10.9</a> landed in the WordPress plugin directory. The update overhauls the Query and Query Loop blocks, allows users to expand or collapse items in the editor list view, and introduces rich URL preview cards for links. The new version also packs in an updated template-mode <a href="https://github.com/WordPress/gutenberg/pull/32427">creation modal</a> and <a href="https://github.com/WordPress/gutenberg/pull/32166">moves the blocks manager</a>.</p>\n\n\n\n<p>This update ships several enhancements, particularly to the user experience. One of my favorite low-key upgrades is <a href="https://github.com/WordPress/gutenberg/pull/32371">a new set</a> of add-card, bug, key, post author, and security icons by Filipe Varela, a product designer at Automattic.</p>\n\n\n\n<p>Another small-but-packs-a-punch UI change is the <a href="https://github.com/WordPress/gutenberg/pull/32609">inclusion of the post type</a> in the editor breadcrumb trail. The type&rsquo;s singular name label now replaces the root &ldquo;Document&rdquo; item.</p>\n\n\n\n<p>For the past several cycles, the new template editor slated to launch with WordPress 5.8 has been enabled by default. The goal was always to allow everyone the chance to experience it, regardless of whether they were on a classic or block theme. The development team has now scaled this back to only be <a href="https://github.com/WordPress/gutenberg/pull/32858">auto-enabled for block themes</a>. Classic themes must opt-in to support it. Theme authors should read the recent <a href="https://make.wordpress.org/core/2021/06/16/introducing-the-template-editor-in-wordpress-5-8/">template editor overview</a> by Riad Benguella for the complete details.</p>\n\n\n\n<h2>Query and Query Loop Blocks Renamed</h2>\n\n\n\n<img />Query Loop block in the editor.\n\n\n\n<p class="has-drop-cap"><em>Query? Query Loop? What the heck is all this?</em> If you are unfamiliar with those terms, you are not alone. Even on the developer end, the early implementation of the Query and its inner Query Loop block could be a little confusing. For the average user, it probably makes even less sense.</p>\n\n\n\n<p>Gutenberg 10.9 takes one step toward <a href="https://github.com/WordPress/gutenberg/pull/32514">clearing up this confusion</a> for end-users. The former Query Loop block is now named Post Template. This is a far more accurate description of what it does. It is the &ldquo;template&rdquo; that outputs individual posts. It contains all the things you see, such as the post content or excerpt, the featured image, tags, categories, and more. This template is, of course, customizable via the block editor.</p>\n\n\n\n<p>While this is a step toward a less complex user experience, it is not quite where it needs to be yet. The Query block has been renamed to Query Loop. Therein lies the remaining issue. The terminology might still be confusing.</p>\n\n\n\n<p>The goal is to expose a variation of this block named Posts List to users. It already exists, but the query-related terminology still appears when using it. There is an <a href="https://github.com/WordPress/gutenberg/issues/32268">open ticket to address this</a>.</p>\n\n\n\n<p>The primary win with this update is the overhauled text in the Query Loop block sidebar. &ldquo;The query block is a powerful and complex block,&rdquo; said lead Gutenberg developer Matias Ventura in a <a href="https://github.com/WordPress/gutenberg/pull/32694">GitHub ticket</a>. &ldquo;It can be intimidated to users without proper guidance. We can use this block as an opportunity to explain some of the underlying concepts of the WordPress software in a more didactic manner.&rdquo;</p>\n\n\n\n<p>The more advanced options, such as whether to inherit from the URL and which post types to include, now have longer descriptions. Each should guide the user through features that have long existed in the developer world.</p>\n\n\n\n<p>If you are a theme author and have already been building with these two blocks, do not worry about everything breaking when updating. The Query block has simply been renamed to &ldquo;Query Loop&rdquo; in user-facing text. Under the hood, it is still the same. The former Query Loop block has literally been renamed to Post Template (<code>core/post-template</code> block name). It is backward compatible. However, you should update any past calls to the <code>wp:query-loop</code> block to <code>wp:post-template</code>.</p>\n\n\n\n<h2>Expand and Collapse Nested List View Blocks</h2>\n\n\n\n<img />List view with collapsed nested blocks.\n\n\n\n<p class="has-drop-cap">The development team introduced an <a href="https://github.com/WordPress/gutenberg/pull/32117">expand/collapse feature</a> for the editor&rsquo;s list view. Once opening the panel, users should now see arrow icons next to each item with nested blocks. Closing one or more of them makes it easier to see all or many top-level blocks at once.</p>\n\n\n\n<p>The downside is that the open/close state is lost once the list view is closed. If I had one request, it would be to store this data while editing the post. That would improve the user experience with longer documents, particularly when switching between navigating and editing.</p>\n\n\n\n<p>This update, along with the persistent behavior of the list view in Gutenberg 10.7, has made for a much more well-rounded document navigation experience.</p>\n\n\n\n<h2>Rich URL Previews</h2>\n\n\n\n<img />\n\n\n\n<p class="has-drop-cap">The editor will now <a href="https://github.com/WordPress/gutenberg/pull/31464">show a website preview</a> in the link editor popup. This feature only works for links in a Rich Text context, such as in the Paragraph, Heading, and List blocks. The preview also only appears after the link has been set and clicked on, not when initially typing it.</p>\n\n\n\n<p>If available, the popup preview displays the site icon, title, image, and description.</p>\n\n\n\n<p>&ldquo;In the near future however, we expect to extend this to provide previews of internal URLs and to roll out support to more areas of the software,&rdquo; wrote George Mamadashvili in the Gutenberg 10.9 announcement post.</p>\n\n\n\n<p>Admittedly, I was not keen on the idea of adding this feature. It felt like unnecessary bloat when more pressing issues were lying on the table. However, in the past day, I have enjoyed the quick previews when double-checking links in posts.</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, 25 Jun 2021 02:34:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:41:"WPTavern: Jetpack Launches New Mobile App";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118883";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:127:"https://wptavern.com/jetpack-launches-new-mobile-app?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-launches-new-mobile-app";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3798:"<div><img /></div>\n\n\n\n<p>Automattic has launched a new <a href="https://jetpack.com/2021/06/21/jetpack-mobile-app/">mobile app for Jetpack</a>, available on iOS and Android. The app features an array of Jetpack-specific features, as well as those applicable to users on paid plans, along with core WordPress features. </p>\n\n\n\n<p>Inside it looks nearly identical to the official WordPress mobile apps, but it is noticeably missing WordPress.com specific features like the Reader. The bottom menu links to &ldquo;My Site&rdquo; and &ldquo;Notifications.&rdquo; </p>\n\n\n\n<p>Those who are on paid Jetpack plans will have access to features like backups, restores, and security scanning for use inside the app when on the go. It also includes the same Activity Log and Stats features found in the main WordPress app. In its current state, it doesn&rsquo;t look like the app offers anything more than what you are used to on the standard mobile apps unless you are a <a href="https://jetpack.com/features/comparison/">paid Jetpack customer</a>. So far, the app doesn&rsquo;t include any upgrade paths for free users or to jump from plan to plan. If Automattic decides to add in-app purchases, it will have to <a href="https://wptavern.com/automattic-tangles-with-apple-over-lack-of-in-app-purchases-in-the-wordpress-for-ios-app">share the revenue with the app stores</a>. Having a separate app from the official mobile apps gives the company the option to build in more direct paths for monetization in the future.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>\n\n\n\n<div><img /></div>\n\n\n\n<p>You may want to stick with the official WordPress apps if you manage both WordPress.com and Jetpack-enabled sites, to keep everything conveniently in the same place. If you decide to use both apps, you will want to remove your Jetpack sites from the main WordPress app so that you aren&rsquo;t getting double notifications from having the site accessible through both apps.</p>\n\n\n\n<p>Automattic&rsquo;s integrated products remain controversial features of the official WordPress apps. It is a good move to separate self-hosted Jetpack sites from the clutter of having WordPress.com-specific features in the app, but it does little for improving the official app&rsquo;s experience for self-hosted users who are not using Jetpack. Clicking on Stats in the app still prompts users to install Jetpack when managing self-hosted sites. The Reader menu item is ever-present at the bottom of the page. These products take up screen real estate regardless of whether they are being used. </p>\n\n\n\n<p>A toggle to turn off these features in the app&rsquo;s settings might be a good stop-gap measure towards disentanglement, but ultimately the official mobile apps should not promote any commercial interests. </p>\n\n\n\n<p>If Automattic moved WordPress.com features into the Jetpack app, then anyone using the company&rsquo;s products could be directed to this app for managing their sites. The official WordPress app could then be kept free of any products that the user doesn&rsquo;t choose to install. If the vanilla state of the app is not enough, users can be prompted to add themes and plugins to enhance the WordPress experience.</p>\n\n\n\n<p>The Jetpack app is aimed at people who have sites using Jetpack but don&rsquo;t need the WordPress.com features that are built into the official WordPress apps. It brings more value to those who are on paid plans and want access to those features on the go. More than 500 people have already downloaded the Android app. It will be interesting to see if Jetpack users will gravitate towards the new app or remain on the standard WordPress app for more centralized management of Jetpack and non-Jetpack enabled websites.  </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, 24 Jun 2021 17:59:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:63:"WPTavern: Clove: A Showcase of Block Patterns by Anariel Design";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=119011";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:169:"https://wptavern.com/clove-a-showcase-of-block-patterns-by-anariel-design?utm_source=rss&utm_medium=rss&utm_campaign=clove-a-showcase-of-block-patterns-by-anariel-design";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5403:"<img />Clove theme homepage.\n\n\n\n<p class="has-drop-cap">Earlier today, Ana Segota <a href="https://twitter.com/Ana_Segota/status/1407694456418152458">tweeted</a> and <a href="https://www.anarieldesign.com/free-full-site-editing-theme-clove/">announced</a> via the Anariel Design blog that her company had submitted its second block-based theme to WordPress.org. Clove is a more well-rounded follow-up to her first such theme, <a href="https://wptavern.com/anariel-design-launches-naledi-a-block-based-wordpress-theme">Naledi</a>. It is currently under review for inclusion in the official directory, but anyone can give it a test run by snagging the ZIP file from <a href="https://themes.trac.wordpress.org/ticket/101349">its ticket</a>. Or, just peruse the <a href="https://anarieldesign.com/themedemos/clove/">live demo</a>.</p>\n\n\n\n<p>This should officially be the 10th <a href="https://wordpress.org/themes/tags/full-site-editing/">block-based theme</a> to go live in the WordPress.org theme directory (note that a couple by Automattic are not tagged). That is assuming all goes well during the review process.</p>\n\n\n\n<p>It has been a long road thus far, but 10 themes with the Full Site Editing tag is a notable milestone. The <a href="https://wptavern.com/exploring-full-site-editing-with-the-q-wordpress-theme">Q theme</a> by Ari Stathopoulos was the first to land in the directory back in October 2020. Now, eight months later, there is still room for other theme authors to become pioneers in the space. With almost no competition, who will design that first block theme that squeezes its way into the most popular list?</p>\n\n\n\n<p>If &ldquo;practice makes perfect,&rdquo; Segota is now ahead of the curve by pushing her second theme to the directory. This makes her theme company only one of two with multiple block themes.</p>\n\n\n\n<p>Clove is experimental, as all block themes are. It relies on the ever-shifting parts of the Gutenberg plugin, but it all comes together into a floral, nature-themed design. There are hints of inspiration from Twenty Twenty-One, but it feels more structured, less chaotic.</p>\n\n\n\n<p>The design is less of a theme and more of a showcase of block patterns and styles. Even on the template level, it reuses those same elements across each of its seven templates, providing multiple entryways for users to tinker with its features.</p>\n\n\n\n<p>Clove even includes pricing columns.  I seem to recall writing about how theme authors could <a href="https://wptavern.com/you-might-not-need-that-block">implement them via patterns</a> just over a month ago. Maybe the Anariel Design team came to the same conclusion. Maybe they took my message and ran with it. I like to think the latter is true. Either way, the result is a beautiful, theme-specific pattern &mdash; the sort of artistry that is tough to achieve from a plugin.</p>\n\n\n\n<img />Customizing the Pricing Columns pattern in the WordPress editor.\n\n\n\n<p>I am less of the fan of the overlapping and uneven columns in some of the designs designs, preferring some of the more-structured patterns, such as Three Quotes Images:</p>\n\n\n\n<img />Three-column pattern that showcases images along with quotes.\n\n\n\n<p>Despite my general dislike of the uneven column style, my favorite piece of the entire theme is the Illustrations page template, which leans into that design method.</p>\n\n\n\n<p>The page intro section is an announcement to the world, &ldquo;Hey, check out my work.&rdquo;</p>\n\n\n\n<img />Illustrations template intro section.\n\n\n\n<p>I also like the Illustrations page template&rsquo;s widgets-like area in the footer. It manages to stuff several blocks in without feeling too crowded. It even showcases a box for artists to highlight their next exhibition.</p>\n\n\n\n<img />Illustrations page template footer &ldquo;widget&rdquo; area.\n\n\n\n<p>The Clove theme also registers 10 block styles for users to choose from. Most of them add different types of borders or frames to various elements. Plus, there is the fun-but-kind-of-an-oddball blob &ldquo;Shape&rdquo; for images.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img />Latest Posts &ndash; Dividers</li><li class="blocks-gallery-item"><img />Image &ndash; Framed</li><li class="blocks-gallery-item"><img />Image &ndash; Shape</li></ul>\n\n\n\n<p>Segota was one of several people to submit custom designs to the upcoming block pattern directory. There is some noticeable crossover between her current theme work and submissions, such as the <a href="https://github.com/WordPress/pattern-directory/issues/149">Playful Gallery</a> pattern that did not quite make the cut. Others, like her <a href="https://wordpress.org/patterns/pattern/recipe/">Recipe design</a>, did. There is still an <a href="https://wptavern.com/open-invitation-to-contribute-to-the-wordpress-block-pattern-directory">open invitation for people to contribute</a>.</p>\n\n\n\n<p>I am always like a kid in a toy store when a new block theme comes along, reaching out to grab the latest gadget. I want to see more experiments like Clove. Keep them coming, theme authors.</p>\n\n\n\n<p><strong>Side note:</strong> For people interested in the background-clipped text design used in Clove&rsquo;s site logo, I <a href="https://github.com/WordPress/gutenberg/issues/32787">opened a ticket</a> to take us one step closer to doing it in the editor. Currently, users must create an off-site image and upload it.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 24 Jun 2021 01:23:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:76:"WordPress Foundation: Answering FAQs on WordPress Trademarks and their usage";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpressfoundation.org/?p=189036";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wordpressfoundation.org/2021/answering-faqs-on-wordpress-trademarks-and-their-usage/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6388:"<p class="has-drop-cap">The WordPress Foundation owns and <a href="https://wordpressfoundation.org/trademark-policy/">manages trademarks</a> for the WordPress and WordCamp names and <a href="http://wordpress.org/about/logos/">logos</a>. Over the years, many people have approached us with questions on WordPress trademarks and how to use them. This blog post aims to address some of the most common questions and clarify the usage of WordPress trademarks.</p>\n\n\n\n<h3>Can I use “WordPress” in my name?</h3>\n\n\n\n<p>Strictly speaking, you cannot use “WordPress” in your website name or your product name. As mentioned in the <a href="https://wordpressfoundation.org/trademark-policy/">WordPress Foundation trademarks page</a>:  </p>\n\n\n\n<blockquote class="wp-block-quote"><p><em>Permission from the WordPress Foundation is required to use the WordPress or WordCamp name or logo as part of any project, product, service, domain name, or company name.</em></p></blockquote>\n\n\n\n<p>The purpose of trademark law is to keep others from using or misusing a trademarked name or logo. But it cannot stop them from picking it up. Sometimes, people use “WordPress” in their name, title, URL, or username when “WordPress” really does not belong there. However, such uses of the trademark violate the WordPress trademark nevertheless, and cannot be allowed.</p>\n\n\n\n<h3>What is the actual trademark Policy?</h3>\n\n\n\n<p>You can find the entire written Trademark policy on the <a href="https://wordpressfoundation.org/trademark-policy/">Trademarks policy page</a> of this website. In short, the purpose of this policy is to make it easy for anyone to use the WordPress or WordCamp name or logo for community efforts that spread and improve WordPress. It also aims to make it difficult for anyone to use the WordPress or WordCamp name or logo to trick or confuse people looking for official WordPress or WordCamp resources. When you are in doubt, ask yourself this question: <em>“Is this an “official” WordPress event or resource?” </em>If the answer is “no,” then you should leave the trademarked name “WordPress” or “WordCamp” out of it.</p>\n\n\n\n<h3>Does this mean I cannot build something for WordPress?</h3>\n\n\n\n<p><strong>NO. </strong>The trademark policy <strong>does not</strong> restrict people from building anything for WordPress. WordPress, both the software and the community surrounding it, is open source. It takes all kinds of contributors to create, build, support, maintain, educate, and energize WordPress. But it does mean if you are creating something within the WordPress space that is not officially part of the WordPress project, you should not use the name “WordPress” to name it. However, you can use an alternative name like “WP” instead of “WordPress” for your products.&nbsp;</p>\n\n\n\n<h3>I was unaware of the Trademark policy and already created something using “WordPress” in the name or the URL. What do I do now?</h3>\n\n\n\n<p>If you happen to be in that position and you want to figure out how to fix things, please feel free to reach out to <a href="mailto:trademarks@wordpressfoundation.org">trademarks@wordpressfoundation.org</a> (or send us a message through the <a href="https://wordpressfoundation.org/trademark-policy/">contact form</a> on this site), and someone will help you bring your site, event, or product into compliance with the WP Trademark.&nbsp;</p>\n\n\n\n<h3>Does the trademark policy apply to WordPress swag?&nbsp;</h3>\n\n\n\n<p>Yes. Using the WordPress logo in products or any sort of swag is not permitted. Without express permission from WordPress Foundation, you cannot sell WordPress goods or co-brand your goods to make them seem affiliated with WordPress.</p>\n\n\n\n<p>However, WordPress swag (shirts, stickers, bags, hand sanitizer, stuffed animals, sweatshirts, mugs, cups, pencils… to name a few) &#8211; given out at a WordCamp is okay. Branded WordPress swag from sponsors at a WordCamp is also allowed. This is because the swag is being given out for free (not for profit) at an official WordPress event, and has been approved. You can also find approved WordPress swag in the <a href="https://mercantile.wordpress.org/">official WordPress swag store</a>.</p>\n\n\n\n<h3>Reading all this, I realize someone I know is not in compliance with the Trademark. What should I do?</h3>\n\n\n\n<p>The first thing is to remember that this person could be unaware they are not complying with the trademark. We want to assume good intent whenever possible. You can talk to them about it if you feel comfortable or even just share <a href="https://wordpressfoundation.org/trademark-policy/">the trademark policy</a> with them. Alternatively, you can submit information to the <a href="https://wordpressfoundation.org/contact/">Trademarks contact form</a> on the site or send an email to trademarks@wordpressfoundation.org and let someone there do the work of assuming good intent and reaching out to them.</p>\n\n\n\n<h3>I have already reported this site/thing/person, and nothing has been done!</h3>\n\n\n\n<p>The process of resolving trademark issues takes a while, so we have assigned more bandwidth to speed up the process.  If you have reported something in the past, know that it is being worked on in the coming months. If you are worried that it got lost, you are welcome to send it in again. </p>\n\n\n\n<h3>Is there anything I can do to help?</h3>\n\n\n\n<p>The biggest help anyone in WordPress can give is to respect the Trademark themselves. I know that it seems like passive work for many, and you may be looking to do something actively. Being an active and respectful part of a community is a big help, though.</p>\n\n\n\n<p><em>This post is based on </em><a href="https://make.wordpress.org/community/2021/03/30/tuesday-trainings-can-i-use-wordpress-in-my-product-name/"><em>Part 1</em></a><em> and </em><a href="https://make.wordpress.org/community/2021/04/06/tuesday-trainings-can-i-use-wordpress-in-my-product-name-part-2-of-2/"><em>Part 2</em></a><em> of the “Can I use “WordPress” in my product name?” </em><a href="https://make.wordpress.org/community/tag/tuesdaytrainings/"><em>Tuesday Training</em></a><em> from </em><a href="https://profiles.wordpress.org/camikaos"><em>@camikaos</em></a><em> in the </em><a href="https://make.wordpress.org/community/"><em>Make WordPress Communities</em></a><em> blog.</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:"Wed, 23 Jun 2021 09:08:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Hari Shanker";s: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:40:"WordPress.org blog: WordPress 5.8 Beta 3";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10843";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2021/06/wordpress-5-8-beta-3/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5564:"<p>WordPress 5.8 Beta 3 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it is not recommended to run this version on a production site. Consider setting up a test site to play with it.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 3 in three ways:</p>\n\n\n\n<ul><li>Install/activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the&nbsp;<code>Bleeding edge</code>&nbsp;channel and the&nbsp;<code>Beta/RC Only</code> stream).</li><li>Direct download the beta version here (<a href="https://wordpress.org/wordpress-5.8-beta3.zip">zip</a>).</li><li>Using WP-CLI to test: <code>wp core update --version=5.8-beta3</code></li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021. That’s just <strong>four weeks away</strong>, so we need your help to make the final release is as good as it can be.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-2/">Beta 2</a>, <a href="https://core.trac.wordpress.org/query?status=closed&changetime=06%2F16%2F2021..06%2F23%2F2021&milestone=5.8&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">38</a> bugs have been fixed. Here is a summary of some of the included changes:</p>\n\n\n\n<ul><li>Block Editor: Move caching to endpoint for unique responses. (<a href="https://core.trac.wordpress.org/ticket/53435">#53435</a>)</li><li>Bundled Themes: Improve display of blocks in widget areas. (<a href="https://core.trac.wordpress.org/ticket/53422">#53422</a>)</li><li>Coding Standards: Bring some consistency to HTML formatting in <code>wp-admin/comment.php</code>. (<a href="https://core.trac.wordpress.org/ticket/52627">#52627</a>)</li><li>Editor: Include Cover block in the list of block types registered using metadata files. (<a href="https://core.trac.wordpress.org/ticket/53440">#53440</a>)</li><li>Editor: Include Cover block in the list of block types registered using metadata files. (<a href="https://core.trac.wordpress.org/ticket/53440">#53440</a>)</li><li>Media: Add new functions to return the previous/next attachment links. (<a href="https://core.trac.wordpress.org/ticket/45708">#45708</a>)</li><li>Media: Improve upload page media item layout on smaller screens. (<a href="https://core.trac.wordpress.org/ticket/51754">#51754</a>)</li><li>Media: Update total attachment count when media added or removed. (<a href="https://core.trac.wordpress.org/ticket/53171">#53171</a>)</li><li>REST API: Decode single and double quote entities in widget names and descriptions. (<a href="https://core.trac.wordpress.org/ticket/53407">#53407</a>)</li><li>Twenty Nineteen: Update margins on full- and wide-aligned blocks in the editor. (<a href="https://core.trac.wordpress.org/ticket/53428">#53428</a>)</li><li>Widgets: Add editor styles to the widgets block editor. (<a href="https://core.trac.wordpress.org/ticket/53344">#53344</a>)</li></ul>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<p>Watch the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a> in the coming weeks, which will break down these and other changes in greater detail.</p>\n\n\n\n<p>So far, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&changetime=..06%2F23%2F2021&milestone=5.8&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">254 tickets in WordPress 5.8</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&status=reopened&changetime=..06%2F23%2F2021&type=enhancement&type=feature+request&milestone=5.8&group=component&col=id&col=summary&col=type&col=status&col=milestone&col=changetime&col=owner&col=priority&col=keywords&order=changetime">91 new features and enhancements</a>, and more bug fixes are on the way.</p>\n\n\n\n<p><strong>Do some testing!</strong></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">Testing for bugs</a> is a vital part of polishing the release during the beta stage and a great way to contribute. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2728.png" alt="✨" class="wp-smiley" /></p>\n\n\n\n<p>If you think you’ve found a bug, please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta</a> area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible <a href="https://make.wordpress.org/core/reports/">bug report</a>, file one on <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href="https://profiles.wordpress.org/jeffpaul/" class="mention"><span class="mentions-prefix">@</span>jeffpaul</a> <a href="https://profiles.wordpress.org/desrosj/" class="mention"><span class="mentions-prefix">@</span>desrosj</a> <a href="https://profiles.wordpress.org/hellofromtonya/" class="mention"><span class="mentions-prefix">@</span>hellofromtonya</a> <a href="https://profiles.wordpress.org/pbiron/" class="mention"><span class="mentions-prefix">@</span>pbiron</a> for reviews and final edits!</em></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>Esperanza first.<br />Want to know the next jazzer?<br />Then please test beta.</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:"Wed, 23 Jun 2021 02:36:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Josepha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:62:"WPTavern: WordPress Theme Lock-In, Silos, and the Block System";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118923";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:165:"https://wptavern.com/wordpress-theme-lock-in-silos-and-the-block-system?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-theme-lock-in-silos-and-the-block-system";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6343:"<p class="has-drop-cap">For many years, I was a hardcore advocate of separating any non-design functionality from themes into their own plugins. I wrote extensively on the issue. Whether it was shortcodes, custom post types, user metadata, and any number of things related to a user&rsquo;s content/data, I drew a deep line in the sand. <em>This belongs in a plugin.</em></p>\n\n\n\n<p>If you have never heard of the &ldquo;theme lock-in effect,&rdquo; that&rsquo;s OK. For many, it is a non-issue. Places like the WordPress.org theme directory have, for the most part, drew a similar line in the sand.</p>\n\n\n\n<p>The goal has always been to avoid trapping a user into perpetual use of a particular theme. It is not an ideal user experience when some crucial data is no longer available when switching designs. And, all users eventually want to change that up from time to time. Getting stuck with <code>[shortcode-soup]</code> tags littered throughout a site is never fun. Neither is losing admin access to dozens, hundreds, or even thousands of pages from a custom post type that suddenly disappears.</p>\n\n\n\n<p>The WordPress theme development community has avoided this problem &mdash; some more so than others &mdash; by bundling crucial content-related features separately in plugins.</p>\n\n\n\n<p>Those theme authors who bypassed theme lock-in via plugins have mostly done so in their own silos. For example, instead of integrating with an existing portfolio plugin, they would just create their own. <em>The only themes that support that plugin?</em> Theirs. Ultimately, users were still trapped.</p>\n\n\n\n<p>I cannot lay the entire weight of this issue on the shoulders of theme authors. Portfolio plugins are a dime a dozen. Supporting WooCommerce for an eCommerce solution or bbPress for forums are easy choices. But, when there is no clear industry front-runner, an in-house solution is just as good as most others.</p>\n\n\n\n<p>However, the block system is already complicating matters. When a theme supports features like font sizes, colors, and gradients, it essentially locks users in. Switch to another with a different configuration, and every font size, color, and gradient the user chose to use is gone.</p>\n\n\n\n<p>Imagine inserting a Paragraph block and choosing that sky blue from your theme as the block&rsquo;s background. Now, imagine doing this a few hundred times only to have it disappear a couple of years down the road when you want to switch designs.</p>\n\n\n\n<p>I won&rsquo;t dive into the technical details of how this works under the hood. It is just the way the system was designed. Some problems <a href="https://github.com/WordPress/gutenberg/issues/7553">could have been mitigated early on</a>, but that ship sailed two and a half years ago with the launch of WordPress 5.0. There are also ways this might be solved in the future with technical workarounds.</p>\n\n\n\n<p>Last week, a reader named Nick <a href="https://wptavern.com/getting-to-know-the-upcoming-wordpress-5-8-template-editor#comment-382930">brought up this issue</a> in regards to block patterns. The theme in question used custom CSS classes to achieve a specific design.</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Because Gutenberg lacks all the features mentioned above, the theme uses some custom CSS classes, and these classes are coded in the theme&rsquo;s style sheet. The problem with this is that now that you have used these patterns, YOU ARE LOCKED IN to this theme. Because the moment you change themes, the new theme will not have these custom classes defined, the patterns will be broken. This is THE SAME reason why shortcodes were outlawed many years ago from inside the themes &mdash; and yet when it comes to patterns, this is somehow allowed?</p></blockquote>\n\n\n\n<p><strong>Note:</strong> Shortcodes were disallowed in the WordPress theme directory because the actual post content was broken on theme switch. It was unrelated to a broken design.</p>\n\n\n\n<p>I already hear what some of you are thinking. <em>This is not the same as &ldquo;content&rdquo; lock-in.</em> No, it is not. Not exactly. However, because the block system intertwines content and design, it sort of is. I doubt the average user appreciates the distinction when they end up in scenarios with white text on a white background, as shown in the following screenshots:</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img />Blue background with one theme.</li><li class="blocks-gallery-item"><img />Blue background gone with second theme.</li></ul>\n\n\n\n<p>That is a <em>very</em> real scenario. I see it almost daily as I test out different themes.</p>\n\n\n\n<p>And, this is just the beginning. As WordPress&rsquo;s design system grows and themers can configure more pieces, users will become more locked into their existing theme. Or, they may be locked into one developer&rsquo;s or one shop&rsquo;s way of doing things.</p>\n\n\n\n<p>I do not necessarily see this as a <em>Bad Thing</em>. We have always had these little silos in the WordPress ecosystem, and they have mostly worked out.</p>\n\n\n\n<p>In a sense, little has changed.</p>\n\n\n\n<p>Users often stick with the same theme companies for one reason or another. And, those same themers tend to build on top of homegrown libraries or frameworks, reusing the same systems &mdash; at least the best ones do. This usually means that users can freely switch between themes made by the same people without losing anything.</p>\n\n\n\n<p>The old-school purity test of not mixing content and design is gone.</p>\n\n\n\n<p>This is a chance for solo developers and shops to strengthen their brand. If this is the system that WordPress is providing, build strong products on top of it. Build naming schemes that allow users to switch between your themes. Create loyal customers who will want to stick with you for years.</p>\n\n\n\n<p>If users are essentially locked into one shop&rsquo;s theme products, that sounds like a lucrative opportunity to build solutions and healthy user communities around individual brands.</p>\n\n\n\n<p>I also envision a future where users will need to switch themes far less often. After the site editor and global styles features become available, users will have more direct control over their design. Once they have settled on a solid theme, they may never need to change it as long as it stays relatively up to date.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 23 Jun 2021 01:04: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:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:78:"WPTavern: WooCommerce Selects Paystack as Preferred Payments Partner in Africa";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118666";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:201:"https://wptavern.com/woocommerce-selects-paystack-as-preferred-payments-partner-in-africa?utm_source=rss&utm_medium=rss&utm_campaign=woocommerce-selects-paystack-as-preferred-payments-partner-in-africa";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3656:"<p>WooCommerce has named Paystack its preferred payments partner for&nbsp;WooCommerce in Africa. More than 20,000 merchants are using the free  <a href="https://wordpress.org/plugins/woo-paystack/">Paystack WooCommerce Payment Gateway</a> plugin but searching for and downloading the plugin separately is no longer required. Store owners can now easily select Paystack as a payment method when inside the WooCommerce dashboard.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>Paystack has a recently updated tutorial for <a href="https://support.paystack.com/hc/en-us/articles/360009881280-How-to-set-up-Paystack-on-WooCommerce">how to set up the gateway in WooCommerce</a>. As an alternative to the recommended method, merchants can opt to <a href="https://wordpress.org/plugins/woo-paystack/">install the free plugin</a> instead.</p>\n\n\n\n<p>Paystack is the most widely used payment gateway in Africa, accounting for more than half of all online transactions in Nigeria. More than 60,000 stores use the gateway. In October 2020, it was <a href="https://wptavern.com/stripe-acquires-paystack-for-200m">acquired by Stripe</a> for more than $200M. The gateway can be used by businesses in Nigeria and Ghana and last month it <a href="https://paystack.com/blog/company-news/sa-launch">added support for South Africa</a>, after a six-month long pilot program. </p>\n\n\n\n<p>&ldquo;Paystack is leading the charge in bringing a world-class payments experience to African merchants,&rdquo; WooCommerce Director of Business Development Mechiel Couvaras said. &ldquo;Their product offering, user experience, and expansion plans within Africa were some of the most important factors in considering the partnership. Receiving funding from&nbsp; Stripe and Visa was also a strong indicator of their potential.&rdquo;</p>\n\n\n\n<p>Paystack, like all of WooCommerce&rsquo;s other payment partners, has a financial arrangement with the e-commerce platform where it pays a percentage of transactions processed. Couvaras said the Paystack partnership is directly with Paystack and separate from WooCommerce&rsquo;s Stripe partnership.</p>\n\n\n\n<p>&ldquo;eCommerce is still very nascent in most African countries, however, <a rel="noreferrer noopener" href="https://trends.builtwith.com/shop/WooCommerce-Checkout/Nigeria" target="_blank">Nigeria</a> and <a rel="noreferrer noopener" href="https://trends.builtwith.com/shop/WooCommerce-Checkout/South-Africa" target="_blank">South Africa</a> are amongst our fastest growing countries globally,&rdquo; Couvaras said. When Stripe acquired Paystack, the company noted that African online commerce is growing 21% year-over-year, 75% faster than the global average. WooCommerce is well-positioned to capture some of that growth with Paystack pre-installed as a preferred payment partner.</p>\n\n\n\n<p>The e-commerce platform is also keeping tabs on other emerging markets, as global market adoption has grown to <a href="https://w3techs.com/technologies/details/cm-woocommerce">8.2% of the Alexa top 10 million websites</a>. Over the past year WooCommerce launched partnerships with Indian payment companies <a rel="noreferrer noopener" href="https://woocommerce.com/products/razorpay-for-woocommerce/" target="_blank">Razorpay</a> and <a rel="noreferrer noopener" href="https://woocommerce.com/products/payu-india/" target="_blank">PayU India</a>, as well as <a rel="noreferrer noopener" href="https://woocommerce.com/products/mercado-pago-checkout" target="_blank">Mercado Pago</a>, a Latin American payments company focused on supporting local payment methods across Mexico, Brazil, Argentina, Colombia, Chile, Peru and Uruguay.</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, 22 Jun 2021 20:52:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:94:"WPTavern: A Throwback to the Past: Refreshing Old Twenty* WordPress Themes With Block Patterns";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118898";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:229:"https://wptavern.com/a-throwback-to-the-past-refreshing-old-twenty-wordpress-themes-with-block-patterns?utm_source=rss&utm_medium=rss&utm_campaign=a-throwback-to-the-past-refreshing-old-twenty-wordpress-themes-with-block-patterns";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5915:"<p class="has-drop-cap">What <a href="https://wptavern.com/past-twenty-wordpress-themes-to-get-new-block-patterns">began as a project in August 2020</a> has now become a reality. All past Twenty* default WordPress themes now have their own unique block patterns. In recent weeks, <a href="https://make.wordpress.org/core/2021/06/21/bundled-themes-changes-in-wordpress-5-8/">Twenty Ten through Twenty Fifteen received updates</a>.</p>\n\n\n\n<p>Designer Mel Choyce-Dwan kick-started tickets for all previous 10 default themes before the WordPress 5.5 release, the first version to support patterns. Twenty Twenty, Twenty Nineteen, Twenty Seventeen, and Twenty Sixteen each made the cut for that update. However, the remaining default themes were left to languish, at least for a few months and WordPress updates.</p>\n\n\n\n<p>Jumping back over a decade to update past themes might seem extreme, but all of the default themes are still some of the most popular from the directory. Granted, they had the benefit of being installed directly in WordPress. Still, the current number of active installations means they are worth a small refresh:</p>\n\n\n\n<ul><li>Twenty Fifteen: 100,000+</li><li>Twenty Fourteen: 100,000+</li><li>Twenty Thirteen: 70,000+</li><li>Twenty Twelve: 100,000+</li><li>Twenty Eleven: 100,000+</li><li>Twenty Ten: 100,000+</li></ul>\n\n\n\n<p>Despite having the lowest installation total, Twenty Thirteen has some of the best pattern designs. The Informational Section and Decorative Gallery patterns stand out the most, but all fit well with the overall theme design.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img />Informational Section</li><li class="blocks-gallery-item"><img />Decorative Gallery</li></ul>\n\n\n\n<p>Twenty Thirteen is also the only remaining default theme that supports wide and full alignments. Its one-column layout affords it more flexibility, and the old design feels fresh again with its new pattern choices. Perhaps they can revive the theme&rsquo;s lagging numbers relative to the other defaults.</p>\n\n\n\n<p>The <a href="https://core.trac.wordpress.org/ticket/51104">initial pattern designs</a> for the theme included a suite of layouts for post formats, one of the features Twenty Thirteen leaned on. Something similar to the first gallery design landed, but the others were left out.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>Patterns designed to match post formats.\n\n\n\n<p>Post formats never garnered widespread support past their launch, and the core development team all but abandoned them, never building atop the feature. However, all of the format-specific patterns might be welcome for those users still running the theme. They would have been a nostalgic nod to the old WordPress, a throwback to yesteryear. If nothing else, maybe they can serve as inspiration for those of us still clinging to that tiny sliver of hope that post formats will make a roaring comeback.</p>\n\n\n\n<p>These theme-bundled designs highlight how the <a href="https://wptavern.com/open-invitation-to-contribute-to-the-wordpress-block-pattern-directory">upcoming pattern directory</a> is not meant to be the only destination for snagging the best layout sections to drop into the block editor. Often, the best choices will be specific to the theme. Much of the flavor of custom design is lost when building for a general audience. What looks good with Twenty Twenty-One may look terrible in another and vice versa. Maybe that will change as block design tools become more robust and how they are used becomes standardized, but for now, at least, the most artistic patterns are those that designers include with their themes.</p>\n\n\n\n<p>Aside from Twenty Thirteen, Twenty Ten&rsquo;s new patterns stood out the most. The theme was the first of the new era of yearly themes, and its classic blog design has weathered the years well &mdash; just ignore the 12-pixel sidebar font size.</p>\n\n\n\n<img />Twenty Ten&rsquo;s new patterns.\n\n\n\n<p>The three patterns are at home in the theme. The Introduction pattern, which showcases the Image, Heading, and Paragraph blocks, is simple, but it relies on Twenty Ten&rsquo;s typography for an elegant article intro. The Quote and Alternating image layouts do not try to do too much, simply highlighting the theme&rsquo;s design.</p>\n\n\n\n<p>Landing squarely in my favorite-but-most-disappointing category was Twenty Fourteen. The About pattern&rsquo;s image and text looked elegant and roomy in the editor, but the front-end view painted a different picture. Because the theme lacks wide-alignment support, the photo was scrunched up. The gallery-supported Summary pattern has a lot of potential as a full-width pattern, but it falls short in the theme&rsquo;s 474-pixel wide content area.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img />About Pattern</li><li class="blocks-gallery-item"><img />Summary Pattern</li></ul>\n\n\n\n<p>There is really no reason why Twenty Fourteen could not support wide and full alignments. It has free space.</p>\n\n\n\n<p>At least the timeline-esque List pattern is pretty sweet in both the editor and front-end views. I may borrow that for my own projects.</p>\n\n\n\n<img />List pattern included with Twenty Fourteen.\n\n\n\n<p>I was not particularly excited over the other patterns, but I am happy to see a little love thrown toward the 600,000 or so users with these themes still active. I am sure many will find something they can use on their own sites.</p>\n\n\n\n<p>The themes are aging; the wrinkles and weaknesses of their designs are showing. With the site editor looming ahead, it might be time to consider retiring them. That is assuming no one wants to take the reigns and update them for a modern era. Otherwise, they will continue falling behind, remaining a relic of classic 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:"Mon, 21 Jun 2021 23:14:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:95:"WPTavern: Google Launches Search Console Insights, a User-Friendly Content Performance Overview";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118774";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:233:"https://wptavern.com/google-launches-search-console-insights-a-user-friendly-content-performance-overview?utm_source=rss&utm_medium=rss&utm_campaign=google-launches-search-console-insights-a-user-friendly-content-performance-overview";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2428:"<p>Google Analytics is powerful if you know exactly what kind of metrics you want to investigate, it but can be overwhelming if you just need a simple overview of your traffic and referrals. <a href="https://search.google.com/search-console/insights/">Search Console Insights</a> is a new tool from the <a href="https://blog.google/web-creators">Google Web Creators</a> team that is aimed at making content performance easier to understand at a glance. It combines data from Search Console and Google Analytics for a user-friendly overview of important metrics for content creators.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>Search Console Insights can help users quickly ascertain which pieces are their best performing content, how new pieces are performing, and how people are discovering the site. Clicking on the little academic cap icon offers more information about understanding the data and tips for improving content engagement and performance.</p>\n\n\n\n<p>The first section shows a site&rsquo;s content performance trend for the past 28 days using page views and page view duration. The next card displays a carousel of new content with page views, average page view duration, and badges for content that has high average duration compared to other content on the site.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>Other cards include the most popular content within the past 28 days, top traffic channels, top Google Search queries, referring links from other websites, and social media.</p>\n\n\n\n<p>The performance cards are not configurable but they give you a starting point if you want to dig deeper into Google Analytics. It would be helpful if each graph was linked to more data where you could adjust the date range.</p>\n\n\n\n<p>Search Console Insights doesn&rsquo;t include all the features unless you are using Google Analytics and associate it with your site&rsquo;s Search Console property. Users can access the tool&rsquo;s overview page by visiting the <a href="https://search.google.com/search-console/insights">link</a> directly. In the near future, Search Console Insights will be available in the iOS and Android Google apps when you tap your profile picture. The tool is <a href="https://blog.google/web-creators/improve-your-content-search-console-insights/">now in beta</a> but Google plans to roll the experience out gradually to all Search Console users in the coming days.</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, 21 Jun 2021 18:43:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:75:"WordPress.org blog: WP Briefing: Episode 11: WordCamp Europe 2021 in Review";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/news/?post_type=podcast&p=10837";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://wordpress.org/news/2021/06/episode-11-wordcamp-europe-2021-in-review/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10494:"<p>In this episode, Josepha Haden Chomphosy does a mini deep dive into WordCamp Europe 2021, specifically the conversation between the project’s co-founder, Matt Mullenweg, and Brian Krogsgard formerly of PostStatus. Tune in to hear her take and for this episode’s small list of big things.</p>\n\n\n\n<p><em><strong>Have a question you&#8217;d like answered? You can submit them to <a href="mailto:wpbriefing@wordpress.org">wpbriefing@wordpress.org</a>, either written or as a voice recording.</strong></em></p>\n\n\n\n<h2>Credits</h2>\n\n\n\n<p>Editor:<a href="https://profiles.wordpress.org/dustinhartzler/"> Dustin Hartzler</a></p>\n\n\n\n<p>Logo:<a href="https://profiles.wordpress.org/beafialho/"> Beatriz Fialho</a></p>\n\n\n\n<p>Production:<a href="https://profiles.wordpress.org/mkaz/"> </a><a href="https://profiles.wordpress.org/cbringmann/">Chloé Bringmann</a></p>\n\n\n\n<p>Song: Fearless First by Kevin MacLeod</p>\n\n\n\n<h2>References </h2>\n\n\n\n<p><a href="https://wordpress.org/news/2021/06/gutenberg-highlights/">Gutenberg Highlights&nbsp;</a></p>\n\n\n\n<p><a href="https://www.youtube.com/watch?v=o-IvKy3322k&t=12428s">Matt Mullenweg in conversation with Brian Krogsgard&nbsp;</a></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/5-8/">5.8 Development Cycle</a></p>\n\n\n\n<p><a href="https://japan.wordcamp.org/2021/">WordCamp Japan</a></p>\n\n\n\n<p><a href="https://europe.wordcamp.org/2021/a-recap-on-wceu-2021/">A recap on WCEU 2021</a></p>\n\n\n\n<h2>Transcript</h2>\n\n\n\n<span id="more-10837"></span>\n\n\n\n<p><strong>Josepha Haden Chomphosy 00:10</strong></p>\n\n\n\n<p>Hello, everyone, and welcome to the WordPress Briefing, the podcast where you can catch quick explanations of the ideas behind the WordPress open source project, some insights into the community that supports it, and get a small list of big things coming up in the next two weeks. I&#8217;m your host, Josepha Haden Chomphosy. Here we go!</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 00:40</strong></p>\n\n\n\n<p>A couple of weeks ago, we hosted WordCamp Europe and had the double pleasure of a demo that showed us a bit about the future of WordPress and an interview that looked back while also looking a bit forward. If you haven&#8217;t seen the demo, it was beautiful. And I&#8217;ve included a link to it in the show notes. And if you haven&#8217;t heard the interview, there were a few specific moments that I&#8217;d like to take the time to delve into a little more. Brian Krogsgard, in his conversation with Matt Mullenweg, brought up three really interesting points. I mean, he brought up a lot of interesting points, but there were three that I would particularly like to look into today. The first was about balance. The second was about cohesion. And the third was about those we leave behind.&nbsp;&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 01:24</strong></p>\n\n\n\n<p>So first is this question of balance. Brian brought this up in the context of the overall economic health of the WordPress ecosystem. And in that particular moment, he talked about companies that are coming together, companies that are merging. And in Matt&#8217;s answer, the part that I found the most interesting was when he said, &#8220;the point at which there is the most commercial opportunity is also the point at which there is the most opportunity for short-termism. He went on to talk about the importance of long-term thinking and collective thinking about what makes us, and us here means probably the WordPress project, more vibrant and vital in 10 or 20 or 30 years. One of the things that he specifically called out in that answer was the responsibility of larger companies in the ecosystem. For instance, like Automattic, to commit fully to giving back, there are many ways now that companies can give back to WordPress so that we all replenish the Commons. They can pay for volunteer contributors&#8217; time; they can create and sponsor entire teams through the Five for the Future program. They can contribute time through our outreach program. And they can even contribute to WordPress&#8217;s ability to own our own voice by engaging their audience&#8217;s awareness of what&#8217;s next in WordPress, or whatever. And I know this balance, this particular balance of paid contributors or sponsored contributors, compared to our volunteer contributors or self-sponsored contributors; I know that this balance is one that people keep an eagle eye on. I am consistently on a tight rope to appropriately balanced those voices. But as with so many things where balance is key, keeping an eye on the middle or the long-distance can really help us get it right.&nbsp;&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 03:23</strong></p>\n\n\n\n<p>The second question was one of cohesion and specifically cohesion over the competition. Brian asked how, if people feel disadvantaged, you can foster a feeling of cohesion rather than competition? And Matt&#8217;s first answer was that competition is great. Specifically, he said that competition is great as long as you consider where your collaboration fits into the mission. And he also spent some time exploring how competitors in the ecosystem can still work from a community-first mindset. I personally cannot agree enough about some of the benefits of collaboration alongside your competitors. I remind sponsored contributors from time to time, and I think it&#8217;s true for any contributor that you are an employee of your company first and a contributor to WordPress second. However, once you step into contribution time, your main concern is the users of WordPress, or new contributors, or the health of the WordPress ecosystem as a whole or the WordPress project. So you get all this subject matter expertise from competitive forces, collaborating in a very us versus the problem way. And when you do that, you&#8217;re always going to find a great solution. It may not be as fast as you want it to build things out in the open in public. And so sometimes we get it wrong and have to come back and fix it but still, given time, we&#8217;re going to come out with the best solution because we have so many skilled people working on this.&nbsp;&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 05:01</strong></p>\n\n\n\n<p>And then the third question that I wanted to really touch on is the question of those we leave behind. Brian asked Matt if he thought mid-sized agencies and mid-sized consultants were being squeezed out with the block editor. Matt&#8217;s high-level answer was no, and I tend to agree with him. It&#8217;s not all mid-sized anything any more than it&#8217;s all small-sized anything. His answer continued to look at what stands to change for users with the block editor and who really can stand to benefit. It made me think back to my WordPress 5.0 listening tour. We launched WordPress 5.0, which was, in case anyone forgets, the first release with the block editor in it. I took a six-month-long tour to anywhere that WordPressers were so I could hear their main worries, what Brian is saying in there, and what Matt is saying to really came up all the time in those conversations. And basically, it was that this update takes all the power away from people who are building websites. And in these conversations, and Matt and Brian&#8217;s conversation, it was really focused on our freelancers and consultants. But at the same time, all of them heard that this update gives power back to all of the people who could build websites.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 06:28</strong></p>\n\n\n\n<p>I could not shake the feeling at the time. And honestly, I can&#8217;t shake it now that no high-end consultants, or freelancers, or any other developer or site creator sit around just longing for maintenance work. After six months of talking to people, I didn&#8217;t hear anyone say, &#8220;you know, I just love making the same author card over and over and over.&#8221; Or, &#8220;updated the footer every week, this month. And that&#8217;s why I got into this business.&#8221; And more than the feeling that there just wasn&#8217;t anyone who just loved maintenance, I got a feeling that there were real problems that needed to be solved for these clients and that they wanted to solve them. And that they also would gladly trade updating footers for the much more interesting work of creating modern and stylish business hubs based on WordPress for the clients who trust them so much. All of that, I guess, is to say that, yes, the block editor does give power back to our clients again, but not at the expense of those who have to build the sites in the first place. I think it stands to restore everyone&#8217;s sense of agency more than we truly realize. So that&#8217;s my deep dive on WordCamp Europe; I included links to the demo and the talk below, just in case you haven&#8217;t seen them yet. And you want to get a little bit of insight into the full context of the conversations that I just did a bit of a deep dive into.&nbsp;</p>\n\n\n\n<p><strong>Josepha Haden Chomphosy 08:15</strong></p>\n\n\n\n<p>And now it&#8217;s time for our smallest of big things. All right, I have three things for you today. Number one, tomorrow, we package WordPress 5.8 beta three. If you&#8217;ve never had a chance to stop by the core channel in slack for the past packaging process, I really encourage you to stop by; we call them release parties. It&#8217;s a bunch of people who stand around and help get it done. So you can also see how it gets done. And if you&#8217;re feeling brave, you can even try your hand at testing out one of the packages as soon as it&#8217;s ready. The second thing is that a week from tomorrow, we reach our first release candidate milestone. So if you have meant to submit any bugs or patches or if you&#8217;ve been procrastinating on documentation, or dev notes, right now is the time so that we can have a chance to get everything into the release by the time we reach the release candidate milestone on the 29th. And the third thing is that we are currently right in the middle of WordCamp Japan. That is a great opportunity to meet some contributors and maybe even get started with contributions yourself. So stop by if you haven&#8217;t had a chance to check it out already. I will leave a link in the show notes. And that, my friends, is your small list of big things. </p>\n\n\n\n<p>Thank you for tuning in today for the WordPress Briefing. I&#8217;m your host, Josepha Haden Chomphosy, and I&#8217;ll see you again in a couple of weeks.</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, 21 Jun 2021 12:33:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Chloe Bringmann";s: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:120:"Gutenberg Times: Block-based Template Editor is coming to WordPress 5.8 and a new Widget Editor – Weekend Edition #174";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=18214";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:126:"https://gutenbergtimes.com/block-based-template-editor-is-coming-to-wordpress-5-8-and-a-new-widget-editor-weekend-edition-174/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:14624:"<p>Howdy, </p>\n\n\n\n<p>Lots happening in the larger WordPress space! More aquisitions and a new service for WordPress plugin business, flippantly named <a href="https://flipwp.co/">FlipWP</a>. </p>\n\n\n\n<p><a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-2/">WordPress 5.8 Beta 2</a>, <a href="https://github.com/WordPress/gutenberg/releases/tag/v10.9.0-rc.1">Gutenberg 10.9 RC</a> released and the first dev notes dropped for the upcoming release. More on that below. </p>\n\n\n\n<p>Don&#8217;t miss next week&#8217;s <strong>Live Q &amp; A on June 24, 2021, at 11am EDT / 15:00 UTC</strong> on theme.json for Theme Authors with our panelists Daisy Olson, Tammie Lister and Jeff Ong. Learn and discuss <a href="https://us02web.zoom.us/webinar/register/4216223029678/WN_gyOVb1h4S4iO_UZi1GMQaA">How to get started with building themes for Full-site editing.</a></p>\n\n\n\n\n\n<p>What are you working on?  Creativity is mushrooming around the WordPress ecosystem and I want to learn from you! Hit reply and let me know! I loved your notes in my inbox! Thank you. </p>\n\n\n\n<p>Yours, 💕<br />Birgit </p>\n\n\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<h2>WordPress 5.8 DevNotes and more</h2>\n\n\n\n<p><strong>Grzegorz Ziolkowski</strong> posted the article <strong><a href="https://make.wordpress.org/core/2021/06/16/block-editor-api-changes-to-support-multiple-admin-screens-in-wp-5-8/">Block Editor API Changes to Support Multiple Admin Screens</a>.</strong> &#8220;WordPress 5.8 is the first&nbsp;core&nbsp;release where the post editor is no longer the only&nbsp;admin&nbsp;screen that uses the&nbsp;block&nbsp;editor. The updated widgets editor screen will also support blocks.&#8221;, he wrote. It&#8217;s quite technical and developers will appreciate it as it opens the doors to use the bock editor on other admin screen, for instance for plugin dashboards and features. It makes my long time wish possible:  replace the &#8220;Quick Draft&#8221; widget with an instance of the block editor and have writers start writing immediately after login, instead of having to open yet another screen. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Riad Benguella</strong> introduces us to the <a href="https://make.wordpress.org/core/2021/06/16/introducing-the-template-editor-in-wordpress-5-8/"><strong>Template Editor coming to WordPress</strong></a> in its 5.8 release. It comes with a series of new blocks to accommodate Site-wide information, like Site Title or Site Logo as well as post parts for the Query Block, like Post Title, Post Excerpt, Feature Image. In total, 13 Blocks that replace some template parts in conventional themes.  Some blocks will be made <a href="https://github.com/WordPress/gutenberg/issues/28744">available also for classic Themes </a>to accommodate <a href="https://github.com/WordPress/gutenberg/issues/29024">hybrid themes</a> and to support the gradual adoption of block-based themes. </p>\n\n\n\n<p><strong>Justin Tadlock</strong> wrote <a href="https://wptavern.com/getting-to-know-the-upcoming-wordpress-5-8-template-editor">about it on the WPTavern</a>, too. </p>\n\n\n\n\n<p><strong>&nbsp;<a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/" target="_blank" rel="noreferrer noopener">&#8220;Keeping up with Gutenberg &#8211; Index 2021&#8221;</a>&nbsp;</strong><br />A chronological list of the WordPress Make Blog posts from various teams involved in Gutenberg development: Design, Theme Review Team, Core Editor, Core JS, Core CSS, Test and Meta team from Jan. 2021 on. Updated by yours truly.  <a href="https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/keeping-up-with-gutenberg-index-2020/">The index 2020 is here</a></p>\n\n\n\n\n<h2>For Site owners and Content Creators</h2>\n\n\n\n<p><strong><a href="https://twitter.com/HariShanker">Hari Shanker</a></strong> from the community team published <a href="https://make.wordpress.org/community/2021/06/18/meetup-group-resources-talking-points-for-wordpress-5-8/"><strong>Talking points for WordPress 5.8</strong></a> of Meetup organizer, that also helps agency owners and freelancers to quickly get an overview of what is coming in the new version. Hari clusters the upcoming changes per WordPress stakeholders. You&#8217;ll find a section for Publishers and users, and another one for site builders and developers. <strong>If you want to read just one article, this would be it. </strong>🚀</p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong><a href="https://twitter.com/chrislema">Chris Lema</a></strong> makes a strong case for  <a href="https://chrislema.com/embracing-gutenberg-completely/"><strong>Embracing Gutenberg Completely</strong></a>. Out of necessity, he decided to rebuild his site with Gutenberg blocks. All site metrics tools suggested reducing the DOM size of his Landing pages build with 3rd party page builders. With this switch, Chris realized, what he needs and doesn&#8217;t need for a highly performing website. His five observations put a few things in perspective for him as a daily writer, he came to appreciate the tools and blocks that come with the block editor. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p>The team at <strong>PublishPress</strong> posted a short tutorial on <strong><a href="https://publishpress.com/blog/gutenberg/nested-blocks-gutenberg-editor/">How to Use Nested Blocks in the Gutenberg Editor</a>,</strong> as it&#8217;s still a little confusing for content creators to navigate, especially Column blocks. The persistent list view coming to WordPress 5.8 will help with this, though. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong><a href="https://twitter.com/javier">Javier Acre</a></strong> from the WordPress design team published a <a href="https://make.wordpress.org/design/2021/06/15/a-walk-around-the-table-block/"><strong>Walk through of possible enhancements for the Table Block</strong></a>. He showcases update to the placeholder state, multicell selection, the sidebar, the toolbar and icon improvements. You&#8217;ll see mock-ups for each. It&#8217;s quite exciting to see, as we probably can all agree that the Table block needs so TLC, 🙂 You can leave your thoughts and ideas in the comments of the post. </p>\n\n\n\n<img />Mockup of Toolbor for the Table block \n\n\n\n<h2>Theme builders</h2>\n\n\n\n<p><strong>Dave Smith</strong> has notes on <a href="https://aheadcreative.co.uk/articles/testing-the-gutenberg-widgets-editor-for-wordpress-5-8"><strong>how to test the new Widget Editor that will come with WordPress 5.8</strong></a>. He followed <a href="https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/">Andrei Draganescu call for testing</a> and logged his experience. To test for backwards compatibility for your existing widgets, you can first create some with the new widget editor disabled using the <a href="https://wordpress.org/plugins/classic-widgets/">Classic Widget plugin,</a> and then deactivate the plugins and try to manage and edit the widgets with the block-based editor. You have only a month to make sure your sites won&#8217;t run into trouble. WordPress 5.8 will be released on July 20th, 2021. </p>\n\n\n\n<div class="wp-block-group has-primary-color has-light-background-background-color has-text-color has-background"><div class="wp-block-group__inner-container">\n<p class="has-normal-font-size"><strong><a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA">Join us for our next Live Q &amp; A</a> </strong>on <strong>June 24, 2021, at 11am EDT / 15:00 UTC</strong></p>\n\n\n\n<a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA"><img /></a>\n\n\n\n<p><strong><a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA">Theme.json for Theme Authors or building themes for full-site editing in WordPress.</a></strong><br /><strong>Host</strong>: Birgit Pauli-Haack<br /><strong>Panel:</strong>&nbsp;Daily Olsen, Tammie Lister and Jeff Ong           <span class="has-inline-color"><strong><a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA">Register Now</a></strong></span></p>\n</div></div>\n\n\n\n<p><br /><a href="https://twitter.com/one_maggie"><strong>Maggie Cabrera</strong></a> posted the <strong><a href="https://make.wordpress.org/themes/2021/06/18/gutenberg-themes-week-of-june-18-2021/">Gutenberg + Themes: Week of June 18, 2021,</a> </strong>roundup of relevant discussions, issue and PRs for Theme builders. She covered Full-Site Editing, Global Styles and block-based Themes. Chime on on the discussion and test the new releases. If you are a theme developer trying to catch up with what&#8217;s happening with Gutenberg, the Overview / Tracking issues section should get you started. You&#8217;ll find links to documentation and tutorials as well. </p>\n\n\n\n\n<p><a href="https://gutenbergtimes.com/podcast/changelog-45-wordpress-5-8-upcoming-live-qa-and-gutenberg-10-7-and-10-8/"><strong>Episode #45</strong> is now available</a> with transcript. <br />Next recording June 25th, 2021</p>\n\n\n\n<p> <strong>Subscribe to the&nbsp;<a href="https://gutenbergtimes.com/podcast/">Gutenberg Changelog</a>&nbsp;podcast </strong><br />🎙️&nbsp;<a href="https://open.spotify.com/show/620NwVKQJGdTupy36zYxvg?mc_cid=4b6c9f88fe">Spotify</a>&nbsp;|&nbsp;<a href="https://podcasts.google.com/feed/aHR0cHM6Ly9ndXRlbmJlcmd0aW1lcy5jb20vZmVlZC9wb2RjYXN0">Google</a>&nbsp;|&nbsp;<a href="https://podcasts.apple.com/us/podcast/gutenberg-changelog/id1469294475">iTunes</a>&nbsp;|&nbsp;<a href="https://pca.st/podcast/f8445ec0-7508-0137-f267-1d245fc5f9cf">PocketCasts</a>&nbsp;|&nbsp;<a href="https://www.stitcher.com/show/gutenberg-changelog">Stitcher</a>&nbsp;|<br />🎙️&nbsp;<a href="https://www.podbean.com/podcast-detail/chi7j-9904a/Gutenberg-Changelog-Podcast">Pod Bean</a>&nbsp;|&nbsp;<a href="https://castbox.fm/channel/Gutenberg-Changelog-id2173375">CastBox</a>&nbsp;|&nbsp;<a href="https://www.podchaser.com/podcasts/gutenberg-changelog-878239/">Podchaser</a>&nbsp;|&nbsp;<a href="https://gutenbergtimes.com/feed/podcast">RSS Feed</a>&nbsp;</p>\n\n\n\n<img />\n\n\n\n\n<h2>Plugin Developers</h2>\n\n\n\n<p><strong>Dave Smith</strong> published a tutorial on <a href="https://aheadcreative.co.uk/articles/mocking-wordpress-api-fetch-in-gutenberg-unit-tests/"><strong>Mocking @wordpress/api-fetch in Gutenberg unit tests</strong></a>. During development you don&#8217;t want to hit an external API everytime you run a unit test, these instructions show you how to mock data coming from an API call in your block or site. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><a href="https://wordpress.org/plugins/genesis-custom-blocks/">Genesis Custom Blocks</a>, (former Block Lab plugin) are a nifty tool to create blocks without going through the pain of learning modern JavaScript. You use the UI to create Field Groups and then add the PHP display code to your theme template. But what if you want to separate the newly create blocks from the theme? Then you could install it on multiple sites, and it would survive a site owners decision to switch themes without loosing content. <strong><a href="https://twitter.com/rob_stino">Rob Stinson</a></strong> has a two-part tutorial for you on <a href="https://studiopress.blog/how-to-package-up-your-custom-blocks-in-a-plugin-part-1/"><strong>How to package up your custom blocks in a plugin</strong></a>. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><strong>Jeffery Carandang</strong>, a Gutenberg adopter of the first hour, <a href="https://jeffreycarandang.com/extendify-is-taking-over-the-editorskit-plugin-and-add-ons-shareablock-and-other-tools/">found a new home for his Gutenberg entities</a>: <strong>Extendify. </strong> Jeffery has been pushing the envelope on what is possible with Gutenberg since it first came out in 2017. <a href="https://wordpress.org/plugins/coblocks/"><strong>CoBlocks</strong></a>, co-authored with Rich Tabor and later sold to GoDaddy, was a favorite block plugin for additional blocks. <strong>EditorsKit</strong> extended blocks with additional tools. We mentioned his <a href="https://shareablock.com/">Share a Block</a> directory on multiple episodes of the podcast. After starting at 10up, he didn&#8217;t find much time anymore for his love projects, especially the very useful <a href="https://wordpress.org/plugins/block-options/">EditorsKit plugin</a> hasn&#8217;t seen updates for the last nine months. It now found a home at Extendify.  <br />See also: </p>\n\n\n\n<ul><li>Arthor Grabowski: <a href="https://extendify.com/extendify-is-adopting-the-editorskit-plugin/">Extendify is Adopting the EditorsKit plugin</a></li><li>Justin Tadlock: <a href="https://wptavern.com/extendify-adopts-editorskit-increasing-its-block-plugin-collection">Extendify Adopts EditorsKit, Increasing Its Block Plugin Collection</a></li></ul>\n\n\n\n\n<p><strong><a href="https://gutenbergtimes.com/need-a-zip-from-master/">Need a plugin .zip from Gutenberg&#8217;s main (trunk) branch?</a></strong><br />Gutenberg Times provides daily build for testing and review. <br />Have you been using it? Hit reply and let me know.</p>\n\n\n\n<p><img alt="GitHub all releases" src="https://img.shields.io/github/downloads/bph/gutenberg/total?style=for-the-badge" /></p>\n\n\n\n<p></p>\n\n\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p class="has-text-align-center"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>\n\n\n\n<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email">Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n\n<p>Featured Image: Miami at Night by Birgit Pauli-Haack</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, 19 Jun 2021 18:11: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:18:"Birgit Pauli-Haack";s: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:68:"WPTavern: Getting To Know the Upcoming WordPress 5.8 Template 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:30:"https://wptavern.com/?p=118777";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:181:"https://wptavern.com/getting-to-know-the-upcoming-wordpress-5-8-template-editor?utm_source=rss&utm_medium=rss&utm_campaign=getting-to-know-the-upcoming-wordpress-5-8-template-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:10320:"<p class="has-drop-cap">WordPress 5.8 is slated for <a href="https://make.wordpress.org/core/5-8/">release on July 20</a>. In just over a month, many users will get their first taste of one of my favorite new features: template-editing mode.</p>\n\n\n\n<p>The template editor is a new tool that allows end-users to create custom templates without ever leaving the post-editing screen. It exists as a stepping stone toward the eventual site editor, a feature that will hand over complete design control to those who want it.</p>\n\n\n\n<p>The downside to the new feature in WordPress 5.8 is that users will not have access to their theme&rsquo;s header, footer, sidebar, or other template parts. It is a blank slate in which they must put on their design caps to create the entire page.</p>\n\n\n\n<p><em>With these limitations in place, what is the point of the template editor launching with WordPress 5.8?</em></p>\n\n\n\n<p>Landing pages.</p>\n\n\n\n<p>A blank slate is not always a bad thing. There is a reason all the best themes include page templates named Blank, Empty, Canvas, Open, or something similar. Sometimes users want control over the entirety of the page&rsquo;s output. And WordPress 5.8 is bringing that capability to every WordPress user.</p>\n\n\n\n<p>I have been editing templates for months now, but always in the context of a block theme. I have built both a <a href="https://wptavern.com/fse-outreach-7-building-a-portfolio-in-the-upcoming-template-editing-mode">photography portfolio</a> and <a href="https://wptavern.com/fse-outreach-round-6-building-a-wordcamp-landing-page-via-the-template-editor">WordCamp landing page</a> as part of the FSE Outreach Program. Despite some hiccups, it has been a worthwhile journey being involved as the feature has come to fruition. However, most of my testing was on top of the <a href="https://wordpress.org/themes/tt1-blocks/">TT1 Blocks theme</a>.</p>\n\n\n\n<p>It was time to put it to a real-world test with themes that are actually in wide use.</p>\n\n\n\n<h2>Will It Work With My Theme?</h2>\n\n\n\n<p class="has-drop-cap">The question many users will have on their minds will be: will this new template editor work with my theme? The answer is that it depends. Generally, yes, it will work to some degree. However, because older designs were not created with the template editor in mind, not all experiences will be the same.</p>\n\n\n\n<p>I wanted to really put this theory of working with every theme to the test. So, I loaded up Twenty Fifteen, one of my favorite default themes from the past decade.</p>\n\n\n\n<p>Perhaps I jumped too far back.</p>\n\n\n\n<img />Twenty Fifteen has a two-color background meant for sidebar and content.\n\n\n\n<p>The block editor did not exist back when Twenty Fifteen was built. Its use of a box-shadow technique on the page background meant the entire page had two colored columns running down it. The design team had to use some hacky methods for equal-height sidebar and content backgrounds. <em>Ahhh&hellip;the good old days before developers had access to CSS flex-box and grid.</em></p>\n\n\n\n<p>It is these sorts of problems that could limit some older themes. In the case of Twenty Fifteen, I could hide the background with a Group or Cover block over the top of it.</p>\n\n\n\n<p>Users will likely get better results when using something more modern, at least a theme built during the block era. Even something as simple as wide-alignment support will change the WYSIWYG nature of the template editor. If a theme does not support the feature, the front end will not match the editor.</p>\n\n\n\n<p>I jumped ahead a few years. Twenty Nineteen was the first default WordPress theme to support blocks. It is old but not ancient in internet years.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>Editor vs. front end of Twenty Nineteen.\n\n\n\n<p>There are some differences between the editor and front-end views. The Cover block padding is off, the vertical spacing does not match, the search input&rsquo;s font size is different, and the search button&rsquo;s border radius is round on the front end. However, it is nearly a three-year-old theme now. It held up better than expected in this simple test.</p>\n\n\n\n<p>Jumping ahead a couple of years, I activated Twenty Twenty-One, WordPress&rsquo;s most recent default theme.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>Editor vs. front end of Twenty Twenty-One.\n\n\n\n<p>The editor is a pretty close approximation of what you see on the front end. The most noticeable differences are the inconsistent padding for the Cover block and the light gray border for the search input field in the editor view.</p>\n\n\n\n<p>It was time to put the template editor to the &ldquo;real&rdquo; test. I activated the latest version of Eksell, one of the <a href="https://wptavern.com/compatibility-is-not-enough-the-eksell-wordpress-theme-creates-art-with-blocks">most well-rounded block themes</a> in existence.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul> Editor vs. front end of Eksell.\n\n\n\n<p>Obviously, the theme outputs a black section on the left. That is intended for the theme&rsquo;s sidebar/menu flyout. However, because the user has no access to the template part that outputs that element, it may be impossible for some to create custom templates with this theme. I am sure that Anders Nor&eacute;n, the developer, will address this problem.</p>\n\n\n\n<p>Similar, unknown issues will arise with the many thousands of themes in the wild. It does not mean a theme is necessarily bad. It just means it was not built with the template editor in mind. Users may need to throttle back their hopes a bit until they have thoroughly tested template-editing mode with their active theme.</p>\n\n\n\n<p>Oh, and that ugly whitespace that shows the content background at the top of the editor? You will see that with literally every theme. I am clueless as to why the development team thought that it would make for a good default. Nearly every web design I have looked at over the years zeroes out the page&rsquo;s <code>&lt;body&gt;</code> element padding.</p>\n\n\n\n<p>For those theme authors who are reading, you will need to deal with this. If you have already been building for the block editor, you are likely a pro at handling such quirks.</p>\n\n\n\n<p>If we look at a custom theme I have been building, you can see no alignment issues between the editor and front end.</p>\n\n\n\n<ul><li class="blocks-gallery-item"><img /></li><li class="blocks-gallery-item"><img /></li></ul>  Editor vs. front end of custom block theme.\n\n\n\n<p>The difference for my theme is that I am building when the template editor is already a part of the Gutenberg plugin. The others were all created earlier. It is not fair to compare them. However, users should know that older themes might not work well. They may need to wait for updates or try out a fresh design before taking advantage of template editing.</p>\n\n\n\n<p>I also chose Twenty Nineteen, Twenty Twenty-One, and Eksell because they were designed by professionals in our industry and were released in the last few years. They each hold up well but have a few issues that would be trivial to fix.</p>\n\n\n\n<p>All of this is to say that results may vary &mdash; wildly.</p>\n\n\n\n<h2>The Ideal Way To Use the Template Editor</h2>\n\n\n\n<p class="has-drop-cap">My fear with the template editor is that users will begin mixing their content directly into the editor. It is an issue I brought up during round #7 of the FSE Outreach Program. Ultimately, it is a question about the boundary between content and template.</p>\n\n\n\n<p>Traditionally, theme authors would build custom templates for their end-users to apply to their pages. Unless those users knew how to make direct code changes, they only selected the template and edited their own content via the editor. It was always clear where content editing ended and template editing began.</p>\n\n\n\n<p>The new mode muddies the waters a bit. Because users have direct access to change the template from within the post/page editor itself, I have no doubt that many will create the entire page&rsquo;s content from within the template editor.</p>\n\n\n\n<p>Even I made the mistake of putting what would typically be content in my example templates above. This was purely for illustration.</p>\n\n\n\n<p>There is nothing wrong with this if it the user&rsquo;s intention. However, templates are generally meant for controlling the layout of the page. Things like the header, footer, and content wrapping element belong within it, while the content itself is stored separately. Templates are also meant to be reused. If you apply the same template to multiple pages, any changes made to that template will update every page.</p>\n\n\n\n<p>My recommended starting point is to simply add the Post Content block to the template. You can do so from the block inserter or by pasting in this code snippet:</p>\n\n\n\n<pre class="wp-block-code"><code>&lt;!-- wp:post-content {"layout":{"inherit":true}} /--&gt;</code></pre>\n\n\n\n<p>If you just want a blank/empty template, which is what the editor is good at right now, this is all you need. You can move back to the page editor and unleash your creativity.</p>\n\n\n\n<p>Here is the start of a novelist landing page I built from this blank template:</p>\n\n\n\n<img />\n\n\n\n<p>The content of the page was added via the post editor rather than in template-editing mode. This will allow me to create multiple pages using the same open canvas.</p>\n\n\n\n<p>If you want to add other layout elements, you can tack them on too. Try mixing and matching the Site Title, Site Tagline, and Navigation blocks as a header. Drop in a Columns block with other blocks to create a &ldquo;widget area&rdquo; in the footer.</p>\n\n\n\n<p>The power of the template editor is coming with block themes. Eventually, designers will be able to pre-build these templates, and users will customize them. They will also have access to a more robust suite of blocks, such as loading up template parts. However, we have to wait until at least WordPress 5.9 later this year before they become available, and that is not set in stone yet.</p>\n\n\n\n<p>Until then, we have a sort-of-OK-but-kind-of-amazing landing page creator.</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, 19 Jun 2021 03:08: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:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:73:"WPTavern: MapLibre Project Gains Momentum with MapLibre GL Native 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:30:"https://wptavern.com/?p=118711";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:191:"https://wptavern.com/maplibre-project-gains-momentum-with-maplibre-gl-native-release?utm_source=rss&utm_medium=rss&utm_campaign=maplibre-project-gains-momentum-with-maplibre-gl-native-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:2774:"<p>The <a href="https://github.com/maplibre/maplibre-gl-js">MapLibre</a> project is picking up speed with the release of <a href="https://www.maptiler.com/news/2021/06/maplibre-gl-native-open-source-mobile-sdk-for-android-and-ios/">MapLibre GL Native</a>, an open source mobile SDK for Android and iOS. As anticipated, MapTiler&rsquo;s fork of Mapbox&rsquo;s mobile map SDKs are coming under the MapLibre umbrella. This free library enables developers to write native applications that can display vector maps on mobile devices, with advanced functionality like custom map styles and integrating specific business data.</p>\n\n\n\n<p>The project was formed by Mapbox&rsquo;s open source contributor community after the company announced that&nbsp;<a href="https://wptavern.com/mapbox-gl-js-is-no-longer-open-source">Mapbox GL JS version 2.0 would be released under a proprietary license</a>.&nbsp;MapLibre GL founders include a diverse group of companies who are contributing to this healthy, community-led fork, including MapTiler, Elastic, StadiaMaps, Microsoft, Ceres Imaging, WhereGroup, Jawg, Stamen Design, and more.</p>\n\n\n\n<p>MapLibre GL Native is developed and maintained as an independent mobile SDK, led by the MapTiler team in cooperation with Amazon, Facebook, Microsoft, and the MapLibre community. MapTiler forked Mapbox&rsquo;s last version released under the OSS license in December 2020, and ensured that developers can migrate their apps with just a few lines of code. The release post identifies a few critical changes in the MapLibre SDK:</p>\n\n\n\n<ul><li>Tracking of end-users (telemetry) has been removed</li><li>OSS license: community ownership ensures it stays open-source forever</li><li>Updated distribution model: the library is now distributed via the Maven Central repository for Android and as a Swift package for iOS</li><li>Optional usage of authorization: access token requirement depended on the map provider and its policy</li></ul>\n\n\n\n<p>WordPress core doesn&rsquo;t include a Map block but WordPress.com and Jetpack both use Mapbox GL JS 1.13.0. This is the last open source version before Mapbox updated to its proprietary license. I created a <a href="https://github.com/Automattic/jetpack/issues/20127">ticket</a> to put it on the Jetpack team&rsquo;s radar, and it looks like they may consider migrating to MapLibre in a future release. <a href="https://wordpress.org/plugins/search/mapbox/">Plugin authors using Mapbox</a> will also be at a crossroads when it comes time to update beyond version 1.13.0. MapLibre is the strongest alternative to Mapbox&rsquo;s proprietary 2.x update. Migration instructions are available in the <a href="https://github.com/maplibre/maplibre-gl-js#migrating-from-mapbox-gl">MapLibre GL readme</a> file.</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, 18 Jun 2021 21:19: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: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:77:"WPTavern: Extendify Adopts EditorsKit, Increasing Its Block Plugin Collection";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118627";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:197:"https://wptavern.com/extendify-adopts-editorskit-increasing-its-block-plugin-collection?utm_source=rss&utm_medium=rss&utm_campaign=extendify-adopts-editorskit-increasing-its-block-plugin-collection";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6709:"<p class="has-drop-cap">Extendify has been scooping up some successful block-related plugins in recent months. It acquired the Redux Framework in November 2020 and followed it up with a <a href="https://wptavern.com/extendify-acquires-editor-plus-introduces-commercial-templates-in-its-plan-to-improve-block-editing">purchase of Editor Plus</a> and Gutenberg Hub in December. Its latest pickup? <a href="https://wordpress.org/plugins/block-options/">EditorsKit</a>.</p>\n\n\n\n<p>This <a href="https://extendify.com/extendify-is-adopting-the-editorskit-plugin/">ownership change</a> was an adoption rather than an acquisition. The company is compensating Jeffrey Carandang, EditorsKit&rsquo;s creator, for helping during the transition.</p>\n\n\n\n<p>&ldquo;The main motivation was to ensure that EditorsKit has a good home,&rdquo; said Extendify co-founder Chris Lubkert. &ldquo;Jeffrey had taken a full-time role with 10up, and the plugin hasn&rsquo;t seen any updates in 9 months. So we are both excited about Extendify building on what Jeffrey has built and continuing to serve the user base.&rdquo;</p>\n\n\n\n<p><a href="https://editorskit.com/">EditorsKit</a> is a playground of extensions on top of the existing blocks. From visibility logic to text formatting to extra block options, it has a little bit of everything. Carandang has often launched features long before something similar has landed in WordPress. It has grown to over 20,000 active installs since he first submitted it to the plugin directory.</p>\n\n\n\n<p>Taking on a new role with 10up as a web engineer left him little time to devote to the plugin. &ldquo;My time was occupied by my full-time work and adjusting through my shifts, personal stuff, and with what&rsquo;s happening in the world due to lockdowns; and the covid virus,&rdquo; he wrote in his own <a href="https://jeffreycarandang.com/extendify-is-taking-over-the-editorskit-plugin-and-add-ons-shareablock-and-other-tools/">farewell post</a>. &ldquo;I hate to admit it but I think I&rsquo;ve neglected my role in the EditorsKit plugin/community that I&rsquo;ve built for the past couple of years. With this, my sincere apology to the plugin users and the whole community.&rdquo;</p>\n\n\n\n<h2>Changes to EditorsKit</h2>\n\n\n\n<p class="has-drop-cap">When a plugin changes owners, users sometimes must brace themselves for changes. Right now, EditorsKit is the same plugin it has always been. However, the Extendify team has introduced some additions.</p>\n\n\n\n<p>The first is a part of what will eventually be a commercial aspect of the plugin: the Extendify Library. The team added this feature to both the Redux and Editor Plus plugins earlier this year. EditorsKit users will see a new &ldquo;Library&rdquo; button at the top of the editor. Once they click it, it opens an overlay for importing patterns and templates from Extendify&rsquo;s collection.</p>\n\n\n\n<img />Popup library for importing Extendify patterns and templates.\n\n\n\n<p>The amount of imports allowed is limited to three without signing up. &ldquo;EditorsKit users have access to the same library of patterns and templates and can import three patterns and/or templates,&rdquo; said Lubkert. &ldquo;Anyone who signs up for the beta program will then receive unlimited imports during the beta period. We expect this to continue for a few more weeks.&rdquo;</p>\n\n\n\n<p>Essentially, the commercial aspect of EditorsKit, Editor Plus, and Redux will be a shared library from the Extendify team. Users of any one of the plugins can continue using their preferred plugin with the option of importing patterns and templates. Lubkert said they still have no plans of rolling all of the plugins into one &ldquo;super plugin,&rdquo; keeping them each as a separate project.</p>\n\n\n\n<p>&ldquo;It makes sense for us to invest our energy into a single library and creating the best experience possible for our users,&rdquo; he said.</p>\n\n\n\n<p>The second change the team has implemented is making the <a href="https://editorskit.com/wordpress-gutenberg-editor-typography-and-google-fonts-add-on/">EditorsKit Typography add-on</a> a free download. The plugin allows users to select from a list of hand-picked Google Fonts and use them anywhere. It also has a customizable set of default font combinations.</p>\n\n\n\n<p>It makes sense to drop the commercial aspect of this add-on. WordPress is already starting to provide theme authors with the tools for typography options at the block level. EditorsKit Typography may be the better of the two right now, but the average user will not need it as the core platform continues to improve.</p>\n\n\n\n<h2>ShareABlock and Other Projects</h2>\n\n\n\n<p class="has-drop-cap">The handover includes Carandang&rsquo;s related sites. <a href="https://shareablock.com/">ShareABlock</a>, <a href="https://copyglyphs.com/">CopyGlphys</a>, and <a href="https://copygradients.com/">CopyGradients</a> are all tools for helping WordPress users build on top of the block system. The Extendify team plans on keeping them alive.</p>\n\n\n\n<p>Carandang <a href="https://wptavern.com/creator-of-editorskit-launches-community-block-sharing-site">launched ShareABlock</a> in December 2019. Essentially, it was a block patterns directory. Only, block patterns were merely an idea in the bowels of the Gutenberg GitHub repository at the time. The upcoming <a href="https://wordpress.org/patterns/">pattern directory</a>, expected to <em>officially</em> open next month, was not even a blip on most people&rsquo;s radar.</p>\n\n\n\n<img />ShareABlock homepage with downloadable &ldquo;patterns.&rdquo;\n\n\n\n<p>ShareABlock has had time to mature. Its designs are more modern than the current offering from the pattern directory. The downside is the reliance on EditorsKit to import them via a JSON file instead of copy-paste block HTML code.</p>\n\n\n\n<p>With a few tweaks, it could be a serious contender as an alternative directory. If the WordPress development team follows through with a ticket I opened for <a href="https://github.com/WordPress/gutenberg/issues/32696">allowing third-party vendors</a> to hook into the system, it would be easy to do.</p>\n\n\n\n<p>&ldquo;In general, we don&rsquo;t see ourselves competing with the pattern directory (or anything else in core Gutenberg),&rdquo; said Lubkert. &ldquo;We&rsquo;d like to solve unmet needs for the community and do so in a way that is complementary to core.&rdquo;</p>\n\n\n\n<p>The team already has the patterns in place. Hooking in its existing library would be more of a value-add. The official directory is limited to what can be done with core block options. Extendify would have the wiggle room for adding designs built with its more robust EditorsKit and Editor Plus toolsets.</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, 18 Jun 2021 00:43:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:83:"WPTavern: Automattic Launches Mayland Blocks, Its Second FSE Theme on 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:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118429";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:209:"https://wptavern.com/automattic-launches-mayland-blocks-its-second-fse-theme-on-wordpress-org?utm_source=rss&utm_medium=rss&utm_campaign=automattic-launches-mayland-blocks-its-second-fse-theme-on-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:5502:"<p class="has-drop-cap">Automattic released its second block theme to the WordPress theme directory last week. <a href="https://wordpress.org/themes/mayland-blocks/">Mayland Blocks</a> is geared toward photographers and other users who want to showcase their projects. It is the child of <a href="https://wptavern.com/the-automattic-theme-team-announces-blockbase-its-new-block-parent-theme">Blockbase</a>, a sort of starter/parent hybrid the company&rsquo;s Theme Team recently announced.</p>\n\n\n\n<p>I had high hopes for Mayland Blocks going in. I have kept a loose eye on its <a href="https://github.com/Automattic/themes/tree/trunk/mayland-blocks">GitHub repository</a> in the last couple of months. It was one of the first 100% block-built themes the team seemed to be working on.</p>\n\n\n\n<p>While block themes are still experimental at this stage, I was admittedly disappointed. Maybe my expectations were too high. I was eager to be wowed when I should have gone into this review more level-headed. However, I am who I am, and that is someone who is genuinely excited each and every time a new block theme comes along. I am ready for the next big thing, but Mayland Blocks did not fit the bill.</p>\n\n\n\n<p>As I began the process of testing the theme, the first order of business was to recreate the Masonry gallery as shown in the theme&rsquo;s screenshot:</p>\n\n\n\n<img />Expected gallery layout from Mayland Blocks\n\n\n\n<p>My first thought was that the default gallery output would <em>automagically</em> work. <em>It did not.</em> Then, I looked for a Gallery block style. <em>Nothing there.</em> I searched for a custom pattern. <em>Nothing there either.</em> In short, it was impossible to recreate the gallery shown in the theme&rsquo;s screenshot &mdash; one of the primary features that drew me to it.</p>\n\n\n\n<p>Bummer. I was looking forward to seeing a Masonry-style gallery of images built on top of the block system.</p>\n\n\n\n<img />Standard gallery output with Mayland Blocks.\n\n\n\n<p>With a tiny bit of sleuthing and peeking under the hood of the <a href="https://maylandblocksdemo.wordpress.com/">theme&rsquo;s demo</a> on WordPress.com, I saw that it was using the <a href="https://wordpress.org/plugins/coblocks/">CoBlocks plugin</a> by GoDaddy. The thing that made the theme special had nothing to do with the theme.</p>\n\n\n\n<p>After a quick install, I converted my existing gallery to the CoBlocks Masonry block. Success!</p>\n\n\n\n<img />Masonry gallery output via CoBlocks.\n\n\n\n<p>At that point, I began to wonder why I was even testing Mayland Blocks at all. Its claim to fame hinged on showcasing photography. The core Gallery block works well enough, and I can use CoBlocks with any theme. Most decent ones provide the sort of open-canvas template that is no different than Mayland&rsquo;s front page.</p>\n\n\n\n<p>What would have made it a great theme would have been living up to its screenshot&rsquo;s promise. This was also a missed opportunity to showcase some alternate Gallery block styles and patterns. If we want more users to buy into this system, some of our best design and development teams need to take that one extra step.</p>\n\n\n\n<p>For such a simple theme, one well-suited as a one-page design, this was the moment to lean into the photography angle.</p>\n\n\n\n<p>Provide users a Polaroid picture frame option:</p>\n\n\n\n<img />\n\n\n\n<p>Add a &ldquo;no gutter&rdquo; block style:</p>\n\n\n\n<img />\n\n\n\n<p>Bundle a few patterns that combine the Gallery block with others. Give us a little flavor.</p>\n\n\n\n<p>Mayland Blocks works well as a WordPress.com child theme because its suite of plugins is available to all users out of the box. For a publicly-released project on WordPress.org, it is a little disappointing that it was a straight port.</p>\n\n\n\n<p>The child theme is essentially its parent with an open-canvas front page template and some trivial font and color changes. Surprisingly, it made it into the theme directory with so few alterations. Two days later, another child theme was <a href="https://themes.trac.wordpress.org/ticket/100381">outright rejected</a> for just adding &ldquo;some minor changes which can be made directly from the parent theme.&rdquo; The inconsistent application of the guidelines by different reviewers has long been a thorny issue, especially when more subjective rules come into play.</p>\n\n\n\n<p>However, block themes have more wiggle room at the moment. There are so few for users to test that it makes sense to let things slide.</p>\n\n\n\n<p>One of the Themes Team&rsquo;s previous hard lines has been that bundled front page templates must respect the user&rsquo;s reading settings. This meant that if a user explicitly chose to show blog posts on their front page, the theme must display those posts.</p>\n\n\n\n<p>Mayland Blocks is the first that I have seen get a pass on this, a hopeful sign of more leeway for directory-submitted themes in the future.</p>\n\n\n\n<p>Block themes are a different beast. HTML files are not dynamic, and there is no way to put a PHP conditional check in a <code>front-page.html</code> file in the same way as themers once did in a <code>front-page.php</code> template. There is a technical workaround for this, but I do not think it is necessary. Block themes are changing the game, and the guidelines will need to follow.</p>\n\n\n\n<p>I love seeing the contribution &mdash; any contribution, really &mdash; of another block theme to WordPress.org. However, I want to see more artistry on top of the Blockbase parent theme.</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, 17 Jun 2021 00:43:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:106:"WPTavern: Alex Denning and Iain Poulson Launch FlipWP, an Acquisitions Marketplace for WordPress Companies";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118501";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:255:"https://wptavern.com/alex-denning-and-iain-poulson-launch-flipwp-an-acquisitions-marketplace-for-wordpress-companies?utm_source=rss&utm_medium=rss&utm_campaign=alex-denning-and-iain-poulson-launch-flipwp-an-acquisitions-marketplace-for-wordpress-companies";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5525:"<p>Alex Denning and Iain Poulson launched <a href="https://flipwp.co/">FlipWP</a> today, a private marketplace  to facilitate acquisitions for WordPress companies. WP Engine&rsquo;s recent published research, which estimates the <a href="https://wpengine.com/wordpress-economy/">WordPress economy at $596.7B</a>, has inspired confidence in the ecosystem. An increasing number of acquisitions announced over the past month is also reinforcing the need for a more centralized marketplace for these opportunities.</p>\n\n\n\n<p>&ldquo;Iain and I started talking a lot more regularly a year ago, when he started Plugin Rank,&rdquo; Denning said. &ldquo;He was getting people asking him for acquisition opportunities, and with Ellipsis I was getting clients asking for help evaluating acquisitions and with sales. There was no go-to marketplace, so in March we started talking about working together on solving the problem.&rdquo;</p>\n\n\n\n<p>Sellers can list on FlipWP privately for free and buyers handle their own sales, with no exclusivity obligation. The site doesn&rsquo;t charge for listings and it doesn&rsquo;t take commission from any sales. The $299 membership for buyers opened today, which offers access to FlipWP&rsquo;s email list of acquisition opportunities. </p>\n\n\n\n<p>Listings include business data, such as ARR and monthly profit, the asking price, and commentary about the opportunity from FlipWP. Buyers can reach out directly to sellers with no middleman involved.</p>\n\n\n\n<p>In the past, finding a buyer for a WordPress company required having a wide network, knowing the right people, or posting on various marketplaces like Flippa and MicroAcquire.</p>\n\n\n\n<p>&ldquo;Every week I was hearing about another acquisition, getting an email from someone looking to buy a plugin business, or emails from developers asking the best way to sell,&rdquo; Poulson said. &ldquo;The need for a WordPress specific acquisition marketplace became more and more apparent.&rdquo;</p>\n\n\n\n<h2>The Acceleration of Acquisitions in the WordPress Ecosystem</h2>\n\n\n\n<p>There is a lot of buzz on Twitter lately, questioning whether an active acquisition market is a healthy development. Some have expressed concern about small, independent tools getting bought up by larger companies and worry that consolidation will lead to lack of competition. </p>\n\n\n\n<p>Eric Karkovack wrote in a <a href="https://speckyboy.com/wordpress-plugin-acquisitions/?mc_cid=fbd013f171&mc_eid=ad602f9b49">post</a> speculating on the future of plugin acquisitions, entertaining the possibility that &ldquo;a few big players simply set the rules for everyone else to follow:&rdquo;</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Frankly, it&rsquo;s becoming a lot harder for solo entrepreneurs or small development shops to manage a popular plugin. Supporting a large userbase while also focusing on the future could become overwhelming.</p><p>Thus, it&rsquo;s not surprising to see that some of these products are being sold off to larger firms. We saw something similar happen with internet providers back in the early 2000s. The more mature the market, the harder it became for a small company to carry out its mission. Pretty soon, they were just about all bought up by corporate interests.</p><p>While that may not fully reflect the case here, it seems to at least be trending in that direction&hellip;</p><p>It will take some time. But there might come a day when a typical business website runs plugins from perhaps only a few big development houses.</p></blockquote>\n\n\n\n<p>Not everyone shares this same bleak outlook on the potential effects of consolidation. During Matt Mullenweg&rsquo;s Q&amp;A at WordCamp Europe, Brian Krogsgard asked what these acquisitions mean for the health of the WordPress economy. Mullenweg sees it as a positive development that should spur more creation:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>It&rsquo;s a really exciting time because it feels so robust and healthy. The fact that these exits are happening then creates more incentives for something new to be created, either from the alumni of these companies or by people that know that they can get something to a certain point and sell it to one of these companies. It&rsquo;s actually not very different from Google and Yahoo and all of these companies that buy up lots of startups. Guess what, that created way more startups, some of which became Airbnb and Uber and challenged the tech giants. That&rsquo;s the beauty of how the ecosystem works.</p></blockquote>\n\n\n\n<p>Poulson and Denning are also optimistic that FlipWP will open up more opportunities for business owners to get connected and accelerate the process for all parties involved.</p>\n\n\n\n<p>&ldquo;The acquisition trend is indicative of WordPress maturing,&rdquo; Denning said. &ldquo;If WP Engine thinks the WordPress economy is <a href="https://wpengine.com/wordpress-economy/">worth $597 billion dollars</a> and the biggest public companies in WordPress are worth ~$20bn, we&rsquo;re about $577bn short. A lot of that number will be made up through the small businesses we see getting sold, and until now they&rsquo;ve not had a way of selling other than &lsquo;post it on Slack.&rsquo; If that study is right, then the one-most-weeks rate of acquisitions might actually be significantly too low, and those businesses are being undervalued, too. We can make it much easier for buyers to find quality WordPress listings, and we can make it much easier for sellers to get the best price.&rdquo;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Jun 2021 21:29: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: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:70:"WPTavern: #4 – Dan Maby on the Importance of the WordPress Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wptavern.com/?post_type=podcast&p=118113";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:183:"https://wptavern.com/podcast/4-dan-maby-on-the-importance-of-the-wordpress-community?utm_source=rss&utm_medium=rss&utm_campaign=4-dan-maby-on-the-importance-of-the-wordpress-community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:58344:"<h2>About this episode.</h2>\n\n\n\n<p>On the podcast today we have Dan Maby.</p>\n\n\n\n<p>Dan has been a user of WordPress for many years. As an agency owner he&rsquo;s used it to build client websites, but, as is so often the case, he came for the software and got caught up in the community.</p>\n\n\n\n<p>Starting out by attending some local WordPress meetups, he engaged with his fellow WordPressers and enjoying the events he was attending. Attendance turned into organising and over time Dan became the lead of four WordPress Meetups spread all over the UK.</p>\n\n\n\n<p>Meetups led to an interest in WordCamps, where he again stepped up to take on leadership roles at WordCamp London.</p>\n\n\n\n<p>In the podcast today we talk about the importance of the WordPress community, not just to him as an individual, but to the future of the project as a whole. After all, it&rsquo;s software created by people, and the health of that community will have a direct impact upon the contributions they make.</p>\n\n\n\n<p>We recorded this podcast at a time unlike any other. In person events have had to stop; the WordCamps and Meetups have all gone virtual. Perhaps there&rsquo;s light at the end of that tunnel, but it&rsquo;s a perfect time to look back and see how the community has adapted to these new circumstances.</p>\n\n\n\n<p>We get into whether hybrid WordPress events should be the new norm, what lessons the community can learn from the past year, and what Dan and his colleagues have done to stay connected and part of a vibrant community. They&rsquo;ve built a platform to enable events and plan on releasing it as a WordPress plugin soon.</p>\n\n\n\n<p>We also discuss an event which Dan has been a key player in organising &ndash; <a href="https://www.wordfest.live/">WordFest Live</a>, a 24-hour online event with a focus upon learning and positive mental health.&nbsp;</p>\n\n\n\n<p>It&rsquo;s a lovely episode with a member of the community who has been giving back for many, many years.</p>\n\n\n\n<h2>Useful links.</h2>\n\n\n\n<p><a href="https://www.wordfest.live/">WordFest Live</a></p>\n\n\n\n<p><a href="https://www.bigorangeheart.org/">Big Orange Heart</a></p>\n\n\n\n<p><a href="https://www.meetup.com/topics/wordpress/">WordPress Meetups</a></p>\n\n\n\n<p><a href="https://central.wordcamp.org/">WordCamp Central</a></p>\n\n\nTranscript<div><div class="chat-transcript"><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:00:00]</div> <div class="chat-text"><p>Welcome to the fourth edition of the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast for the WordPress community. Each month, we bring you someone who is part of that community to give you an insight into a topic or person who you might not be familiar with. If you enjoy the podcast, you can subscribe to future episodes by going to wptavern dot com forward slash feed forward slash podcast.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>If you&rsquo;ve got any feedback about the podcast, which could be a suggestion of a potential guest or a subject, then head over to wptavern dot com forward slash contact forward slash jukebox. There&rsquo;s a contact form there for you to complete, and we&rsquo;d certainly welcome your input. Thanks in advance. If you reach out.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>Okay, so on the podcast today, we have Dan Maby. Dan has been a user of WordPress for many years. As an agency owner, he&rsquo;s used it to build client websites, but as is often the case, he came for the software and got caught up in the community. Starting out by attending some local WordPress meetups, he engaged with his fellow WordPressers and enjoyed the events he was attending. Attendance turned into organizing, and over time, Dan became the lead for four WordPress meetups spread all over the UK. Meetups led to an interest in WordCamps, where he again stepped up to take on leadership roles at WordCamp London. In the podcast today, we talk about the importance of the WordPress community, not just to him as an individual, but to the future of the project as a whole. After all it&rsquo;s software created by people, and the health of that community will have a direct impact upon the contributions they make. We recorded this podcast at a time unlike any other. In-person events have had to stop the; WordCamps and meet-ups have all gone virtual. Perhaps there&rsquo;s a little light at the end of the tunnel, but it&rsquo;s a perfect time to look back and see how the community has adapted to these new circumstances.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>We get into whether hybrid WordPress events should be the new norm. What lessons the community can learn from the past year, and what Dan and his colleagues have done to stay connected and part of a vibrant community. They&rsquo;ve built a platform to enable events and plan on releasing it as a WordPress plugin soon.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>We also discuss an event which Dan has been a key player in organizing, WordFest Live. It&rsquo;s a 24 hour online event with a focus upon learning and positive mental health. It&rsquo;s a lovely episode with a member of the community who has been giving back for many, many years.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>If any of the points raised here, resonate with you, be sure to head over and find the post at wptavern dot com forward slash podcast, and leave a comment there.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>And so without further delay, I bring you Dan Maby.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>Am joined on the podcast today by Dan Maby. Hello, Dan.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:03:46]</div> <div class="chat-text"><p>Good. Speak to you.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:03:46]</div> <div class="chat-text"><p>Yeah, it&rsquo;s really nice to have you on the podcast today. Dan and I have a long history of chatting with each other, so this may end up being quite informal at times, but nevertheless, we&rsquo;re going to talk today about the WordPress community and events in general.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"> <div class="chat-text"><p>To paint some context into that, I wonder Dan, if you wouldn&rsquo;t mind spending just a couple of moments, introducing yourself and perhaps explain your history. Not just with WordPress, the software, but also your history with WordPress as a community.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:04:17]</div> <div class="chat-text"><p>Yeah, absolutely. I guess my journey started 15 years ago with WordPress. Funnily enough, we had obviously the 18th birthday quite recently of WordPress, and I was looking back at my history, trying to figure out what had been doing with it. And I realized that I&rsquo;d started with version 1.5, which at the time was really quite a major introduction. Lots of features in that 1.5 update that we still recognize today in the platform. And it&rsquo;s been, an interesting journey with WordPress and the community. One that I&rsquo;ve absolutely loved over that 15 year journey. But really the journey for me with the community started, I think it was around 2012. I was looking for a way to connect with people that were working with and were interested using WordPress. I was working in London at the time in the UK, looked at a meetup. I came across, there was a WordPress meetup that was being run by Keith Devon at the time, the WordPress London meetup. So I went, I headed over to the meetup, came from my day job at the time, which means I was suited and booted. Wandered into this, a room with a bunch of WordPress developers and users. And felt entirely out of place in that in that first meeting. I was the only person there in a suit. Everybody else was nice and casual, but the welcome that I received in that meetup was second to none. It was really an incredible experience, a first experience of the, the wider WordPress community.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"> <div class="chat-text"><p>And it was actually at that event that Keith had asked if anybody was looking to get involved and support in the delivery of the event and that having been there literally for my first time, stuck my hand up, and that&rsquo;s really where it all started. And very quickly moved into a situation where Keith decided to step away from the event to focus on other things, focus on his agency, et cetera. I&rsquo;ve been running the event ever since. And the WordPress London meetup has been a key aspect to everything that I&rsquo;ve been doing within the community. It&rsquo;s been a real pleasure to be able to be a custodian of a that event.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:06:16]</div> <div class="chat-text"><p>You have a lot more strings to your bow than just the WordPress London meetup. Do you want to tell us a little bit more about some of the other things that you&rsquo;re, well, were involved in? We&rsquo;ll get onto that a little bit later, about the way that things have had to cease, but tell us apart from the WordPress London meetup, tell us about the other things that you were doing on a monthly basis.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:06:37]</div> <div class="chat-text"><p>Sure, so, for me the community was really the important bit, the people within the community. I really grew to develop a, a passion for the people that we were connecting with. And from that point from the running of the WPLDN event, I realized that actually there were other areas that were lacking in meetups across the UK. There were plenty of people running, plenty of meetups, and I was really enjoying being part of that kind of organizers community, if you like a meetup organizers community. But as I said, I noticed that there were areas that were lacking events, even in my local area, as well as further a field, I actually got to the point where I was organizing and leading four meetups a month across the UK, which saw me traveling quite substantial miles on a monthly basis, just to enable these communities to grow and develop.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"> <div class="chat-text"><p>And it was a real pleasure to be able to work with local communities. I always encouraged community members within the local area to come on board as co-hosts and enable them to take the lead and to sow the seed and then move on and help that community thrive. And it was going fantastically well. You know we had, as I say, we have four meetups running across the UK, and then suddenly, obviously we&rsquo;re thrown into the situation where we couldn&rsquo;t physically come together in person.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:07:56]</div> <div class="chat-text"><p>Before we move on to that, perhaps we could paint a little picture about the importance of WordPress in your life, because it strikes me that many people, they may use WordPress as a piece of software. And that&rsquo;s the end of it. They have really no understanding that there is a community which can support you in your WordPress knowledge, but also it can be much more than that. And I think it&rsquo;s fair to say that in your case, many of the people that you&rsquo;ve met through WordPress have become actual friends who you actually socialize with. Enjoy their company and stray into non WordPress things as well. So I&rsquo;m just wondering if you could tell us how it has helped you, but perhaps get into the stuff that&rsquo;s not to do with WordPress. Have you met people that you&rsquo;ve really jelled with and found camaraderie with.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:08:41]</div> <div class="chat-text"><p>I think this is the the beauty of the WordPress community. It&rsquo;s so much more than just the technology. I found it to be quite a unique community as well, in that the way people are open, the way people will communicate and discuss and talk about topics, which, by all rights where we attended an event together, we&rsquo;re essentially often competing with one another. I run an agency which focuses on design and development services, and I will go and speak with many other people that also run agencies. And essentially we are competitors, but that level of competition doesn&rsquo;t really surface too much in the WordPress community. It&rsquo;s predominantly a community that&rsquo;s very supportive and people are very open to discussing issues. Myself, I was seeking out connection, I wanted to be around like-minded individuals because I was in a situation where I was very isolated. I was looking for people to connect with that had an understanding of what I was experiencing. And that&rsquo;s really what the community has been about for me. It has been about this idea of having similar experiences, having, understanding of the challenges that we can face if we&rsquo;re working alone. And my company has run with distributed team members, so I don&rsquo;t have a central office with a team that all works together. We work in our home offices. You miss out on that ability to be able to have those conversations that you would have, potentially in-person. That for me was where I was seeking out the community, and as I did that, I realized that this community really was very open to discussing many issues and very open to sharing experiences and knowledge, which was unique for me at the time. And as you say, that&rsquo;s then led on to building of relationships and those relationships have gone further afield outside your outside of specifically WordPress related. Very happily, I&rsquo;ve got some wonderful friends across the community now, and they are friends and the people that I will hopefully have the pleasure of knowing for the rest of my life. Nathan, I count you in amongst that I can remember a conversation you and I had in a car park post a meetup many years ago and, it&rsquo;s been wonderful to watch the journey that you as an individual have gone on through your experiences of WordPress and podcasting, et cetera, and the many branches and tendrils that we have within the community. It&rsquo;s a very rich experience. I would say being part of the WordPress community.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:11:04]</div> <div class="chat-text"><p>Yeah, I would completely agree. And for those people who perhaps listening to this podcast, obviously this audio will go on in perpetuity, it may be that they&rsquo;re listening to this and the world has become more normal. Shall we say? Perhaps we&rsquo;re allowed to meet up in person again. If that were the case, what would be your best advice for digging into that community? What would your best search be? What would be the best way to go about finding where your local events are taking place?</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:11:32]</div> <div class="chat-text"><p>First off is look for meetups. There are thousands of meetups across the globe that are run by local communities, and I really would encourage anybody if you haven&rsquo;t previously. Take a look head over to you know, there are various sites, whether it&rsquo;s meetup dot com, Eventbrite, et cetera, all those kinds of events websites. Do a search for your local area for WordPress meetup event. Sign yourself up and head over. My personal experience and something that I&rsquo;ve spoken about many times historically is simply getting involved in these events. We have this wonderful ecosystem of WordCamps across the WordPress space. And these WordCamps are, you&rsquo;re basically taking a meetup onto a grander scale, again, encouraging local communities to try and run those WordCamps and larger events, but that can sometimes feel quite daunting, just simply turning up to an event. So if you can get yourself embedded in some way, and volunteering is by far and away, the simplest and best way to do that. Every single one of these meetups and WordCamps are run by teams of volunteers. So signing up as a volunteer, simply putting your hand up and saying, yes, I&rsquo;ll get involved in some way. It gives you a purpose within the event. So you&rsquo;re not simply having to be there and trying to figure out where you fit within it. You&rsquo;re there and you have a role. And this was certainly my experience of getting into the WordCamps space. I&rsquo;ve volunteered. I can remember experience at WordCamp Europe, or I was doing some meeting and greeting as people were arriving, and it just opened up so many interesting and wonderful conversations with people that I still have very interesting, wonderful conversations with today. And it&rsquo;s just that embedding yourself in it and enabling yourself to be part of that community. First step I&rsquo;d say, check meetup, look for an event. Sign yourself up, head over there. And if there&rsquo;s any way that you can get involved, do. Most meetup organizers are so grateful for anybody putting their hand up and say, yeah, look, I&rsquo;ll get involved or stepping forward and saying look, do you need any help with this at all? And that help can vary in so many ways. As a meetup organizer, there&rsquo;s an awful lot often goes on behind the scenes that maybe attendees aren&rsquo;t always aware of that really go into delivering these events.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:13:45]</div> <div class="chat-text"><p>What is the difference between a meetup and a WordCamp? Probably, if you&rsquo;ve attended, either of those you&rsquo;ll know the difference, but if you&rsquo;re new to this whole WordPress community thing, it might be good to paint a bit of clear blue sky between those two different things.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:14:01]</div> <div class="chat-text"><p>So if I use London as an example. Our WordPress London meetup, when we were in person delivering these events, we were seeing the, of an average of a hundred people in attendance every month. So this would run every once a month in our local environment. So the focus for both WordCamps and meetups really are about encouraging local organizers to run them. So our meetup, we feature between two and three speakers on a night. It&rsquo;s usually around two, two and a half hours long. And then post that within, have a bit of a social gathering. Where we continue doing a bit of networking, et cetera. The meetup is a really a trimmed down version, should we say? Or that&rsquo;s probably negative, a negative way of putting it to be honest. The WordCamp is an enlarged version of meetup. Probably the best way of putting it and WordCamps are essentially that. We&rsquo;re taking the concept of a meetup, but on a much, much grander scale. And they don&rsquo;t have to be enormous. I&rsquo;ve attended some you know, a hundred attendee WordCamps and they&rsquo;ve been absolutely spectacular, really personal. And I really enjoy the kind of smaller hundred, hundred and fifty attendee WordCamps, but equally we also have some much, much larger ones. So again, if I look at WordCamp London, the last event we ran we had around 650, I believe was 650 attendees at that event. If we then look at the regional WordCamps. So the likes of WordCamp US, WordCamp Europe or WordCamp Asia. Yeah, WordCamp Europe. I believe there&rsquo;s three and a half thousand attendees at the last event, the last in-person event. So they&rsquo;re often spread across multiple days as well, but not always often there&rsquo;s a, a single day WordCamp as well, but the one telling difference between a WordCamp and a meetup is the WordCamps often have what we call a contributor day associated with them as well, which is a day focused entirely on contributing to WordPress in some way, shape or form. And there are so many ways to contribute. We&rsquo;re not just simply talking about writing code and contributing in that way. There&rsquo;s documentation, there&rsquo;s marketing, there&rsquo;s the multi-lingual there&rsquo;s many ways to get involved. So I really, again, would encourage anybody that&rsquo;s thinking about attending a WordCamp, once we are back to a situation where we are safe to be able to return to in-person events. And obviously some of the virtual events I really would encourage joining the, contributor day in any way that you can.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:16:15]</div> <div class="chat-text"><p>So with all of these events going on, obviously we&rsquo;ve got a thriving piece of software, which is turning out to be widely used over 40% of the web. We have the statistic now using WordPress. So the software is one side, but obviously we&rsquo;ve also, as you&rsquo;ve just painted a picture that we&rsquo;ve got this thriving community as well. An awful lot of the project perhaps was going on, at these community events, a lot of things were being organized, so contributor days, possibly different teams meeting up at various times at these events. And then sometime last year, the world paused and is still in a state of pause. I&rsquo;m wondering if you have any thoughts on whether the project as a whole has been stifled. I know that we&rsquo;ve gone online and we&rsquo;ll come onto that in a moment, but I&rsquo;m just wondering if you&rsquo;ve got any thoughts about the impact that the world pausing and not being able to meet up in person. If the project itself has been stymied by that.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:17:14]</div> <div class="chat-text"><p>I think this is a really interesting discussion. I can sit on both sides of the fence here. I think there is definitely an element of fatigue within the community at this stage. And I think that fatigue is being born out of the fact that potentially we are not having those in-person connections, the wonderful conversations that can be born out of the hallway track, you know it&rsquo;s spectacular, what can happen, and by hallway track, you&rsquo;re simply wandering around the event itself and not necessarily being in a session, but there&rsquo;s, the people are mingling around and the conversations that can be born out of those chance meetings, really are spectacular. Many times I&rsquo;ve run into individuals in the hallway, or we&rsquo;ve just started the conversation and then somebody else has jumped in, somebody else has jumped in and before we know it, there&rsquo;s, there&rsquo;s a really interesting round table conversation going on about the future of the project. Because as an open-source project, we all have the potential to influence them the potential to participate in the project in some way, shape or form. I think in this virtual environment that we&rsquo;re currently in, on a personal level, I believe that we&rsquo;ve lost some of that. We&rsquo;ve lost that ability in many ways. And it&rsquo;s created this fatigue where we&rsquo;re not necessarily having the opportunity to have those discussions and those new ideas, those new thoughts, or those alternative ways of looking at a problem. I think the project has possibly suffered for that, in some respects, I think is partly why WordPress as the software has been so successful is because of WordPress the community has had that really strong in-person connection and that really strong coming together as a community. Having said that equally, there are many benefits to the concept of the virtual environment that we&rsquo;re in. But yes. I certainly think there are some challenges that we have come up against and we&rsquo;ve tried to work towards resolving to some degree as a community in this virtual environment.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:19:07]</div> <div class="chat-text"><p>We&rsquo;re in a strange dichotomy in that we were probably better prepared than almost any industry to move everything online at the drop of a hat, because the WordPress community is online. We understand how to put websites together and turn those websites into virtual events and all of that kind of stuff. Conversely, and perhaps somewhat unexpectedly. We were also a community, that needed to be offline in order to push the project forward. And so in some sense, we were not prepared for that. Two sides of one coin, very well prepared from the technological point of view. But perhaps we didn&rsquo;t really understand that these in-person events, the interactions, the little coincidental meetings that might&rsquo;ve happened, that pushed things forward. The fact that the contributor days, they were a great way of pushing the project forward. All of these little things that required us to be in-person well, they just evaporated and we weren&rsquo;t really prepared for that and that&rsquo;s kinda my take on it. It feels like from the tech point of view, everything&rsquo;s a-okay. We can manage that side really well, but the unexpected consequences from the community going away have become slightly more obvious. And I feel it&rsquo;s not really in any way, catastrophic, it&rsquo;s just little paper cuts. Things haven&rsquo;t perhaps worked as fluidly, perhaps interactions haven&rsquo;t been made, perhaps people have become fatigued, logging onto their computer and so on. And of course, there&rsquo;s the fact that there&rsquo;s a great deal of excitement around turning up to one of these events and whether that&rsquo;s a meetup and you just show up for the evening or you go somewhere further afield. You might need to get in the car or get on a train or get on a plane and you may have booked a hotel and your almost seeing it as a little bit of a vacation, something a little bit outside of the normal experience, all of that side has gone. And so there&rsquo;s less be excited about. And perhaps as you described it fatigue, I&rsquo;m describing it more as a lack of excitement, perhaps that has had a bit of an impact.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:21:10]</div> <div class="chat-text"><p>I think you&rsquo;re absolutely right. There&rsquo;s an excitement when you&rsquo;re coming together in personnel, there&rsquo;s excitement. You don&rsquo;t always know what to expect. You don&rsquo;t always know what&rsquo;s going to come in those conversations. You may have a good idea, but the ability to come together in person and really thrive off that energy of one another, it really can be quite special, but equally there are many people that don&rsquo;t thrive off of that there are many people that really struggle with the idea of being in large groups of people, there&rsquo;s absolutely pros and cons to all of this. And it&rsquo;s something that we were in our events, in the in-person events, we were trying to be aware of, be mindful of that experience for people. Some people, as I say will thrive off that environment of being around lots of people, but those that need their own space sometimes. The idea of delivering quiet rooms at in-person events is really important because some people do just need that time away from the crowd to be able to re-energize themselves, by being by themselves. This idea of enabling all walks of life, all the variations of people that build up our community to be able to participate. And I think this is really where we&rsquo;ve got a huge positive in the virtual environment at the moment we&rsquo;ve brought down so many barriers. For a far greater, far more diverse mix of individuals, whether we&rsquo;re talking about speakers or attendees, we&rsquo;ve got some wonderful opportunities right now in the virtual environment. We&rsquo;re not having to consider visas. We&rsquo;re not having to consider travel expenses. The limitation that we&rsquo;re running on right now in terms of attendance of an event is the bandwidth to be able to connect to that event. We were looking at the positive side of this. There are some really good things I think we need to be very mindful of as we move forward. As we move into, as we start to move into a situation where we, if we&rsquo;re in a safe environment, to be able to return to the in-person events, we also need to be mindful of how do we continue to encourage that very open and very inclusive model that the virtual environment has created.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:23:16]</div> <div class="chat-text"><p>Do you see in the future, and we&rsquo;ll talk more in a moment about specifically what it is that you and your events have done to move online over the last year or so, but just for now, do you see in the future then a model where, let&rsquo;s say that we all go back and the world returns to how it was in 2018. Everybody&rsquo;s allowed to get on planes and trains and everybody can move freely once more. Do you think that we have reached a point where hybrid events and by that I mean, many people will come and be present in the room, but also perhaps we need to provide the internet access so the people from further afield who don&rsquo;t wish to attend, or perhaps they&rsquo;re literally on the other side of the world and they only want to see two or three of the variety of sessions that are on offer that week. It&rsquo;s really not worth them getting on a plane for that, but they could log in and watch them online. So do you feel that there&rsquo;s a hybrid or will we just consign the online events to the realms of history?</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:24:12]</div> <div class="chat-text"><p>So I&rsquo;m very hopeful that as a community, we will adopt the hybrid model. However, having said that, I also appreciate that we need to also figure out what this hybrid model looks like. As a meetup organizer, again, the WordPress London meets up. We were taking quite a considerable amounts of kit into the event to deliver the events. And by kit I&rsquo;m talking about cameras, microphones, tripods, sound equipment, all sorts of stuff, which isn&rsquo;t that common in the meetup space. And as a meet-up organizer, you don&rsquo;t need to be thinking about, or how do I get low cameras, et cetera. But what it meant for us is we were pre pandemic we were already in an environment where we were live streaming the sessions. We were accepting questions coming in from the virtual audience that were consuming the content live whilst the in-person community were also consuming that content. That put us in a very strong model as we move forward, which I can get into in a moment. But the issue that I see is, are we going to try and force the experience where we&rsquo;ve got the in-person and the virtual, combined together at the same time, are we actually going to create a situation where we create the worst of both worlds? So the in-person deteriorates because there&rsquo;s a need for more equipment, there&rsquo;s a need for more organizing and there&rsquo;s need for just a very different experience where you&rsquo;ve got a lot more things needing to happen from an organizer&rsquo;s perspective. And then have you then got the virtual side, is their experience going to deteriorate because the organizers are having to focus on the in person. It&rsquo;s an awful lot to deliver, as an organizer: an event. But to then take that event and say now I need to do at the same time, a hybrid of in-person and live, particularly on the meetup side, I think it&rsquo;s something we&rsquo;re going to have to be very careful of and figure out how do we do that? Are we better to have, I don&rsquo;t know, for example, an in-person event and a virtual event, twice a month. Again, I&rsquo;m not advocating for this for every single meetup because I appreciate every meetup is run by volunteers. It&rsquo;s about the capacity for those organizers. I think when we start to look at WordCamps, it gets a little more interesting because obviously WordCamps do have a slightly larger team often, and there is often some funding supported through sponsorship, et cetera, to enable that. But again, we&rsquo;ve got to look at how do we make sure that the experience is optimal for both the in-person and the virtual. And I&rsquo;m not sure I have the, certainly I don&rsquo;t have the answers to that at this stage, but it&rsquo;s certainly something we&rsquo;ve been having a lot of discussion around internally. And the platform that we&rsquo;ve developed for our virtual events at the moment is something that we&rsquo;re looking to roll into our hybrid model. But again, that we don&rsquo;t have the answers at this stage.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:26:57]</div> <div class="chat-text"><p>I&rsquo;m also conscious that perhaps if everything becomes available online, it may persuade people who are almost going to attend live to not attend live. It may dwindle the audience that turn up to the live event, if you know what I mean, which would be a kind of an unexpected consequence, but those people who were flip-flopping and maybe I&rsquo;ll go, maybe I won&rsquo;t, oh, I&rsquo;ll just watch it on the screen, which is fine. But obviously you don&rsquo;t want to get to the point where the in-person event is attended by just a couple of people, because everybody else is just tuning in online because the sort of sense and the purpose of that event and the camaraderie, all the good stuff that you want to happen, in-person disappears.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:27:38]</div> <div class="chat-text"><p>So this was something that we discussed, a number of times pre pandemic, when we made the decision to start live streaming, the WPLDN events, and we have that exact concern and it&rsquo;s a genuine concern. Are you going to deteriorate the experience by somebody has the option to just simply watch it online? It never happened. Our numbers, stayed consistent and we saw a numbers of in-person stay consistent and we saw our numbers online, grow and grow. And that really demonstrates to us that people want that in person connection, as you just said, there&rsquo;s so much more to the event than simply consuming the the section that&rsquo;s being delivered. So it is those conversations are happening in hallway tracks. It&rsquo;s the, all the other elements to the event that you often can&rsquo;t gain from a virtual environment.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:28:24]</div> <div class="chat-text"><p>Okay. So let&rsquo;s move the conversation a little bit. It was staying on more or less the exact same topic, but I&rsquo;m curious to know what it is technically that you have done since March last year in the UK, March was the moment where everything ground to a halt, and we were unable to see each other. So I just wondered if you could run us through what challenges you faced, how you&rsquo;ve overcome them. And I know that you spent a lot of time trying to build a platform and shape a platform, to make this work in your situation. Perhaps explaining that might encourage other people who would like to take their events online, to reach out to you and see if you can lend them a hand.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:29:00]</div> <div class="chat-text"><p>Sure. Absolutely. Just to give a bit of context before I get into this, the WPLDN events, along with several other events that we deliver, now come under the umbrella of Big Orange Heart, which is a registered nonprofit with a mission to support, promote positive mental health within remote working communities. So a big focus for us is about continuing ways to help reduce social isolation and the delivery of events do that. Now the reason I&rsquo;m saying that is because there&rsquo;s a team of volunteers within Big Orange Heart, that have donated time into helping us deliver them. So what I wouldn&rsquo;t want to portray is yeah I&rsquo;m sitting here on my own and it built this platform that enabled the community to continue to do its thing. It&rsquo;s taken a small village of people to continue to do this. And I appreciate not every meetup has that ability to be able to tap into that. But what we did, we actually back, as I said, previously, we were already live streaming. So we had a pretty good idea of, the, kind of the technical aspects of live streaming content and very fortunate, we&rsquo;ve got a fantastic team on WPLDN, specifically Leo Mindel, Paul Smart and Diane Wallace and myself come together. Leo comes in with some fantastic technical knowledge to help support the live streaming side of it. And we took the decision back in February, so prior to the government making any announcement here in the UK, we took the decision that was going to be our last event until we had more information in relation to the pandemic. Little did we know that would obviously continue on as it is right now, but we took what we were doing in terms of our live streaming; so we did our final in-person event in February. We jumped straight into trying to do a virtual event in our next event in March. So we delivered one event a month through WPLDN. The first thing we did in March was jumped straight into Zoom and said, yep, let&rsquo;s get everybody in. Within minutes, we recognize that Zoom was entirely the wrong platform for us to deliver an event on. It&rsquo;s a great platform, for the purpose of meetings one-to-one or one to many meetings, but it really isn&rsquo;t a good platform for any kind of event. Because if in an event you want the ability for people to freely move around. And we&rsquo;ve seen many events that have used Zoom, used multiple Zoom rooms to enable the attendees to jump into different conversations. The problem with that is you don&rsquo;t know what you&rsquo;re jumping into. We often refer to it as Zoom roulette because you&rsquo;ll be jumping into a Zoom call and you don&rsquo;t know who&rsquo;s in that Zoom call. You don&rsquo;t know what you&rsquo;re jumping into, and it adds a huge cognitive load to the attendees of an event, because not only are they having to figure out where the different Zoom links are, they&rsquo;re also then having to figure out once they&rsquo;ve got in who it is that they&rsquo;re communicating with in that conversation, which it just simply didn&rsquo;t work for us. So we very quickly started to work on a solution that would enable us to have that ability to have freedom of movement within a virtual environment. Now, this led us on to looking, we&rsquo;re huge open-source advocates. And we wanted to continue to deliver, we wanted to build something that would tie in and fit with that ethos of the open source projects that we support. So we quickly discovered Jitsi as source video conferencing solution. Ran into many challenges along the way, in terms of building out the platform. But what we ultimately ended up with was a platform that enabled us to use our existing registration process. So all of our attendees are on meetup. So we wanted for people to be able to obviously log in with their meetup credentials. So register for an event on meetup, if they&rsquo;ve registered, be able to then access the event online. So we built a WordPress site, built a custom app that wrapped around a Jitsi instance, which then enabled us to have this concept of tables within the platform. So attendees would register for the event, jump in. We would be able to stream content into that platform as well as then have this idea of tables where people could freely move around and see exactly who&rsquo;s on what table before they were jumping in. We delivered that I believe that was around May time of that year. So two months following the decision to go to virtual and we continue to iterate and evolve that platform from that point on, which has been, it&rsquo;s been a phenomenal experience, the development of this solution. I just wanted to give a shout out to Louis Cowles, who has been doing an incredible job. Taking what I had originally put together, which was this app wrapped around Jitsi and he has turned it into something far more spectacular, which we are now, almost at the stage of being able to deliver as a WordPress plugin. So if anybody has attended any of the Big Orange Heart events or any of the events, the Big Orange Heart supports, have experienced the platform, which includes WordFest. The whole platform that we have developed there will soon be available as a WordPress plugin as well, which we&rsquo;re really excited about.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:33:56]</div> <div class="chat-text"><p>I have to say from my part, it is now feeling incredibly mature and the fact that it will soon be a WordPress plugin is remarkable. Will that be something that anybody can access and therefore use at their own meetups? Presumably there&rsquo;s some sort of burden of setting up things outside of WordPress. Maybe there&rsquo;s other containers with the Jitsi software that needs to be done, or does it all get rolled into just the plugin and you&rsquo;re good to go.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:34:22]</div> <div class="chat-text"><p>So there&rsquo;s still work that we&rsquo;re working through, how to enable that within the community. Really, what we&rsquo;re trying to do here is build something that is enabling communities to have the experience that we&rsquo;ve had with WPLDN, and also, we&rsquo;re not just simply talking in this current particular space where we&rsquo;ve got the, just virtual again, referring back to the hybrid model. As a platform would work particularly well for the hybrid model, but yes, there are definitely additional technical elements to it, which we will obviously be looking at how we can mitigate that technical challenge that comes with it. There are hosted versions of Jitsi, which you can simply plug into it as it is right now. So again, we&rsquo;ll be able to share more information as we move forward with that. We&rsquo;re really, it&rsquo;s about enabling the community to be able to continue to have that very broad reach. Even as we, as we move back into the in-person.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:35:11]</div> <div class="chat-text"><p>You being you, you weren&rsquo;t content to rest on your laurels and carry on just doing the WPLDN event. You&rsquo;ve obviously got this platform and you decided at some point last year, that you wanted to manage and organize an event which spanned the entire globe. And so WordFest was born. I don&rsquo;t know if WordFest was born, basically out of the fact the world was on pause or whether you&rsquo;d have plans for this prior to that. But perhaps you could spend a few minutes just outlining what WordFest is and by good coincidence, there is actually a WordFest, if you&rsquo;re listening to this podcast episode, soon after it was released, there is actually a WordFest event coming up really soon. So perhaps tell us why you started it and then get onto what&rsquo;s going on in the next few weeks.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:35:59]</div> <div class="chat-text"><p>Sure. So as a charity, we always intended to have some form of larger in-person event. Events have been something that&rsquo;s had a real passion for a very long time. The ethos of bringing people together, helping reduce social isolation of lone workers is something that really fits well with everything that we&rsquo;re doing in terms of Big Orange Heart. So we wanted to enable people to come together. That had always been on the cards from the very early stages of Big Orange Heart. Of course, when we got thrown into this situation with the pandemic, as I say, we moved into the virtual environment for our monthly events, that platform that I&rsquo;ve been discussing, we actually opened up to other communities. So we&rsquo;ve enabled other communities to be able to run their events through our platform, without any charge to them. We just simply wants to be able to create a solution for those communities to continue to come together when they couldn&rsquo;t deliver them in person. What that actually meant was that we, in the first 12 months that we were delivering events through our live dot Big Orange Heart dot org site, we&rsquo;d had over 12,000 attendees come through that platform, which has meant that we&rsquo;d obviously had a huge amount of feedback and we&rsquo;d been able to iterate very quickly across that solution to get to a point where we actually decided that we want to deliver a larger scale event. It&rsquo;s always been on the cards. Why not do that as a virtual conference or virtual festival? That&rsquo;s really where the concept of WordFest was born. And I want to, again, when we give a huge shout out to Brian Richards, particularly of WordSesh. WordSesh has been around, you know, as a virtual WordPress focused virtual event for many years, I can remember way back in the early days of the first WordSesh, the first few WordSesh&rsquo;s, which were 24 hour events and had a lot of fun attending those. And I remember attending my first one and actually attending for the full 24 hours. So this wasn&rsquo;t something that was new in our space. We were very aware that there was a desire for it, but we wanted to wrap together the two elements of what we do. Our hearts really are in WordPress, but our focus is really around wellbeing and mental health, positive mental health. So this concept of WordFest was about bringing those elements together. So if you attend WordFest, you will find content that focuses on both WordPress and our individual wellbeing as remote workers. It really was about this concept of a global celebration of our community. We talked about different ways of delivering it. We talked about do we do over multiple days because we appreciate time zones, how do we, how do we factor in a way of enabling anybody that wants to attend to be able to attend? But we didn&rsquo;t want to just say here&rsquo;s a set time on this day, here&rsquo;s six hours that would deliver it or, over a period of days, we&rsquo;ll do, it was a real challenge. So we, we kept coming back to this 24 hour concept because it would end up, if somebody wants to attend over that one day, there was some point in the day that hopefully they would be able to join us. And it has mushroomed. It&rsquo;s grown and grown. We set out to deliver the first one back in January, this year, 2021, we set a target of 2000 attendees to the event we had just over two and a half thousand attend. So it was, we completely smashed all our expectations in terms of people attending the event. But also we completely smashed our expectations in terms of the number of sessions that we were delivering. We initially set out a wanting to deliver 24 sessions over the 24 hours. That turned into 36 sessions actually ended up being 48 sessions through the first event. I&rsquo;m really happy. I&rsquo;m not sure it&rsquo;s the right word, but I&rsquo;m really happy to say that this time around we&rsquo;ve actually got 66 sessions that are going to be delivered in the 24 hours. It&rsquo;s been a phenomenal experience, delivering this as again, as a wonderful team of volunteers, sitting behind this people like Michelle, Cate, Hauwa, Paul, just wonderful people that are really enabling us to be able to continue to grow this event into a much larger scale event than it ever was initially. So the next WordFest live is taking place on the 23rd of July. So we&rsquo;ll be featuring 66 sessions over a 24 hour period. And it is, I think one of the most wonderful things I took away from the last WordFest was, as an organizer, having organized many in-person events, there&rsquo;s always a connection with your co-organizers. Certainly if you&rsquo;re running a larger event, such as a WordCamp, for example, you build up this rapport and you build up this relationship that on the day of delivering the event often it&rsquo;s, it&rsquo;s, it&rsquo;s tiring. There are, yeah, there are moments of challenges, but there are just wonderful moments as well. But you experience all of those things together as a team. What I took away from WordFest live, which was a genuine surprise to me was we managed to create that same experience. We managed to create that same shared experience as we were delivering the event. I&rsquo;ll never forget sitting here, I think I was in about hour 36 of because I&rsquo;d been up some time before the event and I was sitting there and just the silence that was actually happening as a bunch of organizers, we all knew how, what we were experiencing in that moment. And it was just a real special time. We use various tools to deliver it. And one of the key secret ingredients for us as organizers was Discord. So having an open audio Discord channel for us to be able to just simply be able to speak to one another as we needed in that moment, it worked incredibly well for us.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:41:40]</div> <div class="chat-text"><p>So the event, just tell us one last time. What are the dates and where do we go if we wish to sign up and perhaps importantly, tell us how much does it cost?</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:41:53]</div> <div class="chat-text"><p>I&rsquo;m laughing because it costs you absolutely nothing. WordFest Live is a free event, the next event is taking place on the 23rd of July where we&rsquo;ll be starting at midnight UTC. So time zones are always fun in an event like this. So we base it around UTC. So midnight UTC on the 23rd of July running for 24 hours. So that&rsquo;s the Friday 23rd. You can join us at any point over that 24 hour period, we will be running across six continents. Our time zone starts off in the Australia, Australian time zones. We&rsquo;ll move on to Asia, Africa, Europe, south America, and ending up in North America. And then we&rsquo;ve got Antarctica. You can chill out in our community tent all day long. So over that period, we would love to see you join us. As I say, registration is entirely free. There is an optional $10 donation that you can make when registering, all funds go directly into Big Orange Heart, which was the say is a registered nonprofit. There is also an option there to sign up as a micro sponsor. Should you choose to. Micro sponsorship is charged at $250. And for that, we will obviously get some exposure of your company. And it&rsquo;s really a more a reflection of what it actually costs for us to put this together, in terms of the attendees tickets.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:43:13]</div> <div class="chat-text"><p>This podcast episode, you could probably sum it up with one word and that word would probably be community. If I was to show up to WordFest live and I had ambitions to socialize with other people. That kind of thing is possible? It&rsquo;s not just about show up to the event, watch the speakers and then wait for the next speaker to start. You&rsquo;ve provided opportunities to socialize. So maybe as a final thing, just explain how that works. What&rsquo;s the provision for meeting up with other people and breaking out into different groups and so on.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:43:42]</div> <div class="chat-text"><p>So this was as equally important as finding fantastic speakers. We also needed to make sure that the ability for people to be able to connect, the community, to be able to come together has been a focus for us. So this is where the custom solution that we&rsquo;ve been developing comes into play. So if you are attending WordFest, you can obviously consume, we&rsquo;ve got two tracks running over the 24 hour period. So at any point you have a choice of at least two sessions to choose from. I say at least because there&rsquo;s also some evergreen content that will be available for you to consume through the events as well. And then you can head over to our community tent which we are nicknaming Antarctica this time round, where you can connect with the sponsors. So you will see all the sponsors tables, you can jump in and have conversations, discuss with them for whatever reason you need to to connect with the sponsors, highly encourage you to do that. But in the same space, you can also spin up your own community table. And this is, we try to liken it to a sponsors hall at an in-person event. You might wander into the sponsors hall. You&rsquo;ll have conversations with the sponsors, but equally you might have conversations with your peers, friends, colleagues, in and around the community. So we&rsquo;ve really tried to, as best we can in the virtual environment, replicates that hallway track experience where you&rsquo;re not bound to specific calls, you&rsquo;re not bound to specific tables. You have freedom of movement within that platform to connect with those that you want to connect with. Equally, you also have your own profile within the platform and your own profile then has your own meeting room. So should you want to break out and have you a slightly more private conversation discussion away from the community tent, then again, you have that facility. So it&rsquo;s really about trying to enable people to come together and have the conversations that are so important.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:45:29]</div> <div class="chat-text"><p>Thank you so much, Dan, for putting an event like this on, I know that as you&rsquo;ve said, it&rsquo;s not just you, there&rsquo;s a great large community of people in the background as well. So thank you to them equally and during the last 18 months or so, thanks for being there and making sure that the communities can keep meeting and you&rsquo;ve endeavored to to keep all of that going. And I fear that unless it was for people like you who&rsquo;ve really gone the extra mile, perhaps things wouldn&rsquo;t be quite so bright going forward. From the bottom of my heart. Thank you very much, Dan, for coming on the podcast and for everything that you do.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-2"><div class="chat-author chat-author-danmaby vcard"><cite class="fn">Dan Maby</cite> [00:46:01]</div> <div class="chat-text"><p>Oh I&rsquo;m deeply appreciate. I thank you. Thank you very much, and likewise. Thank you for all that you do across the community. I appreciate it. I&rsquo;ll see, you spent a lot of time chatting with people like me sharing some wonderful stories.</p>\n</div></div><div class="chat-stanza chat-row chat-speaker-1"><div class="chat-author chat-author-nathanwrigley vcard"><cite class="fn">Nathan Wrigley</cite> [00:46:11]</div> <div class="chat-text"><p>Thank you so much.</p>\n</div></div></div></div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 16 Jun 2021 14:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nathan Wrigley";s: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:42:"HeroPress: Changing The World, Changing Me";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=3902";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:134:"https://heropress.com/essays/changing-the-world-changing-me/#utm_source=rss&utm_medium=rss&utm_campaign=changing-the-world-changing-me";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8049:"<img width="1024" height="512" src="https://heropress.com/wp-content/uploads/2021/06/061421-min.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: WordPress has fundamentally changed who I am. I don’t say that lightly." /><p>WordPress was created when I was 10 years old. I try to imagine myself at 10 and the only images I can conjure up are ones of anxiety. My world both felt so small and was so small yet what I felt seemed so big. I don’t look back fondly on those years. I was a ball of competitive anxiety who was just coming out of being made fun of for years for my speech impediments and finally starting to figure out who I might be. My 10 year old self didn’t like change and didn’t know how to cope. My 10 year old self had no concept of what was being created during these strange years and I’m filled with gratitude thinking about those who were paving the way before I could even conceptualize what a website was.</p>\n<p>WordPress has fundamentally changed who I am. I don’t say that lightly. I have an urge to jump into a monologue of, “How do I love thee? Let me count the ways” when I think about WordPress.</p>\n<h3>Finding My Creativity</h3>\n<p>The most profound change started in awakening a sense of creativity and belief in myself. I work hard at things but my earlier black and white point of view often limited any amount of creativity I might have had. I’ll never forget in college working for <a href="http://web.unc.edu/">web.unc.edu</a>, UNC Chapel Hill’s WordPress multisite installation, and discovering that I could create as many sites as I wanted. The ease of use and the unlimited possibilities led me to create site after site. This still happens now with <a href="https://letslifechat.com/">https://letslifechat.com/</a> born this year out of my desire to share my love of questions and deeply connecting with others, especially during a year of profound disconnection. Along the way at UNC, I got to work with brilliant and kind coworkers who believed in me to the point of encouraging me to apply to Automattic after I had to graduate a year early.</p>\n<blockquote><p>Knowing they believed in me helped me apply and the case of redbull they sent me for my trial helped me get the job!</p></blockquote>\n<p>I never saw myself as creative since creativity was defined for so many years as being art focused (poetry, painting, etc) and I have absolutely no artistic abilities. Being able to make an idea come to life online has changed how I view myself – I now see myself as creative and capable. This shift in how I view myself led me to create initiatives like <a href="https://accelerate.lgbt/">accelerate.lgbt</a> and <a href="https://mentoreverywhere.com/">Mentor Everywhere</a> at Automattic in my free time. I never realized that my handwriting and drawing abilities could be terrible yet, at the same time, my creativity could be powerful. The results of my creative actions have solidified a sense of belief in myself that is deeply profound. It’s something I fall back on during tough days of self doubt and tough problems.</p>\n<h3>Finding The World</h3>\n<p>Because of WordPress’ global and distributed nature, I have been afforded the opportunity to travel to far away lands and to be there for meaningful moments with dear loved ones. Being a “nomad” is something I never thought I’d be. Being connected to people all over the world felt unfathomable and still feels like more of a dream than a reality. It’s challenged every aspect of who I am and I am better for it. Combined with the ability to see the world, I get to work with folks from all over the world every single day thanks to WordPress. This has given me the honor of having a global mindset that I carry with me no matter where I go. I feel I have traveled enough for many lifetimes over. Once you begin thinking at that scale, whether due to a global mindset or due to the percentage of the web powered by WordPress, you can’t go back. Something in you changes for the better.</p>\n<h3>Finding Who I Am</h3>\n<p>I think often of LGBTQ+ people of years past and how many likely never would have had the chance at a life that I have. This rings particularly true during Pride Month. On top of everything else, WordPress has given me a platform and a job where I can be my truest self whether that’s sharing my mental health struggles, talking about my evolving thoughts <a href="https://surrogacy-stories.com/">on being born through surrogacy</a>, or imagining a different way of existing <a href="https://nomad.blog/2020/01/16/little-homes/">with many little homes rather than one</a>. With WordPress, I can share my words and I can be heard. I can fiercely be myself and be amplified rather than silenced. I can join community meetings and proudly share a rainbow emoji as I say hi. WordPress has emboldened me and has given me so many opportunities to use my newfound creativity to lead in various spaces.</p>\n<p>None of the above gets to the root of why I LOVE what I do and love what WordPress is to me. Beyond any personal change, WordPress has allowed me to help others and to increase my own impact on this world. Whether it was working with department sites during my time at UNC or helping a local non profit set up a brand new website to bring theirs out of the 90s, I am thrilled to have a job and a passion that centers on helping others succeed.</p>\n<blockquote><p>It’s such a privilege to work with folks during different stages of their sites – it’s always so personal and so sacred.</p></blockquote>\n<p>I can vividly remember the first time this gripped me. I was helping a professor at UNC set up a site and when we finally published it, he couldn’t believe it was “live”. He kept asking me whether other researchers, students, professors, etc. could find him. As I began to explain how everything worked, he was nearly brought to tears.</p>\n<p>“I can’t believe my life’s work can be found by anyone in the world.”</p>\n<p>I was just a freshman at this point and didn’t quite understand what I had stumbled upon with WordPress. I couldn’t have imagined that this would be my life. I had a friend a few years ago say to me, “You are the last person I ever expected to work in technology.” I grew quiet and nodded solemnly, “Me too”. This great adventure and great chance is truly due to those who helped me patiently over the years. It’s also due to those who enabled WordPress to be what it is today and what it will be tomorrow. I don’t take this for granted.</p>\n<h3>Finding My Joy</h3>\n<p>There’s a concept I am stuck on these days. It’s centered on this quote:</p>\n<blockquote><p>“The true meaning of life is to plant trees, under whose shade you do not expect to sit.” – Nelson Henderson</p></blockquote>\n<p>When I was 10, so many were working so immensely hard to create the shade in which I currently sit. This gorgeous, remarkable, world expanding shade that I can’t believe I ever found and that I hardly have the words to describe. I send a tearful “thank you” from my soul into the ether for all of you out there who made this precious life of mine possible.</p>\n<p><a href="https://nomad.blog/2021/04/17/one-year-in-devrel/">Just over a year ago</a>, I switched into a Developer Relations Wrangler position at Automattic as a full time contributor to the WordPress project and my hope now is that I can pay forward what has been given to me through planting trees of my own. To have the chance to give back to something that has given me so much is something I wake up everyday thankful for, even on the tough days. Even better, I now get to play a role in encouraging, supporting, and believing in other people as a core part of my job in the same way so many have done for me.</p>\n<p>The post <a rel="nofollow" href="https://heropress.com/essays/changing-the-world-changing-me/">Changing The World, Changing Me</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, 16 Jun 2021 12:00: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:"Anne McCarthy";s: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:52:"WPTavern: Automattic Acquires Day One Journaling App";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118457";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:149:"https://wptavern.com/automattic-acquires-day-one-journaling-app?utm_source=rss&utm_medium=rss&utm_campaign=automattic-acquires-day-one-journaling-app";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7839:"<img />\n\n\n\n<p>Automattic has <a href="https://wordpress.com/blog/2021/06/14/day-one-the-journaling-app-joins-automattic/">acquired Day One</a>, a journaling app available on iPhone, Android, iPad, Mac, and Apple Watch. The app makes it easy to create journal entries on the go, offers end-to-end encryption for privacy on its paid tier, and has offline capabilities. While most users compose private entries, Automattic&rsquo;s acquisition announcement promises integrations for publishing to the web:</p>\n\n\n\n<p><em>That doesn&rsquo;t mean that everything you journal has to stay private, though. When you want to share specific entries &ndash; or even entire journals with the world &ndash; you can expect seamless integrations with both WordPress.com and Tumblr to do just that. On the flip side of that, importing your favorite content from WordPress.com and Tumblr into Day One is on the near-term roadmap.&nbsp;</em></p>\n\n\n\n<p>In a <a href="https://ma.tt/2021/06/day-one-at-automattic/">post</a> on his personal blog, Automattic CEO Matt Mullenweg said he has been a user of Day One since 2016 and spoke highly of the app&rsquo;s infrastructure: </p>\n\n\n\n<p><em>Day One not only nails the experience of a local blog (or journal as they call it) in an app, but also has (built) a great technical infrastructure &mdash;&nbsp;<s>i</s>t works fantastic (when) offline and has a&nbsp;<a href="https://help.dayoneapp.com/en/articles/840428-end-to-end-encryption-faq">fully encrypted sync</a>&nbsp;mechanism, so the data that&rsquo;s in the cloud is secured in a way that even someone with access to their database couldn&rsquo;t decode your entries, it&rsquo;s only decrypted on your local device. Combining encryption and sync in a truly secure way is tricky, but they&rsquo;ve done it.</em></p>\n\n\n\n<p>A journaling app is a surprising acquisition for Automattic, which has traditionally gravitated towards snapping up publishing-related companies and tools. WordPress is capable of powering nearly every kind of public-facing website, but private publishing has never been its strong suit. Though many have used WordPress in a sort of &ldquo;private&rdquo; mode for journaling, or set up local installations, the software is not streamlined for this particular use case. Day One expertly handles this niche that has remained relatively untouched in the WordPress ecosystem.</p>\n\n\n\n<p>In explaining the acquisition, Mullenweg also touched on his &ldquo;vision of making Automattic the Berkshire Hathaway of the internet,&rdquo; a notion <a href="https://awilkinson.medium.com/the-berkshire-hathaway-of-the-internet-391a8ee83db">shared by Tiny Capital</a> and often applied to Alphabet and its diverse holdings. One distinction is that Automattic&rsquo;s acquisitions tend to complement one another technologically, often introducing the potential for improvements that can be shared with other products through open source software.</p>\n\n\n\n<h2>Day One Community Remains Trepidatious About the Acquisition</h2>\n\n\n\n<p>Why did Automattic buy the company? Day One customers are curious, as some of them perceive Automattic to be another &ldquo;corporate giant&rdquo; gobbling up a scrappy startup, ready to squeeze every possible drop of revenue out of the app&rsquo;s loyal customers. </p>\n\n\n\n<p>Many long-time Day One users have never heard of Automattic and they are understandably leery of seeing their beloved app change hands. Perusing the comments on the <a href="https://twitter.com/dayoneapp/status/1404544058693931012">Twitter announcement</a> and in the app&rsquo;s <a href="https://www.facebook.com/groups/DayOneCommunity/">community on Facebook</a>, the news has precipitated a stream of cancellations and exports as users explore alternatives. Numerous customers were disheartened by one particular ambiguous statement in Day One&rsquo;s <a href="https://dayoneapp.com/blog/day-one-at-automattic">announcement</a>, which left the door open for future changes to the privacy of the app:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Rest assured there are no current plans to change the privacy of Day One; safely protecting memories and creating a 100% personal space is the foundation upon which this company was built.</p></blockquote>\n\n\n\n<p>The statement has since been updated to be more reassuring to users, although it still doesn&rsquo;t explicitly promise no changes. It does contain a hint at why Automattic was interested in acquiring the app:</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Rest assured that Day One&rsquo;s commitment to protecting your privacy remains unchanged. Safely protecting memories and creating a 100% personal space is the foundation upon which this company was built. (In fact, our technical capabilities around privacy are a large part of what Automattic finds valuable in our company).</p></blockquote>\n\n\n\n<p>I have never seen a more engaged community with such a strong reaction following an acquisition. Many are deeply invested, having poured years of their lives and private memories into Day One.</p>\n\n\n\n<p>&ldquo;Oh, great. I find a journaling app I really like and have 10 years of entries invested, and they get gobbled up by a bigger fish,&rdquo; one user <a href="https://www.facebook.com/groups/DayOneCommunity/permalink/4349118571799031/?comment_id=4349151848462370&__cft__%5B0%5D=AZWO-PD5BkU0Im_Ul_AnDXTjKt3zxfrG01C6D63pV2eE2wbMb18YOS1sjNEx5BHzE2F84C27ZAvdZAOoAdu1EjSqPBnqFUe5AcJs8NJAPLWbPEmjajQAbHdqHjXz5wIpAqeciIm_ogE6bnV_nSoBeZfBpT1jOCDH5o3i9P1MwCzUCUuB4f273tuokE2AbPstgPY&__tn__=R%5D-R">commented</a> in the app&rsquo;s Facebook community. &ldquo;What will become of our beloved app? Will the safety, security, and integrity of our data be assured? Time to back up all of my data local.&rdquo;</p>\n\n\n\n<p>Users have <a href="https://www.facebook.com/groups/DayOneCommunity/permalink/4349118571799031/?comment_id=4350115481699340&__cft__%5B0%5D=AZWO-PD5BkU0Im_Ul_AnDXTjKt3zxfrG01C6D63pV2eE2wbMb18YOS1sjNEx5BHzE2F84C27ZAvdZAOoAdu1EjSqPBnqFUe5AcJs8NJAPLWbPEmjajQAbHdqHjXz5wIpAqeciIm_ogE6bnV_nSoBeZfBpT1jOCDH5o3i9P1MwCzUCUuB4f273tuokE2AbPstgPY&__tn__=R%5D-R">concerns</a> about Day One&rsquo;s updated privacy policy&nbsp;and whether the company might share data with affiliates. Many embraced the app because it was free of any ties with social media platforms. They have sewn themselves into this app in the most vulnerable way, and they are worried about how their private data will be handled in the future. Automattic may have a long road ahead in easing customers&rsquo; concerns so that they don&rsquo;t feel the pressure to export and look for alternatives.</p>\n\n\n\n<p>As someone who considered using Day One years ago, I think I would be more likely to use it now, knowing that Automattic is usually in it for the long haul. I passed on Day On at the time because apps come and go and it&rsquo;s not always easy to predict which ones have the right business model to stay afloat. One of my worst recurring nightmares is that I accidentally throw away my paper journals or that my house burns down with my journals inside. Putting trust in a company to keep your electronic data safe and private is an intensely personal decision.</p>\n\n\n\n<p>Knowing that a larger company with more resources is behind Day One, along with leadership that bears a genuine appreciation for its underlying tech, it seems like a safer pick for a journaling app that will be around for the next ten years. The company&rsquo;s founder and CEO Paul Mayne will continue to lead his same team at Automattic and is convinced that the move will be beneficial for &ldquo;the preservation and longevity&rdquo; of the app. Given how passionate Day One&rsquo;s user base is about protecting the app&rsquo;s future, I&rsquo;m eager to see how Automattic handles the challenge of winning their confidence.</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, 16 Jun 2021 05:30:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:101:"WPTavern: Ask the Bartender: Is It OK To Provide WordPress Admin Credentials to Plugin Support Staff?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118497";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:243:"https://wptavern.com/ask-the-bartender-is-it-ok-to-provide-wordpress-admin-credentials-to-plugin-support-staff?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-is-it-ok-to-provide-wordpress-admin-credentials-to-plugin-support-staff";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8410:"<p class="has-drop-cap"><em>No. Nada. Nah. Nope. That&rsquo;s a negative. Under no circumstances. My mama didn&rsquo;t raise no fool. Heck naw. Not on your life.</em> And, the other thousands of ways to tell anyone asking for site credentials to bugger off, even plugin support staff of a &ldquo;trusted&rdquo; WordPress development company.</p>\n\n\n\n<p>That is my way of saying that I do not trust anyone. Neither should you. However, there are cases where it is necessary to provide admin permissions to a plugin&rsquo;s support staff.</p>\n\n\n\n<p>Today&rsquo;s installment of the <a href="https://wptavern.com/tag/ask-the-bartender">Ask the Bartender</a> series comes courtesy of a reader named Niko. Because the entire text is over 1,000 words, I will simply link to the <a href="https://wptavern.com/wp-content/uploads/2021/06/is-it-ok-to-provide-plugin-support-credentials.txt">transcript via a .txt file</a> for those who want to read it in full. Here in the post, I will stick to the vital bits. Or at least the parts that I want to address.</p>\n\n\n\n<p>One of Niko&rsquo;s Facebook group members kicked the discussion off.</p>\n\n\n\n<blockquote class="wp-block-quote"><p>&lsquo;Is it okay to send FTP details for a plugin developer to troubleshoot the issue we are having with WooCommerce. We have already provided WordPress Admin credentials.&rsquo;</p><p>This is pretty normal practice in the WordPress world, right? Plugin developers helping out on issues, and if they can&rsquo;t replicate an issue, they need the access so they can check if it is a plugin issue or a server issue and fix things?</p></blockquote>\n\n\n\n<p>Over the years, I have seen this become more of a common practice. However, it is not a practice that I recommend from either the user or developer end. Any site owner should ask whether they trust the person to whom they are giving credentials. If the answer to that question is no, you have the answer to the first question.</p>\n\n\n\n<p>In over a decade of running a theme and plugin shop, I never needed admin or FTP access to deal with a support question. It did not matter if it was a large and complex plugin or a small one. Because I was the sole person at the company, I also personally answered hundreds of thousands of support questions over the years. Still, not once did I log into a user&rsquo;s site to help them. That always seemed like a liability issue for me, but I also used such scenarios as teaching moments about trust and security.</p>\n\n\n\n<p>Users sometimes provided credentials to me without me asking. Often they posted them in plain text in forums, email, or Slack (also, you should never do that). If on-site code needed changing, my users performed the task themselves or installed a bug-free version of the theme/plugin I handed over.</p>\n\n\n\n<p>If they did not know how to perform a task via the admin, FTP, or otherwise, I took the time to teach them. Yes, that required more energy on both ends, but I believe we were the better for it. More than once, those moments led some users down the path of becoming developers themselves, or it was at least a tiny stepping stone for them. I remain friends with many of them today and am proud that they started with my little solo WordPress shop.</p>\n\n\n\n<p>Some cases were rougher than others. Many times, I would replicate their setup (plugins, theme, etc.) on my machine. The majority of the time, this led me to the solution &mdash; <em>I was using <a href="https://developer.wordpress.org/reference/functions/_doing_it_wrong/"><code>__doing_it_wrong()</code></a> long before WordPress introduced the idea.</em> In the long run, I was able to pass countless bug fixes upstream to other developers. I made a lot of developer friends this way too.</p>\n\n\n\n<p>I have no doubts that the road I traveled was the longer of the two. There were times when I spent an hour, two, or even more addressing one user&rsquo;s needs. Popping into some of their WordPress admins would have been a quicker course.</p>\n\n\n\n<p>However, my theme and plugin users never needed to worry about whether they trusted me enough to provide that level of access. Plus, I had no chance of accidentally breaking their site by making custom changes.</p>\n\n\n\n<p>Are there times when a plugin&rsquo;s support staff <em>really</em> needs access? Probably.</p>\n\n\n\n<p>The original question was regarding WooCommerce. It is one of the most technically advanced plugins in existence for WordPress. Replicating a user&rsquo;s setup off-site for it is trickier than most others. There may be <em><strong>rare</strong></em> times when you need to provide some access, but you should never trust anyone.</p>\n\n\n\n<p>The second part of Niko&rsquo;s question revolves around the European Union&rsquo;s General Data Protection Regulation (GDPR) and user data. It is a vital part of dealing with those times when you decide to hand over the keys to your website.</p>\n\n\n\n<blockquote class="wp-block-quote"><p>Alright so here comes the issue after we think about GDPR. If this developer happens to be outside the EU, then you would need to anonymize customer data and make an NDA agreement with that exact dev or company that is behind the plugin so they can come around and fix things.</p></blockquote>\n\n\n\n<p>I will preface this with the usual <em>I am not a lawyer</em>. However, protecting user data is always a legal and ethical priority on any site you run, regardless of what jurisdiction you fall under.</p>\n\n\n\n<p>In those &mdash; again, rare &mdash; cases where you need to provide access to your WordPress admin, there are steps you could take to better protect your site and its data. Regardless of the trustworthiness of a developer or a support staff member, there is always one rule of thumb when dealing with website security: trust no one and trust nothing.</p>\n\n\n\n<p>The first step should always be having a backup system in place. On the off chance that the support staff breaks something, you will want to revert the site back to its previous state.</p>\n\n\n\n<p>Never provide complete admin-level access. I recommend installing and activating a role and capability management plugin. This will allow you to create a custom role for support help and limit the areas of the site they have access to. You would then create a user account for them with this role. Once they have completed their work, delete their account.</p>\n\n\n\n<p>If you do not want them to see registered users or do anything with user data at all, make sure their user role does not have the following capabilities:</p>\n\n\n\n<ul><li><code>create_users</code></li><li><code>delete_users</code></li><li><code>edit_users</code></li><li><code>list_users</code></li><li><code>promote_users</code></li><li><code>remove_users</code></li></ul>\n\n\n\n<p>There are many other admin-level capabilities like <code>edit_files</code>, <code>edit_plugins</code>, and <code>edit_themes</code> that you should also avoid. Essentially, disallow most of the caps from the <a href="https://wordpress.org/support/article/roles-and-capabilities/#administrator">Administrator list in the WordPress documentation</a>.</p>\n\n\n\n<p>Most likely, plugin teams might need access to the <code>manage_options</code> capability and any that are custom to their plugin. Even those can be dangerous, but that backup you put in place should mitigate any potential issues.</p>\n\n\n\n<p>As for an FTP password? I trust very few people with that level of access.</p>\n\n\n\n<p>This reply probably sounds like I do not think any plugin shops or developers are trustworthy. Honestly, I do not know of any that have breached user trust using login or FTP credentials in this way. On the other hand, I have no way of knowing whether the staff member I am talking to plans to rage quit his job in the afternoon and is willing to burn everything down in the morning.</p>\n\n\n\n<p>I have also seen a handful of cases where a developer dropped in to fix something but ended up breaking the site along the way. Backups were crucial in addressing those issues.</p>\n\n\n\n<p>This post is not meant to make plugin developers or companies appear untrustworthy. Most are good people just trying to make an honest living. However, not trusting anything is website security 101. It is merely the baseline in which users should operate. If you go into any interaction with this mindset, it should help you make smarter decisions on a case-by-case basis.</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, 15 Jun 2021 23:26:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:40:"WordPress.org blog: WordPress 5.8 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:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://wordpress.org/news/?p=10808";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2021/06/wordpress-5-8-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5909:"<p>WordPress 5.8 Beta 2 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so it’s not recommended to run this version on a production site. Consider setting up a test site to play with it.</p>\n\n\n\n<p>You can test the WordPress 5.8 Beta 2 in two ways:</p>\n\n\n\n<ul><li>Install/activate the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (select the <code>Bleeding edge</code> channel and the <code>Beta/RC Only</code> stream)</li><li>Direct download the beta version here (<a href="https://wordpress.org/wordpress-5.8-beta2.zip">zip</a>).</li></ul>\n\n\n\n<p>The current target for the final release is July 20, 2021. That’s just <strong>five weeks away</strong>, so your help is vital to ensure that the final release is as good as it can be.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/">Beta 1</a>, <a href="https://core.trac.wordpress.org/query?status=closed&changetime=06%2F09%2F2021..06%2F15%2F2021&milestone=5.8&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">26</a> bugs have been fixed. Here is a summary of some of the included changes:</p>\n\n\n\n<ul><li>Block Editor: Remove bundled block patterns and support the patterns directory. (<a href="https://core.trac.wordpress.org/ticket/53246">#53246</a>)</li><li>Block Editor: Add a type property to allow Core to identify the source of the editor styles. (<a href="https://core.trac.wordpress.org/ticket/53175">#53175</a>)</li><li>Build/Test Tools: Adds some tests for Quick Draft section in Dashboard. (<a href="https://core.trac.wordpress.org/ticket/52905">#52905</a>)</li><li>Build/Test Tools: Replaced <code>@babel/polyfill</code> with <code>core-js/stable</code>. (<a href="https://core.trac.wordpress.org/ticket/52941">#52941</a>)</li><li>Coding Standards: Further update the code for bulk menu items deletion to better follow WordPress coding standards. (<a href="https://core.trac.wordpress.org/ticket/21603">#21603</a>)</li><li>External Libraries: Update Underscore to version 1.13.1. (<a href="https://core.trac.wordpress.org/ticket/45785">#45785</a>)</li><li>General: A number of block editor, template mode and widget screen related fixes. (<a href="https://core.trac.wordpress.org/changeset/51149">#51149</a>)</li><li>Login and Registration: Improve the unknown username error message. (<a href="https://core.trac.wordpress.org/ticket/52915">#52915</a>)</li><li>Media: Restore AJAX response data shape in media library. (<a href="https://core.trac.wordpress.org/ticket/50105">#50105</a>)</li><li>Site Health: Display a list of file formats supported by the GD library. (<a href="https://core.trac.wordpress.org/ticket/53022">#53022</a>)</li><li><span>Twemoji: It&#8217;s the new one! (</span><a href="https://core.trac.wordpress.org/ticket/52852">#52852</a>)</li></ul>\n\n\n\n<h2><strong>How You Can Help</strong></h2>\n\n\n\n<p>Watch the <a href="https://make.wordpress.org/core/">Make WordPress Core blog</a> for <a href="https://make.wordpress.org/core/tag/5-8+dev-notes/">5.8-related developer notes</a> in the coming weeks, which will break down these and other changes in greater detail.</p>\n\n\n\n<p>So far, contributors have fixed <a href="https://core.trac.wordpress.org/query?status=closed&changetime=..06%2F15%2F2021&milestone=5.8&group=component&max=500&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority">214 tickets in WordPress 5.8</a>, including <a href="https://core.trac.wordpress.org/query?status=closed&status=reopened&changetime=..06%2F15%2F2021&type=enhancement&type=feature+request&milestone=5.8&group=component&col=id&col=summary&col=type&col=status&col=milestone&col=changetime&col=owner&col=priority&col=keywords&order=changetime">87 new features and enhancements</a>, and more bug fixes are on the way.</p>\n\n\n\n<p><strong>Do some testing!</strong></p>\n\n\n\n<p><a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">Testing for bugs</a> is a vital part of polishing the release during the beta stage and a great way to contribute. <img src="https://s.w.org/images/core/emoji/13.1.0/72x72/2728.png" alt="✨" class="wp-smiley" /></p>\n\n\n\n<p>If you think you’ve found a bug, please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta</a> area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible <a href="https://make.wordpress.org/core/reports/">bug report</a>, file one on <a href="https://core.trac.wordpress.org/newticket">WordPress Trac</a>. That’s also where you can find a list of <a href="https://core.trac.wordpress.org/tickets/major">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href="https://profiles.wordpress.org/chanthaboune/" class="mention"><span class="mentions-prefix">@</span>chanthaboune</a> for revision, <a href="https://profiles.wordpress.org/webcommsat/" class="mention"><span class="mentions-prefix">@</span>webcommsat</a>, <a href="https://profiles.wordpress.org/youknowriad/" class="mention"><span class="mentions-prefix">@</span>youknowriad</a>, <a href="https://profiles.wordpress.org/jorbin/" class="mention"><span class="mentions-prefix">@</span>jorbin</a>, <a href="https://profiles.wordpress.org/felipeelia/" class="mention"><span class="mentions-prefix">@</span>felipeelia</a> , and <a href="https://profiles.wordpress.org/jeffpaul/" class="mention"><span class="mentions-prefix">@</span>jeffpaul</a> for proofreading, and <a href="https://profiles.wordpress.org/cbringmann/" class="mention"><span class="mentions-prefix">@</span>cbringmann</a> for final edits!</em></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><em>Install won’t you please<br />WordPress 5-8 Beta 2?<br />We need your help: test!</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, 15 Jun 2021 18:34: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: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: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:72:"WPTavern: Toolbelt Tidies WordPress Plugin and Theme Admin Notifications";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118423";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:189:"https://wptavern.com/toolbelt-tidies-wordpress-plugin-and-theme-admin-notifications?utm_source=rss&utm_medium=rss&utm_campaign=toolbelt-tidies-wordpress-plugin-and-theme-admin-notifications";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5635:"<p class="has-drop-cap"><em>It&rsquo;s a tale as old as</em>, well, WordPress. Ben Gillbanks noticed a conversation where someone thought that admin notices were getting out of hand. Enter another developer&rsquo;s attempt to address this problem. With a few code additions to his <a href="https://wordpress.org/plugins/wp-toolbelt/">Toolbelt plugin</a>, he had a working solution to stop the madness: <a href="https://www.binarymoon.co.uk/2021/06/take-control-of-wordpress-plugin-and-theme-notifications/">the Tidy Notifications module</a>.</p>\n\n\n\n<p>Despite the <a href="https://wptavern.com/is-wp-notify-the-silver-bullet-wordpress-needs-to-end-admin-notification-spam">early promise</a> of the WP Notify project last year, it still feels like we are no closer to addressing the overuse of the current admin notice system in WordPress. In reality, it is not so much a system as a hook that developers can use for literally anything. It is the Wild West of the WordPress admin. No rules. No order. And no proper API for standardizing how notices work.</p>\n\n\n\n<p><a href="https://github.com/WordPress/wp-notify">WP Notify still exists on GitHub</a> and continues to move along at its own pace, but there is no guarantee that it will ever land in the core platform. Sometimes, the best thing a developer can do is solve the existing problem and hope that WordPress follows along down the road with a better solution.</p>\n\n\n\n<p>I am already tidying admin notifications with Toolbelt on my development install. My primary use case is to hide the non-dismissible notice from the Gutenberg plugin that I have a Full Site Editing theme installed &mdash; <em>is there not a guideline against such notices?</em> I did not suddenly forget that I was using such a theme between the 999th and 1,000th time the reminder appeared on every admin screen of my installation.</p>\n\n\n\n<img />Notifications expand when clicking on the bell icon in the toolbar.\n\n\n\n<p>The Tidy Notifications system in Toolbelt neatly tucks all admin notices under a bell icon in the admin toolbar. It also displays the number of notifications.</p>\n\n\n\n<p>It makes the WordPress admin so clutter-free that I do not know how I have lived without it before. I cannot imagine going back.</p>\n\n\n\n<p>The only problem with Toolbelt&rsquo;s solution is that there is no way to distinguish between essential notices and those that should be tucked away. WordPress letting you know that your post was successfully updated is an important notice that should not be hidden. However, a plugin author drumming up five-star reviews, yeah, that should not be front and center.</p>\n\n\n\n<p>Having two systems would be beneficial. The existing <code>admin_notices</code> hook in WordPress should be used for letting users know the outcome of their actions or actions that they should take. The post editor, which does not use page reloads or make the hook available, has replaced this with the snackbar popup system. These necessary notices have their place.</p>\n\n\n\n<p>However, WordPress has no built-in system for non-essential notices. This leaves plugin and theme authors with two options: bundle an entirely custom notification apparatus with each extension or just use the <code>admin_notices</code> hook. The latter is the more efficient use of developer resources.</p>\n\n\n\n<p>Of course, we have had this conversation before. Just shy of a year ago, I wrote a post titled <a href="https://wptavern.com/are-plugin-authors-to-blame-for-the-poor-admin-notices-experience">Are Plugin Authors to Blame for the Poor Admin Notices Experience?</a> In the comments, WordPress project lead Matt Mullenweg <a href="https://wptavern.com/are-plugin-authors-to-blame-for-the-poor-admin-notices-experience#comment-335886">posited that the solution</a> to unwanted notifications is not to build an inbox, comparing WordPress to cell phones. He said that app store guidelines were likely more impactful to user happiness. In general, I agree with that concept. Setting down a few directory UI and UX rules would not hurt.</p>\n\n\n\n<p>Given the more recent <a href="https://wptavern.com/upcoming-changes-and-steps-for-an-overhauled-wordpress-theme-review-system">push to loosen guidelines</a> for the theme directory, that does not seem to be in the cards. Admin notices were not one of the guardrails, the safety net of &ldquo;must-haves&rdquo; from the Themes Team.</p>\n\n\n\n<p>The admin notice spam WordPress users see today most commonly comes from plugins and not themes. <em>Why?</em> It is not because theme authors care more about user happiness levels. It is because the theme review guidelines over the years have been strict. Anything too flamboyant gets the hammer.</p>\n\n\n\n<p>The WordPress Themes Team even has a custom guideline-friendly, <a href="https://github.com/WPTT/admin-notices/">drop-in class</a> that themers can use.</p>\n\n\n\n<p>The plugin and theme directories have taken far different stances on admin notices, and it shows. When the Themes Team moves to minimal checks, there may not be anything to stop themers from competing for the most obnoxious admin notice award. <em>Game on, plugin authors.</em></p>\n\n\n\n<p>&ldquo;Unwanted&rdquo; notifications may even be the wrong terminology. Often, they are &ldquo;unwanted right now.&rdquo; Sometimes, folks might want to read a message &mdash; just later. I am still holding out hope that we will have a notifications/messages inbox in WordPress one day. One that is entirely controlled by the user.</p>\n\n\n\n<p>Until then, I may just stick with the Tidy Notifications module in Toolbelt. There are many other handy components in it too.</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, 14 Jun 2021 22:54:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Justin Tadlock";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:63:"WPTavern: Wordfence Now Authorized as a CVE Numbering Authority";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118413";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:171:"https://wptavern.com/wordfence-now-authorized-as-a-cve-numbering-authority?utm_source=rss&utm_medium=rss&utm_campaign=wordfence-now-authorized-as-a-cve-numbering-authority";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4968:"<p>Wordfence has been <a href="https://www.wordfence.com/blog/2021/06/wordfence-is-now-a-cve-numbering-authority-cna/">authorized</a> by the Common Vulnerabilities and Exposures (CVE&reg;) Program as a CNA (CVE Numbering Authority), which allows the company to directly assign CVE numbers for new vulnerabilities in WordPress core, plugins, and themes. The authority is granted by <a href="https://www.mitre.org/">Mitre Corporation</a>, a federally-funded US non-profit that manages research and development centers. Wordfence anticipates that the ability to create CVE assignments will expedite its security research.</p>\n\n\n\n<p>&ldquo;As the Wordfence Threat Intelligence team continues to produce groundbreaking WordPress security research, Wordfence can more efficiently assign CVE IDs prior to publicly disclosing any vulnerabilities that our team discovers,&rdquo; Wordfence threat analyst Chloe Chamberland said. &ldquo;This means that a CVE ID will be immediately assigned with every vulnerability we discover rather than waiting for an assignment from an external CNA.&rdquo;</p>\n\n\n\n<p>Not having to wait on a CVE ID is a major advantage for the company, especially when working with enterprise installations where WordPress is used in combination with other software. It also helps security personnel prioritize and act based on the potential severity of threats. </p>\n\n\n\n<p>&ldquo;Our efforts to become a CNA had these individuals, institutions, and enterprise personnel in mind, as well as WordPress&rsquo; reputation as a whole,&rdquo; Chamberland said. &ldquo;Now, those tasked with securing WordPress will be able to quickly reference the CVE ID from our blog posts when reporting vulnerabilities throughout their organization and handling security update prioritization. We also hope that by being a CNA, Wordfence will receive even more direct reports from security researchers.&rdquo;</p>\n\n\n\n<p>Becoming a CNA simplifies a security company&rsquo;s process of submitting vulnerabilities. Wordfence is the second company to become one, operating within the scope of WordPress and related vulnerabilities. In January 2021, <a href="https://wptavern.com/wpscan-can-now-assign-cve-numbers-for-wordpress-core-plugin-and-theme-vulnerabilities">WPScan was granted CVE Numbering Authority status</a>. Prior to becoming a CNA, assigning CVEs for every vulnerability in WPScan&rsquo;s database would have been too time consuming.</p>\n\n\n\n<p>&ldquo;Becoming a CNA has allowed us to help security researchers to verify and triage their vulnerabilities,&rdquo; WPScan founder and CEO Ryan Dewhurst said. &ldquo;This has helped grow our WordPress vulnerability database and keep WordPress users secure. But it is just one source of vulnerabilities among many others that we use.&rdquo;</p>\n\n\n\n<p>The process for Wordfence to become a CNA was surprisingly simple. Chamberland said the company filled out a registration form with a few questions. </p>\n\n\n\n<p>&ldquo;Once we were approved and agreed upon a scope, you are required to watch a series of onboarding videos that explain the processes required of a CNA,&rdquo; she said. &ldquo;After that, we had an onboarding meeting to ensure our team was fully trained on CVE Program protocols. It took Wordfence about a month to get authorized as a CNA once they received our registration form.&rdquo;</p>\n\n\n\n<p>Historically, the WordPress ecosystem has been a magnet for those looking to exploit vulnerabilities, due to its large footprint on the web. That trend is likely to continue. Chamberland believes there is room for multiple CNA&rsquo;s in the WordPress space.</p>\n\n\n\n<p>&ldquo;We&rsquo;ve had a great working relationship with WPScan over the years, and we expect that this relationship will continue as we have a similar mission in helping secure the WordPress community,&rdquo; she said.</p>\n\n\n\n<p>&ldquo;As WordPress grows, it becomes a larger and more attractive target for malicious actors. The more hands we have on deck, and the better we collaborate and adhere to industry standard security practices, the safer WordPress will be.&rdquo;</p>\n\n\n\n<p>Attracting more researchers to report vulnerabilities is a major benefit to security companies that gain CNA status, since they are essentially in the business of selling vulnerability protection data. They give their paid customers early access to patches that are not yet available to the general public. Becoming a CNA has the potential to increase the value their businesses can provide. </p>\n\n\n\n<p>&ldquo;With this growth in WordPress, we expect to see more security researchers in the WordPress space,&rdquo; Chamberland said.&nbsp;&ldquo;As such, we are bound to see an increase in CVE ID requests. Having multiple CNA&rsquo;s that can assign CVE IDs to WordPress core, plugins and themes make sense to improve the speed in which security researchers can obtain CVE IDs, and provides researchers with multiple sources for CVE IDs.&rdquo;<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, 14 Jun 2021 21:44:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:27:"Matt: Day One at Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=54355";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"https://ma.tt/2021/06/day-one-at-automattic/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2932:"<p>I&#8217;m not sure when I first came across the <a href="https://dayoneapp.com/">critically acclaimed Day One product</a>, which is the best private blogging and journaling app out there, but I began seriously using it daily in 2016 when my father was in the ICU and <a href="https://ma.tt/2016/04/in-memoriam-chuck-mullenweg/">later passed</a>. Having a private, safe place to write what I was going through kept me sane and helped me process everything.</p>\n\n\n\n<p>Writing has always been a salve for me, and I&#8217;ve had local or private WordPress installations pretty much since 2003 to capture and archive writing that wasn&#8217;t fit for the public web.</p>\n\n\n\n<p>Day One not only nails the experience of a local blog (or journal as they call it) in an app, but also has (built) a great technical infrastructure — it works fantastic (when) offline and has a <a href="https://help.dayoneapp.com/en/articles/840428-end-to-end-encryption-faq">fully encrypted sync</a> mechanism, so the data that&#8217;s in the cloud is secured in a way that even someone with access to their database couldn&#8217;t decode your entries, it&#8217;s only decrypted on your local device. Combining encryption and sync in a truly secure way is tricky, but they&#8217;ve done it.</p>\n\n\n\n<p>This is a long intro to say, as you can read from <a href="https://dayoneapp.com/blog/day-one-at-automattic">Day One&#8217;s founder and CEO Paul Mayne</a>, <a href="https://wordpress.com/blog/2021/06/14/day-one-the-journaling-app-joins-automattic/">from Eli at WordPress.com</a>, and <a href="https://staff.tumblr.com/post/653995690228400128/private-blogging-its-a-vibe-but-some-innermost">on Tumblr</a>, that Paul and the team are joining the team at <a href="https://automattic.com/">Automattic</a>. For many years I&#8217;ve talked to anyone who will listen about my vision of making Automattic the <a href="https://www.berkshirehathaway.com/">Berkshire Hathaway</a> of the internet, and Paul&#8217;s decision to continue to grow his amazing business as part of Automattic is a great validation of the way we&#8217;ve been building our culture and long-term orientation in our business. Day One is a beloved product, and bringing it into the fold is a responsibility I take very seriously and comes from a deep respect for what&#8217;s been built and a belief that working together we can create something for users better than we could working apart.</p>\n\n\n\n<p>Great software takes time, and the Day One team has been at it for <a href="https://dayoneapp.com/about/">about a decade now</a>, I can&#8217;t wait to see what they accomplish in the coming decade and beyond. If you haven&#8217;t tried out Day One yet, please check it out in the <a href="https://apps.apple.com/us/app/day-one-2-journal-notes/id1044867788">Apple</a> or <a href="https://play.google.com/store/apps/details?id=com.dayoneapp.dayone&hl=en">Google&#8217;s</a> app store.</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, 14 Jun 2021 20:53: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: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: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:102:"WPTavern: WordPress 5.8 Beta 1 Released: New Blocks, New Widgets Screen, and Pattern Directory on Deck";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://wptavern.com/?p=118227";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:243:"https://wptavern.com/wordpress-5-8-beta-1-released-new-blocks-new-widgets-screen-and-pattern-directory-on-deck?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-8-beta-1-released-new-blocks-new-widgets-screen-and-pattern-directory-on-deck";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7429:"<p><a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/">WordPress 5.8 beta 1</a> is ready for testing. This upcoming release makes major strides towards solidifying WordPress&rsquo; site building capabilities, along with improvements to features users have enjoyed since the launch of the block editor. It is one of the most feature-packed releases in recent history and as such requires all hands on deck for testing. </p>\n\n\n\n<p>New blocks in 5.8 include Page List, Site Title, Logo, Tagline, Query Loop, and Duotone. I decided to take each one for a spin this weekend on a test site, putting myself in the shoes of someone trying these blocks for the first time.</p>\n\n\n\n<p>I was surprised to learn that the template editor will be available to sites using any WordPress theme, since all the previous FSE testing rounds have called on testers to use the latest version of the&nbsp;<a rel="noreferrer noopener" href="https://wordpress.org/themes/tt1-blocks/" target="_blank">TT1 Blocks Theme</a>. It will be interesting to see how users respond to this and if it works well with older themes. Users can now create and edit custom templates for pages and posts using blocks. </p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>The template editor includes the new List View panel that gives an overview of all the sections and blocks in the template.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>Most of the new blocks in 5.8 are intended to work within the context of the template editor, but they also work in the post editor.</p>\n\n\n\n<p>The Page List block magically populates a list of all the pages on a site as soon as it is inserted. Unfortunately, there isn&rsquo;t a way to delete a single page from the list. If you try to delete a page the entire block disappears. This seems like a bug and is a frustrating experience in the context of the post editor. It may be more useful in terms of building navigation but this seems like a rough first pass.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>The Query Loop block comes with some different designs for how the loop could be displayed. Once a basic layout is chosen for a starting point, users can further customize the blocks within the loop, including typography, color, length of excerpt, and more.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<p>The Site Title, Tagline, and Logo blocks all seem to work as expected but I found previews to be unreliable for things like alignment and spacing. At this point in time, it seems like template editing will be better suited to users who are more adventurous and experimental when it comes to new features.</p>\n\n\n\n<p>Duotone is a fun new core block that you can see in action below, demonstrated by WordPress documentation contributor Milana Cap. The block adds images effects that can be used in media blocks. Theme and plugin developers can also employ and customize the effects for their own particular use cases.</p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Oh. My. Gutenberg.<br /><br />Imagine images in duotone on your website &#129327; <br /><br />And now that you imagined it, you want it, right? Right?<br /><br />It''s coming up in <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a> 5.8 &#128525; stay tuned &#128522; <a href="https://t.co/t5JHBcTEOV">pic.twitter.com/t5JHBcTEOV</a></p>&mdash; Milana Cap (@DjevaLoperka) <a href="https://twitter.com/DjevaLoperka/status/1402552814174457856?ref_src=twsrc%5Etfw">June 9, 2021</a></blockquote>\n</div>\n\n\n\n<h2>Hello New Widgets Screen!</h2>\n\n\n\n<p>WordPress users will be greeted with a new block-based widgets screen in 5.8. It allows you to use blocks in any widgetized area. It wasn&rsquo;t until I saw how this works that I realized how rigid our old widgets system was. Whatever functionality you were trying to insert had to be readily available as a widget or shortcode. Now any block from the vast world of blocks can be added to widgetized areas. </p>\n\n\n\n<p>Justin Tadlock wrote a post about <a href="https://wptavern.com/classic-widgets-plugin-disables-wordpress-5-8s-upcoming-block-based-widgets-system">how users can disable it with the Classic Widgets plugin</a>. Should you disable it? Not unless you are forced to because of using a theme that doesn&rsquo;t support it very well. Using blocks in widget areas is going to give you much more flexibility for what you can insert. You can even continue to use the old style widgets via the&nbsp;<a href="https://developer.wordpress.org/block-editor/how-to-guides/widgets/legacy-widget-block/">Legacy Widget block</a>. Users may need a little time to adapt to the new interface but it&rsquo;s worth it to have access to the growing world of innovative blocks.</p>\n\n\n\n<div class="wp-block-image"><img /></div>\n\n\n\n<h2>Pattern Directory Will Be Integrated with WordPress 5.8</h2>\n\n\n\n<p>The new Pattern Directory will launch on WordPress.org along with the 5.8 release. Justin Tadlock recently <a href="https://wptavern.com/open-invitation-to-contribute-to-the-wordpress-block-pattern-directory">amplified the Design Team&rsquo;s call for pattern contributions</a> that would be available to users right away. Several have already been <a href="https://github.com/WordPress/pattern-directory/issues">submitted via GitHub issues</a> for the directory and the creativity here is energizing. In addition to introducing an exciting new avenue for designers to put their work out into the ecosystem, the Pattern Directory stands to become a valuable resource and inspiration to users who are designing their own websites.</p>\n\n\n\n<img />A &ldquo;<a href="https://github.com/WordPress/pattern-directory/issues/178">How It Works</a>&rdquo; pattern submitted by <a href="https://github.com/laxmariappan">Lax Mariappan</a>\n\n\n\n<p>At launch the directory will only contain patterns that use core blocks but using blocks from WordPress.org may also be a possibility in the future.</p>\n\n\n\n<p>&ldquo;There have definitely been some discussion of allowing any blocks from the&nbsp;Block&nbsp;Directory to be used and that they would be auto-installed if someone inserted the pattern,&rdquo; Shaun Andrews <a href="https://make.wordpress.org/design/2021/06/08/initial-patterns-for-the-wordpress-org-patterns-directory/#comment-26330">commented</a> in response to a theme studio inquiring about submitting their own patterns that use free blocks. &ldquo;I believe this is possible, and something we should do, but there simply hasn&rsquo;t been any work done to enable it yet.</p>\n\n\n\n<p>&ldquo;We&rsquo;re focused on getting the first iteration of the Pattern Directory launched, and then we plan to continue improving things.&rdquo;</p>\n\n\n\n<p>Pattern transformation is a new feature launching with the new directory, which allows users to convert a block or collection of blocks into different patterns. Patterns can also be recommended and selected during block setup, which should make product onboarding easier.</p>\n\n\n\n<p>These are just a few features coming in WordPress 5.8 that need testing. Check out the <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/">5.8 beta 1 release post</a> for a more comprehensive list of all the improvements that are on deck. The official release is scheduled for <a href="https://make.wordpress.org/core/5-8/">July 20, 2021</a>. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 13 Jun 2021 02:07:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:126:"Gutenberg Times: Over 50 Patterns in the  Pattern Directory, Learn Full-site editing, WordCamp Europe – Weekend Edition #173";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=18121";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:129:"https://gutenbergtimes.com/over-50-patterns-in-the-pattern-directory-learn-full-site-editing-wordcamp-europe-weekend-edition-173/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:19222:"<p>Howdy, </p>\n\n\n\n<p>After three and a half years, it was time to replace the WordPress theme on the Gutenberg Times. The trigger: I wrote about <a href="https://web.dev/measure/">Core Web Vitals</a> for a different project and used the Gutenberg Times as a test project, using <a href="https://developers.google.com/web/tools/lighthouse">Google&#8217;s Lighthouse</a> via an incognito browser window. The desktop version performed very well, all circles in the green range, but the mobile version really crawled over the Internet, ranking in the low 40ties. </p>\n\n\n\n<p><a href="https://searchengineland.com/google-postpones-page-experience-update-rollout-347862">Google announced</a> earlier this year that they start rolling out new page experience update in this month, and start using Web Vitals as another ranking factor for organic search results. I also noticed that GT had a very high number of visitors via the desktop, but not many on mobile, which I found odd. Now I know why. </p>\n\n\n\n<p><a href="https://andersnoren.se/introducing-eksell/">Anders Noren&#8217;s Eksell</a> is our new theme. I love the typography, the clean design. and its graphics. I just started exploring it. Nothing gets things done faster than working on the live site. 😊</p>\n\n\n\n<p>The content mostly converted well, except there are no widget areas, so I would need to add the widget via the Legacy widget block. It was hit-and-miss. This exercise turned out to be a great test for the new block-based Widget screen, which will come to a WordPress instance near you in the 5.8 release on July 20th, 2021. </p>\n\n\n\n<p>From the discussions, I learned that the Gutenberg team is leaning towards an opt-out rather than an opt-in implementation. Testing sites with this week&#8217;s <a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/">WordPress 5.8 Beta 1</a>, is definitely recommended. If you don&#8217;t have time to test all the site you are working on, rest easy, there is a <a href="https://wordpress.org/plugins/classic-widgets/">Classic Widget plugin</a> you can install to keep the old Widget screen.  </p>\n\n\n\n<p>What else happened this week? <strong>WordCamp Europe! </strong>It was a great virtual conference. Kudos to the organizers, speakers, sponsors and attendees! If you missed it, you can watch the <a href="https://www.youtube.com/channel/UCaYQGYDpXpU4A17kxN-AgJQ">recordings on YouTube.</a></p>\n\n\n\n<p>The video with the <a href="https://wordpress.org/news/2021/06/gutenberg-highlights/"><strong>Gutenberg Highlights</strong></a> is available for those of use who missed the Conversation with Matt Mullenweg. <strong>Matias Ventura</strong> wrote: &#8220;The video is wonderfully narrated by&nbsp;<strong>Beatriz Fialho</strong>, and it was a great opportunity to celebrate all the incredible work that contributors are doing around the globe to improve the editing and customization experience of WordPress&#8221;. I will <a href="https://gutenbergtimes.com/wordcamp-europe-2021-starts-monday/">update my earlier WCEU post </a>with links to videos and resources over the course of next week. </p>\n\n\n\n<p>As always, I am so glad you are here, reading the eNews every week. Thank you! </p>\n\n\n\n<p>Yours, 💕<br />Birgit</p>\n\n\n\n\n\n<div class="wp-block-group has-primary-color has-light-background-background-color has-text-color has-background"><div class="wp-block-group__inner-container">\n<p class="has-normal-font-size"><strong><a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA">Join us for our next Live Q &amp; A</a> </strong>on <strong>June 24, 2021, at 11am EDT / 15:00 UTC</strong></p>\n\n\n\n<a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA"><img /></a>\n\n\n\n<p><strong><a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA">Theme.json for Theme Authors or building themes for full-site editing in WordPress.</a></strong><br /><strong>Host</strong>: Birgit Pauli-Haack<br /><strong>Panel:</strong>&nbsp;Daily Olson, Tammie Lister and Jeff Ong           <span class="has-inline-color"><strong><a href="https://us02web.zoom.us/webinar/register/8816229019893/WN_gyOVb1h4S4iO_UZi1GMQaA">Register Now</a></strong></span></p>\n</div></div>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<h2>WordPress 5.8 Release Cycle</h2>\n\n\n\n<p><a href="https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/">WordPress 5.8 Beta 1</a> was release on Tuesday. You can use the official  <a href="https://wordpress.org/plugins/wordpress-beta-tester/">Beta Tester Plugin </a>to test this version. If you haven&#8217;t used it before, the Core Team share information and <a href="https://make.wordpress.org/core/handbook/testing/beta-testing/">instructions in their handbook</a>.</p>\n\n\n\n<p>You can read more about the <a href="https://make.wordpress.org/core/5-8/">development cycle of WordPress 5.8 here</a>. Feature Freeze for this upcoming version was May 25. We are right now in the beta phase of the cycle. It will be used for testing and to fix bugs. That is to last until June 29, 2021, when the first Release Candidate will be released.  That&#8217;s also the deadline for Dev Notes and Field Guide. It also comes with a hard-string freeze. That&#8217;s the moment the Polyglots team starts with translations. </p>\n\n\n\n<h3>Features and updates for WordPress 5.8</h3>\n\n\n\n<p>Speaking of <strong>DevNotes</strong>, the Gutenberg team tracks their progress on the  DevNotes via <a href="https://github.com/WordPress/gutenberg/issues/32365">this GitHub issue.</a>  You can get a head start on <a href="https://gist.github.com/gziolo/cbea77500316a243e445d509ced3c231"><strong>&#8220;Block API Enhancements&#8221;</strong></a> by <strong>Grzegorz Ziolkowski</strong> or <strong><a href="https://github.com/WordPress/gutenberg/issues/32365#issuecomment-853726663">&#8220;Contextual patterns for easier creation and block transformations&#8221;</a> </strong>by <strong>Nik Tsekouras</strong> before they are published on the Make Core blog. </p>\n\n\n\n<p><strong>Anne McCarthy</strong> posted about other <strong>Block Editor Enhancements:</strong> </p>\n\n\n\n<ul><li><a href="https://make.wordpress.org/core/2021/05/20/core-editor-improvement-contextual-patterns-for-easier-creation/">Contextual patterns for easier creation</a>  and </li><li>How to <a href="https://make.wordpress.org/core/2021/06/09/core-editor-improvement-improve-your-workflow-with-list-view/">improve your workflow with List View</a>, the former Block Navigator feature. </li></ul>\n\n\n\n<p>On the WordPress News Blog, you found earlier: <a href="https://wordpress.org/news/2021/05/coloring-your-images-with-duotone-filters/"><strong>Coloring Your Images With Duotone Filters</strong></a> by <strong>Alex Lende</strong>. Yes, I am in love with it, that&#8217;s why I mentioned it again. Gutenberg 10.7 also brought the methods to <strong>disable  duotone </strong>via the theme.json file. <a href="https://github.com/WordPress/gutenberg/pull/32002">The details are in this Lende&#8217;s PR</a>. </p>\n\n\n\n<p><strong>Adam Silverstein</strong> published <a href="https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/">WordPress 5.8 adds WebP support</a> dev note. It&#8217;s not directly a block editor update but crucial for content creators and developers alike, especially in context of the Core Web Vitals when speed is becomes of the essence. </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<h2>Gutenberg Changelog</h2>\n\n\n\n<p>It&#8217;s been two years since Mark Uraine and I started the <a href="https://gutenbergtimes.com/podcast">Gutenberg Changelog</a> podcast, and he was my co-host for the first 40 episodes. Grzegorz Ziolkowski joined me as co-host with episode 41. In February 2021, we celebrated the first 10,000 downloads. Now four months later, we passed the 26,000 mark of downloads. For such a narrow niche show, these are mind-boggling numbers.  It is very humbling.  We are very grateful for our faithful listeners! Thank you all very much. </p>\n\n\n\n<p><strong>Grzegorz Ziolkowski</strong> is back from vacation, and we recorded episode 45. We covered Gutenberg 10.7 and 10.8 releases, WordCamp Europe and WordPress 5.8.  It will be published later this weekend. The similar t-shirts? Mere coincidence! </p>\n\n\n\n<img />\n\n\n\n<h2>Gutenberg 10.8</h2>\n\n\n\n<p><strong>Gutenberg 10.8</strong> was released this week. It had quite a few enhancements, and a ton of bug fixes and underlying code change for quality and tooling. <strong>Sandip Mondal</strong> work on his first release and published the release notes: <a href="https://make.wordpress.org/core/2021/06/10/whats-new-in-gutenberg-10-8-9-june/"><strong>What’s new in Gutenberg 10.8? (9 June)</strong></a>. </p>\n\n\n\n<p>Justin Tadlock has more details <strong><a href="https://wptavern.com/gutenberg-10-8-adds-new-typography-controls-and-block-previews">Gutenberg 10.8 Adds New Typography Controls and Block Previews</a></strong></p>\n\n\n\n<p>The enhancements for full-site editing and theme design controls are already for the next WordPress release (5.9) in December and require more testing before they are available for WordPress Core. </p>\n\n\n\n<h2>Block Patterns</h2>\n\n\n\n<p><strong>Kjell Reigstad</strong> posted an invitation for the WordPress community to submit Block Patterns to the official WordPress directory. In his post <a href="https://make.wordpress.org/design/2021/06/08/initial-patterns-for-the-wordpress-org-patterns-directory/"><strong>Initial Patterns for the WordPress.org Patterns Directory</strong></a>, he explained the details of the submission process.  </p>\n\n\n\n<p><strong>Justin Tadlock</strong>, a big fan of block patterns, wrote about the invitation on the <a href="https://wptavern.com/open-invitation-to-contribute-to-the-wordpress-block-pattern-directory">WordPress Tavern </a>and showcased some of his creations. <strong>Ana Segota, </strong>co-founder of <a href="https://www.anarieldesign.com/">Anariel Design</a> shared <a href="https://twitter.com/Ana_Segota/status/1402688373421187080">her submissions via Twitter.</a> </p>\n\n\n\n<p>You can <a href="https://github.com/WordPress/pattern-directory/issues?q=is%3Aissue+label%3A%22%5BType%5D+Pattern+Submission%22+is%3Aclosed"><strong>review the list of submissions on GitHub</strong></a> and learn from the comments on by the design team. Brian Gardner, Tammie Lister, Mel Choyce, Kjell Reigstad and Beatriz Fialho also contributed patterns to the directory. </p>\n\n\n\n<a href="https://wordpress.org/patterns"><img /></a><a href="https://wordpress.org/patterns">Block Patterns on WordPress.org</a> submitted by members of the design team and from the WordPress community. \n\n\n\n<p class="is-style-default">In total, I counted 54 block patterns available to WordPress users. What a great start! </p>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<h2>Full Site Editing</h2>\n\n\n\n<p>At WordCamp Europe 2021, the Panelist <strong>Danielle Zarcaro, Grzegorz Ziółkowski, Koen Van den Wijngaert and Milana Cap</strong> discussed Full Site editing and what it means for the broader WordPress community. <a href="https://gutenbergtimes.com/wordcamp-europe-full-site-editing-panel-discussion/"><strong>We have the recording and the transcript for you</strong></a></p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p>We added the Blockbase Theme to the list of<a href="https://gutenbergtimes.com/themes-for-full-site-editing-and-getting-ready-for-wordpress-5-8-weekend-edition-172/#fsethemes"> available FSE themes</a> last week. <strong>Kjell Reigstad</strong> published <a href="https://themeshaper.com/2021/06/07/using-blockbase-for-a-theme-experiment/">Using Blockbase for a theme&nbsp;experiment</a> on the ThemeShaper blog and take you on a journey on creating a child theme of Blockbase. He wrote &#8220;Overall, I found that the benefit to using Blockbase was peace of mind. Compared to starting fresh or using&nbsp;<code>emptytheme</code>, Blockbase ensured that I had a fully functional block theme immediately.&#8221; Kjell also shared his code on GitHub.</p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p>The <strong>WPMarmite Team</strong> publish the results of their <a href="https://wpmarmite.com/en/fse-study/"><strong>Full Site Editing Study: Will WordPress theme shops embrace this new paradigm?</strong></a> They studied the involvement in the current FSE development of 127 Theme shops.  </p>\n\n\n\n<p>At first glance, these seemed to be a little premature, considering that only architecture for themes supporting FSE is coming to WordPress at the end of July. It certainly sets the base numbers to see what will happen until December. These are the numbers to watch changing in the next half year, and it will answer the original questions. </p>\n\n\n\n<ul><li><strong>57%</strong>&nbsp;of theme shops&nbsp;<strong>feature their Gutenberg compatibility</strong>.</li><li>Only&nbsp;<strong>17%</strong>&nbsp;of theme shops&nbsp;<strong>offer custom Gutenberg blocks</strong>.</li><li><strong>3%</strong>&nbsp;of theme shops&nbsp;<strong>provide block patterns</strong>.</li></ul>\n\n\n\n<p>The team also talked to 22 theme shops about their intentions regards full-site editing.  <a href="https://wpmarmite.com/en/fse-study/">You need to read the article to learn more</a>.  </p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<p><strong>Fränk Klein</strong> at WPDeveloper Courses, released his new course: <a href="https://wpdevelopment.courses/courses/building-block-based-themes/"><strong>Building Block-Based Themes</strong></a>. If you want to learn how to build a real-life example theme and all the ins and outs for a theme using the full-site editing capabilities and theme.json.  </p>\n\n\n\n<p>On Fullsiteediting.com, <strong>Carolina Nymark</strong> has been offering her <a href="https://fullsiteediting.com/courses/full-site-editing-for-theme-developers/">Full Site editing course</a> for free, but that might change soon. </p>\n\n\n\n<p><strong>Joe Casabona</strong> at <a href="https://creatorcourses.com/">CreatorCourses </a>is also working on an update of his Gutenberg Theme course. </p>\n\n\n\n<p>My take-away from the acquisitions of Atomic Blocks, Co Blocks etc. is that early adopters found it quite worth their while to deal with the ever-moving goal posts while developing along site Gutenberg developers.  The future is yours! </p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<h2 id="events">Upcoming WordPress Events</h2>\n\n\n\n<p><strong>June 6, 2021</strong> <strong>7:00 pm EDT / 23:00 UTC</strong><br /><strong><a href="https://www.meetup.com/Philadelphia-WordPress-Meetup-Group/events/278507419/">WordPress Meetup Philadelphia</a></strong><br />Full Site Editing Review and Test-a-thon</p>\n\n\n\n<p><strong>June 7 &#8211; 9th, 2021</strong><br /><strong><a href="https://europe.wordcamp.org/2021/">WordCamp Europe</a></strong><br />A virtual event and contributor day. <a href="https://europe.wordcamp.org/2021/call-for-sponsors/">Call for sponsors is open.</a></p>\n\n\n\n<p><strong>🎉</strong>  Gutenberg Times is a media partner of WordCamp Europe 2021 </p>\n\n\n\n<p><strong>June 10th, 2021</strong><br /><strong><a href="https://www.meetup.com/SF-WordPress-Users/events/278491308">WordPress &#8220;Mega Meetup&#8221;: Plugins That Keep Websites Running</a></strong></p>\n\n\n\n<p><strong>June 20 &#8211; 26, 2021</strong><br /><strong><a href="https://japan.wordcamp.org/2021/">WordCamp Japan</a></strong><br /><em>The schedule has been posted. Most sessions will be in Japanese, with exceptions, I think&#8230; </em></p>\n\n\n\n<p><strong>June 24, 2021 </strong><br /><strong><a href="https://attend.wpengine.com/summit-us-2021/">WPEngine Summit 2021</a></strong><br /><em>The digital breakthrough conference</em> <a href="https://events.wpengine.com/event/fd217870-fc78-46d2-8c5e-96c85e6e371c/websitePage:645d57e4-75eb-4769-b2c0-f201a0bfc6ce?environment=P2&tm=nSwmA1-ZyLXwe2wM80Vzve3wDjKBWeqKrHbJFivPV4o&locale=en-US">released their schedule</a>. Personally, I am very much looking forward to the Keynote talk with <strong>Reshma Saujani</strong>, founder of Girls Who Code and Marshall Plan for Moms at 12:55 EDT / 16:55 UTC.  I also hope to see talks with Rob Stinson, Carrie Dils and Chris Wiegman. There are also deep dive talks listed into Headless WordPress. Enterprise WordPress is definitely heading down that route. </p>\n\n\n\n<p><strong>June 24 &#8211; 26, 2021</strong><br /><strong><a href="https://cochabamba.wordcamp.org/2021/">WordCamp Cochabama</a></strong> (Colombia) </p>\n\n\n\n<p><strong>July 17 + 18th, 2021</strong><br /><strong><a href="https://santaclarita.wordcamp.org/2021/">WordCamp Santa Clarita</a></strong><br />Calls for speakers ends TODAY! </p>\n\n\n\n<p><strong>July 23, 2021</strong><br /><a href="https://www.wordfest.live/"><strong>WordFest Live </strong></a>&#8211; <em>The&nbsp;</em>festival of WordPress</p>\n\n\n\n<p>A<strong>ugust 6 + 7, 2021</strong><br /><a href="https://nicaragua.wordcamp.org/2021/"><strong>WordCamp Nicaragua</strong></a></p>\n\n\n\n<p><strong>September 21 + 22, 2021</strong><br /><a href="https://2021.wpcampus.org/"><strong>WPCampus 2021 Online</strong></a><br />&#8220;A free online conference for web accessibility and WordPress in higher education.&#8221;</p>\n\n\n\n<hr class="wp-block-separator" id="block-ee0670b9-9b56-410a-a5c8-1febc106dca5" />\n\n\n\n<p id="block-8c56f083-3d78-42e0-84ec-62ea90a2afa5">On the<a href="https://wpcalendar.io/online/"> <strong>Calendar for WordPress Online Events</strong> </a>you can browse a list of the upcoming WordPress Meetups, around the world, including WooCommerce, Elementor, Divi Builder and Beaver Builder meetups.</p>\n\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p class="has-text-align-center"><strong>Don&#8217;t want to miss the next Weekend Edition? </strong></p>\n\n\n\n<form class="wp-block-newsletterglue-form ngl-form ngl-portrait" action="https://gutenbergtimes.com/feed/" method="post"><div class="ngl-form-container"><div class="ngl-form-field"><label class="ngl-form-label" for="ngl_email">Type in your Email address to subscribe.</label><div class="ngl-form-input"><input type="email" class="ngl-form-input-text" name="ngl_email" id="ngl_email" /></div></div><button class="ngl-form-button">Subscribe</button><p class="ngl-form-text">We hate spam, too and won&#8217;t give your email address to anyone except Mailchimp to send out our Weekend Edition</p></div><div class="ngl-message-overlay"><div class="ngl-message-svg-wrap"></div><div class="ngl-message-overlay-text">Thanks for subscribing.</div></div><input type="hidden" name="ngl_list_id" id="ngl_list_id" value="26f81bd8ae" /><input type="hidden" name="ngl_double_optin" id="ngl_double_optin" value="yes" /></form>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n\n<p>Featured Image: <a href="https://unsplash.com/@xavi_cabrera?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Photo by&nbsp;</a><a href="https://unsplash.com/@pawel_czerwinski?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Pawel Czerwinski</a>&nbsp;on&nbsp;<a href="https://unsplash.com/s/photos/blocks-of-flats?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</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, 12 Jun 2021 18:39: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:18:"Birgit Pauli-Haack";s: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:68:"Gutenberg Times: WordCamp Europe: Full-Site Editing Panel discussion";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"https://gutenbergtimes.com/?p=18145";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:78:"https://gutenbergtimes.com/wordcamp-europe-full-site-editing-panel-discussion/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:43875:"<p>It was announced as a discussion panel about the present and future of WordPress with Full Site Editing.</p>\n\n\n\n<p>The panelists, highly involved in this new feature, discussed many topics about FSE and how it is going to be a new revolution in the WordPress ecosystem.</p>\n\n\n\n<p>The Panelist were <a href="https://europe.wordcamp.org/2021/speaker/danielle-zarcaro/">Danielle Zarcaro</a>, <a href="https://europe.wordcamp.org/2021/speaker/grzegorz-ziolkowsk/">Grzegorz Ziółkowski</a>, <a href="https://europe.wordcamp.org/2021/speaker/koen-van-den-wijngaert/">Koen Van den Wijngaert</a> and <a href="https://europe.wordcamp.org/2021/speaker/milana-cap/">Milana Cap</a></p>\n\n\n\n<p>Jose Ramon Padron and Lesley Molecke moderated the discussion. </p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<div class="toolbelt-video-wrapper"></div>\n</div>\n\n\n\n<p>Torque Magazine did an outstanding job live tweeting. </p>\n\n\n\n<div class="wp-block-embed__wrapper">\n<blockquote class="twitter-tweet"><p lang="en" dir="ltr">"With FSE a theme developer can develop with a more solid foundation. More of their time and energy can be spent building things that have more value for their customers" <a href="https://twitter.com/vdwijngaert?ref_src=twsrc%5Etfw">@vdwijngaert</a></p>&mdash; Torque (@TheTorqueMag) <a href="https://twitter.com/TheTorqueMag/status/1401945858598338562?ref_src=twsrc%5Etfw">June 7, 2021</a></blockquote>\n</div>\n\n\n\n<p class="has-large-font-size" id="0-the-transcript-and-table-of-contents"><strong>The transcript and table of contents</strong></p>\n\n\n\n<div class="wp-block-sortabrilliant-guidepost"><ul><li><a href="https://gutenbergtimes.com/feed/#0-introduction-of-the-topic-and-the-panelists">Introduction of the topic and the panelists</a></li><li><a href="https://gutenbergtimes.com/feed/#1-what-is-full-site-editing-and-where-did-it-come-from-nbsp">What is full site editing and where did it come from?</a></li><li><a href="https://gutenbergtimes.com/feed/#2-what-problem-does-full-site-editing-solve">What problem does Full-Site Editing solve?</a></li><li><a href="https://gutenbergtimes.com/feed/#3-what-happens-to-websites-that-are-live-in-production-when-word-press-5-8-is-released">What happens to websites that are live (in production) when WordPress 5.8 is released?</a></li><li><a href="https://gutenbergtimes.com/feed/#4-what-does-full-site-editing-change-for-the-various-word-press-stakeholders">What does Full Site Editing change for the various WordPress stakeholders </a></li><li><a href="https://gutenbergtimes.com/feed/#5-why">Why will Full-Site Editing be in Core and not a plugin?</a></li><li><a href="https://gutenbergtimes.com/feed/#6-w">What will be the role of existing page builders?</a></li><li><a href="https://gutenbergtimes.com/feed/#7-what-is-going-to-happen-with-the-rest-of-the-open-source-solutions-like-joomla-drupal">What is going to happen with the rest of the open-source solutions like Joomla, Drupal?</a></li></ul></div>\n\n\n\n<hr class="wp-block-separator is-style-wide" />\n\n\n\n<p><em>José Ramón Padron:</em> Hello, Lesley.</p>\n\n\n\n<p><em>Lesley Molecke:</em> Hey, Moncho.</p>\n\n\n\n<p><em>José Ramón Padron:</em> I&#8217;m laughing, because this is the moment my neighbor started to do this at home. I don&#8217;t know. I hope it doesn&#8217;t sound through the microphone, but I&#8217;m hearing a hammer quite hard on that building. I hope it&#8217;s not-</p>\n\n\n\n<p><em>Lesley Molecke:</em> I can&#8217;t hear anything, but listen, I&#8217;m ready for this next session. I can&#8217;t believe that we&#8217;re already here. It&#8217;s already the final session of the day, and it&#8217;s going to be a good one.&nbsp;</p>\n\n\n\n<h2 id="0-introduction-of-the-topic-and-the-panelists">Introduction of the topic and the panelists</h2>\n\n\n\n<p><em>José Ramón Padron:</em> Yes, it&#8217;s true. It&#8217;s going to be a good one, because we have a lot of good people talking about a quite good and hot topic inside the WordPress community. One of the things we are going to have, really near in, I don&#8217;t know, in 5.8, in the next version of WordPress, full site editing?</p>\n\n\n\n<p><em>Lesley Molecke:</em> Yes. We would like to welcome our panelists. This is a panel presentation, so it should be a good conversation with a number of experts speaking. So they will join us here on stage in just a moment. Hello, hello. Hi, everybody.&nbsp;</p>\n\n\n\n<p><em>Grzegorz Ziółkowski:</em> Hello.</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> Hello, there.&nbsp;</p>\n\n\n\n<p><em>Lesley Molecke:</em> Will you please introduce yourselves?&nbsp;</p>\n\n\n\n<p><em>Milana Cap:</em> Which order?</p>\n\n\n\n<p><em>Lesley Molecke:</em> As you wish.&nbsp;</p>\n\n\n\n<div class="wp-block-image is-style-rounded"><img />Milana Cap</div>\n\n\n\n<p><em>José Ramón Padron:</em> So let&#8217;s start with Milana, just for talking.</p>\n\n\n\n<p><em>Milana Cap: </em>Because I&#8217;m the loudest. Well, you said expert. I&#8217;m here just for the cookies and to bribe contributors to come to documentation. Also, I&#8217;m here as documentation team co-rep. And I&#8217;m the docs focus lead for a new release, 5.8. I should be knowing what&#8217;s happening, hopefully soon. I&#8217;m Milana from Serbia.&nbsp;</p>\n\n\n\n<p><em>Lesley Molecke:</em> How about you, Danielle?</p>\n\n\n\n<p><em>José Ramón Padron:</em> Thank you so much.</p>\n\n\n\n<p><em>Danielle Zarcaro:</em> Sure. I&#8217;m having an issue too. I don&#8217;t know whether he&#8217;s blowing leaves or mowing the lawn? I don&#8217;t know what&#8217;s happening.&nbsp;</p>\n\n\n\n<div class="wp-block-image is-style-rounded"><img />Danielle Zarcaro</div>\n\n\n\n<p><em>Lesley Molecke:</em> We can&#8217;t hear it, it&#8217;s okay.</p>\n\n\n\n<p><em>Danielle Zarcaro:</em> Good. I&#8217;m Danielle. I&#8217;m from the US. I am the head of paperback web development. We build custom WordPress websites and maintain them, and maintain existing websites, and all that that comes with. We just launched overnightwebsite.com. So that&#8217;s mostly what I deal with is the old and the new of WordPress. So it&#8217;s the whole range.</p>\n\n\n\n<p><em>José Ramón Padron:</em> Thanks, Danielle. Let&#8217;s go with Koen.</p>\n\n\n\n<div class="wp-block-image is-style-rounded"><img /><em>Koen Van den Wijngaert</em></div>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> Hey, hi, there. Is this thing on? Hey, Good evening. I&#8217;m Koen. I&#8217;m a WordCamp and meetup organizer from Belgium. I run my own company called NEOK IT, where I provide software consultancy, partly around WordPress. I&#8217;ve been working with WordPress for a few years now. I like to learn things, as well as challenge myself while doing it.&nbsp;</p>\n\n\n\n<p>So for a while now, I&#8217;ve been casually contributing to Gutenberg, as a way of giving back and mostly getting more accustomed to the ins and outs of the project. So that&#8217;s me.&nbsp;</p>\n\n\n\n<div class="wp-block-image is-style-rounded"><img src="https://i1.wp.com/pbs.twimg.com/profile_images/1047874472403845121/ckX4uiBZ_400x400.jpg?resize=203%2C203&ssl=1" alt="Image" width="203" height="203" /><em>Grzegorz Ziółkowsk</em></div>\n\n\n\n<p><em>Grzegorz Ziółkowski:</em> It looks like it&#8217;s me now. So my name is Grzegorz Ziółkowski. I live in Oleśnica, Poland, and I work at Automatic, where I spend all time contributing to the WordPress core. My main focus is Gutenberg. I was helping to merge changes from the plugin, Gutenberg plugin to the WordPress core for the upcoming WordPress 5.8 release, which won&#8217;t contain all the necessary pieces of the full site editing. However, there is a lot of new goodies coming that will be ready to use on the site.&nbsp;</p>\n\n\n\n<p><em>Lesley Molecke:</em> Excellent. So Moncho and I have come up with a bunch of questions for you. They go from really basic, and then they work up and get more and more exciting and interesting. So we&#8217;re going to start with the first one, which is actually, this is my question, because I don&#8217;t know the answer to it yet and hopefully you will educate me. What is full site editing and where did it come from?&nbsp;</p>\n\n\n\n<h2 id="1-what-is-full-site-editing-and-where-did-it-come-from-nbsp">What is full site editing and where did it come from?</h2>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> Maybe if I can start, maybe the best thing to say at first is that full site editing is not just a big monolithic heap of a big function. It&#8217;s better to think of it as a collection of a lot of features that come with Gutenberg, as part of the second phase of the Gutenberg roadmap. Maybe someone else can pitch in now, so I don&#8217;t do a monologue.</p>\n\n\n\n<p><em>Grzegorz Ziółkowski:</em> If you don&#8217;t take a bigger picture, so full site editing is part of the Gutenberg project, there are four phases. And we are reaching this year, the end of phase two. The first one was introducing the building blocks for editing content. Now, we will be editing a full canvas of the sites. And the next two phases are collaborative editing. So to let people collaborate when they are changing websites or writing content. And the fourth one is multilingual support.</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> What everyone is waiting for, I believe. That&#8217;s going to be a big one.&nbsp;</p>\n\n\n\n<h2 id="2-what-problem-does-full-site-editing-solve">What problem does Full-Site Editing solve?</h2>\n\n\n\n<p><em>José Ramón Padron:</em> Anything else? Anything else? Because one of the things inside of Lesley&#8217;s question is, what problem does it solve? Which is, I think, very interesting. What do you think?</p>\n\n\n\n<p><em>Milana Cap:</em> I think that the problem it&#8217;s trying to solve is to give the user one unique workflow to edit everything. Because at this moment, you have post, you have page, and you go to block editor. Or if you are not brave enough, you&#8217;re still using classic editor and you edit your content there.&nbsp;</p>\n\n\n\n<p>But then you want to change your logo, then you have to go to customizer. But then you have some theme options. And it depends on theme from theme, what will you edit and where? I believe the idea is to release end user from need to know everything about the theme, you just go there and you just edit.&nbsp;</p>\n\n\n\n<p>And if you want to edit footer, and you&#8217;re on the post and you&#8217;re editing post, and then you realize the menu is not correct, you edit menu. You don&#8217;t need to know, because nobody cares is it customizer or whatever? People care to know where it is. And it&#8217;s a good thing that you can see how it looks on the front end, which I think was the initial idea for Gutenberg. But who knows? Maybe I&#8217;m wrong.</p>\n\n\n\n<p>I think that&#8217;s a huge problem that will be fixed, and solved with full site editing. For us who are building websites, I know that for every website, I have to create a ton of tutorials and everything, to show clients how to use it. And this will solve all that. So we will be out of job.</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> I also like to think that it brings a lot of power and more freedom and flexibility to end users of a website. Because in the traditional way of doing things, there&#8217;s a few ways one can have a WordPress website. He can have an agency, have a website built for him. Or he could be using some sort of a theme builder, or he could have installed a theme from the theme directory or maybe it&#8217;s even a custom theme.</p>\n\n\n\n<p>But now end users are able to have so much more power about editing templates, and editing all sorts of aspects of their website. I think that&#8217;s really exciting to look forward to.&nbsp;</p>\n\n\n\n<p><em>Danielle Zarcaro:</em> I think it solves a couple of problems, to add to that. It takes away some of the ambiguity around how to edit each individual thing. So WordPress&#8217;s whole thing is to democratize publishing. There were areas of the websites that were just not available to edit to anyone who doesn&#8217;t know code.&nbsp;</p>\n\n\n\n<p>So there&#8217;s the ease of use gap that came about, that you can&#8217;t edit the 404 page, you can&#8217;t edit the header or footer, unless an option is available. Is the theme using the site logo that you upload in WordPress, or you&#8217;re going to upload the image and then theme isn&#8217;t going to show it. It gets rid of those, however the theme developer decided to do it that day, and it streamlines a lot of that process to do some expected behavior to make it easier for anyone to hop into a site and edit it, and it democratizes publishing on a whole new level.&nbsp;</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> That&#8217;s a nice way of saying it. Yes. Because right now there&#8217;s this huge fragmented world of all different ways of themes that came up with our own way of editing site features and headers and customizing things. But there&#8217;s no real standard way of doing that. So it just makes it harder to step out of that particular ecosystem, I think. I&#8217;m looking forward to the standardized way of doing theming in WordPress.</p>\n\n\n\n<p><em>José Ramón Padron</em>: Grzegorz, I think you had something. Yes.</p>\n\n\n\n<p><em>Grzegorz Ziółkowski:</em> I wanted to add some more to it. Because I think it&#8217;s important to note that it&#8217;s not only about unifying everything, but it&#8217;s also to giving the power to users to change those little bits that annoy them, like the color of the header, or the font size.&nbsp;</p>\n\n\n\n<p>Before, you would have, or either learn CSS or learn HTML just to edit that. But now you will have tools that will allow that, and you won&#8217;t have to call your site administrator to do a simple change. So maybe you could tell that, remove the job from those people who maintain those sites, but on the other hand, they will have more time to work on expanding their offering and improving their own products or services, just to use the time.</p>\n\n\n\n<p>So this is something that sounds scary, but on the other hand, it opens a lot of possibilities. Because the idea of blocks also gives you the power that you can create your own blocks that you can use in several websites, and give additional functionality out of the box for your customers.</p>\n\n\n\n<h2 id="3-what-happens-to-websites-that-are-live-in-production-when-word-press-5-8-is-released">What happens to websites that are live (in production) when WordPress 5.8 is released?</h2>\n\n\n\n<p><em>José Ramón Padron:</em> So regarding that this is something new, something is going to happen from 5.8, as far as I know, what happens to the WordPress websites that are already live and in production? Must they be rebuilt in order to use full site editing? Or they&#8217;re going to work in the way they are?&nbsp;</p>\n\n\n\n<p><em>Milana Cap:</em> They have to be rebuilt completely. It will crash. No, it won&#8217;t.</p>\n\n\n\n<p><em>Koen Van den Wijngaert</em>: It will just crash when you update.&nbsp;</p>\n\n\n\n<p><em>Milana Cap:</em> No, it won&#8217;t.</p>\n\n\n\n<p><em>Lesley Molecke:</em>That&#8217;s big news.&nbsp;</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> Oh, we were not supposed to say that, sorry.</p>\n\n\n\n<p><em>Milana Cap:</em> No, they will not be crashed, they will not have to be rebuilt completely. As you all know, WordPress always build in mind with what is already out there, not to crash anything. And in 5.8, not everything will get in. So if I&#8217;m wrong, please correct me, but I think that in 5.8, you will have to install a Gutenberg plugin to actually use full site editing. So not everything will be there, but it will be foundation for the next releases when everything else will come in.&nbsp;</p>\n\n\n\n<p>But still, we will have some nice things coming in and nothing will break. You can go part by part and rebuilding it and adapting for a complete editing experience.&nbsp;</p>\n\n\n\n<p><em>José Ramón Padron:</em> Thanks, Milana. Anything to add ?</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> Maybe Grzegorz can do it.&nbsp;</p>\n\n\n\n<p><em>Grzegorz Ziółkowski:</em> You can go.&nbsp;</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> Okay, but you can just&#8230; Well, some of the full site editing features will be added to 5.8, I think, but Grzegorz will probably be able to say which one exactly. I&#8217;m hearing feedback.&nbsp;</p>\n\n\n\n<p><em>José Ramón Padron:</em> An echo. There is an echo.</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> So it&#8217;s not some monolithic feature, like we said before, but it&#8217;s more like a collection of features and they won&#8217;t be turned off all at once by default, by just upgrading to WordPress 5.8. You do need to have a full site editing team to enable all features, but some of them will also be available for non-block based themes.&nbsp;</p>\n\n\n\n<p>Things like the template editor blocks, the site logo, the tagline, the query blocks, posts, posts related blocks, like post title, post [inaudible 00:14:45], they will all be made available in the post editor. And as well as that, I think it was also possible to also not edit, but with add new templates to a normal theme and edit those in the template editor. It&#8217;s pretty awesome.&nbsp;</p>\n\n\n\n<p><em>Grzegorz Ziółkowski:</em> So the first step is to allow people to change, use the block-based paradigm on a single page. So think about that, about previously you would have to create a PHP file to change a single page view. And now you will be able to do that to through UI, and that will create an override that you would be able to delete later. But as a user, so it&#8217;s more like empowering people who have access to the sites, rather that&#8217;s a feature for the team designer.</p>\n\n\n\n<p>So that&#8217;s one thing. And everything like that is optional, so there will be a flag to disable that. So site owners or theme authors we will say that, &#8220;I don&#8217;t want that,&#8221; and they can remove that.&nbsp;</p>\n\n\n\n<p>The one big change is that not necessarily related to full site editing, but is somehow in the same area is the widget editor, which will be&#8230; I don&#8217;t know what&#8217;s the final decision, but it will be depending on the feedback from the testing, either an opt-in or opt-out.</p>\n\n\n\n<p>So the idea would be that you will be able to use the same blogs you use in your content to use also in site, when you would previously use widgets. So that&#8217;s a nice change. If you have your own custom blocks, you would be able to put there as well, which will open those new possibilities, and also somehow unify the interface.&nbsp;</p>\n\n\n\n<p>But as you could hear, there is a lot of new blocks coming. But it&#8217;s just addition, it&#8217;s not something that you have to use. It&#8217;s just there if you want to try them out, that will be perfect time to do that after 5.8 is out. And there is a-</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> That will be released tomorrow, by the way. So if you want to test it, please do so. It&#8217;s by a lot of users that can test and provide feedback on the new update that we can improve upon those things, and decide what can be added and what should be skipped. So go install it tomorrow.</p>\n\n\n\n<p><em>Lesley Molecke:</em>Yes, we should acknowledge that, that everyone here is actually working really hard right now to create the new release, while also attending WordCamp Europe and being here on this panel and contributing on track too, and y&#8217;all are everywhere. Thank you, thank you, thank you for your time.&nbsp;</p>\n\n\n\n<h2 id="4-what-does-full-site-editing-change-for-the-various-word-press-stakeholders">What does Full Site Editing change for the various WordPress stakeholders </h2>\n\n\n\n<p>My next question has to do with stakeholders. So obviously, a big change like this to WordPress has multiple stakeholder groups. It has the end users, the users of WordPress websites down the road. It has the editors of WordPress websites. It has the companies who build themes and the companies who build plugins, and the people who contribute, all of these different groups.&nbsp;</p>\n\n\n\n<p>I&#8217;m interested in talking about the theme creators who currently primarily rely on offering block patterns with their own header and footer and sidebar management. So how does that work with full site editing?</p>\n\n\n\n<p><em>Danielle Zarcaro:</em> Well, it works the same way. You can offer whatever you want. I think it&#8217;s a misconception that by giving the users the ability to do what they want means that they&#8217;ll be able to do anything they want. If you are someone like me who&#8217;s creating custom sites, you can actually more easy put options and make it so that you don&#8217;t have to install a whole extra plugin to add a couple of extra options. You reserve that for the bigger projects that you&#8217;re doing.</p>\n\n\n\n<p>And it&#8217;s up to the theme creators, if they&#8217;re creating a theme on a wider scale, instead of just an individual client, that&#8217;s up to them to decide how they want it to work. They just opt into stuff, they add stuff, they add their custom options, but it&#8217;s all working within the same ecosystem, and we&#8217;re all speaking the same language now instead.</p>\n\n\n\n<p>So if you don&#8217;t want to make it so that your header and your footer and your sidebars are manageable in the block editor or in full site editing, then I guess you don&#8217;t have to. You can hard code whatever you want, you can do that now, you don&#8217;t have to make any options available.&nbsp;</p>\n\n\n\n<p>But then at some point, you&#8217;re going to start to fall behind, in terms of what you&#8217;re able to do. So it&#8217;s going to work the same way, just with more possibilities. That&#8217;s how I go about looking at it.&nbsp;</p>\n\n\n\n<p><em>Koen Van den Wijngaert:</em> You&#8217;ll be able to turn off or on, or even tweak some of the configuration options just by providing a single JSON file for those things. But also, I like to think that with full site editing, a theme developer or theme designer can benefit from a more solid foundation that is standardized and optimized for things like accessibility, usability and performance.&nbsp;</p>\n\n\n\n<p>That way more of their time and energy can be spent into building things that actually add value to their customers, all the while benefiting from the existing full site editing features and even tweaking them to their liking. So that&#8217;s a big plus, I think. So they don&#8217;t have to go and reinvent the wheel every time they b