![\"Collins](\"https://i2.wp.com/wordpress.org/news/files/2021/12/fimg_collins-agbonghama.jpg?resize=632%2C318&ssl=1\")
Stay hungry. Stay foolish.\nMulti line blockquote with a cite reference:\n
\nmultiple contributors - MDN HTML element reference - blockquote\nThe HTML
<blockquote>Element (or HTML Block Quotation Element) indicates that the enclosed text is an extended quotation. Usually, this is rendered visually by indentation (see Notes for how to change it). A URL for the source of the quotation may be given using the cite attribute, while a text representation of the source can be given using the<cite>element.
| Employee | \nSalary | \n\n |
|---|---|---|
| John Saddington | \n$1 | \nBecause that\'s all Steve Job\' needed for a salary. | \n
| Tom McFarlin | \n$100K | \nFor all the blogging he does. | \n
| Jared Erickson | \n$100M | \nPictures are worth a thousand words, right? So Tom x 1,000. | \n
| Chris Ames | \n$100B | \nWith hair like that?! Enough said... | \n
.post-title {\n margin: 0 0 5px;\n font-weight: bold;\n font-size: 38px;\n line-height: 1.2;\n and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;\n}\nYou will learn later on in these tests that word-wrap: break-word; will be your best friend.\n\nDelete Tag\n\nThis tag will let you <s> instead).\n\nEmphasize Tag\n\nThe emphasize tag should italicize text.\n\nHorizontal Rule Tag\n\n<hr /> tag.\n\nInsert Tag\n\nThis tag should denote inserted text.\n\nKeyboard Tag\n\nThis scarcely known tag emulates keyboard text, which is usually styled like the <code> tag.\n\nPreformatted Tag\n\nThis tag is for preserving whitespace as typed, such as in poetry or ASCII art.\n\nRobert Frost\n\n Two roads diverged in a yellow wood,\n And sorry I could not travel both (\\_/)\n And be one traveler, long I stood (=\'.\'=)\n And looked down one as far as I could (\")_(\")\n To where it bent in the undergrowth;\n\n Then took the other, as just as fair,\n And having perhaps the better claim, |\\_/|\n Because it was grassy and wanted wear; / @ @ \\\n Though as for that the passing there ( > º < )\n Had worn them really about the same, `>>x<<´\n / O \\\n And both that morning equally lay\n In leaves no step had trodden black.\n Oh, I kept the first for another day!\n Yet knowing how way leads on to way,\n I doubted if I should ever come back.\n\n I shall be telling this with a sigh\n Somewhere ages and ages hence:\n Two roads diverged in a wood, and I—\n I took the one less traveled by,\n And that has made all the difference.\n\n\n and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;\n\n\nQuote Tag for short, inline quotes\n\n
Developers, developers, developers...--Steve Ballmer\n\nSubscript Tag\n\nGetting our science styling on with H2O, which should push the \"2\" down.\n\nSuperscript Tag\n\nStill sticking with science and Albert Einstein\'s E = MC2, which should lift the 2 up.', 0, '1', '', 'comment', 0, 0), (8, 1148, 'Anonymous User', 'fake@example.com', '', '', '2013-03-11 23:45:54', '2013-03-12 04:45:54', 'This user it trying to be anonymous.\n\n\n They used a fake email, so there should be no Gravatar associated with it.\n They did not speify a website, so there should be no link to it in the comment.\n', 0, '1', '', 'comment', 0, 0), (9, 1148, 'Jane Doe', 'example@example.org', 'http://example.org/', '', '2013-03-12 13:17:35', '2013-03-12 20:17:35', 'Comments? I love comments!', 0, '1', '', 'comment', 0, 0), (10, 1148, 'John Γιανης Doe Κάποιος', 'example@example.org', 'http://example.org', '', '2013-03-14 07:53:26', '2013-03-14 14:53:26', 'These tests are amazing!', 0, '1', '', 'comment', 0, 0), (11, 1148, 'themedemos', 'themeshaperwp+demos@gmail.com', 'https://wpthemetestdata.wordpress.com/', '', '2013-03-14 07:56:46', '2013-03-14 14:56:46', 'Author Comment.', 0, '1', '', 'comment', 0, 0), (12, 1148, 'John Κώστας Doe Τάδε', 'example@example.org', 'http://example.org/', '', '2013-03-14 07:57:01', '2013-03-14 14:57:01', 'Comment Depth 01', 0, '1', '', 'comment', 0, 0), (13, 1148, 'Jane Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:01:21', '2013-03-14 15:01:21', 'Comment Depth 02', 0, '1', '', 'comment', 12, 0), (14, 1148, 'Fred Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:02:06', '2013-03-14 15:02:06', 'Comment Depth 03', 0, '1', '', 'comment', 13, 0), (15, 1148, 'Fred Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:03:22', '2013-03-14 15:03:22', 'Comment Depth 04', 0, '1', '', 'comment', 14, 0), (16, 1148, 'themedemos', 'themeshaperwp+demos@gmail.com', 'https://wpthemetestdata.wordpress.com/', '', '2013-03-14 08:10:29', '2013-03-14 15:10:29', 'Comment Depth 05\n\nAlso an author comment.', 0, '1', '', 'comment', 15, 0), (17, 1148, 'Jane Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:12:16', '2013-03-14 15:12:16', 'Comment Depth 06 has some more text than some of the other comments on this post.', 0, '1', '', 'comment', 16, 0), (18, 1148, 'Joe Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:12:58', '2013-03-14 15:12:58', 'Comment Depth 07 has a little bit.', 0, '1', '', 'comment', 17, 0), (19, 1148, 'Jane Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:13:42', '2013-03-14 15:13:42', 'Comment Depth 08', 0, '1', '', 'comment', 18, 0), (20, 1148, 'Joe Bloggs', 'example@example.org', 'http://example.org/', '', '2013-03-14 08:14:13', '2013-03-14 15:14:13', 'Comment Depth 09 is way nested, but there are a lot of sites with very nested comments.', 0, '1', '', 'comment', 19, 0), (21, 1148, 'themedemos', 'themeshaperwp+demos@gmail.com', 'https://wpthemetestdata.wordpress.com/', '', '2013-03-14 08:14:47', '2013-03-14 15:14:47', 'Comment Depth 10\n\nAlso an author comment.', 0, '1', '', 'comment', 20, 0), (22, 1148, 'Jane Doe', 'example@example.org', 'http://example.org/', '', '2013-03-14 09:56:43', '2013-03-14 16:56:43', 'Image comment.\n
![\"Albany](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc20050102_192118_51.jpg?w=171&h=128\")
\n If the image imports...\n ', 0, '1', '', 'comment', 0, 0),
(23, 1148, 'John Μαρία Doe Ντουε', 'example@example.org', 'http://example.org/', '', '2013-03-14 11:23:24', '2013-03-14 18:23:24', 'We are totally going to blog about these tests Σίγουρα θα σχολιάσουμε τα τεστς!', 0, '1', '', 'comment', 0, 0),
(24, 1148, 'John Doe', 'example@example.org', 'http://example.org/', '', '2013-03-14 11:27:54', '2013-03-14 18:27:54', 'We use these tests all the time! Killer stuff!', 0, '1', '', 'comment', 0, 0),
(25, 1148, 'Jane Doe', 'example@example.org', 'http://example.org/', '', '2013-03-14 11:30:33', '2013-03-14 18:30:33', 'Thanks for all the comments, everyone!', 0, '1', '', 'comment', 0, 0),
(26, 1148, 'auser', 'auser@example.com', '', '', '2014-09-29 02:52:15', '2014-09-29 09:52:15', 'this is test comment\n\n Feeling testy?', 0, '0', '', 'comment', 0, 0),
(27, 1149, 'Ping 1 « What’s a tellyworth?', '', 'http://tellyworth.wordpress.com/2007/11/21/ping-1/', '', '2007-11-21 11:31:12', '2007-11-21 01:31:12', '[...] Trackback test. [...]', 0, '1', '', 'trackback', 0, 0),
(28, 1149, 'Ping 2 with a much longer title than the previous ping, which was called Ping 1 « What’s a tellyworth?', '', 'http://tellyworth.wordpress.com/2007/11/21/ping-2-with-a-much-longer-title-than-the-previous-ping-which-was-called-ping-1/', '', '2007-11-21 11:35:47', '2007-11-21 01:35:47', '[...] Another trackback test. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit gravida nisi. Praesent libero odio, tincidunt nec, fringilla et, mollis ut, ipsum. Proin a lacus quis nisi pulvinar bibendum. Donec massa justo, dapibus at, imperdiet vestibulum, dapibus in, leo. Donec pretium tellus in dui. Phasellus tristique aliquet justo. Donec sodales. Nulla urna mi, molestie ac, malesuada sit amet, sagittis id, lacus. Mauris auctor leo ac justo. Proin convallis. Nulla eleifend dictum mi. Donec at lectus. Integer augue sapien, ornare vitae, rhoncus quis, rhoncus sed, sapien. Nunc mattis diam sodales diam.Etiam porttitor, ante sed varius semper, ante arcu rutrum tortor, at luctus nunc urna id nibh. Fusce sodales. Integer sed ligula. Donec posuere, nibh aliquet auctor congue, augue est porttitor odio, imperdiet facilisis tortor urna vel mauris. Pellentesque pretium, lorem non pellentesque varius, elit diam ultrices mi, sed posuere sapien lectus sed mi. Donec vestibulum urna. Donec gravida elit et enim. Ut dignissim neque ut erat. Morbi tincidunt nunc vitae lorem. Morbi rhoncus mi. Praesent facilisis tincidunt enim. Ut pulvinar. Suspendisse potenti. Vivamus turpis odio, porta at, malesuada in, iaculis eget, odio. Aenean faucibus, urna quis congue dignissim, orci tellus ornare leo, eget viverra ante ipsum sit amet magna. Suspendisse mattis nunc at justo. Nullam malesuada lobortis lorem. Morbi ultricies. Nam risus erat, sagittis ut, tristique rhoncus, luctus id, ante. Maecenas ac dui. [...]', 0, '1', '', 'trackback', 0, 0),
(29, 1149, 'Ping 4 « What’s a tellyworth?', '', 'http://tellyworth.wordpress.com/2007/11/21/ping-4/', '', '2007-11-21 11:39:25', '2007-11-21 01:39:25', '[...] Another short one. [...]', 0, '1', '', 'pingback', 0, 0),
(30, 1149, 'Ping 3 « What’s a tellyworth?', '', 'http://tellyworth.wordpress.com/2007/11/21/ping-3/', '', '2007-11-21 11:38:22', '2007-11-21 01:38:22', '[...] Just a short one. [...]', 0, '1', '', 'pingback', 0, 0),
(31, 1149, 'John Doe', 'example@example.org', 'http://example.org/', '', '2010-06-11 15:27:04', '2010-06-11 22:27:04', 'This is a comment amongst pingbacks and trackbacks.', 0, '1', '', 'comment', 0, 0),
(32, 1168, 'Jane Doe', 'example@example.org', 'http://example.org/', '', '2013-03-14 11:56:08', '2013-03-14 18:56:08', 'This comment should not be visible until the password is entered.', 0, '1', '', 'comment', 0, 0),
(33, 1170, 'John Doe', 'example@example.org', 'http://example.org/', '', '2013-03-14 12:35:07', '2013-03-14 19:35:07', 'Having no content in the post should have no adverse effects on the layout or functionality.', 0, '1', '', 'comment', 0, 0);
-- --------------------------------------------------------
--
-- Table structure for table `perf_links`
--
CREATE TABLE `perf_links` (
`link_id` bigint UNSIGNED NOT NULL,
`link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_visible` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'Y',
`link_owner` bigint UNSIGNED NOT NULL DEFAULT '1',
`link_rating` int NOT NULL DEFAULT '0',
`link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`link_rel` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
-- --------------------------------------------------------
--
-- Table structure for table `perf_options`
--
CREATE TABLE `perf_options` (
`option_id` bigint UNSIGNED NOT NULL,
`option_name` varchar(191) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`option_value` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`autoload` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'yes'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
--
-- Dumping data for table `perf_options`
--
INSERT INTO `perf_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(1, 'siteurl', 'http://localhost:8080/wordpress', 'yes'),
(2, 'home', 'http://localhost:8080/wordpress', 'yes'),
(3, 'blogname', 'Satish Gandhams Test Site', 'yes'),
(4, 'blogdescription', 'Just another WordPress site', 'yes'),
(5, 'users_can_register', '0', 'yes'),
(6, 'admin_email', 'satish.iitg@gmail.com', 'yes'),
(7, 'start_of_week', '1', 'yes'),
(8, 'use_balanceTags', '0', 'yes'),
(9, 'use_smilies', '1', 'yes'),
(10, 'require_name_email', '1', 'yes'),
(11, 'comments_notify', '1', 'yes'),
(12, 'posts_per_rss', '10', 'yes'),
(13, 'rss_use_excerpt', '0', 'yes'),
(14, 'mailserver_url', 'mail.example.com', 'yes'),
(15, 'mailserver_login', 'login@example.com', 'yes'),
(16, 'mailserver_pass', 'password', 'yes'),
(17, 'mailserver_port', '110', 'yes'),
(18, 'default_category', '1', 'yes'),
(19, 'default_comment_status', 'open', 'yes'),
(20, 'default_ping_status', 'open', 'yes'),
(21, 'default_pingback_flag', '0', 'yes'),
(22, 'posts_per_page', '10', 'yes'),
(23, 'date_format', 'F j, Y', 'yes'),
(24, 'time_format', 'g:i a', 'yes'),
(25, 'links_updated_date_format', 'F j, Y g:i a', 'yes'),
(26, 'comment_moderation', '0', 'yes'),
(27, 'moderation_notify', '1', 'yes'),
(28, 'permalink_structure', '/%year%/%monthnum%/%day%/%postname%/', 'yes'),
(29, 'rewrite_rules', 'a:94:{s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:17:\"^wp-sitemap\\.xml$\";s:23:\"index.php?sitemap=index\";s:17:\"^wp-sitemap\\.xsl$\";s:36:\"index.php?sitemap-stylesheet=sitemap\";s:23:\"^wp-sitemap-index\\.xsl$\";s:34:\"index.php?sitemap-stylesheet=index\";s:48:\"^wp-sitemap-([a-z]+?)-([a-z\\d_-]+?)-(\\d+?)\\.xml$\";s:75:\"index.php?sitemap=$matches[1]&sitemap-subtype=$matches[2]&paged=$matches[3]\";s:34:\"^wp-sitemap-([a-z]+?)-(\\d+?)\\.xml$\";s:47:\"index.php?sitemap=$matches[1]&paged=$matches[2]\";s:47:\"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:42:\"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:23:\"category/(.+?)/embed/?$\";s:46:\"index.php?category_name=$matches[1]&embed=true\";s:35:\"category/(.+?)/page/?([0-9]{1,})/?$\";s:53:\"index.php?category_name=$matches[1]&paged=$matches[2]\";s:17:\"category/(.+?)/?$\";s:35:\"index.php?category_name=$matches[1]\";s:44:\"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:39:\"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:20:\"tag/([^/]+)/embed/?$\";s:36:\"index.php?tag=$matches[1]&embed=true\";s:32:\"tag/([^/]+)/page/?([0-9]{1,})/?$\";s:43:\"index.php?tag=$matches[1]&paged=$matches[2]\";s:14:\"tag/([^/]+)/?$\";s:25:\"index.php?tag=$matches[1]\";s:45:\"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:40:\"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:21:\"type/([^/]+)/embed/?$\";s:44:\"index.php?post_format=$matches[1]&embed=true\";s:33:\"type/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?post_format=$matches[1]&paged=$matches[2]\";s:15:\"type/([^/]+)/?$\";s:33:\"index.php?post_format=$matches[1]\";s:48:\".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$\";s:18:\"index.php?feed=old\";s:20:\".*wp-app\\.php(/.*)?$\";s:19:\"index.php?error=403\";s:18:\".*wp-register.php$\";s:23:\"index.php?register=true\";s:32:\"feed/(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:27:\"(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:8:\"embed/?$\";s:21:\"index.php?&embed=true\";s:20:\"page/?([0-9]{1,})/?$\";s:28:\"index.php?&paged=$matches[1]\";s:41:\"comments/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:36:\"comments/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:17:\"comments/embed/?$\";s:21:\"index.php?&embed=true\";s:44:\"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:39:\"search/(.+)/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:20:\"search/(.+)/embed/?$\";s:34:\"index.php?s=$matches[1]&embed=true\";s:32:\"search/(.+)/page/?([0-9]{1,})/?$\";s:41:\"index.php?s=$matches[1]&paged=$matches[2]\";s:14:\"search/(.+)/?$\";s:23:\"index.php?s=$matches[1]\";s:47:\"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:42:\"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:23:\"author/([^/]+)/embed/?$\";s:44:\"index.php?author_name=$matches[1]&embed=true\";s:35:\"author/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?author_name=$matches[1]&paged=$matches[2]\";s:17:\"author/([^/]+)/?$\";s:33:\"index.php?author_name=$matches[1]\";s:69:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:45:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$\";s:74:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]\";s:39:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$\";s:63:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]\";s:56:\"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:51:\"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:32:\"([0-9]{4})/([0-9]{1,2})/embed/?$\";s:58:\"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true\";s:44:\"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]\";s:26:\"([0-9]{4})/([0-9]{1,2})/?$\";s:47:\"index.php?year=$matches[1]&monthnum=$matches[2]\";s:43:\"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:38:\"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:19:\"([0-9]{4})/embed/?$\";s:37:\"index.php?year=$matches[1]&embed=true\";s:31:\"([0-9]{4})/page/?([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&paged=$matches[2]\";s:13:\"([0-9]{4})/?$\";s:26:\"index.php?year=$matches[1]\";s:58:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:68:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:88:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:83:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:83:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:64:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:53:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/embed/?$\";s:91:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/trackback/?$\";s:85:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&tb=1\";s:77:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]\";s:72:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]\";s:65:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/page/?([0-9]{1,})/?$\";s:98:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&paged=$matches[5]\";s:72:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/comment-page-([0-9]{1,})/?$\";s:98:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&cpage=$matches[5]\";s:61:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)(?:/([0-9]+))?/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&page=$matches[5]\";s:47:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:57:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:77:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:72:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:72:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:53:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&cpage=$matches[4]\";s:51:\"([0-9]{4})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&cpage=$matches[3]\";s:38:\"([0-9]{4})/comment-page-([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&cpage=$matches[2]\";s:27:\".?.+?/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\".?.+?/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\".?.+?/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"(.?.+?)/embed/?$\";s:41:\"index.php?pagename=$matches[1]&embed=true\";s:20:\"(.?.+?)/trackback/?$\";s:35:\"index.php?pagename=$matches[1]&tb=1\";s:40:\"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:35:\"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:28:\"(.?.+?)/page/?([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&paged=$matches[2]\";s:35:\"(.?.+?)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&cpage=$matches[2]\";s:24:\"(.?.+?)(?:/([0-9]+))?/?$\";s:47:\"index.php?pagename=$matches[1]&page=$matches[2]\";}', 'yes'),
(30, 'hack_file', '0', 'yes'),
(31, 'blog_charset', 'UTF-8', 'yes'),
(32, 'moderation_keys', '', 'no'),
(33, 'active_plugins', 'a:1:{i:0;s:41:\"wordpress-importer/wordpress-importer.php\";}', 'yes'),
(34, 'category_base', '', 'yes'),
(35, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'),
(36, 'comment_max_links', '2', 'yes'),
(37, 'gmt_offset', '0', 'yes'),
(38, 'default_email_category', '1', 'yes'),
(39, 'recently_edited', '', 'no'),
(40, 'template', 'twentytwentyone', 'yes'),
(41, 'stylesheet', 'twentytwentyone', 'yes'),
(42, 'comment_registration', '0', 'yes'),
(43, 'html_type', 'text/html', 'yes'),
(44, 'use_trackback', '0', 'yes'),
(45, 'default_role', 'subscriber', 'yes'),
(46, 'db_version', '49752', 'yes'),
(47, 'uploads_use_yearmonth_folders', '1', 'yes'),
(48, 'upload_path', '', 'yes'),
(49, 'blog_public', '0', 'yes'),
(50, 'default_link_category', '2', 'yes'),
(51, 'show_on_front', 'posts', 'yes'),
(52, 'tag_base', '', 'yes'),
(53, 'show_avatars', '1', 'yes'),
(54, 'avatar_rating', 'G', 'yes'),
(55, 'upload_url_path', '', 'yes'),
(56, 'thumbnail_size_w', '150', 'yes'),
(57, 'thumbnail_size_h', '150', 'yes'),
(58, 'thumbnail_crop', '1', 'yes'),
(59, 'medium_size_w', '300', 'yes'),
(60, 'medium_size_h', '300', 'yes'),
(61, 'avatar_default', 'mystery', 'yes'),
(62, 'large_size_w', '1024', 'yes'),
(63, 'large_size_h', '1024', 'yes'),
(64, 'image_default_link_type', 'none', 'yes'),
(65, 'image_default_size', '', 'yes'),
(66, 'image_default_align', '', 'yes'),
(67, 'close_comments_for_old_posts', '0', 'yes'),
(68, 'close_comments_days_old', '14', 'yes'),
(69, 'thread_comments', '1', 'yes'),
(70, 'thread_comments_depth', '5', 'yes'),
(71, 'page_comments', '0', 'yes'),
(72, 'comments_per_page', '50', 'yes'),
(73, 'default_comments_page', 'newest', 'yes'),
(74, 'comment_order', 'asc', 'yes'),
(75, 'sticky_posts', 'a:1:{i:0;i:1241;}', 'yes'),
(76, 'widget_categories', 'a:0:{}', 'yes'),
(77, 'widget_text', 'a:0:{}', 'yes'),
(78, 'widget_rss', 'a:0:{}', 'yes'),
(79, 'uninstall_plugins', 'a:0:{}', 'no'),
(80, 'timezone_string', '', 'yes'),
(81, 'page_for_posts', '0', 'yes'),
(82, 'page_on_front', '0', 'yes'),
(83, 'default_post_format', '0', 'yes'),
(84, 'link_manager_enabled', '0', 'yes'),
(85, 'finished_splitting_shared_terms', '1', 'yes'),
(86, 'site_icon', '0', 'yes'),
(87, 'medium_large_size_w', '768', 'yes'),
(88, 'medium_large_size_h', '0', 'yes'),
(89, 'wp_page_for_privacy_policy', '3', 'yes'),
(90, 'show_comments_cookies_opt_in', '1', 'yes'),
(91, 'admin_email_lifespan', '1658571412', 'yes'),
(92, 'disallowed_keys', '', 'no'),
(93, 'comment_previously_approved', '1', 'yes'),
(94, 'auto_plugin_theme_update_emails', 'a:0:{}', 'no'),
(95, 'auto_update_core_dev', 'enabled', 'yes'),
(96, 'auto_update_core_minor', 'enabled', 'yes'),
(97, 'auto_update_core_major', 'enabled', 'yes'),
(98, 'wp_force_deactivated_plugins', 'a:0:{}', 'yes'),
(99, 'initial_db_version', '49752', 'yes'),
(100, 'perf_user_roles', 'a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:61:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:34:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:10:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:5:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}', 'yes'),
(101, 'fresh_site', '0', 'yes'),
(102, 'widget_block', 'a:6:{i:2;a:1:{s:7:\"content\";s:19:\"\";}i:3;a:1:{s:7:\"content\";s:154:\"The third Release Candidate (RC3) for WordPress 5.9 is here!
\n\n\n\nThank you to everyone who has contributed thus far toward testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated to land in just one week—on January 25, 2022. You still have time to help! Since RC2 arrived last week, testers have found and fixed two bugs, 14 fixes from Gutenberg. There has been one additional Gutenberg fix today.
\n\n\n\nYou can test the WordPress 5.9 release candidate in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nwp core update --version=5.9-RC3wp core update --version=5.9-RC3 --forceYour help to test the third Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users, developers, and the WordPress community.
\n\n\n\nThank you to all contributors who tested the RC2 release and gave feedback. Testing for bugs is a critical part of polishing every release and is a great way to contribute to WordPress.
\n\n\n\nHelp test WordPress 5.9 features – this post provides a guide to set up your testing environment, a list of testable features, and information about how to submit feedback you find as you go.
\n\n\n\nSkilled in languages other than English? Help translate WordPress into more than 100 languages! Thanks to every locale that is working on translations.
\n\n\n\nDevelopers and those interested in more background to the features can find more in the Field Guide. You can also follow the 5.9 development cycle and timeline.
\n\n\n\nIf you have found a bug, you can post the details to the Alpha/Beta area in the support forums.
\n\n\n\nIf you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.
\n\n\n\nFor their help in compiling this post, props to @cbringmann, @webcommsat, @psykro,@marybaum, @chanthaboune, @davidbaumwald, and @hellofromtonya.
\n\";s: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:\"12050\";s: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:58:\"\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:70:\"WP Briefing: Episode 23: A letter from WordPress’ Executive Director\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://wordpress.org/news/2022/01/episode-23-a-letter-from-wordpress-executive-director/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 17 Jan 2022 12: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=12043\";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:\"As we greet a new year, WordPress’ Executive Director writes a letter to the project and community that speaks to the hopes of the year ahead. Have a question you’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 […]\";s: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/2022/01/WP-Briefing-023.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:6741:\"\nAs we greet a new year, WordPress’ Executive Director writes a letter to the project and community that speaks to the hopes of the year ahead.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nJosepha Haden Chomphosy 00:10
\n\n\n\nHello, 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 insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 00:40
\n\n\n\nYesterday marked three years since the WordPress project welcomed me as their executive director. As I start my fourth year, I’ve spent a bit of time considering what the next five years will bring us. WordPress will turn 19 this year, which means that we will soon be a whopping 20 years old; for some of the people who have been with the project since the beginning, that can represent two-thirds of their whole life. And even if you were not that young when you got here, two decades as an open source project is really a cause for celebration.
\n\n\n\nJosepha Haden Chomphosy 01:10
\n\n\n\nI am not in that group that has been here forever. I showed up for the first time in 2009, as a community organizer, self-sponsored, and I learned so much about myself as a person and as a leader while I was doing that. So when I arrived as a sponsored contributor in 2015, I already knew exactly what made this work so fulfilling for me was these three things:
\n\n\n\nJosepha Haden Chomphosy 01:34
\n\n\n\nFirst, the ability to lend a hand in those moments where I wish someone had lent a hand.
\n\n\n\nJosepha Haden Chomphosy 01:40
\n\n\n\nSecond is the delight of seeing people’s first successes and the joy of watching them grow over time.
\n\n\n\nJosepha Haden Chomphosy 01:48
\n\n\n\nAnd the third was a chance to be part of something great, which turned out to be something greater; greater than me or you or a CMS.
\n\n\n\nJosepha Haden Chomphosy 01:58
\n\n\n\nThis list is still at the heart of what I feel I get out of the WordPress project. But it has also grown substantially in my seven years as a sponsored contributor. I now also love how we as a community of contributors get to foster a better way to lead and a better way to collaborate. And through those things help people find a way to have a better life. Not just through WordPress, the CMS, but through WordPress, the people, and WordPress, the project.
\n\n\n\nJosepha Haden Chomphosy 02:25
\n\n\n\nAnd so when I think of what I want for WordPress in its 19th year, so that we can head with confidence and dignity into our 20th year, it is this:
\n\n\n\nJosepha Haden Chomphosy 02:35
\n\n\n\nI want you to remember that you are not alone here. People come together in the world often because of a shared location. But WordPress fosters this beautiful experience of bringing us together because of what we care about. Whether you care about PHP standards, diversity in technology, helping people with their first big wins, making WordPress more secure. I mean, if what you care about is being able to write the most arcane and complex apps on top of WordPress that the world has ever seen. Then there are others out there who want to do that with you, too. We have so many things to connect about. And fortunately, we support a great piece of software for getting our thoughts out in the world. Take some time to see who else shares your thoughts and potentially learn a bit about the view from the other side.
\n\n\n\nJosepha Haden Chomphosy 03:26
\n\n\n\nAnd speaking of the other side, I also want us to approach our discussions as the US versus the Problem TM. WordPress may be 20 years old, and we may stand on the shoulders of giants, but right now, the people who are here you, you are explorers and creators and guides toward the best possible future for WordPress. The tension that we witness between teams is always about the best possible answers for the people who use our software. It is about securing the freedoms of the open web for everyone who comes after us whether they know they need those freedoms or not.
\n\n\n\nJosepha Haden Chomphosy 04:04
\n\n\n\nAnd finally, I want us to expand our reasons for doing this at all. If you are a member of the community of contributors, We frequently talk about how we give back because WordPress gave to us. Or if you are part of a Five for the Future group. You have heard that companies who have experienced success because of WordPress should commit 5% of their resources back to the project to ensure WordPress’ long-term success. But the reason that I keep doing this, and hopefully a new reason for you to keep doing this is that we can take part in securing opportunities for future users of WordPress.
\n\n\n\nJosepha Haden Chomphosy 04:42
\n\n\n\nYes, I want WordPress to be the best CMS. Yes, I want this community to be vibrant and engaged. Yes, I want WordPress to be a shining beacon of how to work remotely. And I want all of that because I know it is our careful and tireless stewardship of this project that lets us continue to lend a hand in those moments where people wish for someone to lend a hand.
\n\n\n\nJosepha Haden Chomphosy 05:11
\n\n\n\nThose are my hopes for WordPress in 2022 to move us forward into WordPress of the future. I hope you all will come with me and we can continue our journey together.
\n\n\n\nJosepha Haden Chomphosy 05:23
\n\n\n\nThanks again for listening. I’m Josepha Haden and this is the WP Briefing. See you again in a couple of weeks.
\n\";s: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:\"12043\";s: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: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:18:\"WordPress 5.9 RC 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:54:\"https://wordpress.org/news/2022/01/wordpress-5-9-rc-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, 11 Jan 2022 20:43:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:3:\"RC2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12014\";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:117:\"The second Release Candidate (RC2) for WordPress 5.9 is available! The final release is slated for January 25, 2022. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Jonathan Bossenger\";s: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:4966:\"\nThe second Release Candidate (RC2) for WordPress 5.9 is now available!
\n\n\n\n“Release Candidate” means the new version of the software is ready for release. It helps the community check that nothing is missed, given the thousands of plugins and themes and differences in how millions of people use the software.
\n\n\n\nThank you to everyone who has contributed thus far towards testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated for release in just two weeks on January 25, 2022. There’s still time to help! Since RC1 was released, six bugs have been found and fixed. There were 13 bug fixes backported from Gutenberg.
\n\n\n\nYou can test the WordPress 5.9 release candidate in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1, on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nCommand One:
\n\n\n\nwp core update --version=5.9-RC2Command Two:
\n\n\n\nwp core update --version=5.9-RC2 --forceYour help to test the second Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.
\n\n\n\nThank you to all of the contributors who tested the RC1 release and gave feedback. Testing for bugs is not just a critical part of polishing every release, it is also a great way to contribute to WordPress.
\n\n\n\nHelp test WordPress 5.9 features – a guide to how you can take part.
\n\n\n\nCan you write in another language other than English? You can help translate WordPress into more than 100 languages! Release Candidate 1 marked the hard string freeze point of the 5.9 release schedule. Thanks to every locale that is already involved with translations.
\n\n\n\nDevelopers and those interested in more of the background to the features can find more in the Field Notes. More developer notes will be added as the release progresses to its final stage. You can also follow the 5.9 development cycle and timeline.
\n\n\n\nIf you think you have found a bug, you can post the details to the Alpha/Beta area in the support forums.
\n\n\n\nIf you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.
\n\n\n\nProps to: @psykro and @webcommsat, and @hellofromtonya, @audrasjb, @cbringmann and @marybaum for final review.
\n\";s: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:\"12014\";s: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: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:32:\"WordPress 5.8.3 Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2022/01/wordpress-5-8-3-security-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jan 2022 21:02: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Security\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11999\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:360:\"This security release features four security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated. WordPress 5.8.3 is a short-cycle security release. The next major release will be version 5.9, which is already in the Release Candidate stage. You […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:3681:\"\nThis security release features four security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.
\n\n\n\nWordPress 5.8.3 is a short-cycle security release. The next major release will be version 5.9, which is already in the Release Candidate stage.
\n\n\n\nYou can update to WordPress 5.8.3 by downloading from WordPress.org or visiting your Dashboard → Updates and clicking Update Now.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nFour security issues affect WordPress versions between 3.7 and 5.8. If you haven’t yet updated to 5.8, all WordPress versions since 3.7 have also been updated to fix the following security issue (except where noted otherwise):
\n\n\n\nThank you to all of the reporters above for privately disclosing the vulnerabilities. This gave the security team time to fix the vulnerabilities before WordPress sites could be attacked. Thank you to the members of the WordPress security team for implementing these fixes in WordPress.
\n\n\n\nFor more information, check out the 5.8.3 HelpHub documentation page.
\n\n\n\nThe 5.8.3 release was led by @desrosj and @circlecube.
\n\n\n\nIn addition to the security researchers and release squad members mentioned above, thank you to everyone who helped make WordPress 5.8.3 happen:
\n\n\n\nAlex Concha, Dion Hulse, Dominik Schilling, ehtis, Evan Mullins, Jake Spurlock, Jb Audras, Jonathan Desrosiers, Ian Dunn, Peter Wilson, Sergey Biryukov, vortfu, and zieladam.
\n\";s: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:\"11999\";s: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:40:\"The Month in WordPress – December 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2022/01/the-month-in-wordpress-december-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jan 2022 19:03:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11972\";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:335:\"December was a busy month for the WordPress community. In the latest episode of the WP Briefing podcast, WordPress Executive Director Josepha Haden Chomphosy shares a carol of thanks and shows her gratitude to all the people who make the WordPress project a success. (…) I know that we have gotten so much done together […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"rmartinezduque\";s: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:13065:\"\nDecember was a busy month for the WordPress community. In the latest episode of the WP Briefing podcast, WordPress Executive Director Josepha Haden Chomphosy shares a carol of thanks and shows her gratitude to all the people who make the WordPress project a success.
\n\n\n\n\n\n\n\n(…) I know that we have gotten so much done together in the last few years. And I am equally sure that we’re going to get so much done in the years to come. And so thank you all so much for your continued work with WordPress and the way that you just bring your best at all times.
Josepha Haden, Executive Director of the WordPress project
We said goodbye to 2021 with the annual State of the Word, along with the release of WordPress 5.9 Beta 4, among many other exciting updates. Read on to learn more about the latest community achievements.
\n\n\n\n\n\n\n\nAre you interested in contributing to WordPress core? Join the #core channel, follow the Core Team blog, and check out the team handbook. Also, don’t miss the Core Team’s weekly developer chat on Wednesdays at 8 PM UTC.
The Core Team launched two new versions of Gutenberg last month. Both come with new features, code quality improvements, and bug fixes.
\n\n\n\n\n\n\n\nWant to get involved in developing Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. Follow the #gutenberg-new tag for details on the latest updates.
\n\n\n\nIf you missed the event’s livestream, you could watch the State of the Word recording and the Q&A session on WordPress.tv.
\n\n\n\nAre you looking for some 5.9 resources to share with your local community? Check out the WordPress 5.9 Talking Points for Meetup Organizers post.
\n\n\n\nShare your feedback on WordPress 5.9.
Don’t miss the following upcoming WordCamps: WordCamp Birmingham, Alabama 2022, WordCamp Genève 2022, WordCamp Vienna 2022, and WordCamp Europe 2022.
\n\n\n\n\n\n\n\nThe Call For Sponsors and Call For Speakers for WordCamp Europe 2022 are open! Read this post to learn more about the Organizing Team’s plans for the first in-person WordCamp Europe in three years.
Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to December 2021’s Month in WordPress: @anjanavasan, @harishanker @lmurillom @meher @nalininonstopnewsuk @webcommsat
\n\";s: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:\"11972\";s: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: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:18:\"WordPress 5.9 RC 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:54:\"https://wordpress.org/news/2022/01/wordpress-5-9-rc-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:\"Tue, 04 Jan 2022 20:43: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: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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11948\";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:101:\"The WordPress 5.9 Release Candidate 1 is available. The final release is slated for January 25, 2022.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:5481:\"\nThe first Release Candidate (RC1) for WordPress 5.9 is now available!
\n\n\n\nThank you to everyone who has contributed to reach this important milestone in the community’s progress towards a WordPress 5.9 release.
\n\n\n\n“Release Candidate” means the new version of the software is ready for release. It helps the community check that nothing is missed, given the thousands of plugins and themes and differences in how millions of people use the software.
\n\n\n\nWordPress 5.9 is slated for release on January 25, 2022. This is just three weeks to go – and there’s still time to help!
\n\n\n\nYou can test the WordPress 5.9 release candidate in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3 or 4 on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nCommand One:
\n\n\n\nwp core update --version=5.9-RC1Command Two:
\n\n\n\nwp core update --version=5.9-RC1 --forceYour help to test the RC1 is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.
\n\n\n\nThank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is not just a critical part of polishing every release; it is also a great way to contribute to WordPress.
\n\n\n\nHelp test WordPress 5.9 features – a guide to how you can take part.
\n\n\n\nThis will be the first release of 2022 and continues the work towards 5.9 from last year. It features the latest advances of the block editor and is the first version of full site editing in Core.
\n\n\n\nWordPress 5.9 also brings more refinements to the developer experience. To keep up with the latest updates and discover more about how the community works to continually improve the software, please subscribe to the Make WordPress Core blog. In particular, the developer notes tag will keep you up to date on changes that might affect your products or how you use the software.
\n\n\n\nPlease test your plugins and themes against WordPress 5.9 and update the Tested up to version to 5.9 in your readme file. If you find compatibility problems, please post to the support forums, so volunteers and developers can help you figure them out before the final release.
\n\n\n\nThe WordPress 5.9 Field Guide will be out very shortly. It will give you a deeper dive into the major changes.
\n\n\n\nDo you speak a language that is not English? You can help translate WordPress into more than 100 languages! Release Candidate 1 marks the hard string freeze point of the 5.9 release schedule. Thanks to every locale that is already involved with translations.
\n\n\n\nIf you think you have found a bug, you can post to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.
\n\n\n\nProps to @webcommsat for the post and to @marybaum @hellofromtonya @audrasjb @davidbaumwald @estelaris @cbringmann for final review.
\n\";s: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:\"11948\";s: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:69:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"People of WordPress: Collins Agbonghama\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/12/people-of-wordpress-collins-agbonghama/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 30 Dec 2021 22:45: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:5:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s: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:2;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:3;a:5:{s:4:\"data\";s:17:\"Contributor Story\";s: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:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11923\";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:130:\"Collins Agbonghama, a web developer from Nigeria, Africa, shares how WordPress gives him a sustainable income and a better future.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:8695:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a website builder from Nigeria, who uses the open source WordPress platform to support his family and to share learning with others in his home country and beyond.
\n\n\n\nCollins Agbonghama started his journey to becoming a web developer by reading the football news headlines on a friend’s mobile phone. His fascination with development and learning continued to grow, and he now makes a living using WordPress and the web.
\n\n\n\nRead on to discover his story, which shows with creativity and determination you can create products and make a living using WordPress.
\n\n\n\n![\"Collins](\"https://i2.wp.com/wordpress.org/news/files/2021/12/collins-agbonghama1.jpg?resize=350%2C426&ssl=1\")
Collins began his exploration of the internet while attending Secondary School in Nigeria, or High School as it is known in some other countries.
\n\n\n\nA friend at the school had a simple mobile phone which could browse the internet. Collins had his first introduction to the World Wide Web through access to this device. He became hooked by reading headlines on a sports site about a famous English Premier League Football Club, Chelsea, a soccer team which he has long supported.
\n\n\n\n“Being a very inquisitive person, I wanted to learn how the web works as well as have my own website. I was able to buy a classic mobile phone through the menial jobs I did after school,” he said.
\n\n\n\nHis first website was a wapsite or Wireless Application Protocol site optimized for mobile devices.
\n\n\n\nHe took to Google to learn how to actually build a site. He discovered he needed something called an ‘email address’ to sign-up for site builders. Google Search came to the rescue again, and he created the first email account for his first website.
\n\n\n\nA desire for a website was the catalyst for further learning, starting with HTML and CSS from an online provider. His interest in building sites with more advanced tools grew, and then he came across WordPress.
\n\n\n\nUsing his savings, he bought the cheapest hosting plan from a local Nigerian web host. He installed WordPress and started writing tutorials for a mobile device platform. He built the site, created the lessons, and started his entry into WordPress all on a mobile phone.
\n\n\n\nThis led to him having the confidence to start building sites for others, and he was able to earn a small income from that.
\n\n\n\nCollins said: “I couldn’t go to the university because of my precarious financial situation. I continued to do menial jobs during the day and started learning PHP in the evenings and at night using my mobile phone via online learning platforms.”
\n\n\n\nHe was later able to get an old laptop, which helped him access ebooks to learn more and practice his coding.
\n\n\n\nKeen to share this learning, he started blogging about what he was learning on his website.
\n\n\n\nCollins said: “I later took up a job teaching children at a school primarily because I got tired of the menial jobs and wanted to earn enough to take care of my internet data plan. After a while, I became fairly proficient in PHP and even took up a job to build a school management system.”
\n\n\n\nCollins’ blog wasn’t making money through advertisements, but he discovered opportunities to write tutorials for other platforms.
\n\n\n\n“I started writing PHP and WordPress development tutorials and got paid a few hundred dollars per article. In Nigeria, that’s quite a lot of money. I was able to improve the life and wellbeing of my family and myself,” he said.
\n\n\n\nAfter getting into a higher education program to study computer science, his life dramatically changed. He decided to stop writing and began to focus on building and selling WordPress plugins. His first one was a user and profile plugin for WordPress sites.
\n\n\n\n“Thankfully, after a year, it started making enough revenue for me to live pretty comfortably here in Nigeria because the cost of living here is relatively low,” he said
\n\n\n\nToday, Collins has several plugins which have given him a sustainable source of income. He’s also a Core and Translation volunteer contributor to the WordPress.org Open Source project.
\n\n\n\nI am thankful for WordPress because without it, I’m really not sure I would have been able to live a decent quality life.
Collins Agbonghama
Who knows what would have become of me?
“I am also thankful for the community. I have made lots of friends that have been very supportive and helpful in my journey.”
\n\n\n\nHe added: “I tell people, life won’t give you what you want. You demand from life what you want. You make these demands by being determined and never giving up on your dreams and aspirations.
\n\n\n\n“If you are poor, perhaps because you came from a humble and poor background, it is not your fault. You can’t go back in time to change things. I implore you to be strong, determined, and work hard.”
\n\n\n\n\n\n\n\nMeet more WordPress community members in our People of WordPress series.
\n\n\n\nThanks to Michael Geheren (@geheren), Abha Thakor (@webcommsat), for writing this feature, to @MeherBala (@meher) for follow-ups and photo-editing, and to Chloe Bringmann (@cbringmann) and Nalini Thakor (@nalininonstopnewsuk) for the final proofing. Thank you to Collins Agbonghama (@collizo4sky) for sharing his Contributor Story.
\n\n\n\nThanks to Josepha Haden Chomphosy (@chanthaboune), Topher DeRosia (@topher1kenobe) and others for their support of this initiative.
\n\n\n\nThe People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia, which highlights people in the WordPress community who have overcome barriers.
\n\n\n\n#HeroPress #ContributorStory
\n\";s: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:\"11923\";s: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: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:20:\"WordPress 5.9 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/12/wordpress-5-9-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:\"Tue, 21 Dec 2021 21:17:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:4:{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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:4:\"beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11876\";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:80:\"WordPress 5.9 Beta 4 released on 21 December 2021 and is 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:18:\"Jonathan Bossenger\";s: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:5052:\"\nWordPress 5.9 Beta 4 is now available for testing!
\n\n\n\nThis software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.
\n\n\n\nYou can test the WordPress 5.9 Beta 4 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, or 3 to Beta 4 on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nCommand One:
\n\n\n\nwp core update --version=5.9-beta4Command Two:
\n\n\n\nwp core update --version=5.9-beta4 --forceThe current target for the final release of 5.9 is January 25, 2022, which is only five weeks away. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.
\n\n\n\nSince Beta 3, 20 bugs have been fixed. Here are a few of the changes you will find in Beta 4:
\n\n\n\nDo some testing!
\n\n\n\nTesting for bugs is vital for polishing the release in the beta stage and a great way to contribute.
\n\n\n\nPlease post to the Alpha/Beta area in the support forums if you find a bug. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nIn the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that will cover these items in detail.
\n\n\n\nSo far, contributors have fixed 326 tickets and 108 new features and enhancements in WordPress 5.9. More bug fixes are on the way with your help through testing.
\n\n\n\nProps to @cbringmann, @psykro, @hellofromtonya, @marybaum, @webcommsat, @audrasjb, @costdev and @meher for contributions to this post.
\n\";s: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:\"11876\";s: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:58:\"\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:42:\"WP Briefing: Episode 22: A Carol of Thanks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2021/12/episode-22-a-carol-of-thanks/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 20 Dec 2021 19:22:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"wp-briefing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=11880\";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:404:\"In this last episode of 2021, Josepha Haden Chomphosy takes the time to appreciate those who make the WordPress project a success and offers a carol of thanks. Have a question you’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: […]\";s: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/12/WP-Briefing-022.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:5720:\"\nIn this last episode of 2021, Josepha Haden Chomphosy takes the time to appreciate those who make the WordPress project a success and offers a carol of thanks.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nHave yourself A Merry Little Christmas
\n\n\n\nJosepha Haden Chomphosy 00:10
\n\n\n\nHello 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 insight into the community that supports it and get a small list of big things coming up in the next two weeks. I’m your host Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 00:39
\n\n\n\nSo, ages and ages ago, when I first started this podcast, someone basically requested that Matt and I do a duet for the last podcast of the year. A Christmas carol duet; him on the saxophone and me on voice. I obviously did not get that coordinated I don’t even know why I said obviously. I’ll tell you right now I did not get that coordinated. I was a very busy lady this year. So I don’t have a Matt on saxophone. Still, I did think that maybe it might be nice just for me to sing a teensy little Christmas carol for you all just because it seems especially poignant the words this year, especially after the 2020, 2021 COVID, all the things and trying to get back in person. So I’m going to sing you all one little verse from Have Yourself a Merry Little Christmas.
\n\n\n\nJosepha Haden Chomphosy 01:35 Singing
\n\n\n\nHave yourself a merry little Christmas
\n\n\n\nLet your heart be light
\n\n\n\nFrom now on our troubles
\n\n\n\nWill be out of sight
\n\n\n\nHave yourself a merry little Christmas
\n\n\n\nMake the Yuletide gay
\n\n\n\nFrom now on our troubles
\n\n\n\nWill be miles away
\n\n\n\nHere we are as in olden days
\n\n\n\nHappy golden days of yore
\n\n\n\nFaithful friends who are dear to us
\n\n\n\nGather near to us, once more
\n\n\n\nThrough the years we all will be together
\n\n\n\nIf the fates allow
\n\n\n\nHang a shining star upon the highest bough
\n\n\n\nAnd have yourself a merry little Christmas now
\n\n\n\nHere we are as in olden days
\n\n\n\nHappy golden days of yore
\n\n\n\nFaithful friends who are dear to us
\n\n\n\nGather near to us, once more
\n\n\n\nThrough the years we all will be together
\n\n\n\nIf the fates allow
\n\n\n\nHang a shining star upon the highest bough
\n\n\n\nAnd have yourself a merry little Christmas now
\n\n\n\nJosepha Haden Chomphosy 03:34
\n\n\n\nAlright, my friends, that was from my heart to yours if you happened to listen. If you skipped a few seconds to get through it, which I would totally understand, that is also fine. But I did want to just kind of wrap up the year to let you all know that I am so incredibly grateful for all of the people who show up for the WordPress project to make it a success. I have made so many friends and wonderful acquaintances throughout my time here with the WordPress project. And especially in my three years as the project’s Executive Director. You all have put a lot of trust in me and a lot of faith. And I know that we have gotten so much done together in the last few years. And I am equally sure that we’re going to get so much done in the years to come. And so thank you all so much for your continued work with WordPress and the way that you just bring your best at all times.
\n\n\n\nJosepha Haden Chomphosy 04:32
\n\n\n\nOne other little thanks I want to give. Over the course of this year, I’ve had an excellent team that works with me on this podcast. I have editing and design folks and people who’ve joined me here and there, folks who helped me with my production. So big thank you to Dustin, Bea, I realize your name is Beatriz in the actual credits, but I call you Bea, and so thank you. Also, a huge thank you to Chloé, who does all of our production and wrangling every couple of weeks. A big round of applause and kudos to that tiny but tough team that helps me get this all done.
\n\n\n\nJosepha Haden Chomphosy 05:10
\n\n\n\nThat’s to go on top of the general thanks to the WordPress project. And if you all are celebrators, I hope you have a wonderful holiday season. If you are not celebrators, I hope that you have a wonderful end to your year and that everything you wanted to get done, you did get done, and that you can start 2022 with a fresh slate. Again, this is the WP Briefing. Thank you so much for listening. I’m your host Josepha Haden Chomphosy, and I’ll see you again in 2022.
\n\";s: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:\"11880\";s: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:38:\"Highlights from State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wordpress.org/news/2021/12/highlights-from-state-of-the-word-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 16 Dec 2021 01:04:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:6:\"WrapUp\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11869\";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:60:\"Highlights and the official video for State of the Word 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Anjana Vasan\";s: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:3653:\"\nState of the Word 2021, the annual keynote from WordPress co-founder Matt Mullenweg, happened on December 14. The hybrid event took place in New York City with a small audience (proof of vaccination required). As Matt said, “we had people join by plane, train, and automobile.” Those who didn’t make the trek to the live event watched the livestream from wherever they call home, all around the world.
\n\n\n\nIt was an exciting moment for the WordPress community which also celebrated its first in-person WordCamp in Sevilla, Spain, after a lengthy hiatus for in-person events.
\n\n\n\nYou can view the full recording, complete with captions and transcripts on WordPress.tv.
\n\n\n\nIt was thrilling to see so many meetup organizers host watch parties worldwide. Twenty-eight watch parties were held across eleven countries, with more than 300 RSVPs.
\n\n\n\nSimilar to past State of the Word events, Matt covered a broad range of topics. This year was no different. WordPress’ past, present, and future were in the spotlight, with highlights on the growth of the contributors, language translations, recent release milestones, and educational initiatives, to name a few.
\n\n\n\nAudience members and livestreamers alike viewed product demos showcasing upcoming features that will be the hallmark of WordPress 5.9, such as full site editing, block patterns, global styling options, and enhanced image controls.
\n\n\n\nMatt took the opportunity to remind everyone of the WordPress roadmap which includes native multi-lingual support and real-time collaborative site editing. He also pointed out that anyone can contribute to WordPress’ progress through a number of different initiatives ranging from creating new features and testing to helping spread the word and educate others.
\n\n\n\nMatt emphasized the way that open source software gets better by reminding everyone that “The more people that use a program like WordPress, the better it gets.”
\n\n\n\nBroader topics covering the tech landscape including web3, merger and acquisition activity, as well as the growth and support of open source software, rounded out the energetic presentation.
\n\n\n\nThe one-hour multimedia presentation was followed by an interactive question and answer session where Matt fielded questions that were submitted ahead of the event, as well as questions from the livestream and studio audience.
\n\n\n\nDiscover everything that was covered by watching the official event recording and join the ongoing #ILoveWP conversation on Twitter!
\n\n\n\nSpecial thanks to @dansoschin for review and edits!
\n\";s: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:\"11869\";s: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:69:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.9 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/12/wordpress-5-9-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:\"Tue, 14 Dec 2021 20:19: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:8:\"category\";a:5:{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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:4:\"beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11835\";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:102:\"WordPress 5.9 Beta 3 is now available for testing. Help test to make the release as good as it can be.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Jonathan Bossenger\";s: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:6087:\"\nWordPress 5.9 Beta 3 is now available for testing!
\n\n\n\nThis software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.
\n\n\n\nYou can test the WordPress 5.9 Beta 3 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version.
\n\n\n\nOption 3: If you use WP-CLI to upgrade from Beta 1 or Beta 2 to Beta 3 on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nCommand One:
\n\n\n\nwp core update --version=5.9-beta2Command Two:
\n\n\n\nwp core update --version=5.9-beta3 --forceThe current target for the final release of 5.9 is January 25, 2022, which gets closer every minute. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.
\n\n\n\nSince Beta 2, 14 bugs have been fixed. Here are a few of the changes you will find in Beta 3:
\n\n\n\nDo some testing!
\n\n\n\nTesting for bugs is vital for polishing the release in the beta stage and a great way to contribute.
\n\n\n\nIf you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.
\n\n\n\nFor even more ways to test, you can also refer to this official Full Site Editing post from @annezazu.
\n\n\n\nIn the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail. So far, contributors have fixed 316 tickets in WordPress 5.9, including 100 new features and enhancements. More bug fixes are on the way with your help through testing.
\n\n\n\nProps to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @costdev, and @audrasjb for contributions to this post.
\n\n\n\nFiled under #release, #5.9, #beta
\n\";s: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:\"11835\";s: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:75:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.9 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/12/wordpress-5-9-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, 07 Dec 2021 22:02:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:7:{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.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:3;a:5:{s:4:\"data\";s:4:\"beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:4;a:5:{s:4:\"data\";s:6:\"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:\"\";}i:5;a:5:{s:4:\"data\";s:12:\"block editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:6;a:5:{s:4:\"data\";s:11:\"WP 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=11794\";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:125:\"Can you help test the latest software version of WordPress? 5.9 Beta 2 was published on 7 December 2021, help find any bugs. \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s: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:6225:\"\nWordPress 5.9 Beta 2 is now available for testing!
\n\n\n\nThis software version is still under development. Please do not run this software on a production site. Instead, install it on a test site, where you can try out the newest features to get a feel for how they will work on your site.
\n\n\n\nYou can test the WordPress 5.9 Beta 2 in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1 to Beta 2 on a case-insensitive filesystem, please use the following command sequence:
Command One:
\n\n\n\nwp core update --version=5.9-beta1 Command Two:
\n\n\n\n wp core update --version=5.9-beta2 --force The current target for the final release of 5.9 is January 25, 2022, which is just seven weeks away. Your help testing this version is a vital part of making this release as good as it can be.
\n\n\n\nSince Beta 1, 24 bugs have been fixed. Here are a few of the changes you will find in Beta 2:
\n\n\n\nAlso, note that some users testing 5.9 Beta 1 faced some fatal errors upon upgrade. In turn, these errors revealed the need for some extra work on the filesystem and upgrader. Those fatal errors are no longer a problem, and the enhancements will be part of version 6.0.
\n\n\n\nDo some testing!
\n\n\n\nTesting for bugs is vital for polishing the release in the beta stage and a great way to contribute.
\n\n\n\nIf you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.
\n\n\n\nIn the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that cover these items in detail.
\n\n\n\nSo far, contributors have fixed 305 tickets in WordPress 5.9, including 110 new features and enhancements. More bug fixes are on the way with your help through testing.
\n\n\n\nProps to @psykro, @estelaris, @hellofromtonya, @marybaum, @webcommsat, @cbringmann, @davidb, @audrasjb, and @pbiron for contributions to this post.
\n\";s: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:\"11794\";s: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: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:40:\"The Month in WordPress – November 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2021/12/month-in-wordpress-november-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 02 Dec 2021 11:30:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:18:\"month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:22:\"the month in wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11763\";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:334:\"Despite the holiday season being around the corner, the WordPress project didn’t slow down. In a recent episode of WP Briefing, Executive Director Josepha Haden shares the first thing she wants people to notice about WordPress, which is also the heart of this open source project: Now, the first thing I want people to see […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Anjana Vasan\";s: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:18257:\"\nDespite the holiday season being around the corner, the WordPress project didn’t slow down. In a recent episode of WP Briefing, Executive Director Josepha Haden shares the first thing she wants people to notice about WordPress, which is also the heart of this open source project:
\n\n\n\n\n\n\n\nNow, the first thing I want people to see on that site is that WordPress has not only 18 years of learned knowledge that every single new user benefits from, but that it also has thousands of really smart people making sure it works and gets better every day.
Josepha Haden, Executive Director of the WordPress project
As always, contributors across various teams are working hard to ensure the upcoming release of WordPress 5.9 doesn’t disappoint. With State of the Word 2021 coming up soon, there are many exciting things in the works. Read the November 2021 edition of the Month in WordPress to learn more about what’s happening.
\n\n\n\n![\"\"](\"https://i2.wp.com/wordpress.org/news/files/2021/12/5.9.png?resize=632%2C309&ssl=1\")
\n\n\n\n\n\n\n\nAre you interested in contributing to WordPress core? Join the #core channel, follow the Core Team blog, and check out the team handbook. Also, don’t miss the Core Team’s weekly developer chat on Wednesdays at 8 PM UTC.
Two new Gutenberg versions have been released!
\n\n\n\n\n\n\n\n\n\n\n\nWant to get involved in developing Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. Follow #gutenberg-new for details on the latest updates.
![\"State](\"https://i2.wp.com/wordpress.org/news/files/2021/12/Web-—-Matt.png?resize=632%2C422&ssl=1\")
\n\n\n\n\n\n\n\nAdd the event to your calendar so you don’t miss State of the Word 2021! Want to ask Matt a question during State of the Word? Please send your questions ahead of time to ask-matt@wordcamp.org or ask them live during the event via YouTube chat.
\n\n\n\n\n\n\n\nWe want to hear from you! Suggest your 2022 goals for the Global Community Team by December 6, 2021.
\n\n\n\n\n\n\n\nThe 2021 WordPress Annual Survey is out! Please respond to the survey, so your WordPress experience is reflected in the results.
\n\n\n\nGive back to open source. Please donate to the WordPress Foundation’s mission this holiday season.
Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to November 2021’s Month in WordPress: @anjanavasan, @harishanker, @rmartinezduque, @callye, @jrf, @webcommsat, and @nalininonstopnewsuk
\n\";s: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:\"11763\";s: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: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.9 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/11/wordpress-5-9-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:\"Tue, 30 Nov 2021 23:35: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: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=11584\";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:307:\"WordPress 5.9 Beta 1 is now available for testing! This version of the WordPress software is under development. You don’t want to run this version on a production site. Instead, it is recommended that you run this on a test site. This will allow you to test out the new version. You can test the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:10992:\"\nWordPress 5.9 Beta 1 is now available for testing!
\n\n\n\nThis version of the WordPress software is under development. You don’t want to run this version on a production site. Instead, it is recommended that you run this on a test site. This will allow you to test out the new version.
\n\n\n\nYou can test the WordPress 5.9 Beta 1 in three ways:
\n\n\n\nwp core update --version=5.9-beta1. Do not use this option if your filesystem is case-insensitive.The current target for the final release is January 25, 2022, which is just eight weeks away. Your help testing this version is vital to make sure the release is as good as it can be.
\n\n\n\nCheck the Make WordPress Core blog for 5.9-related developer notes in the coming weeks which will break down all upcoming changes in greater detail.
\n\n\n\nTesting for bugs is a critical part of polishing the release in the beta stage. It is also a great way to contribute. If you’ve never tested a beta release before, this detailed guide will help walk you through what and how to test.
\n\n\n\nIf you think you’ve found a bug, please report it to the Alpha/Beta area in the support forums. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.
\n\n\n\nTo see every feature in the Gutenberg releases since WordPress 5.8, check out the What’s New In Gutenberg posts for 10.8, 10.9, 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8, and 11.9.
\n\n\n\nBeyond the noted changes, which include 580 enhancements and nearly 450 bug fixes, contributors have fixed 297 tickets for WordPress 5.9, including 110 new features and enhancements. More fixes are on the way.
\n\n\n\nHappy testing!
\n\n\n\nWant to know what’s new in version 5.9? Read on for some highlights.
\n\n\n\nCombine all the features that went live in 5.8 with those making their entrance in 5.9, and you get Full Site Editing.
\n\n\n\nFormerly known as Global Styles, the Styles Interface lets you interact directly with your blocks and elements right in the WordPress Admin. From typography to color palettes, this cohesive design interface means a design change—even a dramatic one—can happen without a theme switch. No code needed.
\n\n\n\nIntroduced in WordPress 5.8, theme.json has been improved to enable features and default styles for your site and its blocks. With 5.9, theme.json can support child themes and the duotone treatment. Coordinate layers of style with theme.json, taking the weight off of your theme’s required CSS.
\n\n\n\nOther features supported by theme.json include:
\n\n\n\nWelcome to the most intuitive way to build navigation: the Navigation Block.
\n\n\n\nHere are the features that need testing the most:
\n\n\n\nWhat if you could treat single images in your Gallery Block the same way you treat the Image Block? Now you can.
\n\n\n\nMake every image in your gallery different from the next, with inline cropping or a duotone and change layouts with the ease of drag and drop. With the improved gallery block, every image is its own Image block.
\n\n\n\nOne thing to note: Have you built a plugin or theme on the Gallery Block functionality? Be sure to review this Dev Note, which details what you need to do for compatibility.
\n\n\n\nBuilding template parts can take a level of focus all its own because you’re making decisions for the entire site. So WordPress 5.9 adds a focus mode that shows you only the part you’re working on right now (and you can get back to the regular view with a keystroke).
\n\n\n\nThe Pattern Directory offers a range of prebuilt block patterns, from a couple of blocks that show an image and text, to an entire page layout with columns and sections. Since the 5.8 release, the directory has become a hub for exploratory UI and patterns, taking submissions and offering them to the community. So now, your creation can help other people build out their perfect site.
\n\n\n\nA whole new way of building WordPress themes.
\n\n\n\nWordPress 5.9 introduces features that make Full Site Editing possible, including the first default block theme.
\n\n\n\nUsing minimal CSS, theme styles reside in theme.json so that you can configure them in the Styles interface of the WordPress Admin. Make this theme take on its own personality site-wide, with a wide array of color schemes, type combinations, page templates, premade components (forms), and image treatments to choose from.
\n\n\n\nProps to @chanthaboune, @priethor, @psykro, @annezazu, @webcommsat, @marybaum, @hellofromtonya, @davidbaumwald, and @rmartinezduque for their research and copy.
\n\";s: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:\"11584\";s: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:72:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"People of WordPress: Devin Maeztri\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2021/11/people-of-wordpress-devin-maeztri/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 30 Nov 2021 22:21:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:6:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s: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:17:\"Contributor Story\";s: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:\"Indonesia\";s: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:5:{s:4:\"data\";s:19:\"People of WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:5;a:5:{s:4:\"data\";s:20:\"Polyglot Contributor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=11678\";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:111:\"Devin Maeztri, a campaigner from Indonesia talks about the difference WordPress makes in her life and her work.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:16562:\"\nIn this series, we share some of the inspiring stories of how WordPress and its global network of contributors can change people’s lives for the better. This month we feature a translator and campaigner who uses WordPress to highlight good causes and helps people in her area benefit from the open source platform.
\n\n\n\n![\"Devin](\"https://i2.wp.com/wordpress.org/news/files/2021/11/devin-with-her-cat.jpg?resize=632%2C843&ssl=1\")
Going to a WordCamp can be a life-changing experience, as Devin Maeztri discovered. Every event she attends is a further step on a journey of discovering the WordPress community and its many opportunities.
\n\n\n\n“It is not that hard to fall for WordPress if you have a chance to experience WordPress. For me, it took a WordCamp.”
Devin Maeztri
Devin’s first experience with camps came when she volunteered impromptu at an Indonesian event, WordCamp Denpasar, Bali in 2016.
\n\n\n\nHere, she made a profound discovery: “WordCamps can bring people who will give back to the community, even if they don’t get anything from WordPress directly.”
\n\n\n\nWith every WordCamp after that first experience, she became more interested in WordPress and the community.
\n\n\n\nOver time, Devin found she wanted to be part of WordPress events more often. She became a regular at Meetups in Ubud and Jakarta, joining as a co-organizer at WordCamp Jakarta in 2017 and 2019. Later, she took on the role of co-organizer for Meetups in Jakarta and Ubud.
\n\n\n\nSmitten by what WordCamps can offer and how they can bring people together across national borders, she joined the organizing team for WordCamp Asia 2020. Sadly, this event was to become the first major WordPress event to be cancelled in the COVID-19 pandemic.
\n\n\n\nNaturally, Devin hopes WordCamp Asia will happen someday very soon. Beyond the expected WordPress learning and sharing that event will promote, she believes its very scale will showcase how WordCamps add international tourism and cultural understanding everywhere they take place.
\n\n\n\n![\"Devin](\"https://i1.wp.com/wordpress.org/news/files/2021/11/wcasia_2020_organizers_in_wceu_2019.jpeg?resize=632%2C632&ssl=1\")
After experiencing several events, Devin had questions: “At WordCamps and Meetups, you hear stories about how WordPress powers the web. How it changes the lives of so many people, how it helps dreams come true. It made me think, considering WordPress is that powerful, why are there not even more people in Indonesia using websites, and more using WordPress? Why aren’t more talented Indonesian WordPress users, developers, designers, and business owners taking part in WordPress.org projects? Language, for me, was the main answer.”
\n\n\n\nThe solution Devin felt was to make WordPress available in the main local language. She said: “I believe, the more content translated into Indonesian, the more Indonesian WordPress users see WordPress as more than just a blogging platform or a content management system. They will realize it’s a huge open source community that works together to make the web a better place. The more plugins and themes translated, the easier the work of the developer and designer will be. The more people see how WordPress can enhance their life, the better the ecosystem for business owners becomes.”
\n\n\n\nAfter talking with others about how WordPress could be even more useful in Indonesia, Devin felt she had to make a personal commitment to reviving the polyglot project in Indonesia. With another volunteer contributor and through promotion, the local polyglot team got bigger and the interest in translation grew. She also took on the responsibility of a General Translation Editor for the language.
\n\n\n\n![\"Polyglot](\"https://i1.wp.com/wordpress.org/news/files/2021/11/featured-img-used-for-devin-pow2.jpg?resize=632%2C318&ssl=1\")
Through the efforts of Devin and the other translation editors, Indonesia took part in WordPress Translation Day in 2020, and in 2021 held sprints and learning sessions spanning the whole 30 days of the event.
\n\n\n\nHer enthusiasm and dedication to helping others translate WordPress locally and promoting the global community were recognized in the Polyglot Appreciation Nominations for 2021.
\n\n\n\nThrough her involvement in translation, Devin noticed there were not many women involved in the WordPress community in Indonesia. Often, she found herself the only woman at an event.
\n\n\n\nSo, along with a couple of community members, she started Perempuan WordPress, a local initiative. This group is open for everyone to join, but prioritizes women as event speakers.
\n\n\n\nDevin has gone on to support the work of the Diversity Speaker Training group in the Community Team, translating materials and promoting initiatives in Indonesia. She is keen to encourage others to get involved with this initiative which helps increase the diversity of presenters at Meetups and WordCamps.
\n\n\n\n![\"\"](\"https://i1.wp.com/wordpress.org/news/files/2021/11/devin-at-wc-jakarta2019.png?resize=600%2C534&ssl=1\")
In her professional roles, Devin is an advocate for WordPress as a tool for people with a wide variety of skill sets. She does not code, but uses the platform extensively for her projects. In 2014, she signed up for a free account on WordPress.com to keep and share notes about what she saw or was thinking about as she commuted on public transport to work. This site did not turn into a blog, but instead introduced her to other opportunities and the vast capabilities of the platform.
\n\n\n\nWith a background in environmental activism, Devin has worked for international development organizations on everything from policymaking to campaigning.
\n\n\n\nBehind the desk, she worked with policymakers and organized conferences and meetings. That meant doing a lot of writing and translating and working with people on the ground who were impacted by the policies. “My work on the ground usually involved researching, movement building and community empowerment,” she noted.
\n\n\n\nHer work with events inspired Devin to get involved in WordCamps and Meetups and share her energy for making things happen. As in her professional work, she felt WordPress was an opportunity to work and share with people about something that can make a positive impact on someone else’s life.
\n\n\n\n“For me, everything comes from the heart. I do things that I feel so strongly about. Things that call me, and things that I am good at but still giving me room to learn and become better at. WordPress can be the perfect place for this.”
\n\n\n\nWhile she was between jobs, Devin was encouraged to volunteer at WordCamp Denpasar 2016. With some help, she created an online CV. She also learned to manage a WordPress site, navigate the wp-admin, and make the content appeal to potential employers.
\n\n\n\nShe eventually got a job as a campaigner to build a movement online and offline. The brainchild of many university friends in America, who used digital campaigns to go global, the campaign used WordPress.
\n\n\n\nDevin worked alongside a digital campaigner and helped shape the content, the call to action, and the user experience. She also had to use the wp-admin to make some amendments. As a global movement, it developed its resources in English, so she also reviewed the work of the translators she worked with.
\n\n\n\n![\"One](\"https://i2.wp.com/wordpress.org/news/files/2021/11/cat-watching-translation.jpg?resize=632%2C474&ssl=1\")
She left her job as a campaigner at the end of 2018 to concentrate on freelancing – and to spend more of her free time contributing to the WordPress community. She also took up the initiative to help street cats in Jakarta.
\n\n\n\nDevin said: “So, I am busy helping these cats but also learning how to fundraise using a website. I’m learning to use online forms, set up a payment service provider, work on SEO, and do other new things I need to learn to grow my initiative. I do have the privilege to learn directly from a personal guru. The same person who convinced me to volunteer at WordCamp Denpasar, and who I married in 2018.”
\n\n\n\nDevin was so enthused by being a contributor for WordPress, she took part in the video shorts following the Translation Day events.
\n\n\n\nShe is also active in other Contributor Teams and decided to become a Community Team Deputy to support meetups in new cities across Indonesia and perhaps future WordCamps.
\n\n\n\nShe said: “One of the things that I like about WordPress is that it is very welcoming and open to people like me, who don’t code at all. At the same time, it shows me a different way of looking at the world.”
\n\n\n\nDevin believes in the power of WordPress to give ‘everyone a chance to learn new things’ and allows her to contribute and share her knowledge and experience. “By contributing, I hope to make a difference in someone’s life. I hope they feel the benefit of using WordPress and want to give back to create a healthier WordPress community.”
\n\n\n\nThank you to Abha Thakor (@webcommsat) and Mary Baum (@marybaum) for the interviews and writing this feature, and to Devin Maeztri (@devinmaeztri) for sharing her story. Thanks to Meher Bala (@meher) for work on the images, and to Chloé Bringmann (@cbringmann) and Collieth Clarke (@callye) for proofing.
\n\n\n\nThanks to Josepha Haden Chomphosy (@chanthaboune) and Topher DeRosia (@topher1kenobe) for their support for the series.
\n\n\n\nThis People of WordPress feature is inspired by an essay originally published on HeroPress.com, a community initiative created by Topher DeRosia. It highlights people in the WordPress community who have overcome barriers and whose stories might otherwise go unheard. #HeroPress #ContributorStory
\n\n\n\n\n\";s: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:\"11678\";s: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: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:49:\"WP Briefing: Episode 21: All Things Block Themes!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wordpress.org/news/2021/11/episode-21-all-things-block-themes/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 29 Nov 2021 12:07: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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11636\";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:436:\"In episode 21 of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy, talks all things block themes with developers and theme specialists Maggie Cabrera and Jeff Ong. Have a question you’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 […]\";s: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/11/WP-Briefing-021.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:26887:\"\nIn episode 21 of the WordPress Briefing, Executive Director, Josepha Haden Chomphosy, talks all things block themes with developers and theme specialists Maggie Cabrera and Jeff Ong.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nJosepha Haden Chomphosy 00:11
\n\n\n\nHello, 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 insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. See, here we go!
\n\n\n\nJosepha Haden Chomphosy 00:40
\n\n\n\nWell, today, folks, in our podcast, I am joined by a couple of special guests. I know it’s been a bit since I’ve had a guest, so I’m very excited to introduce you to who I have with me today. Today, I have Maggie Cabrera and Jeff Ong. They both are working on themes, and especially the future of themes as we move into this low code, no code block based experience of editing things in WordPress. And there have been so many questions lately about what does the landscape of being a theme developer turns into once we move fully into this excellent promise of user empowerment for Gutenberg? I figured who best to come and talk to us about that than these two. So welcome, Maggie. Welcome, Jeff. I’m really excited to have this conversation with you today.
\n\n\n\nJeff Ong 01:39
\n\n\n\nThank you for having us. Excited to be here.
\n\n\n\nJosepha Haden Chomphosy 01:45
\n\n\n\nI’m just gonna hop right in, and we will see what happens. The first thing that I want to chat about, I hear so many questions and so much discussion about patterns in a lot of different places. Like obviously, the work that I helped to steward the most is around like the Block Pattern directory and various other user-facing tools. And so I have never really been able to give a really solid answer about like patterns and how they work inside themes. And so I wondered if you all had anything that you could offer to our listeners to help clarify what is the power of patterns inside themes in the future? Implementation of themes?
\n\n\n\nJeff Ong 02:34
\n\n\n\nI can try to start unless, Maggie? Okay. Well, if you take a look at what I’ve been doing for the last couple of months working on Twenty Twenty-Two. And if you look at that theme, it’s mostly just the collection of patterns. Patterns. As you know, if you read the description, the theme, it’s designed to be the most flexible and kind of like flexible theme ever, dare I say ever created.
\n\n\n\nJosepha Haden Chomphosy 03:04
\n\n\n\nI think you can dare to say it.
\n\n\n\nJeff Ong 03:03
\n\n\n\nAnd, you know, I think a huge part of that is because of the Full Site Editing being launched, introduced in 5.9. And also that theme itself ships with all of these patterns in it that work with the overall design, but really can be configured to your own kind of unique liking and kind of taste and ultimately, what you want to accomplish, whether that’s I want to make a portfolio, I want to make, you know, a single-page website promoting like my podcast, or there are patterns for that kind of shipping with the theme. And they’ve all been kind of designed and tailored to work with the typography choices at a baseline level with the color choices at a baseline level, but can very easily be tweaked. And you can kind of rely on them to work with the editor. And I guess, kind of zooming out for a little bit, not just about Twenty-Twenty Two.
\n\n\n\nJeff Ong 04:04
\n\n\n\nBut like patterns as this idea that a theme, hopefully, what it is, it’s a collection of different design options or layout options that are ultimately presented as patterns to the user, the patterns are just a really easy way to basically say “I want you this layout, like two columns of text or with like some images here.” Basically, a theme becomes a way of packaging the patterns together in a way that feels like a coherent piece of a coherent website. And I think that’s a pretty powerful idea. I know that the patterns directory is also opening up making those patterns pretty widely available. But I think a theme you could think of as like a curation of those patterns in a way that makes sense. And I think Twenty-Twenty Two is a really good example. I mean, I’m biased.
\n\n\n\nJosepha Haden Chomphosy 05:03
\n\n\n\nI also think it’s a good example. Maggie, did you have anything that you wanted to add to that?
\n\n\n\nMaggie Cabrera 05:08
\n\n\n\nYeah, What I really like about patterns is how it empowers the user, even if they don’t really have like a deep knowledge of code, or they’re not used to the more complex blocks. When the theme developer gives you this pattern about using the query block, for example, it lays out your posts in a very compelling manner. And you can edit it if you want it or just use it out of the box. And you have this dynamic blog that it’s, like, such a big important part of your website. Like if you want to have a page where you have, you have maybe a podcast website, and you want to showcase your podcasts differently than your regular blog posts. So you can use a different gray pattern for that. And it’s like, really, really easy to use, even if you’re not familiar with it.
\n\n\n\nJosepha Haden Chomphosy 06:07
\n\n\n\nOne of the things that I have found compelling about this new version of themes and kind of the way that themes are planning to look in the future; it’s going to be like a super throwback, so everyone get ready for me to sound old, my guests and my listeners alike. It reminds me of my original days of blogging on the web. I was not a developer and even though I had this really short stint of working with JavaScript in my career, at some point. Like no one actually would ever look to me and be like, that one is excellent at design and fixing everything with code, like I was just killer at searching for the right pieces of code, right.
\n\n\n\nJosepha Haden Chomphosy 06:57
\n\n\n\nAnd so I remember sitting there on Zynga, which is, of course, now powered by WordPress, I absolutely just went out and found bundles of code that are now what we would consider themes and modified the small pieces that I needed to change in order to like really suit what I wanted to have happen on the site at the time. And they’re like, I knew I could break it all. Really easily. But also, it was, it was not scary to think about breaking it. Like it was clear how I could fix it if I really broke it. The content, like what I had written, was separate from everything to do with the way that it was looking. And so like, I wouldn’t destroy all of my work, just because I didn’t put a semicolon in the right place, or whatever it was in that moment. And so like, this future of themes really reminds me of this a lot where someone has curated how it can look how it should look. And you can just like add in modular pieces that will augment what was already intended, but still kind of work. And if it’s not gonna work, it’s kind of easy to fix too. So like, I’m excited. That was a really exciting time in my learning of the web and certainly was formative in my career, as we all now see. And so yeah, I think that’s really exciting.
\n\n\n\nJosepha Haden Chomphosy 08:20
\n\n\n\nI did have actually another question that this conversation has kind of brought up for me. I have, obviously just use the term modular, which no one has ever used in the context of themes for WordPress. And I know that there is a lot there are a lot of terms kind of wandering around about themes right now. And especially as we’re moving into what themes can look like in the future. There was block based theme as a term for a while. And now it’s block themes. There was like this floating around the term, universal themes. And now we’re looking at just like block themes forever. And so I wondered if y’all could give us a just like a clear understanding of these terms that had been being used and maybe are going out of fashion? Like, are they important for us to keep knowing?
\n\n\n\nJeff Ong 09:11
\n\n\n\nSo yes, the history of terms around themes. And obviously, even my knowledge only goes back so far. But it was around when we started doing the block based themes meeting. And trying to I think that’s where that term kind of came from is like, oh, let’s, let’s start talking about this idea that themes can be completely made up out of blocks. And what does that mean?
\n\n\n\nJeff Ong 09:33
\n\n\n\nI think over time, it wasn’t just block themes, because, you know, previously, there were themes and even default themes that used and took into account the fact that blocks existed. So there was some confusion there. Enough time has gone on where we focus on this idea that themes whose templates are ultimately made out of blocks are block themes. And to me, it’s kind of as simple as that. Its themes that supply a set of templates that previously in the past were a collection of PHP and various template tags and whatnot is all transitioned to themes made up including other blocks, as well as themes that supply styles through theme.json configuration instead of supplying it in raw CSS. To me this idea is really crystallizing around like this is a block theme, one that is really, at its core, supplying a set of templates, and styles through a language that WordPress understands natively, and can allow it to be configured and customized in a really powerful way. And then maybe someday in the future, they’ll just be called themes again. If we do a good enough they will just be called themes.
\n\n\n\nJosepha Haden Chomphosy 10:57
\n\n\n\nI’m gonna, I’m gonna take us into a philosophical area now that you’ve just put us in there. You said, someday they’ll be called Themes. Again, I’ve talked about this on this podcast a few times. And for anyone who’s worked with me for any length of time, like you all probably heard this from me as well. But like, adjectives are so frequently the realm of things that are not what you expect, right? Because like you have coffee, and then decaf coffee, no one’s like caffeinated coffee, because that’s what you expect out of it. And so when you’re like themes, and block themes, it makes it look like block themes are secondary, which at the moment, they are, ish. But in the future, I think you’re probably right, there will be a time when the modifier isn’t necessary anymore because it will be hopefully a much better way for people to kind of change the way that their themes work and make it more usable for users and people who are, you know, having to manage their own site without necessarily wanting to or being able to, like, have a Maggie in the room to fix everything that they break.
\n\n\n\nJosepha Haden Chomphosy 12:08
\n\n\n\nMaggie is nowhere near me. And so she’s never been in the room when I’ve broken anything. But I believe that Maggie on one occasion, at least, has come in and helped me fix something that I definitely broke. I’m an excellent breaker of WordPress things. Maggie, did you have anything you wanted to add to that question?
\n\n\n\n12:29
\n\n\n\nYeah, I guess, maybe clarify a bit, what universal themes are because, yeah, maybe some people have heard about the term but they don’t really know what they are. And maybe just clarify that. The term was born when developing block themes wasn’t something that you could actually do for production websites like you could build them to test some experiments, but they weren’t really ready for users to use. So universal themes want to grasp the power of love themes while still being ready for users. So the way they do it is they are block based, like we used to call them in the sense that the templates are made of blocks. But they are also able to be customized using the customizer, which is the old way of customizing themes, instead of using the site editor. So they can have a balance between two worlds between the worlds of classic themes and block themes. But they are, at heart, a temporary concept. They are bound to be blocked themes in the future, but with maybe a foot in the past, where they can actually serve users who are not ready for full-on site editor. But they are bound to be full block themes in the future.
\n\n\n\nJosepha Haden Chomphosy 14:00
\n\n\n\nThere’s a really interesting concept in there. So universal themes, it sounds like are basically kind of like an on-ramp for people who are not really ready to fully commit to this for any number of reasons. Like we never want to say that we know the reason that people would be a little bit shy to get started with this. But like it’s kind of like an on-ramp, it’s a safe way to get back to something that they do know, in the event that what they don’t know, really hinders their progress makes it hard for them to get the work done.
\n\n\n\nMaggie Cabrera 14:31
\n\n\n\nI think I wouldn’t say that they are for people shyer to get into new stuff rather than developers who want to embrace the new stuff before it’s even really ready. They really want to embrace the power of the blocks instead of doing things the old way. But even if it’s not fully ready.
\n\n\n\nJeff Ong 14:54
\n\n\n\nThey still need to support the old way of doing things.
\n\n\n\nMaggie Cabrera 14:58
\n\n\n\nLike being backward compatible and being ready for any kind of user.
\n\n\n\nJosepha Haden Chomphosy 15:05
\n\n\n\nSo mostly for developers, everyone who heard me just talking about how it was a great thing for users, ignore it.
\n\n\n\nMaggie Cabrera 15:12
\n\n\n\nIt’s also good for users; If they feel secure in using the customizer.
\n\n\n\nJosepha Haden Chomphosy 15:20
\n\n\n\nWell, I think that there’s something important here that we certainly learned with the adoption of Gutenberg in 5.0. Right, which is that there is certainly one method of helping people to adopt things, which is to go like the art of war style, and kind of smash their rice pots and burn all their boats, like, that’s one way. Which works for a lot of companies in the world, I’m sure. But WordPress has always had kind of a commitment, not even kind of, has always had a commitment to backward compatibility. And like, we know that a lot of the work on Gutenberg is going to represent some breaking changes around the around workflows and around the user experience the interface, especially like, we know that. But the opportunity to like have a thing that gives you an early taste of what’s coming but also the ability to keep kind of working in your old space where you need to, I think it’s an excellent way to bring people forward into the future of things, I have never been a fan of the just like cut off all avenues and hope that they stay with your method because of course, like you can’t cut off all the methods. You can’t cut off all the ways people can get away from you. And even if we could, it wouldn’t be in line with how WordPress hopes to kind of help people through some tough stuff like making your first website is hard. If you are doing it as part of, an overall campaign that’s supposed to bring in leads for you or generate revenue like you don’t want to necessarily play with that in a way that could break things and be risky for you in the long term. So I think all the tools that we offer to help people kind of move forward with the technology move forward with the CMS as it’s moving forward, I think it’s really smart. And so universal themes are one of those things, but also not around to stay. As we move into non modified themes, just the word themes that happen to be based in blocks. If I’ve confused anyone, please email me at wpbriefing@wordpress.org. And tell me how I confused you. And I will do a follow-up to unconfuse everyone.
\n\n\n\nJosepha Haden Chomphosy 17:40
\n\n\n\nSo speaking of the way that we help people kind of move forward with WordPress and with the technology. So much has been done in the CMS in the past 12 months in the past 18 months to be able to move themes into this same future as the rest of the editor. Right. So like, for folks who have not been listening to me for the last five years, you may not know this. So I’m going to tell everybody now, like one of the pain points that Gutenberg overall is solving is the fact that you for a long time had to learn five different editing interfaces to get one thing done in WordPress, right. And so like the advent of blocks and moving it into more and more spaces in the CMS is intended to really flatten the editing experience by making the type of user interaction the type of workflow really similar across all of the editing interfaces in the CMS. And so themes are a natural extension of that, where we can take similar user patterns and workflows, and work them out into themes. So over the last 12 months or so probably a little bit more, there’s been a lot of work on the CMS to move us forward in that that is now enabling the work that we want to be able to do to move things forward ahead. And so, I mean, this is probably our last question. Is there anything that you all want to offer to people who maybe saw themes early on or saw Gutenberg early on and felt like this is just not for me, in that in that context of like, how far it’s moved ahead in the past 12 months or so.
\n\n\n\nJeff Ong 19:23
\n\n\n\nSo you’re asking like, what in the last 12 months has maybe like really surprised me or like sticks out to me as something that like, Wow, look how far we’ve come?
\n\n\n\nJosepha Haden Chomphosy 19:36
\n\n\n\nYeah, yeah. So like, if you’re looking at what is the one thing that you saw in the last 12 months, that changed in the CMS that really enabled something wonderful for themes or from the other side of it. Like if someone had looked at themes or WordPress 18 months ago, and now they’re looking at it and seeing this new and different way to do things with the look and feel of their site, like what is one thing that they should be aware of? On either side of that question,
\n\n\n\nMaggie Cabrera 20:05
\n\n\n\nI think there’s more than one thing that has really evolved through this last year, year and a half. Like the maturity of some of the blocks is astounding now, like navigation blog, for example, was really bare-bones at the start and now it’s full potential, and it’s really looking really great. I would say the same thing about those days or the features on fire, like how basic it was at the start, was full potential. But now it’s really, really mature in terms of how much you can do with it. Like, I think the example, the perfect example of that is the work that Kjell [Reigstad] has done on Twenty-Twenty Two with the alternative theme.json files, where just changing that file basically feels like a new theme, with just the configuration and the styles. And without writing any CSS without changing any templates. It’s really, really amazing how that can turn into a reality. And it’s so easy for users to tinker with that if they want to. And it’s much easier than having to delve deep into CSS and changing everything in like 2000 lines of code.
\n\n\n\nJeff Ong 21:23
\n\n\n\nYeah, I probably would echo most of that. What the thing that astounds me is global styles and how the UI can be shipping a theme or default theme with basically like, 20 lines of CSS, and have it be one of them. A beautiful, beautiful, like crisp and sharp, like, experience. It’s super fast. And it’s like, what this is a theme, you know, I thought a theme was supposed to supply all the styles like no, like, it’s just yeah. And workers do for you. Exactly. And like that. That’s pretty amazing to think in the last 12 months, we can go from, you know, shipping 1000s of lines of CSS to you none, it’s like, Wow, pretty cool.
\n\n\n\nJosepha Haden Chomphosy 22:10
\n\n\n\nWell, my friends, thank you so much for joining me today. This has been a really interesting conversation. I hope that all y’all out listening. Also find it interesting. As I mentioned, if you have any follow-up questions, absolutely. Send them to me via email. And I collect all of my questions that I get through the year for answering at the end of the year, mostly because I don’t get lots of questions that people want to be answered on this. Everyone just asked me their questions on Twitter and in Slack, which is fine as well.
\n\n\n\nJosepha Haden Chomphosy 22:41
\n\n\n\nSo, Maggie, Jeff, thank you both for joining me. And I’m sure that we’ll talk to you all again soon.
\n\n\n\nJosepha Haden Chomphosy 22:56
\n\n\n\nThat brings us now to our small list of big things. In the last episode, I got all excited about being in the beta phase. But today, I’m rolling that back a little bit. As part of our usual open source processes, a group of contributors did a deep dive review on the WordPress 5.9 release and found a workflow that needed some refinement. So we are delaying the beta.
\n\n\n\nJosepha Haden Chomphosy 23:19
\n\n\n\nSince we are in the midst of a major commerce slash/sales season, and of course, a lengthy holiday season, that delay also means that it makes sense to delay WordPress 5.9 final release a little as well. And so we are delaying that all the way into 2022 to January 25. For me, the trade-off works really well there. Every decision that we make in open source, of course, has some balance to it. It’s great for these aspects, it is less great for these aspects over here. But for myself, the opportunity to make sure that we have a really excellent experience for our users and also an opportunity to kind of avoid all of the chaos and hustle and bustle of the end of the year. Really, it seemed like a no-brainer for me. So in case you want to learn a little bit more about why we made the decision and get some insight into the actual milestones and where they have moved now, I’ll include some posts in the show notes below in case you want to read more and of course, if you have any additional questions you can always ask.
\n\n\n\nJosepha Haden Chomphosy 24:33
\n\n\n\nThe second small list of big things is that the first back to people WordCamp. I don’t think that’s what we’re calling it. Our first back to people WordCamp is happening in a couple of weeks actually. WordCamp Sevilla is happening in person on December 11. And I’m so excited I wish I were local, but I’m not so if you are local stop by their website and pick up your ticket.
\n\n\n\nJosepha Haden Chomphosy 24:55
\n\n\n\nAnd the third thing on our smallest a big things is that it is, of course, charitable giving season. I don’t know if you do your charitable giving at the end of the year or if that’s even part of your general ways of giving back. But I can think of two or three charitable organizations inside the WordPress ecosystem. There’s of course the WordPress Foundation, but also Big Orange Heart and HeroPress. If there are others out there, I certainly do want to know about them. WordPress Foundation also does additional giving on behalf of just like the open web and open source as a whole. So if you’re the sort of person who does their charitable giving at the end of the year, just a reminder that you have some options inside the WordPress ecosystem if you were trying to figure out some new places to donate to in 2021.
\n\n\n\nJosepha Haden Chomphosy 25:42
\n\n\n\nAnd that is your small list of big things. Thank you so much for tuning in today for the WordPress Briefing. Thank you again to our special guests, Maggie and Jeff. I’m your host Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\";s: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:\"11636\";s: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:57:\"\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:68:\"Watch State of the Word at a Watch Party with your WordPress Friends\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"https://wordpress.org/news/2021/11/watch-state-of-the-word-at-a-watch-party-with-your-wordpress-friends/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 24 Nov 2021 18:30:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11641\";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:322:\"State of the Word 2021 is just around the corner! Although attending State of the Word in person would be ideal, not all WordPress community members get to enjoy the experience of attending the speech live with friends. This year, as State of the Word is streamed live for the second time, we want to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Hari Shanker R\";s: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:20064:\"\nState of the Word 2021 is just around the corner!
\n\n\n\nAlthough attending State of the Word in person would be ideal, not all WordPress community members get to enjoy the experience of attending the speech live with friends.
\n\n\n\nThis year, as State of the Word is streamed live for the second time, we want to restore that in person camaraderie through State of the Word watch parties for WordPress Community members around the world.
\n\n\n\n\n\n\n\nWe encourage WordPress meetup organizers and community members worldwide to (safely) host State of the Word 2021 watch parties —read this handbook to learn more.
You can choose to host a watch party online or in person. Check out our handbook for detailed instructions on how to schedule an event (including event templates).
\n\n\n\nThe simplest way to organize an online watch party is to schedule an online event for your WordPress group and add the State of the Word YouTube streaming link directly on Meetup.com. Alternatively, you can schedule an online meeting using tools like Zoom and broadcast the live stream over there by screen sharing––thereby facilitating better engagement.
\n\n\n\nIf your region meets the guidelines for in person events (if vaccines and testing are freely available), you can organize an in person watch party event (for fully vaccinated OR recently tested OR recently recovered folks) for your WordPress Meetup! Group members can hang out together (following local safety guidelines of course) and watch State of the Word live.
\n\n\n\nNOTE: If State of the Word is happening at an odd hour in your timezone, you can still organize a watch party by organizing a replay of live stream, at a date/time that is convenient for your group.
\n\n\n\n\n\n\n\nIf your Local WordPress Meetup is organizing an in person watch party, fill out this form so that we can ship some swag for your group to celebrate!
Deadline: November 30, 2021
Excited? To help you get started, we’ve put together a few resources:
\n\n\n\n\n\n\n\nNOTE: The guidelines in this post are primarily aimed at WordPress Meetup organizers. However, you do not need to be a Meetup organizer to schedule a watch party! You can simply hang out together with your friends online or in person (while following local safety guidelines) and catch the event live!
We have compiled a list of State of the Word Watch Parties around the world. If you don’t see a watch party in your region listed here, check this page on Meetup.com to see if your local WordPress group is organizing one. If not, why don’t you consider organizing a watch party on your own? ![\"🙂\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f642.png\")
![\"🇺🇸\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1f8.png\")
[WordPress NYC Meetup] An In Person MeetUp: The State of the Word 2021 is in Manhattan. [South Jersey WordPress Meetup] JerseyPress: State of the Word 2021 Watch Party [Morris County NJ WordPress Meetup] JerseyPress: State of the Word 2021 Watch Party [WordPress Montclair Meetup] JerseyPress: State of the Word 2021 Watch Party [WordPress Santa Clarita Valley] State of the Word 2021 Watch Party [The Houston WordPress Meetup Group] State of the Word 2021 Watch Party (Online) [North East Ohio WordPress Meetup] State of Word 2021 Watch Party (Online) [Birmingham WordPress Meetup] State of the Word Watch Party [Lehigh Valley WordPress Meetup] State of the Word 2021 Watch Party (Online) [Metro Detroit WordPress Meetup] State of the Word 2021 Watch Party (Online) [Greater Milwaukee Area WordPress Meetup] State of the Word 2021 Watch Party (Online) [The East Bay WordPress Meetup Group] State of the Word 2021 (Online) [Sacramento WordPress Meetup] State of the Word 2021 Watch Party (Online) [WordPress Louisville] State of the Word Watch Party and Discussion (WP Louisville, KY)![\"🇨🇴\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1e8-1f1f4.png\")
[WordPress Medellín] State of the Word 2021: Discurso de Matt & Fiesta de Comunidad (Online)![\"🇭🇹\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ed-1f1f9.png\")
[Port-au-Prince WordPress Meetup Group] Rejoignez-nous le 14 décembre pour regarder State of the Word 2021 (online)![\"🇬🇧\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ec-1f1e7.png\")
[WordPress Coventry Meetup] State of the Word 2021 Watch Party (Online) [WordPress Exeter] State of the Word 2021 Watch Party (Online)![\"🇮🇹\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ee-1f1f9.png\")
[WordPress Meetup Torino] State of the Word 2021 Video Party (Online)![\"🇷🇼\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f7-1f1fc.png\")
[Kigali WordPress Meetup] State of the Word 2021 Watch Party (Online)![\"🇳🇬\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f3-1f1ec.png\")
[Lagos WordPress Community] State of the Word 2021 Watch Party (Online) [Ijebu WordPress Meetup] State of the Word 2021 Watch Party (Online)![\"🇺🇬\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1fa-1f1ec.png\")
[Jinja WordPress Meetup] State of the Word 2021 Watch Party – WordPress Community Uganda (Online) [Kampala WordPress Meetup] State of the Word Livestream![\"🇵🇰\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f5-1f1f0.png\")
[WordPress Meetups Lahore] State of the Word 2021 Watch Party (In-person)![\"🇮🇳\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1ee-1f1f3.png\")
[WordPress Bhopal] State of the Word 2021 Watch Party (In-person) [Bengaluru WordPress] WordPress Meetup – State of the word -Watch Party![\"🇸🇬\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f1f8-1f1ec.png\")
[WordPress Singapore] State of the Word 2021 Watch Party (Online)If you are planning a watch party for State of the Word, and have questions, please drop us an email to: support@wordcamp.org if you have any questions. We are happy to help you in the best way possible.
\n\n\n\nThe following folks contributed to this post: @anjanavasan @eidolonnight @evarlese and @rmartinezduque
\n\";s: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:\"11641\";s: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: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:23:\"A Look at WordPress 5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wordpress.org/news/2021/11/a-look-at-wordpress-5-9/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 Nov 2021 21:02:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:6:\"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:\"\";}i:1;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:2;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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11625\";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:322:\"WordPress 5.9 is expected to be a ground-breaking release. It will introduce the next generation of themes with Twenty Twenty-Two joining the fun and over 30 theme blocks to build all parts of your site. In anticipation of the January 25th release, we hope you enjoy this sneak peek of 5.9. New design tools will […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Kelly Hoffman\";s: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:2987:\"\nWordPress 5.9 is expected to be a ground-breaking release. It will introduce the next generation of themes with Twenty Twenty-Two joining the fun and over 30 theme blocks to build all parts of your site. In anticipation of the January 25th release, we hope you enjoy this sneak peek of 5.9.
\n\n\n\nNew design tools will allow you to create exactly what you want, from adding filters to all your images to fine-tuning the border radius on all your buttons. With WordPress 5.9 providing more design control along with streamlined access to patterns, you can easily change the entire look and feel of your site without switching themes.
\n\n\n\nNo matter what you’re editing, whether it’s crafting a new post or working on a header, improvements to List View make it simple to navigate content regardless of complexity. More improvements and features for everyone are to come in this release and we can’t wait to see what you create with WordPress 5.9!
\n\n\n\nStay tuned for more updates as the date draws near. If you want to help, the best thing you can do is test everything! For all the details, check out this Make Core post.
\n\n\n\nVideo props: @annezazu (also co-wrote the post) @michaelpick @matveb @beafialho @javiarce @critterverse @joen.
\n\";s: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:\"11625\";s: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:57:\"\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:56:\"Join us for State of the Word 2021, in person or online!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://wordpress.org/news/2021/11/join-us-for-state-of-the-word-2021-in-person-or-online/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 22 Nov 2021 21:08: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11611\";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:297:\"As previously announced, State of the Word will be livestreamed from New York City. That means that you can join the fun either online or in person, on December 14, 2021, between 5 and 7 pm EST! To join State of the Word 2021 online, check your Meetup chapter for a local watch party, or […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:1726:\"\nAs previously announced, State of the Word will be livestreamed from New York City. That means that you can join the fun either online or in person, on December 14, 2021, between 5 and 7 pm EST!
\n\n\n\nTo join State of the Word 2021 online, check your Meetup chapter for a local watch party, or simply visit wordpress.org/news, where the livestream will be embedded.
\n\n\n\nIf you would like to participate in person in New York City, please request a seat by filling out the registration form by Sunday, November 28. Not all requests will receive a seat due to venue capacity, but everyone who requests one will receive further notification on Tuesday, November 30.
\n\n\n\nIn person attendees will be asked to show their COVID vaccination card at the venue entrance, and are expected to follow the safety measures in place. Because of these safety measures, there is a maximum of 50 attendees.
\n\n\n\nWhether you participate in person or online, we are so excited to see you on December 14! Don’t forget, State of the Word will be followed by a Question & Answer session. If you have a question for Matt, you can send your question ahead of time to ask-matt@wordcamp.org, or ask during the event in the YouTube chat.
\n\";s: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:\"11611\";s: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: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:44:\"WP Briefing: Episode 20: WordPress=Blogging+\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"https://wordpress.org/news/2021/11/episode-20-wordpressblogging/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Nov 2021 12: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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/?post_type=podcast&p=11556\";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:386:\"In this episode, WordPress’s Executive Director, Josepha Haden Chomphosy, answers two recently asked questions. Tune in to hear what those questions were and her response, in addition to this week’s small list of big things. Have a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording. Credits […]\";s: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/11/WP-Briefing-020.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:10275:\"\nIn this episode, WordPress’s Executive Director, Josepha Haden Chomphosy, answers two recently asked questions. Tune in to hear what those questions were and her response, in addition to this week’s small list of big things.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nJosepha Haden Chomphosy 00:10
\n\n\n\nHello, 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 insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 00:40
\n\n\n\nSo I was in a meeting recently, which I realize isn’t saying much for me since I spend a quarter of my time in meetings. But in this particular meeting, I was asked a couple of questions that I absolutely loved. The first question was, “if there were one thing you could change in people’s minds about WordPress, what would it be?” And my answer, predictable though it may be, was that I want to change the idea that WordPress is just a blogging platform.
\n\n\n\nJosepha Haden Chomphosy 01:06
\n\n\n\nWordPress has grown into a lot more than that. But the idea of a content management system, even now, sometimes gets a mental shorthand where content is a stand-in for the word writing or words. If you’re using WordPress today in an enterprise context, or as part of a governmental agency, or if you use it in a classroom setting, you know that your content cannot be confined that way. And if you’re supporting or building anything to hand off to clients, you know that timely, easy-to-ship changes on a site are considered a vital part of any overarching brand and marketing strategy. And when was the last time that any marketing strategy was literally only about the words?
\n\n\n\nJosepha Haden Chomphosy 01:51
\n\n\n\nSo that was the first question. And also my first answer. There is also this kind of annual, not fear, necessarily, but this annual question that is sort of related that is raised to me and has been asked of me recently, that I’m just going to give you a small answer to. One annual worry that I get every year around November and December is, “What are we going to do about the fact that the term blog and blogging are declining in search popularity?” And I was gonna say it’s been a while since I answered that in any sort of public format. But I think maybe I’ve never answered it in a public format at all. And so I’m just going to answer it here. Because I think maybe a lot of people have that same question.
\n\n\n\nJosepha Haden Chomphosy 02:36
\n\n\n\nSo number one, I think that the way that people search now is different. There’s a lot more semantic cognition. This is not the way to answer this — search engines are smarter now. So like, it used to be the case with early search engines that yeah, there was a lot of just like, individual search terms that were looked for. But now, people are asking full questions; they have, essentially, an entire sentence that they are searching for. And then, search engines are able to parse that information better and get more high-quality answers and information for them. So like, that’s one thing that I’m already not worried about. If people are searching for individual words anymore, it’s so that they can get a definition of that word. So I’m not specifically worried about a decline in search volume for the word blog or blogging for that reason. But the answer to my first question, if there is probably the real reason that I’m not actually super worried about any decline in search volume for the word blog, or blogging, is that WordPress has really moved beyond that. And since we have moved beyond that, then it doesn’t necessarily make sense for WordPress as an entity for WordPress as a project to get overly hung up on the idea that the term blog has gone out of fashion.
\n\n\n\nJosepha Haden Chomphosy 03:52
\n\n\n\nOkay, now that I did my first question, and the answer, and then an additional question that only ever gets asked in private and is being answered by me for the first time in public, I will tell you now, the second question that I loved, someone asking of me, and that question is this: “What is one thing you’d like people to see or experience, right when they first land on wordpress.org?” Now, I often don’t get asked questions about the wordpress.org website, like administrative tasks, things that we need to update, move around where they should go. Sure. But like, “Josepha, what’s the point and purpose of this site?” Never. I’ve never been asked that, and so I was really excited that someone asked me, and I’m going to give you a heads up. I think some of you might disagree with my answer.
\n\n\n\nJosepha Haden Chomphosy 04:40
\n\n\n\nSo the primary thing that I want people to see or experience when they first get to wordpress.org, the website is the depth of WordPress. Not which audience segment they should belong to or that we believe they should belong to or raw data about the CMS or even how much we care about the freedoms of open source. Now the first thing I want people to see on that site is that WordPress has not only 18 years of learned knowledge that every single new user benefits from, but that it also has 1,000s of really smart people making sure it works and gets better every day, now.
\n\n\n\nJosepha Haden Chomphosy 05:19
\n\n\n\nWordPress is a Goliath in its field. I know that we cite this bit of context. Frequently, we say that we are 42% of the web. And that is true that is the percentage by usage. But in its field, which is websites that are using a content management system, we actually have a 65% market share. This is very easy to find. It’s on the W3Techs website: I can put a link in the show notes, but you could find it just by searching for it.
\n\n\n\nJosepha Haden Chomphosy 05:46
\n\n\n\nSo WordPress is a Goliath in its field of websites that are run using a CMS. Because we have always brought our learnings forward with us with the understanding that knowledge, when shared grows rather than diminishes. But open source, the heart of what defines this project, open source is not a Goliath; it’s barely even David somedays. Even though the web is built on scads of open source software, there’s a pervasive public perception that it is built by and for hobbyists or that it is inherently risky, and that if there were if it were worth something, then people would pay something. And I just know that if the first impression of WordPress, we’re, “we’ve got 18 years of experience and learning that brought us to today,” the rest of the sale to adopt software that protects other people’s freedoms would take care of itself. And I guess, to quote John Oliver, at this point, “And now this.”
\n\n\n\nJosepha Haden Chomphosy 06:59
\n\n\n\nAlright, that brings us now to our small list of big things. There are actually quite a few big things on this small list today. So number one, we have reached the beta phase for the year’s final release, which means that WordPress 5.9 beta one is happening tomorrow, Tuesday, November 16. And then seven days later, I believe on the 23rd, if I recall correctly, comes beta two.
\n\n\n\nJosepha Haden Chomphosy 07:24
\n\n\n\nThe second thing on my list is that team rep nominations are happening all over the project right now. I’ve got a post that I will share in the notes below that I believe all the team reps have put their team’s nomination posts on. So if you have had an interest in learning more about that and what it means to help keep teams kind of running in the WordPress project, then this is a great opportunity to check those out.
\n\n\n\nJosepha Haden Chomphosy 07:49
\n\n\n\nAnd the third thing, this last thing actually isn’t in the next two weeks, but it is very important, nonetheless. Matt’s annual State of the Word is coming up on December 14. So basically a month from today. It’s going to join the growing list of in-person events that are on the calendar. It will be in New York City but will also be live-streamed across the world as usual. Keep an eye out for additional updates about that for anyone who, like me, really looks forward to this particular presentation from our project co-founder every year.
\n\n\n\nJosepha Haden Chomphosy 08:25
\n\n\n\nAnd that is your small list of big things. Thank you for tuning in today for the WordPress briefing. I’m your host, Josepha Haden Chomphosy, and I’ll see you again in a couple of weeks.
\n\";s: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:\"11556\";s: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:\"Mon, 24 Jan 2022 10:18:35 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:\"Tue, 18 Jan 2022 22:28:12 GMT\";s:4:\"link\";s:63:\"Well, who would have thunk when I started the newsletter in 2018, that I will still be doing it four years later. Welcome to the 200th edition! A huge “Thank you” to you, dear reader, for browsing and reading it week after week.
\n\n\n\nI am also deeply grateful for the contributors working on the block editor and the theme and plugin developers building on top of it. I am an absolute fan and love to be a scribe of your work and art. And there are others in the community who write, test, and build sites with it. All your encouragement, tips, news and conversations, make working on this newsletter an absolute pleasure.
\n\n\n\nBesides the weekend editions, we also publish other articles. There might be more in the future, too. Let me point you to two here.
\n\n\n\nDon’t miss Anne McCarthy’s article How 5.9 creates a strong foundation for the future. She wrote about the various features the developers are working on and how to participate in the process.
\n\n\n\nAs a reminder, I list here the WordPress 5.9 Reading list for FSE and Block Themes.
\n\n\n\nAnd now I get out of the way to the rest of the Gutenberg news. Have a great weekend,
\n\n\n\nYours, 💕
Birgit
PS: Last Monday, I was having great fun with the members at the WordPress Meetup in Boulder on a panel with Brian Gardner and Courtney Robertson. discussing various aspects of the upcoming WordPress 5.9 Release. The video and the document with questions and links are now available. Huge Thank you to Angela Bowman for the invitation. She is a wiz with excellent moderating and live demoing skills and she was doing both at the same time.
\n\n\n\n\nTonya Mork, release coordinator for WordPress 5.9 invites you to join the team for the WordPress 5.9 Release Party 🙌 on Tuesday, January 25th, 2022 at 11 am ET / 16:00 UTC. You bring your favorite beverage and cookies, as it all will happen in the #core channel on WordPress Slack. You would need to have an account there.
\n\n\n\nThe BuddyPress Team released the 10.0 version. In his release post Mathieu Viet wrote: “We’ve adjusted our BP Theme Compatibility API so that you can enjoy this amazing feature, making sure that BuddyPress-generated content integrates optimally within themes supporting it.”. Take a look at the rest of the post as the team added some neat features to the social networks plugin for self-hosted WordPress sites.
\n\n\n\nIn a separate note, Viet also announced that the new version won’t load legacy widget by default anymore. Details in this separate note by
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
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. The index 2020 is here
Alex Lende published the release notes for this week’s release: What’s new in Gutenberg 12.4 (19 January )
\n\n\n\nThe highlighted features and enhancements
\n\n\n\nIn a new section he also give kudos to first time contributors for their first merged PRs in this release.
\n\n\n\nFor the 59th episode of the Gutenberg Changelog podcast, my co-host, Grzegorz Ziolkowski and I were delighted to have Fabian Kägy as our guest on the show. We discussed Gutenberg 12.4, Developer Hours, how to best implement extensibility of the block editor and much more.
\n\n\n\nNever miss an episode again 🙂
\n\n\n\nSubscribe to the Gutenberg Changelog podcast
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed
On the WPTavern, Justin Tadlock, took the new Gutenberg release for a spin. Gutenberg 12.4 Includes Accessibility Improvements, Categories Reminder, and a Tag Cloud Outline Style
\n\n\n\nCheck out Fabian Kägy’s project: Gutenberg Playgrond enables a way to embed a browser-based coding experience of example code within a post. This allows the reader to modify that code on the fly and see the changes, without a build steps or setting up a local dev environment. The project is in its infancy and was inspired by the beta of ReactJS new documentation site. We spoke with Kägy about that project on the Gutenberg Changelog #59
\n\n\n\nFor February and March, we plan a series of Developer Hours, for theme, plugin, freelance, or agency developers to get their burning questions about building blocks, and other feature for the block editor answered. Expert panelist, developers from the Community will be available to discuss code problems, different approaches to solve a problem or just bounce of ideas for future development. You can read more about the details in this Proposal on the Make Blog.
The first event will take place on February 8th, 2022 at 11 am ET / 16:00 UTC with Tammie Lister, Fabian Kägy and Nick Diego. You can register via the WordPress Social Learning space on Meetup.
\n\n\n\nMarie Comet has to convert content created with the Classic Block to Block and found that tables carefully created, would to be so beautiful when converted to a table block. Her plugin Gutenberg-Convert-Table-Classic, taps into the conversion script and keeps tables in Custom HTML blocks instead. If you ran into a similar problem, modify your plugin as you see fit.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s main (trunk) branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Joe Dolson who works as an accessibility consultant and is part of the WordPress Accessibility team posted an answer to those who mocked the WordPress project for hundreds of open accessibility issues on the GitHub repository. It’s rather a sign of increased focus on accessibility. But read for yourself Don’t judge progress by the number of open issues.
\n\n\n\nFor the Torque Magazine, Nick Diego, developer advocate at WPEngine, wrote about Guide to Explorie Block Patterns and answers questions as the Why used them, where to find them and how to use block patterns.
\n\n\n\nAsk the Bartender: Are There Any Compact and Personal Block Themes? “By “compact and personal,” I think of something like a small room cramped with all your belongings, photos, postcards, etc., giving it a cozy feeling (Tumblr themes kind of fit this). ” wrote the person asking the question. Justin Tadlock has some suggestions for her. “Right now, I only know of one block theme that fits into the compact-and-cozy category, and that is Kubrick2. I covered it in detail last month in a review. It is now live on WordPress.org.” Tadlock wrote.
\n\n\n\nAnne McCarthy is chipping way on the long list of End-user Documentation for WordPress 5.9 and just published the Dimension Controls.
\n\n\n\nA list of more new documentation pages is available in this post WordPress 5.9 Reading List on Block Themes and Full Site Editing
\n\n\n\nTodo plugin by David Towoju
\n\n\n\n“Your todo checkboxes will appear both on the frontend and backend. It will even keep the current state of the checkbox when shown on the frontend.” Towoju wrote.
\n\n\n\nHere is Justin Tadlock’s review on the WPTavern: Create Todo and Checklists in the WordPress Editor With New Plugin
\n\n\n\nNewsletter Glue by Lesley Sim and Ahmed Fouad
\n\n\n\nIn her post, Newsletter Glue released 2.0, Lesley Sim Informs their users about the the brand-new admin settings user interface for the premium version of the plugin. I have been using this plugin since Dec. 2020, and I would not go back to any other newsletter tool.
\n\n\n\nSocial Sharing Block by Nick Diego
\n\n\n\n“A simple little block that allows you to add social share icons to the Block Editor. Choose from 10+ of the most popular social channels.” Diego wrote
\n\n\n\nJustin Tadlock took it for a spin and shared his thought in his article, Nick Diego Forks Core WordPress Block, Creates Social Sharing Plugin.
\n\n\n\nWicked Block Builder by Wicked Plugins
\n\n\n\n“Create your own custom blocks with Wicked Block Builder! ”
\n\n\n\nSeems to land in the same space as Genesis Custom Blocks (former Block Labs), Lazy Blocks, ACF Blocks.
\n\n\n\nYou can learn more in from Justin Tadlock on the WPTavern. Wicked Plugins Launches UI-Based WordPress Block Builder
\n\n\n\nIn his tutorial, An Introduction to WordPress Block Themes, Eric Karkovack takes you on a tour of the different components that make a Block Theme: Template files, folder structure, using theme.json for styling and creating templates. The article is a quick overview with a comprehensive list of resources to learn more.
\n\n\n\nTheme team member, Ganga Kafle started a Twitter Thread with this question:
\n\n\n\n\n\n\n\nWhy are you not submitting block themes in WordPress as you submit classic themes on a regular basis? What are the reasons behind it? Please comment below.
Ganga Kafle on Twitter
Sarah Gooding picked up the answers and put them into bigger context. “Why Aren’t More WordPress Theme Authors Creating Block Themes?”.
\n\n\n\nWhen I saw the tweet, I thought, WordPress 5.9 hasn’t been released yes, how can there be an expectation that there is a mass submission of block themes happening? Some theme developers did anyway. Ahead of Tuesday’s release, 42 Block Themes built for Fullsite Editing are already available in the WordPress Themes directory.
\n\n\n\nJanuary 23, 2022 – 4 pm ET / 21:00 UTC
WordPress: the Next Generation with Sallie Goetsch via The East Bay WordPress Meetup Group
January 24, 2022, 6 pm ET / 23:00 UTC
What Will WordPress 5.9 Mean for You? with Ray and Peter Ingersoll via WordPress Hartford, CT
January 26 , 2022, 1 pm ET / 18:00 UTC
Zero to Block Theme Series #2: theme.json with Daisy Olsen via WordPress Social Learning Spaces
January 26, 2022, 6 pm ET / 23:00 UTC
Intro to Templates and Template Parts (Full Site Editing) with Wes Theron via WordPress Social Learning Spaces
January 28, 2022, 3 pm ET / 20:00 UTC
Demo: Build Your Homepage Using Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
February 4, 2022, 3 pm ET / 20:00 UTC
Beginner’s Guide to Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
February 7, 2022, 12pm (noon) ET / 17:00 UTC
Taking Control Over the Editor for Client Builds with Fabian Kägy via WordPress Social Learning Spaces
February 8th, 2022 11 am / 16:00 UTC
Developer Hours with Birgit Pauli-Haack and expert panel via WordPress Social Learning Spaces
February 9th, 2022 5pm ET / 22:00 UTC
Using Block Patterns with Wes Theron via WordPress Social Learning Spaces
February 11, 2022 – 3 pm ET / 20:00 UTC
Breaking it Down: Blocks, Patterns, And Templates with Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
February 14, 2022 – 4 pm ET / 21:00 UTC
Exploring Theme Blocks with Wes Theron via WordPress Social Learning Spaces
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nBirgit Pauli-Haack and Grzegorz Ziolkowski discuss with their guest, Fabian Kägy Gutenberg 12.4, Developer Hours, and how to best implement extensibility of the block editor
\n\n\n\nSubscribe to the Gutenberg Changelog podcast via your favorite podcast apps!
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed
Show Notes
\n\n\n\nDeveloper Hours – Register for Feb 8th, 2022 at 11 am ET / 16:00 UTC via Meetup
\n\n\n\nGutenberg Playground website
\n\n\n\n\n\n\n\n\n\n\n\nWordPress 5.9 Release Day Process and Party!
\n\n\n\nWhat’s new in Gutenberg 12.4 ( 19 January )
\n\n\n\n\n\n\n\nProposal for opening the editor interface to more extensibility GitHub Discussion started by Fabian Kägy
\n\n\n\nQuery Loop: Add support for custom taxonomies filtering
\n\n\n\nQuery Loop: Add multiple authors support
\n\n\n\nAllow switching global styles variations
\n\n\n\nStay in Touch
\n\n\n\nTranscript
\n\n\n\nTranscript is in the works…
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 22 Jan 2022 19:46: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: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: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:78:\"WPTavern: WP Career Summit Opens Registration, Calls for Speakers and Sponsors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128725\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:199:\"https://wptavern.com/wp-career-summit-opens-registration-calls-for-speakers-and-sponsors?utm_source=rss&utm_medium=rss&utm_campaign=wp-career-summit-opens-registration-calls-for-speakers-and-sponsors\";s: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:3159:\"WP Career Summit is a new event hosted by the Post Status community that will take place on April 8, 2022. The summit is the first of its kind in the WordPress space – an event entirely focused on job seekers and employers.
\n\n\n\nAttendees will have the opportunity to network with each other, check out job postings, visit live virtual sponsor tables, and connect with companies that are actively hiring.
\n\n\n\n“Back in 2020 I saw companies posting jobs and I saw friends posting a need for jobs, and I thought we needed to find a way to match those people with companies,” WP Career Summit organizer Michelle Frechette said. “So I built wpcareerpages.com and started tweeting a job thread every Wednesday.”
\n\n\n\nAfter awhile of regularly tweeting the Wednesday job thread, Frechette found that it started to take off. Depending on the week, her threads would get anywhere from 2k-18k impressions.
\n\n\n\n“Clearly, there is a need,” she said. “I’ve had people tell me they’ve found their new job through those tweets. As a result of that project and conversations with Allie Nimmons around underrepresentation, underrepresentedintech.com was born, and projects and people started getting paired up through that site.”
\n\n\n\nFrechette said when she first joined the team at Post Status, she was tasked with writing about underrepresentation and job-related content, topics for which she has a passion. She pitched the idea of a career conference to Cory Miller, the club’s new owner, and he loved it.
\n\n\n\n“My hope is that this summit is the start of even bigger conversations in the WordPress community about connecting talent with opportunity, especially for those graduating from training and education and starting their careers,” Frechette said. “If we can get younger talent into WordPress, in my opinion, we should see even more growth in our ecosystem.”
\n\n\n\nThe call for speakers and sponsors is now open. Jonathan Wold is managing the sponsorship aspect of the event and Post Status has hired Dan Maby from Big Orange Heart to run the tech part of the conference using the platform he developed and uses for WordFest.
\n\n\n\nOrganizers are looking for speakers who are particularly adept at job hunting or who are knowledgeable about how to recruit and hire talent. Selected speakers will share their expertise in 30-minute recorded presentations and will receive a $200 stipend for participating. WP Career Summit will be a virtual event but will have 15 minutes of live Q&A time immediately following each session.
\n\n\n\nRegistration is now open and is free, thanks to the event’s sponsors. Attendees will be emailed information about how to log in and participate closer to the event.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 22 Jan 2022 02:50:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:70:\"WPTavern: BlackPress Meetup To Host Meet and Greet Mixer on January 27\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=128621\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:185:\"https://wptavern.com/blackpress-meetup-to-host-meet-and-greet-mixer-on-january-27?utm_source=rss&utm_medium=rss&utm_campaign=blackpress-meetup-to-host-meet-and-greet-mixer-on-january-27\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4794:\"Established this year by Destiny Fox Kanno and Joe A. Simpson, Jr, the BlackPress Meetup group will host its first event next week. It will be a meet-and-greet social hour for attendees. The session will run from 7pm to 8pm CST on Thursday, January 27.
\n\n\n\nThere is also a BlackPress Slack group they want to raise awareness about and bring more people in. It can be handy for members to asynchronously communicate about the event, discuss broader topics, and talk with others.
\n\n\n\n“Our goal is to both bring more creators of Black African descent into the WordPress Community and also provide a Community space for those already there to connect, learn from, and support each other,” responded the organizers on the reason for the Meetup. “This Meetup was also created to raise awareness about WordPress, recruit organizers and volunteers, and eventually lead to a WordCamp-style event on an HBCU campus.”
\n\n\n\nKanno is an Automattic-sponsored Developer Relations Advocate from the San Francisco Bay area. She helps global WordPress contributors get the most out of available tools and resources to create products and sites for and with globally-diverse online communities.
\n\n\n\nSimpson is a Digital Communications Administrator at Metro Los Angeles and a team rep for the WordPress Accessibility Team. He is also a Community Deputy, leading three WordCamps and two WordPress-related Meetups in Santa Clarita, California.
\n\n\n\nThe format of the event is an open video chat. There will be a central room where anyone can chime in at any time. However, there will also be some time in breakout rooms if there is a large enough turnout. This would allow more intimate discussions and attendees to speak directly with others.
\n\n\n\nCurrently, the co-organizers are not yet shooting for weekly meetings. “We would love to have a regular schedule like that, but since this group has just started, we are targeting monthly Meetups for now while we build our network and momentum,” they responded. “Once we have regular membership, we will most definitely try to accommodate not only more regular meetings but more meetings in other time zones as well.”
\n\n\n\nThis also plays into how they will run future events and their content. The goal for the first Meetup is to identify the community’s needs. Some example questions they posed were:
\n\n\n\n“Once we get a better understanding of this, we would like to create more targeted events and spaces for folks to knowledge share and collaborate with their peers,” they said.
\n\n\n\nThey are also looking for speakers to present at future events. Anyone interested should let the co-organizers know if they can contribute.
\n\n\n\n“We definitely have ambitions to have our next Meetup event include a speaker for a certain topic — potentially a look ahead for the 6.0 WordPress release,” they said. “We are also hopeful to have a Mega Meetup event as this is a globally-focused group and an end-of-year release holiday party event.”
\n\n\n\nThursday, January 27, 2022
7pm – 8pm CST
Description: Please join us for BlackPress’s first meetup event focused on networking with fellow community members. During this first social hour, we’d like to also talk about what you’d like to see from this meetup group! Do you have a speaker you’d like to invite or a discussion topic for our next meetup? We’re all ears!
\n\n\n\nLooking forward to connecting with you all!
\nOpen source governance and WordPress as a commons have been a hot topic this past couple of weeks. Having both watched the discussion and shared my informal thoughts on Twitter as well as the Post Status Slack group, I was invited to write a lengthier article about the subject.
\n\n\n\nTo begin, here’s a summary of my current thoughts:
\n\n\n\nAs WordPress matures, I believe more open discussion needs to be had about:
\n\n\n\nI agreed to write this article as I’ve long been interested in this topic. It was the excuse I needed to dive headfirst into the multitude of posts, research, and books that I knew existed but didn’t previously have time for.
\n\n\n\nAs it turns out, this article was very difficult to write because the more I learned, the more my views and writing evolved.
\n\n\n\n\n\n\n\nI’m writing this to bring awareness and not blind criticism to these issues. I want to ignite curiosity and conversation around them as I believe they are worth discussing.
Where I’ve landed is a place of empathy, respect, and curiosity. To get to where we are, WordPress’ leaders had to get so much right. It’s impressive, and I’m so glad to be a part of this community.
\n\n\n\nAnd yet, there’s so much more to be done.
\n\n\n\nWhat follows are my thoughts and explorations on this subject. I’m writing them not because I believe I’m smart and/or right, but because:
\n\n\n\nIn short, I’m writing this to bring awareness and not blind criticism to these issues. I want to ignite curiosity and conversation around them as I believe they are worth discussing.
\n\n\n\nThere’s a lack of clarity and distinction around the roles and responsibilities of Automattic, WordPress.com, WordPress.org, and the WordPress Foundation.
\n\n\n\nAs a result, it’s not clear who external and internal parties should turn to for guidance, governance, and more.
\n\n\n\nAs an example, here’s some of the confusing overlap between leadership roles at WordPress:
\n\n\n\nMatt Mullenweg is the CEO of Automattic, the organization that runs WordPress.com: a hosting company. He is also the Director of the WordPress Foundation, a charitable organization he founded.
\n\n\n\nJosepha Haden Chomphosy is an employee of Automattic and the lead for their open source division. She is also the Executive Director of the WordPress Project. As far as I can tell, Josepha has no direct ties to the WordPress Foundation despite the significant overlap in its mission and her job scope.
\n\n\n\nIf all this sounds quite confusing, it’s because it is. Personally, I didn’t even know the WordPress Foundation existed until I did the research for this article.
\n\n\n\nIn fact, Matt and Josepha, themselves, have difficulty delineating where Automattic begins and WordPress.org starts. Here’s an excerpt from Episode 8: The Commons of Images at the WP Briefing, a podcast hosted by Josepha. This episode features Matt talking about Automattic’s acquisition of CC Search, now renamed Openverse:
\n\n\n\n\n\n\n\nJosepha Haden Chomphosy 15:47
I’ve been asked a few times, and I think you have been asked a few times whether this is an actual acquisition. And If yes, then what entity is it under? Is it under the WordPress Foundation? Is it under Automattic?
Matt Mullenweg 16:10
It’s a little complicated because, as you know, WordPress.org is not part of the Foundation. So basically, Automattic paid Creative Commons, the nonprofit. They will essentially redirect the old URL, so old links to Creative Commons Search won’t break. And we ended up hiring some of the people that they were parting ways with into Automattic. And then we put that open source code, and we’ll run the service on WordPress.org, and then those we hired, Automattic hired, will contribute to WordPress.org and the open source projects that power what we’re calling Openverse now.
Josepha Haden Chomphosy 16:54
I am.
Matt Mullenweg 16:56
That’s kind of an acquisition, but also from a nonprofit, and then going into something, which is not a nonprofit, but is open source and sort of freely available, which is WordPress.org, the website.
Josepha Haden Chomphosy 17:06
Yeah, that has been hard for me to answer because you’re right, it’s not like it was donated to WordPress or something. But everything that we’re doing is being donated back to the project, and of course, hopefully, really living into that WordPress ethos that we have of giving back to, to the project, something that made your work and your life better. So there’s some, some finger-crossing going on in there.
Episode 8: The Commons of Images at the WP Briefing.
As you can see, the blurred lines can lead to some very interesting organizational relationships. Many of which are difficult, if not impossible, to untangle.
\n\n\n\nTo be fair, this isn\'t just criticism. I believe the blurred lines are a large reason why the WordPress open source project has been so successful. It’s much easier to advance an open source project from the CEO seat of a multi-billion dollar corporation than it is as the Director of a charitable organization with donations amounting to $10k in 2020.
\n\n\n\nThis benefit is huge and why it’s hard to confidently say the current state of affairs is untenable. This is also why I\'m calling for discussion rather than a call to action.
\n\n\n\nNext, let\'s look at the internal and external implications of this entanglement.
\n\n\n\nWordPress doesn’t exist in a vacuum. It’s built on the backs of other open source projects, like PHP. Additionally, there are many other open source CMSes that exist, like Drupal. Finally, millions of sites are built on WordPress, like whitehouse.gov. This is the ecosystem within which WordPress exists.
\n\n\n\nOpen source projects like PHP and Drupal have foundations and associations that are the faces of the software projects and their communities. When things go wrong, stakeholders need to have somewhere to find guidance and seek help. Through these organizations, each project has the leadership to guide and defend it. In contrast, WordPress’ foundation seems more like a side project than a governing body.
\n\n\n\nWordPress professionals often throw around the 40% market share figure WordPress commands. A number that spiked in the pandemic and has only continued to grow.
\n\n\n\nBut as adoption increases, so do the risks. Having a small hamstrung foundation is an interesting experiment if WordPress was simply a quaint, albeit popular, way to blog. It becomes an issue when the American government calls the next Open Source Summit and 40% of the web is not adequately represented.
\n\n\n\nAs I mentioned at the beginning, the point of this post isn’t to provide answers. It’s to ignite curiosity and conversation. Here are some questions worth asking:
\n\n\n\nQuestions about WordPress and the wider ecosystem
\n\n\n\nQuestions about The WordPress Foundation
\n\n\n\nQuestions about potential conflicts of interest
\n\n\n\nInternally, there are two key issues that surface time and again in varying forms within the WordPress community. They are:
\n\n\n\nAt the face of it, these issues don’t seem related to governance or the lack of clarity and formalization around leadership and systems. But once you dig deeper, you’ll see how they’re linked. For example, the lack of formalization around WordPress’ governance makes enforceability difficult as enforcers don’t have much of a mandate. It also makes it hard to lobby for more resources when you don’t know to whom you should lobby or how.
\n\n\n\nLet’s explore these concerns with more specificity below.
\n\n\n\nBad actors are inevitable in a project as large and diverse as WordPress. Eliminating them would be as impossible as eliminating crime in a country. This isn’t a discussion about that.
\n\n\n\nInstead, what matters is the lack of disincentives for bad actors. Rules are notoriously implemented on an ad hoc basis, and people who have been banned can simply reappear with new email addresses. Furthermore, there are no repercussions for poor or inconsistent enforcement. Nor are there formal processes to report poor enforcement or review how the rules are being applied. If no one is watching the watchers, how do we know if they’re doing a good job?
\n\n\n\nAs WordPress grows, the number of contributors needs to grow too. To understand the mindset of a potential contributor, we can use a simple equation proposed by Aldo Cortesi that’s inspired by Elinor Ostrom’s original equation governing physical commons.
\n\n\n\nBC > BN + C
\n\n\n\nBC is the benefit of contributing, which has to outweigh the cost of contributing (C) plus the benefit of not contributing (BN).
\n\n\n\nBC (benefit of contributing) can also be called Incentives.
\n\n\n\nCurrently, most major contribution efforts are from full-time employees of some of the biggest companies in the ecosystem. Their remuneration is their main incentive for doing the work. This is pretty clear-cut.
\n\n\n\n\n\n\n\nLet’s make it even simpler: You want to introduce FOMO for non-contributors.
The long tail of work is contributed out of personal interest and wanting to give back to the community aka a “helping the commons” mentality.
\n\n\n\nPeople are often quick to equate incentives with money, but money is just one of many incentives, and I believe it’s the least compelling.
\n\n\n\nWhile money is a critical and necessary part of any incentive structure, it’s never just about the money for most people. If it were, people would optimize solely to make it. They wouldn’t be contributing to an open source project, they’d be trading NFTs, mining minerals, financing M&A; or whatever it is that brings in the most money these days.
\n\n\n\nProminent open source maintainer Jeff Geerling explains in a helpful blog post on the burdens of an open source maintainer, “The truth is, money won\'t prevent the next Log4J vulnerability or prevent maintainer burnout (leading to the next colors and faker fiasco). It helps, and it\'s necessary to try to fund developers better—but you can\'t just say “Microsoft should pay developer X $80,000/year and that will prevent another Shellshock.”
\n\n\n\nIn practice, money can only solve money problems, like rent, medical bills, and debt. But beyond that, additional incentives are needed to ensure meaningful contributions are made to maintain a healthy commons.
\n\n\n\nThe goal is to have as low a BN as possible.
\n\n\n\nThe weird “benefit that you want to reduce” phrasing is tricky to understand. Here’s how you can look at it:
\n\n\n\nAll improvements made to the WordPress commons are shared by all. When this happens, people benefit even when they don’t contribute. In order to reduce the benefit of not contributing, you want to create some benefits that are only accessible to people who do contribute.
\n\n\n\nLet’s make it even simpler: You want to introduce FOMO for non-contributors. (Fear of Missing Out)
\n\n\n\nGot it? Great.
\n\n\n\nOne need only turn to Twitter to feel the frustrations of the high costs of contributing. As WordPress developer, Dan Cameron, shared in his tweet, “the major problem, from my experience, is that a valid contribution can be ignored — for years. The only way to “contribute” is to be directed by a release lead, and most of those experiences can be very exhausting/frustrating.”
\n\n\n\nI imagine many others have similar experiences. It has been my experience too. In the past couple of years, I’ve made tiny contributions in the form of FSE testing, reporting a bug, and most recently, proofreading posts for Learn WP.
\n\n\n\nIn all three cases, I needed at least 10-20 mins of help each from Anne McCarthy, Tonya Mork, Israel Barragan, and Courtney Robertson. They helpfully explained the steps I needed to take to contribute. They helped me get set up, gave me context, and set expectations so I was able to contribute correctly and in the WordPress way.
\n\n\n\nI need to make it clear that the 3 tasks I did were very simple things. The amount of time it took for them to help me was far more than the time I took to contribute.
\n\n\n\nNow imagine scaling this up and you can quickly see the bottleneck.
\n\n\n\nGeneral questions
\n\n\n\nQuestions about benefits of contributing (BC)
\n\n\n\nQuestions about benefits of not contributing (BN)
\n\n\n\nQuestions about costs of contributing
\n\n\n\nIf you made it this far, you might have noticed I mentioned ‘WordPress as a commons’ multiple times. Indeed, that’s the title of this post!
\n\n\n\nSo before I wrap up, let’s explore this concept a little bit more and see why it matters.
\n\n\n\nThe term tragedy of the commons was conceived of by Garrett Hardin in 1968.
\n\n\n\nTo understand what it means, let’s refer to an explanation by the International Association for the Study of the Commons:
\n\n\n\nWhen people share a resource they will over-harvest it because it is in their individual interest to take as much from the resource as possible; depletion of the commons could, according to Hardin, only be prevented via private property rights and governmental regulation. The term ‘tragedy’ referred to the argument that people are not able to self-govern common resources.
\n\n\n\nMatt Mullenweg loves talking about WordPress as a commons. In fact, he recently spoke at length about it in the State of the Word 2021. Here’s an excerpt:
\n\n\n\n\n\n\n\nIn the digital world, at least, I think it’s possible to have an abundance of the commons. So the more people that use a program the better. It gets [better] in so many ways — more bugs get reported, more translations happening,… more plugins get developed, more themes get developed. And so the more people that use WordPress, WordPress doesn’t get any worse for any of you. In fact, the more people that use it, the better it gets.
But part of that is some percentage of the people who essentially directly benefit from WordPress, putting something back into the comments, fertilizing the soil, planting some more grass…
Excerpt taken from The WP Minute’s transcription of the talk.
Since learning about the tragedy of the commons in university, I always believed the tragedy was inevitable and every commons was bound to either fail or become privatized. And all one could do was put off the inevitable for as long as possible.
\n\n\n\nImagine my delight when I found out researchers across multiple fields have found many real-world examples of self-sustaining commons that neither ended in tragedy nor needed the installation of private property rights or government regulation.
\n\n\n\nThe most notable of these researchers is Nobel Laureate, Elinor Ostrom.
\n\n\n\nMost famously, she derived 8 principles necessary for successful self-governance. They are:
\n\n\n\nGiven how often Matt talks about it, I’ve always found it curious that he never mentions Ostrom or that this problem has already been demonstrably solved many times or that principles exist to solve it.
\n\n\n\nHowever, I thought to bring it up because so many of her principles map to the issues raised in this article.
\n\n\n\nAs I said at the beginning, I don’t profess to have any answers. The purpose of this post was to further discussion around a variety of topics because I believe they are important ones for the community.
\n\n\n\nAs such, I’ve asked a lot of questions in this post. So it’s only fitting that I end it with even more!
\n\n\n\nHere are a bunch of bird’s eye view questions to further the discussion:
\n\n\n\nI want to thank Dan Knauss for helping edit this monster of a piece and encouraging me to write it in the first place. Blame me for all the bad stuff, and thank him for all the good! Big thanks also to Aurooba Ahmed for providing a final sanity check and round of edits.
\n\n\n\nFinally, I’d like to reiterate that WordPress is a gigantic project and while this post is wide-ranging, it doesn’t begin to cover all the facets and considerations out there. I know I’ve failed to highlight many important facts and perspectives. That’s inevitable.
\n\n\n\nRather than attempt to do it all myself, I heartily encourage you to join the conversation and write a blog post of your own!
\n\n\n\nThanks for reading. I hope I sparked your interest in these topics, and I can’t wait to see where your curiosity takes you.
\n\n\n\n\n\n\n\n![\"Lesley](\"https://cdn.poststatus.com/wp-content/uploads/2021/10/DSC06964_01-square-min-Lesley-Sim-752x752.jpg\")
Lesley Sim has been a government employee, an ad agency suit, and a freediving instructor… and then she found WordPress. She built sites on WordPress as part of her digital marketing agency and moved on to building plugins last year. Now, she focuses on Newsletter Glue, a plugin that connects your email service provider to WordPress and turns the block editor into a newsletter builder so you can build and send newsletters directly from WordPress.
\nMany of the big companies in tech have a practice of issuing annual Calls for Proposals for research into key questions relevant to their industry and the toughest challenges they face. Microsoft, Google, IBM, and Amazon all sponsor research awards and academic programs.
\n\n\n\nWhy not WordPress?
\n\n\n\nMost open-source software (OSS) projects suffer from sustainability issues that could affect their long-term future survival and/or impact many other projects that are built on top of them.
\n\n\n\nAs with any shared resource, OSS has a participation-inequality problem where participants can benefit from others’ contributions even if they do not contribute themselves, but if nobody cooperates the community loses as a whole. This “volunteer’s dilemma” is similar to the well-known concept of the tragedy of the commons.
\n\n\n\n\n\n\n\nFollowing a Community-wide Call for Proposals that generates many well-defined, actionable research ideas, we could pursue the resources needed to make the research studies a reality.
The more critical the project, the more we should all be concerned about its future. Today, WordPress and a number of well-known WordPress plugins are indeed critical projects in a global context where big Tech companies and national governments are taking a deeper interest in their security.
\n\n\n\nThanks to initiatives like Five for the Future, WordPress (core) has a significant number of paid contributors so it is in a better situation than many other projects, but this doesn’t mean we are safe or that we could not advance faster if we were able to attract (and retain!) more contributors in the WordPress ecosystem.
\n\n\n\nThere are many strategies we could borrow from other communities, but each community is different we cannot just copy and paste their solutions. No single solution has had spectacular success on its own anyway; in fact, OSS sustainability is an important ongoing research area because there are no definitive solutions.
\n\n\n\nWe need to first agree on what (sub)challenges we consider the most relevant one/s, what resources are available to address those challenges, and how we want to allocate these resources.
\n\n\n\nLet’s look at some (overlapping) topics I’d like to see discussed/analyzed in the coming year and beyond. The questions below target different dimensions of the WordPress community, and many of them are inspired by some of the research I’ve seen or done in software analytics conferences and journals like OSS, MSR, or EMSE.
\n\n\n\nFollowing a Community-wide Call for Proposals that generates many well-defined, actionable research ideas, we could pursue the resources needed to make the research studies a reality.
\n\n\n\nFor example:
\n\n\n\nDo you have ideas for a WordPress research project? Do you have the capacity to fund or perform research?
\n\n\n\nWe\'d like your considered response to this proposal in Post Status Slack, if you\'re a Post Status member. You can also get in touch with Jordi there and through his contact information below.
\n\n\n\nIf you\'d like to get in touch with the Post Status team with a proposal of your own for the WordPress community, we welcome all thoughtful submissions.
\n\n\n\n\n\n\n\n![\"Jordi](\"https://cdn.poststatus.com/wp-content/uploads/2022/01/89725522ecef5872ff34df4c7ac09d02.jpeg\")
Jordi Cabot is currently an ICREA Research Professor at the Interdisciplinary Internet Institute (IN3), a research center of the Open University of Catalonia (UOC) in Barcelona where he leads the SOM research team for “Systems, Software and Models.”
Jordi can be reached in Post Status Slack or at jordicabot.com and jordi.cabot@icrea.cat.
Front-end performance in WordPress is all about first impressions and using those first impressions to create a positive experience for your website visitors. In this webinar, Mike Crantea and Sabrina Zeidan from XWP unpack how to think about front-end performance and where to focus your efforts to create positive experiences for your site\'s visitors.
\n\n\n\nThis webinar is focused on guiding business owners on how to think about performance in WordPress. You will learn the general principles behind front end performance. Then you\'ll get an introduction to some standard tools for monitoring site performance followed by some tactics for improving your website\'s performance.
\n\n\n\nHost: Jonathan Wold, Post Status Partnerships
\n\n\n\n![\"🤔\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f914.png\")
![\"🔧\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f527.png\")
![\"💁♀️\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f481-200d-2640-fe0f.png\")
Principal Engineer at XWP and Performance Advocate.
\n\n\n\nPassionate for Frontend Architecture and Web Performance, writing about it.
\n\n\n\n\nPerformance Engineer at XWP.
\n\n\n\nAll-things WordPress performance, and talking about it.
\n\n\n\nOne of the many whose lives have been changed by the WordPress Community.
\n\n\n\nContent Team Lead at WordCamp Europe 2022.
\n\n\n\nFollow Sabrina on Twitter.
\n![\"\"](\"https://cdn.poststatus.com/wp-content/uploads/2021/12/1622579176499-752x752.jpg\")
Jonathan Wold is the Strategist for Post Status. He joined the WordPress community in 2004, fell in love with WordPress, and has been all in ever since. Jonathan thinks about WordPress as an Operating System for creating on the Open Web and invests his time and energy into growing the WordPress ecosystem. He leads partnership efforts at Post Status and stirs up trouble wherever he can.
\nEvery week Post Status Live will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash. ![\"⚡\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/26a1.png\")
You can listen to past episodes of Post Status Live, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS. ![\"🎧\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f3a7.png\")
![\"🔗\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f517.png\")
Mentioned in the show:BuddyPress 10.0.0 “La Pino’z” was released today, named for a popular pizza chain in India with more than 350 restaurants.
\n\n\n\nThis major release introduces a Site Membership Requests feature, which can be enabled in the Options screen of the BuddyPress settings menu in the admin. When active, it changes the registration process so that visitors can submit a membership request, which must be manually approved by a site administrator.
\n\n\n\nPending accounts can be managed in the admin on the Users screen. Check out the BuddyPress codex for screenshots of every step in the site membership requests workflow.
\n\n\n\nVersion 10.0.0 brings major visual improvements to the activity logs, designed to make them more engaging. Activity items like changed profile pictures, new friends, new group creation, and other updates will now be displayed with images.
\n\n\n\n“The new update also saves your avatar change timeline,” BuddyPress developer Varun Dubey said in the feature’s dev note. “For example, when a user uploads a new avatar, the previously uploaded one is moved inside a history subdirectory of the user’s avatar directory. This avatar’s history is then available for the new_avatar activities to display the avatar the user had when these were published.”
\n\n\n\nUsers will also notice a new “Recycle” tab inside the change profile photo UI that lets them manage and delete previously uploaded avatars.
\n\n\n\nOther notable additions include updates to the BuddyPress administration UI, with screens that match the layout WordPress uses for its tabbed screens like Site Health or Privacy.
\n\n\n\nVersion 10.0.0 introduces a new BuddyPress Add-Ons tab on the “Add Plugins” admin screen where users can find stable BP Components or BP Blocks that are maintained by the BuddyPress development team. These are features they have decided to keep independent from core but want to make more widely available in the plugin directory. The BP Search Block is the first to be displayed on this screen.
\n\n\n\nThis release updates the BP Theme Compatibility API so that BuddyPress content is compatible with FSE in WordPress 5.9. It also adds companion stylesheets to the BP Nouveau Template Pack for compatibility with the new Twenty Twenty-Two default theme.
\n\n\n\nFor a full rundown of everything new in 10.0.0, including more than 70 changes and performance improvements, check out the release notes.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 21 Jan 2022 03:48:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:67:\"Gutenberg Times: How 5.9 creates a strong foundation for the future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://gutenbergtimes.com/?p=20103\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/how-5-9-creates-a-strong-foundation-for-the-future/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:10960:\"Photo by Rodolfo Quirós from Pexels
\n\n\n\nWith attention on WordPress 5.9 set to launch January 25th, 2022, this post seeks to paint a picture of the future that this strong foundation of this upcoming WordPress release provides. In many ways, what you’ll find in 5.9 is just the beginning of various pieces of functionality and, by the end of the post, you too should see why.
For now, keep in mind two things: it’s impossible to estimate when the following items will be implemented and these are just a few of many exciting things being explored.
Table of Contents
\n\n\n\nWhile 5.9 marks the exciting introduction of block themes, the power of this new approach to themes doesn’t stop there, especially when you think about what will be possible across different block themes. For example, imagine a world where one could seamlessly take patterns from one theme, styling from another, and templates from yet another to create a site. Or imagine being able to switch themes while retaining your favorite palette of colors and typography. This is all being explored! To learn more, check out this wonderful design dive from a Core contributor on the design team.
\n\n\n\nRight now, each block theme comes with one set of styles and settings bundled in a theme.json file. In the future, block themes can be bundled with multiple Style options, allowing you to switch between vastly different looks without changing themes. In the future, after finding one you like, you could then customize your site further using the Styles system in place from 5.9! This could radically change the experience of exploring and using themes, perhaps allowing you to use Styles from one theme in a different one or allowing theme authors to ship new Style variations as updates to their theme. All of this begs the question of how the theme directory can be reimagined to highlight how there are almost multiple themes built into each block theme thanks to these different variations. There’s both a ton to be figured out here and to look forward to.
\n\n\n\nYou can see this concept demonstrated in the following video pulled from the Introducing Twenty Twenty-Two post:
\n\n\n\n\n\n\n\nTo stay on top of this work, check out this PR currently underway.
\n\n\n\nWhile WordPress 5.9 allows you to add some types of templates, there are numerous others that folks are keen to build. For example, what if you wanted a custom template for a specific category of posts or for a custom post type? These are all different types of templates to explore adding to the site editor! To see what types of templates are being explored, check out this GitHub issue on the topic.
\n\n\n\nWith more color options coming to WordPress, the color panel is getting a makeover to ensure it’s even easier to customize for all the various blocks that make use of this functionality.
\n\n\n\nCurrent design
\n\n\n\n![\"Current](\"https://lh4.googleusercontent.com/vX5UFoR1_XnXChT7yYUd2Sdr6djGOlZAwE8jRy_xF9HT06eqg2fmQ688cVde1g6gMgsE0BhU09BrVPsPeymljRMHWzQwelVIZbXFrwIpF4ATI3pt2o85kvr9rUlbY6UVF6eUPtga\")
\n\n\n\nUpcoming design
\n\n\n\n![\"Upcoming](\"https://lh6.googleusercontent.com/kszCKaLN1RbIcOqY-6TNDVIZP4ywmoWmVmRd0W2yV9Ho1F_ogNuZqob9mkg3m57mNu-9CYHARgMlWmktyh512e2HkO8ywRKMccuFtjQazykLFlgWf5LQIxAp6cD_xKyBSvLrpfbn\")
\n\n\n\nAs you can see, with this new experience, it makes better use of the sidebar and it allows you to see the current choices at a glance. To stay up to date with this work, check out this overview GitHub tracking issue.
\n\n\n\nIn the Customizer, you could save and schedule changes you wanted to make to your site’s design. Currently, in the site editor, this isn’t yet possible but is being planned. To stay up to date with this work, check out this issue.
\n\n\n\nBlock Patterns are a powerful way to quickly build beautiful content. While patterns can be bundled with themes and there’s a new modal for exploring patterns, lots of work remains to have patterns appear right when you need them. For a sampling of enhancements to look forward to, check out the following:
\n\n\n\nTo connect some dots, if all of these were implemented today, you could do things like create a new template and be presented with patterns built into the experience that include blocks you’re likely to use like a navigation block, site title, and site logo put together in various options to pick from. Don’t like what you see? You could then use the transform menu to pick something else. All of this should streamline site creation.
\n\n\n\nWhile WordPress 5.9 includes a ton more customization options for blocks, there are even more to come. You can learn more about what’s planned in this overview issue. With each added control to each block comes an infinite number of possible combinations. Here’s just a brief taste of what you’ll be able to do with 5.9 to help give you a sense of what will be possible going forward too:
\n\n\n\n\n\n\n\nWhile more options lead to excitement for some folks, questions of locking down the experience come up for others. WordPress 5.9 introduces a new block level locking mechanism to work alongside template locking that helps set this foundation but know that there’s more to come. Imagine creating a custom pattern for a client and ensuring it’s locked in a way so that the content can be edited and the entire pattern can be moved around but the blocks within it can’t be removed. Or imagine you help set up a site for a client and you want to ensure some key information about their business (like opening hours) both can’t be removed or moved but can be updated as needed. This is the sort of functionality this work allows. It also ties directly into Phase 3 of the roadmap (collaborative editing) so expect much of this work to be explored and aligned as Phase 3 gets underway.
\n\n\n\nFor a practical example of what’s possible today, check out this awesome tweet from Matías Ventura. As for what will be possible tomorrow? Stay tuned and check out this overview issue.
\n\n\n\nIf reading this got you excited about what’s to come and curious to learn more, I recommend joining the FSE Outreach Program where these sorts of early explorations are regularly shared and discussed, often with feedback from the program incorporated into the future of WordPress.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 21 Jan 2022 02:17:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:76:\"WPTavern: Create Todo and Checklists in the WordPress Editor With New 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=128018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/create-todo-and-checklists-in-the-wordpress-editor-with-new-plugin?utm_source=rss&utm_medium=rss&utm_campaign=create-todo-and-checklists-in-the-wordpress-editor-with-new-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:4318:\"Todo lists. Checklists. While there are differences in their purposes, their output is essentially the same. They are lists of items with boxes to tick off, and a plugin like David Towoju’s Todo Block allows users to create them.
\n\n\n\n\n\n\n\nI first downloaded and installed the plugin two weeks ago, but it had a problem. It did not seem to add any blocks at all. This was likely some mistake with porting the plugin over from its development repository. I have been testing it since its update a few days ago and like where it is headed.
\n\n\n\nTechnically, the plugin has two blocks. One exists for the outer list container and the other for the inner list items.
\n\n\n\nIt works similarly to the standard List block. Once users insert the Todo block into the post, they can add tasks. Hitting the Enter key creates a new item.
Users can customize the typography and colors for individual Todo Item blocks. The latter is a welcome option for people who categorize items or tasks by color.
\n\n\n\nHowever, there are no such options on the outer Todo List block. More often than not, users might want to customize everything at once.
\n\n\n\nEach item can also be set to “Read Only” or “Disabled.” Since this plugin does not send data through a form on the front end, the differences between the two are subtle. Site visitors cannot check a read-only field, but they can focus on them via mouse or keyboard. They can do neither for disabled items.
\n\n\n\nIf it seems like I was touting a similar plugin not that long ago, it is because I was. In July 2021, Rich Tabor released the Todo List Block plugin. The primary difference between them is that Tabor’s is an editor-only plugin. He built the block as a tool for his publishing flow.
\n\n\n\nThere is also a checklist block feature request in the Gutenberg repository. However, there has been no indication of work on it since 2019. Matias Ventura shared a concept via video in April of that year. Ella van Durpe followed up with a pull request in October. Since then, only a few people have commented. The concept may be too niche to ever land in WordPress, despite my desire for it.
\n\n\n\nOne of the reasons I want to see such a block in core WordPress is because it would be handy for various patterns. I have already built several for recipe and food bloggers, and I used the Todo Block plugin to test the concept.
\n\n\n\nThere are two features really missing in the plugin. The first is a <label> element wrapping the checkbox and text. Adding this would allow checking the box on the front end by clicking the text or the checkbox itself.
The second is crossing out each item as it is checked. Some systems also gray out tasks as they are finished. A “task complete” indicator is a relatively standard feature for todo list apps.
\n\n\n\nOther than that, Todo Block is a plugin that I could see myself using for some projects. At the very least, I could handle the crossed-out style through my theme’s stylesheet.
\n\n\n\nA question to our readers: I am trying something different with this post. Some of you may have noticed the WordPress.org plugin embed/card at the top. Would you like to see similar treatments for plugins or themes in the future? Does it get in the way of the article or feel too promotional? Alternatively, I considered putting this at the bottom under a “Plugins Mentioned in This Post” section.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 21 Jan 2022 00:49:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:47:\"BuddyPress: BuddyPress 10.0.0 “La Pino’z”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=322980\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://buddypress.org/2022/01/buddypress-10-0-0-la-pinoz/\";s: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:12827:\"“La Pino’z” is our first major release of 2022, and it’s version 10 of BuddyPress! It all started for us in 2009, 2 years before Sanam Kapoor opened his very first pizzeria in his hometown of Chandigarh, India. Known for its delicious and rich traditional Italian pizza, “La Pino’z” soon became one of the most famous foods shared in the Indian community. From that very moment to 350 plus restaurants over India today and soon elsewhere in the world, Sanam and his team have unquestionably come a very long and successful way. La Pino’z is also the only pizza chain in India equipped with giant pizza machines producing the 24” inch monster pizza ![\"😜\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f61c.png\")
![\"Valentine\'s](\"https://buddypress.org/wp-content/uploads/1/2022/01/lapinoz.jpg\")
With love,
the BP Team.
Photo credits knoksense.com
\n\n\n\nYou can get it clicking on the above button, downloading it from the WordPress.org plugin directory or checking it out from our Subversion repository.
\n\n\n\nIf you’re upgrading from a previous version of BuddyPress, it’s always a good idea to back up your WordPress database and files ahead of time.
\n\n\n\nYou can review all of the changes in this 10.0.0 release in the release notes. Please note that BuddyPress 10.0.0 requires WordPress 5.4.
\n\n\n\nThat being said, let’s talk about the new delicious features we believe you are going to enjoy a lot!
\n\n\n\n\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2022/01/prevent-spammer-registration.png\")
The pending accounts administration screenTake control of your site’s membership! With site membership requests, administrators can significantly reduce the number of spam users trolling their sites.
\n\n\n\nWhen requests are enabled, visitors may submit a membership request, which must be manually approved by a site administrator. Read more about this feature.
\n\n\n\n\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2022/01/logging-activity.png\")
These simple activities about specific user interactions or events (for example, you and me are now friends) are more visually attractive to improve user engagement in your community.
\n\n\n\nThe most impressive new activity is that which is generated when a user updates her profile photo: it will include the profile photo that spurred the creation of the activity item, even if it has been changed since. Learn more about it by reading this developer note.
\n\n\n\n\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2022/01/bp-settings-screen.png\")
As shown in the image above, the BuddyPress administration screens are now using the layout WordPress uses for its tabbed administration screens such as the Site-Health or Privacy screens.
\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2022/01/edit-pages-screen.png\")
Knowing the WordPress pages BuddyPress uses for its front-end directory screens is simpler with special status information displayed beside all BuddyPress pages.
\n\n\n\n\n\n\n\nBuddyPress Add-ons are experimental plugins, beta features packaged as plugins, that will be made available into the official WordPress.org plugins directory so that it’s easier for you to test them and give the development team your feedback.
\n\n\n\nThe more we are to get involved into the future of our open source project, the brighter it will be and the faster we’ll be able to include great new features!
\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2022/01/hello-buddypress-addons.png\")
BuddyPress Add-ons are also stable complementary BP Components or BP Blocks, which we have decided to keep independent from the core of BuddyPress, leaving you the choice whether to use the feature or not. The BP Search Block is the first example of this second category of add-ons. Give it a try; you can easily install it from your BuddyPress Add-ons administration screen.
\n\n\n\n\n\n\n\n![\"\"](\"https://buddypress.org/wp-content/uploads/1/2022/01/welcome2022.png\")
WordPress 5.9 will introduce Full Site Editing featuring the new default theme Twenty Twenty-Two.
\n\n\n\nWe’ve adjusted our BP Theme Compatibility API so that you can enjoy this amazing feature, making sure that BuddyPress-generated content integrates optimally within themes supporting it.
\n\n\n\n![\"➕\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/2795.png\")
The BP Nouveau Template Pack also includes a companion stylesheet to maximize BP pages layout within Twenty Twenty-Two.
10.0.0 comes with more than 70 changes including performance improvements to the BP Notifications, BP Activity and BP Signups APIs; Date Query support for the Members, Groups and Sites loops; new BP Avatar UI Recycle tab, improved inline documentation/translators comments and code formatting. Have a look to the release notes to discover them all!
\n\n\n\n\n\n\n\nAchilles4400, Adil Öztaşer (oztaser), Boone B Gorges (boonebgorges), Brajesh Singh (sbrajesh), Christian Wach (needle), comminski, Dan Caragea (dancaragea), David Cavins (dcavins), Dhaval Kasavala (dhavalkasvala), Dion Hulse (dd32), durdenx, ellucinda, Evan Stein (vanpop), Gary Jones (garyj), Hasanuzzaman (hasanuzzamanshamim), jakubrak, Jean-David Daviet (Jean-David), Jennifer Burnett (jenfraggle) John James Jacoby (johnjamesjacoby), josett225, Ketan Chawda (ketan_chawda), konnektiv, Laurens Offereins (Offereins), magland, mandro, marioshtika, Mark Robson (markscottrobson), Mathieu Viet (imath), Nifty (niftythree), nunks, oddev56, Paul Gibbs (DJPaul), r-a-y, Renato Alves (espellcaste), rigsbyx, thomaslhotta, Varun Dubey (vapvarun), venutius, yesbutmaybeno.
\n\n\n\n\n\n\n\nReceiving your feedback and suggestions for future versions of BuddyPress genuinely motivates and encourages our contributors. Please share it ![\"🙏\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f64f.png\")
Nobody likes spam. Well, except for the spammers.
\n\n\n\nBut spam plagues every single website, no matter its size. It shows up in comments, contact form submissions, and user registrations. And not only is it annoying and time-consuming to deal with, it can be damaging for your reputation and your website.
\n\n\n\nSo how do you prevent it? Let’s take a closer look at spam, learn why a plugin is your best solution, and compare the best anti-spam plugins for WordPress.
\n\n\n\n\n\n\n\nIn its simplest form, spam is unwanted commercial communication. Typically, for you as a website owner, spam looks like irrelevant, strange comments on posts, pages, products, or form submissions. Not only is it annoying, but it also makes you look unprofessional, negatively affects your search engine rankings, and can even direct site visitors and customers to malware and phishing sites. You want to prevent it as much as possible to protect both your reputation and your site visitors.
\n\n\n\nYou can, of course, manually moderate each comment and delete any and all spam. However, spammers can leave dozens — and sometimes hundreds — of spam comments each day on a single website. That can be very time-consuming and also leaves a lot of room for error. You have better things to spend your time on!
\n\n\n\nThat’s why WordPress anti-spam plugins are so helpful and why we’ve covered the best WordPress anti-spam solutions in the industry. They automatically filter through each and every one of your comments (and sometimes form submissions) and delete spam for you. You don’t waste any time, but you know that this critical task is taken care of.
\n\n\n\nHow do they do this? Well, spammers aren’t typically very clever. They leave valuable clues in their comments, such as misspellings, strange links, and sales pitches. Anti-spam plugins have a database of this information and use it to identify and get rid of spam without you having to lift a finger.
\n\n\n\nThere are a variety of anti-spam plugins out there. How do you know which one is the right fit for your website?
\n\n\n\nHere are some important features of anti-spam plugins:
\n\n\n\nSpam doesn’t just happen in the comment section of your site. Spambots can take advantage of contact forms and use them to send out spam emails to your email list or customers. Plus, tons of spam contact form submissions in your inbox every day is frustrating.
\n\n\n\nSo, make sure that your anti-spam plugin protects both your comment forms and contact forms.
\n\n\n\nIf you’re adding an anti-spam plugin to an existing WordPress site, it’s especially important that it works well with the plugins you already have installed. This might include contact form plugins (like Jetpack, Contact Form 7, or WPForms), forum plugins like bbPress, or eCommerce plugins like WooCommerce.
\n\n\n\nIn order to correctly identify spam, plugins need to have lots of information. They need to have observed spam on lots and lots of sites for a long time so they can identify common characteristics. After all, you want real comments to stick around, but the bad ones to disappear.
\n\n\n\nYou’re probably familiar with CAPTCHAs — tools that make you check a box or select all the photos with stop signs to prove you’re not a robot. While they’re relatively easy to use, they’re just one extra step that someone has to take in order to reach out to you or engage with your content. And every single step makes it more likely that they’ll get frustrated or distracted and give up.
\n\n\n\nSo, ideally, you’ll want to go with a solution that doesn’t require CAPTCHAs to make the user experience as seamless as possible.
\n\n\n\nWhile a high-quality anti-spam plugin is extremely accurate, it’s not perfect. There may be times that it incorrectly identifies a valid comment as spam or misses a spam comment. So, if comments are extra valuable to your website, you may want to be able to override the decisions your anti-spam tool makes.
\n\n\n\nAt the same time, though, you shouldn’t have to put any effort into spam prevention. Once you set up the plugin, you should be able to sit back, relax, and know that spam is taken care of.
\n\n\n\nInstalling and setting up the plugin should be super simple, even if you don’t have much tech experience.
\n\n\n\nYou don’t want a plugin that adds a lot of extra weight to your server, slowing things down. That’ll only make things more difficult for site visitors and hurt your SEO rankings. Make sure that the plugin you choose keeps things speedy. Typically, an anti-spam plugin does this by running all operations on its own server, rather than on your site.
\n\n\n\nAkismet is the anti-spam plugin created specifically for WordPress by the team behind WordPress.com. It’s blocked billions of spam comments to date and integrates seamlessly with top WordPress contact form plugins. It’s trusted and reliable, can be set up in minutes, and offers reasonably-priced plans for personal sites and businesses.
\n\n\n\nFeatures:
\n\n\n\nPros:
\n\n\n\nCons:
\n\n\n\nEase of use:
\n\n\n\nAkismet is super easy to set up, requiring no server access or development experience. All you have to do is go to Plugins → Add New in your WordPress dashboard. Search for Akismet, then click Install Now → Activate. From there, simply choose the plan you’d like, set up an account, copy and paste your API key in Akismet settings, and you’re up and running!
\n\n\n\nPricing:
\n\n\n\nNote that an API call is an individual request to Akismet servers. So each comment and form submission is one API call.
\n\n\n\nAntispam Bee is a straightforward, free anti-spam plugin available directly from the WordPress plugin library. It automatically blocks spam comments, pingbacks, and trackbacks.
\n\n\n\nFeatures:
\n\n\n\nPros:
\n\n\n\nCons:
\n\n\n\nEase of use:
\n\n\n\nAntispam Bee is very easy to set up. Just install and activate the plugin from the WordPress dashboard — that’s it! If you want to customize settings, you can visit Settings → Antispam Bee.
\n\n\n\nPricing:
\n\n\n\nAntispam Bee is free for all users.
\n\n\n\nTitan Antispam and Security is exactly what its name implies — a security and anti-spam plugin for WordPress. The anti-spam feature first checks for known spam comments. Then, it checks any remaining comments a second time using a smart system that’s constantly learning how to identify unwanted messages.
\n\n\n\nFeatures:
\n\n\n\nPros:
\n\n\n\nCons:
\n\n\n\nEase of use:
\n\n\n\nTitan Antispam is very easy to set up — just install and activate the plugin. Then, choose the settings you’d like to enable.
\n\n\n\nPricing:
\n\n\n\nWordPress Zero Spam is a free anti-spam plugin available in the WordPress plugin repository. It uses the power of AI combined with databases of known spam IPs to protect sites against malicious comments, registrations, and form submissions.
\n\n\n\nFeatures:
\n\n\n\nPros:
\n\n\n\nCons:
\n\n\n\nEase of use:
\n\n\n\nSetup of WordPress Zero Spam is simple and quick. Simply install and activate the plugin, then visit its settings page to configure functionality however you’d like.
\n\n\n\nPricing:
\n\n\n\nWordPress Zero Spam is free for all users and doesn’t have any paid features.
\n\n\n\nCleanTalk Spam Protection is a premium tool that blocks spam from a variety of sources, including comments and contact forms. It’s a cloud-based service that uses an advanced database of information to validate comments.
\n\n\n\nFeatures:
\n\n\n\nPros:
\n\n\n\nCons:
\n\n\n\nEase of use:
\n\n\n\nCleanTalk is also straightforward and simple. Install and activate the plugin, set up an account and get an access key, then test the setup using a dummy comment.
\n\n\n\nPricing:
\n\n\n\nCleanTalk offers a free trial, then is $8 per year.
\n\n\n\nThe reCaptcha plugin adds a CAPTCHA to login, registration, password recovery, comment, and contact forms. This requires site visitors to prove they’re not a robot before submitting the form.
\n\n\n\nFeatures:
\n\n\n\nPros:
\n\n\n\nCons:
\n\n\n\nEase of use:
\n\n\n\nreCaptcha is a bit harder to set up as it requires finding and creating API keys with Google. If you’re not familiar with this process, it can be confusing.
\n\n\n\nPricing:
\n\n\n\n| Akismet | Antispam Bee | Titan Antispam and Security | WordPress Zero Spam | CleanTalk Spam Protection | reCaptcha by BestWebSoft | |
| Prevents comment spam | Yes | Yes | Yes | Yes | Yes | Yes |
| Prevents contact form spam | Yes | No | No | Yes | Yes | Yes |
| Prevents user registration spam | No | No | Yes | Yes | Yes | Yes |
| Integrations with contact form plugins | Jetpack, Gravity Forms, Contact Form 7, and more | None | None | Contact Form 7, WPForms, and more | WPForms, Jetpack, Contact Form 7, and more | Contact Form 7, Gravity Forms, and more |
| Requires CAPTCHA | No | No | No | No | No | Yes |
| Price | Free to $208/mo (for enterprise users) | Free | Free to $319/yr | Free | Free trial, then $8/yr | Free to $211 one time |
While there are several different high-quality options to choose from, it’s important that you consider the functionality and pricing that best fits your unique scenario.
\n\n\n\nFor most WordPress sites, Akismet is the best WordPress anti-spam solution. It was built by the same people behind WordPress.com, so it has the most extensive spam database and integrates seamlessly with major form plugins. And since it’s cloud-based, it won’t slow down your website like many of the other tools on this list. Plus, it’s completely free for personal sites and offers very affordable paid tiers for businesses. That’s exactly why it already has more than five million installations!
\n\n\n\nHowever, if you need a completely free tool, you might want to consider Antispam Bee. And if you’re looking specifically for a CAPTCHA, the reCaptcha by BestWebSoft plugin is a great solution.
\n\n\n\nSpam bots are automated tools used to leave spam comments on posts, products, and more. They’re programmed to fill out any required fields and can even be taught to look like legitimate users. Then, they search the web for sites that meet certain requirements and leave as many spam comments as they can.
\n\n\n\nHere are some typical qualities of spam comments:
\n\n\n\nThere are a variety of WordPress settings that help prevent spam. If you take all of the steps below, you’ll maximize spam prevention. However, not all of these settings will be right for every website.
\n\n\n\nStart by going to Settings → Discussion in your WordPress dashboard. Then:
\n\n\n\nThen, if you start to see common phrases, URLS, emails, etc. in your spam comments, add them to the box under “Comment moderation”. This will block any comments that include those characteristics.
\n\n\n\nYes, absolutely. By default, WordPress allows you to go through each comment and decide to mark it as spam or approve it. However, it can take a lot of time to go through comments on a daily or weekly basis — time better spent invested in your blog or business!
\n\n\n\nThis completely depends on your site and goals. In many cases, comments can be an excellent way to answer questions, encourage discussion, and engage with your site visitors. They can even be used to create a community around your brand.
\n\n\n\nHowever, this may not be right for every website. If you do choose to disable comments, you can do so in your WordPress Discussion settings.
\n\n\n\nHere are some reasons people leave spam comments:
\n\n\n\nThere may be times that you want to turn off comments for one particular post rather than all of the posts or pages on your site. All you have to do is go to Posts → All Posts in your WordPress dashboard and click on the one you want to edit. Then, click the gear icon at the top right of the page and expand the Discussion section. Uncheck the box next to Allow Comments, then save your post.
\n\n\n\nYour comment moderation queue lists all of the comments that need your approval before they go live on your site. This is your chance to either mark them as spam, publish them on your site, or delete them entirely.
\n\n\n\nTo find the WordPress comment moderation section, click on Comments in your WordPress dashboard. All unmoderated comments will appear with a yellow background and red bar on the left. Underneath each comment, you can choose to approve, reply, edit, trash, or mark the comment as spam.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 20 Jan 2022 11:05:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Simon Keating\";s: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:112:\"WPTavern: Gutenberg 12.4 Includes Accessibility Improvements, Categories Reminder, and a Tag Cloud Outline Style\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=128613\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:265:\"https://wptavern.com/gutenberg-12-4-includes-accessibility-improvements-categories-reminder-and-a-tag-cloud-outline-style?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-12-4-includes-accessibility-improvements-categories-reminder-and-a-tag-cloud-outline-style\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7042:\"Gutenberg 12.4 landed in the WordPress plugin directory earlier today. With the push to get WordPress 5.9 out the door next week, it can be easy to forget all the development behind the scenes, waiting to make its appearance in future versions of WordPress.
\n\n\n\nThe latest release focuses more on polishing existing features and introducing a few nice-to-haves. Accessibility improvements are always a welcome sight. The update adds an always-available close button in the block inserter for screen readers. And, when closing the list view, the focus state moves to its button.
\n\n\n\nSome theme-related blocks have also been relocated within the inserter. Post Template, Pagination, Next Page, Previous Page, and Page Numbers were previously housed under the Design category. Now, they are appropriately under Theme.
\n\n\n\nGutenberg 12.4 seems to introduce a new bug inside of the site editor. When opening the block inserter, its scrollbar does not appear. This creates a long list of blocks down the side of the page. The canvas area gets set to a fixed height with its own scrollbar.
\n\n\n\nThis issue does not prevent inserting blocks. Nor does it make the site editor unusable. It is more of an annoyance than anything.
\n\n\n\nThis creates a big usability issue. If you try to insert a block after scrolling beyond the height of the content canvas, you cannot see where it gets added until scrolling back up the page.
\n\n\n\nThere are also other scrollbar-related issues. The Site Logo and Image blocks have them in the site editor, and the problem is the same for patterns in the inserter.
\n\n\n\nThanks to Anne McCarthy for being a second set of eyes, confirming this issue, and reporting it.
\n\n\n\nCategories now have their own section in the pre-publish panel for posts. If the user has not selected one, a new tab will appear that reads, “Suggestion: Assign a category.” The user can then open it and check any they want to add to the post.
\n\n\n\nI am a fan of this addition. Even as someone who writes daily, I must routinely remind myself to select a category for my posts. Meta information like this is something I always leave to the end of the writing process, and it is nice to have a reminder. I would also welcome a featured image check.
\n\n\n\nThis is one of my favorite enhancements in the Gutenberg 12.4 release. Users can now transform Post Content to the Post Excerpt block and vice versa.
\n\n\n\nOne of my complaints with Automattic’s recent Livro theme was that it shows the full post content instead of excerpts on its blog and archive pages. I had to remove the Post Content block and insert Post Excerpt to change it.
\n\n\n\nThis is relatively easy for someone as familiar with the site editor as me. However, some users could unintentionally put the replacement block in the wrong place and mess up their entire layout. With the ability to transform the blocks, they can do it with just a couple of mouse clicks.
\n\n\n\nThe latest release adds a new Outline style for the Tag Cloud block. I have said it multiple times, but it might be worth repeating. I dislike Gutenberg adding in too many new block styles. It feels like theme territory. The core system should focus on the foundational features, and themers should extend it with custom options.
\n\n\n\nIt is not that I dislike the outline design for tags. It was the first custom style I added for the Tag Cloud block when designing my own theme. However, every new block style adds some potential burden to theme authors.
\n\n\n\nOne of those issues is that themes need to support it. For example, the padding used for the Tag Cloud links is too large for some theme designs. It is a hardcoded value, so designers must explicitly overwrite it to tone it down. Alternatively, they must deregister the block style if they do not want to make it available.
\n\n\n\nWe need to leave some fun things for third-party developers to implement. Otherwise, themes become less and less relevant.
\n\n\n\nAfter happily reporting font-family support for the Paragraph block in Gutenberg 12.3, it is disheartening to lose it in a mere two-week span. Developers reverted the recent change.
\n\n\n\nAndy Peatling cited a few reasons behind the decision in another ticket:
\n\n\n\nThe web fonts API was slated to land in WordPress 5.9, but it was punted to a future version in November 2021. Work on the project is now ongoing within the Gutenberg repository. Until it is complete, font-family options for any new blocks will likely stall until the new API is in place.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 20 Jan 2022 02:20: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: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:74:\"WPTavern: Why Aren’t More WordPress Theme Authors Creating Block Themes?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128509\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:187:\"https://wptavern.com/what-arent-more-wordpress-theme-authors-creating-block-themes?utm_source=rss&utm_medium=rss&utm_campaign=what-arent-more-wordpress-theme-authors-creating-block-themes\";s: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:7966:\"Block themes are trickling into the official WordPress Themes Directory at a slow rate ahead of full-site editing’s debut in WordPress 5.9. There are now 39 themes that support site editing features, up from 28 in December 2021, when Matt Mullenweg commented on it during the State of the Word address.
\n\n\n\n“That needs to be 5,000,” Mullenweg said. Later during the presentation he said he hopes that WordPress will “have 300 or ideally 3,000 of these block themes” before entering the Collaboration phase of the Gutenberg project.
\n\n\n\nWhy the strong push towards kickstarting the block theme market? The upcoming 5.9 release is set to deliver a solid set of groundbreaking design tools in core that will change WordPress website building in a major way. These include editing page layouts with a drag-and-drop interface and a new Global Styles interface for changing typography, colors, sizes, layouts, padding, and other aspects of design.
\n\n\n\nUsers cannot take advantage of all these new features without a block theme. That’s why WordPress 5.9 is introducing a new default theme, Twenty Twenty-Two, that will make it easy for anyone to get started using a block theme. But with just 39 block themes available right now, early adopters haven’t found a lot of variety.
\n\n\n\nFor whatever reason, more than 5 million WordPress users have still not transitioned to the block editor and are using the Classic Editor plugin. This experience is a shadow of what WordPress has become since the block editor made its debut in 5.0 more than three years ago. Even among users who have embraced the block editor, FSE early adopters are few and far between.
\n\n\n\nWhy aren’t theme authors creating block themes to have their products become some of the first on the market? WordPress Themes Team Representative Ganga Kafle jumped into this topic yesterday, asking why theme authors continue to make classic themes instead of getting on the block theme train.
\n\n\n\n\n\n\n\nResponses showed that theme developers have a variety of different motivations for holding out on building block themes.
\n\n\n\n“I asked some local agencies here in Cape Town, and some of them indicated workflow – in that they were extremely efficient at creating sites with ‘their’ theme, and making a new block theme would eat into profits,” Automattic Theme Development Team Lead Jeffrey Pearce said. “They are waiting to see block themes ‘mature.\'”
\n\n\n\nOnce 5.9 is released and FSE themes are officially supported, agencies will likely become more motivated to update their workflows to develop block themes more efficiently. During this in-between time, it’s easier to maintain the status quo, but now is the time to get prepared to hit the ground running. Once users know there is more to WordPress, they won’t want to be limited by a classic theme.
\n\n\n\nFor some theme developers, it’s a matter of not having the skills yet.
\n\n\n\n“There is a learning curve but I expect more and more people will start building and submitting block themes,” WordPress consultant Krasen Slavov said. “I am personally eager to experiment and learn, but since it is a totally new way of building themes and we all need first to pay the bills, this should be in my spare time.”
\n\n\n\nWordPress developer Sallie Goetsch, who said she builds themes for clients and not for the WordPress directory, is also eager to make the jump into FSE but has the same learning needs.
\n\n\n\n“While I definitely plan to switch to FSE, there’s a lot for me to learn and experiment with before I’m confident enough to use it in production,” Goetsch said.
\n\n\n\nOther theme developers cited difficulties keeping up with the ever-changing landscape of FSE theme development.
\n\n\n\n“We can’t keep up with the changes,” CSS Igniter co-founder Gerasimos Tsiamalos said. “It’s miles away from offering something other than dead simple themes. [There are] too many inconsistencies to streamline.”
\n\n\n\nDue to the nature of their day-to-day work load, some theme developers do not perceive early adoption of FSE themes as a practical move at this time.
\n\n\n\n“We’re very happy using blocks for posts, but block enabled themes don’t give us the flexibility we need to build pages at the speed required,” Designs43 agency responded. “And there are too many changes to keep up with also. We tend to use a fairly basic theme and put customizations into the child.”
\n\n\n\n“I guess the missing flexibility is a killer feature for theme authors,” WordPress theme developer Jessica Lyschik said. “It‘s very easy to bump into things that just don‘t work at all or yet.”
\n\n\n\nThe demand for block themes is not easy to measure. A conservative estimate of active installs of FSE themes hosted on WordPress.org is ~3,000 sites, based on the stats for the small number available. Once the world is introduced to WordPress 5.9 next week, that number is likely to shoot up overnight.
\n\n\n\n“We have a few free FSE themes and working on a premium one,” WordPress Theme shop owner Ana Segota said. “I love themes are more design now and they are easier to use but it’s still a long way. We need to find a way to educate users about the new way of building websites and also it’s hard to follow all the changes.”
\n\n\n\nAlthough block theme development is still in its infancy, there are a few educational resources for authors who are ready to take the plunge.
\n\n\n\nMarcus Kazmierczak published a brief introduction to building block themes, which links to helpful resources from the Block Editor Handbook. Most notably, these include an overview of block themes, how to create a block theme, and a guide to Global Settings and Styles (theme.json). Carolina Nymark has also published a quick guide to creating block themes on fullsiteediting.com. If you’re looking for a starter for building block themes, Justin Tadlock has a few recommendations in one of his recent Ask The Bartender posts.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 19 Jan 2022 21:07: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: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:88:\"Post Status: Post Status Excerpt (No. 42) — What’s Coming Up in 2022 For Post Status\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://poststatus.com/?p=92595&preview=true&preview_id=92595\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/42/\";s: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:31171:\"In this episode of Post Status Excerpt, David sits down with Michelle Frechette to talk about what Post Status is planning for its community and the WordPress crowd as a whole in the first half of 2022. They cover three new events: the Weekly WordPress Job Chat on Twitter Spaces, WP Career Summit, and the first-ever Post Status Twitter Conference. (The conference theme is “Give. Grow. Together.”)
\n\n\n\nWhy This Is Important: Post Status is listening to members and watching what discussions are happening in the WordPress community. Michelle points out why each of these events is important to certain sections of the community — each event will touch the lives of many WordPress professionals in some way.
\n\n\n\n\n\n\n\nEvery week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash.
You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS.
Mentioned in the show: Sponsor: BluehostEverything your website needs — from start-up to success story — is at Bluehost. Whether you\'re looking to create a website, blog, or online store, Bluehost will get you started with an all-in-one website platform tailored to your specific needs. Get a free domain name in your first year, free 24/7 lifetime support, and total design freedom with WordPress at Bluehost.
\n\n\n\nEpisode 43
\n\n\n\nDavid Bisset: [00:00:00] Yeah, I\'m surprised people haven\'t hunted me down yet. Thanks to, um, whenever a lot of the podcasts that I\'m doing now, it\'s like, forget to turn off slack and they get that one slack notification. I go, oh crap. All six people that listen to me, whatever how many people it is. They\'ll they\'ll just go did I just get a slack notification while I was out running and listening to this podcast?
\n\n\n\nMichelle Frechette: Exactly. It\'s like, I, I always check and see if I just got the notification, but no, it was in the, it was in the podcast, somebody else\'s.
\n\n\n\nDavid Bisset: So the reason why Michelle, you and I are talking here today and has nothing to do with blackmail. It has more to do though with what we want to share with our Post Status listeners.
\n\n\n\nYou know, everybody\'s doing these posts or visions of what\'s coming in 2022. And with Post Status, we\'ve got a good pulse. On the community, what they\'re hoping to see what they are doing and what they probably will be looking for in 2022. I think you and I are in a good position. To talk about some of these things that post that is, is particularly planning to help out the [00:01:00] WordPress community in particular, the WordPress professionals.
\n\n\n\nSo I thought that was a good way to kind of get the year started so people can mark these on their calendar. Although if you go to poststatus.com/events, it\'s there to. But let\'s, let\'s say, where do you want to start in terms of what we\'re planning for Post Status in 22? Yeah.
\n\n\n\nMichelle Frechette: So what are the things? So when I joined Post Status, uh, last, was it fall, I guess October-ish, uh, you know, Corey and I had talked about some different things in ways for me to be involved.
\n\n\n\nAnd part of that was writing about, um, the job situation, whether it\'s about helping people with resumes or, you know, a lot of the, you can see a lot of the posts that I\'ve put together. Um, the Post Status.com site. About hiring and also about getting hired. We also have a great, um, you know, podcasts. We\'ve got a whole season out there from get hired.
\n\n\n\nI with Courtney and Corey about, um, getting hired in, in WordPress and, you know, Courtney does a lot of our training and things like that. And some of the ideas that I had coming in were not just writing about [00:02:00] underrepresented, underrepresented topics and job topics, but like, Hey, let\'s take this kind of thing to the next level.
\n\n\n\nLet\'s actually do some event. That we can get the, they, uh, not only the Post Status community involved with, with the whole WordPress community as well. And some of those things are, the WP career summit that we\'ve been talking about, which I\'m building the website. I promise it\'s getting done this week.
\n\n\n\nUm,
\n\n\n\nDavid Bisset: it\'s a summit, Michelle. I mean, these things take time.
\n\n\n\nMichelle Frechette: I know, but like, I should have a landing page at least. Right. So that\'s what I\'m working on, um, is WP career summit.com by the time this airs, it should be out there. So go to WP career summit.com and you can learn about what we\'re planning to do.
\n\n\n\nIt is the first ever summit or conference about working in WordPress specifically. And the goal is two tracks. We\'ll have two tracks, it\'ll run, uh, through the course of the day. One for employers and how to do better, hiring how to do better at evaluate, [00:03:00] evaluating applicants, how to do better recruiting, how to recruit for, you know, inclusion and . Diversity, how to do things without tokenization.
\n\n\n\nFor example, how to evaluate, um, international. Applicants and those kinds of things. So we\'re working on getting together some really good speakers that will speak to employers, but the other track is for job seekers. So if you are looking for a job in WordPress or tech, what are some things that will be helpful to you, understanding how to build a resume for technology, understanding how to put together your GitHub repo, to make sure that people can see the work that you\'re doing.
\n\n\n\nHow do you build a portfolio? what social media should you be involved in? How do you make sure that you have a good LinkedIn profile?
\n\n\n\nDavid Bisset: Not looking for a job and I feel like I got to go off and do that now.
\n\n\n\nMichelle Frechette: Talk to me later, I\'ll help you, but having a career summit like that, where not only do we have those two tracks, but we will have 12 sponsors, uh, [00:04:00] working with us that day, who will have tables.
\n\n\n\nUm, similar, if you\'ve been to WordPress, we\'re going to actually use the word Fest setup. We\'ve hired out, uh, Dan maybe, and his crew to create that same environment for us to use for the WP career summit. So you\'ll have the tracks, you\'ll be able to watch the videos as they\'re, as they are, do live Q and A\'s.
\n\n\n\nBut then you\'ll also be able to go to this open space and meet up with the different employers who are sponsoring to learn more about their companies and maybe even, you know, give them your resume and set up a time to do an interview. We\'ll also have an online career fair at the same time. So any company that wants to sponsor at a smaller level will be able to have, um, their career page, their recruiting page, specifically linked on our job fair sites so that they have a better opportunity to recruit anybody who\'s in attendance at the WP career summit.
\n\n\n\nThe goal behind the career summit is to really bring together employers and potential employees and to [00:05:00] educate the whole WordPress space and best practices for hiring and best practices for getting hired and really start those conversations. There\'s not a lot of conversations. There\'s a ton of people posting jobs.
\n\n\n\nThere\'s a ton of people saying I need a job. It\'s the idea of bringing all those things together and helping the people who are hiring of the people who are looking to get together in the same space, um, and hopefully fill each other\'s needs by getting some great employees into those, into those offices.
\n\n\n\nDavid Bisset: I think one of the advantages of this will be, and maybe this is just a tip from somebody who\'s looked for jobs before.
\n\n\n\nIf you\'re aware of a summit, usually it was in the context of a physical conference, but regardless if it\'s physical or, or remote or virtual. If, you know, in advance, who\'s going to be there. Um, it\'s also, if, if you\'re serious baby, maybe it\'s, um, maybe it\'s maybe you are, have a particular company in mind, or maybe you heard this company\'s really, really good to work for, or they have exciting projects or they [00:06:00] get good PR or whatever, whatever floats your boat in terms of stuff.
\n\n\n\nWe have there\'s this opportunity, especially through Post Status slack to reach out to them prior to. To the summit and say, listen, I would love to talk to you at this summit about this. I just want to make sure that, you know, do an initial contact, nothing fancy in my opinion. But if you really think that you have a good shot at getting, if you want to be noticed, like.
\n\n\n\nUm, it is one of those tips where in this situation, where if, if someone remembers your resume and they\'re comparing that with other people for position, somebody says, well, what w you know, which one of these was most eager? If that question ever came up, you would, it would be at least an advantage to say, this person reached out to me prior, even before coming to the summit.
\n\n\n\nThey wanted to speak to us. And they were very interested who knows that could be the edge and there\'s nothing, there\'s no rule that says you can\'t talk to these people. Until you get to the summit. I think the summits, the best [00:07:00] place to have properly a deep conversation, but just like these days, it\'s whatever it takes sometimes to get noticed.
\n\n\n\nSo I think, I think your summit is going to be set up very, very well for that.
\n\n\n\nMichelle Frechette: Cool. I mean, do you think about when, when you\'re mountain climbing, they talk about somebody like you\'re climbing Everest, for example, they don\'t talk about. Being at the summit until you\'re actually at the top. Right? So it\'s a process you\'re climbing, you\'re getting to that point.
\n\n\n\nAnd so there\'s plenty of opportunity to do that both on your way up and after the summit as well. So, um, the summit should be that focal point where everything kind of comes together, but there\'s lots that you can do in advance. And there\'s lots that you can do as follow up afterwards, for sure.
\n\n\n\nDavid Bisset: You can\'t really relate to the closest thing.
\n\n\n\nI can relate to that as I got on top one time of a big pile of leaves in my yard and I was out of breath. So I, if it\'s the same thing as that, I can definitely.
\n\n\n\nMichelle Frechette: Well, don\'t you work in your basement. I mean, you got to climb the stairs, right?
\n\n\n\nDavid Bisset: Well, yeah. Yes. I\'m not up to that. I\'m not, I don\'t have one of those elevator sit in a [00:08:00] chair and it takes me up things yet.
\n\n\n\nAlthough my wife that is that is, could potential 20th anniversary gift. I\'ll just slip that to my wife. I\'m in the DMS. I
\n\n\n\nMichelle Frechette: dunno. I just saw Gremlin\'s again, recently rewatched around the holidays. And that thing was pretty scary, how I shot that we\'re going to right out the windows. So it just,
\n\n\n\nDavid Bisset: if only it could go that fast, that would be awesome.
\n\n\n\nBut yeah, there are a lot of people I get constant emails or pings on slack or something that says, Hey, we\'re going to put this out there on Twitter. We know you\'re going to retweet it. Or do you happen to know a recommend someone for this? It was a lot of background chatter going around and I\'m, I\'m getting these requests, not just.
\n\n\n\nOther employee, I\'m getting these requests from like, um, head people in head WordPress agencies that ping me just because we know each other. So there is, there, there is a lot of improvement and efficiency still, I think. And I think the summits kind of help with that. And if, even if you\'re not maybe looking forward to.
\n\n\n\nMichelle Frechette: Yeah, absolutely. And it\'s [00:09:00] free to attend. It\'s free to attend the summit. We\'re not charging anything to be there. Um, the worst thing I think that you can do is when somebody is looking for a job is to say, Hey, pay to come learn about how to do better at getting jobs. So the sponsorship is going to cover all of the costs of it.
\n\n\n\nAnd so we want everybody who wants to be there. You don\'t have to say you\'re looking for a job or not, but you\'re welcome to kind of come in and observe either track and bounce back and forth. If you want to and learn best practices on either side of things. Uh it\'s uh, it\'s just there for edification for anybody who wants to learn.
\n\n\n\nDavid Bisset: Gotcha.
\n\n\n\nAlright. Job summit. Yeah.
\n\n\n\nMichelle Frechette: So the other thing along that same lines though, is, um, starting, uh, so starting on January 12th. So this is, I think this is where Eric next week. So it\'ll have been a last week already. I\'m going to be doing weekly Twitter chats. About what\'s happening in, uh, jobs in WordPress.
\n\n\n\nSo most people are aware that every Wednesday [00:10:00] or I should say most Wednesdays, I tweet out a list of job openings that I\'m aware of in the WordPress space. And some of that comes, I\'ve created a site called WP career pages.com. Um, that was one of my, my pandemic projects during their initial lockdown.
\n\n\n\nBack in 2020 was to create a site where people could just go and look at. For jobs and this pin up any of the career pages that are there and see what\'s available. So on Wednesdays, I go through, I pull, you know, 10 or 15 of those and I set up, send out a tweet saying, there\'s all these jobs. If you\'re interested in applying, you might want to apply for this job here.
\n\n\n\nThat\'s that\'s up there. And I was approached by Daniel Schutzsmith asking if I thought that would be fun to do as a Twitter space. And so I piloted it just to see what would happen back in December, before the holidays and everything else. And we had quite a few people actually show up to hear what I had to say.
\n\n\n\nAnd so. I start doing that on a weekly basis. It may be five minutes. It may be half an [00:11:00] hour. It depends on who joins me and what kinds of questions they have. But I will, at that point, talk through some of the openings that I\'ve seen and answer any questions that people have about getting hired and about resumes and anything else that they have to ask.
\n\n\n\nSo we\'ve kind of an open space on Twitter every Wednesday at 1:00 PM Eastern time, uh, as, for however long it lasts, but no more than a half an hour. Cause I do have a day job too. And we\'ll see how it goes. For sure. Um, but you\'ll be able to get to that, uh, through, uh, by, by looking at that events page that you mentioned, cause they\'re going to be listed there, but also just going to the post status, Twitter on Wednesdays at 1:00 PM.
\n\n\n\nExcellent. Join that Twitter space.
\n\n\n\nDavid Bisset: Yeah. Twitter space seems to be like, if you want a casual conversation, not so much formal, but yeah, I think that works out well. I\'ve had some experience with that as well. I would,
\n\n\n\nMichelle Frechette: if I\'m working from home, I might add pajamas, but you\'ll never know because it\'s audio only, right.[00:12:00]
\n\n\n\nDavid Bisset: Everybody goes to Dave\'s on audio. Thank God. All right. If David\'s audio only, only I\'ll go talk to him. I\'ll go see what Dave\'s doing. Sure. Why not? I\'m sure they\'ll work out. Fantastic. Yes. And again, if you go. I\'m going to put the link to the career pages. And I remember when you started doing this, um, the career pages, um, thing, and then on the Twitter every Wednesday.
\n\n\n\nAnd, um, we\'ll probably share link for one of the later last ones she did for that as well. That, to me, it\'s always great to have something consistent like that. I\'ve seen your stuff for Wednesday, for Wednesday after Wednesday after Wednesday. And I think if something ever drastically happened to my job situation, I would look and see when the next available Wednesday was.
\n\n\n\nIt\'s like, okay, well I know on Wednesday, I\'m going to, yeah, well, I won\'t even have to think about it because it\'s all, it\'s all. It\'s, you\'re, you\'re very consistent on that and kudos, kudos to you for that. So I\'ll share the link for the career pages. The one of the law, one of the latter ones you did on Wednesday.
\n\n\n\nUh, into the show notes too. Yeah,
\n\n\n\nMichelle Frechette: what\'s [00:13:00] interesting is, I mean, we can\'t see each other\'s Twitter analytics. Of course, you know, you can only see your own, uh, but I get anywhere from 3000 to 20,000 impressions on those Wednesday tweet threads, depending on who sees it, what\'s going on in the day. If there\'s a ton of, you know, other activities happening in the world, et cetera.
\n\n\n\nUm, and whoever\'s on Twitter and happens to retweet it, but. Uh, but yeah, we\'ve got as many as 20,000 impressions on those. So clearly they\'re hitting the mark and people are interested in seeing what\'s happening out there. And in the career field
\n\n\n\nDavid Bisset: these days, your situation can change at a moment\'s notice.
\n\n\n\nSo I think having a constant beacon every week, even if. This week, you\'re fine. Next week, who knows? Oh, or you could, or you could suddenly have inspiration to look for something better or different, you know,
\n\n\n\nMichelle Frechette: exactly. No judgment. There\'s no judgment,
\n\n\n\nDavid Bisset: no judgment here.
\n\n\n\nMichelle Frechette: They\'ve just been here. And then I had an interesting idea to do yet glutton for punishment.
\n\n\n\nI put out as many conferences and things [00:14:00] I\'m on. Um, I\'m on the team for work camp Europe. I am on the word Fest team. Um, and I do a lot. The seller is seller WP, as far as, um, attending conference word camps and conferences. But I had an idea for another one. Which is, um, the people behind, Hey, Presto conference actually reached out to me and said, just want you to know, I know that you\'ve participated in the past.
\n\n\n\nWe\'re not going to continue with the, Hey Presto, Twitter conferences anymore. They\'re just decided to go in a different direction. They\'re not going to do that. I said, Hey, would you mind if I picked up the reins and. Carried on doing something very similar and not necessarily the same exact thing that they were doing, but, um, along those lines, and they\'re like with our blessing.
\n\n\n\nAnd so May 24th, we will have the first ever, uh, online. Post status Twitter conference. And that will be May 24th. And it\'s going to run from 9:00 AM until I think, I can\'t remember 10:00 AM to 5:00 PM or something like that Eastern time. And I get central and Eastern. I [00:15:00] can\'t remember what I\'ve scheduled when I\'m, but just go to the website.
\n\n\n\nIt\'s there. We have it all there
\n\n\n\nDavid Bisset: All I know is it\'s bright outside therefore I\'m narrowing down what the time is. Right.
\n\n\n\nMichelle Frechette: But what it is is it\'s going to be an opportunity for people to present at a conference. Ha by creating a series of 15 tweets, you\'ll be assigned a particular point of time. During that day, every half hour, there will be a new presenter.
\n\n\n\nThe first 15 minutes, they\'ll present a tweet a minute. And the second, 15 minutes of their half hour be Q and A and opportunity to have conversation. Uh, I\'m using the conference hashtag and then whatever, um, you know, um, mentioning the, uh, the particular presenter. I keep saying speaker, but you\'re not technically speaking.
\n\n\n\nYou\'re just presenting. Um, again, this is something you could do in your pajamas too, because it\'s Twitter do whatever you\'d like. So, but, but we will be organizing it as a conference and have official. You know, schedule of presenters during that day. And so we [00:16:00] have people already applying to speak, uh, sorry, present.
\n\n\n\nSee, it\'s not easy to say. I have that
\n\n\n\nShould have a big word just printed across the screen. So I don\'t mess it up, but we have people already applying to present on different topics. Our, um, and I know you\'ve talked about this before, but as post status. Um, tenant for this year is give, grow together.
\n\n\n\nAnd so that is also the theme of the Twitter conference. And so we\'re hoping that people will incorporate that into the topics that they apply to present so that we can make sure that we\'re all moving together forward giving and growing together.
\n\n\n\nDavid Bisset: You . What does that mean to you personally?
\n\n\n\nMichelle Frechette: Um, I mean,
\n\n\n\nDavid Bisset: I think to me it seems to be a lot of what I already do, so I
\n\n\n\ndemonstrated you give a lot.
\n\n\n\nYeah.
\n\n\n\nMichelle Frechette: But I try to do it not in avoid. Right. So [00:17:00] I try to work with other people. That\'s why I\'ve joined Post Status. And that\'s why I\'m here. With everybody here. It\'s why I am the president of big Barnhart, because I like to do things with other people and to move the community forward and to be somebody who is hopefully a catalyst for good and for more, uh, people working with one another and to build better community and a more inclusive community.
\n\n\n\nFor sure. And so to me, give, grow together. Is about each of us giving what we can to grow the community and help each other grow individually and obviously doing it together so that we can, um, as one build the community to be as good as it possibly can be.
\n\n\n\nDavid Bisset: Right. Looking for the, looking for the good in others and looking for the good in ourselves that we can share.
\n\n\n\nThat means a positive influence on as many people as possible because. Uh, in an upbuilding way too, because obviously for the past couple of years, people sorely need uplifting, positive [00:18:00] momentum. And I mean, you know, have a great tech talk. That\'s fine. I, but you know, I get a feeling when word camps are fully, fully back.
\n\n\n\nYeah, there\'s going to be so many of these, um, touchy, feely, emotional dogs, where they were working at Miami. We always would sprinkle them out, you know, in, in various parts and get people motivated and stuff. Um, but now I think we need that. We need that motivation. We need that togetherness. Where we can get it, right?
\n\n\n\nIt\'s not, we\'re not waiting for this point in the year where we\'re either travel or don\'t, or watch it virtually or something. We need it where we can get it. Some people even need it on a daily basis sometimes to survive mentally. So I think this, I, I think it\'s something that, that, that should feel if there\'s any gap in somebody\'s wondering if they need to contribute or be on the receiving end to.[00:19:00]
\n\n\n\nOf that pro and give. Go ahead and check out the conference. And the best part is, are using Twitter. So, I mean, you can, you can, you can leak and look at the celebrity gossip. And then there was a tweet from this conference. And then, you know,
\n\n\n\nMichelle Frechette: You dont even have to register because like what we can\'t gatekeeper Twitter.
\n\n\n\nThere\'s there\'s, there\'s no ticket selling Twitter
\n\n\n\nDavid Bisset: already has its claws in you. We\'re not asking for anything.
\n\n\n\nMichelle Frechette: We\'re just saying, go pay attention to this hashtag. And we will be turning each, um, each presentation, each presenter into Twitter moments so that we\'ll be able to have all of their, um, presentation in one space so that you\'ll be able to consume that at a later date, too.
\n\n\n\nUh, but you know, considering it live while it happens is even better because you could engage with the presenter and ask any questions that you have, um, which helps you at home.
\n\n\n\nDavid Bisset: Plus also, it also stops that nagging question that usually people ask ever after all the other conferences, what\'s your Twitter handle.
\n\n\n\n[00:20:00] If I had a dime, I can say it a bunch of times. Well, that sounds fantastic. So let\'s see if I got this straight. We have the career summit. We have the, uh, live spaces. Um, I should say Twitter spaces for the, um, for the weekly WordPress jobs. And then we have the Twitter, um, conference happening. Remind me again, that what the date was May 24th, May 24th, right?
\n\n\n\nUm, at 9:00 AM to 4:00 PM. Currently as the time of this recording, 9:00 AM to 4:00 PM Eastern time on there. And that\'s what we have. That\'s what we have to willing to share right now to the public. Um, and right now, but if you want to S if you\'re listening to this and you want to see maybe the latest. Um, cause we\'re going to be adding to this.
\n\n\n\nI mean, there\'s more coming down the road. You just can\'t tell me about it on a recording. That\'s fine.
\n\n\n\nMichelle Frechette: I actually had a conversation this morning about something that\'s probably coming up pretty soon that we\'re working on. So [00:21:00] that\'s all I\'m going to say.
\n\n\n\nDavid Bisset: Stop teasing me! stop teasing me
\n\n\n\nMichelle Frechette: I\'ll DM you later, but yes, there definitely will be more.
\n\n\n\nAnd if there are things that you, dear, dear reader, dear listener.
\n\n\n\nDavid Bisset: You say speaker and we always have to constant
\n\n\n\nMichelle Frechette: gentle listener, whatever whoever\'s listening to us right now. If there are things that you think that we can be doing and doing better and ways that we can be meeting the needs of our community at plus status and the greater community, we want to hear about it.
\n\n\n\nIf you\'ve got ideas, as a matter of fact, the idea that I was kicking around this morning with some of our. Post status people was brought to me by a post status member. And so we definitely are listening to the things that you think would be edifying for our community. And if there\'s some, if it\'s something we can move forward with and help facilitate, we were very interested in doing that.
\n\n\n\nSo we are absolutely open to ideas. The whole idea of together is an us sitting at post status, [00:22:00] handing down all of these events. But certainly doing it together with you. And we want to make sure that we\'re just not guessing what might be good events, but also I\'m listening to you and your needs. And so bring us your ideas.
\n\n\n\nDavid Bisset: Fantastic. So again, uh, once again, post-test dot com slash offense. And if you want the, like Michelle said, reach out to us with some of your ideas, uh, best way to do that is just to reach out to us via our contact, um, form. Well share let\'s let\'s just get this on the record. What are the ways people can reach out to, to, to learn more or to.
\n\n\n\nMichelle Frechette: Yep. So I\'m on Twitter at, @michelleames or you can, I also could, uh, can get into the, @post_status so you can message us either place there. If you are on slack, you can find me on the post status lack. I I\'m very easy to find and I\'m, I guess, ubiquitous I\'m everywhere
\n\n\n\nDavid Bisset: right now. Follow the rainbow of smiles and you will find it.
\n\n\n\nYou\'ll find Michelle. Michelle is probably one of the best people. Um, but that [00:23:00] doesn\'t, that I don\'t owe money to. She\'s a great focal point. So I encourage you. If you have some feedback on the stuff that we were talking about or something new or need that you see in the WordPress community. I mean, we\'re not the eye of Sauron here.
\n\n\n\nWe can\'t see everything. I\'m not even sure if that\'s the correct reference. I got to go through,
\n\n\n\nMichelle Frechette: go back to the books, had the word
\n\n\n\nDavid Bisset: that\'s good. So thank you very much, Michelle, for covering all of this and, um, getting the word out about this and I\'m looking forward to. One of your first, um, Wednesday Twitter spaces.
\n\n\n\nIn addition to all the addition to all the other things we\'ve been talking about here. So thanks again. Super excited.
\n\n\n\nMichelle Frechette: It\'s my pleasure. Thanks.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 19 Jan 2022 04:45: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:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"Post Status: Post Status Comments (No. 6) — The State of the WordPress News European Edition\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=92340\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/comments/6/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:81405:\"After the first Post Status WordPress News Draft went so well, we decided to do a more European timezone-friendly version. The group of news “avengers” that assembled in this episode are Winstina Hughes, Tammie Lister, Nathan Wrigley, Amber Hinds, Yvette Sonneveld, and Malcom Peralty — with David Bisset hosting. In three rounds of draft picks, this group assembled new and interesting picks of the most noteworthy or influential WordPress news stories of 2021.
\n\n\n\nAlso: Video recordings of some of our members\' single biggest news picks were included in this episode.
\n\n\n\n\n\n\n\nPost Status Comments ![\"💬\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f4ac.png\")
is a stage for WordPress professionals to exchange ideas and talk about recent topics and trends.
Browse past episodes and subscribe to our podcasts on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or get them by RSS. ![\"🎙\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f399.png\")
Mentioned in the show:![\"GitHub](\"https://img.shields.io/github/downloads/bph/gutenberg/total\")
Theme.json horizon. Sponsor: BluehostEverything your website needs — from start-up to success story — is at Bluehost. Whether you\'re looking to create a website, blog, or online store, Bluehost will get you started with an all-in-one website platform tailored to your specific needs. Get a free domain name in your first year, free 24/7 lifetime support, and total design freedom with WordPress at Bluehost.
\n\n\n\n\n\n\n\nPSC Episode 6
\n\n\n\nDavid Bisset: Welcome to the second episode of the WordPress draft. I call this the European edition because we had a people saying, why don\'t you make one for the other time zones, let\'s go around and introduce our players slash panelists. Let\'s start off with Tammie.
\n\n\n\nTammie Lister: Hi, I am Tammie. I work with design at SVP, amongst other things and drug was being,
\n\n\n\nDavid Bisset: yeah.
\n\n\n\nSo, okay. On our next, on our list, Malcolm, you\'re up next.
\n\n\n\nMalcolm Perotti: Hi, I\'m Malcolm Perotti. I\'m the co-founder of PressTitan and a product owner at Canberra creative.
\n\n\n\nDavid Bisset: Yes. You also do a podcast with Jeff Chandler.
\n\n\n\nMalcolm Perotti: Yeah. Co-host the WP mainline podcast.
\n\n\n\nDavid Bisset: Yes. Feel free to guilt Jeff for not being here by the way
\n\n\n\nMalcolm Perotti: . I will definitely
\n\n\n\nDavid Bisset: not too much. It\'s out of his control. Up next is Amber
\n\n\n\nAmber Hinds: I\'m Amber Hinds. I\'m the founder of equalize digital, which is an accessibility company. And I also organize the WordPress accessibility meetup.
\n\n\n\nDavid Bisset: Our next panelist, wasn\'t able to meet with us in person, but the panel lie, but she be prerecorded her introduction and her news picks Winstina Hughes, please introduce yourself.
\n\n\n\nWinstina: Hi. I\'m Winstina Hughes. I\'m a core contributor and the community contributor. You know, me as part of the WordPress nearest to the meetup community, I\'m to be an organizer that works with the Maryland department of transportation state highway administration. I started as an assistant regional planner, and I\'m currently working as a customer in government relations manager.
\n\n\n\nDavid Bisset: after her
\n\n\n\ncomes the almighty Nathan,
\n\n\n\nNathan: um Nathan Wrigley from the web builds podcast and the WP Tavern jukebox podcast,
\n\n\n\nDavid Bisset: which means he\'s a better, more professional speaker slash podcaster than me, ladies and gentlemen finally is your Yvette.
\n\n\n\nYvette: Thank you. Oh my all those podcasts, we\'ve had some failed. I work as a team lead community for Yoast, pretty active in the WordPress community, but speaking and in the marketing team and very excited to be here.
\n\n\n\nDavid Bisset: Just had some news yesterday about, um,
\n\n\n\nYvette: Shopify
\n\n\n\nDavid Bisset: I was going to say Spotify. Um, I\'m not even going to edit this out. I\'m not even good at this out. I talked to taco yesterday. I said, congratulations on Spotify. And he says, everybody does that for the first month.
\n\n\n\nYvette: I do it all the time too. So don\'t worry about it. And other than that,
\n\n\n\nDavid Bisset: all right, so let\'s get things started here.
\n\n\n\nWe\'re here to share our favorite or the biggest, most influential news stories of 2021 related to WordPress that meant the most to us. And if you are new to this concept at listener, we are going to link in the show notes for the first edition. We did have this a couple of weeks ago. There was no need to listen to that episode first.
\n\n\n\nThis is brand new people with probably a lot of interesting picks. The order has been selected by random.org, Tammie, your first, what is your first news pick for us?
\n\n\n\nTammie Lister: Oh, my first one is going to be the pattern directory and that\'s the launch of it. So the first bit of it, um, existing, I guess, uh, there, there was a post when it was stolen on the make matter.
\n\n\n\nAnd that was kind of like- it had kind of been happening. We could be an adding to it. And over the year more of that\'s happened. I wanted to kind of put a focus on that because it\'s something more relatable to pretty much use it, then blocks it. And it shown that you can really rapidly build a patterns and from, and maybe I\'m slipping into the default theme with patterns, but honestly it feels like a theme that\'s kind of running here, but I go that the panel directory is a great news story to kind of start us off
\n\n\n\nDavid Bisset: And you may have said so-
\n\n\n\nTammie Lister: April, April was the sort of things were happening before, but there was a post on the 28th of April on make matter.
\n\n\n\nDavid Bisset: So it was April and man, it seems like we\'ve been talking about this for a long time. We\'re recording this in 2022 also is not helping much, even if it\'s the 5th of January, anytime there\'s a new directory and let\'s be honest.
\n\n\n\nWhat other new directories as WordPress had. I mean, even the concept of a new directory blows a lot of people\'s minds because I can\'t remember when the theme and plugin directories came into being, but it\'s kinda like, yeah, it\'s been a
\n\n\n\nTammie Lister: while. And I mean, this is the 2022 news, but now it\'s opening up the patent actually.
\n\n\n\nSo it\'s a whole year span, pretty much from existing to having submission to now being open up for people to start adding. Um, but it\'s just really exciting.
\n\n\n\nDavid Bisset: All right. Well, good, good, good. Will anybody who had that scratch that off your list. Good. Good job. Good first pick there, Tammie. Thank you very much.
\n\n\n\nUm, Malcolm, you\'re up next? What is your, um, first round pick?
\n\n\n\nMalcolm Perotti: My first round pick is actually going to be the gravity forums. 2.5 update that happened in April as well of 2021. That overhauled UI, uh, changed how I use gravity forms that helped a lot of people kind of, um, use gravity forms more efficiently.
\n\n\n\nUh, it had a focus on accessibility. I mean, I don\'t, from my perspective, I don\'t know how much the accessibility changes really help people. For me like gravity forms is like one of the first plugins I install in pretty much every WordPress install, this, this UI update just made it so much easier to lay out pretty forms.
\n\n\n\nIt made it so much easier just to interact with it. It made it feel more like, you know, day-to-day WordPress. And I think it was one of the most impactful changes that they could have made. And, uh, because it\'s the plugin, my go-to plugin for collecting user data for like anything. Um, it was just kind of a really important thing for me and the users and clients that we have.
\n\n\n\nSo that, that huge overhaul that they did for gravity forms, 2.5, um, would be my top story.
\n\n\n\nDavid Bisset: That was the first commercial plug-in I ever purchased, uh, or I had a license for. And that was you\'re talking like maybe 12, 13 years ago maybe. And their design was definitely the most radical that I\'ve seen throughout it.
\n\n\n\nI think they obviously went for a more block based approach, but it really was. All that different to me. So have you been using gravity forms for awhile? It wasn\'t too radical.
\n\n\n\nMalcolm Perotti: Yeah. And I think the, the big advantage that it gave you as the ability to start really, truly laying out your forms, um, the original format or from version 2.4 and below was really about like a, um, vertical structure form where you could kind of do a little bit more horizontal stuff and put things next to each other and split the form in half and kind of do a little bit more design-related stuff.
\n\n\n\nI think one of the things that has always held people back from using gravity forms, especially over the last year or two as other competitors have really moved very well in that space is the design aspect of the forms. And so to see them start taking that a little bit more seriously was, was a good change.
\n\n\n\nDavid Bisset: So
\n\n\n\nNathan: is that, is that
\n\n\n\nDavid Bisset: allowed? Oh yeah, this is a discussion. Oh, okay. I\'ll privately shame you in zoom, zoom chat, but otherwise,
\n\n\n\nNathan: Don Malcolm, do you, do you feel that they were kind of behind the curve a little bit? Do you think their update came a couple of years too
\n\n\n\nMalcolm Perotti: late? For sure. I think that, you know, in terms of the ability to, as a developer to work with gravity forms, they\'ve always been kind of ahead of the curve there, in my perspective, their hooks and, and things like that have been very generous.
\n\n\n\nAnd how much control you have the ability to build your own? Add-ons very easily was always very, um, powerful. but in terms of the, the design language of forums and the control of forums, I think they kind of leaned too much on their community to kind of fill that gap and it let them kind of near right lag behind a lot of other competitors in the space.
\n\n\n\nAnd I still to this day feel that they\'re a little bit behind some of their other competitors in the. Um, true design control and you still kind of have to use some third-party ad-ons to really do really beautify gravity forms without knowing how to develop a code. Um, but I think it\'s come a long way and I look forward to seeing them continue to push that.
\n\n\n\nAmber Hinds: I mean, it\'s nice not to have to explain CSS classes to clients, right. That\'s how you had to do it before. This is how you put things in columns.
\n\n\n\nDavid Bisset: Uh, speaking of now, Amber, now that you\'ve spoken up, it just so happens. You\'re next? Thank you very much, Malcolm for that one, Amber, what\'s your first round pick.
\n\n\n\nAmber Hinds: Yeah, so I will say that one was not my first round, but it was on my list. So my first round, I think the thing that really got the most attention was, uh ACF asking lifetime users to buy a subscription. I see. It\'s interesting because I am a lifetime. Like, I mean, I bought a lifetime license. I don\'t know what, in 2011, it was long time ago, but.
\n\n\n\nYeah, I also have, and I, and we put it on every website. We built literally every single website, right. So I have more than gotten my money\'s worth. We don\'t really ask for support, but that said like, you know, we can probably pay more. And, and it is interesting too, because a lot of people were getting really upset about it.
\n\n\n\nAnd, you know, I think maybe the way they went about it could have been a little better, but having recently entered the, I sell commercial plug-in space myself in the past 12 months. It kinda, you know, for me, I also see it from the business side. And, you know, and also from the side of, well, if they went away, I use this on every website I built now I have to come up with a different tool.
\n\n\n\nI feel like it got a lot of one-sided press and maybe not as much.
\n\n\n\nDavid Bisset: Was it the concept or how they asked or both or neither? I
\n\n\n\nAmber Hinds: mean, maybe it was because they didn\'t like during black Friday, which is when people are expecting to not pay for things or they\'re expecting to pay a 50%.
\n\n\n\nDavid Bisset: Yeah. That\'s kind of like going up to my parents and saying, it\'s like my parents\' anniversary party where I go up to them and says, by the way you owe me 20 bucks, that\'s kind of an awkward conversation.
\n\n\n\nAmber Hinds: Yeah at Christmas, I think, I think they probably could have done a lot more to communicate why pay, you know, what are the costs of this plugin? How many, and I know we\'ve seen some that in the past, like the support requests on it are exponential, right? And it\'s got a huge free user base that are referring support as well, but maybe outlining some of the numbers on that might have made it more understandable to people, as opposed to just being like, Hey, want to help us out buy a subscription when you\'ve already paid for this thing.
\n\n\n\nDavid Bisset: When I was thinking about that story and emphasize to me the importance of lifetime subscriptions, um, if you are someone who\'s acquiring another company and I\'m sure thought went into that. Um, in fact there was, there was discussion even before that notice went out about lifetime subscriptions. But with any business that you\'re acquiring that lifetime subscription chunk is obviously something you need to, to pay close attention to. And I think they did, but I think the messaging was probably, like you said, partly mistimed, if you are able to give some additional incentives to people with lifetime subscriptions. Great. If I was starting a new plug-in service today would be one of those very careful decisions you have to make about like, like short-term lifetime subscriptions could be great for your business, but further down the road.
\n\n\n\nAmber Hinds: Yeah. I mean, like that was something we decided, right. We were like, all right, let\'s offer lifetime licenses as like a Kickstarter. Right. So we did it for maybe six months. Never going to do it again. It\'s like a small amount. It\'s enough people that it\'s manageable. It brought in extra revenue that we wouldn\'t have had if we didn\'t do that.
\n\n\n\nBut it\'s not, I think for, from a plugin developer standpoint, you can\'t think of that as like. Primary way of selling your product
\n\n\n\nDavid Bisset: or you do something really evil and you only offer lifetime subscriptions to very, very old people. That\'s the only, that\'s the only way I can see what we\'re working around that, but that would be cool.
\n\n\n\nNathan: I was just going to interject here and say, this was the, I think for me, this was the only story that kept coming back in the air. I think it, the, the story itself was June, maybe July, something like that, but that it was acquired from Elliot Condon and, uh, went under the stewardship of delicious brains.
\n\n\n\nBut then, then there was a couple of occasions subsequently where Ernie, I think it was Twitter. Um, the. You might characterize it as a misstep on Twitter, you know, and a poorly thought out phrase, essentially kind of asking, uh, what, what people\'s thoughts would be about the, the restructuring of the pricing model and, and the inevitable storm that that happened.
\n\n\n\nThen most of the WordPress news from the, for this year just sort of happened and went away. This one happened, went away, came back, went away, came back. And then here we are still talking about this six months later,
\n\n\n\nWinstina: it\'s this a maturity, right? We can\'t maybe use such wide terms as like forever and lifetime.
\n\n\n\nWe have to be a bit more true to what, what things mean, right. Because lifetime\'s a long time and it\'s sort of that kind of trust, you know, additional product has had the same trusses and you don\'t have in physical products, those kinds of perceptions or those things. And we have to kind of change it\'s the growing up of our ecosystem and that kind of changing.
\n\n\n\nSo I think it\'s a sign of a positive sign about ecosystem.
\n\n\n\nDavid Bisset: All right next up is Winstina Hughes, please heal us. Your first round news picks.
\n\n\n\nWinstina: I cannot believe that y\'all are missing this number one acquisition use melt choice. And how long have you Sandy had been acquired outside of the word prosperity?
\n\n\n\nAll this is talent acquisition, Mel and Helen. I\'m a silent admire. Y\'all know I\'m my own little corner. I want you to know that you will be missed. You are two incredible contributors. Um, Mel, I want to give you prompts for what touches my world really directly. I know that you were part of a 4.8 team, um, core team.
\n\n\n\nAnd one of the contributions that you were a part of was that widget and dashboard by let\'s, you know, users know about upcoming. So I want you to know that that work that you did, this is really important directly impacts me the stats that you guys gave 30% increase in meetups. Um, that\'s pretty special for us.
\n\n\n\nSo thank you for that, Helen. You\'re a boss. I just love how full people are. Um, and I, you know, um, just listened to your commitment to Tena, you know, um, you and I spoke really briefly about it. Just really giving them, you know, so much of your, your time, right? And, um, like your, your contribution, um, to building that company and also to making improvements in core is really phenomenal, uh, directly.
\n\n\n\nThat you\'ve impacted, um, me and our New York city meetup group, uh, is your being part of that panel of women in 2017, you know, discussing, uh, just the needs of women than the WordPress community are women of WordPress. And so they made up series as a direct result of that panel discussion. And so, you know, thank you for that.
\n\n\n\nUm, so to take in the fact that, you know, these like really two incredible sources of talent have been acquired beyond the WordPress space.
\n\n\n\nDavid Bisset: Yeah. We don\'t really think a lot about talent sometimes, especially when it leaves the WordPress computer. Although we, we do, I think we clarified a little bit that, um, Mel hasn\'t left WordPress itself.
\n\n\n\nUm, Tammie, where did you say she was going?
\n\n\n\nTammie Lister: I know she just released a post saying that she went to ATF in her review something. Oh, so we can link to that. She did a annual summary and she said where she was going in that.
\n\n\n\nAmber Hinds: Yeah. I mean, 18 S is the digital services for the government in the United States.
\n\n\n\nRight. So she\'s probably going to do some WordPress there. Maybe not because it\'s not explicitly. I mean, it\'s focuses a lot on accessibility too, which is kind of cool. That\'s probably a footnote right. In the last one, someone mentioned Pippin leaving right after the acquisition of Sandhills. And he\'s like, I\'m not going to do WordPress at all.
\n\n\n\nLike, it is an interesting thing, right? It, it changes the community when people like that leave.
\n\n\n\nDavid Bisset: It does a lot of the original tech players, like the people who started Google, the people who started obviously apple. Um, there are people that started, um, uh, Amazon, all of the big, big people that started those companies are no longer there. They\'ve retired. They moved on. So it\'s almost happening. The same thing in the WordPress space with acquisitions and people retiring or moving onto, uh, Nathan, uh, what is your first round?
\n\n\n\nNathan: So my first round pick is the, is the ACF news, but that\'s been stolen from on-demand.
\n\n\n\nSo I\'m going to get it to my, yeah, that\'s right. I\'m going to go to my pick number two, which is open verse the, uh, the fabulous open verse, which you can find at wordpress.org forward slash open verse. If you\'ve not come across this before, it\'s basically CC search, which kind of appears to have lost its way.
\n\n\n\nI don\'t really know if that was financial or, uh, bodies on the ground working on it, but it\'s come under the stewardship of wordpress.org and it\'s, um, it\'s a way that you can go and search currently for, well, it says 500 million images, most of which are CC zero. So you\'ll be able to use these images and not worry about having to get a lawyer involved in a couple of months time, because Getty come after you because you\'ve inadvertently put something on your website, which is copyrighted and the, the most exciting thing isn\'t really, for me, that, that exists under the stewardship of wordpress.org. It\'s really how this is going to be integrated in the future with the block editor. Just the idea that hopefully at some point in the future, if you upload something to your media library, that there\'s talk about the fact that you may be able to just tick a box and that the simple ticking of that box will therefore make your media available to everybody in the same way that you can get other people\'s media at the moment.
\n\n\n\nSo imagine how many, how many media libraries contain, how many images throughout the WordPress universe. And it must be tens of millions. And if by simply ticking a box, you could make that available for everybody. That would be fabulous. And that as well, we\'ll end up with this, um, talking on a podcast episode with some people that are working on the project, you never know, you might be able to upload your block patterns for, um, various other things like that.
\n\n\n\nSo the scope is much bigger. It could be PDFs, it could be images, it could be audio, it could be video, but also the idea that design, uh, templates, so block patterns. And so on that that you could make those freely available is just fine.
\n\n\n\nDavid Bisset: I would love to have a discussion about that. I think it\'s, it\'s nothing that\'s probably going to it\'s we\'re talking like, like a year, long years, long project, there were
\n\n\n\nNathan: several, several years
\n\n\n\nDavid Bisset: away, but there that I think fits really well into.
\n\n\n\nIf you listen to Matt state of word, his overall goal is not just about WordPress, but Gutenberg being bigger than WordPress and all of these acquisitions automatic has done through the years about acquiring this piece of open-source. the, You know, this messaging app, this journaling app, tumbler, all of these things, he seems to be collecting one of every type of different corner of the web in and through automatic.
\n\n\n\nCause that\'s probably where it probably makes financial Lawyerist sense to probably do that. But, but if you want an open web, which has been really pushed for the past year, I think even as much as the Gutenberg has been pushed, this, this CC, um, this creative comments acquire, uh, I think fits well into that strategy.
\n\n\n\nAnd I\'d love to talk about more about that. I think Nathan, you just, I think I just had a, um, thought explosion in my head, um,
\n\n\n\nWinstina: talk about democratizing design publishing, but it\'s kind of a democratizing of design and the leveling up and access of design for everybody which were part of the work that is happening with the editor is about, you know, enabling everyone to have a base line of design and the boundary, because if you give too many tools to do that, you\'re setting people up for failure by having, you know, patterns is one of them, but also templates and having, this knowledge that was kind of locked and told and ancient tools and all those kinds of things, it shouldn\'t be, it should be access.
\n\n\n\nYes. There\'s always going to be a need for craft. And there\'s always going to need to be a need for design systems designer, but there still should be access to that information. And I won\'t have a design sense and I won\'t you think to ask it because I have to experience it. So, you know, it\'s part of that.
\n\n\n\nJust as we try to have coding standards, having design standards before we create as well, I think it\'s so, so important.
\n\n\n\nDavid Bisset: It has been removed from the board. And I must say that was a pick that somebody had in our last episode to it. So it was a very, very popular, very bird about nines. Yes. But you, you actually brought a whole new angle to it.
\n\n\n\nSo thank you for that, Yvette, what do you got for us?
\n\n\n\nYvette: One on my list and it hasn\'t the workers, community, uh, announcement that the team was proposing a decision checklist to restart local events, which initially really excited me. And then as the world progresses, whereas I could jump into an event tomorrow or my heart would love to because connecting with the people that I love and that I resonate with and that hanging out with all those brilliant minds can\'t happen soon enough, but safe.
\n\n\n\nSo now every time something pops up around in-person events I Get excited. And then I won\'t allow myself to get excited because well, safety. Um, but I think the fact that the checklist is there to help prepare events safely is really a good thing.
\n\n\n\nAmber Hinds: I think it was hard after state of the word. Like I was like, oh, Hey, there, there is a first example of an in-person event.
\n\n\n\nIt was small. And then I heard like a bunch of people got COVID. Right. So, so that it\'s like,
\n\n\n\nDavid Bisset: and there\'s work camps starting, I think next month, um, in, in the U S and in other locations as well. So yeah, but not to, not to put words in your mouth, but the checklist being the top story for you is getting some order and procedures in place.
\n\n\n\nSo regardless of when and how these things start, there\'s at least some order to it. Right.
\n\n\n\nYvette: I think it\'s really helpful that they were there and I can wait. Uh, for events to get started.
\n\n\n\nDavid Bisset: Normally I would go next, but I already went, I already shared my news is in another episode. So I\'m actually sharing now a real quick one here from, I\'m going to say, I\'m going to Butch, sorry.
\n\n\n\nIf I butcher your name LA lax. It\'s Lax Mariappan. And he\'s going to tell us from our zip message, what his new story picked for 2021 was,
\n\n\n\nLax Mariappan: um, I\'m lax. I\'m a backend engineer at WebDevStudios. Uh, for me personally, I like themed dot Jason or like the full site editing experience. Uh, it\'s kind of a game changer, but I would say, uh, as I started in 2010 and where you have to, uh, create templates and other stuff, you know, you know, it takes time to do that.
\n\n\n\nNow it\'s all in a single file. Great.
\n\n\n\nDavid Bisset: Well, short and sweet and I love that. So if you had themed Jason, the introduction of which on your list, feel free to remove that. It\'s something that\'s. It\'s still kind of developing, but if you can create customizers, people are creating customizers in the web like web forms to be able to customize your theme dot Jason.
\n\n\n\nUm, I\'ll put a link to the introduction of theme, dive Jason from the wordpress.org associated with that pick into, into the show notes for that good pick Lex. Thank you, lacks. I should say thank you very much, Tammie. You are up. We\'re going to, we\'re doing a second round here, which is second news pick.
\n\n\n\nWinstina: I am going to tangent on to that, looking at the theme Jason horizon.
\n\n\n\nAnd so Makiah slowed the pace back in August about the ingest of horizon and this isn\'t necessarily a news post. This is a thought post. And I kind of think it\'s really interesting to balance in these posts posts because, um, those are how we kind of start thinking about things a little bit. And this post really was about.
\n\n\n\nThe now and the future of theme, Jason. Um, so theme Jason was a previous year this year and the future year thing. It spanned multiple years really. Um, and in that it really dare to dream about thinking about design structure and portability and thinking about native apps and how it could even control ads, maybe in the future events super-wide in this post.
\n\n\n\nAnd I think it\'s really interesting to start thinking about, um, there was a term used in it about coded recipe if they have a site looks and feels. And I think starting to not just think of like this little bit of script, which is what we\'re kind of focusing on with the, and Jason, but as a mechanism of where it could become how it can ease things like accessibility, just make design more accessible to everybody to understand, and then bring in kind of apps and maybe even a more medical admin space.
\n\n\n\nSo it\'s, it\'s one of one. Bloodsport pieces, I guess, too. It\'s one of those posts that I think sometimes we have all these, like opposition is on the stupid side and stuff, and sometimes posts like this kind of like really quietly. Um, and I think it\'s really important to kind of go back to them and kind of digest them.
\n\n\n\nIt\'s about that. That was back in August. And it\'s a post I\'ve gone back to a few times.
\n\n\n\nDavid Bisset: Yeah. The sheer readability of dot Jason and its flexibility as loud already. Like I mentioned before, a couple of people creating tools for its customization. That\'s the kind of innovation maybe it\'s been because of the last couple of years, for me personally, about listening to people, discuss how difficult it is to customize blocks without, and then, you know, ACF and PHP and all of that.
\n\n\n\nBut you know, in the beginning, you know, you know, you have to learn react. You have to learn this in order to do the two blocks and so forth. There was, there was definitely a learning curve there and there still is. And there\'s other tools that are helping with that, but just the theme, Jason, right off the bat is human readable.
\n\n\n\nWinstina: Yeah. I said it needs to be things, but it\'s also the mechanism and what it for tolls. And I think that\'s the interesting part about this post and the interesting kind of change. Like we\'ve, we\'ve got the mechanisms and now are they, where can that go and start into that\'s something like damning to dream.
\n\n\n\nAnd I, that\'s kind of what I liked about one candidate for, to dream about the, what ifs in it as well. So yeah, I think that that is something we should do more of. So for me, it was.
\n\n\n\nDavid Bisset: And before I dare to dream, I\'m going to first next dare to ask Malcolm what his second round draft newspaper.
\n\n\n\nMalcolm Perotti: Yes. So my second round is actually going to be a story from way back in January of 2021. And basically I want to put it under the umbrella umbrella of like good WordPress search gets harder.
\n\n\n\nUm, so elasticpress.io, um, was trying to figure out what the heck they were going to do next. After the elastic search project abandoned their open source licensing in, in the general sense of WordPress search is not talked about much other than to say. Basic built-in WordPress search kinda sucks. Um, and this was an opportunity to kind of improve that.
\n\n\n\nAnd now there\'s been some step backs away from that due to, you know, some licensing issues. Um, you know, there\'s, uh, open search, which is a fork of elastic search and there\'s a lot of different things kind of happening in that space. Um, I really think that the elastic press service from TenUp is, is a great, easy kind of entry point for a lot of people to get good search on WordPress.
\n\n\n\nUm, and I\'ll be interested to see kind of how they deal with these continuing issues. I don\'t know that they\'ve announced any change yet. I think the conversation was maybe that they would use open search instead of elastic search, um, for elastic press. And I don\'t know if that means they\'ll change it to.
\n\n\n\nOpen press.io instead of elastic press that AOR or however they\'re going to deal with that, that kind of issue. But, um, I think that, you know, as a WordPress community, we still need to kind of fight for better search in WordPress. Um, it\'s one of the two main issues that I see in WordPress currently agree.
\n\n\n\nThat\'s what we do. Right. We drop back to Google, which is not ideal, well,
\n\n\n\nDavid Bisset: that\'s not the open web that, um, yeah, I think if performance, wasn\'t such a distracting factor in terms of WordPress, in terms of like teams to put together, I\'d love to put a search team together. Performance effects, all WordPress sites.
\n\n\n\nSearch is huge, but it doesn\'t affect everybody right now, I guess, because not everybody searches through a site, but they just had an article. Um, I earlier this year about how young people, these days don\'t know what a file or folder system. I don\'t I\'ll have I\'ll share the link. I don\'t have time to explain it now because
\n\n\n\nAmber Hinds: I don\'t have any frame of reference because vanilla folder stuck in a
\n\n\n\nDavid Bisset: drawer, but what do they know?
\n\n\n\nBut what do they know search, right. But what if there was like a little, uh, there\'s a, plug-in like this that already kind of exists where you hit a key command on, on your WordPress site. And like a little window shows up, like on a Mac that you have the, um, Alfred or something, and you can type in a few words, but it\'s not the UI that it\'s the, it\'s the effectiveness of the search built in.
\n\n\n\nRight. So I think Malcolm knew regardless, and I think, uh, please feel free to include any, uh, extra link in there for some of the things that you mentioned. If, if it\'s not covered. I definitely think search has been one of those long time neglected. Oh, I\'ll just use something else to get by and search WP, which by the way is also an awesome thing as well.
\n\n\n\nBut it\'s kind of a slightly, it\'s a slightly different tool. Um, I think, but built in better built in WordPress or. Whatever can get us there or thinking more about it, I think is fantastic. So Malcolm hats off to you, because I didn\'t even think about that until now. Shame on me. Must be the coffee talk.
\n\n\n\nIt\'s the coffee talking. Speaking of coffee, talking, Amber, what is your second round pick? My coffee wants to know.
\n\n\n\nAmber Hinds: So my second round pick, I don\'t think got a ton of traction in WordPress, but it has huge implications for all websites, WordPress websites. Um, and that was, um, the eyebobs versus Murphy settlement, which was a lawsuit against a website that used the accessibility accessibility overlay, and they had it already and they got sued.
\n\n\n\nAnd then. Karl groves who was of tenon and is now of level access. People may have heard of him because he did a lot of the initial accessibility audits for Gutenberg. And he actually was an expert witness in that case. And the, the whole, I mean, it\'s fascinating. I\'ll give you a link to the PDF of the case because there\'s a 50 page attachment that talks about how.
\n\n\n\nExcessively actually adds accessibility problems to websites. And so that was the original piece, which was, they got sued even though they had it. But this year, the big news that really went around the accessibility community was that they settled, they removed the overlay. And as part of the settlement agreement, they agreed that they had to make their, um, excessive, their website accessible the real way, not using an overlay.
\n\n\n\nAnd so that really. I wish it had gotten more traction in the WordPress space or with web developers or designers. Um, you know, it\'s harder for small businesses, but I feel like even a lot of web developers don\'t pay enough attention to this. And, and a lot of them are kind of just being like, oh, I just put an overlay on the site, you know, excessively or, uh, what is it a user way is a really big one in WordPress that probably, I think that one has the most active installed.
\n\n\n\nUm, and, and this case was pretty much like that will not help your clients. They will get sued. You might get sued too. So for me, that was a huge one.
\n\n\n\nYvette: To accessibility experts from the Netherlands actually wrote quite a really good article about that. And you sniped me with the story, but it would be nice maybe to include the link in, in what you were saying, because I think it\'s yeah.
\n\n\n\nUh, accessibility. It\'s just so, so important. And the overlays.
\n\n\n\nDavid Bisset: Don\'t do don\'t do shortcuts like that bad idea. Um, Winstina you\'re up, give us your second newspaper, please.
\n\n\n\nWinstina: My second job pick comes from the post status extra archives, number 37. And, uh, I am pulling from it, Mary job\'s suggestion that we have a WordCamp Africa. I love it. I love the idea of having a word camp Africa.
\n\n\n\nYou know, this is a reflection of my, my African pride. I am I\'m west African, and so is Mary Job and, and they think that there is definitely an African massive within the WordPress community. And this massive has so much to offer. And you know, this massive, you know, is, is, has like a large diaspora, um, and let\'s put together work camp Africa we have, who were in camp US.
\n\n\n\nWhich I wrap heart. Um, we have a WordCamp, Europe. We have a WordCamp Asia. Um, it\'s time, it\'s time for WordCamp Africa. You, um, have a lead organized already. Mary\'s stepped up and said that this is something that she wants. And, I think that we definitely have the resources and we have the capacity to make it happen, whether or not this is a combination of remote, um, you know, having something that\'s online and also in person, maybe it\'s an online word camp and then like an in-person, contributor day.
\n\n\n\nI don\'t know. Um, I don\'t know the logistics of it. I\'m in the U S I\'m not part of the west African, um, community, uh, you know, that\'s, that\'s on the continent. I can\'t speak to what the needs are. I can only advocate for, for us and say, you know, it\'s, it\'s time, it\'s time where.
\n\n\n\nDavid Bisset: Put that on. I was going to say bumper sticker, but that doesn\'t, that doesn\'t even cover it. That should be, it should be a full-fledged t-shirt and clothing line. I\'m actually going to point for her pick. I\'m going to point to the news link for the post status episode. She\'s actually referring to, to summarize that as best I can, from that conversation with Mary, there is such an explosion of.
\n\n\n\nThings that are happening in Africa right now, dealing with WordPress and the communities, and they\'re doing a fair share of it on their own. And I, and I don\'t know if that was the, it\'s the best way to describe it, but they\'ve started, I think WP, africa.org, they are running with these various kinds of meetups, I think 10 years ago where the WordPress community was in the America and Europe.
\n\n\n\nThey\'re, you know, they\'re, they\'re kind of running their own show. They don\'t really have a, they only have a few WordCamps now in Africa, but they don\'t have anything globally yet tied together. And I think now that they\'re starting to get the kind of, kind of getting that mass, that mass point where they could have some sort of, you know, continental type of movement they\'re, um, they\'re, they\'re becoming more and more unified in their networks and structures.
\n\n\n\nSo I think that\'s a excellent link, new suggestion for just making sure that we\'re aware of all of the continents and spaces on the globe.
\n\n\n\nAmber Hinds: Well, I think too, what comes in with that is like, is there a possibility for having more. WordCamps or talks that end up on wordpress.tv that are not in English, because I really feel like that would make a huge difference in allowing more people access to learning WordPress.
\n\n\n\nAnd, you know, I don\'t know if it\'s all of Africa, maybe it is going to be an English word camp. Maybe don\'t, I don\'t know. Maybe we\'ll be French, but, um, like that is an interesting thought, like, could there be a lot of different languages that come out of that?
\n\n\n\nDavid Bisset: So, yeah, we\'ll see. I mean, obviously COVID is putting some stints in the plans Africa right now is obviously not doing very well with, COVID just like other parts of the world as well, but I think we should just pay more attention, pay more attention to places other than the us and Europe, sometimes a lot of other stuff happening in the rest of the world.
\n\n\n\nSo if you haven\'t checked out. My discussion with Mary and the, or at least the links in the show notes for that episode, please feel free to do so. All right, good pick, uh, Nathan, uh, what I, what\'s your number two,
\n\n\n\nNathan: my number two really doesn\'t have a URL associated with it, but, um, it is the fact that we are still as a community.
\n\n\n\nHanging in there had a couple of years where yeah, but what, what I\'m meaning is, you know, this could literally have fallen to pieces over the last couple of years. You know, we relied a great deal on in-person events. We have gone through an awful lot and yet I see people all over the place. Making incredible commitments to making sure that we\'re still able to do things like this.
\n\n\n\nSo here we are. And David, thank you. There\'s six of us on the screen at the moment.
\n\n\n\nDavid Bisset: I\'m thinking don\'t thank me. I\'m just trying to get away from my family,
\n\n\n\nNathan: but I\'m thinking of events. One that Springs to mind, uh, is WordFest, uh, an event which is completely free to attend, um, has built a platform to make that event possible, um, loads and loads of people volunteering to, to be involved.
\n\n\n\nAnd so that really is, is on what I\'m talking about it\'s the sort of the maturation of the community, the maturation of online events, the fact that we\'ve managed to keep going, we\'re patting ourselves on the back. We, we were hoping for events to come around next year, going back to the vet\'s point from the first round.
\n\n\n\nMaybe that\'s not going to happen, but for reasons that I can\'t quite explain, we\'re still managing to hang in there and on the whole, we\'re not falling out with each other and. Mirror that across different industries and just see how that falls out. And my prediction is it won\'t be quite as rosy as our little community has been.
\n\n\n\nWinstina: Okay. And my press one, I think we\'re adapting to be more robust. So I think in the future, remembering that some people won\'t be able to travel. Some people aren\'t ever going to want a chapel that some people have changed and people have adapted deadlines and that\'s totally cool. And the spec in that going forward, maybe we rely too much on impassive, maybe relied too much on different things and finding these new kids so healthy and it sets us up for stronger and it makes us more global and it helps us.
\n\n\n\nBe more inclusive if we want to have longevity and we want the habits, it\'s part of that doing it. It\'s hard to do, right? Because they are easier. Wasn\'t easier getting on planes and doing things. It just felt easier because it was what we may be new. But yeah, it\'s super exciting to see how we can be more inclusive in different ways.
\n\n\n\nYvette: So many of our people, people of our community have relied on each other to get through these periods where, um, not everyone in your physical circles was. Comfy with zoom and, and all the tools that we use that we already use to connect. So we had, uh, I\'ve, I\'ve been part of a group that played, um, uh, Dungeons and dragons, sir, for a year, like every other, every two, three weeks.
\n\n\n\nJust to have that moment where you\'re not just among your family or on the phone with other family and friends and do something entirely different. And for me personally, I think for the other people in that group too, it made such a difference. Um, not falling out, like you say, Nathan, and, uh, even strengthening friendships.
\n\n\n\nNathan: Yeah. I think really, I was just trying to congratulate us as a whole on. You know, if anybody put on an event, if anybody contributed anything or committed anything, anybody showed up and gave 20 minutes here, there, and everywhere to make a thing happen that wouldn\'t have otherwise happened. Uh, all of these little paper cots add up to a great big injury, what a terrible analogy.
\n\n\n\nUm, you get the point. Yeah. But you get the point, you know, lots and lots of little things happening largely in, in many cases on, on song, on accounted for, you know, if it\'ll probably never be acknowledged and written about in blog posts or on podcasts, but people hanging in keeping the community together.
\n\n\n\nAnd I, for one totally rely on it now, you know, it\'s like it is an extended family and it means a lot to me. And I\'m glad that everybody\'s hanging on in there with me.
\n\n\n\nAmber Hinds: The zoom meet ups, I would tend to in the past, like two years, I\'ve attended all these WordPress meetup. Across the U S and Canada, like once I would never go to, and I\'ve gotten to hear other people talk that I would never normally hear speak.
\n\n\n\nUm, and I\'ve been able to speak at some that I would, you know, like you, you\'re not going to fly somewhere to speak out a WordPress meetup. Right. Uh, and, and I just feel like I\'ve actually strengthened some of my connections with people because of all of the four switch to digital that we maybe didn\'t have.
\n\n\n\nNo, it\'s a bummer local meetup. We\'re not doing the zoom stuff. Cause it feels too hard. But, uh, but there are definitely a lot that are, and I think that\'s, it\'s, it\'s been nice.
\n\n\n\nWinstina: I know, I would add that. I think it\'s, there\'s a personal choice there as well, which I think is really nice. So I\'ve probably done less meat-ups, but that\'s also a personal choice, which I think.
\n\n\n\nWe have that now. And we have the more options that people can do. And I guess that\'s kind of an, I am so grateful for all the people, giving all the options for those of us that maybe didn\'t have the bandwidth for different people have had to do different things during this time. And different people are going to do different things as a process during this time.
\n\n\n\nAnd this is a time which wasn\'t just the time that you experienced it, it\'s the time that you processed after it because we\'re all humans and you need to do that. Right. Um, so we\'re going to need to sit so that I even need to take the burden for the people that have the Baton and did all this sauce and stuff for me, you know, that\'s that\'s community by picking up something and taking it.
\n\n\n\nUm, and I knew I could stay connected with the community, but I could step back and I could do that because my community was there. Being informed by things that post status and other things. And I could do my creative thing, but that had that information that we didn\'t have a few years ago. We didn\'t have that kind of thing.
\n\n\n\nI didn\'t need to attend things. Um, so it\'s just been able to like turn the volume up or down as you need to still remain connected with the community, but still feel a sense of belonging and still having people check on you. It\'s beautiful. Plus one with the beauty and the heart and the group\'s hugs, but just the choice having career option choices and personal choices in how you do your path in this community is, is a huge part of this now.
\n\n\n\nDavid Bisset: All right. Speaking of love, let\'s give some love to you vet. Uh, what is your second round pick here? My second
\n\n\n\nYvette: one has to do with, uh, with the growth rate of WordPress, and the fact that that\'s actually slowing down and while we\'re so like humongous in the CMS space. Um, we\'re not growing as fast as we used to be.
\n\n\n\nNow, part of that has to do with the growth of e-commerce because COVID forced everyone to move to online, shopping, maybe a bit faster than they were comfortable with. Um, but it\'s also something that we do need to be aware of. And as some people already have been warning us for, for more than a year, we are losing terrain when it comes to organic traffic.
\n\n\n\nUm, for people\'s searching for things like starting a website, uh, starting a web shop. Um, and there is talk about this. Um, but I think it needs more.
\n\n\n\nDavid Bisset: There is going to be discussion more discussion. I think this year about what market share really means. I think we\'ve been looking at the percentage numbers and by the way, the, those percentage numbers are, might be going away.
\n\n\n\nWe might not have that statistic by mid-year because Alexa, not that Alexa, the other Alexa, Alexa, that\'s been twice. Yes. I know if I say it a third time, she comes through the window or the mirror. Um, but, but that, that, that, um, way of getting in that market share that 43% where it is right now. That\'s no longer going to be a source for w three texts, um, coming to, so I think going along with your point and again, feel free to link the provost appropriate news article to that, um, market share slowing down, but in overall, like what market share should we be paying attention to what statute we paying attention to?
\n\n\n\nAnd I think your pick fits perfectly along with that, you\'re fixated on one number. What happens regardless of how legitimate the number is, what happens when that. Stop slow us down. What does it do? I mean, if it, if it\'s, if it\'s my blood pressure, then that\'s great. But when it comes to WordPress market share maybe, maybe not so much.
\n\n\n\nRight.
\n\n\n\nYvette: I know among the WordPress marketing team, I mean, this is a team that has been growing with ups and downs and all sorts of twists and twirls. Um, but years ago we already asked for things like KPIs and growth and access to analytics, um, And we\'re really happy that we have some more sponsor contributors on our team now.
\n\n\n\nSo hopefully this will also spark that fire of where do we want to go? What do our target audiences look like? Um, how do we really convert them from hearing about word press when you\'re doing that first research about, um, getting a website up and running to how flexible is this and how am I going to get locked in with, with this or with closed source, et cetera.
\n\n\n\nThere\'s so I, one of my pet peeves is teaching this new selling, and that really, uh, is something that we could be better at, within the WordPress community. Um, like entry-level content for people that doing that first research winter building.
\n\n\n\nDavid Bisset: Absolutely. Wow. That was a great two rounds. I love the fact that we\'ve got so many different perspectives here.
\n\n\n\nSo what we\'re going to go through next for the next, maybe 10 minutes is like a, you\'re going to go through the rest of your picks that you brought with you. And if you may feel free to mention a snipe, just briefly mentioned the pic. Um, you don\'t have to go into detail. In fact, we don\'t have the time to go into details on them, but before.
\n\n\n\nSo I\'m going to give you a minute to kind of look over the rest of your list and decide what to share as we go through one last time. While I do that, though, I\'m going to play responses, things that the community has been sharing, but I just felt like we should share at least one, one is from Mr. Strebel.
\n\n\n\nStrebel: I think the biggest story of 2021 in WordPress was Jason St. Anne\'s full site editing post. That was a meat and potatoes deep dive into the current state of the editor, which as it continues to evolve will be the experience for tens and tens of millions of site.
\n\n\n\nUm,
\n\n\n\nI think that got my most, the most attention out of me.
\n\n\n\nAnd I\'m a little bias. Pepsi was mentioned.
\n\n\n\nDavid Bisset: Well, it, it\'s not a struggle video without a Pagely mention. So check that box, but I think I, I can\'t help, but think that\'s a good post to have when you\'re viewing, when you need some good absorption on the subject. So kudos to struggle for that. Let me share with you mats real quick here member Doris had said, well, it\'s Matt from our report media and the WP minute.com.
\n\n\n\nMatt Medeiros: I think the biggest story,
\n\n\n\nDavid Bisset: I just want to say, just look how you people are listening to this all linked to this and listen, listening just looks so professional. Usually has that jacket on that makes him look like he\'s recording from Antarctica. Like if you ever seen him like that, if not, I\'ll share it with you later, but I just wanted to say a map before we even hear you.
\n\n\n\nGreat professional job, sending us your, a video here. Here we go
\n\n\n\nMatt Medeiros: from airport media and the WP minute.com. I think the biggest story of 2021 are all of the new faces in the WordPress community. Showing up on my timeline. I\'m hearing them in podcasts. I\'m seeing them on YouTube and it\'s fantastic to see a whole new cohort of people supporting the community and bringing in fresh ideas and fresh perspectives.
\n\n\n\nSo I applaud everyone really stepping it up, uh, in WordPress as my number one news item for 2021. And Hey, by the way, David Short form community contributed content. This is a fantastic. Idea.
\n\n\n\nDavid Bisset: Okay. A compliment will not get past the point that you didn\'t give a specific news item mat. So, you know, minus one point for you.
\n\n\n\nBut I do will have to acknowledge that. Um, and this may be Tyson to Nathan\'s a bit, a little bit. We are, we\'re surviving together as a community and still taking in new people. We\'re seeing, we\'re definitely seeing new people present their voices. Here\'s one more from, um, Mr. Bob, Don here. Hey
\n\n\n\nBob Dunn: Bob, Do The Woo. So I think that\'s a big news. You\'re here. I\'m here. Yes, we it\'s almost the end of the year. We\'ll be here in 2022. So daycare B-cell man,ource. This is WordPress. I mean any open source community and the tool has its ups and downs. And Hey, I\'d say there\'s a lot more ups than downs and Hey… yeah, I\'ve talked to new people. I\'ve talked to people who\'ve been in space.I love seeing who is out there and who is doing with WordPress. So I think that\'s a big news. You\'re here. I\'m here. Yes, we it\'s almost the end of the year. We\'ll be here in 2022. So take care be well man.
\n\n\n\nDavid Bisset: I think, I think it\'s because it\'s just, you know, year two, a pandemic, everybody\'s kind of just thankful that we\'re all here together.
\n\n\n\nRight? We actually have two more videos. One from Michelle Fran yet,
\n\n\n\nMichelle Frechette: For me the biggest WordPress news story of this year was acquisitions, but it was specifically the acquisition of give WP into liquid web because it affected me personally. I was the director of customer success that give WP at the time and give WP joined the liquid web family and was under, became under the umbrella of our software.
\n\n\n\nWhich is stellar WP. I was the director of customer success, forgive, and I am the director of community engagement
\n\n\n\nfor stellar WP. I get to do lots of fun things with that, including the
\n\n\n\nwork that I do at post status, um, and being on the team, they\'re contributing in many ways
\n\n\n\nand, uh, what I do in big orange heart, et cetera.
\n\n\n\nSo that was pretty big news for me. And it opened up a whole new world of possibilities and allowed me to do many things like attending the state of the word. So, yeah, that\'s what I would say.
\n\n\n\nDavid Bisset: And we have a video here from Rob Carnes
\n\n\n\n\n\n\n\n\n\n\n\nRob Carnes: Everybody Rob Carnes here. I wanted to talk about what I thought was the most important word, press story the year.
\n\n\n\nAnd I think it will shock a lot of people, but it won\'t, and that\'s our community. Our community has had a really rough go with this year between Gutenberg, mergers and acquisitions. And the fractioning in our community to do the other issues, or do you usual wordpress.com versus where press.org and depending on who you talk to, the belief that automatic cause doing the right thing or wrong thing, I think we have a lot of work to do within our own community.
\n\n\n\nAnd I think this is the whole future of WordPress and there\'s the whole future of open source. And it\'s why it\'s the number one issue we face today. And that\'s the problems in our own community. And it seems the issue has never changed and nobody ever looks at the people causing the issues instead of realizing.
\n\n\n\nThat we need to keep building the community. And one of those reasons, and it\'s been hard to do without word camps in the pandemic is to keep building our online communities towards our door on Twitter, with Iran, Facebook, whether it\'s the new WordPress product community I\'m involved with in LinkedIn, we need to keep building those communities and we need to work really hard at it.
\n\n\n\nAnd that is the biggest story. And that\'s the future of WordPress. To some degree. I do agree that there is some disagreement in the WordPress community. I don\'t think it\'s something we haven\'t faced in the past, though. If you are interested in the WordPress community, there is an excellent episode, upcoming of post status excerpt, where I talked to Bob Dunn about the community.
\n\n\n\nDavid Bisset: I suggest you check out. Like I promised let\'s bring out quickly are the picks that we didn\'t get a chance to share. Nathan, since you have to step out real quick, let\'s take you first.
\n\n\n\nNathan: I want to mention, now this, this project may have been going for a little while, but I\'m just really impressed with a particular individual and a community that has grown up around a product that he\'s released.
\n\n\n\nAnd it\'s a page builder actually, and it\'s called bricks. I don\'t know if you\'ve come across this page builder in the past, but it seems to be gaining a lot of attention. You can find it at bricks, builder.io. I confess I have not really used it, but I\'ve kind of been looking in their group and I\'m just extraordinarily amazed at what this guy Thomas has been able to pull off seemingly.
\n\n\n\nAll by himself in the space of, well, I\'m going to say it\'s about 18 months, but really kind of came around the beginning portion of last year and, um, and in their community and in various other communities that there\'s always the contrast. There\'s always the people drawing the contrast between the, the, the pace of change on the WordPress Gutenberg side and the fact that people an individual in this case, or a small team in the case of other page builders can manage to pivot and iterate so very, very quickly.
\n\n\n\nAnd I just wanted to give a shout out to Thomas for all the work that he\'s doing. He\'s managed to gather himself a nice sizeable Facebook group of devoted followers. So just kudos to
\n\n\n\nDavid Bisset: him. Well, good. That\'s another thing I can look forward to exploring, cause I haven\'t had a chance to, to explore that yet.
\n\n\n\nAll right. Um, so Tammie, what\'s what, uh, real quick here, what is anything left in your truck? Yeah,
\n\n\n\nTammie Lister: I have two things. One is the release, uh, Alibaba from, uh, announced the release of eight either. I am O uh, theme. Um, I, it\'s an amazing theme, um, that lots of started blood-based themes and happening, but this one was really pivotal for me.
\n\n\n\nThis is kind of was in August. It was very all the way through, uh, it\'s got incredible paddle library and also commerce support. And I think that that is kind of essential kind of things. Approach is really one of that systematic approach to design and is a combination. So I think the work that is happening with her and her partner in the studio is really, really crucial for this space.
\n\n\n\nAnd the other one is, um, experimentations, I mean, excited about genuinely people experimenting. Um, and how did a. Kind of presentation about that for us. And then he posted that on his blog, his presentation, um, about how by experimenting, using existing features and pushing the boundaries of them. So he did it with block styles.
\n\n\n\nUh, we start to know the boundaries, but also what could become. So I think that that shows that, you know, um, we only get to know really where we\'re going to go as a project that starting to experiment. And we only get to know how to use these things by experimenting. So those are the two picks that no one picked.
\n\n\n\nSo I\'m kind of excited that no one picked my pigs.
\n\n\n\nDavid Bisset: That\'s that\'s a good thing. It shows you\'re you\'re you\'ve you been a worthy, worthy adversary? Um, Malcolm what\'s quickly. What\'s your anything?
\n\n\n\nMalcolm Perotti: Yeah. So I was interested in talking about the whole delicious sprains ACF thing, but that we kind of covered that.
\n\n\n\nUm, the other two things that I had was the GoDaddy plain text password issue. I think it kind of, you know, we have to really continue to think about security, not just in WordPress, but the partners that we use to, um, you know, manage and grow our sites. And then the other thing that I wanted to talk about was, uh, you know, on WP mainline, Jeff posted about his issue with trying to transform two paragraph blocks in an ordered list into a quote block.
\n\n\n\nUm, I think we need to continue to work on Gutenberg and those, those abilities that we had, um, before with the editor to be able to kind of have that publishing experience be just as good or better with the block editor. I think there\'s still these edge cases that are missing that support. So those, the only ones I had left
\n\n\n\nDavid Bisset: Jeff seems to hit a lot of those.
\n\n\n\nI think it\'d be, he needs to continue writing. Yeah, let\'s see. Um, Amber what\'s. Yeah.
\n\n\n\nAmber Hinds: So that was a great segway into classic editor support continues for at least a year block editor, Ben wagon pretty early. I mean, we did it from the beginning. We still have some clients, especially like universities or government, like things that really need a lot of control that are like, they are classic editor all the way, you know?
\n\n\n\nAnd so, so I think that\'s a big deal that that\'s continuing. And I know they said for a year, I\'m certain that we\'ll get another year extension next year. Um,
\n\n\n\nDavid Bisset: the other thing kind of like my taxes, but yes,
\n\n\n\nAmber Hinds: the other thing that kinda stood out for me this year was the weird Wix versus WordPress battle,
\n\n\n\nright.
\n\n\n\nWith sending everyone the headphones and Matt writing a pretty. Snarky dab, field blog posts at them. And you know, it\'s, it\'s weird. Cause it is, it is an interesting, like, okay, we are a competitor, right. Obviously massively competitor, but at the same time for me, I\'m a little bit like. Okay, this feels childish.
\n\n\n\nLet\'s all just move on. Like, what does this say about us? You know, so
\n\n\n\nDavid Bisset: I agree. And then Matt mentioned them at the state of the word and that kind of just fell apart
\n\n\n\nAmber Hinds: very intentionally. Right. And I, and I like some of them, I was just like, okay, come
\n\n\n\nDavid Bisset: on. No, but, but no, I forgot about that marketing campaign, the weirdest marketing campaign, guerrilla style.
\n\n\n\nAnd then you had the ads with the, with the weird people in the ads, or at least it was weird to me. So it\'s the headphones. It was the weird ad campaign. And then there was the public back and forth. So that\'s yeah. Let\'s yeah.
\n\n\n\nAmber Hinds: The footnote on that ad campaign too was it\'s it was a little bit interesting to see who Wix thought was a WordPress influencer.
\n\n\n\nThere were some people that were like, okay. Yes, of course it makes sense that they would, and then there were other people that were like weird. I got, I had friends from Wix and.
\n\n\n\nDavid Bisset: Some people got, and I bet you some people\'s feelings got hurt when they didn\'t get their headphones.
\n\n\n\nI\'m sorry. I had something in my phone, but okay. Yes. Great. Never forget a Wix 2021. Never forget. Um, that I think this is we\'re down to you now. Is there anything quickly you want to just touch base before we close out here?
\n\n\n\nYvette: Absolutely. I had some broad match, uh, topics on my list.
\n\n\n\nDavid Bisset: Keep it short, keep it short because I got eventually feed my kids.
\n\n\n\nOkay. Yeah,
\n\n\n\nYvette: I will totally do that. Uh, one was an article, uh, about an open source license that requires you to do no harm. And while that\'s probably not tying in with GPL, really just like that, I thought it brought up some philosophical things about good versus bad and inclusive versus protecting your community from.
\n\n\n\nEagles influences evil being a little bit too strong of a word, but you\'re probably get the
\n\n\n\nDavid Bisset: Evil spirits.
\n\n\n\nYvette: Um, yeah, so I thought I was really interesting and maybe something for conversations down the road, what do we want, what do we not want within our community? Then there was an article about how people who could not attend group therapy physically really turned to open, uh, to, to online, uh, platforms.
\n\n\n\nAnd that made me feel really thankful for the fact that we basically have her own mental health blood from inner community where people can connect with people that they\'re already have some things in common with, which makes building those friendships and helping each other out really, really, um, so much easier.
\n\n\n\nUh, and there\'s one really not news, but a thread on Twitter that just really worked my heart. And it was Michelle Frechette offering people in anyone basically who tied in to that or asked for it, uh, To create, um, haikus or limericks or a compliment for them. And I think that was just, well, it was really hard to.
\n\n\n\nDavid Bisset: Wow. That\'s yeah, let\'s not forget too much quote, the technical stuff, but yeah, let\'s not forget to the, uh, the heartwarming stuff too. I wanted to share one last one. Last thing, I think it was from Joe. Hey everybody, Joe. Casabona here from the, how I built it. Podcasts and WP review. And I think the biggest story in WordPress in 2021 was the delay of the release of WordPress 5.9, I think since 5.0, we\'ve seen, uh, seemingly arbitrary deadlines get pushed.
\n\n\n\nEven when features haven\'t been fully ready. We\'ve seen features get put into release candidates, even though there should be a feature freeze then. And I feel like 5.9 is a turning point where we don\'t push out the release until the core features. The main headline features are ready, and that is good for the development team.
\n\n\n\nAnd it\'s good for the end user, which is ultimately. We\'ve had some things before in previous releases that maybe weren\'t ready or were pushed or something. And we have this thing about deadlines, but, uh, I\'m not sure if this is sends a huge trend because I, because I know that there\'s four releases may be being planned next year.
\n\n\n\nYou know, we\'re squeezing them in like little sausages, but I\'m sure everything will work out fine. I\'m sure everything is, but this does give you an example of saying, Hey, listen, something wasn\'t ready. And I realized there was a big, we, I have a episode with Anne McCarthy on this. Like everything was spaghetti, like everything was tied to everything else.
\n\n\n\nSo you couldn\'t really, it was very, very difficult to push just a part of the release out. Um, think I\'m going to summarize, I think that\'s a decent way of summarizing that. So I think it was a great idea not to wait and pushing out at the end of January, but it does give you at least some precedent to say, Hey, listen, we pay attention to these things.
\n\n\n\nAnd if something needs to be moved, it\'s moved. So that kind of gives you hope for the future.
\n\n\n\nWinstina: Uh, so it\'s a Bita inevitably. So it\'s a difference for two reasons.
\n\n\n\nDavid Bisset: I wanted to thank everybody here for participating in this. I thought this was a great, um, great diversity. I think we only repeated like maybe one or two news posts from the previous episode, which shows you like how much there happened in 2021, but also a lot of things that I don\'t think I even gave that much consideration to.
\n\n\n\nAnd I think when people listen to this podcast, I think they\'re going to be able to appreciate the same things I did so quickly around the table. Let\'s just say farewell and just remind us where we can find you on social it start with Tammie.
\n\n\n\nTammie Lister: Uh, you can find me in common ties and own things and thank you so much.
\n\n\n\nAnd I hope everyone has just a calm and the year that they really need.
\n\n\n\nDavid Bisset: Yes. Yes. I think my coffee\'s kicking in now. So I think, I think I got all that in Malcolm. Um, share with us where we can find you.
\n\n\n\nMalcolm Perotti: Uh, the best place to find me is on Twitter, uh, at find purpose and, uh, always check me out on the WP mainline podcasts at WP mainline.
\n\n\n\nDavid Bisset: And thanks for coming Malcolm. I greatly appreciate it. And don\'t forget to rub it in to a Jeff Amber. Thank you for coming. You\'ve been a real joy.
\n\n\n\nAmber Hinds: Oh, thank you for having me. So the best social media for me is on Twitter and I really got to update my handle, but it\'s, uh, at a core blog, which is a U C O E U R blog.
\n\n\n\nAnd otherwise, if it\'s easier, you can just go to equalize digital.com and get to me that way.
\n\n\n\nDavid Bisset: And I\'m most of you are probably on post status as well. I think, um, at least if, if not shame on you, Nathan, where can we find.
\n\n\n\nOh, Nathan and Nathan, I think you\'re muted. Otherwise you\'re there you go.
\n\n\n\nNathan: Sorry. Enormous. PhotoPass sorry about that. WP belts.com or on Twitter. It\'s just WP builds
\n\n\n\nDavid Bisset: and thank you for coming, Nathan. I greatly appreciate it. You probably didn\'t know what you were getting into. And I think this is the first time you and I have talked.
\n\n\n\nAnd for all I know,
\n\n\n\nNathan: it\'s very nice to meet you all
\n\n\n\nDavid Bisset: It could be the last too for if I didn\'t do my job right. Um, and finally, Yvette, it was nice to see your face. And I think this is the first time we\'ve met as well. Can you tell people where to find you?
\n\n\n\nYvette: Yes. Thank you. You\'ll find me at, uh, with, uh, at, if had some failed, um, on Twitter, Facebook, LinkedIn, um, WordPress slack, and I\'ll, I am on post status.
\n\n\n\nDavid Bisset: Okay. Great. That\'s awesome. Um, why am I whispering? Thank you Yvette. Very much for that. I greatly appreciate it. I, and I appreciate everyone here. This was meant for the European time zone, but some of you were awesome. You woke up in the morning on an Eastern time zone. Thank you very much for all. And, um, we\'ll talk in the future and, um, we\'ll see this episode soon on post status.
\n\n\n\nGoodbye, everybody.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 19 Jan 2022 04:15:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Olivia Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:77:\"WPTavern: Ask the Bartender: Are There Any Compact and Personal Block Themes?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128512\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:195:\"https://wptavern.com/ask-the-bartender-are-there-any-compact-and-personal-block-themes?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-are-there-any-compact-and-personal-block-themes\";s: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:5300:\"\n\n\n\nAll the block themes seem to have something similar in how they look. Although unique in their own ways, being generally wide, spacy, and modular instantly make them look like they came from the same mold. This is not to say they’re bad though… I’m just not really fond of such design. I prefer something more compact and personal.
By “compact and personal,” I think of something like a small room cramped with all your belongings, photos, postcards, etc., giving it a cozy feeling (Tumblr themes kind of fit this). The block themes I’ve seen are all just so airy and professional-looking that using them is like taking cautious first steps in a big fancy office, where you’re afraid of making too much sound.
What do you think of this design trend in block themes? And do you happen to know of any “compact and personal”-looking block themes?
Isabel
I love that description of the type of theme you are looking for. It reminds me of my college years where my roommates and I had our own cramped bedrooms. I would always decorate my walls with drawings and other things I had created. I piled my favorite books on the shelves of an old TV entertainment unit that my grandpa had built. Across the top, I lined trinkets and other keepsakes from adventures I had been on.
\n\n\n\nIt was my own little paradise, my world in about 120 square feet. If you walked into that room, it would not take long for you to get to know the person behind it.
\n\n\n\nThat is what I love about personal websites. They can be like college dorm rooms, giving us a glimpse into the unique personalities behind them.
\n\n\n\nFar too often, it feels like WordPress themers have moved away from the core audience that played at least some part in the platform’s initial popularity. Today, everything seems to be catered to business, eCommerce, portfolios, and minimalist blogging.
\n\n\n\nTo answer your first question, I am a fan of open-canvas designs. The space gives me room to focus on my content.
\n\n\n\nHowever, like you, I am not seeing enough variety. This is not necessarily specific to block themes. You will find similar trends for classic WordPress.
\n\n\n\nWith that said, the block system does play a part in what designers are creating. We are still in the infancy of block themes. Technically, they are not supported by WordPress yet. However, they will be when version 5.9 launches next week. Many designers will be timid at first, not really pushing the boundaries of what is possible. It is similar to taking that first step in a pool’s shallow end. You are acquainting yourself with the water, getting a feel for the temp, before you wade farther in.
\n\n\n\nI expect that we will see more variety over the coming months as more theme authors begin learning the new system. I hope that includes more designs like what you are asking for.
\n\n\n\nWhen I first read your question, a Carrd site that I have had bookmarked for a while immediately came to mind. I came across it when venturing down the rabbit hole of anime-related fan sites around the web. The design does not fit my personal brand, but I have been fascinated by it for months.
\n\n\n\nThe site screams personal and cozy. It reminds me of some of my early days on the web when every other blog I visited seemed to have its own brand of quirkiness. You can still find a lot of that if you really dive into the various brands of fandom that are out there.
\n\n\n\nEvery now and then, I come back to this site for design inspiration. I envision building something like this on top of WordPress. The community is sorely missing out on the fun side of the web.
\n\n\n\nMany Carrd sites like the one shown above have a bit of this, but they are not full-blown websites. They are essentially personal landing pages.
\n\n\n\nTumblr is the king when it comes to themes with personality. Where else can I possibly consider switching over to a design dedicated to Taylor Swift?
\n\n\n\nYou will be hard-pressed to find anything like that in the WordPress theme directory.
\n\n\n\nRight now, I only know of one block theme that fits into the compact-and-cozy category, and that is Kubrick2. I covered it in detail last month in a review. It is now live on WordPress.org.
\n\n\n\nKubrick was one of the early default WordPress themes, and Kubrick2 is a recreation of it using blocks. It has that compact layout that seems to fit the description you provided. But, the design is a bit outdated.
\n\n\n\nFortunately, it is customizable via the site editor. It is also one of the least complex block themes out there. In mere minutes, you could modify its design with little effort.
\n\n\n\nUntil we see more themes, Kubrick2 is likely your best option.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 19 Jan 2022 00:52: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: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: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:37:\"WordPress.org blog: WordPress 5.9 RC3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=12050\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2022/01/wordpress-5-9-rc3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4710:\"The third Release Candidate (RC3) for WordPress 5.9 is here!
\n\n\n\nThank you to everyone who has contributed thus far toward testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated to land in just one week—on January 25, 2022. You still have time to help! Since RC2 arrived last week, testers have found and fixed two bugs, 14 fixes from Gutenberg. There has been one additional Gutenberg fix today.
\n\n\n\nYou can test the WordPress 5.9 release candidate in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nwp core update --version=5.9-RC3wp core update --version=5.9-RC3 --forceYour help to test the third Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users, developers, and the WordPress community.
\n\n\n\nThank you to all contributors who tested the RC2 release and gave feedback. Testing for bugs is a critical part of polishing every release and is a great way to contribute to WordPress.
\n\n\n\nHelp test WordPress 5.9 features – this post provides a guide to set up your testing environment, a list of testable features, and information about how to submit feedback you find as you go.
\n\n\n\nSkilled in languages other than English? Help translate WordPress into more than 100 languages! Thanks to every locale that is working on translations.
\n\n\n\nDevelopers and those interested in more background to the features can find more in the Field Guide. You can also follow the 5.9 development cycle and timeline.
\n\n\n\nIf you have found a bug, you can post the details to the Alpha/Beta area in the support forums.
\n\n\n\nIf you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.
\n\n\n\nFor their help in compiling this post, props to @cbringmann, @webcommsat, @psykro,@marybaum, @chanthaboune, @davidbaumwald, and @hellofromtonya.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 Jan 2022 22:28: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: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: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:81:\"WPTavern: WooCommerce Aims to Produce MVP of Custom Tables for Orders by Q3, 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128435\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:205:\"https://wptavern.com/woocommerce-aims-to-produce-mvp-of-custom-tables-for-orders-by-q3-2022?utm_source=rss&utm_medium=rss&utm_campaign=woocommerce-aims-to-produce-mvp-of-custom-tables-for-orders-by-q3-2022\";s: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:2611:\"The WooCommerce development team announced today that they have started working on an implementation of custom tables for orders, a long-awaited improvement that promises significant performance gains for stores.
\n\n\n\nAdding custom tables for orders is a complex undertaking that will impact the entire ecosystem, so the team is soliciting feedback from the developer community as they proceed with the project.
\n\n\n\nWhen working with WooCommerce data, developers have been encouraged to use CRUD objects since they were introduced in version 3.0, as an alternative to directly updating metadata or using WordPress post objects.
\n\n\n\n“We still utilize wp_post and wp_postmeta table structures to store this information for WooCommerce stores even with the CRUD layer,” WooCommerce core developer Vedanshu Jain said.
“While these WordPress-provided APIs and tables have served us well over the years, we now want to take a step further with a rock-solid and easy-to-understand database structure that is intentionally designed for commerce needs.”
\n\n\n\nWooCommerce core developers have three primary objectives for introducing custom order tables – to improve scalability, simplicity, and reliability. They anticipate it will lessen the need for merchants to seek developer support when scaling their stores. Having orders in custom tables should also allow WooCommerce developers to extend core more easily, as well as create and restore data backups.
\n\n\n\nThe WooCommerce development team is tracking the project on GitHub and is aiming to have an initial implementation ready by early Q3 2022. They have published the first draft of the database schema they are proposing for building out the custom tables and feedback is welcome on the post.
\n\n\n\n“For this project, we expect that some work may be required by extensions and custom code developers to take full benefit of the new table structure,” Vedanshu Jain said. “As we go further along in the implementation, we plan to publish upgrade guides to support the adoption of custom order tables.
\n\n\n\n“During the rollout, we aim to keep this feature strictly opt-in in the beginning, giving everyone enough time to make their shops compatible.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 Jan 2022 03:23:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:78:\"WPTavern: Nick Diego Forks Core WordPress Block, Creates Social Sharing 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=128423\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:199:\"https://wptavern.com/nick-diego-forks-core-wordpress-block-creates-social-sharing-plugin?utm_source=rss&utm_medium=rss&utm_campaign=nick-diego-forks-core-wordpress-block-creates-social-sharing-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:4644:\"Raise your hand if you have seen this before. Yet another social sharing plugin. But, with the block system, all things are new again. Some things simply need to be ported over from their former PHP-based equivalents. Others are fresh takes on old ideas, and a few may set the standard for years to come.
\n\n\n\nNick Diego forked the core Social Icons block to create Social Sharing Block. Everything about it looks and feels like it is supposed to be in WordPress, so much so that he thinks it could be a candidate for inclusion.
\n\n\n\n“I tried to replicate the Gutenberg file structure as much as possible,” he said. “It’s close, but they are doing some webpack wizardry. I would love to see this ultimately get included in the core in some form, but may be too niche. I am going to put together a draft PR at some point though after 5.9 is out and I am sure the plugin is 100% solid.”
\n\n\n\nWhile it may not ever land in WordPress, it will likely be a go-to solution as more and more users begin to use block themes. Currently, the plugin requires either WordPress 5.9 or the latest version of Gutenberg. It uses some newer components, but it does not make sense to make it backward compatible with earlier versions anyway. The block works best when coupled with the site editor, which requires a block theme.
\n\n\n\nThe plugin deviates from the core block in one necessary way. Instead of users typing in the URL to their social profiles, the Social Sharing block automatically outputs the proper “sharer” URL for whichever service is selected.
\n\n\n\nIt even handles email and print links. Outside of that, it currently supports 10 social networks:
\n\n\n\nDiego said via Twitter that he plans to support more services in future iterations.
\n\n\n\nSocial Sharing Block is a prime example of the promise of the block system. In classic WordPress, users were limited to whatever design the developer made possible. Often, plugins would output sharing links automatically, and users would need to configure options via a settings page entirely detached from what it would look like on the front end.
\n\n\n\nWith this block, users have flexibility. They have control over every aspect of how their social sharing links are output, at least within the limits of the site editor. Everything from the label to the colors to the preceding “share this” text is at their fingertips.
\n\n\n\nThis is also one of the reasons I am already a fan of this young plugin. It does not try to do too much. It does not concern itself with design aspects outside of the social sharing list that it outputs.
\n\n\n\nIt is a simple thing. However, it represents the control that users have rarely seen. For example, I wanted to add the text “Share Via” before the social share buttons. This is not configurable via the block itself. Instead, I get to decide its layout through the site editor.
\n\n\n\n\nI hopped over to the site editor and opened the single post template to build that layout. I scrolled down to the post meta area and inserted a Row block. From that point, it was a matter of adding my custom text via a paragraph before inserting the social sharing links.
\n\n\n\nAs I said, it is such a simple thing. However, the control over how this appears on the front end cannot be understated.
\n\n\n\nNot all third-party blocks are built like this. Far too often, they try to control the entire experience, creating what should be patterns instead. When developers treat blocks as self-contained components that do one thing well, it adds flexibility for users.
\n\n\n\nIt also helps theme authors when deciding which plugins to support. It would be a no-brainer for themers to build custom patterns and block styles around Social Sharing Block.
\n\n\n\nIt also has one extra option that the WordPress Social Icons block does not. Users can enable the text label alongside each icon. During our conversation, I hinted that this was something sorely needed for core’s Social Icons block and that there was already an open ticket for it. Diego seems interested in creating a patch to address it.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 Jan 2022 00:33:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:64:\"WordCamp Central: WP Y’all has been Postponed until the Spring\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=3144092\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://central.wordcamp.org/news/2022/01/17/wp-yall-has-been-postponed-until-the-spring/\";s: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:323:\"The WordCamp Birmingham Organizing Team has unanimously decided to postpone WP Y’all until a future date in April or May when we can safely hold the event for our attendees.
\nSee our full announcement on our site.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 17 Jan 2022 12:35:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Ryan Marks\";s: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:90:\"WordPress.org blog: WP Briefing: Episode 23: A letter from WordPress’ Executive Director\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=12043\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://wordpress.org/news/2022/01/episode-23-a-letter-from-wordpress-executive-director/\";s: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:6739:\"As we greet a new year, WordPress’ Executive Director writes a letter to the project and community that speaks to the hopes of the year ahead.
\n\n\n\nHave a question you’d like answered? You can submit them to wpbriefing@wordpress.org, either written or as a voice recording.
\n\n\n\nJosepha Haden Chomphosy 00:10
\n\n\n\nHello, 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 insight into the community that supports it, and get a small list of big things coming up in the next two weeks. I’m your host, Josepha Haden Chomphosy. Here we go!
\n\n\n\nJosepha Haden Chomphosy 00:40
\n\n\n\nYesterday marked three years since the WordPress project welcomed me as their executive director. As I start my fourth year, I’ve spent a bit of time considering what the next five years will bring us. WordPress will turn 19 this year, which means that we will soon be a whopping 20 years old; for some of the people who have been with the project since the beginning, that can represent two-thirds of their whole life. And even if you were not that young when you got here, two decades as an open source project is really a cause for celebration.
\n\n\n\nJosepha Haden Chomphosy 01:10
\n\n\n\nI am not in that group that has been here forever. I showed up for the first time in 2009, as a community organizer, self-sponsored, and I learned so much about myself as a person and as a leader while I was doing that. So when I arrived as a sponsored contributor in 2015, I already knew exactly what made this work so fulfilling for me was these three things:
\n\n\n\nJosepha Haden Chomphosy 01:34
\n\n\n\nFirst, the ability to lend a hand in those moments where I wish someone had lent a hand.
\n\n\n\nJosepha Haden Chomphosy 01:40
\n\n\n\nSecond is the delight of seeing people’s first successes and the joy of watching them grow over time.
\n\n\n\nJosepha Haden Chomphosy 01:48
\n\n\n\nAnd the third was a chance to be part of something great, which turned out to be something greater; greater than me or you or a CMS.
\n\n\n\nJosepha Haden Chomphosy 01:58
\n\n\n\nThis list is still at the heart of what I feel I get out of the WordPress project. But it has also grown substantially in my seven years as a sponsored contributor. I now also love how we as a community of contributors get to foster a better way to lead and a better way to collaborate. And through those things help people find a way to have a better life. Not just through WordPress, the CMS, but through WordPress, the people, and WordPress, the project.
\n\n\n\nJosepha Haden Chomphosy 02:25
\n\n\n\nAnd so when I think of what I want for WordPress in its 19th year, so that we can head with confidence and dignity into our 20th year, it is this:
\n\n\n\nJosepha Haden Chomphosy 02:35
\n\n\n\nI want you to remember that you are not alone here. People come together in the world often because of a shared location. But WordPress fosters this beautiful experience of bringing us together because of what we care about. Whether you care about PHP standards, diversity in technology, helping people with their first big wins, making WordPress more secure. I mean, if what you care about is being able to write the most arcane and complex apps on top of WordPress that the world has ever seen. Then there are others out there who want to do that with you, too. We have so many things to connect about. And fortunately, we support a great piece of software for getting our thoughts out in the world. Take some time to see who else shares your thoughts and potentially learn a bit about the view from the other side.
\n\n\n\nJosepha Haden Chomphosy 03:26
\n\n\n\nAnd speaking of the other side, I also want us to approach our discussions as the US versus the Problem TM. WordPress may be 20 years old, and we may stand on the shoulders of giants, but right now, the people who are here you, you are explorers and creators and guides toward the best possible future for WordPress. The tension that we witness between teams is always about the best possible answers for the people who use our software. It is about securing the freedoms of the open web for everyone who comes after us whether they know they need those freedoms or not.
\n\n\n\nJosepha Haden Chomphosy 04:04
\n\n\n\nAnd finally, I want us to expand our reasons for doing this at all. If you are a member of the community of contributors, We frequently talk about how we give back because WordPress gave to us. Or if you are part of a Five for the Future group. You have heard that companies who have experienced success because of WordPress should commit 5% of their resources back to the project to ensure WordPress’ long-term success. But the reason that I keep doing this, and hopefully a new reason for you to keep doing this is that we can take part in securing opportunities for future users of WordPress.
\n\n\n\nJosepha Haden Chomphosy 04:42
\n\n\n\nYes, I want WordPress to be the best CMS. Yes, I want this community to be vibrant and engaged. Yes, I want WordPress to be a shining beacon of how to work remotely. And I want all of that because I know it is our careful and tireless stewardship of this project that lets us continue to lend a hand in those moments where people wish for someone to lend a hand.
\n\n\n\nJosepha Haden Chomphosy 05:11
\n\n\n\nThose are my hopes for WordPress in 2022 to move us forward into WordPress of the future. I hope you all will come with me and we can continue our journey together.
\n\n\n\nJosepha Haden Chomphosy 05:23
\n\n\n\nThanks again for listening. I’m Josepha Haden and this is the WP Briefing. See you again in a couple of weeks.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 17 Jan 2022 12: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: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: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:100:\"Gutenberg Times: Level Up with Query Block, FSE for Classic Themes and more – Weekend edition #199\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=19873\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:135:\"https://gutenbergtimes.com/level-up-with-query-block-fse-for-classic-themes-and-the-customizer-isnt-going-anywhere-weekend-edition-199/\";s: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:20519:\"Howdy,
\n\n\n\nYes, I am so happy to be back in Florida, and I enjoy the warmth of the sun, and the palm trees. ☀️ ⛱️ 🌴. Earlier this week, I was sitting outside chatting with my girlfriendsin Naples, FL, squinting into the setting sun. After sunset all we needed was a normal sweater to keep us comfortable as opposed to the 15 pounds of clothes, I had to put on in Whistler to spend five minutes outside.
\n\n\n\nAlas, the break is over. It’s down to the wire. We are a little over a week away from the WordPress 5.9 release on January 25th, 2022. If you haven’t caught up with all the new features, the Field Guide is now available on WordPress.org. Last week, I also published a reading list on block themes and full site editing for End-users, site builders and theme developers/designers.
\n\n\n\nThe training team around Learn.WordPress released a ton of additional Social Learning events, that should make it easier for users to learn more about the Site editor, the Theme Blocks and the Styles interface. You’ll find the list of 12 upcoming event at the end of the newsletter. Big Thank you to Destiny Fox Kanno, for researching and compiling the list!
\n\n\n\nWith that I leave you to the rest of the news around the Block editor.
\n\n\n\nYours, 💕
Birgit
PS: Join us on Monday night at the virtual WordPress Meetup Boulder event about What’s new in WordPress 5.9 and a panel discussion with Brian Garnder, Courtney Robertson and yours truly.
\n\n\n\n\nTable of Contents
\n\n\n\nThe founders of WPExperts.io, Saad Iqbal and Ahmed Salah, put on their magic hats and explained in their post “How Gutenberg will revolutionize the WordPress industry in 2022“.
\n\n\n\nAnne McCarthy joined DocPop and Nick Diego on the Torque Social Hour. They discussed WordPress 5.9 delay of the release, about accessibility, locking Blocks and also how the customizer is to work for with block themes or not.
\n\n\n\nOn the WPTavern, Justin Tadlock gave an overview of What Are Block Themes? What You Need To Know Before WordPress 5.9 for those WordPress users, who only heard recently about Block Themes and Full site editing. It’s a great post to share with your clients, and users, that are just now getting interested in the WordPress 5.9 features.
\n\n\n\n\n “Keeping up with Gutenberg – Index 2022”
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. The index 2020 is here
Justin Tadlock at WPTavern reviewed Automattic’s Livro Is a Minimal Block Theme for Writers. Is a minmalistic block theme. It also is a bit opinionated on certain features and designs, but nothing that wasn’t possible to fix within the new site editor.
\n\n\n\nJamie Marsland was a guest at the latest Do The Woo Podcast and discussed with Anne Maria Radu and Bob Dunn BobWP Woo Product Pages wtih Blocks and Full Site Editing customizations
\n\n\n\nAlso, in Customizer Will Disappear for Some Block Theme Users With WordPress 5.9, Tadlock outlines how the Customizer is not going to go away.
Only when you activate a Block Theme. And only if you don’t have plugins installed that tap into the Customizer for additional feature settings. If you don’t change your theme, all your customization will stay in place and you won’t loose any Custom CSS code.
The first FSE course is live on Lean.WordPress.org: Simple Site Design with Full Site Editing. “This course will review the interconnected features that make up full site editing (FSE) and how they are going to help you create beautiful site designs without needing to use any code.” Check it out!
\n\n\n\nIn her post What to expect in WordPress 5.9 from Gutenberg, Tammie Lister gives you a high-level overview of the features that make up Full Site Editing and will arrive at a WordPress instance near you, provided you activate a Block Theme.
\n\n\n\nIn this video WooCommerce and Full Site Editing Jamie Marsland gives you a first look at what the team at PootlePress has been working on for the past two months. You get a sneak peak of the Single Product template that comes with the WooCommerce Blocks plugin.
\n\n\n\nExtendify launched a new pattern library plugin by the same name. It’s theme agnostic and includes a “library of reusable website patterns and full page layouts can be assembled to rapidly build beautiful websites.” You can read a longer review on the WPTavern site
\n\n\n\nClaire Brotherton published post Gutentor: A Popular and Powerful WordPress Page Builder Plugin. She reviewed building full page layouts with this plugin for various purposes and explains their screens. You can try the plugin yourself for free and install it directly from the WordPress plugins repository.
\n\n\n\nBetween the holidays, Anne McCarthy expanded her Connecting the Dot YouTube Series with the video Level up with Query Loop block. This video focuses on how using the Query Loop block can both help you level up your content and streamline your workflows, depending on what you’re trying to accomplish. “In this case, I recreated a page from a site I run letslifechat.com/lifechat-starters/ and showed off some of the neat things you can do to customize what I created further. ” McCarthy wrote.
\n\n\n\nJustin Tadlock reviewed in his post Creating Speech Balloons With the WordPress Block Editor the Liquid Speech Balloon plugin available in the WordPress repository. Its feature help you create conversations or quotes mimicking the text message interfaces. It’s a neat little add-in to the block editor. Tadlock offers a lot of detail and use cases. Check out his review
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s main (trunk) branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
The recording of the first session Creating a block-based theme with Daisy Olsen and Ryan Welcher is now up on YouTube.
\n\n\n\nTopics covered:
\n\n\n\nBookmark the playlist, session 2 and 3 follow.
\n\n\n\nDave Smith gave a technical overview for the new Navigation block, that will be released with WordPress 5.9. Specifically he covered how the block saves its data and how decoupling this from the block’s presentation helps to make the block more powerful. You’ll find full details in the DevNote, also composed by Dave Smith.
\n\n\n\nCarolina Nymark updated her post on how to add full site editing features to classic themes with the latest information and tools. “The only two features not available to classic themes are the site editor and the global styles interface. You can add template editing to the theme and keep widgets and the customizer.” she wrote.
\n\n\n\nFabian Kägy, developer with 10up, core contributor and friend of the Gutenberg Times, published a proposal on GitHub Discussions Proposal for opening the editor interface to more extensibility and asked for our input ideas and insights. Kägy list examples for suitable extensions, like allowing Posts without titles, allowing for semantic settings next to core settings or greater controls for the placement of panels in the sidebar of the editor. I learned quite a bit from Riad Benguella’s comment, especially about the fact that any extensibility feature built now also has to promised backwards compatibility for the future and that might hold the current development and explorations of the editor back.
\n\n\n\nIf you are a plugin developer, it would be great if you could chime in on the GitHub discussion especially if you haven’t found a way to tap into the code base of the block editor as you used to with the Classic Editor.
\n\n\n\nJason Bahl walks you through the latest update of his work on supporting Gutenberg Blocks in WPGraphQL and demos in his video the Query on post and block data. The code for the new WPGraphQL Block Editor integration can be found on GitHub. As Bahl mentiones in his video, this integration is in very early stages but he will explore some more to support Gutenberg blocks for Headless WordPress.
\n\n\n\nA long-standing request for an API that allows for locking blocks and patterns is now coming to WordPress 5.9. Read more from Sarah Gooding in here post WordPress 5.9 to Introduce New API for Locking Blocks with links to DevNote and documentation.
\n\n\n\nIn the post React For WordPress Developers, Lax Mariappan recounts his story learning ReactJS, the Why of the investment of time and about the resources that are available.
\n\n\n\nJanuary 17, 2022 3 pm ET / 20:00 UTC
Advanced Layouts with the Block Editor with Wes Theron via WordPress Social Learning Spaces
January 17, 2022 8 pm ET / 1:00 UTC
What’s coming in WordPress 5.9 Panel discussion with Brian Gardner, Courtney Robertson, and Birgit Pauli-Haack via WordPress Meetup Boulder, Co
January 19, 2022 3:00 PM ET / 20:00 UTC
Zero to Block Theme Series #2: theme.json with Daisy Olsen and Sarah Snow via WordPress Social Learning Spaces
January 20, 2022 – 7 pm ET / 00:00 UTC
WordPress “Mega Meetup”: Block Patterns, WordPress 5.9
South Florida WordPress Meetup Group
January 21, 2022 – 7 pm ET / 00:00 UTC
Breaking it Down: Blocks, Patterns, And Templates with Roxy Kohilakis via WordPress Social Learning Spaces
January 23, 2022 – 4 pm ET / 21:00 UTC
WordPress: the Next Generation with Sallie Goetsch via The East Bay WordPress Meetup Group
January 24, 2022, 6 pm ET / 23:00 UTC
What Will WordPress 5.9 Mean for You? with Ray and Peter Ingersoll via WordPress Hartford, CT
January 26, 2022, 6 pm ET / 23:00 UTC
Intro to Templates and Template Parts (Full Site Editing) with Wes Theron via WordPress Social Learning Spaces
January 28, 2022, 3 pm ET / 20:00 UTC
Demo: Build Your Homepage Using Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
February 4, 2022, 3 pm ET / 20:00 UTC
Beginner’s Guide to Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
February 11, 2022 – 3 pm ET / 20:00 UTC
Breaking it Down: Blocks, Patterns, And Templates with Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
February 14, 2022 – 4 pm ET / 21:00 UTC
Exploring Theme Blocks with Wes Thoren via WordPress Social Learning Spaces
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nWordCamp Birmingham’s organizers announced today that the in-person event planned for the first week in February is now postponed until April or May. Organizers had been planning the event since August 2021 and had just announced the last group of speakers a week ago.
\n\n\n\n“In the last 30 days, our local COVID-19 numbers have risen dramatically as a result of the highly-transmissible Omicron variant,” lead organizer Ryan Marks said in the announcement.
\n\n\n\n“The WordPress community is bigger than any single WordCamp. We cannot in good conscience continue forward with our event, given the current risk, since this decision could negatively impact other in-person WordCamps currently in the planning stages.”
\n\n\n\nMarks said all attendees will be automatically refunded within the next few days. WordPress Community Support administrator Angela Jin has prepared an official letter for those who need proof of cancellation for getting travel refunded.
\n\n\n\nWordCamp Birmingham organizers are looking at dates in April or May, 2022, but said that rescheduling will depend on local infection rates and venue availability. Their contract with the Sidewalk Film Center + Cinema allowed organizers to cancel without any loss of deposit as long as they gave more than seven days notice.
\n\n\n\nThe event’s COVID-19 safety protocols, which were written before Omicron was spreading in the area, came under greater scrutiny a week ago. Shortly thereafter, organizers updated the guidelines to have a more rigid masking requirement, but some attendees and sponsors had already decided not to attend due to current conditions.
\n\n\n\n\n\n\n\nWhile WordCamp Birmingham organizers worked to update the COVID-19 safety protocols, more concerned community members condemned the gathering as “irresponsible” at a time when hospitals have been pushed to the brink.
\n\n\n\nOrganizers continued to monitor the situation, hoping for the opportunity to hold a safe event. After assessing the timing of the event and the level of community spread, they unanimously decided to that it was necessary to postpone. They had also reached the point where some of their payments would have been nonrefundable and needed to act in stewardship of their funds.
\n\n\n\n“We knew that being the first in-person US WordCamp was both a risk and a responsibility,” lead organizer Ryan Marks said. “If we could do it safely, other WordCamps in the US could do the same. If lots of people got sick, we’d set back US WordCamps such as Montclair, NJ, and Buffalo, NY, and possibly the global program as a whole from moving toward having safe in-person WordCamps.
\n\n\n\n“We saw news reports and estimates indicating Omicron cases would be peaking right as we were hosting WordCamp. That was sufficient for our organizing team to make the call to postpone. Pushing the event a couple months could mean a much safer event for everyone.”
\n\n\n\nAlabama has the second lowest percentage of vaccinated residents in the US, with just 48.1% fully vaccinated. The state currently has an average positive test rate of 37.4%. More than 25% of Alabama students have shifted to remote learning as more school systems have had to close due to record-breaking COVID rates.
\n\n\n\n“Our problem is we just don’t have enough adults to safely and effectively operate the school…in some cases, now we’re seeing up to 35% of the faculty report that they have COVID, or they’re close contact,” Alabama State Superintendent Eric Mackey told AL.com. The local mitigation efforts are not working to slow the spread of Omicron in the Birmingham area right now.
\n\n\n\nMany attendees communicated their disappointment about the postponed WordCamp on social media but were supportive of the organizers’ decision.
\n\n\n\n\n\n\n\nWhen WordCamp Birmingham’s organizers began planning in August, they had no idea that a new more transmissible variant would be making its way across the world just as the in-person event was set to kick off. The timing is unfortunate, and the stakes are too high to risk pushing forward.
\n\n\n\nWordCamp Birmingham’s previously selected speakers will be invited to speak at the rescheduled event, pandemic conditions permitting. The 200 people who signed up to attend will need to buy their tickets again and reschedule their accomodations.
\n\n\n\n“Our goal is to have the same great event we have currently planned, just a bit later,” Marks said.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Jan 2022 01:32:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:66:\"WPTavern: Wicked Plugins Launches UI-Based WordPress Block Builder\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=125721\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:177:\"https://wptavern.com/wicked-plugins-launches-ui-based-wordpress-block-builder?utm_source=rss&utm_medium=rss&utm_campaign=wicked-plugins-launches-ui-based-wordpress-block-builder\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5170:\"Last week, Wicked Plugins launched version 1.0 of its Wicked Block Builder. I have kept my eye on this plugin since its November 2021 beta release. The project promised that developers would be able to “effortlessly build custom blocks,” and I was finally ready to put that to the test.
\n\n\n\nIn the past two months, I have activated the plugin every so often. I knew a review of it would take me a while, and I would deactivate it before diving in. I kept feeling overwhelmed by the enormity of it — there are tons of settings to configure. The holiday season did not help either. I wanted to sit down with a clear head and decide whether this plugin was something developers in the WP Tavern audience should put in their toolbox.
\n\n\n\nThe short answer: yes.
\n\n\n\nOr, at least you should give it a spin to see how it compares to similar plugins. This is a version 1.x project, so there are still some missing pieces. However, it will make client builds easier to put together without writing anything more than CSS for custom blocks.
\n\n\n\nWhen I first began using the plugin, I seemed to hit issue after issue. Like always, I was trying to run before I could walk. I like to test new plugins at full speed and often forget to stop and RTFM. With complex projects like Wicked Block Builder, I must remind myself that it is OK to seek help from the docs.
\n\n\n\nThe plugin has a bit of a learning curve if you want to do anything advanced. My suggestion is to do the opposite of what I did. Start with a simple use case.
\n\n\n\nFortunately, the plugin development team has a tutorial video that will have you building custom blocks in less than five minutes. I recommend following along when creating your first.
\n\n\n\n\n\n\n\nOnce I hopped over that initial hurdle, using the plugin was a breeze.
\n\n\n\nThe plugin allows developers to add blocks, block categories, patterns, and pattern categories. I primarily focused on block creation. The plugin worked in much the same way as other pattern builders.
\n\n\n\nFollowing along with the tutorial video, I created a Resource Card block. It included an image, title, summary, and button.
\n\n\n\nThere are multiple tabs for developers to build out their blocks. Aside from the primary Settings tab, most of the work will happen under Attributes and Editor View. The Front-end View is only necessary if the block’s output does not match what it looks like in the editor. The screen also has a Styles panel for adding custom CSS, which is loaded for the editor and front-end.
\n\n\n\nThe UI seems mostly straightforward when following along with the tutorial. However, there are tons of options, and it is easy to get lost once you start digging into them all.
\n\n\n\nOnce I pieced together my custom block, it correctly appeared in the inserter. I also tested a slash command for /resource card to ensure it worked.
A couple of missing features I immediately noticed once inserting my block was a custom icon and example/preview. Both are relatively simple to add when creating a block type from code, so I hope they are on the agenda for a future version.
\n\n\n\nWhile searching for the custom block type via the inserter worked, I would also welcome an option to create custom keywords.
\n\n\n\nI filled in the details of the Resource Card block and saved it.
\n\n\n\nTo my surprise, I did not break anything. I began wondering, Could creating blocks be this easy?
\n\n\n\nI ran through a few other simple block ideas, and the experience was enjoyable. While I no longer work with clients, I could see how this could save hours. Pairing it with template locking would also be a routine use case so that clients would only need to plug in their content and publish.
\n\n\n\nThere are some block-supported features that I would like to see added. The plugin currently allows devs to enable alignment and wide alignment. However, others like spacing, typography, and color would be easy wins.
\n\n\n\nI tested the free version of the Wicked Block Builder. For simple blocks, it worked well. For more complex use cases, developers will need to upgrade to the pro version. It runs between $49 and $299 per year, depending on the number of supported sites.
\n\n\n\nWhile I have not tested the pro version, it does offer post and term selects, repeater fields, conditional logic, and inner-block support. After exhausting the basics, these will likely be necessary on some projects. However, the free version can still get you pretty far.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Jan 2022 00:42:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:66:\"WPTavern: Creating Speech Balloons With the WordPress Block Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=128271\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:177:\"https://wptavern.com/creating-speech-balloons-with-the-wordpress-block-editor?utm_source=rss&utm_medium=rss&utm_campaign=creating-speech-balloons-with-the-wordpress-block-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4215:\"I do not know how I overlooked LIQUID SPEECH BALLOON. The plugin is less than a month shy of being three years old, and I follow block-related projects religiously. This one slipped through the cracks, at least until I haphazardly stumbled upon it when searching for something else entirely.
\n\n\n\nIt is also relatively popular for a single-block plugin. There are not that many with more than 10,000 active installs. I had to know what it was doing to draw such a crowd.
\n\n\n\nIn the comments on yesterday’s post about Automattic’s Livro theme, Nick Hamze wanted to know where all the fun theme designs were. Perhaps it was fortuitous timing that I also happened to be playing around with a plugin that might fit the bill. Sure, it is not a theme, but it can definitely be used to spruce up an otherwise boring or plain design.
\n\n\n\nSo, I spun up a few Speech Balloon blocks and just had fun creating a chat with a some cartoon animals:
\n\n\n\nI tend to gravitate toward clean, open-canvas themes because they allow me to add all the fun elements via the post content. That is why I love finding plugins like LIQUID SPEECH BALLOON. They add that visual flair to pages that can sometimes be boring.
\n\n\n\nUsing the plugin’s Speech Balloon block is straightforward. It presents users with a single section for inserting rich text content.
\n\n\n\nIn the block options sidebar, users can choose an avatar. They can also make several design adjustments, including background and text colors.
\n\n\n\nThe block is falling slightly behind the times, though. Since the plugin’s release nearly three years ago, WordPress has added several new design components that could be used to make its block even better, such as padding, border, and typography controls.
\n\n\n\nThe plugin can also be used for testimonials or other types of reviews. It works well enough for more business-friendly layouts if that is the sort of thing you are after.
\n\n\n\nThe plugin’s biggest failure is in how it handles avatars. It is also why it does not make for the best option for testimonials. Users cannot add avatars directly via the block. Instead, they must register them via an entirely separate admin screen. Then, they can select from their saved avatars list within the block.
\n\n\n\nUnder the Settings > LIQUID SPEECH BALLOON page, the plugin presents users with several rows of fields. They can add a name and image URL for each avatar.
\n\n\n\nThis is where the user experience falls apart a bit. There is no way to upload avatars on this screen. Instead, users must upload them via their media library, copy the URL, and paste it into the image URL field.
\n\n\n\nThe plugin provides the necessary documentation and links to work through this process. The overall experience is simply lackluster.
\n\n\n\nHowever, if users only need a limited number of avatars, the system works well enough once everything is uploaded. The images are always available whenever inserting the Speech Bubble block — no need to search through the media library or upload a new one.
\n\n\n\nI am not sure if this will go in my plugin toolbox. Outside of a few stylistic elements, such as the speech bubble’s tail, users could readily recreate something similar with a few blocks, as shown in the following screenshot:
\n\n\n\nWithin a few minutes, I created this with what is already available in core WordPress, and I actually had several more design choices by doing so. I could see keeping a block pattern on hand for such a layout in the future.
\n\n\n\nFor those who want a quick and easy solution without all the fuss of mixing and matching blocks, LIQUID SPEECH BALLOON would be the better option.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 14 Jan 2022 02:22:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"WPTavern: Automattic’s Livro Is a Minimal Block Theme for Writers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128178\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:173:\"https://wptavern.com/automattics-livro-is-a-minimal-block-theme-for-writers?utm_source=rss&utm_medium=rss&utm_campaign=automattics-livro-is-a-minimal-block-theme-for-writers\";s: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:4992:\"Sometimes the sweetest things in life are the simplest. Automattic’s latest block theme landed in the review queue yesterday, and I had to give it a spin. What I found was a minimally-elegant design that I fell in love with.
\n\n\n\nReally. I even dedicated an entire demo post on my install to it:
\n\n\n\nWell, that and Valentine’s Day is a mere month away. It felt like the right time to mix up my install’s test content anyway.
\n\n\n\nLet me preface the rest of this review by saying that I hate dark themes with a fiery passion. However, every now and again, one comes along that makes me rethink my position. Livro is one such theme. I may dislike it in a week, but I have genuinely loved using it for two days.
\n\n\n\nThe theme’s most impressive feat was using a single font family, Newsreader, across the entire design. It never felt like it needed anything else to separate body copy, secondary text, and headings.
\n\n\n\nLivro will not meet everyone’s needs — not by a long shot. However, it is the sort of theme that will appeal to those who do not like any bells and whistles whatsoever. The type where content reigns supreme, where a few words and pictures are all that is necessary to make a point.
\n\n\n\nI did not immediately hop on this whirlwind affair with Livro at first sight. Things started a bit rocky. The theme managed to implement my top three pet-peeves:
\n\n\n\nOne extra issue I noticed with the post content on the blog and archive pages was that wide and full-aligned blocks were the same width as normal content. I do not know if that is a WordPress or theme-specific issue. Since I planned on switching to excerpts, I did not look too deeply into the code.
\n\n\n\nThe Navigation block issue is, in part, a problem with WordPress itself. It will fall back to the core Page List block in specific scenarios. However, theme authors can also address this via the block_core_navigation_render_fallback hook, introduced in Gutenberg 12.1.
Fortunately, all of these issues are dead simple to correct in the world of block themes. The site editor is just a click away, and users are no longer bound to the oddities of otherwise solid theme designs. In moments, I was able to customize how things looked.
\n\n\n\nThe theme bundles 15 block patterns in total. Eight of them are for headers, and five are for footers. Most of these are variations on the same concept, primarily changing the position of the default elements.
\n\n\n\nI was a little disappointed to not see more variety for page or general-use patterns. The theme ships one for an About page and another for a Contact page. They both use an offset-column design that I hope one day gets dropped into the black hole where other web design trends go to die.
\n\n\n\nThe nav menu’s “x” close button is on the far right edge of the screen, but the open icon is on the far left. This is more of a problem with WordPress’s handling of the Navigation block than the theme. Nevertheless, it is still irritating trying to find the close button. Ideally, the open and close buttons would always be in the same place.
\n\n\n\nOne way to mitigate this issue is to use the “Header with site title on left and button on right” pattern — yes, all the short names were taken on header-pattern naming day.
\n\n\n\nUsers can switch it by modifying the Header template in the site editor. It puts the nav menu open button on the right side of the page. The close button will still be slightly off, but it is a better experience than the default.
\n\n\n\nFor a theme that I claim to love, I did focus on its downsides in this review. Part of that is to show that such issues need not always be the reason to overlook a block-based theme. If they are relatively minor problems, it does not take a programmer to make those adjustments. All of the design elements that I enjoyed about the theme were already there. It just needed some coaxing to make it perfect for me.
\n\n\n\nI would still like to see the Automattic Theme Team add a few patterns to the mix. Livro’s clean canvas seems to invite a mashup of media and text blocks.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jan 2022 01:46: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: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:55:\"WPTavern: Extendify Launches New Pattern Library 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=128175\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/extendify-launches-new-pattern-library-plugin?utm_source=rss&utm_medium=rss&utm_campaign=extendify-launches-new-pattern-library-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:4062:\"Extendify has simplified access to its pattern library with a new plugin that offers patterns and full-page layouts for WordPress sites using Gutenberg-friendly themes. The company has high expectations for the product, publishing it under the name “Extendify” as its flagship free plugin in the official directory.
\n\n\n\nAlthough a different version of the pattern library is included in Extendify’s popular Gutenberg Template Library & Redux Framework plugin, which has more than a million active installs, this new plugin is focused simply on site design tools.
\n\n\n\n“If you’ve tried out the Extendify Library previously, then you’ll find this new version is completely refreshed,” Extendify’s Head of Product Rich Tabor said. “We rebuilt the library, and all our patterns/layouts, from the ground up — with a focus on augmenting the editing experience of both existing and new themes.”
\n\n\n\nExtendify functions as a SaaS connector plugin that uses a custom API to fetch block patterns and page layouts from the company’s servers. Once installed, the plugin has no separate settings page. Extendify adds a “Library” button at the top of the editor to launch a modal with patterns and layouts.
\n\n\n\nIf you haven’t selected a “Site Type” in the sidebar of the modal, all the patterns and layouts will be black and white. Selecting a Site Type will update the previews to show insert industry-specific copy and pictures with color.
\n\n\n\nIf you find a page layout that you like, it’s easy to get a beautifully designed page in a matter of seconds. However, the way it is set up at the moment, free users only have access to five imports. Subscribers can get unlimited imports for $49.50/year for one site.
\n\n\n\nUsers who are not planning to upgrade must be judicious about the patterns and layouts they choose to preview on the page. The plugin will warn free users about the remaining number of imports before proceeding. This mode of limitation may slow the plugin’s adoption, because users have to be careful about trying too many patterns and layouts on their sites. The plugin’s FAQs state that “Each user receives a limited number of imports completely free” but users would be better served by knowing that it’s a total of five imports before installing.
\n\n\n\nOne of the good things about the plugin is that it is theme-agnostic and the patterns and layouts should still work nicely, even if you decide to change themes.
\n\n\n\n“All our patterns and layouts are built completely with core blocks, infused with a clever utility design system (which lets us have neat patterns like this one and are built to be Full Site Editing / Block Theme first – although we support most themes that support Gutenberg properly),” Tabor said.
\n\n\n\nPreviously, Extendify’s pattern library was only available as an SDK inside the company’s other related Gutenberg projects. This plugin makes it more accessible for site builders who only need the pattern/layout capabilities.
\n\n\n\n“This effort was geared towards lowering that barrier and bringing the best of what we have to offer to anyone interested in building sites with the block editor,” Tabor said. “The new Extendify plugin is really the first big push in this direction, but we’re also leaning in on other ways to augment the editing experience to better empower both small business owners and site builders alike.
\n\n\n\n“Block themes are where the future is and we’re aiming for the pole position with this newest effort.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jan 2022 23:16: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: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: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:80:\"Post Status: Impossibly Knotted Together: Meditations on 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:31:\"https://poststatus.com/?p=92470\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"https://poststatus.com/impossibly-knotted-together/\";s: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:10926:\"This article is part of a conversation we\'d like you to join.
\n\n\n\nWhat were the good and bad features of the first three versions of the WordPress community? What were the major bugs? What should the Post Status community look like in 2022 — and beyond? What should leadership in this space look like? What are the principles that should drive it? What are your own questions and What Ifs?
\n\n\n\nYou can leave a comment here or get in touch on any Post Status channel, on or off the record. Blog about it. Tweet about it. Write for us. Help start this needed conversation.
\n\n\n\n\n\n\n\nI first meet J as she’s staffing a table at a WordCamp. We talk about what brought us there, what we did before being involved in the WordPress community, what we hope to get from the day. There’s a problem she’s working through and I mention someone who has been through something similar, in case it helps. She tells me about a resource I hadn’t heard of, and I’m excited to check it out.
\n\n\n\nOver the years that follow, J and I remain WordPress friends. At various times we encounter each other at events, in elevators, at receptions, across hallways, during meals, in Slack. The conversation picks back up where it left off. “How’d that thing go?” “You did an awesome job navigating that conflict!” “How’s your new team at work?” “Congrats on that cool thing you launched!” Being a part of the WordPress community gives J and me an anchor point, a foundation, and we build on it from there.
\n\n\n\nThere are many WordPress friends. I may not encounter them for months or years, and the connections may not always be as wide or deep as other friendships, but they have a special place in my heart. I smile when I notice them, online or in person. I celebrate their successes. I cherish our shared experience of building something together.
\n\n\n\n\n\n\n\nWe have to talk more about the role of elders in our community. Definitely not elder as in “old entitled men” but elder as in “someone with life experience and wisdom who can be looked to for guidance as the community evolves.” We are old enough as a community to have elders, whether we see them as such or not.
\n\n\n\nAs communities go through transitions and face challenges, it’s often the elders who ground us and guide us. Not by wielding their power to keep order or fighting for the status quo, but by helping us weave the stories of our origins and past into our dreams for the future. This can happen in code, in community conversations, in documentation, or anywhere else.
\n\n\n\nElders can help us build relationships and connections across different parts of the community, promoting mutual respect and welcoming newcomers. Elders can pass down knowledge, teaching, and modeling cultural traditions and beliefs. Elders can deal with discrimination and oppression, using their standing to call out problematic behavior. Elders can help build sustainable infrastructure, making sure there are tools and services in place for the challenges we will face. Elders can help protect our identity while also helping us to adapt and evolve.
\n\n\n\nHow do WordPress community elders see themselves and their role? If they aren’t being celebrated for committing the latest hotness to an upcoming release or giving an exciting WordCamp talk, do we let them just fade into the background? If they branch out into other interests beyond WordPress, do we still find ways to harness their experiences and wisdom? Do we take care of them as they take care of us?
\n\n\n\nDo our elders even know they are elders? Are you a WordPress community elder?
\n\n\n\n\n\n\n\nSmall enough that you can make a difference\nBig enough that you can grow\nComfortable enough that you feel supported\nChallenging enough that you stay flexible\nFilled with people who want the best for you\nIntentional places and spaces for celebrating\nJust enough certainty to create a sense of purpose\nJust enough uncertainty to keep us humble\nNorms, ground rules and accountability\nPatience and respect built on safety and care\nCreative, kind and loving acts at the heart\nWhen people get a taste, they wonder\nWho created this, and how can I be a part of it?\n\n\n\n\n\n\n\n
I was a WordPress user and developer for 10 years before I knew who Matt Mullenweg is. I’d bet that most WordPress users still don’t know who he is. And yet conversations about what Matt wants, what Matt thinks, what Matt is going to do sometimes play an outsized role in our community. People can worry when they think a thing they love or depend on is too much in the hands of forces they don’t know or understand. Nobody wants a broken heart.
\n\n\n\nFor a time I ended up working for Matt, reporting to Matt. I discovered that he has a superpower: he can see around corners and beyond horizons in ways that few other people can. I’d suspect time travel is involved if I didn’t know better. Sometimes he has trouble bringing the rest of us along, like trying to show a 19th-century carpenter the schematics for a space station. Other times, I think it’s just too many hearts and hopes and dreams for one person to carry gently. But on the whole, Matt is responsible for leading us to some amazing milestones.
\n\n\n\nWhen things go well, Matt usually credits people in the community. When things aren’t going well, Matt usually gets or takes the blame. When we challenge him thoughtfully, he usually welcomes the growth and learning that goes with it. But Matt knows that WordPress and the WordPress community are bigger than him. I think he’s happy to be a part of building a thing that will outlive him, and probably all of us. He’s made it his life’s work. We can honor and celebrate that legacy without reservation.
\n\n\n\nAs a community, we can also build for a future that does not depend on any one person. We can make sure there’s a plan for maintaining our “commons.” There are other superpowers out there; I bet you have at least one to contribute. If we do it right, a shared vision for our community’s future will come from everyone who loves or benefits from WordPress in some way.
\n\n\n\n\n\n\n\nWhen intentional communities form in the real world, their members think about the characteristics that will make their community resilient, sustainable, and able to thrive. These characteristics might include:
\n\n\n\nWe can’t always choose our fellow community members and software that powers a huge chunk of the web is hard to make small and local again. But what can we learn from intentional communities? When you examine the physical places and spaces in your world that feel most welcoming, thriving, and sustainable, what do you notice?
\n\n\n\nDo we want to create community experiences that are not so small as to preclude diversity, space, and freedom, but small enough to be accessible and not overwhelming? How can we make the daily experience of being in the WordPress community more personal, meaningful, and accessible?
\n\n\n\nIf real-world communities have a distinct center, defined boundaries, smaller sub-centers of activity, and open areas flowing all around, what does that look like for the WordPress community? How can we make sure our community spaces evolve to support interactive and supportive social structures?
\n\n\n\nAs pandemics and climate crises and polarization and uncertainty circle around us, what would it mean to feel grounded and safe in a resilient WordPress community?
\n\n\n\nAdapted in part from Chapter 4 of Norwood and Smith’s “Rebuilding Community in America” (1995).
\n\n\n\nEven with its wonderful diversity and global reach, I don’t think we’ve even begun to explore the WordPress community niches that exist out there.
\n\n\n\nYou could probably have a gathering for Canadian WordPress developers under 40 who specialize in funeral home websites and get a solid showing.
\n\n\n\nThere could be an entire weekly newsletter devoted to tips for pet adoption and rescue organizations who use WordPress to help animals find their forever homes, and someone would still suggest it needs to come out daily.
\n\n\n\nThe trials and tribulations of the Restaurants On WordPress scene are waiting to be chopped apart, lightly sauteed and served up with a side of Food Blogger Business Models.
\n\n\n\nThere are WordPress sub-communities and sub-cultures and niches and nooks and crannies that would take a lifetime to begin uncovering and exploring. There are so many stories to tell, and so many of them are nothing like our own. If we are to appreciate the beauty of the WordPress community as a whole, we have to seek them out.
\n\n\n\nBeware anyone who tells you that they fully understand the WordPress community, or that they have their finger on the pulse of all things WordPress. Some of us have made more stops than others, but we are all travelers in a wonderful vastness that has no end.
\n\n\n\n\n\n\n\nComment sections can be goldmines for engaging with your audience. Yet unmoderated comments can quickly descend into chaos. If you don’t keep an eye out for spam, it may overrun every comment section on your website. These messages can scare real readers away, and prevent them from interacting with other users (and with you).
\n\n\n\nIn most cases, spam is easy to recognize. Users or guests will leave links to other websites without explaining why, or start talking about products and services that have nothing to do with your content. If you put measures in place to stop these messages, you can keep your comment sections protected and valuable to your audience.
\n\n\n\nIn this article, we’re going to take a good look at how spam appears in a comment section. We’ll show you how to identify spam comments on your WordPress websites, and talk about how they negatively affect your website. Finally, we’ll show you eight ways to prevent comment spam in WordPress. Let’s get to it!
\n\n\n\n\n\n\n\nIf you use the internet, you’re already familiar with spam. You probably get dozens of emails per week advertising fraudulent products and offers. But spam messages don’t just come in the shape of emails — they’re everywhere on the web.
\n\n\n\nSpammers tend to gravitate towards comment sections because they offer the opportunity to target a broad audience. On popular blogs, it’s not uncommon to have comment sections with dozens of users engaging in discussion. A single spam comment pointing to another website can easily get a few clicks, and even more so if it blends into the conversation.
\n\n\n\nGenerally speaking, comment spam is any content with the sole purpose of pointing visitors towards other websites. Spam commenters may be trying to get people to buy or sign up for something, phish sensitive information from visitors, or install malware on their device. Occasionally you’ll see legitimate comments that point readers towards third-party websites, but these links have to make sense in the context of the discussion.
\n\n\n\nIt can be tempting to simply ignore comment spam, but that can have a negative impact on your website. If you visit a site and you see that its comment sections are overrun with spam messages, you might not trust its content or the business that owns it. We’ll touch on other ways that spam can affect your site, but first let’s talk about how to spot this type of comment.
\n\n\n\nSpam comments tend to be very easy to spot. In a lot of cases, bots — not actual people — are behind them. These bots are programmed to target comment sections that don’t require any type of verification and post messages that will lead readers to third-party websites.
\n\n\n\nIf you’re ever on the fence about whether a comment is spam or not, there are several signs that you can check for. Signs of comment spam include:
\n\n\n\nSometimes, you might get comments in poor taste or that don’t add anything to the discussion. Those commenters may be genuine in their opinions and honestly think that they’re contributing to the community, or they may be trolling. But those comments are not necessarily spam.
\n\n\n\nThere are a couple of key differences between trolls and spam. Trolls are real people and spam is most often spread by bots. Also, a troll’s main goal is to disrupt discussion, sow division, and elicit emotional responses from other individuals. The main goal of spam is usually some kind of financial gain, whether it’s an unethical (but genuine) marketing tactic, or an attempt to scam people.
\n\n\n\nIf you’re working on your first WordPress website, you may think that spam bots have it out for you. Unfortunately, comment spam is something that almost every website has to deal with (unless you turn comments off entirely).
\n\n\n\nBots crawl the web looking for comment sections that they can target. They don’t differentiate between sites that are and are not relevant to the websites, products, and services that they’re promoting. For spammers, it’s all a matter of numbers. If they leave thousands of comments across many different websites, at least some readers will take the bait.
\n\n\n\nSome of those users will go on to share personal information or even payment details that spammers can steal. In some cases, spammers might benefit directly from making sales to users who aren’t aware of their underhanded practices.
\n\n\n\nComment sections can be an incredible source for engaging discussions and ideas within your website. They can encourage users to look out for new posts and build relationships with other commenters. On the other hand, the price that you pay for having a comment section is needing to deal with spam.
\n\n\n\nLuckily, WordPress empowers you with several tools and features that make dealing with spam comments that much easier. We’ll explore those in a second, but for now let’s talk about the rest of the ways that spam comments can affect your website.
\n\n\n\nIf you come across a website that looks credible, but it’s full to the brim with spam comments, you might believe that the site is abandoned. At the very least, you’ll tell yourself that its owners might not care about cleaning up their comment sections, or that they don’t pay attention to comments at all.
\n\n\n\nThe more obvious the spam is, the more negatively it will impact your website’s image.
\n\n\n\nTech-savvy users might not judge you too harshly for having spam on your website, since they understand where it comes from. But not all of your audience will know that they should ignore spam comments.
\n\n\n\nSome users will see spam and think that since it’s on your website, you’re endorsing it or promoting the offers the comments include. If that translates to them making a scam purchase or sharing personal information online, it will diminish their trust in you.
\n\n\n\nIf you have a website with a comment section, it’s your responsibility to keep it clean, and not just so that your site looks better. You have to consider that some of your audience doesn’t have the technical know-how to differentiate spam offers from real content, and it’s your job to ‘protect’ them while they’re on your site.
\n\n\n\nIf you’re a user trying to have a real discussion in a comment section, navigating spam can be frustrating. Genuine replies to the topic at hand can easily get lost as bots overrun the comment section.
\n\n\n\nThat frustration can lead to users deciding that commenting on your content is simply not worth it. Comments can be a great source for critical discussion about your posts, questions that can lead to new content, and even users simply thanking you for your efforts.
\n\n\n\nIf you allow spam to run unchecked on your website, you lose out on a lot of the value that comment sections can provide. At that point, you might be better off disabling comments altogether.
\n\n\n\nGetting a website to rank well on search engines takes a lot of time and effort. Often, it can take months or even years to grow a website to the point where it’s getting decent traffic from search results. That process involves dozens of SEO tasks, tweaking your pages and posts so they’re well-optimized, and publishing better content than your competitors.
\n\n\n\nUnfortunately, spam comments can negatively impact your SEO if you leave them unchecked. Most spam includes links to external websites, and search engines can’t differentiate between those links and the ones that you include within your content.
\n\n\n\nFrom the search engine’s perspective, all they see is that your website suddenly includes a lot of ‘low-value’ links. Since links are one of the many signals that search engines use to determine rankings, spam comments can cause your site to plummet in the results.
\n\n\n\nConsidering how critical search engine traffic is to most websites’ growth, you can’t allow spam comments to linger on your site. That’s why you need to put measures in place to prevent spam, and to weed it out if it makes it past your defenses.
\n\n\n\nIf you’re getting a lot of spam bots attempting to submit comments, these requests can affect your website’s performance. If your site is having to handle thousands of spam submissions a day, that can use up a lot of your site’s resources — especially if you’re on a budget hosting plan. Additionally, if you let spam comments pile up, you may end up with some serious database bloat, further slowing your site’s load times.
\n\n\n\nIf your readers have to wait a long time for your pages to render, they’re less likely to stick around to read your content, let alone leave a comment (unless it’s to complain about how slow your site is).
\n\n\n\nAt this point, we wouldn’t blame you if you’re very concerned. Spam causes a lot of problems, and it’s almost guaranteed that bots will try and post these types of messages on your site. So what can you do about it?
\n\n\n\nThe good news is that WordPress offers a variety of ways in which you can prevent and filter spam comments from your WordPress website. In this section, we’ll explore all of the approaches that you can take to prevent spam and protect your comment sections.
\n\n\n\nThe best way to deal with spam is to use a plugin that can automatically detect which comments are legitimate and which ones aren’t. That’s a lot to ask from a plugin, but it’s precisely what Akismet does.
\n\n\n\nWhen you use Akismet, the plugin analyzes each comment that visitors submit on your website. It accesses Akismet’s global database and checks to see if the comments match other known spam entries and sources.
\n\n\n\nAll of that happens in the background, in a matter of seconds. If Akismet marks a comment as spam, it’s flagged and it doesn’t get published. Fortunately, you can also review these comments manually, to double-check that no real entries get flagged by mistake.
\n\n\n\nIf you want to approve a comment, you can mark it for publication and it will show up on your website. But you save a lot of time by focusing only on the comments that Akismet flags versus reviewing every comment submission manually.
\n\n\n\nThere is a free version of the plugin, which is perfect for most websites. On the other hand, if you’re running a commercial site or get a large volume of traffic, you’ll want to look into premium plans.
\n\n\n\nIf you want to stop spam altogether, you can disable comments throughout your website. This is an extreme approach, so we only recommend that you disable comments if you’re certain that they won’t contribute anything to your site.
\n\n\n\nTo disable comments in WordPress, access your dashboard and go to Settings → Discussion. Look for the section that reads Default post settings at the top of the screen, and uncheck the Allow people to submit comments on new posts option:
\n\n\n\nThat setting will disable comments for every post that you publish from now on. But comments will remain active for old posts and pages. To disable those comment sections, go into the Posts or Pages tab. Select a post or page, and click on Quick edit below its name. You’ll see an option that reads Allow Comments.
\n\n\n\nIf that option is checked, disable it. Repeat this process for every page and post where you want to disable comments.
\n\n\n\nDepending on the type of website you’re running, disabling comments altogether might cost you some user engagement. Fortunately, there are other ways to reduce spam.
\n\n\n\nOne of the best ways to reduce comment spam in WordPress is to make it more difficult for bots to make submissions. Forcing bots to register and log in before they can comment can go a long way towards reducing spam entries on your posts and pages.
\n\n\n\nWordPress enables you to do that by checking a single setting on your website. Go to Settings → Discussion and scroll down to the Other comment settings section. Tick the box for the setting that reads Users must be registered and logged in to comment.
\n\n\n\nBy enabling that setting, you force spammers and bots to go through the registration process if they want to submit anything on your website. In a lot of cases, that can be enough to deter spammers. But since spam user registration does happen, you may have to implement a few more preventative measures.
\n\n\n\nBy default, WordPress publishes comments as soon as users submit them. It also comes with a moderation queue where you can review comments and approve or reject them before they go live.
\n\n\n\nYou can configure WordPress so that your website requires you to approve every comment manually. To do so, go to Settings → Discussion and scroll down to the Before a comment appears section. Enable the setting that reads Comment must be manually approved.
\n\n\n\nThere’s also another setting that tells WordPress it can automatically publish comments if you’ve already approved submissions from the same user. That setting can save you a lot of time, as you’ll only have to review submissions from each user once.
\n\n\n\nTo access pending comments, click on the chat box icon in the top menu within the dashboard. That icon should display a number to its right, which shows the number of pending comments in the queue.
\n\n\n\nFrom this screen, you can review comments one by one and approve those that aren’t spam. If you see a spam comment, you can delete it permanently.
\n\n\n\nGenerally speaking, there aren’t many situations where it makes sense for legitimate comments to include links. Your readers might want to point each other towards relevant content, but usually, comments that include links tend to fall into the spam category.
\n\n\n\nWordPress offers an elegant solution to that problem by enabling you to configure how many links a comment can include before it gets flagged as spam. You can find that setting on the Settings → Discussion page under the Comment Moderation section.
\n\n\n\nBy default, WordPress will flag any comment that includes two or more links within its body. If you want to play it safe, you can reduce that number to one link. This means any comments that include links will go into the moderation queue to await your approval.
\n\n\n\nThis section also enables you to set keywords that WordPress will use to flag comments. If it detects those words within new comments, WordPress will hold them in the moderation queue. Some common keywords that you can set include:
\n\n\n\nAll of those keywords are pretty good indicators of spam comments. You can be as aggressive as you want when it comes to choosing what terms to filter, but keep in mind that this means you’ll need to spend more time approving comments manually.
\n\n\n\nRather than deciding what keywords to ‘blocklist’ on your own, you can also benefit from the collective experience of the WordPress community. For example, you might download the recommended Comment Blacklist for WordPress that’s featured on GitHub.
\n\n\n\nYou may have noticed that a lot of comment sections force you to solve a CAPTCHA before you can submit an entry. CAPTCHAs are simple tests designed to stop bots from posting and ensure that you’re a human.
\n\n\n\nWordPress doesn’t include CAPTCHA functionality out of the box. The good news is that you can easily add this feature using a plugin like reCaptcha.
\n\n\n\nThis plugin enables you to add CAPTCHAs to multiple elements within your website. You can add them to comment sections, registration and login forms, contact forms, and more.
\n\n\n\nIf visitors (or bots) can’t solve the CAPTCHAs, they won’t be able to submit comments. But CAPTCHAs don’t always catch every spam comment. Bots become smarter each day and often find ways around even the trickiest of puzzles.
\n\n\n\nThe WordPress comment system works seamlessly and includes a lot of features to make your life easier. Yet it lacks things like social media integration and the ability for visitors to reply using images or GIFs, emoticons, and other options.
\n\n\n\nIf you want to give your audience access to that type of functionality, you can replace the default WordPress comment system with a different one altogether. There are plenty of WordPress plugins that enhance your comment section:
\n\n\n\nComment plugins that include social media components offer a fantastic way to reduce spam in WordPress. By forcing users to log in through social media to comment, you make it harder for spammers to submit fake entries on your website.
\n\n\n\nUsing a WAF can help you prevent attackers from accessing your website. WAFs enable you to configure rules that govern who can use your site. That means you can block IP addresses, visitors from specific regions, bots that try to access your site repeatedly in short amounts of time, and more.
\n\n\n\nIf you’ve ever run into a website that uses Cloudflare or Sucuri, then you’ve already seen WAFs in action. Most content delivery networks (CDNs) offer WAF functionality, since it helps them protect their users against malicious traffic.
\n\n\n\nUsing a CDN will also help you improve load times throughout your website. Depending on which service you use, you might also get access to features like automatic image optimization, denial of service (DDoS) protection, and more.
\n\n\n\nSome CDNs will help protect your website against known bots and spammers. Simply enabling the CDN will block those known agents from accessing your website and being able to leave comments.
\n\n\n\nIf you have comment sections on your website, you’re going to be faced with spam. Spam bots are everywhere, and if you ignore them, they can quickly overrun your comment sections with links to other websites and offers that will scare some of your real visitors away.
\n\n\n\nFortunately, WordPress offers a number of ways to deal with comment spam. You can use built-in settings to make it harder for spammers to submit responses to your posts and pages. You can also use plugins that automatically filter out easily recognizable WordPress comment spam, add CAPTCHAs to your comment sections, or require visitors to log in using their social media accounts.
\n\n\n\nIf you want a simple but effective solution, you can begin by setting up Akismet. This plugin will automatically filter spam comments on your WordPress website, so you don’t have to spend time going over your entire moderation queue manually. Akismet also integrates with some of WordPress’ most popular plugins like Jetpack, Contact Form 7, Gravity Forms, Formidable Forms, and others.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jan 2022 10:09:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Simon Keating\";s: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:75:\"WPTavern: What Are Block Themes? What You Need To Know Before WordPress 5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=127927\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/what-are-block-themes-what-you-need-to-know-before-wordpress-5-9?utm_source=rss&utm_medium=rss&utm_campaign=what-are-block-themes-what-you-need-to-know-before-wordpress-5-9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7228:\"WordPress 5.9 is set to launch on January 25, and many users will be in for a surprise. The upcoming release will be the most monumental shift in how the platform works since the introduction of the block-based content editor in 5.0. Block themes, global styles, and the site editor will kick-start a new future for WordPress.
\n\n\n\nFor the average WP Tavern reader, this is not news. We have covered block themes here for over a year. For those out of the loop, there is a lot to catch up on within the next two weeks.
\n\n\n\nOne of the complaints with the launch of the block editor in 2018 was that users could only opt-out of using it by installing Classic Editor or a related plugin. This is not the case for the new features in 5.9. Users can keep on using their current setup without any changes at all. Accessing the site editor and global styles is an opt-in process. It requires the activation of a block theme.
\n\n\n\nThe upcoming changes will affect two primary groups of users. The first are those who prefer to run the latest default WordPress theme. The second will be those ready to try out the new system.
\n\n\n\nCurrently, there are 35 block themes in the directory on WordPress.org, with more in the review queue. That limits the available options for now.
\n\n\n\nAfter WordPress 5.9 launches and developers become more familiar with building on the new system, I expect that we will see a noticeable uptick in block themes in the coming months.
\n\n\n\nNote: this post focuses on user-facing changes. If you are a developer who wants to get started with block theme design, read Marcus Kazmierczak’s overview of building block themes for WordPress 5.9.
\n\n\n\nThe latest default WordPress theme, Twenty Twenty-Two, will launch alongside version 5.9. While I have a few nit-picks about it, it might just be my all-time favorite default theme ever created.
\n\n\n\nWordPress 5.9 RC 2 was released earlier today. Now is as good a time as any to give it a test run. Twenty Twenty-Two is already bundled with this version.
\n\n\n\nAs is often the case with default themes, it is likely to become the de facto standard in which developers build their own projects. It uses all the latest features and is one of the most up-to-date themes out there. This makes it the ideal starting point for users who want to test the new system.
\n\n\n\nThe theme is merely one component of a broader system. For users, it can be something they set and forget. Or, they can take it to the next level and customize their front end until their heart is content.
\n\n\n\nBlock themes are different than many traditional themes. In the classic era, users activated a theme and customized whatever options the developer made available. It was a rigid system that often did not give users much flexibility unless they knew how to write code.
\n\n\n\nUsers can access a boatload of new features after activating a block theme. This is done via the site editor, located under the Appearance > Editor admin screen. Users can modify their theme templates directly on the canvas and customize their design through the global styles panel.
\n\n\n\nThe first experience with the site editor can be overwhelming. Some might prefer diving right in, while others take a different approach. Regardless of how you learn, I recommend going through the Simple Site Design with Full Site Editing course from Learn WordPress. The Training team has created a 15-lesson plan that walks you through everything you need to know. They also have a six-minute workshop on using global styles.
\n\n\n\nUsing the site editor can be fun, but it can also be frustrating. This is essentially a “version 1.0” of the feature. It will not meet everyone’s needs with its launch in two weeks. It will take some time to mature and for theme authors to build on top of it.
\n\n\n\nI spent over a decade building themes professionally. One of the most common questions I got was, “How do I change the post meta area?” Users would want to remove the author, move the category list, and do numerous other things. No amount of theme options covered every scenario. I often resorted to walking non-coders through making changes to their theme templates.
\n\n\n\nExcept in the most complex cases, this problem no longer exists. Through the site editor, users can choose what appears.
\n\n\n\nI wish we had such a system a decade ago. It would have saved me hours of support work.
\n\n\n\nOf course, this is a simple example of what is possible with the site editor. Everything from changing bits of a template to creating an entire custom color palette is mere mouse-clicks away from reality.
\n\n\n\nHowever, the possibilities are not boundless. There are limitations that users will undoubtedly run into as they get more and more advanced with design ideas. Contributors have taken massive strides to get this first version ready for WordPress 5.9. And, there will be more to come.
\n\n\n\nThe most shocking thing for those who have been out of the loop will likely be the disappearance of the customizer, widgets, and nav menus admin screens. These components are replaced by the site editor when using a block theme.
\n\n\n\nThere are some known issues related to the customizer, such as no custom CSS option, live previews, or site icon setting. I covered this in more detail in a previous post.
\n\n\n\nNav menus are now handled via the Navigation block:
\n\n\n\nIt could take some getting used to. While I am a fan of the block system, I, admittedly, still prefer managing menus via the classic screen. However, I am starting to come around. The contributors who have been working on the block have made the experience far better than it was just a few months ago.
\n\n\n\nAs for dynamic sidebars and widgets, they are gone, at least in the traditional sense. Everything is a block now. Theme authors can create columns or containers that look like sidebars of the past, but they are all managed via the site editor. And, users can stick any block they want anywhere.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jan 2022 02:11:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:63:\"WPTavern: WordPress 5.9 to Introduce New API for Locking Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=128129\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/wordpress-5-9-to-introduce-new-api-for-locking-blocks?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-9-to-introduce-new-api-for-locking-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2675:\"The advent of block themes delivers more creative power into the hands of users, but there are times when theme authors may want to lock down key elements of a design and its designated content areas. First introduced in Gutenberg 11.6, the upcoming WordPress 5.9 release will include a new API for locking blocks.
\n\n\n\nTemplate level locking has been available in Gutenberg for a few years, allowing developers to lock the template on the UI so that users can’t manipulate the blocks. This new API offers more granular control that can be applied on the block level and override template locking.
\n\n\n\n“Instead of applying a lock to all inner blocks, you can apply it selectively to individual blocks via the lock attribute,” Marcus Kazmierczak said in the dev note. “The block level locking would supersede the inherited templateLock value. You can choose to lock moving or removing a block.”
One of the primary use cases for locking individual blocks, cited in the ticket proposing the new API, is where one might lock the “post-content” block of a single template so users can’t remove it.
“Another use case that we’re building for is having a Checkout Block with different blocks that act as fundamental steps, we don’t want people to delete or move those steps since they’re fundamental and their order is also important, but we want to allow people to select them, access settings, and insert blocks in between them,” WooCommerce engineer Seghir Nadir said.
\n\n\n\nKazmierczak’s dev note demonstrates how developers can lock a specific block in a pattern and explained how block level locking is not inheritable.
\n\n\n\n“If a block is locked from being removed, its children can still be removed,” Kazmierczak said. “If you want to apply locking on children as well, add templateLock to the inner block component, or templateLock attribute to supporting blocks.”
For more information on the new locking mechanism, check out the Block Editor Handbook and the code examples in the dev note.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jan 2022 21:01:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"WordPress.org blog: WordPress 5.9 RC 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=12014\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://wordpress.org/news/2022/01/wordpress-5-9-rc-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:4916:\"The second Release Candidate (RC2) for WordPress 5.9 is now available!
\n\n\n\n“Release Candidate” means the new version of the software is ready for release. It helps the community check that nothing is missed, given the thousands of plugins and themes and differences in how millions of people use the software.
\n\n\n\nThank you to everyone who has contributed thus far towards testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated for release in just two weeks on January 25, 2022. There’s still time to help! Since RC1 was released, six bugs have been found and fixed. There were 13 bug fixes backported from Gutenberg.
\n\n\n\nYou can test the WordPress 5.9 release candidate in three ways:
\n\n\n\nOption 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
\n\n\n\nOption 2: Direct download the beta version here (zip).
\n\n\n\nOption 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1, on a case-insensitive filesystem, please use the following command sequence:
\n\n\n\nCommand One:
\n\n\n\nwp core update --version=5.9-RC2Command Two:
\n\n\n\nwp core update --version=5.9-RC2 --forceYour help to test the second Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.
\n\n\n\nThank you to all of the contributors who tested the RC1 release and gave feedback. Testing for bugs is not just a critical part of polishing every release, it is also a great way to contribute to WordPress.
\n\n\n\nHelp test WordPress 5.9 features – a guide to how you can take part.
\n\n\n\nCan you write in another language other than English? You can help translate WordPress into more than 100 languages! Release Candidate 1 marked the hard string freeze point of the 5.9 release schedule. Thanks to every locale that is already involved with translations.
\n\n\n\nDevelopers and those interested in more of the background to the features can find more in the Field Notes. More developer notes will be added as the release progresses to its final stage. You can also follow the 5.9 development cycle and timeline.
\n\n\n\nIf you think you have found a bug, you can post the details to the Alpha/Beta area in the support forums.
\n\n\n\nIf you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.
\n\n\n\nProps to: @psykro and @webcommsat, and @hellofromtonya, @audrasjb, @cbringmann and @marybaum for final 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:\"Tue, 11 Jan 2022 20:43:58 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Jonathan Bossenger\";s: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:97:\"Post Status: Post Status Excerpt (No. 41) — WordPress Community Versions: Past, Present, Future\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=92231\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/41/\";s: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:68552:\"In this episode of Post Status Excerpt, David has an honest and deep dive with Bob Dunn into the “versions” of the WordPress community — something Bob covered in a recent blog post that has gotten some attention recently. They discuss what each “version” was like, how money can make a community act differently, and how people position themselves, for better or worse, in reaction to changes in the community.
\n\n\n\nAlso: David asks Bob if certain changes are unavoidable once a community gets to a certain size and asks what is missing from the WordPress community today that existed in the early days.
\n\n\n\n\n\n\n\nEvery week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash.
You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS.
Mentioned in the show: Sponsor: GoDaddy ProManage your clients, websites, and tasks from a single dashboard with GoDaddy Pro. Perform security scans, backups, and remote updates to many sites on any host. Check up on site performance, monitor uptime and analytics, and then send reports to your clients. GoDaddy Pro is free — and designed to make your life better.
\n\n\n\nDavid Bisset: [00:00:00] So as soon as I saw this particular post, which you did on November 23rd, it\'s called, are we in WordPress community version 3.0, as soon as I read this, first of all clicked with me and I knew I was going to talk to you about it, but you start off. It\'s a very simple post. It takes a minute to read it. If you are listening to this, now you should pull over to the side of the road, you know, stop watching your children.
\n\n\n\nStop paying attention to the world. Take five minutes to read this and then come back to this because this is basically all we\'re discussing. So I\'m going to allow you to, in your own words, to explain, I think the easiest would be version 1.0,
\n\n\n\nBob Dunn: you know, as I thought about this and I\'ll just preface it a little bit.
\n\n\n\nThis was after listening to Cory Miller and Josh Strebel. Talk about the acquisition of Pagely so I\'ve listened to the podcast and they were talking about community. And I started thinking through, because I had thought about this before, so right away, I thought what version are, where app, because
\n\n\n\nDavid Bisset: and [00:01:00] version.You think version because we\'re into software, right?
\n\n\n\nBob Dunn: I even do a change log for my website. I\'ve gotten into change logs. Cause I think they\'re so cool. And they can be more than four erotic
\n\n\n\nDavid Bisset: I do change logs for my kids, but I mean, that\'s another subject, but yeah.
\n\n\n\nBob Dunn: Yeah. And I love that it\'s so I thought, okay, the version, the first version is, yeah, it\'s when WordPress, it was before my time, you know, cause I didn\'t get into it till 2017, but I thought there was app time that WordPress was new and it was doing its thing.
\n\n\n\nIt was you know, the little bit of glitter in Mullenweg\'s Eye. And you know, that was it. It was just as simple as that version. 1.0, is those first few years as this kind of found its legs
\n\n\n\nDavid Bisset: that would cover the years from about 2004, I think to about 2009. Yeah. Based on yours. And I use 2004. I don\'t know if anybody wants to go back earlier, but that\'s when [00:02:00] WordPress 1.0 was released 2004 to 2009 was the first generation.
\n\n\n\nAnd I can tell you that I was, I came into WordPress maybe around 20, like encountering the software itself around the version when themes came out. So I\'m a little fuzzy on that. I was three, 1.3, 1.4. Maybe I\'m going to say 2005, maybe 2006, somewhere around there. And my dates could be off. So whatever I wasn\'t in the community, I was just by myself and I really didn\'t get into the community until maybe 2000.
\n\n\n\nSo I am kind of in the middle of that version 1.0, because word camp Miami was started. Like we got together in 2008, me, John James Jacoby, who was down here and a few other people got together 2008 is when we started rearing up WordCamp Miami, there was no foundation or anything like that. So version 1.0 was there was no WordPress foundation.
\n\n\n\nThere was maybe a couple of word camps going on at the end of 2009 work. Our first WordCamp Miami [00:03:00] would have been over by then, but we had no rules. We had people nationally would come because there were just so few word camps existing at the time. And you just expected the entire WordPress community.
\n\n\n\nIt wa it was that where it\'s like, are you going? It\'s basically there\'s nothing else to do for this month. Let me, let\'s get, let\'s go down to Miami. That\'s how I remember the WordPress community at the time. I remember any of the big contributors. There were very few names that you associate with WordPress contributions.
\n\n\n\nThere was mark Jake with um, he was a big name that you would talk about during contributorship at that time, but it was a really big pioneering days. I remember WP candy. I don\'t know if you remember WP candy, Brian, I believe I remember they covered our first WordCamp Miami, and they were just a bunch of people typing on laptops in the back.
\n\n\n\nAnd I didn\'t know that I, if I, man, if I knew him at the time. And our first work in Miami actually had a lot of people from the internet community involved like people, you would probably not no longer see it eventual WordCamps because [00:04:00] it was just generally about blogging customization. I did my.first BuddyPress talk, but it was just a room, maybe of 50 people listening to my presentation, but there was the WordPress community at a time that was just so new young, you would probably anybody you saw at that camper, the fewer there\'s at that time, that was the WordPress community. In a nutshell, anyone else that was doing WordPress at the time was just fiddling with it. You could go up and literally ask someone about a core ticket and it would only be melt maybe a half a dozen people that you would go up to a recognize and ask about a core ticket.
\n\n\n\nAnd they were co and there wasn\'t like a big committee back then, or a big, there was a team back then, but basically you\'re the, most of the team was sitting in the same room as you. There was no com contribution. There are no contributor days or anything. The people were actually committing code, I think, to WordPress during the conference, during the talks.
\n\n\n\nSo that\'s how like fly by the seat of the pants. It was. So that to me was word, press version 1.0. [00:05:00] Everybody kind of knew everybody else. It was like one giant meetup. Yeah. And a lot of the rules, the red tape or whatever it is you want to call it just simply didn\'t exist. Social didn\'t exist. Social networking really didn\'t exist.
\n\n\n\nFriendster, I think was the hottest thing in social media at the time. And then in the iPhone, didn\'t come out 2007. One of the biggest things was just seeing your website on an iPhone or a mobile device back then, too. So that to me was version one. And thank you for allowing me to indulge you, Bob, because I thought you were part of that and I just didn\'t see you because I\'ve just taken it.
\n\n\n\nI\'ve just assumed you\'ve always been around. I\'ve been feels that way. So version two, there is, so version two, according to your posts takes you from 2010 to 2018, and this is your Jen. This is your version, right?
\n\n\n\nBob Dunn: Right. He is because when, so I started dabbling in WordPress in 2017 and. So I was coming from having run [00:06:00] a business, or I was still running a business.
\n\n\n\nI was in the, I think 15th year of it, a marketing design business. And I was looking at WordPress for blogging, for creating sites, you know, building sites. Cause I wasn\'t a developer during that time. So I was involved with like the business community in those years, which was in real life.
\n\n\n\nYou know, you lived in the community and you related with other businesses. And in the early around that same time, there was a online site called dot com and it no longer exists, but it was a very unique one of the first endeavors in bringing people online and it started in Seattle and it actually grew nationally and was a bit international and it did a mix of in-person and online events and you\'d network and you\'d, you know, comment and talk to each other on it.
\n\n\n\nAnd it grew quite a bit. Yeah, I\'m not getting the whole story of that, but that was where I started to learn more about, or actually delve more into [00:07:00] the online community. WordPress just segwayed into my life easily. Cause I was already, you know, thinking community, you know, there\'s some kind of community wherever you go, of course, open source is very different to me.
\n\n\n\nAnd it was very embracing and it was like, wow, this is cool. You know, people are so different because it\'s not these chamber of commerce meetings. It\'s just a different feel to it. And I, you know, me I just started diving into it and by 2010 I said, okay, Totally closed down our other business and I\'m going to create this other brand that came up with Bob WP, which, you know, some people looked at me at that time said, you know, can I, why are you doing that?
\n\n\n\nDavid Bisset: It\'s like getting a tattoo. Right? It\'s like, listen, it seems cool now, but have you thought five years ahead?
\n\n\n\nBob Dunn: And you know, I, when I [00:08:00] started WordPress I started WordPress at the age of 50. So I was kind of different, you know, I mean, I had a different perspective cause I was later on in life. So I was looking at something new and exciting.
\n\n\n\nAnd I think that time I look back at it and I didn\'t realize it until later on in the years when I would talk to a lot of people that had been in the space at the same time. And I realized that they all were saying, yeah, you know, when I really got involved with WordPress was around 2009, 2010, or that\'s when I started.
\n\n\n\nYou know, there\'s all the big, you know, Yoast, gravity forums, all these ones that started around that period of time. And it just seemed like it was a time I came in at a prime time where there was this open innovation in WordPress where people were doing a lot of stuff and things are coming out left and right.
\n\n\n\nAnd it was just, it was fascinating and themes were, you know, growing more and more. And [00:09:00] it just, I just dove into it and I thought I\'ve got to get into this community because it\'s just seems cool. I mean, the people, you know, who I\'ve related to. So I think my first, I don\'t know if I did a word camp in 2010 by now I was in Chicago in 2011 and I spoke at that and I, again, just went full force into it and went to these, the first word camp, I word camp, and thought, wow, this is really cool.
\n\n\n\nBeing able to, you know, meet these people. And there was such a natural I don\'t know what you want to call it, but everybody seemed together. It was like,
\n\n\n\nDavid Bisset: don\'t worry, we\'ll flesh it out. We\'ll flesh it out because this is part of the reason why I want to get into this overall, because I mean, I don\'t, you know, we\'ll go into each, we\'ll go into a little bit more depth on each one.
\n\n\n\nI was just trying to make, you know, for somebody who hasn\'t read the post is not listening to me and reading this first. We have, so, and here\'s also about that time period of two. When we say [00:10:00] version two was around 2010 right before 2010 is when Sandhills development. Awesome motive started 2009 is actually when WP beginner was launched by Syed.
\n\n\n\nSo like we say, 2010. And I think that was a good cutoff time because I think in 2009, It needed a little bit of ramping up it didn\'t and a lot of other companies too, I\'m just picking -. It\'s amazing Sandhills and Awesome Motive and WP beginner started around that time in late, I think, late 2009s.
\n\n\n\nSo version 2.0, started in 2010. According to your post, it ran for about eight years, till 2018, which we\'ll get to why in a second. And between that time, like I said, it\'s when those companies that we, that the mergers that were acquisitions that we\'re hearing about today from quote unquote, big companies, a lot of them got their start at the beginning of the 2.0 era.
\n\n\n\nBob Dunn: Yeah, exactly.
\n\n\n\nDavid Bisset: And yeah, so I think that\'s, that was a perfect time in your blog post to kind of, you know, make 2009, 2010, the next cutoff [00:11:00] point, because I think like earlier, when we just talked about everybody was just. If you had a problem with WordPress and people, weren\'t really starting to build really good businesses around WordPress in version 1.0, if you were building websites and if you were making good money, you usually just a big, good agency or you\'re just building websites.
\n\n\n\nBut then 2.0 era started with the companies actually building commercial products with plugins or for tutorial sites. And that\'s how I think, that\'s how I saw reflecting back because I was too ignorant to realize what was going on at the time. How 2.0 started in that kind of, like you said, when you got into the game 2016, 2017 near the closing of that particular era, it was going full force by then.
\n\n\n\nI mean, there weren\'t really a lot of acquisitions happening in this era. It was just a lot of businesses being created.
\n\n\n\nRight. And there was a lot of people that I\'ve met that weren\'t necessarily, you know, like. Doing the big business or doing the big [00:12:00] products, but they, I was still amazing. How many? Yeah, I started my agency around 2009, 2010.
\n\n\n\nSo that, just that number kept coming back at me and I thought, wow, I made a lot of sense because it\'s how I felt when I got into it. It was like, okay, something\'s happened in here, you know, and I seem to got into this at a really prime point in time
\n\n\n\nthat, that period too probably saw the biggest or maybe most noticeable jump in WordPress market share.
\n\n\n\nAlso at the same time you had web 2.0, kind of take off in that same time period. So between the social between the boom and like the overall span of tech and I think this was when other competition from WordPress started to get a little further in the rear view mirror too. I think movable type was by this time period, probably.
\n\n\n\nFading in terms, I believe, I can\'t remember exactly when they changed their business model, but I believe it was early during this time period where you had this other, you had your choices in Joomla and Drupal were still very strong in this era, but they were becoming, [00:13:00] it was becoming the big three in terms of CMS.
\n\n\n\nAs in, at that time they were all the top three, they were open source. So that\'s and WordCamps to exploded. I think once we got to 2012, 2013, that\'s when you saw a lot of first-time WordCamps, startup and WordCamp, I think by the time that WordCamp Miami got to its fourth or fifth year, that\'s when we had to start coordinating with other word camps, you know, around the same time period to make sure we didn\'t have the lap and all of that.
\n\n\n\nSo, and we had buddy camps and we had our first kids camp, I think it was in 2015 or something like that. So by the time that happened, And I forget what WordCamp Arizona. I think I went to my first word camp in Arizona was working in Phoenix. I believe that was in 2013. Maybe. I don\'t know.
\n\n\n\nI have to Google ice Luiz WordCamp and figure out what I\'m really. I know. So that was 2.0, from 2010 to 2018. So Bob, when, tell us about what transition from version 2.0 to [00:14:00] 3.0 and your blog posts made you land on 2018.
\n\n\n\nBob Dunn: You know, I think it was, there was a lot of, I mean, it revolved around, but we\'re pressing was doing technically, I mean, you know, Gutenberg 5.0, all that stuff, because there was that huge shift at that point.
\n\n\n\nI think that people just started, I don\'t know. The climate changed and how people looked at it. And there was a little bit more, you know, yeah, people were anti this or they were, you know, reluctant of this. And is this changing for the best? I feel like things were changing in WordPress that affected the community in a lot of ways positively.
\n\n\n\nAnd in some ways people were a little bit reluctant and things were starting to get more into that mix of at, you know, not the boom, like it is now with the acquisitions, but. We were starting to see, you know, let me explain it this way. And this is kind of a strange way to [00:15:00] explain it. Maybe people won\'t really get it.
\n\n\n\nI always say I used to work in the real business world and that was outside of WordPress. And I\'m, it\'s a little bit of sarcasm there, but it\'s how, you know, regular business works, how it runs, how, you know, people get acquired corporations, all that stuff. I\'ve dealt with it in the past. I felt like that was a time that WordPress matured and thus the community had to start to accept that in the sense of this is becoming big business.
\n\n\n\nNow, you know, this is becoming a bigger thing then. Sure. It\'s open source still. There\'s that community there\'s everything that WordPress is, but now more and more people are taking note of WordPress more and more people are wanting to get into WordPress and it just. From the, around that time, I think it\'s just as grown more and more that attitude, the you know, and it is it\'s a [00:16:00] lot of people have pivoted or changed their mind on WordPress during that time.
\n\n\n\nAnd you saw more of that, I think, and maybe it always was happening, but it was just vocalized more as far as, you know, oh, I don\'t like the direction it\'s going now or, you know, I don\'t agree with it. And the, and that was cool. That was fine. I mean, everybody\'s got a right to, you know, do that. And also the other thing I think is this was when you think of all those people that started in 2009, 2010, that really started, this might be the moment they start thinking of different transitions as well, because they\'ve been in it for a while and that transition may be do an acquisition. They may be getting out of the space entirely moving on with their life in another direction. However, so I think we saw that bunch of people that were so in our view and in our, you know, that we saw them a day [00:17:00] in and day out, maybe after, you know, this period of eight years or nine years or whatever, they were ready to start slipping things a little bit in their own business or how they approach WordPress or how they approach their business.
\n\n\n\nDavid Bisset: Well, we\'re going to get into the community now more now that we know where, when we talk, we say version one, version two, version three, again, version one was from the beginning up to 2009 version. Two\'s kind of like 2010 to 2018 when Gutenberg was launched. And then version three is pretty much present quote unquote, present day.
\n\n\n\nRight. And who knows we may talk about another version. We\'ll see what. I\'m going to open up our post status conversation we had in here, like a day or two ago too. But so let\'s talk about the community a little bit in terms of, and it sounds like to me, when you, when we, both of us are kind of old timers a little bit we\'re both remembering back when the businesses were just starting to get off the ground.
\n\n\n\nWould you define version 3.0 [00:18:00] as, as basically more commercial,
\n\n\n\nBob Dunn: you know, in a sense it is, and it\'s probably viewed as more commercial because of the nature of open source. So bringing bigger businesses, bringing the model of, you know, business growth, acquisitions, how normal, I almost say normal, but how businesses in the real world that exists and how they.
\n\n\n\nGet together and how they merge now. They, you know, whatever direction they go. I think it\'s become a little bit more commercial, but I don\'t know if that\'s the exact word it\'s because it\'s, I think some people would say that I really think they would define maybe that and they would define it in the sense of a negative connotation to that commercial is become too commercial.
\n\n\n\nAnd that\'s kind of in the eyes of the viewer, you know, before, [00:19:00]
\n\n\n\nDavid Bisset: let me play devil\'s advocate for a second, because once money gets involved, it\'s like, whenever it\'s, how do I explain this? Like, if I have a good friend, I, and if I have a laptop, I\'ll give him the laptop. I won\'t sell him the laptop. Why?
\n\n\n\nBecause he\'s my friend and I, if there\'s something goes wrong, I don\'t want anything to damage that relationship. So when money comes into the picture, closer relationships tend to get a little bit more complex in my experience. That\'s just my experience. So do you think part of the, and we\'ll get into the good old days slogan in a second here, but do you think part of the resistance or part of the, maybe just general uncomfortableness of this new version that you call it is because it is more commercial, therefore money, you know, money hiring acquisitions, all of that is together.
\n\n\n\nSo therefore when you go up and talk to someone at a WordCamp, or you don\'t, you know, you have to be careful what you say. You have to be careful of how you talk outside of a conference room. You [00:20:00] don\'t want to say the wrong thing or be viewed as this type of person, which makes it a little more awkward, which makes limits it a little bit of your freedom, which makes, again, goes back to you being a little bit more comfortable.
\n\n\n\nDo you think that has anything to do with some people reactions?
\n\n\n\nBob Dunn: You know, I think you, I think that\'s a. I think it\'s pretty spot on because it is it\'s, you know, there is that level of walking the thin line. Sometimes you don\'t want to, you know, you maybe felt you didn\'t have to walk that so much before you could be a little bit more open and now there\'s too many buyers that could ignite, I think the money.
\n\n\n\nYeah. When people see now, I don\'t remember ever back the valuation or what you would think of, you know, we don\'t know often what, how much these businesses are being bought for, but the reality is, yeah. Now we\'re seeing that there is some tied dollar value to these businesses that have done amazing stuff for, you know, close to a decade or less.
\n\n\n\n[00:21:00] And yeah, that money kind of gets you like, whoa, you know, this is all feeling, not the same, you know, and it can be for some that it can be kind of a creepy feeling. You know, they feel like money is corporate and money is commercial and, you know, money talks and that\'s what drives everything.
\n\n\n\nYou know, lots of people are doing their businesses and that what drives them is to actually make a Duff to survive and have a decent life
\n\n\n\nDavid Bisset: or because, or somebody on stage talking about a certain subject because they have some sort of financial gain indirectly, perhaps, but even there. So sometimes I feel like some people don\'t take, I\'m trying to find the right words here.
\n\n\n\nAnd I swear, I\'m not going to edit this part out because I want people to hear the awkwardness in this conversation. Exactly. It\'s well, that person is doing that or broadcasting that because they have a business to run or their business is doing this in the WordPress space. And you know, that.[00:22:00]
\n\n\n\nYou know, that can be understandable in other industries, but for WordPress, I think it\'s kind of new if you\'ve been around it a long if you\'ve been in since version one or the early days since version two I don\'t know. I\'ve heard it. We\'ll talk about offhand comments in a little bit, but I pieced together some of the comments from Twitter, some things I hear over my shoulder word camps and, you know, and it\'s a very fine and respectable group still, but I know that, you know, I put on working at Miami for years and sometimes I get questions, like, why is this person on at this time?
\n\n\n\nSometimes it\'s purely coincidental often it\'s purely coincidental, but I get asked, you have to be more conscious of that back now than you were 10 years ago. And because I think it all boils down to money and companies and expansion and all of that but, you know, and which kind of leads me to my next question for you, Bob, in terms of money, just, you know, even if you put money in.
\n\n\n\nYou know, we\'re both community managers not just with not just with me with [00:23:00] WordCamps, but you know, w my, my, my daughter and my wife, they hold other communities and I\'ve seen communities grow over the years. I handle the local meetups along with a few other people too. I\'ve seen things grow.
\n\n\n\nI\'m also, I here\'s a side note for you. I use apple pro I use apple products. I wouldn\'t consider myself an apple super fan, but I\'ve used apple products for a long time. Like since I was in high school. And I\'ve done PC and windows over the years, but I mainly, I\'ve mainly been an apple person, but I\'ve noticed through the years, even before the iPhone came about, this was way before the iPhone apple came out with the iPhone when they were almost a bankrupt company, I\'ve been with them.
\n\n\n\nBut I noticed over the past decade as the company has gotten bigger, and this happens with other companies too, but in particular with apple, my experience they\'ve gotten, people have gotten more outspoken. More bold in their comments and click baity to an opinionated and whether or not that some of that is based on truth and you know, apple like any other company is not perfect, but [00:24:00] it seems like the bigger you get, the more criticism gets thrown at you in, regardless of what I can\'t think of a company that has gotten bigger over, you know, given enough time over the last 10 years, it has not had criticism leveled at them.
\n\n\n\nAnd I feel that once you get to a certain size from a community standpoint, not really from a business company standpoint market share, but that obviously has a factor into it too. Once you get to, once a community gets to a certain size and grows and you start to see bad actors just because maybe it\'s the scale and it\'s, and maybe when it\'s smaller, they were always there, but there was just harder to see for them to blend into the mass.
\n\n\n\nFor example, and we\'ll take this, we\'ll take this as an example, bad actors. What do you mean by bad actors? There\'s always people that want to scam other people or users and in when the WordPress was in version one very few times, have you saw people trying to scam other people? Because the community was so small, right?
\n\n\n\nThe, it didn\'t seem to happen [00:25:00] very often. And in same thing for like apple and WordPress community, didn\'t seem to be a lot of people trying to take advantage of trying to steal this. And, you know, cause you know, windows was the big one durability. You want it to target cause a lot of people used it.
\n\n\n\nI, so here\'s my question for you. Do you believe that any community wants to reaches a certain size is going to have certain problems? Like not just bad actors that want to scan, but just critics that just maybe feel like they need to, they feel like their job is to probably call. Accompany once it gets to a certain size, what do you think about that?
\n\n\n\nBob Dunn: Oh, I think that\'s right on, I mean, is it\'s so obvious because it\'s like success breeds.
\n\n\n\nI don\'t know if there\'s actually a saying, but success breeds craziness or something
\n\n\n\nDavid Bisset: I\'m gonna use that quote
\n\n\n\nBob Dunn: yeah. Yeah. Success breeds crazy days because it does, the more you become the bigger you become, the more of a tar more touch points you have and [00:26:00] you become that target. You do. And more people are going to be attracted.
\n\n\n\nCause there\'s some people that they live for, that they live for the big names or the, they want to be in the limelight in that community, but in a different limelight as a backnet bad actor, because that is it just, you know, Reproduces itself is going to, it\'s going to attract people and all it takes us, you know, a few to start it and more and more are going to enter it.
\n\n\n\nAnd that\'s what know, I I\'ve thought over the years is this is growing into what probably every community does grow into. It\'s huge. How can we not avoid? I think of, I could step back to the time when I was, you know, not online. I was in a business community that was a real life community town.
\n\n\n\nAnd as that town grew bigger and bigger, more businesses moved in and there were more that early. [00:27:00] That were running businesses and we\'d come in and they would always be there at whatever meeting or something criticizing something. So it\'s not anything new. I think it\'s very, I don\'t want, I hate to use the word natural, but I think there\'s no way around it.
\n\n\n\nI think with growth, you\'re just going to, that\'s going to happen and you have to know, the best you can do is it\'s, you know, as, as long as we, and you don\'t want to ignore, but you don\'t want to, I want to fire.
\n\n\n\nDavid Bisset: Right. And I want to make a good distinction here because not everything I say, negative things about WordPress all the time, too.
\n\n\n\nIn fact, I have created memes around certain things in WordPress. That\'s still annoying me to this very day. And you know, you know, like the number of admin notices on a dashboard has gotten me more likes on Twitter than I probably know what to do with. So. What, one of the natural things that comes when you, when your community grows is [00:28:00] that there is more to criticize.
\n\n\n\nSo there is, you know, it goes perfectly along with, yes, a lot of the criticism that\'s leveled against WordPress is legitimate. And everybody has different viewpoints in they\'re coming at it from certain angles. Somebody from this industry is obviously gonna feel stronger than someone who comes from this industry and so forth like that.
\n\n\n\nBut I just think that part of this, I think what has been a staple I\'ve I think in the version 3.0 is just the, has been maybe a little bit more cynicism than that I saw in the previous two versions. Exactly. Yeah. And as much, and like I told you, I think that comes with, I write that off as scale.
\n\n\n\nLike I said, when you\'re dealing with. In terms of like, you know, they were just a bunch of people, friendly people helping each other out on forums and all of that back in the day, just like we were like in the very early days of WordPress. And now there are so many people and because I guess a lot of people [00:29:00] have so much writing on WordPress too, that sometimes naturally it does come off as well.
\n\n\n\nIf my entire business of my entire life is running off of WordPress or companies like automatic that in my mind influence WordPress to a certain degree, then I should be the one or I should be in a position to say what I want or be critical of this or that in terms of leadership and ownership and all of that.
\n\n\n\nAnd I\'m not saying leadership and ownership, isn\'t a bad stuff in and of themselves, but it\'s not something that we saw in previous versions of WordPress.
\n\n\n\nBob Dunn: Right. And I think we also look at WordPress where it came along in the, in history. I mean, you know, short history, but we are, if you think of back from 2010 to now, how social has brought on the aspect of being able to vocalize yourself and it has brought out peoples that wouldn\'t normally, you know, you would, I mean, I could [00:30:00] look back at again, I\'ll go back to way back, you know, at a chamber of commerce meeting, we\'re all sitting around in person, nobody\'s going to jump up from different table to table say, Hey, you know, that business sure does suck.
\n\n\n\nOr, you know, why are they doing that? Or why did they buy them? Why is this all going on now? We\'re to a point where we\'re all
\n\n\n\nbehind journalists,
\n\n\n\nwe all got an opinion. And we got to, we got a place to make that opinion. So that has grown just historically in technology. I mean, you know, that has happened.
\n\n\n\nSo that then right along with it, WordPress has grown. So it\'s almost like this. There are both on the same level. Yeah, more people are able to get online and say exactly how they feel are most people are not shy about doing it.
\n\n\n\nSo what do you think here\'s a thinking question for your Bible. What do you think the WordPress community has today that it didn\'t have back in the early days?
\n\n\n\nBoy, that\'s a, wow. That\'s a good question. I think there\'s [00:31:00] just more,
\n\n\n\nWow. That\'s a tough one because I think it has okay to two things. One is it has more voices in it and I\'m not seeing voices as far as negative and positive and neutral voices. I\'m talking about voices, worldwide diversity countries, all the different cultures that are coming in. I think that. Really has changed things. And I think it\'s changed for the better obviously.
\n\n\n\nAnd again, kind of historically, you know, hopefully getting where there\'s more, you know, things are a little bit more equal. I know they\'re far from being equal, but
\n\n\n\nDavid Bisset: yeah, there\'s a table, right. Everybody gets to come to the table and hopefully that table has grown in size with more chairs available to fit.
\n\n\n\nBob Dunn: Exactly. Yeah. I think it\'s that. And I think innovation, I think is just, I think people feel, even though sometimes we feel that it\'s, there\'s so much stuff go, you know, there\'s so many plug-ins how can we do more [00:32:00] plugins? How can we do this? But again, naturally over time, I think we have a lot more at our disposal as far as.
\n\n\n\nBe more innovative with WordPress then, you know, back then, and that again is not necessarily the word press or the community is just how technology has evolved. So I think we, I think WordPress benefits from the time it\'s in, because of everything that keeps turning and sure we there\'s changes. And maybe some we don\'t like, and some we do, like, I think, you know, in the end they\'re still all going in the right direction.
\n\n\n\nAnd now those changes are technically within WordPress should hopefully reflect on the community and they feel like, okay, we\'re going in the right direction because we got to continue to grow.
\n\n\n\nDavid Bisset: Okay. Was it, you said two things, was that both of them or do you remember?
\n\n\n\nBob Dunn: It\'s really, it\'s kind of that feel of the community and the [00:33:00] diversity and that, and then it\'s an actual, more of innovation.
\n\n\n\nI think the technology now we have the, I really feel like the opportunities are. More open to everybody in the WordPress space, even though, you know, we think it may be overcrowded. I think there\'s still a lot.
\n\n\n\nDavid Bisset: Okay. So here, I asked myself that same question in the shower for unluckily for me, it was a 45 minute shower cause I wasn\'t leaving until I got an answer.
\n\n\n\nI think the communication from the quote unquote, the source has gotten better over the years. Unless you heard Matt Mullenweg speak from a word camp or in his blog, sometimes you were a bit, a little bit confused in the very on maybe late version 1.0 early 2.0 days in terms of heck maybe even further on to 2.0 days, what was happening with the project or what was happening with the direction of WordPress.
\n\n\n\nAnd this was before Gutenberg. You know, there were improvements. You could talk to people on contribute, you know, charter contributors and all of that. And there were new [00:34:00] sites keeping up. But I think once we started getting into what you call the version three, once Gutenberg ramped up.
\n\n\n\nBut I think, especially, I think maybe I\'ll say six months, it seemed like six months after Gutenberg was launched. It seemed like the communication was improving. I think Josepha, I\'m not sure when she became, she took her role and Incorrectly state her role here, because I don\'t want to do that. But she is, she has acted like a director or a pro like an overall project manager.
\n\n\n\nI\'m not saying that\'s her role, but she\'s been acting like that. She has been part of for a key part of the communication. Now for a while, in terms of trying to translate what the WordPress project is, the general direction of where it\'s going. And, you know, Matt did do that to a certain extent, but I don\'t think it was as often or as regular and as consistent as they\'re doing it now with the blog posts and Josepha, and there\'s even podcasts now with Josepha on them and so forth.
\n\n\n\nSo for me the communication and the openness about especially about [00:35:00] core is what we, I think we have today that really wasn\'t there too much in the early days, because there just wasn\'t enough time to talk about it. Now don\'t hate me. Oh, wait. There\'s a podcast is still young here. I\'m going to flip the question around.
\n\n\n\nSo what do you think is missing today from the WordPress community? But one looks back in the early days and say, oh, wow, that existed there. Or I even missed that. Fill in the blank. I
\n\n\n\nBob Dunn: need a long shower for that one.
\n\n\n\nDavid Bisset: This is going to be weird. Intermission music, but sure, sure. So by, so maybe stalling you a little bit here, you know, when you buy a car and you get that new car smell.
\n\n\n\nYeah. Okay. So it\'s gone and then your car can still be exciting. It can be wonderful. There\'s that honeymoon period. But what, and I\'m not pushing you into a negative or positive territory here, [00:36:00] but what do you think was existed in the early days that you can remember the works community that you don\'t see.
\n\n\n\nThat you don\'t see today as much.
\n\n\n\nBob Dunn: I miss a little bit of the and that I want to say it\'s the warm and fuzzy feeling. Cause that\'s not fair to say. It\'s kind of a little bit of the tighter community that was there when I first got into it. And what I mean by that is, and let me give you an example.
\n\n\n\nThis was very interesting and I get to bring up the, say the word smaller group. And I saw Matt Mullenweg in a different lens. At that event. He was walking around. I mean, it was a smaller group and he was really interacting with people and laughing. And he was kind of more in his element because he was with his eye.
\n\n\n\nSounds weird with his peeps. I mean, instead of this huge, you know, multi hundred or a thousand person conference, and sometimes I [00:37:00] miss that. And it\'s not an exclusive thing either, but those smaller times, I go back to a meetup. I remember the meetups I used to do in Seattle in the early two thousands.
\n\n\n\nWe\'d get like 70, 80 people and everybody was so happy and energized and it was fun. And you were meeting new people and there was this just constant energy that was going. And I think is just like probably anything in it\'s younger. I mean, even us as humans,
\n\n\n\nDavid Bisset: every time you go to a WordCamp, you\'d meet a ton of new people, a ton.
\n\n\n\nBob Dunn: Yeah, you do. And I kind, kinda miss that and maybe it\'s, you know, it\'s just that smaller. I miss the meetups. Like they used to be. I, and I know that is just, I, and not even this put us COVID aside. It\'s not even that it\'s just that I miss that [00:38:00] smaller local community that used to thrive. I think a lot more, that\'s got segmented and it\'s been segmented just because of the growth and because of the community is so big.
\n\n\n\nAnd there\'s so many people you\'re meeting, you know, another countries across the globe. There\'s a little bit of that I miss now, whether that could really come back. That\'s the thing, that\'s a big question. I don\'t know if it\'s really necessary to be needed, right. Again, but some I wish there was some way to still have those smaller groups and they don\'t have to be, you know, WordCamps on, I don\'t even know what they are, you know, and that would, of course would have to be, you know, when the time comes that you can actually do that, but there was something that was just a little bit different. That part of it, I miss, and I don\'t know there was there was the energy, maybe that was it.
\n\n\n\nDavid Bisset: It\'s kind of hard to put into words. You\'ve attempted to do that two days ago. I\'m going to share a link in the show notes for a slack conversation we [00:39:00] had. And I put up on purpose prior to this both Eric and Natalie said something about 2008, 2009, 2010. There was definitely. Definitely those were big years.
\n\n\n\nThere was some generations based on what people came into the community and what they were doing there. And then you said something around 2010 or so was very generational. There was huge pivots in the space around space, around growth during that time. And then someone responded and says that time was very unique.
\n\n\n\nIt felt like anyone with the ambition and drive could learn to create something special with WordPress. It wasn\'t something reserved for only a small group of corporations. And it looks like Eric made that comment there. So I guess it was you know, it was a gold rush period, but not just to make money, but also to make like relationships.
\n\n\n\nAnd here\'s the key when you said that earlier and forgive me if I\'m mispronouncing your name. Dave is David Lutes who says, yep. The hippie times are over. And it\'s not meant in a bad way. In my opinion, this is him still talking quote. It already has started a few years before Gutenberg, when more and [00:40:00] more sponsored contributors raised up.
\n\n\n\nAlso people became paid from day one when they stepped brand new into the WordPress community. And like he said, it\'s not bad. It\'s an evolution. It\'s got all the way to it\'s. He says it\'s all got gotten. Translating here, all gotten too big to handle, and I have tremendous respect for the pure volunteers out there.
\n\n\n\nSo hippie times are over or according to Dave loots here. And we\'ll put all of those links in the show notes. And by the way, just to remind you what you said, a response, you said you could be very well, right? The last decade could easily have pushed out three instead of two versions when you get down to the nitty gritty.
\n\n\n\nSo, yeah. Wow. Yeah. Hippie times are over. So like I\'m always never, I\'m not that old to appreciate the hippie times of the sixties, but I\'ve read about it enough and I can see where there was a time I\'ve heard that phrase repeated elsewhere in terms of, okay, the hippie era is over and now I actually have to have a real job and a real business.
\n\n\n\nAnd that whole time of peace and love was great, but we were young. And [00:41:00] do you think maybe that\'s part of what maybe is missing a little bit from WordPress
\n\n\n\nBob Dunn: and it\'s that, yeah, it is that time of having that. It a freedom. I mean, and especially if you had the experience of it, you know, if you did, you were, you came in at some point there, it is nostalgic and I\'d love Dave\'s, everything you said in there because it\'s true.
\n\n\n\nIt\'s like anything. I mean, hippie times never, you know, except for some people that are stuck being hippies for their entire life or something they\'re going to end at some point and they\'re nostalgic and they\'re good. And you probably know it, won\'t go back to that. You know, you know that in your heart, but
\n\n\n\nDavid Bisset: seems like the harder you fight it.
\n\n\n\nYeah. The change is inevitable. And I think for the rest of those, I think for the rest of the lifetime of WordPress, there\'s going to be a healthy dose of criticism that follows it. So w so as WordPress grows is going to be scrutinized by some people for how it grows [00:42:00] and when the market share stops. Or there\'s less contributions or something noticeable starts to slow down.
\n\n\n\nThere\'ll be another round of WordPress criticism problem. You know, like the apple is doomed or WordPress is doomed by probably those same people. Right. Do you think people should accept the generational changes in the WordPress community? Or how should they look at it?
\n\n\n\nBob Dunn: Yeah, I think it\'s really, I hate to say it\'s both ways.
\n\n\n\nI mean, you got to accept it as globally. You got to accept that this is, you know, if he can\'t be a bit flux flexible, then you shouldn\'t be in any part of the tech space. You know, you got to have some flexibility and you\'ve got to not become the old grumpy man and saying, this is how it was and why we\'ll never be that way again, you know, so globally you need to accept it.
\n\n\n\nIn your own community, because how we\'re all defining communities is going to be different. How you define it. Maybe one way somebody else defines another way. Somebody may [00:43:00] have 200 people they think of as this is my WordPress community. You can still make changes within the smaller community that can blossom out into different ways into the bigger community.
\n\n\n\nI mean, you\'re not, you know, if we\'re talking WordPress community, every builder, then that\'s a lot, every builder and user, then that\'s an exponentially a lot. So I think that you can make small changes and I don\'t think you should ever say, I\'m just going to roll over. And you know, if I don\'t think this is right, you know, you don\'t have to nag and moan and groan on Twitter day after day, but you can fight.
\n\n\n\nCreative and useful ways to try to work towards, you know, if something really, if you think it needs to be changed, I would never say people should back down you know, unless it\'s really detrimental to the community, then that\'s maybe when you want to step back. Okay.
\n\n\n\nDavid Bisset: I, a lot of times the, [00:44:00] if there are people that rubbed me a little bit, the wrong way and listen, it\'s be honest.
\n\n\n\nI mean, there are people that do that. It\'s human nature, right? It\'s not what they say is sometimes their approach to it. And I have a lot of experience sometimes working and talking with people because we\'re cam Miami has allowed me to be like, sometimes I would deliberately put people in WordCamp, Miami lineups to offer those opinions.
\n\n\n\nAnd sometimes. It\'s just their personal nature. Sometimes it is you know, I, if I run a, if I wanted to write a tell all book, just on what I know about certain people on working in Miami, it would be controversial. A lot of people probably wouldn\'t like me, but that\'s fine. But there are some people that like, feel their message is so important.
\n\n\n\nThey, it boosts their ego or it boosts their, like, they feel like this message is so important. They need to get outside the lines to be able to tell it whether how effective that is or whether that strikes the right chords or not. I mean, go you do you, you know, that\'s not really my, you know, I\'m not in charge of WordPress messaging.
\n\n\n\nBut you know, if you want to, if you [00:45:00] feel something so important that you communicate it, I mean, as long as you\'re not hurting others, I mean, feel free to give it a shot, just watch on any reaction or reaction to that. But it\'s also funny too, that some people, when we talk about the WordPress community, some people says I\'m leaving WordPress, I\'m leaving the WordPress committee.
\n\n\n\nOr they stop or stop using WordPress oftentimes in my experience, and this is over 10 years, this is not any particular case, but over the 10 years where people have said that you still see them on Twitter, or you still see them in the WordPress community, talking with the same people, almost like nothing ever happened.
\n\n\n\nAnd I, and sometimes I think these people, whether the legitimate reasons or not you know, they\'re trying to make a statement. It says I\'m leaving WordPress, but they\'re not really leaving WordPress. WordPress is the community and of itself, regardless of like, maybe you\'re not using the software or you put your pretty much, nothing else has changed.
\n\n\n\nSo if you\'re using it to make a statement, whether you\'re using WordPress or not, congratulations, you\'ve made. Or maybe you\'re taking a break, you know, those people that make the big announcements, I\'m taking a break from Twitter and they\'re making a big hoo ha about it. Like maybe celebrities or something like [00:46:00] that.
\n\n\n\nAnd you\'re like, okay, maybe you\'ll be back. Okay. You know, once, once it\'s died down or whatever, but I think some people like to have their cake and eat it too, where like, I\'m making this big statement, but I can\'t really, I don\'t really want to leave the community because there\'s some good things in it.
\n\n\n\nYeah,
\n\n\n\nBob Dunn: exactly. And I think they\'re trying to stand up there. They think that, you know, it gives a, it shows the side of their strength. They want everybody to think that, oh yeah, they\'ve been there standing up for what they\'re really, you know, they\'ve kind of walking the talk. Finally, they\'d been saying all this, but then like you said, you see, oh yeah, they\'re still wandering around bed in there.
\n\n\n\nI still see them popping up here and there. And it\'s like, you know, you\'re just. Kind of toned down a little bit maybe,
\n\n\n\nDavid Bisset: and you know what that is within the right to there. Like I said, however you want to get that message out is however you do. But I just think that\'s so interesting that the community of it itself is more, is stronger sometimes than the software.
\n\n\n\nBob Dunn: Oh, it is. It is. And I think that\'s what most, I [00:47:00] agree with you with a lot of people saying, you know, oh I\'m going to leave the community, but you know, I couldn\'t quite leave this part of it or this part of it. And they\'re not saying they\'re not literally saying that, but they\'re doing that through actions.
\n\n\n\nYou can see that they\'ve gained a lot of great relationships with some people and they can\'t let go of that. And that relationship in turn still connects him with WordPress. So they, and connects them with the community. So, yeah it\'s interesting human. Nature\'s
\n\n\n\nDavid Bisset: interesting. Yeah. And of course there\'s always legitimate reasons.
\n\n\n\nLike if there\'s, if you like, you\'ve people have felt like legitimately they\'ve been neglected, abused, all of that stuff. That\'s not really taking care of that part cause that\'s kind of a toll different, totally different ballgame. So yeah. So do you feel, so here comes, our, here comes as we close out this conversation, which has been fantastic by the way.
\n\n\n\nI think we only mentioned WooCommerce only a few times. I haven\'t said it enough for something like WooCommerce to appear in a mirror or something like that [00:48:00] instead of three times, probably yet. But here\'s the two remaining questions I wanted to jam with you about one. What do you think version four would be?
\n\n\n\nHas it happened? Is it happening now or do you think we\'re not, we haven\'t seen that yet.
\n\n\n\nBob Dunn: You know, that\'s weird because I know you had warned me that you might ask about that.
\n\n\n\nYeah. And I have pondered on it a bit and I thought, you know, yeah, maybe I could have some, a wishlist of what I\'d like to see, but you know, I think it\'s going to be.
\n\n\n\nWhere this commercial part we\'ve talked about, becomes a little bit more leveled out. I think four is where we don\'t get all excited and, you know, acquisitions no longer are like the biggest news in WordPress. They Almaz say they become everyday normal things and people will still talk about them.
\n\n\n\nBut I think those moves that we\'ve been [00:49:00] making to where we see that it\'s becoming a bigger thing. And I also see that 4.0 is, and it\'s already, maybe it is already happening. I see a lot of attraction even more so I\'m more visibly from outside. Businesses, you know, that say, I want a piece of WordPress. I want a piece of WooCommerce.
\n\n\n\nI mean, I get this a lot through conversations and companies that reach out to me, you know, they want to get in on it. They want to get in on the action. So that\'s almost like an, and however people view that, you know, that they view that as positive or negative is not really the point that, but I think that is becoming people are companies are being a bit more visible.
\n\n\n\nAnd I think this will be part of 4.0 is in their interest in WordPress where it used to be WordPress is [00:50:00] open source and you know, it\'s not that big of a deal and stuff. And now it\'s like, they\'re flat out saying, Hey, we want in, how do we get in? We want to be, because
\n\n\n\nDavid Bisset: it\'s like we said, it\'s a little hot about the money.
\n\n\n\nBob Dunn: Exactly.
\n\n\n\nDavid Bisset: Once you see these aquifers, I think, you know, like once you start seeing bigger acquisitions, they\'re taking headlights now in tech crunch, all these other things, people are starting to, I guess, pay attention. Oh wow. There is money to be made here. So I\'m yeah. I mean, I want to I, wouldn\'t thinking about the same thing and I don\'t have a year in mind yet.
\n\n\n\nOf course, if I did, I\'d probably play the lottery or something, but what I see are four potential factors for version four, if you want to call it that, and maybe they all are playing. One, I think we\'re in, I think we\'re version three still includes the acquisitions craze that we\'re going through right now, because I think the acquisitions, if you look back a little bit far enough after Gutenberg, I think launched. To me, it just seemed a lot more common.
\n\n\n\nIt\'s really exploded the last couple of years. I don\'t think it\'s over, but I still think we\'re in the same general [00:51:00] time period acquisitions were happening before Gutenberg came out, but I think Gutenberg probably has triggered a lot of companies, smaller companies for, to be acquired by hosting companies and others because of the blocks, the themes and all of that.
\n\n\n\nAnd of course, we\'re not even going to talk about theme, you know, WordPress themes at all, or we\'re not even about WooCommerce or e-commerce, I\'m not even going to talk about that stuff cause that\'s too much. But I think if I was to guess what a version four would be, and this is commute, this it\'s sad because I\'m not talking much about the community.
\n\n\n\nI\'m just thinking of the, community\'s going to react to these things. And that becomes version for the community outside investments. How we react to that outside investments might mean more people coming in from the outside, even if it\'s just from a business standpoint, but they would be part of the community.
\n\n\n\nI think too, it\'s possible than an aversion for maybe near the end of that. We will see acquisitions, maybe become normal, more normal. But I think we\'re also going to see market share eventually [00:52:00] level off. And that could be years from now. It\'s going to be hard to calculate it because they\'re shutting down Alexa, not that Alexa, the other Alexa next year.
\n\n\n\nAnd we don\'t know exactly how we\'re going to be able to determine them at the market share metric because we\'ve kind of taken advantage and abuse it over the years. But I tend to see a general acquisitions being more of the norm market share, not as explosive as it used to be, because quite it\'s kind of like apple.
\n\n\n\nIt\'s kind of, again, I go back to apple, they were selling iPhones one year. That would, their total sales of iPhones for one year would be all of the sales for the previous years combined. And they had that kind of explosive growth. Then it stopped because you couldn\'t sell that many phones anymore. But look at them today.
\n\n\n\nThey\'re doing just fine. They\'re doing just fine. So I think that\'s going to be the way with WordPress. We\'re going to see market share slowed down because quite far, I mean, whether it gets to 50% or not, I don\'t care. It could be beyond that. It could be years from now, but eventually the market share has to slow down.
\n\n\n\nAnd then I\'ll ask you a [00:53:00] question about market share in a second. I think acquisitions nor market share slows down. We\'re going to get more, you know, outside investments. We\'ll see those. And then I think matt\'s master plan. Maybe I\'m not sure what you would call this his plan of an open web.
\n\n\n\nIf you looked at the acquisitions and I\'m not sure if you had the read the piece by David Pierce yet on ma on mat, it was a click baity title. It was can Matt Mullenweg save the internet if you haven\'t read it because it basically folk you would think, oh, it\'s a piece about Matt WordPress and yes it is, but it goes along also the acquisitions automatic has taken over the past couple of years and individually by themselves were like, oh, that\'s neat. They have this little thing. But if you add them together, Matt is slowly accumulating like a collection of these technologies and these corners of the internet that I think needs to be maintained as open, like a diary app and a photos on creative commons.
\n\n\n\nAnd there\'s analytics, statistics company that they acquired that I can\'t remember the name of, but it\'s like, he\'s collecting almost one of each or automatic is collecting one of each of [00:54:00] everything. And I think that is going to change. Maybe it\'s making the community more open source minded than WordPress minded maybe, but I think there\'s a cat there.
\n\n\n\nThere\'s going to be some change. There may be an, a version four, maybe a version five. However you want to split it where we\'re going to see, like we\'re going to be so more fighting for the open source or the open web. And WordPress is just going to be part of that. In fact, I think didn\'t Matt say that Gutenberg is going to be bigger than WordPress. Yeah. Yeah. That\'s a state of the word. So if I had to guess that\'s my version for, I don\'t know, that\'s it. And the
\n\n\n\nBob Dunn: only other thing I\'d add, and this is more around the people side of things. I\'m really curious that by version four, if we will have a bigger turnover in who you really notice in the WordPress space.
\n\n\n\nI mean, we got all these people that I\'ve, you know, kind of are the faces we\'ve been around forever. We\'ve seen them, is there going to be a new generation and a kind of influx of newer [00:55:00] people stepping up and taking over the roles in the bigger WordPress community. And some of the other people that have been in a while might be at that point in time.
\n\n\n\nAnd maybe again, we can\'t get 4.0 will start, but will they be stepping back and maybe doing other things with their lives? And it\'ll be this. This whole new kind of, even though each one has been a generation in its own, that might be a more pivotable generation. That with, when you look at the kids and what your kids are doing, I mean, what so many of them are doing that they could come in and just, you know, barnstormed the place and ,
\n\n\n\n, but you see it, like how many P how many original people of the original tech companies are still around Microsoft?
\n\n\n\nNo bill gates has gone even his can\'t remember his name now developers, guy has gone. The original owners are starters of Google aren\'t there anymore. All of in fact, I think an apple of course, has a leader. They\'ll probably transition like, like the only person left is Zuckerberg is still a [00:56:00] Facebook.
\n\n\n\nEveryone else has had one or two leadership changes. Very recently, Jack is no longer Twitter. So we\'re seeing that, but also in the WordPress space you know, the advanced custom fields, Sandhill development these people that have been like the starters from day one, they\'re moving on, whether they\'re moving on retiring or they\'re moving on to other projects or other companies through acquisitions is up for debate or whether it\'s, they\'re doing, but we\'re seeing the same thing happen in the global tech community.
\n\n\n\nSo exactly. So, yeah, I, wow. This has been a really deep conversation about community, but I didn\'t think, but it was all because of your all because of your blog posts really. And that\'s really
\n\n\n\nright. I wrote it and I wrote the, I titled it in a question because I thought, okay, this is just a little snap, a snapshot in my brain.
\n\n\n\nAnd I want people to think about this and I love that you did this. And I loved hearing on slack and hopefully, you know, this might. Inspire some some blog posts, cause I\'d love to hear other ideas and stuff. [00:57:00] So, so, it did its job and that, that\'s what I wanted it to do. Get people thinking about
\n\n\n\nDavid Bisset: it. I know I\'ve taken too much of your time already talking about this.
\n\n\n\nIt\'s like, what else am I going to do? And we got to go out and do, let me direct you to one last thing earlier today, because I don\'t plan enough far enough in advance for half of our conversations. I put up a Twitter poll and that\'s going to run for another two days. So, while we\'ve been talking about here, strangely enough, we\'ve had at least 10 people vote on it and it\'s only been.
\n\n\n\nThree or four hours since I put the vote up has been over 40 votes on it so far, but for a Twitter poll for me, that\'s on a new year\'s Eve. That\'s pretty good. So I asked based on your post, where do people feel they belong in terms of what WordPress generation and I we\'ve listed the version one version two, version three, and then whatever, if there\'s other than replying, the comments nobody\'s replied other yet.
\n\n\n\nSo they pick one or two or three. So after 41 votes, let\'s see, just making sure I got my numbers, right. [00:58:00] 41 votes. So 39% responded version one. This is 36% version two. So that\'s 2010 from 2018 and 24% said two to 2018 and above for version three. Interesting. So it\'s, you know, it\'s only 40 votes if it was more evenly split between thirds the last time I saw it, but you are getting a little bit more.
\n\n\n\nA slightly older people are older versions. Yeah. So I just thought that was interesting. We\'ll link to this in the in the show notes as well. So by the time you hear this recording, this poll would have ended long ago. It should be interesting to see what it ends up being. Yeah.
\n\n\n\nThat\'s fantastic. Was there anything else that we didn\'t cover about that post that you think we should have?
\n\n\n\nBob Dunn: No, I think we, we dove into a deep, yeah, we
\n\n\n\nDavid Bisset: killed, we deep dive and killed it, buried it. We used every part of the Buffalo. Yeah. Bobby could be
\n\n\n\nBob Dunn: and now, everybody else can chime in and create their own posts and create their own tweets.
\n\n\n\nAnd [00:59:00] then talk about this. Yeah. Yeah.
\n\n\n\nDavid Bisset: You know, besides Bob, other than my wife, you\'re the only adult I\'ve spoken to in the last couple of days. Anyway. So maybe it\'s nice to have a good conversation. We don\'t have WordCamps anymore. This is the type of conversations I\'d love to have. Right at word camps.
\n\n\n\nAnd it\'s the parts that, that I miss the most, but we can still do them up to this point. And I\'m looking forward to that time where you and I can sit together and talking you know what? Version three is coming to a close, or maybe we\'ll say it probably a year after it\'s happened. Cause you know, retrospect is Einstein sights, 2021.
\n\n\n\nAnyway, Bob tell us where people can find you or version two, but on the web.
\n\n\n\nBob Dunn: Okay. I\'m version two. Best place I hang out a lot of on Twitter, you can either @BobWP or @dothewoo depending on what you want to do. Bob wp.com is I\'ve kind of revived that blog. I took all the WooCommerce stuff off and I\'m basically just talking about community.
\n\n\n\nSo these kinds of little thoughts come to me and that\'s what I\'m going to be putting there. And if you want [01:00:00] to, you know, again, woo commerce do the blue dot on.
\n\n\n\nDavid Bisset: Okay, great. Yeah, and like I said, check the show notes for this episode. We will throw Bob\'s link to his blog post in there, specifically this Twitter poll that I did and a few other tidbits as well.
\n\n\n\nBob, it has been awesome. Thank you very much for sharing all this thoughts with us. And I really hope this at least brings a couple of ideas and thoughts into people\'s heads, not just ones that have come into the WordPress community recently, but also the ones that have been around with it since version one, maybe, or version two, we\'ll see where the poll ends up.
\n\n\n\nBob Dunn: Cool. Thanks, David. This has been a blast. Thank you.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jan 2022 04:55:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:107:\"WPTavern: WordPress Community Team Proposes Stricter COVID-19 Safety Protocols for In-Person Events in 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128077\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:259:\"https://wptavern.com/wordpress-community-team-proposes-stricter-covid-19-safety-protocols-for-in-person-events-in-2022?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-community-team-proposes-stricter-covid-19-safety-protocols-for-in-person-events-in-2022\";s: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:6953:\"Mounting concerns about loose safety protocols at upcoming WordPress events, and the prevalence of the highly transmissible Omicron variant, have prompted the Community Team to be more explicit in its COVID-19 safety guidelines. The team is proposing additional measures previously not required.
\n\n\n\nCurrently, in-person attendees are required to be fully vaccinated, recently tested negative, or recently recovered from COVID-19. Every one of these requirements is vague and open to multiple interpretations. Recent spikes in infection in both vaccinated and unvaccinated populations has caused the Community Team to propose the following:
\n\n\n\nOne of the concerns with imposing more mandatory safety measures is enforcement. WordPress events are generally hosted by volunteers who would now need to go beyond simply facilitating an event to being ready to confront and remove those who don’t comply with safety protocols. In a community of people with diverse convictions, what happens if some members decide that WordCamp is a good place to protest pandemic restrictions?
\n\n\n\n“I appreciate very much the heart behind wanting to keep the community safe, but have significant issue with how this is being proposed, and how it would be enforced, and how it shifts the burden of health and safety to a volunteer team of organizers who are not in any way trained or equipped to handle making medical decisions,” Ben Meredith said.
\n\n\n\n“Further, there are many jurisdictions where the proposed changes (like a mask mandate) are specifically prohibited by local law or executive order.
\n\n\n\n“Trying to make a policy from the international level (WordCamp central) that applies fairly and equitably to all local jurisdictions is a fool’s errand. What works in Los Angeles probably wont in Louisiana or Lagos. That’s why organizers are local.”
\n\n\n\nIf the WordPress community is fixed on hosting events at this time, then there are many more responsibilities organizers are now obligated to assume in order to ensure the safety of attendees. Participants in the discussion on the proposal raised dozens of questions about how these new safety measures might be implemented.
\n\n\n\n“On temp checks, if someone reads high ( they may not even be aware) would we then refund their ticket to the event assuming we are talking a WordCamp?” Laura Byrne asked.
\n\n\n\nWordCamp organizer and speaker David Ryan raised questions about masks, will the requirements outline what qualifies as a mask? (“Does a plastic face shield qualify as a mask? Are masks with ventilation valves acceptable? A bandana?”) Does the requirement include speakers while they are speaking? “This should be clear in advance for both speakers and attendees to make informed choices without surprises day-of,” Ryan said.
\n\n\n\nHe also asked if the masking policies extend to other venues, such as the official event hotel and after parties, the way the Code of Conduct applies.
\n\n\n\nRefunds are another consideration. Will WordCamps refund people who test positive right before the event? Will the event refund if people arrive and are not comfortable or are asked to leave for not complying with the safety measures?
\n\n\n\n“In addition to these proposed guidelines, I also recommend that we remove our existing guideline of allowing recent-recovered community members from attending a WordPress event since new COVID variants like Omicron are known to cause reinfection,” Automattic-sponsored WordPress Community Wrangler Hari Shanker said in the proposal.
\n\n\n\nLaura Byrne urged the Community Team to clearly define this guideline.
\n\n\n\n“We are in for a boatload of trouble with the word ‘recent,\'” Byrn said. “In other words, something along the lines of, ‘anyone who has tested positive for COVID may not attend a WordPress event until X days after they are no longer testing positive.\'”
\n\n\n\nSome participants in the discussion see the additional safety measures as an overreach for WordPress events. It’s easier and more straightforward to recommend organizers stick with local requirements for anything related to health safety.
\n\n\n\n“Surely I’m not the only one thinking that the foundation shouldn’t be setting health guidelines at all?” Cameron Jones said. “Compliance with local regulations should be the only requirement.”
\n\n\n\nThe problem with this is that many locations and regions do not have any kind of precautions in place, due to political differences, or are slow in recognizing emerging threats. Lax local guidelines for large gatherings may leave the WordPress community vulnerable to outbreaks.
\n\n\n\n“As a WordCamp organizer and speaker, and more personally as a recent cancer survivor and immunocompromised person, State of the Word was a troubling event to observe,” David Ryan said.
\n\n\n\n“Local legal requirements were met, but not proven event practices that eliminated or greatly-reduced positivity rate at larger gatherings in 2021 compared to the results of SOTW (namely, masks and testing). Planning, day-of and response afterwards didn’t inspire confidence this community was prepared to run safer and inclusive events — so this is an encouraging step towards remedying concerns many have expressed.”
\n\n\n\nComments on the proposal are open until January 22, 2022. The Community team plans to assess the feedback and finalize the updated guidelines in time to publish them to the handbook in early February 2022.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jan 2022 04:27: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: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:81:\"WPTavern: Customizer Will Disappear for Some Block Theme Users With WordPress 5.9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=128089\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:207:\"https://wptavern.com/customizer-will-disappear-for-some-block-theme-users-with-wordpress-5-9?utm_source=rss&utm_medium=rss&utm_campaign=customizer-will-disappear-for-some-block-theme-users-with-wordpress-5-9\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5712:\"Nine years ago, the customizer had a rocky start among theme authors and users. Despite this, it has become the standard for modifying the look and feel of a website. Developers have become comfortable with the API. Users have grown accustomed to adjusting colors, fonts, and even internal WordPress options through it. However, it will disappear for many once a block theme is activated.
\n\n\n\nI began writing this post on the upcoming block-based theme system and site editor. However, I spent so much time explaining the customizer changes that I thought it best to focus on that aspect to let users know their options if they run into a snag.
\n\n\n\nIt is also a follow-up to a post I published in October 2021 on the same subject. Since then, some things have changed.
\n\n\n\nWordPress 5.9 will launch with several of the final components of Full Site Editing. The centerpiece of these features will be a new theme system, which allows themers to build designs entirely out of blocks. Once such a theme is active, users can edit their site’s front end via the site editor and global styles system.
\n\n\n\nThe site editor is, essentially, the next iteration of what the customizer aimed to do. The difference is that users can now customize every aspect of their site’s front-end and not just configure the options their theme author made available.
\n\n\n\nFor many block theme users, the disappearance of the customizer will be a non-issue. However, three missing options have no exact equivalent:
\n\n\n\nTechnically, the customizer is available via /wp-admin/customize.php. Even though no links to it are shown in the admin, any user with the requisite permissions can access it via that URL. At the very least, the first two issues can be mitigated by editing options in this way. It is not ideal, but it will work in a pinch.
The Site Logo block has a “use as site icon” option. This is a quick and easy way to update the logo and favicon via the new site editor, assuming they use the same image.
\n\n\n\nIf they are different images or if the user does not use a logo, the only built-in way to change the site icon directly is through the customize.php URL trick mentioned above. The Site Logo block also adds a link to the customizer option. Users can also opt for one of the dozens of favicon plugins.
A custom CSS solution in core WordPress is unlikely to be reimplemented in the site editor. The global styles panel and per-block design options are the future of styling. This makes many of the most common stylistic tasks much easier for non-coders. In the context of block-based themes, the average user is unlikely to need the CSS editor in the customizer.
\n\n\n\nHowever, there are situations where custom CSS is necessary. Again, the easy answer is to access customize.php once again. For a more dedicated solution, there are numerous plugins available.
There is currently no solution for live previewing and customizing inactive block themes. With classic ones, users can test customizations before activation. In the customizer, block themes will appear with a warning message.
\n\n\n\nOnce a block theme is activated from the customizer, WordPress will return the user to the Appearance > Themes page in the admin. They can then modify their site via the site editor.
\n\n\n\nHowever, this can be problematic for some sites. Just about any theme change will mean there is at least some customization work in order, and most people will not want their visitors to see an unfinished site. Working from a dev or staging site before migrating the changes is ideal. However, that option is not always available or even easy to figure out for everyone.
\n\n\n\nAnother solution is to install a maintenance-mode plugin if working on a live site. This way, visitors will at least know some changes are happening under the hood and that they can return later.
\n\n\n\nThere is an open ticket for previewing and editing inactive block themes. As ticket creator Anton Vlasenko wrote as the proposed solution, “It’s simple: we need to implement that feature.” In the long term, this is a must-have feature.
\n\n\n\nThere is one situation where the customizer will still be accessible via the admin menu and toolbar. WordPress will automatically detect when a plugin or theme hooks into the customizer and make links to it available. I like to think that my first post covering block themes and the customizer raised awareness of this issue. At the very least, we now have a fix in place.
\n\n\n\nAssuming there are no other changes in the next two weeks, this is how the customizer will function when paired with an active block theme.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jan 2022 00:22:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s: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:138:\"Gutenberg Times: Gutenberg Changelog #58 – Gutenberg 12.2 and 12.3, WordPress 5.9 RC and DevNotes for Full-Site Editing and Block Themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://gutenbergtimes.com/?post_type=podcast&p=19982\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://gutenbergtimes.com/podcast/gutenberg-changelog-58-devnotes-for-full-site-editing/\";s: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:8312:\"Birgit Pauli-Haack and Grzegorz Ziolkowski talk about WordPress 5.9 release and DevNotes for Full-site Editing and block themes, and Gutenberg 12.2 and 12.3.
\n\n\n\nSubscribe to the Gutenberg Changelog podcast via your favorite podcast apps!
🎙️ Spotify | Google | iTunes | PocketCasts | Stitcher |
🎙️ Pod Bean | CastBox | Podchaser | RSS Feed
Show Notes
\n\n\n\nJessica Lyschik (Question tweeted)
\n\n\n\n[Paragraph Block] add font family support
\n\n\n\n\n\n\n\nThank you to Jessica and Aditya for your great questions!
\n\n\n\nIf you have questions about Gutenberg, Block Themes or Full-site Editing, email us changelog@gutenbergtimes.com or DM on Twitter @gutenbergtimes or WP Slack.
\n\n\n\nState of the Word 2021 on WordPress.tv
\n\n\n\nQ & A after State of the Word on WordPress.tv
\n\n\n\nJosepha Haden: State of the Word 2021 | Q&A
\n\n\n\nAbout Themes
\n\n\n\nBlock Building and extending Gutenberg
\n\n\n\nNew Blocks
\n\n\n\n\n\n\n\nIf you need additional reading or if those are too developer centered for your taste, Birgit collected additional resource to a Reading List for developers, designers, site builders and content creators.
\n\n\n\nWordPress 5.8.3 Security Release Update Now!
\n\n\n\nWhat’s in the Works or Discussed?
\n\n\n\nProposal: Changes to JavaScript Coding Standards for Full Prettier Compatibility
\n\n\n\nJanuary 17, 2022 8 pm ET / 1:00 am UTC
What’s coming in WordPress 5.9 Panel discussion w/ Brian Gardner, Courtney Robertson and Birgit Pauli-Haack via WordPress Meetup Boulder, Co
Stay in Touch
\n\n\n\nTranscript
\nHappy New Year! 🎆 🙌 🎉🥂
\n\n\n\nI hope you all had wonderful time over the Holidays and you didn’t have to work. And if you had to work, that it was quiet time for reflection, catch-up and strategic planning. At Whistler, we encountered -21 °C (-5.8 °F) weather and this Florida Weather wimp had to put on about 15 pounds (ca. 7 kg) of layered clothes to feel warm enough to go outside. It is easy to forget what Real Winter feels like. I also was pretty amazed how fast one can adapt to anything, given enough time.
\n\n\n\nAfter a day and a half, we were ready to head up to the top of the mountain and all the suffering was definitely worth it. Look at the view!
\n\n\n\nBefore I get out of the way of the curated list of fabulous Gutenberg content, I want to express my wishes for you and the New Year: Good health, stay safe, prosperity, lots of laughter and loads of love for you and yours.
\n\n\n\nYours, 💕
Birgit
Table of Contents
\n\n\n\nIn the 39th episode of the Post Status Excerpt Podcast guest Anne McCarthy talked with David Bisset about the delay of WordPress 5.9, Automattic, COVID’s impact on contributors, Full Site Editing, and the future of the Customizer.
\n\n\n\nThere’s a new Hallway Chats episode! Topher and Cate DeRosia sat with Tammie Lister, Senior Product Designer at XWP, and talked about what it means to be a web designer these days, as well as how Gutenberg and the WordPress editor are changing and growing.
\n\n\n\nAbout Themes
\n\n\n\nBlock Building and extending Gutenberg
\n\n\n\nNew Blocks
\n\n\n\n\n\n\n\nWordPress 5.9 Release Candidate was released on Tuesday, January 4th, 2022 and the version is on schedule to be released on January 25, 2022.
\n\n\n\nIf you have a some spare time, Anne McCarthy has great instructions and topics on how you can Help test WordPress 5.9 Features. It’s a huge release and test can help.
\n\n\n\nA full reading list about the Block editor updates for WordPress 5.9 for developers, site builders and content creators is in the works. You can start reading here.
“Keeping up with Gutenberg – Index 2022”
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. The index 2020 is here
Only Gutenberg features and enhancements until version 11.9 made it into the WordPress 5.9 version. Only Bug and UI fixes to existing features of later Gutenberg plugin version were backported to WordPress 5.9
\n\n\n\nAnton Vlasenko published the release notes: What’s new in Gutenberg 12.2? (22 December) and points out as highlight the following:
\n\n\n\nFontSizePicker componentJustin Tadlock gave it a whirl in his post Gutenberg 12.2 Focuses on User Experience Improvements.
\n\n\n\nLuis Herranz released Gutenberg 12.3 and published the release notes on January 5th, 2021: What’s new in Gutenberg 12.3? (5 January).
\n\n\n\nHighlighted PRs are listed as follows.
\n\n\n\nThe last bullet point references the new Handbook page Core Block Reference and it is a big step forward to a complete and updated documentation of the core blocks. The blocks’ block.json information feeds into this page automatically.
\n\n\n\nJustin Tadlock wrote about it in Gutenberg 12.3 Introduces New Blocks, Design Options, and a Complete Core Blocks Reference
\n\n\n\nGrzegorz Ziolkowski and I recorded the 58th Gutenberg Changelog episode on Friday, January 7th, 2022. We talk about WordPress 5.9 release and DevNotes for Full-site Editing and block themes, and Gutenberg 12.2 and 12.3. We also, answered listener questions, this time by Aditya Kane and Jessica Lyschik.
\n\n\n\nFor those among us, who still rely on ACF for site data handling, Joey Farruggio built a command line tool to streamline the ACF blocks creation. You can read more about the context and the making of the CLI and what you can delegate to a script. The Create-ACF-Block CLI code is available on GitHub.
\n\n\n\nSpeaking of scaffolding blocks, the official WordPress create-block received and update, too. Once you are done with developing your plugin, you can automatically assemble the plugin.zip that you can upload to WordPress or share with other users via the plugin directory. Here is a short blog post about it: Run plugin.zip for create-block.
\n\n\n\nIn his tweet, Ryan Welcher pointed to the most recent Block Plugin Checker updates. When you submit your single block plugin to the directory, the Plugin Checker now validates against the block.json schema and also has a check for unique plugin namespaces as well. You can read about the details in this trac ticket: Block plugin validation tool UI improvements.
\n\n\n\nOnly tangentially related to the block editor, Grzegorz Ziolkowski published for the Core JavaScript team a proposal on Changes to JavaScript Coding Standards for Full Prettier Compatibility. Several contributor and developers have already commented. Let you opinion heard.
\n\n\n\nIn his post, How Advanced Custom Fields handle blocks, Carlo Bravo, discusses how you can create blocks with ACF (the plugin Advanced Custom Fields), what advantage is has and what downsides are for the users of such blocks. If you try to decide to invest in learning how to create dynamic blocks or ACF Blocks it’s a great article to start the process.
\n\n\n\nMarie Comet explains in her post Adding options and controls to an existing Gutenberg block, how to extend core blocks with an additional button in its Toolbar or more option controls in the sidebar. Sometimes extending existing blocks is faster than recreating features via Custom Blocks.
\n\n\n\n\nNeed a plugin .zip from Gutenberg’s main (trunk) branch?
Gutenberg Times provides daily build for testing and review.
Have you been using it? Hit reply and let me know.
Apart from the list of developer notes and reading list, Angela Jin published a Proposal for Approving Block Patterns Submissions to the directory. If you are a designer, or theme developer it might be interesting for you, and you might have an opinion how submissions should be curated on the official WordPress repository.
\n\n\n\nSpeaking of the WordPress repository, Munir Kamal created his idea of a Theme directory via the Gutenberg Hub: Re-Imagined WordPress themes directory. I really like the way how themes details on color schema, typography, and block styles can be surfaced to a Theme directory page. Kamal was right when he wrote: “This makes it much easier to find the theme that’s right for you without having to download and test multiple themes.”
\n\n\n\nJustin Tadlock at the WPTavern also took a look and wrote: “In the dawn of the block theme era, the WordPress theme directory could use a reimagining.” The rest of the article is ready for your purusal.
\n\n\n\nCarolina Nymark, write and developer on Fullsiteediting.com has a tutorial for you on how to use a php template to create a block template for Custom Post Type. Given how often I see the question on what about Custom Post Types, this is a very timely tutorial for Theme Developers. Nymark wrote: “The main pain point is that people are expecting to be able to create this type of template via the new Site Editor interface. This is a reasonable expectation, unfortunately the feature is not complete yet and not included in WordPress 5.9.0.”. In her post she shows you a viable workaround, that doesn’t leave you with too much technical debt.
\n\n\n\nCarlo Daniele took a Deep Dive into Twenty Twenty-Two and WordPress Block Themes for Kinsta. The article describes the upcoming new WordPress default theme, that will be the first default block Theme. Kjell Reigstad and Jeff Ong worked on the design and development. The Theme will come out bundled with WordPress 5.9
\n\n\n\nIf you like to get started on block theme development, there are a few choices depending on how you want to learn.
\n\n\n\nThe Developer Handbook on WordPress.org hold all the documentation about Block Themes. You start at the Overview page, then walk along the Create a Block Theme tutorial to learn more about the templates, template parts, template hierarchy and all necessary files. A primer on theme.json enables you to control the feature set and setting for Global Styles.
\n\n\n\nMarcus Kazmierczak‘s Devnote Block themes, a new way to build themes in WordPress 5.9 catches you up on the latest updates.
\n\n\n\nAnother opportunity to is the Twitch live stream series by Ryan Welcher and Daisy Olsen Creating a block-based theme. Part 1 is available on Twitch, and will later be posted on YouTube. The start was a bit wonky with some audio issues that cleared up at the timestamp 14:32. The next session will be next week, Thursday at 10:30 am ET / 15:30 UTC
\n\n\n\nOn January 12th, Daisy Olsen and Sarah Snow present the first installment of another series: “Zero to Block Theme Series: Foundations” at 1pm ET / 18:00 UTC.
\n\n\n\nKelly Choyce-Dwan, core contributor on the meta team, takes you along her journey while switching to a block based theme. She shares with you her process and her challenges and how she overcame them. Choyce-Dwan also surfaced a few things that are bugs and some have already been fixed. She also noticed that there is no way to give buttons or links hover state/colors, and CSS is your fallback. In conclusion, she wrote: “It was a fun experiment to refresh this site, and I really see the promise of block-based themes for easy site building. It’s a new framework to get used to, and sure there are bumps to work through, but it’s going to be great.”
\n\n\n\nIn her latest YouTube video Connecting The Dots: Level up with Query Loop block, Anne McCarthy is showing off a real-world example of the Query Loop block, and she demonstrates how it saves her time.
\n\n\n\nIn his review Anariel Design Releases Bricksy, Its Third WordPress Block Theme, Justin Tadlock gives Ana Segota, designer at Anariel Designs, and her theme high marks on beauty and versatility. It sports 32 Block patterns and also supports WooCommerce. Certainly, worth checking out.
\n\n\n\nAlexandra Yap introduced you to a new feature from the team at Stackable: Their plugins now gives you the option to start your design process directly in the Site editor. Learn how you can use Gutenberg to wireframe a website.
\n\n\n\nAlthough the block editor can handle Markdown in and of itself, it’s not the most convenient Markdown editor. The MarkUp MarkDown plugin seems to change that although it gives me unwanted flashback to pre-block editor times. In his review, New WordPress Plugin Offers a Markdown Editor Solution Justin Tadlock, is of other opinion, so it was a worth a read for me.
\n\n\n\nSpeaking of Flashback, read A Throwback to the Past: Retro Winamp Block by Justin Tadlock on his take on the block plugin that allows you to embed a Winamp player and skin into your 21st-century website.
\n\n\n\nPhil Webster created the Newspaper Column block, and interesting approach to have this block automatically display text over three or four columns automatically. It works best with paragraph and lists. Webster also plans to work on Accessible Block Collection to offer additional accessibility features for core blocks and build blocks that are missing for instance an Accordion block.
\n\n\n\nAs a sidenote, here is a twitter exchange with Webster about what is best for the user: Single purpose blocks or bock collections. What has been the better experience been for you? And would you pay for a single block premium plugin? And more. I found it quite insightful.
\n\n\n\nGood news for site owners looking for high-quality block themes: WP Engine Acquires Brian Gardner’s Frost, Opens It to the Public – now available for free. Justin Tadlock has the skinny for you.
\n\n\n\nKelly Choyce-Dwan released ‘a souped-up Spacer-type block’. With the Grainy Gradient Block plugin end-users can decorate the area with various gradient backgrounds and spruce up their content with interesting forms and color combinations. Justin Tadlock took it for a spin and shared ways he experimented with with the block on the WPTavern.
\n\n\n\nJanuary 12, 2022, 1 pm ET / 18:00 UTC
Zero to Block Theme Series: FoundationsJoin this space via WordPress Social Learning Spaces
January 14, 2022 1pm ET / 18:00 UTC
Demo: All About Colors with Full Site Editing with Roxy Kohilakis via WordPress Social Learning Spaces
January 17, 2022 3pm ET / 20:00 UTC
Advanced Layouts with the Block Editor with Wes Theron via WordPress Social Learning Spaces
January 17, 2022 8 pm ET / 1:00 am UTC
What’s coming in WordPress 5.9 Panel discussion w/ Brian Gardner, Courtney Robertson and Birgit Pauli-Haack via WordPress Meetup Boulder, Co
January 20, 2022 – 7 pm ET / 00:00 UTC
WordPress “Mega Meetup”: Block Patterns, WordPress 5.9
South Florida WordPress Meetup Group
January 26, 2022, 6:00 pm ET / 23:00 UTC
Intro to Templates and Template Parts (Full Site Editing) with Wes Theron via WordPress Social Learning Spaces
Don’t want to miss the next Weekend Edition?
\n\n\n\n\n\n\n\nIn July 2020, Bing released its first official plugin for WordPress that allowed site owners to submit URLS and get their content indexed immediately, instead of waiting for the search engine to crawl the site. The IndexNow API, which debuted in October 2021, is the next evolution of the Bing URL submissions API, created by Microsoft Bing and Yandex.
\n\n\n\nBing Webmasters has released a new IndexNow plugin for WordPress sites to take advantage of this new protocol. It makes it possible for websites to notify participating search engines whenever content is created, updated, or deleted, so that the site is indexed faster for updated search results. The Microsoft Bing Webmaster Tools team anticipates that it will minimize the need for crawling:
\n\n\n\n\n\n\n\nIndexNow is an initiative for a more efficient Internet: By telling search engines whether an URL has been changed, website owners provide a clear signal helping search engines to prioritize crawl for these URLs, thereby limiting the need for exploratory crawl to test if the content has changed. In the future, search engines intend to limit crawling of websites adopting IndexNow.
IndexNow is also an initiative for a more open Internet: By notifying one search engine you will notify all search engines that have adopted IndexNow.
The IndexNow WordPress plugin tracks changes in content and automatically submits the URLS in the background. It comes with a few basic features and configuration options:
\n\n\n\nThe IndexNow protocol is supported by Microsoft Bing and Yandex. Google is testing the protocol to see if it makes sense for a more sustainable approach to indexing the web.
\n\n\n\nBing Principal Program Manager Fabrice Canel proposed WordPress core integrate the IndexNow protocol but contributors suggested Microsoft keep it as a plugin until it’s more widely adopted by major search engines and proves that it has a positive effect on reducing the need for crawling.
\n\n\n\n“By releasing this plugin, we aim not only to benefit right away WordPress websites adopting it, but also learn, tweak as needed to someday release IndexNow in WordPress core to benefit all websites and all existing and upcoming search engines adopting IndexNow,” Canel said on the ticket.
\n\n\n\nThe IndexNow plugin already has 800 active installs but it’s a long road for Microsoft to prove that its API is effective at streamlining indexing for search engines. If Google agrees to support it after testing, the protocol may gain enough momentum to attract other search engines’ support.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 08 Jan 2022 03:14: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:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"WPTavern: Decorating Web Pages With the Grainy Gradient Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=128020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:167:\"https://wptavern.com/decorating-web-pages-with-the-grainy-gradient-block?utm_source=rss&utm_medium=rss&utm_campaign=decorating-web-pages-with-the-grainy-gradient-block\";s: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:3198:\"Yesterday, Kelly Choyce-Dwan released a souped-up Spacer-type block. However, instead of just empty space on the screen, end-users can decorate the area with various gradient backgrounds.
\n\n\n\nGrainy Gradient Block is just the type of plugin that I look forward to tinkering with. It is not complex. It stays in its lane. And, it is just plain fun to use.
\n\n\n\nThe block was inspired by the grainy gradient trend touted by CSS-Tricks in 2021. Now, users can use them directly in the WordPress editor.
\n\n\n\nThe plugin’s single block has four variations, as shown in the following screenshot:
\n\n\n\nThe variations are:
\n\n\n\nAfter far too much time attempting new design ideas with the plugin, I finally landed on something that I liked. I pulled a sunset image from WordPress Photos by Mark Westguard and used it within a cover block. Then, I applied a couple of different Grainy Gradient blocks over it.
\n\n\n\nThe goal was to give it an old, worn painting feel. I was happy with how it and several other variations I worked through turned out.
\n\n\n\nI wanted to see what I could do with some real-world art — I had paintings on my mind at that point. So, I grabbed a photo of a piece I completed a week or two ago and began anew.
\n\n\n\nThis time, I used a similar process. I wrapped everything in a Cover block and applied a duotone filter over the image. Then, I placed the Grainy Gradient block inside and switched it to the Horizontal Grain variation.
\n\n\n\nIt turned out similar to a poor photocopy of a hand-drawn piece. Essentially, it was better than my original artwork.
\n\n\n\nDo not let my imagination fool you into thinking this plugin is limited to just a handful of ideas. There are 1,000s upon 1,000s of variations users can create. For example, just dropping it in a column next to a text-heavy section can spruce up a page’s design a bit:
\n\n\n\nIf I had one request, it would be to add grainy gradient backgrounds to the Group and Cover blocks. Both allow for gradients but not of the grainy variety. The effect is created via an SVG filter, which is how the duotone feature in core works. There seems to at least be some appetite for other filter types. Maybe we will see a more broad list of such options in the future.
\n\n\n\nFor now, I think I will continue playing around with Grainy Gradient Block.
\n\n\n\nThe development version of the plugin is also available via GitHub.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 08 Jan 2022 00:35:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"Gutenberg Times: What’s new in WordPress 5.9 – a Reading list on Full-Site Editing and Block Themes.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=19945\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://gutenbergtimes.com/whats-new-in-wordpress-5-9-a-reading-list-on-full-site-editing-and-block-themes/\";s: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:11766:\"WordPress 5.9 Release Candidate 1 was released on Tuesday, January 4th, 2022 and the version is on schedule to be released on January 25, 2022.
\n\n\n\nThe WordPress 5.9 release mostly introduces Full Site Editing to WordPress user. It’s the biggest release since the roll-out of the block editor in December 2018. The umbrella term Full-site Editing covers a multitude of editing features.
\n\n\n\nThis reading list covers the latest publication of Developer Notes and User Documentation related to the Block Editor.
\n\n\n\nAlso, see the WordPress 5.9 Field Guide with all DevNotes for the upcoming release.
\n\n\n\nTable of Content
\n\n\n\nAlso don’t miss Anne McCarthy’s article on what’s still in the works for the next version of Full-site Editing and Block themes.
\n\n\n\n\n\n\n\nAbout Themes
\n\n\n\nBlock Building and extending Gutenberg
\n\n\n\nNew Blocks
\n\n\n\n\n\n\n\nLearn more about the progress on performance improvement efforts coming to WordPress 5.9 Performance Improvements
\n\n\n\nIt is only available to content creators who are using a Block theme. When you are using the Site Editor, most changes here are made across your entire site.
\n\n\n\n\n\n\n\nA block theme is a theme that uses blocks for all parts of a site, including navigation menus, header, content, and site footer.
\n\n\n\n\n\n\n\nThis is a new feature in WordPress 5.9 that comes included in Block themes that allows you to customize your site as much as you’d like with different colors, typography, layouts, and more
\n\n\n\n\n\n\n\nThe Navigation Block is an advanced block in WordPress 5.9 that enables you to edit your site’s navigation menu, both in terms of structure and design. The Navigation block can be used with a block theme or a theme that has support for template editing.
\n\n\n\n\n\n\n\nThe Template Part block is an advanced block introduced in WordPress 5.9 that can be used with a block theme or a theme that supports template editing.
\n\n\n\nAnd more…
\n\n\n\n\n\n\n\nReady to Test? To date, you’ll find 34 block Themes already in the WordPress repository that are prepared for Full-Site Editing.
\n\n\n\nI often get the question: “What are the few themes you like?” Here is my list:
\n\n\n\nI received similar questions at meetup gatherings. Here are the themes of my response.
\n\n\n\n\n\n\n\nAll three are from trusted theme designers, and were reviewed by Justin Tadlock at the WPTavern.
\n\n\n\nAutomattic also published a set of themes, all focused on blogging and writing:
\n\n\n\n\n\n\n\nI am also a huge fan of the first WordPress default block theme, called Twenty-Twenty-Two. Carlo Danielle did a deep dive into the inner workings for Twenty-Twenty two. and takes you along for the ride in his post for Kinsta. Designer-developers Kjell Reigstad and Jeff Ong worked on it with other contributors. It will be released with WordPress 5.9. New WordPress site will activate it out of the box.
\n\n\n\nShare in the comments if you find a block-based theme that you like or built.
\n\n\n\nAt Learn.WordPress.org the course Simple Site Design with Full Site Editing is now available online. It’s part 1 in a series of 2 or 3 courses to come out soon. It’s free of charge
\n\n\n\nAt Fullsiteediting.com, Carolina Nymark, contributor on the WordPress theme team prepared two courses
\n\n\n\n\n\n\n\n\n\n\n\nSocial Learning events around the new features. Register on Meetup.com
\n\n\n\nFeatured Image: “Mitchell Library, Sydney (#24)” by Christopher Chan is licensed under CC BY-NC-ND 2.0 found on OpenVerse
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jan 2022 21:36: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: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:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"WordCamp Central: Call For Speakers for WordCamp Europe 2022 in Porto is Open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=3143943\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"https://central.wordcamp.org/news/2022/01/07/call-for-speakers-for-wordcamp-europe-2022-in-porto-is-open/\";s: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:813:\"Call For Speakers for WordCamp Europe (2-4 June, Porto, Portugal) is open and we are inviting you to apply!
\nWhether you have given thousands of talks in front of a large audience or you have moderate experience in public speaking, if you have the practical knowledge to share — please, do it, apply to speak!
\nWordCamp Europe organizers will soon be hosting an online Q&A session where you can ask questions and get guidance on how to raise the chance for your application to be selected. Keep an eye out on the WCEU website to be notified of the same.
\nWe look forward to seeing your application soon!
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jan 2022 07:32:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Sabrina Zeidan\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"Post Status: Post Status Excerpt (No. 40) — Post Status from 2021 to 2022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=92232\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://poststatus.com/excerpt/40/\";s: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:27913:\"In this episode of Post Status Excerpt, David and Cory chat about the key events for Post Status in 2021, including Cory\'s acquisition of Post Status from Brian in May, StellarWP‘s sponsorship of Post Status Slack to go pro, and the acquisition tracker. Cory also explains how his understanding of Post Status has changed since acquiring it.
\n\n\n\nAlso: David and Cory also discuss what they hope Post Status can become in early 2022.
\n\n\n\n\n\n\n\nEvery week Post Status Excerpt will brief you on important WordPress news — in about 15 minutes or less! Learn what\'s new in WordPress in a flash.
You can listen to past episodes of The Excerpt, browse all our podcasts, and don’t forget to subscribe on Spotify, Amazon Music, Google Podcasts, iTunes, Castro, YouTube, Stitcher, Player.fm, Pocket Casts, Simplecast, or by RSS.
Mentioned in the show: Sponsor: GoDaddy ProManage your clients, websites, and tasks from a single dashboard with GoDaddy Pro. Perform security scans, backups, and remote updates to many sites on any host. Check up on site performance, monitor uptime and analytics, and then send reports to your clients. GoDaddy Pro is free — and designed to make your life better
\n\n\n\nDavid Bisset: It may seem like [00:01:00] yesterday, but you know, we started 2021 with Brian\'s still at the helm of Post Status. You were a partner, but that changed in the middle of the year, around may or June and where you are fully acquired Post Status. So you remember that still.
\n\n\n\nCory Miller: Oh yeah.
\n\n\n\nVividly. We were just kind of prepared for this. It was just pulling me back and going. It\'s really good to reflect, you know, and review what\'s going on. And I don\'t take enough time for this instead of member huddle, but, you know, we didn\'t really talk about this linking back for posts specifically on, remember how that on some, I\'m glad to do it because.
\n\n\n\nI think if I look back, it was me taking over full-time with Post Status going from what was kind of a part-time gig and a really fun gig to a very busy gig. And because we\'re growing the vision and it just I think there was, you know, if I can look back on the year related to Post Status for me, it was.
\n\n\n\nThis light bulb moment of like, I can do anything. I want, not that I couldn\'t with Brian, it was just like, okay, I\'ve got [00:02:00] full control of this. I don\'t know if a lot of people realize David, but at I themes, I actually wasn\'t the majority owner. And I start when I started in 2008, I met two, my, my two partners and they gave me some initial funding.
\n\n\n\nTo to get started with iThemes. And so, I had partners all along and there\'s many pluses to that, by the way. But this magical moment that happened to me was over that summer and just realizing one day. This is all mine. Not to sound very selfish about it. You know, Dave, because I\'ve tried to be very collaborative and share everything we\'re doing, but I go, I can do anything I want, what do I want to do?
\n\n\n\nOh, wow. Like, yeah. And again, not that brian was holding me back at all. It was just, it was this moment of going, this is mine. And then another day, wake it up and go on everything I want to do I can do here. So those are huge light bulb moments for me looking back in this year.
\n\n\n\nAnd I hope everybody can see that my energy, like we\'re we were a [00:03:00] bunch of part-timers David you\'re part time Dan\'s part-time more or less. I was part time. Brian was part-time like, when we all we said, and I gather, we probably have a couple of full-time people here. But this was just different fitting for me this next adventure spirit Post Status.
\n\n\n\nAnd I\'m, really pumped about it.
\n\n\n\nDavid Bisset: So obviously you saw potential in Post Status when you first joined Brian, I\'m going to say sometime in 2020.
\n\n\n\nCory Miller: Yes, January 2020, right before the pandemic. And he came out and we had a lot of cool plans that we\'re now gonna start doing, starting in February. Some of our in-person things, very small groups now with omicron going on and we\'ll see how everything goes, but we\'re going, we\'re pushing forward with our first in-person meetup.
\n\n\n\nOur partner summit in February in Oklahoma city. But yeah, that was pre printed. January, 2020. It\'s crazy to think our fastest.
\n\n\n\nDavid Bisset: So you cruise through and then May 2021 you acquired. [00:04:00] So what is the difference between how you\'re looking at Post Status and your goals when you acquired it from Brian then versus now, like what\'s changed in your mind?
\n\n\n\nWhat goals have changed? What potential are you realizing?
\n\n\n\nCory Miller: You know, being very honest and reflective about all of this David it\'s just going we\'ll maintain cool stuff. That process was already doing. That was the previous mindset. The mindset today is now we\'re going to grow. We\'re going to do 10 times what we\'ve done in the past.
\n\n\n\nWe\'re going to take community to a whole new level. We\'re going to really blow out what we\'re doing at post-test and truly become and be, and showcase. We are the professional community of the open web. That WordPress leads in that we, as WordPress leaders are a part of that bigger ecosystem, but the whole point of we are Post Status.
\n\n\n\nIt\'s an energizing, shared vision that rallies all of us together. And that\'s why I\'m so energized about all of this, because it\'s, what I [00:05:00] love to do is help bring people together. And it\'s just funny, the artificial boundaries and barriers we\'ve put on ourselves, but that\'s what I had. Previously, when I took over, I thought I will maintain this awesome community.
\n\n\n\nThat was my, that was pretty much my vision. I\'ll do cool stuff. Get to work with cool people, get the, hang out with all of my friends. You know, now it\'s even a bigger vision and I\'ve had a lot of. With that Jonathan Wald, yourself, Dan, or editor-in-chief Michelle Frechette. My wife Lindsay is always my number one partner in anything I do.
\n\n\n\nShe\'s always there to help and support me. Now we have Felicia on full-time to take over operations here. Our first full-time employee. I don\'t know, I guess technically second, because you can count Brian in the past. So, Yeah. It\'s spark. You just got me all excited, just thinking about that, but that was on this truth.
\n\n\n\nThat was, as far as I could see at that point, you know, was let\'s make them this cool thing. Let\'s don\'t do anything to break it, [00:06:00]
\n\n\n\nDavid Bisset: right? Yeah. When you inherit something precious, the first thing I do is like, don\'t break anything. Don\'t don\'t mess up. And then eventually you\'re like, okay, how can I expand this without breaking it?
\n\n\n\nNow I wrote down, you know, Your better journalist and I am, but what I did was I wrote down, I tried to write down the top three Post Status moments of the past year. And frankly, I think palpably, since you took over, I think has before, you know, with everything going on, I can barely remember the last six minutes, let alone six months.
\n\n\n\nSo we\'re starting from you, acquiring from may have going forward. So one of those was actually something you touched on before, and I think it caught a few people, maybe not delight, surprise, but something that, what is this. You, you mentioned an open source manifesto, or you talk to, you mentioned about seeing Matt and talking about open source, the open source manifestos on our site right now at poststatus.com/open-web-manifesto.
\n\n\n\nAnd it says Post Status seeks to grow WordPress economy in three [00:07:00] ways, guide, connect, and elevate. Was this an idea that you and the in the team had, you know, when you acquire Post Status or when did this come into real clear picture? They feel like, oh, I know I\'m going to talk to Matt about it.
\n\n\n\nOh, I\'m going to, we\'re going to put this together, put on our website and what, you know, what was the, what was, what were you trying to get out of this by posting this Manifesto?
\n\n\n\nCory Miller: Yeah, that was you know, everything I do it\'s just a collaboration and I try never to take credit for things to that.
\n\n\n\nI don\'t do I work so much better in a band or an orchestra or whatever, like with other people. And this was a vision that Jonathan Walton. You know, crystallized in my head he shared the vision of the open web, what she\'s talked about and blogged about prolifically on his own site. And then he shared that with me and I asked him questions and clarify, like, okay, what do we mean when we say that?
\n\n\n\nHow does WordPress fit into all of that? And super got energized by that vision shared vision [00:08:00] that, that really is it connects all of us here at Post Status in the bigger ecosystem of WordPress. And so, And I just like, I love building community, a little blood pulling people together. And I know that one way to do that is to have a shared vision that energizes us just like WordPress is the shared vision of democratizing publishing for postage.
\n\n\n\nThe open web, we are builders and makers of the Oakland web, you know, crux guard did a shirt like that back in the day. And I thought it was the coolest thing. I\'d seen a, I make the internet or something like that was the shirt that we\'re going to bring back by the way. So this has been, this is not a new vision necessarily.
\n\n\n\nIt\'s a clarification of one, but so much of what we\'re doing today is what was built with the bedrock of what Brian did. And then you David and Dan. And now me and now Michelle, now Jonathan NA AIG. Now all these different people that we\'ve got on our contributing team to build something cool. But the open web manifest is sometimes just want to keep [00:09:00] ringing the bell.
\n\n\n\nWhen they think of Post Status. I want them to think open web. We are the makers of the open web.
\n\n\n\nDavid Bisset: Yeah. Cause it says here we offer guidance on how to think and where to focus. Businesses, we help our members get connected with each other and we grow businesses or growing businesses need support. And we\'re committed to doing what needs to be done to help our members grow.
\n\n\n\nSo that actually fits into something that you mentioned. You\'ve been one message you have been repeating in some form more or less, I\'d say you fully took over in may or June is that Post Status is not a news site. So if somebody came up to you and said, is Post Status a new site, how would you respond to.
\n\n\n\nCory Miller: We\'re not there\'s variations of that. We happen to break news. We happen to commentate on these, but I\'m a purist as a journalist and I go, true news is, should be balanced. It should be fair. It should be. Objective as possible within our humans feces about we can be, and that\'s just not what we do here.
\n\n\n\nWe serve and support WordPress professionals and WordPress businesses. [00:10:00] That\'s what we do. So we\'re not a journalistic outlet. We are ho what can we do that serves and supports our members and makes our life better? How do we help think ahead for them? How do we think, like one of the stalwarts of post as for you.
\n\n\n\nWith Brian and you and Dan later on, was that too long? Didn\'t read email. I got every week and I would sit and read that and go, okay. I can\'t keep up with drama press sometime. I can just scroll through my email and go “here\'s the interesting things. I should probably pay attention,”. And so that\'s the guide part as part of our mission guide connected elevate.
\n\n\n\nAnd so the we\'ve been doing that for years. That\'s a legacy that Brian has a huge fingerprint on going forward from forever here at Post Statuses. We should give he, I loved his thought analysis pieces his commentary and his insights. And I pushed our team and brought in more contributors to say, don\'t just say this.
\n\n\n\nIt doesn\'t, that\'s a headline they can get anywhere. That [00:11:00] doesn\'t help people. It just shoves a headline in your face. But if it says, how does this, what does this mean for me in a couple of lines succinctly, which is hardware, by the way, that\'s what we want to be doing at Post Status is saying the too long didn\'t read. Here we can help you say brain processing power and keep up with all the stuff going on that you can\'t within this amazing ecosystem called WordPress and the open web. So that\'s the way I see our content. What we publish here is everything that just helps our members think about, get ahead, stay ahead of what\'s going on in their world.
\n\n\n\nDavid Bisset: Yeah, good. Cause you know, I can\'t stop giving my 2 cents on anything. So that kind of fits well with the analysis part of it. All of it. One of the things we did do that seemed, I mean, I think may have, seemed like news in the beginning, but we kept one of the top three, I think highlights of my personal highlights of post status over the past year is we started the acquisition tracker. You [00:12:00] know, you can look at that as news. I kind of look at it as more of a guide for all of WordPress to look at because now I think whenever there is an acquisition. Either me or Dan get pinged on Twitter or in post that a stock that somebody else randomly reset the calories at the counter or some other podcasts goes, this is where, and you can see now it\'s a very useful tool for now, for me personally, even though we\'re the ones who put it together, that wow, you can look, I was reading article about Matt Mullenweg the other day about his role in trying to push the open web. And in order to do that, he needs he through automatic. For the most part, we\'re making these certain acquisitions in certain categories and you\'re reading the article and you go, well, I, you know, you look at, and then look at the acquisition page and you see all the acquisitions, automatic is put together.
\n\n\n\nYou begin to see, wow, this is starting to make sense. It\'s like, you know, the over not to get into a story about Matt and the acquisitions, but you begin to see. Wow. This particular journalism app has been acquired this particular photo, you know, the creative comments thing has been acquired or [00:13:00] absorbed into the project and you begin to see a grander picture and, you know, embarrassed.
\n\n\n\nI am to probably have read I think it was David Pearce\'s article or something on this, but you can go back and look at a nice orderly list, like the acquisition tracker and we\'ll have more stuff next year, probably to go along with that. So I thought that was a real. Good thing for us post status people to put up because everybody seems to use it.
\n\n\n\nAnd, you know, I like putting up stuff. That\'s actually useful to people.
\n\n\n\nCory Miller: Again, we should be giving those type of tools for people it\'s not about, it\'s not about breaking news. It\'s about which we happen to do with the Pagely announcement. But like, that was a member longstanding member of our community who wanted it of the two that news to be broken through post status, which he in.
\n\n\n\nLovely wife has, co-founders have supported for years here. And that\'s why we broke that news. But yes, it comes down to those tools. Like how can we help our members? You know, keep up. We have a set of members that are founders here. We want to help them [00:14:00] move up, take the next level and things like that.
\n\n\n\nAnd yeah, that all just kind of gets me excited. Cause that\'s what I want to be doing more and more of here at post status and to
\n\n\n\nDavid Bisset: be clear our own community is adding. List as well. They\'re not waiting for us to read stuff and update their they\'re just sending us stuff to update. So to me now it\'s more of like a.
\n\n\n\nBorderline Wiki page at this point.
\n\n\n\nCory Miller: But this is why I love the word collaboration, because there is no way I can do it by myself, no way. And it\'s so obvious that I love it because then we can say like, I don\'t know whose idea was the tracker, but it wasn\'t mine. And when that, then I was like, yes, we, but when I heard that deal, I was like, absolutely this fits perfectly. We should do that. And then we got it out and it has been a community collaboration because I know we miss things. We\'re not in a news, you know, watch Doug and financial.
\n\n\n\nDavid Bisset: We\'re not a news site as you\'re saying well, so, so here\'s the last thing on my list. And I wanted, I want to talk to you about stellar WP [00:15:00] provided us a sponsorship that allowed our post status slack to be fully upgraded to I guessing the pro version, which means you get access to all of the past conversations and a lots of other bells and whistles as well.
\n\n\n\nWeeks before that announcement was made publicly. You were talking about that internally with us as a possibility, and you were very excited about that possibility. Can you tell me why it was so important for you to, with stellar WP to pursue this particular upgrade and what it means for the post status community?
\n\n\n\nCory Miller: I had heard from a number of people, you know, this is the hallway track. This is the in between times where we see each other, you know, team. Meet all the time, see each other all the time, but we have so many amazing community members that are on different teams. And hosts has, is the glue is the hub.
\n\n\n\nAnd I had heard from so many members over the two years of being a part of post status now. And that issue would be [00:16:00] nice. Well, when I asked, I was like, okay, a pressing increase right now is not going to is probably not going to work or fund us, you know, for the foreseeable future. So I valued the preservation of memories and conversations and things like, particularly in the DMS, our stats say it every single week.
\n\n\n\nIt\'s just conversations don\'t happen in public, on Prestos. They haven\'t happened in the DMS and then you lose track of the conversation. You and I might have had five years ago, Dave, and you know, and now we get it back and we can kind of retrace that. I think that\'s valuable because there\'s so many best practices, tips, cool stuff that we share with each other, and it just needed a better way to be preserved.
\n\n\n\nAnd this is my short term solution. I think, you know, you and I\'ve talked and our team has talked about how. Going forward. When I talked to Matt Mullenweg in San Francisco, a couple in back in where was it? December? Earlier this month when I mentioned we\'re going to paid slack he mentioned an open source project [00:17:00] that I don\'t think is ready for the prime time just yet, but that they were looking to use for the.org project.
\n\n\n\nAnd I was like, okay, that\'s interesting. But really the premise is just maintaining that hub. To connect with each other. That\'s the essence of why we did, why I sought out a sponsorship, but then out into the universe. And then our friends at seller WP said, we\'ll take it. We\'d love to be that sponsor.
\n\n\n\nAnd I\'m so thankful for Hazel and her team and core course, Michelle Frechette and her new role over at seller WP and being a huge part of our culture contributing team here at Post Status is pretty awesome. So synergy, can I use that?
\n\n\n\nDavid Bisset: You can use whatever word you want. As long as it\'s family friendly.
\n\n\n\nThat\'s my only thing for this show. Cause my kids listened to this. Believe it or not. Yeah. They really need to get them a Disney plus subscription they\'re going into from now. well, Olivia, my 17 year old daughter It\'s getting to be more of a [00:18:00] production type oriented type of person, probably a lot more professional than me.
\n\n\n\nSo she actually listens and tells me when I mispronounced things and when I could have done better. So what do you, so we\'ve kind of covered what was the quickly the big, exciting moments of post status last year. And I don\'t want to put you too much on the spot, cause I think we can probably.
\n\n\n\nDo a whole other episode about what\'s coming in 2022, but what are you most excited about maybe generally speaking, whether involves post status or not, as we kind of get into the first quarter of 2022 what Scott what\'s on your radar in terms of things that are interesting you the most in this.
\n\n\n\nCory Miller: For process specifically it\'s small group cohort type meetings that we\'re going to be starting posters. So like we\'ll be starting January 12th. I think it is on the Wednesday, our first 2022 member huddle each week. We\'ll do that on slack. There\'s a channel there for that. So I like more than. We went, you know, finishing the year, getting to be with Matt Mullenweg and [00:19:00] awesome members like Aaron Campbell, and Jordan, Michelle Frechette and a different people in person for state of the word was freaking awesome.
\n\n\n\nWe, we missed the human. We have so much miss that human component in a recognize that in lieu of being able to do that. And we\'re going to try to do that in 2022 is be together, is if we can\'t, you know, in person we\'ll make the most of our online experiences. And so that\'s what I\'m most excited for the first quarter at Post Status.
\n\n\n\nDavid Bisset: Oh, great. I, again, I go back to the manifesto that was published and beyond the open web, again, there, there is a, the post status credo. Is embedded in, into growing the WordPress economy. And then by and by that, we mean growing the businesses that need the support, the individuals too, that also need that support a rising tide lifts all the boats.
\n\n\n\nSo in order for WordPress [00:20:00] to like eventually market share is not going to matter anymore. It\'s either, we\'re going to be able to lose the ability for the reporting of it or something else will take its place or the market share. From a certain metric is going to stop. I\'ve always said that\'s not really a good measure of how WordPress is doing. That\'s just an easy number to pluck off you know, in, in sticking in a sticker or stick it in a headline, stick it in a tweet, but the best way for, to judge the growth of WordPress in my opinion has always been the community, the strength of the community, because you can have software. Without the community.
\n\n\n\nBut you can\'t, there\'s not really much, you\'re going to be able to do with it. You\'re not going to enjoy using it. You\'re not going to look forward to using it with other people. And I think what you\'re discussing here is more than just centering around WordPress, the software. Once you have this community and slack and Post Status slack, you\'re talking to people about running your business.
\n\n\n\nYou\'re talking to these, all these great people and it\'s just, WordPress becomes just a thinner line that connects everybody into one. Great, huge. Community. And I\'m really looking forward, like you to see [00:21:00] how this expanded slack goes, how this more interactive ability, like some people will use, we use Post Status and just like they\'ll drop into slack, have a few conversation, reads things and leave.
\n\n\n\nBut I think now, especially going to 2022 is whether or not we\'re trying to judge carefully how to step back into the public, you know, however way that is and wherever we live. We need to be able to take advantage of having this collective community bonding together and meeting together regularly.
\n\n\n\nBecause sometimes even though you may not feel like it, sometimes you really need to have to talk to someone or be coached by someone or be enlightened, be refreshed, be relaxed by someone. And sometimes being people around that digitally even is better than nothing you don\'t want to be alone. I don\'t think for very long in this space emotionally or.
\n\n\n\nFinancially or business-wise either. So I think that\'s one of the best things of appreciating. Our direction at Post Status. It\'s not just like you said, we\'re not a new site. We\'re offering commentary, but what I\'m most excited, [00:22:00] what I saw you especially talk about is we\'re trying to get people to have conversations together.
\n\n\n\nAnd, you know, on my end too, I\'m putting out a stage on Twitter spaces. For example, people communicating together their ideas because our community isn\'t going to be strong unless we\'re continuing the exchange of idea. And thoughts and advice. So that\'s awesome. Corey, that your vision, it kind of goes along that same path to.
\n\n\n\nYou know, I don\'t want to, I mean, it\'s not the, it\'s not the alcohol talking right now because it\'s still too early for that, but I do appreciate what you\'re doing. And so, yeah, so we\'ll, I\'m going to wish you a good year because there\'s only two more days left of it. So I mean, what could possibly go wrong?
\n\n\n\nWe\'ll talk next year. Yep. And I\'ll see you then and best to the family.
\n\n\n\nCory Miller: You bet. Thanks so much for what you do, David. Your commitment to the WordPress community and also post status
\n\n\n\nDavid Bisset: and our team and our team. You know, our team deserves our team. The team itself deserves [00:23:00] all the praise we can get, especially in these in these times confusing times.
\n\n\n\nSo yes, we thank them as well.
\n\n\n\nCory Miller: Yep.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jan 2022 05:00:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Bisset\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: New WordPress Plugin Offers a Markdown Editor Solution\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=127968\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:173:\"https://wptavern.com/new-wordpress-plugin-offers-a-markdown-editor-solution?utm_source=rss&utm_medium=rss&utm_campaign=new-wordpress-plugin-offers-a-markdown-editor-solution\";s: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:4955:\"Earlier today, a new editor plugin named Markup Markdown landed in the WordPress directory. It replaces both the classic and block editors with a Markdown solution. It is the first plugin by an author simply known as Peter, or @peter202202.
\n\n\n\nAs someone who almost always writes in Markdown, I did not think twice about downloading, installing, and activating it. I was pleasantly surprised to find a decent editor that I enjoyed — after making a few changes, at least.
\n\n\n\nThe plugin is not complicated to use. If you are familiar with writing in Markdown, you need to only activate it. There are no settings. Markup Markdown replaces the editor for all post types with its own.
\n\n\n\nThe plugin relies on the Parsedown PHP library to handle front-end output, turning the Markdown into HTML. On the backend, it uses the EasyMDE script for a JS-based editor.
\n\n\n\nWhile I am generally a fan of option-less plugins, this one could use a few. At the very least, users should get to choose which editor they prefer via their profile. On a multi-author site like the Tavern, not having this option means the plugin is a non-starter. I would also like to choose between editors for individual posts. It does not make sense for one already written in blocks to be edited in Markdown.
\n\n\n\nThe biggest issue I ran into with the plugin’s editor was that the font size was far too small and the content area too wide for comfortable writing. Therefore, I made a few CSS adjustments to make it more to my liking.
\n\n\n\nWithout these adjustments, I genuinely liked the plugin. However, the older I get, the more crucial readable typography becomes. My eyes prefer the change.
\n\n\n\nIn the future, I would like to see the plugin author at least use the theme-defined content width to set the writing area. With theme.json files becoming standard, I would pull typography-related styles in too. It does not need to do much — no need to try to go for a WYSIWYG experience.
An alternative would be to add a few design options for configuring the editor. A handful of settings would go a long way in creating a more user-friendly experience.
\n\n\n\nFor the most part, I enjoyed tinkering with Markup Markdown. If this were five years ago, I would already have it on all my sites. And, it is likely an ideal solution for many Markdown lovers today.
\n\n\n\nI still prefer the overall interface of the modern post-editing screen. I feel like I am traveling through time whenever I encounter the classic version. It is jarring enough that I doubt I would seriously use this plugin today. I would prefer a Markdown solution built on top of the block system.
\n\n\n\nOne downside of the plugin is that it may not work alongside some block themes. Some rely solely on theme.json-generated styles at the block level to handle their design. This means that valid HTML output not generated by the block system may be left unaccounted for.
For example, the following <img> (image) tag wrapped inside <p> (paragraph) blows out of the layout when using Twenty Twenty-Two:
There is nothing wrong with the HTML, and it is the standard way Markdown outputs images. This mistake is from the theme, not the plugin. The design is not accounting for large images when not output by a block. This is something that nearly all classic themes handle.
\n\n\n\nA theme that covers all its bases will show the following:
\n\n\n\nI love block themes, but this is something to watch out for if using one alongside this plugin. Most of those I tested did not handle this scenario. This same problem could affect content written in the classic era or custom HTML.
\n\n\n\nWhile on the subject of images, the plugin sticks with pure Markdown output. It has a button for pulling up the media library, but there is no way to insert anything but the full-sized image. Alignment classes are not available either.
\n\n\n\nThe latter problem could be solved if the plugin bundled Parsedown Extra, a Parsedown extension that supports Markdown Extra. The specification allows “special attributes.” As someone who routinely writes in Markdown, I almost exclusively use this feature to add classes to images.
\n\n\n\nOverall, the plugin is a solid solution for those looking for a Markdown-based editor. With it being a 1.x release, I look forward to seeing where it goes in the future.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jan 2022 01:11:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"BuddyPress: BuddyPress 10.0.0 Release Candidate\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=322784\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://buddypress.org/2022/01/buddypress-10-0-0-release-candidate/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6063:\"\n\n\n\n“Release Candidate” means that we believe the new version is ready for release, but with more than 200,000 active installs, hundreds of BuddyPress plugins and thousands of WordPress themes, it’s possible we missed something. BuddyPress 10.0.0 is slated for release on January 17, 2022, but your help is needed to get there .
You can get the 10.0.0-RC1 pre-release package in 4 ways:
\n\n\n\nsvn co https://buddypress.svn.wordpress.org/trunk/git clone git://buddypress.git.wordpress.org/![\"🛂\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f6c2.png\")
Site Membership RequestsSite Administrators wishing to have more control over who can join their community will be able to enable site membership requests from their BuddyPress Options Administration screen. Once done, BuddyPress sign-ups are transformed into membership requests to be manually reviewed and approved by an administrator to validate new user accounts.
\n\n\n\n\n\n\n\n![\"🗞\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f5de.png\")
More engaging logging activitiesThese simple activities about specific user interactions or events (e.g.: a user became a friend of another user) will be more visually attractive to improve user engagement in your community. The most impressive new activity is that which is generated when a user updates their profile photo: it will include the profile photo that spurred the creation of the activity item, even if it has been updated since ![\"📸\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f4f8.png\")
!
![\"🎨\"](\"https://s.w.org/images/core/emoji/13.1.0/72x72/1f3a8.png\")
WordPress Full Site Editing compatibilityYou’re beta testing WordPress 5.9: first thank you, second please take a few more minutes to check the improvements we’ve made to our BP Theme Compatibility API to play nice with themes supporting Full Site Editing such as the next WordPress default theme: Twenty Twenty-Two.
\n\n\n\n\n\n\n\n A new place to easily discover our next BuddyPress Add-onsBuddyPress Add-ons are side projects/projects as features/next BuddyPress blocks maintained by the BuddyPress development team we’ll soon make more widely available by publishing them on the WordPress plugin directory. When BuddyPress 10.0.0 is released, you’ll find a new tab to your “Add Plugins” Administration screen. On it, you’ll see a new add-on for a potentially upcoming feature: BP Rewrites. We think this will bring more contributions to the BuddyPress project as a whole.
\n\n\n\nA detailed changelog will be part of our official release note. In the meantime, you can check the 10.0.0 milestone changes list from our Trac environment.
\n\n\n\n\n\n\n\nTranslate BuddyPress into your language. The release candidate also marks the string freeze point of the 10.0.0 release schedule. And we don’t have much time to update all of the BuddyPress translations. So if you speak a language other than English, please help us translate BuddyPress into as many languages as possible!
\n\n\n\nIf you think you’ve found a bug, you can share it with us replying to this support topic or if you’re comfortable writing a reproducible bug report, file one on BuddyPress Trac.
\n\n\n\n\n\n\n\nThanks in advance for your help–we can’t build BuddyPress without you! Happy 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jan 2022 00:41:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"David Cavins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:127:\"WPTavern: WordCamp Birmingham Updates COVID-19 Protocols Amid Omicron Surge, WordCamp Europe Still Planning for In-Person Event\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=127922\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:297:\"https://wptavern.com/wordcamp-birmingham-updates-covid-19-protocols-amid-omicron-surge-wordcamp-europe-still-planning-for-in-person-event?utm_source=rss&utm_medium=rss&utm_campaign=wordcamp-birmingham-updates-covid-19-protocols-amid-omicron-surge-wordcamp-europe-still-planning-for-in-person-event\";s: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:10040:\"WordCamp organizers are responding to community concerns this week, as the more highly transmissible Omicron variant surges in many locations around the world. With WordCamp Birmingham less than a month away, the event’s COVID precautions came under greater scrutiny this week, as organizers work to adapt to the changing pandemic landscape.
\n\n\n\nYesterday, the event’s masking policy stated “Masks are required for entry and preferred throughout the event,” setting off a heated conversation on Twitter.
\n\n\n\n\n\n\n\nWordCamp Birmingham has since updated its COVID-19 safety protocols to require masks inside the venue except when eating or drinking:
\n\n\n\nAttendees are also required to be vaccinated, or have recovered from COVID-19 within the last 3 months, or have recently tested negative. It doesn’t state any specific timeframe for having tested negative.
\n\n\n\n“Our original masking recommendations were published prior to Omicron really taking hold and were based on our local laws, local health regulations, our venue’s input, and direction from WordPress Community Support,” WordCamp Birmingham lead organizer Ryan Marks said. “Since Omicron has become more prevalent, we are monitoring the situation and have evolved our guidelines as a result.”
\n\n\n\nIn what seemed to be an attempt to woo vaccine-hesitant Americans, the CDC removed indoor masking requirements for those who were fully vaccinated in May 2021, when vaccines were working well. Since that time, coronavirus variants have emerged that evade both vaccine and virus-induced immunity. However, many gatherings and indoor event organizers have been slow to change their COVID-19 protocols in response to the latest developments.
\n\n\n\nWordCamp Europe tweeted an update recognizing the recent discussions and changeable nature of the current threat, linking to a post on COVID planning from November 2021.
\n\n\n\n\n\n\n\nNilo Velez, one of the lead organizers for WordCamp Seville, which took place in mid-December 2021, responded to WCEU organizers with some advice.
\n\n\n\n“I’ve been organizing in-person events during the last few months (including WordCamp Sevilla, with zero positives so far),” Velez said. “My top two take aways: 1) Airflow is your friend: plan for well-ventilated spaces and use CO2 meters on high people concentration areas.
\n\n\n\n“2) Enforce the use of face masks indoors, always. Enforce as in ‘Put a f*cking mask on or go home’ Excessive? State of the Word proves otherwise.”
\n\n\n\nVelez referenced the recent incident at the State of the Word 2021 event where attendees were not required to wear masks indoors. Multiple attendees reported infections following the event, which generated exposure notices for all in attendance. Attendees were left to make their own choices regarding indoor masking, and the resulting lack of masks was alarming to many onlookers as Omicron was spreading rapidly through New York City. Prospective attendees for future in-person WordCamps shared their reservations about the lax protocols on Twitter and said they are reconsidering WordCamps as a result.
\n\n\n\n“In my opinion, masks are not a choice but a must,” Velez told the Tavern. “In Seville, the precautions we took were simple:
\n\n\n\nVelez said his team had a streaming option for those who aren’t ready for in-person WordCamps and they were ready to switch to an entirely online event if necessary.
\n\n\n\n“We also have had three in-person meetups with no reported cases so far,” Velez said. “Weather helps a lot. Today at noon (5th of January) we were at 20ºC (68ºC). That allows you to stay indoors only during the talks and have all the social activities outside.”
\n\n\n\nWordCamp Birmingham attendees have posted about how excited they are to attend the event, no matter what the protocols, after two years away from their WordPress friends. On the other hand, there are others who hold the opinion that organizing any kind of in-person event at this time while, hospitals are becoming overwhelmed, is premature and irresponsible.
\n\n\n\n\n\n\n\nAfter speaking with WordCamp Europe’s lead organizers this morning, they are closely monitoring the situation and believe that a safe in-person event is still possible.
\n\n\n\n“WordCamp Seville was a successful and safe event,” co-organizer Bernhard Kau said. “Some of our organizers went there. Also, the Web Summit in Lisbon with more than 42,000 had excellent measures. Those are events we see as examples.”
\n\n\n\nOrganizers are eager to host the first in-person WordCamp Europe in three years but are willing to move to alternatives if new pandemic threats emerge in the next five months.
\n\n\n\n“At the moment our plan is to go for an in-person event but there will always be a plan B or C,” WCEU Public Relations team leader Evangelia Pappa said. “We wouldn’t want people to get in danger in any way. These people are our friends and family. They’re not just attendees or sponsors, speakers, volunteers. Keeping safe means also keeping our beloved safe when we get back home.”
\n\n\n\nPappa said the team plans to follow all local regulations for in-person events with more than 1,000 attendees in a closed space. The regulations keep changing but for now they are requiring the following:
\n\n\n\n“Since we’re keeping constantly an eye on this, we may enforce other regulations on top of these, but it depends on the gravity of the situation,” Pappa said.
\n\n\n\n“Our aim is to get back to seeing our people, have a great in-person event, but when everyone goes back home, we’re all safe, our families are safe and we get to remember the WCEU 2022 as an amazing experience.”
\n\n\n\nWordPress’ Community Team has been discussing new ideas for supporting the safety of in-person events in 2022 and plans to share more in a blog post next week. One safety measure suggested is mandatory masks for all attendees (even in regions that do not have a mask mandate at this time). WordCamp Central has agreed to cover the budget for additional safety measures like free masks and hand sanitization stations. Contributors plan to engage this sensitive topic with a larger discussion next week.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jan 2022 22:14: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:46;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WordPress.org blog: WordPress 5.8.3 Security Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11999\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2022/01/wordpress-5-8-3-security-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3679:\"This security release features four security fixes. Because this is a security release, it is recommended that you update your sites immediately. All versions since WordPress 3.7 have also been updated.
\n\n\n\nWordPress 5.8.3 is a short-cycle security release. The next major release will be version 5.9, which is already in the Release Candidate stage.
\n\n\n\nYou can update to WordPress 5.8.3 by downloading from WordPress.org or visiting your Dashboard → Updates and clicking Update Now.
\n\n\n\nIf you have sites that support automatic background updates, they’ve already started the update process.
\n\n\n\nFour security issues affect WordPress versions between 3.7 and 5.8. If you haven’t yet updated to 5.8, all WordPress versions since 3.7 have also been updated to fix the following security issue (except where noted otherwise):
\n\n\n\nThank you to all of the reporters above for privately disclosing the vulnerabilities. This gave the security team time to fix the vulnerabilities before WordPress sites could be attacked. Thank you to the members of the WordPress security team for implementing these fixes in WordPress.
\n\n\n\nFor more information, check out the 5.8.3 HelpHub documentation page.
\n\n\n\nThe 5.8.3 release was led by @desrosj and @circlecube.
\n\n\n\nIn addition to the security researchers and release squad members mentioned above, thank you to everyone who helped make WordPress 5.8.3 happen:
\n\n\n\nAlex Concha, Dion Hulse, Dominik Schilling, ehtis, Evan Mullins, Jake Spurlock, Jb Audras, Jonathan Desrosiers, Ian Dunn, Peter Wilson, Sergey Biryukov, vortfu, and zieladam.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jan 2022 21:02: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: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:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: Gutenberg 12.3 Introduces New Blocks, Design Options, and a Complete Core Blocks Reference\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=127924\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:241:\"https://wptavern.com/gutenberg-12-3-introduces-new-blocks-design-options-and-a-complete-core-blocks-reference?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-12-3-introduces-new-blocks-design-options-and-a-complete-core-blocks-reference\";s: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:6363:\"The first Gutenberg plugin release of the year contains loads of features. Developers should enjoy a completed core blocks reference. Group block spacing controls offer more layout flexibility, and a new Post Author Name block has arrived on the scene. Overall, the site editing experience is shaping up.
\n\n\n\nThe latest release adds a couple of nice-to-have design options. The Group block now supports typography options. This should make it easier for users and theme designers to change the font size, family, and more for all child blocks at once. The Spacer block supports custom units, so users are no longer restricted to pixels. Paragraphs now have a font-family option.
\n\n\n\nTheme authors can now register “nameless” font sizes to support the core sizes. They also have new Comments Pagination Previous and Next blocks for handling paged comments.
\n\n\n\nUsers without the edit_theme_options capability (Administrators by default) can no longer create nav menus via the site editor. However, they can select an existing one via the Navigation block. This returns menu creation to its original restrictions.
Let us dive right into some of the big features.
\n\n\n\nWhile the average user may never look at it, the Core Blocks Reference in the editor handbook should be a welcome sight to developers. It is almost impossible to remember all the blocks and everything about them.
\n\n\n\nThe data is automatically generated. Each block in the reference displays the following information:
\n\n\n\nI would love for WordPress.org to automatically display this for all block plugins in the future. The data is standardized through block.json files, so there is no reason it should not be possible. Otherwise, individual plugin authors would need to recreate this to share their own references.
Users can now save the image used for the Site Logo block as their site icon (favicon) via the site editor. This is a step in the right direction now that the customizer is disappearing for block theme users. They will need an easy way to set this.
\n\n\n\nThere are two downsides to this solution. The first is that this option is enabled by default. If a user does not notice it, they could be overwriting their existing site icon without knowing. Logos and icons do not always match. The WP Tavern website shows a prime example of this.
\n\n\n\nThe second issue is that we need a dedicated site icon option. Adding it to one of the available settings screens in the admin would be a simple solution. That would give time to figure out how to eventually work it into the site editor.
\n\n\n\nGutenberg 12.3 introduces a new Post Author Name block. As its name suggests, it displays a post’s author. It is something so seemingly simple, but when you have been waiting ages for it — well, since May 2021, technically — it feels monumental. To show how happy I am to see this block, I made five custom styles for it.
\n\n\n\nThis is a part of an effort to split the original Post Author block into smaller components. Currently, it can display the author name, avatar, bio, and custom byline text. If a theme designer needs just the author text in a one-line meta area, a user enabling those other elements via the site editor usually blows the entire thing up.
\n\n\n\nSeparate Post Author Avatar and Post Author Bio blocks are planned. When these next two land, it will give theme authors more flexibility.
\n\n\n\nI feel like a kid in a toyshop to see more than one of my long-time gripes taken care of in this release. The Group block now supports the Block Spacing control. This allows users and theme authors to define the margin between its child blocks.
\n\n\n\nOne of the primary use cases for this is collapsing margins between similar elements. For example, a user might want to group three File blocks together without any whitespace between them, as shown in the following screenshot:
\n\n\n\nTypically, these blocks would have the standard top margins between each. By setting the block spacing to 0, users can wipe them out.
“Zeroing out” margins has been one of the most frustrating problems to solve for some themers, especially when dealing with wide or full-aligned blocks. The WordPress editor’s HTML markup does not match the front-end in those cases. A block spacing control on the Group block solves this issue for several scenarios.
\n\n\n\nOf course, it is not all about getting rid of margins between blocks. It is also possible to create even more space.
\n\n\n\nWhen using the Row variation of the Group block, the spacing is horizontal. This should also take care of a lot of theme layout needs.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jan 2022 01:14:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WordPress.org blog: The Month in WordPress – December 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://wordpress.org/news/?p=11972\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2022/01/the-month-in-wordpress-december-2021/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:13055:\"December was a busy month for the WordPress community. In the latest episode of the WP Briefing podcast, WordPress Executive Director Josepha Haden Chomphosy shares a carol of thanks and shows her gratitude to all the people who make the WordPress project a success.
\n\n\n\n\n\n\n\n(…) I know that we have gotten so much done together in the last few years. And I am equally sure that we’re going to get so much done in the years to come. And so thank you all so much for your continued work with WordPress and the way that you just bring your best at all times.
Josepha Haden, Executive Director of the WordPress project
We said goodbye to 2021 with the annual State of the Word, along with the release of WordPress 5.9 Beta 4, among many other exciting updates. Read on to learn more about the latest community achievements.
\n\n\n\n\n\n\n\nAre you interested in contributing to WordPress core? Join the #core channel, follow the Core Team blog, and check out the team handbook. Also, don’t miss the Core Team’s weekly developer chat on Wednesdays at 8 PM UTC.
The Core Team launched two new versions of Gutenberg last month. Both come with new features, code quality improvements, and bug fixes.
\n\n\n\n\n\n\n\nWant to get involved in developing Gutenberg? Follow the Core Team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Make WordPress Slack. Follow the #gutenberg-new tag for details on the latest updates.
\n\n\n\nIf you missed the event’s livestream, you could watch the State of the Word recording and the Q&A session on WordPress.tv.
\n\n\n\nAre you looking for some 5.9 resources to share with your local community? Check out the WordPress 5.9 Talking Points for Meetup Organizers post.
\n\n\n\nShare your feedback on WordPress 5.9.
Don’t miss the following upcoming WordCamps: WordCamp Birmingham, Alabama 2022, WordCamp Genève 2022, WordCamp Vienna 2022, and WordCamp Europe 2022.
\n\n\n\n\n\n\n\nThe Call For Sponsors and Call For Speakers for WordCamp Europe 2022 are open! Read this post to learn more about the Organizing Team’s plans for the first in-person WordCamp Europe in three years.
Have a story that we could include in the next ‘Month in WordPress’ post? Let us know by filling out this form.
\n\n\n\nThe following folks contributed to December 2021’s Month in WordPress: @anjanavasan, @harishanker @lmurillom @meher @nalininonstopnewsuk @webcommsat
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jan 2022 19:03:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"rmartinezduque\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: Anariel Design Releases Bricksy, Its Third WordPress Block Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=127820\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/anariel-design-releases-bricksy-its-third-wordpress-block-theme?utm_source=rss&utm_medium=rss&utm_campaign=anariel-design-releases-bricksy-its-third-wordpress-block-theme\";s: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:4675:\"Yesterday, Anariel Design’s third block theme, Bricksy, went live in the WordPress.org directory. Ana Segota, the co-founder and self-proclaimed “creative motor” of the company, has almost become a master at block-based theme design at this point, and this project is just her showing off her skills.
\n\n\n\nI actually took the theme for a spin over the weekend when I saw it was waiting in the review queue, so I have had a few days to play around with it. Despite a few trivial issues, it has quickly become one of my favorite block themes.
\n\n\n\nWhile I have generally liked Anariel Design’s two previous block themes, Naledi and Clove, I could not see myself installing them on a real-world project. They were simply not my personal style. However, Bricksy is a theme I would definitely use if I had a project for it at the moment.
\n\n\n\nOne of my favorite design elements is the cursive handwriting for the site logo, which is also used across various patterns.
\n\n\n\nThe downside is that these are images, so they are not easily recreated by end-users without Photoshop chops. I would like to see the team reconsider using a handwriting-style font — maybe one from Google Fonts — that allows users to add custom text directly from the editor.
\n\n\n\nBricksy has, hands down, some of the most beautifully-designed patterns I have seen in a block theme yet. In total, there are 32.
\n\n\n\nIt is making an early bid for my favorite theme of 2022, but I will not get ahead of myself. We still have almost an entire 12 months to go before I make that call.
\n\n\n\nIt even includes a custom social links layout. More and more themes are bundling their own takes on this pattern, but Bricksy’s color scheme and default Cover block image stand out.
\n\n\n\nWith 32 patterns, I could dedicate an entire post to them all, but I am limited on time. For the most part, they are layout-focused rather than industry-focused patterns. This means they can be used on a vast range of sites. However, the pricing tables and team sections make sense for small businesses. Bricksy also supports WooCommerce.
\n\n\n\nThe most striking thing about each pattern is that they all seem to fit within the theme’s overall design. Often, when themes include dozens of block patterns, some of them can feel like an additional option simply for the sake of adding one more thing in. And, that never feels like the case with Bricksy.
\n\n\n\nFor long-form content, the theme is decent. However, it could be better. Its 720px content width and 18px font size can quickly grow hard to read. Cutting the width anywhere from 80px to 120px makes it much more comfortable. Bumping the font size up a couple of extra pixels works too.
\n\n\n\nWhen I first activated the theme, I thought it was utterly broken. I had wondered how it managed to slip through the review system. The theme’s header was outputting seemingly random demo content. But, it was also familiar. I was positive it was a test post from my install.
\n\n\n\nThe issue was tough to hunt down. After everything from deactivating plugins to scrubbing templates from the database, I finally found it. The ref key for the Navigation block in the theme’s header.html template part was the culprit. Bricksy pointed to a specific post ID in the code:
<!-- wp:navigation {\"ref\":4790,\"layout\":{\"type\":\"flex\",\"setCascadingProperties\":true,\"justifyContent\":\"right\"}} /-->4790 is the ID of a literal post on my test install, so the Navigation block showed its content instead of a menu. Most likely, this was directly copied or exported from the site editor. Theme authors need to watch out for specific ID references in their code when building from the editor, making sure to remove them before shipping.
Aside from a couple of trivial issues and a single OMGBBQ one after activation, I enjoyed using the theme. It has found its place in my recommended-themes list.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jan 2022 23:42:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 24 Jan 2022 10:18:37 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Mon, 24 Jan 2022 10:00:07 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:2:\"br\";}}s:5:\"build\";s:14:\"20201016115008\";}', 'no'); INSERT INTO `perf_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (153, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1643062718', 'no'), (154, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1643019518', 'no'), (155, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1643062718', 'no'), (156, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '', 'no'); -- -------------------------------------------------------- -- -- Table structure for table `perf_postmeta` -- CREATE TABLE `perf_postmeta` ( `meta_id` bigint UNSIGNED NOT NULL, `post_id` bigint UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `perf_postmeta` -- INSERT INTO `perf_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES (1, 2, '_wp_page_template', 'default'), (2, 3, '_wp_page_template', 'default'), (5, 1726, '_menu_item_type', 'custom'), (6, 1726, '_menu_item_menu_item_parent', '0'), (7, 1726, '_menu_item_object_id', '1726'), (8, 1726, '_menu_item_object', 'custom'), (9, 1726, '_menu_item_target', ''), (10, 1726, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (11, 1726, '_menu_item_xfn', ''), (12, 1726, '_menu_item_url', '#'), (13, 1727, '_menu_item_type', 'custom'), (14, 1727, '_menu_item_menu_item_parent', '0'), (15, 1727, '_menu_item_object_id', '1727'), (16, 1727, '_menu_item_object', 'custom'), (17, 1727, '_menu_item_target', ''), (18, 1727, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (19, 1727, '_menu_item_xfn', ''), (20, 1727, '_menu_item_url', '#'), (21, 1728, '_menu_item_type', 'taxonomy'), (22, 1728, '_menu_item_menu_item_parent', '1727'), (23, 1728, '_menu_item_object_id', '31'), (24, 1728, '_menu_item_object', 'category'), (25, 1728, '_menu_item_target', ''), (26, 1728, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (27, 1728, '_menu_item_xfn', ''), (28, 1728, '_menu_item_url', ''), (29, 1729, '_menu_item_type', 'taxonomy'), (30, 1729, '_menu_item_menu_item_parent', '1727'), (31, 1729, '_menu_item_object_id', '136'), (32, 1729, '_menu_item_object', 'category'), (33, 1729, '_menu_item_target', ''), (34, 1729, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (35, 1729, '_menu_item_xfn', ''), (36, 1729, '_menu_item_url', ''), (37, 1730, '_menu_item_type', 'taxonomy'), (38, 1730, '_menu_item_menu_item_parent', '1727'), (39, 1730, '_menu_item_object_id', '52'), (40, 1730, '_menu_item_object', 'category'), (41, 1730, '_menu_item_target', ''), (42, 1730, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (43, 1730, '_menu_item_xfn', ''), (44, 1730, '_menu_item_url', ''), (45, 1731, '_menu_item_type', 'custom'), (46, 1731, '_menu_item_menu_item_parent', '0'), (47, 1731, '_menu_item_object_id', '1731'), (48, 1731, '_menu_item_object', 'custom'), (49, 1731, '_menu_item_target', ''), (50, 1731, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (51, 1731, '_menu_item_xfn', ''), (52, 1731, '_menu_item_url', '#'), (53, 1732, '_menu_item_type', 'custom'), (54, 1732, '_menu_item_menu_item_parent', '1731'), (55, 1732, '_menu_item_object_id', '1732'), (56, 1732, '_menu_item_object', 'custom'), (57, 1732, '_menu_item_target', ''), (58, 1732, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (59, 1732, '_menu_item_xfn', ''), (60, 1732, '_menu_item_url', '#'), (61, 1733, '_menu_item_type', 'custom'), (62, 1733, '_menu_item_menu_item_parent', '1732'), (63, 1733, '_menu_item_object_id', '1733'), (64, 1733, '_menu_item_object', 'custom'), (65, 1733, '_menu_item_target', ''), (66, 1733, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (67, 1733, '_menu_item_xfn', ''), (68, 1733, '_menu_item_url', '#'), (69, 1734, '_menu_item_type', 'custom'), (70, 1734, '_menu_item_menu_item_parent', '1733'), (71, 1734, '_menu_item_object_id', '1734'), (72, 1734, '_menu_item_object', 'custom'), (73, 1734, '_menu_item_target', ''), (74, 1734, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (75, 1734, '_menu_item_xfn', ''), (76, 1734, '_menu_item_url', '#'), (77, 1735, '_menu_item_type', 'custom'), (78, 1735, '_menu_item_menu_item_parent', '1734'), (79, 1735, '_menu_item_object_id', '1735'), (80, 1735, '_menu_item_object', 'custom'), (81, 1735, '_menu_item_target', ''), (82, 1735, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (83, 1735, '_menu_item_xfn', ''), (84, 1735, '_menu_item_url', '#'), (85, 1736, '_menu_item_type', 'custom'), (86, 1736, '_menu_item_menu_item_parent', '1735'), (87, 1736, '_menu_item_object_id', '1736'), (88, 1736, '_menu_item_object', 'custom'), (89, 1736, '_menu_item_target', ''), (90, 1736, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (91, 1736, '_menu_item_xfn', ''), (92, 1736, '_menu_item_url', '#'), (93, 1737, '_menu_item_type', 'custom'), (94, 1737, '_menu_item_menu_item_parent', '1736'), (95, 1737, '_menu_item_object_id', '1737'), (96, 1737, '_menu_item_object', 'custom'), (97, 1737, '_menu_item_target', ''), (98, 1737, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (99, 1737, '_menu_item_xfn', ''), (100, 1737, '_menu_item_url', '#'), (101, 1738, '_menu_item_type', 'custom'), (102, 1738, '_menu_item_menu_item_parent', '1737'), (103, 1738, '_menu_item_object_id', '1738'), (104, 1738, '_menu_item_object', 'custom'), (105, 1738, '_menu_item_target', ''), (106, 1738, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (107, 1738, '_menu_item_xfn', ''), (108, 1738, '_menu_item_url', '#'), (109, 1739, '_menu_item_type', 'custom'), (110, 1739, '_menu_item_menu_item_parent', '1738'), (111, 1739, '_menu_item_object_id', '1739'), (112, 1739, '_menu_item_object', 'custom'), (113, 1739, '_menu_item_target', ''), (114, 1739, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (115, 1739, '_menu_item_xfn', ''), (116, 1739, '_menu_item_url', '#'), (117, 1740, '_menu_item_type', 'custom'), (118, 1740, '_menu_item_menu_item_parent', '1739'), (119, 1740, '_menu_item_object_id', '1740'), (120, 1740, '_menu_item_object', 'custom'), (121, 1740, '_menu_item_target', ''), (122, 1740, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (123, 1740, '_menu_item_xfn', ''), (124, 1740, '_menu_item_url', '#'), (125, 1741, '_menu_item_type', 'custom'), (126, 1741, '_menu_item_menu_item_parent', '1740'), (127, 1741, '_menu_item_object_id', '1741'), (128, 1741, '_menu_item_object', 'custom'), (129, 1741, '_menu_item_target', ''), (130, 1741, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (131, 1741, '_menu_item_xfn', ''), (132, 1741, '_menu_item_url', '#'), (133, 1742, '_menu_item_type', 'custom'), (134, 1742, '_menu_item_menu_item_parent', '0'), (135, 1742, '_menu_item_object_id', '1742'), (136, 1742, '_menu_item_object', 'custom'), (137, 1742, '_menu_item_target', ''), (138, 1742, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (139, 1742, '_menu_item_xfn', ''), (140, 1742, '_menu_item_url', '#'), (141, 1743, '_menu_item_type', 'custom'), (142, 1743, '_menu_item_menu_item_parent', '0'), (143, 1743, '_menu_item_object_id', '1743'), (144, 1743, '_menu_item_object', 'custom'), (145, 1743, '_menu_item_target', ''), (146, 1743, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (147, 1743, '_menu_item_xfn', ''), (148, 1743, '_menu_item_url', '#'), (149, 1744, '_menu_item_type', 'custom'), (150, 1744, '_menu_item_menu_item_parent', '1742'), (151, 1744, '_menu_item_object_id', '1744'), (152, 1744, '_menu_item_object', 'custom'), (153, 1744, '_menu_item_target', ''), (154, 1744, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (155, 1744, '_menu_item_xfn', ''), (156, 1744, '_menu_item_url', '#'), (157, 1745, '_menu_item_type', 'custom'), (158, 1745, '_menu_item_menu_item_parent', '1742'), (159, 1745, '_menu_item_object_id', '1745'), (160, 1745, '_menu_item_object', 'custom'), (161, 1745, '_menu_item_target', ''), (162, 1745, '_menu_item_classes', 'a:1:{i:0;s:21:\"custom-menu-css-class\";}'), (163, 1745, '_menu_item_xfn', ''), (164, 1745, '_menu_item_url', '#'), (165, 1746, '_menu_item_type', 'custom'), (166, 1746, '_menu_item_menu_item_parent', '1742'), (167, 1746, '_menu_item_object_id', '1746'), (168, 1746, '_menu_item_object', 'custom'), (169, 1746, '_menu_item_target', '_blank'), (170, 1746, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (171, 1746, '_menu_item_xfn', ''), (172, 1746, '_menu_item_url', 'https://wordpressfoundation.org/'), (173, 1747, '_menu_item_type', 'custom'), (174, 1747, '_menu_item_menu_item_parent', '0'), (175, 1747, '_menu_item_object_id', '1747'), (176, 1747, '_menu_item_object', 'custom'), (177, 1747, '_menu_item_target', ''), (178, 1747, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (179, 1747, '_menu_item_xfn', ''), (180, 1747, '_menu_item_url', 'https://twitter.com/wordpress'), (181, 1748, '_menu_item_type', 'custom'), (182, 1748, '_menu_item_menu_item_parent', '0'), (183, 1748, '_menu_item_object_id', '1748'), (184, 1748, '_menu_item_object', 'custom'), (185, 1748, '_menu_item_target', ''), (186, 1748, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (187, 1748, '_menu_item_xfn', ''), (188, 1748, '_menu_item_url', 'https://www.facebook.com/WordPress/'), (189, 1749, '_menu_item_type', 'custom'), (190, 1749, '_menu_item_menu_item_parent', '0'), (191, 1749, '_menu_item_object_id', '1749'), (192, 1749, '_menu_item_object', 'custom'), (193, 1749, '_menu_item_target', ''), (194, 1749, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (195, 1749, '_menu_item_xfn', ''), (196, 1749, '_menu_item_url', 'https://github.com/WordPress/'), (197, 1750, '_menu_item_type', 'custom'), (198, 1750, '_menu_item_menu_item_parent', '0'), (199, 1750, '_menu_item_object_id', '1750'), (200, 1750, '_menu_item_object', 'custom'), (201, 1750, '_menu_item_target', ''), (202, 1750, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (203, 1750, '_menu_item_xfn', ''), (204, 1750, '_menu_item_url', 'https://www.instagram.com/photomatt/'), (205, 1751, '_menu_item_type', 'custom'), (206, 1751, '_menu_item_menu_item_parent', '0'), (207, 1751, '_menu_item_object_id', '1751'), (208, 1751, '_menu_item_object', 'custom'), (209, 1751, '_menu_item_target', ''), (210, 1751, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (211, 1751, '_menu_item_xfn', ''), (212, 1751, '_menu_item_url', 'https://www.linkedin.com/company/wordpress/'), (213, 1752, '_menu_item_type', 'post_type'), (214, 1752, '_menu_item_menu_item_parent', '0'), (215, 1752, '_menu_item_object_id', '703'), (216, 1752, '_menu_item_object', 'page'), (217, 1752, '_menu_item_target', ''), (218, 1752, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (219, 1752, '_menu_item_xfn', ''), (220, 1752, '_menu_item_url', ''), (221, 1753, '_menu_item_type', 'post_type'), (222, 1753, '_menu_item_menu_item_parent', '0'), (223, 1753, '_menu_item_object_id', '1725'), (224, 1753, '_menu_item_object', 'page'), (225, 1753, '_menu_item_target', ''), (226, 1753, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (227, 1753, '_menu_item_xfn', ''), (228, 1753, '_menu_item_url', ''), (229, 1754, '_menu_item_type', 'post_type'), (230, 1754, '_menu_item_menu_item_parent', '1753'), (231, 1754, '_menu_item_object_id', '501'), (232, 1754, '_menu_item_object', 'page'), (233, 1754, '_menu_item_target', ''), (234, 1754, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (235, 1754, '_menu_item_xfn', ''), (236, 1754, '_menu_item_url', ''), (237, 1755, '_menu_item_type', 'post_type'), (238, 1755, '_menu_item_menu_item_parent', '1753'), (239, 1755, '_menu_item_object_id', '155'), (240, 1755, '_menu_item_object', 'page'), (241, 1755, '_menu_item_target', ''), (242, 1755, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (243, 1755, '_menu_item_xfn', ''), (244, 1755, '_menu_item_url', ''), (245, 1756, '_menu_item_type', 'post_type'), (246, 1756, '_menu_item_menu_item_parent', '1753'), (247, 1756, '_menu_item_object_id', '156'), (248, 1756, '_menu_item_object', 'page'), (249, 1756, '_menu_item_target', ''), (250, 1756, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (251, 1756, '_menu_item_xfn', ''), (252, 1756, '_menu_item_url', ''), (253, 1757, '_menu_item_type', 'post_type'), (254, 1757, '_menu_item_menu_item_parent', '0'), (255, 1757, '_menu_item_object_id', '146'), (256, 1757, '_menu_item_object', 'page'), (257, 1757, '_menu_item_target', ''), (258, 1757, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (259, 1757, '_menu_item_xfn', ''), (260, 1757, '_menu_item_url', ''), (261, 1758, '_menu_item_type', 'post_type'), (262, 1758, '_menu_item_menu_item_parent', '0'), (263, 1758, '_menu_item_object_id', '703'), (264, 1758, '_menu_item_object', 'page'), (265, 1758, '_menu_item_target', ''), (266, 1758, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (267, 1758, '_menu_item_xfn', ''), (268, 1758, '_menu_item_url', ''), (269, 1759, '_menu_item_type', 'post_type'), (270, 1759, '_menu_item_menu_item_parent', '0'), (271, 1759, '_menu_item_object_id', '701'), (272, 1759, '_menu_item_object', 'page'), (273, 1759, '_menu_item_target', ''), (274, 1759, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (275, 1759, '_menu_item_xfn', ''), (276, 1759, '_menu_item_url', ''), (277, 1760, '_menu_item_type', 'post_type'), (278, 1760, '_menu_item_menu_item_parent', '0'), (279, 1760, '_menu_item_object_id', '1725'), (280, 1760, '_menu_item_object', 'page'), (281, 1760, '_menu_item_target', ''), (282, 1760, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (283, 1760, '_menu_item_xfn', ''), (284, 1760, '_menu_item_url', ''), (285, 1761, '_menu_item_type', 'post_type'), (286, 1761, '_menu_item_menu_item_parent', '0'), (287, 1761, '_menu_item_object_id', '501'), (288, 1761, '_menu_item_object', 'page'), (289, 1761, '_menu_item_target', ''), (290, 1761, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (291, 1761, '_menu_item_xfn', ''), (292, 1761, '_menu_item_url', ''), (293, 1762, '_menu_item_type', 'post_type'), (294, 1762, '_menu_item_menu_item_parent', '0'), (295, 1762, '_menu_item_object_id', '155'), (296, 1762, '_menu_item_object', 'page'), (297, 1762, '_menu_item_target', ''), (298, 1762, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (299, 1762, '_menu_item_xfn', ''), (300, 1762, '_menu_item_url', ''), (301, 1763, '_menu_item_type', 'post_type'), (302, 1763, '_menu_item_menu_item_parent', '0'), (303, 1763, '_menu_item_object_id', '156'), (304, 1763, '_menu_item_object', 'page'), (305, 1763, '_menu_item_target', ''), (306, 1763, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (307, 1763, '_menu_item_xfn', ''), (308, 1763, '_menu_item_url', ''), (309, 1764, '_menu_item_type', 'post_type'), (310, 1764, '_menu_item_menu_item_parent', '0'), (311, 1764, '_menu_item_object_id', '174'), (312, 1764, '_menu_item_object', 'page'), (313, 1764, '_menu_item_target', ''), (314, 1764, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (315, 1764, '_menu_item_xfn', ''), (316, 1764, '_menu_item_url', ''), (317, 1765, '_menu_item_type', 'post_type'), (318, 1765, '_menu_item_menu_item_parent', '0'), (319, 1765, '_menu_item_object_id', '173'), (320, 1765, '_menu_item_object', 'page'), (321, 1765, '_menu_item_target', ''), (322, 1765, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (323, 1765, '_menu_item_xfn', ''), (324, 1765, '_menu_item_url', ''), (325, 1766, '_menu_item_type', 'post_type'), (326, 1766, '_menu_item_menu_item_parent', '0'), (327, 1766, '_menu_item_object_id', '172'), (328, 1766, '_menu_item_object', 'page'), (329, 1766, '_menu_item_target', ''), (330, 1766, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (331, 1766, '_menu_item_xfn', ''), (332, 1766, '_menu_item_url', ''), (333, 1767, '_menu_item_type', 'post_type'), (334, 1767, '_menu_item_menu_item_parent', '0'), (335, 1767, '_menu_item_object_id', '146'), (336, 1767, '_menu_item_object', 'page'), (337, 1767, '_menu_item_target', ''), (338, 1767, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (339, 1767, '_menu_item_xfn', ''), (340, 1767, '_menu_item_url', ''), (341, 1768, '_menu_item_type', 'post_type'), (342, 1768, '_menu_item_menu_item_parent', '0'), (343, 1768, '_menu_item_object_id', '703'), (344, 1768, '_menu_item_object', 'page'), (345, 1768, '_menu_item_target', ''), (346, 1768, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (347, 1768, '_menu_item_xfn', ''), (348, 1768, '_menu_item_url', ''), (349, 1769, '_menu_item_type', 'post_type'), (350, 1769, '_menu_item_menu_item_parent', '0'), (351, 1769, '_menu_item_object_id', '701'), (352, 1769, '_menu_item_object', 'page'), (353, 1769, '_menu_item_target', ''), (354, 1769, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (355, 1769, '_menu_item_xfn', ''), (356, 1769, '_menu_item_url', ''), (357, 1770, '_menu_item_type', 'post_type'), (358, 1770, '_menu_item_menu_item_parent', '0'), (359, 1770, '_menu_item_object_id', '1725'), (360, 1770, '_menu_item_object', 'page'), (361, 1770, '_menu_item_target', ''), (362, 1770, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (363, 1770, '_menu_item_xfn', ''), (364, 1770, '_menu_item_url', ''), (365, 1771, '_menu_item_type', 'post_type'), (366, 1771, '_menu_item_menu_item_parent', '1770'), (367, 1771, '_menu_item_object_id', '501'), (368, 1771, '_menu_item_object', 'page'), (369, 1771, '_menu_item_target', ''), (370, 1771, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (371, 1771, '_menu_item_xfn', ''), (372, 1771, '_menu_item_url', ''), (373, 1772, '_menu_item_type', 'post_type'), (374, 1772, '_menu_item_menu_item_parent', '1770'), (375, 1772, '_menu_item_object_id', '155'), (376, 1772, '_menu_item_object', 'page'), (377, 1772, '_menu_item_target', ''), (378, 1772, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (379, 1772, '_menu_item_xfn', ''), (380, 1772, '_menu_item_url', ''), (381, 1773, '_menu_item_type', 'post_type'), (382, 1773, '_menu_item_menu_item_parent', '1770'), (383, 1773, '_menu_item_object_id', '156'), (384, 1773, '_menu_item_object', 'page'), (385, 1773, '_menu_item_target', ''), (386, 1773, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (387, 1773, '_menu_item_xfn', ''), (388, 1773, '_menu_item_url', ''), (389, 1774, '_menu_item_type', 'post_type'), (390, 1774, '_menu_item_menu_item_parent', '0'), (391, 1774, '_menu_item_object_id', '174'), (392, 1774, '_menu_item_object', 'page'), (393, 1774, '_menu_item_target', ''), (394, 1774, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (395, 1774, '_menu_item_xfn', ''), (396, 1774, '_menu_item_url', ''), (397, 1775, '_menu_item_type', 'post_type'), (398, 1775, '_menu_item_menu_item_parent', '1774'), (399, 1775, '_menu_item_object_id', '173'), (400, 1775, '_menu_item_object', 'page'), (401, 1775, '_menu_item_target', ''), (402, 1775, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (403, 1775, '_menu_item_xfn', ''), (404, 1775, '_menu_item_url', ''), (405, 1776, '_menu_item_type', 'post_type'), (406, 1776, '_menu_item_menu_item_parent', '1775'), (407, 1776, '_menu_item_object_id', '172'), (408, 1776, '_menu_item_object', 'page'), (409, 1776, '_menu_item_target', ''), (410, 1776, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (411, 1776, '_menu_item_xfn', ''), (412, 1776, '_menu_item_url', ''), (413, 1777, '_menu_item_type', 'post_type'), (414, 1777, '_menu_item_menu_item_parent', '0'), (415, 1777, '_menu_item_object_id', '146'), (416, 1777, '_menu_item_object', 'page'), (417, 1777, '_menu_item_target', ''), (418, 1777, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (419, 1777, '_menu_item_xfn', ''), (420, 1777, '_menu_item_url', ''), (421, 582, '_oembed_4321638fc1a6fee26443f7fe8a70a871', ''), (422, 582, '_oembed_29351fff85c1be1d1e9a965a0332a861', ''), (423, 582, '_oembed_9fcc86d7d9398ff736577f922307f64d', ''), (424, 582, '_oembed_366237792d32461d0052efb2edec37f5', ''), (425, 582, '_oembed_37fdfe862c13c46a93be2921279bf675', ''), (426, 587, 'enclosure', 'https://wpthemetestdata.files.wordpress.com/2008/06/originaldixielandjazzbandwithalbernard-stlouisblues.mp3\n3043247\naudio/mpeg\n'), (427, 1011, '_thumbnail_id', '1022'), (428, 1016, '_thumbnail_id', '1027'), (429, 1163, '_thumbnail_id', '1628'), (430, 1177, '_thumbnail_id', '1023'), (431, 1179, '_oembed_time_d01e104b758ab65a49dfdede5913069c', '1410548953'), (432, 1179, '_oembed_ac49b172e1844531a885a53eff2efd91', ''), (433, 1179, '_oembed_time_ac49b172e1844531a885a53eff2efd91', '1420203780'), (434, 1179, '_oembed_d01e104b758ab65a49dfdede5913069c', ''), (435, 1778, 'enclosure', 'https://wpthemetestdata.files.wordpress.com/2008/06/originaldixielandjazzbandwithalbernard-stlouisblues.mp3\n3043247\naudio/mpeg\n'), (436, 1778, 'enclosure', 'https://wpthemetestdata.files.wordpress.com/2013/12/2014-slider-mobile-behavior.mov\n29881426\nvideo/quicktime\n'), (437, 1781, '_oembed_874fe46ae491204826d1694d2ef33bc0', ''), (438, 1781, '_oembed_8391feecdd4849ee3e1e157e0c2149eb', 'WordPress 5.0 Beta 2 https://t.co/Bn5QRqAwLN
— WordPress (@WordPress) October 30, 2018
'), (439, 1781, '_oembed_time_8391feecdd4849ee3e1e157e0c2149eb', '1541053042'), (440, 1781, '_oembed_time_874fe46ae491204826d1694d2ef33bc0', '1541177221'), (441, 1781, '_oembed_8954002f3cee8b890d4d590be308ea1a', ''), (442, 1781, '_oembed_time_8954002f3cee8b890d4d590be308ea1a', '1541177221'), (443, 1781, '_oembed_b0ae412e6c1109b456d564d524e039f4', 'WordPress 5.0 Beta 2 https://t.co/Bn5QRqAwLN
— WordPress (@WordPress) October 30, 2018
Many of the WordPress contribution teams have been working hard on the new WordPress editor, and the tools, services,...
Publicerat av WordPress Måndag 3 september 2018
'), (446, 1781, '_oembed_time_6fa7bb5895e39bde447f2aa42112350c', '1541177222'), (447, 1781, '_oembed_f284bc472428c21b3a384f58eeabdfe9', ''), (448, 1781, '_oembed_time_f284bc472428c21b3a384f58eeabdfe9', '1541177222'), (449, 1781, '_oembed_8c87a830bb75021cd30329a001513994', '
'), (450, 1781, '_oembed_time_8c87a830bb75021cd30329a001513994', '1541092484'), (451, 1781, '_oembed_574f2ec202809f638414562e06899fc7', ''), (452, 1781, '_oembed_time_574f2ec202809f638414562e06899fc7', '1541092484'), (453, 1781, '_oembed_26afb00b3c55411ff47bd585cbb4a4eb', 'WordPress 5.0 Beta 2 https://t.co/Bn5QRqAwLN
— WordPress (@WordPress) October 30, 2018
Many of the WordPress contribution teams have been working hard on the new WordPress editor, and the tools, services,...
Publicerat av WordPress Måndag 3 september 2018
'), (456, 1781, '_oembed_time_915f84bafbd1c86d8d5092d985805e15', '1541092485'), (457, 1781, '_oembed_e77958e689d5721871a80e7c8a612eb8', ''), (458, 1781, '_oembed_time_e77958e689d5721871a80e7c8a612eb8', '1541092486'), (459, 1787, '_thumbnail_id', '771'), (460, 1809, '_wp_page_template', 'default'), (461, 1811, '_wp_page_template', 'default'), (462, 1813, '_wp_page_template', 'default'), (463, 1814, '_menu_item_type', 'post_type'), (464, 1814, '_menu_item_menu_item_parent', '1726'), (465, 1814, '_menu_item_object_id', '1133'), (466, 1814, '_menu_item_object', 'page'), (467, 1814, '_menu_item_target', ''), (468, 1814, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (469, 1814, '_menu_item_xfn', ''), (470, 1814, '_menu_item_url', ''), (471, 1815, '_menu_item_type', 'post_type'), (472, 1815, '_menu_item_menu_item_parent', '1726'), (473, 1815, '_menu_item_object_id', '1134'), (474, 1815, '_menu_item_object', 'page'), (475, 1815, '_menu_item_target', ''), (476, 1815, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (477, 1815, '_menu_item_xfn', ''), (478, 1815, '_menu_item_url', ''), (479, 1816, '_menu_item_type', 'post_type'), (480, 1816, '_menu_item_menu_item_parent', '0'), (481, 1816, '_menu_item_object_id', '1133'), (482, 1816, '_menu_item_object', 'page'), (483, 1816, '_menu_item_target', ''), (484, 1816, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (485, 1816, '_menu_item_xfn', ''), (486, 1816, '_menu_item_url', ''), (487, 1817, '_menu_item_type', 'post_type'), (488, 1817, '_menu_item_menu_item_parent', '0'), (489, 1817, '_menu_item_object_id', '1134'), (490, 1817, '_menu_item_object', 'page'), (491, 1817, '_menu_item_target', ''), (492, 1817, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (493, 1817, '_menu_item_xfn', ''), (494, 1817, '_menu_item_url', ''), (495, 1818, '_menu_item_type', 'post_type'), (496, 1818, '_menu_item_menu_item_parent', '0'), (497, 1818, '_menu_item_object_id', '746'), (498, 1818, '_menu_item_object', 'page'), (499, 1818, '_menu_item_target', ''), (500, 1818, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (501, 1818, '_menu_item_xfn', ''), (502, 1818, '_menu_item_url', ''), (503, 1819, '_menu_item_type', 'post_type'), (504, 1819, '_menu_item_menu_item_parent', '0'), (505, 1819, '_menu_item_object_id', '748'), (506, 1819, '_menu_item_object', 'page'), (507, 1819, '_menu_item_target', ''), (508, 1819, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (509, 1819, '_menu_item_xfn', ''), (510, 1819, '_menu_item_url', ''), (511, 1820, '_menu_item_type', 'post_type'), (512, 1820, '_menu_item_menu_item_parent', '0'), (513, 1820, '_menu_item_object_id', '742'), (514, 1820, '_menu_item_object', 'page'), (515, 1820, '_menu_item_target', ''), (516, 1820, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (517, 1820, '_menu_item_xfn', ''), (518, 1820, '_menu_item_url', ''), (519, 1821, '_menu_item_type', 'post_type'), (520, 1821, '_menu_item_menu_item_parent', '0'), (521, 1821, '_menu_item_object_id', '744'), (522, 1821, '_menu_item_object', 'page'), (523, 1821, '_menu_item_target', ''), (524, 1821, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (525, 1821, '_menu_item_xfn', ''), (526, 1821, '_menu_item_url', ''), (527, 1822, '_menu_item_type', 'post_type'), (528, 1822, '_menu_item_menu_item_parent', '0'), (529, 1822, '_menu_item_object_id', '733'), (530, 1822, '_menu_item_object', 'page'), (531, 1822, '_menu_item_target', ''), (532, 1822, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (533, 1822, '_menu_item_xfn', ''), (534, 1822, '_menu_item_url', ''), (535, 1823, '_menu_item_type', 'post_type'), (536, 1823, '_menu_item_menu_item_parent', '0'), (537, 1823, '_menu_item_object_id', '735'), (538, 1823, '_menu_item_object', 'page'), (539, 1823, '_menu_item_target', ''), (540, 1823, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (541, 1823, '_menu_item_xfn', ''), (542, 1823, '_menu_item_url', ''), (543, 1824, '_menu_item_type', 'post_type'), (544, 1824, '_menu_item_menu_item_parent', '1770'), (545, 1824, '_menu_item_object_id', '1133'), (546, 1824, '_menu_item_object', 'page'), (547, 1824, '_menu_item_target', ''), (548, 1824, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (549, 1824, '_menu_item_xfn', ''), (550, 1824, '_menu_item_url', ''), (551, 1825, '_menu_item_type', 'post_type'), (552, 1825, '_menu_item_menu_item_parent', '1770'), (553, 1825, '_menu_item_object_id', '1134'), (554, 1825, '_menu_item_object', 'page'), (555, 1825, '_menu_item_target', ''), (556, 1825, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (557, 1825, '_menu_item_xfn', ''), (558, 1825, '_menu_item_url', ''), (559, 1826, '_menu_item_type', 'post_type'), (560, 1826, '_menu_item_menu_item_parent', '1775'), (561, 1826, '_menu_item_object_id', '746'), (562, 1826, '_menu_item_object', 'page'), (563, 1826, '_menu_item_target', ''), (564, 1826, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (565, 1826, '_menu_item_xfn', ''), (566, 1826, '_menu_item_url', ''), (567, 1827, '_menu_item_type', 'post_type'), (568, 1827, '_menu_item_menu_item_parent', '1775'), (569, 1827, '_menu_item_object_id', '748'), (570, 1827, '_menu_item_object', 'page'), (571, 1827, '_menu_item_target', ''), (572, 1827, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (573, 1827, '_menu_item_xfn', ''), (574, 1827, '_menu_item_url', ''), (575, 1828, '_menu_item_type', 'post_type'), (576, 1828, '_menu_item_menu_item_parent', '1774'), (577, 1828, '_menu_item_object_id', '742'), (578, 1828, '_menu_item_object', 'page'), (579, 1828, '_menu_item_target', ''), (580, 1828, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (581, 1828, '_menu_item_xfn', ''), (582, 1828, '_menu_item_url', ''), (583, 1829, '_menu_item_type', 'post_type'), (584, 1829, '_menu_item_menu_item_parent', '1774'), (585, 1829, '_menu_item_object_id', '744'), (586, 1829, '_menu_item_object', 'page'), (587, 1829, '_menu_item_target', ''), (588, 1829, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (589, 1829, '_menu_item_xfn', ''), (590, 1829, '_menu_item_url', ''), (591, 1830, '_menu_item_type', 'post_type'), (592, 1830, '_menu_item_menu_item_parent', '0'), (593, 1830, '_menu_item_object_id', '733'), (594, 1830, '_menu_item_object', 'page'), (595, 1830, '_menu_item_target', ''), (596, 1830, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (597, 1830, '_menu_item_xfn', ''), (598, 1830, '_menu_item_url', ''), (599, 1831, '_menu_item_type', 'post_type'), (600, 1831, '_menu_item_menu_item_parent', '0'), (601, 1831, '_menu_item_object_id', '735'), (602, 1831, '_menu_item_object', 'page'), (603, 1831, '_menu_item_target', ''), (604, 1831, '_menu_item_classes', 'a:1:{i:0;s:0:\"\";}'), (605, 1831, '_menu_item_xfn', ''), (606, 1831, '_menu_item_url', ''); -- -------------------------------------------------------- -- -- Table structure for table `perf_posts` -- CREATE TABLE `perf_posts` ( `ID` bigint UNSIGNED NOT NULL, `post_author` bigint UNSIGNED NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_parent` bigint UNSIGNED NOT NULL DEFAULT '0', `guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `menu_order` int NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_count` bigint NOT NULL DEFAULT '0' ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; -- -- Dumping data for table `perf_posts` -- INSERT INTO `perf_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES (1, 1, '2022-01-24 10:16:52', '2022-01-24 10:16:52', '\n
Welcome to WordPress. This is your first post. Edit or delete it, then start writing!
\n', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2022-01-24 10:16:52', '2022-01-24 10:16:52', '', 0, 'http://localhost:8080/wordpress/?p=1', 0, 'post', '', 1), (2, 1, '2022-01-24 10:16:52', '2022-01-24 10:16:52', '\nThis is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:
\n\n\n\n\n\n\n\nHi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)
...or something like this:
\n\n\n\n\n\n\n\nThe XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.
As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!
\n', 'Sample Page', '', 'publish', 'closed', 'open', '', 'sample-page', '', '', '2022-01-24 10:16:52', '2022-01-24 10:16:52', '', 0, 'http://localhost:8080/wordpress/?page_id=2', 0, 'page', '', 0), (3, 1, '2022-01-24 10:16:52', '2022-01-24 10:16:52', 'Suggested text: Our website address is: http://localhost:8080/wordpress.
Suggested text: When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Suggested text: If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Suggested text: If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Suggested text: Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Suggested text: If you request a password reset, your IP address will be included in the reset email.
Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
Suggested text: If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Suggested text: Visitor comments may be checked through an automated spam detection service.
', 'Privacy Policy', '', 'draft', 'closed', 'open', '', 'privacy-policy', '', '', '2022-01-24 10:16:52', '2022-01-24 10:16:52', '', 0, 'http://localhost:8080/wordpress/?page_id=3', 0, 'page', '', 0), (4, 1, '2022-01-24 10:17:09', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2022-01-24 10:17:09', '0000-00-00 00:00:00', '', 0, 'http://localhost:8080/wordpress/?p=4', 0, 'post', '', 0), (146, 1, '2007-09-04 09:52:50', '2007-09-04 16:52:50', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec mollis. Quisque convallis libero in sapien pharetra tincidunt. Aliquam elit ante, malesuada id, tempor eu, gravida id, odio. Maecenas suscipit, risus et eleifend imperdiet, nisi orci ullamcorper massa, et adipiscing orci velit quis magna. Praesent sit amet ligula id orci venenatis auctor. Phasellus porttitor, metus non tincidunt dapibus, orci pede pretium neque, sit amet adipiscing ipsum lectus et libero. Aenean bibendum. Curabitur mattis quam id urna. Vivamus dui. Donec nonummy lacinia lorem. Cras risus arcu, sodales ac, ultrices ac, mollis quis, justo. Sed a libero. Quisque risus erat, posuere at, tristique non, lacinia quis, eros.\n\nCras volutpat, lacus quis semper pharetra, nisi enim dignissim est, et sollicitudin quam ipsum vel mi. Sed commodo urna ac urna. Nullam eu tortor. Curabitur sodales scelerisque magna. Donec ultricies tristique pede. Nullam libero. Nam sollicitudin felis vel metus. Nullam posuere molestie metus. Nullam molestie, nunc id suscipit rhoncus, felis mi vulputate lacus, a ultrices tortor dolor eget augue. Aenean ultricies felis ut turpis. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Suspendisse placerat tellus ac nulla. Proin adipiscing sem ac risus. Maecenas nisi. Cras semper.\n\nPraesent interdum mollis neque. In egestas nulla eget pede. Integer eu purus sed diam dictum scelerisque. Morbi cursus velit et felis. Maecenas faucibus aliquet erat. In aliquet rhoncus tellus. Integer auctor nibh a nunc fringilla tempus. Cras turpis urna, dignissim vel, suscipit pulvinar, rutrum quis, sem. Ut lobortis convallis dui. Sed nonummy orci a justo. Morbi nec diam eget eros eleifend tincidunt.\n\nՀայերեն\n\nLorem Ipsum-ը տպագրության և տպագրական արդյունաբերության համար նախատեսված մոդելային տեքստ է: Սկսած 1500-ականներից` Lorem Ipsum-ը հանդիսացել է տպագրական արդյունաբերության ստանդարտ մոդելային տեքստ, ինչը մի անհայտ տպագրիչի կողմից տարբեր տառատեսակների օրինակների գիրք ստեղծելու ջանքերի արդյունք է: Այս տեքստը ոչ միայն կարողացել է գոյատևել հինգ դարաշրջան, այլև ներառվել է էլեկտրոնային տպագրության մեջ` մնալով էապես անփոփոխ: Այն հայտնի է դարձել 1960-ականներին Lorem Ipsum բովանդակող Letraset էջերի թողարկման արդյունքում, իսկ ավելի ուշ համակարգչային տպագրության այնպիսի ծրագրերի թողարկման հետևանքով, ինչպիսին է Aldus PageMaker-ը, որը ներառում է Lorem Ipsum-ի տարատեսակներ:\n\nБългарски\n\nLorem Ipsum е елементарен примерен текст, използван в печатарската и типографската индустрия. Lorem Ipsum е индустриален стандарт от около 1500 година, когато неизвестен печатар взема няколко печатарски букви и ги разбърква, за да напечата с тях книга с примерни шрифтове. Този начин не само е оцелял повече от 5 века, но е навлязъл и в публикуването на електронни издания като е запазен почти без промяна. Популяризиран е през 60те години на 20ти век със издаването на Letraset листи, съдържащи Lorem Ipsum пасажи, популярен е и в наши дни във софтуер за печатни издания като Aldus PageMaker, който включва различни версии на Lorem Ipsum.\n\nCatalà\n\nLorem Ipsum és un text de farciment usat per la indústria de la tipografia i la impremta. Lorem Ipsum ha estat el text estàndard de la indústria des de l\'any 1500, quan un impressor desconegut va fer servir una galerada de text i la va mesclar per crear un llibre de mostres tipogràfiques. No només ha sobreviscut cinc segles, sinó que ha fet el salt cap a la creació de tipus de lletra electrònics, romanent essencialment sense canvis. Es va popularitzar l\'any 1960 amb el llançament de fulls Letraset que contenien passatges de Lorem Ipsum, i més recentment amb programari d\'autoedició com Aldus Pagemaker que inclou versions de Lorem Ipsum.\n\nHrvatski\n\nLorem Ipsum je jednostavno probni tekst koji se koristi u tiskarskoj i slovoslagarskoj industriji. Lorem Ipsum postoji kao industrijski standard još od 16-og stoljeća, kada je nepoznati tiskar uzeo tiskarsku galiju slova i posložio ih da bi napravio knjigu s uzorkom tiska. Taj je tekst ne samo preživio pet stoljeća, već se i vinuo u svijet elektronskog slovoslagarstva, ostajući u suštini nepromijenjen. Postao je popularan tijekom 1960-ih s pojavom Letraset listova s odlomcima Lorem Ipsum-a, a u skorije vrijeme sa software-om za stolno izdavaštvo kao što je Aldus PageMaker koji također sadrži varijante Lorem Ipsum-a.\n\nČesky\n\nLorem Ipsum je demonstrativní výplňový text používaný v tiskařském a knihařském průmyslu. Lorem Ipsum je považováno za standard v této oblasti už od začátku 16. století, kdy dnes neznámý tiskař vzal kusy textu a na jejich základě vytvořil speciální vzorovou knihu. Jeho odkaz nevydržel pouze pět století, on přežil i nástup elektronické sazby v podstatě beze změny. Nejvíce popularizováno bylo Lorem Ipsum v šedesátých letech 20. století, kdy byly vydávány speciální vzorníky s jeho pasážemi a později pak díky počítačovým DTP programům jako Aldus PageMaker.\n\nRomâna\n\nLorem Ipsum este pur şi simplu o machetă pentru text a industriei tipografice. Lorem Ipsum a fost macheta standard a industriei încă din secolul al XVI-lea, când un tipograf anonim a luat o planşetă de litere şi le-a amestecat pentru a crea o carte demonstrativă pentru literele respective. Nu doar că a supravieţuit timp de cinci secole, dar şi a facut saltul în tipografia electronică practic neschimbată. A fost popularizată în anii \'60 odată cu ieşirea colilor Letraset care conţineau pasaje Lorem Ipsum, iar mai recent, prin programele de publicare pentru calculator, ca Aldus PageMaker care includeau versiuni de Lorem Ipsum.\n\nСрпски\n\nLorem Ipsum је једноставно модел текста који се користи у штампарској и словослагачкој индустрији. Lorem ipsum је био стандард за модел текста још од 1500. године, када је непознати штампар узео кутију са словима и сложио их како би направио узорак књиге. Не само што је овај модел опстао пет векова, него је чак почео да се користи и у електронским медијима, непроменивши се. Популаризован је шездесетих година двадесетог века заједно са листовима летерсета који су садржали Lorem Ipsum пасусе, а данас са софтверским пакетом за прелом као што је Aldus PageMaker који је садржао Lorem Ipsum верзије.\n\nΕλληνικά\n\nΤάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός. Ϊϊϋ, Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός. ΤΑΧΙΣΤΗ ΑΛΩΠΗΞ ΒΑΦΗΣ ΨΗΜΕΝΗ ΓΗ, ΔΡΑΣΚΕΛΙΖΕΙ ΥΠΕΡ ΝΩΘΡΟΥ ΚΥΝΟΣ. Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός. Ϊϊϋ, Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός Τάχιστη αλώπηξ βαφής ψημένη γη, δρασκελίζει υπέρ νωθρού κυνός. ΤΑΧΙΣΤΗ ΑΛΩΠΗΞ ΒΑΦΗΣ ΨΗΜΕΝΗ ΓΗ, ΔΡΑΣΚΕΛΙΖΕΙ ΥΠΕΡ ΝΩΘΡΟΥ ΚΥΝΟΣ.', 'Lorem Ipsum', '', 'publish', 'closed', 'closed', '', 'lorem-ipsum', '', '', '2007-09-04 09:52:50', '2007-09-04 16:52:50', '', 0, 'https://wpthemetestdata.wordpress.com/lorem-ipsum/', 7, 'page', '', 0), (155, 1, '2007-09-04 10:47:47', '2007-09-04 17:47:47', 'Repository-hosted Themes are required to support display of comments on static Pages as well as on single blog Posts. This static Page has comments, and these comments should be displayed.\nIf the Theme includes a custom option to prevent static Pages from displaying comments, such option must be disabled (i.e. so that static Pages display comments) by default.\nAlso, verify that this Page does not display taxonomy information (e.g. categories or tags) or time-stamp information (Page publish date/time).', 'Page with comments', '', 'publish', 'open', 'closed', '', 'page-with-comments', '', '', '2007-09-04 10:47:47', '2007-09-04 17:47:47', '', 1725, 'https://wpthemetestdata.wordpress.com/page-with-comments/', 3, 'page', '', 3), (156, 1, '2007-09-04 10:48:10', '2007-09-04 17:48:10', 'This static Page is set not to allow comments. Verify that the Page does not display a comment list, comment reply links, or comment reply form.\nAlso, verify that the Page does not display a \"comments are closed\" type message. Such messages are not suitable for static Pages, and should only be used on blog Posts.', 'Page with comments disabled', '', 'publish', 'closed', 'closed', '', 'page-with-comments-disabled', '', '', '2007-09-04 10:48:10', '2007-09-04 17:48:10', '', 1725, 'https://wpthemetestdata.wordpress.com/page-with-comments-disabled/', 4, 'page', '', 0), (172, 1, '2007-12-11 16:23:16', '2007-12-11 06:23:16', 'Level 3 of the reverse hierarchy test.', 'Level 3', '', 'publish', 'closed', 'closed', '', 'level-3', '', '', '2007-12-11 16:23:16', '2007-12-11 06:23:16', '', 173, 'https://wpthemetestdata.wordpress.com/level-3/', 0, 'page', '', 0), (173, 1, '2007-12-11 16:23:33', '2007-12-11 06:23:33', 'Level 2 of the reverse hierarchy test.', 'Level 2', '', 'publish', 'closed', 'closed', '', 'level-2', '', '', '2007-12-11 16:23:33', '2007-12-11 06:23:33', '', 174, 'https://wpthemetestdata.wordpress.com/level-2/', 0, 'page', '', 0), (174, 1, '2007-12-11 16:25:40', '2007-12-11 23:25:40', 'Level 1 of the reverse hierarchy test. This is to make sure the importer correctly assigns parents and children even when the children come first in the export file.', 'Level 1', '', 'publish', 'closed', 'closed', '', 'level-1', '', '', '2007-12-11 16:25:40', '2007-12-11 23:25:40', '', 0, 'https://wpthemetestdata.wordpress.com/level-1/', 5, 'page', '', 0), (358, 1, '2010-10-05 00:27:25', '2010-10-05 07:27:25', 'All children, except one, grow up. They soon know that they will grow up, and the way Wendy knew was this. One day when she was two years old she was playing in a garden, and she plucked another flower and ran with it to her mother. I suppose she must have looked rather delightful, for Mrs. Darling put her hand to her heart and cried, \"Oh, why can\'t you remain like this for ever!\" This was all that passed between them on the subject, but henceforth Wendy knew that she must grow up. You always know after you are two. Two is the beginning of the end.\n\n\n\nMrs. Darling first heard of Peter when she was tidying up her children\'s minds. It is the nightly custom of every good mother after her children are asleep to rummage in their minds and put things straight for next morning, repacking into their proper places the many articles that have wandered during the day.\n\nIf you could keep awake (but of course you can\'t) you would see your own mother doing this, and you would find it very interesting to watch her. It is quite like tidying up drawers. You would see her on her knees, I expect, lingering humorously over some of your contents, wondering where on earth you had picked this thing up, making discoveries sweet and not so sweet, pressing this to her cheek as if it were as nice as a kitten, and hurriedly stowing that out of sight. When you wake in the morning, the naughtiness and evil passions with which you went to bed have been folded up small and placed at the bottom of your mind and on the top, beautifully aired, are spread out your prettier thoughts, ready for you to put on.\n\nI don\'t know whether you have ever seen a map of a person\'s mind. Doctors sometimes draw maps of other parts of you, and your own map can become intensely interesting, but catch them trying to draw a map of a child\'s mind, which is not only confused, but keeps going round all the time. There are zigzag lines on it, just like your temperature on a card, and these are probably roads in the island, for the Neverland is always more or less an island, with astonishing splashes of colour here and there, and coral reefs and rakish-looking craft in the offing, and savages and lonely lairs, and gnomes who are mostly tailors, and caves through which a river runs, and princes with six elder brothers, and a hut fast going to decay, and one very small old lady with a hooked nose. It would be an easy map if that were all, but there is also first day at school, religion, fathers, the round pond, needle-work, murders, hangings, verbs that take the dative, chocolate pudding day, getting into braces, say ninety-nine, three-pence for pulling out your tooth yourself, and so on, and either these are part of the island or they are another map showing through, and it is all rather confusing, especially as nothing will stand still.\n\nOf course the Neverlands vary a good deal. John\'s, for instance, had a lagoon with flamingoes flying over it at which John was shooting, while Michael, who was very small, had a flamingo with lagoons flying over it. John lived in a boat turned upside down on the sands, Michael in a wigwam, Wendy in a house of leaves deftly sewn together. John had no friends, Michael had friends at night, Wendy had a pet wolf forsaken by its parents, but on the whole the Neverlands have a family resemblance, and if they stood still in a row you could say of them that they have each other\'s nose, and so forth. On these magic shores children at play are for ever beaching their coracles [simple boat]. We too have been there; we can still hear the sound of the surf, though we shall land no more.\n\nOf all delectable islands the Neverland is the snuggest and most compact, not large and sprawly, you know, with tedious distances between one adventure and another, but nicely crammed. When you play at it by day with the chairs and table-cloth, it is not in the least alarming, but in the two minutes before you go to sleep it becomes very real. That is why there are night-lights.\n\nOccasionally in her travels through her children\'s minds Mrs. Darling found things she could not understand, and of these quite the most perplexing was the word Peter. She knew of no Peter, and yet he was here and there in John and Michael\'s minds, while Wendy\'s began to be scrawled all over with him. The name stood out in bolder letters than any of the other words, and as Mrs. Darling gazed she felt that it had an oddly cocky appearance.', 'Post Format: Standard', '', 'publish', 'closed', 'closed', '', 'post-format-standard', '', '', '2010-10-05 00:27:25', '2010-10-05 07:27:25', '', 0, 'https://wpthemetestdata.wordpress.com/?p=358', 0, 'post', '', 0), (501, 1, '2010-08-01 09:42:26', '2010-08-01 16:42:26', 'The last item in this page\'s content is a thumbnail floated left. There should be page links following it. Make sure any elements after the content are clearing properly.\n\n The float is cleared when it does not stick out the bottom of the parent container, and when other elements that follow it do not wrap around the floated element.\n\n![\"\"](\"https://wpthemetestdata.files.wordpress.com/2010/08/manhattansummer.jpg?w=150\" "\\"Camera\\"")
This is the second page', 'Clearing Floats', '', 'publish', 'closed', 'closed', '', 'clearing-floats', '', '', '2010-08-01 09:42:26', '2010-08-01 16:42:26', '', 1725, 'https://wpthemetestdata.wordpress.com/', 2, 'page', '', 0),
(555, 1, '2010-09-10 07:24:14', '2010-09-10 14:24:14', '[gallery]\n\n\n\nYou can use this page to test the Theme\'s handling of the gallery shortcode, including the columns parameter, from 1 to 9 columns. Themes are only required to support the default setting (3 columns), so this page is entirely optional.\n![\"chunk](\"https://wpthemetestdata.files.wordpress.com/2013/09/dsc20040724_152504_532.jpg\" "\\"dsc20040724_152504_532\\"")
[/caption]\n', 'Post Format: Image (Linked)', '', 'publish', 'closed', 'closed', '', 'post-format-image-linked', '', '', '2010-08-06 08:09:39', '2010-08-06 15:09:39', '', 0, 'https://wpthemetestdata.wordpress.com/?p=568', 0, 'post', '', 0),
(575, 1, '2010-02-05 08:13:15', '2010-02-05 15:13:15', 'Only one thing is impossible for God: To find any sense in any copyright law on the planet.\nMark Twain', 'Post Format: Quote', '', 'publish', 'closed', 'closed', '', 'post-format-quote', '', '', '2010-02-05 08:13:15', '2010-02-05 15:13:15', '', 0, 'https://wpthemetestdata.wordpress.com/?p=575', 0, 'post', '', 0), (579, 1, '2010-04-04 08:21:24', '2010-04-04 15:21:24', 'WordPress, how do I love thee? Let me count the ways (in 140 characters or less).', 'Post Format: Status', '', 'publish', 'closed', 'closed', '', 'post-format-status', '', '', '2010-04-04 08:21:24', '2010-04-04 15:21:24', '', 0, 'https://wpthemetestdata.wordpress.com/?p=579', 0, 'post', '', 0), (582, 1, '2010-06-03 08:25:58', '2010-06-03 15:25:58', 'https://wordpress.tv/2009/03/16/anatomy-of-a-wordpress-theme-exploring-the-files-behind-your-theme/\n\nPosted as per the instructions in the Codex.', 'Post Format: Video (WordPress.tv)', '', 'publish', 'closed', 'closed', '', 'post-format-video-wordpresstv', '', '', '2010-06-03 08:25:58', '2010-06-03 15:25:58', '', 0, 'https://wpthemetestdata.wordpress.com/?p=582', 0, 'post', '', 0), (587, 1, '2010-07-02 08:36:44', '2010-07-02 15:36:44', 'Link:\n\nSt. Louis Blues\n\nAudio shortcode:\n\n[audio https://wpthemetestdata.files.wordpress.com/2008/06/originaldixielandjazzbandwithalbernard-stlouisblues.mp3]', 'Post Format: Audio', '', 'publish', 'closed', 'closed', '', 'post-format-audio', '', '', '2010-07-02 08:36:44', '2010-07-02 15:36:44', '', 0, 'https://wpthemetestdata.wordpress.com/?p=587', 0, 'post', '', 0), (701, 1, '2011-05-20 18:49:43', '2011-05-21 01:49:43', 'Use this static Page to test the Theme\'s handling of the Front Page template file.\n\nThis is the Front Page content. Use this static Page to test the Front Page output of the Theme. The Theme should properly handle both Blog Posts Index as Front Page and static Page as Front Page.\n\nIf the site is set to display the Blog Posts Index as the Front Page, then this text should not be visible. If the site is set to display a static Page as the Front Page, then this text may or may not be visible. If the Theme does not include a front-page.php template file, then this text should appear on the Front Page when set to display a static Page. If the Theme does include a front-page.php template file, then this text may or may not appear.', 'Front Page', '', 'publish', 'open', 'closed', '', 'front-page', '', '', '2011-05-20 18:49:43', '2011-05-21 01:49:43', '', 0, 'https://wpthemetestdata.wordpress.com/?page_id=701', 0, 'page', '', 0), (703, 1, '2011-05-20 18:51:43', '2011-05-21 01:51:43', 'Use this static Page to test the Theme\'s handling of the Blog Posts Index page. If the site is set to display a static Page on the Front Page, and this Page is set to display the Blog Posts Index, then this text should not appear. The title might, so make sure the theme is not supplying a hard-coded title for the Blog Post Index.', 'a Blog page', '', 'publish', 'open', 'closed', '', 'blog', '', '', '2011-05-20 18:51:43', '2011-05-21 01:51:43', '', 0, 'https://wpthemetestdata.wordpress.com/?page_id=703', 0, 'page', '', 0), (733, 1, '2011-06-23 18:38:52', '2011-06-24 01:38:52', 'Integer posuere erat a ante venenatis dapibus posuere velit aliquet. Aenean lacinia bibendum nulla sed consectetur. Etiam porta sem malesuada magna mollis euismod. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus.', 'Page A', '', 'publish', 'open', 'closed', '', 'page-a', '', '', '2011-06-23 18:38:52', '2011-06-24 01:38:52', '', 0, 'https://wpthemetestdata.wordpress.com/?page_id=733', 10, 'page', '', 0), (735, 1, '2011-06-23 18:39:14', '2011-06-24 01:39:14', '(lorem ipsum)', 'Page B', '', 'publish', 'open', 'closed', '', 'page-b', '', '', '2011-06-23 18:39:14', '2011-06-24 01:39:14', '', 0, 'https://wpthemetestdata.wordpress.com/?page_id=735', 11, 'page', '', 0), (742, 1, '2011-06-23 19:03:33', '2011-06-24 02:03:33', '(lorem ipsum)', 'Level 2a', '', 'publish', 'open', 'closed', '', 'level-2a', '', '', '2011-06-23 19:03:33', '2011-06-24 02:03:33', '', 174, 'https://wpthemetestdata.wordpress.com/?page_id=742', 0, 'page', '', 0), (744, 1, '2011-06-23 19:04:03', '2011-06-24 02:04:03', '(lorem ipsum)', 'Level 2b', '', 'publish', 'open', 'closed', '', 'level-2b', '', '', '2011-06-23 19:04:03', '2011-06-24 02:04:03', '', 174, 'https://wpthemetestdata.wordpress.com/?page_id=744', 0, 'page', '', 0), (746, 1, '2011-06-23 19:04:24', '2011-06-24 02:04:24', '(lorem ipsum)', 'Level 3a', '', 'publish', 'open', 'closed', '', 'level-3a', '', '', '2011-06-23 19:04:24', '2011-06-24 02:04:24', '', 173, 'https://wpthemetestdata.wordpress.com/?page_id=746', 0, 'page', '', 0), (748, 1, '2011-06-23 19:04:46', '2011-06-24 02:04:46', '(lorem ipsum)', 'Level 3b', '', 'publish', 'open', 'closed', '', 'level-3b', '', '', '2011-06-23 19:04:46', '2011-06-24 02:04:46', '', 173, 'https://wpthemetestdata.wordpress.com/?page_id=748', 0, 'page', '', 0), (993, 1, '2012-03-15 14:38:08', '2012-03-15 21:38:08', 'This is the post content. It should be displayed in place of the user-defined excerpt in single-page views.', 'Template: Excerpt (Defined)', 'This is a user-defined post excerpt. It should be displayed in place of the post content in archive-index pages. It can be longer than the automatically generated excerpts, and can have HTML tags.', 'publish', 'closed', 'closed', '', 'template-excerpt-defined', '', '', '2012-03-15 14:38:08', '2012-03-15 21:38:08', '', 0, 'http://wptest.io/demo/?p=993', 0, 'post', '', 0), (996, 1, '2012-03-15 14:41:11', '2012-03-15 21:41:11', 'This content is before the more tag.\n\nRight after this sentence should be a \"continue reading\" button of some sort on list pages of themes that show full content. It won\'t show on single pages or on themes showing excerpts.\n\n\n\nAnd this content is after the more tag. (which should be the anchor link for when the button is clicked)', 'Template: More Tag', '', 'publish', 'closed', 'closed', '', 'template-more-tag', '', '', '2012-03-15 14:41:11', '2012-03-15 21:41:11', '', 0, 'http://wptest.io/demo/?p=996', 0, 'post', '', 0), (1000, 1, '2009-05-15 14:48:32', '2009-05-15 21:48:32', 'Nested and mixed lists are an interesting beast. It\'s a corner case to make sure that\n
![\"Image](\"https://wpthemetestdata.files.wordpress.com/2013/03/image-alignment-580x300.jpg\" "\\"Image")
![\"Image](\"https://wpthemetestdata.files.wordpress.com/2013/03/image-alignment-150x150.jpg\" "\\"Image")
The rest of this paragraph is filler for the sake of seeing the text wrap around the 150x150 image, which is left aligned. \n\nAs you can see there should be some space above, below, and to the right of the image. The text should not be creeping on the image. Creeping is just not right. Images need breathing room too. Let them speak like you words. Let them do their jobs without any hassle from the text. In about one more sentence here, we\'ll see that the text moves from the right of the image down below the image in seamless transition. Again, letting the do it\'s thang. Mission accomplished!\n\nAnd now for a massively large image. It also has no alignment.\n\n![\"Image](\"https://wpthemetestdata.files.wordpress.com/2013/03/image-alignment-1200x4002.jpg\" "\\"Image")
\n\nThe image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n\n\n\nAnd we try the large image again, with the center alignment since that sometimes is a problem. The image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n\n![\"Image](\"https://wpthemetestdata.files.wordpress.com/2013/03/image-alignment-300x200.jpg\" "\\"Image")
\n\nAnd now we\'re going to shift things to the right align. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there... Hey guy! Way to rock that right side. I don\'t care what the left aligned image says, you look great. Don\'t let anyone else tell you differently.\n\nIn just a bit here, you should see the text start to wrap below the right aligned image and settle in nicely. There should still be plenty of room and everything should be sitting pretty. Yeah... Just like that. It never felt so good to be right.\n\nAnd just when you thought we were done, we\'re going to do them all over again with captions!\n\n[caption id=\"attachment_906\" align=\"aligncenter\" width=\"580\"] Look at 580x300 getting some caption love.[/caption]\n\nThe image above happens to be centered. The caption also has a link in it, just to see if it does anything funky.\n\n[caption id=\"attachment_904\" align=\"alignleft\" width=\"150\"] Bigger caption than the image usually is.[/caption]\n\nThe rest of this paragraph is filler for the sake of seeing the text wrap around the 150x150 image, which is left aligned. \n\nAs you can see the should be some space above, below, and to the right of the image. The text should not be creeping on the image. Creeping is just not right. Images need breathing room too. Let them speak like you words. Let them do their jobs without any hassle from the text. In about one more sentence here, we\'ll see that the text moves from the right of the image down below the image in seamless transition. Again, letting the do it\'s thang. Mission accomplished!\n\nAnd now for a massively large image. It also has no alignment.\n\n[caption id=\"attachment_907\" align=\"alignnone\" width=\"1200\"] Comment for massive image for your eyeballs.[/caption]\n\nThe image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n[caption id=\"attachment_907\" align=\"aligncenter\" width=\"1200\"] This massive image is centered.[/caption]\n\nAnd again with the big image centered. The image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n\n[caption id=\"attachment_905\" align=\"alignright\" width=\"300\"] Feels good to be right all the time.[/caption]\n\nAnd now we\'re going to shift things to the right align. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there... Hey guy! Way to rock that right side. I don\'t care what the left aligned image says, you look great. Don\'t let anyone else tell you differently.\n\nIn just a bit here, you should see the text start to wrap below the right aligned image and settle in nicely. There should still be plenty of room and everything should be sitting pretty. Yeah... Just like that. It never felt so good to be right.\n\nAnd that\'s a wrap, yo! You survived the tumultuous waters of alignment. Image alignment achievement unlocked! Last thing is a small image aligned right. Whatever follows should be unaffected. ', 'Page Image Alignment', '', 'publish', 'open', 'open', '', 'page-image-alignment', '', '', '2013-03-15 18:19:23', '2013-03-15 23:19:23', '', 1725, 'http://wptest.io/demo/?page_id=1080', 0, 'page', '', 0);
INSERT INTO `perf_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES
(1134, 1, '2013-03-15 18:20:05', '2013-03-15 23:20:05', 'Headings\nStay hungry. Stay foolish.\nMulti line blockquote with a cite reference:\n
\nmultiple contributors - MDN HTML element reference - blockquote\nThe HTML
<blockquote>Element (or HTML Block Quotation Element) indicates that the enclosed text is an extended quotation. Usually, this is rendered visually by indentation (see Notes for how to change it). A URL for the source of the quotation may be given using the cite attribute, while a text representation of the source can be given using the<cite>element.
| Employee | \nSalary | \n\n |
|---|---|---|
| Jane | \n$1 | \nBecause that\'s all Steve Jobs needed for a salary. | \n
| John | \n$100K | \nFor all the blogging he does. | \n
| Jane | \n$100M | \nPictures are worth a thousand words, right? So Tom x 1,000. | \n
| Jane | \n$100B | \nWith hair like that?! Enough said... | \n
.post-title {\n margin: 0 0 5px;\n font-weight: bold;\n font-size: 38px;\n line-height: 1.2;\n and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;\n}\nYou will learn later on in these tests that word-wrap: break-word; will be your best friend.\n\nDelete Tag\n\nThis tag will let you <s> instead).\n\nEmphasize Tag\n\nThe emphasize tag should italicize text.\n\nHorizontal Rule Tag\n\n<hr /> tag.\n\nInsert Tag\n\nThis tag should denote inserted text.\n\nKeyboard Tag\n\nThis scarcely known tag emulates keyboard text, which is usually styled like the <code> tag.\n\nPreformatted Tag\n\nThis tag is for preserving whitespace as typed, such as in poetry or ASCII art.\n\n Robert Frost\n\n\n Two roads diverged in a yellow wood,\n And sorry I could not travel both (\\_/)\n And be one traveler, long I stood (=\'.\'=)\n And looked down one as far as I could (\")_(\")\n To where it bent in the undergrowth;\n\n Then took the other, as just as fair,\n And having perhaps the better claim, |\\_/|\n Because it was grassy and wanted wear; / @ @ \\\n Though as for that the passing there ( > º < )\n Had worn them really about the same, `>>x<<´\n / O \\\n And both that morning equally lay\n In leaves no step had trodden black.\n Oh, I kept the first for another day!\n Yet knowing how way leads on to way,\n I doubted if I should ever come back.\n\n I shall be telling this with a sigh\n Somewhere ages and ages hence:\n Two roads diverged in a wood, and I—\n I took the one less traveled by,\n And that has made all the difference.\n\n\n and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;\n\nQuote Tag for short, inline quotes\n\n
Developers, developers, developers...--Steve Ballmer\n\nStrike Tag (deprecated in HTML5) and S Tag\n\nThis tag shows
<code> tag.\n\nUnderline Tag deprecated in HTML 4, re-introduced in HTML5 with other semantics\n\nThis tag shows underlined text.\n\nVariable Tag\n\nThis allows you to denote variables.', 'Page Markup And Formatting', '', 'publish', 'open', 'open', '', 'page-markup-and-formatting', '', '', '2013-03-15 18:20:05', '2013-03-15 23:20:05', '', 1725, 'http://wptest.io/demo/?page_id=1083', 0, 'page', '', 0),
(1148, 1, '2012-01-03 10:11:37', '2012-01-03 17:11:37', 'This post tests comments in the following ways.\n![\"\"](\"https://wpthemetestdata.files.wordpress.com/2008/06/100_5540.jpg\")
', 'Post Format: Image', '', 'publish', 'closed', 'closed', '', 'post-format-image', '', '', '2010-08-08 05:00:39', '2010-08-08 12:00:39', '', 0, 'https://wpthemetestdata.wordpress.com/?p=568', 0, 'post', '', 0),
(1161, 1, '2010-06-02 02:00:58', '2010-06-02 09:00:58', 'https://www.youtube.com/watch?v=SQEQr7c0-dw\n\nLearn more about WordPress Embeds.', 'Post Format: Video (YouTube)', '', 'publish', 'closed', 'closed', '', 'post-format-video-youtube', '', '', '2010-06-02 02:00:58', '2010-06-02 09:00:58', '', 0, 'https://wpthemetestdata.wordpress.com/?p=582', 0, 'post', '', 0),
(1163, 1, '2010-08-07 06:00:19', '2010-08-07 13:00:19', '[caption id=\"attachment_754\" align=\"alignnone\" width=\"604\"]![\"Bell](\"https://wpthemetestdata.files.wordpress.com/2008/06/100_5478.jpg\")
Bell on wharf in San Francisco[/caption]', 'Post Format: Image (Caption)', '', 'publish', 'closed', 'closed', '', 'post-format-image-caption', '', '', '2010-08-07 06:00:19', '2010-08-07 13:00:19', '', 0, 'https://wpthemetestdata.wordpress.com/?p=674', 0, 'post', '', 0),
(1164, 1, '2013-04-09 11:20:39', '2013-04-09 18:20:39', 'This post is drafted and not published yet.\n\nIt should not be displayed by the theme.', 'Draft', '', 'draft', 'closed', 'closed', '', '', '', '', '2013-04-09 11:20:39', '2013-04-09 18:20:39', '', 0, 'http://wptest.io/demo/?p=922', 0, 'post', '', 0),
(1168, 1, '2012-01-04 09:38:05', '2012-01-04 16:38:05', 'This content, comments, pingbacks, and trackbacks should not be visible until the password is entered.', 'Template: Password Protected (the password is \"enter\")', '', 'publish', 'closed', 'closed', 'enter', 'template-password-protected', '', '', '2012-01-04 09:38:05', '2012-01-04 16:38:05', '', 0, 'https://wpthemetestdata.wordpress.com/2007/09/04/test-with-secret-password/', 0, 'post', '', 1),
(1169, 1, '2009-09-05 09:00:23', '2009-09-05 16:00:23', 'This post has no title, but it still must link to the single post view somehow.\n\nThis is typically done by placing the permalink on the post date.', '', '', 'publish', 'closed', 'closed', '', 'edge-case-no-title', '', '', '2009-09-05 09:00:23', '2009-09-05 16:00:23', '', 0, 'https://wpthemetestdata.wordpress.com/2007/09/04/14/', 0, 'post', '', 0),
(1170, 1, '2009-08-06 09:39:56', '2009-08-06 16:39:56', '', 'Edge Case: No Content', '', 'publish', 'closed', 'closed', '', 'edge-case-no-content', '', '', '2009-08-06 09:39:56', '2009-08-06 16:39:56', '', 0, 'https://wpthemetestdata.wordpress.com/2007/09/04/this-post-has-no-body/', 0, 'post', '', 1),
(1171, 1, '2012-01-08 10:00:20', '2012-01-08 17:00:20', 'Post Page 1\n\n\n\nPost Page 2\n\n\n\nPost Page 3', 'Template: Paginated', '', 'publish', 'closed', 'closed', '', 'template-paginated', '', '', '2012-01-08 10:00:20', '2012-01-08 17:00:20', '', 0, 'https://noeltest.wordpress.com/?p=188', 0, 'post', '', 0),
(1173, 1, '2013-01-05 10:00:49', '2013-01-05 17:00:49', 'Verify that:\n| ! | \n\" | \n# | \n$ | \n% | \n& | \n\' | \n( | \n) | \n* | \n
| + | \n, | \n- | \n. | \n/ | \n0 | \n1 | \n2 | \n3 | \n4 | \n
| 5 | \n6 | \n7 | \n8 | \n9 | \n: | \n; | \n> | \n= | \n< | \n
| ? | \n@ | \nA | \nB | \nC | \nD | \nE | \nF | \nG | \nH | \n
| I | \nJ | \nK | \nL | \nM | \nN | \nO | \nP | \nQ | \nR | \n
| S | \nT | \nU | \nV | \nW | \nX | \nY | \nZ | \n[ | \n\\ | \n
| ] | \n^ | \n_ | \n` | \na | \nb | \nc | \nd | \ne | \nf | \n
| g | \nh | \ni | \nj | \nk | \nl | \nm | \nn | \no | \np | \n
| q | \nr | \ns | \nt | \nu | \nv | \nw | \nx | \ny | \nz | \n
| { | \n| | \n} | \n~ | \n\n | \n | \n | \n | \n | \n |
-ms-word-wrap: break-word;\nword-wrap: break-word;\n ', 'Taumatawhakatangihangakoauauotamateaturipukakapikimaungahoronukupokaiwhenuakitanatahu', '', 'publish', 'closed', 'closed', '', 'title-should-not-overflow-the-content-area', '', '', '2009-10-05 12:00:59', '2009-10-05 19:00:59', '', 0, 'http://wptest.io/demo/?p=877', 0, 'post', '', 0), (1176, 1, '2013-01-09 09:00:39', '2013-01-09 16:00:39', '
This is a paragraph. It is left aligned. Because of this, it is a bit more liberal in it\'s views. It\'s favorite color is green. Left align tends to be more eco-friendly, but it provides no concrete evidence that it really is. Even though it likes share the wealth evenly, it leaves the equal distribution up to justified alignment.
\n\nThis is a paragraph. It is center aligned. Center is, but nature, a fence sitter. A flip flopper. It has a difficult time making up its mind. It wants to pick a side. Really, it does. It has the best intentions, but it tends to complicate matters more than help. The best you can do is try to win it over and hope for the best. I hear center align does take bribes.
\n\nThis is a paragraph. It is right aligned. It is a bit more conservative in it\'s views. It\'s prefers to not be told what to do or how to do it. Right align totally owns a slew of guns and loves to head to the range for some practice. Which is cool and all. I mean, it\'s a pretty good shot from at least four or five football fields away. Dead on. So boss.
\n\nThis is a paragraph. It is justify aligned. It gets really mad when people associate it with Justin Timberlake. Typically, justified is pretty straight laced. It likes everything to be in it\'s place and not all cattywampus like the rest of the aligns. I am not saying that makes it better than the rest of the aligns, but it does tend to put off more of an elitist attitude.
', 'Markup: Text Alignment', '', 'publish', 'closed', 'closed', '', 'markup-text-alignment', '', '', '2013-01-09 09:00:39', '2013-01-09 16:00:39', '', 0, 'http://wptest.io/demo/?p=895', 0, 'post', '', 0), (1177, 1, '2013-01-10 20:15:40', '2013-01-11 03:15:40', 'Welcome to image alignment! The best way to demonstrate the ebb and flow of the various image positioning options is to nestle them snuggly among an ocean of words. Grab a paddle and let\'s get started.\n\nOn the topic of alignment, it should be noted that users can choose from the options of None, Left, Right, and Center. In addition, they also get the options of Thumbnail, Medium, Large & Fullsize. Be sure to try this page in RTL mode and it should look the same as LTR. \n
The rest of this paragraph is filler for the sake of seeing the text wrap around the 150x150 image, which is left aligned. \n\nAs you can see the should be some space above, below, and to the right of the image. The text should not be creeping on the image. Creeping is just not right. Images need breathing room too. Let them speak like you words. Let them do their jobs without any hassle from the text. In about one more sentence here, we\'ll see that the text moves from the right of the image down below the image in seamless transition. Again, letting the do it\'s thang. Mission accomplished!\n\nAnd now for a massively large image. It also has no alignment.\n\n\n\nThe image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n\n\n\nAnd we try the large image again, with the center alignment since that sometimes is a problem. The image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n\n\n\nAnd now we\'re going to shift things to the right align. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there... Hey guy! Way to rock that right side. I don\'t care what the left aligned image says, you look great. Don\'t let anyone else tell you differently.\n\nIn just a bit here, you should see the text start to wrap below the right aligned image and settle in nicely. There should still be plenty of room and everything should be sitting pretty. Yeah... Just like that. It never felt so good to be right.\n\nAnd just when you thought we were done, we\'re going to do them all over again with captions!\n\n[caption id=\"attachment_906\" align=\"aligncenter\" width=\"580\"] Look at 580x300 getting some caption love.[/caption]\n\nThe image above happens to be centered. The caption also has a link in it, just to see if it does anything funky.\n\n[caption id=\"attachment_904\" align=\"alignleft\" width=\"150\"] Bigger caption than the image usually is.[/caption]\n\nThe rest of this paragraph is filler for the sake of seeing the text wrap around the 150x150 image, which is left aligned. \n\nAs you can see the should be some space above, below, and to the right of the image. The text should not be creeping on the image. Creeping is just not right. Images need breathing room too. Let them speak like you words. Let them do their jobs without any hassle from the text. In about one more sentence here, we\'ll see that the text moves from the right of the image down below the image in seamless transition. Again, letting the do it\'s thang. Mission accomplished!\n\nAnd now for a massively large image. It also has no alignment.\n\n[caption id=\"attachment_907\" align=\"alignnone\" width=\"1200\"] Comment for massive image for your eyeballs.[/caption]\n\nThe image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n[caption id=\"attachment_907\" align=\"aligncenter\" width=\"1200\"] This massive image is centered.[/caption]\n\nAnd again with the big image centered. The image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.\n\n[caption id=\"attachment_905\" align=\"alignright\" width=\"300\"] Feels good to be right all the time.[/caption]\n\nAnd now we\'re going to shift things to the right align. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there... Hey guy! Way to rock that right side. I don\'t care what the left aligned image says, you look great. Don\'t let anyone else tell you differently.\n\nIn just a bit here, you should see the text start to wrap below the right aligned image and settle in nicely. There should still be plenty of room and everything should be sitting pretty. Yeah... Just like that. It never felt so good to be right.\n\nAnd that\'s a wrap, yo! You survived the tumultuous waters of alignment. Image alignment achievement unlocked! One last thing: The last item in this post\'s content is a thumbnail floated right. Make sure any elements after the content are clearing properly.\n\n![\"\"](\"https://wpthemetestdata.files.wordpress.com/2010/08/manhattansummer.jpg\" "\\"Camera\\"")
', 'Markup: Image Alignment', '', 'publish', 'closed', 'closed', '', 'markup-image-alignment', '', '', '2013-01-10 20:15:40', '2013-01-11 03:15:40', '', 0, 'http://wptest.io/demo/?p=903', 0, 'post', '', 0),
(1178, 1, '2013-01-11 20:22:19', '2013-01-12 03:22:19', 'Headings\nStay hungry. Stay foolish.\nMulti line blockquote with a cite reference:\n
\nmultiple contributors - MDN HTML element reference - blockquote\nThe HTML
<blockquote>Element (or HTML Block Quotation Element) indicates that the enclosed text is an extended quotation. Usually, this is rendered visually by indentation (see Notes for how to change it). A URL for the source of the quotation may be given using the cite attribute, while a text representation of the source can be given using the<cite>element.
| Employee | \nSalary | \n\n |
|---|---|---|
| John Doe | \n$1 | \nBecause that\'s all Steve Jobs needed for a salary. | \n
| Jane Doe | \n$100K | \nFor all the blogging she does. | \n
| Fred Bloggs | \n$100M | \nPictures are worth a thousand words, right? So Jane x 1,000. | \n
| Jane Bloggs | \n$100B | \nWith hair like that?! Enough said... | \n
.post-title {\n margin: 0 0 5px;\n font-weight: bold;\n font-size: 38px;\n line-height: 1.2;\n and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;\n}\nYou will learn later on in these tests that word-wrap: break-word; will be your best friend.\n\nDelete Tag\n\nThis tag will let you <s> instead).\n\nEmphasize Tag\n\nThe emphasize tag should italicize text.\n\nHorizontal Rule Tag\n\n<hr /> tag.\n\nInsert Tag\n\nThis tag should denote inserted text.\n\nKeyboard Tag\n\nThis scarcely known tag emulates keyboard text, which is usually styled like the <code> tag.\n\nPreformatted Tag\n\nThis tag is for preserving whitespace as typed, such as in poetry or ASCII art.\n\nRobert Frost\n\n\n Two roads diverged in a yellow wood,\n And sorry I could not travel both (\\_/)\n And be one traveler, long I stood (=\'.\'=)\n And looked down one as far as I could (\")_(\")\n To where it bent in the undergrowth;\n\n Then took the other, as just as fair,\n And having perhaps the better claim, |\\_/|\n Because it was grassy and wanted wear; / @ @ \\\n Though as for that the passing there ( > º < )\n Had worn them really about the same, `>>x<<´\n / O \\\n And both that morning equally lay\n In leaves no step had trodden black.\n Oh, I kept the first for another day!\n Yet knowing how way leads on to way,\n I doubted if I should ever come back.\n\n I shall be telling this with a sigh\n Somewhere ages and ages hence:\n Two roads diverged in a wood, and I—\n I took the one less traveled by,\n And that has made all the difference.\n\n\n and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;\n\nQuote Tag for short, inline quotes\n\n
Developers, developers, developers...--Steve Ballmer\n\nStrike Tag (deprecated in HTML5) and S Tag\n\nThis tag shows
<code> tag.\n\nUnderline Tag deprecated in HTML 4, re-introduced in HTML5 with other semantics\n\nThis tag shows underlined text.\n\nVariable Tag\n\nThis allows you to denote variables.', 'Markup: HTML Tags and Formatting', '', 'publish', 'closed', 'closed', '', 'markup-html-tags-and-formatting', '', '', '2013-01-11 20:22:19', '2013-01-12 03:22:19', '', 0, 'http://wptest.io/demo/?p=919', 0, 'post', '', 0),
(1179, 1, '2011-03-15 15:47:16', '2011-03-15 22:47:16', 'https://twitter.com/nacin/status/319508408669708289\n\nThis post tests WordPress\' Twitter Embeds feature.', 'Media: Twitter Embeds', '', 'publish', 'closed', 'closed', '', 'media-twitter-embeds', '', '', '2011-03-15 15:47:16', '2011-03-15 22:47:16', '', 0, 'http://wptest.io/demo/?p=1027', 0, 'post', '', 0),
(1241, 1, '2012-01-07 07:07:21', '2012-01-07 14:07:21', 'This is a sticky post.\n\nThere are a few things to verify:\n.sticky class if you are using the post_class() function to generate your post classes, which is a best practice.excerpt_length and excerpt_more, display properly.', 'Template: Excerpt (Generated)', '', 'publish', 'closed', 'closed', '', 'template-excerpt-generated', '', '', '2012-03-14 09:49:22', '2012-03-14 16:49:22', '', 0, 'https://wpthemetestdata.wordpress.com/?p=1446', 0, 'post', '', 0),
(1724, 2, '2018-10-20 20:03:48', '2018-10-21 03:03:48', '\nThere are many different ways to use the web besides a mouse and a pair of eyes. Users navigate for example with a keyboard only or with their voice.
\n\n\n\nAll the functionality, including menus, links and forms should work using a keyboard only. This is essential for all assistive technology to work properly. The only way to test this, at the moment, is manually. The best time to test this is during development.
\n\n\n\nTab through your pages, links and forms to do the following tests:
\n\n\n\nThe Common category includes the following blocks: Paragraph, image, headings, list, gallery, quote, audio, cover, video.
\n\n\n\nThe paragraph block is the default block type. It should not have any alignment of any kind. It should just flow like you would normally expect. Nothing fancy. Just straight up text, free flowing, with love.
\n\n\n\nThis paragraph is left aligned.
\n\n\n\nThis italic paragraph is right aligned.
\n\n\n\nNeither of these paragraphs care about politics, but this one is bold, medium sized and has a drop cap.
\n\n\n\nThis paragraph is centered.
\n\n\n\nThis paragraph prefers Jazz over Justin Timberlake. It also uses the small font size.
\n\n\n\nThis paragraph has something important to say: It has a large font size, which defaults to 36px.
\n\n\n\nThe huge text size defaults to 46px, but the size can be customized.
\n\n\n\nThis paragraph is colorful, with a red background and white text (maybe). Colored blocks should have a high enough contrast, so that the text is readable.
\n\n\n\nBelow this block, you will see a single image with a circle mask applied.
\n\n\n\n![\"Brazil](\"https://wpthemetestdata.files.wordpress.com/2008/06/img_0747.jpg\")
![\"Huatulco](\"https://wpthemetestdata.files.wordpress.com/2008/06/img_0513-1.jpg\")
![\"Windmill\"](\"https://wpthemetestdata.files.wordpress.com/2008/06/windmill.jpg\")
![\"Huatulco](\"https://wpthemetestdata.files.wordpress.com/2008/06/img_0767.jpg\")
![\"\"](\"https://wpthemetestdata.files.wordpress.com/2012/06/dsc20040724_152504_532.jpg\")
![\"Big](\"https://wpthemetestdata.files.wordpress.com/2008/06/michelle_049.jpg\")
\n\n\n\nQuote
Cite
Cover block with background image
\nThe file block has a setting that lets us show or hide a download button with editable text:
\n\n\n\n\n\n\n\n\n\n\n\nVideo blocks have settings for showing and hiding the playback controls. Use autoplay and playback controls responsibly.
\n\n\n\nThe video block below is muted and has a poster image that displays before the video starts:
\n\n\n\nThe formatting category includes the following blocks:
\n\n\n\nThe code block starts with\n<!-- wp:code -->\n<?php echo \'Hello World\'; ?>\nThe classic block can have almost anything in it.
\nThe preformatted block.\n\n\n\n
The Road Not Taken
Robert Frost
Two roads diverged in a yellow wood,
And sorry I could not travel both (\\_/)
And be one traveler, long I stood (=\'.\'=)
And looked down one as far as I could (\")_(\")
To where it bent in the undergrowth;
Then took the other, as just as fair,
And having perhaps the better claim, |\\_/|
Because it was grassy and wanted wear; / @ @ \\
Though as for that the passing there ( > º < )
Had worn them really about the same, `>>x<<´
/ O \\
And both that morning equally lay
In leaves no step had trodden black.
Oh, I kept the first for another day!
Yet knowing how way leads on to way,
I doubted if I should ever come back.
I shall be telling this with a sigh
Somewhere ages and ages hence:
Two roads diverged in a wood, and I—
I took the one less traveled by,
And that has made all the difference.
and here\'s a line of some really, really, really, really long text, just to see how it is handled and to find out how it overflows;
The pull quote can be aligned or wide or neither.
Theme Reviewer
| The table block | This is the default style. |
| The cell next to this is empty. | |
| Cell #5 | Cell #6 |
| This is the striped style. | This row should have a background color. |
| The cell next to this is empty. | |
| This table has fixed width table cells. | |
Make sure that the text wraps correctly. |
The Verse block\n', 'Block category: Formatting', '', 'publish', 'open', 'open', '', 'blocks-formatting', '', '', '2018-11-01 06:03:22', '2018-11-01 06:03:22', '', 0, 'https://wpthemetestdata.wordpress.com/?p=1732', 0, 'post', '', 0), (1780, 2, '2018-11-01 06:08:25', '2018-11-01 06:08:25', '\n
A block for haiku?
Why not?
Blocks for all the things!
The Layout Elements category includes the following blocks: Group, Button, Columns, Media & Text, separator, spacer, read more, and page break.
\n\n\n\nThis group block has a light green background color.
\n\n\n\n\n\n\n\nThe read more block should be right below this text, but only on list pages of themes that show the full content. It won\'t show on the single page or on themes showing excerpts.
\nThe columns:
\nColumn two.
\nColumn three.
\nColumn four.
\n![\"Boardwalk\"](\"https://wpthemetestdata.files.wordpress.com/2008/06/dcp_2082.jpg\")
Media &Text
\n\n\n\nFor displaying media and text next to each other. By default, the media is to the left.
\nThis time our block is full width, and the image is to the right.
\n\n\n\nThe background color is a pale blue.
\nTest to make sure that the editor and the front match. To test the Stack on mobile setting, reduce the browser window width.
\n\n\n\nThe control these settings, the block uses the css classes \"has-media-on-the-right\" and \"is-stacked-on-mobile\".
\n\n\n\nThe separator has three styles: default, wide line, and dots.
\n\n\n\nThe spacer block has a default height of 100 pixels:
\n\n\n\n\n\n\n\nAnd finally, the page break:
\n\n\n\n\n\n\n\nThis paragraph block is on page two, after the page break.
\n\n\n\n\n', 'Block category: Layout Elements', '', 'publish', 'open', 'open', '', 'blocks-layout-elements', '', '', '2018-11-01 06:08:25', '2018-11-01 06:08:25', '', 0, 'https://wpthemetestdata.wordpress.com/?p=1734', 0, 'post', '', 0), (1781, 2, '2018-11-01 06:18:46', '2018-11-01 06:18:46', '\n \nThis post tests various embed blocks:
\n\n \n\nThe shortcode widget:
\n\n\n\n[gallery columns=2 ids=\"770,771\"]\n\n\n\nThe Archive Widget:
\n\n\n\n\n\nThe same Archive widget but as a dropdown:
\n\n\n\n\n\n\n\nThe Category widget block has an additional option for showing category hierarchies:
\n\n\n\n\n\nThe Latest Comments widget can display or hide the avatars, the date, and the comment excerpt:
\n\n\n\n\n\nHere is an example of the Comments widget with all the options disabled. The number of comments has been reduced to two.
\n\n\n\n\n\nAnd here is the Latest Posts widget in the list view, with dates:
\n\n\n\n\n\nGrid view, now sorted from A -Z.
\n\n\n\n\n\nYou can also change the number of columns used to display the latest posts. The block below only displays posts from the Block category:
\n\n\n\n\n\nSearch widget:
\n\n\n\n\n\nTag Cloud widget:
\n\n\n\n\n\nRSS Feed widget:
\n\n\n\n ', 'Block category: Widgets', '', 'publish', 'open', 'open', '', 'blocks-widgets', '', '', '2018-11-01 06:14:47', '2018-11-01 06:14:47', '', 0, 'https://wpthemetestdata.wordpress.com/?p=1736', 0, 'post', '', 0), (1783, 2, '2018-11-02 12:10:00', '2018-11-02 12:10:00', '\nThis page tests how the theme displays the columns block. The first block tests a two column block with paragraphs.
\nThis is the second column. It should align next to the first column. Reduce the browser window width to test the responsiveness.
\nThis is the second column block. It has 3 columns.
\nParagraph 2 is in the middle.
\nParagraph 3 is in the last column.
\nThe third column block has 4 columns. Make sure that all the text is visible and that it is not cut off.
\nNow the columns are getting narrower.
\nThe margins between the columns should be wide enough,
\nso that the content of the columns does not run into or overlap each other.
\nColumn one.
\nColumn two.
\nColumn three.
\nColumn four.
\nColumn five.
\nTo change the number of columns, select the column block to open the settings panel. You can show up to 6 columns. If the theme has support for wide align, you can also set the alignments to wide and full width.
\n\n\n\nBelow is a column block with six columns, and no alignment:
\n\n\n\nColumn one.
\nColumn two.
\nColumn three.
\nColumn four.
\nColumn five.
\nColumn six.
\nNext is a 3 column block, with a wide alignment:
\n\n\n\nColumn one.
\nColumn two.
\nColumn three.
\nAnd here is a two column block with full width, and a longer text. Make sure that the text wraps correctly.
\n\n\n\nThis is column one. Sometimes, you may want to use columns to display a larger text, so, lets add some more words. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec mollis. Quisque convallis libero in sapien pharetra tincidunt. Aliquam elit ante, malesuada id, tempor eu, gravida id, odio. Maecenas suscipit, risus et eleifend imperdiet, nisi orci ullamcorper massa, et adipiscing orci velit quis magna. Praesent sit amet ligula id orci venenatis auctor. Phasellus porttitor, metus non tincidunt dapibus, orci pede pretium neque, sit amet adipiscing ipsum lectus et libero. Aenean bibendum. Curabitur mattis quam id urna. Vivamus dui. Donec nonummy lacinia lorem. Cras risus arcu, sodales ac, ultrices ac, mollis quis, justo. Sed a libero. Quisque risus erat, posuere at, tristique non, lacinia quis, eros.
\nColumn two. Cras volutpat, lacus quis semper pharetra, nisi enim dignissim est, et sollicitudin quam ipsum vel mi. Sed commodo urna ac urna. Nullam eu tortor. Curabitur sodales scelerisque magna. Donec ultricies tristique pede. Nullam libero. Nam sollicitudin felis vel metus. Nullam posuere molestie metus. Nullam molestie, nunc id suscipit rhoncus, felis mi vulputate lacus, a ultrices tortor dolor eget augue. Aenean ultricies felis ut turpis. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Suspendisse placerat tellus ac nulla. Proin adipiscing sem ac risus. Maecenas nisi. Cras semper.
\nWe can also add blocks inside columns:
\n\n\n\nThe middle column has a paragraph with an image block below.
\n\n\n\n![\"canola\"](\"https://wpthemetestdata.files.wordpress.com/2008/06/canola2.jpg\")
\n-This third column has a quote
Theme Reviewer
But wait there is more! We also have a block called Media & Text, which is a two column block that helps you display media and text content next to each other, without having to first setup a column block:
\n\n\n\n![\"dsc20050813_115856_52\"](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc20050813_115856_52.jpg\")
Media & Text
\n\n\n\nA paragraph block sits ready to be used, below your headline.
\n\n\n\n\nThis is a left aligned cover block with a background image.
The cover block lets you add text on top of images or videos.
\n\n\n\nThis blocktype has several alignment options, and you can also align or center the text inside the block.
\n\n\n\nThe background image can be fixed and you can change its opacity and add an overlay color.
\n\n\n\nMake sure that the text wraps correctly over the image, and that text markup and alignments are working.
\n\n\n\nThe next image should have a pink overlay color, the text should be bold and aligned to the left:
\n\n\n\nA center aligned cover image block, with a left aligned text.
This is a full width cover block with a fixed background image with a 20% opacity.
Make sure that all the text is readable.
\n\n\n\nOur last cover image block has a wide width.
This is a wide cover block with a video background.
Compare the video and image blocks.
This block is centered.
The block below has no alignment, and the text is a link. Overlay colors must also work with video backgrounds.
\n\n\n\n\n', 'Block: Cover', '', 'publish', 'open', 'open', '', 'block-cover', '', '', '2018-11-03 12:25:00', '2018-11-03 12:25:00', '', 0, 'https://wpthemetestdata.wordpress.com/?p=1745', 0, 'post', '', 0), (1785, 2, '2018-11-03 13:20:00', '2018-11-03 13:20:00', '\nButton blocks are not semantically buttons, but links inside a styled div.
\n\n\n\nIf you do not add a link, a link tag without an anchor will be used.
\n\n\n\n\n\n\n\nCheck to make sure that the text wraps correctly when the button has more than one line of text, and when it is extra long.
\n\n\n\n\n\n\n\nButtons have three styles:
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nIf the theme has a custom color palette, test that background color and text color settings work correctly.
\n\n\n\n\n\n\n\nNow lets test how buttons display together with large texts.
\n\n\n\nLorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec mollis. Quisque convallis libero in sapien pharetra tincidunt. Aliquam elit ante, malesuada id, tempor eu, gravida id, odio.
\n\n\n\n\n\n\n\nMaecenas suscipit, risus et eleifend imperdiet, nisi orci ullamcorper massa, et adipiscing orci velit quis magna. Praesent sit amet ligula id orci venenatis auctor. Phasellus porttitor, metus non tincidunt dapibus, orci pede pretium neque, sit amet adipiscing ipsum lectus et libero. Aenean bibendum. Curabitur mattis quam id urna.
\n\n\n\n\n\n\n\nVivamus dui. Donec nonummy lacinia lorem. Cras risus arcu, sodales ac, ultrices ac, mollis quis, justo. Sed a libero. Quisque risus erat, posuere at, tristique non, lacinia quis, eros.
\n', 'Block: Button', '', 'publish', 'open', 'open', '', 'block-button', '', '', '2018-11-03 13:20:00', '2018-11-03 13:20:00', '', 0, 'https://wpthemetestdata.wordpress.com/?p=1747', 0, 'post', '', 0); INSERT INTO `perf_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES (1786, 2, '2018-11-01 15:28:56', '2018-11-01 15:28:56', '\nThe quote block has two styles, regular:
\n\n\n\n\n\n\n\nGutenberg is more than an editor.
The Gutenberg Team
and large:
\n\n\n\n\n\n\n\nYes, it is a press, certainly, but a press from which shall flow in inexhaustible streams, the most abundant and most marvelous liquor that has ever flowed to relieve the thirst of men!
Johannes Gutenberg
The quote blocks themselves have no alignments but the text can be aligned, bold, italic, and linked:
\n\n\n\nTheme Review\n\n\n\n
In addition to the quote block, we also have the pull quote, with a regular and a solid color style.
\n\n\n\nYou can change the color of the border and the text with the regular style:
\n\n\n\nIn addition to the quote block, we also have the pull quote.
Theme Reviewer
Or change the background color and text color with the solid color style:
\n\n\n\na solid color style
Theme Reviewer
Gallery blocks have two settings: the number of columns, and whether or not images should be cropped. The default number of columns is three, and the maximum number of columns is eight.
\n\n\n\nBelow is a three column gallery at full width, with cropped images.
\n\n\n\n![\"Sunburst](\"https://wpthemetestdata.files.wordpress.com/2008/06/cep00032.jpg\")
![\"Orange](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc02085.jpg\")
![\"\"](\"https://wpthemetestdata.files.wordpress.com/2014/01/spectacles.gif\")
![\"Unicorn](\"https://wpthemetestdata.files.wordpress.com/2012/12/unicorn-wallpaper.jpg\")
![\"Boat](\"https://wpthemetestdata.files.wordpress.com/2008/06/img_8399.jpg\")
Some more text for taking up space.
\n\n\n\nA two column gallery, aligned to the left, linked to media file.
\n\n\n\nIn the editor, the image captions can be edited directly by clicking on the text.
\n\n\n\nIf the number of images cannot be divided into the number of columns you have selected, the default is to have the last image(s) automatically stretch to the width of your gallery.
\n\n\n\n\n\n\n\nA four column gallery with a wide width:
\n\n\n\n![\"\"](\"https://wpthemetestdata.files.wordpress.com/2013/09/dsc20050604_133440_34211.jpg\")
![\"\"](\"https://wpthemetestdata.files.wordpress.com/2014/01/dsc20050315_145007_132.jpg\")
![\"dsc20050727_091048_222\"](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc20050727_091048_222.jpg\")
A five column gallery with normal images:
\n\n\n\n![\"Horizontal](\"https://wpthemetestdata.files.wordpress.com/2013/03/featured-image-vertical.jpg\")
![\"Horizontal](\"https://wpthemetestdata.files.wordpress.com/2013/03/featured-image-horizontal.jpg\")
This is the same gallery, but with cropped images.
\n\n\n\nSix columns: does it work at all window sizes?
\n\n\n\n![\"Sydney](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc09114.jpg\")
![\"Rusty](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc20051220_173257_119.jpg\")
![\"Yachtsody](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc03149.jpg\")
![\"Antique](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc20051220_160808_102.jpg\")
![\"Rain](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc04563.jpg\")
![\"Wind](\"https://wpthemetestdata.files.wordpress.com/2008/06/dsc20050102_192118_51.jpg\")
Seven columns: how does this look on a narrow window?
\n\n\n\n![\"\"](\"https://wpthemetestdata.files.wordpress.com/2010/08/triforce-wallpaper.jpg\")
![\"Sea](\"https://wpthemetestdata.files.wordpress.com/2008/06/dscn3316.jpg\")
Eight columns:
\n\n\n\nWelcome to image alignment! If you recognize this post, it is because these are blocks that have been converted from the classic Markup: Image Alignment post. The best way to demonstrate the ebb and flow of the various image positioning options is to nestle them snuggly among an ocean of words. Grab a paddle and let\'s get started. Be sure to try it in RTL mode. Left should stay left and right should stay right for both reading directions.
\n\n\n\nOn the topic of alignment, it should be noted that users can choose from the options of None, Left, Right, and Center. If the theme has added support for align wide, images can also be wide and full width. Be sure to test this page in RTL mode.
\n\n\n\nIn addition, they also get the options of the image dimensions 25%, 50%, 75%, 100% or a set width and height.
\n\n\n\nThe image above happens to be centered.
\n\n\n\nThe rest of this paragraph is filler for the sake of seeing the text wrap around the 150x150 image, which is left aligned.
\n\n\n\nAs you can see the should be some space above, below, and to the right of the image. The text should not be creeping on the image. Creeping is just not right. Images need breathing room too. Let them speak like you words. Let them do their jobs without any hassle from the text. In about one more sentence here, we\'ll see that the text moves from the right of the image down below the image in seamless transition. Again, letting the do it\'s thang. Mission accomplished!
\n\n\n\nAnd now for a massively large image. It also has no alignment.
\n\n\n\nThe image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.
\n\n\n\nAnd now we\'re going to shift things to the right align. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there… Hey guy! Way to rock that right side. I don\'t care what the left aligned image says, you look great. Don\'t let anyone else tell you differently.
\n\n\n\nIn just a bit here, you should see the text start to wrap below the right aligned image and settle in nicely. There should still be plenty of room and everything should be sitting pretty. Yeah… Just like that. It never felt so good to be right.
\n\n\n\nAnd just when you thought we were done, we\'re going to do them all over again with captions!
\n\n\n\nThe image above happens to be centered. The caption also has a link in it, just to see if it does anything funky.
\n\n\n\nThe rest of this paragraph is filler for the sake of seeing the text wrap around the 150x150 image, which is left aligned.
\n\n\n\nAs you can see the should be some space above, below, and to the right of the image. The text should not be creeping on the image. Creeping is just not right. Images need breathing room too. Let them speak like you words. Let them do their jobs without any hassle from the text. In about one more sentence here, we\'ll see that the text moves from the right of the image down below the image in seamless transition. Again, letting the do it\'s thang. Mission accomplished!
\n\n\n\nAnd now for a massively large image. It also has no alignment.
\n\n\n\nThe image above, though 1200px wide, should not overflow the content area. It should remain contained with no visible disruption to the flow of content.
\n\n\n\nAnd now we\'re going to shift things to the right align. Again, there should be plenty of room above, below, and to the left of the image. Just look at him there… Hey guy! Way to rock that right side. I don\'t care what the left aligned image says, you look great. Don\'t let anyone else tell you differently.
\n\n\n\nIn just a bit here, you should see the text start to wrap below the right aligned image and settle in nicely. There should still be plenty of room and everything should be sitting pretty. Yeah… Just like that. It never felt so good to be right.
\n\n\n\nImagine that we would find a use for the extra wide image! This image has the wide width alignment:
\n\n\n\nCan we go bigger? This image has the full width alignment:
\n\n\n\nAnd that\'s a wrap, yo! You survived the tumultuous waters of alignment. Image alignment achievement unlocked! One last thing: The last item in this post\'s content is a thumbnail floated right. Make sure any elements after the content are clearing properly.
\n\n\n\nΠάντα να είναι περίεργος.\nΠολλές γραμμέ με αναφορά Multi line blockquote with a cite reference:\n
Το HTML\nmultiple contributors - MDN HTML element reference - blockquote\n<blockquote>Element (ή HTML Block Quotation Element) καταδεικνύει ότι το κείμενο έχει μια παράθεση. Συνήθως οπτικοποιείται με εσοχή (δείτε Σημειώσεις για το πως να το αλλάξετε. Ίσως να δίνεται και URL πηγής με την χρήση του cite attribute, μπλα, μπλα<cite>.
| Υπάλληλος Employee | \nΜισθός Salary | \n\n |
|---|---|---|
| Τάδε κάποιος | \n$1 | \nΓιατί τόσα χρειάζεται για να ζήσει | \n
| Jane Doe | \n$100K | \nFor all the blogging she does. | \n
| Fred Bloggs | \n$100M | \nPictures are worth a thousand words, right? So Jane x 1,000. | \n
| Jane Bloggs | \n$100B | \nWith hair like that?! Enough said... | \n
.post-title {\nmargin: 0 0 5px;\nfont-weight: bold;\nfont-size: 38px;\nline-height: 1.2;\nκαι μία γραμμή με πολύ πάρα πολύ υπερβολικά πάρα πολύ μεγάλο κείμενο που πρέπει να δούμε πως το χειρίζεται η γραμματοσειρά και αν ξεχειλίζει από τις γραμμές και δημιουργεί πρόβλημα;\n}\n\nΔιαγραφή Delete Tag\n\nΜπορείτε να <κώδικα code> tag.\n\nΠροδιαμορφωμένο Preformatted Tag\nRobert Frost\n Δυο δρόμοι διασταυρώθηκαν σ\' ένα χρυσαφένιο δάσος ,\n Και προς λύπη μου και τους δυο τα πόδια μου να ταξιδέψουν δεν μπορούσαν\n Κι επί μακρόν εστάθηκα , καθώς ένας ήμουν ταξιδευτής μονάχος ,\n κι έστρεψα το βλέμμα μου στον πρώτο όσο να χαθεί στο βάθος\n μέχρι εκεί που χάνονταν στα άγρια χόρτα που βλαστούσαν.\n\n Two roads diverged in a yellow wood,\n And sorry I could not travel both (\\_/)\n And be one traveler, long I stood (=\'.\'=)\n And looked down one as far as I could (\")_(\")\n To where it bent in the undergrowth;\n\n Then took the other, as just as fair,\n And having perhaps the better claim, |\\_/|\n Because it was grassy and wanted wear; / @ @ \\\n Though as for that the passing there ( > º < )\n Had worn them really about the same, `>>x<<´\n / O \\\n And both that morning equally lay\n In leaves no step had trodden black.\n Oh, I kept the first for another day!\n Yet knowing how way leads on to way,\n I doubted if I should ever come back.\n\n I shall be telling this with a sigh\n Somewhere ages and ages hence:\n Two roads diverged in a wood, and I—\n I took the one less traveled by,\n And that has made all the difference.\n\n\n και μία μακριά, πάρα πολύ μακριά, υπερβολικά μακροσκελής δίχως νόημα πρόταση για να δούμε πως το χειρίζεται το θέμα εμφάνισης και αν αναδιπλώνεται, κρύβεται ή ξεχειλίζει;\n\nQuote Tag for short, inline quotes\n\n
Προγραμματιστές, προγραμματιστές, developers...--Steve Ballmer\n\nStrike Tag (deprecated in HTML5) and S Tag\n\nΑυτή η ετικέτα είναι με διαγράμμιση strike-through
<κώδικα code> tag.\n\nUnderline Tag deprecated in HTML 4, re-introduced in HTML5 with other semantics\n\nΑυτή η ετικέτα δείχνει υπογράμμιση underlined text.\n\nVariable Tag\n\nΑυτή η ετικέτα δείχνει παράμετροι variables.', 'Ελληνικά-Greek', '', 'publish', 'closed', 'closed', '', 'greek', '', '', '2020-02-14 13:31:00', '2020-02-14 10:31:00', '', 0, 'https://wpthemetestdata.wordpress.com/?page_id=1809', 0, 'page', '', 0),
(1811, 2, '2020-02-14 13:31:47', '2020-02-14 10:31:47', 'Σελίδα 2ου επιπέδου - Second level page\n', 'Επίπεδο 2 -Second Greek level', '', 'publish', 'closed', 'closed', '', '%ce%b5%cf%80%ce%af%cf%80%ce%b5%ce%b4%ce%bf-2', '', '', '2020-02-14 13:31:47', '2020-02-14 10:31:47', '', 1809, 'https://wpthemetestdata.wordpress.com/?page_id=1811', 0, 'page', '', 0),
(1813, 2, '2020-02-14 13:32:50', '2020-02-14 10:32:50', '', 'Επίπεδο 3', '', 'publish', 'closed', 'closed', '', '%ce%b5%cf%80%ce%af%cf%80%ce%b5%ce%b4%ce%bf-3', '', '', '2020-02-14 13:32:50', '2020-02-14 10:32:50', '', 1811, 'https://wpthemetestdata.wordpress.com/?page_id=1813', 0, 'page', '', 0),
(1814, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1814', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 1725, 'http://localhost:8080/wordpress/2022/01/24/1814/', 8, 'nav_menu_item', '', 0),
(1815, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1815', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 1725, 'http://localhost:8080/wordpress/2022/01/24/1815/', 9, 'nav_menu_item', '', 0),
(1816, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1816', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 1725, 'http://localhost:8080/wordpress/2022/01/24/1816/', 5, 'nav_menu_item', '', 0),
(1817, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1817', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 1725, 'http://localhost:8080/wordpress/2022/01/24/1817/', 6, 'nav_menu_item', '', 0),
(1818, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1818', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 173, 'http://localhost:8080/wordpress/2022/01/24/1818/', 13, 'nav_menu_item', '', 0),
(1819, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1819', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 173, 'http://localhost:8080/wordpress/2022/01/24/1819/', 14, 'nav_menu_item', '', 0),
(1820, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1820', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 174, 'http://localhost:8080/wordpress/2022/01/24/1820/', 15, 'nav_menu_item', '', 0),
(1821, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1821', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 174, 'http://localhost:8080/wordpress/2022/01/24/1821/', 16, 'nav_menu_item', '', 0),
(1822, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1822', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 0, 'http://localhost:8080/wordpress/2022/01/24/1822/', 18, 'nav_menu_item', '', 0),
(1823, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1823', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 0, 'http://localhost:8080/wordpress/2022/01/24/1823/', 19, 'nav_menu_item', '', 0),
(1824, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1824', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 1725, 'http://localhost:8080/wordpress/2022/01/24/1824/', 5, 'nav_menu_item', '', 0),
(1825, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1825', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 1725, 'http://localhost:8080/wordpress/2022/01/24/1825/', 6, 'nav_menu_item', '', 0),
(1826, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1826', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 173, 'http://localhost:8080/wordpress/2022/01/24/1826/', 13, 'nav_menu_item', '', 0),
(1827, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1827', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 173, 'http://localhost:8080/wordpress/2022/01/24/1827/', 14, 'nav_menu_item', '', 0),
(1828, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1828', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 174, 'http://localhost:8080/wordpress/2022/01/24/1828/', 15, 'nav_menu_item', '', 0),
(1829, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1829', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 174, 'http://localhost:8080/wordpress/2022/01/24/1829/', 16, 'nav_menu_item', '', 0),
(1830, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1830', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 0, 'http://localhost:8080/wordpress/2022/01/24/1830/', 18, 'nav_menu_item', '', 0),
(1831, 1, '2022-01-24 10:18:29', '2022-01-24 10:18:29', ' ', '', '', 'publish', 'closed', 'closed', '', '1831', '', '', '2022-01-24 10:18:29', '2022-01-24 10:18:29', '', 0, 'http://localhost:8080/wordpress/2022/01/24/1831/', 19, 'nav_menu_item', '', 0);
-- --------------------------------------------------------
--
-- Table structure for table `perf_termmeta`
--
CREATE TABLE `perf_termmeta` (
`meta_id` bigint UNSIGNED NOT NULL,
`term_id` bigint UNSIGNED NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
-- --------------------------------------------------------
--
-- Table structure for table `perf_terms`
--
CREATE TABLE `perf_terms` (
`term_id` bigint UNSIGNED NOT NULL,
`name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`slug` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`term_group` bigint NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
--
-- Dumping data for table `perf_terms`
--
INSERT INTO `perf_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES
(1, 'Uncategorized', 'uncategorized', 0),
(2, 'aciform', 'aciform', 0),
(3, 'antiquarianism', 'antiquarianism', 0),
(4, 'arrangement', 'arrangement', 0),
(5, 'asmodeus', 'asmodeus', 0),
(6, 'Block', 'block', 0),
(7, 'Blogroll', 'blogroll', 0),
(8, 'broder', 'broder', 0),
(9, 'buying', 'buying', 0),
(10, 'Cat A', 'cat-a', 0),
(11, 'Cat B', 'cat-b', 0),
(12, 'Cat C', 'cat-c', 0),
(13, 'championship', 'championship', 0),
(14, 'chastening', 'chastening', 0),
(15, 'Classic', 'classic', 0),
(16, 'clerkship', 'clerkship', 0),
(17, 'disinclination', 'disinclination', 0),
(18, 'disinfection', 'disinfection', 0),
(19, 'dispatch', 'dispatch', 0),
(20, 'echappee', 'echappee', 0),
(21, 'Edge Case', 'edge-case-2', 0),
(22, 'enphagy', 'enphagy', 0),
(23, 'equipollent', 'equipollent', 0),
(24, 'fatuity', 'fatuity', 0),
(25, 'Foo A', 'foo-a', 0),
(26, 'Foo Parent', 'foo-parent', 0),
(27, 'gaberlunzie', 'gaberlunzie', 0),
(28, 'illtempered', 'illtempered', 0),
(29, 'insubordination', 'insubordination', 0),
(30, 'lender', 'lender', 0),
(31, 'Markup', 'markup', 0),
(32, 'Media', 'media-2', 0),
(33, 'monosyllable', 'monosyllable', 0),
(34, 'packthread', 'packthread', 0),
(35, 'palter', 'palter', 0),
(36, 'papilionaceous', 'papilionaceous', 0),
(37, 'Parent', 'parent', 0),
(38, 'Parent Category', 'parent-category', 0),
(39, 'personable', 'personable', 0),
(40, 'Post Formats', 'post-formats', 0),
(41, 'propylaeum', 'propylaeum', 0),
(42, 'pustule', 'pustule', 0),
(43, 'quartern', 'quartern', 0),
(44, 'scholarship', 'scholarship', 0),
(45, 'selfconvicted', 'selfconvicted', 0),
(46, 'showshoe', 'showshoe', 0),
(47, 'sloyd', 'sloyd', 0),
(48, 'sub', 'sub', 0),
(49, 'sublunary', 'sublunary', 0),
(50, 'tamtam', 'tamtam', 0),
(51, 'Template', 'template-2', 0),
(52, 'Unpublished', 'unpublished', 0),
(53, 'weakhearted', 'weakhearted', 0),
(54, 'ween', 'ween', 0),
(55, 'wellhead', 'wellhead', 0),
(56, 'wellintentioned', 'wellintentioned', 0),
(57, 'whetstone', 'whetstone', 0),
(58, 'years', 'years', 0),
(59, 'Child 1', 'child-1', 0),
(60, 'Child 2', 'child-2', 0),
(61, 'Child Category 01', 'child-category-01', 0),
(62, 'Child Category 02', 'child-category-02', 0),
(63, 'Child Category 03', 'child-category-03', 0),
(64, 'Child Category 04', 'child-category-04', 0),
(65, 'Child Category 05', 'child-category-05', 0),
(66, 'Foo A', 'foo-a-foo-parent', 0),
(67, 'Grandchild Category', 'grandchild-category', 0),
(68, '8BIT', '8bit', 0),
(69, 'alignment', 'alignment-2', 0),
(70, 'Articles', 'articles', 0),
(71, 'aside', 'aside', 0),
(72, 'audio', 'audio', 0),
(73, 'captions', 'captions-2', 0),
(74, 'categories', 'categories', 0),
(75, 'chat', 'chat', 0),
(76, 'chattels', 'chattels', 0),
(77, 'cienaga', 'cienaga', 0),
(78, 'claycold', 'claycold', 0),
(79, 'Codex', 'codex', 0),
(80, 'comments', 'comments-2', 0),
(81, 'content περιεχόμενο', 'content-2', 0),
(82, 'crushing', 'crushing', 0),
(83, 'css', 'css', 0),
(84, 'depo', 'depo', 0),
(85, 'dinarchy', 'dinarchy', 0),
(86, 'doolie', 'doolie', 0),
(87, 'dowork', 'dowork', 0),
(88, 'edge case', 'edge-case', 0),
(89, 'embeds', 'embeds-2', 0),
(90, 'energumen', 'energumen', 0),
(91, 'ephialtes', 'ephialtes', 0),
(92, 'eudiometer', 'eudiometer', 0),
(93, 'excerpt', 'excerpt-2', 0),
(94, 'Fail', 'fail', 0),
(95, 'featured image', 'featured-image', 0),
(96, 'figuriste', 'figuriste', 0),
(97, 'filler', 'filler', 0),
(98, 'formatting', 'formatting-2', 0),
(99, 'FTW', 'ftw', 0),
(100, 'Fun', 'fun', 0),
(101, 'gallery', 'gallery', 0),
(102, 'goes here', 'goes-here', 0),
(103, 'habergeon', 'habergeon', 0),
(104, 'hapless', 'hapless', 0),
(105, 'hartshorn', 'hartshorn', 0),
(106, 'hostility impregnability', 'hostility-impregnability', 0),
(107, 'html', 'html', 0),
(108, 'image', 'image', 0),
(109, 'impropriation', 'impropriation', 0),
(110, 'is', 'is', 0),
(111, 'jetpack', 'jetpack-2', 0),
(112, 'knave', 'knave', 0),
(113, 'layout', 'layout', 0),
(114, 'link', 'link', 0),
(115, 'lists', 'lists-2', 0),
(116, 'lorem', 'lorem', 0),
(117, 'Love', 'love', 0),
(118, 'markup', 'markup-2', 0),
(119, 'media', 'media', 0),
(120, 'misinformed', 'misinformed', 0),
(121, 'moil', 'moil', 0),
(122, 'more', 'more', 0),
(123, 'mornful', 'mornful', 0),
(124, 'Mothership', 'mothership', 0),
(125, 'Must Read', 'mustread', 0),
(126, 'Nailed It', 'nailedit', 0),
(127, 'outlaw', 'outlaw', 0),
(128, 'pagination', 'pagination', 0),
(129, 'pamphjlet', 'pamphjlet', 0),
(130, 'password', 'password-2', 0),
(131, 'Pictures', 'pictures', 0),
(132, 'pingbacks', 'pingbacks-2', 0),
(133, 'pneumatics', 'pneumatics', 0),
(134, 'portly portreeve', 'portly-portreeve', 0),
(135, 'post', 'post', 0),
(136, 'Post Formats', 'post-formats', 0),
(137, 'precipitancy', 'precipitancy', 0),
(138, 'privation', 'privation', 0),
(139, 'programme', 'programme', 0),
(140, 'psychological', 'psychological', 0),
(141, 'puncher', 'puncher', 0),
(142, 'quote', 'quote', 0),
(143, 'ramose', 'ramose', 0),
(144, 'read more', 'read-more', 0),
(145, 'readability', 'readability', 0),
(146, 'renegade', 'renegade', 0),
(147, 'retrocede', 'retrocede', 0),
(148, 'shortcode', 'shortcode', 0),
(149, 'stagnation unhorsed', 'stagnation-unhorsed', 0),
(150, 'standard', 'standard-2', 0),
(151, 'status', 'status', 0),
(152, 'sticky', 'sticky-2', 0),
(153, 'Success', 'success', 0),
(154, 'Swagger', 'swagger', 0),
(155, 'Tag A', 'tag-a', 0),
(156, 'Tag B', 'tag-b', 0),
(157, 'Tag C', 'tag-c', 0),
(158, 'tag1', 'tag1', 0),
(159, 'tag2', 'tag2', 0),
(160, 'tag3', 'tag3', 0),
(161, 'Tags', 'tags', 0),
(162, 'template', 'template', 0),
(163, 'text', 'text', 0),
(164, 'the man', 'the-man', 0),
(165, 'thunderheaded', 'thunderheaded', 0),
(166, 'tiled', 'tiled', 0),
(167, 'title', 'title', 0),
(168, 'trackbacks', 'trackbacks-2', 0),
(169, 'twitter', 'twitter-2', 0),
(170, 'unculpable', 'unculpable', 0),
(171, 'Unseen', 'unseen', 0),
(172, 'video', 'video', 0),
(173, 'videopress', 'videopress', 0),
(174, 'withered brandnew', 'withered-brandnew', 0),
(175, 'WordPress', 'wordpress', 0),
(176, 'wordpress.tv', 'wordpress-tv', 0),
(177, 'xanthopsia', 'xanthopsia', 0),
(178, 'All Pages', 'all-pages', 0),
(179, 'All Pages Flat', 'all-pages-flat', 0),
(180, 'Empty Menu', 'empty-menu', 0),
(181, 'Short', 'short', 0),
(182, 'Testing Menu', 'testing-menu', 0),
(183, 'Social menu', 'social-menu', 0),
(184, 'Gallery', 'post-format-gallery', 0),
(185, 'Aside', 'post-format-aside', 0),
(186, 'Chat', 'post-format-chat', 0),
(187, 'Link', 'post-format-link', 0),
(188, 'Image', 'post-format-image', 0),
(189, 'Quote', 'post-format-quote', 0),
(190, 'Status', 'post-format-status', 0),
(191, 'Video', 'post-format-video', 0),
(192, 'Audio', 'post-format-audio', 0),
(193, 'content περιεχόμενο', 'content', 0),
(194, 'Columns', 'columns', 0);
-- --------------------------------------------------------
--
-- Table structure for table `perf_term_relationships`
--
CREATE TABLE `perf_term_relationships` (
`object_id` bigint UNSIGNED NOT NULL DEFAULT '0',
`term_taxonomy_id` bigint UNSIGNED NOT NULL DEFAULT '0',
`term_order` int NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
--
-- Dumping data for table `perf_term_relationships`
--
INSERT INTO `perf_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES
(1, 1, 0),
(358, 15, 0),
(358, 40, 0),
(358, 136, 0),
(358, 145, 0),
(358, 150, 0),
(555, 15, 0),
(555, 40, 0),
(555, 101, 0),
(555, 136, 0),
(555, 148, 0),
(555, 184, 0),
(559, 15, 0),
(559, 40, 0),
(559, 71, 0),
(559, 136, 0),
(559, 185, 0),
(562, 15, 0),
(562, 40, 0),
(562, 75, 0),
(562, 136, 0),
(562, 186, 0),
(565, 15, 0),
(565, 40, 0),
(565, 114, 0),
(565, 136, 0),
(565, 187, 0),
(568, 15, 0),
(568, 40, 0),
(568, 108, 0),
(568, 136, 0),
(568, 188, 0),
(575, 15, 0),
(575, 40, 0),
(575, 136, 0),
(575, 142, 0),
(575, 189, 0),
(579, 15, 0),
(579, 40, 0),
(579, 136, 0),
(579, 151, 0),
(579, 190, 0),
(582, 15, 0),
(582, 40, 0),
(582, 89, 0),
(582, 136, 0),
(582, 172, 0),
(582, 176, 0),
(582, 191, 0),
(587, 15, 0),
(587, 40, 0),
(587, 72, 0),
(587, 136, 0),
(587, 148, 0),
(587, 192, 0),
(993, 1, 0),
(993, 15, 0),
(993, 51, 0),
(993, 81, 0),
(993, 93, 0),
(993, 162, 0),
(996, 1, 0),
(996, 15, 0),
(996, 51, 0),
(996, 81, 0),
(996, 144, 0),
(996, 162, 0),
(1000, 15, 0),
(1000, 21, 0),
(1000, 81, 0),
(1000, 83, 0),
(1000, 88, 0),
(1000, 115, 0),
(1000, 118, 0),
(1011, 1, 0),
(1011, 15, 0),
(1011, 51, 0),
(1011, 79, 0),
(1011, 88, 0),
(1011, 95, 0),
(1011, 108, 0),
(1011, 162, 0),
(1016, 1, 0),
(1016, 15, 0),
(1016, 51, 0),
(1016, 79, 0),
(1016, 88, 0),
(1016, 95, 0),
(1016, 108, 0),
(1016, 162, 0),
(1031, 15, 0),
(1031, 40, 0),
(1031, 101, 0),
(1031, 111, 0),
(1031, 136, 0),
(1031, 148, 0),
(1031, 166, 0),
(1031, 184, 0),
(1148, 1, 0),
(1148, 15, 0),
(1148, 51, 0),
(1148, 80, 0),
(1148, 162, 0),
(1149, 1, 0),
(1149, 15, 0),
(1149, 51, 0),
(1149, 80, 0),
(1149, 132, 0),
(1149, 162, 0),
(1149, 168, 0),
(1150, 1, 0),
(1150, 15, 0),
(1150, 51, 0),
(1150, 80, 0),
(1150, 162, 0),
(1151, 15, 0),
(1151, 21, 0),
(1151, 68, 0),
(1151, 69, 0),
(1151, 70, 0),
(1151, 73, 0),
(1151, 74, 0),
(1151, 75, 0),
(1151, 79, 0),
(1151, 80, 0),
(1151, 81, 0),
(1151, 83, 0),
(1151, 87, 0),
(1151, 88, 0),
(1151, 89, 0),
(1151, 93, 0),
(1151, 94, 0),
(1151, 95, 0),
(1151, 99, 0),
(1151, 100, 0),
(1151, 101, 0),
(1151, 107, 0),
(1151, 108, 0),
(1151, 111, 0),
(1151, 113, 0),
(1151, 114, 0),
(1151, 117, 0),
(1151, 118, 0),
(1151, 124, 0),
(1151, 125, 0),
(1151, 126, 0),
(1151, 131, 0),
(1151, 136, 0),
(1151, 142, 0),
(1151, 148, 0),
(1151, 150, 0),
(1151, 153, 0),
(1151, 154, 0),
(1151, 161, 0),
(1151, 162, 0),
(1151, 167, 0),
(1151, 169, 0),
(1151, 171, 0),
(1151, 172, 0),
(1151, 173, 0),
(1151, 175, 0),
(1151, 176, 0),
(1152, 2, 0),
(1152, 3, 0),
(1152, 4, 0),
(1152, 5, 0),
(1152, 8, 0),
(1152, 9, 0),
(1152, 10, 0),
(1152, 11, 0),
(1152, 12, 0),
(1152, 13, 0),
(1152, 14, 0),
(1152, 15, 0),
(1152, 16, 0),
(1152, 17, 0),
(1152, 18, 0),
(1152, 19, 0),
(1152, 20, 0),
(1152, 21, 0),
(1152, 22, 0),
(1152, 23, 0),
(1152, 24, 0),
(1152, 25, 0),
(1152, 26, 0),
(1152, 27, 0),
(1152, 28, 0),
(1152, 29, 0),
(1152, 30, 0),
(1152, 31, 0),
(1152, 32, 0),
(1152, 33, 0),
(1152, 34, 0),
(1152, 35, 0),
(1152, 36, 0),
(1152, 37, 0),
(1152, 38, 0),
(1152, 39, 0),
(1152, 40, 0),
(1152, 41, 0),
(1152, 42, 0),
(1152, 43, 0),
(1152, 44, 0),
(1152, 45, 0),
(1152, 46, 0),
(1152, 47, 0),
(1152, 48, 0),
(1152, 49, 0),
(1152, 50, 0),
(1152, 52, 0),
(1152, 53, 0),
(1152, 54, 0),
(1152, 55, 0),
(1152, 56, 0),
(1152, 57, 0),
(1152, 58, 0),
(1152, 59, 0),
(1152, 60, 0),
(1152, 61, 0),
(1152, 62, 0),
(1152, 63, 0),
(1152, 64, 0),
(1152, 65, 0),
(1152, 66, 0),
(1152, 67, 0),
(1152, 74, 0),
(1152, 88, 0),
(1153, 15, 0),
(1153, 52, 0),
(1153, 81, 0),
(1158, 15, 0),
(1158, 40, 0),
(1158, 108, 0),
(1158, 136, 0),
(1158, 188, 0),
(1161, 15, 0),
(1161, 40, 0),
(1161, 136, 0),
(1161, 191, 0),
(1163, 15, 0),
(1163, 40, 0),
(1163, 108, 0),
(1163, 136, 0),
(1163, 148, 0),
(1163, 188, 0),
(1164, 15, 0),
(1164, 52, 0),
(1164, 81, 0),
(1168, 1, 0),
(1168, 15, 0),
(1168, 51, 0),
(1168, 130, 0),
(1168, 162, 0),
(1169, 15, 0),
(1169, 21, 0),
(1169, 88, 0),
(1169, 113, 0),
(1169, 167, 0),
(1170, 15, 0),
(1170, 21, 0),
(1170, 81, 0),
(1170, 88, 0),
(1170, 113, 0),
(1171, 1, 0),
(1171, 15, 0),
(1171, 51, 0),
(1171, 81, 0),
(1171, 128, 0),
(1171, 162, 0),
(1173, 15, 0),
(1173, 31, 0),
(1173, 83, 0),
(1173, 107, 0),
(1173, 167, 0),
(1174, 15, 0),
(1174, 31, 0),
(1174, 107, 0),
(1174, 118, 0),
(1174, 135, 0),
(1174, 167, 0),
(1175, 15, 0),
(1175, 21, 0),
(1175, 81, 0),
(1175, 83, 0),
(1175, 88, 0),
(1175, 107, 0),
(1175, 113, 0),
(1175, 167, 0),
(1176, 15, 0),
(1176, 31, 0),
(1176, 69, 0),
(1176, 81, 0),
(1176, 83, 0),
(1176, 118, 0),
(1177, 15, 0),
(1177, 31, 0),
(1177, 69, 0),
(1177, 73, 0),
(1177, 81, 0),
(1177, 83, 0),
(1177, 108, 0),
(1177, 118, 0),
(1178, 15, 0),
(1178, 31, 0),
(1178, 81, 0),
(1178, 83, 0),
(1178, 98, 0),
(1178, 107, 0),
(1178, 118, 0),
(1179, 15, 0),
(1179, 32, 0),
(1179, 81, 0),
(1179, 89, 0),
(1179, 119, 0),
(1179, 169, 0),
(1241, 1, 0),
(1241, 15, 0),
(1241, 152, 0),
(1241, 162, 0),
(1446, 1, 0),
(1446, 15, 0),
(1446, 51, 0),
(1446, 81, 0),
(1446, 93, 0),
(1446, 162, 0),
(1724, 1, 0),
(1724, 79, 0),
(1726, 182, 0),
(1727, 182, 0),
(1728, 182, 0),
(1729, 182, 0),
(1730, 182, 0),
(1731, 182, 0),
(1732, 182, 0),
(1733, 182, 0),
(1734, 182, 0),
(1735, 182, 0),
(1736, 182, 0),
(1737, 182, 0),
(1738, 182, 0),
(1739, 182, 0),
(1740, 182, 0),
(1741, 182, 0),
(1742, 182, 0),
(1743, 182, 0),
(1744, 182, 0),
(1745, 182, 0),
(1746, 182, 0),
(1747, 183, 0),
(1748, 183, 0),
(1749, 183, 0),
(1750, 183, 0),
(1751, 183, 0),
(1752, 181, 0),
(1753, 181, 0),
(1754, 181, 0),
(1755, 181, 0),
(1756, 181, 0),
(1757, 181, 0),
(1758, 179, 0),
(1759, 179, 0),
(1760, 179, 0),
(1761, 179, 0),
(1762, 179, 0),
(1763, 179, 0),
(1764, 179, 0),
(1765, 179, 0),
(1766, 179, 0),
(1767, 179, 0),
(1768, 178, 0),
(1769, 178, 0),
(1770, 178, 0),
(1771, 178, 0),
(1772, 178, 0),
(1773, 178, 0),
(1774, 178, 0),
(1775, 178, 0),
(1776, 178, 0),
(1777, 178, 0),
(1778, 6, 0),
(1778, 89, 0),
(1778, 101, 0),
(1778, 108, 0),
(1778, 172, 0),
(1778, 193, 0),
(1779, 6, 0),
(1779, 98, 0),
(1779, 193, 0),
(1780, 6, 0),
(1780, 193, 0),
(1781, 6, 0),
(1781, 32, 0),
(1781, 89, 0),
(1781, 193, 0),
(1782, 6, 0),
(1782, 193, 0),
(1783, 6, 0),
(1783, 193, 0),
(1783, 194, 0),
(1784, 6, 0),
(1784, 108, 0),
(1785, 6, 0),
(1785, 193, 0),
(1786, 6, 0),
(1786, 193, 0),
(1787, 6, 0),
(1787, 101, 0),
(1787, 108, 0),
(1787, 193, 0),
(1787, 194, 0),
(1788, 6, 0),
(1788, 108, 0),
(1788, 193, 0),
(1814, 182, 0),
(1815, 182, 0),
(1816, 179, 0),
(1817, 179, 0),
(1818, 179, 0),
(1819, 179, 0),
(1820, 179, 0),
(1821, 179, 0),
(1822, 179, 0),
(1823, 179, 0),
(1824, 178, 0),
(1825, 178, 0),
(1826, 178, 0),
(1827, 178, 0),
(1828, 178, 0),
(1829, 178, 0),
(1830, 178, 0),
(1831, 178, 0);
-- --------------------------------------------------------
--
-- Table structure for table `perf_term_taxonomy`
--
CREATE TABLE `perf_term_taxonomy` (
`term_taxonomy_id` bigint UNSIGNED NOT NULL,
`term_id` bigint UNSIGNED NOT NULL DEFAULT '0',
`taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`description` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`parent` bigint UNSIGNED NOT NULL DEFAULT '0',
`count` bigint NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
--
-- Dumping data for table `perf_term_taxonomy`
--
INSERT INTO `perf_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES
(1, 1, 'category', '', 0, 13),
(2, 2, 'category', '', 0, 1),
(3, 3, 'category', '', 0, 1),
(4, 4, 'category', '', 0, 1),
(5, 5, 'category', '', 0, 1),
(6, 6, 'category', 'Items in the block category have been created with the block editor.', 0, 11),
(7, 7, 'category', '', 0, 0),
(8, 8, 'category', '', 0, 1),
(9, 9, 'category', '', 0, 1),
(10, 10, 'category', '', 0, 1),
(11, 11, 'category', '', 0, 1),
(12, 12, 'category', '', 0, 1),
(13, 13, 'category', '', 0, 1),
(14, 14, 'category', '', 0, 1),
(15, 15, 'category', 'Items in the classic category have been created with the classic editor.', 0, 37),
(16, 16, 'category', '', 0, 1),
(17, 17, 'category', '', 0, 1),
(18, 18, 'category', '', 0, 1),
(19, 19, 'category', '', 0, 1),
(20, 20, 'category', '', 0, 1),
(21, 21, 'category', 'Posts that have edge-case related tests', 0, 6),
(22, 22, 'category', '', 0, 1),
(23, 23, 'category', '', 0, 1),
(24, 24, 'category', '', 0, 1),
(25, 25, 'category', '', 0, 1),
(26, 26, 'category', '', 0, 1),
(27, 27, 'category', '', 0, 1),
(28, 28, 'category', '', 0, 1),
(29, 29, 'category', '', 0, 1),
(30, 30, 'category', '', 0, 1),
(31, 31, 'category', 'Posts in this category test markup tags and styles.', 0, 6),
(32, 32, 'category', 'Posts that have media-related tests', 0, 3),
(33, 33, 'category', '', 0, 1),
(34, 34, 'category', '', 0, 1),
(35, 35, 'category', '', 0, 1),
(36, 36, 'category', '', 0, 1),
(37, 37, 'category', '', 0, 1),
(38, 38, 'category', 'This is a parent category. It will contain child categories', 0, 1),
(39, 39, 'category', '', 0, 1),
(40, 40, 'category', 'Posts in this category test post formats.', 0, 15),
(41, 41, 'category', '', 0, 1),
(42, 42, 'category', '', 0, 1),
(43, 43, 'category', '', 0, 1),
(44, 44, 'category', '', 0, 1),
(45, 45, 'category', '', 0, 1),
(46, 46, 'category', '', 0, 1),
(47, 47, 'category', '', 0, 1),
(48, 48, 'category', '', 2, 1),
(49, 49, 'category', '', 0, 1),
(50, 50, 'category', '', 0, 1),
(51, 51, 'category', 'Posts with template-related tests', 0, 10),
(52, 52, 'category', 'Posts in this category test unpublished posts.', 0, 1),
(53, 53, 'category', '', 0, 1),
(54, 54, 'category', '', 0, 1),
(55, 55, 'category', '', 0, 1),
(56, 56, 'category', '', 0, 1),
(57, 57, 'category', '', 0, 1),
(58, 58, 'category', '', 0, 1),
(59, 59, 'category', '', 37, 1),
(60, 60, 'category', '', 59, 1),
(61, 61, 'category', 'This is a description for the Child Category 01.', 38, 1),
(62, 62, 'category', 'This is a description for the Child Category 02.', 38, 1),
(63, 63, 'category', 'This is a description for the Child Category 03.', 38, 1),
(64, 64, 'category', 'This is a description for the Child Category 04.', 38, 1),
(65, 65, 'category', 'This is a description for the Child Category 05.', 38, 1),
(66, 66, 'category', '', 26, 1),
(67, 67, 'category', 'This is a description for the Grandchild Category.', 63, 1),
(68, 68, 'post_tag', 'Tags posts about 8BIT.', 0, 1),
(69, 69, 'post_tag', '', 0, 3),
(70, 70, 'post_tag', 'Tags posts about Articles.', 0, 1),
(71, 71, 'post_tag', '', 0, 1),
(72, 72, 'post_tag', '', 0, 1),
(73, 73, 'post_tag', '', 0, 2),
(74, 74, 'post_tag', '', 0, 2),
(75, 75, 'post_tag', '', 0, 2),
(76, 76, 'post_tag', '', 0, 0),
(77, 77, 'post_tag', '', 0, 0),
(78, 78, 'post_tag', '', 0, 0),
(79, 79, 'post_tag', '', 0, 4),
(80, 80, 'post_tag', '', 0, 4),
(81, 81, 'post_tag', '', 0, 12),
(82, 82, 'post_tag', '', 0, 0),
(83, 83, 'post_tag', '', 0, 7),
(84, 84, 'post_tag', '', 0, 0),
(85, 85, 'post_tag', '', 0, 0),
(86, 86, 'post_tag', '', 0, 0),
(87, 87, 'post_tag', 'Tags posts about #dowork.', 0, 1),
(88, 88, 'post_tag', '', 0, 8),
(89, 89, 'post_tag', '', 0, 5),
(90, 90, 'post_tag', '', 0, 0),
(91, 91, 'post_tag', '', 0, 0),
(92, 92, 'post_tag', '', 0, 0),
(93, 93, 'post_tag', '', 0, 3),
(94, 94, 'post_tag', 'Tags posts about fail.', 0, 1),
(95, 95, 'post_tag', '', 0, 3),
(96, 96, 'post_tag', '', 0, 0),
(97, 97, 'post_tag', '', 0, 0),
(98, 98, 'post_tag', '', 0, 2),
(99, 99, 'post_tag', '', 0, 1),
(100, 100, 'post_tag', 'Tags posts about fun.', 0, 1),
(101, 101, 'post_tag', '', 0, 5),
(102, 102, 'post_tag', '', 0, 0),
(103, 103, 'post_tag', '', 0, 0),
(104, 104, 'post_tag', '', 0, 0),
(105, 105, 'post_tag', '', 0, 0),
(106, 106, 'post_tag', '', 0, 0),
(107, 107, 'post_tag', '', 0, 5),
(108, 108, 'post_tag', '', 0, 11),
(109, 109, 'post_tag', '', 0, 0),
(110, 110, 'post_tag', '', 0, 0),
(111, 111, 'post_tag', '', 0, 2),
(112, 112, 'post_tag', '', 0, 0),
(113, 113, 'post_tag', '', 0, 4),
(114, 114, 'post_tag', '', 0, 2),
(115, 115, 'post_tag', '', 0, 1),
(116, 116, 'post_tag', '', 0, 0),
(117, 117, 'post_tag', 'Tags posts about love.', 0, 1),
(118, 118, 'post_tag', '', 0, 6),
(119, 119, 'post_tag', '', 0, 1),
(120, 120, 'post_tag', '', 0, 0),
(121, 121, 'post_tag', '', 0, 0),
(122, 122, 'post_tag', '', 0, 0),
(123, 123, 'post_tag', '', 0, 0),
(124, 124, 'post_tag', 'Tags posts about motherships.', 0, 1),
(125, 125, 'post_tag', 'Tags posts about articles you must read.', 0, 1),
(126, 126, 'post_tag', 'Tags posts about that nailed it.', 0, 1),
(127, 127, 'post_tag', '', 0, 0),
(128, 128, 'post_tag', '', 0, 1),
(129, 129, 'post_tag', '', 0, 0),
(130, 130, 'post_tag', '', 0, 1),
(131, 131, 'post_tag', '', 0, 1),
(132, 132, 'post_tag', '', 0, 1),
(133, 133, 'post_tag', '', 0, 0),
(134, 134, 'post_tag', '', 0, 0),
(135, 135, 'post_tag', '', 0, 1),
(136, 136, 'post_tag', '', 0, 15),
(137, 137, 'post_tag', '', 0, 0),
(138, 138, 'post_tag', '', 0, 0),
(139, 139, 'post_tag', '', 0, 0),
(140, 140, 'post_tag', '', 0, 0),
(141, 141, 'post_tag', '', 0, 0),
(142, 142, 'post_tag', '', 0, 2),
(143, 143, 'post_tag', '', 0, 0),
(144, 144, 'post_tag', '', 0, 1),
(145, 145, 'post_tag', '', 0, 1),
(146, 146, 'post_tag', '', 0, 0),
(147, 147, 'post_tag', '', 0, 0),
(148, 148, 'post_tag', '', 0, 5),
(149, 149, 'post_tag', '', 0, 0),
(150, 150, 'post_tag', '', 0, 2),
(151, 151, 'post_tag', '', 0, 1),
(152, 152, 'post_tag', '', 0, 1),
(153, 153, 'post_tag', 'Tags posts about success.', 0, 1),
(154, 154, 'post_tag', 'Tags posts about swagger.', 0, 1),
(155, 155, 'post_tag', '', 0, 0),
(156, 156, 'post_tag', '', 0, 0),
(157, 157, 'post_tag', '', 0, 0),
(158, 158, 'post_tag', '', 0, 0),
(159, 159, 'post_tag', '', 0, 0),
(160, 160, 'post_tag', '', 0, 0),
(161, 161, 'post_tag', 'Tags posts about tags. #inception', 0, 1),
(162, 162, 'post_tag', '', 0, 12),
(163, 163, 'post_tag', '', 0, 0),
(164, 164, 'post_tag', '', 0, 0),
(165, 165, 'post_tag', '', 0, 0),
(166, 166, 'post_tag', '', 0, 1),
(167, 167, 'post_tag', '', 0, 5),
(168, 168, 'post_tag', '', 0, 1),
(169, 169, 'post_tag', '', 0, 2),
(170, 170, 'post_tag', '', 0, 0),
(171, 171, 'post_tag', 'Tags posts about things that cannot be unseen.', 0, 1),
(172, 172, 'post_tag', '', 0, 3),
(173, 173, 'post_tag', '', 0, 1),
(174, 174, 'post_tag', '', 0, 0),
(175, 175, 'post_tag', 'Tags posts about WordPress.', 0, 1),
(176, 176, 'post_tag', '', 0, 2),
(177, 177, 'post_tag', '', 0, 0),
(178, 178, 'nav_menu', '', 0, 18),
(179, 179, 'nav_menu', '', 0, 18),
(180, 180, 'nav_menu', '', 0, 0),
(181, 181, 'nav_menu', '', 0, 6),
(182, 182, 'nav_menu', '', 0, 23),
(183, 183, 'nav_menu', '', 0, 5),
(184, 184, 'post_format', '', 0, 2),
(185, 185, 'post_format', '', 0, 1),
(186, 186, 'post_format', '', 0, 1),
(187, 187, 'post_format', '', 0, 1),
(188, 188, 'post_format', '', 0, 3),
(189, 189, 'post_format', '', 0, 1),
(190, 190, 'post_format', '', 0, 1),
(191, 191, 'post_format', '', 0, 2),
(192, 192, 'post_format', '', 0, 1),
(193, 193, 'post_tag', '', 0, 10),
(194, 194, 'post_tag', '', 0, 2);
-- --------------------------------------------------------
--
-- Table structure for table `perf_usermeta`
--
CREATE TABLE `perf_usermeta` (
`umeta_id` bigint UNSIGNED NOT NULL,
`user_id` bigint UNSIGNED NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
--
-- Dumping data for table `perf_usermeta`
--
INSERT INTO `perf_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES
(1, 1, 'nickname', 'satish'),
(2, 1, 'first_name', ''),
(3, 1, 'last_name', ''),
(4, 1, 'description', ''),
(5, 1, 'rich_editing', 'true'),
(6, 1, 'syntax_highlighting', 'true'),
(7, 1, 'comment_shortcuts', 'false'),
(8, 1, 'admin_color', 'fresh'),
(9, 1, 'use_ssl', '0'),
(10, 1, 'show_admin_bar_front', 'true'),
(11, 1, 'locale', ''),
(12, 1, 'perf_capabilities', 'a:1:{s:13:\"administrator\";b:1;}'),
(13, 1, 'perf_user_level', '10'),
(14, 1, 'dismissed_wp_pointers', ''),
(15, 1, 'show_welcome_panel', '1'),
(16, 1, 'session_tokens', 'a:1:{s:64:\"ab12ebeb95006177ff575138f19b2aae9b5aba44027d4ed8d0e0552b5e958f47\";a:4:{s:10:\"expiration\";i:1643192227;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:120:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36\";s:5:\"login\";i:1643019427;}}'),
(17, 1, 'perf_dashboard_quick_press_last_post_id', '4'),
(18, 2, 'nickname', 'Rahul'),
(19, 2, 'first_name', ''),
(20, 2, 'last_name', ''),
(21, 2, 'description', ''),
(22, 2, 'rich_editing', 'true'),
(23, 2, 'syntax_highlighting', 'true'),
(24, 2, 'comment_shortcuts', 'false'),
(25, 2, 'admin_color', 'fresh'),
(26, 2, 'use_ssl', '0'),
(27, 2, 'show_admin_bar_front', 'true'),
(28, 2, 'locale', ''),
(29, 2, 'perf_capabilities', 'a:1:{s:10:\"subscriber\";b:1;}'),
(30, 2, 'perf_user_level', '0'),
(31, 2, 'dismissed_wp_pointers', '');
-- --------------------------------------------------------
--
-- Table structure for table `perf_users`
--
CREATE TABLE `perf_users` (
`ID` bigint UNSIGNED NOT NULL,
`user_login` varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_pass` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_nicename` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_url` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`user_activation_key` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_status` int NOT NULL DEFAULT '0',
`display_name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
--
-- Dumping data for table `perf_users`
--
INSERT INTO `perf_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES
(1, 'satish', '$P$BBrIGcyFZjixJAfebBS55fkd/hFiV0.', 'satish', 'satish.iitg@gmail.com', 'http://localhost:8080/wordpress', '2022-01-24 10:16:52', '', 0, 'satish'),
(2, 'Rahul', '$P$BORFiQkbJCaZcW4qZReQW.5Z0c8zqW1', 'rahul', '', '', '2022-01-24 10:18:28', '', 0, 'Rahul');
--
-- Indexes for dumped tables
--
--
-- Indexes for table `perf_commentmeta`
--
ALTER TABLE `perf_commentmeta`
ADD PRIMARY KEY (`meta_id`),
ADD KEY `comment_id` (`comment_id`),
ADD KEY `meta_key` (`meta_key`(191));
--
-- Indexes for table `perf_comments`
--
ALTER TABLE `perf_comments`
ADD PRIMARY KEY (`comment_ID`),
ADD KEY `comment_post_ID` (`comment_post_ID`),
ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
ADD KEY `comment_date_gmt` (`comment_date_gmt`),
ADD KEY `comment_parent` (`comment_parent`),
ADD KEY `comment_author_email` (`comment_author_email`(10));
--
-- Indexes for table `perf_links`
--
ALTER TABLE `perf_links`
ADD PRIMARY KEY (`link_id`),
ADD KEY `link_visible` (`link_visible`);
--
-- Indexes for table `perf_options`
--
ALTER TABLE `perf_options`
ADD PRIMARY KEY (`option_id`),
ADD UNIQUE KEY `option_name` (`option_name`),
ADD KEY `autoload` (`autoload`);
--
-- Indexes for table `perf_postmeta`
--
ALTER TABLE `perf_postmeta`
ADD PRIMARY KEY (`meta_id`),
ADD KEY `post_id` (`post_id`),
ADD KEY `meta_key` (`meta_key`(191));
--
-- Indexes for table `perf_posts`
--
ALTER TABLE `perf_posts`
ADD PRIMARY KEY (`ID`),
ADD KEY `post_name` (`post_name`(191)),
ADD KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`),
ADD KEY `post_parent` (`post_parent`),
ADD KEY `post_author` (`post_author`);
--
-- Indexes for table `perf_termmeta`
--
ALTER TABLE `perf_termmeta`
ADD PRIMARY KEY (`meta_id`),
ADD KEY `term_id` (`term_id`),
ADD KEY `meta_key` (`meta_key`(191));
--
-- Indexes for table `perf_terms`
--
ALTER TABLE `perf_terms`
ADD PRIMARY KEY (`term_id`),
ADD KEY `slug` (`slug`(191)),
ADD KEY `name` (`name`(191));
--
-- Indexes for table `perf_term_relationships`
--
ALTER TABLE `perf_term_relationships`
ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`),
ADD KEY `term_taxonomy_id` (`term_taxonomy_id`);
--
-- Indexes for table `perf_term_taxonomy`
--
ALTER TABLE `perf_term_taxonomy`
ADD PRIMARY KEY (`term_taxonomy_id`),
ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
ADD KEY `taxonomy` (`taxonomy`);
--
-- Indexes for table `perf_usermeta`
--
ALTER TABLE `perf_usermeta`
ADD PRIMARY KEY (`umeta_id`),
ADD KEY `user_id` (`user_id`),
ADD KEY `meta_key` (`meta_key`(191));
--
-- Indexes for table `perf_users`
--
ALTER TABLE `perf_users`
ADD PRIMARY KEY (`ID`),
ADD KEY `user_login_key` (`user_login`),
ADD KEY `user_nicename` (`user_nicename`),
ADD KEY `user_email` (`user_email`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `perf_commentmeta`
--
ALTER TABLE `perf_commentmeta`
MODIFY `meta_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `perf_comments`
--
ALTER TABLE `perf_comments`
MODIFY `comment_ID` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=34;
--
-- AUTO_INCREMENT for table `perf_links`
--
ALTER TABLE `perf_links`
MODIFY `link_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `perf_options`
--
ALTER TABLE `perf_options`
MODIFY `option_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=157;
--
-- AUTO_INCREMENT for table `perf_postmeta`
--
ALTER TABLE `perf_postmeta`
MODIFY `meta_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=607;
--
-- AUTO_INCREMENT for table `perf_posts`
--
ALTER TABLE `perf_posts`
MODIFY `ID` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=1832;
--
-- AUTO_INCREMENT for table `perf_termmeta`
--
ALTER TABLE `perf_termmeta`
MODIFY `meta_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `perf_terms`
--
ALTER TABLE `perf_terms`
MODIFY `term_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=195;
--
-- AUTO_INCREMENT for table `perf_term_taxonomy`
--
ALTER TABLE `perf_term_taxonomy`
MODIFY `term_taxonomy_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=195;
--
-- AUTO_INCREMENT for table `perf_usermeta`
--
ALTER TABLE `perf_usermeta`
MODIFY `umeta_id` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=32;
--
-- AUTO_INCREMENT for table `perf_users`
--
ALTER TABLE `perf_users`
MODIFY `ID` bigint UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
COMMIT;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;