text: -- phpMyAdmin SQL Dump
  -- version 5.0.2
  -- https://www.phpmyadmin.net/
  --
  -- Хост: mysql:3306
  -- Время создания: Янв 29 2021 г., 12:12
  -- Версия сервера: 10.4.15-MariaDB
  -- Версия PHP: 7.3.26
  
  SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
  START TRANSACTION;
  SET time_zone = "+00:00";
  
  
  /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
  /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
  /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
  /*!40101 SET NAMES utf8mb4 */;
  
  --
  -- База данных: `wordpress`
  --
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_commentmeta`
  --
  
  CREATE TABLE `wp_commentmeta` (
    `meta_id` bigint(20) UNSIGNED NOT NULL,
    `comment_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
    `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_comments`
  --
  
  CREATE TABLE `wp_comments` (
    `comment_ID` bigint(20) UNSIGNED NOT NULL,
    `comment_post_ID` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `comment_author` tinytext COLLATE utf8mb4_unicode_ci NOT NULL,
    `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
    `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
    `comment_content` text COLLATE utf8mb4_unicode_ci NOT NULL,
    `comment_karma` int(11) NOT NULL DEFAULT 0,
    `comment_approved` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '1',
    `comment_agent` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `comment_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'comment',
    `comment_parent` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_comments`
  --
  
  INSERT INTO `wp_comments` (`comment_ID`, `comment_post_ID`, `comment_author`, `comment_author_email`, `comment_author_url`, `comment_author_IP`, `comment_date`, `comment_date_gmt`, `comment_content`, `comment_karma`, `comment_approved`, `comment_agent`, `comment_type`, `comment_parent`, `user_id`) VALUES
  (1, 1, 'A WordPress Commenter', 'wapuu@wordpress.example', 'https://wordpress.org/', '', '2021-01-29 12:08:19', '2021-01-29 12:08:19', 'Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from <a href=\"https://gravatar.com\">Gravatar</a>.', 0, '1', '', 'comment', 0, 0);
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_links`
  --
  
  CREATE TABLE `wp_links` (
    `link_id` bigint(20) UNSIGNED NOT NULL,
    `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'Y',
    `link_owner` bigint(20) UNSIGNED NOT NULL DEFAULT 1,
    `link_rating` int(11) NOT NULL DEFAULT 0,
    `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
    `link_rel` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `link_notes` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
    `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ''
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_options`
  --
  
  CREATE TABLE `wp_options` (
    `option_id` bigint(20) UNSIGNED NOT NULL,
    `option_name` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
    `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes'
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_options`
  --
  
  INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
  (1, 'siteurl', 'http://34.116.235.52:5050', 'yes'),
  (2, 'home', 'http://34.116.235.52:5050', 'yes'),
  (3, 'blogname', 'cbach', 'yes'),
  (4, 'blogdescription', 'Just another WordPress site', 'yes'),
  (5, 'users_can_register', '0', 'yes'),
  (6, 'admin_email', 'cbach@cbach.cbach', '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', '1', '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', '', 'yes'),
  (29, 'rewrite_rules', '', 'yes'),
  (30, 'hack_file', '0', 'yes'),
  (31, 'blog_charset', 'UTF-8', 'yes'),
  (32, 'moderation_keys', '', 'no'),
  (33, 'active_plugins', 'a:0:{}', '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', '1', '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:0:{}', 'yes'),
  (76, 'widget_categories', 'a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', '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', '1627474099', '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, 'initial_db_version', '49752', 'yes'),
  (99, 'wp_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'),
  (100, 'fresh_site', '1', 'yes'),
  (101, 'widget_search', 'a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}', 'yes'),
  (102, 'widget_recent-posts', 'a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}', 'yes'),
  (103, 'widget_recent-comments', 'a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}', 'yes'),
  (104, 'widget_archives', 'a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', 'yes'),
  (105, 'widget_meta', 'a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}', 'yes'),
  (106, 'sidebars_widgets', 'a:4:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:3:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";}s:9:\"sidebar-2\";a:3:{i:0;s:10:\"archives-2\";i:1;s:12:\"categories-2\";i:2;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}', 'yes'),
  (107, 'cron', 'a:7:{i:1611922111;a:1:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1611922112;a:4:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1611922131;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1611922135;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1611922191;a:1:{s:28:\"wp_update_comment_type_batch\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:0:{}}}}i:1612008511;a:1:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}}s:7:\"version\";i:2;}', 'yes'),
  (108, 'widget_pages', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (109, 'widget_calendar', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (110, 'widget_media_audio', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (111, 'widget_media_image', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (112, 'widget_media_gallery', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (113, 'widget_media_video', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (114, 'widget_tag_cloud', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (115, 'widget_nav_menu', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (116, 'widget_custom_html', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'),
  (117, '_transient_doing_cron', '1611922269.0945549011230468750000', 'yes'),
  (118, '_site_transient_update_core', 'O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:57:\"https://downloads.wordpress.org/release/wordpress-5.6.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:57:\"https://downloads.wordpress.org/release/wordpress-5.6.zip\";s:10:\"no_content\";s:68:\"https://downloads.wordpress.org/release/wordpress-5.6-no-content.zip\";s:11:\"new_bundled\";s:69:\"https://downloads.wordpress.org/release/wordpress-5.6-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:3:\"5.6\";s:7:\"version\";s:3:\"5.6\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.6\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1611922132;s:15:\"version_checked\";s:3:\"5.6\";s:12:\"translations\";a:0:{}}', 'no'),
  (119, '_site_transient_update_plugins', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1611922132;s:8:\"response\";a:1:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.1.8\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.8.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}s:6:\"tested\";s:3:\"5.6\";s:12:\"requires_php\";b:0;s:13:\"compatibility\";O:8:\"stdClass\":0:{}}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:1:{s:9:\"hello.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}}}}', 'no'),
  (120, '_site_transient_timeout_theme_roots', '1611923932', 'no'),
  (121, '_site_transient_theme_roots', 'a:3:{s:14:\"twentynineteen\";s:7:\"/themes\";s:12:\"twentytwenty\";s:7:\"/themes\";s:15:\"twentytwentyone\";s:7:\"/themes\";}', 'no'),
  (122, '_site_transient_update_themes', 'O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1611922133;s:7:\"checked\";a:3:{s:14:\"twentynineteen\";s:3:\"1.8\";s:12:\"twentytwenty\";s:3:\"1.6\";s:15:\"twentytwentyone\";s:3:\"1.0\";}s:8:\"response\";a:2:{s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"1.9\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.1.9.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentytwentyone\";a:6:{s:5:\"theme\";s:15:\"twentytwentyone\";s:11:\"new_version\";s:3:\"1.1\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentytwentyone/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentytwentyone.1.1.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.6\";}}s:9:\"no_update\";a:1:{s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.6\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.6.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}}s:12:\"translations\";a:0:{}}', 'no'),
  (123, '_site_transient_timeout_browser_8a761d7d184b5e8f7a8e1a279afdabf6', '1612526933', 'no'),
  (124, '_site_transient_browser_8a761d7d184b5e8f7a8e1a279afdabf6', 'a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:12:\"88.0.4324.96\";s:8:\"platform\";s:5:\"Linux\";s:10:\"update_url\";s:29:\"https://www.google.com/chrome\";s:7:\"img_src\";s:43:\"http://s.w.org/images/browsers/chrome.png?1\";s:11:\"img_src_ssl\";s:44:\"https://s.w.org/images/browsers/chrome.png?1\";s:15:\"current_version\";s:2:\"18\";s:7:\"upgrade\";b:0;s:8:\"insecure\";b:0;s:6:\"mobile\";b:0;}', 'no'),
  (125, '_site_transient_timeout_php_check_27ba000775e29cd0fe5915760b10a2bf', '1612526935', 'no'),
  (126, '_site_transient_php_check_27ba000775e29cd0fe5915760b10a2bf', 'a:5:{s:19:\"recommended_version\";s:3:\"7.4\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:1;s:9:\"is_secure\";b:1;s:13:\"is_acceptable\";b:1;}', 'no'),
  (127, 'can_compress_scripts', '1', 'no'),
  (128, '_site_transient_timeout_community-events-e2f2ed925cc0dc7eddd67ec58c0404fa', '1611965336', 'no'),
  (129, '_site_transient_community-events-e2f2ed925cc0dc7eddd67ec58c0404fa', 'a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:10:\"172.17.0.0\";}s:6:\"events\";a:2:{i:0;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:49:\"Discussion group: How To Find Help With WordPress\";s:3:\"url\";s:72:\"https://www.meetup.com/learn-wordpress-discussions/events/xdcjdsyccdbwb/\";s:6:\"meetup\";s:27:\"Learn WordPress Discussions\";s:10:\"meetup_url\";s:51:\"https://www.meetup.com/learn-wordpress-discussions/\";s:4:\"date\";s:19:\"2021-02-03 20:00:00\";s:8:\"end_date\";s:19:\"2021-02-03 21:00:00\";s:20:\"start_unix_timestamp\";i:1612411200;s:18:\"end_unix_timestamp\";i:1612414800;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"US\";s:8:\"latitude\";d:37.779998779297;s:9:\"longitude\";d:-122.41999816895;}}i:1;a:10:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:23:\"WordCamp India (Online)\";s:3:\"url\";s:32:\"https://india.wordcamp.org/2021/\";s:6:\"meetup\";N;s:10:\"meetup_url\";N;s:4:\"date\";s:19:\"2021-01-30 00:00:00\";s:8:\"end_date\";s:19:\"2021-02-14 00:00:00\";s:20:\"start_unix_timestamp\";i:1611945000;s:18:\"end_unix_timestamp\";i:1613241000;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"IN\";s:8:\"latitude\";d:20.593684;s:9:\"longitude\";d:78.96288;}}}}', 'no'),
  (130, '_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3', '1611965336', 'no');
  INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
  (131, '_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3', 'a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"News –  – WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"https://wordpress.org/news\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"WordPress News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Jan 2021 18:27: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:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"en-US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=5.7-alpha-50070\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:10:{i:0;a:6:{s:4:\"data\";s:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"People of WordPress: Thelma Mutete\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/01/people-of-wordpress-thelma-mutete/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 21 Jan 2021 16:40:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:9:\"heropress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:16:\"ContributorStory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:13:\"Web developer\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9518\";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:171:\"From writing her first line of code when she was 16, Thelma Mutete knew she wanted to work in IT. She shares her journey in web development and her discovery 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: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:8707:\"\n<p><em>WordPress is open source software, maintained by a global network of contributors. There are many examples of how WordPress has changed people’s lives for the better. In this monthly series, we share some of those lesser-known, amazing stories.</em></p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" src=\"https://i1.wp.com/wordpress.org/news/files/2021/01/Thelma-Mutete.jpg?resize=500%2C750&#038;ssl=1\" alt=\"Thelma Mutete at a WordCamp\" class=\"wp-image-9564\" width=\"500\" height=\"750\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2021/01/Thelma-Mutete.jpg?w=667&amp;ssl=1 667w, https://i1.wp.com/wordpress.org/news/files/2021/01/Thelma-Mutete.jpg?resize=200%2C300&amp;ssl=1 200w\" sizes=\"(max-width: 500px) 100vw, 500px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<p>From a young age Thelma was encouraged by her father to ‘work hard, and dream big’. In High School, she pursued a career in Computer Science. She said: “I did not know what I would be doing or how I would get there but I just knew that I was going to pursue a career in information technology.”</p>\n\n\n\n<p>She wrote her first line of code at the age of 16 living in Zimbabwe, Africa. This was to mark the beginning of her enthusiasm for computer programming.</p>\n\n\n\n<p>When she joined the school’s computer class, Thelma thought she would learn Excel and Word. Instead, the assignment was to write her first program in C. She said: “It was not easy, but it was very exciting. l remember writing up simple code for a Video Club – a check-in/out for VHS tapes and CDs. Thus began my fascination with computers.”</p>\n\n\n\n<p>Seven years later, she went on to university to study for a Bachelors in Business Management and Information Technology. Her third year internship was at a local web design and hosting company. Though she had hoped her placement would be at a local bank or telecommunications company, the chance to discover website design turned out to be the best thing that could have happened.&nbsp;</p>\n\n\n\n<p>In 2017, Thelma went on to work for a company designing websites using HTML, CSS, PHP, JavaScript and Joomla. She had heard about WordPress but had not used it. She recalls: “People have this misconception that WordPress is not for real developers and it is not secure and at that time I was one of those people.”</p>\n\n\n\n<h2>Finding a local community</h2>\n\n\n\n<p>From a discussion with a member of the local WordPress community, <a href=\"https://heropress.com/essays/wordpress-opened-whole-new-world/\">Thabo Tswana</a>, about a striking swag gift from a WordCamp, Thelma’s interest was sparked.&nbsp;</p>\n\n\n\n<p>She started to find out more about WordPress and WooCommerce, and visited her local WordCamp Harare website. She was delighted to find that she could learn more about WordPress without needing any pre-existing knowledge, and wanted to be involved. So instead of just attending the camp, she volunteered too!&nbsp;</p>\n\n\n\n<p>Her response to her first WordPress event mirrors the experience of many others in the community. She said: “I only started using WordPress because of the awesome people that l had met at that WordCamp. Everyone was so welcoming.”</p>\n\n\n\n<p>A week later, with help from Thabo, she designed her first website using WordPress.</p>\n\n\n\n<p>She soon became more involved with the community and Meetups. Thelma participated in the first-ever ‘Women Who WordPress’ Meetup in 2018, with lots of women getting involved from bloggers to developers.&nbsp;</p>\n\n\n\n<p>She said: “We were free to talk and discuss a lot of things. We had more time to discuss the difference between WordPress.com and WordPress.org, we shared views on how to handle discrimination at work, how to promote your website and a whole lot of other things.”</p>\n\n\n\n<h2>Establishing roots in WordPress</h2>\n\n\n\n<p>In 2018, WordCamp Harare had its first-ever female Lead Organizer <a href=\"https://tapiwanashe.com/\">Tapiwanashe Manhobo</a>. Thelma was part of the organising team that year and was assigned to handle Harare’s first Kids Camp to take place eight months later. You can read more about her experiences of organizing a <a href=\"https://thelmachido.wordpress.com/2019/11/21/wordpress-juniours-first-edition/\"><strong>Kids Camp</strong></a> on her blog.</p>\n\n\n\n<p>She said: “After the first Kids Camp, we had several people in the local Zimbabwean WordPress community who were enthusiastic about encouraging young people to embrace ICT. In 2019, we had not planned to have a Kids Camp because of financial constraints but to our surprise, we had some anonymous donations and we managed to have a WordPress Community outreach to a youth centre, <a href=\"https://cttzim.org/\"><strong>Centre for Total Transformation</strong></a>, a week after our WordCamp. It is a non-formal school that caters for underprivileged and vulnerable children. The group were able to share practical skills about using WordPress, computer hardware and software.</p>\n\n\n\n<p>Thelma shares that she became hooked on WordPress because of its community. “I enjoy attending WordCamps, meeting new people and just learning new stuff. I have a huge list of WordCamps I would like to attend. Last year I managed to cross WordCamp Johannesburg off my list. When everything is back to normal my plan to travel to WordCamps will proceed (fingers crossed).”</p>\n\n\n\n<h2>Reaping the fruits of ongoing learning</h2>\n\n\n\n<p>Thelma is committed to ongoing development training. She said: “Even though I can still cook up code in C and Java, for now, I have also included WordPress PHP functions to the mix. It was not easy to get to this point, daring myself got me to this slightly better stage. I try to do my best where I can and I am happy to say it has paid off so far.”</p>\n\n\n\n<p>Thelma has continued her journey working in design and digital marketing last year with Trust Nhokovenzo who works in digital marketing and is active in&nbsp; the WordPress Community. He came across her name as a developer from talking with others involved in WordPress. She went to work with his team at a marketing agency.</p>\n\n\n\n<p>Her interest in the development of WordPress continued and she joined the <a href=\"https://wordpress.org/news/2020/12/simone/\">5.6 Release Squad</a> in the mid 2020.&nbsp;At the end of 2020, she moved to become a Happiness Engineer working with WordPress.com. Thelma’s fascination with the platform and the community continues to grow and her contributor story is ongoing.</p>\n\n\n\n<p>Find out more about the <a href=\"https://www.meetup.com/Harare-WordPress-Meetup\">Harare WordPress community</a> in Zimbabwe.</p>\n\n\n\n<h2>Contributors</h2>\n\n\n\n<p>Thanks to Nalini Thakor (<a href=\'https://profiles.wordpress.org/nalininonstopnewsuk/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>nalininonstopnewsuk</a>) and Surendra Thakor (<a href=\'https://profiles.wordpress.org/sthakor/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>sthakor</a>), Yvette Sonneveld (<a href=\'https://profiles.wordpress.org/yvettesonneveld/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>yvettesonneveld</a>), Abha Thakor (<a href=\'https://profiles.wordpress.org/webcommsat/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webcommsat</a>), Larissa Murillo (<a href=\'https://profiles.wordpress.org/lmurillom/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>lmurillom</a>), Meher Bala (<a href=\'https://profiles.wordpress.org/meher/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>meher</a>), Josepha Haden (<a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a>), and Chloé Bringmann (<a href=\'https://profiles.wordpress.org/cbringmann/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>cbringmann</a>). Thank you to Thelma Mutete (<a href=\'https://profiles.wordpress.org/thelmachido/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>thelmachido</a>) for sharing her #ContributorStory.</p>\n\n\n\n<figure class=\"wp-block-image\"><img src=\"https://lh4.googleusercontent.com/s24EVZGKbxVeafljPU1ubF1DjIwn98E3-wGx1LD2CWYk7zYQppFhXNpb0aUhGe01TStMdTwXrcYaxBZQHRgZJ10lvW2hsg61Ce37_pBGJuTRQlJ6r9iUxlJtvuDuwLhIvPo1MVEb\" alt=\"HeroPress logo\" /></figure>\n\n\n\n<p><em>This post is based on </em><a href=\"https://heropress.com/essays/hello-world-discovering-the-world-through-wordpress/\"><em>an article originally published on HeroPress.com</em></a><em>, a community initiative created by </em><a href=\"https://profiles.wordpress.org/topher1kenobe/\"><em>Topher DeRosia</em></a><em>. HeroPress highlights people in the WordPress community</em>.</p>\n\n\n\n<p>#ContributorStory #HeroPress</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9518\";s: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: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:37:\"The Month in WordPress: December 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2021/01/the-month-in-wordpress-december-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 10:55:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9508\";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:333:\"We bid goodbye to 2020 in style with the release of WordPress 5.6 and the launch of Learn WordPress. But these weren’t the only exciting updates from WordPress in December. Read on to learn more! WordPress 5.6 is here The latest major WordPress release, version 5.6 “Simone”, came out on December 8. The release ships [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"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:11612:\"\n<p>We bid goodbye to 2020 in style with the release of WordPress 5.6 and the launch of Learn WordPress. But these weren’t the only exciting updates from WordPress in December. Read on to learn more!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.6 is here</h2>\n\n\n\n<p>The latest major WordPress release,<a href=\"https://wordpress.org/news/2020/12/simone/\"> version 5.6</a> “Simone”, came out on December 8. The release ships with a new default theme called <a href=\"https://wordpress.org/themes/twentytwentyone/\">Twenty Twenty One</a>. It offers a host of features, including:</p>\n\n\n\n<ul><li>Greater layout flexibility</li><li>More block patterns</li><li>Video captioning support</li><li>Auto-updates</li><li>Beta-compatibility for PHP 8.0</li><li>Application password support for the REST API</li><li>Updates to jQuery</li></ul>\n\n\n\n<p>In addition, WordPress 5.6 is now available in 55 languages. You can find more information about the release in the <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">field guide</a>, and you can update to the latest version directly from your WordPress dashboard or by <a href=\"https://wordpress.org/download/\">downloading</a> it directly from WordPress.org. A total of 605 people hailing from 57 different countries contributed to the development of WordPress 5.6. <a href=\'https://profiles.wordpress.org/audrasjb/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>audrasjb</a> has <a href=\"https://jeanbaptisteaudras.com/en/2020/12/wordpress-5-6-core-stats-contributions-by-country-company/\">compiled many more stats like that</a>, showing what a tremendous group effort this was—they’re well worth a read!</p>\n\n\n\n<p>Want to contribute to upcoming WordPress releases? Join the WordPress <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel on the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a> and follow the <a href=\"https://make.wordpress.org/core/\">Core team blog</a> to learn the <a href=\"https://make.wordpress.org/core/2020/12/21/wordpress-5-7-planning-roundup/\">latest on WordPress 5.7</a>, which is <a href=\"https://wordpress.org/about/roadmap/\">slated to be out by March 9, 2021</a>. The Core team hosts weekly chats on Wednesdays at <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=5&amp;min=00&amp;sec=0\">5 a.m.</a> and <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=20&amp;min=00&amp;sec=0\">8 p.m.</a> UTC.</p>\n\n\n\n<h2>Watch the State of the Word 2020 recording</h2>\n\n\n\n<p><a href=\"https://wordpress.org/news/\">State of the Word 2020</a>, the annual keynote address delivered by WordPress co-founder Matt Mullenweg, was streamed online for the first time on December 17. It was followed by a live Q&amp;A from community members all across the world. You can find the stream recording on <a href=\"https://www.youtube.com/watch?v=QI3qCoiuG3w\">YouTube</a>, <a href=\"https://www.facebook.com/WordPress/videos/1281447442248369\">Facebook</a>, and <a href=\"https://twitter.com/i/broadcasts/1dRKZNvnrmdKB\">Twitter</a>. The <a href=\"https://wordpress.tv/2020/12/17/matt-mullenweg-2020-state-of-the-word/\">State of the Word</a> video and the <a href=\"https://wordpress.tv/2020/12/17/matt-mullenweg-2020-state-of-the-word-qa/\">Q&amp;A session</a> are also available on WordPress.tv.&nbsp;</p>\n\n\n\n<h2>Learn WordPress has launched</h2>\n\n\n\n<p>Learn WordPress, a new free, on-demand WordPress learning resource, launched officially on December 15. It offers <a href=\"https://learn.wordpress.org/workshops/\">workshops</a>, <a href=\"https://learn.wordpress.org/lesson-plans/\">lesson plans</a>, quizzes, and <a href=\"https://learn.wordpress.org/courses/\">courses</a> for anyone interested in publishing with, building for, or contributing to WordPress. WordPress enthusiasts can also <a href=\"https://www.meetup.com/learn-wordpress-discussions/\">participate in discussion groups</a> focused on specific topics to learn with and from each other.</p>\n\n\n\n<p>Want to participate in Learn WordPress? <a href=\"https://learn.wordpress.org/contribute/\">Here are four ways you can do so</a>! Additionally, contributors have <a href=\"https://make.wordpress.org/training/2020/12/03/learn-wordpress-blue-sky-thinking/\">launched a discussion</a> on the future of <a href=\"https://learn.wordpress.org/\">Learn WordPress</a>—feel free to share your thoughts in the comments. To help promote Learn WordPress, check out the <a href=\"https://make.wordpress.org/marketing/\">Marketing Team</a>’s <a href=\"https://make.wordpress.org/marketing/2020/12/09/help-us-promote-learn-wordpress/\">materials</a>, which detail a <a href=\"https://make.wordpress.org/marketing/2020/12/09/help-us-promote-learn-wordpress/\">range of fun and creative ways</a> to share this new resource.</p>\n\n\n\n<h2>Give feedback on the Full Site Editing project</h2>\n\n\n\n<p>Contributor teams have kicked off the <a href=\"https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/\">Full Site Editing (FSE) outreach program</a> for anyone who is building or maintaining a WordPress site so that they can give feedback on the upcoming <a href=\"https://make.wordpress.org/design/handbook/focuses/full-site-editing/\">FSE feature</a> that will be part of Gutenberg Phase 2. Your feedback will go a long way in improving FSE user flows. To participate, <a href=\"https://make.wordpress.org/test/2020/12/23/fse-program-testing-call-1-template-editing/\">check out the initial testing call</a> on the <a href=\"https://make.wordpress.org/test/\">Make/Test blog</a> and join the <a href=\"https://make.wordpress.org/core/tag/fse-outreach-experiment/\">#fse-outreach-experiment</a> Slack channel.<br><br>Want to follow updates on the FSE project? Check out <a href=\"https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/\">this blog post</a>. You can find <a href=\"https://make.wordpress.org/core/2020/12/10/status-check-site-editing-and-customization/\">2020 updates to the FSE project</a> in the Make/Core blog.</p>\n\n\n\n<h2>BuddyPress 7.0 “Filippi” and 7.10 are now available</h2>\n\n\n\n<p><a href=\"https://buddypress.org/2020/12/buddypress-7-0-0-filippi/\">BuddyPress version 7.0</a> went live on December 9. Its features include:&nbsp;</p>\n\n\n\n<ul><li>New administration screens to manage Member and Group Types</li><li>New BP blocks for posts and pages</li><li>A default profile image for network sites</li><li>Improved BuddyPress Noveau support for the Twenty Twenty One theme.&nbsp;</li></ul>\n\n\n\n<p>A BuddyPress maintenance release (<a href=\"https://buddypress.org/2020/12/buddypress-7-1-0-maintenance-release/\">version 7.1</a>) launched on December 21.&nbsp;</p>\n\n\n\n<p>Want to provide feedback or suggestions for BuddyPress? Share your comments on the announcement posts for <a href=\"https://buddypress.org/2020/12/buddypress-7-0-0-filippi/\">7.0</a> or <a href=\"https://buddypress.org/2020/12/buddypress-7-1-0-maintenance-release/\">7.1</a>. If you find a bug, please report it in the <a href=\"https://buddypress.org/support/\">support forums</a>.&nbsp;</p>\n\n\n\n<h2>Gutenberg 9.5 and 9.6 released</h2>\n\n\n\n<p>The Core team launched <a href=\"https://make.wordpress.org/core/2020/12/02/whats-new-in-gutenberg-2-december/\">version 9.5</a> and <a href=\"https://make.wordpress.org/core/2020/12/23/whats-new-in-gutenberg-23-december/\">9.6</a> of Gutenberg last month. Both versions include several improvements to FSE flows, bug fixes, and feature upgrades. Version 9.5 introduces features like full height alignment and support for font sizes in the code block. Version 9.6 includes features like the ability to drag blocks from the inserter and a vertical layout for buttons.&nbsp;</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading</h2>\n\n\n\n<ul><li>The Community team <a href=\"https://make.wordpress.org/community/2020/12/01/discussion-how-can-the-wordpress-community-return-to-hosting-safe-in-person-events/\">kicked off a discussion</a> about what the WordPress Community can do to host safe, in-person events again, in light of the continuing pandemic. </li><li>The Polyglots team published its <a href=\"https://make.wordpress.org/polyglots/2020/12/30/polyglots-team-end-of-year-post-2020/\">end-of-year post</a>, along with the <a href=\"https://make.wordpress.org/polyglots/author/evarlese/\">results of its 2020 translator survey</a>.</li><li><a href=\"https://sevilla.wordcamp.org/2020/\">WordCamp Sevilla 2020</a> was held online from December 26-29. You can catch the recorded livestream playback on <a href=\"https://www.youtube.com/c/wordpresssevilla/live\">YouTube</a>. Videos of the event will <a href=\"https://wordpress.tv/event/wordcamp-sevilla-2020/\">soon be available on WordPress.tv</a>.</li><li>WordPress project executive director <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a> and project co-founder <a href=\"https://profiles.wordpress.org/matt/\">Matt Mullenweg</a> will be jointly hosting <a href=\"https://make.wordpress.org/core/2020/12/15/regular-office-and-listening-hours/\">quarterly office and listening hours</a> in 2021. Sign-ups for the <a href=\"https://make.wordpress.org/core/2020/12/15/regular-office-and-listening-hours/\">first ones in January 2021</a> are almost filled up.</li><li>The Core team <a href=\"https://make.wordpress.org/core/2020/12/02/wp-notify-project-review/\">published updates</a> on the <a href=\"https://make.wordpress.org/core/tag/feature-notifications/\">WP Notify project</a>, which seeks to <a href=\"https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/\">improve the notifications system</a> in WordPress Core.</li><li>The Support team <a href=\"https://make.wordpress.org/support/2020/12/handling-potential-jquery-issues-in-wordpress-5-6/\">published a post</a> detailing jQuery issues in WordPress 5.6.</li><li><a href=\"https://india.wordcamp.org/2021/\">WordCamp India Online 2021</a> will be held over three weekends between January 30 and February 14. There will be workshops, a contributor event, and sessions (in that order). The calls for <a href=\"https://india.wordcamp.org/2021/call-for-sponsors/\">sponsors</a>, <a href=\"https://india.wordcamp.org/2021/call-for-workshops/\">workshop presenters</a>, <a href=\"https://india.wordcamp.org/2021/call-for-contributor-team-leads/\">contributor team leads</a>, and <a href=\"https://india.wordcamp.org/2021/call-for-volunteers/\">volunteers</a> are now open. Don’t forget to grab your <a href=\"https://india.wordcamp.org/2021/tickets/\">free tickets</a>!</li><li>The Documentation team <a href=\"https://make.wordpress.org/docs/2020/12/01/external-linking-policy-1st-review-of-plugin-developer-handbook/\">shared a first review</a> of its <a href=\"https://make.wordpress.org/docs/tag/external-linking-policy/\">external linking policy</a>. It is using the <a href=\"https://developer.wordpress.org/plugins/\">plugin developer handbook</a> as a test.</li></ul>\n\n\n\n<p><br><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it using this form</em></a><em>.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9508\";s: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: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:27:\"Introducing Learn 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:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://wordpress.org/news/2020/12/introducing-learn-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:\"Tue, 15 Dec 2020 13: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:3:{i:0;a:5:{s:4:\"data\";s:7:\"Updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:14:\"learnwordpress\";s: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:7:\"learnwp\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9444\";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:133:\"Learn WordPress is a learning resource providing workshops, quizzes, courses, and lesson plans to help you to do more with WordPress.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:10336:\"\n<p><strong><a href=\"https://learn.wordpress.org/\">Learn WordPress</a> is a learning resource providing workshops, quizzes, courses, lesson plans, and discussion groups so that anyone, from beginners to advanced users, can learn to do more with WordPress. Learning how to use, build for, and contribute to WordPress is essential for anyone wanting to dive deeper into the software and its community.&nbsp;</strong></p>\n\n\n\n<div class=\"wp-block-buttons aligncenter\">\n<div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"https://learn.wordpress.org/\">Learn WordPress</a></div>\n</div>\n\n\n\n<p>This cross-team initiative is part of the WordPress.org network and features content from contributors from the global community. It will be updated weekly and will help connect new and existing WordPress users with the broader community while they learn.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"331\" src=\"https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?resize=632%2C331&#038;ssl=1\" alt=\"\" class=\"wp-image-9457\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?resize=1024%2C537&amp;ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?resize=300%2C157&amp;ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?resize=768%2C403&amp;ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?resize=1536%2C806&amp;ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?w=1700&amp;ssl=1 1700w, https://i1.wp.com/wordpress.org/news/files/2020/12/learn-link-preview.png?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h2>What can you learn about WordPress?</h2>\n\n\n\n<p>On Learn WordPress you can find a range of material and opportunities to use at the time which works for you.</p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/workshops/\"><strong>Workshops</strong></a> are practical, skills-based videos that show viewers how to do new things with WordPress, whether you publish, manage, develop with, or contribute to WordPress. Most workshops include quizzes for you to test your newly gained knowledge.</p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/discussion-groups/\"><strong>Discussion groups</strong></a> provide an opportunity for further collaborative learning with participants meeting together to discuss the workshop content &#8211; they take place online, either in video calls or Slack and accommodate all time zones.</p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/lesson-plans/\"><strong>Lesson plans</strong></a> are guides for facilitators to use while presenting at events or within educational environments. Facilitators will find learning objectives (telling people what they are going to learn), any prerequisite skills, assets such as screenshots and slide decks, and learning assessments.&nbsp;</p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/courses/\"><strong>Courses</strong></a> are a series of interconnected lesson plans to be presented by a facilitator that will strategically focus on defined learning outcomes. Participants can go through these courses individually or as part of a group. After completing the learning, attendees should be able to apply their skills in the real world.</p>\n\n\n\n<p>In addition to the wealth of valuable content available on Learn WordPress, the platform provides an opportunity for individuals to learn alongside other community members and become connected with a global network of WordPress users, developers, and contributors.</p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe class=\'youtube-player\' width=\'632\' height=\'356\' src=\'https://www.youtube.com/embed?version=3&#038;rel=1&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;fs=1&#038;hl=en-US&#038;autohide=2&#038;wmode=transparent&#038;listType=playlist&#038;list=PLCVEqsAbLffeEXhn9T1yBVTMaHIMtlzFj\' allowfullscreen=\'true\' style=\'border:0;\' sandbox=\'allow-scripts allow-same-origin allow-popups allow-presentation\'></iframe>\n</div></figure>\n\n\n\n<p><a href=\"https://www.youtube.com/playlist?list=PLCVEqsAbLffeEXhn9T1yBVTMaHIMtlzFj\">Why you should use Learn WordPress</a> &#8211; videos from our community.</p>\n\n\n\n<h2>How can you get involved?</h2>\n\n\n\n<div class=\"wp-block-buttons aligncenter\">\n<div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"https://learn.wordpress.org/\">Start learning today!</a></div>\n</div>\n\n\n\n<p>Learn WordPress is an open-source platform available for anyone to contribute content in any areas mentioned above. <a href=\"https://learn.wordpress.org/contribute/\">Find out more about how you can get involved</a> with this initiative.</p>\n\n\n\n<p><a href=\"https://make.wordpress.org/marketing/2020/12/09/help-us-promote-learn-wordpress/\">Take part in our fun promotion campaigns</a> on social and with your local community.</p>\n\n\n\n<p><em>Hundreds of people spanning a number of years have contributed to the development of learning materials. Thanks to everyone who worked so hard to make Learn WordPress a reality.&nbsp;</em></p>\n\n\n\n<p><strong><em>Particular thanks to</em></strong>:</p>\n\n\n\n<p><strong><em>Training:</em></strong><em> <a href=\'https://profiles.wordpress.org/courane01/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>courane01</a>, <a href=\'https://profiles.wordpress.org/azhiyadev/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>azhiyadev</a>, <a href=\'https://profiles.wordpress.org/geheren/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>geheren</a>, <a href=\'https://profiles.wordpress.org/webtechpooja/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webtechpooja</a>, <a href=\'https://profiles.wordpress.org/jessecowens/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jessecowens</a>, <a href=\'https://profiles.wordpress.org/onealtr/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>onealtr</a>, <a href=\'https://profiles.wordpress.org/rastaban/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>rastaban</a>, <a href=\'https://profiles.wordpress.org/evarlese/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>evarlese</a>, <a href=\'https://profiles.wordpress.org/manzwebdesigns/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>manzwebdesigns</a></em><br><strong><em>Meta: </em></strong><em><a href=\'https://profiles.wordpress.org/coreymckrill/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>coreymckrill</a>, <a href=\'https://profiles.wordpress.org/dufresnesteven/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>dufresnesteven</a>, <em><a href=\'https://profiles.wordpress.org/jonoaldersonwp/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>jonoaldersonwp</a></em></em><br><strong><em>Community:</em></strong><em> <a href=\'https://profiles.wordpress.org/hlashbrooke/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>hlashbrooke</a>, <a href=\'https://profiles.wordpress.org/camikaos/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>camikaos</a>, <a href=\'https://profiles.wordpress.org/harishanker/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>harishanker</a>, <a href=\'https://profiles.wordpress.org/angelasjin/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>angelasjin</a>, <a href=\'https://profiles.wordpress.org/nao/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>nao</a>, <a href=\'https://profiles.wordpress.org/courtneypk/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>courtneypk</a>, <a href=\'https://profiles.wordpress.org/andreamiddleton/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>andreamiddleton</a>, <a href=\'https://profiles.wordpress.org/rmarks/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>rmarks</a>, <a href=\'https://profiles.wordpress.org/sippis/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>sippis</a></em><br><strong><em>Marketing: </em></strong><em><a href=\'https://profiles.wordpress.org/webcommsat/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webcommsat</a>,  <a href=\'https://profiles.wordpress.org/oglekler/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>oglekler</a>, <a href=\'https://profiles.wordpress.org/lmurillom/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>lmurillom</a>, <a href=\'https://profiles.wordpress.org/yvettesonneveld/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>yvettesonneveld</a>, <a href=\'https://profiles.wordpress.org/meher/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>meher</a>, <a href=\'https://profiles.wordpress.org/nalininonstopnewsuk/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>nalininonstopnewsuk</a>, <a href=\'https://profiles.wordpress.org/megphillips91/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>megphillips91</a>, <a href=\'https://profiles.wordpress.org/marks99/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>marks99</a>, <em><a href=\'https://profiles.wordpress.org/marybaum/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>marybaum</a></em></em>, <em><a href=\'https://profiles.wordpress.org/antialiasfactory/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>antialiasfactory</a>, <a href=\'https://profiles.wordpress.org/herculespekkas/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>herculespekkas</a>, <a href=\'https://profiles.wordpress.org/chaion07/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chaion07</a></em><br><strong><em>Design:</em></strong><em> <a href=\'https://profiles.wordpress.org/melchoyce/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>melchoyce</a> </em></p>\n\n\n\n<p><em>For a fuller list of the contributors who have been involved in training and Learn WordPress, visit <a href=\"https://make.wordpress.org/community/2020/08/12/learn-wordpress-is-live/\">the initial beta launch post</a>. Thanks to everyone who has been involved to date and will be in the future.&nbsp;</em></p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/tag/learnwordpress\">#LearnWordPress</a> <a href=\"https://learn.wordpress.org/tag/learnwp\">#LearnWP</a></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9444\";s: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:26:\"WordPress 5.6 “Simone”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://wordpress.org/news/2020/12/simone/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 08 Dec 2020 19:46: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:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9325\";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:206:\"Meet Simone, our latest and greatest WordPress release. Named for the legendary performer Nina Simone. Fire up a playlist with her best work and read on to discover what WordPress 5.6 has in store for 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: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:63934:\"\n<p>Meet Simone, our latest and greatest WordPress release. Named for the legendary performer Nina Simone, who is known for tunes like &#8220;Feeling Good&#8221;, &#8220;Young, Gifted and Black&#8221;, and &#8220;Four Women&#8221;. Fire up a playlist with her best work and read on to discover what we have in store for you. </p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"633\" src=\"https://i2.wp.com/wordpress.org/news/files/2020/12/wordpress-5-6_cover-a11y.jpg?resize=632%2C633&#038;ssl=1\" alt=\"WordPress 5.6 Simone with a photo of Nina Simone\" class=\"wp-image-9416\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2020/12/wordpress-5-6_cover-a11y.jpg?resize=1022%2C1024&amp;ssl=1 1022w, https://i2.wp.com/wordpress.org/news/files/2020/12/wordpress-5-6_cover-a11y.jpg?resize=300%2C300&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2020/12/wordpress-5-6_cover-a11y.jpg?resize=150%2C150&amp;ssl=1 150w, https://i2.wp.com/wordpress.org/news/files/2020/12/wordpress-5-6_cover-a11y.jpg?resize=768%2C769&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2020/12/wordpress-5-6_cover-a11y.jpg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<div class=\"wp-block-cover has-background-dim\" style=\"background-color:#d1e4dd;min-height:300px\"><div class=\"wp-block-cover__inner-container\">\n<p class=\"has-text-align-center has-black-color has-text-color has-background has-large-font-size\" style=\"background-color:#d1e4dd;padding: 10px\">Welcome to WordPress 5.6</p>\n<h3 class=\"has-text-align-center has-black-color has-text-color\">Sharing your stories has never been easier.</h3>\n</div></div>\n\n\n\n<p>WordPress 5.6 brings you countless ways to set your ideas free and bring them to life. With a brand-new default theme as your canvas, it supports an ever-growing collection of blocks as your brushes. Paint with words. Pictures. Sound. Or rich embedded media.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"234\" src=\"https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-1.jpeg?resize=632%2C234&#038;ssl=1\" alt=\"colored circles\" class=\"wp-image-9346\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-1.jpeg?resize=1024%2C379&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-1.jpeg?resize=300%2C111&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-1.jpeg?resize=768%2C284&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-1.jpeg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h3>Greater layout flexibility</h3>\n\n\n\n<p>Bring your stories to life with more tools that let you edit your layout with or without code. Single column blocks, designs using mixed widths and columns, full-width headers, and gradients in your cover block—make small changes or big statements with equal ease!</p>\n\n\n\n<h3>More block patterns</h3>\n\n\n\n<p>In some themes, preconfigured block patterns make setting up standard pages on your site a breeze. Let the power of patterns streamline your workflow and save you clicks. Plus, share these features with clients, editors, and more.</p>\n\n\n\n<h3>Better video captioning</h3>\n\n\n\n<p>To help you add subtitles or captions to your videos, you can now upload them within your post or page. This makes it easier than ever to make your videos accessible for anyone who needs or prefers to use subtitles.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"120\" src=\"https://i2.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-2.jpeg?resize=632%2C120&#038;ssl=1\" alt=\"black vertical line\" class=\"wp-image-9347\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-2.jpeg?resize=1024%2C194&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-2.jpeg?resize=300%2C57&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-2.jpeg?resize=768%2C146&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-2.jpeg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h2>Twenty Twenty-One is here!</h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"714\" src=\"https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?resize=632%2C714&#038;ssl=1\" alt=\"Examples of block patterns available in Twenty Twenty-One.\" class=\"wp-image-9426\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?resize=907%2C1024&amp;ssl=1 907w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?resize=266%2C300&amp;ssl=1 266w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?resize=768%2C867&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?resize=1360%2C1536&amp;ssl=1 1360w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?resize=1814%2C2048&amp;ssl=1 1814w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?w=1975&amp;ssl=1 1975w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?w=1264&amp;ssl=1 1264w, https://i0.wp.com/wordpress.org/news/files/2020/12/TT1-Screenshots-Compressed.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure>\n\n\n\n<p>Twenty Twenty-One is a blank canvas for your ideas, and the block editor is the best brush. It is built for the block editor and packed with brand-new block patterns you can only get in the default themes. Try different layouts in a matter of seconds, and let the theme’s eye-catching, yet timeless design make your work shine.&nbsp;</p>\n\n\n\n<p>What’s more, this default theme puts accessibility at the heart of your website. It conforms to the <a href=\"https://make.wordpress.org/themes/handbook/review/accessibility/\">WordPress accessibility-ready guidelines</a> and addresses several more specialized standards from the <a href=\"https://www.w3.org/WAI/WCAG2AAA-Conformance\">Web Content Accessibility Guidelines (WCAG) 2.1 at level AAA</a>. It will help you meet the highest level of international accessibility standards when you create accessible content and choose plugins which are accessible too!</p>\n\n\n\n<h3>A rainbow of soft pastels</h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?ssl=1\"><img loading=\"lazy\" width=\"632\" height=\"167\" src=\"https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?resize=632%2C167&#038;ssl=1\" alt=\"A mobile screenshot of each included color palette in Twenty Twenty-One, going in ROYGBIV order.\" class=\"wp-image-9424\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?resize=1024%2C270&amp;ssl=1 1024w, https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?resize=300%2C79&amp;ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?resize=768%2C202&amp;ssl=1 768w, https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?resize=1536%2C405&amp;ssl=1 1536w, https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?resize=2048%2C540&amp;ssl=1 2048w, https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?w=1264&amp;ssl=1 1264w, https://i2.wp.com/wordpress.org/news/files/2020/12/Rainbow-Compressed.png?w=1896&amp;ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></a></figure>\n\n\n\n<p>Perfect for a new year, Twenty Twenty-One gives you a range of pre-selected color palettes in pastel, all of which conform to AAA standards for contrast. You can also choose your own background color for the theme, and the theme chooses accessibility-conscious text colors for you — automatically!</p>\n\n\n\n<p>Need more flexibility than that? You can also choose your own color palette from the color picker.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"151\" src=\"https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-3.jpeg?resize=632%2C151&#038;ssl=1\" alt=\"colored circles\" class=\"wp-image-9351\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-3.jpeg?resize=1024%2C245&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-3.jpeg?resize=300%2C72&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-3.jpeg?resize=768%2C183&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress5-6-3.jpeg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h2>Improvements for everyone</h2>\n\n\n\n<h3>Expanding auto-updates</h3>\n\n\n\n<p>For years, only developers have been able to update WordPress automatically. But now you have that option, right in your dashboard. If this is your first site, you have auto-updates ready to go, right now! Upgrading an existing site? No problem! Everything is the same as it was before.</p>\n\n\n\n<h3>Accessibility Statement&nbsp;</h3>\n\n\n\n<p>Even if you’re not an expert, you can start letting others know about your site’s commitment to accessibility! The new <a href=\"https://github.com/10degrees/accessibility-statement-plugin\">feature plugin</a> includes template copy for you to edit and publish, and it’s written to support different contexts and jurisdictions.&nbsp;&nbsp;</p>\n\n\n\n<h3>Built-in Patterns</h3>\n\n\n\n<p>If you’ve not had the chance to play with block patterns yet, all default themes now feature a range of block patterns that let you master complex layouts with minimal effort. Customize the patterns to your liking with the copy, images, and colors that fit your story or brand.&nbsp;</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" width=\"632\" height=\"185\" src=\"https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress-5-6-4.jpeg?resize=632%2C185&#038;ssl=1\" alt=\"colored and textured rectangles\" class=\"wp-image-9352\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress-5-6-4.jpeg?resize=1024%2C300&amp;ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress-5-6-4.jpeg?resize=300%2C88&amp;ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress-5-6-4.jpeg?resize=768%2C225&amp;ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2020/12/WordPress-5-6-4.jpeg?w=1264&amp;ssl=1 1264w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h2>For developers</h2>\n\n\n\n<h3>REST API authentication with Application Passwords</h3>\n\n\n\n<p>Thanks to the API’s new Application Passwords authorization feature, third-party apps can connect to your site seamlessly and securely. This new REST API feature lets you see what apps are connecting to your site and control what they do.&nbsp;</p>\n\n\n\n<h3>More PHP 8 support</h3>\n\n\n\n<p>5.6 marks the first steps toward WordPress Core support for PHP 8. Now is a great time to start planning how your WordPress products, services, and sites can support the latest PHP version. For more information about what to expect next, <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\">read the PHP 8 developer note</a>.</p>\n\n\n\n<h3>jQuery</h3>\n\n\n\n<p>Updates to jQuery in WordPress take place across three releases 5.5, 5.6, and 5.7. As we reach the mid-point of this process, <a href=\"https://wordpress.org/plugins/wp-jquery-update-test/\">run the update test plugin to check your sites for errors</a> ahead of time.&nbsp;&nbsp;&nbsp;&nbsp;</p>\n\n\n\n<p>If you find issues with the way your site looks ( e.g. a slider doesn’t work, a button is stuck — that sort of thing), install <a href=\"https://wordpress.org/plugins/enable-jquery-migrate-helper/\">the jQuery Migrate plugin</a>.</p>\n\n\n\n<h3>Check out the Field Guide</h3>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">Read about the latest version of WordPress in this guide.</a> It highlights developer notes for each change in the release.&nbsp;</p>\n\n\n\n<div class=\"wp-block-cover has-background-dim\" style=\"background-color:#d1e4dd;min-height:300px\"><div class=\"wp-block-cover__inner-container\">\n<p class=\"has-text-align-center has-black-color has-text-color has-background has-large-font-size\" style=\"background-color:#d1e4dd;padding: 10px\">“It’s a new day, it’s a new life for me&#8230;.and I’m feeling good.”</p>\n<h3 class=\"has-text-align-center has-black-color has-text-color\">~Nina Simone</h3>\n</div></div>\n\n\n\n<h2>The Squad</h2>\n\n\n\n<p>The WordPress 5.6 release comes to you from an all-women and non-binary identifying release squad:  </p>\n\n\n\n<ul><li><strong>Release Lead:</strong> Josepha Haden (<a href=\"https://profiles.wordpress.org/chanthaboune/\">@chanthaboune</a>).&nbsp; Cohort: Chloé Bringmann (<a href=\"https://profiles.wordpress.org/cbringmann/\">@cbringmann</a>) and Angela Jin (<a href=\"https://profiles.wordpress.org/angelasjin/\">@angelasjin</a>).</li><li><strong>Release Coordinator:</strong> Dee Teal (<a href=\"https://profiles.wordpress.org/thewebprincess/\">@thewebprincess</a>).&nbsp; Cohort: Thelma Mutete (<a href=\"https://profiles.wordpress.org/thelmachido/\">@thelmachido</a>) and Laura Nelson (<a href=\"https://profiles.wordpress.org/laurora/\">@laurora</a>).</li><li><strong>Triage Lead:</strong> Tonya Mork (<a href=\"https://profiles.wordpress.org/hellofromtonya/\">@hellofromtonya</a>).&nbsp;</li><li><strong>Core Tech Lead:</strong> Helen Hou-Sandì (<a href=\"https://profiles.wordpress.org/helen/\">@helen</a>).&nbsp; Cohort: Amy Kamala (<a href=\"https://profiles.wordpress.org/amykamala/\">@amykamala</a>) and Ebonie Butler (<a href=\"https://profiles.wordpress.org/metalandcoffee/\">@metalandcoffee</a>).</li><li><strong>Editor Tech Lead:</strong> Isabel Brison (<a href=\"https://profiles.wordpress.org/isabel_brison/\">@isabel_brison</a>).&nbsp; Cohort: Chandrika Guntur (<a href=\"https://profiles.wordpress.org/cguntur/\">@cguntur</a>), Anchen le Roux (<a href=\"https://profiles.wordpress.org/anchenlr/\">@anchenlr</a>), and Rebecca Hum (<a href=\"https://profiles.wordpress.org/rebasaurus/\">@rebasaurus</a>).</li><li><strong>Design Leads:</strong> Ellen Bauer (<a href=\"https://profiles.wordpress.org/elmastudio/\">@elmastudio</a>) and Tammie Lister (<a href=\"https://profiles.wordpress.org/karmatosed/\">@karmatosed</a>).&nbsp; Cohort: Anyssa Ferreira (<a href=\"https://profiles.wordpress.org/anyssa/\">@anyssa</a>), Estela Rueda (<a href=\"https://profiles.wordpress.org/estelaris/\">@estelaris</a>), Tracy Apps (<a href=\"https://profiles.wordpress.org/tray/\">@tray</a>), and Sophia DeRosia (<a href=\"https://profiles.wordpress.org/eringoblog/\">@eringoblog</a>).</li><li><strong>Design Tech Lead:</strong> Shital Marakana (<a href=\"https://profiles.wordpress.org/shital-patel/\">@shital-patel</a>).</li><li><strong>Accessibility Lead:</strong> Sarah Ricker (<a href=\"https://profiles.wordpress.org/sarahricker/\">@sarahricke<strong>r</strong></a>).&nbsp;Cohort: Hauwa Abashiya (<a href=\"https://profiles.wordpress.org/azhiyadev/\">@azhiyadev</a>).</li><li><strong>Marketing &amp; Communications Leads:</strong> Abha Thakor (<a href=\"https://profiles.wordpress.org/webcommsat/\">@webcommsat</a>) and Yvette Sonneveld (<a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld</a>).&nbsp;Cohort: Nalini Thakor (<a href=\"https://profiles.wordpress.org/nalininonstopnewsuk/\">@nalininonstopnewsuk</a>), Meher Bala (<a href=\"https://profiles.wordpress.org/meher/\">@meher</a>), Olga Gleckler (<a href=\"https://profiles.wordpress.org/oglekler/\">@ogleckler</a>), Larissa Murrillo (<a href=\"https://profiles.wordpress.org/lmurillom/\">@lmurillom</a>), Michelle Frechette (<a href=\"https://profiles.wordpress.org/michelleames/\">@michelleames</a>), Breann McDede (<a href=\"https://profiles.wordpress.org/bmcdede/\">@bmcdede</a>), and Afshana Diya (<a href=\"https://profiles.wordpress.org/afshanadiya/\">@afshanadiya</a>).</li><li><strong>Documentation Lead: </strong>Shawntelle Coker (<a href=\"https://profiles.wordpress.org/sncoker/\">@sncoker</a>). Cohort: Daisy Olsen (<a href=\"https://profiles.wordpress.org/daisyo/\">@DaisyO</a>), Meher Bala (<a href=\"https://profiles.wordpress.org/meher/\">@meher</a>), Winstina Hughes (<a href=\"https://profiles.wordpress.org/planningwrite/\">@planningwrite</a>).</li><li><strong>Documentation Review Lead:</strong> Michele Butcher-Jones (<a href=\"https://profiles.wordpress.org/m_butcher/\">@m_butcher</a>).&nbsp; Cohort: Nidhi Jain (<a href=\"https://profiles.wordpress.org/jainnidhi/\">@jainnidhi</a>), Laura Byrne Cristiano (<a href=\"https://wordpress.org/support/users/newyorkerlaura/\">@newyorkerlaura</a>).</li><li><strong>Default Theme Design Lead:</strong> Mel Choyce-Dwan (<a href=\"https://profiles.wordpress.org/melchoyce/\">@melchoyce</a>).&nbsp; Cohort: Ellen Bauer (<a href=\"https://profiles.wordpress.org/elmastudio/\">@elmastudio</a>).</li><li><strong>Default Theme Development Lead:</strong> Carolina Nymark (<a href=\"https://profiles.wordpress.org/poena/\">@poena</a>).&nbsp; Cohort: Kelly Choyce-Dwan (<a href=\"https://profiles.wordpress.org/ryelle/\">@ryelle</a>) and Jessica Lyschik (<a href=\"https://profiles.wordpress.org/luminuu/\">@luminuu</a>).</li><li><strong>Default Theme Wrangler:</strong> Jessica Lyschik (<a href=\"https://profiles.wordpress.org/luminuu/\">@luminuu</a>).</li><li><strong>Test Lead:</strong> Monika Rao (<a href=\"https://profiles.wordpress.org/monikarao/\">@monikarao</a>).&nbsp; Cohort: Allie Nimmons (<a href=\"https://profiles.wordpress.org/alliennimmons/\">@alliennimmons</a>).</li><li><strong>Support Lead:</strong> Bet Hannon (<a href=\"https://profiles.wordpress.org/bethannon1/\">@bethannon1</a>).</li></ul>\n\n\n\n<p>As always, this release reflects the hard work of 605 generous volunteer contributors. They collaborated on nearly 350 tickets on Trac and over 1,000 pull requests on GitHub.</p>\n\n\n\n<a href=\"https://profiles.wordpress.org/zgrkaralar/\">&#214;zg&#252;r KARALAR</a>, <a href=\"https://profiles.wordpress.org/1naveengiri/\">1naveengiri</a>, <a href=\"https://profiles.wordpress.org/a5hleyrich/\">A5hleyRich</a>, <a href=\"https://profiles.wordpress.org/aaroncampbell/\">Aaron D. Campbell</a>, <a href=\"https://profiles.wordpress.org/jorbin/\">Aaron Jorbin</a>, <a href=\"https://profiles.wordpress.org/aaronrobertshaw/\">aaronrobertshaw</a>, <a href=\"https://profiles.wordpress.org/abderrahman/\">abderrahman</a>, <a href=\"https://profiles.wordpress.org/webcommsat/\">Abha Thakor</a>, <a href=\"https://profiles.wordpress.org/abhijitrakas/\">Abhijit Rakas</a>, <a href=\"https://profiles.wordpress.org/pokhriyal/\">Abhishek Pokhriyal</a>, <a href=\"https://profiles.wordpress.org/acosmin/\">acosmin</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\">Adam Silverstein</a>, <a href=\"https://profiles.wordpress.org/zieladam/\">Adam Zielinski</a>, <a href=\"https://profiles.wordpress.org/addiestavlo/\">Addie</a>, <a href=\"https://profiles.wordpress.org/adriandegrafreak/\">Adri&#225;n de Grafreak</a>, <a href=\"https://profiles.wordpress.org/adriantirusli/\">Adrianti Rusli</a>, <a href=\"https://profiles.wordpress.org/afshanadiya/\">Afshana Diya</a>, <a href=\"https://profiles.wordpress.org/chaion07/\">Ahmed Chaion</a>, <a href=\"https://profiles.wordpress.org/elgameel/\">Ahmed Elgameel</a>, <a href=\"https://profiles.wordpress.org/ajensen/\">ajensen</a>, <a href=\"https://profiles.wordpress.org/ajitbohra/\">Ajit Bohra</a>, <a href=\"https://profiles.wordpress.org/atachibana/\">Akira Tachibana</a>, <a href=\"https://profiles.wordpress.org/aktasfatih/\">aktasfatih</a>, <a href=\"https://profiles.wordpress.org/aljullu/\">Albert Juh&#233; Lluveras</a>, <a href=\"https://profiles.wordpress.org/albertomake/\">albertomake</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/akirk/\">Alex Kirk</a>, <a href=\"https://profiles.wordpress.org/cawa-93/\">Alex Kozack</a>, <a href=\"https://profiles.wordpress.org/ajlende/\">Alex Lende</a>, <a href=\"https://profiles.wordpress.org/viper007bond/\">Alex Mills</a>, <a href=\"https://profiles.wordpress.org/alexstandiford/\">Alex Standiford</a>, <a href=\"https://profiles.wordpress.org/alexstine/\">alexstine</a>, <a href=\"https://profiles.wordpress.org/allancole/\">allancole</a>, <a href=\"https://profiles.wordpress.org/alliennimmons/\">Allie Nimmons</a>, <a href=\"https://profiles.wordpress.org/ambienthack/\">ambienthack</a>, <a href=\"https://profiles.wordpress.org/wpamitkumar/\">Amit Dudhat</a>, <a href=\"https://profiles.wordpress.org/amolv/\">Amol Vhankalas</a>, <a href=\"https://profiles.wordpress.org/amykamala/\">Amy Kamala</a>, <a href=\"https://profiles.wordpress.org/anandau14/\">Anand Upadhyay</a>, <a href=\"https://profiles.wordpress.org/anchenlr/\">Anchen le Roux</a>, <a href=\"https://profiles.wordpress.org/anlino/\">Anders Nor&#233;n</a>, <a href=\"https://profiles.wordpress.org/nosolosw/\">Andr&#233; Maneiro</a>, <a href=\"https://profiles.wordpress.org/afercia/\">Andrea Fercia</a>, <a href=\"https://profiles.wordpress.org/andreamiddleton/\">Andrea Middleton</a>, <a href=\"https://profiles.wordpress.org/baicusandrei/\">Andrei Baicus</a>, <a href=\"https://profiles.wordpress.org/andraganescu/\">Andrei Draganescu</a>, <a href=\"https://profiles.wordpress.org/aduth/\">Andrew Duthie</a>, <a href=\"https://profiles.wordpress.org/nacin/\">Andrew Nacin</a>, <a href=\"https://profiles.wordpress.org/azaozz/\">Andrew Ozz</a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey \"Rarst\" Savchenko</a>, <a href=\"https://profiles.wordpress.org/afragen/\">Andy Fragen</a>, <a href=\"https://profiles.wordpress.org/apeatling/\">Andy Peatling</a>, <a href=\"https://profiles.wordpress.org/andy/\">Andy Skelton</a>, <a href=\"https://profiles.wordpress.org/andystitt829/\">Andy Stitt</a>, <a href=\"https://profiles.wordpress.org/akissz/\">Angel Hess</a>, <a href=\"https://profiles.wordpress.org/angelasjin/\">Angela Jin</a>, <a href=\"https://profiles.wordpress.org/wpgurudev/\">Ankit Gade</a>, <a href=\"https://profiles.wordpress.org/ankitmaru/\">Ankit Panchal</a>, <a href=\"https://profiles.wordpress.org/annezazu/\">Anne McCarthy</a>, <a href=\"https://profiles.wordpress.org/antpb/\">Anthony Burchell</a>, <a href=\"https://profiles.wordpress.org/ahortin/\">Anthony Hortin</a>, <a href=\"https://profiles.wordpress.org/antonlukin/\">Anton Lukin</a>, <a href=\"https://profiles.wordpress.org/antonisme/\">Antonis Lilis</a>, <a href=\"https://profiles.wordpress.org/anuj2/\">anuj2</a>, <a href=\"https://profiles.wordpress.org/anyssa/\">Anyssa Ferreira</a>, <a href=\"https://profiles.wordpress.org/apedog/\">apedog</a>, <a href=\"https://profiles.wordpress.org/apermo/\">Apermo</a>, <a href=\"https://profiles.wordpress.org/archduck/\">archduck</a>, <a href=\"https://profiles.wordpress.org/archon810/\">archon810</a>, <a href=\"https://profiles.wordpress.org/aristath/\">Ari Stathopoulos</a>, <a href=\"https://profiles.wordpress.org/arippberger/\">arippberger</a>, <a href=\"https://profiles.wordpress.org/arjendejong/\">arjendejong</a>, <a href=\"https://profiles.wordpress.org/arnaudban/\">ArnaudBan</a>, <a href=\"https://profiles.wordpress.org/arpitgshah/\">Arpit G Shah</a>, <a href=\"https://profiles.wordpress.org/passoniate/\">Arslan Ahmed</a>, <a href=\"https://profiles.wordpress.org/akkspro/\">Arslan Ahmed Kalwar</a>, <a href=\"https://profiles.wordpress.org/asvinballoo/\">Asvin Balloo</a>, <a href=\"https://profiles.wordpress.org/tacitonic/\">Atharva Dhekne</a>, <a href=\"https://profiles.wordpress.org/austyfrosty/\">Austin Passy</a>, <a href=\"https://profiles.wordpress.org/austin880625/\">austin880625</a>, <a href=\"https://profiles.wordpress.org/avixansa/\">avixansa</a>, <a href=\"https://profiles.wordpress.org/ayesh/\">ayesh</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/backups/\">BackuPs</a>, <a href=\"https://profiles.wordpress.org/barry/\">Barry</a>, <a href=\"https://profiles.wordpress.org/bartczyz/\">Bart Czyz</a>, <a href=\"https://profiles.wordpress.org/bduclos/\">bduclos</a>, <a href=\"https://profiles.wordpress.org/beafialho/\">Beatriz Fialho</a>, <a href=\"https://profiles.wordpress.org/benmeredithgmailcom/\">Ben Meredith</a>, <a href=\"https://profiles.wordpress.org/kau-boy/\">Bernhard Kau</a>, <a href=\"https://profiles.wordpress.org/bernhard-reiter/\">Bernhard Reiter</a>, <a href=\"https://profiles.wordpress.org/bethannon1/\">Bet Hannon</a>, <a href=\"https://profiles.wordpress.org/bethsoderberg/\">Beth Soderberg</a>, <a href=\"https://profiles.wordpress.org/bgermann/\">bgermann</a>, <a href=\"https://profiles.wordpress.org/hareshlive/\">Bhagvan Mangukiya</a>, <a href=\"https://profiles.wordpress.org/bhautikvirani/\">bhautikvirani</a>, <a href=\"https://profiles.wordpress.org/bananastalktome/\">Billy S</a>, <a href=\"https://profiles.wordpress.org/birgire/\">Birgir Erlendsson (birgire)</a>, <a href=\"https://profiles.wordpress.org/bph/\">Birgit Pauli-Haack</a>, <a href=\"https://profiles.wordpress.org/bobbingwide/\">bobbingwide</a>, <a href=\"https://profiles.wordpress.org/boldgrid/\">BoldGrid</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/ibdz/\">Boy Witthaya</a>, <a href=\"https://profiles.wordpress.org/bradyvercher/\">Brady Vercher</a>, <a href=\"https://profiles.wordpress.org/kraftbj/\">Brandon Kraft</a>, <a href=\"https://profiles.wordpress.org/bpayton/\">Brandon Payton</a>, <a href=\"https://profiles.wordpress.org/bmcdede/\">Breann McDede</a>, <a href=\"https://profiles.wordpress.org/bmillersw/\">Brent Miller</a>, <a href=\"https://profiles.wordpress.org/brentswisher/\">Brent Swisher</a>, <a href=\"https://profiles.wordpress.org/brianhenryie/\">Brian Henry</a>, <a href=\"https://profiles.wordpress.org/brianhogg/\">Brian Hogg</a>, <a href=\"https://profiles.wordpress.org/bridgetwillard/\">Bridget Willard</a>, <a href=\"https://profiles.wordpress.org/brijeshb42/\">brijeshb42</a>, <a href=\"https://profiles.wordpress.org/burhandodhy/\">Burhan Nasir</a>, <a href=\"https://profiles.wordpress.org/icaleb/\">Caleb Burks</a>, <a href=\"https://profiles.wordpress.org/calin/\">Calin Don</a>, <a href=\"https://profiles.wordpress.org/cvoell/\">Cameron Voell</a>, <a href=\"https://profiles.wordpress.org/campusboy1987/\">campusboy</a>, <a href=\"https://profiles.wordpress.org/carike/\">Carike</a>, <a href=\"https://profiles.wordpress.org/poena/\">Carolina Nymark</a>, <a href=\"https://profiles.wordpress.org/carolinegeven/\">Caroline</a>, <a href=\"https://profiles.wordpress.org/ceyhun0/\">ceyhun0</a>, <a href=\"https://profiles.wordpress.org/chadreitsma/\">Chad Reitsma</a>, <a href=\"https://profiles.wordpress.org/cguntur/\">Chandrika Guntur</a>, <a href=\"https://profiles.wordpress.org/cpapazoglou/\">Charalampos Papazoglou</a>, <a href=\"https://profiles.wordpress.org/chetan200891/\">Chetan Prajapati</a>, <a href=\"https://profiles.wordpress.org/chexwarrior/\">chexwarrior</a>, <a href=\"https://profiles.wordpress.org/chintan1896/\">Chintan hingrajiya</a>, <a href=\"https://profiles.wordpress.org/chipsnyder/\">Chip Snyder</a>, <a href=\"https://profiles.wordpress.org/cbringmann/\">Chloé Bringmann</a>, <a href=\"https://profiles.wordpress.org/chouby/\">Chouby</a>, <a href=\"https://profiles.wordpress.org/alexandec/\">Chris Alexander</a>, <a href=\"https://profiles.wordpress.org/chrisvanpatten/\">Chris Van Patten</a>, <a href=\"https://profiles.wordpress.org/chriscct7/\">chriscct7</a>, <a href=\"https://profiles.wordpress.org/ctmartin0/\">Christian Martin</a>, <a href=\"https://profiles.wordpress.org/christophherr/\">Christoph Herr</a>, <a href=\"https://profiles.wordpress.org/vimes1984/\">Christopher Churchill</a>, <a href=\"https://profiles.wordpress.org/chunkysteveo/\">chunkysteveo</a>, <a href=\"https://profiles.wordpress.org/claudiulodro/\">Claudiu Lodromanean</a>, <a href=\"https://profiles.wordpress.org/claytoncollie/\">Clayton Collie</a>, <a href=\"https://profiles.wordpress.org/collizo4sky/\">Collins Agbonghama</a>, <a href=\"https://profiles.wordpress.org/commeuneimage/\">Commeuneimage</a>, <a href=\"https://profiles.wordpress.org/copons/\">Copons</a>, <a href=\"https://profiles.wordpress.org/salzano/\">Corey Salzano</a>, <a href=\"https://profiles.wordpress.org/cranewest/\">cranewest</a>, <a href=\"https://profiles.wordpress.org/littlebigthing/\">Csaba (LittleBigThings)</a>, <a href=\"https://profiles.wordpress.org/ctmartin/\">ctmartin</a>, <a href=\"https://profiles.wordpress.org/davidszabo/\">D&#225;vid Szab&#243;</a>, <a href=\"https://profiles.wordpress.org/daisyo/\">Daisy Olsen</a>, <a href=\"https://profiles.wordpress.org/danfarrow/\">Dan Farrow</a>, <a href=\"https://profiles.wordpress.org/danielbachhuber/\">Daniel Bachhuber</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/mte90/\">Daniele Scasciafratte</a>, <a href=\"https://profiles.wordpress.org/danieltj/\">danieltj</a>, <a href=\"https://profiles.wordpress.org/dantahoua/\">dantahoua</a>, <a href=\"https://profiles.wordpress.org/dkotter/\">Darin Kotter</a>, <a href=\"https://profiles.wordpress.org/dmchale/\">Dave McHale</a>, <a href=\"https://profiles.wordpress.org/davilera/\">David Aguilera</a>, <a href=\"https://profiles.wordpress.org/davidanderson/\">David Anderson</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">David Baumwald</a>, <a href=\"https://profiles.wordpress.org/dgwyer/\">David Gwyer</a>, <a href=\"https://profiles.wordpress.org/dlh/\">David Herrera</a>, <a href=\"https://profiles.wordpress.org/dshanske/\">David Shanske</a>, <a href=\"https://profiles.wordpress.org/get_dave/\">David Smith</a>, <a href=\"https://profiles.wordpress.org/davidjlaietta/\">David Wolfpaw</a>, <a href=\"https://profiles.wordpress.org/davidbinda/\">david.binda</a>, <a href=\"https://profiles.wordpress.org/davisshaver/\">Davis Shaver</a>, <a href=\"https://profiles.wordpress.org/dd32/\">dd32</a>, <a href=\"https://profiles.wordpress.org/p00ya/\">Dean</a>, <a href=\"https://profiles.wordpress.org/dkarfa/\">Debabrata Karfa</a>, <a href=\"https://profiles.wordpress.org/thewebprincess/\">Dee Teal</a>, <a href=\"https://profiles.wordpress.org/deepaklalwani/\">Deepak Lalwani</a>, <a href=\"https://profiles.wordpress.org/dekervit/\">dekervit</a>, <a href=\"https://profiles.wordpress.org/demetris/\">demetris (Demetris Kikizas)</a>, <a href=\"https://profiles.wordpress.org/denis-de-bernardy/\">Denis de Bernardy</a>, <a href=\"https://profiles.wordpress.org/valendesigns/\">Derek Herman</a>, <a href=\"https://profiles.wordpress.org/designer023/\">Designer023</a>, <a href=\"https://profiles.wordpress.org/dfenton/\">dfenton</a>, <a href=\"https://profiles.wordpress.org/dharm1025/\">Dharmesh Patel</a>, <a href=\"https://profiles.wordpress.org/dharmin16/\">Dharmin Shah</a>, <a href=\"https://profiles.wordpress.org/dhruvin/\">Dhruvin</a>, <a href=\"https://profiles.wordpress.org/dhulwells/\">Dhul Wells</a>, <a href=\"https://profiles.wordpress.org/dietpawel/\">dietpawel</a>, <a href=\"https://profiles.wordpress.org/dilipbheda/\">Dilip Bheda</a>, <a href=\"https://profiles.wordpress.org/dingo_d/\">dingo-d</a>, <a href=\"https://profiles.wordpress.org/djzone/\">DjZoNe</a>, <a href=\"https://profiles.wordpress.org/dogwithblog/\">dogwithblog</a>, <a href=\"https://profiles.wordpress.org/ocean90/\">Dominik Schilling</a>, <a href=\"https://profiles.wordpress.org/donmhico/\">donmhico</a>, <a href=\"https://profiles.wordpress.org/donsony/\">donsony</a>, <a href=\"https://profiles.wordpress.org/dossy/\">Dossy Shiobara</a>, <a href=\"https://profiles.wordpress.org/dpacks/\">dpacks</a>, <a href=\"https://profiles.wordpress.org/raubvogel/\">Dr. Ronny Harbich</a>, <a href=\"https://profiles.wordpress.org/dratwas/\">dratwas</a>, <a href=\"https://profiles.wordpress.org/drewapicture/\">Drew Jaynes</a>, <a href=\"https://profiles.wordpress.org/dsifford/\">dsifford</a>, <a href=\"https://profiles.wordpress.org/dushakov/\">dushakov</a>, <a href=\"https://profiles.wordpress.org/dushanthi/\">dushanthi</a>, <a href=\"https://profiles.wordpress.org/dyrer/\">dyrer</a>, <a href=\"https://profiles.wordpress.org/elrae/\">Earle Davies</a>, <a href=\"https://profiles.wordpress.org/metalandcoffee/\">Ebonie Butler</a>, <a href=\"https://profiles.wordpress.org/ediamin/\">Edi Amin</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\">Ella van Durpe</a>, <a href=\"https://profiles.wordpress.org/elmastudio/\">Ellen Bauer</a>, <a href=\"https://profiles.wordpress.org/enej/\">Enej Bajgorić</a>, <a href=\"https://profiles.wordpress.org/nrqsnchz/\">Enrique S&#225;nchez</a>, <a href=\"https://profiles.wordpress.org/epiqueras/\">epiqueras</a>, <a href=\"https://profiles.wordpress.org/kebbet/\">Erik Betshammar</a>, <a href=\"https://profiles.wordpress.org/erikjandelange/\">erikjandelange</a>, <a href=\"https://profiles.wordpress.org/folletto/\">Erin \'Folletto\' Casali</a>, <a href=\"https://profiles.wordpress.org/eringoblog/\">eringoblog</a>, <a href=\"https://profiles.wordpress.org/eroraghav/\">eroraghav</a>, <a href=\"https://profiles.wordpress.org/estelaris/\">Estela Rueda</a>, <a href=\"https://profiles.wordpress.org/etoledom/\">etoledom</a>, <a href=\"https://profiles.wordpress.org/thegp/\">EugeneBos</a>, <a href=\"https://profiles.wordpress.org/circlecube/\">Evan Mullins</a>, <a href=\"https://profiles.wordpress.org/fabifott/\">Fabian</a>, <a href=\"https://profiles.wordpress.org/fabiankaegy/\">Fabian K&#228;gy</a>, <a href=\"https://profiles.wordpress.org/gaambo/\">Fabian Todt</a>, <a href=\"https://profiles.wordpress.org/felipeelia/\">Felipe Elia</a>, <a href=\"https://profiles.wordpress.org/flixos90/\">Felix Arntz</a>, <a href=\"https://profiles.wordpress.org/ferkho/\">Ferenc Forgacs</a>, <a href=\"https://profiles.wordpress.org/mista-flo/\">Florian TIAR</a>, <a href=\"https://profiles.wordpress.org/flymike/\">flymike</a>, <a href=\"https://profiles.wordpress.org/francina/\">Francesca Marano</a>, <a href=\"https://profiles.wordpress.org/frank-klein/\">Frank Klein</a>, <a href=\"https://profiles.wordpress.org/fjarrett/\">Frankie Jarrett</a>, <a href=\"https://profiles.wordpress.org/fullofcaffeine/\">fullofcaffeine</a>, <a href=\"https://profiles.wordpress.org/ecgan/\">Gan Eng Chin</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse/\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/garyc40/\">Gary Cao</a>, <a href=\"https://profiles.wordpress.org/garyj/\">Gary Jones</a>, <a href=\"https://profiles.wordpress.org/pento/\">Gary Pendergast</a>, <a href=\"https://profiles.wordpress.org/gchtr/\">gchtr</a>, <a href=\"https://profiles.wordpress.org/soulseekah/\">Gennady Kovshenin</a>, <a href=\"https://profiles.wordpress.org/subscriptiongroup/\">George</a>, <a href=\"https://profiles.wordpress.org/georgestephanis/\">George Stephanis</a>, <a href=\"https://profiles.wordpress.org/geriux/\">geriux</a>, <a href=\"https://profiles.wordpress.org/glauberglauber/\">Glauber Mota</a>, <a href=\"https://profiles.wordpress.org/glendaviesnz/\">glendaviesnz</a>, <a href=\"https://profiles.wordpress.org/goldenapples/\">goldenapples</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Greg Zi&#243;łkowski</a>, <a href=\"https://profiles.wordpress.org/guidooffermans/\">guidooffermans</a>, <a href=\"https://profiles.wordpress.org/gumacahin/\">gumacahin</a>, <a href=\"https://profiles.wordpress.org/hvar/\">H-var</a>, <a href=\"https://profiles.wordpress.org/hakre/\">hakre</a>, <a href=\"https://profiles.wordpress.org/happiryu/\">happiryu</a>, <a href=\"https://profiles.wordpress.org/hareesh-pillai/\">Hareesh</a>, <a href=\"https://profiles.wordpress.org/isharis/\">Haris Zulfiqar</a>, <a href=\"https://profiles.wordpress.org/harrym/\">harrym</a>, <a href=\"https://profiles.wordpress.org/harshbarach/\">harshbarach</a>, <a href=\"https://profiles.wordpress.org/azhiyadev/\">Hauwa Abashiya</a>, <a href=\"https://profiles.wordpress.org/hazdiego/\">Haz</a>, <a href=\"https://profiles.wordpress.org/helen/\">Helen Hou-Sandí</a>, <a href=\"https://profiles.wordpress.org/henrywright/\">Henry Wright</a>, <a href=\"https://profiles.wordpress.org/herregroen/\">Herre Groen</a>, <a href=\"https://profiles.wordpress.org/hoasi/\">HoaSi</a>, <a href=\"https://profiles.wordpress.org/hongnizzle/\">Hong Nga Nguyen</a>, <a href=\"https://profiles.wordpress.org/howdy_mcgee/\">Howdy_McGee</a>, <a href=\"https://profiles.wordpress.org/hlashbrooke/\">Hugh Lashbrooke</a>, <a href=\"https://profiles.wordpress.org/iandunn/\">Ian Dunn</a>, <a href=\"https://profiles.wordpress.org/igorradovanov/\">Igor Radovanov</a>, <a href=\"https://profiles.wordpress.org/gsayed786/\">Imran Sayed</a>, <a href=\"https://profiles.wordpress.org/ingereck/\">ingereck</a>, <a href=\"https://profiles.wordpress.org/ipstenu/\">Ipstenu (Mika Epstein)</a>, <a href=\"https://profiles.wordpress.org/iqbalbary/\">iqbalbary</a>, <a href=\"https://profiles.wordpress.org/ireneyoast/\">Irene Strikkers</a>, <a href=\"https://profiles.wordpress.org/isabel_brison/\">Isabel Brison</a>, <a href=\"https://profiles.wordpress.org/jagirbaheshwp/\">jagirbaheshwp</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/twentyzerotwo/\">Jake Whiteley</a>, <a href=\"https://profiles.wordpress.org/jamescollins/\">James Collins</a>, <a href=\"https://profiles.wordpress.org/jameskoster/\">James Koster</a>, <a href=\"https://profiles.wordpress.org/jnylen0/\">James Nylen</a>, <a href=\"https://profiles.wordpress.org/jamesros161/\">James Rosado</a>, <a href=\"https://profiles.wordpress.org/jameslnewell/\">jameslnewell</a>, <a href=\"https://profiles.wordpress.org/janthiel/\">Jan Thiel</a>, <a href=\"https://profiles.wordpress.org/javidalkaruzi/\">Janvo Aldred</a>, <a href=\"https://profiles.wordpress.org/jaredcobb/\">Jared Cobb</a>, <a href=\"https://profiles.wordpress.org/jaswrks/\">Jason Caldwell</a>, <a href=\"https://profiles.wordpress.org/madtownlems/\">Jason LeMahieu (MadtownLems)</a>, <a href=\"https://profiles.wordpress.org/javorszky/\">javorszky</a>, <a href=\"https://profiles.wordpress.org/jaydeep-rami/\">Jaydip Rami</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jean-Baptiste Audras</a>, <a href=\"https://profiles.wordpress.org/jeffmatson/\">Jeff Matson</a>, <a href=\"https://profiles.wordpress.org/jffng/\">Jeff Ong</a>, <a href=\"https://profiles.wordpress.org/jeffpaul/\">Jeff Paul</a>, <a href=\"https://profiles.wordpress.org/jeffikus/\">jeffikus</a>, <a href=\"https://profiles.wordpress.org/jellypixel/\">jellypixel</a>, <a href=\"https://profiles.wordpress.org/jeremyfelt/\">Jeremy Felt</a>, <a href=\"https://profiles.wordpress.org/jeremyescott/\">Jeremy Scott</a>, <a href=\"https://profiles.wordpress.org/jeremyyip/\">Jeremy Yip</a>, <a href=\"https://profiles.wordpress.org/jeroenrotty/\">Jeroen Rotty</a>, <a href=\"https://profiles.wordpress.org/jeryj/\">jeryj</a>, <a href=\"https://profiles.wordpress.org/jeslen/\">Jeslen Bucci</a>, <a href=\"https://profiles.wordpress.org/luminuu/\">Jessica Lyschik</a>, <a href=\"https://profiles.wordpress.org/jfoulquier/\">jfoulquier</a>, <a href=\"https://profiles.wordpress.org/jimyaghi/\">jimyaghi</a>, <a href=\"https://profiles.wordpress.org/jipmoors/\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/joedolson/\">Joe Dolson</a>, <a href=\"https://profiles.wordpress.org/joemcgill/\">Joe McGill</a>, <a href=\"https://profiles.wordpress.org/joelyoder/\">Joel Yoder</a>, <a href=\"https://profiles.wordpress.org/joelclimbsthings/\">joelclimbsthings</a>, <a href=\"https://profiles.wordpress.org/joen/\">Joen Asmussen</a>, <a href=\"https://profiles.wordpress.org/johannadevos/\">Johanna de Vos</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/johnny5/\">John Godley</a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\">John James Jacoby</a>, <a href=\"https://profiles.wordpress.org/jb510/\">Jon Brown</a>, <a href=\"https://profiles.wordpress.org/psykro/\">Jonathan Bossenger</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/jonathanstegall/\">Jonathan Stegall</a>, <a href=\"https://profiles.wordpress.org/spacedmonkey/\">Jonny Harris</a>, <a href=\"https://profiles.wordpress.org/jonoaldersonwp/\">Jono Alderson</a>, <a href=\"https://profiles.wordpress.org/joostdevalk/\">Joost de Valk</a>, <a href=\"https://profiles.wordpress.org/jordesign/\">jordesign</a>, <a href=\"https://profiles.wordpress.org/koke/\">Jorge Bernal</a>, <a href=\"https://profiles.wordpress.org/jorgefilipecosta/\">Jorge Costa</a>, <a href=\"https://profiles.wordpress.org/joseaneto/\">joseaneto</a>, <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a>, <a href=\"https://profiles.wordpress.org/joshlevinson/\">Josh Levinson</a>, <a href=\"https://profiles.wordpress.org/shelob9/\">Josh Pollock</a>, <a href=\"https://profiles.wordpress.org/joshuatf/\">joshuatf</a>, <a href=\"https://profiles.wordpress.org/tai/\">JOTAKI, Taisuke</a>, <a href=\"https://profiles.wordpress.org/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/jsnajdr/\">jsnajdr</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/junaidbhura/\">Junaid Bhura</a>, <a href=\"https://profiles.wordpress.org/justinahinon/\">Justin Ahinon</a>, <a href=\"https://profiles.wordpress.org/justlevine/\">justlevine</a>, <a href=\"https://profiles.wordpress.org/kadamwhite/\">K. Adam White</a>, <a href=\"https://profiles.wordpress.org/kevin940726/\">Kai Hao</a>, <a href=\"https://profiles.wordpress.org/trepmal/\">Kailey (trepmal)</a>, <a href=\"https://profiles.wordpress.org/akabarikalpesh/\">Kalpesh Akabari</a>, <a href=\"https://profiles.wordpress.org/karthikbhatb/\">Karthik Bhat</a>, <a href=\"https://profiles.wordpress.org/kasparsd/\">Kaspars</a>, <a href=\"https://profiles.wordpress.org/ryelle/\">Kelly Dwan</a>, <a href=\"https://profiles.wordpress.org/kellychoffman/\">Kelly Hoffman</a>, <a href=\"https://profiles.wordpress.org/kelsu02/\">Kelly R</a>, <a href=\"https://profiles.wordpress.org/kellybleck/\">kellybleck</a>, <a href=\"https://profiles.wordpress.org/kellylawrence/\">kellylawrence</a>, <a href=\"https://profiles.wordpress.org/khag7/\">Kevin Hagerty</a>, <a href=\"https://profiles.wordpress.org/kharisblank/\">Kharis Sulistiyono</a>, <a href=\"https://profiles.wordpress.org/kipperlenny/\">Kipperlenny</a>, <a href=\"https://profiles.wordpress.org/kirilzh/\">Kiril Zhelyazkov</a>, <a href=\"https://profiles.wordpress.org/kburgoine/\">Kirsty Burgoine</a>, <a href=\"https://profiles.wordpress.org/kishanjasani/\">Kishan Jasani</a>, <a href=\"https://profiles.wordpress.org/ixkaito/\">Kite</a>, <a href=\"https://profiles.wordpress.org/kittmedia/\">KittMedia</a>, <a href=\"https://profiles.wordpress.org/kjbenk/\">kjbenk</a>, <a href=\"https://profiles.wordpress.org/kjellr/\">Kjell Reigstad</a>, <a href=\"https://profiles.wordpress.org/knutsp/\">Knut Sparhell</a>, <a href=\"https://profiles.wordpress.org/komagain/\">komagain</a>, <a href=\"https://profiles.wordpress.org/obenland/\">Konstantin Obenland</a>, <a href=\"https://profiles.wordpress.org/krupajnanda/\">Krupa</a>, <a href=\"https://profiles.wordpress.org/kbjohnson90/\">Kyle B. Johnson</a>, <a href=\"https://profiles.wordpress.org/landau/\">landau</a>, <a href=\"https://profiles.wordpress.org/lmurillom/\">Larissa Murillo</a>, <a href=\"https://profiles.wordpress.org/latifi/\">latifi</a>, <a href=\"https://profiles.wordpress.org/newyorkerlaura/\">Laura Byrne</a>, <a href=\"https://profiles.wordpress.org/laurora/\">Laura Nelson</a>, <a href=\"https://profiles.wordpress.org/laxman-prajapati/\">Laxman Prajapati</a>, <a href=\"https://profiles.wordpress.org/leogermani/\">leogermani</a>, <a href=\"https://profiles.wordpress.org/gamerz/\">Lester Chan</a>, <a href=\"https://profiles.wordpress.org/leutrimh/\">Leutrim Husaj</a>, <a href=\"https://profiles.wordpress.org/limera1n/\">lim3ra</a>, <a href=\"https://profiles.wordpress.org/lpointet/\">Lionel Pointet</a>, <a href=\"https://profiles.wordpress.org/llizard/\">llizard</a>, <a href=\"https://profiles.wordpress.org/louislaugesen/\">Louis</a>, <a href=\"https://profiles.wordpress.org/lucagrandicelli/\">Luca Grandicelli</a>, <a href=\"https://profiles.wordpress.org/_luigi/\">Luigi Cavalieri</a>, <a href=\"https://profiles.wordpress.org/lukecavanagh/\">Luke Cavanagh</a>, <a href=\"https://profiles.wordpress.org/lumne/\">Lumne</a>, <a href=\"https://profiles.wordpress.org/mager19/\">mager19</a>, <a href=\"https://profiles.wordpress.org/onemaggie/\">Maggie Cabrera</a>, <a href=\"https://profiles.wordpress.org/mahesh901122/\">Mahesh Waghmare</a>, <a href=\"https://profiles.wordpress.org/mailnew2ster/\">mailnew2ster</a>, <a href=\"https://profiles.wordpress.org/shamimmoeen/\">Mainul Hassan Main</a>, <a href=\"https://profiles.wordpress.org/malinajirka/\">malinajirka</a>, <a href=\"https://profiles.wordpress.org/manzwebdesigns/\">manzwebdesigns</a>, <a href=\"https://profiles.wordpress.org/mkaz/\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/marekhrabe/\">Marek Hrabe</a>, <a href=\"https://profiles.wordpress.org/chaton666/\">Marie Comet</a>, <a href=\"https://profiles.wordpress.org/marijnkoopman/\">Marijn Koopman</a>, <a href=\"https://profiles.wordpress.org/tyxla/\">Marin Atanasov</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius Jensen</a>, <a href=\"https://profiles.wordpress.org/markjaquith/\">Mark Jaquith</a>, <a href=\"https://profiles.wordpress.org/markparnell/\">Mark Parnell</a>, <a href=\"https://profiles.wordpress.org/markscottrobson/\">Mark Robson</a>, <a href=\"https://profiles.wordpress.org/marks99/\">Mark Smallman</a>, <a href=\"https://profiles.wordpress.org/mapk/\">Mark Uraine</a>, <a href=\"https://profiles.wordpress.org/markoheijnen/\">Marko Heijnen</a>, <a href=\"https://profiles.wordpress.org/markshep/\">markshep</a>, <a href=\"https://profiles.wordpress.org/m-e-h/\">Marty Helmick</a>, <a href=\"https://profiles.wordpress.org/marybaum/\">Mary Baum</a>, <a href=\"https://profiles.wordpress.org/wetah/\">Mateus Machado Luna</a>, <a href=\"https://profiles.wordpress.org/imath/\">Mathieu Viet</a>, <a href=\"https://profiles.wordpress.org/matveb/\">Matias Ventura</a>, <a href=\"https://profiles.wordpress.org/webdevmattcrom/\">Matt Cromwell</a>, <a href=\"https://profiles.wordpress.org/gothickgothickorguk/\">Matt Gibson</a>, <a href=\"https://profiles.wordpress.org/mattkeys/\">Matt Keys</a>, <a href=\"https://profiles.wordpress.org/matt/\">Matt Mullenweg</a>, <a href=\"https://profiles.wordpress.org/mattwiebe/\">Matt Wiebe</a>, <a href=\"https://profiles.wordpress.org/mattchowning/\">mattchowning</a>, <a href=\"https://profiles.wordpress.org/pfefferle/\">Matthias Pfefferle</a>, <a href=\"https://profiles.wordpress.org/mattoperry/\">mattoperry</a>, <a href=\"https://profiles.wordpress.org/mayankmajeji/\">Mayank Majeji</a>, <a href=\"https://profiles.wordpress.org/meaganhanes/\">Meagan Hanes</a>, <a href=\"https://profiles.wordpress.org/megphillips91/\">Meg Phillips</a>, <a href=\"https://profiles.wordpress.org/meher/\">Meher Bala</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/mgol/\">mgol</a>, <a href=\"https://profiles.wordpress.org/mgrenierfarmmedia/\">mgrenierfarmmedia</a>, <a href=\"https://profiles.wordpress.org/michael-arestad/\">Michael Arestad</a>, <a href=\"https://profiles.wordpress.org/tw2113/\">Michael Beckwith</a>, <a href=\"https://profiles.wordpress.org/m_butcher/\">Michele Butcher-Jones</a>, <a href=\"https://profiles.wordpress.org/michelleames/\">Michelle Frechette</a>, <a href=\"https://profiles.wordpress.org/mcsf/\">Miguel Fonseca</a>, <a href=\"https://profiles.wordpress.org/mihdan/\">mihdan</a>, <a href=\"https://profiles.wordpress.org/mikeschroder/\">Mike Schroder</a>, <a href=\"https://profiles.wordpress.org/mikelopez/\">mikelopez</a>, <a href=\"https://profiles.wordpress.org/mikeyarce/\">Mikey Arce</a>, <a href=\"https://profiles.wordpress.org/dimadin/\">Milan Dinić</a>, <a href=\"https://profiles.wordpress.org/milana_cap/\">Milana Cap</a>, <a href=\"https://profiles.wordpress.org/eemitch/\">Mitchell Bennis</a>, <a href=\"https://profiles.wordpress.org/mmarco9/\">mmarco9</a>, <a href=\"https://profiles.wordpress.org/batmoo/\">Mohammad Jangda</a>, <a href=\"https://profiles.wordpress.org/monikarao/\">Monika Rao</a>, <a href=\"https://profiles.wordpress.org/mopsyd/\">mopsyd</a>, <a href=\"https://profiles.wordpress.org/morganestes/\">Morgan Estes</a>, <a href=\"https://profiles.wordpress.org/gwendydd/\">Morgan Kay</a>, <a href=\"https://profiles.wordpress.org/man4toman/\">Morteza Geransayeh</a>, <a href=\"https://profiles.wordpress.org/computerguru/\">mqudsi</a>, <a href=\"https://profiles.wordpress.org/mreishus/\">mreishus</a>, <a href=\"https://profiles.wordpress.org/mrgrt/\">mrgrt</a>, <a href=\"https://profiles.wordpress.org/mrjoeldean/\">mrjoeldean</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/munyagu/\">munyagu</a>, <a href=\"https://profiles.wordpress.org/musicaljoeker/\">musicaljoeker</a>, <a href=\"https://profiles.wordpress.org/mweichert/\">mweichert</a>, <a href=\"https://profiles.wordpress.org/n5hzr/\">n5hzr</a>, <a href=\"https://profiles.wordpress.org/nabilmoqbel/\">Nabil Moqbel</a>, <a href=\"https://profiles.wordpress.org/nalininonstopnewsuk/\">Nalini Thakor</a>, <a href=\"https://profiles.wordpress.org/naoki0h/\">Naoki Ohashi</a>, <a href=\"https://profiles.wordpress.org/nao/\">Naoko Takano</a>, <a href=\"https://profiles.wordpress.org/nateinaction/\">Nate Gay</a>, <a href=\"https://profiles.wordpress.org/nathanatmoz/\">Nathan Johnson</a>, <a href=\"https://profiles.wordpress.org/navanathbhosale/\">Navanath Bhosale</a>, <a href=\"https://profiles.wordpress.org/naveenkharwar/\">Naveen Kharwar</a>, <a href=\"https://profiles.wordpress.org/lcyh78/\">Neil James (lcyh78)</a>, <a href=\"https://profiles.wordpress.org/nendeb55/\">nendeb</a>, <a href=\"https://profiles.wordpress.org/krstarica/\">net</a>, <a href=\"https://profiles.wordpress.org/arealnobrainer/\">Netravnen</a>, <a href=\"https://profiles.wordpress.org/nicomollet/\">nicomollet</a>, <a href=\"https://profiles.wordpress.org/jainnidhi/\">Nidhi Jain</a>, <a href=\"https://profiles.wordpress.org/nielslange/\">Niels Lange</a>, <a href=\"https://profiles.wordpress.org/ntsekouras/\">Nik Tsekouras</a>, <a href=\"https://profiles.wordpress.org/nikolam/\">Nikola</a>, <a href=\"https://profiles.wordpress.org/nbachiyski/\">Nikolay Bachiyski</a>, <a href=\"https://profiles.wordpress.org/njbrown/\">njbrown</a>, <a href=\"https://profiles.wordpress.org/nlpro/\">nlpro</a>, <a href=\"https://profiles.wordpress.org/noahtallen/\">Noah Allen</a>, <a href=\"https://profiles.wordpress.org/noahshrader/\">noahshrader</a>, <a href=\"https://profiles.wordpress.org/nourma/\">nourma</a>, <a href=\"https://profiles.wordpress.org/oakesjosh/\">oakesjosh</a>, <a href=\"https://profiles.wordpress.org/oguzkocer/\">oguzkocer</a>, <a href=\"https://profiles.wordpress.org/oglekler/\">Olga Gleckler</a>, <a href=\"https://profiles.wordpress.org/alshakero/\">Omar Alshaker</a>, <a href=\"https://profiles.wordpress.org/omarreiss/\">Omar Reiss</a>, <a href=\"https://profiles.wordpress.org/oolleegg55/\">oolleegg55</a>, <a href=\"https://profiles.wordpress.org/optimizingmatters/\">Optimizing Matters</a>, <a href=\"https://profiles.wordpress.org/ov3rfly/\">Ov3rfly</a>, <a href=\"https://profiles.wordpress.org/ovann86/\">ovann86</a>, <a href=\"https://profiles.wordpress.org/ovenall/\">ovenall</a>, <a href=\"https://profiles.wordpress.org/oxyc/\">oxyc</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/jhonqwerty/\">pabloselin</a>, <a href=\"https://profiles.wordpress.org/paddy/\">Paddy</a>, <a href=\"https://profiles.wordpress.org/pankajmohale/\">Pankaj Mohale</a>, <a href=\"https://profiles.wordpress.org/swissspidy/\">Pascal Birchler</a>, <a href=\"https://profiles.wordpress.org/casiepa/\">Pascal Casier</a>, <a href=\"https://profiles.wordpress.org/pbearne/\">Paul Bearne</a>, <a href=\"https://profiles.wordpress.org/pbiron/\">Paul Biron</a>, <a href=\"https://profiles.wordpress.org/pabline/\">Paul Bunkham</a>, <a href=\"https://profiles.wordpress.org/paulschreiber/\">Paul Schreiber</a>, <a href=\"https://profiles.wordpress.org/paulstonier/\">Paul Stonier</a>, <a href=\"https://profiles.wordpress.org/pschrottky/\">Paul Von Schrottky</a>, <a href=\"https://profiles.wordpress.org/pedromendonca/\">Pedro Mendon&#231;a</a>, <a href=\"https://profiles.wordpress.org/pentatonicfunk/\">pentatonicfunk</a>, <a href=\"https://profiles.wordpress.org/pputzer/\">pepe</a>, <a href=\"https://profiles.wordpress.org/pekz0r/\">Peter Elmered</a>, <a href=\"https://profiles.wordpress.org/psmits1567/\">Peter Smits</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/johnstonphilip/\">Phil Johnston</a>, <a href=\"https://profiles.wordpress.org/pierlo/\">Pierre Gordon</a>, <a href=\"https://profiles.wordpress.org/decrecementofeliz/\">Pilar Mera</a>, <a href=\"https://profiles.wordpress.org/wppinar/\">Pinar</a>, <a href=\"https://profiles.wordpress.org/boniu91/\">Piotrek Boniu</a>, <a href=\"https://profiles.wordpress.org/pishmishy/\">pishmishy</a>, <a href=\"https://profiles.wordpress.org/pkvillanueva/\">pkvillanueva</a>, <a href=\"https://profiles.wordpress.org/prashanttholia/\">prashanttholia</a>, <a href=\"https://profiles.wordpress.org/pratikkry/\">Pratik K. Yadav</a>, <a href=\"https://profiles.wordpress.org/presskopp/\">Presskopp</a>, <a href=\"https://profiles.wordpress.org/presstoke/\">presstoke</a>, <a href=\"https://profiles.wordpress.org/prionkor/\">prionkor</a>, <a href=\"https://profiles.wordpress.org/psealock/\">psealock</a>, <a href=\"https://profiles.wordpress.org/puneetsahalot/\">Puneet Sahalot</a>, <a href=\"https://profiles.wordpress.org/itsjonq/\">Q</a>, <a href=\"https://profiles.wordpress.org/rachelbaker/\">Rachel Baker</a>, <a href=\"https://profiles.wordpress.org/rajanit2000/\">Rajan Vijayan</a>, <a href=\"https://profiles.wordpress.org/rajeshsingh520/\">rajeshsingh520</a>, <a href=\"https://profiles.wordpress.org/ramiy/\">Rami Yushuvaev</a>, <a href=\"https://profiles.wordpress.org/jontyravi/\">Ravi Vaghela</a>, <a href=\"https://profiles.wordpress.org/ravipatel/\">ravipatel</a>, <a href=\"https://profiles.wordpress.org/rebasaurus/\">rebasaurus</a>, <a href=\"https://profiles.wordpress.org/redstar504/\">redstar504</a>, <a href=\"https://profiles.wordpress.org/regankhadgi/\">Regan Khadgi</a>, <a href=\"https://profiles.wordpress.org/renehermi/\">Rene Hermenau</a>, <a href=\"https://profiles.wordpress.org/retlehs/\">retlehs</a>, <a href=\"https://profiles.wordpress.org/retrofox/\">retrofox</a>, <a href=\"https://profiles.wordpress.org/riaanlom/\">riaanlom</a>, <a href=\"https://profiles.wordpress.org/youknowriad/\">Riad Benguella</a>, <a href=\"https://profiles.wordpress.org/ribaricplusplus/\">ribaricplusplus</a>, <a href=\"https://profiles.wordpress.org/richtabor/\">Rich Tabor</a>, <a href=\"https://profiles.wordpress.org/rnaby/\">Rnaby</a>, <a href=\"https://profiles.wordpress.org/noisysocks/\">Robert Anderson</a>, <a href=\"https://profiles.wordpress.org/miqrogroove/\">Robert Chapin</a>, <a href=\"https://profiles.wordpress.org/kreppar/\">Rodrigo Arias</a>, <a href=\"https://profiles.wordpress.org/rogerlos/\">rogerlos</a>, <a href=\"https://profiles.wordpress.org/roikles/\">roikles</a>, <a href=\"https://profiles.wordpress.org/rolfsiebers/\">Rolf Siebers</a>, <a href=\"https://profiles.wordpress.org/ronakganatra/\">Ronak Ganatra</a>, <a href=\"https://profiles.wordpress.org/roo2/\">roo2</a>, <a href=\"https://profiles.wordpress.org/rtagliento/\">rtagliento</a>, <a href=\"https://profiles.wordpress.org/bookdude13/\">Ryan Fredlund</a>, <a href=\"https://profiles.wordpress.org/ryankienstra/\">Ryan Kienstra</a>, <a href=\"https://profiles.wordpress.org/rmccue/\">Ryan McCue</a>, <a href=\"https://profiles.wordpress.org/welcher/\">Ryan Welcher</a>, <a href=\"https://profiles.wordpress.org/soean/\">S&#246;ren Wrede</a>, <a href=\"https://profiles.wordpress.org/sabrinazeidan/\">Sabrina Zeidan</a>, <a href=\"https://profiles.wordpress.org/saeedfard/\">Saeed Fard</a>, <a href=\"https://profiles.wordpress.org/salvoaranzulla/\">salvoaranzulla</a>, <a href=\"https://profiles.wordpress.org/samful/\">Sam Fullalove</a>, <a href=\"https://profiles.wordpress.org/sswebster/\">Sam Webster</a>, <a href=\"https://profiles.wordpress.org/otto42/\">Samuel Wood (Otto)</a>, <a href=\"https://profiles.wordpress.org/sanzeeb3/\">Sanjeev Aryal</a>, <a href=\"https://profiles.wordpress.org/saqibameen/\">Saqib Ameen</a>, <a href=\"https://profiles.wordpress.org/sarahricker/\">Sarah Ricker</a>, <a href=\"https://profiles.wordpress.org/sarayourfriend/\">sarayourfriend</a>, <a href=\"https://profiles.wordpress.org/sawanoboly/\">sawanoboly</a>, <a href=\"https://profiles.wordpress.org/scarolan/\">scarolan</a>, <a href=\"https://profiles.wordpress.org/l3rady/\">Scott Cariss</a>, <a href=\"https://profiles.wordpress.org/coffee2code/\">Scott Reilly</a>, <a href=\"https://profiles.wordpress.org/scribu/\">scribu</a>, <a href=\"https://profiles.wordpress.org/scruffian/\">scruffian</a>, <a href=\"https://profiles.wordpress.org/seanpaulrasmussen/\">seanpaulrasmussen</a>, <a href=\"https://profiles.wordpress.org/sebastianpisula/\">Sebastian Pisula</a>, <a href=\"https://profiles.wordpress.org/sebsz/\">SeBsZ</a>, <a href=\"https://profiles.wordpress.org/senning/\">Senning</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">Sergey Biryukov</a>, <a href=\"https://profiles.wordpress.org/yakimun/\">Sergey Yakimov</a>, <a href=\"https://profiles.wordpress.org/sergioestevao/\">SergioEstevao</a>, <a href=\"https://profiles.wordpress.org/shaunandrews/\">shaunandrews</a>, <a href=\"https://profiles.wordpress.org/sncoker/\">Shawntelle Coker</a>, <a href=\"https://profiles.wordpress.org/shital-patel/\">Shital Marakana</a>, <a href=\"https://profiles.wordpress.org/shramee/\">shramee</a>, <a href=\"https://profiles.wordpress.org/sresok/\">Simon Resok</a>, <a href=\"https://profiles.wordpress.org/sirreal/\">sirreal</a>, <a href=\"https://profiles.wordpress.org/smerriman/\">smerriman</a>, <a href=\"https://profiles.wordpress.org/snapfractalpop/\">snapfractalpop</a>, <a href=\"https://profiles.wordpress.org/sproutchris/\">sproutchris</a>, <a href=\"https://profiles.wordpress.org/stulab/\">St&#233;phane Treilhou</a>, <a href=\"https://profiles.wordpress.org/metodiew/\">Stanko Metodiev</a>, <a href=\"https://profiles.wordpress.org/garubi/\">Stefano Garuti</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\">Stephen Bernhardt</a>, <a href=\"https://profiles.wordpress.org/dufresnesteven/\">Steve Dufresne</a>, <a href=\"https://profiles.wordpress.org/sterndata/\">Steven Stern (sterndata)</a>, <a href=\"https://profiles.wordpress.org/stevenlinx/\">stevenlinx</a>, <a href=\"https://profiles.wordpress.org/stoyangeorgiev/\">Stoyan Georgiev</a>, <a href=\"https://profiles.wordpress.org/sudoshreyansh/\">sudoshreyansh</a>, <a href=\"https://profiles.wordpress.org/smub/\">Syed Balkhi</a>, <a href=\"https://profiles.wordpress.org/szaqal21/\">szaqal21</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/utz119/\">TeBenachi</a>, <a href=\"https://profiles.wordpress.org/techboyg5/\">techboyg5</a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>, <a href=\"https://profiles.wordpress.org/thefarlilacfield/\">thefarlilacfield</a>, <a href=\"https://profiles.wordpress.org/thelmachido/\">Thelma Mutete</a>, <a href=\"https://profiles.wordpress.org/thib3113/\">thib3113</a>, <a href=\"https://profiles.wordpress.org/thijsvanloef/\">thijsvanloef</a>, <a href=\"https://profiles.wordpress.org/webzunft/\">Thomas M</a>, <a href=\"https://profiles.wordpress.org/thomasplevy/\">Thomas Patrick Levy</a>, <a href=\"https://profiles.wordpress.org/thomaslhotta/\">thomaslhotta</a>, <a href=\"https://profiles.wordpress.org/timhavinga/\">Tim Havinga</a>, <a href=\"https://profiles.wordpress.org/hedgefield/\">Tim Hengeveld</a>, <a href=\"https://profiles.wordpress.org/sippis/\">Timi Wahalahti</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/timotijhof/\">TimoTijhof</a>, <a href=\"https://profiles.wordpress.org/tkama/\">Tkama</a>, <a href=\"https://profiles.wordpress.org/tmdesigned/\">tmdesigned</a>, <a href=\"https://profiles.wordpress.org/tobiasbg/\">TobiasBg</a>, <a href=\"https://profiles.wordpress.org/tobifjellner/\">tobifjellner (Tor-Bjorn Fjellner)</a>, <a href=\"https://profiles.wordpress.org/hellofromtonya/\">Tonya Mork</a>, <a href=\"https://profiles.wordpress.org/toro_unit/\">Toro_Unit (Hiroshi Urabe)</a>, <a href=\"https://profiles.wordpress.org/torres126/\">torres126</a>, <a href=\"https://profiles.wordpress.org/zodiac1978/\">Torsten Landsiedel</a>, <a href=\"https://profiles.wordpress.org/itowhid06/\">Towhidul I Chowdhury</a>, <a href=\"https://profiles.wordpress.org/tray/\">tracy apps</a>, <a href=\"https://profiles.wordpress.org/treibstoff/\">treibstoff</a>, <a href=\"https://profiles.wordpress.org/trisha_cornelius/\">Trisha Cornelius</a>, <a href=\"https://profiles.wordpress.org/dinhtungdu/\">Tung Du</a>, <a href=\"https://profiles.wordpress.org/tzafrir/\">tzafrir</a>, <a href=\"https://profiles.wordpress.org/desaiuditd/\">Udit Desai</a>, <a href=\"https://profiles.wordpress.org/grapplerulrich/\">Ulrich</a>, <a href=\"https://profiles.wordpress.org/uxkai/\">uxkai</a>, <a href=\"https://profiles.wordpress.org/valentinbora/\">Valentin Bora</a>, <a href=\"https://profiles.wordpress.org/contact-banker/\">Varun Sharma</a>, <a href=\"https://profiles.wordpress.org/vcanales/\">vcanales</a>, <a href=\"https://profiles.wordpress.org/ravivaddweb/\">vidhiaddweb</a>, <a href=\"https://profiles.wordpress.org/vinayakanivase/\">Vinayak Anivase</a>, <a href=\"https://profiles.wordpress.org/vinita29/\">Vinita Tandulkar</a>, <a href=\"https://profiles.wordpress.org/usestrict/\">Vinny</a>, <a href=\"https://profiles.wordpress.org/virgodesign/\">virgodesign</a>, <a href=\"https://profiles.wordpress.org/webmandesign/\">WebMan Design &#124; Oliver Juhas</a>, <a href=\"https://profiles.wordpress.org/webmigrates/\">Webmigrates Technologies</a>, <a href=\"https://profiles.wordpress.org/westonruter/\">Weston Ruter</a>, <a href=\"https://profiles.wordpress.org/earnjam/\">William Earnhardt</a>, <a href=\"https://profiles.wordpress.org/williampatton/\">williampatton</a>, <a href=\"https://profiles.wordpress.org/planningwrite/\">Winstina Hughes</a>, <a href=\"https://profiles.wordpress.org/wittich/\">wittich</a>, <a href=\"https://profiles.wordpress.org/worldweb/\">worldweb</a>, <a href=\"https://profiles.wordpress.org/y_kolev/\">Y_Kolev</a>, <a href=\"https://profiles.wordpress.org/yansern/\">Yan Sern</a>, <a href=\"https://profiles.wordpress.org/yoavf/\">Yoav Farhi</a>, <a href=\"https://profiles.wordpress.org/yscik/\">yscik</a>, <a href=\"https://profiles.wordpress.org/fierevere/\">Yui</a>, <a href=\"https://profiles.wordpress.org/yvettesonneveld/\">Yvette Sonneveld</a>, and <a href=\"https://profiles.wordpress.org/zebulan/\">Zebulan Stanphill</a>.\n\n\n\n<p></p>\n\n\n\n<p>In addition, many thanks to all of the community volunteers who contribute in the <a href=\"https://wordpress.org/support/\">support forums</a>. They answer questions from people across the world, whether they are using WordPress for the first time, or they’ve been around since the first release all the way back in 2003. These releases are as successful as they are because of their efforts!</p>\n\n\n\n<p>Finally, thanks to all the community translators who helped make WordPress 5.6. available in 38 languages at the time of release. Our community translators are hard at work ensuring more languages are on their way (70 are already at 90%). If contributing to WordPress appeals to you, it’s easy to learn more. Check out <a href=\"https://make.wordpress.org/\">Make WordPress</a> or the <a href=\"https://make.wordpress.org/core/\">core development blog</a>.</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9325\";s: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: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:22:\"State of the Word 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2020/12/state-of-the-word-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 04 Dec 2020 22:55: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: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:34:\"https://wordpress.org/news/?p=9296\";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:110:\"State of the Word will be streamed on Facebook, YouTube, and Twitter on Thursday, Dec 17th, 2020  at 1600 UTC.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:1225:\"\n<p>State of the Word is an annual keynote address delivered by the project co-founder, Matt Mullenweg. Catch this year&#8217;s keynote in the video below!</p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe class=\'youtube-player\' width=\'632\' height=\'356\' src=\'https://www.youtube.com/embed/QI3qCoiuG3w?version=3&#038;rel=1&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;fs=1&#038;hl=en-US&#038;autohide=2&#038;wmode=transparent\' allowfullscreen=\'true\' style=\'border:0;\' sandbox=\'allow-scripts allow-same-origin allow-popups allow-presentation\'></iframe>\n</div></figure>\n\n\n\n<h3>New to State of the Word?</h3>\n\n\n\n<p>If this is your first time hearing of this talk, you’re in luck! Check out previous recordings below.</p>\n\n\n\n<ul><li><a href=\"https://wordpress.tv/2019/11/03/2019-state-of-the-word/\">State of the Word 2019 &#8211; WordCamp US, St. Louis</a></li><li><a href=\"https://wordpress.tv/2018/12/27/state-of-the-word-2018/\">State of the Word 2018 &#8211; WordCamp US, Nashville</a></li><li><a href=\"https://wordpress.tv/tag/state-of-the-word/\">All recordings</a></li></ul>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9296\";s: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: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:37:\"The Month in WordPress: November 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2020/12/the-month-in-wordpress-november-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 02 Dec 2020 09:13:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9283\";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:304:\"November 2020 saw several updates to the WordPress 5.6 release. Read on to follow all the latest news from the WordPress world! WordPress 5.6 updates The Core team released WordPress 5.6 Beta 3 on Nov. 2, Beta 4 on Nov. 12, release candidate 1 on Nov. 17, and release candidate 2 on Dec. 1. You [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"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:10892:\"\n<p>November 2020 saw several updates to the WordPress 5.6 release. Read on to follow all the latest news from the WordPress world!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.6 updates</h2>\n\n\n\n<p>The Core team released WordPress 5.6 <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-3/\">Beta 3</a> on Nov. 2, <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-4/\">Beta 4</a> on Nov. 12, <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-release-candidate/\">release candidate</a> 1 on Nov. 17, and <a href=\"https://wordpress.org/news/2020/12/wordpress-5-6-release-candidate-2/\">release candidate 2</a> on Dec. 1. You can test the Beta versions and the release candidates by <a href=\"https://wordpress.org/wordpress-5.6-beta2.zip\">downloading them from WordPress.org</a> or by using the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin. Check out the <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">WordPress 5.6 field guide</a> to understand the features of WordPress 5.6 and learn how you can incorporate them into your websites. WordPress 5.6 <a href=\"https://make.wordpress.org/core/5-6/\">will be out by Dec. 9, 2020</a>. </p>\n\n\n\n<p>But our work is never done: You can submit <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-5-7-whats-on-your-wishlist/\">feature suggestions for WordPress 5.7</a> by Dec. 15.&nbsp;</p>\n\n\n\n<p>Want to contribute to upcoming WordPress releases? Join the WordPress Core dev chats on Wednesdays at 5 a.m. and 8 p.m. UTC in the <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel on the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a>, and <a href=\"https://make.wordpress.org/core/tag/dev-chat/\">catch up with recaps</a> on the <a href=\"https://make.wordpress.org/core/\">Core team blog</a>. If you would like to help with WordPress 5.6 outreach, contact the <a href=\"https://make.wordpress.org/marketing/\">WordPress Marketing team</a> on the <a href=\"https://wordpress.slack.com/archives/C0GKJ7TFA\">#marketing</a> channel.</p>\n\n\n\n<h2>Gutenberg 9.3 and 9.4 are out</h2>\n\n\n\n<p>Contributor teams released Gutenberg <a href=\"https://make.wordpress.org/core/2020/11/04/whats-new-in-gutenberg-4-november/\">Version 9.3</a> on Nov. 4 and <a href=\"https://make.wordpress.org/core/2020/11/19/whats-new-in-gutenberg-18-november-2/\">Version 9.4</a> on Nov. 18. Both versions include&nbsp; several improvements to Full Site Editing (FSE) flows, in addition to bug fixes and feature upgrades. Version 9.3 is the first release that isn’t included entirely in WordPress 5.6; the version automatically enables FSE experiments when a block-based theme is active. Version 9.4 introduces some new features like percentage width for button blocks, block variation transformations, social icon support, and font size support for the list block. You can find out more about the Gutenberg roadmap in the <a href=\"https://make.wordpress.org/core/2020/11/02/whats-next-in-gutenberg-november-2020/\">What’s next in Gutenberg blog post</a>.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Learn WordPress updates</h2>\n\n\n\n<p>WordPress contributor teams are all set to launch <a href=\"https://learn.wordpress.org/\">Learn WordPress</a> in December. Community members can now watch<a href=\"https://learn.wordpress.org/workshops\"> video workshops</a> to learn about various WordPress topics, <a href=\"https://www.meetup.com/learn-wordpress-discussions/\">participate in discussion groups</a>, and use <a href=\"https://learn.wordpress.org/lesson-plans/\">lesson plans</a> for organizing their own workshops. Contributor teams have launched <a href=\"https://make.wordpress.org/community/2020/11/18/quizzes-are-now-live-on-learn-wordpress/\">quizzes</a> and are also working on <a href=\"https://make.wordpress.org/community/2020/11/18/standards-for-learn-wordpress-workshop-content/\">setting standards</a> for workshops.<br></p>\n\n\n\n<p>Want to contribute to Learn WordPress? You can now submit a <a href=\"https://learn.wordpress.org/workshop-presenter-application/\">workshop application</a> (submissions in languages other than English are welcome!), apply to become a <a href=\"https://learn.wordpress.org/discussion-group-leader-application/\">discussion group leader</a>, organize <a href=\"https://make.wordpress.org/community/handbook/virtual-events/organize-learn-wordpress-discussion-groups-for-your-wordpress-meetup/\">discussions for your local WordPress meetup group</a>, or <a href=\"https://make.wordpress.org/training/2020/11/25/high-priority-items-before-learn-wordpress-org-launch-part-2/\">help fix issues with existing lesson plans</a>.</p>\n\n\n\n<h2>WordPress 5.6 Translations and Polyglots survey</h2>\n\n\n\n<p>WordPress 5.6 is ready to be translated and is now at <a href=\"https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze\">hard string freeze</a>. If you would like to contribute, <a href=\"https://make.wordpress.org/polyglots/2020/11/07/wordpress-5-6-ready-to-be-translated/\">check out these instructions</a> and ensure that <a href=\"https://make.wordpress.org/polyglots/handbook/translating/packaging-localized-wordpress/automated-release-packages/\">your locale is ready for an automated release</a>. The Polyglots team has also kicked off its <a href=\"https://wordpressdotorg.survey.fm/polyglots-translator-research\">translator research survey</a>. Please <a href=\"https://wordpressdotorg.survey.fm/polyglots-translator-research\">participate in the survey</a>, share the <a href=\"https://wordpressdotorg.survey.fm/polyglots-translator-research\">survey link</a> with members of your locale, and help amplify the <a href=\"https://www.facebook.com/WPTranslationDay/posts/1275404086174610\">Facebook</a>, <a href=\"https://twitter.com/TranslateWP/status/1333342595913834496\">Twitter</a>, and <a href=\"https://www.linkedin.com/posts/wptranslationday_makewordpress-wordpress-activity-6739110862650523648-fX8R/\">LinkedIn</a> posts about it.</p>\n\n\n\n<p>Want to help WordPress speak your language? Follow <a href=\"https://make.wordpress.org/polyglots\">the Polyglots team blog</a> and join the <a href=\"https://wordpress.slack.com/archives/C02RP50LK\">#polyglots</a> channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.&nbsp;</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li><a href=\"https://www.php.net/releases/8.0/en.php\">PHP 8</a> is out, and WordPress 5.6 <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\">aims to be &#8220;beta-compatible&#8221; with the latest PHP version</a>.</li><li>Contributor teams have kicked off <a href=\"https://make.wordpress.org/themes/2020/11/18/theme-previews-in-the-time-of-blocks/\">an ongoing discussion on starter content for WordPress themes</a>. Starter content for the <a href=\"http://wp-themes.com/twentytwentyone/\">Twenty Twenty One</a>, <a href=\"http://wp-themes.com/twentytwenty/\">Twenty Twenty</a>, and <a href=\"http://wp-themes.com/twentyseventeen/\">Twenty Seventeen</a> themes are now available.</li><li>The Accessibility team is <a href=\"https://github.com/10degrees/accessibility-statement-plugin\">testing a tool</a> to generate the structure of an accessibility statement for WordPress websites based on <a href=\"https://www.w3.org/WAI/planning/statements/generator/#create\">W3C standards</a>, and it is <a href=\"https://github.com/10degrees/accessibility-statement-plugin/issues\">requesting feedback from the community</a>.</li><li>The <a href=\"https://wordpressfoundation.org/\">WordPress Foundation</a> has published a <a href=\"https://wordpressfoundation.org/2020/open-source-workshops-november-2020-report/\">report on Open Source workshops</a> that were held online in 2020, based on the <a href=\"https://learn.wordpress.org/\">Learn WordPress</a> platform.</li><li>The Docs team is actively <a href=\"https://make.wordpress.org/docs/2020/11/12/follow-up-on-gutenberg-developer-documentation-restructuring-proposal/\">following up</a> on a proposal to <a href=\"https://make.wordpress.org/docs/2020/08/13/plan-proposal-for-a-new-better-structured-gutenberg-developer-documentation/\">restructure the Gutenberg developer documentation</a>.</li><li>The Community team is back with <a href=\"https://make.wordpress.org/community/tag/tuesdaytrainings/\">Tuesday Trainings</a>. The team is <a href=\"https://make.wordpress.org/community/2020/11/16/community-team-goals-for-2021-share-your-suggestions/\">also inviting suggestions on team goals for 2021</a> with a deadline of Dec. 14.</li><li>The Support team is <a href=\"https://make.wordpress.org/support/2020/11/changing-up-the-forum-front-page/\">making changes to the forum page</a> to improve discoverability. </li><li>Two online WordCamps took place in November: <a href=\"https://finland.wordcamp.org/2020/\">WordCamp Finland Online</a> and <a href=\"https://mexico.wordcamp.org/2020/\">WordCamp Mexico Online</a>. You can find Livestream recaps of the events on their websites. Videos will soon be available on WordPress.tv as well.</li><li>The Themes team <a href=\"https://make.wordpress.org/themes/2020/11/11/meeting-notes-tuesday-november-10-2020/\">made some changes to WordPress theme requirements</a>. These include removing updated CSS guidelines and a proposed plan to make WordPress themes accessibility-ready. The team is also <a href=\"https://make.wordpress.org/themes/2020/11/19/feedback-requested-resolution-process-for-issues-found-in-live-themes/\">requesting feedback</a> on the resolution process for issues found in live themes.</li><li>WordPress 5.6 will feature a <a href=\"https://make.wordpress.org/core/2020/11/05/updating-core-jquery-to-version-3-part-2/\">major jQuery change</a>, with the bundled jQuery version being updated to Version 3.5.1 and jQuery Migrate being updated to Version 3.3.2.</li><li>The <a href=\"https://make.wordpress.org/community/tag/wpdiversity/\">Diversity speaker training group</a> of the Community team is requesting feedback on reimagining their work. Please <a href=\"https://make.wordpress.org/community/2020/11/12/input-requested-re-imagining-the-work-of-the-diverse-speaker-training-group-wpdiversity/\">share your feedback as comments on the post</a> by Dec. 18.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9283\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 5.6 Release Candidate 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:69:\"https://wordpress.org/news/2020/12/wordpress-5-6-release-candidate-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, 01 Dec 2020 22:09:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9274\";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:388:\"The second release candidate for WordPress 5.6 is here! WordPress 5.6 is slated for release on December 8, 2020, and we need your help to get there—if you haven’t tried 5.6 yet, now is the time! You can test WordPress 5.6 release candidate 2 in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option). Or download the release [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2249:\"\n<p>The second release candidate for WordPress 5.6 is here!</p>\n\n\n\n<p>WordPress 5.6 is slated for release on <strong>December 8, 2020</strong>, and we need <em>your</em> help to get there—if you haven’t tried 5.6 yet, now is the time!</p>\n\n\n\n<p>You can test WordPress 5.6 release candidate 2 in two ways:</p>\n\n\n\n<ul><li>Try the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (choose the “bleeding edge nightlies” option).</li><li>Or <a href=\"https://wordpress.org/wordpress-5.6-RC2.zip\">download the release candidate here (zip)</a>.</li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>Plugin and Theme Developers</h2>\n\n\n\n<p>Please test your plugins and themes against WordPress 5.6 and update the <em>Tested up to</em> version in the readme file to 5.6. If you find compatibility problems, please be sure to post to the <a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a>. That way, those can be figured out before the final release. </p>\n\n\n\n<p>For a more detailed breakdown of the changes included in WordPress 5.6, check out the <a href=\"https://wordpress.org/news/2020/10/wordpress-5-6-beta-1/\">WordPress 5.6 beta 1 post</a>. The <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">WordPress 5.6 Field Guide</a> is also out! It’s your source for details on all the major changes.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English? <a href=\"https://translate.wordpress.org/projects/wp/dev\">Help translate WordPress into more than 100 languages!</a></p>\n\n\n\n<p><em><strong>Think you found a bug?</strong> Post it to the <a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible bug report you can <a href=\"https://make.wordpress.org/core/reports/\">file one on WordPress Trac</a>. Don&#8217;t forget to check <a href=\"https://core.trac.wordpress.org/tickets/major\">the list of known bugs</a></em>!</p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9274\";s: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:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 5.6 Release Candidate\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2020/11/wordpress-5-6-release-candidate/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 17 Nov 2020 22:43: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: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.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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9258\";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:49:\"WordPress 5.6 Release Candidate is now available!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:3349:\"\n<p>The first release candidate for WordPress 5.6 is now available!</p>\n\n\n\n<p>This is an important milestone in the community’s progress toward the final release of WordPress 5.6.</p>\n\n\n\n<p>“Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.6 is slated for release&nbsp;on&nbsp;<strong>December 8, 2020</strong>, but we need&nbsp;<em>your</em>&nbsp;help to get there—if you haven’t tried 5.6 yet,&nbsp;<strong>now is the time</strong>!</p>\n\n\n\n<p>You can test the WordPress 5.6 release candidate in two ways:</p>\n\n\n\n<ul><li>Try the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (choose the “Bleeding edge&#8221; channel and Beta/RC Only” stream options)</li><li>Or <a href=\"https://wordpress.org/wordpress-5.6-RC1.zip\">download the release candidate here (zip)</a>.</li></ul>\n\n\n\n<p>Thank you to all of the contributors who tested the&nbsp;Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.</p>\n\n\n\n<h2>What’s in WordPress 5.6?</h2>\n\n\n\n<p>The final release of 2020 continues the annual tradition of a new default theme that is custom built to showcase the new features and functionality of the software. Continued progress on the block editor is especially clear in this release, which brings more blocks to more places, and fewer clicks to implement your layouts.</p>\n\n\n\n<p>WordPress 5.6 also has lots of refinements to polish the developer experience. To learn more, subscribe to the&nbsp;<a href=\"https://make.wordpress.org/core/\">Make WordPress Core blog</a>&nbsp;and pay special attention to the&nbsp;<a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">developer notes</a>&nbsp;tag for updates on those and other changes that could affect your products.</p>\n\n\n\n<h2>Plugin and Theme Developers</h2>\n\n\n\n<p>Please test your plugins and themes against WordPress 5.6 and update the&nbsp;<em>Tested up to</em>&nbsp;version in the readme file to 5.6. If you find compatibility problems, please be sure to post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">support forums</a>,&nbsp;so those can be figured out before the final release.</p>\n\n\n\n<p>The&nbsp;WordPress 5.6 Field Guide, due very shortly, will give you a more detailed dive into the major changes.</p>\n\n\n\n<h2>How to Help</h2>\n\n\n\n<p>Do you speak a language other than English?&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Help us translate WordPress into more than 100 languages!</a>&nbsp;This release also marks the&nbsp;<a href=\"https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze\">hard string freeze</a>&nbsp;point of the 5.6 release schedule.</p>\n\n\n\n<p><em><strong>If you think you’ve found a bug</strong>, you can post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a>&nbsp;in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report,&nbsp;<a href=\"https://make.wordpress.org/core/reports/\">file one on WordPress Trac</a>, where you can also find&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">a list of known bugs</a>.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9258\";s: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:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.6 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/2020/11/wordpress-5-6-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:\"Thu, 12 Nov 2020 23:49:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a: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.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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9249\";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:363:\"WordPress 5.6 Beta 4 is now available for testing! This software is still in development,&#160;so we recommend that you run this version on a test site. You can test the WordPress 5.6 beta in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option). Or download the beta here (zip). The current target for the [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:5658:\"\n<p>WordPress 5.6 Beta 4 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so we recommend that you run this version on a test site.</p>\n\n\n\n<p>You can test the WordPress 5.6 beta in two ways:</p>\n\n\n\n<ul><li>Try the <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (choose the “bleeding edge nightlies” option).</li><li>Or <a href=\"https://wordpress.org/wordpress-5.6-beta4.zip\">download the beta here (zip)</a>.</li></ul>\n\n\n\n<p>The current target for the final release is December 8, 2020. This is just over<strong> three weeks away</strong>, so your help is needed to ensure this release is tested properly.</p>\n\n\n\n<p>Thank you to all of the contributors that tested the <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-3/\">beta 3</a> development release and provided feedback. Testing for bugs is an important part of polishing each release and a great way to contribute to WordPress.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since beta 3, <a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/query?status=closed&amp;changetime=11%2F04%2F2020..11%2F12%2F2020&amp;milestone=5.6&amp;group=component&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">42 bugs</a> have been fixed. Here is a summary of a few changes included in beta 4:</p>\n\n\n\n<ul><li>There was a change to the auto-updates implementation for new installations of the software (<a href=\"https://core.trac.wordpress.org/ticket/50907\">#50907</a>). <em><a href=\"https://make.wordpress.org/core/2020/11/10/upgrade-install-component-meeting-summary-november-10-2020/\">Next steps</a>, and <a href=\"https://make.wordpress.org/core/2020/11/10/wp5-6-auto-update-implementation-change/\">rationale</a> are both available.</em></li><li>Added better handling of unexpected values in Site Health (<a href=\"https://core.trac.wordpress.org/ticket/50145\">#50145</a>).</li><li>Added a way for developers to filter the available authors list in Quick Edit (<a href=\"https://core.trac.wordpress.org/ticket/47685\">#47685</a>).</li><li>More accessible handling of the tag cloud widget (<a href=\"https://core.trac.wordpress.org/ticket/51455\">#51455</a>).</li><li><a href=\"https://core.trac.wordpress.org/query?status=closed&amp;changetime=11%2F04%2F2020..11%2F12%2F2020&amp;component=Media&amp;milestone=5.6&amp;group=component&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">Multiple improvements in the Media component</a>.</li><li><a href=\"https://core.trac.wordpress.org/query?status=closed&amp;changetime=11%2F04%2F2020..11%2F12%2F2020&amp;component=Build%2FTest+Tools&amp;milestone=5.6&amp;group=component&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">Multiple improvements in the Build/Test Tools component</a>.</li></ul>\n\n\n\n<p><em>To see all of the features for each Gutenberg release in detail, check out the release posts: <a href=\"https://make.wordpress.org/core/2020/07/22/whats-new-in-gutenberg-july-22/\">8.6</a>, <a href=\"https://make.wordpress.org/core/2020/08/05/whats-new-in-gutenberg-august-5/\">8.7</a>, <a href=\"https://make.wordpress.org/core/2020/08/19/whats-new-in-gutenberg-august-19/\">8.8</a>, <a href=\"https://make.wordpress.org/core/2020/09/03/whats-new-in-gutenberg-2-september/\">8.9</a>, <a href=\"https://make.wordpress.org/core/2020/09/16/whats-new-in-gutenberg-16-september/\">9.0</a>, <a href=\"https://make.wordpress.org/core/2020/10/01/whats-new-in-gutenberg-30-september/\">9.1</a>, <a href=\"https://make.wordpress.org/core/2020/10/21/whats-new-in-gutenberg-21-october/\">9.2</a>, and <a href=\"https://github.com/WordPress/gutenberg/releases/tag/v9.3.0-rc.1\">9.3</a>.</em></p>\n\n\n\n<h2 id=\"block-76156b2b-0a52-4502-b585-6cbe9481f55b\">Developer notes</h2>\n\n\n\n<p id=\"block-3fe5e264-0a95-4f12-9a18-0cb9dc5955d1\">WordPress 5.6 has lots of refinements to the developer experience. To keep up, subscribe to the <a href=\"https://make.wordpress.org/core/\">Make WordPress Core blog</a> and pay special attention to the <a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">developers’ notes</a> for updates on those and other changes that could affect your products.</p>\n\n\n\n<h2 id=\"block-bc89fd56-47b0-439f-8e2c-4a642c80a616\">How to Help</h2>\n\n\n\n<p id=\"block-9d871099-ec49-446c-8322-9e49b7498c10\">If you think you’ve found a bug, you can post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">Alpha/Beta area</a>&nbsp;in the support forums. We’d love to hear from you!</p>\n\n\n\n<p id=\"block-bd71c1d3-39d9-4b2a-8193-3486497b45fd\">If you’re comfortable writing a reproducible bug report,&nbsp;<a href=\"https://core.trac.wordpress.org/newticket\">file one on WordPress Trac</a>,&nbsp;where you can also find a list of&nbsp;<a href=\"https://core.trac.wordpress.org/query?status=new&amp;milestone=5.6&amp;group=component&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">known bugs</a>.</p>\n\n\n\n<p><em>Props to @tonyamork, @audrasjb for technical notes and @angelasjin,<em> </em><a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld</a><em>, </em><a href=\"https://profiles.wordpress.org/cguntur/\">@cguntur</a>, <a href=\'https://profiles.wordpress.org/cbringmann/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>cbringmann</a> for final review.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9249\";s: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:63:\"\n		\n		\n		\n		\n		\n				\n		\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.6 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/2020/11/wordpress-5-6-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:\"Mon, 02 Nov 2020 21:23:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a: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.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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9234\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:379:\"WordPress 5.6 Beta 3 is now available for testing! This software is still in development,&#160;so we recommend that you run this version on a test site. You can test the WordPress 5.6 beta in two ways: Try the&#160;WordPress Beta Tester&#160;plugin (choose the “bleeding edge nightlies” option). Or&#160;download the beta here&#160;(zip). The current target for the [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:5206:\"\n<p>WordPress 5.6 Beta 3 is now available for testing!</p>\n\n\n\n<p><strong>This software is still in development,</strong>&nbsp;so we recommend that you run this version on a test site.</p>\n\n\n\n<p>You can test the WordPress 5.6 beta in two ways:</p>\n\n\n\n<ul><li>Try the&nbsp;<a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;plugin (choose the “bleeding edge nightlies” option).</li><li>Or&nbsp;<a href=\"https://wordpress.org/wordpress-5.6-beta3.zip\">download the beta here&nbsp;(zip)</a>.</li></ul>\n\n\n\n<p>The current target for the final release is December 8, 2020. This is just&nbsp;<strong>five weeks away</strong>, so your help is needed to ensure this release is tested properly.</p>\n\n\n\n<p>Thank you to all of the contributors that tested the&nbsp;<a href=\"https://wordpress.org/news/2020/10/wordpress-5-6-beta-2/\">beta 2&nbsp;</a>development release and provided feedback. Testing for bugs is an important part of polishing each release and a great way to contribute to WordPress.</p>\n\n\n\n<h2><strong>Some Highlights</strong></h2>\n\n\n\n<p>Since&nbsp;beta 2,&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/query?status=closed&amp;changetime=10%2F28%2F2020..11%2F03%2F2020&amp;milestone=5.6&amp;group=component&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">20 bugs</a>&nbsp;have been fixed. Here is a summary of a few changes included in beta 3:</p>\n\n\n\n<ul><li>Added block patterns for Twenty Twenty (see&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/ticket/51098\">#51098</a>) and Twenty Nineteen (see&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/ticket/51099\">#51099</a>) themes.</li><li>Added theme support for navigation-widgets (see&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/ticket/51445\">#51445</a>).</li><li>Fixed incorrect slashes in the URL if the parent is empty for REST API (see&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/ticket/44745\">#44745</a>).</li><li>Added a test to Site Health to verify that the&nbsp;<code>Authorization</code>&nbsp;header is working as expected for Application Passwords (see&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://core.trac.wordpress.org/ticket/51638\">#51638</a>).</li><li>10 additional bugs fixed in the block editor (see&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://github.com/WordPress/gutenberg/pull/26588\">#26588</a>).</li></ul>\n\n\n\n<p>To see all of the features for each Gutenberg release in detail, check out the release posts:&nbsp;<a href=\"https://make.wordpress.org/core/2020/07/22/whats-new-in-gutenberg-july-22/\">8.6</a>,&nbsp;<a href=\"https://make.wordpress.org/core/2020/08/05/whats-new-in-gutenberg-august-5/\">8.7</a>,&nbsp;<a href=\"https://make.wordpress.org/core/2020/08/19/whats-new-in-gutenberg-august-19/\">8.8</a>,&nbsp;<a href=\"https://make.wordpress.org/core/2020/09/03/whats-new-in-gutenberg-2-september/\">8.9</a>,&nbsp;<a href=\"https://make.wordpress.org/core/2020/09/16/whats-new-in-gutenberg-16-september/\">9.0</a>,&nbsp;<a href=\"https://make.wordpress.org/core/2020/10/01/whats-new-in-gutenberg-30-september/\">9.1</a>, <a href=\"https://make.wordpress.org/core/2020/10/21/whats-new-in-gutenberg-21-october/\">9.2</a>, and <a href=\"https://github.com/WordPress/gutenberg/releases/tag/v9.3.0-rc.1\">9.3</a>.</p>\n\n\n\n<h2 id=\"block-76156b2b-0a52-4502-b585-6cbe9481f55b\">Developer notes</h2>\n\n\n\n<p id=\"block-3fe5e264-0a95-4f12-9a18-0cb9dc5955d1\">WordPress 5.6 has lots of refinements to the developer experience as well. To keep up, subscribe to the&nbsp;<a href=\"https://make.wordpress.org/core/\">Make WordPress Core blog</a>&nbsp;and pay special attention to the&nbsp;<a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">developers’ notes</a>&nbsp;for updates on those and other changes that could affect your products.</p>\n\n\n\n<h2 id=\"block-bc89fd56-47b0-439f-8e2c-4a642c80a616\">How to Help</h2>\n\n\n\n<p id=\"block-9d871099-ec49-446c-8322-9e49b7498c10\">If you think you’ve found a bug, you can post to the&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">Alpha/Beta area</a>&nbsp;in the support forums. We’d love to hear from you!</p>\n\n\n\n<p id=\"block-bd71c1d3-39d9-4b2a-8193-3486497b45fd\">If you’re comfortable writing a reproducible bug report,&nbsp;<a href=\"https://core.trac.wordpress.org/newticket\">file one on WordPress Trac</a>,&nbsp;where you can also find a list of&nbsp;<a href=\"https://core.trac.wordpress.org/query?status=new&amp;milestone=5.6&amp;group=component&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">known bugs</a>.</p>\n\n\n\n<p><em>Props to <a href=\'https://profiles.wordpress.org/hellofromtonya/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>hellofromtonya</a> for help and <a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a>  for final review.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"9234\";s: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:\"Fri, 29 Jan 2021 12:08:56 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 27 Jan 2021 18:27:09 GMT\";s:4:\"link\";s:63:\"<https://wordpress.org/news/wp-json/>; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";}}s:5:\"build\";s:14:\"20210129120756\";}', 'no');
  INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
  (132, '_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1611965336', 'no'),
  (133, '_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3', '1611922136', 'no'),
  (134, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1611965337', 'no');
  INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
  (135, '_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9', 'a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:61:\"\n	\n	\n	\n	\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"WordPress Planet\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://planet.wordpress.org/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:2:\"en\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:50:{i:0;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"WPTavern: WP Lookout Lets WordPress Users Track and Receive Notifications for Their Preferred Plugins and 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=108062\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:269:\"https://wptavern.com/wp-lookout-lets-wordpress-users-track-and-receive-notifications-for-their-preferred-plugins-and-themes?utm_source=rss&utm_medium=rss&utm_campaign=wp-lookout-lets-wordpress-users-track-and-receive-notifications-for-their-preferred-plugins-and-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:8074:\"<p class=\"has-drop-cap\"><em>Should WordPress notify users of plugin ownership changes?</em> That was the question that Ian Atkins asked two months ago. WP Tavern readers seemed to think it was a good idea, at least those who commented on our <a href=\"https://wptavern.com/should-wordpress-notify-users-of-plugin-ownership-changes\">coverage of it</a>. However, the original <a href=\"https://meta.trac.wordpress.org/ticket/5509\">Trac ticket</a> has not seen any movement since.</p>\n\n\n\n<p>There are real technical issues with automating the process. A change of ownership does not necessarily equate to a change of the plugin author. This is often the case when someone acquires a company and maintains the brand.</p>\n\n\n\n<p>Tracking such changes does not necessarily need to go through WordPress. Chris Hardie built a service called <a href=\"https://wplookout.com/\">WP Lookout</a> that notifies users of such changes and much more. It has also been available since August of 2020.</p>\n\n\n\n<p>&ldquo;WP Lookout watches for interesting changes to the WordPress themes and plugins that someone cares about,&rdquo; said Hardie. &ldquo;I created WP Lookout for professional WordPress developers, consultants, and site managers who want to stay more informed about the plugins and themes that they (and their clients) depend on.&rdquo;</p>\n\n\n\n<p>While WP Lookout faces the same challenges with plugin ownership changes, it does have an advantage. It also <a href=\"https://wplookout.com/2020/12/tracking-mentions-in-wordpress-news/\">tracks WordPress news organizations</a>, including WP Tavern and <a href=\"https://poststatus.com/\">Post Status</a>. Even if the ownership change is not reflected on the plugin&rsquo;s WordPress.org page, the story may be picked up in the news.</p>\n\n\n\n<p>Hardie launched the news-tracking feature in early December 2020. It includes the <a href=\"https://www.wordfence.com/blog/category/vulnerabilities/\">Wordfence vulnerabilities blog</a> and <a href=\"https://ithemes.com/category/wordpress-vulnerability-roundup/\">iThemes vulnerabilities roundup blog</a> as a part of the service&rsquo;s security notification system. The service also scans change logs for keywords related to security.</p>\n\n\n\n<p>Notifications do not stop there. The WP Lookout tracks plugin, theme, and core WordPress updates. It also supports several commercial plugins such as Advanced Custom Fields Pro, Gravity Forms, and WP Rocket.</p>\n\n\n\n<p>&ldquo;When we first decide to use a theme or plugin on a WordPress site, we hopefully research it thoroughly &mdash; code quality, ratings, support responsiveness, new release history, speed of security fixes, and so on &mdash; but once it&rsquo;s installed it&rsquo;s easy to neglect those important bits of &lsquo;health&rsquo; information over time,&rdquo; said Hardie. &ldquo;Auto-updates are great from many perspectives, but I think anyone who has had to manage and troubleshoot a non-trivial WordPress site over time knows that it&rsquo;s also important to stay aware of, for example, what&rsquo;s happening in the change log or whether ownership of a plugin has changed hands. But nobody wants to log in to wp-admin on a bunch of sites every week to gather that info.&rdquo;</p>\n\n\n\n<p>Hardie said WP Lookout will always have a robust free option for people who just want a daily email notification for a handful of plugins and themes. However, there are paid tiers for customers to access more features. They allow users to track more plugins and themes and get immediate alerts through email, RSS, Slack, or custom webhooks.</p>\n\n\n\n<p>&ldquo;The middle tier supports up to 50 themes/plugins, immediate email notifications, and a personalized RSS feed,&rdquo; he said. &ldquo;The Builder tier supports up to 200 themes/plugins and adds in Slack and custom webhook support along with the option to just get security-related notifications. With more real-world user feedback, we may adjust what&rsquo;s in each tier over time.&rdquo;</p>\n\n\n\n<p>All users get access to the Builder tier for a few weeks after signing up. After that, they must subscribe or stick with the free tier features.</p>\n\n\n\n<h2>How the Service Works</h2>\n\n\n\n<img />Single plugin tracking history.\n\n\n\n<p class=\"has-drop-cap\">WP Lookout allows users to search for and add a tracker for individual plugins. The service primarily relies on the public WordPress.org API for getting plugin and theme data. This is the same system that WordPress uses to check to see if updates are available.</p>\n\n\n\n<p>&ldquo;But it also goes beyond what the API offers,&rdquo; said Hardie. &ldquo;For example, there&rsquo;s no standard yet for theme authors to provide .ORG theme change logs, and so that information doesn&rsquo;t show up when you go to update a theme in wp-admin; you&rsquo;d have to go poking around in Trac or source files to find it. So WP Lookout follows the trail to the change log details and <a href=\"https://wplookout.com/2020/08/wordpress-theme-changelog-details/\">puts that right in front of you</a>.&rdquo;</p>\n\n\n\n<img />Active plugin trackers.\n\n\n\n<p>There is also a <a href=\"https://wordpress.org/plugins/wp-lookout/\">WP Lookout plugin</a> available in the plugin directory. It uses an API key, which users can get from the WP Lookout website. The plugin then lets the WP Lookout service know what plugins and themes are installed and adds them as trackers. Using the plugin is far more efficient than manually adding individual plugins and themes.</p>\n\n\n\n<p>For plugins and themes that are not on WordPress.org, the service uses custom update APIs provided by the third-party developers. If that is not sufficient, it uses webpage scraping. For news sources, it parses RSS feeds.</p>\n\n\n\n<p>&ldquo;It&rsquo;s been interesting to see the wide variety of ways that WordPress theme and plugin authors do or don&rsquo;t manage and present data publicly about their products,&rdquo; said Hardie. &ldquo;Some have API endpoints that return the same level of detail as the .ORG API, others have change log/version documents generated by some internal tools, and still others don&rsquo;t bother doing much at all. I think an argument could be made to standardize on something here for the long-run to help boost the culture of keeping software updated, even/especially if it eventually makes the need for a tool like WP Lookout obsolete.&rdquo;</p>\n\n\n\n<h2>The Future of WP Lookout</h2>\n\n\n\n<p class=\"has-drop-cap\">Hardie has no plans of sitting on what he has already built. One of the next goals is regularly adding new themes and plugins that are not on WordPress.org. This will mean connecting with development teams and figuring out how users can get notifications of things that often have no public APIs. The lack of standardization in the space could be a tough hurdle to jump.</p>\n\n\n\n<p>&ldquo;I have a long list of features I&rsquo;m planning to add, including things like integrating tracking GitHub repo releases, bringing some helpful data points from WP Lookout into the wp-admin interface, WordPress Packagist integration, allowing per-tracker Slack channel configurations, better internationalization, and better handling of change logs that theme/plugin authors chose to maintain outside of their .org code repositories,&rdquo; he said.</p>\n\n\n\n<p>Hardie does not want to get too far ahead of himself with feature ideas. He said he is excited to get more feedback from users about what they find useful. Currently, there are 80 users, which is publicly available data. WP Lookout maintains an <a href=\"https://wplookout.com/open/\">open data and financial transparency page</a>.</p>\n\n\n\n<p>&ldquo;Despite having paid options for more advanced users, I mostly think of this as a service I want to operate for the WordPress community, and I&rsquo;ll always have a robust set of free functionality,&rdquo; he said. &ldquo;I&rsquo;m also committed to participation in Five for the Future, bringing what I&rsquo;ve learned here back into improvements that might benefit all WordPress users, whether they take advantage of WP Lookout or not.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 28 Jan 2021 21:56:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:1;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:104:\"WPTavern: ElasticPress.io Service Considers Next Move after Elasticsearch Abandons Open Source Licensing\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110644\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:253:\"https://wptavern.com/elasticpress-io-service-considers-next-move-after-elasticsearch-abandons-open-source-licensing?utm_source=rss&utm_medium=rss&utm_campaign=elasticpress-io-service-considers-next-move-after-elasticsearch-abandons-open-source-licensing\";s: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:6933:\"<p>Elastic, makers of the search and analytic engine&nbsp;<a rel=\"noreferrer noopener\" href=\"https://www.elastic.co/what-is/elasticsearch\" target=\"_blank\">Elasticsearch</a>, have re-licensed its core product so that it is no longer open source. The company is moving new versions of both Kibana and Elasticsearch from the&nbsp;<a rel=\"noreferrer noopener\" href=\"https://www.apache.org/licenses/LICENSE-2.0\" target=\"_blank\">Apache 2.0-license</a>&nbsp;to be dual-licensed under the&nbsp;<a rel=\"noreferrer noopener\" href=\"https://www.mongodb.com/licensing/server-side-public-license\" target=\"_blank\">Server Side Public License (SSPL)</a>&nbsp;and the&nbsp;<a rel=\"noreferrer noopener\" href=\"https://github.com/elastic/elasticsearch/blob/0d8aa7527e242fbda9d84867ab8bc955758eebce/licenses/ELASTIC-LICENSE.txt\" target=\"_blank\">Elastic License</a>, which do not meet the <a href=\"https://opensource.org/osd\">Open Source Definition</a>. </p>\n\n\n\n<p>In a post titled &ldquo;<a href=\"https://www.elastic.co/blog/why-license-change-AWS\">Amazon: NOT OK &ndash; why we had to change Elastic licensing</a>,&rdquo; Elastic blames Amazon for the license change:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Our license change is aimed at preventing companies from taking our Elasticsearch and Kibana products and providing them directly as a service without collaborating with us.</p><p>Our license change comes after years of what we believe to be Amazon/AWS misleading and confusing the community &ndash; enough is enough.</p></blockquote>\n\n\n\n<p>Elastic claims AWS&rsquo;s behavior has &ldquo;forced&rdquo; the company to abandon its open source licensing, citing examples of what they perceive to be &ldquo;ethically challenged behavior.&rdquo; In 2019, Amazon created an Open Distro for Elasticsearch, and Elastic claims they used code copied by a third party from their commercial code, further dividing the community.</p>\n\n\n\n<p>As a result of the license change, Amazon <a href=\"https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/\">announced</a> its intention to officially fork Elasticsearch and Kibana, with plans to roll the forks into its Open Distro distributions:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Our forks of Elasticsearch and Kibana will be based on the latest ALv2-licensed codebases, version 7.10. We will publish new GitHub repositories in the next few weeks. In time, both will be included in the existing Open Distro distributions, replacing the ALv2 builds provided by Elastic. We&rsquo;re in this for the long haul, and will work in a way that fosters healthy and sustainable open source practices&mdash;including implementing shared project governance with a community of contributors.</p></blockquote>\n\n\n\n<p>The Open Source Initiative (OSI) <a href=\"https://opensource.org/node/1099\">reacted</a> to the news of the license change, calling the SSPL a &ldquo;fauxpen&rdquo; source license:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Fauxpen source licenses allow a user to view the source code but do not allow other highly important rights protected by the <a href=\"https://opensource.org/osd\">Open Source Definition</a>, such as the right to make use of the program for any field of endeavor. By design, and as explained by <a href=\"https://www.elastic.co/blog/licensing-change\">the most recent adopter</a>, Elastic, in a post it unironically titled &ldquo;<a href=\"https://www.elastic.co/blog/licensing-change\">Doubling Down on Open</a>,&rdquo; Elastic says that it now can &ldquo;restrict cloud service providers from offering our software as a service&rdquo; in violation of OSD6. Elastic didn&rsquo;t double down, it threw its cards in.</p></blockquote>\n\n\n\n<p>Elastic&rsquo;s license changes may affect a few companies in the WordPress ecosystem that are redistributing Elasticsearch as a commercial offering. <a href=\"https://10up.com/\">10up</a>, creators of <a href=\"https://wordpress.org/plugins/elasticpress/\">ElasticPress</a>, by far the most popular Elasticsearch plugin for WordPress, also runs the&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"http://elasticpress.io/\">ElasticPress.io</a>&nbsp;SaaS platform. More than 6,000 sites are using the open source plugin, but the company said these users will not be affected.</p>\n\n\n\n<p>&ldquo;No matter what this won&rsquo;t affect the EP plugin,&rdquo; 10up vice president of engineering Taylor Lovett said. &ldquo;I would say the news is definitely discouraging and not a great look for Elastic.&rdquo;</p>\n\n\n\n<p>10up <a href=\"https://wptavern.com/10up-unveils-elasticpress-io-elasticsearch-as-a-service-for-wordpress-sites\">launched</a> ElasticPress.io in 2017 and Lovett says it has become &ldquo;an active part of the business with a plethora of customers,&rdquo; and continues to grow. The company is currently seeking legal advice on how Elasticsearch&rsquo;s licensing change will affect the ElasticPress.io service. Since previous versions of Elasticsearch remain open source, the company has time to figure out a new way forward.</p>\n\n\n\n<p>&ldquo;Right now we really don&rsquo;t know what&rsquo;s going to happen,&rdquo; Lovett said. &ldquo;There is no rush for us to upgrade&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"http://elasticpress.io/\">ElasticPress.io</a>&nbsp;to Elasticsearch 7.11+ so we have plenty of time to decide how to address the issue.&rdquo;</p>\n\n\n\n<p>Lovett confirmed that 10up is considering using the Amazon fork as an option but has not  made a decision on the matter yet.</p>\n\n\n\n<p>&ldquo;I will say this does affect the end user in a way that they may end up having to choose between different flavors of Elasticserarch,&rdquo; Lovett said.<br /><br />&ldquo;For example, you may need to decide if you want the official Elastic distribution or if you want to go with AWS&rsquo;s fork.&rdquo;</p>\n\n\n\n<p>Unfortunately, for businesses that built services on top of redistributing the previously open source Elasticsearch, Elastic&rsquo;s creators have gone back on <a href=\"https://web.archive.org/web/20200120104750/https:/www.elastic.co/what-is/open-x-pack\">the promise they made in 2018</a> to never change the license of any of the Apache 2.0 code of Elasticsearch, Kibana, Beats, and Logstash projects.&nbsp;As a consequence, Amazon has emerged as the one to drive the truly open source option for Elasticsearch and Kibana for the future.</p>\n\n\n\n<p>&ldquo;Elastic&rsquo;s relicensing is not evidence of any failure of the open source licensing model or a gap in open source licenses,&rdquo; the OSI board of directors stated in a recent <a href=\"https://opensource.org/node/1099\">post</a> on the matter. &ldquo;It is simply that Elastic&rsquo;s current business model is inconsistent with what open source licenses are designed to do. Its current business desires are what proprietary licenses (which includes source available) are designed for.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 28 Jan 2021 20:25:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"WPTavern: Automattic Launches the Blank Canvas WordPress Theme for Building Single-Page Websites\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110986\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:237:\"https://wptavern.com/automattic-launches-the-blank-canvas-wordpress-theme-for-building-single-page-websites?utm_source=rss&utm_medium=rss&utm_campaign=automattic-launches-the-blank-canvas-wordpress-theme-for-building-single-page-websites\";s: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:7389:\"<img />Split Screen pattern from Blank Canvas.\n\n\n\n<p class=\"has-drop-cap\">On Monday, Automattic <a href=\"https://wordpress.com/blog/2021/01/25/building-single-page-websites-on-wordpress-com/\">announced its Blank Canvas theme</a> on WordPress.com. The goal is to allow end-users to build single-page websites, such as an &ldquo;about me&rdquo; or product landing page.</p>\n\n\n\n<p>Blank Canvas is a child theme of <a href=\"https://wptavern.com/exploring-seedlet-automattics-block-first-wordpress-theme\">Seedlet</a>, which Automattic&rsquo;s <a href=\"https://themeshaper.com/about/\">Theme Team</a> has been using as a launchpad. One example is its recently-released <a href=\"https://wptavern.com/automattic-releases-spearhead-a-seedlet-child-theme-aimed-at-podcasters-and-content-creators\">Spearhead</a> child theme. It also provided the foundational work for the recent Twenty Twenty-One default WordPress theme.</p>\n\n\n\n<p>One-page themes are nothing new. Theme builders have been releasing them for years in various forms.</p>\n\n\n\n<p>&ldquo;We&rsquo;ve been working on block patterns a lot lately, and it became clear that many of the single-page websites we come across daily &mdash; collections of links, newsletter signups, etc. &mdash; are basically just simple block patterns sitting on an otherwise blank page,&rdquo; said Kjell Reigstad, the lead developer on the theme. &ldquo;That being the case, it seemed like WordPress should be able to power these sorts of single-page sites pretty easily. Blank Canvas is an attempt to try that out.&rdquo;</p>\n\n\n\n<p>WordPress is not the ideal platform for the majority of one-page sites. Doing so includes setting up a database, installing the software, and keeping everything updated. The admin interface is not well-suited to those types of sites. WordPress is a content management system. One page is not enough content to need a full-blown CMS to manage. There simply is little upside for the average user to go through the hassle of doing this on even the cheapest of shared hosting.</p>\n\n\n\n<p>However, if you have a network where someone else, such as WordPress.com, takes out all the hassle of maintaining the backend and when it does not cost you a dime, WordPress suddenly makes more sense. It becomes an ideal platform for these types of sites.</p>\n\n\n\n<p>Frankly, I do not know why they have not pushed this concept sooner. Jason Schuller has made a go of it with Leeflets in the past. Since then, he and Philip Kurth have taken that idea further and launched <a href=\"https://wptavern.com/landing-kit-for-wordpress-maps-any-post-or-page-to-a-custom-domain\">WP Landing Kit</a>, which builds on the same concept of creating multiple single-page landing sites from one WordPress installation.</p>\n\n\n\n<p>In some respects, Blank Canvas offers a glimpse into Full Site Editing. It is almost a stepping stone or a small yet limited preview of things to come. The theme puts the entire design process into a single page and a single editor. Eventually, this will be extended to the whole website.</p>\n\n\n\n<p>&ldquo;I think that&rsquo;s a great way to think about it,&rdquo; said Reigstad. &ldquo;Full Site Editing is coming soon, but in the meantime, Blank Canvas lets you do just a little bit more with Gutenberg than you could before.&rdquo;</p>\n\n\n\n<h2>About the Theme</h2>\n\n\n\n<p class=\"has-drop-cap\">The theme is called <strong>Blank</strong> Canvas for a reason. Its <a href=\"https://blankcanvasdemo.wordpress.com/\">demo page</a> is literally a blank screen with a footer message. The idea is that the end-user designs their homepage &mdash; or their entire site in the case of a single-page website &mdash; via the block editor.</p>\n\n\n\n<p>For those who need a starting point, the theme comes packaged with six block patterns:</p>\n\n\n\n<ul><li>About Me</li><li>Links</li><li>Invitation</li><li>Split Screen</li><li>Card</li><li>Email Signup</li></ul>\n\n\n\n<img />Invitation block pattern.\n\n\n\n<p>Self-hosted WordPress users can install the theme too. It is currently awaiting review for the theme directory, but they can snag the ZIP file or SVN link from its <a href=\"https://themes.trac.wordpress.org/ticket/94482\">Trac ticket</a>. For those giving it a test, be sure to disable the title and tagline via the customizer so they do not appear on the front end. That is assuming you want to use the theme as intended. It will also work as a more traditional theme because the Seedlet parent theme covers all the necessary features.</p>\n\n\n\n<p>There are differences between the theme on WordPress.com and that submitted to the WordPress.org theme directory. The .ORG version has only four block patterns. The .COM version includes an additional Card pattern, which integrates with Automattic&rsquo;s Layout Grid plugin. The Email Signup pattern needs Jetpack&rsquo;s form feature.</p>\n\n\n\n<p>Simple conditional checks for Layout Grid or Jetpack before registering the patterns would suffice for users with those plugins installed. &ldquo;That&rsquo;s planned,&rdquo; said Reigstad of adding the missing patterns, &ldquo;but we just didn&rsquo;t implement it yet.&rdquo;</p>\n\n\n\n<img />Email Signup block pattern.\n\n\n\n<p>WordPress.com users have something else to look forward to. In November, the service <a href=\"https://wptavern.com/wordpress-com-drops-over-100-block-patterns-carving-a-path-the-design-community-should-follow\">launched over 100 patterns</a>. &ldquo;One of the nice things is that there are already a lot of patterns out there that seem ready-made for single-page websites,&rdquo; said Reigstad.</p>\n\n\n\n<p>He did say the team is working on bundling more patterns in the future. These may include more &ldquo;link in bio&rdquo; designs that expand on the one already in the theme today.</p>\n\n\n\n<h2>Pioneering Block-Friendly Themes</h2>\n\n\n\n<p class=\"has-drop-cap\">Several of the ideas available in this theme seemed to have started from the WordPress <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments repository</a>. It features block patterns similar in scope to the <a href=\"https://wptavern.com/carrd-like-theme-experiment-provides-a-glimpse-into-the-future-of-theming\">Carrd-like theme</a> Reigstad built last October.</p>\n\n\n\n<p>&ldquo;In general, building block-based themes helped redefine our idea of what a theme needed to be,&rdquo; he said. &ldquo;We&rsquo;d tended to think of a theme as a complicated piece of software that accounts for every scenario you throw at it: a blog, custom post types, category pages, search pages, the 404 page, etc.&rdquo;</p>\n\n\n\n<p>Reigstad said that the block-based themes paradigm has forced the Theme Team to start small. Because Full Site Editing is still in flux, its features not ready, the team has built proof-of-concept themes with limited functionality.</p>\n\n\n\n<p>&ldquo;The possibilities for block-based themes have grown considerably since then (as shown by TT1 Blocks, Q, Block-based Bosco, and others), but the early constraints helped spark ideas like that Carrd-inspired theme,&rdquo; he said. &ldquo;It turned out that you could build a pretty useful site with just a handful of blocks.</p>\n\n\n\n<p>&ldquo;That mindset definitely informed Blank Canvas &mdash; we started small, with just the functionality someone would need to build a single-page site. Since it&rsquo;s based on a full-featured theme (Seedlet), you can grow with it too.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Jan 2021 22:11:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"WPTavern: Plugin Team Draws a Line: Plugins Must Not Change WordPress’ Default Automatic Update Settings\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=111034\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:249:\"https://wptavern.com/plugin-team-draws-a-line-plugins-must-not-change-wordpress-default-automatic-update-settings?utm_source=rss&utm_medium=rss&utm_campaign=plugin-team-draws-a-line-plugins-must-not-change-wordpress-default-automatic-update-settings\";s: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:3110:\"<p>WordPress&rsquo; plugin team has published a <a href=\"https://make.wordpress.org/plugins/2021/01/26/reminder-plugins-must-not-interfere-with-updates/\">statement</a> regarding plugins making changes to users&rsquo; update services: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Unless your&nbsp;plugin&nbsp;has the&nbsp;<em>purpose</em>&nbsp;of managing updates, you&nbsp;<strong>must not</strong>&nbsp;change the&nbsp;defaults&nbsp;of WordPress&rsquo; update settings.</p><p>You&nbsp;<em>may</em>&nbsp;offer a feature to auto-update, but it has to honor the&nbsp;core&nbsp;settings. This means if someone has set their site to &ldquo;Never update any of my plugins or themes&rdquo; you are not to change those for them unless they opt-in and request it.</p></blockquote>\n\n\n\n<p>The statement was prompted by plugins overstepping this boundary, which, up until recently, has simply been understood but not explicitly forbidden. Mika Epstein said the practice &ldquo;destroys the faith users have in you to not break their sites.&rdquo; It also reflects poorly on WordPress as a whole when plugin authors abuse core features to serve their own interests.</p>\n\n\n\n<p>&ldquo;Sadly, this happened recently to a well used plugin, and the fallout has been pretty bad,&rdquo; Epstein said. </p>\n\n\n\n<p>She did not identify the plugin in question, but one particular incident that happened last month bears a strong likeness to this description. On December 21, 2020, the <a href=\"https://wptavern.com/all-in-one-seo-plugin-turns-on-automatic-updates-without-notifying-users-removes-functionality-in-latest-release\">All in One SEO plugin turned on automatic updates without notifying its users</a>, aside from a short, ambiguous note in the changelog.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>All in One SEO was active on more than 2 million WordPress sites when it rolled out this update. Many users were frustrated to discover that their sites had been updated without permission, despite having auto updates turned off for the plugin. The plugin&rsquo;s developers removed the auto updates wrapper&nbsp;functionality from the plugin earlier this month, in favor of letting WordPress handle updates.</p>\n\n\n\n<p>After this incident, those who were affected were left with questions. Should WordPress allow this practice? Should plugin developers be required to place a notice in the dashboard if they are going to flip automatic updates on? While many users are willing to trust WordPress core to do automatic updates in a safe way, some are not willing to extend that trust to plugin developers, whose quality of updates vary widely. The plugin team offering guidance and communication on this matter was absolutely necessary to deter aggressive plugin developers from destroying what is still a fragile trust in automatic updates.</p>\n\n\n\n<p>&ldquo;At this time, we have no plans to spell this out in a guideline,&rdquo; Epstein said. &ldquo;We do currently, regularly flag plugins that go outside their dictated (self defined) boundaries, and this is not a change. Please, respect your users.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Jan 2021 20:43:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"WPTavern: Jetpack Launches Customer Research Project to Improve the Plugin and Reduce User Frustration\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110995\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:249:\"https://wptavern.com/jetpack-launches-customer-research-project-to-improve-the-plugin-and-reduce-user-frustration?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-launches-customer-research-project-to-improve-the-plugin-and-reduce-user-frustration\";s: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:6244:\"<p>Jetpack&rsquo;s Design and Research Team is <a href=\"https://automattic.design/2021/01/26/were-all-ears/\">launching a new customer research panel</a> as part of an ongoing effort to collect feedback in advance of launching new features. They are allocating one day every month to talk with users:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>It&rsquo;s a small step toward an important goal of better understanding what our users need, seeing and hearing first hand where they are frustrated, and learning how Jetpack can work better for them.</p><p>The relationship benefits both sides. Our customers enjoy a sneak preview of features coming down the roadmap, and are empowered to help shape the product&rsquo;s future. And our design slash research team sees first hand, how our products perform with real folks using them.</p></blockquote>\n\n\n\n<p>Jetpack is recruiting customers for 45-minute long interviews on Zoom where they will preview some new designs and talk about proposed product improvements that are already in the works. In exchange, participants receive a $25 Amazon gift card.  </p>\n\n\n\n<p>This outreach effort may help in easing the periodic friction between Automattic and the larger WordPress community, which tends to emerge like pop-up storms on social media and quickly dissipate, but not without taxing onlookers&rsquo; good will. Although Jetpack is active on more than 5 million sites, and is marketed as &ldquo;the most popular WordPress plugin for just about everything,&rdquo; its team occasionally seems out of touch with users.</p>\n\n\n\n<p>One recent example of this happened when Matt Medeiros drew attention to the wording for the Jetpack Scan upsells that appear on the plugins page in the admin.  Specifically, people took issue with the claim that &ldquo;adding plugins can expose your site to security risks.&rdquo; While this is true, participants in the resulting heated discussion said it implies that Jetpack, the plugin that claims to do &ldquo;just about everything,&rdquo; is the only safe plugin. </p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Everyone: WordPress is amazing because you can use plugins! <br />Jetpack: Careful, it\'s a scary place that WordPress repo is.<br />Everyone: Didn\'t you come from .org? <br />Jetpack: Just buy my protection plan. <a href=\"https://t.co/5oqbsroqSA\">pic.twitter.com/5oqbsroqSA</a></p>&mdash; I podcast a lot&#127897; (@mattmedeiros) <a href=\"https://twitter.com/mattmedeiros/status/1352275821763948550?ref_src=twsrc%5Etfw\">January 21, 2021</a></blockquote>\n</div>\n\n\n\n<p>Some perceived it to be in violation of <a href=\"https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#11-plugins-should-not-hijack-the-admin-dashboard\">#11 of the Plugin Directory guidelines</a>, which states that plugins should not hijack the admin dashboard. The guideline also recommends avoiding advertising in the admin &ldquo;as it is generally ineffective,&rdquo; as well as frustrating for users who are not looking for additional complications while solving problems.</p>\n\n\n\n<p>This particular case was resolved after Automattic product designer Jeff Golenski took the community feedback to his team. They <a href=\"https://twitter.com/jeffgolenski/status/1352417067849428993\">updated the advertisement</a> to be less fear-inspiring regarding the WordPress plugin ecosystem.</p>\n\n\n\n<p>In another potent example of disconnect from the larger community, <a href=\"https://wptavern.com/jetpack-7-1-adds-feature-suggestions-to-plugin-search-results\">Jetpack 7.1 quietly introduced suggestions to the plugin search screen</a>. The update artificially inserted a search result into the first plugin card slot, identifying the corresponding Jetpack feature if one was available. Jetpack&rsquo;s module placement in the results subtly implied that other plugins were inferior options to its existing modules. Some of the modules advertised required an upgrade. The UI did not make it clear that the artificial search result was not coming from the plugin directory&rsquo;s algorithm. The Jetpack team claimed that it was designed to be a notice but its implementation was virtually indistinguishable from an advertisement.</p>\n\n\n\n<p>In a later release, Jetpack <a href=\"https://wptavern.com/jetpack-7-2-1-removes-promotions-for-paid-upgrades-from-the-search-screen\">removed all feature suggestions that previously advertised upgrades</a>, characterizing the mistake as &ldquo;an error in judgment.&rdquo; This kind of misstep could have easily been avoided if the feature had been presented to actual users in advance. User researchers could have asked, &ldquo;How would you like it if we put some of our paid upgrades in the top search spot when you are searching for a new plugin?&rdquo; </p>\n\n\n\n<p>Historically, the company has had a few rocky launches where it seemed some product teams did not consider the community&rsquo;s perception in their marketing approaches. Most recently, this was evident in the launch of WordPress.com&rsquo;s new&nbsp;<a href=\"https://wptavern.com/wordpress-com-rattles-freelancer-community-with-new-website-building-service-launch\">website building service</a>, which failed to include important information, i.e. that the intention was to refer business out. </p>\n\n\n\n<p>The new customer research panel is a strategic move for Automattic and should allow the company to avoid a lot more frustration and miscommunication around Jetpack. It could also be valuable as a means of testing potential marketing angles, beyond just specific features the team is developing.</p>\n\n\n\n<p>&ldquo;When you have a team continually connecting with their customers, you find that they start to become internal ambassadors for the users, helping to weave the user&rsquo;s voice into product and design conversations throughout the entire product design process.&rdquo; Automattic UX/Product Designer Yvonne Doll said in the announcment.</p>\n\n\n\n<p>If you want to help the Jetpack team realize these goals and become ambassadors for their users, visit the plugin&rsquo;s <a href=\"https://jetpackresearch.blog/\">user research blog</a> and sign up to participate in upcoming interviews. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 27 Jan 2021 02:33: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:5;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: WP Buffs Finalizes First Acquisition, Purchases WP EZI\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110796\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/wp-buffs-finalizes-first-acquisition-purchases-wp-ezi?utm_source=rss&utm_medium=rss&utm_campaign=wp-buffs-finalizes-first-acquisition-purchases-wp-ezi\";s: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:6915:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Earlier today, WP Buffs <a href=\"https://wpbuffs.com/wp-ezi-acqusition/\">announced that it had acquired WP EZI</a>, a WordPress maintenance and support service. It was a five-figure acquisition for 64 active subscriptions and 343 total customers. Paul Tselekidis, the former owner of WP EZI, is <a href=\"https://wpezi.com/joining-wp-buffs/\">stepping away from the project</a>.</p>\n\n\n\n<p>WP Buffs offers 24/7 WordPress website management. Its team works directly with website owners and startups. They also work with white-label partners in the WordPress space. Agencies, freelancers, and hosting companies resell the WP Buffs subscription services instead of hiring a global team of their own.</p>\n\n\n\n<p>This is the first acquisition for the company and was done through their new <a href=\"https://wpbuffs.com/acquisitions/\">Business Acquisition Unit</a>.</p>\n\n\n\n<p>For WP EZI users, nothing should change about how they use the service. &ldquo;The day-to-day of the folks at WP EZI (aside from Paul) will continue unchanged as they&rsquo;ve all decided to stay on board and are excited for this new chapter of the business,&rdquo; said Joe Howard, the Founder and CEO of WP Buffs. &ldquo;For the time being, they will continue to function as team members of WP EZI, although they&rsquo;ll, of course, be given a warm welcome as new members of the WP Buffs family.&rdquo;</p>\n\n\n\n<p>At the moment, none of the pre-acquisition WP Buffs staff will move over to any WP EZI projects or vice versa. The two brands will remain separate.</p>\n\n\n\n<p>&ldquo;Mostly, this is for current WP EZI subscription clients, as keeping them happy and unbothered is our top priority,&rdquo; said Howard.</p>\n\n\n\n<p>One change coming to WP EZI is that it will no longer offer new care plan subscriptions. The goal is to send those leads to WP Buffs. WP EZI will continue serving current care plan customers and handle one-off projects.</p>\n\n\n\n<p>&ldquo;The strength of WP Buffs is in our strong systems and scalable business model of selling and executing on subscription services,&rdquo; said Howard. &ldquo;That&rsquo;s why we&rsquo;ll continue to accept new care plans there and send all one-time requests to WP EZI. They have experience with this business model, so we&rsquo;re going to keep that team doing the work they&rsquo;ve proved to be strong at.&rdquo;</p>\n\n\n\n<p>Howard did not give much away in terms of long-term changes. He said that while they are mulling over some ideas, their priorities were a peaceful transition for WP EZI clients and learning from and helping the current team.</p>\n\n\n\n<p>&ldquo;Most of the benefits for WP Buffs come from acquiring an already profitable business and client base,&rdquo; he said. &ldquo;Furthermore, the acquisition allows us to funnel care plan leads into WP Buffs and more one-time work into WP EZI. These silos will allow each team to be more efficient since they&rsquo;ll be able to focus on their areas of strength.&rdquo;</p>\n\n\n\n<h2>On Acquisitions and Growth</h2>\n\n\n\n<p class=\"has-drop-cap\">On the low end, the deal was likely at least mid to upper-five figures. We know that it was a five-figure acquisition. There were 64 active customers with an $87 per month subscription or more. This also assumes a consistent active subscription count for the last year or so. This is speculation but should provide some low ballpark numbers for others looking to sell a WordPress-related business.</p>\n\n\n\n<p>While Howard did not provide an exact figure, his company provided far more information than is typical of business acquisitions in the WordPress ecosystem. Often, these deals are made only with an agreement that neither party share the sale price. The transparency from WP Buffs should come as a breath of fresh air to other small business owners. It can be overwhelming venturing into a first acquisition from either end.</p>\n\n\n\n<p>One of his goals is to be transparent with how WP Buffs is run. His <a href=\"https://wpbuffs.com/2020-year-in-review/\">2020 year in review</a> post is lengthy, but he does not hold back on mistakes and successes. It provides a lot of insight that other business owners can learn from.</p>\n\n\n\n<p>Howard has some experience scaling businesses beyond that $10,000 &ndash; $15,000 monthly recurring revenue (MRR) spot, which is where some small businesses begin to plateau. I asked him to share his experience with other business owners.</p>\n\n\n\n<p>&ldquo;WP Buffs now does $100,000+ MRR,&rdquo; he said. &ldquo;That means we don&rsquo;t have the same issues as a care plan company at the scale of WP EZI &mdash; and if we do, we can pay to make those challenges go away.&rdquo;</p>\n\n\n\n<p>With WP Buffs now in control of the WP EZI brand, they can dedicate funding where needed and use their leadership and management where needed. Because their team has been here before, it should provide the experience to push past any hurdles.</p>\n\n\n\n<p>&ldquo;The reality here is just an economics of scale,&rdquo; said Howard. &ldquo;&lsquo;Bigger&rsquo; companies can simply flex a little more muscle to get rid of roadblocks. Plus, they have more financial flexibility to experiment and get things wrong to find that one thing that makes the difference when it comes to growth.&rdquo;</p>\n\n\n\n<p>He wrapped up his advice by saying that businesses should focus on their subscription metrics:</p>\n\n\n\n<ul><li>Develop 1-2 predictable, lead acquisition channels and grow those (increase MRR growth from new sales).</li><li>Get a ton of client feedback and make fast adjustments to keep them happy (lower churn).</li><li>From the client feedback, implement new features, offerings, value to current clients so they&rsquo;ll stay with you longer and tell others about you (increase expansion revenue and lifetime value).</li></ul>\n\n\n\n<p>&ldquo;One basic piece of advice is it&rsquo;s never too early to start thinking about selling, even if it&rsquo;s not on your roadmap,&rdquo; said Howard. &ldquo;Whether you ever want to sell your business or not, the things that make the kind of business people want to purchase are the same things that simply make it a good business, so why not do them?&rdquo;</p>\n\n\n\n<p>Howard and Tselekidis had an <a href=\"https://wpmrr.com/podcast/paul-kidis-wp-ezi/\">open and honest conversation</a> about the acquisition on the WPMRR podcast. Some of it is personal, but it provides a glimpse behind the curtain of a WordPress business sale.</p>\n\n\n\n<p>Tselekidis talked about spreading himself too thin among his various projects in the podcast. After a self-analysis and reevaluating his interests, he decided to find a new home for WP EZI. This will allow him to focus on and pursue other goals. &ldquo;It&rsquo;s time to move on; like it&rsquo;s my time,&rdquo; he said of continuing work that he was not as passionate about. &ldquo;I don&rsquo;t want to do a disservice by my clients.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 26 Jan 2021 21:41:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:6;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"Matt: Revue Joins Twitter\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://ma.tt/2021/01/revue-joins-twitter/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"https://ma.tt/2021/01/revue-joins-twitter/\";s: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:591:\"<p>Very excited to share the <a href=\"https://blog.twitter.com/en_us/topics/company/2021/making-twitter-a-better-home-for-writers.html\">news that Revue is joining Twitter</a>. I’m a huge fan of the idea of better newsletters and <a href=\"https://automattic.com\">Automattic</a> was the largest investor in <a href=\"https://www.getrevue.co/\">Revue</a>. I’m looking forward to seeing what the very talented team will do as part of the Twitter network. Also many thanks to <a href=\"https://kk.org\">Kevin Kelly</a> and <a href=\"https://om.co\">Om</a> for introducing me to Revue early on. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 26 Jan 2021 18:43:18 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"WPTavern: WordPress Roadmap Update: Full-Site Editing Targeted for 5.8 Release in June 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:30:\"https://wptavern.com/?p=110884\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:225:\"https://wptavern.com/wordpress-roadmap-update-full-site-editing-targeted-for-5-8-release-in-june-2021?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-roadmap-update-full-site-editing-targeted-for-5-8-release-in-june-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:3700:\"<p>WordPress core contributors are pushing forward on an ambitious plan to land full-site editing in core before the end of the year. Josepha Haden Chomphosy, the open source project&rsquo;s executive director, published an <a href=\"https://make.wordpress.org/updates/2021/01/21/big-picture-goals-2021/\">updated roadmap</a> for 2021 that aims to get an MVP of full-site editing (FSE) in the Gutenberg plugin by April, 2021. FSE v1 would then be on track for shipping with WordPress 5.8, which is anticipated in June, 2021.</p>\n\n\n\n<table><tbody><tr><th>5.7&nbsp;</th><td>April 2021 &ndash; <strong>MVP for FSE in Gutenberg plugin</strong></td></tr><tr><th>5.8</th><td>June 2021 &ndash; <strong>&nbsp;v1 in Core</strong></td></tr></tbody></table>\n\n\n\n<p>Chomphosy defined the scope of FSE as &ldquo;the ability to edit all elements of a site using Gutenberg blocks&rdquo; and said it will include &ldquo;all in-progress features designed to help existing users transition to Gutenberg as well.&rdquo;</p>\n\n\n\n<p>When asked what would be considered an MVP of full-site editing, Chomphosy pointed to <a href=\"https://github.com/WordPress/gutenberg/issues/24551\">a GitHub issue</a> that contributors are using for tracking all the milestones associated with the project. Part of the infrastructure and UI is marked as complete, as well as browsing between pages, templates, and template parts. Styling, theme blocks, the query block, and the navigation block still need more work. More progress may have been made but the tracking issue has not been updated since December 19, 2020. </p>\n\n\n\n<p>Dipping into the <a href=\"https://make.wordpress.org/core/2021/01/22/editor-chat-summary-20th-january-2021/\">notes</a> from the recent editor meetings shows a steady stream of FSE improvements, which presumably will coalesce into an MVP in approximately five weeks. Chomphosy&rsquo;s announcement avoided explicit promises regarding what features are expected at that time.  </p>\n\n\n\n<p>Related projects like the widgets and navigation block editors have new dedicated Slack channels for those interested in following and contributing: </p>\n\n\n\n<ul><li><a rel=\"noreferrer noopener\" href=\"https://wordpress.slack.com/archives/C01D71823PB\" target=\"_blank\">#feature-widgets-block-editor</a></li><li><a rel=\"noreferrer noopener\" href=\"https://wordpress.slack.com/archives/C01KDAZJMQ9\" target=\"_blank\">#feature-navigation-block-editor</a></li></ul>\n\n\n\n<p>If you have questions about where FSE is headed, an upcoming Gutenberg Times Live Q&amp;A episode titled &ldquo;<em>Updates on WordPress Site-Editor (FSE) and Themes</em>&rdquo; will feature a panel of people who are actively contributing in these areas. It includes Carolina Nymark, author of <a href=\"https://fullsiteediting.com/\">a course on full site editing and block based themes</a>, Ari Stathopoulos, core contributor and author of the first block-based theme in the repository, and Anne McCarthy, who is managing the FSE outreach experiment. </p>\n\n\n\n<p>The episode will air live on Friday, January 29th, 2021, at 11AM EST, hosted by Birgit Pauli-Haack, curator of the <a href=\"https://gutenbergtimes.com/\">Gutenberg Times</a>. <a href=\"https://us02web.zoom.us/webinar/register/9716061492351/WN_vtNXZ0zTTs2S0S98X0Y9og\">Registration</a> for the event is free. Pauli-Haack plans to cover all the latest updates on full-site editing, block-based themes, and global styles. The panel will also touch on the navigation and widget screens, as well as what features will most likely land in WordPress 5.7. Viewers can bring questions and participate via Zoom and YouTube live. The episode will be recorded and shared afterwards with a transcript and resources.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 26 Jan 2021 03:16:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:81:\"WPTavern: Jump-Start a Year’s Worth of Content via the Launch With Words 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=110800\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:201:\"https://wptavern.com/jump-start-a-years-worth-of-content-via-the-launch-with-words-plugin?utm_source=rss&utm_medium=rss&utm_campaign=jump-start-a-years-worth-of-content-via-the-launch-with-words-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:8435:\"<p class=\"has-drop-cap\">On Sunday, Bridget Willard announced her latest project, <a href=\"http://launchwithwords.com\">Launch With Words</a>. In collaboration with Ronald Huereca, who performed the development work, they built a plugin that helps clients jump-start routine, monthly blog posts. In the future, there will be premium &ldquo;content packs&rdquo; that include content for various industries.</p>\n\n\n\n<p>The Launch With Words plugin is essentially a JSON importer for blog posts. The plugin itself is simple. However, the idea is what makes this plugin special.</p>\n\n\n\n<p>&ldquo;The audience is small business owners,&rdquo; said Willard. &ldquo;So many of us in the WordPress ecosystem are overeducated. We are annoyed that clients don&rsquo;t know how to do X, Y, and Z. But that&rsquo;s not their job; it&rsquo;s ours.&rdquo;</p>\n\n\n\n<p>Willard wrote starter content for both the Twenty Nineteen and Twenty Twenty default WordPress themes. She said it occurred to her that theme starter content is great, but why was no one tackling this for blog posts?</p>\n\n\n\n<p>&ldquo;This plugin comes from something I&rsquo;ve been saying to friends for years, &lsquo;launch with words; get paid faster,\'&rdquo; she said. &ldquo;<em>Lorem ipsum</em> is such a pain. Seriously. As someone who partners with WordPress agencies and freelancers to write copy for website launches, placeholder text is my nemesis.&rdquo;</p>\n\n\n\n<p>Willard <a href=\"https://bridgetwillard.com/\">runs her own business</a>, which offers social media management, copywriting, consulting, and business coaching. She is a marketing consultant who has been writing for the web since 2001.</p>\n\n\n\n<p>&ldquo;I was a secretary by trade with a background in accounts receivables and collections,&rdquo; she said. &ldquo;After I earned my teaching credential, I spent a year teaching junior high and high school math before I realized I didn&rsquo;t like parents. But hey, that bachelor&rsquo;s degree isn&rsquo;t wasted. I decided to go back to office work and landed in accounting (hello, algebra). I excelled in accounts receivable and collections but was at the top of my salary range.&rdquo;</p>\n\n\n\n<p>She left the construction industry in 2015 and began working for an advertising agency. During this time, she helped build the GiveWP brand. She also led the WordPress Marketing Team for two years.</p>\n\n\n\n<h2>How the Plugin Works</h2>\n\n\n\n<img />Importing content with the Launch With Words plugin.\n\n\n\n<p class=\"has-drop-cap\">Launch With Words simply imports content. On its own, it does nothing else. Willard provides a downloadable JSON file via the Launch With Words website. This &ldquo;<a href=\"https://bridgetwillard.com/downloads/launch-with-words-starter-content-pack/\">starter pack</a>&rdquo; is available for free to everyone. It includes 12 draft blog posts to keep users blogging on their site for the next year.</p>\n\n\n\n<p>While it is geared toward freelancers and agencies working with small business owners, anyone can use the plugin and starter pack. If you are having trouble pushing out content regularly, the monthly prompts could be the injection you need to get the creative juices flowing.</p>\n\n\n\n<p>Each draft post includes a topic theme, topic type, and blog checklist. The topic theme is centered on usual events or holidays that match the month of the year. For example, the following is the theme for May:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Topic Theme: Summer is around the corner and, if your business is seasonal, you may have a bit of extra time or be swamped. It generally depends on your sales cycle.</p><p>This is a great time to go to your inspiration journal and look for a case study that can be written. Get the content published before people start going on vacations and forget about hiring a small business.</p></blockquote>\n\n\n\n<p>Just pull up each month&rsquo;s draft post, follow the topic, and go from there.</p>\n\n\n\n<img />Draft blog post for December.\n\n\n\n<p>Willard says that the plugin builds off the services she offers. &ldquo;This plugin absolutely solves the repeated issues I encounter with people &mdash; namely, &lsquo;What do I write about?\'&rdquo;</p>\n\n\n\n<p>She has not started using the Launch With Words plugin with her clients yet. In the past, she has used the <a href=\"https://bit.ly/BridgetWebQuestions\">Website Content Questionnaire</a>, a tool she built that others can copy to their Google Drive for free.</p>\n\n\n\n<p>&ldquo;What makes web copy great is having a bit of the backstory about people,&rdquo; she said. &ldquo;What makes them different? Do they like hockey? Did they start working in fast food? Are they building sites for the healthcare industry?&rdquo;</p>\n\n\n\n<h2>Premium Content Packs</h2>\n\n\n\n<p class=\"has-drop-cap\">Willard will begin offering premium content packs soon. Each will come with 12 fully-written blog post drafts for each month of the year, catering to specific industries. She plans to launch these individual packs at $497.</p>\n\n\n\n<p>&ldquo;I get asked how I come up with prices often,&rdquo; she said. &ldquo;Because I look at websites and products and SaaS services constantly, pricing is now intuitive to me. It&rsquo;s pretty easy for a developer or a small business to throw down $500 knowing it will give them content for a year. It&rsquo;s a crazy low price. I&rsquo;m not a fan of the word &lsquo;cheap.&rsquo; But this is buying in bulk. This is the Costco model.&rdquo;</p>\n\n\n\n<p>The blog posts should range between 300 and 500 words, a service in which Willard would generally charge $200.</p>\n\n\n\n<p>&ldquo;Anyone can tweak the copy to localize it or make it their own,&rdquo; she said. &ldquo;Before you ask, the only thing worse than duplicate content is no content. It&rsquo;s not novel to offer content; what&rsquo;s novel is to offer content that lives in a blog post. It&rsquo;s not an RSS feed from a syndication service that you can&rsquo;t edit. It&rsquo;s amazing how much franchises pay for boring content to distribute to their networks. Any business should have access to quality content that they can localize.&rdquo;</p>\n\n\n\n<p>One has to wonder how Willard could pace herself and produce quality content for these premium packs. However, she is no stranger to the writing process. She has published several books, writing four in the past year.</p>\n\n\n\n<p>&ldquo;I write to teach,&rdquo; she said. &ldquo;If you boil my essence down, I am a teacher. A few people have encouraged me to publish books. I have two Christian-based books out on Amazon that I did on Lulu.com, but it was so painful, I didn&rsquo;t bother.&rdquo;</p>\n\n\n\n<p>It was not until she talked with Nathan Ingram, a business coach in the WordPress space, at WordCamp Seattle in 2019 that she decided to give things another go. He introduced her to Kindle Direct Publishing, a driving factor behind her more recent publishing success.</p>\n\n\n\n<p>&ldquo;So I took a blog series idea, &lsquo;Dysfunctional Love Songs,&rsquo; and wrote and published that book in April as my COVID project. In October, &lsquo;Keys to Being Social,&rsquo; my life&rsquo;s work was published. &lsquo;The Definitive Guide to Twitter Marketing&rsquo; was written on a Sunday in January. My fourth book, &lsquo;How to Market Your WordPress Plugin&rsquo; is with my editor and will be published this year.&rdquo;</p>\n\n\n\n<p>Willard said these writing projects have helped her stay focused on positive things during the Covid-era.</p>\n\n\n\n<p>&ldquo;Otherwise, it&rsquo;s easy for things to turn dark &mdash; if we&rsquo;re all going to die, why pay off my credit cards? You know? I can&rsquo;t just sit around watching Netflix. I do, but I need an outlet.&rdquo;</p>\n\n\n\n<p>She does not plan on going it alone for all of the premium content packs. She is already in talks with writers in other fields who would be better suited to the specific subject matter. However, Willard will lean on her construction-related expertise to build some of the packs.</p>\n\n\n\n<p>&ldquo;The best advice writers give is that you should write what you know,&rdquo; she said. &ldquo;It&rsquo;s the first chapter in Anne Lamott&rsquo;s &lsquo;Bird by Bird.&rsquo; I&rsquo;ve been writing about construction for 20 years. It won&rsquo;t require very much research. I mean, if I can sit down on a Sunday and write 7,000 words on Twitter for that book, I&rsquo;m pretty sure I can write 12 blog posts fairly soon.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 25 Jan 2021 21:57:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"WPTavern: Ask the Bartender: How To Bulk Convert Classic WordPress Posts To 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=110841\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/ask-the-bartender-how-to-bulk-convert-classic-wordpress-posts-to-blocks?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-how-to-bulk-convert-classic-wordpress-posts-to-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:5513:\"<blockquote class=\"wp-block-quote\"><p>I was wondering if you could help me. I want to convert all of my old posts (about 600) to Gutenberg blocks. Do you know an easy way to do that?</p><p>Philip</p></blockquote>\n\n\n\n<p class=\"has-drop-cap\">I often get these short questions via private messages. I always try my best to help other WordPress users whenever I can. This was an easy solution in Philip&rsquo;s case. After a quick chat, he actually learned that he did not need to migrate his posts to the block system. I thought it would be best to open this topic to a wider audience. Maybe it would help someone else along the way.</p>\n\n\n\n<p>There is currently an <a href=\"https://github.com/WordPress/gutenberg/issues/18645\">open ticket</a> on the Gutenberg repository for a bulk converter. It has sat dormant until a few days ago. The primary argument for including this feature in the plugin and eventually WordPress itself is that the lack of this option is an obstacle for newcomers to the block editor.</p>\n\n\n\n<p>I disagree with the notion that it is any sort of obstacle for block-editor adoption. There does not seem to be a massive call for the feature in the WordPress support forums. Web searches do not pull up too many support queries for it. It seems to be a niche use case. Or, in some cases, there is a simple misunderstanding that end-users need to do any sort of conversion or migration at all.</p>\n\n\n\n<p>However, the biggest reason it is a non-obstacle is that posts written in the classic editor are still basic HTML. Regardless of the editor, older content will output just fine on the front end, at least in most cases.</p>\n\n\n\n<p>The first question anyone should ask before deciding on bulk converting their old posts to the newer block format is whether they should do it at all. The answer for the majority of users will simply be <em><strong>no</strong></em>. There are few reasons to do so.</p>\n\n\n\n<p>Doing a mass conversion like this, especially with hundreds or more posts, is subject to broken sites. I have done enough single-post updates to know that the process does not always go smoothly. Sometimes, I need to touch up something here or do some manual changes there. On a large scale, there really is no way to know what got broken until you test every single post or page on the site. In some cases, everything is OK. In others, it is a nightmare.</p>\n\n\n\n<p>If you are thinking of going down the bulk-conversion route, make a backup first. There is a good chance that you will need it. You should also test this on a staging site.</p>\n\n\n\n<p>My recommendation for most users is to convert posts on an as-needed basis. I like to make the switch any time I edit an old post. The only reason I convert them is that I prefer working with the block editor over classic.</p>\n\n\n\n<p>Posts written in the old editor will be in the Classic block. After selecting the block that houses the content, I hit the &ldquo;Convert to blocks&rdquo; button in the block toolbar. I do a quick check of anything that might need to be fixed before hitting the update button.</p>\n\n\n\n<img />&ldquo;Convert to blocks&rdquo; button for the Classic block.\n\n\n\n<p>In most cases, there is no reason to convert old posts to blocks except when you are actually editing those posts.</p>\n\n\n\n<p>Despite claims that things will &ldquo;just work&rdquo; when switching to the block editor, that is not the day-to-day reality of all WordPress users. Some of the biggest reasons I have seen to bulk convert are around theme design issues. For example, the block system made some fundamental changes to image markup. If your theme handles left and right-aligned images added via the block editor but breaks down on your old posts, bulk converting may be an option. However, the first course of action should be checking in with your theme author about adding support for the classic markup.</p>\n\n\n\n<p>There are likely numerous other edge cases. Bulk converting posts is an invasive operation that can only be reverted by restoring a pre-conversion backup. It should be a last resort.</p>\n\n\n\n<p>If you are at the point where you know you need to convert all your old posts, there are a few options available.</p>\n\n\n\n<p>The <a href=\"https://wordpress.org/plugins/bulk-block-converter/\">Bulk Block Converter</a> plugin is likely the most-used solution at the moment. Organic Themes released it a little over a year ago but has only updated it once. User reviews have been mixed. A few of the problems seemingly stem from WordPress &mdash; the plugin extends the core WordPress block converter used in single posts.</p>\n\n\n\n<p>For those with clients who want to find a middle ground between bulk conversion and having the client manually convert their old posts, 10up&rsquo;s <a href=\"https://github.com/10up/convert-to-blocks\">Convert to Blocks</a> plugin might be the right solution. It converts posts on the fly, only making changes when a user opens the post-editing screen.</p>\n\n\n\n<p>Fr&auml;nk Klein is also working on a PHP-based bulk converter plugin named <a href=\"https://bulkconverttoblocks.com/\">Bulk Convert to Blocks</a>. It is currently in the development stage and not ready for use on live sites. It offers a screen in the WordPress admin to perform the conversion and will continue working in the background if the user leaves the page. Because it runs via PHP, developers can extend it with custom actions and filters. It also provides a WP CLI command for those who prefer to work from the command line.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Jan 2021 22:39:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"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:66:\"WPTavern: TasteWP Spins Up Free WordPress Testing Sites in Seconds\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110274\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/tastewp-spins-up-free-wordpress-testing-sites-in-seconds?utm_source=rss&utm_medium=rss&utm_campaign=tastewp-spins-up-free-wordpress-testing-sites-in-seconds\";s: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:5318:\"<p><a href=\"https://tastewp.com/\">TasteWP</a> is a newcomer among online WordPress sandboxing solutions. The site allows users to spin up a new WordPress instance in a matter of seconds. Web-based sandboxes like these have been popular for a long time, since they are convenient to fire up and destroy when performing a quick test on a plugin or theme. It&rsquo;s easier than maintaining a local development environment, which many casual WordPress users have not taken the time to set up. </p>\n\n\n\n<p>TasteWP&rsquo;s temporary testing sites are hosted for 48 hours for non-logged-in users and 7 days for those who are logged in. The one-click setup gives you a random site URL and login credentials.</p>\n\n\n\n<img />\n\n\n\n<p>The free sites are limited to 220MB per instance. A successful set-up notice is displayed in the dashboard with information on when the site will be automatically deleted. TasteWP limits non-logged-in users to creating 2 sites and the limit is 6 for logged-in users. They can be removed or added within the site manager. </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>When creating a new site, the Advanced Options allows users to set up multisite, select a PHP version, WordPress version, and choose from a number of advanced configuration options and pre-installed extensions. The PHP version can also be changed later within the site manager.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>TasteWP is reminiscent of the now defunct <a href=\"https://wptavern.com/poopy-life-lets-you-create-free-unlimited-wordpress-test-installs\">poopy.life</a> service. In addition to the unsavory and unforgettable name, poopy.life was laden with obtrusive upgrade ads that floated across the screen periodically. TasteWP takes a different route for promotion and includes three of its plugins pre-installed on the default testing sites.</p>\n\n\n\n<p>TasteWP is run by <a href=\"https://inisev.com/\">Inisev</a>, a 15-person company that has been developing&nbsp;WordPress&nbsp;plugins for four years.</p>\n\n\n\n<p>&ldquo;Our key motivator for starting&nbsp;TasteWP&nbsp;was a) scratching our own itch (we needed a platform ourselves to try out new plugin versions on different&nbsp;WP/PHP version combinations) and b) promoting our products,&rdquo; Inisev co-founder Nicolas Ahmann said.</p>\n\n\n\n<p>&ldquo;Having said that, if there is enough demand (and there seems to be), we&rsquo;ll also offer very affordable premium plans for non-expiring instances with bumped space soon.&rdquo;</p>\n\n\n\n<p>Ahmann said the team is currently funding their projects from their own pockets as well as a few private investors.</p>\n\n\n\n<p>&ldquo;We had some VCs knock at our door recently, and while we don&rsquo;t rule out taking them on board at some point in the future, we feel quite comfortable with our current approach where we grow organically (i.e. without too much ad spending),&rdquo; Ahmann said. &ldquo;I&rsquo;m sure, if we had taken on a lot of capital a few years ago, we would have spent a lot of marketing budget on products which weren&rsquo;t ready at the time. Instead, we were forced to make the products better. Limited budgets sharpen your mind immensely.&rdquo;</p>\n\n\n\n<p>Ahmann said the company has several enhancements planned for TasteWP, but they don&rsquo;t want to make the product more complicated to use. </p>\n\n\n\n<p>&ldquo;We developed a Linux application which copies exactly the same moves as user would do to create a website, except that we&rsquo;re omitting the front-end and graphics rendering parts which makes it much easier to process by the computer,&rdquo; he said. &ldquo;Also we inject anything that is needed into the database directly. That allows us to create those sites so fast without preparing them before (but still fully customized for each user).&rdquo;</p>\n\n\n\n<p>The company is planning to enable users to call specific URLs, such as&nbsp;<a rel=\"noreferrer noopener\" href=\"https://tastewp.com/?themeslug=slug-of-theme\" target=\"_blank\">https://tastewp.com?themeslug=slug-of-theme</a>,&nbsp;which would spin up an instance with that theme or plugin already installed. This would allow theme and plugin creators to share the link with their potential users/customers so that they can play around themselves. </p>\n\n\n\n<p>Localization is also a high priority for future TasteWP enhancements, since the company is based in Europe where many languages are spoken. </p>\n\n\n\n<p>&ldquo;We always felt that it doesn&rsquo;t get the attention as it needs, considering that approximately<a href=\"https://w3techs.com/technologies/overview/content_language\"> 40% of websites are not in English,</a>&rdquo; Ahmann said. &ldquo;It&rsquo;s often just DIY people (not devs) who are trying to create their websites. We always encourage them to learn English (as it&rsquo;s the world&rsquo;s&nbsp;language). But imagine you grew up in Turkey, for example. Nobody around you speaks English &ndash; the teachers in schools only speak it in a broken way. In those cases it&rsquo;s key that people can take their first&nbsp;WordPress&nbsp;steps in their language, and what&rsquo;s easier to&nbsp;do&nbsp;so than spinning up an instance with one click on&nbsp;TasteWP&nbsp;which is in your language? Long story short: we&rsquo;ll keep translating it into (many) more languages.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 Jan 2021 20:47:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:11;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:119:\"WPTavern: Gutenberg 9.8 Brings Rounded Borders To the Group Block and Moves the Site Editor Canvas Into an Inline Frame\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110768\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:283:\"https://wptavern.com/gutenberg-9-8-brings-rounded-borders-to-the-group-block-and-moves-the-site-editor-canvas-into-an-inline-frame?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-8-brings-rounded-borders-to-the-group-block-and-moves-the-site-editor-canvas-into-an-inline-frame\";s: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:6699:\"<p class=\"has-drop-cap\">Gutenberg 9.8 <a href=\"https://make.wordpress.org/core/2021/01/20/whats-new-in-gutenberg-9-8-20-january/\">launched yesterday</a> with a few minor UI improvements. The development team added an initial implementation for border-radius support for the Group block that theme authors can opt into. They also moved the site editor into an iframe element to remove CSS conflicts from the global admin styles.</p>\n\n\n\n<p>Those who have been testing Full Site Editing should be pleased that they will no longer need to deal with the seemingly never-ending creation of auto-drafts for templates and template parts. <em>Good riddance.</em> They would have inevitably caused user confusion in the long run. The change took around a <a href=\"https://github.com/WordPress/gutenberg/pull/27910\">month of discussion and work</a>, but it reduced a complex and fragile process into a more stable system for the long term.</p>\n\n\n\n<p>While the previous plugin release saw barely more than a handful of bug fixes, version 9.8 jumped back to over two dozen. A Gutenberg update without at least that many just does not feel right.</p>\n\n\n\n<h2>Minor UI Improvements</h2>\n\n\n\n<p class=\"has-drop-cap\">The latest version of the plugin improves the UI when working with the Spacer block. When a user selected the block in the past, it appeared as a light gray rectangle. Now, it is <a href=\"https://github.com/WordPress/gutenberg/pull/28103\">semi-transparent. </a>This allows whatever is in the background, such as the Cover block with a background image, to show. This change should help users more easily make size adjustments in cases where viewing the background is necessary.</p>\n\n\n\n<img />Semi-transparent Spacer block when selected.\n\n\n\n<p>While I hope the Spacer block will eventually die a slow and agonizing death as it is replaced by more appropriate margin and padding block options, this change does help in the interim.</p>\n\n\n\n<p>In a follow-up to the UI improvements in Gutenberg 9.7, work on block variations continues. Variations are when one block is used as the foundation to create multiple variations of the same block. The most common example is the Embed block, which has YouTube, Vimeo, and other variations. Before 9.7, these variations shared the same generic icon, name, and description in the block inspector and navigation instead of the variation-specific information.</p>\n\n\n\n<p>Gutenberg 9.8 builds on the trend of using the variation&rsquo;s data where it makes sense. The block switcher (transform) button in the editor toolbar now <a href=\"https://github.com/WordPress/gutenberg/pull/27903\">displays the variation&rsquo;s icon</a>.</p>\n\n\n\n<img />Variation icon in use in the block switcher.\n\n\n\n<p>It is a small change, but it shows the development team&rsquo;s continued devotion to polishing the editor interface.</p>\n\n\n\n<h2>Loading the Site Editor Canvas in an iframe</h2>\n\n\n\n<p class=\"has-drop-cap\">Gutenberg 9.8 separates the canvas area of the <a href=\"https://github.com/WordPress/gutenberg/pull/25775\">site editor into an iframe</a>. This separation means that global admin styles do not bleed into or override styles within the editor itself. The good news is this is a first step toward doing the same in the post editor too.</p>\n\n\n\n<p>This has been a change that I have been waiting for since the inception of the block editor. From a theme development and design standpoint, styling the editor to match the front end is ripe with issues. It has meant nesting CSS selectors when it should have been unnecessary. It has meant adding a few <code>!important</code> rules to overwrite what seems like oddities in the core CSS. While styling the block editor has improved by leaps and bounds in the past couple of years, it can still often be a pain.</p>\n\n\n\n<p>WordPress core committer Ella van Durpe <a href=\"https://github.com/WordPress/gutenberg/issues/20797#issue-579381499\">listed the benefits</a> of moving the canvas into an iframe:</p>\n\n\n\n<ul><li>There would be no admin CSS bleed at all. This is something we&rsquo;ve been struggling with since the beginning.</li><li>There would be no need to simulate media queries, which is arguably technically more difficult than using an iframe.</li><li>Relative units like <code>(r)em</code> and <code>vw</code>/<code>vh</code> just work.</li><li>For a full site, a theme stylesheet can be just dropped in the editor without any adjustment. I think this is important as it makes the life of theme authors much easier.</li><li>It&rsquo;s possible to have one selection per window, so one in the admin and one in the content. This is useful for e.g. the link UI where the selection in the content can be kept while the selection is also in an input element (for the URL). Maybe be useful in other cases.</li></ul>\n\n\n\n<p>While I find it tough to believe that theme stylesheets would just work without a hitch &mdash; <em>does such a world exist?</em> &ndash;, they should work far better than in the past. There are likely items theme authors will need to contend with, but they should be minimal. Developers should keep a close eye on the future development of this.</p>\n\n\n\n<h2>Border Radius Support for the Group Block</h2>\n\n\n\n<p class=\"has-drop-cap\">As part of Gutenberg&rsquo;s experimental feature set, the Group block now supports a <a href=\"https://github.com/WordPress/gutenberg/pull/27665\">border radius option</a>. However, end-users will not automatically see it in the block inspector. This is an opt-in feature for themes at the moment. Presumably, it will be a part of the default set of options for several blocks in the future.</p>\n\n\n\n<img />Setting the border-radius value for the Group block.\n\n\n\n<p>For theme authors who want to add support, they will need to drop the following code snippet into their <code>experimental-theme.json</code> file and edit the <code>radius</code> value:</p>\n\n\n\n<pre class=\"wp-block-code\"><code>\"core/group\" : {\n        \"styles\" : {\n                \"border\" : {\n                        \"radius\" : \"50px\"\n                }\n        }\n}</code></pre>\n\n\n\n<p>This will allow theme authors to set the default border-radius for the group block. However, it will not hand over control to users. For that, themes will need to add the following snippet under the <code>settings</code> section of their <code>experimental-theme.json</code> file:</p>\n\n\n\n<pre class=\"wp-block-code\"><code>\"border\" : {\n        \"customRadius\" : true\n}</code></pre>\n\n\n\n<p>I tested this with a modified version of the <a href=\"https://wordpress.org/themes/tt1-blocks/\">TT1 Blocks </a>theme without issue. Mostly, I am looking forward to more styling options like this in future iterations of the plugin.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Jan 2021 22:31: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: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: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:54:\"WordPress.org blog: People of WordPress: Thelma Mutete\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9518\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/01/people-of-wordpress-thelma-mutete/\";s: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:8322:\"<p><em>WordPress is open source software, maintained by a global network of contributors. There are many examples of how WordPress has changed people’s lives for the better. In this monthly series, we share some of those lesser-known, amazing stories.</em></p>\n\n\n\n<img src=\"https://i1.wp.com/wordpress.org/news/files/2021/01/Thelma-Mutete.jpg?resize=500%2C750&ssl=1\" alt=\"Thelma Mutete at a WordCamp\" class=\"wp-image-9564\" width=\"500\" height=\"750\" />\n\n\n\n<p>From a young age Thelma was encouraged by her father to ‘work hard, and dream big’. In High School, she pursued a career in Computer Science. She said: “I did not know what I would be doing or how I would get there but I just knew that I was going to pursue a career in information technology.”</p>\n\n\n\n<p>She wrote her first line of code at the age of 16 living in Zimbabwe, Africa. This was to mark the beginning of her enthusiasm for computer programming.</p>\n\n\n\n<p>When she joined the school’s computer class, Thelma thought she would learn Excel and Word. Instead, the assignment was to write her first program in C. She said: “It was not easy, but it was very exciting. l remember writing up simple code for a Video Club – a check-in/out for VHS tapes and CDs. Thus began my fascination with computers.”</p>\n\n\n\n<p>Seven years later, she went on to university to study for a Bachelors in Business Management and Information Technology. Her third year internship was at a local web design and hosting company. Though she had hoped her placement would be at a local bank or telecommunications company, the chance to discover website design turned out to be the best thing that could have happened.&nbsp;</p>\n\n\n\n<p>In 2017, Thelma went on to work for a company designing websites using HTML, CSS, PHP, JavaScript and Joomla. She had heard about WordPress but had not used it. She recalls: “People have this misconception that WordPress is not for real developers and it is not secure and at that time I was one of those people.”</p>\n\n\n\n<h2>Finding a local community</h2>\n\n\n\n<p>From a discussion with a member of the local WordPress community, <a href=\"https://heropress.com/essays/wordpress-opened-whole-new-world/\">Thabo Tswana</a>, about a striking swag gift from a WordCamp, Thelma’s interest was sparked.&nbsp;</p>\n\n\n\n<p>She started to find out more about WordPress and WooCommerce, and visited her local WordCamp Harare website. She was delighted to find that she could learn more about WordPress without needing any pre-existing knowledge, and wanted to be involved. So instead of just attending the camp, she volunteered too!&nbsp;</p>\n\n\n\n<p>Her response to her first WordPress event mirrors the experience of many others in the community. She said: “I only started using WordPress because of the awesome people that l had met at that WordCamp. Everyone was so welcoming.”</p>\n\n\n\n<p>A week later, with help from Thabo, she designed her first website using WordPress.</p>\n\n\n\n<p>She soon became more involved with the community and Meetups. Thelma participated in the first-ever ‘Women Who WordPress’ Meetup in 2018, with lots of women getting involved from bloggers to developers.&nbsp;</p>\n\n\n\n<p>She said: “We were free to talk and discuss a lot of things. We had more time to discuss the difference between WordPress.com and WordPress.org, we shared views on how to handle discrimination at work, how to promote your website and a whole lot of other things.”</p>\n\n\n\n<h2>Establishing roots in WordPress</h2>\n\n\n\n<p>In 2018, WordCamp Harare had its first-ever female Lead Organizer <a href=\"https://tapiwanashe.com/\">Tapiwanashe Manhobo</a>. Thelma was part of the organising team that year and was assigned to handle Harare’s first Kids Camp to take place eight months later. You can read more about her experiences of organizing a <a href=\"https://thelmachido.wordpress.com/2019/11/21/wordpress-juniours-first-edition/\"><strong>Kids Camp</strong></a> on her blog.</p>\n\n\n\n<p>She said: “After the first Kids Camp, we had several people in the local Zimbabwean WordPress community who were enthusiastic about encouraging young people to embrace ICT. In 2019, we had not planned to have a Kids Camp because of financial constraints but to our surprise, we had some anonymous donations and we managed to have a WordPress Community outreach to a youth centre, <a href=\"https://cttzim.org/\"><strong>Centre for Total Transformation</strong></a>, a week after our WordCamp. It is a non-formal school that caters for underprivileged and vulnerable children. The group were able to share practical skills about using WordPress, computer hardware and software.</p>\n\n\n\n<p>Thelma shares that she became hooked on WordPress because of its community. “I enjoy attending WordCamps, meeting new people and just learning new stuff. I have a huge list of WordCamps I would like to attend. Last year I managed to cross WordCamp Johannesburg off my list. When everything is back to normal my plan to travel to WordCamps will proceed (fingers crossed).”</p>\n\n\n\n<h2>Reaping the fruits of ongoing learning</h2>\n\n\n\n<p>Thelma is committed to ongoing development training. She said: “Even though I can still cook up code in C and Java, for now, I have also included WordPress PHP functions to the mix. It was not easy to get to this point, daring myself got me to this slightly better stage. I try to do my best where I can and I am happy to say it has paid off so far.”</p>\n\n\n\n<p>Thelma has continued her journey working in design and digital marketing last year with Trust Nhokovenzo who works in digital marketing and is active in&nbsp; the WordPress Community. He came across her name as a developer from talking with others involved in WordPress. She went to work with his team at a marketing agency.</p>\n\n\n\n<p>Her interest in the development of WordPress continued and she joined the <a href=\"https://wordpress.org/news/2020/12/simone/\">5.6 Release Squad</a> in the mid 2020.&nbsp;At the end of 2020, she moved to become a Happiness Engineer working with WordPress.com. Thelma’s fascination with the platform and the community continues to grow and her contributor story is ongoing.</p>\n\n\n\n<p>Find out more about the <a href=\"https://www.meetup.com/Harare-WordPress-Meetup\">Harare WordPress community</a> in Zimbabwe.</p>\n\n\n\n<h2>Contributors</h2>\n\n\n\n<p>Thanks to Nalini Thakor (<a href=\"https://profiles.wordpress.org/nalininonstopnewsuk/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>nalininonstopnewsuk</a>) and Surendra Thakor (<a href=\"https://profiles.wordpress.org/sthakor/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>sthakor</a>), Yvette Sonneveld (<a href=\"https://profiles.wordpress.org/yvettesonneveld/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>yvettesonneveld</a>), Abha Thakor (<a href=\"https://profiles.wordpress.org/webcommsat/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>webcommsat</a>), Larissa Murillo (<a href=\"https://profiles.wordpress.org/lmurillom/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>lmurillom</a>), Meher Bala (<a href=\"https://profiles.wordpress.org/meher/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>meher</a>), Josepha Haden (<a href=\"https://profiles.wordpress.org/chanthaboune/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chanthaboune</a>), and Chloé Bringmann (<a href=\"https://profiles.wordpress.org/cbringmann/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>cbringmann</a>). Thank you to Thelma Mutete (<a href=\"https://profiles.wordpress.org/thelmachido/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>thelmachido</a>) for sharing her #ContributorStory.</p>\n\n\n\n<img src=\"https://lh4.googleusercontent.com/s24EVZGKbxVeafljPU1ubF1DjIwn98E3-wGx1LD2CWYk7zYQppFhXNpb0aUhGe01TStMdTwXrcYaxBZQHRgZJ10lvW2hsg61Ce37_pBGJuTRQlJ6r9iUxlJtvuDuwLhIvPo1MVEb\" alt=\"HeroPress logo\" />\n\n\n\n<p><em>This post is based on </em><a href=\"https://heropress.com/essays/hello-world-discovering-the-world-through-wordpress/\"><em>an article originally published on HeroPress.com</em></a><em>, a community initiative created by </em><a href=\"https://profiles.wordpress.org/topher1kenobe/\"><em>Topher DeRosia</em></a><em>. HeroPress highlights people in the WordPress community</em>.</p>\n\n\n\n<p>#ContributorStory #HeroPress</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Jan 2021 16:40:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:\"\";}}}}}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:82:\"WPTavern: Gutenberg Contributors Consider Implementing a Bot to Close Stale Issues\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=110562\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/gutenberg-contributors-consider-implementing-a-bot-to-close-stale-issues?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-contributors-consider-implementing-a-bot-to-close-stale-issues\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5386:\"<p>Gutenberg project contributors are considering <a href=\"https://make.wordpress.org/core/2021/01/14/stale-issues-in-gutenberg-repository/\">implementing a stale bot</a> to tame the repository&rsquo;s overgrown <a href=\"https://github.com/WordPress/gutenberg/issues\">issues</a> queue, which currently has 2,733 open issues. Stale bots are usually employed to automatically close &ldquo;stale&rdquo; issues and PRs based on a predefined set of parameters for inactivity. </p>\n\n\n\n<p>&ldquo;The current recommendation is to set our policy to a 180-day of no activity, so if no comments or commits are on an issue or PR in 180 days, then the bot will post a comment to the issue alerting the user it will be closed in 7-days due to inactivity,&rdquo; Marcus Kazmierczak proposed.</p>\n\n\n\n<p>One important concern is getting the tone right for the automatically-generated message. When you&rsquo;re employing bots on a widely used open source project, they had better be friendly. A chilly, indifferent bot can unwittingly turn away potential contributors with the wrong kind of messaging. Kazmierczak proposed the following message:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>This is an auto-generated message to let you know that this issue has gone 180 days without any activity and meets the project&rsquo;s definition of stale. This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a &ldquo;bump&rdquo; to keep it open, or add the &ldquo;[Status] Not Stale&rdquo; label. Thanks for keeping our repository healthy!</p></blockquote>\n\n\n\n<p>Participants in the discussion on the proposal are divided on the best approach. Daniel Llewellyn, one of the most vocal opponents to using a stale bot, contends that an automatically closing issues sends the wrong message. </p>\n\n\n\n<p>&ldquo;If we care about users and that they trust that we will fix their problem then automatically closing their issue gives them the signal that we don&rsquo;t,&rdquo; Llewellyn said.</p>\n\n\n\n<p>&ldquo;If you don&rsquo;t want to fix a problem then it is better for a human to explain why the problem won&rsquo;t be fixed and personally close the issue. Automating this on the assumption that because nobody has commented in a while means it isn&rsquo;t important is bad!&rdquo;</p>\n\n\n\n<p>Joy Reynolds agreed with this assessment, noting that closing issues through any means can be discouraging.</p>\n\n\n\n<p>&ldquo;I&rsquo;ve had issues closed by humans for being stale, also, and it isn&rsquo;t any better,&rdquo; Reynolds said. &ldquo;I&rsquo;ve had issues closed because someone created a new issue on the same thing. This loses all the history and the watchers.</p>\n\n\n\n<p>&ldquo;I&rsquo;ve also had an issue closed at Launchpad for being stale (and their system used only two weeks as a time frame). That served no purpose at all. It only makes people go away, frustrated.&rdquo;</p>\n\n\n\n<p>Kazmierczak reiterated in the comments that the bot can be configured to skip issues labeled as bugs and that issues and PRs can be bumped to reset the 6-month clock.</p>\n\n\n\n<p>&ldquo;The overall goal of the proposal is to improve feedback and responses to issues by ensuring what&rsquo;s there is relevant,&rdquo; Kazmierczak said.</p>\n\n\n\n<p>Auto-closing issues is the most controversial part of the plan. The general consensus in the comments leans towards using the bot for labeling and triaging in order to manually close the issue later.</p>\n\n\n\n<p>&ldquo;My preference would be for a bot to alert humans in a&nbsp;slack&nbsp;channel when a&nbsp;ticket&nbsp;is declared stale and become progressively more insistent until a human responds,&rdquo; Peter Wilson said. </p>\n\n\n\n<p>Milana Cap suggested using a bot to nudge the ticket author as a compromise between &ldquo;being friendly and thoughtful to contributors while keeping maintainers sane.&rdquo;</p>\n\n\n\n<p>Whatever approach contributors land on, excluding tickets marked as bugs is going to be critical for making the stale bot productive. Otherwise, it becomes just a fancy way of kicking the can down the road, delaying the inevitable. </p>\n\n\n\n<p>In a recent post titled &ldquo;<a href=\"https://blog.benwinding.com/github-stale-bots/\">Github Stale Bots: A False Economy</a>,&rdquo; software developer Ben Winding wrote about why stale bots don&rsquo;t deliver what maintainers are aiming to achieve. Based on his experience with the <a href=\"https://github.com/angular/angular/issues\">Angular</a> repository&rsquo;s bot, Winding summarized the stale bot&rsquo;s effect on the issues queue: </p>\n\n\n\n<ol><li>Reduce the metric of&nbsp;<em>Open Issues</em>&nbsp;in github</li><li>Made duplicate issues far more likely</li><li>Increased friction of users reporting that the issue still exists</li><li>Ultimately decreased the quality of the software, as the issues don&rsquo;t accurately reflect reality</li></ol>\n\n\n\n<p>If the Gutenberg repository&rsquo;s stale bot can be configured not to close bugs and used to maximize human involvement, it will be less likely to deter people from reporting issues. Feedback on the <a href=\"https://make.wordpress.org/core/2021/01/14/stale-issues-in-gutenberg-repository/\">proposal</a> is open until January 29, 2021. Kazmierczak is seeking input on the bot&rsquo;s implementation, specifically its time threshold and messaging.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Jan 2021 16:03:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:24:\"Matt: New WhiteHouse.gov\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53526\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://ma.tt/2021/01/new-whitehouse-gov/\";s: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:2842:\"<p>After you&#8217;ve watched <a href=\"https://www.npr.org/sections/inauguration-day-live-updates/2021/01/20/958743170/poet-amanda-gorman-reads-the-hill-we-climb\">the amazing poem from Amanda Gorman</a>, check out the <a href=\"https://www.whitehouse.gov/\">new WhiteHouse.gov that re-launched today</a> using WordPress &amp; Gutenberg with a number of cool features including dark mode, text zoom, a totally responsive layout, and a Spanish version of the site. The site is clean, <a href=\"https://twitter.com/wesbos/status/1351957829461155849\">fast</a>, and accessible. It&#8217;s exciting and an honor that the online home for the Executive branch is on Open Source software, and I&#8217;m proud WordPress can carry the torch that <a href=\"https://dri.es/whitehouse-gov-using-drupal\">Drupal lit in 2009</a>.</p>\n\n\n\n<p>Besides Gutenberg, poking around I noticed a HTTP header and HTML comment <a href=\"https://usds.gov/apply\">encouraging people to join USDS</a>, and this great #46 easter egg in the theme file:</p>\n\n\n\n<img />\n\n\n\n<p>Anyone notice any other plugins? I haven&#8217;t spoken to him directly but I&#8217;d be shocked if <a href=\"https://nacin.com/\">Nacin</a> wasn&#8217;t involved with this one. I&#8217;m also curious if any of the WP agencies were involved, it has touches of <a href=\"https://10up.com/\">10up</a> but I don&#8217;t see any mention of it on their site or <a href=\"https://twitter.com/10up\">Twitter</a>. <a href=\"https://twitter.com/HoeflerCo/status/1351984719634771970\">Hoefler&amp;Co  credits</a> <a href=\"https://wideeye.co/\">Wide Eye Creative with the design</a>.</p>\n\n\n\n<p>I noticed a few people happy that some previous pages and files on the old site were returning 404 errors, like the <a href=\"https://www.nbcnews.com/news/nbcblk/how-trump-administration-s-1776-report-warps-history-racism-slavery-n1254926\">controversial 1776 report</a>, but on this I think the webmasters of the United States of America should demand better, since <a href=\"https://www.w3.org/Provider/Style/URI\">Cool URIs Don&#8217;t Change</a>. Previous websites are <a href=\"https://www.archives.gov/presidential-libraries/archived-websites\">all saved by the National Archives</a>, but there doesn&#8217;t appear to be any sort of norm for automatically redirecting links that went to any subdirectories or addresses under WhiteHouse.gov. </p>\n\n\n\n<p>There are WP plugins that could help, like <a href=\"https://wordpress.org/plugins/redirection/\">Redirection</a>, but also perhaps the root domain itself could always redirect to a subdomain, like 46.whitehouse.gov, so we&#8217;d have a consistent domain and permalinks for everything, and then each new administration would get a new subdomain.</p>\n\n\n\n<p><a href=\"https://wptavern.com/biden-white-house-sticks-with-wordpress-for-website-relaunch\">More coverage on WP Tavern</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Jan 2021 01:15:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:70:\"WPTavern: Biden White House Sticks with WordPress for Website Relaunch\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110712\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/biden-white-house-sticks-with-wordpress-for-website-relaunch?utm_source=rss&utm_medium=rss&utm_campaign=biden-white-house-sticks-with-wordpress-for-website-relaunch\";s: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:3896:\"<img />\n\n\n\n<p>President Joe Biden took office today and unveiled a new <a href=\"https://www.whitehouse.gov/\">whitehouse.gov</a> that has been relaunched on WordPress. The previous administration switched from Drupal to WordPress in 2017, and technologists working with the Biden administration decided to stick with the same CMS. </p>\n\n\n\n<p>In keeping with the multilingual and accessibility features implemented on <a href=\"https://wptavern.com/biden-harris-transition-website-launches-on-wordpress\">the Biden-Harris transition team website</a>, whitehouse.gov launched with toggles for contrast and font size, along with a Spanish language switcher. The relaunched site also includes an <a href=\"https://www.whitehouse.gov/accessibility/\">accessibility statement</a> with a commitment from the administration to work towards conforming to the Web Content Accessibility Guidelines (WCAG) version 2.1, level AA criteria.</p>\n\n\n\n<p>Much of the content and design from the transition website has been preserved. The transition site now forwards to whitehouse.gov, while links to the previous administration&rsquo;s pages land on a 404 page with a link to <a href=\"https://www.archives.gov/presidential-libraries/archived-websites\">archived presidential websites</a>.</p>\n\n\n\n<p>Savvy observers might notice that the typography has been updated from the transition site, flipping the Mercury and Decimal typefaces. Hoefler&amp;Co, the typeface design firm that <a href=\"https://www.typography.com/blog/biden-fonts\">created these typefaces</a> for Biden&rsquo;s 2020 campaign, <a href=\"https://twitter.com/HoeflerCo/status/1351984719634771970\">tweeted</a> about how &ldquo;the serif Mercury felt more like the voice of the institution.&rdquo;  The sans-serif Decimal functions more in a supporting role on the site.</p>\n\n\n\n<p>Web professionals kicked the tires a bit and noticed the site is putting up fairly decent Lighthouse scores.  </p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://t.co/hoaioTVqE3\">https://t.co/hoaioTVqE3</a> scoring super well on lighthouse, has dark mode and font size selector<br /><br />h8ers gonna be mad that it\'s wordpress and jQuery tho <a href=\"https://t.co/tyMNjdmnTH\">pic.twitter.com/tyMNjdmnTH</a></p>&mdash; Wes Bos (@wesbos) <a href=\"https://twitter.com/wesbos/status/1351957829461155849?ref_src=twsrc%5Etfw\">January 20, 2021</a></blockquote>\n</div>\n\n\n\n<p>Under the hood, code snoopers noticed an advertisement for the <a href=\"https://www.usds.gov/\">U.S. Digital Service</a> (USDS), the group of technologists who maintain many of the federal government&rsquo;s public-facing digital services.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>In addition to the message from USDS, the site&rsquo;s source code includes a link to the US government&rsquo;s analytics program at <a rel=\"noreferrer noopener\" href=\"https://analytics.usa.gov/\" target=\"_blank\">analytics.usa.gov</a>. Tim Lowden, who manages the federal government&rsquo;s aggregated web analytics initiative, <a href=\"https://twitter.com/tdlowden/status/1351939004342685697\">said</a> this data has been made available for the first time since late 2017.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The analytics service records more than 2.5 billion pageviews across federal government websites each month. The data is available to the public, but it&nbsp;<a href=\"https://www.digitalgov.gov/services/dap/common-questions-about-dap-faq/#part-4\">does not track individuals</a>, and&nbsp;<a href=\"https://support.google.com/analytics/answer/2763052?hl=en\">anonymizes the IP addresses</a>&nbsp;of visitors. It shows information for visitors&rsquo; devices, browsers, operating systems, and location broken down into cities and countries. Many of those visiting the site today are from countries other than the U.S. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Jan 2021 00:20:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:46:\"Gary: WordPress Importers: Free (as in Speech)\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=5478\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://pento.net/2021/01/21/wordpress-importers-free-as-in-speech/\";s: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:8227:\"<p>Back at<a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\"> the start of this series</a>, I listed four problems within the scope of the WordPress Importers that we needed to address. Three of them are largely technical problems, which I covered in previous posts. In wrapping up this series, I want to focus exclusively on the fourth problem, which has a philosophical side as well as a technical one — but that does not mean we cannot tackle it!</p>\n\n\n\n<div class=\"wp-block-group alignwide is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p class=\"has-text-align-center\">Problem Number 4</p>\n\n\n\n<p class=\"alignwide has-extra-large-font-size\"><strong>Some services work against their customers, and actively prevent site owners from controlling their own content.</strong></p>\n</div></div>\n\n\n\n<p>Some services are merely inconvenient: they provide exports, but it often involves downloading a bunch of different files. Your CMS content is in one export, your store products are in another, your orders are in another, and your mailing list is in yet another. It&#8217;s not ideal, but they at least let you get a copy of your data.</p>\n\n\n\n<p>However, there&#8217;s another class of services that actively work against their customers. It&#8217;s these services I want to focus on: the services that don&#8217;t provide any ability to export your content — effectively locking people in to using their platform. We could offer these folks an escape! The aim isn’t to necessarily make them use WordPress, it’s to give them a way out, if they want it. Whether they choose to use WordPress or not after that is immaterial (though I certainly hope they would, of course). The important part is freedom of choice.</p>\n\n\n\n<p>It&#8217;s worth acknowledging that this is a different approach to how WordPress has historically operated in relation to other CMSes. We provide <em>importers</em> for many CMSes, but we previously haven&#8217;t written <em>exporters</em>. However, I don&#8217;t think this is a particularly large step: for CMSes that already provide exports, we&#8217;d continue to use those export files. This is focussed on the few services that try to lock their customers in.</p>\n\n\n\n<h2>Why Should WordPress Take This On?</h2>\n\n\n\n<p>There are several aspects to <em>why</em> we should focus on this.</p>\n\n\n\n<p>First of all, it&#8217;s the <a href=\"https://wordpress.org/about/\">the WordPress mission</a>. Underpinning every part of WordPress is the simplest of statements: </p>\n\n\n\n<p class=\"has-text-align-center\"><strong>Democratise Publishing</strong></p>\n\n\n\n<p class=\"has-text-align-center\"><em>The freedom to build. The freedom to change. The freedom to share.</em></p>\n\n\n\n<p>These freedoms are the pillars of a Free and Open Web, but they’re not invulnerable: at times, they need to be defended, and that needs people with the time and resources to offer a defence.</p>\n\n\n\n<p>Which brings me to my second point: WordPress has the people who can offer that defence! The WordPress project has so many individuals working on it, from such a wide variety of backgrounds, we&#8217;re able to take on a vast array of projects that a smaller CMS just wouldn&#8217;t have the bandwidth for. That&#8217;s not to say that we can do <em>everything</em>, but when there&#8217;s a need to defend the entire ecosystem, we&#8217;re able to devote people to the cause.</p>\n\n\n\n<p>Finally, it’s important to remember that WordPress doesn’t exist in a vacuum, we’re part of a broad ecosystem which can only exist through the web remaining open and free. By encouraging all CMSes to provide proper exports, and implementing them for those that don’t, we help keep our ecosystem healthy.</p>\n\n\n\n<p>We have the ability to take on these challenges, but we have a responsibility that goes alongside. We can&#8217;t do it solely to benefit WordPress, we need to make that benefit available to the entire ecosystem. This is why it&#8217;s important to<a href=\"https://pento.net/2021/01/20/wordpress-importers-defining-a-schema/\"> define a WordPress export schema</a>, so that any CMS can make use of the export we produce, not just WordPress. If you’ll excuse the imagery for a moment, we can be the knight in shining armour that frees people — then gives them the choice of what they do with that freedom, without obligation.</p>\n\n\n\n<h2>How Can We Do It?</h2>\n\n\n\n<p>Moving on to the technical side of this problem, I can give you some good news: the answer is definitely <em>not</em> screen scraping. <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f604.png\" alt=\"😄\" class=\"wp-smiley\" /> Scraping a site is fragile, impossible to transform into the full content, and provides an incomplete export of the site: anything that&#8217;s only available in the site dashboard can&#8217;t be obtained through scraping.</p>\n\n\n\n<p>I&#8217;ve recently been experimenting with an alternative approach to solving this problem. Rather than trying to create something resembling a traditional exporter, it turns out that modern CMSes provide the tools we need, in the form of REST APIs. All we need to do is call the appropriate APIs, and collate the results. The fun part is that we can authenticate with these APIs as the site owner, by calling them from a browser extension! So, that’s what I’ve been experimenting with, and it’s showing a lot of promise.</p>\n\n\n\n<p>If you&#8217;re interested in playing around with it, <a href=\"https://github.com/pento/free-as-in-speech\">the experimental code is living in this repository</a>. It&#8217;s a simple proof of concept, capable of exporting the text content of a blog on a Wix site, showing that we can make a smooth, comprehensive, easy-to-use exporter for any Wix site owner.</p>\n\n\n\n<img width=\"904\" height=\"446\" src=\"https://pento.net/wp-content/uploads/2021/01/Screen-Shot-2021-01-20-at-5.26.38-pm.png\" alt=\"Screenshot of the \" />\n\n\n\n<p>Clicking the export button starts a background script, which calls Wix&#8217;s REST APIs <em>as the site owner</em>, to get the original copy of the content. It then packages it up, and presents it as a WXR file to download.</p>\n\n\n\n<img width=\"972\" height=\"948\" src=\"https://pento.net/wp-content/uploads/2021/01/Screen-Shot-2021-01-20-at-5.27.38-pm.png\" alt=\"Screenshot of a Firefox download dialog, showing a Wix site packaged up as a WXR file.\" class=\"wp-image-5528\" />\n\n\n\n<p>I&#8217;m really excited about how promising this experiment is. It can ultimately provide a full export of any Wix site, and we can add support for other CMS services that choose to artificially lock their customers in.</p>\n\n\n\n<h2>Where Can I Help?</h2>\n\n\n\n<p>If you’re a designer or developer who’s excited about working on something new, head on over to the repository and <a href=\"https://github.com/pento/free-as-in-speech/issues\">check out the open issues</a>: if there’s something that isn’t already covered, feel free to open a new issue.</p>\n\n\n\n<p>Since this is new ground for a WordPress project, both technically and philosophically, I&#8217;d love to hear more points of view. It’s being discussed in <a href=\"https://make.wordpress.org/core/2021/01/19/dev-chat-agenda-for-january-20-2021-january-21-2021/#comment-40563\">the WordPress Core Dev Chat this week</a>, and you can also let me know what you think in the comments!</p>\n\n\n\n<div class=\"wp-block-group is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p><em>This post is part of a series, talking about the WordPress Importers, their history, where they are now, and where they could go in the future.</em></p>\n\n\n\n<ul><li><em><a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\">Part 1: Stating the Problem</a></em></li><li><em><a href=\"https://pento.net/2021/01/19/wordpress-importers-getting-our-house-in-order/\">Part 2: Getting Our House in Order</a></em></li><li><em><a href=\"https://pento.net/2021/01/20/wordpress-importers-defining-a-schema/\">Part 3: Defining a Schema</a></em></li><li><a href=\"https://pento.net/2021/01/21/wordpress-importers-free-as-in-speech/\"><em>Part 4: Free (as in Speech)</em></a></li></ul>\n\n\n\n<p></p>\n</div></div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 Jan 2021 00:14:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Gary\";s: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:102:\"WPTavern: First Round of the FSE Outreach Program Concludes, Identifies Template-Editing Mode Problems\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110638\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:247:\"https://wptavern.com/first-round-of-the-fse-outreach-program-concludes-identifies-template-editing-mode-problems?utm_source=rss&utm_medium=rss&utm_campaign=first-round-of-the-fse-outreach-program-concludes-identifies-template-editing-mode-problems\";s: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:5309:\"<p class=\"has-drop-cap\">The Full Site Editing (FSE) <a href=\"https://wptavern.com/help-steer-the-future-of-wordpress-via-the-fse-outreach-program\">Outreach Program</a> has now concluded its <a href=\"https://make.wordpress.org/test/2021/01/15/fse-program-template-editing-testing-summary/\">first round of testing</a>. Its first focus area was centered on the template-editing mode introduced in <a href=\"https://make.wordpress.org/core/2020/12/23/whats-new-in-gutenberg-23-december/\">Gutenberg 9.6</a>. The volunteers involved with the project identified several pain points.</p>\n\n\n\n<p>Gutenberg 9.6 added a new button that allows end-users, provided they are using a block-based theme, to switch between editing their post and the template that displays the post. As Josepha Haden <a href=\"https://wptavern.com/gutenberg-9-3-provides-indicator-of-where-full-site-editing-is-going-a-future-without-widgets-and-customizer-screens\">said last year</a>, the ultimate goal is to &ldquo;consolidate down to just one beautiful, intuitive interface.&rdquo; Essentially, this new feature merges content and design in a way we have not seen in core WordPress before. It is a step toward that lofty goal.</p>\n\n\n\n<p>Traditionally, WordPress has always separated content from design. However, these two aspects of websites are continually merging together. There is a desire for this. The adoption of page builders over the last half-decade or so has made it abundantly clear.</p>\n\n\n\n<p>The biggest issue with this new template mode is that users need a working knowledge of the WordPress template system to understand the ramifications of their edits. One of the primary questions of the focus area was whether it was clear that the user was making large-scale changes to all posts when switching to the template-editing mode.</p>\n\n\n\n<p>&ldquo;I believe it was not clear enough how those changes could impact the site,&rdquo; <a href=\"https://make.wordpress.org/test/2020/12/23/fse-program-testing-call-1-template-editing/#comment-1307\">wrote H&eacute;ctor Prieto in response</a>. &ldquo;If you don&rsquo;t already know how templates, template parts, and global blocks like Site Title work, you might not understand how your editing will affect the rest of the site.&rdquo;</p>\n\n\n\n<p>Switching modes does create a quick popup at the bottom left of the screen that reads:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Editing template. Changes made here affect all posts and pages that use the template.</p></blockquote>\n\n\n\n<p>It is easy to miss before it fades away. There is a ticket to <a href=\"https://github.com/WordPress/gutenberg/issues/28175\">stick this message</a> on the screen and allow the user to dismiss it. There is also another ticket for clarifying when a user is <a href=\"https://github.com/WordPress/gutenberg/issues/27849\">editing a template vs. content</a>.</p>\n\n\n\n<img />Entering template-editing mode from the post editor.\n\n\n\n<p>Gutenberg&rsquo;s current method is different than what you might see in a typical page builder. When switching to template-editing mode, the user is no longer editing that single post&rsquo;s front-end output. Instead, they are making global edits. A page builder would generally save any customizations to that page alone. If this remains the same, it could be a hurdle for the average user to clear.</p>\n\n\n\n<p>A template creation feature needs to be a part of this new mode. Users should be able to fork or clone their existing single post template and save it as a new template specific to that post. Or, maybe hand them a way to save it as a reusable template (i.e., &ldquo;page&rdquo; template). Paal Joachim Romdahl <a href=\"https://make.wordpress.org/test/2020/12/23/fse-program-testing-call-1-template-editing/#comment-1303\">shared a similar thought</a>, likening it to the &ldquo;Save As&hellip;&rdquo; feature commonly found in computer programs.</p>\n\n\n\n<p>I do question whether users should be able to edit global templates while editing a single post. The two are only related insofar as the template displays the post content on the front end. WordPress should explore any type of design work from the post-editing screen as, first and foremost, specific to that post.</p>\n\n\n\n<p>The volunteers also identified other issues. Applying changes to the template and saving drops the user back into the post editor. The &ldquo;cancel&rdquo; button is tough to find &mdash; it is in a different location than where the user clicked to go into template-editing mode.</p>\n\n\n\n<p>Switching between post and template editing feels like an FSE 2.0 type of thing. The development team has enough issues on its plate with the normal site editor. It is a far cry from being a viable, production-ready product. The team&rsquo;s focus should be on working the kinks out of that system before merging it with the post editor. Crawl before you walk. Walk before you run.</p>\n\n\n\n<p>However, I am willing to be pleasantly surprised. In the long run, it will probably be a good thing that we are getting an early look at what these two different pieces of WordPress will look like working in conjunction.</p>\n\n\n\n<p>This is also why participation in the FSE Outreach Program is vital. The community needs this more formal type of process to identify areas that need improvement.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Jan 2021 23:17:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:18;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"HeroPress: Changing Careers Into WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=3454\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:136:\"https://heropress.com/essays/changing-careers-into-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=changing-careers-into-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6844:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2022/01/012021-min.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: With WordPress skills, you have more concrete skills to offer.\" /><p>If you’re looking to change careers into technology, WordPress is a great way to do it.</p>\n<p>In 2013, I was in a career counselor’s office. Just realizing that I needed to change careers out of music, almost the only thing I had known for the last 20 years:</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2022/01/trombone-namm.jpg\"><img /></a>At NAMM in Anaheim, California\n<p>Aside from feeling like a huge failure, I knew I’d need a lot of luck to get a job.</p>\n<p>Someone would have to take a big chance on me.</p>\n<p>But there were a few problems.</p>\n<p>I was terrified of talking to strangers, much less asking them big favors. And I had almost no traditionally useful skills.</p>\n<p>Enter WordPress.</p>\n<h2>Lots Of Options</h2>\n<p>When you’re changing careers, you’ll want skills that will help no matter what you end up doing.</p>\n<p>You don’t want to deep-dive into calculus and find out that it won’t help.</p>\n<p>Learning WordPress is perfect.</p>\n<p>If you get really interested in the technical side, you can be a JS or PHP developer.</p>\n<p>If you really like content creation, that’s also great. You can start a blog or work in marketing.</p>\n<p>If none of it interests you, at least you can help people set up a website as you look for another career.</p>\n<p>So soon after meeting with the career counselor, I took Zac Gordon’s course on WordPress Theme Development.</p>\n<p>I wrote a theme based on his course, and really liked how WordPress worked.</p>\n<p>He taught me to build sites, and later write plugins.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2022/01/with-zac-gordon.jpg\"><img /></a>Zac Gordon with XWP\n<h2>Invite Yourself To The Party</h2>\n<p>The great thing about WordPress is that you can contribute right away.</p>\n<p>With some careers, you need somebody to take a chance on you before you can do much.</p>\n<p>To get experience as an investment banker or business consultant, you probably need to actually have the job.</p>\n<p>But with WordPress, you can invite yourself.</p>\n<p>You can open pull requests to Core or Gutenberg without anyone asking.</p>\n<p>You can deploy plugins to wp.org that real people use, without having a college degree.</p>\n<p>With this growing experience, I applied online to <a href=\"https://xwp.co/\">XWP</a>.</p>\n<p>Weston Ruter responded right away, and was really helpful.</p>\n<p>I started opening simple PRs to “help” with the Customizer work.</p>\n<p>In reality, my work might have slowed things down, and was really simple.</p>\n<p>But I didn’t have to wait to be invited. I invited myself to the party, and one of the PRs was merged into Core.</p>\n<p>Later, when I interviewed with <a href=\"https://xwp.co/\">XWP</a> and got the job, I could show that I had a little experience working with other developers.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2022/01/with-xwp-1.jpg\"><img /></a>XWP At WordCamp US Contributor Day, 2017\n<p>It’s still embarrassing looking back at the work I did. But WordPress allows you to contribute, regardless of your experience level.</p>\n<p>Years later, when I lived in Mexico City, one of my friends got interested in technology.</p>\n<p>He was like me. He had a degree in an unrelated field, and wanted a great career.</p>\n<p>So I showed him how much opportunity WordPress has.</p>\n<p>He did something similar to what I did.</p>\n<p>He opened PRs to an agency’s repos, and the agency asked him if he wanted to talk about a job, without him needing to apply. Years later, he’s still doing really well at his job.</p>\n<p>I did very little, other than point him to a huge opportunity: WordPress.</p>\n<h2>Concrete Skills</h2>\n<p>Changing careers is really awkward.</p>\n<p>You read about networking, which seems like you’re asking strangers for favors and sending spam DMs.</p>\n<p>You also learn to reframe things as transferable skills.</p>\n<p>So if you’ve done hard things, you can say you’re “comfortable with ambiguity.”</p>\n<p>But with WordPress skills, you have more concrete skills to offer.</p>\n<p>It’s less awkward explaining to someone why they should take a chance on you.</p>\n<p>You’ve shown you’re committed to your career path by your portfolio of plugins.</p>\n<p>And you don’t have to send spam DMs on LinkedIn.</p>\n<p>In 2014, I went to my first WordPress meetup, <a href=\"https://www.meetup.com/WPLosAngeles\">WordPress Los Angeles</a>. I was nervous, but I wasn’t trying to take any value.</p>\n<p>I could even answer a few questions.</p>\n<p>Renee Johnson and I met there. We even reunited in WordCamp Europe and Mexico City several years later when I lived there:</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2022/01/with-renee.jpg\"><img /></a>Yani Jimenez and Renee Johnson, Mexico City\n<p>With WordPress skills, you can flip from taking to giving value. Everything is much less awkward.</p>\n<p>As you probably know, there are many self-taught developers in WordPress.</p>\n<p>College degrees rarely come up in hiring conversations, at least in my experience.</p>\n<p>And I’ve found WordPress very accepting of different career backgrounds. Matt Mullenweg was a musician, famously naming every release after a jazz musician.</p>\n<p>People in WordPress are very understanding about changing careers.</p>\n<p>Now, I don’t hide it, and it’s rarely more than a footnote in conversations.</p>\n<h2>Mentorship</h2>\n<p>Don’t go it alone.</p>\n<p>It’s easy to think that you can just take online courses and eventually be ready for a job.</p>\n<p>But code reviews are one of the main ways you’ll learn. And people in WP want to help.</p>\n<p>If you contribute a few PRs to someone’s GitHub repo, they’ll probably do a quick code review of your own plugin or theme.</p>\n<p>Weston was really helpful in doing a detailed review of my theme.</p>\n<p>You also can learn a lot contributing to Gutenberg or other plugins.</p>\n<p>They’ll give you detailed reviews. And you’ll basically get the same experience as if you were getting paid.</p>\n<p>But if I were to do this again, I’d also look for more formal mentorship.</p>\n<p>Hiring someone to review your plugins and themes would probably help.</p>\n<h2>Nothing To Fix</h2>\n<p>There’s a saying in marketing “what you can’t fix, you feature.”</p>\n<p>In WordPress, you don’t have to fix your non-traditional career background.</p>\n<p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/changing-careers-into-wordpress/\">Changing Careers Into WordPress</a> appeared first on <a rel=\"nofollow\" href=\"https://heropress.com\">HeroPress</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 Jan 2021 17:50: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:\"Ryan Kienstra\";s: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:44:\"Gary: WordPress Importers: Defining a Schema\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=5495\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://pento.net/2021/01/20/wordpress-importers-defining-a-schema/\";s: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:8792:\"<p>While schemata are usually implemented using language-specific tools (eg, XML uses <a href=\"https://www.w3.org/standards/xml/schema\">XML Schema</a>, JSON uses <a href=\"https://json-schema.org/\">JSON Schema</a>), they largely use the same concepts when talking about data. This is rather helpful, we don&#8217;t need to make a decision on <a href=\"https://pento.net/2021/01/19/wordpress-importers-getting-our-house-in-order/\">data formats</a> before we can start thinking about how the data should be arranged.</p>\n\n\n\n<p><em>Note: Since these concepts apply equally to all data formats, I&#8217;m using &#8220;WXR&#8221; in this post as shorthand for &#8220;the structured data section of whichever file format we ultimately use&#8221;, rather than specifically referring to the existing WXR format.</em> <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" /></p>\n\n\n\n<h2>Why is a Schema Important?</h2>\n\n\n\n<p>It&#8217;s fair to ask why, if the WordPress Importers have survived this entire time <em>without</em> a formal schema, why would we need one now?</p>\n\n\n\n<p>There are two major reasons why we haven&#8217;t needed one in the past:</p>\n\n\n\n<ul><li>WXR has remained largely unchanged in the last 10 years: there have been small additions or tweaks, but nothing significant. There&#8217;s been no need to keep track of changes.</li><li>WXR is currently very simple, with just a handful of basic elements. In a recent experiment, I was able to implement a JavaScript-based WXR generator in just a few days, entirely by referencing <a href=\"https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes/export.php\">the Core implementation</a>.</li></ul>\n\n\n\n<p>These reasons are also why it would help to implement a schema for the future:</p>\n\n\n\n<ul><li>As work on WXR proceeds, there will likely need to be substantial changes to what data is included: adding new fields, modifying existing fields, and removing redundant fields. Tracking these changes helps ensure any WXR implementations can stay in sync.</li><li>These changes will result in a more complex schema: relying on the source to re-implement it will become increasingly difficult and error-prone. Following Gutenberg&#8217;s lead, it&#8217;s likely that we&#8217;d want to provide official libraries in both PHP and JavaScript: keeping them in sync is best done from a source schema, rather than having one implementation copy the other.</li></ul>\n\n\n\n<p>Taking the time to plan out a schema now gives us a solid base to work from, and it allows for future changes to happen in a reliable fashion.</p>\n\n\n\n<h2>WXR for all of WordPress</h2>\n\n\n\n<p>With a well defined schema, we can start to expand what data will be included in a WXR file.</p>\n\n\n\n<h3>Media</h3>\n\n\n\n<p>Interestingly, many of the challenges around media files are less to do with WXR, and more to do with importer capabilities. The biggest headache is retrieving the actual files, which the importer currently handles by trying to retrieve the file from the remote server, as defined in the <code>wp:attachment_url</code> node. In context, this behaviour is understandable: 10+ years ago, personal internet connections were too slow to be moving media around, it was better to have the servers talk to each other. It&#8217;s a useful mechanism that we should keep as a fallback, but the more reliable solution is to include the media file with the export.</p>\n\n\n\n<h3>Plugins and Themes</h3>\n\n\n\n<p>There are two parts to plugins and themes: the code, and the content. Modern WordPress sites <em>require</em> plugins to function, and most are customised to suit their particular theme.</p>\n\n\n\n<p>For exporting the code, I wonder if a tiered solution could be applied:</p>\n\n\n\n<ul><li>Anything from WordPress.org would just need their slug, since they can be re-downloaded during import. Particularly as WordPress continues to move towards an auto-updated future, modified versions of plugins and themes are explicitly not supported.</li><li>Third party plugins and themes would be given a filter to use, where they can provide a download URL that can be included in the export file.</li><li>Third party plugins/themes that don’t provide a download URL would either need to be skipped, or zipped up and included in the export file.</li></ul>\n\n\n\n<p>For exporting the content, WXR already includes custom post types, but doesn&#8217;t include custom settings, or custom tables. The former should be included automatically, and the latter would likely be handled by an appropriate action for the plugin to hook into.</p>\n\n\n\n<h3>Settings</h3>\n\n\n\n<p>There are a currently handful of special settings that are exported, but (as I just noted, particularly with plugins and themes being exported) this would likely need to be expanded to included most items in&nbsp;<code>wp_options</code>.</p>\n\n\n\n<h3>Users</h3>\n\n\n\n<p>Currently, the bare minimum information about users who’ve authored a post is included in the export. This would need to be expanded to include more user information, as well as users who aren’t post authors.</p>\n\n\n\n<h2>WXR for <em>parts</em> of WordPress</h2>\n\n\n\n<p>The modern use case for importers isn&#8217;t just to handle a full site, but to handle keeping sites in sync. For example, most news organisations will have a staging site (or even several layers of staging!) which is synchronised to production.</p>\n\n\n\n<p>While it&#8217;s well outside the scope of this project to directly handle every one of these use cases, we should be able to provide the framework for organisations to build reliable platforms on. Exports should be repeatable, objects in the export should have unique identifiers, and the importer should be able to handle any subset of WXR.</p>\n\n\n\n<h2>WXR Beyond WordPress</h2>\n\n\n\n<p>Up until this point, we&#8217;ve really been talking about&nbsp;WordPress→WordPress migrations, but I think WXR is a useful format beyond that. Instead of just containing direct exports of the data from particular plugins, we could also allow it to contain &#8220;types&#8221; of data. This turns WXR into an intermediary language, exports can be created from any source, and imported into WordPress.</p>\n\n\n\n<p>Let&#8217;s consider an example. Say we create a tool that can export a Shopify, Wix, or GoDaddy site to WXR, how would we represent an online store in the WXR file? We don&#8217;t want to export in the format that any particular plugin would use, since a WordPress Core tool shouldn&#8217;t be advantaging one plugin over others.</p>\n\n\n\n<p>Instead, it would be better if we could format the data in a platform-agnostic way, which plugins could then implement support for. As luck would have it, <a href=\"https://schema.org/\">Schema.org</a> provides exactly the kind of data structure we could use here. It&#8217;s been <a href=\"https://schema.org/docs/releases.html\">actively maintained for nearly nine years</a>, it supports a <a href=\"https://schema.org/docs/schemas.html\">wide variety of data types</a>, and is intentionally platform-agnostic.</p>\n\n\n\n<p>Gazing into my crystal ball for a moment, I can certainly imagine a future where plugins could implement and declare support for importing certain data types. When handling such an import (assuming one of those plugins wasn&#8217;t already installed), the WordPress Importer could offer them as options during the import process. This kind of seamless integration allows WordPress to show that it offers the same kind of fully-featured site building experience that modern CMS services do.</p>\n\n\n\n<p>Of course, reality is never quite as simple as crystal balls and magic wands make them out to be. We have to contend with services that provide incomplete or fragmented exports, and there are even services that deliberately don&#8217;t provide exports at all. In the next post, I&#8217;ll be writing about why we should address this problem, and how we might be able to go about it.</p>\n\n\n\n<div class=\"wp-block-group is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p><em>This post is part of a series, talking about the WordPress Importers, their history, where they are now, and where they could go in the future.</em></p>\n\n\n\n<ul><li><em><a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\">Part 1: Stating the Problem</a></em></li><li><em><a href=\"https://pento.net/2021/01/19/wordpress-importers-getting-our-house-in-order/\">Part 2: Getting Our House in Order</a></em></li><li><em><a href=\"https://pento.net/2021/01/20/wordpress-importers-defining-a-schema/\">Part 3: Defining a Schema</a></em></li><li><a href=\"https://pento.net/2021/01/21/wordpress-importers-free-as-in-speech/\"><em>Part 4: Free (as in Speech)</em></a></li></ul>\n\n\n\n<p></p>\n</div></div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Jan 2021 23:13:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Gary\";s: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:101:\"WPTavern: Custom Layouts Plugin Creates a Posts Display System for Both the Classic and Block Editors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110409\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:247:\"https://wptavern.com/custom-layouts-plugin-creates-a-posts-display-system-for-both-the-classic-and-block-editors?utm_source=rss&utm_medium=rss&utm_campaign=custom-layouts-plugin-creates-a-posts-display-system-for-both-the-classic-and-block-editors\";s: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:5383:\"<p class=\"has-drop-cap\">Ross Morsali, via his brand Code Amp, released the <a href=\"https://wordpress.org/plugins/custom-layouts/\">Custom Layouts</a> plugin last week. The plugin&rsquo;s goal is to provide a visual post layout builder for users of both the block and classic editors.</p>\n\n\n\n<p>For end-users, this is yet another choice between the multitude of plugins for displaying posts. After years of new plugins launching in this space, it would seem that there would be a clear front-runner, but developers are still trying to tame this wild and complex feature. The Custom Layouts plugin has its own approach, and it is worth giving it a quick spin to see if it suits you.</p>\n\n\n\n<p>I have written extensively about the <a href=\"https://wptavern.com/gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block\">upcoming Query block</a> and its role in the <a href=\"https://wptavern.com/understanding-the-query-block-and-its-importance-in-site-editing\">future of WordPress</a>. However, it is necessary to look at alternative solutions for displaying posts via the block editor. The Gutenberg development team should take note of the things that work and those that do not.</p>\n\n\n\n<p>For developers, the plugin is a noteworthy experiment that uses the block editor component system outside of the actual editor. Custom Layouts uses these various components on its custom Layout and Template Editor screens.</p>\n\n\n\n<p>The plugin is a product of Morsali learning React and the block system in the last year and a half. &ldquo;Working with Gutenberg and the Block Editor as a developer is a far superior experience to the old paradigm (the classic editor) &mdash; the learning curve is definitely greater, but once you get over the hump it seems the future is bright,&rdquo; he wrote in the <a href=\"https://codeamp.com/creating-the-custom-layouts-plugin/\">plugin&rsquo;s announcement post</a>. &ldquo;I also love the fact that we don&rsquo;t actually need to be using the Block Editor to use Gutenberg components &mdash; that means we can still build what we want and how we want it (providing we&rsquo;re using React), whilst keeping the UI in tune with the rest of WordPress.&rdquo;</p>\n\n\n\n<h2>How the Plugin Works</h2>\n\n\n\n<img />Template editor screen.\n\n\n\n<p class=\"has-drop-cap\">Custom Layouts takes a different route than similar plugins, splitting its components into different screens. The terminology can be confusing to the uninitiated. The plugin introduces two parts that serve as the foundation of its system:</p>\n\n\n\n<ul><li><strong>Templates:</strong> Handles the design of individual posts.</li><li><strong>Layouts:</strong> Controls queried posts and their layout.</li></ul>\n\n\n\n<p>I have had a beta version of the plugin since late December. This has given me three weeks to decide whether I like the approach. On the one hand, the plugin caters to two different user bases. One set can implement their layouts via the Custom Layouts block. Those on the classic editor can use the Layout Editor screen. Both share the Template Editor.</p>\n\n\n\n<img />Creating a three-column grid layout.\n\n\n\n<p>The plugin&rsquo;s system is a good option for users of the classic editor. It comes with a visual interface they would otherwise not have. It also provides a shortcode for easy copying/pasting into the post editor.</p>\n\n\n\n<p>For users of the block editor, having a separate screen for the template builder will likely feel unnatural. Because the block editor is a visual interface itself, the multiple screens create a disjointed atmosphere that never feels <em>right</em>.</p>\n\n\n\n<p>However, there is a solution for that in the plugin. I recommend users skip the Template Editor and Layout Editor screens altogether. The Custom Layouts block serves as an alternative layout builder in the block editor. Plus, users can edit existing templates via a popup overlay or even create new ones without ever leaving the post-editing screen. </p>\n\n\n\n<img />Overlay for editing a template.\n\n\n\n<p>Building everything from the post editor feels like it should feel. Users get more of that instant feedback that they are accustomed to through the block editor.</p>\n\n\n\n<p>There are benefits to the multi-component system. Separating the template builder means that users can build and reuse a specific design from a single source. They can also update individual templates, which will subsequently apply to all uses of those templates across the site.</p>\n\n\n\n<p>The other benefit is that end-users are not overloaded with choices. Building a query-related block, widget, shortcode, or similar component is fraught with complexity. This is because there are three pieces of laying out a list of posts: the query to load them, the overall layout, and the design of the individual posts. Putting options for each of these pieces into the block inspector, for example, means creating a balance between sacrificing some choices and providing every possible setting to the user. This balancing act is what drove Morsali toward separating the components of the plugin.</p>\n\n\n\n<p>On the whole, Custom Layouts is a solid plugin. The downside is that there is a little bit of a learning curve because it serves two audiences. Users will need to figure out which workflow best suits them first. Once they figure that out, the plugin is pretty nice to work with.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Jan 2021 21:48:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:84:\"WPTavern: WordPress for Android Previews New Story Posts Feature, Now in Public 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:30:\"https://wptavern.com/?p=110474\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:211:\"https://wptavern.com/wordpress-for-android-previews-new-story-posts-feature-now-in-public-beta?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-for-android-previews-new-story-posts-feature-now-in-public-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3697:\"<p>WordPress users on Android may have noticed a new prompt in the mobile app for publishing Story posts. This feature is now in public beta in the Android app, ahead of an upcoming launch on the WordPress iOS app. Stories will also coming to the Block editor on WordPress.com in early 2021. </p>\n\n\n\n<p>Early access to Story posts is available in version 16.3+ of the app, released in mid-December. The prompt appears at the bottom of the site management screen. Selecting a Story post immediately takes you to your phone&rsquo;s media where you can add photos or a video.</p>\n\n\n\n<ul><li class=\"blocks-gallery-item\"><img /></li><li class=\"blocks-gallery-item\"><img /></li></ul>\n\n\n\n<p><br />The mobile app&rsquo;s implementation of the Stories feature is different from other platforms, like Instagram and Facebook, in several key ways. Most importantly, WordPress stories are not ephemeral. They live permanently on your site and anyone can view them after they are published. WordPress.com&rsquo;s <a href=\"https://wordpress.com/support/story-block/\">documentation</a> for the block highlights a few differences: </p>\n\n\n\n<ul><li>Posts with Stories won&rsquo;t disappear after 24 hours.&nbsp;</li><li>The Story content can be added to and edited after publishing.&nbsp;</li><li>Anyone visiting your site can view the Story.&nbsp;</li><li>You can share your Story on any platform using the post&nbsp;<a href=\"https://wordpress.com/support/permalinks-and-slugs/\">permalink</a>.</li></ul>\n\n\n\n<p>After testing the feature, I can confirm a few more differences. While the WordPress app&rsquo;s implementation transcends other platforms&rsquo; limitations on the duration of the story&rsquo;s visibility, it lacks basic features that users have come to expect from other apps. It doesn&rsquo;t support animated gifs, effects, location, stickers, music, and other embellishments that make stories such a creative social medium. At the moment, the only thing you can do is add colored text with a background.</p>\n\n\n\n<ul><li class=\"blocks-gallery-item\"><img /></li><li class=\"blocks-gallery-item\"><img /></li></ul>\n\n\n\n<p>Videos work as Stories, too, but they don&rsquo;t seem to have the same preview with a thumbnail image. It&rsquo;s just a generic placeholder for now. That may be something the team is still working on, but I logged an <a href=\"https://github.com/wordpress-mobile/WordPress-Android/issues/13809\">issue</a> on GitHub for it, in case it&rsquo;s a bug. </p>\n\n\n\n<ul><li class=\"blocks-gallery-item\"><img /></li><li class=\"blocks-gallery-item\"><img /></li></ul>\n\n\n\n<p>In the interest of owning your own content, I can see it being useful to create stories on your own website and share them to other networks. The current implementation is basically a fullscreen slideshow. It is not yet more compelling than what social networks offer, but it looks like WordPress for iOS <a href=\"https://github.com/tumblr/kanvas-ios/projects/1\">plans to expand on these features</a> using the open source <a href=\"https://github.com/tumblr/kanvas-ios\">Kanvas library</a> from Tumblr.</p>\n\n\n\n<p>Kanvas makes it possible to add&nbsp;effects, drawings, text, stickers, and make GIFs from existing media or the camera. If you have ever used the&nbsp;<a href=\"https://apps.apple.com/us/app/tumblr/id305343404\">Tumblr iOS app</a> then you have seen Kanvas in action in the camera, media editor, GIF maker, and media posting tool. It should make for a more exciting Stories implementation on iOS, with features on par with what users have come to expect from other platforms. Something similar for Android may be in the works and this post will be updated as soon as we receive comments from the mobile team.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Jan 2021 23:55:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:53:\"Gary: WordPress Importers: Getting Our House in Order\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=5465\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"https://pento.net/2021/01/19/wordpress-importers-getting-our-house-in-order/\";s: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:15440:\"<p>The <a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\">previous post</a> talked about the broad problems we need to tackle to bring our importers up to speed, making them available for everyone to use.</p>\n\n\n\n<p>In this post, I&#8217;m going to focus on what we could do with the existing technology, in order to give us the best possible framework going forward.</p>\n\n\n\n<h2>A Reliable Base</h2>\n\n\n\n<p>Importers are an interesting technical problem. Much like you&#8217;d expect from any backup/restore code, importers need to be extremely reliable. They need to comfortable handle all sorts of unusual data, and they need to keep it all safe. Particularly considering their age, the WordPress Importers do a remarkably good job of handling most content you can throw at it.</p>\n\n\n\n<p>However, modern development practices have evolved and improved since the importers were first written, and we should certainly be making use of such practices, when they fit with our requirements.</p>\n\n\n\n<p>For building reliable software that we expect to largely run by itself, a variety of comprehensive automated testing is critical. This ensures we can confidently take on the broader issues, safe in the knowledge that we have a reliable base to work from.</p>\n\n\n\n<p>Testing <em>must</em> be the first item on this list. A variety of automated testing gives us confidence that changes are safe, and that the code can continue to be maintained in the future.</p>\n\n\n\n<p>Data formats must be well defined. While this is useful for ensuring data can be handled in a predictable fashion, it&#8217;s also a very clear demonstration of our commitment to data freedom.</p>\n\n\n\n<p>APIs for creating or extending importers should be straightforward for hooking into.</p>\n\n\n\n<h3>Performance Isn&#8217;t an Optional Extra</h3>\n\n\n\n<p>With sites constantly growing in size (and with the export files potentially gaining a heap of extra data), we need to care about the performance of the importers.</p>\n\n\n\n<p>Luckily, there&#8217;s already been some substantial work done on this front:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"wp-embedded-content\"><a href=\"https://make.wordpress.org/core/2015/11/18/wordpress-importer-redux/\">WordPress Importer Redux</a></blockquote>\n</div>\n\n\n\n<p>There are other groups in the WordPress world who&#8217;ve made performance improvements in their own tools: gathering all of that experience is a relatively quick way to bring in production-tested improvements.</p>\n\n\n\n<h2>The WXR Format</h2>\n\n\n\n<p>It&#8217;s worth talking about the WXR format itself, and determining whether it&#8217;s the best option for handling exports into the future. XML-based formats are largely viewed as a relic of days gone past, so (if we were to completely ignore backwards compatibility for a moment) is there a modern data format that would work better?</p>\n\n\n\n<p>The short answer&#8230; kind of. <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" /></p>\n\n\n\n<p>XML is actually well suited to this use case, and (particularly when looking at performance improvements) is the only data format for which PHP comes with a built-in streaming parser.</p>\n\n\n\n<p>That said, WXR is basically an extension of the RSS format: as we add more data to the file that clearly doesn&#8217;t belong in RSS, there is likely an argument for defining an entirely WordPress-focused schema.</p>\n\n\n\n<h3>Alternative Formats</h3>\n\n\n\n<p>It&#8217;s important to consider what the priorities are for our export format, which will help guide any decision we make. So, I&#8217;d like to suggest the following priorities (in approximate priority order):</p>\n\n\n\n<ul><li><strong>PHP Support</strong>: The format should be natively supported in PHP, thought it is still workable if we need to ship an additional library.</li><li><strong>Performant</strong>: Particularly when looking at very large exports, it should be processed as quickly as possible, using minimal RAM.</li><li><strong>Supports Binary Files</strong>: <a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/#comment-37926\">The first comments on my previous post</a> asked about media support, we clearly should be treating it as a first-class citizen.</li><li><strong>Standards Based</strong>: Is the format based on a documented standard? (Another way to ask this: are there multiple different implementations of the format? Do those implementations all function the same?</li><li><strong>Backward Compatible</strong>: Can the format be used by existing tools with no changes, or minimal changes?</li><li><strong>Self Descriptive</strong>: Does the format include information about what data you&#8217;re currently looking at, or do you need to refer to a schema?</li><li><strong>Human Readable</strong>: Can the file be opened and read in a text editor?</li></ul>\n\n\n\n<p>Given these priorities, what are some options?</p>\n\n\n\n<h4>WXR (XML-based)</h4>\n\n\n\n<p>Either the RSS-based schema that we already use, or a custom-defined XML schema, the arguments for this format are pretty well known.</p>\n\n\n\n<p>One argument that hasn&#8217;t been well covered is how there&#8217;s a definite trade-off when it comes to supporting binary files. Currently, the importer tries to scrape the media file from the original source, which is not particularly reliable. So, if we were to look at including media files in the WXR file, the best option for storing them is to base64 encode them. Unfortunately, that would have a serious effect on performance, as well as readability: adding huge base64 strings would make even the smallest exports impossible to read.</p>\n\n\n\n<p>Either way, this option would be mostly backwards compatible, though some tools may require a bit of reworking if we were to substantial change the schema.</p>\n\n\n\n<h4>WXR (ZIP-based)</h4>\n\n\n\n<p>To address the issues with media files, an alternative option might be to follow the path that Microsoft Word and OpenOffice use: put the text content in an XML file, put the binary content into folders, and compress the whole thing. </p>\n\n\n\n<p>This addresses the performance and binary support problems, but is initially worse for readability: if you don&#8217;t know that it&#8217;s a ZIP file, you can&#8217;t read it in a text editor. Once you unzip it, however, it does become quite readable, and has the same level of backwards compatibility as the XML-based format.</p>\n\n\n\n<h4>JSON</h4>\n\n\n\n<p>JSON could work as a replacement for XML in both of the above formats, with one additional caveat: there is no streaming JSON parser built in to PHP. There are 3rd party libraries available, but given <a href=\"http://seriot.ch/parsing_json.php\">the documented differences between JSON parsers</a>, I would be wary about using one library to produce the JSON, and another to parse it.</p>\n\n\n\n<p>This format largely wouldn&#8217;t be backwards compatible, though tools which rely on the export file being plain text (eg, command line tools to do broad search-and-replaces on the file) can be modified relatively easily.</p>\n\n\n\n<p>There are additional subjective arguments (both for and against) the readability of JSON vs XML, but I&#8217;m not sure there&#8217;s anything to them beyond personal preference.</p>\n\n\n\n<h4>SQLite</h4>\n\n\n\n<p>The <a href=\"https://sqlite.org/index.html\">SQLite</a> team wrote <a href=\"https://www.sqlite.org/affcase1.html\">an interesting (indirect) argument</a> on this topic: OpenOffice uses a ZIP-based format for storing documents, the SQLite team argued that there would be benefits (particularly around performance and reliability) for OpenOffice to switch to SQLite.</p>\n\n\n\n<p>They key issues that I see are:</p>\n\n\n\n<ul><li>SQLite is included in PHP, but <a href=\"https://www.php.net/manual/en/sqlite3.installation.php\">not enabled by default on Windows</a>.</li><li>While the SQLite team have a strong commitment to providing long-term support, SQLite is not a standard, and the only implementation is the one provided by the SQLite team.</li><li>This option is not backwards compatible at all.</li></ul>\n\n\n\n<h4>FlatBuffers</h4>\n\n\n\n<p><a href=\"http://google.github.io/flatbuffers/\">FlatBuffers</a> is an interesting comparison, since it&#8217;s a data format focussed entirely on speed. The down side of this focus is that it <em>requires</em> a defined schema to read the data. Much like SQLite, the only standard for FlatBuffers is the implementation. Unlike SQLite, FlatBuffers has made no commitments to providing long-term support.</p>\n\n\n\n<table class=\"has-fixed-layout\"><thead><tr><th></th><th class=\"has-text-align-center\">WXR (XML-based)</th><th class=\"has-text-align-center\">WXR (ZIP-based)</th><th class=\"has-text-align-center\">JSON</th><th class=\"has-text-align-center\">SQLite</th><th class=\"has-text-align-center\">FlatBuffers</th></tr></thead><tbody><tr><td>Works in PHP?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td></tr><tr><td>Performant?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td></tr><tr><td>Supports Binary Files?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td></tr><tr><td>Standards Based?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /> / <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td></tr><tr><td>Backwards Compatible?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td></tr><tr><td>Self Descriptive?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td></tr><tr><td>Readable?</td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/26a0.png\" alt=\"⚠\" class=\"wp-smiley\" /> / <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/2705.png\" alt=\"✅\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td><td class=\"has-text-align-center\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/274c.png\" alt=\"❌\" class=\"wp-smiley\" /></td></tr></tbody></table>\n\n\n\n<p>As with any decision, this is a matter of trade-offs. I&#8217;m certainly interested in hearing additional perspectives on these options, or thoughts on options that I haven&#8217;t considered.</p>\n\n\n\n<p>Regardless of which particular format we choose for storing WordPress exports, every format should have (or in the case of FlatBuffers, <em>requires</em>) a schema. We can talk about schemata without going into implementation details, so I&#8217;ll be writing about that in the next post.</p>\n\n\n\n<div class=\"wp-block-group is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p><em>This post is part of a series, talking about the WordPress Importers, their history, where they are now, and where they could go in the future.</em></p>\n\n\n\n<ul><li><em><a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\">Part 1: Stating the Problem</a></em></li><li><em><a href=\"https://pento.net/2021/01/19/wordpress-importers-getting-our-house-in-order/\">Part 2: Getting Our House in Order</a></em></li><li><em><a href=\"https://pento.net/2021/01/20/wordpress-importers-defining-a-schema/\">Part 3: Defining a Schema</a></em></li><li><a href=\"https://pento.net/2021/01/21/wordpress-importers-free-as-in-speech/\"><em>Part 4: Free (as in Speech)</em></a></li></ul>\n\n\n\n<p></p>\n</div></div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Jan 2021 22:50:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Gary\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:23;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"WPTavern: Kinsta Launches Free Local WordPress Development Tool\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110351\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/kinsta-launches-free-local-wordpress-development-tool?utm_source=rss&utm_medium=rss&utm_campaign=kinsta-launches-free-local-wordpress-development-tool\";s: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:5961:\"<p class=\"has-drop-cap\">Kinsta, a managed WordPress hosting company, announced its local development tool named <a href=\"https://kinsta.com/devkinsta/\">DevKinsta</a> earlier today. The tool allows developers to spin up new WordPress sites, including multisite support, in moments. Each site is automatically configured with Nginx, PHP, and MySQL.</p>\n\n\n\n<p>DevKinsta packages Adminer, an open-source database manager. The system also includes an SMTP server and email inbox for testing outgoing emails locally.</p>\n\n\n\n<p>&ldquo;This is the first version of the tool, let&rsquo;s say the MVP, but we have a dedicated development team supporting and adding a lot of new features to it,&rdquo; said Tom Zsomborgi, Kinsta&rsquo;s Chief Business Officer.</p>\n\n\n\n<p>Developers can run and test HTTPS support and enable <code>WP_DEBUG</code> at the flip of a switch. Kinsta web hosting customers can also deploy their sites directly from the interface.</p>\n\n\n\n<p>It took me around an hour to get the system set up and running. To be more exact, I spent 53 minutes. Close enough. Between having to sign out, restart my laptop, and waiting for various pieces to install, I at least managed to get a little laundry done in those dull, in-between moments.</p>\n\n\n\n<img />Installing DevKinsta on Windows.\n\n\n\n<p>The setup process was not a completely pain-free affair. However, the price of admission to use this tool &mdash; a little bit of my time &mdash; was well worth it.</p>\n\n\n\n<p>Let me be clear. I have tested far worse systems. Even with over 15 years of development experience under my belt, I have utterly failed at setting up other local dev environments. For DevKinsta to simply get me to the finish line is a success.</p>\n\n\n\n<p>However, I like simple things, and I prefer them to move along relatively quickly. I am accustomed to a 20-minute XAMPP setup. While it may not be as fancy or have the bells and whistles of more sophisticated development tools, it gets the job done and rarely doles out headaches.</p>\n\n\n\n<p>The holdup was setting up Windows Subsystem for Linux (WSL 2) and Docker, which are both requirements. Jump-starting DevKinsta itself was a breeze. And, as an old-school XAMPP user, DevKinsta&rsquo;s ease of use has pulled me in enough to do more than just give it a passing glance. I could actually see myself using this on a day-to-day basis.</p>\n\n\n\n<p>In short, I am sold. DevKinsta is a tool all WordPress developers should at least spin up once.</p>\n\n\n\n<p>Thus far, the <a href=\"https://twitter.com/kinsta/status/1351177344740941829\">feedback on Twitter</a> has been generally positive. However, Linux users may have to wait a bit because the tool is only available for macOS and Windows at the moment.</p>\n\n\n\n<p>&ldquo;I love seeing companies releasing local development tools but I wish more would offer their services to Linux users,&rdquo; <a href=\"https://twitter.com/chadmccullough/status/1351195217483988998\">tweeted</a> WordPress developer Chad McCullough. &ldquo;There are a lot of us developers out there running Linux.&rdquo; The Kinsta team responded that the tool will eventually support Linux and that news is forthcoming.</p>\n\n\n\n<img />Spinning up a new WordPress site.\n\n\n\n<p>The simple and straightforward UI is what makes this tool useful. Most developers do not need overly complicated configurations and options. They simply need to launch an environment that lets them work on their own projects. Anything beyond the basics far too often gets in the way.</p>\n\n\n\n<p>DevKinsta makes it easy to launch and manage multiple development installs. Developers can also switch PHP versions via a simple dropdown &mdash; versions 7.2 &ndash; 8.0 are currently supported.</p>\n\n\n\n<img />Site management screen.\n\n\n\n<p>The obvious comparison for DevKinsta will be against <a href=\"https://localwp.com/\">Local by Flywheel</a>, which has increasingly become a primary tool for many WordPress developers.</p>\n\n\n\n<p>Zsomborgi explained why the company thinks DevKinsta is a better option. &ldquo;In our case, Docker is an important part here. Local doesn&rsquo;t use virtualization in the background. Local has to install every piece of the environment to the host machine (NGINX, apache, different PHP versions, etc.). DevKinsta encapsulates these technologies into containers. Containers do make things easier for maintaining different applications without interrupting the host OS or installing many of the dependencies that are not required. We pretty much don&rsquo;t touch the host OS, but have Docker as our main dependency to run the applications on their own environments.&rdquo;</p>\n\n\n\n<p>He said this speeds up the upgrade process and makes it easier to maintain bug fixes and send out security patches. He also said that because each application runs on its own Kernel namespace, any security issues should not affect the host OS.</p>\n\n\n\n<p>&ldquo;If the user is comfortable enough with Docker, he can extend DevKinsta features,&rdquo; said Zsomborgi. &ldquo;For example, he can monitor the usage of the container, or the PHP usage specifically as an example with docker monitoring tools that comes out of the box with Docker installation. The user can install any utility inside DevKinsta containers without touching the host OS and use applications that are not supported on Windows, for example.&rdquo;</p>\n\n\n\n<p>One of the use cases he mentioned was installing a benchmark tool to get statistics about site performance. This can be installed inside the Nginx container as a sidecar or separate container.</p>\n\n\n\n<p>&ldquo;In the past, Local didn&rsquo;t use exactly Docker,&rdquo; said Zsomborgi. &ldquo;They used VirtualBox + DockerMachine. We tried it, and it was a bit painful. But without VirtualBox, DevKinsta can be more stable and scalable. So we use Docker without VirtualBox. It also needs virtualization, but nowadays, there are fewer Windows computers that have disabled virtualization by default.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Jan 2021 21:07:16 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:46:\"Gary: WordPress Importers: Stating the Problem\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=5449\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\";s: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:8838:\"<p>It&#8217;s time to focus on the WordPress Importers.</p>\n\n\n\n<p>I&#8217;m not talking about tidying them up, or improve performance, or fixing some bugs, though these are certainly things that should happen. Instead, we need to consider their purpose, how they fit as a driver of WordPress&#8217; commitment to Open Source, and how they can be a key element in helping to keep the Internet Open and Free.</p>\n\n\n\n<h2>The History</h2>\n\n\n\n<p>The WordPress Importers are arguably <em>the</em> key driver to WordPress&#8217; early success. Before the importer plugins existed (before WordPress even supported plugins!) there were a handful of <code>import-*.php</code> scripts in the <a href=\"https://core.trac.wordpress.org/browser/trunk/wp-admin?rev=688\"><code>wp-admin</code> directory</a> that could be used to import blogs from other blogging platforms. When other platforms fell out of favour, WordPress already had an importer ready for people to move their site over. One of the most notable instances was in 2004, <a href=\"https://github.com/WordPress/book/blob/trunk/Content/Part%202/9-freedom-zero.md\">when Moveable Type changed their license and prices</a>, suddenly requiring personal blog authors to pay for something that had previously been free. WordPress was fortunate enough to be in the right place at the right time: many of WordPress&#8217; earliest users came from Moveable Type.</p>\n\n\n\n<p>As time went on, WordPress became well known in its own right. Growth relied less on people wanting to switch from another provider, and more on people choosing to start their site with WordPress. For <a href=\"https://core.trac.wordpress.org/ticket/13307\">practical reasons</a>, the importers were moved out of WordPress Core, and into their own plugins. Since then, they&#8217;ve largely been in maintenance mode: bugs are fixed when they come up, but since export formats rarely change, they&#8217;ve just continued to work for all these years.</p>\n\n\n\n<p>An unfortunate side effect of this, however, is that new importers are rarely written. While a new breed of services have sprung up over the years, the WordPress importers haven&#8217;t kept up.</p>\n\n\n\n<h2>The New Services</h2>\n\n\n\n<p>There are many new CMS services that have cropped up in recent years, and we don&#8217;t have importers for any of them. WordPress.com has a few extra ones written, but they&#8217;ve been built on the WordPress.com infrastructure out of necessity.</p>\n\n\n\n<p>You see, we&#8217;ve always assumed that other CMSes will provide some sort of export file that we can use to import into WordPress. That isn&#8217;t always the case, however. Some services (notable, <a href=\"https://support.wix.com/en/article/exporting-or-embedding-your-wix-site-elsewhere\">Wix</a> and <a href=\"https://godaddy.com/community/Websites-Marketing-Website/Exporting-Website-Builder-Site-to-Word-Press/td-p/124526\">GoDaddy Website Builder</a>) deliberately don&#8217;t allow you to export your own content. Other services provide incomplete or fragmented exports, needlessly forcing stress upon site owners who want to use their own content outside of that service.</p>\n\n\n\n<p>To work around this, WordPress.com has implemented importers that effectively scrape the site: while this has worked to some degree, it does require regular maintenance, and the importer has to do a lot of guessing about how the content should be transformed. This is clearly not a solution that would be maintainable as a plugin.</p>\n\n\n\n<div class=\"wp-block-group alignwide is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p class=\"has-text-align-center\">Problem Number 4</p>\n\n\n\n<p class=\"alignwide has-extra-large-font-size\"><strong>Some services work against their customers, and actively prevent site owners from controlling their own content.</strong></p>\n</div></div>\n\n\n\n<p>This strikes at the heart of the <a href=\"https://wordpress.org/about/#bill-of-rights\">WordPress Bill of Rights</a>. WordPress is built with fundamental freedoms in mind: all of those freedoms point to owning your content, and being able to make use of it in any form you like. When a CMS actively works against providing such freedom to their community, I would argue that we have an obligation to help that community out.</p>\n\n\n\n<h2>A Variety of Content</h2>\n\n\n\n<p>It&#8217;s worth discussing how, when starting a modern CMS service, the bar for success is very high. You can&#8217;t get away with just providing a basic CMS: you need to provide all the options. Blogs, eCommerce, mailing lists, forums, themes, polls, statistics, contact forms, integrations, embeds, the list goes on. The closest comparison to modern CMS services is&#8230; the <em>entire</em> WordPress ecosystem: built on WordPress core, but with the myriad of plugins and themes available, along with the variety of services offered by a huge array of companies.</p>\n\n\n\n<p>So, when we talk about the importers, we need to consider how they&#8217;ll be used.</p>\n\n\n\n<div class=\"wp-block-group alignwide is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p class=\"has-text-align-center\">Problem Number 3</p>\n\n\n\n<p class=\"alignwide has-extra-large-font-size\"><strong>To import from a modern CMS service into WordPress, your importer needs to map from service features to WordPress plugins.</strong></p>\n</div></div>\n\n\n\n<h2>Getting Our Own House In Order</h2>\n\n\n\n<p>Some of these problems don&#8217;t just apply to new services, however.</p>\n\n\n\n<p>Out of the box, WordPress exports to WXR (WordPress eXtended RSS) files: an XML file that contains the <em>content</em> of the site. Back when WXR was first created, this was all you really needed, but much like the rest of the WordPress importers, it hasn&#8217;t kept up with the times. A modern WordPress site isn&#8217;t just the sum of its content: a WordPress site has plugins and themes. It has various options configured, it has huge quantities of media, it has masses of text content, far more than the first WordPress sites ever had.  </p>\n\n\n\n<div class=\"wp-block-group alignwide is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p class=\"has-text-align-center\">Problem Number 2</p>\n\n\n\n<p class=\"alignwide has-extra-large-font-size\"><strong>WXR doesn&#8217;t contain a full export of a WordPress site.</strong></p>\n</div></div>\n\n\n\n<p>In my view, WXR is a solid format for handling exports. An XML-based system is quite capable of containing all forms of content, so it&#8217;s reasonable that we could expand the WXR format to contain the entire site.</p>\n\n\n\n<h2>Built for the Future</h2>\n\n\n\n<p>If there&#8217;s one thing we can learn from the history of the WordPress importers, it&#8217;s that maintenance will potentially be sporadic. Importers are unlikely to receive the same attention that the broader WordPress Core project does, owners may come and go. An importer will get attention if it breaks, of course, but it otherwise may go months or years without changing.</p>\n\n\n\n<div class=\"wp-block-group alignwide is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p class=\"has-text-align-center\">Problem Number 1</p>\n\n\n\n<p class=\"alignwide has-extra-large-font-size\"><strong>We can&#8217;t depend on regular importer maintenance in the future.</strong></p>\n</div></div>\n\n\n\n<p>It&#8217;s quite possible to build code that will be running in 10+ years: we see examples all across the WordPress ecosystem. Doing it in a reliable fashion needs to be a deliberate choice, however.</p>\n\n\n\n<h2>What&#8217;s Next?</h2>\n\n\n\n<p>Having worked our way down from the larger philosophical reasons for the importers, to some of the more technically-oriented implementation problems; I&#8217;d like to work our way back out again, focussing on each problem individually. In the following posts, I&#8217;ll start laying out how I think we can bring our importers up to speed, prepare them for the future, and make them available for everyone.</p>\n\n\n\n<div class=\"wp-block-group is-style-twentytwentyone-border\"><div class=\"wp-block-group__inner-container\">\n<p><em>This post is part of a series, talking about the WordPress Importers, their history, where they are now, and where they could go in the future.</em></p>\n\n\n\n<ul><li><em><a href=\"https://pento.net/2021/01/18/wordpress-importers-stating-the-problem/\">Part 1: Stating the Problem</a></em></li><li><em><a href=\"https://pento.net/2021/01/19/wordpress-importers-getting-our-house-in-order/\">Part 2: Getting Our House in Order</a></em></li><li><em><a href=\"https://pento.net/2021/01/20/wordpress-importers-defining-a-schema/\">Part 3: Defining a Schema</a></em></li><li><a href=\"https://pento.net/2021/01/21/wordpress-importers-free-as-in-speech/\"><em>Part 4: Free (as in Speech)</em></a></li></ul>\n\n\n\n<p></p>\n</div></div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 Jan 2021 00:25:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Gary\";s: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:77:\"WPTavern: MapLibre Launches as Official Open Source Successor to Mapbox GL JS\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110489\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/maplibre-launches-as-official-open-source-successor-to-mapbox-gl-js?utm_source=rss&utm_medium=rss&utm_campaign=maplibre-launches-as-official-open-source-successor-to-mapbox-gl-js\";s: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:2864:\"<p>In December, Mapbox shocked its open source contributor community with the news that <a href=\"https://wptavern.com/mapbox-gl-js-is-no-longer-open-source\">Mapbox GL JS version 2.0 would be released under a proprietary license</a>. The JavaScript library powers interactive, customizable vector maps on many high profile websites like CNN, The New York Times, Ancestry, Strava, Shopify, Facebook, and more. Older versions remain open source but Mapbox will only be investing in developing new features for the proprietary version going forward.</p>\n\n\n\n<p>Multiple parties started their own forks immediately following Mapbox&rsquo;s announcement. In an effort to avoid fragmentation, the community worked together to merge their ideas under one project. One month later, <a href=\"https://github.com/maplibre/maplibre-gl-js\">MapLibre GL</a> is now the official open source successor to Mapbox GL JS. The project&rsquo;s founders represent a diverse group of companies who relied on the open source software, including MapTiler, Elastic, StadiaMaps, Microsoft, Ceres Imaging, WhereGroup, Jawg, Stamen Design, and more.</p>\n\n\n\n<p>&ldquo;In December 2020, Mapbox released the second version of their JavaScript library for publishing maps online,&rdquo; MapTiler founder and CEO Petr Pridal said. &ldquo;However, this time all the new features were overshadowed by a change in the license: previously free as in freedom, it became closed for external contributors and usage was restricted to people with active Mapbox subscriptions. One has to pay even for loading this JavaScript library.&rdquo;</p>\n\n\n\n<p>Pridal said the MapLibre project name is a shortened form of &ldquo;Map library restarted (or reinvented),&rdquo; with <em>libre</em> referring to freedom and independence. Its founders agreed that MapLibre should be provider-independent, so developers can load maps from their preferred providers or self-hosted maps.</p>\n\n\n\n<p> The community-led fork may also become home to <a href=\"https://github.com/maptiler/maplibre-gl-native\">MapLibre GL Native</a>, as contributors are considering a proposal to put MapTiler&rsquo;s open source fork of Mapbox&rsquo;s mobile map SDKs for Android and iOS under the MapLibre umbrella.</p>\n\n\n\n<p>Mapbox is used by <a href=\"https://jetpack.com/support/jetpack-blocks/map-block/\">WordPress.com</a> as well as in Jetpack for the <a href=\"https://jetpack.com/support/jetpack-blocks/map-block/\">Map block</a>. The library is also used in many&nbsp;<a href=\"https://wordpress.org/plugins/search/mapbox/\">plugins</a>&nbsp;on WordPress.org, some with tens of thousands of users. Plugin developers who have integrated Mapbox GL JS version 1.13 or older will want to check out the <a href=\"https://github.com/maplibre/maplibre-gl-js\">MapLibre</a> project as an open source alternative to Mapbox&rsquo;s proprietary 2.0 update. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 15 Jan 2021 23:51:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:26;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"WPTavern: A Multi-Theme System, the Decade-Long Wait for Grandchild Themes, and Themeless Templates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110476\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:239:\"https://wptavern.com/a-multi-theme-system-the-decade-long-wait-for-grandchild-themes-and-themeless-templates?utm_source=rss&utm_medium=rss&utm_campaign=a-multi-theme-system-the-decade-long-wait-for-grandchild-themes-and-themeless-templates\";s: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:5994:\"<p class=\"has-drop-cap\">Around 2010, child theming had finally caught its stride. Bigger theme shops were starting to take note, and some were implementing advanced parent themes that were meant to serve as a &ldquo;framework&rdquo; for creating child themes. The theme development community hit a bit of a brick wall amid this explosion of child theming. Grandchild themes became a topic of debate.</p>\n\n\n\n<p>One of the use cases for child themes was to protect customizations made by end-users. When the parent theme was updated, those changes remained intact within the child theme. Users could get bug fixes and enhancements without worry. It was an ingenious system.</p>\n\n\n\n<p>However, another use case for child themes was to create vast customizations of the parent theme. Many of these child themes were marketed and sold to end-users. <em>The problem?</em> There was no way for users to protect their customizations if and when the developer updated the child theme. WordPress had no grandchild theme concept or any other sort of cascading theme system beyond the parent-child relationship.</p>\n\n\n\n<p>So, the problem remained. Unsolved.</p>\n\n\n\n<p>Some businesses such as StudioPress and its Genesis parent theme thrived over the years with this system. Others moved along. In reality, child theming became a niche feature that WordPress never expanded upon in any meaningful way. Theme authors were left to their own devices. With the arrival of the customizer and the expansion of page builders, code customizations almost disappeared. Most modifications were handled via an interface launched from the WordPress admin. The average user had little need to DIY their way through custom templates. Thus began child theming&rsquo;s drizzle into near obscurity.</p>\n\n\n\n<p>Gutenberg&rsquo;s site editor, which will likely land in WordPress this year, had seemed to be the upcoming final blow to the child theming paradigm. Everyone from developers to end-users will be able to roll out custom templates directly from the WordPress admin.</p>\n\n\n\n<p>However, should we be rethinking the role of a hierarchical theming system?</p>\n\n\n\n<p>Full Site Editing is already introducing an extra level to the hierarchy. Traditionally, WordPress theming had a two-tier template hierarchy. In the future, it will add a tier for user-created templates. If that is possible, why not go ahead and throw in grandchild themes? Or, simply do away with such arbitrary limitations altogether?</p>\n\n\n\n<p>A new pull request to the Gutenberg repository essentially <a href=\"https://github.com/WordPress/gutenberg/pull/28131\">creates a multi-theme system</a>. Or, rather, it creates a multi-theme templating system. Aside from the <code>style.css</code>, <code>functions.php</code>, and <code>theme.json</code> files, block-based themes are essentially a collection of templates.</p>\n\n\n\n<p>The patch is proposing that users should be able to opt into this multi-template system. They would have the option to keep templates from an old theme around when they switch to a new one. While not currently implemented in the pull request, he also proposes allowing users to clone templates from their old theme.</p>\n\n\n\n<p>&ldquo;In recent months, there have been whispers around the future possibility of multiple themes being active, templates being &lsquo;themeless,&rsquo; etc.,&rdquo; wrote the patch creator. &ldquo;This branch is an implementation of that. The idea behind this implementation is there can only be one active theme at a time, but the <code>wp_theme</code> taxonomy can be used to link up individual templates / template parts with one or more themes at a time.&rdquo;</p>\n\n\n\n<p>It does not fulfill the dreams of a decade-old grandchild theme system. However, it could provide some precedent for exploring a full hierarchical theme system.</p>\n\n\n\n<p>With the simplification and further standardization of how themes work, we should be dusting off old ideas and shoving them into a new light.</p>\n\n\n\n<p>Full Site Editing will eventually solve the grandchild theme problem regardless of whether it had intended to. With the new tier of custom user templates, the upgradability problem created years ago will simply disappear. Users will be able to readily update their parent and child themes without fear of losing customizations. WordPress will safely store their custom templates in the database. It will even keep their design changes via the Global Styles system. Maybe, just maybe, child themes will begin to reach their initial height of popularity.</p>\n\n\n\n<p>With the proposed system, users could mix and match templates from unrelated themes. If this happens, it begs the question of whether <em>theme</em> templates are even necessary.</p>\n\n\n\n<p>Last year, Rich Tabor opened a discussion on the possibility of a <a href=\"https://richtabor.com/the-future-of-wordpress-themes/\">single master theme</a> for WordPress. In that system, WordPress would create a set of base templates. Theme authors could simply override the pieces that they wanted. They could even pare themes down to simple <code>style.css</code> and <code>theme.json</code> files.</p>\n\n\n\n<p>That almost seems to be a recipe for bland and boring themes. However, if you couple it with a template directory on WordPress.org similar to what GutenbergHub has <a href=\"https://wptavern.com/gutenberg-hub-launches-landing-page-templates-directory\">already introduced</a>, users could pick and choose the templates they want. It could be both wondrous and disastrous, but I would not mind exploring the idea.</p>\n\n\n\n<p>WordPress and its Gutenberg project have a lot of options on the table. Theme building could become interesting in the next year or two.</p>\n\n\n\n<p class=\"is-style-highlight\"><strong>Update:</strong><em> some names have been removed from this post at the request of the people in question.  While this is not standard procedure, they were removed because they were not integral to the story in this instance.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 15 Jan 2021 21:04:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:83:\"WPTavern: New Local Blueprint Enables One-Click Setup for Testing 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=110252\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:211:\"https://wptavern.com/new-local-blueprint-enables-one-click-setup-for-testing-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=new-local-blueprint-enables-one-click-setup-for-testing-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:5484:\"<p>If you haven&rsquo;t yet tested the Gutenberg team&rsquo;s progress on the full site editing (FSE) project, WordPress developer Carrie Dils has created a <a href=\"https://carriedils.com/full-site-editing-blueprint-for-local/\">blueprint for Local</a> that makes it easy to jump right in. Full site editing is phase 2 on the Gutenberg roadmap and is one of the <a href=\"https://wptavern.com/wordpress-5-7-development-kicks-off-with-focus-on-full-site-editing\">main focuses</a> for WordPress core development in 2021. (Check out <a href=\"https://wptavern.com/what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress\">What Is Full Site Editing and What Does It Mean for the Future of WordPress</a> for a more in-depth look at why it is critical for end users to provide feedback during its development.)</p>\n\n\n\n<p><a href=\"https://localwp.com/\">Local</a> is one of the most popular free development tools for WordPress that allows users to set up new testing sites with one click, along with a host of more advanced features. Blueprints make it possible for users to save any site as a Blueprint so that it can be used as a quick start setup option later. The blueprint includes all files, databases, config files, and Local settings. Dils&rsquo; <a href=\"https://carriedils.com/full-site-editing-blueprint-for-local/\">full site editing blueprint</a> includes the following: </p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/gutenberg/\">Gutenberg</a>&nbsp;plugin (with &ldquo;Full Site Editing&rdquo; experiment enabled)</li><li><a href=\"https://github.com/WordPress/theme-experiments\">WordPress theme experiments</a>&nbsp;(these are themes with support for full site editing) with the Twenty Twenty-One Blocks theme enabled</li><li><a href=\"https://github.com/Automattic/theme-tools/tree/master/gutenberg-test-data\">Gutenberg test data</a>&nbsp;(demo blog posts that use the most common Gutenberg blocks)</li></ul>\n\n\n\n<p>Follow Dils&rsquo; instructions for downloading and installing the FSE blueprint on MacOS or Windows. Local does not yet have an easy way for installing and sharing blueprints to other Local users, so you will need to add it to the right place within the application&rsquo;s files. If you find that you don&rsquo;t have a Blueprints folder, it may be because it is hidden or because you have never created a blueprint before. Once the zip file is in the right location, you will see the full site editing blueprint among the advanced options when you set up a new site: </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Once your site is set up, you can start exploring the brave new world of full site editing. (Be prepared &ndash; it is far from production ready but FSE is at a critical time in its development where it needs testing from real users to be a success.) The Gutenberg plugin may need to be updated to the latest. Your new site editing playground can be launched from the Site Editor menu item. </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>On the frontend you will find the Twenty Twenty Blocks theme activated. You can also test using the <a href=\"https://wordpress.org/themes/tt1-blocks/\">Twenty Twenty-One (TT1) Blocks theme</a>, which was added to the WordPress.org Themes directory today, or any of the other experimental block based themes included in the blueprint. Click around, explore the template browser, try editing the template parts, change the global styles, and see how it&rsquo;s coming along. </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The current state of full site editing is rough. It&rsquo;s hard to tell a feature from a bug at times, but once you get familiar with navigating it you might consider joining the <a href=\"https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/\">FSE Outreach Experiment</a>. This is an effort to test different aspects of site editing in order to ground the interface in real world feedback as it is developed. For the past few weeks, contributors have been testing the interaction between editing a post versus editing templates. </p>\n\n\n\n<p>Anne McCarthy posted the <a href=\"https://make.wordpress.org/test/2020/12/23/fse-program-testing-call-1-template-editing/\">first call for testing</a> to the&nbsp;<a href=\"https://make.wordpress.org/test/\">Make Test</a>&nbsp;blog with instructions for participants. </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>This call for testing is designed to explore the interaction between the two editing experiences (post vs. template editing) to make sure it&rsquo;s clear when you&rsquo;re editing each, granular saving works properly, etc. Ultimately, being able to edit templates like index, single, or archive directly is a huge leap forward compared to what&rsquo;s been possible in the past! Unlocking this level of customization gives you far more control to build the site you want and this call for testing is to help ensure it&rsquo;s as intuitive as possible.</p></blockquote>\n\n\n\n<p>The second testing challenge should be published soon. Anyone can contribute by following along with the test script and leaving comments on the post or <a href=\"https://github.com/WordPress/gutenberg/issues\">logging them as issues on GitHub</a>. Participants are also invited to join the&nbsp;<a href=\"https://make.wordpress.org/core/tag/fse-outreach-experiment/\">#fse-outreach-experiment</a>&nbsp;channel on WordPress Slack for updates or questions regarding testing.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 15 Jan 2021 08:21:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:73:\"WPTavern: Show and Hide Content via the Block Visibility WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=110411\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/show-and-hide-content-via-the-block-visibility-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=show-and-hide-content-via-the-block-visibility-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5736:\"<p class=\"has-drop-cap\">Nick Diego&rsquo;s <a href=\"https://wordpress.org/plugins/block-visibility/\">Block Visibility</a> is not the only plugin to take on the challenge of controlling when blocks are visible on the front end. Other plugins like EditorsKit do a fine job of it. However, Block Visibility is a solution users should not overlook, even if they have already begun testing other options.</p>\n\n\n\n<p>Diego first released the plugin in August 2020. Since then, he has added routine updates that have added value without shifting its focus.</p>\n\n\n\n<p>One of the biggest reasons to use this plugin is that it is a standalone project. It is purely about doing one thing and doing it well. Its settings are all about giving users complete control over how they want to manage block visibility. From my experience with it, the plugin does its job better than alternatives.</p>\n\n\n\n<p>It may not have a large number of installs, but if its five-star rating on WordPress.org is any indication, it at least has a happy user base.</p>\n\n\n\n<p>Diego does have plans for a <a href=\"https://www.blockvisibilitywp.com/premium/\">pro add-on</a>. The tentative release date is set for Spring 2021. He seems to be moving forward with that launch after adding some foundational code in the recent version 1.4 release.</p>\n\n\n\n<p>&ldquo;As Block Visibility grows, there will be advanced and/or niche functionality that will be useful for certain users,&rdquo; wrote Diego in the <a href=\"https://www.blockvisibilitywp.com/whats-new-in-version-1-4/\">1.4 release announcement</a>. &ldquo;Think integrations with other third-party plugins. There will always be a free version of the plugin but some of these additional features will ultimately be provided by a premium (paid) add-on called Block Visibility Pro.&rdquo;</p>\n\n\n\n<p>In my previous job, one of my primary products focused on membership solutions. There is a seemingly endless number of possibilities that users dream up to control content visibility. I have little doubt that a pro add-on is necessary for catching all of the edge cases.</p>\n\n\n\n<h2>How the Plugin Works</h2>\n\n\n\n<p class=\"has-drop-cap\">Block Visibility is easy to use. End-users click a toggle switch, select from a date-picker, or tick a radio box. Their blocks are shown or hidden on the front end based on their selections. It does not get much simpler than that.</p>\n\n\n\n<p>The plugin adds a new &ldquo;Visibility&rdquo; tab for each block, which displays the visibility controls. The exception to this is for inner blocks. For example, the Columns block has controls, but the inner Column blocks do not. However, this can be enabled for inner blocks via the &ldquo;Full Control Mode&rdquo; on the plugin&rsquo;s settings screen.</p>\n\n\n\n<p>There are three primary types of options:</p>\n\n\n\n<ul><li>Hide the block from everyone.</li><li>Time-based start and stop dates for displaying.</li><li>Visibility by user role.</li></ul>\n\n\n\n<img />Block Visibility&rsquo;s controls in the inspector.\n\n\n\n<p>Hiding the block from everyone might be useful for users who are testing on a page or for blocks that are a work in progress. Start and stop dates create the potential for drip or trial content on membership-based sites, especially when combined with the role-based visibility options.</p>\n\n\n\n<p>These basic options will cover the majority of scenarios that the average user will need them for.</p>\n\n\n\n<p>One of the nicer features of the plugin is that it adds a transparent gray overlay, dashed border, and icon to each block that has visibility options set. This is shown when the block is not selected in the editor. It is one of those small touches that make the plugin useful.</p>\n\n\n\n<img />Overlay for blocks with visibility options.\n\n\n\n<p>There is one confusing piece of the UI. There are two instances where there is a &ldquo;public&rdquo; option. That label immediately makes me think that the block should be visible to everyone. However, reading the description is necessary. These options are for showing content to logged-out users only. I would rather see these two options renamed to &ldquo;logged out&rdquo; for clarity.</p>\n\n\n\n<h2>A Promising Future</h2>\n\n\n\n<p class=\"has-drop-cap\">While Block Visibility is a solid plugin right now, we are barely scratching the surface of what will be possible in the long run. In version 1.4, released two weeks ago, Diego added preliminary compatibility with Full Site Editing. This means visibility options will no longer be confined to the post or page content.</p>\n\n\n\n<p>&ldquo;Once every piece of content on a website is a &lsquo;block,&rsquo; you will be able to easily control the visibility of practically anything on a WordPress website,&rdquo; wrote Diego in the version 1.4 announcement post. &ldquo;From dynamic navigation menus to user specific headers and footers, the possibilities are endless!&rdquo;</p>\n\n\n\n<p>Gutenberg&rsquo;s site editor is a beta feature right now, but the plugin&rsquo;s integration seems to already work well. I ran a quick test to show a custom nav menu to shop customers only. I had no problems on my end.</p>\n\n\n\n<img />Setting visibility options for a menu in Gutenberg&rsquo;s site editor.\n\n\n\n<p>Users will not be limited to such basic needs in the future. Imagine showing ads in a sidebar to logged-out users. Imagine adding a time-sensitive holiday sale banner in the header. Imagine designing a homepage template that displays different content to subscribers vs. visitors.</p>\n\n\n\n<p>There are ways to do all of this today by piecing various plugins together, using custom shortcodes, or writing code. However, when an entire site is made of blocks, you only need one method to control anything&rsquo;s visibility. Literally.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 14 Jan 2021 22:23:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: WordPress Proposal To Align Release Cycle With Industry Standard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110354\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/wordpress-proposal-to-align-release-cycle-with-industry-standard?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-proposal-to-align-release-cycle-with-industry-standard\";s: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:7102:\"<p class=\"has-drop-cap\">Yesterday, Francesca Marano opened a <a href=\"https://make.wordpress.org/core/2021/01/12/recap-and-proposal-align-the-wordpress-release-cycle-with-the-industry-standard/\">proposal for changing the phases</a> of the core WordPress release cycle. It was a recap of a <a href=\"https://make.wordpress.org/core/2020/10/29/discussion-align-the-wordpress-release-cycle-with-the-industry-standard/\">discussion</a> the began in October 2020. The goal is to align the platform&rsquo;s phases with the larger development industry standard.</p>\n\n\n\n<p>Aside from naming, WordPress has mostly followed the software industry in how it tackles its release cycle. Following a well-known convention can make it easier for developers outside of the WordPress ecosystem to transition into it. It would also allow developers to follow cycles of other projects, many of which are WordPress dependencies. This sort of standardization is generally viewed as a good thing throughout the software development world.</p>\n\n\n\n<p>Based on the ongoing discussions since October, there is a consensus on renaming the phases to align with the standard. The following table shows what each phase would be renamed to:</p>\n\n\n\n<table class=\"has-subtle-pale-blue-background-color has-background\"><thead><tr><th class=\"has-text-align-right text-right\">Phase</th><th>Current Name</th><th>Proposed Name</th></tr></thead><tbody><tr><td class=\"has-text-align-right text-right\"><strong>1</strong></td><td>Planning and securing team leads</td><td>Preliminary Planning</td></tr><tr><td class=\"has-text-align-right text-right\"><strong>2</strong></td><td>Development work begins</td><td>Alpha</td></tr><tr><td class=\"has-text-align-right text-right\"><strong>3</strong></td><td>Beta</td><td>Beta</td></tr><tr><td class=\"has-text-align-right text-right\"><strong>4</strong></td><td>Release candidate</td><td>Release Candidate</td></tr><tr><td class=\"has-text-align-right text-right\"><strong>5</strong></td><td>Launch</td><td>General release</td></tr></tbody></table>\n\n\n\n<p>However, this is a two-part proposal. Simply renaming the phases does not change how the release cycle works. To follow the standard strictly, WordPress would need to change when code is committed too.</p>\n\n\n\n<h2>How To Handle the Beta Phase</h2>\n\n\n\n<p class=\"has-drop-cap\">There is one point of contention with how to handle the Beta stage. The standard calls for no additional code changes other than new bug fixes introduced earlier in the cycle. For the WordPress project, this creates a problem.</p>\n\n\n\n<p>WordPress will be 18 years old this year. Over the years, it has racked up a ton of older bugs. These are often fixed later in the cycle, sometimes during the Beta stage. These older bugs may not have been a part of the Preliminary Planning phase, but does that mean they should wait until the next release to go in? Strictly following the proposal, they should be put on hold.</p>\n\n\n\n<p>It would also introduce a hard freeze on any enhancements set for the release but incomplete.</p>\n\n\n\n<p>&ldquo;I worry that we aren&rsquo;t allowing space for older bugs that aren&rsquo;t specific to the planned features in the release,&rdquo; wrote Josepha Haden in a <a href=\"https://make.wordpress.org/core/2020/10/29/discussion-align-the-wordpress-release-cycle-with-the-industry-standard/#comment-40391\">comment on the initial discussion</a>. &ldquo;I also worry that by calling hard freeze earlier in the process we narrow the window for feature inclusion too much. I don&rsquo;t like limiting ourselves to feature specific bugs right now, since that excludes so many of our volunteer contributors. It&rsquo;s harder to work on features since they are complex and fast-moving, and older bugs present more opportunities for casual contributors.&rdquo;</p>\n\n\n\n<p>On the flip side, there is potential that a bug fix could introduce new, unforeseen bugs. The later it is added during Beta, the less likely such bugs are noticed before the General Release phase. Waiting for the next cycle provides more time for testing.</p>\n\n\n\n<p>One of the benefits of this system is that almost no new bugs would be created during Beta. This would allow volunteers to shift more efforts to testing and fixing issues that emerged in Alpha.</p>\n\n\n\n<p>WordPress has always marched to the beat of its own drum. It can more closely follow standards while breaking free from strict confines when it makes sense to do so for the project. Beta-stage bug fixes not intended for a particular release could be handled on a case-by-case basis. We have people in leadership positions who are capable of making these calls when they arise. With automatic updates for minor releases, I am less concerned about late-stage bugs.</p>\n\n\n\n<p>Tonya Mork <a href=\"https://make.wordpress.org/core/2020/10/29/discussion-align-the-wordpress-release-cycle-with-the-industry-standard/#comment-40380\">proposed two solutions</a> for defect work to continue in and around the release cycle. Both would require that WordPress branch off at Beta, providing contributors an avenue to push forward fixing bugs.</p>\n\n\n\n<p>The first proposal calls for an earlier feature freeze, providing two or three weeks before Beta 1. This period at the end of the Alpha phase would be solely dedicated to defect work.</p>\n\n\n\n<p>The second solution moves this defect work to overlap the previous release&rsquo;s Beta and Release Candidate. This allows work to continue during the time between major releases. It could also shorten the overall major release cycle.</p>\n\n\n\n<p>This second solution is also consistent with Joost de Valk&rsquo;s thoughts on handling defect work. &ldquo;I think we should just branch off earlier, and keep trunk open for normal business,&rdquo; <a href=\"https://make.wordpress.org/core/2020/10/29/discussion-align-the-wordpress-release-cycle-with-the-industry-standard/#comment-40393\">he said on the proposal</a>. &ldquo;That way, <em>everything</em> can be worked on all the time, but it won&rsquo;t be included in the next release depending on when you commit it. That&rsquo;s fine, every piece of open source software I know in the world works like that, except for WordPress.&rdquo;</p>\n\n\n\n<p>Many plugin and theme developers already find it tough to keep up when changes drop in the Beta or Release Candidate phases. Having a clear and defined point where changes land will benefit the extension ecosystem, also helping end-users in the long run. This second solution would do that.</p>\n\n\n\n<p>There is nothing wrong with combining both solutions either.  Since the plan would be to branch off at the Beta phase, the second solution is already in place by the act of branching.  The real discussion is over whether the project should dedicate a block of time during its Alpha stage that focuses purely on bug fixes.</p>\n\n\n\n<p>Comments on the proposal are open through January 20 before moving toward a final decision.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p>The next proposal: <a href=\"https://semver.org/\">semantic versioning</a>, anyone? <em>Anyone? Is this thing on?</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Jan 2021 21:52:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: WPScan Can Now Assign CVE Numbers for WordPress Core, Plugin, and Theme Vulnerabilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110347\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:235:\"https://wptavern.com/wpscan-can-now-assign-cve-numbers-for-wordpress-core-plugin-and-theme-vulnerabilities?utm_source=rss&utm_medium=rss&utm_campaign=wpscan-can-now-assign-cve-numbers-for-wordpress-core-plugin-and-theme-vulnerabilities\";s: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:3148:\"<p><a href=\"https://wpscan.com/\">WPScan</a>, a security company that maintains a database of WordPress vulnerabilities, has been officially designated as a CVE (Common Vulnerability and Exposures) Numbering Authority (CNA). The company joins <a href=\"https://cve.mitre.org/cve/request_id.html#cna_participants\">151</a>&nbsp;organizations from&nbsp;<a href=\"https://cve.mitre.org/cve/cna.html#cnas_growth\">25</a>&nbsp;countries that participate in the <a href=\"https://cve.mitre.org/\">CVE Program</a> as CNAs. These organizations are authorized to assign&nbsp;<a href=\"https://cve.mitre.org/about/terminology.html#cve_id\">CVE Identifiers (CVE IDs)</a>&nbsp;to vulnerabilities within their own distinct scopes of work, contributing to CVE&rsquo;s <a href=\"https://cve.mitre.org/cve/\">list</a>&nbsp;of records for publicly known security vulnerabilities.</p>\n\n\n\n<p>WPScan&rsquo;s scope includes WordPress core, plugin, and theme vulnerabilities. The company has catalogued more than 21,905 vulnerabilities since 2014 in its database, which it makes available to the community through an API. That API is also used by the <a href=\"https://wordpress.org/plugins/wpscan/\">WPScan Security Scanner</a> plugin, which is installed on 5,000+ websites. </p>\n\n\n\n<p>Being designated as a CNA helps WPScan better manage WordPress vulnerabilities by assigning them unique IDs that are recognized across the industry.</p>\n\n\n\n<p>&ldquo;Asking MITRE to assign CVEs for each of our vulnerabilities would have been too time consuming in the past,&rdquo; WPScan founder and CEO Ryan Dewhurst said. &ldquo;Although some security researchers will go through this process directly with MITRE, we didn&rsquo;t due to the volume of vulnerabilities we have to manage. And security researchers only requested them themselves very rarely. The new process means that we ourselves can assign CVE numbers directly to vulnerabilities. This will result in many more WordPress related vulnerabilities being assigned CVE numbers.&rdquo;</p>\n\n\n\n<p>WPScan is a team of three security researchers who come from penetration testing backgrounds and have worked within security consulting for the past 10 to 15 years. The company started with a simple Ruby script in 2011, which identified vulnerabilities in self-hosted WordPress sites. For the past two years, Automattic has sponsored the company&rsquo;s efforts in maintaining the database, as WPScan has transitioned to become a sustainable business by selling access to its API.</p>\n\n\n\n<p>Dewhurst said the company&rsquo;s customers include &ldquo;some of the biggest security plugins and hosting companies in the world,&rdquo; but many of them don&rsquo;t advertise the fact that use a third-party to source the vulnerabilities. Most of WPScan&rsquo;s enterprise customers are security plugins, companies, and hosts that integrate data from the vulnerability database into their own products and services.</p>\n\n\n\n<p>&ldquo;Our business is doing well,&rdquo; he said. &ldquo;Right now we are trying to find the right balance between being a business and making money, while also benefiting the community as much as possible.&rdquo; </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Jan 2021 20:52:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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: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:73:\"WPTavern: Google Introduces Performance Report for Google News Publishers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110267\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/google-introduces-performance-report-for-google-news-publishers?utm_source=rss&utm_medium=rss&utm_campaign=google-introduces-performance-report-for-google-news-publishers\";s: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:2915:\"<p>Google has <a href=\"https://developers.google.com/search/blog/2021/01/google-news-performance-report\">launched</a> a new Search Console performance report for sites that appear in Google News. Publishers can now track clicks, impressions, and CTR for traffic coming from <a href=\"https://news.google.com/\">news.google.com</a> and the Google News apps for Android and iOS.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The report helps publishers see how often their articles appear to users in Google News and which ones performed the best. It also includes breakdowns for countries, devices, and dates to give publishers a better overall understanding of how visitors are interacting with their content through Google News. Although the date period defaults to the last three months, the data only goes as far back as December 15, 2020.</p>\n\n\n\n<p>In the past, publishers had to submit their sites to be eligible for inclusion in Google News but the policy <a href=\"https://support.google.com/news/publisher-center/answer/9607025\">changed in 2019</a>. Sites are now automatically considered for Top stories or the News tab of Search as long as they &ldquo;produce high-quality content and comply with Google News content policies.&rdquo; </p>\n\n\n\n<p>This new report does not include stats from the News tab on Google Search. That information was added in July 2020, when Google updated the Performance report section of its Search Console to allow publishers to filter by News. This screen also lets users compare different traffic sources, i.e. Web vs News to see the impact of articles showing up under the News tab.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The new report can be grouped by dimensions to get more specific information with different combinations of date ranges, reader locations, devices, and pages. For example, you can get a detailed look at clicks, impressions, and average CTR on a per country basis. This can also be filtered for one certain article to explore more narrow branches of the content&rsquo;s reach.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Publishers who are using AMP will want to note that this new report includes data from the canonical URL. If you have multiple versions for different devices, the report contains data for both:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Data will only be shown in the property that contains the canonical URL. Therefore, if you have both&nbsp;AMP and desktop versions of a page, the desktop property (which is usually the canonical property) will contain all the data for both AMP and desktop clicks, impressions, and CTR.</p></blockquote>\n\n\n\n<p>Google has published a <a href=\"https://support.google.com/webmasters/answer/10083653?hl=en&ref_topic=9384513\">help document</a> with more information on configuring the report, data discrepancies, and how to filter and compare data across groups.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 13 Jan 2021 03:54:38 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:72:\"WPTavern: Ask the Bartender: How to Build WordPress Themes from Scratch?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110276\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/ask-the-bartender-how-to-build-wordpress-themes-from-scratch?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-how-to-build-wordpress-themes-from-scratch\";s: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:9037:\"<img />\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I would like to ask, what is the best way to learn to create WordPress themes from scratch? I would like to learn, but there seems to be no comprehensive resource for this.</p><p>Thanks for any help.</p><p>Mark</p></blockquote>\n\n\n\n<p class=\"has-drop-cap\">I have been around the WordPress community long enough to remember the days when there were sparse resources available. Those who were just starting out with theme development 15 or more years ago usually resorted to hacking away at an existing WordPress theme. Budding theme authors were building upon the shoulders of those few giants who had already taken the first steps. It was the magic of open-source at work &mdash; development learned through the act of forking.</p>\n\n\n\n<p>Maybe it is the way I learned. Perhaps it is part nostalgia for those early days of going down an unknown path and arriving at the other side with a creation of all my own. But, I still believe the best way to learn any type of development cannot be found in documentation or books (<em>says the co-author of a development book</em>).</p>\n\n\n\n<p>It is learned through trial and error.</p>\n\n\n\n<p>It is learned through hours of mangling a project and not stopping until you fix it.</p>\n\n\n\n<p>It is learned through sheer force of will, fueled by some innate passion within you that wants to see a project through. It is frustrating, but you keep going because you are having fun.</p>\n\n\n\n<p>The best developers I have had the privilege to work with were not always the most knowledgeable. They were seemingly natural problem solvers. However, they did not awake one day with this ability. They earned it through years of tackling real problems.</p>\n\n\n\n<p>First and foremost, the best resource for learning to build themes is an existing WordPress theme. Any of the default Twenty* themes are great starting points. Choose one, start making changes via your code editor, refresh your browser, and see what happens. Read the code. Look for patterns across various files.</p>\n\n\n\n<p>You will not learn theme development overnight. It will probably take a few months before you are building basic themes from scratch. It will probably be a year before you are actually good at it. However, everyone is different. The amount of time you put into it is a factor. Your preexisting development knowledge and skills can change that. Sometimes, your innate gifts and ability to learn play into it. But, you will get there with a bit of effort.</p>\n\n\n\n<p>I will be honest. The old-timers here in the community, those of us who started out early in WordPress&rsquo;s history, had some help. Tung Do, known as Small Potato at the time, wrote one of the most comprehensive tutorial series on theme development the community has ever had on his now-defunct web design blog. It was an invaluable resource for several years. It was the answer to the missing documentation that everyone was asking for.</p>\n\n\n\n<p>Theme development was also far simpler during that time. With a handful of files and templates, you could build something special.</p>\n\n\n\n<p>Today, the landscape is much different. If you want to be competitive as a theme shop owner or build custom solutions for clients, you need a broader skillset. Even as a hobbyist, you need to pick up a few more things than you would have a decade and a half ago.</p>\n\n\n\n<p>There is good news: the community is teeming with useful resources.</p>\n\n\n\n<h2>Traditional vs. Block-Based Themes</h2>\n\n\n\n<img />\n\n\n\n<p class=\"has-drop-cap\">The theme development market is nearing an inflection point. WordPress will be introducing more and more tools for <a href=\"https://wptavern.com/what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress\">Full Site Editing</a> in 2021, and this trend will continue in the years beyond. Traditional theme development will be around for a while &mdash; likely a few more years. However, block-based themes are the long-term bet. While there is some crossover between the two, they are entirely different systems.</p>\n\n\n\n<p>Realistically, you will need to learn both methods, especially if you have financial motives for going down this journey.</p>\n\n\n\n<p>However, you should learn traditional theme development first. This will make it easier to transition down the road. There are far more resources available too.</p>\n\n\n\n<p>Another issue with learning block-based theme development as a starting point is that you may not know whether you are at fault if something is broken. The features that make up Full Site Editing are in a rough beta stage. The experience is still a partially broken one. Beginner theme authors should not pile onto what can sometimes be a frustrating experience.</p>\n\n\n\n<p>It is time to start reading about Full Site Editing and testing block-based themes like <a href=\"https://wordpress.org/themes/q/\">Q</a> and <a href=\"https://wordpress.org/themes/block-based-bosco/\">Block-Based Bosco</a>. Then, wait for others as they become available in the <a href=\"https://wordpress.org/themes/tags/full-site-editing/\">theme directory.</a></p>\n\n\n\n<h2>Resources to Begin Theme Development</h2>\n\n\n\n<img />\n\n\n\n<p class=\"has-drop-cap\">Many people will point you to starter themes, command-line scripts, and other automated tools for kick-starting your theme development journey. However, there is no substitute for building a solid foundation.</p>\n\n\n\n<p>I will assume you have some basic or intermediate HTML and CSS knowledge under your belt. If not, you should learn to build simple web pages first. Again, there is no substitute for building that foundation. It will carry you through as you get into more advanced topics. Knowing some basic PHP helps too. However, you can hack your way through your first WordPress theme with just WordPress &ldquo;template tags,&rdquo; which are technically PHP functions that sound less scary.</p>\n\n\n\n<p>Your go-to resource should be the official <a href=\"https://developer.wordpress.org/themes/\">theme developer handbook</a>.</p>\n\n\n\n<p>The breadth of knowledge available there was unavailable for those starting in the early days. You can build a WordPress theme from scratch by simply following along each page in the handbook.</p>\n\n\n\n<p>While it was written in 2012, ThemeShaper has a <a href=\"https://themeshaper.com/2012/10/22/the-themeshaper-wordpress-theme-tutorial-2nd-edition/\">17-part tutorial series</a> on developing themes from start to finish. With a few exceptions, most of the information in the tutorials is accurate. The underpinning of traditional theme development has not changed much over the years. This includes basic concepts like templates, The Loop, and similar elements.</p>\n\n\n\n<p>ThemeShaper&rsquo;s <a href=\"https://themeshaper.com/category/theme-development/\">Theme Development</a> category is a resource any theme author should be subscribed to. The team continues to post up-to-date tutorials on building themes. Recently, they have focused on block-based theme development. I am sure more tutorials are forthcoming as new features related to Full Site Editing unfold.</p>\n\n\n\n<p>Of course, search engines are your friends. Run into a problem? I guarantee you are not the first with that specific problem. The solution is documented somewhere across the web.</p>\n\n\n\n<p>If you want to begin block-based theme development, you will need to install the <a href=\"https://wordpress.org/plugins/gutenberg/\">Gutenberg</a> plugin for testing. Your resources will be limited. You will need to be a pioneer, mowing a path for others to follow. It will be a rough trek, but it also offers adventures that others have not taken.</p>\n\n\n\n<p>WordPress&rsquo;s block editor handbook has a <a href=\"https://developer.wordpress.org/block-editor/tutorials/block-based-themes/\">guide on creating block-based themes</a>. It makes some assumptions about your knowledge level in terms of theme development. Carolina Nymark, one of the Themes Team representatives, has a site called <a href=\"https://fullsiteediting.com/\">Full Site Editing</a>. It includes an extensive course that is worth taking. There is also the <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments</a> repository for testing what some people are currently building.</p>\n\n\n\n<p>My strongest recommendation is to learn through trial and error while using documentation as a backup when you get stuck. Start playing around with <a href=\"https://wordpress.org/themes/twentytwenty/\">Twenty Twenty</a> or <a href=\"https://wordpress.org/themes/twentytwentyone/\">Twenty Twenty-One</a>, the two most recent default WordPress themes. Make changes. Get yourself in trouble and break things. Learn by getting yourself out of whatever hole you have dug. Every failure is part of your path toward success. Most of all, enjoy it.</p>\n\n\n\n<p>Now, I will throw this question out to our readers, many of whom are theme authors themselves.  Will you share you tips, tricks, and resources for someone who is just starting to build themes?</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Jan 2021 21:58: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: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:18:\"Matt: Iceland Film\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53458\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://ma.tt/2021/01/iceland-film/\";s: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:359:\"<p>I wanted to share with you all a short film I made with the help of Stephen Bollinger, with videos I made a few years ago on a photography trip to Iceland with <a href=\"https://om.co/\">Om</a> and <a href=\"https://twitter.com/markkawano\">Mark</a>. I hope it provides five minutes of serenity in your day.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Jan 2021 21:46: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:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WPTavern: Gutenberg’s Faster Performance Is Eroding Page Builders’ Dominance\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110192\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/gutenbergs-faster-performance-is-eroding-page-builders-dominance?utm_source=rss&utm_medium=rss&utm_campaign=gutenbergs-faster-performance-is-eroding-page-builders-dominance\";s: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:6016:\"<p>WordPress&rsquo; block editor, colloquially still widely known as Gutenberg, is making inroads into the segment of users who have heavily relied on page builders for years. For the most part, <a href=\"https://publishpress.com/blog/gutenberg/growth-pagebuilders/\">page builder plugins have either declined in growth or stagnated in 2020</a>, with the exception of Elementor. In contrast, block collections with page builder features are gaining more users. Performance is becoming an important factor in this migration.</p>\n\n\n\n<p>In a post titled &ldquo;<a rel=\"noreferrer noopener\" href=\"https://gutenbergtimes.us1.list-manage.com/track/click?u=e3062ef0fb204dbbc2135b555&id=47325f0912&e=68ffa9a210\" target=\"_blank\">Damn.&nbsp;Gutenberg&nbsp;Smokes Elementor</a>,&rdquo; Kyle Van Deusen published benchmarks from his experience building a simple landing page using Elementor and then Gutenberg. </p>\n\n\n\n<p>&ldquo;Like any Elementor user, I&rsquo;ve become increasingly anxious about the future of Elementor and just how bloated it is,&rdquo; Van Deusen said. &ldquo;I think Google PageSpeed Insights agrees.&rdquo;</p>\n\n\n\n<p>After recreating the same design with Gutenberg and <a href=\"https://generateblocks.com/\">GenerateBlocks</a>, Van Deusen saw a small difference in <a href=\"https://gtmetrix.com/\">GTMetrix</a> scores. </p>\n\n\n\n<div class=\"wp-block-image\"><img />GTMetrix scores: Elementor vs Gutenberg</div>\n\n\n\n<p>He found the most profound difference when testing with Google&rsquo;s <a rel=\"noreferrer noopener\" href=\"https://developers.google.com/speed/pagespeed/insights/\" target=\"_blank\">PageSpeed Insights</a>, where Elementor scored 46% on mobile, and 83% on desktop.</p>\n\n\n\n<p>&ldquo;Because I&rsquo;ve had such poor luck getting any kind of decent scores with Elementor sites (especially on mobile), I&rsquo;ve given up using this tool,&rdquo; Van Deusen said. &ldquo;Not because it&rsquo;s not a valuable metric (in fact, it may be the most valuable since this is how Google sees things), but because there wasn&rsquo;t much I could do about it.&rdquo;</p>\n\n\n\n<p>In contrast, the page built with Gutenberg gave him a 94% score on mobile and a 99% on desktop.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>&ldquo;In terms of performance, straight out of the box; Gutenberg absolutely smokes Elementor,&rdquo; Van Deusen said. &ldquo;However, each time I&rsquo;ve taken Gutenberg for a spin, I&rsquo;ve left frustrated. As soon as I feel like I&rsquo;m getting the hang of it, eventually the wheels come off and I&rsquo;m back to installing Elementor.</p>\n\n\n\n<p>&ldquo;But when your PageSpeed Insights scores go from 46% to 94%, it&rsquo;s time to perk up and pay attention.&rdquo;</p>\n\n\n\n<p>Van Deusen said it took him more time to recreate the design in Gutenberg and he had trouble with mobile views. At the moment, he doesn&rsquo;t see switching as an advantageous move for his business.</p>\n\n\n\n<p>&ldquo;While I think we can conclusively say, at least for performance, Gutenberg is the clear winner &mdash; it&rsquo;s just not at a point where a guy like me can jump ship,&rdquo; Van Deusen said.</p>\n\n\n\n<p>&ldquo;Gutenberg is fun to play with, and I enjoy dreaming of the day when it&rsquo;s viable for me&mdash; but I like to put food on my table. Elementor still helps me do that more efficiently.&rdquo;</p>\n\n\n\n<p>In another experiment, WordPress developer Munir Kamal <a href=\"https://gutenberghub.com/gutenberg-vs-elementor-html-bloat/\">rebuilt Elementor&rsquo;s homepage in Gutenberg</a> to compare the HTML markup both page builders generate. The page built with Elementor includes 356 div&rsquo;s in the markup vs 77 for Gutenberg. Kamal found that Elementor generated 796 lines of code vs Gutenberg&rsquo;s 206 lines, resulting in a difference of 99kb vs 28kb respectively. </p>\n\n\n\n<p>In August 2020, DearHive, the makers of the DearFlip WordPress plugin, left CodeCanyon to sell plugins from their own site. DearHive&rsquo;s company site was built with Elementor, but suddenly Google ranking mattered for their product site now that they were selling independently from CodeCanyon. Deepak Ghimire, a software developer at the company, cited performance as the chief issue that impacted their ranking and drove them to <a href=\"https://medium.com/wpunbox/our-move-from-elementor-to-gutenberg-why-we-left-elementor-b525b4caa3da\">switch to Gutenberg</a>.</p>\n\n\n\n<p>&ldquo;Our page speed went from 83 with Elementor to 98 with Gutenberg,&rdquo; Ghimire said. </p>\n\n\n\n<p>Page builder plugins may still have more features at this point in time, but performance is becoming a critical consideration for those who are doing business online. In May 2021, Google plans to&nbsp;<a href=\"https://wptavern.com/google-search-to-add-page-experience-to-ranking-signals-in-may-2021\">introduce a new ranking signal</a>&nbsp;for Search, based on page experience as measured by&nbsp;<a href=\"https://web.dev/vitals/#core-web-vitals\">Core Web Vitals</a>&nbsp;metrics. Performance is an important part of delivering the kind of scores necessary to pass the Core Web Vitals assessment. This ranking signal update from Google may compel even more site owners to migrate away from slow page builders.</p>\n\n\n\n<p>For the past two years, WordPress users have been asking if Gutenberg will replace page builders. It looks more and more likely if the most popular ones remain bloated alternatives and the smaller ones keep on the same trajectory of attrition. It won&rsquo;t happen overnight, but it is bound to accelerate when full-site editing makes its debut in WordPress core. </p>\n\n\n\n<p>For those who build websites for clients, the best way to future-proof your skills is to learn how to build pages within the framework of the block editor and, if you can, learn how to build custom blocks. It&rsquo;s also a good time to be experimenting with different block collections to streamline your setup so that you don&rsquo;t have to sacrifice high performance in order to build sites efficiently.  </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Jan 2021 04:15: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: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:18:\"Matt: Thirty-seven\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53415\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"https://ma.tt/2021/01/thirty-seven/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2689:\"<p>I turn 37 today. I look around and I feel incredibly lucky to be writing this after a topsy-turvy year. I have health. I have friends whom I love. These are all good reasons to feel optimistic about the future. A few unconnected thoughts today:</p>\n\n\n\n<p>My father had me when he was exactly 13,300 days old, and this year I passed that number of rotations of the Earth.</p>\n\n\n\n<p>It&#8217;s hard to plan when so much is changing, so resolutions this year haven&#8217;t felt the same. But in times like these it&#8217;s even more important to plan for the long-term. A look back, once a year, is enough to remind of what remains.</p>\n\n\n\n<p>I&#8217;m so thankful for the internet. It&#8217;s where I learned and practiced my trade. It&#8217;s where I connect every day with the most interesting and eclectic group of people I could imagine, a modern day Florence during the Renaissance. I hope to make a lot more internet and enable others to do the same.</p>\n\n\n\n<p>Many years ago I said &#8220;Technology is best when it brings people together.&#8221; This quote has <a href=\"https://www.google.com/search?q=technology+is+best+when+it+brings+people+together&tbm=isch\">taken on a life of its own on motivational posters and images</a>. When I first said it I think I had in mind WordCamps and meetups and other physical gatherings; this year it transformed for me seeing how technology brought together those separated by the pandemic. This year has appeared divisive, so it&#8217;s easy to overlook how many times people came together. It&#8217;s like the old saying, it&#8217;s not how many times you fall, it&#8217;s how many times you get up. Fall thirty-six times, get up thirty-seven.</p>\n\n\n\n<p>All birthday posts: <a href=\"https://ma.tt/2003/01/bday/\">19</a>, <a href=\"https://ma.tt/2004/01/so-im-20/\">20</a>, <a href=\"https://ma.tt/2005/01/hot-barely-legal-matt/\">21</a>, <a href=\"https://ma.tt/2006/01/matt-22/\">22</a>, <a href=\"https://ma.tt/2007/01/twenty-three/\">23</a>, <a href=\"https://ma.tt/2008/01/twenty-four/\">24</a>, <a href=\"https://ma.tt/2009/01/twenty-five/\">25</a>, <a href=\"https://ma.tt/2010/01/twenty-six/\">26</a>, <a href=\"https://ma.tt/2011/01/twenty-seven/\">27</a>, <a href=\"https://ma.tt/2012/01/twenty-eight/\">28</a>, <a href=\"https://ma.tt/2013/01/twenty-nine/\">29</a>, <a href=\"https://ma.tt/2014/01/matt-3-0/\">30</a>, <a href=\"https://ma.tt/2015/01/thirty-one/\">31</a>, <a href=\"https://ma.tt/2016/01/thirty-two/\">32</a>, <a href=\"https://ma.tt/2017/01/thirty-three/\">33</a>, <a href=\"https://ma.tt/2018/01/thirty-four/\">34</a>, <a href=\"https://ma.tt/2019/01/thirty-five/\">35</a>, <a href=\"https://ma.tt/2020/01/thirty-six/\">36</a>, 37.</p>\n\n\n\n<p></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 Jan 2021 03:07:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:78:\"WPTavern: EatsWP Brings Virtual Restaurant Menus to 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=110174\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:201:\"https://wptavern.com/eatswp-brings-virtual-restaurant-menus-to-the-wordpress-block-editor?utm_source=rss&utm_medium=rss&utm_campaign=eatswp-brings-virtual-restaurant-menus-to-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:5639:\"<p class=\"has-drop-cap\">Yesterday, Jack Kitterhing launched <a href=\"http://eatswp.com/\">EatsWP</a>, his new restaurant-related WordPress plugin. It is a menu creation system that works in the block editor. It also has a built-in QR code feature to work with customers&rsquo; phones.</p>\n\n\n\n<p>Kitterhing is the Product Manager at LearnDash. He is also the founder of Immerseus, a shop that builds plugins for the learning management system. He is now extending his reach with the founding of EatsWP. He contracted out the development work to a private freelancer with who he regularly works.</p>\n\n\n\n<p>&ldquo;Apart from that, it&rsquo;s just me on this project,&rdquo; said Kitterhing. &ldquo;My other business, I have five full-time employees, and so if required, one of those could be brought over for support. We, myself and my friend, took this idea to launch in under a month, which I&rsquo;m very pleased with considering that Christmas was in the middle as well.&rdquo;</p>\n\n\n\n<p>Kitterhing decided to build this plugin based on what he was seeing with small restaurant owners he knew. Some of the issues facing these single-location restaurants are with their physical menus.</p>\n\n\n\n<p>&ldquo;It&rsquo;s expensive to update them or make any changes as it requires a whole new print run,&rdquo; he said. &ldquo;By having a digital menu, they can update in minutes and generate a new QR code print. Then combine that with the current world situation, it also isn&rsquo;t very healthy to have everyone touching physical menus, so digital menus made more sense than ever.&rdquo;</p>\n\n\n\n<p><a href=\"https://eatswp.com/pricing/\">Pricing for the plugin</a> begins at $37 per year and increases based on the number of sites the user wants updates and support on.  Kitterhing also offers a custom menu design and setup tier.</p>\n\n\n\n<h2>How the Plugin Works</h2>\n\n\n\n<img />Editing an EatsWP menu item in the block editor.\n\n\n\n<p class=\"has-drop-cap\">At the moment, EatsWP is a simple affair. The plugin does not offer hundreds of options or every feature imaginable for a menu-type of plugin. It is a 1.0. However, for the features it does provide, it does them reasonably well. Kitterhing is off to a good start. He has set a foundation, and the only way to go from here is up.</p>\n\n\n\n<p>Where the plugin tends to shine is with its primary features, which are its array of blocks. Users begin by adding the Eats Menu block. From there, they have a selection of inner blocks they can place within the menu:</p>\n\n\n\n<ul><li>Item With Picture</li><li>Item With Picture and Addons</li><li>Item Without Picture</li><li>Item Without Picture and Addons</li><li>Eats Section Heading</li></ul>\n\n\n\n<p>In reality, most of the blocks are just prearranged sets of existing core WordPress blocks. They provide structure and loads of color options. Plus, end-users can click a button to add a &ldquo;New&rdquo; or &ldquo;Popular&rdquo; tag to their menu items. It is a nice touch.</p>\n\n\n\n<p>The color options offer some customizability. In the long term, users will likely want more design options. However, it may be prudent for the plugin author to follow core&rsquo;s lead here and implement such options as they become available in the block editor API.</p>\n\n\n\n<p>The one missing feature that should be available now is support for wide and full alignments. Kitterhing assured me this would land in the first quarter of this year.</p>\n\n\n\n<p>On top of the plugin&rsquo;s blocks, EatsWP allows end-users to generate a QR code for the page their restaurant&rsquo;s menu is on. When a customer scans the QR code with their phone, the page then opens.</p>\n\n\n\n<p>&ldquo;The QR code generation is more straightforward than most people expect,&rdquo; said Kitterhing. &ldquo;We&rsquo;re using a well-known QR code generation library. You then simply select the page your menu is on, generate the QR code, print it off, or show it on your website and you&rsquo;re ready to go.&rdquo;</p>\n\n\n\n<h2>The Future of EatsWP</h2>\n\n\n\n<p class=\"has-drop-cap\">On the EatsWP website, Kitterhing lightheartedly writes that &ldquo;delicious desserts&rdquo; are coming soon. This includes WooCommerce integration, recipes, and other secret features. Integrating with WooCommerce could open a new avenue for restaurant owners to explore as part of their checkout process.</p>\n\n\n\n<p>&ldquo;I&rsquo;m hoping that WooCommerce support will be coming Q1 this year,&rdquo; said Kitterhing. &ldquo;As I&rsquo;m sure you can imagine, it&rsquo;s reasonably technically challenging to incorporate this in a user-friendly way. The goal is to have all the connections and product creation actually done within the block editor interface. So someone wouldn&rsquo;t have to go off to WooCommerce to set a product and come back as that&rsquo;s rather long-winded. I&rsquo;m excited to show everyone!&rdquo;</p>\n\n\n\n<p>It will be interesting to watch how this integration unfolds in the coming months. Menus are a solid starting point, but having a payment option is necessary in a world with more people are ordering online. This is especially true in the Covid-era where contactless forms of payment are becoming the norm for takeout. Restaurants need simple solutions that they are not hacking together from multiple, non-integrated sources.</p>\n\n\n\n<p>&ldquo;The goal within the next 12 months is to turn EatsWP into everything that a restaurant needs to offer a minimal-contact experience for customers,&rdquo; said Kitterhing. &ldquo;Many restaurants don&rsquo;t have websites either, so I&rsquo;m looking into a SaaS option where I&rsquo;d host the menu/site for the restaurant.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 11 Jan 2021 21:46: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:37;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"WPTavern: WordPress Community Team Proposes Using a Decision Checklist to Restart Local 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:30:\"https://wptavern.com/?p=110022\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:233:\"https://wptavern.com/wordpress-community-team-proposes-using-a-decision-checklist-to-restart-local-events?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-community-team-proposes-using-a-decision-checklist-to-restart-local-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4502:\"<img />photo credit: <a href=\"https://stocksnap.io/photo/checklist-goals-TBJ9OPDGMK\">Glenn Carstens-Peters</a>\n\n\n\n<p>WordPress&rsquo; Community Team has been <a href=\"https://wptavern.com/wordpress-community-team-discusses-return-to-in-person-events\">discussing the return to in-person events</a> since early December 2020, and has landed on an idea that would allow local meetup organizers to determine readiness <a href=\"https://make.wordpress.org/community/2021/01/07/proposal-decision-making-checklist-for-safe-in-person-meetups/\">using a COVID-19 risk-assessment checklist</a>. This would enable organizers to restart meetups when it is safe for their communities, instead of applying a blanket global policy.</p>\n\n\n\n<p>Countries like Australia, New Zealand, The Bahamas, Iceland, and Vietnam, are a few examples of locations that are doing a decent job containing the virus. In contrast, the United States logged more than 4,000 coronavirus deaths in a single day this week, pushing the daily average to over 2,700. While the situation remains bleak for many areas of the world, vaccines are rolling out to vulnerable populations, albeit slowly and with a few snags.</p>\n\n\n\n<p>In the previous discussion that happened in early December, WordPress lead developer Dion Hulse shared some feedback from Australian organizers who have been eager to restart their meetups.</p>\n\n\n\n<p>&ldquo;One of the problems faced in Australia (and probably NZ &amp; Taiwan too) has been the blanket worldwide restrictions companies have put in place,&rdquo; Hulse said. &ldquo;Australia/NZ have been lucky, the pandemic has been successfully contained &ndash; Australia has seen less than 30k cases this year, and NZ 2k cases. To put that in context, the USA has recorded more (detected) cases in 3 hours today than Australia did all year, and more in 30 minutes than NZ.&rdquo;</p>\n\n\n\n<p>Hulse said a few Australian meetup groups were denied the go-ahead for restarting because of the global restrictions, which has &ldquo;led to the abandonment of meetups once again (as online meetups have simply not worked here, as most people can still go out in person, so there&rsquo;s been no major push from most Australians to the online platforms like elsewhere).&rdquo;</p>\n\n\n\n<p>The Community Team&rsquo;s proposal for a checklist takes these more unique situations into consideration and allows organizers to move forward in areas where public health measures have adequately curbed the spread of the virus. A few example checklist items include the following:</p>\n\n\n\n<ol><li>Is your country&rsquo;s (or state&rsquo;s) average positivity rate over the past 28 days under 4%?</li><li>In the past 28 days, has your country or area&rsquo;s&nbsp;<a href=\"https://en.wikipedia.org/wiki/Basic_reproduction_number\">basic reproduction number</a>&nbsp;stayed under 1?</li><li>In the past 14 days, have there been under 50 new cases per 100,000 people reported?</li><li>Does your local government allow for in-person events?</li><li>If there is a cap on the number of people who can meet at a time, will you as an organizer follow this guideline?</li></ol>\n\n\n\n<p>Contributor feedback so far includes recommendations for dealing with violations of the guidelines and assessing the need for contact tracing in case meetup attendees are exposed during an event. Cami Kaos recommended that the team share a list of locations that have already been vetted using the checklist and have not met requirements.</p>\n\n\n\n<p>&ldquo;My hope is that this would reduce a lot of duplicated time and effort for areas that we already know aren&rsquo;t yet, by the standards we&rsquo;re setting, safe,&rdquo; Kaos said. &ldquo;It would save time and disappointment for organizers hoping to meet in person and also contributor time and energy for those deputies who will vet the applications to hold in-person events.&rdquo;</p>\n\n\n\n<p>Since the virus is mutating and countries are adapting in different ways, the situation can change rapidly, so organizers would need to be prepared to roll back to online events if conditions for safe meetups deteriorate. WordCamps are still out of the question for the time being, but the Community Team is seeking feedback on the <a href=\"https://make.wordpress.org/community/2021/01/07/proposal-decision-making-checklist-for-safe-in-person-meetups/\">proposal</a> by January 15, 2021, including additions to the checklist and recommendations for public health resources that could aid in guiding the process.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 09 Jan 2021 16:50:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"Matt: Autonomous and Beautiful Home Devices\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53404\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"https://ma.tt/2021/01/autonomous-and-beautiful-home-devices/\";s: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:1532:\"<p>Of all the smart home upgrades I&#8217;ve made, replacing all my regular smoke detectors with Nest Protects (Google&#8217;s smoke detector) has been the one that I regret the most.</p>\n\n\n\n<p>I don&#8217;t really need a smart smoke detector. It doesn&#8217;t need to talk, connect to wifi, and cost hundreds of dollars. I don&#8217;t need it integrated with my Google account which is impossible to share, so I need to be personally involved to replace one.</p>\n\n\n\n<p>But other smoke detectors are just so unsightly, and the Nest is light years ahead of the competition from a design standpoint.</p>\n\n\n\n<img />\n\n\n\n<p>There&#8217;s such an opportunity for something that looks as good as the Nest, but doesn&#8217;t require two-factor authentication to replace. I didn&#8217;t want to call it dumb but beautiful, so let&#8217;s say &#8220;autonomous and beautiful&#8221; appliances and home devices. I still want it to be smart, but if you&#8217;re going to have the risk profile of a device that connects to the internet, it needs to be worth it, like <a href=\"https://www.brilliant.tech/\">Brilliant</a>, <a href=\"https://www.sonos.com/\">Sonos</a>, smart TVs, or connected cameras.</p>\n\n\n\n<p>I&#8217;m becoming more wary of any hardware that requires an app, just because of the natural decay of non-SaaS and non-open source software. <a href=\"https://www.vanmoof.com/en-US\">Van Moof bikes</a> are beautiful, but will they still connect well when iOS 24 is out and Bluetooth has been removed from iPhones for security reasons?</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Jan 2021 23:45: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:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:94:\"WPTavern: Blocked-Based Version of Twenty Twenty-One Nearing Readiness for the Theme Directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110087\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:233:\"https://wptavern.com/blocked-based-version-of-twenty-twenty-one-nearing-readiness-for-the-theme-directory?utm_source=rss&utm_medium=rss&utm_campaign=blocked-based-version-of-twenty-twenty-one-nearing-readiness-for-the-theme-directory\";s: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:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Twenty Twenty-One Blocks, now renamed to TT1 Blocks, is inching its way toward the WordPress theme directory. Kjell Reigstad mentioned the prospect in this week&rsquo;s <a href=\"https://make.wordpress.org/themes/2021/01/06/block-based-meeting-notes-january-6/\">block-based themes meeting</a>. Contributors to the theme, which is part of the <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments</a> project, have pushed some much-needed code updates to the repository.</p>\n\n\n\n<p><a href=\"https://github.com/WordPress/theme-experiments/tree/master/tt1-blocks\">TT1 Blocks</a> is the block-based version of the Twenty Twenty-One theme. Its goal is to provide a version of the original theme that works with Full Site Editing (FSE), currently only available through the Gutenberg plugin.</p>\n\n\n\n<p>FSE needs more testers. And, testers need themes that will enable the site editor in Gutenberg. Currently, there are only two WordPress themes, <a href=\"https://wptavern.com/q-first-fse-wordpress-theme-now-live\">Q</a> and <a href=\"https://wptavern.com/block-based-bosco-second-full-site-editing-theme-lands-in-the-wordpress-directory\">Block-Based Bosco</a>, in the directory that support the site editor. <a href=\"https://wptavern.com/armando-wordpress-theme-provides-insight-into-the-current-state-of-full-site-editing\">Armando</a> should join them shortly. If a user attempts to find one via the <a href=\"https://wordpress.org/themes/tags/full-site-editing/\">FSE filter</a>, they will get no results, as pointed out by Gary Taylor in a <a href=\"https://wptavern.com/gutenberg-9-7-improves-user-experience-updates-reusable-blocks-and-brings-page-templates-to-fse-themes#comment-359503\">recent comment</a>. This seems to be an oversight by the theme authors and should be corrected.</p>\n\n\n\n<p>With most block-based themes relegated to a few GitHub repositories, it does not bode well if no one can find themes to test the most important set of features coming to WordPress in 2021. Users should be able to easily install an FSE-ready theme today.</p>\n\n\n\n<p>&ldquo;It has been brought up that it may be easier for people to test and contribute to full site editing if Twenty Twenty-One blocks was available in the WordPress theme directory,&rdquo; wrote Themes Team representative Carolina Nymark in a <a href=\"https://github.com/WordPress/theme-experiments/issues/140\">ticket about renaming TT1 Blocks</a>.</p>\n\n\n\n<p>TT1 Blocks is something that feels more official. While third-party block-based themes are needed, the <em>officialness</em> of something from core contributors gives more users a sense of trust. Plus, it would be easy for someone with .ORG administrator privileges to stick it to the top of the theme directory&rsquo;s featured page to get more eyes on it. <em>Doing this with a third-party theme would unleash a hoard of developers who want the same treatment for their themes.</em></p>\n\n\n\n<p>The prospect of the theme coming to the directory is something the WordPress project needs.</p>\n\n\n\n<p>The volunteers who have been chipping away at this TT1 Blocks have turned a <a href=\"https://wptavern.com/twenty-twenty-one-blocks-theme-launching-as-a-separate-project\">bare-bones theme</a> into something closer to the original Twenty Twenty-One. There are still some leaps remaining to get it to where it needs to be. Much is this rests in the Gutenberg development team&rsquo;s hands. There are currently over a <a href=\"https://github.com/WordPress/theme-experiments/projects/1#column-12084948\">dozen blockers</a> identified by the Theme Experiments project that need to be resolved in the Gutenberg plugin first.</p>\n\n\n\n<img />Single post in the site editor with TT1 Blocks\n\n\n\n<p>There are multiple open tickets on the <a href=\"https://github.com/WordPress/theme-experiments/projects/1\">project board</a> for theme developers who are looking for a way to contribute. This is an opportunity to learn more about block-based themes and pay it forward.</p>\n\n\n\n<p>At the moment, I am not-so-patiently awaiting the release of TT1 Blocks to the theme directory.</p>\n\n\n\n<p>There are days when I wonder if there is a final destination, some light at the end of this never-ending tunnel that leads to block-based themes being the norm. I get overexcited about each new project. I quickly test pull requests and updates on the handful of repositories I am watching, hoping for a glimpse of something spectacular.</p>\n\n\n\n<p>Part of this excitement is because I designed and developed WordPress themes for around 15 years in some form or fashion. Today, I am no longer in the design and development game. I must live vicariously through the people who are putting untold hours into this grand experiment. I get to tell their stories, which has its own rewards.</p>\n\n\n\n<p>I also know that this sort of development is a slog. Everyone has big ideas, but the real world calls for slow, steady, and dedicated work. Often it is thankless.</p>\n\n\n\n<p>When I saw the mere mention of TT1 Blocks potentially coming to the theme directory, it added a bit of spark to an otherwise rough few days. I wanted to end this particular week with something hopeful. And, testing out the latest work those volunteers have put into TT1 Blocks has done just that.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 08 Jan 2021 23:12: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:74:\"WPTavern: JetBrains Denies Being Under Investigation for SolarWinds Attack\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=110028\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/jetbrains-denies-being-under-investigation-for-solarwinds-attack?utm_source=rss&utm_medium=rss&utm_campaign=jetbrains-denies-being-under-investigation-for-solarwinds-attack\";s: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:4847:\"<p>JetBrains, makers of Phpstorm, one of the most popular IDEs for PHP developers, has published a <a href=\"https://blog.jetbrains.com/teamcity/2021/01/statement-on-the-story-from-the-new-york-times-regarding-jetbrains-and-solarwinds/\">statement</a> denying any involvement in the SolarWinds attack, which compromised multiple US federal agencies and private companies. The company stated that it has not been the subject of an official investigation:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>JetBrains has not taken part or been involved in this attack in any way. SolarWinds is one of our customers and uses TeamCity, which is a Continuous Integration and Deployment System, used as part of building software. SolarWinds has not contacted us with any details regarding the breach and the only information we have is what has been made publicly available.</p></blockquote>\n\n\n\n<p>This statement contradicts a recent New York Times <a href=\"https://www.nytimes.com/2021/01/06/us/politics/russia-cyber-hack.html\">article</a> that claimed unspecified officials were investigating the company&rsquo;s TeamCity continuous integration software as a possible entry point for the attack: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>By compromising TeamCity, or exploiting gaps in how customers use the tool, cybersecurity experts say the Russian hackers could have inconspicuously planted back doors in an untold number of JetBrains&rsquo; clients. Because TeamCity is so widely deployed, experts said, it is imperative to determine whether its software contains a vulnerability, or if attackers exploited TeamCity customers via stolen passwords or gaps in unpatched, outdated software.</p></blockquote>\n\n\n\n<p>The New York Times did not specify which officials and &ldquo;cybersecurity experts&rdquo; were the source for this information but claimed that SolarWinds was also investigating the software internally. A <a href=\"https://web.archive.org/web/20210106195835/https://www.nytimes.com/2021/01/06/us/politics/russia-cyber-hack.html\">previous version</a> of the article referred to JetBrains as &ldquo;an obscure software company,&rdquo; which <a href=\"https://twitter.com/razvanbunea/status/1347254615616729090\">ruffled the feathers</a> of the company&rsquo;s most ardent customers. SolarWinds told both the Times and <a href=\"https://www.wsj.com/articles/solarwinds-hack-breached-justice-department-systems-11609958761\">The Wall Street Journal</a> that it has not confirmed a definitive link between JetBrains and the breach of its own software.</p>\n\n\n\n<p>A&nbsp;<a rel=\"noreferrer noopener\" href=\"https://www.dni.gov/index.php/newsroom/press-releases/press-releases-2021/item/2176-joint-statement-by-the-federal-bureau-of-investigation-fbi-the-cybersecurity-and-infrastructure-security-agency-cisa-the-office-of-the-director-of-national-intelligence-odni-and-the-national-security-agency-nsa\" target=\"_blank\">joint statement</a> from the FBI, the Cybersecurity and Infrastructure Security Agency (CISA), the Office of the Director of National Intelligence (ODNI) and the National Security Agency (NSA) released this week points to Russia as the origin of the attacks: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>This work indicates that an Advanced Persistent Threat (APT) actor, likely Russian in origin, is responsible for most or all of the recently discovered, ongoing cyber compromises of both government and non-governmental networks. At this time, we believe this was, and continues to be, an intelligence gathering effort. We are taking all necessary steps to understand the full scope of this campaign and respond accordingly.</p></blockquote>\n\n\n\n<p>Phpstorm is widely used among WordPress developers, especially since&nbsp;<a rel=\"noreferrer noopener\" href=\"https://wptavern.com/phpstorm-8-released-with-full-wordpress-support\" target=\"_blank\">version 8 added official support for WordPress</a> in 2014. JetBrains users took to Twitter with questions and concerns about claims that the company was under investigation. Today, JetBrains published another <a href=\"https://blog.jetbrains.com/blog/2021/01/07/an-update-on-solarwinds/\">update</a> that clarifies its previous statement. It states that the company&rsquo;s IDEs are standalone tools with no relation to TeamCity and that there is no evidence that any of their servers or tools have been tampered with. </p>\n\n\n\n<p>JetBrains is organizing an independent security audit of TeamCity and has promised a transparent report of any vulnerabilities found that may have led to a breach.</p>\n\n\n\n<p>&ldquo;For over 20 years, one of our pillars has been to be transparent, honest, and truthful with our customers, and nothing hurts us more than seeing unfounded allegations that damage our reputation and instill doubt on our customers,&rdquo; JetBrains CEO Maxim Shafirov said.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 07 Jan 2021 23:12: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"WPTavern: Gutenberg 9.7 Improves User Experience, Updates Reusable Blocks, and Brings Page Templates to FSE 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=110018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:269:\"https://wptavern.com/gutenberg-9-7-improves-user-experience-updates-reusable-blocks-and-brings-page-templates-to-fse-themes?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-7-improves-user-experience-updates-reusable-blocks-and-brings-page-templates-to-fse-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:7906:\"<p class=\"has-drop-cap\">Gutenberg 9.7 <a href=\"https://make.wordpress.org/core/2021/01/07/whats-new-in-gutenberg-6-january/\">landed yesterday</a> with several updates and improvements. Users should expect to see changes to the interface for block variations, transforms, and patterns. Reusable blocks are being worked on after what seemed to be a hiatus. Developers can also now add custom page templates to their block-based WordPress themes.</p>\n\n\n\n<p>This release had the fewest number of bug fixes I have seen in a while. The development team only pushed eight fixes into the update, which could signal that things were more stable than usual after the 9.6 release a couple of weeks ago.</p>\n\n\n\n<p>Most of the work in 9.7 dealt with new features and enhancements. As expected, Full Site Editing got its fair share of time. However, even this seemed dialed back a bit for this release. Many of the updates are to the post-editing interface.</p>\n\n\n\n<h2>User Experience Improvements</h2>\n\n\n\n<p class=\"has-drop-cap\">The team pushed out several updates to how features work in the editor. Some of them might seem minor but improve the overall editor experience.</p>\n\n\n\n<p>Block variations received a welcome enhancement. Variations are when one underlying block is used to create multiple variations of the same block. For example, the Embed block has YouTube, Twitter, and other variations. In past versions, the block inspector in the sidebar and block navigation would show the generic name, icon, and description. However, Gutenberg 9.7 will now show the <a href=\"https://github.com/WordPress/gutenberg/pull/27469\">details for the variation</a> in use.</p>\n\n\n\n<img />YouTube variation for the Embed block.\n\n\n\n<p>When transforming a block, <a href=\"https://github.com/WordPress/gutenberg/pull/27861\">users can see a preview</a> of what the block will look like. This is a small improvement. However, it might save a few headaches when before deciding to transform one block into another.</p>\n\n\n\n<img />Preview when transforming Quote block into a Pullquote.\n\n\n\n<p>Gutenberg 9.6 introduced a <a href=\"https://wptavern.com/gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block\">drag-and-drop feature</a> for blocks in the inserter. The team has now <a href=\"https://github.com/WordPress/gutenberg/pull/27927\">extended that feature to block patterns</a>. This is just another rung on the ladder for those looking for more drag-and-drop capabilities.</p>\n\n\n\n<h2>Reusable Blocks Updated</h2>\n\n\n\n<p class=\"has-drop-cap\">It has been a while since I tested reusable blocks. The feature has seemingly taken a backseat to other, newer features in the past year or so. It never felt much better than an initial prototype. There is still no way to easily manage them unless you know where to look. However, it appears the Gutenberg development team is <a href=\"https://github.com/WordPress/gutenberg/pull/27887\">actively developing</a> this almost-forgotten feature.</p>\n\n\n\n<p>Users can expect more in future releases. &ldquo;Based on these changes, the UI for reusable blocks is most likely going to see some iterations on the upcoming weeks,&rdquo; wrote Riad Benguella in the announcement post.</p>\n\n\n\n<p>I ran an initial test to see what the feature looked like in Gutenberg 9.7. After clicking the &ldquo;Add to reusable blocks&rdquo; button, the editor did a quick flash. Then, a notification appeared at the bottom of the screen that the reusable block had been created. Because I did not have my block options sidebar panel open at the time, I saw no way to edit the reusable block&rsquo;s title. My immediate thought was that the team took an already half-baked feature and made it exponentially worse.</p>\n\n\n\n<p>Upon further digging, I found that users can edit the reusable block&rsquo;s title in the block options sidebar. However, the team did not stop there. They added several improvements to the feature.</p>\n\n\n\n<img />Editing the reusable block name in the sidebar panel.\n\n\n\n<p>Reusable blocks are now editable within the post editor itself. Users can drag an image out of the block, for example. The inspector sidebar is available for the inner blocks. Reusable blocks now look and feel like any other part of the editor. Any edits will reflect across all instances of the reusable blocks on the site.</p>\n\n\n\n<p>The big difference is in how they are saved.</p>\n\n\n\n<img />Saving a reusable block along with the post.\n\n\n\n<p>Reusable blocks are now a part of the &ldquo;multi-entity&rdquo; save system. When clicking the editor&rsquo;s update button, users will have an option to save the entire post and/or individual reusable blocks.</p>\n\n\n\n<h2>Custom &ldquo;Page&rdquo; Templates for FSE Themes</h2>\n\n\n\n<p class=\"has-drop-cap\">Block-based <a href=\"https://github.com/WordPress/gutenberg/pull/27778\">themes now support</a> what has been traditionally known as page templates. All post types are technically supported with the feature. However, the team seems to be sticking with the &ldquo;page&rdquo; terminology after some discussion.</p>\n\n\n\n<p>It took some digging because there is no existing documentation and the original example in the ticket did not reflect the end result of the code that passed. However, I managed to suss out how the feature works. For theme authors who want to test this feature, use the following example code of adding a &ldquo;contact&rdquo; template. Place it at the root level of your theme&rsquo;s <code>experimental-theme.json</code> file. You will also need to accompany this with a <code>block-templates/contact.html</code> template in your theme.</p>\n\n\n\n<pre class=\"wp-block-code\"><code>\"pageTemplates\": {\n        \"contact\": {\n                \"title\": \"Contact\",\n                \"postTypes\": [\n                        \"page\"\n                ]\n        }\n}</code></pre>\n\n\n\n<p>This feature does not do anything particularly groundbreaking right now. It merely adds the custom template to the drop-down select on the edit post/page screen. It is the equivalent of the current page template system available to traditional themes.</p>\n\n\n\n<img />Selecting a custom page template from FSE theme.\n\n\n\n<p>While this is a nice development, traditional page templates may not make much sense in the block theming paradigm. There is no way to change the visual output of the page in the editor based on the selected template &mdash; users must still view the page on the front end to see the result of its application. The block system is about instant visual feedback. Page templates need to be rethought for the new era.</p>\n\n\n\n<p>&ldquo;In terms of UI and integration with the template mode, we can do a lot more than the old select box,&rdquo; said Benguella, who was the developer behind the pull request. &ldquo;We can show a preview for templates and offer a modal or something like that for folks to pick from&hellip;We&rsquo;d need some design thinking and explorations there. This PR just sets the technical requirements to make it work.&rdquo;</p>\n\n\n\n<p>Much, but not all, of what page templates were needed for in the past decade can now be replaced by block patterns.</p>\n\n\n\n<p>In the long term, I would rather see page templates that behaved more like predesigned block layouts. This is how block templates for custom post types work today. However, that is on the post-type level rather than the level of the individual post.</p>\n\n\n\n<p>Traditional page templates are dated. Themes rarely offer more than a few. One to remove the sidebar. One to move the sidebar to the left or right. Another to make the page content area wider.</p>\n\n\n\n<p>What is clear is that we need more exploration on what page templates of the future will look like. Are they necessary in the block system? Are there better ways of handling what traditional themes are using them for? How will they work in an interface that needs visual feedback?</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 07 Jan 2021 22:34:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:123:\"WPTavern: All in One SEO Plugin Turns on Automatic Updates without Notifying Users, Removes Functionality in Latest Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109933\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:289:\"https://wptavern.com/all-in-one-seo-plugin-turns-on-automatic-updates-without-notifying-users-removes-functionality-in-latest-release?utm_source=rss&utm_medium=rss&utm_campaign=all-in-one-seo-plugin-turns-on-automatic-updates-without-notifying-users-removes-functionality-in-latest-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:4960:\"<p>Buried in the <a href=\"https://aioseo.com/changelog/\">changelog</a> of a series of minor releases that dropped before the Christmas holiday, <a href=\"https://wordpress.org/plugins/all-in-one-seo-pack/\">All in One SEO</a> plugin users were given the surprise gift of automatic updates. After a seemingly endless run of releases (12 updates during a span of six weeks at the end of 2020), the plugin&rsquo;s developers decided to change its auto update policy so that it defaults to &ldquo;on.&rdquo; The plugin is installed on more than 2 million WordPress sites.</p>\n\n\n\n<p>Version 4.0.8, released December 21, 2020, flipped on automatic updates without notifying users of the change. Despite having auto updates turned off for the plugin, many users discovered the change when they were notified by email that their sites had been updated without permission. </p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Frustrated users took to the plugin&rsquo;s support forums to report the issue and find out how it was possible.</p>\n\n\n\n<p>&ldquo;Multiple sites have updated to 4.0.11 without my permission and while all auto updates are disabled,&rdquo; one user <a href=\"https://wordpress.org/support/topic/auto-update-29/#post-13837970\">said</a>. &ldquo;I/we do not want to hear that &lsquo;it shouldn&rsquo;t happen&rsquo; and we are looking into.</p>\n\n\n\n<p>&ldquo;Your once reliable plugin has destroyed hundreds of pages of social meta data on multiple sites, broken layout (and this after I fixed the problems and told you last week, I will be disabling all updates).&rdquo;</p>\n\n\n\n<p>Others commented on the issue, citing problems with a previous major release as the source of many bugs that followed.</p>\n\n\n\n<p>&ldquo;The rollout of version 4, and auto-updating without any chance to backup first was a blunder by AIOSEO,&rdquo; plugin user Derek Haines <a href=\"https://wordpress.org/support/topic/sudden-rush-of-5-star-reviews/\">said</a>. &ldquo;It has cost me hours, days, and now weeks to fix the problems caused.&rdquo;</p>\n\n\n\n<p>The All in One SEO plugin team <a href=\"https://wordpress.org/support/topic/auto-update-29/#post-13840599\">apologized</a> for the inconvenience users experienced but said they could not reproduce it on their end. The plugin&rsquo;s settings page has a toggle for auto updates but it is just a wrapper for WordPress&rsquo; auto updater.</p>\n\n\n\n<p>&ldquo;I just wanted to give you an update and let you know that we&rsquo;ve decided to remove our own auto-update functionality all together since this issue seems to be happening on a limited amount of websites and we aren&rsquo;t able to reproduce it on our end,&rdquo; Arnaud Broes said.</p>\n\n\n\n<p>The problem was also <a href=\"https://www.facebook.com/groups/advancedwp/permalink/3806581632737356\">discussed</a> in the Advanced WordPress Facebook group.</p>\n\n\n\n<p>&ldquo;All In One SEO Pack apparently turned auto updates on, and in a few cases I found sites where those updates failed,&rdquo; Eric Karkovack reported. &ldquo;I had no idea they were turned on and in one case a site was inaccessible.&rdquo;</p>\n\n\n\n<p>Karkovack noted that there was only a small mention in the changelog, despite the plugin liberally using the dashboard notification UI for sales.</p>\n\n\n\n<p>William Earnhardt, WordPress core contributor and developer at Bluehost, offered some insight as someone who has worked on core as well as plugins installed on a massive scale.</p>\n\n\n\n<p>&ldquo;In my experience if you are weighing the two options, auto-updates prevent significantly more issues and support requests than they create,&rdquo; Earnhardt said. &ldquo;So I&rsquo;m strongly in the camp of enabling them by default, with a mechanism for preventing or disabling for those who prefer (core makes this possible with filters and now with per-plugin UI). </p>\n\n\n\n<p>&ldquo;I think when making these decisions, we as developers have to consider what is best for the broadest number of users and be realistic about the type of users we have. If a user is already not updating plugins regularly, it is unlikely they are going to have the awareness to flip a toggle to turn auto-updates on. So opt-in makes them mostly useless.&rdquo;</p>\n\n\n\n<p>Earnhardt agreed that notifying users of the change would have been a good idea, but admin notices are already &ldquo;frequently abused and quite noisy.&rdquo;</p>\n\n\n\n<p>&ldquo;It would likely be missed if not persistent, but really should only show after the update and then go away,&rdquo; he said. &ldquo;Is that enough when combined with a note in the changelog? Probably for most, but I&rsquo;m sure some would disagree.&rdquo;</p>\n\n\n\n<p>As promised nine days ago, All in One SEO&rsquo;s developers have now removed the functionality from the plugin in its first update of 2021, version 4.0.12 released today. It is noted in the changelog: &ldquo;Fixed: Completely remove auto updates wrapper to let WordPress handle updates.&rdquo; </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 06 Jan 2021 23:47: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: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: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:84:\"WPTavern: Liquid Web Acquires The Events Calendar WordPress Plugin From Modern Tribe\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109909\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:213:\"https://wptavern.com/liquid-web-acquires-the-events-calendar-wordpress-plugin-from-modern-tribe?utm_source=rss&utm_medium=rss&utm_campaign=liquid-web-acquires-the-events-calendar-wordpress-plugin-from-modern-tribe\";s: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:4092:\"<p class=\"has-drop-cap\">Liquid Web <a href=\"https://ithemes.com/the-events-calendar-plugin-joining-liquid-web-family/\">announced today</a> via the iThemes blog that it acquired The Events Calendar from Modern Tribe. The acquisition gives them ownership of the plugin, its suite of event-related plugins, and the team behind it all.</p>\n\n\n\n<p>&ldquo;We&rsquo;ve acquired all the associated plugins, including Event Tickets, etc.,&rdquo; said Matt Danner, the COO at iThemes. &ldquo;They identify under the single umbrella of The Events Calendar as a team, so we&rsquo;ve continued to position the team that way.&rdquo;</p>\n\n\n\n<p>As part of the acquisition, the 50+ employees from The Events Calendar plugin team are now a part of the Liquid Web family. They will continue working on the plugin and its related products. Zach Tirrell <a href=\"https://theeventscalendar.com/blog/news/the-events-calendar-joins-the-liquid-web-family/\">announced on The Events Calendar blog</a> that he would remain at the helm and that the team structure was not changing.</p>\n\n\n\n<p>The remaining 74 employees of Modern Tribe will continue working on the agency&rsquo;s other projects, including clients like Microsoft and Harvard University. Reid Peifer, the Creative Director at Modern Tribe, teased potential future projects in his <a href=\"https://tri.be/blog/the-events-calendar-joins-the-liquid-web-family/\">announcement post</a>. &ldquo;We can&rsquo;t help but make things, so you may see a few surprises from us in the coming months as well.&rdquo;</p>\n\n\n\n<p><a href=\"https://wordpress.org/plugins/the-events-calendar/\">The Events Calendar plugin</a> on WordPress.org currently has over 800,000 active installs with an average rating of 4.4 out of 5 stars. Modern Tribe launched the plugin in 2011 and has continued to build a larger product line and customer base around it over the last decade.</p>\n\n\n\n<p>For existing customers, it should be business as usual. Nothing has changed about who is currently developing The Events Calendar. The website is still a separate entity, and billing will remain the same.</p>\n\n\n\n<p>The acquisition is mere months after iThemes, owned by Liquid Web, <a href=\"https://wptavern.com/ithemes-enters-the-wordpress-membership-plugin-market-acquires-restrict-content-pro\">purchased Restrict Content Pro</a> (RCP), a membership plugin. While RCP continues to have an independent site, users can snag it with one of the plugin bundles directly from the iThemes website.</p>\n\n\n\n<p>However, The Events Calendar will be wholly independent of iThemes. Customers hoping to see a similar bundle with The Events Calendar will be out of luck.</p>\n\n\n\n<p>&ldquo;The RCP acquisition was done under the iThemes brand,&rdquo; said Danner. &ldquo;We brought that team into our team, and the membership product is a key part of how we&rsquo;re positioning iThemes. The Event Calendar&rsquo;s acquisition was done under the larger Liquid Web brand. Their team is coming into Liquid Web alongside iThemes as part of the bigger software division. While we definitely think there are future opportunities to collaborate between our teams (which could include bundles of products from both teams), their products are not going to become part of the iThemes product line.&rdquo;</p>\n\n\n\n<p>One of the biggest remaining questions is whether the separate teams will eventually create integrations between The Events Calendar and RCP. There are multiple reasons event organizers might want to restrict content based on memberships, especially when it comes to virtual events. Danner did not give up any specific plans in his response.</p>\n\n\n\n<p>&ldquo;We&rsquo;re very excited to explore all the opportunities to integrate our products,&rdquo; he said. &ldquo;I think there are some great opportunities for RCP and TEC to work more closely together, and both customer bases have requested deeper integration between the two. This acquisition was a perfect fit from so many angles. The people, the values of the team, and the products all align with what we&rsquo;re building at Liquid Web.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 06 Jan 2021 22:21: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: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:71:\"Akismet: Version 4.1.8 of the Akismet WordPress Plugin is Now Available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"http://blog.akismet.com/?p=2109\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://blog.akismet.com/2021/01/06/version-4-1-8-of-the-akismet-wordpress-plugin-is-now-available/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:667:\"<p>Version 4.1.8 of <a href=\"http://wordpress.org/plugins/akismet/\">the Akismet plugin for WordPress</a> is now available. It contains the following changes:</p>\n<ul>\n<li>Removal of a deprecated jQuery function.</li>\n<li>A fix for a bug causing some data to be excluded from API calls when marking a comment as spam or not-spam.&nbsp; This should improve spam detection accuracy.</li>\n</ul>\n<p>To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in <a href=\"http://wordpress.org/plugins/akismet/\">the WordPress plugins directory</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 06 Jan 2021 17:01: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:17:\"Christopher Finke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:33:\"Matt: Farnam Street and Postlight\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53384\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"https://ma.tt/2021/01/farnam-street-and-postlight/\";s: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:2137:\"<p>I recorded two interviews very far apart from each other, but which have surprisingly both come out today. The first is for one of my favorite sites on the web, <a href=\"https://fs.blog/\">Farnam Street</a>. I was honored to be <a href=\"https://fs.blog/knowledge-project/\">episode 100 on their Knowledge Project podcast</a>. Knowledge Project is probably one of the podcasts I&#8217;ve listened to the most since it started. Please check out their other guests as well, they really do have the most interesting conversations with the most interesting folks.</p>\n\n\n\n<p>Shane and I cover turnarounds, how environment affects performance, pros and cons of distributed work, uncovering your lacuna, mental models, and patterns of decision making.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>On a completely different vein, I did a deep geek-out on technology and content management systems with <a href=\"https://ginatrapani.org/\">Gina Trapani</a> and <a href=\"https://www.ftrain.com/\">Paul Ford</a>, two of my favorite technologists, <a href=\"https://postlight.com/podcast/wordpress-and-beyond-with-matthew-mullenweg\">on the Postlight podcast</a>. We covered a lot of tech history, my thoughts on Chromium and Mozilla&#8217;s Gecko engine, structured data, Gutenberg, and a lot more. If you&#8217;re a developer or a long-time WordPress community member you&#8217;ll enjoy this one, but it might be esoteric or technical if you&#8217;re not immersed in this world. Here&#8217;s a Spotify embed of the episode:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>In both we do touch on my idea that, on a long enough timeline, the survival rate for all proprietary software drops to zero. (Hat tip to Fight Club.) Proprietary software is an evolutionary dead end. You can think of open source packages like <a href=\"https://en.wikipedia.org/wiki/Gene-centered_view_of_evolution\">genetic alleles that have a higher fitness function</a>, and eventually become the fittest organism. The longer I spend watching mega-trends in technology, the more I see that pattern everywhere, from encyclopedias to cryptocurrencies.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 23:51: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:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"WPTavern: Block System Will Create More Commercial Opportunities for WordPress Theme Authors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109904\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:229:\"https://wptavern.com/block-system-will-create-more-commercial-opportunities-for-wordpress-theme-authors?utm_source=rss&utm_medium=rss&utm_campaign=block-system-will-create-more-commercial-opportunities-for-wordpress-theme-authors\";s: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:6978:\"<p class=\"has-drop-cap\">Ten years ago, a potential WordPress theme buyer might stumble upon a site like ThemeForest. The themes on the site would primarily tout the hundreds of shortcodes they included. These shortcodes would allow the user to build anything they wanted with simple BBCode-like brackets around some tag or another.</p>\n\n\n\n<p>The practice was not limited to ThemeForest. Nearly every theme development company at the time &mdash; and they were sprouting up by the dozens a decade ago &mdash; needed to compete in the same arena. Despite all their faults (never mind that no user could reasonably remember hundreds of them), shortcodes topped the list of features.</p>\n\n\n\n<p>Today, the landscape is much different. In part powered by page builders like Elementor and Beaver Builder, themes are more apt to offer pre-built design options. Gone are the days when users must painstakingly fill their pages with shortcode soup manually. At the click of a button, their theme will automate the design of their homepage for them. The user merely needs to fill in the content. At the click of another button, the user gets a contact or services page. A restaurant owner might get a fully-laid out food menu. A new online shop owner can get a full set of pre-built WooCommerce products by importing their theme&rsquo;s demo content.</p>\n\n\n\n<p><em>Customizability</em> is the name of the game. This has not really changed over the years, but the methods for getting there have.</p>\n\n\n\n<p>When perusing commercial theme shops today, the common thread is the multitude of demos. These demos showcase the various layouts the user can have if they just fork over the $50 or $60 for access. There are themes with over 500 demos.</p>\n\n\n\n<p>Some themes market hundreds of templates or dozens of pre-built, one-click website designs. At the end of the day, it is all about making the user&rsquo;s site look a certain way without the hassle of hours of work.</p>\n\n\n\n<p>The problem with traditional theming is that all of these themes are built with non-standard solutions. This is no fault of the theme authors. They had to build or use third-party systems where WordPress had failed. Elementor has standardized this to some degree &mdash; many commercial theme shops fully support it, often as the default experience. However, it still only represents a fraction of the market and is not a part of the core platform.</p>\n\n\n\n<p>WordPress is still catching up to the dream that the premium marketplace has already been capitalizing on.</p>\n\n\n\n<p>However, WordPress can do this better in the long term and level the playing field for many other theme developers. We are on the verge of true one-click solutions from the core platform. It will be a tough run for the next year, but the theme shops that adopt the block system the soonest stand the most to gain.</p>\n\n\n\n<h2>What the System Offers</h2>\n\n\n\n<p class=\"has-drop-cap\">If you have ever installed themes that offered dozens of header designs, the experience has likely been hit or miss. Most such themes require users to go through dozens of options fields in the customizer or &mdash; <em>yikes!</em> &mdash; a custom-built options page that looks nothing like the WordPress interface. While there are simpler solutions that some theme authors have created, WordPress has never had a built-in way of allowing users to do this.</p>\n\n\n\n<p>Enter template parts made out of blocks.</p>\n\n\n\n<p>Themes Team rep Carolina Nymark showcased just how simple this is with the upcoming site editor. Her <a href=\"https://wptavern.com/armando-wordpress-theme-provides-insight-into-the-current-state-of-full-site-editing\">Armando theme</a> offers three custom header templates.</p>\n\n\n\n<img />Selecting a header template with the Armando theme.\n\n\n\n<p>The system is far from ready. There are missing features that we will likely not see for a while. For example, there&rsquo;s currently no way to categorize or otherwise group all the header templates just yet. Users can just as easily replace the header with a footer template.</p>\n\n\n\n<p>However, this is an important step forward.  The theme author did not write any complicated PHP or JavaScript. There was no need to build a custom options panel or fields. No third-party system was warranted. The developer created the templates, and they became instantly available through the site-editing interface. The theme author&rsquo;s responsibility went back to simply designing. The user has access through a standardized interface.</p>\n\n\n\n<p>If theme authors want to offer hundreds of switchable templates, they can. If they want to add two or three while upselling the others, they can do that too.</p>\n\n\n\n<p>Now, expand upon this idea with other types of templates. These can be a footer, sidebar, homepage, or any template. The commercial applications are endless. Theme authors can offer commercial themes or upsells with far less work than ever before.</p>\n\n\n\n<p>The possibilities do not end with templates. Block patterns are another viable feature to commercialize. As shown with the Genesis Blocks plugin, its &ldquo;layout selector&rdquo; offers various patterns to quickly insert into the post content.</p>\n\n\n\n<img />Slate collection from the Genesis Blocks plugin.\n\n\n\n<p>Genesis Blocks even offers collections of these patterns that share a similar design aesthetic. In other words, these are essentially pattern categories.</p>\n\n\n\n<p>This is an easy path forward for theme authors who are looking to upsell. Build one or two categories of patterns. Periodically bring in new groups of patterns for users who want a fresh look without changing themes.</p>\n\n\n\n<p>Gutenberg Hub already provides hundreds of <a href=\"https://wptavern.com/gutenberg-hub-launches-collection-of-100-block-templates\">templates and patterns</a>, filling a void that is currently missing from the theme ecosystem. The site offers convenient solutions, but something is missing: they are not tied into the theme&rsquo;s design. Forward-thinking theme authors should already be building competing solutions that offer all the same templates and patterns that match their themes.</p>\n\n\n\n<img />Gutenberg Hub&rsquo;s landing page &ldquo;templates&rdquo; (patterns).\n\n\n\n<p>A year or two ago, there was some rumbling about the block editor leading to the death of WordPress theming. <em>Traditional</em> theming will trickle into nonexistence in the coming years. Of course, there will be pockets of holdouts, but the future is about one-click solutions. And, WordPress is setting the stage for all users to have this ability at their fingertips. The theme shops that recognize this the soonest will profit from it the most. Everyone else will be fighting for the scraps they leave behind.</p>\n\n\n\n<p>It is not time to abandon traditional theming or forgo page-builder support. However, it is time for themers to begin rolling out block patterns and to start outlining, testing, and building block-based themes.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 22:34:08 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:57:\"WordPress.org blog: The Month in WordPress: December 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9508\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/2021/01/the-month-in-wordpress-december-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11600:\"<p>We bid goodbye to 2020 in style with the release of WordPress 5.6 and the launch of Learn WordPress. But these weren’t the only exciting updates from WordPress in December. Read on to learn more!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.6 is here</h2>\n\n\n\n<p>The latest major WordPress release,<a href=\"https://wordpress.org/news/2020/12/simone/\"> version 5.6</a> “Simone”, came out on December 8. The release ships with a new default theme called <a href=\"https://wordpress.org/themes/twentytwentyone/\">Twenty Twenty One</a>. It offers a host of features, including:</p>\n\n\n\n<ul><li>Greater layout flexibility</li><li>More block patterns</li><li>Video captioning support</li><li>Auto-updates</li><li>Beta-compatibility for PHP 8.0</li><li>Application password support for the REST API</li><li>Updates to jQuery</li></ul>\n\n\n\n<p>In addition, WordPress 5.6 is now available in 55 languages. You can find more information about the release in the <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">field guide</a>, and you can update to the latest version directly from your WordPress dashboard or by <a href=\"https://wordpress.org/download/\">downloading</a> it directly from WordPress.org. A total of 605 people hailing from 57 different countries contributed to the development of WordPress 5.6. <a href=\"https://profiles.wordpress.org/audrasjb/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>audrasjb</a> has <a href=\"https://jeanbaptisteaudras.com/en/2020/12/wordpress-5-6-core-stats-contributions-by-country-company/\">compiled many more stats like that</a>, showing what a tremendous group effort this was—they’re well worth a read!</p>\n\n\n\n<p>Want to contribute to upcoming WordPress releases? Join the WordPress <a href=\"https://wordpress.slack.com/archives/C02RQBWTW\">#core</a> channel on the <a href=\"https://make.wordpress.org/chat/\">Make WordPress Slack</a> and follow the <a href=\"https://make.wordpress.org/core/\">Core team blog</a> to learn the <a href=\"https://make.wordpress.org/core/2020/12/21/wordpress-5-7-planning-roundup/\">latest on WordPress 5.7</a>, which is <a href=\"https://wordpress.org/about/roadmap/\">slated to be out by March 9, 2021</a>. The Core team hosts weekly chats on Wednesdays at <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=5&min=00&sec=0\">5 a.m.</a> and <a href=\"https://www.timeanddate.com/worldclock/fixedtime.html?hour=20&min=00&sec=0\">8 p.m.</a> UTC.</p>\n\n\n\n<h2>Watch the State of the Word 2020 recording</h2>\n\n\n\n<p><a href=\"https://wordpress.org/news/\">State of the Word 2020</a>, the annual keynote address delivered by WordPress co-founder Matt Mullenweg, was streamed online for the first time on December 17. It was followed by a live Q&amp;A from community members all across the world. You can find the stream recording on <a href=\"https://www.youtube.com/watch?v=QI3qCoiuG3w\">YouTube</a>, <a href=\"https://www.facebook.com/WordPress/videos/1281447442248369\">Facebook</a>, and <a href=\"https://twitter.com/i/broadcasts/1dRKZNvnrmdKB\">Twitter</a>. The <a href=\"https://wordpress.tv/2020/12/17/matt-mullenweg-2020-state-of-the-word/\">State of the Word</a> video and the <a href=\"https://wordpress.tv/2020/12/17/matt-mullenweg-2020-state-of-the-word-qa/\">Q&amp;A session</a> are also available on WordPress.tv.&nbsp;</p>\n\n\n\n<h2>Learn WordPress has launched</h2>\n\n\n\n<p>Learn WordPress, a new free, on-demand WordPress learning resource, launched officially on December 15. It offers <a href=\"https://learn.wordpress.org/workshops/\">workshops</a>, <a href=\"https://learn.wordpress.org/lesson-plans/\">lesson plans</a>, quizzes, and <a href=\"https://learn.wordpress.org/courses/\">courses</a> for anyone interested in publishing with, building for, or contributing to WordPress. WordPress enthusiasts can also <a href=\"https://www.meetup.com/learn-wordpress-discussions/\">participate in discussion groups</a> focused on specific topics to learn with and from each other.</p>\n\n\n\n<p>Want to participate in Learn WordPress? <a href=\"https://learn.wordpress.org/contribute/\">Here are four ways you can do so</a>! Additionally, contributors have <a href=\"https://make.wordpress.org/training/2020/12/03/learn-wordpress-blue-sky-thinking/\">launched a discussion</a> on the future of <a href=\"https://learn.wordpress.org/\">Learn WordPress</a>—feel free to share your thoughts in the comments. To help promote Learn WordPress, check out the <a href=\"https://make.wordpress.org/marketing/\">Marketing Team</a>’s <a href=\"https://make.wordpress.org/marketing/2020/12/09/help-us-promote-learn-wordpress/\">materials</a>, which detail a <a href=\"https://make.wordpress.org/marketing/2020/12/09/help-us-promote-learn-wordpress/\">range of fun and creative ways</a> to share this new resource.</p>\n\n\n\n<h2>Give feedback on the Full Site Editing project</h2>\n\n\n\n<p>Contributor teams have kicked off the <a href=\"https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/\">Full Site Editing (FSE) outreach program</a> for anyone who is building or maintaining a WordPress site so that they can give feedback on the upcoming <a href=\"https://make.wordpress.org/design/handbook/focuses/full-site-editing/\">FSE feature</a> that will be part of Gutenberg Phase 2. Your feedback will go a long way in improving FSE user flows. To participate, <a href=\"https://make.wordpress.org/test/2020/12/23/fse-program-testing-call-1-template-editing/\">check out the initial testing call</a> on the <a href=\"https://make.wordpress.org/test/\">Make/Test blog</a> and join the <a href=\"https://make.wordpress.org/core/tag/fse-outreach-experiment/\">#fse-outreach-experiment</a> Slack channel.<br /><br />Want to follow updates on the FSE project? Check out <a href=\"https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/\">this blog post</a>. You can find <a href=\"https://make.wordpress.org/core/2020/12/10/status-check-site-editing-and-customization/\">2020 updates to the FSE project</a> in the Make/Core blog.</p>\n\n\n\n<h2>BuddyPress 7.0 “Filippi” and 7.10 are now available</h2>\n\n\n\n<p><a href=\"https://buddypress.org/2020/12/buddypress-7-0-0-filippi/\">BuddyPress version 7.0</a> went live on December 9. Its features include:&nbsp;</p>\n\n\n\n<ul><li>New administration screens to manage Member and Group Types</li><li>New BP blocks for posts and pages</li><li>A default profile image for network sites</li><li>Improved BuddyPress Noveau support for the Twenty Twenty One theme.&nbsp;</li></ul>\n\n\n\n<p>A BuddyPress maintenance release (<a href=\"https://buddypress.org/2020/12/buddypress-7-1-0-maintenance-release/\">version 7.1</a>) launched on December 21.&nbsp;</p>\n\n\n\n<p>Want to provide feedback or suggestions for BuddyPress? Share your comments on the announcement posts for <a href=\"https://buddypress.org/2020/12/buddypress-7-0-0-filippi/\">7.0</a> or <a href=\"https://buddypress.org/2020/12/buddypress-7-1-0-maintenance-release/\">7.1</a>. If you find a bug, please report it in the <a href=\"https://buddypress.org/support/\">support forums</a>.&nbsp;</p>\n\n\n\n<h2>Gutenberg 9.5 and 9.6 released</h2>\n\n\n\n<p>The Core team launched <a href=\"https://make.wordpress.org/core/2020/12/02/whats-new-in-gutenberg-2-december/\">version 9.5</a> and <a href=\"https://make.wordpress.org/core/2020/12/23/whats-new-in-gutenberg-23-december/\">9.6</a> of Gutenberg last month. Both versions include several improvements to FSE flows, bug fixes, and feature upgrades. Version 9.5 introduces features like full height alignment and support for font sizes in the code block. Version 9.6 includes features like the ability to drag blocks from the inserter and a vertical layout for buttons.&nbsp;</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the <a href=\"https://wordpress.slack.com/archives/C02QB2JS7\">#core-editor</a> channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading</h2>\n\n\n\n<ul><li>The Community team <a href=\"https://make.wordpress.org/community/2020/12/01/discussion-how-can-the-wordpress-community-return-to-hosting-safe-in-person-events/\">kicked off a discussion</a> about what the WordPress Community can do to host safe, in-person events again, in light of the continuing pandemic. </li><li>The Polyglots team published its <a href=\"https://make.wordpress.org/polyglots/2020/12/30/polyglots-team-end-of-year-post-2020/\">end-of-year post</a>, along with the <a href=\"https://make.wordpress.org/polyglots/author/evarlese/\">results of its 2020 translator survey</a>.</li><li><a href=\"https://sevilla.wordcamp.org/2020/\">WordCamp Sevilla 2020</a> was held online from December 26-29. You can catch the recorded livestream playback on <a href=\"https://www.youtube.com/c/wordpresssevilla/live\">YouTube</a>. Videos of the event will <a href=\"https://wordpress.tv/event/wordcamp-sevilla-2020/\">soon be available on WordPress.tv</a>.</li><li>WordPress project executive director <a href=\"https://profiles.wordpress.org/chanthaboune/\">Josepha Haden</a> and project co-founder <a href=\"https://profiles.wordpress.org/matt/\">Matt Mullenweg</a> will be jointly hosting <a href=\"https://make.wordpress.org/core/2020/12/15/regular-office-and-listening-hours/\">quarterly office and listening hours</a> in 2021. Sign-ups for the <a href=\"https://make.wordpress.org/core/2020/12/15/regular-office-and-listening-hours/\">first ones in January 2021</a> are almost filled up.</li><li>The Core team <a href=\"https://make.wordpress.org/core/2020/12/02/wp-notify-project-review/\">published updates</a> on the <a href=\"https://make.wordpress.org/core/tag/feature-notifications/\">WP Notify project</a>, which seeks to <a href=\"https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/\">improve the notifications system</a> in WordPress Core.</li><li>The Support team <a href=\"https://make.wordpress.org/support/2020/12/handling-potential-jquery-issues-in-wordpress-5-6/\">published a post</a> detailing jQuery issues in WordPress 5.6.</li><li><a href=\"https://india.wordcamp.org/2021/\">WordCamp India Online 2021</a> will be held over three weekends between January 30 and February 14. There will be workshops, a contributor event, and sessions (in that order). The calls for <a href=\"https://india.wordcamp.org/2021/call-for-sponsors/\">sponsors</a>, <a href=\"https://india.wordcamp.org/2021/call-for-workshops/\">workshop presenters</a>, <a href=\"https://india.wordcamp.org/2021/call-for-contributor-team-leads/\">contributor team leads</a>, and <a href=\"https://india.wordcamp.org/2021/call-for-volunteers/\">volunteers</a> are now open. Don’t forget to grab your <a href=\"https://india.wordcamp.org/2021/tickets/\">free tickets</a>!</li><li>The Documentation team <a href=\"https://make.wordpress.org/docs/2020/12/01/external-linking-policy-1st-review-of-plugin-developer-handbook/\">shared a first review</a> of its <a href=\"https://make.wordpress.org/docs/tag/external-linking-policy/\">external linking policy</a>. It is using the <a href=\"https://developer.wordpress.org/plugins/\">plugin developer handbook</a> as a test.</li></ul>\n\n\n\n<p><br /><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it using this form</em></a><em>.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 10:55:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:\"\";}}}}}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:93:\"WPTavern: WordPress.com Rattles Freelancer Community with New Website Building Service Launch\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109818\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:231:\"https://wptavern.com/wordpress-com-rattles-freelancer-community-with-new-website-building-service-launch?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-com-rattles-freelancer-community-with-new-website-building-service-launch\";s: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:7137:\"<p>WordPress.com launched a new <a href=\"https://wordpress.com/built-by-wordpress-com/?utm_source=enblog&utm_medium=automattic_referred&utm_campaign=january_2021_launch&flags=a8c-analytics.on,ad-tracking,google-analytics&ga_optimize=on\">website building service</a> today with prices starting at $4,900. Automattic has been beta testing the service since the last quarter of 2020. The product <a href=\"https://wordpress.com/blog/2021/01/04/let-our-experts-build-your-dream-website/\">announcement</a> invites customers to let WordPress.com&rsquo;s&nbsp;professional team &ldquo;translate your vision into a compelling and modern website&rdquo; but does not specify pricing for more customized websites:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Whether you need a fast and performant eCommerce store for your products and/or services, a polished website for your professional services firm, or an educational website for your online courses, our experts can build it for you on WordPress.com, the most powerful platform for businesses and enterprises large and small.</p></blockquote>\n\n\n\n<p>Initial reactions from the WordPress developer and freelance community were mixed. Some see the competition as good and others perceived it as a threat to WordPress consultants and small agencies, because a product from WordPress.com carries the full weight of the official WordPress brand. </p>\n\n\n\n<p>&ldquo;Whether this succeeds or not there are a lot of folks with a sick stomach today because of it,&rdquo; WordPress developer Chris Wiegman <a href=\"https://twitter.com/ChrisWiegman/status/1346151976296443904\">said</a>.</p>\n\n\n\n<p>Automattic stepping into the $5k website market came as a surprise to many, after years of keeping to the enterprise space with its <a href=\"https://wpvip.com/\">WordPress.com VIP</a> service. (Sometime in 2019 the service started going by &ldquo;WordPress VIP&rdquo; without the &ldquo;.com&rdquo; appended to it.) Freelancers haven&rsquo;t had to worry too much about competing against a large company like Automattic when trying to attract clients. It&rsquo;s also an interesting move because the company <a href=\"https://wptavern.com/automattic-has-discontinued-active-development-on-edit-flow-plugin\">seemed stretched thin</a> when it came to maintaining plugins used by VIP clients in 2019, despite seeing &ldquo;demand for WordPress in the enterprise market like never before,&rdquo; <a href=\"https://wptavern.com/automattic-has-discontinued-active-development-on-edit-flow-plugin#comment-307821\">according to Nick Gernert</a>, head of VIP. </p>\n\n\n\n<p>&ldquo;Can&rsquo;t say I&rsquo;m surprised by this announcement, but it doesn&rsquo;t bode well for the community, to be honest,&rdquo; WordPress consultant Joshua Nelson <a href=\"https://twitter.com/onemorejosh/status/1346147871465353216\">said</a>. &ldquo;Freelancers will be hurt the most. A for instance: My custom built sites start at $3k. Once you factor in a designer that $4.9k rate looks very competitive.&rdquo;</p>\n\n\n\n<p>In response to community concerns on Twitter, Automattic CEO Matt Mullenweg said the product is targeted at people who have a difficult time getting started with WordPress.</p>\n\n\n\n<p>&ldquo;I would be extremely surprised if this impacts anyone&rsquo;s consulting business, if you do have a current or potential client leave for it please let me know &mdash; it should be all new-to-WP users who wouldn&rsquo;t have been successful getting started,&rdquo; Mullenweg <a href=\"https://twitter.com/photomatt/status/1346212091200491520\">said</a>. He also confirmed that the new service was set up for &ldquo;referring business out&rdquo; and referenced a previous experiment in 2018 where WordPress.com <a href=\"https://wordpress.com/support/upwork/\">partnered with Upwork</a> to refer clients for custom development.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\nhttps://twitter.com/photomatt/status/1346212543732170752\n</div>\n\n\n\n<p>The product launch lacked this information and some <a href=\"https://twitter.com/mattmedeiros/status/1346221279246999552\">noted</a> the copy was confusing with phrases like &ldquo;Built by us&rdquo; and &ldquo;Our experts can build it for you.&rdquo;</p>\n\n\n\n<p>WordPress professionals took to <a href=\"https://poststatus.com/\">Post Status</a>&lsquo; Slack to discuss the implications of Automattic&rsquo;s new offering. Mullenweg responded to them, saying he is &ldquo;100% certain this will drive more up-market consulting in the future&rdquo; to consultants who handle larger projects and potentially bring more business to plugin and theme developers. He also noted that <a href=\"https://www.web.com/websites/website-design-services\">Bluehost&rsquo;s full service</a> product is a similar solution and that services like <a href=\"http://web.com/\">Web.com</a> have been competing in this space for awhile.</p>\n\n\n\n<p>&ldquo;Typically these are called DIFM (do it for me) vs DIY (do it yourself),&rdquo; he said.</p>\n\n\n\n<p>Automattic must be witnessing a strong demand for DIFM, as participants in the discussion at Post Status referenced Mullenweg&rsquo;s comments on the topic during his most recent <a href=\"https://wptavern.com/state-of-the-word-2020-wordpress-moves-toward-full-site-editing\">State of the Word</a> address delivered in December 2020:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Lots of people lost their jobs. Lots of people were looking to supplement their income. This drove an incredible amount of entrepreneurship, so people who were looking for people who knew WordPress. And on the other side of that, normal folks who knew or learned WordPress found that they had a lot to demand for their work, so they were able to supplement or replace their income, essentially for folks who have a do it for me mentality, so someone who is looking for someone else to build a website. It&rsquo;s never been a better time to learn and invest in improving your WordPress skills.</p></blockquote>\n\n\n\n<p>The idea behind this product is to help those who get stuck with WordPress  before they turn to competitors that market website creation to beginners. It indicates that WordPress still has a long road ahead before it is truly an approachable tool for beginners embarking on their first site building experience.</p>\n\n\n\n<p>Automattic has not published a pricing structure for the features included in a basic $4900 website. Based on images on the <a href=\"https://wordpress.com/built-by-wordpress-com/\">landing page</a>, the sites do not seem extensively customized beyond what existing themes offer. It seems like more of a website setup service and does not explicitly promise custom development.</p>\n\n\n\n<p>When asked how agencies can apply to be put into the pipeline for referrals from WordPress.com&rsquo;s new service, Mullenweg indicated that the product is still in the experimental stage.</p>\n\n\n\n<p>&ldquo;It&rsquo;s unclear if anyone wants this yet, so for this experiment don&rsquo;t have that yet,&rdquo; Mullenweg <a href=\"https://twitter.com/photomatt/status/1346258917135769600\">said</a>. &ldquo;If it works then definitely we will try to open it up.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 05 Jan 2021 04:40:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:47:\"WPTavern: 2021: Reshaping the Tavern Experience\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109489\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:137:\"https://wptavern.com/2021-reshaping-the-tavern-experience?utm_source=rss&utm_medium=rss&utm_campaign=2021-reshaping-the-tavern-experience\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4025:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Resolutions. Goals. Guidelines for the year ahead. Call them what you want. Not everyone takes part, but I am a firm believer in having a vision for the coming months. That vision can be malleable, flowing with the changes of time, yielding to new ideas as they are birthed. However, some large, beaming guideposts help when setting foot into the wild of a new year.</p>\n\n\n\n<p>Our team at WP Tavern has gotten a bit of a breather over the holidays. We have an exciting project we are just getting off the ground. We set some things in motion months ago. Now, it is time to push forward.</p>\n\n\n\n<p>Without going into all of the details, which are currently in flux, the following are the big goals for the site in 2021.</p>\n\n\n\n<h2>New Design</h2>\n\n\n\n<p class=\"has-drop-cap\">The biggest goal of 2021 is to add a fresh coat of paint to the website. Going hand in hand with that goal is to launch this new design 100% on blocks. To effectively write about WordPress&rsquo;s upcoming changes, we need to be ahead of the game. That means living a bit on the bleeding edge, running a block-based theme, and testing the site editor. It means sharing what we love and airing our frustrations.</p>\n\n\n\n<p>Changing designs is not simply about slapping on some fresh colors. Design is about functionality. At the center of such a change is providing more tools for engagement.</p>\n\n\n\n<p>We are thinking over multiple ideas about what this might look like, and we have a generous third-party team standing by to help us implement much of this. Some of those ideas are things like showing the top comments and trending forum topics. Feedback from our readers is more than welcome in this regard. Ultimately, this is the part of the Tavern experience that belongs to you.</p>\n\n\n\n<p>The keen-eyed among you may have noticed I slipped in something about forum topics in the preceding paragraph. That was no accident. The return of the Tavern forums is a distinct possibility in 2021. There are many considerations we must make before going down this road around how it is moderated. The goal would be to provide an inviting atmosphere where people could freely talk about our beloved content management system. Again, this would be a feature of the site that is primarily about you.</p>\n\n\n\n<h2>Podcast</h2>\n\n\n\n<p class=\"has-drop-cap\">While many of you are avid readers of our content, we know some of you have asked us to bring back a podcast in some form. Some of you want to listen to WordPress-related news on your drive to work or while you unwind at the end of a busy day.</p>\n\n\n\n<p>We heard you loud and clear.</p>\n\n\n\n<p>Our team is actively pursuing adding a podcast. This is a project that we have been working on for a while now. It is something we genuinely want to happen.</p>\n\n\n\n<p>Before exploring this project, I had no idea of the amount of work necessary for producing a professional podcast. If you had put me behind the mic a few months ago, I would just be shooting from the hip, hoping to hit a target, any target. I have a newfound respect for anyone who produces a podcast today.</p>\n\n\n\n<p>If we get a new podcast off the ground in 2021, it will be a professionally-produced show. The goal is to have planned topics and guests representative of the diversity of the WordPress community. I am excited about the possibility.</p>\n\n\n\n<h2>Welcome to 2021</h2>\n\n\n\n<p class=\"has-drop-cap\">A new design and potential podcast are big-ticket items. They are not features we can launch overnight. When we do them, we want to do them right.</p>\n\n\n\n<p>There are other items on the checklist we will likely get to throughout the year too. But, this is a point in the year where we should sit back and listen. Are there things you want to see changed about the Tavern experience? Are there topics we missed last year that you want to see us cover more?</p>\n\n\n\n<p>As always, our team looks forward to bringing you our regular news, reviews, and opinions throughout the year. Stay tuned in for more.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 04 Jan 2021 21:36:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Fri, 29 Jan 2021 12:08:56 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Fri, 29 Jan 2021 12: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:4:\"gzip\";}}s:5:\"build\";s:14:\"20210129120756\";}', 'no');
  INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
  (136, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1611965337', 'no'),
  (137, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1611922137', 'no'),
  (138, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1611965337', 'no'),
  (139, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '<div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2021/01/people-of-wordpress-thelma-mutete/\'>People of WordPress: Thelma Mutete</a></li><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2021/01/the-month-in-wordpress-december-2020/\'>The Month in WordPress: December 2020</a></li></ul></div><div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wptavern.com/wp-lookout-lets-wordpress-users-track-and-receive-notifications-for-their-preferred-plugins-and-themes?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wp-lookout-lets-wordpress-users-track-and-receive-notifications-for-their-preferred-plugins-and-themes\'>WPTavern: WP Lookout Lets WordPress Users Track and Receive Notifications for Their Preferred Plugins and Themes</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/elasticpress-io-service-considers-next-move-after-elasticsearch-abandons-open-source-licensing?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=elasticpress-io-service-considers-next-move-after-elasticsearch-abandons-open-source-licensing\'>WPTavern: ElasticPress.io Service Considers Next Move after Elasticsearch Abandons Open Source Licensing</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/automattic-launches-the-blank-canvas-wordpress-theme-for-building-single-page-websites?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=automattic-launches-the-blank-canvas-wordpress-theme-for-building-single-page-websites\'>WPTavern: Automattic Launches the Blank Canvas WordPress Theme for Building Single-Page Websites</a></li></ul></div>', 'no');
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_postmeta`
  --
  
  CREATE TABLE `wp_postmeta` (
    `meta_id` bigint(20) UNSIGNED NOT NULL,
    `post_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
    `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_postmeta`
  --
  
  INSERT INTO `wp_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES
  (1, 2, '_wp_page_template', 'default'),
  (2, 3, '_wp_page_template', 'default');
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_posts`
  --
  
  CREATE TABLE `wp_posts` (
    `ID` bigint(20) UNSIGNED NOT NULL,
    `post_author` bigint(20) 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_ci NOT NULL,
    `post_title` text COLLATE utf8mb4_unicode_ci NOT NULL,
    `post_excerpt` text COLLATE utf8mb4_unicode_ci NOT NULL,
    `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish',
    `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open',
    `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open',
    `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `to_ping` text COLLATE utf8mb4_unicode_ci NOT NULL,
    `pinged` text COLLATE utf8mb4_unicode_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_ci NOT NULL,
    `post_parent` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `guid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `menu_order` int(11) NOT NULL DEFAULT 0,
    `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post',
    `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `comment_count` bigint(20) NOT NULL DEFAULT 0
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_posts`
  --
  
  INSERT INTO `wp_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, '2021-01-29 12:08:19', '2021-01-29 12:08:19', '<!-- wp:paragraph -->\n<p>Welcome to WordPress. This is your first post. Edit or delete it, then start writing!</p>\n<!-- /wp:paragraph -->', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2021-01-29 12:08:19', '2021-01-29 12:08:19', '', 0, 'http://34.116.235.52:5050/?p=1', 0, 'post', '', 1),
  (2, 1, '2021-01-29 12:08:55', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2021-01-29 12:08:55', '0000-00-00 00:00:00', '', 0, 'http://34.116.235.52:5050/?p=4', 0, 'post', '', 0);
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_termmeta`
  --
  
  CREATE TABLE `wp_termmeta` (
    `meta_id` bigint(20) UNSIGNED NOT NULL,
    `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
    `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_terms`
  --
  
  CREATE TABLE `wp_terms` (
    `term_id` bigint(20) UNSIGNED NOT NULL,
    `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `term_group` bigint(10) NOT NULL DEFAULT 0
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_terms`
  --
  
  INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES
  (1, 'Uncategorized', 'uncategorized', 0);
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_term_relationships`
  --
  
  CREATE TABLE `wp_term_relationships` (
    `object_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `term_order` int(11) NOT NULL DEFAULT 0
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_term_relationships`
  --
  
  INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES
  (1, 1, 0);
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_term_taxonomy`
  --
  
  CREATE TABLE `wp_term_taxonomy` (
    `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL,
    `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
    `parent` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `count` bigint(20) NOT NULL DEFAULT 0
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_term_taxonomy`
  --
  
  INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES
  (1, 1, 'category', '', 0, 1);
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_usermeta`
  --
  
  CREATE TABLE `wp_usermeta` (
    `umeta_id` bigint(20) UNSIGNED NOT NULL,
    `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT 0,
    `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
    `meta_value` longtext COLLATE utf8mb4_unicode_ci DEFAULT NULL
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_usermeta`
  --
  
  INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES
  (1, 1, 'nickname', 'cbach'),
  (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, 'wp_capabilities', 'a:1:{s:13:\"administrator\";b:1;}'),
  (13, 1, 'wp_user_level', '10'),
  (14, 1, 'dismissed_wp_pointers', ''),
  (15, 1, 'show_welcome_panel', '1'),
  (16, 1, 'session_tokens', 'a:1:{s:64:\"97b3c2c9d2de30a625bf9aa3f08411d41bf3ec4b280ee5de2e3d141081149f9c\";a:4:{s:10:\"expiration\";i:1612094931;s:2:\"ip\";s:10:\"172.17.0.1\";s:2:\"ua\";s:104:\"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36\";s:5:\"login\";i:1611922131;}}'),
  (17, 1, 'wp_dashboard_quick_press_last_post_id', '4'),
  (18, 1, 'community-events-location', 'a:1:{s:2:\"ip\";s:10:\"172.17.0.0\";}'),
  (19, 2, 'nickname', 'test'),
  (20, 2, 'first_name', ''),
  (21, 2, 'last_name', ''),
  (22, 2, 'description', ''),
  (23, 2, 'rich_editing', 'true'),
  (24, 2, 'syntax_highlighting', 'true'),
  (25, 2, 'comment_shortcuts', 'false'),
  (26, 2, 'admin_color', 'fresh'),
  (27, 2, 'use_ssl', '0'),
  (28, 2, 'show_admin_bar_front', 'true'),
  (29, 2, 'locale', ''),
  (30, 2, 'wp_capabilities', 'a:1:{s:10:\"subscriber\";b:1;}'),
  (31, 2, 'wp_user_level', '0'),
  (32, 2, 'dismissed_wp_pointers', ''),
  (33, 3, 'nickname', 'test2'),
  (34, 3, 'first_name', ''),
  (35, 3, 'last_name', ''),
  (36, 3, 'description', ''),
  (37, 3, 'rich_editing', 'true'),
  (38, 3, 'syntax_highlighting', 'true'),
  (39, 3, 'comment_shortcuts', 'false'),
  (40, 3, 'admin_color', 'fresh'),
  (41, 3, 'use_ssl', '0'),
  (42, 3, 'show_admin_bar_front', 'true'),
  (43, 3, 'locale', ''),
  (44, 3, 'wp_capabilities', 'a:1:{s:11:\"contributor\";b:1;}'),
  (45, 3, 'wp_user_level', '1'),
  (46, 3, 'dismissed_wp_pointers', ''),
  (47, 4, 'nickname', 'test3'),
  (48, 4, 'first_name', ''),
  (49, 4, 'last_name', ''),
  (50, 4, 'description', ''),
  (51, 4, 'rich_editing', 'true'),
  (52, 4, 'syntax_highlighting', 'true'),
  (53, 4, 'comment_shortcuts', 'false'),
  (54, 4, 'admin_color', 'fresh'),
  (55, 4, 'use_ssl', '0'),
  (56, 4, 'show_admin_bar_front', 'true'),
  (57, 4, 'locale', ''),
  (58, 4, 'wp_capabilities', 'a:1:{s:6:\"author\";b:1;}'),
  (59, 4, 'wp_user_level', '2'),
  (60, 4, 'dismissed_wp_pointers', ''),
  (61, 5, 'nickname', 'test4'),
  (62, 5, 'first_name', ''),
  (63, 5, 'last_name', ''),
  (64, 5, 'description', ''),
  (65, 5, 'rich_editing', 'true'),
  (66, 5, 'syntax_highlighting', 'true'),
  (67, 5, 'comment_shortcuts', 'false'),
  (68, 5, 'admin_color', 'fresh'),
  (69, 5, 'use_ssl', '0'),
  (70, 5, 'show_admin_bar_front', 'true'),
  (71, 5, 'locale', ''),
  (72, 5, 'wp_capabilities', 'a:1:{s:6:\"editor\";b:1;}'),
  (73, 5, 'wp_user_level', '7'),
  (74, 5, 'dismissed_wp_pointers', '');
  
  -- --------------------------------------------------------
  
  --
  -- Структура таблицы `wp_users`
  --
  
  CREATE TABLE `wp_users` (
    `ID` bigint(20) UNSIGNED NOT NULL,
    `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
    `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
    `user_status` int(11) NOT NULL DEFAULT 0,
    `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ''
  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
  
  --
  -- Дамп данных таблицы `wp_users`
  --
  
  INSERT INTO `wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES
  (1, 'cbach', '$P$BqWq48B0t1PAU0h7i50s0zm283uYWO1', 'cbach', 'cbach@cbach.cbach', 'http://34.116.235.52:5050', '2021-01-29 12:08:19', '', 0, 'cbach'),
  (2, 'test', '$P$BQ19vUlEDKgXEhgSqhyoKYeaqLaLao.', 'test', 'test@test.test', '', '2021-01-29 12:09:12', '1611922152:$P$BCSb32692jf1qqN2EZ9Q0EVviY22fa1', 0, 'test'),
  (3, 'test2', '$P$BX/CUd5xekJ7Txb3/Ubv2y3KIkwT0L0', 'test2', 'test2@test2.test2', '', '2021-01-29 12:09:21', '1611922161:$P$BZO1Wpjp4HhEv3mxsTZ9/TFQ6S8hZ21', 0, 'test2'),
  (4, 'test3', '$P$B/1J1rqYk4YFwzHSxRkGoYZeZe1Rqu.', 'test3', 'test3@test3.test3', '', '2021-01-29 12:09:37', '1611922177:$P$B9RSjrVDsUpSBPImKvUKoeboizCiwU.', 0, 'test3'),
  (5, 'test4', '$P$BRkB4BOK2yvEliu4lWDvTbIfVVH1t4.', 'test4', 'test4@test4.test4', '', '2021-01-29 12:09:51', '1611922192:$P$BilI27YvpftKNXbDhS72gxqm0DvM3F0', 0, 'test4');
  
  --
  -- Индексы сохранённых таблиц
  --
  
  --
  -- Индексы таблицы `wp_commentmeta`
  --
  ALTER TABLE `wp_commentmeta`
    ADD PRIMARY KEY (`meta_id`),
    ADD KEY `comment_id` (`comment_id`),
    ADD KEY `meta_key` (`meta_key`(191));
  
  --
  -- Индексы таблицы `wp_comments`
  --
  ALTER TABLE `wp_comments`
    ADD PRIMARY KEY (`comment_ID`),
    ADD KEY `comment_post_ID` (`comment_post_ID`),
    ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
    ADD KEY `comment_date_gmt` (`comment_date_gmt`),
    ADD KEY `comment_parent` (`comment_parent`),
    ADD KEY `comment_author_email` (`comment_author_email`(10));
  
  --
  -- Индексы таблицы `wp_links`
  --
  ALTER TABLE `wp_links`
    ADD PRIMARY KEY (`link_id`),
    ADD KEY `link_visible` (`link_visible`);
  
  --
  -- Индексы таблицы `wp_options`
  --
  ALTER TABLE `wp_options`
    ADD PRIMARY KEY (`option_id`),
    ADD UNIQUE KEY `option_name` (`option_name`),
    ADD KEY `autoload` (`autoload`);
  
  --
  -- Индексы таблицы `wp_postmeta`
  --
  ALTER TABLE `wp_postmeta`
    ADD PRIMARY KEY (`meta_id`),
    ADD KEY `post_id` (`post_id`),
    ADD KEY `meta_key` (`meta_key`(191));
  
  --
  -- Индексы таблицы `wp_posts`
  --
  ALTER TABLE `wp_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`);
  
  --
  -- Индексы таблицы `wp_termmeta`
  --
  ALTER TABLE `wp_termmeta`
    ADD PRIMARY KEY (`meta_id`),
    ADD KEY `term_id` (`term_id`),
    ADD KEY `meta_key` (`meta_key`(191));
  
  --
  -- Индексы таблицы `wp_terms`
  --
  ALTER TABLE `wp_terms`
    ADD PRIMARY KEY (`term_id`),
    ADD KEY `slug` (`slug`(191)),
    ADD KEY `name` (`name`(191));
  
  --
  -- Индексы таблицы `wp_term_relationships`
  --
  ALTER TABLE `wp_term_relationships`
    ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`),
    ADD KEY `term_taxonomy_id` (`term_taxonomy_id`);
  
  --
  -- Индексы таблицы `wp_term_taxonomy`
  --
  ALTER TABLE `wp_term_taxonomy`
    ADD PRIMARY KEY (`term_taxonomy_id`),
    ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
    ADD KEY `taxonomy` (`taxonomy`);
  
  --
  -- Индексы таблицы `wp_usermeta`
  --
  ALTER TABLE `wp_usermeta`
    ADD PRIMARY KEY (`umeta_id`),
    ADD KEY `user_id` (`user_id`),
    ADD KEY `meta_key` (`meta_key`(191));
  
  --
  -- Индексы таблицы `wp_users`
  --
  ALTER TABLE `wp_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 для сохранённых таблиц
  --
  
  --
  -- AUTO_INCREMENT для таблицы `wp_commentmeta`
  --
  ALTER TABLE `wp_commentmeta`
    MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_comments`
  --
  ALTER TABLE `wp_comments`
    MODIFY `comment_ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_links`
  --
  ALTER TABLE `wp_links`
    MODIFY `link_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_options`
  --
  ALTER TABLE `wp_options`
    MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=140;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_postmeta`
  --
  ALTER TABLE `wp_postmeta`
    MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_posts`
  --
  ALTER TABLE `wp_posts`
    MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_termmeta`
  --
  ALTER TABLE `wp_termmeta`
    MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_terms`
  --
  ALTER TABLE `wp_terms`
    MODIFY `term_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_term_taxonomy`
  --
  ALTER TABLE `wp_term_taxonomy`
    MODIFY `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_usermeta`
  --
  ALTER TABLE `wp_usermeta`
    MODIFY `umeta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=75;
  
  --
  -- AUTO_INCREMENT для таблицы `wp_users`
  --
  ALTER TABLE `wp_users`
    MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
  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 */;
  