--
-- Host: localhost    Database: norteldata
-- ------------------------------------------------------


--
-- Table structure for table `wp_alm`
--

CREATE TABLE `wp_alm` (
  `id` mediumint(9) NOT NULL AUTO_INCREMENT,
  `name` text COLLATE utf8_unicode_ci NOT NULL,
  `repeaterDefault` longtext COLLATE utf8_unicode_ci NOT NULL,
  `repeaterType` text COLLATE utf8_unicode_ci NOT NULL,
  `pluginVersion` text COLLATE utf8_unicode_ci NOT NULL,
  UNIQUE KEY `id` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

--
-- Dumping data for table `wp_alm`
--

INSERT INTO `wp_alm` VALUES (1,'default','<?php $category = get_the_category(); ?>\n<article id=\"post-<?php the_ID(); ?>\" class=\"linkarticle\">\n    <a href=\"<?php the_permalink(); ?>\" class=\"contentImage\">\n        <?php if(has_post_thumbnail()): ?>\n            <?php the_post_thumbnail( \'thumb-post-medium\' ); ?>\n        <?php endif; ?>\n    </a>\n    <header>     \n        <h5><a href=\"<?php the_permalink(); ?>\"><?php the_title(); ?></a></h5>\n        <div class=\"meta\">\n        	<?php if(\'post\' == get_post_type()): ?>\n            <a href=\"<?php echo get_category_link($category[0]->term_id); ?>\" class=\"bt-category bg-cat-<?php echo $category[0]->slug; ?>\"><?php echo $category[0]->cat_name; ?></a>\n            <span class=\"separador\"></span>\n        	<?php endif; ?>\n            <span class=\"data\"><?php the_time(\'d\'); ?>/<?php the_time(\'m\'); ?>/<?php the_time(\'Y\'); ?></span> \n        </div><!-- .meta -->\n    </header>\n</article>','default','5.4.0');

--
-- Table structure for table `wp_commentmeta`
--

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

--
-- Dumping data for table `wp_commentmeta`
--


--
-- Table structure for table `wp_comments`
--

CREATE TABLE `wp_comments` (
  `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0',
  `comment_author` tinytext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_content` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `comment_karma` int(11) NOT NULL DEFAULT '0',
  `comment_approved` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '1',
  `comment_agent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `comment_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'comment',
  `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0',
  `user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`comment_ID`),
  KEY `comment_post_ID` (`comment_post_ID`),
  KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
  KEY `comment_date_gmt` (`comment_date_gmt`),
  KEY `comment_parent` (`comment_parent`),
  KEY `comment_author_email` (`comment_author_email`(10))
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_comments`
--


--
-- Table structure for table `wp_links`
--

CREATE TABLE `wp_links` (
  `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_visible` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'Y',
  `link_owner` bigint(20) unsigned NOT NULL DEFAULT '1',
  `link_rating` int(11) NOT NULL DEFAULT '0',
  `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `link_rel` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  `link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
  `link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
  PRIMARY KEY (`link_id`),
  KEY `link_visible` (`link_visible`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;

--
-- Dumping data for table `wp_links`
--


--
-- Table structure for table `wp_options`
--

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

--
-- Dumping data for table `wp_options`
--

INSERT INTO `wp_options` VALUES (3,'siteurl','https://norteldata.labcp.co/wp','yes'),(4,'home','https://norteldata.labcp.co/wp','yes'),(5,'blogname','Norteldata','yes'),(6,'blogdescription','','yes'),(7,'users_can_register','0','yes'),(8,'admin_email','dev@cappen.com','yes'),(9,'start_of_week','0','yes'),(10,'use_balanceTags','0','yes'),(11,'use_smilies','1','yes'),(12,'require_name_email','1','yes'),(13,'comments_notify','1','yes'),(14,'posts_per_rss','10','yes'),(15,'rss_use_excerpt','0','yes'),(16,'mailserver_url','mail.example.com','yes'),(17,'mailserver_login','login@example.com','yes'),(18,'mailserver_pass','password','yes'),(19,'mailserver_port','110','yes'),(20,'default_category','1','yes'),(21,'default_comment_status','open','yes'),(22,'default_ping_status','open','yes'),(23,'default_pingback_flag','1','yes'),(24,'posts_per_page','10','yes'),(25,'date_format','j \\d\\e F \\d\\e Y','yes'),(26,'time_format','H:i','yes'),(27,'links_updated_date_format','j \\d\\e F \\d\\e Y, H:i','yes'),(28,'comment_moderation','0','yes'),(29,'moderation_notify','1','yes'),(30,'permalink_structure','/%postname%/','yes'),(31,'rewrite_rules','a:94:{s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:17:\"^wp-sitemap\\.xml$\";s:23:\"index.php?sitemap=index\";s:17:\"^wp-sitemap\\.xsl$\";s:36:\"index.php?sitemap-stylesheet=sitemap\";s:23:\"^wp-sitemap-index\\.xsl$\";s:34:\"index.php?sitemap-stylesheet=index\";s:48:\"^wp-sitemap-([a-z]+?)-([a-z\\d_-]+?)-(\\d+?)\\.xml$\";s:75:\"index.php?sitemap=$matches[1]&sitemap-subtype=$matches[2]&paged=$matches[3]\";s:34:\"^wp-sitemap-([a-z]+?)-(\\d+?)\\.xml$\";s:47:\"index.php?sitemap=$matches[1]&paged=$matches[2]\";s:47:\"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:42:\"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:23:\"category/(.+?)/embed/?$\";s:46:\"index.php?category_name=$matches[1]&embed=true\";s:35:\"category/(.+?)/page/?([0-9]{1,})/?$\";s:53:\"index.php?category_name=$matches[1]&paged=$matches[2]\";s:17:\"category/(.+?)/?$\";s:35:\"index.php?category_name=$matches[1]\";s:44:\"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:39:\"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:20:\"tag/([^/]+)/embed/?$\";s:36:\"index.php?tag=$matches[1]&embed=true\";s:32:\"tag/([^/]+)/page/?([0-9]{1,})/?$\";s:43:\"index.php?tag=$matches[1]&paged=$matches[2]\";s:14:\"tag/([^/]+)/?$\";s:25:\"index.php?tag=$matches[1]\";s:45:\"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:40:\"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:21:\"type/([^/]+)/embed/?$\";s:44:\"index.php?post_format=$matches[1]&embed=true\";s:33:\"type/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?post_format=$matches[1]&paged=$matches[2]\";s:15:\"type/([^/]+)/?$\";s:33:\"index.php?post_format=$matches[1]\";s:12:\"robots\\.txt$\";s:18:\"index.php?robots=1\";s:13:\"favicon\\.ico$\";s:19:\"index.php?favicon=1\";s:48:\".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$\";s:18:\"index.php?feed=old\";s:20:\".*wp-app\\.php(/.*)?$\";s:19:\"index.php?error=403\";s:18:\".*wp-register.php$\";s:23:\"index.php?register=true\";s:32:\"feed/(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:27:\"(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:8:\"embed/?$\";s:21:\"index.php?&embed=true\";s:20:\"page/?([0-9]{1,})/?$\";s:28:\"index.php?&paged=$matches[1]\";s:27:\"comment-page-([0-9]{1,})/?$\";s:38:\"index.php?&page_id=6&cpage=$matches[1]\";s:41:\"comments/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:36:\"comments/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:17:\"comments/embed/?$\";s:21:\"index.php?&embed=true\";s:44:\"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:39:\"search/(.+)/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:20:\"search/(.+)/embed/?$\";s:34:\"index.php?s=$matches[1]&embed=true\";s:32:\"search/(.+)/page/?([0-9]{1,})/?$\";s:41:\"index.php?s=$matches[1]&paged=$matches[2]\";s:14:\"search/(.+)/?$\";s:23:\"index.php?s=$matches[1]\";s:47:\"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:42:\"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:23:\"author/([^/]+)/embed/?$\";s:44:\"index.php?author_name=$matches[1]&embed=true\";s:35:\"author/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?author_name=$matches[1]&paged=$matches[2]\";s:17:\"author/([^/]+)/?$\";s:33:\"index.php?author_name=$matches[1]\";s:69:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:45:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$\";s:74:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]\";s:39:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$\";s:63:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]\";s:56:\"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:51:\"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:32:\"([0-9]{4})/([0-9]{1,2})/embed/?$\";s:58:\"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true\";s:44:\"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]\";s:26:\"([0-9]{4})/([0-9]{1,2})/?$\";s:47:\"index.php?year=$matches[1]&monthnum=$matches[2]\";s:43:\"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:38:\"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:19:\"([0-9]{4})/embed/?$\";s:37:\"index.php?year=$matches[1]&embed=true\";s:31:\"([0-9]{4})/page/?([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&paged=$matches[2]\";s:13:\"([0-9]{4})/?$\";s:26:\"index.php?year=$matches[1]\";s:27:\".?.+?/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\".?.+?/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\".?.+?/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"(.?.+?)/embed/?$\";s:41:\"index.php?pagename=$matches[1]&embed=true\";s:20:\"(.?.+?)/trackback/?$\";s:35:\"index.php?pagename=$matches[1]&tb=1\";s:40:\"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:35:\"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:28:\"(.?.+?)/page/?([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&paged=$matches[2]\";s:35:\"(.?.+?)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&cpage=$matches[2]\";s:24:\"(.?.+?)(?:/([0-9]+))?/?$\";s:47:\"index.php?pagename=$matches[1]&page=$matches[2]\";s:27:\"[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\"[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\"[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\"[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\"[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\"[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"([^/]+)/embed/?$\";s:37:\"index.php?name=$matches[1]&embed=true\";s:20:\"([^/]+)/trackback/?$\";s:31:\"index.php?name=$matches[1]&tb=1\";s:40:\"([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?name=$matches[1]&feed=$matches[2]\";s:35:\"([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?name=$matches[1]&feed=$matches[2]\";s:28:\"([^/]+)/page/?([0-9]{1,})/?$\";s:44:\"index.php?name=$matches[1]&paged=$matches[2]\";s:35:\"([^/]+)/comment-page-([0-9]{1,})/?$\";s:44:\"index.php?name=$matches[1]&cpage=$matches[2]\";s:24:\"([^/]+)(?:/([0-9]+))?/?$\";s:43:\"index.php?name=$matches[1]&page=$matches[2]\";s:16:\"[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:26:\"[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:46:\"[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:41:\"[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:41:\"[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:22:\"[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";}','yes'),(32,'hack_file','0','yes'),(33,'blog_charset','UTF-8','yes'),(34,'moderation_keys','','no'),(35,'active_plugins','a:6:{i:0;s:25:\"add-to-any/add-to-any.php\";i:1;s:34:\"advanced-custom-fields-pro/acf.php\";i:2;s:33:\"ajax-load-more/ajax-load-more.php\";i:3;s:36:\"contact-form-7/wp-contact-form-7.php\";i:4;s:21:\"safe-svg/safe-svg.php\";i:5;s:41:\"wordpress-importer/wordpress-importer.php\";}','yes'),(36,'category_base','','yes'),(37,'ping_sites','http://rpc.pingomatic.com/','yes'),(38,'comment_max_links','2','yes'),(39,'gmt_offset','','yes'),(40,'default_email_category','1','yes'),(41,'recently_edited','','no'),(42,'template','norteldata','yes'),(43,'stylesheet','norteldata','yes'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','48748','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','page','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'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'),(79,'widget_text','a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}','yes'),(80,'widget_rss','a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}','yes'),(81,'uninstall_plugins','a:0:{}','no'),(82,'timezone_string','America/Sao_Paulo','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','6','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'wp_page_for_privacy_policy','3','yes'),(92,'show_comments_cookies_opt_in','1','yes'),(93,'admin_email_lifespan','1621192686','yes'),(94,'disallowed_keys','','no'),(95,'comment_previously_approved','1','yes'),(96,'auto_plugin_theme_update_emails','a:0:{}','no'),(97,'initial_db_version','48748','yes'),(98,'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'),(99,'fresh_site','0','yes'),(100,'WPLANG','pt_BR','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:2:{s:19:\"wp_inactive_widgets\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}','yes'),(107,'bedrock_autoloader','a:2:{s:7:\"plugins\";a:0:{}s:5:\"count\";i:0;}','no'),(108,'cron','a:6:{i:1611001086;a:1:{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;}}}i:1611040686;a:3:{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:1611083886;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:1611083892;a:3:{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;}}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:1611170286;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'),(109,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(110,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(111,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(112,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(113,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(114,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(115,'nonce_key','R&4Qiap_Sk,i e3aLJ9r@:=2BcV#4$~7mF;,kLu#N_6{2fnn5g<~<5vD_/b?AwJy','no'),(116,'nonce_salt','Vi^i.VnJBY`YCI8>9|:+(6tOB^yU_$CS~h 3JRj];(@uF;j%Q,{HiVKO -=F!3je','no'),(117,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(118,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(119,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(121,'theme_mods_twentytwenty','a:2:{s:18:\"custom_css_post_id\";i:-1;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1605640727;s:4:\"data\";a:3:{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\";}}}}','yes'),(122,'recovery_keys','a:0:{}','yes'),(125,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1610997535;s:7:\"checked\";a:4:{s:10:\"norteldata\";s:5:\"1.0.0\";s:14:\"twentynineteen\";s:3:\"1.7\";s:15:\"twentyseventeen\";s:3:\"2.4\";s:12:\"twentytwenty\";s:3:\"1.5\";}s:8:\"response\";a:3:{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:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"2.5\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.2.5.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}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:9:\"no_update\";a:0:{}s:12:\"translations\";a:0:{}}','no'),(126,'secure_auth_key','zm.6{:)O)_sd?usit+ # (hi+omu4x>BEL`c:DW7u09W,EJdL?V=^{5[MRx$tM12','no'),(127,'secure_auth_salt','^d}*zZ*:SHe3J57fYU$(mfk?=2}1t{JQ7^_WLG%`rm7b$,IB?UkW?OUJqEvt|yhx','no'),(128,'logged_in_key','TY}Y|Ob~U!7V}|WTz/T7H|;2:R@kW|uQ~DZ<0EDMHvkE/eR`6)P#>argRPN1&3@8','no'),(129,'logged_in_salt','[Az+yBc]DfEeaG5#VnyINZtIv4W:T%}3$%Mi@s9vG$4<^h3OA;^gx,2+aQEx$Jym','no'),(141,'can_compress_scripts','0','no'),(148,'template_root','/themes','yes'),(149,'stylesheet_root','/themes','yes'),(150,'current_theme','norteldata','yes'),(151,'theme_mods_norteldata','a:3:{i:0;b:0;s:18:\"nav_menu_locations\";a:0:{}s:18:\"custom_css_post_id\";i:-1;}','yes'),(152,'theme_switched','','yes'),(155,'finished_updating_comment_type','1','yes'),(158,'_site_transient_update_core','O:8:\"stdClass\":4:{s:7:\"updates\";a:3:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:7:\"upgrade\";s:8:\"download\";s:63:\"https://downloads.wordpress.org/release/pt_BR/wordpress-5.6.zip\";s:6:\"locale\";s:5:\"pt_BR\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:63:\"https://downloads.wordpress.org/release/pt_BR/wordpress-5.6.zip\";s:10:\"no_content\";s:0:\"\";s:11:\"new_bundled\";s:0:\"\";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:\"\";}i:1;O:8:\"stdClass\":10:{s:8:\"response\";s:7:\"upgrade\";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:\"\";}i:2;O:8:\"stdClass\":11:{s:8:\"response\";s:10:\"autoupdate\";s:8:\"download\";s:63:\"https://downloads.wordpress.org/release/pt_BR/wordpress-5.6.zip\";s:6:\"locale\";s:5:\"pt_BR\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:63:\"https://downloads.wordpress.org/release/pt_BR/wordpress-5.6.zip\";s:10:\"no_content\";s:0:\"\";s:11:\"new_bundled\";s:0:\"\";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:9:\"new_files\";s:1:\"1\";}}s:12:\"last_checked\";i:1610997534;s:15:\"version_checked\";s:5:\"5.5.3\";s:12:\"translations\";a:0:{}}','no'),(165,'auth_key','}uqQDL`s@JA+H= l^K??vbWmRuXKwBL>WqZRvWZ;bI/*7i[^!$bH,>l%h{h]d<o#','no'),(166,'auth_salt','v=-<-Zz vxm+&BP:$xjDO`z+$$<9zd*_<J/pzFj}>!8I01FN&C?3Nb_o7a5R.g,i','no'),(167,'nav_menu_options','a:1:{s:8:\"auto_add\";a:0:{}}','yes'),(176,'_transient_health-check-site-status-result','{\"good\":\"10\",\"recommended\":\"8\",\"critical\":\"2\"}','yes'),(189,'recently_activated','a:0:{}','yes'),(190,'acf_version','5.9.3','yes'),(219,'wpcf7','a:2:{s:7:\"version\";s:3:\"5.3\";s:13:\"bulk_validate\";a:4:{s:9:\"timestamp\";i:1605899527;s:7:\"version\";s:3:\"5.3\";s:11:\"count_valid\";i:1;s:13:\"count_invalid\";i:0;}}','yes'),(220,'secret_key','&A=k}CHNv<t=9Tzl}S]ypm{Zb03}?y9/o=eBWaSJP>I0C_f7J0cXg`xO@G_jjCy]','no'),(223,'options_texto_privacy','Privacy','no'),(224,'_options_texto_privacy','field_5fb80cef00eb4','no'),(225,'options_link_privacy','http://google.com','no'),(226,'_options_link_privacy','field_5fb80b4d60c74','no'),(227,'options_copyright','© 2020 / Copyright - Norteldata','no'),(228,'_options_copyright','field_5fb80ca451a2b','no'),(229,'options_social_media_0_rede','Twitter','no'),(230,'_options_social_media_0_rede','field_5fb80b8560c77','no'),(231,'options_social_media_0_link','https://mobile.twitter.com/ENorteldata','no'),(232,'_options_social_media_0_link','field_5fb80b9b60c78','no'),(233,'options_social_media_0_icone','82','no'),(234,'_options_social_media_0_icone','field_5fb80baa60c79','no'),(235,'options_social_media_0_icone_hover','83','no'),(236,'_options_social_media_0_icone_hover','field_5fb80bbc60c7a','no'),(237,'options_social_media_1_rede','Instagram','no'),(238,'_options_social_media_1_rede','field_5fb80b8560c77','no'),(239,'options_social_media_1_link','https://www.instagram.com/norteldata/','no'),(240,'_options_social_media_1_link','field_5fb80b9b60c78','no'),(241,'options_social_media_1_icone','80','no'),(242,'_options_social_media_1_icone','field_5fb80baa60c79','no'),(243,'options_social_media_1_icone_hover','81','no'),(244,'_options_social_media_1_icone_hover','field_5fb80bbc60c7a','no'),(245,'options_social_media_2_rede','Facebook','no'),(246,'_options_social_media_2_rede','field_5fb80b8560c77','no'),(247,'options_social_media_2_link','https://www.facebook.com/norteldata','no'),(248,'_options_social_media_2_link','field_5fb80b9b60c78','no'),(249,'options_social_media_2_icone','78','no'),(250,'_options_social_media_2_icone','field_5fb80baa60c79','no'),(251,'options_social_media_2_icone_hover','79','no'),(252,'_options_social_media_2_icone_hover','field_5fb80bbc60c7a','no'),(261,'options_social_media','3','no'),(262,'_options_social_media','field_5fb80b7460c76','no'),(320,'widget_a2a_share_save_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(321,'widget_a2a_follow_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(324,'alm_version','5.4.0','yes'),(325,'alm-install-date','2020-11-24','no'),(326,'addtoany_options','a:32:{s:8:\"position\";s:6:\"bottom\";s:30:\"display_in_posts_on_front_page\";s:2:\"-1\";s:33:\"display_in_posts_on_archive_pages\";s:2:\"-1\";s:19:\"display_in_excerpts\";s:2:\"-1\";s:16:\"display_in_posts\";s:2:\"-1\";s:16:\"display_in_pages\";s:2:\"-1\";s:22:\"display_in_attachments\";s:2:\"-1\";s:15:\"display_in_feed\";s:2:\"-1\";s:7:\"onclick\";s:2:\"-1\";s:9:\"icon_size\";s:2:\"40\";s:7:\"icon_bg\";s:6:\"custom\";s:13:\"icon_bg_color\";s:7:\"#aca8ba\";s:7:\"icon_fg\";s:6:\"custom\";s:13:\"icon_fg_color\";s:7:\"#ffffff\";s:6:\"button\";s:4:\"NONE\";s:13:\"button_custom\";s:0:\"\";s:17:\"button_show_count\";s:2:\"-1\";s:6:\"header\";s:0:\"\";s:23:\"additional_js_variables\";s:0:\"\";s:14:\"additional_css\";s:0:\"\";s:12:\"custom_icons\";s:2:\"-1\";s:16:\"custom_icons_url\";s:1:\"/\";s:17:\"custom_icons_type\";s:3:\"png\";s:18:\"custom_icons_width\";s:0:\"\";s:19:\"custom_icons_height\";s:0:\"\";s:5:\"cache\";s:2:\"-1\";s:11:\"button_text\";s:12:\"Compartilhar\";s:24:\"special_facebook_options\";a:1:{s:10:\"show_count\";s:2:\"-1\";}s:15:\"active_services\";a:4:{i:0;s:9:\"copy_link\";i:1;s:8:\"whatsapp\";i:2;s:7:\"twitter\";i:3;s:8:\"facebook\";}s:29:\"special_facebook_like_options\";a:2:{s:10:\"show_count\";s:2:\"-1\";s:4:\"verb\";s:4:\"like\";}s:29:\"special_twitter_tweet_options\";a:1:{s:10:\"show_count\";s:2:\"-1\";}s:29:\"special_pinterest_pin_options\";a:1:{s:10:\"show_count\";s:2:\"-1\";}}','yes'),(327,'alm_settings','a:11:{s:19:\"_alm_container_type\";s:1:\"2\";s:14:\"_alm_classname\";s:0:\"\";s:16:\"_alm_disable_css\";s:1:\"1\";s:14:\"_alm_btn_color\";s:7:\"default\";s:15:\"_alm_inline_css\";s:1:\"1\";s:18:\"_alm_btn_classname\";s:0:\"\";s:21:\"_alm_legacy_callbacks\";s:1:\"0\";s:14:\"_alm_uninstall\";s:1:\"0\";s:20:\"_alm_disable_dynamic\";s:1:\"0\";s:13:\"_alm_hide_btn\";s:1:\"0\";s:18:\"_alm_error_notices\";s:1:\"1\";}','yes'),(335,'_site_transient_update_plugins','O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1610997534;s:8:\"response\";a:3:{s:33:\"ajax-load-more/ajax-load-more.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:28:\"w.org/plugins/ajax-load-more\";s:4:\"slug\";s:14:\"ajax-load-more\";s:6:\"plugin\";s:33:\"ajax-load-more/ajax-load-more.php\";s:11:\"new_version\";s:7:\"5.4.2.1\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/ajax-load-more/\";s:7:\"package\";s:57:\"https://downloads.wordpress.org/plugin/ajax-load-more.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/ajax-load-more/assets/icon-256x256.png?rev=1631559\";s:2:\"1x\";s:67:\"https://ps.w.org/ajax-load-more/assets/icon-128x128.png?rev=1667395\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:69:\"https://ps.w.org/ajax-load-more/assets/banner-772x250.jpg?rev=2117690\";}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:36:\"contact-form-7/wp-contact-form-7.php\";O:8:\"stdClass\":12:{s:2:\"id\";s:28:\"w.org/plugins/contact-form-7\";s:4:\"slug\";s:14:\"contact-form-7\";s:6:\"plugin\";s:36:\"contact-form-7/wp-contact-form-7.php\";s:11:\"new_version\";s:5:\"5.3.2\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/contact-form-7/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/plugin/contact-form-7.5.3.2.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:67:\"https://ps.w.org/contact-form-7/assets/icon-256x256.png?rev=2279696\";s:2:\"1x\";s:59:\"https://ps.w.org/contact-form-7/assets/icon.svg?rev=2339255\";s:3:\"svg\";s:59:\"https://ps.w.org/contact-form-7/assets/icon.svg?rev=2339255\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:69:\"https://ps.w.org/contact-form-7/assets/banner-1544x500.png?rev=860901\";s:2:\"1x\";s:68:\"https://ps.w.org/contact-form-7/assets/banner-772x250.png?rev=880427\";}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:34:\"advanced-custom-fields-pro/acf.php\";O:8:\"stdClass\":8:{s:4:\"slug\";s:26:\"advanced-custom-fields-pro\";s:6:\"plugin\";s:34:\"advanced-custom-fields-pro/acf.php\";s:11:\"new_version\";s:5:\"5.9.4\";s:3:\"url\";s:36:\"https://www.advancedcustomfields.com\";s:6:\"tested\";s:3:\"5.6\";s:7:\"package\";s:0:\"\";s:5:\"icons\";a:1:{s:7:\"default\";s:63:\"https://ps.w.org/advanced-custom-fields/assets/icon-256x256.png\";}s:7:\"banners\";a:2:{s:3:\"low\";s:77:\"https://ps.w.org/advanced-custom-fields/assets/banner-772x250.jpg?rev=1729102\";s:4:\"high\";s:78:\"https://ps.w.org/advanced-custom-fields/assets/banner-1544x500.jpg?rev=1729099\";}}}s:12:\"translations\";a:2:{i:0;a:7:{s:4:\"type\";s:6:\"plugin\";s:4:\"slug\";s:14:\"contact-form-7\";s:8:\"language\";s:5:\"pt_BR\";s:7:\"version\";s:3:\"5.3\";s:7:\"updated\";s:19:\"2020-11-09 20:49:35\";s:7:\"package\";s:79:\"https://downloads.wordpress.org/translation/plugin/contact-form-7/5.3/pt_BR.zip\";s:10:\"autoupdate\";b:1;}i:1;a:7:{s:4:\"type\";s:6:\"plugin\";s:4:\"slug\";s:18:\"wordpress-importer\";s:8:\"language\";s:5:\"pt_BR\";s:7:\"version\";s:3:\"0.7\";s:7:\"updated\";s:19:\"2020-04-10 06:32:15\";s:7:\"package\";s:83:\"https://downloads.wordpress.org/translation/plugin/wordpress-importer/0.7/pt_BR.zip\";s:10:\"autoupdate\";b:1;}}s:9:\"no_update\";a:3:{s:25:\"add-to-any/add-to-any.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:24:\"w.org/plugins/add-to-any\";s:4:\"slug\";s:10:\"add-to-any\";s:6:\"plugin\";s:25:\"add-to-any/add-to-any.php\";s:11:\"new_version\";s:6:\"1.7.42\";s:3:\"url\";s:41:\"https://wordpress.org/plugins/add-to-any/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/add-to-any.1.7.42.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:62:\"https://ps.w.org/add-to-any/assets/icon-256x256.png?rev=972738\";s:2:\"1x\";s:54:\"https://ps.w.org/add-to-any/assets/icon.svg?rev=972738\";s:3:\"svg\";s:54:\"https://ps.w.org/add-to-any/assets/icon.svg?rev=972738\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:66:\"https://ps.w.org/add-to-any/assets/banner-1544x500.png?rev=2167358\";s:2:\"1x\";s:65:\"https://ps.w.org/add-to-any/assets/banner-772x250.png?rev=2167357\";}s:11:\"banners_rtl\";a:0:{}}s:21:\"safe-svg/safe-svg.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:22:\"w.org/plugins/safe-svg\";s:4:\"slug\";s:8:\"safe-svg\";s:6:\"plugin\";s:21:\"safe-svg/safe-svg.php\";s:11:\"new_version\";s:5:\"1.9.9\";s:3:\"url\";s:39:\"https://wordpress.org/plugins/safe-svg/\";s:7:\"package\";s:57:\"https://downloads.wordpress.org/plugin/safe-svg.1.9.9.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:61:\"https://ps.w.org/safe-svg/assets/icon-256x256.png?rev=1706191\";s:2:\"1x\";s:53:\"https://ps.w.org/safe-svg/assets/icon.svg?rev=1706191\";s:3:\"svg\";s:53:\"https://ps.w.org/safe-svg/assets/icon.svg?rev=1706191\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/safe-svg/assets/banner-1544x500.png?rev=1706191\";s:2:\"1x\";s:63:\"https://ps.w.org/safe-svg/assets/banner-772x250.png?rev=1706191\";}s:11:\"banners_rtl\";a:0:{}}s:41:\"wordpress-importer/wordpress-importer.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:32:\"w.org/plugins/wordpress-importer\";s:4:\"slug\";s:18:\"wordpress-importer\";s:6:\"plugin\";s:41:\"wordpress-importer/wordpress-importer.php\";s:11:\"new_version\";s:3:\"0.7\";s:3:\"url\";s:49:\"https://wordpress.org/plugins/wordpress-importer/\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/plugin/wordpress-importer.0.7.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:71:\"https://ps.w.org/wordpress-importer/assets/icon-256x256.png?rev=1908375\";s:2:\"1x\";s:63:\"https://ps.w.org/wordpress-importer/assets/icon.svg?rev=1908375\";s:3:\"svg\";s:63:\"https://ps.w.org/wordpress-importer/assets/icon.svg?rev=1908375\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:72:\"https://ps.w.org/wordpress-importer/assets/banner-772x250.png?rev=547654\";}s:11:\"banners_rtl\";a:0:{}}}}','no'),(384,'new_admin_email','dev@cappen.com','yes'),(810,'_site_transient_timeout_php_check_8445f3f6d5c32e543da408dfa7e06e48','1611237145','no'),(811,'_site_transient_php_check_8445f3f6d5c32e543da408dfa7e06e48','a:5:{s:19:\"recommended_version\";s:3:\"7.4\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:0;s:9:\"is_secure\";b:1;s:13:\"is_acceptable\";b:1;}','no'),(827,'_site_transient_timeout_browser_94fb6483abf307a4bafac80827dcc22a','1611583912','no'),(828,'_site_transient_browser_94fb6483abf307a4bafac80827dcc22a','a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"87.0.4280.141\";s:8:\"platform\";s:7:\"Windows\";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'),(829,'_site_transient_timeout_community-events-ca7ff8b6c58d2c97253fe366cc5386dc','1611022313','no'),(830,'_site_transient_community-events-ca7ff8b6c58d2c97253fe366cc5386dc','a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:13:\"191.187.128.0\";}s:6:\"events\";a:2:{i:0;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:42:\"Discussion group: Custom CSS in the Editor\";s:3:\"url\";s:68:\"https://www.meetup.com/learn-wordpress-discussions/events/275746097/\";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-01-19 01:00:00\";s:8:\"end_date\";s:19:\"2021-01-19 02:00:00\";s:20:\"start_unix_timestamp\";i:1611046800;s:18:\"end_unix_timestamp\";i:1611050400;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'),(831,'_transient_timeout_feed_b85365aa61afaf3d4189819a6f57c4c4','1611022313','no'),(832,'_transient_feed_b85365aa61afaf3d4189819a6f57c4c4','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"Blog | 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:24:\"https://br.wordpress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Dec 2020 19:12:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"pt-BR\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=5.7-alpha-49973\";s:7:\"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: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:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Introdução ao 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:66:\"https://br.wordpress.org/2020/12/21/introducao-ao-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:\"Mon, 21 Dec 2020 19:12:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://br.wordpress.org/?p=2163\";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:365:\"Learn WordPress é um espaço de aprendizagem que oferece workshops, quizzes, cursos, planos de aula e grupos de discussão para que qualquer pessoa, desde iniciantes até usuários avançados, possa aprender a fazer mais com o WordPress. Aprender a usar, construir e colaborar para o WordPress é essencial para quem quer mergulhar mais fundo no programa [&#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:13:\"Andre Ribeiro\";s: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:9452:\"\n<p><a href=\"https://learn.wordpress.org/\">Learn WordPress</a> é um espaço de aprendizagem que oferece workshops, quizzes, cursos, planos de aula e grupos de discussão para que qualquer pessoa, desde iniciantes até usuários avançados, possa aprender a fazer mais com o WordPress. Aprender a usar, construir e colaborar para o WordPress é essencial para quem quer mergulhar mais fundo no programa e em sua comunidade.</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 has-white-color has-text-color has-background\" href=\"https://learn.wordpress.org/\" style=\"border-radius:5px;background-color:#0085ba\">Learn WordPress</a></div>\n</div>\n\n\n\n<p>Essa iniciativa entre equipes faz parte da rede&nbsp;WordPress.org&nbsp;e apresenta conteúdo de colaboradores da comunidade global. Ele será atualizado semanalmente e ajudará a conectar novos usuários do WordPress com a sua imensa comunidade enquanto aprendem.</p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><a href=\"https://br.wordpress.org/files/2020/12/learn-link-preview.png\"><img loading=\"lazy\" width=\"1024\" height=\"537\" src=\"https://br.wordpress.org/files/2020/12/learn-link-preview-1024x537.png\" alt=\"\" class=\"wp-image-2168\" srcset=\"https://br.wordpress.org/files/2020/12/learn-link-preview-1024x537.png 1024w, https://br.wordpress.org/files/2020/12/learn-link-preview-300x157.png 300w, https://br.wordpress.org/files/2020/12/learn-link-preview-768x403.png 768w, https://br.wordpress.org/files/2020/12/learn-link-preview-1536x806.png 1536w, https://br.wordpress.org/files/2020/12/learn-link-preview.png 1700w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></a></figure></div>\n\n\n\n<h2>O que você pode aprender sobre o WordPress?</h2>\n\n\n\n<p>No Learn WordPress você pode encontrar uma variedade de materiais e oportunidades para usar no momento em que lhe for conveniente.</p>\n\n\n\n<p><a href=\"https://learn.wordpress.org/workshops/\">Workshops</a> são vídeos práticos e baseados em habilidades que mostram aos espectadores como fazer coisas novas com o WordPress, se você publica, gerencia, desenvolve ou colabora para o WordPress. A maioria das oficinas incluem quizzes para você testar seus conhecimentos recém-adquiridos.</p>\n\n\n\n<p>Os <a href=\"https://learn.wordpress.org/discussion-groups/\">grupos de discussão</a> oferecem uma oportunidade de maior aprendizado colaborativo com os participantes reunidos para discutir o conteúdo do workshop – eles ocorrem online, seja em chamadas de vídeo ou no Slack e acomodam todos os fusos horários.</p>\n\n\n\n<p>Os <a href=\"https://learn.wordpress.org/lesson-plans/\">planos de aula</a> são guias para os facilitadores usarem enquanto se apresentam em eventos ou em ambientes educacionais. Os facilitadores encontrarão objetivos de aprendizagem (dizendo às pessoas o que elas vão aprender), quaisquer habilidades pré-requisitos, ativos como capturas de tela e apresentações de slides e avaliações de aprendizagem.</p>\n\n\n\n<p>Os <a href=\"https://learn.wordpress.org/courses/\">cursos</a> são uma série de planos de aula interconectados a serem apresentados por um facilitador que se concentrará estrategicamente nos resultados de aprendizagem definidos. Os participantes podem passar por esses cursos individualmente ou como parte de um grupo. Após completar o aprendizado, os participantes devem ser capazes de aplicar suas habilidades no mundo real.</p>\n\n\n\n<p>Além da riqueza de conteúdo valioso disponível no Learn WordPress, a plataforma oferece uma oportunidade para os indivíduos aprenderem ao lado de outros membros da comunidade e se conectarem com uma rede global de usuários, desenvolvedores e colaboradores do WordPress.</p>\n\n\n\n<figure class=\"wp-block-embed aligncenter 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=\'612\' height=\'345\' src=\'https://www.youtube.com/embed/vYH0GrbQ5QM?version=3&#038;rel=1&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;fs=1&#038;hl=pt-BR&#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><figcaption><a href=\"https://www.youtube.com/playlist?list=PLCVEqsAbLffeEXhn9T1yBVTMaHIMtlzFj\">Por que você deve usar o Learn WordPress?</a>&nbsp;– vídeos da nossa comunidade.</figcaption></figure>\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 has-white-color has-text-color has-background\" href=\"https://learn.wordpress.org/\" style=\"border-radius:5px;background-color:#0085ba\">Comece a aprender hoje!</a></div>\n</div>\n\n\n\n<p>Learn WordPress é uma plataforma de código aberto disponível para qualquer pessoa colaborar com conteúdo em quaisquer áreas mencionadas acima. <a href=\"https://learn.wordpress.org/contribute/\">Saiba mais sobre como você pode se envolver</a> com essa iniciativa.</p>\n\n\n\n<p><a href=\"https://make.wordpress.org/marketing/2020/12/09/help-us-promote-learn-wordpress/\">Participe de nossas divertidas campanhas</a> de promoção nas redes sociais e com sua comunidade local.</p>\n\n\n\n<p>Centenas de pessoas que se estendem por vários anos colaboraram para o desenvolvimento de materiais didáticos. Agradecemos a todos que trabalharam tanto para tornar o Learn WordPress uma realidade.</p>\n\n\n\n<p>É importante destacar que atualmente o Learn WordPress está disponível apenas em inglês. Isso acontece principalmente por se tratar de algo ainda novo precisando de amadurecimento e evolução dentro da comunidade. O objetivo é certamente ter materiais disponível em diversos idiomas e você pode se engajar para participar disso <a href=\"https://br.wordpress.org/team/handbook/comunidade-no-slack/\">dentro da nossa comunidade local no Slack</a> para contribuir com conteúdo em português.</p>\n\n\n\n<h3>Agradecimentos especiais para:</h3>\n\n\n\n<p><strong><em>Treinamento:</em></strong><em>&nbsp;<a href=\"https://profiles.wordpress.org/courane01/\">@courane01</a>,&nbsp;<a href=\"https://profiles.wordpress.org/azhiyadev/\">@azhiyadev</a>,&nbsp;<a href=\"https://profiles.wordpress.org/geheren/\">@geheren</a>,&nbsp;<a href=\"https://profiles.wordpress.org/webtechpooja/\">@webtechpooja</a>,&nbsp;<a href=\"https://profiles.wordpress.org/jessecowens/\">@jessecowens</a>,&nbsp;<a href=\"https://profiles.wordpress.org/onealtr/\">@onealtr</a>,&nbsp;<a href=\"https://profiles.wordpress.org/rastaban/\">@rastaban</a>,&nbsp;<a href=\"https://profiles.wordpress.org/evarlese/\">@evarlese</a>,&nbsp;<a href=\"https://profiles.wordpress.org/manzwebdesigns/\">@manzwebdesigns</a></em><br><strong><em>Meta:&nbsp;</em></strong><em><a href=\"https://profiles.wordpress.org/coreymckrill/\">@coreymckrill</a>,&nbsp;<a href=\"https://profiles.wordpress.org/dufresnesteven/\">@dufresnesteven</a>,&nbsp;<em><a href=\"https://profiles.wordpress.org/jonoaldersonwp/\">@jonoaldersonwp</a></em></em><br><strong><em>Comunidade:</em></strong><em>&nbsp;<a href=\"https://profiles.wordpress.org/hlashbrooke/\">@hlashbrooke</a>,&nbsp;<a href=\"https://profiles.wordpress.org/camikaos/\">@camikaos</a>,&nbsp;<a href=\"https://profiles.wordpress.org/harishanker/\">@harishanker</a>,&nbsp;<a href=\"https://profiles.wordpress.org/angelasjin/\">@angelasjin</a>,&nbsp;<a href=\"https://profiles.wordpress.org/nao/\">@nao</a>,&nbsp;<a href=\"https://profiles.wordpress.org/courtneypk/\">@courtneypk</a>,&nbsp;<a href=\"https://profiles.wordpress.org/andreamiddleton/\">@andreamiddleton</a>,&nbsp;<a href=\"https://profiles.wordpress.org/rmarks/\">@rmarks</a>,&nbsp;<a href=\"https://profiles.wordpress.org/sippis/\">@sippis</a></em><br><strong><em>Marketing:&nbsp;</em></strong><em><a href=\"https://profiles.wordpress.org/webcommsat/\">@webcommsat</a>,&nbsp;&nbsp;<a href=\"https://profiles.wordpress.org/oglekler/\">@oglekler</a>,&nbsp;<a href=\"https://profiles.wordpress.org/lmurillom/\">@lmurillom</a>,&nbsp;<a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld</a>,&nbsp;<a href=\"https://profiles.wordpress.org/meher/\">@meher</a>,&nbsp;<a href=\"https://profiles.wordpress.org/nalininonstopnewsuk/\">@nalininonstopnewsuk</a>,&nbsp;<a href=\"https://profiles.wordpress.org/megphillips91/\">@megphillips91</a>,&nbsp;<a href=\"https://profiles.wordpress.org/marks99/\">@marks99</a>,&nbsp;<em><a href=\"https://profiles.wordpress.org/marybaum/\">@marybaum</a></em></em>,&nbsp;<em><a href=\"https://profiles.wordpress.org/antialiasfactory/\">@antialiasfactory</a>,&nbsp;<a href=\"https://profiles.wordpress.org/herculespekkas/\">@herculespekkas</a>,&nbsp;<a href=\"https://profiles.wordpress.org/chaion07/\">@chaion07</a></em><br><strong><em>Design:</em></strong><em>&nbsp;<a href=\"https://profiles.wordpress.org/melchoyce/\">@melchoyce</a>&nbsp;</em></p>\n\n\n\n<p>Para obter uma lista mais completa dos colaboradores envolvidos nos treinamentos e no Learn WordPress, visite a <a href=\"https://make.wordpress.org/community/2020/08/12/learn-wordpress-is-live/\">publicação inicial de lançamento beta</a>. Agradecemos a todos que estiveram envolvidos até agora e estarão no futuro.</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:\"\";}}}}}i:1;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:3:{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:57:\"https://br.wordpress.org/2020/12/09/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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 09 Dec 2020 10:26:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:32:\"https://br.wordpress.org/?p=2142\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:381:\"Conheça Simone, nosso melhor e mais recente lançamento do WordPress. Nomeado em homenagem à lendária artista Nina Simone, conhecida por músicas como “Feeling Good”, “Young, Gifted and Black” e “Four Women”. Abra uma lista de reprodução com suas melhores músicas e continue lendo para descobrir o que temos reservado para você. O WordPress 5.6 oferece [&#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:13:\"Andre Ribeiro\";s: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:61638:\"\n<p id=\"tw-target-text\">Conheça Simone, nosso melhor e mais recente lançamento do WordPress. Nomeado em homenagem à lendária artista Nina Simone, conhecida por músicas como “Feeling Good”, “Young, Gifted and Black” e “Four Women”. Abra uma lista de reprodução com suas melhores músicas e continue lendo para descobrir o que temos reservado para você.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y.jpg\"><img loading=\"lazy\" width=\"1022\" height=\"1024\" src=\"https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y-1022x1024.jpg\" alt=\"\" class=\"wp-image-2143\" srcset=\"https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y-1022x1024.jpg 1022w, https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y-300x300.jpg 300w, https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y-150x150.jpg 150w, https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y-768x769.jpg 768w, https://br.wordpress.org/files/2020/12/wordpress-5-6_cover-a11y.jpg 1264w\" sizes=\"(max-width: 1022px) 100vw, 1022px\" /></a></figure>\n\n\n\n<div class=\"wp-block-cover has-background-dim\" style=\"background-color:#d1e4dd\"><div class=\"wp-block-cover__inner-container\">\n<p class=\"has-text-align-center has-black-color has-text-color has-large-font-size\">Boas-vindas ao WordPress 5.6</p>\n\n\n\n<p class=\"has-text-align-center has-black-color has-text-color\" id=\"tw-target-text\">Compartilhar suas histórias nunca foi tão fácil.</p>\n</div></div>\n\n\n\n<p>O WordPress 5.6 oferece inúmeras maneiras de libertar suas ideias e torná-las realidade. Com um novo tema padrão como tela, ele oferece suporte a uma coleção cada vez maior de blocos como pincéis. Pinte com palavras. Fotos. Som. Ou mídia.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://br.wordpress.org/files/2020/12/WordPress5-6-1.jpeg\"><img loading=\"lazy\" width=\"1024\" height=\"379\" src=\"https://br.wordpress.org/files/2020/12/WordPress5-6-1-1024x379.jpeg\" alt=\"\" class=\"wp-image-2144\" srcset=\"https://br.wordpress.org/files/2020/12/WordPress5-6-1-1024x379.jpeg 1024w, https://br.wordpress.org/files/2020/12/WordPress5-6-1-300x111.jpeg 300w, https://br.wordpress.org/files/2020/12/WordPress5-6-1-768x284.jpeg 768w, https://br.wordpress.org/files/2020/12/WordPress5-6-1.jpeg 1264w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></a></figure>\n\n\n\n<h3>Maior flexibilidade no visual do seu site</h3>\n\n\n\n<p>Dê vida às suas histórias com mais ferramentas que permitem editar o visual do seu site com ou sem código. Blocos de coluna única, designs usando diferentes colunas e larguras, cabeçalhos ocupando toda a largura da tela e vídeos no bloco de cobertura. Faça pequenas alterações ou grandes declarações com a mesma facilidade!</p>\n\n\n\n<h3>Mais padrões de blocos</h3>\n\n\n\n<p>Em temas selecionados, os padrões de bloco pré-configurados facilitam a configuração de padrões de páginas em seu site. Encontre o poder dos padrões para agilizar seu fluxo de trabalho ou compartilhe um pouco desse poder com seus clientes e economize alguns cliques.</p>\n\n\n\n<h3>Envie legendas de vídeo diretamente no editor de bloco</h3>\n\n\n\n<p>Para ajudar você a adicionar subtítulos ou legendas para seus vídeos, você pode agora enviá-los dentro de seu post ou página. Isso facilita mais do que nunca tornar seus vídeos acessíveis para qualquer um que precise ou prefira usar legendas.</p>\n\n\n\n<h3>O Twenty Twenty-One está aqui!</h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed.png\"><img loading=\"lazy\" width=\"907\" height=\"1024\" src=\"https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed-907x1024.png\" alt=\"\" class=\"wp-image-2145\" srcset=\"https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed-907x1024.png 907w, https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed-266x300.png 266w, https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed-768x867.png 768w, https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed-1360x1536.png 1360w, https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed-1814x2048.png 1814w, https://br.wordpress.org/files/2020/12/TT1-Screenshots-Compressed.png 1975w\" sizes=\"(max-width: 907px) 100vw, 907px\" /></a></figure>\n\n\n\n<p>O Twenty Twenty-One é uma tela em branco para suas ideias, e o editor de blocos é o melhor pincel. É construído para o editor de bloco e embalado com novos padrões de bloco que você só pode obter nos temas padrão. Experimente visuais diferentes em questão de segundos e deixe que o design atraente, mas atemporal do tema, faça o seu trabalho brilhar.</p>\n\n\n\n<p>Além disso, este tema padrão foi feito para dar mais acessibilidade para o seu site. Ele segue as <a href=\"https://make.wordpress.org/themes/handbook/review/accessibility/\">diretrizes de acessibilidade do WordPress</a>, bem como vários outros padrões especializados da <a href=\"https://www.w3.org/WAI/WCAG2AAA-Conformance\">Diretrizes de Acessibilidade para Conteúdo Web (WCAG) 2.1 no nível AAA</a>. Tenha o mais alto nível de padrão internacional de acessibilidade, criando conteúdo acessível e escolhendo plugins também acessíveis!</p>\n\n\n\n<h3>Um arco-íris de tons pastéis suaves</h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow.png\"><img loading=\"lazy\" width=\"1024\" height=\"270\" src=\"https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow-1024x270.png\" alt=\"\" class=\"wp-image-2146\" srcset=\"https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow-1024x270.png 1024w, https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow-300x79.png 300w, https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow-768x202.png 768w, https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow-1536x405.png 1536w, https://br.wordpress.org/files/2020/12/twentytwentyone-rainbow-2048x540.png 2048w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></a></figure>\n\n\n\n<p>Perfeito para um novo ano, o Twenty Twenty-One (2021) oferece uma gama de paletas de cores em tons pastéis pré-definidas, todas atendendo aos padrões AAA para contraste. Você também pode escolher sua própria cor de fundo para o tema, e o tema escolhe para você as cores de texto com acessibilidade — automaticamente!</p>\n\n\n\n<p>Precisa de mais flexibilidade? Você também pode escolher sua própria paleta no seletor cores.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://br.wordpress.org/files/2020/12/WordPress5-6-3.jpeg\"><img loading=\"lazy\" width=\"1024\" height=\"245\" src=\"https://br.wordpress.org/files/2020/12/WordPress5-6-3-1024x245.jpeg\" alt=\"\" class=\"wp-image-2147\" srcset=\"https://br.wordpress.org/files/2020/12/WordPress5-6-3-1024x245.jpeg 1024w, https://br.wordpress.org/files/2020/12/WordPress5-6-3-300x72.jpeg 300w, https://br.wordpress.org/files/2020/12/WordPress5-6-3-768x183.jpeg 768w, https://br.wordpress.org/files/2020/12/WordPress5-6-3.jpeg 1264w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></a></figure>\n\n\n\n<h3>Melhorias para todos</h3>\n\n\n\n<h3>Expandindo atualizações automáticas</h3>\n\n\n\n<p>Por anos, apenas desenvolvedores foram capazes de atualizar o WordPress automaticamente. Mas agora, você tem essa opção, direto no seu painel. Se este é seu primeiro site, você tem atualizações automáticas prontas para começar, agora mesmo! Atualizando um site existente? Sem problemas! Tudo está igual a antes.</p>\n\n\n\n<h3>Modelo de declaração de acessibilidade</h3>\n\n\n\n<p>Mesmo se você não for um especialista, pode começar a contar às pessoas sobre o compromisso do seu site com acessibilidade com o clique de um botão! Este novo <a href=\"https://github.com/10degrees/accessibility-statement-plugin\">plugin</a> inclui um modelo que você pode atualizar e publicar, e foi escrito para oferecer suporte a diferentes contextos e jurisdições.</p>\n\n\n\n<h3>Padrões integrados</h3>\n\n\n\n<p>Se você ainda não teve a chance de brincar com os padrões de bloco, todos os temas padrão agora apresentam uma variedade de padrões de bloco que permitem criar visuais complexos com o mínimo de esforço. Personalize os padrões ao seu gosto com o texto, imagens e cores que se adaptam à sua mensagem ou marca.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><a href=\"https://br.wordpress.org/files/2020/12/WordPress-5-6-4.jpeg\"><img loading=\"lazy\" width=\"1024\" height=\"300\" src=\"https://br.wordpress.org/files/2020/12/WordPress-5-6-4-1024x300.jpeg\" alt=\"\" class=\"wp-image-2148\" srcset=\"https://br.wordpress.org/files/2020/12/WordPress-5-6-4-1024x300.jpeg 1024w, https://br.wordpress.org/files/2020/12/WordPress-5-6-4-300x88.jpeg 300w, https://br.wordpress.org/files/2020/12/WordPress-5-6-4-768x225.jpeg 768w, https://br.wordpress.org/files/2020/12/WordPress-5-6-4.jpeg 1264w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></a></figure>\n\n\n\n<h3>Para desenvolvedores</h3>\n\n\n\n<h3>Autenticação da API REST com senhas de aplicação</h3>\n\n\n\n<p>Graças ao novo recurso de senhas de autorização de aplicação da API, aplicativos de terceiros podem se conectar ao seu site de forma contínua e segura. Este novo recurso da API REST permite que você veja quais aplicativos estão se conectando ao seu site e controle o que eles fazem.</p>\n\n\n\n<h3>Mais suporte para o PHP 8</h3>\n\n\n\n<p>A versão 5.6 marca os primeiros passos do WordPress em direção ao suporte para o PHP 8. Agora é um ótimo momento para começar a planejar como seus produtos, serviços e sites WordPress podem funcionar com a versão mais recente do PHP. Para mais informações sobre o que esperar em seguida, <a href=\"https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/\">leia a nota para desenvolvedores sobre o PHP 8</a>.</p>\n\n\n\n<h3>jQuery</h3>\n\n\n\n<p>As atualizações do jQuery no WordPress ocorrem em três versões: 5.5, 5.6 e 5.7. Conforme avançamos neste processo, execute o <a href=\"https://wordpress.org/plugins/wp-jquery-update-test/\">plugin de teste de atualização</a> para verificar se há erros em seus site com antecedência.</p>\n\n\n\n<p>Se você encontrar problemas na aparência de seu site como, por exemplo, um carrossel ou um botão que não funcionam (esse tipo de coisa), instale o <a href=\"https://wordpress.org/plugins/enable-jquery-migrate-helper/\">plugin jQuery Migrate</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h3>Consulte o guia final para mais informações!</h3>\n\n\n\n<p>Confira a versão mais recente do <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">guia final do WordPress 5.6</a>. Ele destaca as notas para desenvolvedores para cada mudança que você deseja conhecer.</p>\n\n\n\n<div class=\"wp-block-cover has-background-dim\" style=\"background-color:#d1e4dd\"><div class=\"wp-block-cover__inner-container\">\n<p class=\"has-text-align-center has-black-color has-text-color has-large-font-size\" id=\"tw-target-text\">&#8220;It’s a new day, it’s a new life for me…. and I’m feeling good.&#8221;</p>\n\n\n\n<p class=\"has-text-align-center has-black-color has-text-color\" id=\"tw-target-text\">~Nina Simone</p>\n</div></div>\n\n\n\n<h3>O esquadrão</h3>\n\n\n\n<p>O WordPress 5.6 chega até você através de um equipe composta exclusivamente por mulheres:</p>\n\n\n\n<ul><li><strong>Líder da versão:</strong> Josepha Haden (<a href=\"https://profiles.wordpress.org/chanthaboune/\">@chanthaboune</a>).  Equipe: Chloé Bringmann (<a href=\"https://profiles.wordpress.org/cbringmann/\">@cbringmann</a>) e Angela Jin (<a href=\"https://profiles.wordpress.org/angelasjin/\">@angelasjin</a>).</li><li><strong>Coordenação da versão:</strong> Dee Teal (<a href=\"https://profiles.wordpress.org/thewebprincess/\">@thewebprincess</a>).  Equipe: Thelma Mutete (<a href=\"https://profiles.wordpress.org/thelmachido/\">@thelmachido</a>) e Laura Nelson (<a href=\"https://profiles.wordpress.org/laurora/\">@laurora</a>).</li><li><strong>Líder de triagem:</strong> Tonya Mork (<a href=\"https://profiles.wordpress.org/hellofromtonya/\">@hellofromtonya</a>). </li><li><strong>Líder Técnica:</strong> Helen Hou-Sandì (<a href=\"https://profiles.wordpress.org/helen/\">@helen</a>).  Equipe: Amy Kamala (<a href=\"https://profiles.wordpress.org/amykamala/\">@amykamala</a>) e Ebonie Butler (<a href=\"https://profiles.wordpress.org/metalandcoffee/\">@metalandcoffee</a>).</li><li><strong>Líder editora técnica:</strong> Isabel Brison (<a href=\"https://profiles.wordpress.org/isabel_brison/\">@isabel_brison</a>).  Equipe: Chandrika Guntur (<a href=\"https://profiles.wordpress.org/cguntur/\">@cguntur</a>), Anchen le Roux (<a href=\"https://profiles.wordpress.org/anchenlr/\">@anchenlr</a>) e Rebecca Hum (<a href=\"https://profiles.wordpress.org/rebasaurus/\">@rebasaurus</a>).</li><li><strong>Líderes de design:</strong> Ellen Bauer (<a href=\"https://profiles.wordpress.org/elmastudio/\">@elmastudio</a>) e Tammie Lister (<a href=\"https://profiles.wordpress.org/karmatosed/\">@karmatosed</a>).  Equipe: 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>), e Sophia DeRosia (<a href=\"https://profiles.wordpress.org/eringoblog/\">@eringoblog</a>).</li><li><strong>Líder de design técnico:</strong> Shital Marakana (<a href=\"https://profiles.wordpress.org/shital-patel/\">@shital-patel</a>).</li><li><strong>Líder de acessibilidade:</strong> Sarah Ricker (<a href=\"https://profiles.wordpress.org/sarahricker/\">@sarahricke<strong>r</strong></a>). Equipe: Hauwa Abashiya (<a href=\"https://profiles.wordpress.org/azhiyadev/\">@azhiyadev</a>).</li><li><strong>Líder de marketing e comunicação:</strong> Abha Thakor (<a href=\"https://profiles.wordpress.org/webcommsat/\">@webcommsat</a>) e Yvette Sonneveld (<a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld</a>). Equipe: 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>) e Afshana Diya (<a href=\"https://profiles.wordpress.org/afshanadiya/\">@afshanadiya</a>).</li><li><strong>Líder de documentação: </strong>Shawntelle Coker (<a href=\"https://profiles.wordpress.org/sncoker/\">@sncoker</a>). Equipe: Daisy Olsen (<a href=\"https://wordpress.slack.com/team/U8D7JFA3X\">@DaisyO</a>), Meher Bala (<a href=\"https://profiles.wordpress.org/meher/\">@meher</a>) e Winstina Hughes (<a href=\"https://profiles.wordpress.org/planningwrite/\">@planningwrite</a>).</li><li><strong>Líder de revisão de documentação:</strong> Michele Butcher-Jones (<a href=\"https://profiles.wordpress.org/m_butcher/\">@m_butcher</a>).  Equipe: Nidhi Jain (<a href=\"https://profiles.wordpress.org/jainnidhi/\">@jainnidhi</a>) e Laura Byrne Cristiano (<a href=\"https://wordpress.org/support/users/newyorkerlaura/\">@newyorkerlaura</a>).</li><li><strong>Líder de design do tema padrão:</strong> Mel Choyce-Dwan (<a href=\"https://profiles.wordpress.org/melchoyce/\">@melchoyce</a>).  Equipe: Ellen Bauer (<a href=\"https://profiles.wordpress.org/elmastudio/\">@elmastudio</a>).</li><li><strong>Líder de desenvolvimento do tema padrão:</strong> Carolina Nymark (<a href=\"https://profiles.wordpress.org/poena/\">@poena</a>).  Equipe: Kelly Choyce-Dwan (<a href=\"https://profiles.wordpress.org/ryelle/\">@ryelle</a>) e Jessica Lyschik (<a href=\"https://profiles.wordpress.org/luminuu/\">@luminuu</a>).</li><li><strong>Curadora do tema padrão:</strong> Jessica Lyschik (<a href=\"https://profiles.wordpress.org/luminuu/\">@luminuu</a>).</li><li><strong>Líder de testes:</strong> Monika Rao (<a href=\"https://profiles.wordpress.org/monikarao/\">@monikarao</a>).  Equipe: Allie Nimmons (<a href=\"https://profiles.wordpress.org/alliennimmons/\">@alliennimmons</a>).</li><li><strong>Líder de suporte:</strong> Bet Hannon (<a href=\"https://profiles.wordpress.org/bethannon1/\">@bethannon1</a>).</li></ul>\n\n\n\n<p>Como sempre, este lançamento reflete o trabalho árduo de 605 generosos colaboradores voluntários. Eles colaboraram em cerca de 350 tíquetes no Trac e mais de 1.000 solicitações de <code>pull request</code> no GitHub.</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/zgrkaralar/\">Özgü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á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é 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/\">Alex Stine</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</a>, <a href=\"https://profiles.wordpress.org/anlino/\">Anders Norén</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 &#8220;Rarst&#8221; 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/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/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</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/bmcdede/\">bmcdede</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/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/\">bridgetwillard</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/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/cpapazoglou/\">cpapazoglou</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ávid Szabó</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 Bajgoric</a>, <a href=\"https://profiles.wordpress.org/nrqsnchz/\">Enrique Sá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 &#8216;Folletto&#8217; Casali</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ä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ół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/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/joelclimbsthings/\">joelclimbsthings</a>, <a href=\"https://profiles.wordpress.org/joelyoder/\">joelyoder</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/\">karthikbhatb</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/laurora/\">Laura Nelson</a>, <a href=\"https://profiles.wordpress.org/laxman-prajapati/\">Laxman Prajapati</a>, <a href=\"https://profiles.wordpress.org/lcyh78/\">lcyh78</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</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/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/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/nosolosw/\">O André</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ç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ö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é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/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 | 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> e <a href=\"https://profiles.wordpress.org/zebulan/\">Zebulan Stanphill</a>.</p>\n\n\n\n<p>Além disso, agradecemos a todos os voluntários da comunidade que contribuem nos <a href=\"https://wordpress.org/support/\">fóruns de suporte</a>. Eles respondem a perguntas de pessoas em todo o mundo, estejam eles usando o WordPress pela primeira vez ou que já o conhecem desde o primeiro lançamento em 2003. Esses lançamentos também são bem-sucedidos por causa de seus esforços!</p>\n\n\n\n<p>Finalmente, agradecemos a todos os tradutores da comunidade que ajudaram a fazer o WordPress 5.6 disponível em 38 idiomas no momento do lançamento. Os tradutores da nossa comunidade estão trabalhando arduamente para garantir que mais idiomas estejam a caminho (70 já são 90%). Se contribuir para o WordPress é do seu interesse, é fácil aprender mais. Confira o <a href=\"https://make.wordpress.org/\">Make do WordPress</a> ou o <a href=\"https://make.wordpress.org/core/\">blog de desenvolvimento do núcleo</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:\"\";}}}}}i:2;a:6:{s:4:\"data\";s:60:\"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{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:70:\"https://br.wordpress.org/2020/12/02/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:\"Wed, 02 Dec 2020 01:06: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:32:\"https://br.wordpress.org/?p=2140\";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:343:\"O segundo release candidate (versão candidata, em tradução livre) do WordPress 5.6 já está disponível! O WordPress 5.6 está programado para lançamento em 8 de dezembro de 2020, e precisamos da sua ajuda para chegar lá — se você ainda não experimentou a versão 5.6, agora é a hora! Você pode testar o release candidate [&#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:13:\"Andre Ribeiro\";s: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:2807:\"\n<p>O segundo <em>release candidate</em> (versão candidata, em tradução livre) do WordPress 5.6 já está disponível!</p>\n\n\n\n<p id=\"tw-target-text\">O WordPress 5.6 está programado para lançamento em<strong> 8 de dezembro de 2020</strong>, e precisamos da sua ajuda para chegar lá — se você ainda não experimentou a versão 5.6, agora é a hora!</p>\n\n\n\n<p id=\"tw-target-text\">Você pode testar o release candidate 2 do WordPress 5.6 de duas maneiras:</p>\n\n\n\n<ul><li>Experimente o plugin <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> (escolha a opção “bleeding edge nightlies”) ou</li><li><a href=\"https://wordpress.org/wordpress-5.6-RC2.zip\">Baixe a versão release candidate aqui</a> (zip).</li></ul>\n\n\n\n<p>Agradecemos a todos os colaboradores que testaram as versões Beta e compartilharam seus comentários. O teste de erros é uma parte importante do aprimoramento de cada versão e uma ótima maneira de contribuir com o WordPress.</p>\n\n\n\n<h2 id=\"tw-target-text\">Desenvolvedores de plugins e temas</h2>\n\n\n\n<p>Teste seus plugins e temas com o WordPress 5.6 e atualize para 5.6 a versão no campo&nbsp;<em>Tested up to</em>&nbsp;do arquivo readme. Se encontrar problemas de compatibilidade, tenha certeza de publicar no&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta/\">fórum</a>&nbsp;para que possamos agir antes do lançamento final.</p>\n\n\n\n<p id=\"tw-target-text\">Para uma análise mais detalhada das mudanças incluídas no WordPress 5.6, confira o a publicação do <a href=\"https://br.wordpress.org/2020/10/21/wordpress-5-6-beta-1/\">WordPress 5.6 Beta 1</a>. O <a href=\"https://make.wordpress.org/core/2020/11/20/wordpress-5-6-field-guide/\">Guia final do WordPress 5.6</a> também foi lançado! É a sua fonte para obter detalhes sobre todas as principais mudanças.</p>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Ajude a tradução em Português!&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev\">Ajude-nos a traduzir o WordPress para o português!</a>&nbsp;O lançamento dessa versão também significa que&nbsp;<a href=\"https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze\">novas strings para a tradução</a>&nbsp;da versão 5.6 serão evitadas.</p>\n\n\n\n<p><em><strong>Se acha que encontrou um erro</strong>, você pode publicá-lo na&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">área Alpha/Beta</a>&nbsp;nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro,&nbsp;<a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar uma&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">lista de erros conhecidos</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:\"\";}}}}}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:3:{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:68:\"https://br.wordpress.org/2020/11/18/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:\"Wed, 18 Nov 2020 00:11:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:32:\"https://br.wordpress.org/?p=2134\";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:374:\"O primeiro release candidate (versão candidata, em tradução livre) do WordPress 5.6 já está disponível! Este é um marco importante no progresso da comunidade em direção ao lançamento final do WordPress 5.6. “Release Candidate” significa que a nova versão está pronta para lançamento, mas com milhões de usuários e milhares de plugins e temas, é [&#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:13:\"Andre Ribeiro\";s: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:3672:\"\n<p id=\"tw-target-text\">O primeiro <em>release candidate</em> (versão candidata, em tradução livre) do WordPress 5.6 já está disponível!</p>\n\n\n\n<p id=\"tw-target-text\">Este é um marco importante no progresso da comunidade em direção ao lançamento final do WordPress 5.6.</p>\n\n\n\n<p id=\"tw-target-text\">“Release Candidate” significa que a nova versão está pronta para lançamento, mas com milhões de usuários e milhares de plugins e temas, é possível que algo tenha sido esquecido. O WordPress 5.6 está programado para lançamento em <strong>8 de dezembro de 2020</strong>, mas precisamos da sua ajuda para que isso aconteca. Se você ainda não testou a versão 5.6, <strong>a hora é essa</strong>!</p>\n\n\n\n<p>Existem duas formas de testar o WordPress 5.6 release candidate:</p>\n\n\n\n<ul><li>Experimente o plugin <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> (escolha a opção “bleeding edge nightlies” em conjunto com &#8220;Beta/RC Only&#8221;) ou</li><li><a href=\"https://wordpress.org/wordpress-5.6-RC1.zip\">Baixe a versão release candidate aqui</a> (zip).</li></ul>\n\n\n\n<p>Agradecemos a todos os colaboradores que testaram as versões Beta e compartilharam seus comentários. O teste de erros é uma parte importante do aprimoramento de cada versão e uma ótima maneira de contribuir com o WordPress.</p>\n\n\n\n<h2>O que há de novo no WordPress 5.6?</h2>\n\n\n\n<p id=\"tw-target-text\">O lançamento final de 2020 continua a tradição anual de um novo tema padrão que é personalizado para mostrar os novos recursos e funcionalidades da versão. O progresso contínuo no editor de blocos é especialmente claro nesta versão, que traz mais blocos para mais lugares e menos cliques para implementar suas páginas.</p>\n\n\n\n<p id=\"tw-target-text\">O WordPress 5.6 possui muitas novidades para aprimorar a experiência do desenvolvedor. Para acompanhar, assine o <a href=\"https://make.wordpress.org/core/\">blog do Core do WordPress</a> e fique atento especialmente às <a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">notas dos desenvolvedor</a> para obter atualizações sobre essas e outras alterações que podem afetar seus produtos.</p>\n\n\n\n<h2 id=\"tw-target-text\">Desenvolvedores de plugins e temas</h2>\n\n\n\n<p>Teste seus plugins e temas com o WordPress 5.6 e atualize para 5.6 a versão no campo <em>Tested up to</em> do arquivo readme. Se encontrar problemas de compatibilidade, tenha certeza de publicar no <a href=\"https://wordpress.org/support/forum/alphabeta/\">fórum</a> para que possamos agir antes do lançamento final.</p>\n\n\n\n<p>O guia final do WordPress 5.6 será publicado em breve e irá fornecer dados mais detalhados sobre as principais mudanças.</p>\n\n\n\n<h2>Como ajudar</h2>\n\n\n\n<p>Ajude a tradução em Português! <a href=\"https://translate.wordpress.org/projects/wp/dev\">Ajude-nos a traduzir o WordPress para o português!</a> O lançamento dessa versão também significa que <a href=\"https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze\">novas strings para a tradução</a> da versão 5.6 serão evitadas.</p>\n\n\n\n<p><em><strong>Se acha que encontrou um erro</strong>, você pode publicá-lo na <a href=\"https://wordpress.org/support/forum/alphabeta\">área Alpha/Beta</a> nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro, <a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar uma <a href=\"https://core.trac.wordpress.org/tickets/major\">lista de erros conhecidos</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:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:60:\"\n		\n		\n		\n		\n		\n				\n		\n		\n\n					\n										\n					\n		\n		\n			\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:3:{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:57:\"https://br.wordpress.org/2020/11/13/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:\"Fri, 13 Nov 2020 11:39:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:32:\"https://br.wordpress.org/?p=2119\";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:358:\"O WordPress 5.6 Beta 4 já está disponível para teste! Esta versão ainda está em desenvolvimento, portanto, recomendamos que você execute esta versão em um site de teste. Você pode testar o WordPress 5.6 Beta de duas maneiras: Experimente o plugin WordPress Beta Tester (escolha a opção “bleeding edge nightlies”). Ou baixe o Beta aqui [&#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:13:\"Andre Ribeiro\";s: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:6187:\"\n<p id=\"tw-target-text\">O WordPress 5.6 Beta 4 já está disponível para teste!</p>\n\n\n\n<p><strong><strong>Esta versão ainda está em desenvolvimento</strong>,</strong> portanto, recomendamos que você execute esta versão em um site de teste.</p>\n\n\n\n<p>Você pode testar o WordPress 5.6 Beta de duas maneiras:</p>\n\n\n\n<ul><li>Experimente o plugin <a href=\"https://wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> (escolha a opção “bleeding edge nightlies”).</li><li>Ou <a href=\"https://wordpress.org/wordpress-5.6-beta4.zip\">baixe o Beta aqui (zip)</a> .</li></ul>\n\n\n\n<p>A meta atual para o lançamento final é 8 de dezembro de 2020. Faltam pouco mais de <strong>três semanas</strong>, então, contamos com a sua ajuda para garantir que este lançamento seja adequadamente testado.</p>\n\n\n\n<p>Agradecemos a todos que contribuiram testando a versão de  desenvolvimento <a href=\"https://wordpress.org/news/2020/11/wordpress-5-6-beta-3/\">Beta 3 (em inglês)</a> e compartilharam seus comentários. O teste de erros é uma parte importante do aprimoramento de cada versão e uma ótima maneira de contribuir com o WordPress.</p>\n\n\n\n<h2><strong>Alguns destaques</strong></h2>\n\n\n\n<p>Desde a versão 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 erros</a> foram corrigidos. Aqui está um resumo de algumas alterações incluídas na versão Beta 4:</p>\n\n\n\n<ul><li>Houve uma mudança na implementação de atualizações automáticas para novas instalações do programa (<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/\">Próximas etapas</a> e a <a href=\"https://make.wordpress.org/core/2020/11/10/wp5-6-auto-update-implementation-change/\">justificativa</a> estão disponíveis.</em></li><li>Adicionado melhor tratamento de valores inesperados na integridade do site (<a href=\"https://core.trac.wordpress.org/ticket/50145\">#50145</a>).</li><li>Adicionada uma maneira dos desenvolvedores filtrarem a lista de autores disponíveis na edição rápida (<a href=\"https://core.trac.wordpress.org/ticket/47685\">#47685</a>).</li><li>Manipulação mais acessível do widget de nuvem de tags (<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\">Várias melhorias no componente de mídia</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\">Várias melhorias no componente Build / Test Tools</a>.</li></ul>\n\n\n\n<p><em>Para ver todos os recursos de cada versão do Gutenberg em detalhes, visite os links das versões:&nbsp;<em>&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>,&nbsp;<a href=\"https://make.wordpress.org/core/2020/10/21/whats-new-in-gutenberg-21-october/\">9.2</a> e <a href=\"https://github.com/WordPress/gutenberg/releases/tag/v9.3.0-rc.1\">9.3</a>.</em></em></p>\n\n\n\n<h3>Notas para desenvolvedores</h3>\n\n\n\n<p id=\"block-c706675c-5a17-48a0-9fd8-5aa5703cb735\">O WordPress 5.6 também traz muitas melhorias para experiência de desenvolvimento. Fique de olho no&nbsp;<a href=\"https://make.wordpress.org/core/\">blog do núcleo do WordPress</a>&nbsp;para&nbsp;<a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">acompanhar as notas de desenvolvimento da versão 5.6</a>&nbsp;nas próximas semanas, detalhando essas e outras alterações.</p>\n\n\n\n<h3 id=\"block-37ee7e87-d852-40f7-9657-90d42a3879dc\">Como ajudar</h3>\n\n\n\n<p id=\"block-ab1acb90-0f9f-4424-a058-3cc22d9d1662\">Ajude a tradução em Português!&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a></p>\n\n\n\n<p id=\"block-97acd446-e0d0-4142-9442-15f4174e2e66\"><strong>Se acha que encontrou um erro</strong>, você pode publicá-lo na&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">área Alpha/Beta</a>&nbsp;nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro,&nbsp;<a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar uma&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">lista de erros conhecidos</a>.</p>\n\n\n\n<p><em>Agradecimentos especiais para @tonyamork, <a href=\'https://profiles.wordpress.org/audrasjb/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>audrasjb</a> pelas notas técnicas e <a href=\'https://profiles.wordpress.org/angelasjin/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>angelasjin</a>, <a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld </a>,&nbsp; <a href=\"https://profiles.wordpress.org/cguntur/\">@cguntur</a> , <a href=\"https://profiles.wordpress.org/cbringmann/\">@ cbringmann</a> pela revisão final.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s: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:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"WordPress 5.5.3 – Atualização de manutenção\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://br.wordpress.org/2020/10/31/wordpress-5-5-3-atualizacao-de-manutencao/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 31 Oct 2020 12:56:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://br.wordpress.org/?p=2110\";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:361:\"O WordPress 5.5.3 já está disponível. Esta versão de manutenção corrige um problema introduzido no WordPress 5.5.2 que torna impossível instalar o WordPress em um site totalmente novo que não tenha uma conexão de banco de dados configurada. Esta versão não afeta sites onde uma conexão de banco de dados já está configurada, por exemplo, [&#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:13:\"Andre Ribeiro\";s: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:3418:\"\n<p>O WordPress 5.5.3 já está disponível.</p>\n\n\n\n<p>Esta versão de manutenção corrige um problema introduzido no WordPress 5.5.2 que torna impossível instalar o WordPress em um site totalmente novo que não tenha uma conexão de banco de dados configurada. Esta versão não afeta sites onde uma conexão de banco de dados já está configurada, por exemplo, por meio de instaladores de um clique ou um arquivo <code>wp-config.php</code> existente.</p>\n\n\n\n<h2>Problema com a versão 5.5.3-alpha</h2>\n\n\n\n<p id=\"tw-target-text\">Anteriormente &#8211; entre aproximadamente 12:30 e 13:00 (horário de Brasília) do dia 30/10/2020 &#8211; o sistema de atualização automática para WordPress atualizou alguns sites da versão 5.5.2 para a versão 5.5.3-alpha. Esta atualização automática foi devido a um erro na API de atualizações causado pelos preparativos da versão 5.5.3 (veja mais aqui). A versão 5.5.3-alpha neste ponto era funcionalmente idêntica à 5.5.2, pois nenhum trabalho de desenvolvimento havia sido iniciado no 5.5.3. No entanto, as seguintes alterações podem ter sido feitas em seu site:</p>\n\n\n\n<ul><li>Instalado o tema padrão &#8220;Twenty Twenty&#8221; como parte do pacote de pré-lançamento.</li><li>Instalado o plugin &#8220;Akismet&#8221; como parte do pacote de pré-lançamento.</li></ul>\n\n\n\n<p>Este tema e plugin não foram ativados e, portanto, permanecem não funcionais, a menos que você os tenha instalado anteriormente. É seguro excluir esses recursos, caso você prefira não usá-los.</p>\n\n\n\n<p id=\"tw-target-text\">Se você não estiver usando a versão 5.5.2 ou tiver as atualizações automáticas para versões menores desativadas, atualize manualmente para a versão 5.5.3 baixando o WordPress 5.5.3 ou visitando o Painel → Atualizações e clique em “Atualizar agora”.</p>\n\n\n\n<p id=\"tw-target-text\">Para mais detalhes técnicos sobre o problema, postamos em nosso <a href=\"https://make.wordpress.org/core/2020/10/30/wordpress-5-5-3-release-some-technical-details/\">blog de desenvolvimento do core</a>.</p>\n\n\n\n<h2>Agradecimentos</h2>\n\n\n\n<p>Agradecemos a todos que contribuíram para o lançamento da versão 5.5.3: <a href=\"https://profiles.wordpress.org/audrasjb/\">@audrasjb</a>, <a href=\"https://profiles.wordpress.org/barry/\">@barry</a>, <a href=\"https://profiles.wordpress.org/chanthaboune/\">@chanthaboune</a>, <a href=\"https://profiles.wordpress.org/cbringmann/\">@cbringmann</a>, <a href=\"https://profiles.wordpress.org/clorith/\">@clorith</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">@davidbaumwald</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">@desrosj</a>, <a href=\"https://profiles.wordpress.org/hellofromtonya/\">@hellofromtonya</a>, <a href=\"https://profiles.wordpress.org/jeffpaul/\">@jeffpaul</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">@johnbillion</a>, <a href=\"https://profiles.wordpress.org/garubi/\">@garubi</a>, <a href=\"https://profiles.wordpress.org/metalandcoffee/\">@metalandcoffee</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">@mukesh27</a>, <a href=\"https://profiles.wordpress.org/otto42/\">@otto42</a>, <a href=\"https://profiles.wordpress.org/punitsoftac/\">@punitsoftac</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\">@sergeybiryukov</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\">@whyisjake</a> e <a href=\"https://profiles.wordpress.org/xknown/\">@xknown</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:\"\";}}}}}i:6;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:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"WordPress 5.5.2 – Atualização de segurança e manutenção\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://br.wordpress.org/2020/10/30/wordpress-5-5-2-atualizacao-de-seguranca-e-manutencao/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 30 Oct 2020 01:36:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://br.wordpress.org/?p=2101\";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:377:\"O WordPress 5.5.2 já está disponível! Esta versão de segurança e manutenção apresenta 14 correções de erros, além de 10 correções de segurança. Como esta é uma atualização de segurança, é recomendável que você atualize seus sites imediatamente. Todas as versões desde o WordPress 3.7 também foram atualizadas. O WordPress 5.5.2 é uma versão de [&#8230;]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Andre Ribeiro\";s: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:7752:\"\n<p>O WordPress 5.5.2 já está disponível!</p>\n\n\n\n<p id=\"tw-target-text\">Esta versão de segurança e manutenção apresenta <a href=\"https://core.trac.wordpress.org/query?milestone=5.4.1&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priorityhttps://core.trac.wordpress.org/query?milestone=5.5.2&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">14 correções de erros</a>, além de 10 correções de segurança. Como esta é uma <strong>atualização de segurança</strong>, é recomendável que você atualize seus sites imediatamente. Todas as versões desde o WordPress 3.7 também foram atualizadas.</p>\n\n\n\n<p id=\"tw-target-text\">O WordPress 5.5.2 é uma versão de segurança e manutenção de ciclo curto. O próximo lançamento principal será a versão 5.6.</p>\n\n\n\n<p id=\"tw-target-text\">Você pode baixar o WordPress 5.5.2 em WordPress.org ou visite seu Painel → Atualizações e clique em Atualizar agora.</p>\n\n\n\n<p id=\"tw-target-text\">Se você tiver sites que suportam atualizações automáticas em segundo plano, eles já iniciaram o processo de atualização.</p>\n\n\n\n<h3>Atualizações de segurança</h3>\n\n\n\n<p id=\"tw-target-text\">Sete problemas de segurança afetam as versões 5.5 e anteriores do WordPress. Se você ainda não atualizou para a 5.5, todas as versões do WordPress desde 3.7 também foram atualizadas para corrigir os seguintes problemas de segurança:</p>\n\n\n\n<ul><li>Agradecemos a Alex Concha da equipe de segurança do WordPress por seu trabalho no reforço de solicitações de desserialização.</li><li>Agradecemos a David Binovec por uma correção para desativar a incorporação de spam em sites desativados de uma rede multisite.</li><li>Agradecimentos a Marc Montas, da Sucuri, por relatar um problema que poderia levar ao uso de XSS de variáveis ​​globais.</li><li>Agradecimentos a Justin Tran que relatou um problema em torno do escalonamento de privilégios em XML-RPC. Ele também encontrou e divulgou um problema sobre o escalonamento de privilégios em torno de comentários de postagem via XML-RPC.</li><li>Agradecemos a Omar Ganiev, que relatou um método em que um ataque DoS pode levar ao RCE.</li><li>Agradecimentos a Karim El Ouerghemmi, da RIPS, que divulgou um método para armazenar XSS em pós-slugs.</li><li>Agradecemos a Slavco por relatar, assim como Karim El Ouerghemmi, um método para contornar meta campos protegidos que poderia levar à exclusão arbitrária de arquivos.</li><li>E uma agradecimento especial a <a href=\"https://profiles.wordpress.org/zieladam/\">@zieladam</a>, que foi parte integrante de muitas das correções durante esta versão.</li></ul>\n\n\n\n<p id=\"tw-target-text\">Agradecemos pela divulgação das vulnerabilidades em privado. Isso deu à equipe de segurança tempo para corrigir as vulnerabilidades antes que os sites WordPress pudessem ser atacados.</p>\n\n\n\n<p id=\"tw-target-text\">Para obter mais informações, navegue na <a href=\"https://core.trac.wordpress.org/query?milestone=5.5.2&amp;group=component&amp;col=id&amp;col=summary&amp;col=milestone&amp;col=owner&amp;col=type&amp;col=status&amp;col=priority&amp;order=priority\">lista completa de alterações</a> no Trac ou verifique a <a href=\"https://wordpress.org/support/wordpress-version/version-5-5-2/\">página de documentação do HelpHub da versão 5.5.2</a>.</p>\n\n\n\n<h2>Agradecimentos</h2>\n\n\n\n<p>A versão 5.5.2 foi liderada por&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://profiles.wordpress.org/whyisjake/\">@whyisjake</a>&nbsp;e a pela seguinte equipe do lançamento: &nbsp;<a href=\"https://profiles.wordpress.org/audrasjb/\">@audrasjb</a>,&nbsp;<a href=\"https://profiles.wordpress.org/davidbaumwald/\">@davidbaumwald</a>,&nbsp;<a href=\"https://profiles.wordpress.org/desrosj/\">@desrosj</a>,&nbsp;<a href=\"https://profiles.wordpress.org/johnbillion/\">@johnbillion</a>, <a href=\"https://profile.wordpress.org/metalandcoffee\">@metalandcoffee</a>, <a href=\"https://profiles.wordpress.org/noisysocks\">@noisysocks</a>&nbsp;<a href=\"https://profiles.wordpress.org/planningwrite/\">@planningwrite</a>, <a href=\"https://profiles.wordpress.org/sarahricker/\">@sarahricker</a> e&nbsp;<a href=\"https://profiles.wordpress.org/sergeybiryukov/\">@sergeybiryukov</a>.</p>\n\n\n\n<p id=\"tw-target-text\">Além dos pesquisadores de segurança e membros da equipe de lançamento mencionados acima, agradecemos a todos que ajudaram a fazer o WordPress 5.5.2 acontecer:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/jorbin/\">Aaron Jorbin</a>, <a href=\"https://profiles.wordpress.org/xknown/\">Alex Concha</a>, <a href=\"https://profiles.wordpress.org/wpamitkumar/\">Amit Dudhat</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/ayeshrajans/\">Ayesh Karunaratne</a>, <a href=\"https://profiles.wordpress.org/bridgetwillard/\">bridgetwillard</a>, <a href=\"https://profiles.wordpress.org/talldanwp/\">Daniel Richards</a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\">David Baumwald</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/mista-flo/\">Florian TIAR</a>, <a href=\"https://profiles.wordpress.org/hareesh-pillai/\">Hareesh</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/whyisjake/\">Jake Spurlock</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/johnbillion/\">John Blackbourn</a>, <a href=\"https://profiles.wordpress.org/desrosj/\">Jonathan Desrosiers</a>, <a href=\"https://profiles.wordpress.org/jb510/\">Jon Brown</a>, <a href=\"https://profiles.wordpress.org/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/jrf/\">Juliette Reinders Folmer</a>, <a href=\"https://profiles.wordpress.org/kellybleck/\">kellybleck</a>, <a href=\"https://profiles.wordpress.org/mailnew2ster/\">mailnew2ster</a>, <a href=\"https://profiles.wordpress.org/mkaz/\">Marcus Kazmierczak</a>, <a href=\"https://profiles.wordpress.org/clorith/\">Marius L. J.</a>, <a href=\"https://profiles.wordpress.org/dimadin/\">Milan Dinić</a>, <a href=\"https://profiles.wordpress.org/batmoo/\">Mohammad Jangda</a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/paaljoachim/\">Paal Joachim Romdahl</a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\">Peter Wilson</a>, <a href=\"https://profiles.wordpress.org/regankhadgi/\">Regan Khadgi</a>, <a href=\"https://profiles.wordpress.org/noisysocks/\">Robert Anderson</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/smub/\">Syed Balkhi</a>, <a href=\"https://profiles.wordpress.org/szaqal21/\">szaqal21</a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</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/itowhid06/\">Towhidul I. Chowdhury</a>, <a href=\"https://profiles.wordpress.org/vinayakanivase/\">Vinayak Anivase</a> e <a href=\"https://profiles.wordpress.org/zieladam/\">zieladam</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:\"\";}}}}}i:7;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:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.6 Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2020/10/28/wordpress-5-6-beta-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 28 Oct 2020 12:37:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:32:\"https://br.wordpress.org/?p=2091\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:381:\"O WordPress 5.6 Beta 2 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão. Você pode testar o WordPress 5.6 Beta de duas formas: Usando o plugin&#160;WordPress Beta Tester&#160;(escolha a opção “bleeding edge nightlies”) ou [&#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:13:\"Felipe Santos\";s: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:4703:\"\n<p id=\"block-ff20919b-adab-490c-9d59-dbb924c0ab5a\">O WordPress 5.6 Beta 2 já está disponível!</p>\n\n\n\n<p id=\"block-2d137d3e-7769-41c6-bf93-3cf571fd8c4b\"><strong>Esta versão ainda está em desenvolvimento</strong>, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão.</p>\n\n\n\n<p id=\"block-0115d5c3-51f8-4695-bab3-dd109cb5e9cb\">Você pode testar o WordPress 5.6 Beta de duas formas:</p>\n\n\n\n<ul id=\"block-e7378510-27a4-4ff7-9f52-d1e2f30f473d\"><li>Usando o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(escolha a opção “bleeding edge nightlies”) ou</li><li><a href=\"https://wordpress.org/wordpress-5.6-beta2.zip\">Baixando a versão beta aqui</a>&nbsp;(zip).</li></ul>\n\n\n\n<p id=\"block-951f074c-d2b1-42c4-9cd5-e88c24ef5514\">O lançamento está agendado para <a href=\"https://make.wordpress.org/core/5-6/\">8 de dezembro de 2020</a>, e&nbsp;nós precisamos da sua ajuda para testar da melhor forma possível!</p>\n\n\n\n<p>Agradecemos a quem conseguiu contribuir testando a versão <a href=\"https://br.wordpress.org/2020/10/21/wordpress-5-6-beta-1/\">Beta 1</a> e enviando seus comentários. Testar para encontrar problemas é uma parte importante para aperfeiçoar cada lançamento e uma ótima forma de contribuir para o WordPress.</p>\n\n\n\n<h3 id=\"block-84b85969-b25c-49d1-9aba-583e8451b928\">Alguns destaques</h3>\n\n\n\n<p>Foram corrigidos <a href=\"https://core.trac.wordpress.org/query?status=closed&amp;changetime=10%2F21%2F2020..10%2F27%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\">53 novos</a> erros desde o lançamento do beta 1. Aqui está um resumo de algumas mudanças que fazem parte do beta 2:</p>\n\n\n\n<ul><li>6 problemas adicionais foram corrigidos no editor de blocos (<a href=\"https://github.com/WordPress/gutenberg/pull/26442\">#26442</a>);</li><li>Design unificado para formulários de pesquisa e resultados dentro do admin (<a href=\"https://core.trac.wordpress.org/ticket/37353\">#37353</a>);</li><li>Novo bloco&nbsp;<code>embed</code>&nbsp;do Gutenberg adicionado ao núcleo (<a href=\"https://core.trac.wordpress.org/ticket/51531\">#51531</a>);</li><li>Versões atualizadas para Twemoji (<a href=\"https://core.trac.wordpress.org/ticket/51356\">#51356</a>), React (<a href=\"https://core.trac.wordpress.org/ticket/51505\">#51505</a>) e Akismet (<a href=\"https://core.trac.wordpress.org/ticket/51610\">#51610</a>);</li><li>Melhorias de acessibilidade (além de outras coisas) adicionadas para as senhas de aplicativos (<a href=\"https://core.trac.wordpress.org/ticket/51580\">#51580</a>) e</li><li>Indicador para detalhes da imagem adicionado em imagens anexadas com uma opção do site (<a href=\"https://core.trac.wordpress.org/ticket/42063\">#42063</a>).</li></ul>\n\n\n\n<h3>Notas para desenvolvedores</h3>\n\n\n\n<p id=\"block-c706675c-5a17-48a0-9fd8-5aa5703cb735\">O WordPress 5.6 também traz muitas melhorias para experiência de desenvolvimento. Fique de olho no&nbsp;<a href=\"https://make.wordpress.org/core/\">blog do núcleo do WordPress</a>&nbsp;para&nbsp;<a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">acompanhar as notas de desenvolvimento da versão 5.6</a>&nbsp;nas próximas semanas, detalhando essas e outras alterações.</p>\n\n\n\n<h3 id=\"block-37ee7e87-d852-40f7-9657-90d42a3879dc\">Como ajudar</h3>\n\n\n\n<p id=\"block-ab1acb90-0f9f-4424-a058-3cc22d9d1662\">Ajude a tradução em Português!&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a></p>\n\n\n\n<p id=\"block-97acd446-e0d0-4142-9442-15f4174e2e66\"><strong>Se acha que encontrou um erro</strong>, você pode publicá-lo na&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">área Alpha/Beta</a>&nbsp;nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro,&nbsp;<a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar uma&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">lista de erros conhecidos</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" id=\"block-fa7bcd97-ea6e-409b-913c-3de3416e26a1\" />\n\n\n\n<p id=\"block-ebf2a35a-f0be-493d-bdc9-a26084b413cc\"><em>Originalmente escrito por <a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a></em> em <a href=\"https://wordpress.org/news/2020/10/wordpress-5-6-beta-2/\">WordPress 5.6 Beta 2</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:\"\";}}}}}i:8;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:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.6 Beta 1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"https://br.wordpress.org/2020/10/21/wordpress-5-6-beta-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 21 Oct 2020 17:01:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:12:\"Lançamentos\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.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:32:\"https://br.wordpress.org/?p=2078\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:381:\"O WordPress 5.6 Beta 1 já está disponível! Esta versão ainda está em desenvolvimento, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão. Você pode testar o WordPress 5.6 Beta de duas formas: Usando o plugin&#160;WordPress Beta Tester&#160;(escolha a opção “bleeding edge nightlies”) ou [&#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:13:\"Felipe Santos\";s: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:9230:\"\n<p>O WordPress 5.6 Beta 1 já está disponível!</p>\n\n\n\n<p><strong>Esta versão ainda está em desenvolvimento</strong>, portanto não recomendamos seu uso em ambientes de produção. Considere criar um site de testes para testar a nova versão.</p>\n\n\n\n<p>Você pode testar o WordPress 5.6 Beta de duas formas:</p>\n\n\n\n<ul><li>Usando o plugin&nbsp;<a href=\"https://br.wordpress.org/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a>&nbsp;(escolha a opção “bleeding edge nightlies”) ou</li><li><a href=\"https://wordpress.org/wordpress-5.6-beta1.zip\">Baixando a versão beta aqui</a>&nbsp;(zip).</li></ul>\n\n\n\n<p>O lançamento está agendado para 8 de dezembro de 2020, <strong>faltando apenas sete semanas</strong>, e&nbsp;nós precisamos de sua ajuda para testar da melhor forma possível!</p>\n\n\n\n<h3>Melhorias no editor</h3>\n\n\n\n<p>O WordPress 5.6 incluirá sete versões do plugin Gutenberg. Aqui estão alguns recursos de destaque:</p>\n\n\n\n<ul><li>Suporte aprimorado para posicionamento de vídeo em blocos de capa.</li><li>Melhorias para padrões de blocos com inclusão de strings traduzíveis. </li><li>Contador de caracteres no painel informativo, melhor navegação pelo teclado e outros ajustes para ajudar usuários a encontrarem melhor o que estão buscando.</li><li>Interface aprimorada para funcionalidade de arrastar e soltar, assim como opções para mover os blocos.</li></ul>\n\n\n\n<p>Para ver todos os recursos de cada versão em detalhes, confira as versões:&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> e 9.2&nbsp;<em>(link ainda não disponível)</em>.</p>\n\n\n\n<h3>Melhorias no núcleo</h3>\n\n\n\n<h4>Um novo tema padrão</h4>\n\n\n\n<p>O tema padrão está sendo renovado novamente com o <a href=\"https://make.wordpress.org/core/2020/09/23/introducing-twenty-twenty-one/\">Twenty Twenty-One</a>. Este tema terá um destaque pela sua eficiência e o seu design elegante, além do objetivo de atingir <a href=\"https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-levels-head\">um nível AAA de conformidade</a>.</p>\n\n\n\n<h4>Opção de atualização automática para lançamentos principais</h4>\n\n\n\n<p>O muito esperado recurso de atualizações automáticas (caso ativado manualmente) será oferecido neste lançamento. Com esta funcionalidade você terá a opção de realizar essas atualizações do software do WordPress em segundo plano sem nenhum trabalho adicional.</p>\n\n\n\n<h4>Suporte aprimorado para o PHP 8</h4>\n\n\n\n<p>O próximo lançamento da versão principal do PHP, 8.0.0, está programado para apenas alguns dias antes do WordPress 5.6. O projeto WordPress tem uma longa história de compatibilidade com novas versões de PHP, e este lançamento não será diferente.</p>\n\n\n\n<p>O PHP 8 é uma versão principal e alterações que quebram a compatibilidade com versões anteriores ou compatibilidade com várias APIs podem acontecer. Temos trabalhado arduamente para corrigir as <a href=\"https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/\">incompatibilidades conhecidas com o PHP 8</a> no WordPress durante o ciclo de lançamento 5.6.</p>\n\n\n\n<p>Embora todos os problemas detectáveis no WordPress possam ser corrigidos, você precisará verificar se todos os seus plugins e temas também são compatíveis com PHP 8 antes da atualização. Fique de olho <a href=\"https://make.wordpress.org/core/\">no blog da equipe do núcleo do WordPress</a> nas próximas semanas para obter informações detalhadas sobre novidades.</p>\n\n\n\n<h4>Senhas de aplicativo para a autenticação na REST API</h4>\n\n\n\n<p>Desde que a API REST foi incorporada ao núcleo, apenas a autenticação baseada em cookies e nonce está disponível (sem o uso de um plugin). Este método de autenticação pode ser uma experiência frustrante para desenvolvedores, muitas vezes limitando como os aplicativos podem interagir com endpoints protegidos.</p>\n\n\n\n<p>Com a introdução da <a href=\"https://make.wordpress.org/core/2020/09/23/proposal-rest-api-authentication-application-passwords/\">senha de aplicativo</a> no WordPress 5.6, acabou essa frustração e a necessidade de se reautenticar quando os cookies expiram. De qualquer forma, não se preocupe, a autenticação por cookie e nonce permanecerá no WordPress como está, se você não estiver pronto para mudar.</p>\n\n\n\n<p>As senhas de aplicativos são específicas para usuários e facilitam a concessão/revogação do acesso para usuários ou aplicativos específicos (individualmente ou em massa). Informações como &#8220;Última utilização&#8221; são registradas e é fácil rastrear credenciais inativas ou agentes mal-intencionados em locais inesperados.</p>\n\n\n\n<h4>Melhor acessibilidade</h4>\n\n\n\n<p>A cada versão, o WordPress trabalha duro para melhorar a acessibilidade. A versão 5.6 não é diferente e inclui várias correções e aprimoramentos de acessibilidade. Dê uma olhada:</p>\n\n\n\n<ul><li>Anuncia alterações de seleção de bloco manualmente nas janelas.</li><li>Evita o foco no botão de seleção de bloco em cada renderização.</li><li>Evita a renderização da área de texto da área de transferência dentro do botão.</li><li>Corrige a perda de foco do menu suspenso ao usar as teclas de seta com Safari e Voiceover.</li><li>Corrige problema para arrastar vários blocos para baixo, o que resultava em blocos inseridos na posição errada.</li><li>Corrige a <em>aria description</em> incorreta na visualização da lista de blocos.</li><li>Adiciona navegação de seta no menu de pré-visualização.</li><li>Impede que os links sejam focalizáveis dentro do componente desabilitado.</li></ul>\n\n\n\n<h3>Como ajudar</h3>\n\n\n\n<p>Fique de olho no&nbsp;<a href=\"https://make.wordpress.org/core/\">blog do núcleo do WordPress</a>&nbsp;para&nbsp;<a href=\"https://make.wordpress.org/core/tag/5-6+dev-notes/\">acompanhar as notas de desenvolvimento da versão 5.6</a>&nbsp;nas próximas semanas, detalhando essas e outras alterações.</p>\n\n\n\n<p>Até o momento, os colaboradores corrigiram mais de&nbsp;<a href=\"https://core.trac.wordpress.org/query?status=closed&amp;milestone=5.6&amp;group=component&amp;max=500&amp;col=id&amp;col=summary&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;col=version&amp;order=priority\">188 tickets no WordPress 5.6</a>, incluindo&nbsp;<a href=\"https://core.trac.wordpress.org/query?status=closed&amp;status=reopened&amp;type=enhancement&amp;milestone=5.6&amp;or&amp;status=closed&amp;status=reopened&amp;type=feature+request&amp;milestone=5.6&amp;col=id&amp;col=summary&amp;col=type&amp;col=status&amp;col=milestone&amp;col=owner&amp;col=priority&amp;col=changetime&amp;col=keywords&amp;order=changetime\">82 novos recursos e melhorias</a>, e mais correções de erros estão por vir.</p>\n\n\n\n<p>Ajude a tradução em Português!&nbsp;<a href=\"https://translate.wordpress.org/projects/wp/dev/pt-br/default\">Ajude-nos a traduzir o WordPress para o português!</a></p>\n\n\n\n<p><em><strong>Se acha que encontrou um erro</strong>, você pode publicá-lo na&nbsp;<a href=\"https://wordpress.org/support/forum/alphabeta\">área Alpha/Beta</a>&nbsp;nos fóruns de suporte (em inglês). Nós vamos adorar ouvir você! Se você se sente confortável para escrever um relatório de como reproduzir o erro,&nbsp;<a href=\"https://make.wordpress.org/core/reports/\">envie para o Trac do WordPress</a>, onde também é possível encontrar uma&nbsp;<a href=\"https://core.trac.wordpress.org/tickets/major\">lista de erros conhecidos</a>.</em></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p><em>Originalmente escrito por <a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a>. Agradecimentos para&nbsp;<a href=\'https://profiles.wordpress.org/webcommsat/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>webcommsat</a>,&nbsp;<a href=\'https://profiles.wordpress.org/yvettesonneveld/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>yvettesonneveld</a>,&nbsp;<a href=\'https://profiles.wordpress.org/estelaris/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>estelaris</a>,&nbsp;<a href=\'https://profiles.wordpress.org/cguntur/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>cguntur</a>,&nbsp;<a href=\'https://profiles.wordpress.org/desrosj/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>desrosj</a> e&nbsp;<a href=\'https://profiles.wordpress.org/marybaum/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>marybaum</a>&nbsp;pela revisão e edição, além de&nbsp;<a href=\'https://profiles.wordpress.org/davidbaumwald/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>davidbaumwald</a>&nbsp;pela revisão final.</em></p>\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:3:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"Dia internacional de tradução do WordPress 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:84:\"https://br.wordpress.org/2020/10/02/dia-internacional-de-traducao-do-wordpress-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, 02 Oct 2020 20:28:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:5:\"Geral\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:7:\"Meetups\";s: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:15:\"Temas e Plugins\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://br.wordpress.org/?p=2059\";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:347:\"O WordPress Translation Day é um evento que une a comunidade WordPress do mundo todo em um dia dedicado à tradução e localização de tudo relacionado ao WordPress. São milhares de participantes espalhados ao redor do mundo, e todos com o mesmo objetivo: estender o alcance do WordPress e torná-lo mais inclusivo e acessível. Este [&#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:13:\"Felipe Santos\";s: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:1925:\"\n<p>O <em>WordPress Translation Day</em> é um evento que une a comunidade WordPress do mundo todo em um dia dedicado à tradução e localização de tudo relacionado ao WordPress. São milhares de participantes espalhados ao redor do mundo, e todos com o mesmo objetivo: estender o alcance do WordPress e torná-lo mais inclusivo e acessível.</p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" width=\"1024\" height=\"512\" src=\"https://br.wordpress.org/files/2020/10/wptranslationday-1024x512.png\" alt=\"\" class=\"wp-image-2074\" srcset=\"https://br.wordpress.org/files/2020/10/wptranslationday-1024x512.png 1024w, https://br.wordpress.org/files/2020/10/wptranslationday-300x150.png 300w, https://br.wordpress.org/files/2020/10/wptranslationday-768x384.png 768w, https://br.wordpress.org/files/2020/10/wptranslationday.png 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" /></figure></div>\n\n\n\n<p>Este ano o evento será realizado através de eventos menores ao redor do mundo, e a versão da comunidade do WordPress Brasil vai acontecer no dia 3 de outubro.</p>\n\n\n\n<p>Alguns dos nossos editores de tradução estarão disponíveis no canal #traducao do Slack da comunidade para ajudar quem quiser começar com traduções, se tornar PTE, revisão de traduções e tudo mais relacionado com tradução.</p>\n\n\n\n<p>Se ainda não fizer parte da comunidade no Slack, você pode <a href=\"https://br.wordpress.org/team/handbook/comunidade-no-slack/\">conferir o nosso guia de como entrar para mais informações</a>.</p>\n\n\n\n<hr class=\"wp-block-separator is-style-wide\" />\n\n\n\n<p>Ref: <a href=\"https://br.wordpress.org/team/2020/09/14/dia-internacional-de-traducao-do-wordpress/\">https://br.wordpress.org/team/2020/09/14/dia-internacional-de-traducao-do-wordpress/</a></p>\n\n\n\n<p>Agradecimentos para <a href=\"https://profiles.wordpress.org/andr3ribeiro/\">Andre Ribeiro</a> pela arte gráfica.</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:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:35:\"https://br.wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s: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:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Mon, 18 Jan 2021 14:11:53 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 06 Sep 2017 19:17:40 GMT\";s:4:\"link\";s:61:\"<https://br.wordpress.org/wp-json/>; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20201029203228\";}','no'),(833,'_transient_timeout_feed_mod_b85365aa61afaf3d4189819a6f57c4c4','1611022313','no'),(834,'_transient_feed_mod_b85365aa61afaf3d4189819a6f57c4c4','1610979113','no'),(835,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1611022314','no'),(836,'_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: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:8443:\"<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></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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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:2687:\"<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&nbsp;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 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: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: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: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: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: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: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:15;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:94:\"WPTavern: 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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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: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:\"\";}}}}}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:30:\"Matt: What’s In My Bag, 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:22:\"https://ma.tt/?p=53341\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:43:\"https://ma.tt/2021/01/whats-in-my-bag-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:15521:\"<p>Instead of <a href=\"https://ma.tt/category/in-my-bag/\">sharing what&#8217;s in my backpack</a> this year, I want to share the apps and pandemic purchases that were meaningful to me, along with a few words on each. Something I haven&#8217;t shared with you yet on this blog is&#8230; I went down a #vanlife rabbit hole and ended up camping and working remotely a decent chunk of the year. I learned a ton and feel much more resilient. So this is a phoneful and truckful update of my year.</p>\n\n\n\n<p>First I&#8217;ll start with apps, these all link to Apple&#8217;s app store but almost all have Android equivalents that I also use:</p>\n\n\n\n<ul><li><a href=\"https://apps.apple.com/us/app/calm/id571800810\">Calm</a> and <a href=\"https://apps.apple.com/us/app/waking-up-guided-meditation/id1307736395\">Waking Up</a> —&nbsp;Very different but both incredibly valuable meditation apps. I had an 82-day streak with Calm this year! I wouldn&#8217;t have survived without these.</li><li><a href=\"https://apps.apple.com/us/app/fitbod-workout-fitness-plans/id1041517543\">Fitbod</a> —&nbsp;You tell the app what equipment you have, how much time you have, and it gives you a workout like a trainer would, rotating muscle groups.</li><li><a href=\"https://apps.apple.com/us/app/streaks/id963034692\">Streaks</a> — An app for starting and tracking habits. This is a funny one because I actually stopped using it because it worked. The things I was tracking on Streaks became daily habits and I stopped using the app every day. The same thing happened for me with <a href=\"https://www.zerofasting.com/\">Zero</a>, my daily fast became part of my routine so I&#8217;d only use Zero if I was doing a longer one.</li><li><a href=\"https://apps.apple.com/us/app/tumblr/id305343404\">Tumblr</a> —&nbsp;It was so nice to have a social network centered around creativity and humor.</li><li><a href=\"https://apps.apple.com/us/app/asana-your-work-manager/id489969512\">Asana</a> —&nbsp;Getting organized helped lessen anxiety.</li><li><a href=\"https://itunes.apple.com/au/app/pocket-casts/id414834813\">Pocket Casts</a> —&nbsp;I switched to this because it syncs between devices, and I used my Android device a lot especially while driving.</li><li><a href=\"https://apps.apple.com/us/app/alltrails-hike-bike-run/id405075943\">AllTrails</a> — I spent more time in nature this year than almost any previous, and AllTrails was an amazing way to find great hikes.</li><li><a href=\"https://apps.apple.com/us/app/the-economist/id1239397626\">The Economist</a> —&nbsp;The most insightful news, and the weekly cadence helped me avoid the wild variance of the daily news cycle. My favorite news app.</li><li><a href=\"https://apps.apple.com/us/app/youtube-watch-listen-stream/id544007664\">YouTube</a> —&nbsp;Wow, there&#8217;s a lot of stuff on here. This was the year I started to &#8220;get&#8221; why people spend so much time on YouTube. Some favorite finds were <a href=\"https://www.youtube.com/channel/UCtmY49Zn4l0RMJnTWfV7Wsg\">Jacob Collier</a> and <a href=\"https://www.youtube.com/channel/UCY1kMZp36IQSyNx_9h4mpCg\">Mark Rober</a>.</li><li><a href=\"https://apps.apple.com/us/app/walmart-shopping-grocery/id338137227\">Walmart</a> —&nbsp;Surprisingly good on road trips for curbside pickup orders scheduled a few hours ahead. Yes, I have now <a href=\"https://www.cnbc.com/2017/04/12/nearly-every-american-spent-money-at-wal-mart-last-year.html\">joined 95% of the US population</a>.</li><li><a href=\"https://apps.apple.com/us/app/blueground/id1183301329\">Blueground</a> and <a href=\"https://apps.apple.com/us/app/avantstay/id1455404746\">Avantstay</a> —&nbsp;Good for longer stays in places. I found both through <a href=\"https://www.airbnb.com/\">Airbnb</a>, which is still the king.</li><li>Food apps in order of usage: <a href=\"https://apps.apple.com/us/app/doordash-food-delivery/id719972451\">DoorDash</a>, <a href=\"https://apps.apple.com/us/app/uber-eats-food-delivery/id1058959277\">Uber Eats</a>, <a href=\"https://apps.apple.com/us/app/tock-restaurant-reservations/id1369347408\">Tock</a>, <a href=\"https://apps.apple.com/us/app/toast-takeout-delivery/id1362180579\">Toast TakeOut</a>.</li><li>Camping apps in order of usage: <a href=\"https://apps.apple.com/us/app/alltrails-hike-bike-run/id405075943\">AllTrails</a>, <a href=\"https://apps.apple.com/us/app/chimani-national-park-guides/id436381327\">Chimani</a>, <a href=\"https://apps.apple.com/us/app/recreation-gov/id1440487780\">Recreation.gov</a>, <a href=\"https://apps.apple.com/us/app/ioverlander/id894352689\">iOverlander</a>,  <a href=\"https://apps.apple.com/us/app/boondocking/id561352659\">Boondocking</a>, <a href=\"https://apps.apple.com/us/app/freeroam-boondocking-more/id1434359242\">FreeRoam</a>, <a href=\"https://apps.apple.com/us/app/harvest-hosts/id1321631420\">Harvest Hosts</a>.</li><li>App I deleted and re-added the most: <a href=\"https://apps.apple.com/us/app/twitter/id333903271\">Twitter</a>. I love the things I learn from using it, but hate feeling like I&#8217;m wasting time.</li></ul>\n\n\n\n<p>When on road trips I found Android Auto running off the Pixel 5 much more reliable than CarPlay, which would frequently freeze up on me. Things have improved with iOS 14, but I still always use the Pixel when I&#8217;m on a longer drive.</p>\n\n\n\n<p>I also have been living with my Mom since July, including her two cats and <a href=\"https://matt.blog/2021/01/02/introducing-lily-belle/\">new Coton du Tulear puppy</a>. Pets are humbling! It&#8217;s been great to learn how to support them best, as I last lived with animals when I was in high school and wasn&#8217;t that conscious of the responsibility then.</p>\n\n\n\n<p>Amazon says I made over 850 orders this year, more than double from any previous year. Here are the non-tech purchases that ended up having a big impact on me:</p>\n\n\n\n<ul><li><a href=\"https://www.amazon.com/gp/product/B07GZ2DY7K/?tag=photomatt08-20\">SmartMouth mouthwash</a> —&nbsp;Available in <a href=\"https://www.amazon.com/gp/product/B01IADXVUY/?tag=photomatt08-20\">travel packs as well</a>, this is magical for having great breath, which you&#8217;ll notice more now that you&#8217;re wearing a mask all the time.</li><li><a href=\"https://www.amazon.com/gp/product/B06XHMNGF9/?tag=photomatt08-20\">Marvis Royal Toothpaste</a> —&nbsp;Delicious! SLS-free! I switch between this and the <a href=\"https://www.amazon.com/gp/product/B000MUH344/?tag=photomatt08-20\">SmartMouth toothpaste</a> which works better but isn&#8217;t as luxuriously tasty.</li><li><a href=\"https://www.amazon.com/Theragun-Elite-Generation-Percussive-Treatment/dp/B08G3Q44YJ/?tag=photomatt08-20\">Theragun</a> — Because you can&#8217;t get a massage.</li><li><a href=\"https://www.amazon.com/gp/product/B07N41D7QY/?tag=photomatt08-20\">Hurtle vibration platform</a> —&nbsp;Really weird but seems to shake the stress out of you, especially if you stretch on it for 5-10 minutes.</li><li><a href=\"https://www.amazon.com/Bowflex-SelectTech-Adjustable-Dumbbells-Pair/dp/B001ARYU58/?tag=photomatt08-20\">Bowflex Adjustable Dumbbells</a> —&nbsp;I was lucky enough to get these before they sold out and became crazy expensive. </li><li><a href=\"https://www.amazon.com/gp/product/B01JQU3BPK/?tag=photomatt08-20\">Buckwheat meditation cushion</a> — So much more comfortable to have a cushion, especially for longer meditation sessions. <a href=\"https://www.amazon.com/gp/product/B01GDF47Q8/?tag=photomatt08-20\">Here&#8217;s a smaller version</a> I use on the road.</li><li><a href=\"https://www.philips-hue.com/en-us\">Tons of Philips Hue lights</a> —&nbsp;Got a ton of joy from playing with the colors on these.</li><li><a href=\"https://www.amazon.com/gp/product/B07S7DWWJZ/?tag=photomatt08-20\">Cloth napkins</a> —&nbsp;Felt so luxurious, easy to wash and re-use.</li><li><a href=\"https://www.amazon.com/gp/product/B07HML9YLD/?tag=photomatt08-20\">Heated cat bed</a> —&nbsp;My Mom&#8217;s cats are obsessed with this now. </li><li><a href=\"https://www.amazon.com/SHARONDS-Scissors-Thinning-Professional-Stainless/dp/B08BWXWHWH/?tag=photomatt08-20\">Sharonds hair cutting scissors</a> —&nbsp;10x better than the scissors I had lying around the house.</li><li><a href=\"https://www.amazon.com/dp/B07L67KL81/?tag=photomatt08-20\">Babyliss clippers</a> —&nbsp;They&#8217;re gold and have a &#8220;Lamborghini&#8221; motor which is ostentatious but works great.</li><li><a href=\"https://www.amazon.com/gp/product/B07GB4TDST/?tag=photomatt08-20\">Hair Apron Cape</a> — You feel like a dog with <a href=\"https://neothesamoyed.tumblr.com/post/173710808330/ice-cream-cone-boy\">one of those cones</a>, but mostly works.</li><li><a href=\"https://www.amazon.com/gp/product/B07QN7FWC9/?tag=photomatt08-20\">Yeti Lowlands picnic blanket</a> — Expensive but sturdy.</li><li><a href=\"https://www.amazon.com/gp/product/B07V6MR1R5/?tag=photomatt08-20\">Cliq camping chair</a> —&nbsp;Super small and great design, but ended up using these less than I thought because we mostly just stayed on the ground on the Yeti blanket.</li><li><a href=\"https://www.amazon.com/gp/product/B07RX1TBKM/?tag=photomatt08-20\">Isdin foot care cream</a> —&nbsp;Really softens your feet.</li><li><a href=\"https://www.amazon.com/gp/product/B018GXZ016/?tag=photomatt08-20\">Silicone tip cooking chopsticks</a> or the <a href=\"https://www.amazon.com/gp/product/B07LC6253B/?tag=photomatt08-20\">ones with the spoon on the end</a>.</li><li><a href=\"https://www.amazon.com/Surpahs-Multipurpose-Roll-Up-Drying-Inches/dp/B08196DX71/?tag=photomatt08-20\">Roll-up drying rack</a> —&nbsp;Goes great over the sink.</li><li>Joseph Joseph <a href=\"https://www.amazon.com/gp/product/B07TD663Y1/?tag=photomatt08-20\">nesting kitchen tools</a>, <a href=\"https://www.amazon.com/dp/B006BSBRWK/?tag=photomatt08-20\">nesting bowls</a> —&nbsp;They&#8217;re so pretty as well.</li><li><a href=\"https://www.amazon.com/gp/product/B07CPSJRT4/\">Hanging solar mason jar lights</a> —&nbsp;Like fireflies in a jar.</li><li><a href=\"https://www.amazon.com/dp/B0828BNW82/?tag=photomatt08-20\">Matador Freerain32 waterproof packable backpack</a> — My new favorite for hiking.</li><li><a href=\"https://www.amazon.com/gp/product/B07PFJZ1LV/?tag=photomatt08-20\">Matador Transit30 packable duffle bag</a> —&nbsp;I ended up using this way more than I expected.</li><li><a href=\"https://www.amazon.com/gp/product/B08CXPBZLD/?tag=photomatt08-20\">This bamboo table</a> —&nbsp;Just the right size for eating or working on the ground.</li><li><a href=\"https://www.amazon.com/Ikea-Large-Shopping-Bags-SET/dp/B00KVJJGN2/?tag=photomatt08-20\">Ikea Frakta bag</a> —&nbsp;Just a few dollars each and can hold so much, and available on Amazon.</li></ul>\n\n\n\n<p>Clothing and wearables, like much of the world I trended toward comfort and away from normal shoes and socks:</p>\n\n\n\n<ul><li><a href=\"https://www.amazon.com/gp/product/B01IKRF2PW/?tag=photomatt08-20\">Bumpers flip flops</a> — Weird but you get used to them.</li><li><a href=\"https://www.oofos.com/products/mens-ooahh-sport-slide-sandal-black-matte\">Oofos slide sandals</a> —&nbsp;Ridiculously comfortable, and this model looks like it has the <a href=\"https://automattic.com/\">Automattic</a> logo on it.</li><li><a href=\"https://www.amazon.com/gp/product/B077LJSDQL/?tag=photomatt08-20\">Glerups wool slippers</a> —&nbsp;Like wool clogs, I wear the rubber-soled ones out if just stepping out for a bit.</li><li><a href=\"https://www.patagonia.com/shop/capilene-air-baselayers\">Patagonia Capilene Air baselayers</a> — So warm! Addictive.</li><li><a href=\"https://fahertybrand.com/\">Faherty Brand</a> — I just love their whole look and feel, and have met the brothers before.</li><li><a href=\"https://www.aloyoga.com/\">Alo Yoga</a> —&nbsp;Pricey but looks great and fun to workout in. I&#8217;ve had some quality issues with their items though.</li><li><a href=\"https://shop.lululemon.com/\">Lululemon</a> —&nbsp;Especially their new tech canvas pants.</li><li><a href=\"https://unboundmerino.com/\">Unbound Merino</a> —&nbsp;My go-to shirt, also decent socks.</li><li><a href=\"https://www.uniqlo.com/us/en/home/\">Uniqlo</a> —&nbsp;Great value, and no logos!</li></ul>\n\n\n\n<p>Electronics:</p>\n\n\n\n<ul><li><a href=\"https://ma.tt/2020/05/ceo-video-streaming/\">Everything in the streaming post</a> — I ended up doing a ton of press and talks this year as the world became more <a href=\"https://distributed.blog/\">distributed</a>. I also personally helped many others get similar setups.</li><li><a href=\"https://store.ui.com/\">Everything Unifi</a> — It&#8217;s a year I really appreciated solid internet. </li><li><a href=\"https://www.amazon.com/gp/product/B01LVZ3UI6/?tag=photomatt08-20\">Retractable 50&#8242; ethernet cord</a> — I actually daisy-chained two of these to do an internal company town hall presentation.</li><li><a href=\"https://www.amazon.com/gp/product/B07RVF386D/?tag=photomatt08-20\">25&#8242; retractable power extension cord</a> — I also carry two of these.</li><li><a href=\"https://www.apple.com/macbook-pro-13/\">Macbook 13&#8243; M1</a> — It really is the fastest computer you&#8217;ve ever used. This replaced a maxed out 16&#8243;.</li><li><a href=\"https://www.amazon.com/gp/product/B088666T68/?tag=photomatt08-20\">Hyppr 100w USB-C charger</a> — Smaller and better than Apple&#8217;s charger.</li><li><a href=\"https://www.apple.com/airpods-max/\">Airpods Max</a> — I didn&#8217;t want to like them but they&#8217;re slick.</li><li><a href=\"https://www.amazon.com/gp/product/B089N2RJ4X/?tag=photomatt08-20\">Airpods Pro Dekoni Tips</a> — Great upgrade for normal Airpods.</li><li><a href=\"https://www.apple.com/iphone-12-pro/\">iPhone 12 Pro Max</a> — It&#8217;s like a mini iPad. Camera with RAW support is fantastic.</li><li><a href=\"https://www.apple.com/pro-display-xdr/\">Apple Pro Display XDR</a> — Wow.</li><li><a href=\"https://store.google.com/us/product/pixel_5\">Pixel 5</a> — Pretty great that they got the fingerprint reader back in as FaceID with a mask is terrible, so this has become my primary device if I&#8217;m out for a walk.</li><li><a href=\"https://store.google.com/product/pixelbook_go\">Pixelbook Go</a> — For my Mom.</li><li><a href=\"https://store.google.com/product/chromecast_google_tv\">Chromecast with Google TV</a> — Bad name but great product. Truly. Really well designed.</li><li><a href=\"https://www.amazon.com/gp/product/B07FJ91TLB/\">Kindle Oasis with the new warm light</a> — Even though I read less this year, this made what I did read a pleasure.</li><li>Sinjimou charging stand for <a href=\"https://www.amazon.com/Sinjimoru-Including-iPhone-Convenient-Silicone/dp/B07GQNY5RD/?tag=photomatt08-20\">iPhone</a> and <a href=\"https://www.amazon.com/gp/product/B07GQV2NXN/?tag=photomatt08-20\">USB-C</a> — Works great, really cheap.</li><li><a href=\"https://www.amazon.com/gp/product/B07DD9TQSG/?tag=photomatt08-20\">Megaboom 3</a> — Two of these paired together in stereo is the best sound, weight, and battery life combo I&#8217;ve found on the road and in parks.</li><li><a href=\"https://www.amazon.com/dp/B07QTVMWVL/?tag=photomatt08-20\">Garmin 945 watch</a> — I&#8217;ve talked about this watch previously, but this year I discovered the GPS maps feature when in hiking mode, which can literally be a lifesaver. Amazing for going off-trail.</li></ul>\n\n\n\n<p>There you have it. As always, if you&#8217;ve tried something here and found an alternative that&#8217;s better, let me know in the comments!</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 03 Jan 2021 04:37:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:39:\"WPTavern: 2020: Step Away From the Fire\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109487\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:121:\"https://wptavern.com/2020-step-away-from-the-fire?utm_source=rss&utm_medium=rss&utm_campaign=2020-step-away-from-the-fire\";s: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:11328:\"<img />\n\n\n\n<p class=\"has-drop-cap\">If there was a common theme that held humanity together in 2020, it was that most of us agreed that the year was nothing short of a dumpster fire.  That and <a href=\"https://wptavern.com/you-deserve-to-wear-sweatpants-dont-let-anyone-tell-you-any-different\">sweatpants.</a></p>\n\n\n\n<p>As people <a href=\"https://wptavern.com/finding-balance-in-these-uncertain-times-remote-work-and-sharing-our-struggles\">learned to cope</a> with a new reality in the Covid-19 era, the WordPress community has been a <a href=\"https://wptavern.com/need-to-smile-today-stay-wordpress-strong\">beacon of hope</a>. When other industries needed to learn how to work remotely, we were already <a href=\"https://wptavern.com/leave-at-door-new-free-woocommerce-plugin-enables-contact-free-delivery\">ahead of the pack</a> and <a href=\"https://wptavern.com/big-orange-heart-opens-2020-remote-work-wellbeing-and-mental-health-survey\">willing to help</a>. As people dealt with the stress of not having meetups in person, the WordPress community thrived with online events.</p>\n\n\n\n<p>The early year was tough. From toilet paper shortages to being unable to work from a favorite coffee shop, the pandemic took its toll.</p>\n\n\n\n<p>However, we have learned to cope throughout the year. We used new ways to communicate from a distance. Created new circles of friends. Found extra time for long-forgotten hobbies online and off.</p>\n\n\n\n<p>We continued to create art, which is the thing that makes our species so undeniably unique.</p>\n\n\n\n<p>Maybe it is all the lessons we have learned through the past several months. Perhaps it is that a new year is upon us. The winds of change feel like they are gently nudging us forward.</p>\n\n\n\n<p>Over the past couple of months, I have noticed a new calmness. A new hopefulness. A feeling that we will continue to rise above any challenges that come our way. While death and illness are still a part of our daily reality, we must continue to lean on the people within communities like WordPress for support. We will continue marching ahead together.</p>\n\n\n\n<p>I always like to take stock of the past year. This helps keep me grounded and remain optimistic about the future. The following is a look back at 2020 for WP Tavern and WordPress.</p>\n\n\n\n<h2>WP Tavern Stats</h2>\n\n\n\n<p class=\"has-drop-cap\">We have had a solid year of publishing here at the Tavern. Our team, including guest authors, wrote 401 posts. In 2019, we knocked out 382. Next year, I expect that figure to increase.</p>\n\n\n\n<p>Our word count average soared. This year, we averaged 790 words per post. In 2019, that number was 589. While word count is not a testament to quality writing, we did have opportunities to dive deeper into topics than before. In total, we wrote over 315,000 words. That is about 80,000 words shy of Brandon Sanderson&rsquo;s <em>The Way of Kings</em>. You could say that we wrote enough to fill an epic fantasy novel.</p>\n\n\n\n<p>&ldquo;Likes&rdquo; were up this year too. We went from an average of 7.0 likes per post in 2019 to 8.7 in 2020.</p>\n\n\n\n<p>For comments, it is hard to gauge. The WordPress.com Stats feature does not seem to be accurately tracking our comment counts. The figure is nowhere close to correct. By my rough estimate (counting in hundreds), we have at least twice as many published comments as the data shows.</p>\n\n\n\n<p>There were a few days scattered throughout the year in which we came within a hair&rsquo;s breadth of surpassing the site&rsquo;s all-time daily view count. But, alas, we fell just shy of the mark. <em>Maybe next year.</em></p>\n\n\n\n<h2>Most Viewed Posts of the Year</h2>\n\n\n\n<p class=\"has-drop-cap\">The following is a list of the 10 most-viewed posts published this year. They are not necessarily representative of our best work. However, they do represent what folks were reading. Everything beyond this was pretty close in terms of stats.</p>\n\n\n\n<ol><li><a href=\"https://wptavern.com/preparing-for-wordpress-5-4-changes-theme-and-plugin-developers-should-know-about\">Preparing for WordPress 5.4: Changes Theme and Plugin Developers Should Know About</a></li><li><a href=\"https://wptavern.com/matt-mullenweg-unveils-gutenberg-roadmap-at-wceu-wordpress-agencies-and-product-developers-sprint-to-prepare\">Matt Mullenweg Unveils Gutenberg Roadmap at WCEU, WordPress Agencies and Product Developers Sprint to Prepare</a></li><li><a href=\"https://wptavern.com/w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft\">W3C Drops WordPress from Consideration for Redesign, Narrows CMS Shortlist to Statamic and Craft</a></li><li><a href=\"https://wptavern.com/major-jquery-changes-on-the-way-for-wordpress-5-5-and-beyond\">Major jQuery Changes on the Way for WordPress 5.5 and Beyond</a></li><li><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></li><li><a href=\"https://wptavern.com/biden-harris-transition-website-launches-on-wordpress\">Biden-Harris Transition Website Launches on WordPress</a></li><li><a href=\"https://wptavern.com/wordpress-5-6-will-ship-with-another-major-jquery-change\">WordPress 5.6 Will Ship With Another Major jQuery Change</a></li><li><a href=\"https://wptavern.com/godaddys-go-wordpress-theme-offers-a-page-building-experience-via-the-block-editor\">GoDaddy&rsquo;s &lsquo;Go&rsquo; WordPress Theme Offers a Page-Building Experience via the Block Editor</a></li><li><a href=\"https://wptavern.com/font-awesome-releases-new-covid-19-awareness-icons\">Font Awesome Releases New COVID-19 Awareness Icons</a></li><li><a href=\"https://wptavern.com/automatic-theme-and-plugin-updates-slated-for-wordpress-5-5\">Automatic Theme and Plugin Updates Slated for WordPress 5.5</a></li></ol>\n\n\n\n<p>For some reason, Sarah&rsquo;s piece on <a href=\"https://wptavern.com/how-to-add-subscript-and-superscript-characters-in-wordpress\">adding subscript and superscript characters</a> from 2014 always sneaks its way into the most-viewed posts of the year. It was technically #6 on the list, but it wasn&rsquo;t published in 2020.</p>\n\n\n\n<h2>The Year in WordPress</h2>\n\n\n\n<p class=\"has-drop-cap\">It was the year that saw the rise of online-only WordCamps. What started with WordCamp Asia <a href=\"https://wptavern.com/wordcamp-asia-2020-canceled-over-covid-19-concerns\">canceling its inaugural event</a> in February ended with Matt Mullenweg giving the annual <a href=\"https://wptavern.com/state-of-the-word-2020-wordpress-moves-toward-full-site-editing\">State of the Word</a> virtually, a first. WordCamp Europe <a href=\"https://wptavern.com/wordcamp-europe-2020-online-registration-now-open-tickets-are-free\">took its massive event online</a> for 2020 while WordCamp U.S. canceled its planned virtual get-together after months of <a href=\"https://wptavern.com/wordcamp-us-2020-canceled-due-to-pandemic-stress-and-online-event-fatigue\">pandemic stress and online event fatigue</a>.</p>\n\n\n\n<p>We saw the community rise up and tackle problems from the beginning. Companies like Wordfence, Yoast, and GoDaddy <a href=\"https://wptavern.com/the-international-wordpress-community-and-wordcamps-amid-covid-19\">provided help</a> for those who were not refunded travel expenses after cancellations. At the end of the day, that is what the WordPress community is all about: people helping other people.</p>\n\n\n\n<p>WordPress kept chugging along, despite the stressful year. The big highlights were three major releases of the software:</p>\n\n\n\n<ul><li><a href=\"https://wptavern.com/wordpress-5-4-adderley-released-includes-improved-editor-new-blocks-and-developer-apis\">WordPress 5.4 &ldquo;Adderley&rdquo;</a></li><li><a href=\"https://wptavern.com/wordpress-5-5-eckstine-introduces-block-directory-block-patterns-and-automatic-updates-for-themes-and-plugins\">WordPress 5.5 &ldquo;Eckstine&rdquo;</a></li><li><a href=\"https://wptavern.com/wordpress-5-6-simone-includes-new-twenty-twenty-one-theme-and-improved-editor\">WordPress 5.6 &ldquo;Simone&rdquo;</a></li></ul>\n\n\n\n<p>WordPress also <a href=\"https://wptavern.com/happy-17th-wordpress\">turned 17</a> this year.  Its step into adulthood next year should be an adventure.</p>\n\n\n\n<h2>Posts From Contributing Writers</h2>\n\n\n\n<p class=\"has-drop-cap\">Rather than focusing too much on the work that Sarah and I have put into the Tavern this year, I want to say thank you to our contributing writers. They managed to fill some gaps when we were unable to throughout the past 12 months. They have added viewpoints outside of our own, enriching the content that our site offers. If anything, I want to see further contributions from a wider range of the WordPress community in the future.</p>\n\n\n\n<p>I do not typically like to play favorites with our guest writers, but Francesca Marano&rsquo;s piece titled <a href=\"https://wptavern.com/a-non-technical-release-leads-journey-to-becoming-a-mentor-for-wordpress-core-development\">A Non-Technical Release Lead&rsquo;s Journey to Becoming a Mentor for WordPress Core Development</a> was one of my favorite reads of the year. Her backstory is a good intro to the article. Her depth of knowledge and insight into <em>the room where it happens</em> makes it a must-read for anyone unfamiliar with how WordPress gets made.</p>\n\n\n\n<p>Chris Maiorana&rsquo;s <a href=\"https://wptavern.com/wordpress-university-was-always-online\">WordPress University Was Always Online</a> is a reminder that the education we need to excel in the online business market is but at our fingertips. It also touches on how the pandemic has allowed more people to realize that the traditional college experience is not the only path forward. It is a great piece that forces us to explore alternatives. And, these alternatives have always been available in the WordPress ecosystem.</p>\n\n\n\n<p>Maiorana&rsquo;s piece on the <a href=\"https://wptavern.com/state-of-the-meetup-under-lockdown\">State of the Meetup Under Lockdown</a> explores how the virtual realm has changed meetups. <a href=\"https://wptavern.com/bringing-back-blogs-in-the-age-of-social-media-censorship\">Bringing Back Blogs in the Age of Social Media Censorship</a> is a look into how blogs are the answer in the age of censorship, even when we disagree with a person&rsquo;s position on a subject.</p>\n\n\n\n<p>On the technical end of things, Jonathan Bossenger wrote an in-depth piece for <a href=\"https://wptavern.com/getting-your-wordpress-plugins-and-themes-ready-for-php-8\">Getting Your WordPress Plugins and Themes Ready for PHP 8</a>. He goes through everything that developers need to know to get their projects updated. The article also provides tools and resources to make things easier.</p>\n\n\n\n<h2>Goodbye, 2020</h2>\n\n\n\n<p class=\"has-drop-cap\">While the year might not have been ideal in many ways, there were some great moments. As I reflect upon the events of the last 12 months, I do not see a complete dumpster fire. There was a lot of good that came out of it. The world has changed in some large ways. Our societies have undergone some subtle reshaping. I do not know what 2021 holds, but I remain optimistic.</p>\n\n\n\n<p>I look forward to another year covering the events surrounding WordPress. I hope you continue down this journey with the WP Tavern 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:\"Thu, 31 Dec 2020 22:44:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:43:\"Matt: Jack Dorsey and Running Two Companies\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53328\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"https://ma.tt/2020/12/running-two-companies/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1808:\"<p>I had the <a href=\"https://distributed.blog/2020/12/16/episode-26-jack-dorsey-and-remote-collaboration/\">pleasure of interviewing Jack Dorsey for the Distributed podcast</a>, a conversation that ended up going a bit deeper and longer than previous episodes.</p>\n\n\n\n<p>In preparation for the interview I kept coming across people critical about the fact that Jack is the CEO of two companies simultaneously, <a href=\"https://twitter.com/\">Twitter</a> and <a href=\"https://squareup.com\">Square</a>, each having over 5,000 employees.</p>\n\n\n\n<p>I think what people miss is that at that scale, running a company is not that different from running a large division of a company. No one asks Jeff Bezos how he&#8217;s CEO of both a retail company and a cloud computing one (AWS), or Tim Cook how he&#8217;s CEO of a hardware business and a services business, and of course with both of those examples the breadth of what the companies cover is much wider. Also as an added benefit, shareholders can choose to invest in Square and Twitter together or not.</p>\n\n\n\n<p>All of that said, I think having a CEO-level seat at two of the most influential technology companies today does allow for accelerated learning, as organizational experiments will naturally happen at each company and then the best practice can be shared to the other. Jack wasn&#8217;t aware how much peer executives at each company meet with each other to share learnings, but that seems like an obvious win. </p>\n\n\n\n<p>Readers of this blog will especially appreciate how much we talked about open source and cryptocurrencies, and his view on the three things he&#8217;s responsible for as CEO. <a href=\"https://distributed.blog/2020/12/16/episode-26-jack-dorsey-and-remote-collaboration/\">Give it a listen and let me know what you think</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, 31 Dec 2020 03:18:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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: Understanding the Query Block and Its Importance in 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=109593\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/understanding-the-query-block-and-its-importance-in-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=understanding-the-query-block-and-its-importance-in-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:5285:\"<blockquote class=\"wp-block-quote\"><p>I really don&rsquo;t understand this Query block even though it&rsquo;s been mentioned in several Tavern posts. My eyes seem to gloss over when reading about it &ndash; ha!</p><p>Is it important that regular WordPress users understand this block, or is it really a block for developers?</p><p><a href=\"https://wptavern.com/gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block#comment-357249\">Marcus</a></p></blockquote>\n\n\n\n<p class=\"has-drop-cap\">I have given the Query block a lot of attention as of late. On occasion, I may have even called it one of the largest hurdles the Gutenberg development team has needed to jump before block-based themes become a reality. However, the &ldquo;query&rdquo; WordPress term is not something all users or Tavern readers are familiar with. It is a concept as old as WordPress and generally something that only developers needed to familiarize themselves with. When Full Site Editing lands in WordPress, the new block will expose the Query to far more users as part of the site editor interface.</p>\n\n\n\n<p>It is a block that is currently a part of the Gutenberg plugin but not WordPress core. However, at some point in 2021, more and more end-users and developers will be working with it.</p>\n\n\n\n<p>In WordPress terminology, we are really talking about two things, the Query and the Loop. The Query is defined by a set of arguments or options that determine what posts to display. The Loop is the part of the machine that &ldquo;loops&rdquo; through the queried posts and displays them, one after another. The Query asks for posts; the Loop cycles through them.</p>\n\n\n\n<p>Traditionally, theme authors were responsible for adding the Loop code to their templates, which used the global Query that WordPress supplied. Themes could also create custom queries, such as adding a posts list widget, categorized homepage post sections, or anything. And, &ldquo;posts&rdquo; can be anything from normal blog posts to WooCommerce products to the latest topics from the bbPress plugin.</p>\n\n\n\n<p>The Query may be one of the single most important aspects of WordPress. In essence, it is the engine behind displaying the content of every page on the site. Without it, all WordPress sites would simply be a header and a footer.</p>\n\n\n\n<p>The Gutenberg plugin provides two blocks for the Query:</p>\n\n\n\n<ul><li><strong>Query:</strong> The outer block for setting the options for which posts will show.</li><li><strong>Query Loop:</strong> The inner block, which is automatically added when using Query.</li></ul>\n\n\n\n<p>Currently, users can select between four fairly standard variations when first adding the Query block. They are combinations of the post featured image, title, date, and excerpt.</p>\n\n\n\n<img />Query block variations.\n\n\n\n<p>These can be further customized via the block options panel in the sidebar. Users can also find &ldquo;view&rdquo; options in the toolbar for selecting between List and Grid views. The List view is the traditional list of posts flowing vertically down the page. The Grid view displays posts in two to six columns.</p>\n\n\n\n<img />Grid view of posts while using the Query block.\n\n\n\n<p>The Query block has a basic set of options for which post types to display and how to order them. It has filters for categories, tags, authors, and keywords. The block is not as robust as what is possible with code yet. It is missing some basic options like a post number limit and nearly all of the more advanced parameters. However, it is a promising starting point.</p>\n\n\n\n<p>The more exciting aspects of this feature for end-users may not be the Query block at all. It is customizing the blocks that go inside, which display things like the featured image, post title, and more.</p>\n\n\n\n<p>As a former theme author, I cannot count the number of times users have asked me about customizing some aspect of the posts layout. Having them dive into code to make minor changes, such as removing the post author name or displaying the category in a different place, was not an ideal experience. The site editor will put this power directly into each user&rsquo;s hands.</p>\n\n\n\n<img />Adding post-related blocks to the Query block in Grid view.\n\n\n\n<p>The comment by Marcus was on the Tavern&rsquo;s post covering <a href=\"https://wptavern.com/gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block\">Gutenberg 9.6</a>. The latest version of the plugin introduced global query inheritance for the Query block. This means that theme authors can now replicate the content layer in block-based themes. Previously, pages like archives and search results would simply display the latest posts when a theme used the Query block. Now, each of those pages can display the correct posts.</p>\n\n\n\n<p>However, the Query block is so much more than that. In the hands of users, it can be a powerful tool for creating custom output on a homepage &mdash; think newspaper-style categorized sections. Users can also create post lists in a sidebar, such as the latest forum replies or products. Theme authors can offer templates or block patterns with unique designs or as starting points for end-users to modify. There is no shortage of possibilities.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 30 Dec 2020 23:05: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: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:158:\"WPTavern: GitHub’s 2020 State of the Octoverse Report Highlights: Developers are Working More Hours but Turning to Open Source Projects for Creative Outlets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109613\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:353:\"https://wptavern.com/githubs-2020-state-of-the-octoverse-report-highlights-developers-are-working-more-hours-but-turning-to-open-source-projects-for-creative-outlets?utm_source=rss&utm_medium=rss&utm_campaign=githubs-2020-state-of-the-octoverse-report-highlights-developers-are-working-more-hours-but-turning-to-open-source-projects-for-creative-outlets\";s: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:3644:\"<p>GitHub has published its annual <a href=\"https://octoverse.github.com/\">Octoverse report</a> for 2020. The code hosting platform currently serves more than 56 million developers who created 60+ million new repositories this past year. The volume of work pumping through GitHub&rsquo;s pipes and its preeminence as the world&rsquo;s largest developer platform gives the company access to a trove of data on how people have been working during the pandemic. </p>\n\n\n\n<p>The Productivity report shows that developers have been putting in longer hours as compared to the previous year. It includes data on what time of day people seem to be more productive, as well as minute changes in the volume of work across various time zones and countries with different COVID-19 responses. The graph below tracks the US Pacific Time Zone, showing a spike in the push window and work volume beginning in mid-March with lockdowns. The volume of work remained consistently higher than the previous year.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>GitHub recorded 35% more repositories created than last year and 7.5 hours faster pull request merge times in teams&rsquo; most productive and collaborative weeks.</p>\n\n\n\n<p>Developers seem to be getting more done and GitHub attributes this to people using automation to accelerate their work, improved development practices, and the flexibility of blurring the lines between work and life. The report also cautions that this high volume of work may not be sustainable long-term should be tempered with regular breaks and conscious energy management practices.</p>\n\n\n\n<p>This collection of reports also highlights a few trends in the wider open source community. Alongside a general jump in work volume, GitHub tracked an increase in open source activity on weekends and holidays, at the same time that Enterprise developer activity dropped. Open source project creation is also up by 25% year over year since April 2020.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The data suggests that even when developers conclude their regular work, they are turning to open source projects for creative outlets. These projects often provide meaningful connections and community while the world is stuck at home.</p>\n\n\n\n<p>Based on these findings, GitHub recommends that organizations recognize the importance open source projects hold for employee wellbeing and enrichment when they are contributing outside of work.</p>\n\n\n\n<p>The State of the Octoverse also includes reports on Community and Security. GitHub found that 17% of the vulnerabilities hosted on its platform were explicitly malicious but triggered just 0.2% of alerts. The remaining 83% of vulnerabilities were the result of mistakes. The company found that vulnerabilities are fixed 1.4x faster when repositories are set up to automatically generate a pull request when a patch is available.</p>\n\n\n\n<p>In 2020, the average time for vulnerabilities to go undetected before being identified is four years for GitHub-hosted repositories. On average, it takes 4.4 weeks for the community to code and release a fix, and 10 weeks to alert the community on the availability of a security update. Once notified, users generally apply the update within one week.</p>\n\n\n\n<p>GitHub reports that its community is becoming more diverse as those who identify as developers have decreased from 60% in 2016 to 54% in 2020. Profiles related to education are growing (up from 17% in 2016 to 23% in 2020), followed by users working in data. The platform is becoming more approachable for collaborators who do not come from a development background. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 30 Dec 2020 07:08:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:94:\"WPTavern: Armando WordPress Theme Provides Insight Into the Current State of 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=109503\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/armando-wordpress-theme-provides-insight-into-the-current-state-of-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=armando-wordpress-theme-provides-insight-into-the-current-state-of-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:5271:\"<p class=\"has-drop-cap\">As we inch closer to a year in which <a href=\"https://wptavern.com/what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress\">WordPress&rsquo;s primary focus</a> will be on Full Site Editing, it is fortunate timing that Themes Team representative Carolina Nymark publicly <a href=\"https://twitter.com/carolinapoena/status/1343541924028968963\">announced her latest theme</a>, Armando. It is a blogging theme that makes use of the latest features from the Gutenberg plugin.</p>\n\n\n\n<p>The theme is currently <a href=\"https://themes.trac.wordpress.org/ticket/93476\">awaiting review</a> for the WordPress theme directory. It is also <a href=\"https://github.com/carolinan/fullsiteediting/tree/course/armando\">available via GitHub</a>.</p>\n\n\n\n<p>The news of Armando came moments after Nymark <a href=\"https://twitter.com/carolinapoena/status/1343538279346544643\">announced a redesign</a> of her <a href=\"https://fullsiteediting.com/\">Full Site Editing</a> website. The site is a resource for WordPress users and developers to learn more about upcoming features. It is built entirely out of blocks. It is also one of the few sites in the wild running a block-based theme in production.</p>\n\n\n\n<p>Armando is one of the better themes for testing Full Site Editing. This should come as no surprise. Nymark is a veteran of the Themes Team. She tends to cover all the bases and has done so with this theme. There are even notes in the code where she intends to change things as site editing improves.</p>\n\n\n\n<p>The theme is a solid starting point for theme authors who have yet to dip their toes into block-based theme development. It is also usable enough for end-users who want to experience the current state of Full Site Editing.</p>\n\n\n\n<img />Editing a single post template in the site editor.\n\n\n\n<p>The theme does not have a particular artistic flair. It is simple. It is a basic blogging theme that showcases each element the Gutenberg team has covered thus far in its journey toward the new block-based design system.</p>\n\n\n\n<p>Armando also uncovers some of the current problems with the system. As Nymark noted in her stylesheet, &ldquo;Date and categories are all block elements, we need to adjust them to align them better next to each other.&rdquo; On the front end, the theme&rsquo;s CSS adjusts these block-level elements to correctly line up with each other. However, as seen in the site editor view, they are separated as blocks. Post metadata like the author, date, and category often need to be inline. This choice for aligning basic elements of theme design also needs to exist in the site editor. That is if we ever want theme authors to adopt it. <em>And, we haven&rsquo;t even gotten to the complicated stuff yet.</em></p>\n\n\n\n<p>Armando is one of the first block-based themes I have seen to include a 404 template. This is important because it is one reason the site editor needs to exist in WordPress. Throughout all of the platform&rsquo;s history, there was no standard way for users to edit their 404 page, which is the page visitors see when they travel to an invalid URL on a site.</p>\n\n\n\n<img />Editing the 404 template \n\n\n\n<p>Landing on a 404 page on most WordPress sites is one of the worst user experiences a site visitor can have on the web. Traditionally, themes might have added some unhelpful text, a search box, and maybe a list of recent posts. But, most users had no control over it unless they directly edited their theme&rsquo;s code. They could not add a bit of pizzazz, personalized messages, or more meaningful directions for the visitor who stumbled upon the page through no fault of their own. Some themes have provided workarounds for this over the years. Such solutions have included allowing users to assign a private page or adding customizer options. However, changing themes meant losing that 404-page customization because it was a non-standard solution.</p>\n\n\n\n<p>Full Site Editing changes that. Users will have direct access to creating a custom 404 page that best suits their site. It is nice that the Armando theme already includes a template to start from.</p>\n\n\n\n<p>The Armando theme also includes three different header templates for users to switch between. This could offer some insight into how theme authors may tackle design choices in the future. Traditional themes often have numerous checkboxes, input fields, and dropdowns for changing such design elements. Selectable template parts could be the alternative.</p>\n\n\n\n<img />Switching the header template part.\n\n\n\n<p>I lean more toward seeing theme authors using block patterns rather than templates for this. However, WordPress needs to add a method for designating patterns on specific editing screens (e.g., post editor vs. site editor). In the long run, the patterns UI feels like it will be a better place. That is assuming it ever receives an <a href=\"https://wptavern.com/proposal-to-create-an-expanded-view-or-overlay-for-the-block-patterns-inserter\">expanded view or overlay option</a>.  There may be solutions where patterns and template parts merge as well.</p>\n\n\n\n<p>Either way, this type of experimentation is what we need to see in the WordPress theme development world at the moment. I welcome more of it.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Dec 2020 22:37: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:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: AMP Under Fire in New Antitrust Lawsuit Against Google\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109265\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:173:\"https://wptavern.com/amp-under-fire-in-new-antitrust-lawsuit-against-google?utm_source=rss&utm_medium=rss&utm_campaign=amp-under-fire-in-new-antitrust-lawsuit-against-google\";s: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:6515:\"<p><a href=\"https://amp.dev/\">AMP</a> (Accelerated Mobile Pages), an open source initiative that originated with Google, is coming under greater scrutiny at the tail end of 2020, as the company is facing a rash of antitrust lawsuits beginning in October. The second suit is the one most pertinent to the AMP project. (A third suit brought by 38 state attorneys general alleges that Google is operating an illegal monopoly for online search and search advertising.)</p>\n\n\n\n<p>The second suit is led by Texas Attorney General Ken Paxton and nine other state attorneys general. It alleges that AMP was created for the purpose of pushing publishers away from &ldquo;header bidding,&rdquo; an advertising mechanism that allows sites to route their ad inventory through several ad exchanges and sell the space to the highest bidder. Header bidding requires JavaScript and therefore doesn&rsquo;t play well with AMP.</p>\n\n\n\n<p>The <a href=\"https://www.texasattorneygeneral.gov/sites/default/files/images/admin/2020/Press/20201216%20COMPLAINT_REDACTED.pdf\">complaint</a> claims that &ldquo;Google&rsquo;s program secretly let its own<br />exchange win, even when another exchange submitted a higher bid.&rdquo; It also alleges that &ldquo;Google ad server employees met with AMP employees to strategize about using AMP to impede header bidding, and how much pressure publishers and advertisers would tolerate:&rdquo; </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>First, Google restricted the code to prohibit publishers from routing their bids to or sharing their user data with more than a few exchanges a time, which limited AMP compatibility with header bidding. At the same time, Google made AMP fully compatible with routing to exchanges through Google. Google also designed AMP to force publishers to route rival exchange bids through Google&rsquo;s ad server so that Google could continue to peek at rivals&rsquo; bids and trade on inside information. Third, Google designed AMP so that users loading AMP pages would make direct communication with Google servers, rather than publishers&rsquo; servers. This enabled Google&rsquo;s access to publishers&rsquo; inside and non-public user data. AMP pages also limit the number of ads on a page, the types of ads publishers can sell, as well as enriched content that publishers can have on their pages.</p></blockquote>\n\n\n\n<p>There are many more claims about collusion with Facebook and other anti-competitive practices, but the section regarding AMP may be of particular interest to publishers who are considering implementing it:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Google falsely told publishers that adopting AMP would enhance load times, but Google employees knew that AMP only improves the [redacted] and AMP pages can actually [redacted] [redacted] [redacted]. In other words, the ostensible benefits of faster load times for cached AMP version of webpages were not true for publishers that designed their web pages for speed. Some publishers did not adopt AMP because they knew their pages actually loaded faster than AMP pages.</p><p>Google also [redacted]&nbsp;<em>of non-AMP ads by giving them artificial one second delays</em>&nbsp;in order to give Google AMP a [redacted] [redacted] slows down header bidding, which Google uses to turn around and denigrate header bidding for being too slow.</p></blockquote>\n\n\n\n<p>The complaint references internal documents that demonstrate how AMP is an inferior product when compared to the options previously available to publishers:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Google gave publishers a Faustian bargain: (1) publishers could lose more money by using header bidding because Google Search would suppress their search rankings and send traffic to competing AMP-compatible publishers; or (2) publishers could lose less money by using AMP pages and forgoing exchange competition in header bidding. Either option was far inferior to the options available to publishers before AMP was introduced. Just how inferior? [redacted] [redacted] [redacted] according to internal Google documents.</p></blockquote>\n\n\n\n<p>Just 48 hours after this lawsuit was filed, AMP Advisory Committee member Terence Eden <a href=\"https://shkspr.mobi/blog/2020/12/i-have-resigned-from-the-google-amp-advisory-committee/\">resigned</a> from his position as a non-corporate representative. </p>\n\n\n\n<p>The <a href=\"https://github.com/ampproject/meta-ac/blob/master/WORKING_MODE.md#goal-of-the-ac\">goal of the AMP AC</a> is to &ldquo;Make AMP a great web citizen,&rdquo; but Eden declined to nominate a replacement candidate, because he is concerned that &ldquo;Google has limited interest in that goal.&rdquo;</p>\n\n\n\n<p>&ldquo;Google&rsquo;s thesis is that the mobile-web is dying and people prefer to use apps &ndash; therefore making the web faster and more app-like will retain users,&rdquo; Eden wrote.&nbsp;&ldquo;<a href=\"https://github.com/ampproject/meta-ac/issues/32\">Google doesn&rsquo;t publish data about this</a>, so I can&rsquo;t directly criticize their motives. But I do not think AMP, in its current implementation, helps make the web better.</p>\n\n\n\n<p>&ldquo;I remain convinced that AMP is poorly implemented, hostile to the interests of both users and publishers, and a proprietary and unnecessary incursion into the open web.&rdquo;</p>\n\n\n\n<p>In a follow-up email to&nbsp;<em><a href=\"https://www.theregister.com/2020/12/19/google_amp_resignation\">The Register</a></em>, Eden&nbsp;said, &ldquo;I don&rsquo;t know what Google&rsquo;s motives are. But AMP has not been responsive to the needs of users, publishers, or the web community. We need an open, standards based approach to the web.&rdquo;</p>\n\n\n\n<p>Where will AMP go in 2021? Publishers have already invested a lot of resources in order to comply with its proprietary subset of HTML. Smaller sites often lack the resources to support AMP, which may be one reason why Google began investing heavily in developing <a href=\"https://profiles.wordpress.org/google/#content-plugins\">WordPress plugins</a> that make its products easier to use. More than 500,000 WordPress site are now using the official <a href=\"https://wordpress.org/plugins/amp/\">AMP plugin</a>.</p>\n\n\n\n<p>Google has spent years clawing for greater AMP adoption, despite widespread criticism that the project is a threat to the open web. Every last bit of that effort is now in jeopardy if the complaints in the antitrust lawsuits and their supporting documents are found to be true.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Dec 2020 05:43:57 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"WPTavern: Navigate the Content Canvas With the Block Editor Outline 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=109480\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/navigate-the-content-canvas-with-the-block-editor-outline-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=navigate-the-content-canvas-with-the-block-editor-outline-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:4173:\"<p class=\"has-drop-cap\">Last week, Kalimah Apps released its <a href=\"https://wordpress.org/plugins/editor-block-outline/\">Editor Block Outline</a> plugin to the WordPress plugin repository. The idea is simple. The plugin adds a bordered outline to each block in the document along with their associated labels. For some users, this will help them navigate more complex layouts.</p>\n\n\n\n<p>There is little information available about Kalimah Apps through the usual WordPress-related channels. However, this is its second plugin in the directory. Its first plugin, which has not been updated in four years, was a massive library of over 40 shortcodes, 1,000s of icons, and dozens of animations. Editor Block Outline is much more scaled back and lean.</p>\n\n\n\n<p>The plugin adds a new sidebar panel to the editor. Its icon, located in the upper right of the screen, looks like a picture frame. It has several options to allow users to personalize the experience, such as what contexts to show the outline and whether to show the block name. The latter option is sometimes best disabled when inserting blocks with many inner blocks. Otherwise, the interface may look a bit cluttered.</p>\n\n\n\n<p>Users can also select an outline color, border style, and opacity. I recommend knocking opacity down below 50% for more of a <em>guideline</em> look, something that is visible but does not feel like it is a part of the content.</p>\n\n\n\n<img />Selecting outline options for Editor Block Outline.\n\n\n\n<p>All of the settings are stored as user metadata. Using this data storage method means that each user can decide how they want to use this plugin. Or, they can even disable it altogether. Because it is stored this way, settings will carry over from one post to the next.</p>\n\n\n\n<p>&ldquo;Do you want to know the feeling of driving while drunk, or to move around with blinders on? Then use Gutenberg without this plugin!!!&rdquo; That is how one user <a href=\"https://wordpress.org/support/topic/works-perfectly-2168/\">reviewed this plugin</a>. While I may not describe the default editor quite so &mdash; ahem &mdash; <em>eloquently</em>, this plugin does solve some problems, particularly when you need to more easily click around the interface.</p>\n\n\n\n<p>As Brian Gardner <a href=\"https://twitter.com/bgardner/status/1329543944401801227\">joked on Twitter</a>, selecting some blocks like Columns is tedious work or a fun game of whack-a-mole:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Live footage of me trying to select the main Columns block in WordPress to increase the number. <a href=\"https://t.co/Fud3DLQ4VH\">pic.twitter.com/Fud3DLQ4VH</a></p>&mdash; Brian Gardner (@bgardner) <a href=\"https://twitter.com/bgardner/status/1329543944401801227?ref_src=twsrc%5Etfw\">November 19, 2020</a></blockquote>\n</div>\n\n\n\n<p>Of course, there are ways around that, such as using the navigation tree, breadcrumbs, or keyboard commands. However, the block editor is meant to be a visual interface that allows end-users to simply point and click on the elements they wish to edit. Selecting specific blocks has generally improved over time, but users still run into issues. Editor Block Outline makes it a much simpler affair.</p>\n\n\n\n<img />Selecting the Columns block.\n\n\n\n<p>In Full Site Editing (FSE) mode with the Gutenberg plugin enabled, the plugin did not hold up quite as well. Depending on the theme in use, the blocks&rsquo; text labels were sometimes huge or did not match across the canvas. The plugin&rsquo;s icon was also not available on the site editor screen.</p>\n\n\n\n<p>FSE is still in beta. The plugin cannot be expected to work with it yet. However, this is where I imagine the plugin will make the most sense for many users. In the post editor, it would get in the way of writing long-form posts. However, the plugin could become an invaluable tool for navigating complex layouts in both the post and site editors.</p>\n\n\n\n<p>More than anything, the reason I like Editor Block Outline is its dedication to a singular purpose. It adds a simple feature that enhances the editor without taking on too large of a role.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 28 Dec 2020 21:05: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:\"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: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:46:\"BuddyPress: BuddyPress in 2020, it’s a wrap!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=316282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:61:\"https://buddypress.org/2020/12/buddypress-in-2020-its-a-wrap/\";s: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:9203:\"<p>Hello dear members of the BuddyPress community,</p>\n\n\n\n<p>For this last day of 2020, we are inaugurating our very first End of Year wrap-up post. We believe it&#8217;s a good way to congratulate ourselves (<em>the whole BuddyPress community</em>) about the free &amp; priceless hard work we&#8217;ve all put together into our open source project.</p>\n\n\n\n<p>There are many ways we are <a href=\"https://codex.buddypress.org/participate-and-contribute/\">getting involved</a> into BuddyPress and we all know the best way to maintain BuddyPress in the long term is to give some of our spare time to carry on bringing that little piece to the project. Every contribution makes a difference.</p>\n\n\n\n<p>Let&#8217;s thank us all, the users, the support forum moderators, the documentation writers, the translators, the theme designers, the plugin developers &amp; the BuddyPress Core committers team. We have built great community features all along the 2020 year.</p>\n\n\n\n<p class=\"has-text-align-center has-huge-font-size\"><img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f44f.png\" alt=\"?\" class=\"wp-smiley\" /></p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>Here are our results:</h2>\n\n\n\n<h3>2020 releases</h3>\n\n\n\n<ul><li>9 releases (3 more than in 2019)</li><li><strong>2 major releases</strong> (1 more than in 2019)</li><li>7 minor releases (2 more than in 2019)</li></ul>\n\n\n\n<h3>2020 Tickets</h3>\n\n\n\n<ul><li>We&#8217;ve fixed 186 tickets, it&#8217;s <strong>62% more than in 2019</strong>.</li><li>The 6.0.0 release (May 2020) was the one which fixed the most tickets for 2 years (89).</li><li>Comparing to 2019, we&#8217;ve increased the fixed tickets per release average from 14 to 23.</li></ul>\n\n\n\n<h3>2020 Code contributors</h3>\n\n\n\n<ul><li>7.0.0 gathered the highest number of contributors for 2 years. We were <strong>55</strong> involved into the making of this release. It&#8217;s almost twice the number of contributors the 5.0.0 release got in 2019.</li><li>For each release we are an average of 14 contributors per release. In 2019 we were 9 contributors. <strong>Contributions to the BuddyPress project grew by 40% in 2020</strong>.</li></ul>\n\n\n\n<h3>2020 Downloads</h3>\n\n\n\n<ul><li>Most important spike for 2 years happened in 2020 for the 7.0.0 releases: <strong>34.236 downloads</strong> on December 11.</li><li>BuddyPress was downloaded more than 1.257.556 times in 2020 (the year is not finished yet <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f60c.png\" alt=\"?\" class=\"wp-smiley\" />).</li><li><strong>The growth ratio is 23% compared to 2019</strong>.</li></ul>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>Here are our achievements:</h2>\n\n\n\n<h3>Acknowledging <a href=\"https://translate.wordpress.org/projects/wp-plugins/buddypress/contributors/\">Polyglots contributions</a></h3>\n\n\n\n<p>Making BuddyPress available in as many languages as possible is very important to ensure the best user experience of the plugin features. We are always trying to improve how we credits translators and ease their tasks. During the 6.0.0 release, we&#8217;ve reviewed all the strings needing translators comments to explain the meaning of the placeholders we use (e.g.: <code>%s</code>, <code>%d</code>, <code>%1$s</code>, etc.).</p>\n\n\n\n<p>We&#8217;ve also decided to include, from now on, into major release credits the translation contributor names that have given their times to make sure the development (Trunk) translation is 100% ready once our major releases final string freeze step is over. <strong>This work is strategic to BuddyPress users</strong> as they will be able to get the new strings translation as soon as they upgrade or install the plugin.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Easing &amp; welcoming code contributions</h3>\n\n\n\n<p>At the end of 2019, we&#8217;ve made available a <a href=\"https://wordpress.org/plugins/bp-beta-tester/\">new plugin to ease beta-testing</a>, this year we&#8217;ve added the <code><a href=\"https://developer.wordpress.org/block-editor/packages/packages-env/\">@wordpress/env</a></code> package to our development version (Trunk) and <a href=\"https://codex.buddypress.org/participate-and-contribute/contribute-with-code/\">wrote a tutorial</a> about how you can easily set up a development environment to play with BuddyPress code thanks to it. We believe it&#8217;s an important step towards making contributing to BuddyPress easier and we hope it will increase the number of people getting involved into BuddyPress source code improvements.</p>\n\n\n\n<p>Before starting the 7.0.0 development cycle and just like the WordPress Core team does before each major milestone, we&#8217;ve published <a href=\"https://bpdevel.wordpress.com/2020/05/27/buddypress-7-0-0-call-for-tickets/\">our first &#8220;Call for tickets&#8221;</a>. We&#8217;ll do it before each major release so that you can share with the BuddyPress Core committers the tickets you think should be fixed for the next development cycle. <strong>The priorities of the BuddyPress community matter</strong>, we encourage you to use this call for tickets to make your voice heard.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Informing BuddyPress Theme &amp; Plugin authors about important changes</h3>\n\n\n\n<p>During the 6.0.0 development cycle we (<em>re</em>)started to take the time to write developer notes as soon as possible. We also organized these notes into categories according to the version number of the release being built.</p>\n\n\n\n<ul><li>To prepare 6.0.0, we&#8217;ve published <a href=\"https://bpdevel.wordpress.com/category/development-notes/6-0/\">4 notes</a>,</li><li>To prepare 7.0.0, we&#8217;ve published <a href=\"https://bpdevel.wordpress.com/category/development-notes/7-0/\">9 notes</a>.</li></ul>\n\n\n\n<p>Our goals doing so is to limit the risk of &#8220;breaking&#8221; your active theme or plugins keeping their authors aware of changes they should check before a major release is published. It can also help developers to start working early on extending BuddyPress new features. Please do read these notes and share them with your networks to increase their audience and contribute to cover this risk.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Checking how you use BuddyPress and what are your needs:</h3>\n\n\n\n<p>BuddyPress surveys are back! <strong>BuddyPress is about users</strong>: we are very happy we could organize the <a href=\"https://buddypress.org/2020/12/buddypress-2020-survey-results/\">2020 survey</a> to get you inputs about your BuddyPress usage and about the specific directions for the plugin we are thinking of for its future.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Introducing new community features to the BuddyPress plugin:</h3>\n\n\n\n<ul><li>The BP REST API welcomed 6 new endpoints to help you build great interactions from your applications about: Blogs, Blog avatar, Friends, Group Cover Image, Member Cover Image, and User Signups.</li><li>5 BuddyPress blocks have landed into the BuddyPress blocks category of your WordPress Block Editor.</li><li>New Administration screens to manage BuddyPress Types (Member &amp; Group ones) are now available within your WordPress Dashboard. </li><li>Just like Members &amp; Groups, the Blogs component can now enjoy a new default avatar for Sites.</li><li>A great 2.0 version of BP WP CLI to help you manage your BuddyPress site right from the command lines.</li><li>And many fixes and improvements about the existing features (See <a href=\"https://codex.buddypress.org/releases/version-6-0-0/\">6.0.0</a> &amp; <a href=\"https://codex.buddypress.org/releases/version-7-0-0/\">7.0.0</a> release notes)</li></ul>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3>Starting side projects:</h3>\n\n\n\n<ul><li>A new design for the BuddyPress.org network</li><li><a href=\"https://github.com/buddypress/bp-blocks/pull/7\">Block based Activity Post Form</a>.</li><li>Migrating the <a href=\"https://bpdevel.wordpress.com/\">Developer Updates blog</a> from WordPress.com to BuddyPress.org (See <a href=\"https://buddypress.trac.wordpress.org/ticket/5525#comment:11\">#5525</a>).</li></ul>\n\n\n\n<p>If one of these projects is interesting you, don&#8217;t hesitate to contribute to it.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>2021 Goals</h2>\n\n\n\n<p>Based on the discussions the Core Team had during our development meetings (every other Wednesday at 19:00 UTC in <a href=\"https://wordpress.slack.com/messages/buddypress\">#BuddyPress</a>), here&#8217;s a list of directions we mostly agree on about: </p>\n\n\n\n<ul><li>A fantastic standalone BuddyPress theme.</li><li>BuddyPress code reference.</li><li>A BuddyPress Attachments component.</li><li>Improve ways to get help about &amp; for BuddyPress.</li></ul>\n\n\n\n<p><strong>Let&#8217;s try to make them concrete in 2021!</strong></p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<p><em>Thanks for reading this post and for your involvement in contributing to BuddyPress in 2020. Let&#8217;s wish us all a great new year&#8217;s eve <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f389.png\" alt=\"?\" class=\"wp-smiley\" />. Bye 2020 and Happy 2021, full of great contributions, to the BuddyPress community.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 28 Dec 2020 19:29: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:12:\"Mathieu Viet\";s: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:28:\"Matt: 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=53321\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://ma.tt/2020/12/sotw-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:1319:\"<p>This tumultuous year, two things really helped me get through it: my colleagues at <a href=\"https://automattic.com/\">Automattic</a> and the community of <a href=\"https://wordpress.org/\">WordPress</a>. </p>\n\n\n\n<p>At the end of the year I usually deliver a speech to the WP community we call the State of the Word, that celebrates what we accomplished the previous year and shines a light on what we could focus on in the coming year. There&#8217;s always a great energy in the room and I love mixing with the audience before and after the talk. This year we did it online, which meant we could produce the talk a little more, and we made extra time for the Q&amp;A afterward with answers not just from me but folks across the community. </p>\n\n\n\n<p>One thing I&#8217;ll call out <a href=\"https://wordpress.org/news/2020/12/simone/\">WordPress 5.6</a> had an all women and non-binary release squad of over 50 people, a first for WordPress and probably any large open source project. Also the <a href=\"https://w3techs.com/technologies/history_overview/content_management/all/y\">market share of WordPress</a> grew more in 2020 than it has in any year since it started being tracked!</p>\n\n\n\n<p>If you&#8217;re curious about what&#8217;s next for WordPress, check it out:</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:\"Sun, 27 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: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:115:\"WPTavern: Google to Migrate Structured Data Testing Tool to New Domain after Backlash from Deprecation Announcement\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109332\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:275:\"https://wptavern.com/google-to-migrate-structured-data-testing-tool-to-new-domain-after-backlash-from-deprecation-announcement?utm_source=rss&utm_medium=rss&utm_campaign=google-to-migrate-structured-data-testing-tool-to-new-domain-after-backlash-from-deprecation-announcement\";s: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:2781:\"<p>Google&rsquo;s <a href=\"https://search.google.com/test/rich-results\">Rich Results Test</a> came <a href=\"https://developers.google.com/search/blog/2020/07/rich-results-test-out-of-beta\">out of beta</a> in July with support for all Google Search rich result features like carousels, images, or other non-textual elements. At that time, Google announced it would be deprecating the <a href=\"https://search.google.com/structured-data/testing-tool/u/0/\">Structured Data Testing Tool</a>, which SEOs, developers, and site owners have relied on for testing structured markup and troubleshooting schema issues.</p>\n\n\n\n<p>The SEO community reacted strongly to this change, because the Rich Results Test only validates structured data that is supported by Google. It also does not provide much useful feedback on errors. </p>\n\n\n\n<p>&ldquo;This is awful,&rdquo; SEO consultant Barry Adams said in response to the change. &ldquo;The SDTT is a tool that validates ALL schemas and helps make the web a semantically richer place. The RR test only supports a tiny narrow subset of Google-approved schemas. You&rsquo;re downgrading the web with this move.&rdquo;</p>\n\n\n\n<p>When Google <a href=\"https://twitter.com/googlesearchc/status/1280507131318460418\">announced</a> the Structured Data Testing Tool&rsquo;s deprecation on Twitter, comments from various web professions indicated widespread disappointment in the decision.</p>\n\n\n\n<p>&ldquo;The new tool is painfully slow,&rdquo; digital marketing consultant Ian Lurie said. &ldquo;The old tool showed a structured data result for the URL tested above. It provided useful feedback and supported industry-wide standardization. The truth is, you&rsquo;re replacing a great structured data tool for an inferior Google-specific one.&rdquo;</p>\n\n\n\n<p>After taking note of all the negative feedback, Google <a href=\"https://developers.google.com/search/blog/2020/12/structured-data-testing-tool-update\">announced</a> last week that it will no longer be deprecating the tool. Instead, the company plans to migrate it to a new domain:  </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>To better support open standards and development experience, we&rsquo;re refocusing the Structured Data Testing Tool and migrating it to a new domain serving the schema.org community by April 2021. The main purpose of the tool will be to check syntax and compliance of markup with schema.org standards.&nbsp;</p></blockquote>\n\n\n\n<p>Google is making some changes to the tool to differentiate it from the Rich Results Test. The Structured Data Testing tool will not be able to check for Google Search rich result types. It will be refocused to validate only schema.org properties, and is recommended for validating types that Google Search doesn&rsquo;t yet consume.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 23:56:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:61:\"WPTavern: Learn WordPress Launches Trac Introductory Workshop\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109334\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:167:\"https://wptavern.com/learn-wordpress-launches-trac-introductory-workshop?utm_source=rss&utm_medium=rss&utm_campaign=learn-wordpress-launches-trac-introductory-workshop\";s: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:2230:\"<p>Jonathan Desrosiers, a WordPress core committer and software engineer at Bluehost, has published a new workshop titled &ldquo;<a href=\"https://learn.wordpress.org/workshop/how-to-use-trac/\">How to Use Trac</a>&rdquo; on the <a href=\"https://learn.wordpress.org/\">Learn WordPress</a> platform. The 20-minute video offers a crash course on  the ticket tracking software that WordPress relies on to manage core development. Trac is also used for contributing to <a href=\"https://meta.trac.wordpress.org/\">WordPress&rsquo; meta</a> component, which includes WordPress.org sites and API, directories, support areas, and other projects.</p>\n\n\n\n<p>Trac&rsquo;s antiquated UI can be intimidating for newcomers, posing another barrier to contribution. Even experienced WordPress contributors are eager to move core development to GitHub or some other platform. It can get confusing since bugs related to the editor need to be reported on GitHub instead of Trac. Until WordPress adopts another platform, the ability to navigate Trac remains an important skill.</p>\n\n\n\n<p>Desrosiers&rsquo; workshop covers topics like searching for pre-existing tickets before reporting a new issue, how to write a good bug report or feature request, how to identify component maintainers, attaching patches, and how proper classification of the ticket can help other teams get involved. He also helps workshop students understand ticket resolutions so they can frame their expectations accordingly. This video includes a full walkthrough of creating a new ticket where Desrosiers explains each field on the form. </p>\n\n\n\n<p>Once you get up to speed on learning Trac and start contributing, you may also want to follow the <a href=\"https://twitter.com/wordpresstrac\">WordPress Trac on Twitter</a>. New contributors may also want to explore <a href=\"https://wptavern.com/wptracsearch-an-elasticsearch-powered-search-interface-for-wordpress-trac-tickets\">WPTracSearch</a>, an unofficial project that provides an alternative Elasticsearch-powered interface for searching WordPress Trac tickets. WPTracSearch delivers more accurate results, even for basic queries, that can be filtered based on milestone, component, focuses, usernames, and more criteria.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 21:38: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: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:98:\"WPTavern: Gutenberg 9.6 Introduces Drag-and-Drop Blocks and Global Inheritance for the Query Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109323\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:241:\"https://wptavern.com/gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-6-introduces-drag-and-drop-blocks-and-global-inheritance-for-the-query-block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5098:\"<p class=\"has-drop-cap\">For some people, Christmas arrived a couple of days early. <a href=\"https://make.wordpress.org/core/2020/12/23/whats-new-in-gutenberg-23-december/\">Gutenberg 9.6 launched</a> with its first iteration of drag-and-drop blocks from the inserter. There are some other enhancements like <a href=\"https://github.com/WordPress/gutenberg/pull/27297\">vertical buttons</a>, heaps of bug fixes, new APIs, and other improvements. But, let&rsquo;s be real. The ability to drag blocks from the inserter into the content canvas is the highlight of this release.</p>\n\n\n\n<p>Another key feature is that the Query block, which is only available when Full Site Editing is enabled, now <a href=\"https://github.com/WordPress/gutenberg/pull/27128\">inherits from the global query arguments</a>. As has been usual as of late, much of the work in the Gutenberg plugin has focused on improving the site editor.</p>\n\n\n\n<h2>Drag Blocks Into the Content Canvas</h2>\n\n\n\n<img />Dragging a block from the inserter and dropping it between paragraphs.\n\n\n\n<p class=\"has-drop-cap\">Perhaps the Gutenberg development team has <a href=\"https://wptavern.com/wordpress-5-7-development-kicks-off-with-focus-on-full-site-editing#comment-357130\">seen</a> <a href=\"https://wptavern.com/proposal-to-create-an-expanded-view-or-overlay-for-the-block-patterns-inserter#comment-353059\">your</a> <a href=\"https://wptavern.com/google-search-to-add-page-experience-to-ranking-signals-in-may-2021#comment-351977\">comments</a> and <a href=\"https://wptavern.com/gutenberg-9-0-brings-major-improvements-to-navigation-screen-and-query-block#comment-344463\">your</a> <a href=\"https://wptavern.com/wordpress-5-6-wish-list-homepage-post-type-selection-and-block-management#comment-336374\">other</a> <a href=\"https://wptavern.com/gutenberg-8-5-adds-single-gallery-image-editing-allows-image-uploads-from-external-sources-and-improves-drag-and-drop#comment-334299\">comments</a>. If there is one common thread among the comments on our Gutenberg-related posts, it is that a segment of the WordPress user base wants more drag-and-drop capabilities.</p>\n\n\n\n<p>The new feature only works with blocks right now. Users cannot yet drag and drop patterns from the inserter.</p>\n\n\n\n<p>After several tests since Gutenberg 9.6 Release Candidate 1 landed last week, I have had no issues with it. For the most part, the experience felt smooth and easy to use.</p>\n\n\n\n<p>I have never seen the allure of drag-and-drop features in a content editor. If I am not typing in Markdown, I am in the WordPress editor and using keyboard shortcuts. Throughout my career, I have either been writing code or writing words daily. Picking up my fingers from the keyboard only serves to waste time.</p>\n\n\n\n<p>Sometimes I forget that the block editor already has some drag-and-drop capabilities available, which allow end-users to move blocks from one position to another in the canvas. I tend to work with the top toolbar enabled, so I rarely see the feature.</p>\n\n\n\n<p>Nevertheless, I do see how dragging and dropping blocks could be useful to some users. I use them in other types of editors, such as Gimp or Photoshop, at times. The one thing I like about those is the toolset is always available in the sidebar. This is not the case with the block inserter. While it will stay open for users to drag multiple elements into their content, it disappears once users begin working elsewhere. That could become irritating if the user is in more of a visual-design workflow instead of a content-editing mode.</p>\n\n\n\n<p>Dragging blocks from the inserter would make more sense for my workflow in the upcoming site editor rather than the post editor. The feature works great in that context too.</p>\n\n\n\n<h2>Query Block Supports Inheriting the Global Query Arguments</h2>\n\n\n\n<img />Inheriting the Query block&rsquo;s options from the URL.\n\n\n\n<p class=\"has-drop-cap\">The low-key star of this release is an update to the Query block, which is only available when using a block-based theme. The update is one of the most important breakthroughs for Full Site Editing, a pivotal moment in the history of the Gutenberg project.</p>\n\n\n\n<p>In previous iterations, the Query block required that themes via their block templates or end-users via the site editor define which posts to display. While that is a necessary function of the block, the missing piece was the global query support.</p>\n\n\n\n<p>In the simplest terms, whatever URL a visitor lands upon tells WordPress which posts to load. The data for loading these posts is all stored in a global set of query arguments. Themes can then loop through these posts to display them.</p>\n\n\n\n<p>In Gutenberg 9.6, the Query block can now inherit these query arguments. This means that things like the blog posts page, category archives, search results, and more will display the correct posts when someone visits one of those specific URLs.</p>\n\n\n\n<p>On the surface, this change merely adds a single option to the interface. However, under the hood, it is a achievement that clears a gaping path for developing 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:\"Wed, 23 Dec 2020 20:16:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:79:\"WPTavern: Exploring Photo Blocks, an Experimental FSE-Ready Photoblogging Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109274\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/exploring-photo-blocks-an-experimental-fse-ready-photoblogging-theme?utm_source=rss&utm_medium=rss&utm_campaign=exploring-photo-blocks-an-experimental-fse-ready-photoblogging-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4979:\"<p class=\"has-drop-cap\">Kjell Reigstad announced the <a href=\"https://github.com/WordPress/theme-experiments/tree/master/photo-blocks\">Photo Blocks</a> theme on December 9. It is a part of an ongoing set of experimental work from the WordPress <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments</a> repository on GitHub. It is essentially a testbed of ideas that are helping to propel the upcoming block-based theming era.</p>\n\n\n\n<p>In the past few months, I have covered the repository&rsquo;s <a href=\"https://wptavern.com/carrd-like-theme-experiment-provides-a-glimpse-into-the-future-of-theming\">Carrd-like landing page theme</a>, <a href=\"https://wptavern.com/twenty-twenty-one-blocks-theme-launching-as-a-separate-project\">Twenty Twenty-One Blocks</a>, and the Full Site Editing (FSE) <a href=\"https://wptavern.com/jump-start-block-based-theme-development-with-the-fse-theme-generator\">Theme Generator</a>. There is a lot of movement happening in the repository that theme developers would be remiss to overlook.</p>\n\n\n\n<p>&ldquo;I built a new block-based photoblog theme in the experiments repo,&rdquo; Reigstad <a href=\"https://twitter.com/kjellr/status/1336697938538618882\">tweeted</a> just a couple of weeks ago. &ldquo;It&rsquo;s refreshing to see how well this works just with existing FSE tools.&rdquo;</p>\n\n\n\n<p>Like most FSE-capable themes currently making the rounds, it is simple. There are miles left before block-based themes and the upcoming site editor reach maturity. Photo Blocks showcases yet another step in the evolution of the system.</p>\n\n\n\n<img />Posts page view of Photo Blocks in the site editor.\n\n\n\n<p>The theme uses the Query block&rsquo;s new grid view, which was added in <a href=\"https://wptavern.com/gutenberg-9-5-improves-site-editor-and-adds-new-options-for-cover-and-code-blocks\">Gutenberg 9.5</a>. The Query block is one of the most important pieces of the Full Site Editing system. Like in traditional themes, the query and &ldquo;the loop&rdquo; output posts on the front end.</p>\n\n\n\n<p>The addition of the grid view allows themes to output their posts in columns. This is a nice addition for Photo Blocks and other photoblogging or portfolio themes. Currently, the Query block supports only a second type of view, the default list of posts. It all seems to limit design possibilities right now, but the grid option does provide some hope that more robust tools are coming.</p>\n\n\n\n<p>The Query block is undoubtedly one of the most complex features the Gutenberg team is building, and it is a crucial block for the upcoming site editor.</p>\n\n\n\n<p>There is also no posts pagination or navigation at the moment. That is because the Gutenberg team is still <a href=\"https://github.com/WordPress/gutenberg/issues/26557\">ironing out the details</a> of such a block. This is another Herculean task given the near-limitless variations on designing posts navigation. The block will need to provide theme authors the flexibility they are accustomed to when writing code.</p>\n\n\n\n<h2>Why Testing and Building Experimental Themes Matters</h2>\n\n\n\n<p class=\"has-drop-cap\">The development of Photo Blocks exposed some missing features in Gutenberg. Without community feedback from building and testing block-based themes, it is tough for the development team to identify such issues.</p>\n\n\n\n<p>Currently, the only way to have same-height images in the Photo Blocks theme&rsquo;s post grid is to manually crop and upload images with the same aspect ratio. Reigstad opened a ticket to <a href=\"https://github.com/WordPress/gutenberg/issues/27620\">set a consistent crop</a> for the Post Featured Image block. <em>I would also recommend an image-size option similar to how it is handled in the Image block.</em></p>\n\n\n\n<p>Traditionally, themes that output a grid of featured images would fall back to a default image or use the first image from the post content if one was not set. There is currently no way to do this with the Post Featured Image block &mdash; another missing key feature. Reigstad opened a new ticket that proposed <a href=\"https://github.com/WordPress/gutenberg/issues/27617\">taking the idea further</a>.</p>\n\n\n\n<p>&ldquo;In the past, the featured image was a single image, added and managed separately from the rest of the post content,&rdquo; he wrote. &ldquo;For block-based sites however, that restriction is largely unnecessary. Rather than just an image, we should consider making it possible to set a video or audio embed as the &lsquo;Featured&rsquo; block. Also, since posts are made up of structured data, it&rsquo;s theoretically possible to signify any block from within post content as a &lsquo;Featured&rsquo; block.&rdquo;</p>\n\n\n\n<p>The idea of featured media is not new. Many themes have had featured audio and video in the past. However, the concept of marking any type of block as featured is worth exploring. Even if not every block lends itself well to this, surely some do beyond images.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Dec 2020 00:35:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"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:57:\"WPTavern: Shutterstock Launches Official 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=108844\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:159:\"https://wptavern.com/shutterstock-launches-official-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=shutterstock-launches-official-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:2130:\"<p>Shutterstock has released an <a href=\"https://wordpress.org/plugins/shutterstock\">official plugin for WordPress</a>. The 17-year old company is as old as WordPress itself but this is the first time it has provided convenient access to its library inside the admin.  </p>\n\n\n\n<p>Seven years ago, Shutterstock released a <a href=\"https://wordpress.org/plugins/shutterstock-affiliate-plugin/\">plugin for affiliates</a> using a third-party development company, but it failed to gain much traction and is no longer updated. The new block-based plugin applies more broadly to WordPress site owners looking for commercial stock photography. It provides a block that allows users to search Shutterstock&rsquo;s library of 340 million images and get suggestions based on the text content. Users can place preview images on pages and posts, license with one click, download, and publish images and editorial content.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Shutterstock&rsquo;s plugin respects WordPress&rsquo; user roles and permissions system, so organizations can restrict image licensing to editors and administrators while still allowing authors to insert image previews. The plugin also has access to the user&rsquo;s license history so they can download any content that has been previously licensed on Shutterstock.</p>\n\n\n\n<p>A couple weeks after launching, the plugin is active on fewer than 10 WordPress sites. It&rsquo;s not clear if that is due to its customers not knowing about it or the endless variety of free images that WordPress users have access to through other services. Since the plugin only offers access to a limited library by default, it is primarily aimed at Shutterstock customers who have an existing subscription to connect for the full collection.  </p>\n\n\n\n<p>Along with the official plugin release, Shutterstock also announced a new partnership with WordPress.com VIP. It is now one of the service&rsquo;s &ldquo;<a href=\"https://wpvip.com/partner/shutterstock/\">Featured Technology Partners</a>,&rdquo; streamlining the publishing workflow for Automattic&rsquo;s enterprise customers. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 22 Dec 2020 23:32:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:86:\"WPTavern: What Is Full Site Editing and What Does It Mean for the Future of WordPress?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=109217\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:215:\"https://wptavern.com/what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=what-is-full-site-editing-and-what-does-it-mean-for-the-future-of-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:10892:\"<img />Block-based Twenty Twenty-One theme in the site editor.\n\n\n\n<p class=\"has-drop-cap\">As I said last week, <em>2021 will be the year of the site editor</em>.  Matt Mullenweg&rsquo;s <a href=\"https://wptavern.com/state-of-the-word-2020-wordpress-moves-toward-full-site-editing\">State of the Word</a> confirms it.  WordPress 5.7&rsquo;s <a href=\"https://wptavern.com/wordpress-5-7-development-kicks-off-with-focus-on-full-site-editing\">release planning</a> is focused on it.  It has been a long journey getting to this point, and it will be a much longer adventure afterward. The ultimate promise of the work that <a href=\"https://wptavern.com/wordpress-core-editor-team-publishes-ui-prototype-for-gutenberg-an-experimental-block-based-editor\">began nearly four years ago</a> is nigh.</p>\n\n\n\n<p>The Gutenberg project was never <em>just</em> about editing content. WordPress was aging software by late 2016. It needed to cater to modern audiences who may be less tech-savvy than the platform&rsquo;s existing user base. It needed to capture a younger generation of developers who were looking at the greener grass of JavaScript-heavy software. It needed to offer an experience on par with modern web applications. WordPress had a lot of boxes it needed to check or face irrelevance.</p>\n\n\n\n<p>The one thing that has truly kept the platform afloat is its large and diverse ecosystem of third-party developers.</p>\n\n\n\n<p><em>One of the most popular types of plugins?</em> Page builders. Those such as Elementor, which launched in early 2016, were filling in the experience gaps that WordPress was missing. While it was a testament to the platform&rsquo;s extendibility for such third-party projects to arise, it was also a failure that the core platform could not offer a better experience to both users and developers out of the box. Far too many theme authors were forced into supporting third-party builders to remain relevant. They were focusing more and more on compatibility with plugins than simply designing.</p>\n\n\n\n<p>The shortcomings of the widgets, shortcodes, meta boxes, and settings systems meant that developers had to either rely on non-core frameworks or reinvent the wheel. Every new API brought with it a new method for adding basic form fields. At best, it was inelegant, a platter of spaghetti that had been thrown at the wall, some of it managing to stick.</p>\n\n\n\n<p>WordPress was beginning to show its wrinkles. It needed to revolutionize itself. It needed to feel fresh again. For better or worse, the developers behind the Gutenberg project have been putting in the work to do just that.</p>\n\n\n\n<p>It is slow work. But, it is promising work.</p>\n\n\n\n<p>While the term &ldquo;Gutenberg&rdquo; is often used interchangeably with &ldquo;block editor,&rdquo; the two are not one and the same. Gutenberg is a project. A plugin. An idea. A new way of thinking about publishing on the web. As the opening lines of the description of the plugin read:</p>\n\n\n\n<blockquote><p>&ldquo;Gutenberg&rdquo; is a codename for a whole new paradigm in WordPress site building and publishing, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word.</p></blockquote>\n\n\n\n<p>The project has four phases:</p>\n\n\n\n<ol><li>Easier Editing</li><li>Customization</li><li>Collaboration</li><li>Multilingual</li></ol>\n\n\n\n<p>WordPress users who have not been testing the Gutenberg plugin have only experienced Phase 1 of the project. The launch of the block editor in <a href=\"https://wptavern.com/wordpress-5-0-bebo-released-lays-a-foundation-for-the-platforms-future\">WordPress 5.0</a> and its continued work set the stage for the phases to follow. The underlying block system is what will fuel the next decade or longer of WordPress.</p>\n\n\n\n<p>Today, we are firmly in the midst of Phase 2. And, this is where things will get interesting.</p>\n\n\n\n<h2>Full Site Editing</h2>\n\n\n\n<img />Selecting a template in the site editor, using the Block-Based Bosco theme.\n\n\n\n<p class=\"has-drop-cap\">Phase 2 of Gutenberg, which began in late 2018, promised to bring blocks outside of the post content. In an introduction to this next step, Mel Choyce-Dwan <a href=\"https://make.wordpress.org/core/2018/12/08/gutenberg-phase-2/\">outlined the three main focuses:</a></p>\n\n\n\n<ul><li>Be outside of <code>post_content</code>.</li><li>Focus on customization.</li><li>Upgrading themes, widgets, and menus.</li></ul>\n\n\n\n<p>Since then, those core concepts have remained the same. However, the full picture, the shape of what those concepts would look like, has changed in the last two years. If there is one thing anyone on the development team has learned, it is probably that it is hard to launch such drastic changes.</p>\n\n\n\n<p>Full Site Editing is a mix of concepts. It is one part transition from tradition and one part full overhaul of how users and developers design the front end of WordPress sites.</p>\n\n\n\n<p>Nav menus and widgets, which are a part of the old paradigm, have been set to relaunch under the block system for the past two major WordPress releases. They were not ready. Users should expect to see them in WordPress 5.7. However, these feature upgrades are merely stepping stones to true the true Full Site Editing feature. They offer a way for end-users who are still using classic WordPress themes to get a taste of blocks outside of the post-editing screen.</p>\n\n\n\n<p>For the users who take the next step, widgets and nav menus &mdash; at least the traditional admin screens &mdash; will disappear. The customizer, which was once touted as the future of theme development, is also getting the ax. Site customization via a system where everything is a block will reign supreme.</p>\n\n\n\n<p>Once the switch flips, the world will be looking at a whole new WordPress.</p>\n\n\n\n<p>WordPress 5.7 and beyond will be about the site editor and block-based themes. The site editor is the visual representation of block templates that theme developers offer to users. Templates are infinitely customizable by the user from the WordPress admin. While themers will create custom configurations and set defaults, the power to decide what the front end of the site will look like will ultimately reside in the user&rsquo;s hands.</p>\n\n\n\n<p>Since the launch of Phase 1, the block editor has been a love/hate affair. Expect the site editor to be no less controversial.</p>\n\n\n\n<p>Underneath it all, a theme&rsquo;s code and the site editor will be talking in the same language. This essentially means that users could transition to theme authors if they have a knack for design or simply want to give it a go.  They  should be able to do this without leaving the comfort of the trusty site editor, which already allows exporting templates.</p>\n\n\n\n<p>Because the post editor and the site editor both work on the same, underlying block-based foundation, there is no reason for users to not be able to seamlessly switch between the two. There is <a href=\"https://github.com/WordPress/gutenberg/pull/26355\">currently a ticket</a> for adding such a toggle on the post-editing screen. It will allow users to switch to a template-editing mode while never leaving the post editor.</p>\n\n\n\n<img />Template-editing mode likely to land in Gutenberg 9.6.\n\n\n\n<p>This is not a newly-introduced concept. Josepha Haden, who led the WordPress 5.6 release, <a href=\"https://wptavern.com/wordpress-5-6-release-team-pulls-the-plug-on-block-based-widgets\">touched on this earlier this year</a>. &ldquo;I think one of the problems that we&rsquo;re trying to solve with Gutenberg has always been a more consistent experience for editing elements across the WordPress interface,&rdquo; she said. &ldquo;No user should have to learn five different workflows to make sure their page looks the way they imagined it when it&rsquo;s published.&rdquo;</p>\n\n\n\n<p>One of the larger goals is reducing the number of workflows into a single interface. We are likely years away from seeing the whole of WordPress site management reduced that far. However, the site editor is the next step toward that potential user experience.</p>\n\n\n\n<h2>What Does All This Mean for the Future?</h2>\n\n\n\n<p class=\"has-drop-cap\">While the last few years may have felt like a whirlwind of changes to our beloved platform, <em>you ain&rsquo;t seen nothing yet</em>. We were just getting our bearings in Phase 1. The development team was building the foundation while also launching the user-facing block editor. With that foundation in place, the team can focus more on features. This will especially be true as the <a href=\"https://wptavern.com/g2-components-a-from-scratch-reimagining-of-wordpress-components\">G2 Components project </a>overhauls and standardizes how core and third-party developers build upon the block system.</p>\n\n\n\n<p>The big Phase 2 changes this year means that theme authors will need to get up to speed. Traditional WordPress themes will still be necessary for a while. However, any theme author who is not already tinkering with block-based themes is already months behind. This is the time to be exploring and helping to shape the system. It is time to be filing bug reports and feature requests.</p>\n\n\n\n<p>If possible, theme authors should be attending the twice-monthly <a href=\"https://make.wordpress.org/themes/handbook/about/#meetings\">block-based themes meetings</a>. If time does not allow for attendance, you should at least be reading and participating on the <a href=\"https://make.wordpress.org/themes/\">Make Themes blog</a>.</p>\n\n\n\n<p>It is also important to check out projects like the <a href=\"https://wptavern.com/q-first-fse-wordpress-theme-now-live\">Q theme</a> or follow the <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments</a> repository.</p>\n\n\n\n<img /><a href=\"https://wptavern.com/carrd-like-theme-experiment-provides-a-glimpse-into-the-future-of-theming\">Carrd-like theme experiment</a> from the site editor.\n\n\n\n<p>For end-users, this entire project is about you. Your feedback is crucial. If you are not already testing your site with the Gutenberg plugin, you should be. It is sometimes weeks or months ahead of what you are getting with WordPress alone.  Try out an FSE theme like <a href=\"https://wptavern.com/block-based-bosco-second-full-site-editing-theme-lands-in-the-wordpress-directory\">Block-Based Bosco</a>.  Consider joining the <a href=\"https://wptavern.com/help-steer-the-future-of-wordpress-via-the-fse-outreach-program\">FSE Outreach Program</a>. You can test and provide feedback directly on upcoming features.</p>\n\n\n\n<p>FSE brings with it the promise of major changes in 2021. Many of these changes will uproot old methods of managing your WordPress websites. Those methods will be replaced with one of the largest overhauls to the platform in its history. It is time to get prepared.</p>\n\n\n\n<p>It is going to be an interesting new year.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 22 Dec 2020 00:56:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:77:\"WPTavern: WordPress 5.7 Development Kicks Off with Focus on 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=109212\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/wordpress-5-7-development-kicks-off-with-focus-on-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-7-development-kicks-off-with-focus-on-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:3662:\"<p>If the 2020 <a href=\"https://wptavern.com/state-of-the-word-2020-wordpress-moves-toward-full-site-editing\">State of the Word</a> address was any indication, WordPress is moving full steam ahead to land full site editing in 2021. The 5.7 release cycle <a href=\"https://make.wordpress.org/core/2020/12/21/wordpress-5-7-planning-roundup/\">kicked off</a> this week with the proposed scope centered around full site editing via&nbsp;Gutenberg. Matt Mullenweg will be leading the release and the rest of the team leadership is still being rounded up. Bug scrubs for<em>&nbsp;</em><a rel=\"noreferrer noopener\" href=\"https://core.trac.wordpress.org/tickets/early\" target=\"_blank\">early tickets</a> that require more time or early testing are already underway. </p>\n\n\n\n<p>WordPress 5.7 contributors anticipate working on the following features in the next release:</p>\n\n\n\n<ul><li>Update WordPress&nbsp;Core&nbsp;to include current releases of the Gutenberg&nbsp;plugin</li><li>Gutenberg: ship additional blocks, refine the&nbsp;UI, add tools for themes and design, and continue working on the&nbsp;widget&nbsp;screen</li><li>Continue work on&nbsp;<a href=\"https://make.wordpress.org/core/2020/11/10/wp5-6-auto-update-implementation-change/\">auto-updates</a>&nbsp;and<a href=\"https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/\">&nbsp;jQuery</a></li></ul>\n\n\n\n<p>&ldquo;We might add more items in the upcoming weeks, and we will reconfirm the above-proposed list after the end-of-Gregorian year holidays,&rdquo; Francesca Marano said in a planning roundup post. She said core development is not &ldquo;closing up shop&rdquo; for the holidays, and volunteers plan to run&nbsp;<a href=\"https://make.wordpress.org/core/2020/12/11/call-for-volunteers-early-bug-scrubs-for-wordpress-5-7/\">bug scrubs</a>&nbsp;and&nbsp;<a href=\"https://make.wordpress.org/core/2020/12/11/dev-chat-schedule-for-the-end-of-the-year/\">dev chats</a>. Those who cannot attend a meeting but want to advocate for a ticket can always comment on the dev chat agenda post to have it included in the discussion.</p>\n\n\n\n<p>Matias Ventura created a GitHub issue in August for contributors to track the progress of <a href=\"https://github.com/WordPress/gutenberg/issues/24551\">full-site editing milestones</a>. Some of the infrastructure and UI is already in place, as well as the ability to navigate through pages, templates, parts, and know which is area is active. Styling, theme blocks, the Query block, and the Navigation block are still in progress.</p>\n\n\n\n<p>There are a lot of moving pieces to make full-site editing features cohesive and ready for prime time. In Ventura&rsquo;s most recent <a href=\"https://make.wordpress.org/core/2020/12/10/status-check-site-editing-and-customization/\">status update</a> on the project he reported that all of the features outlined are &ldquo;in advanced stages&rdquo; and can be used in the Gutenberg plugin already.</p>\n\n\n\n<p>&ldquo;The main hurdle to include the work in major WordPress releases are the various dependencies between each project when it comes to ensuring a great user experience,&rdquo; Ventura said. &ldquo;The immediate focus is then on completing the milestones, stabilizing the work, and doing as much testing with different kinds of users as possible.&rdquo; </p>\n\n\n\n<p>WordPress contributors are planning <a href=\"https://wordpress.org/about/roadmap/\">four releases in 2021</a>, allowing for multiple opportunities to introduce new features.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Beta 1 for 5.7 is planned for early February and the general release is expected March 9, 2021. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Dec 2020 23:18:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:48:\"BuddyPress: BuddyPress 7.1.0 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=316287\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://buddypress.org/2020/12/buddypress-7-1-0-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1204:\"<p>Immediately available is&nbsp;<a href=\"https://downloads.wordpress.org/plugin/buddypress.7.1.0.zip\">BuddyPress 7.1.0</a>. This maintenance release fixes two bugs related to issues introduced in the 7.0.0 release.</p>\n\n\n\n<ul><li>It makes sure the BP Blogs tools to repare Site icons / Site profile photos synchronization is only available to WordPress multisite configs, </li><li>It fixes the unavailability of the Groups Admin screen for site networks using the BuddyPress multiblog mode.</li></ul>\n\n\n\n<p>For details on the changes, please read the&nbsp;<a href=\"https://codex.buddypress.org/releases/version-7-1-0/\">7.1.0 release notes</a>.</p>\n\n\n\n<p>Update to BuddyPress 7.1.0 today in your WordPress Dashboard, or by&nbsp;<a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</a>.</p>\n\n\n\n<h2>Many thanks to 7.1.0 contributors&nbsp;<span class=\"dashicons dashicons-heart\"></span></h2>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/hareesh-pillai/\"></a><a href=\"https://profiles.wordpress.org/shawfactor\">shawfactor</a>, <a href=\"https://profiles.wordpress.org/slaffik\">slaFFik</a> &amp; <a href=\"https://profiles.wordpress.org/imath/\">imath</a></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Dec 2020 21:08: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:12:\"Mathieu Viet\";s: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:91:\"WPTavern: Ask the Bartender: Integrate With Third-Party App or Use Native 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=109173\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:223:\"https://wptavern.com/ask-the-bartender-integrate-with-third-party-app-or-use-native-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-integrate-with-third-party-app-or-use-native-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:5054:\"<blockquote class=\"wp-block-quote\"><p>My question to you is how you see the future (or even the present) of integrating software with WordPress and when you should make the distinction of going the integration vs. native approach.</p><p>In other words, with the vast ecosystem of WordPress plugins out there, how can a website owner discern which responsibilities WordPress the software should handle and whether that functionality is actually better to plug another software or service into instead?</p><p>Alex</p></blockquote>\n\n\n\n<p class=\"has-drop-cap\">There was a time when I would have said build <em>all the things</em> in WordPress. I was younger then, a bit more naive. I was optimistic about using WordPress as a framework to build anything. There is a part of me that still leans in this direction. Mostly, this is because I want to see what developers in the WordPress ecosystem can achieve. I applaud anyone who pushes the platform beyond its current limits.</p>\n\n\n\n<p>Few people would have guessed that WordPress would become an eCommerce powerhouse. However, WooCommerce has proven it can be done. I still remember when nearly every WordPress theme and plugin author was selling their commercial products via E-junkie. Now, Easy Digital Downloads is the go-to solution, and AffiliateWP handles the affiliate side of things.</p>\n\n\n\n<p>Some of the best products from the WordPress plugin market arose from issues with third-party app integration. Their creators bucked the system and brought useful tools directly into WordPress. Many of these are now multi-million dollar products and companies that employ dozens, hundreds, or even thousands of people. They have their own ecosystems that allow even more third-party developers to make a living. And this is all done on top of WordPress.</p>\n\n\n\n<p>I will always root for the home team, for the developers in our community to build native solutions.</p>\n\n\n\n<p>However, the reality is that WordPress is not the best solution for everything. Depending on the application, the development team has likely put years of work into it, creating a specialized system that caters to that application&rsquo;s users. The experience can often be far better than something available for WordPress.</p>\n\n\n\n<p>I cannot imagine using WordPress as the backbone of a social video site like YouTube, even if it was a small site. The hosting costs would be astronomical. It is far easier and cheaper to rely on integration with YouTube rather than trying to rebuild it.</p>\n\n\n\n<p>In Alex&rsquo;s original correspondence, he also brought up a specific case about integrating with a third-party forum. This is a far more realistic quandary than an average user trying to build the next YouTube. It is also a question that does not have a single answer.</p>\n\n\n\n<p>For users who are creating forums on their site for the first time, my advice would be to go with bbPress. It is a plugin that brings native forums to WordPress. While it is not nearly as powerful as some third-party forum applications, its best feature is that it works directly with the built-in user, role, and capability systems in WordPress. These are some of the more complex APIs in WordPress, and trying to sync user accounts between applications can often be a headache. It is also a complex technical topic that goes beyond the scope of this post. If starting from scratch, I would recommend bbPress or another WordPress forum plugin.</p>\n\n\n\n<p>On the other hand, if a user already has an existing forum with a large amount of content, I would lean toward integrating it and WordPress, particularly if the site owner plans to keep user registrations strictly within the forum software. Much of that will come down to what the end-user feels comfortable with. If they have a strong history with their existing application, making a change may simply not be the best route. There are other items to consider, such as whether sharing a single theme across both platforms is necessary. bbPress can also import content from many existing forum applications.</p>\n\n\n\n<p>The answer to the question is that it depends. Each use case is different.</p>\n\n\n\n<p><em>Should a popular seller on Etsy move everything to WooCommerce?</em> Probably not. That user might want to install the <a href=\"https://wordpress.org/plugins/etsy-shop/\">Etsy Shop</a> integration plugin. Eventually, they might expand their brand enough to no longer rely on the Etsy platform. At that point, WooCommerce could be the answer.</p>\n\n\n\n<p>It comes down to time, cost, research, and testing. Even when a plugin brings a native solution to WordPress that is ideal for most people, it might not be the best answer for an individual. Specifics matter, and I am always happy to talk those over.</p>\n\n\n\n<p class=\"has-white-color has-blue-700-background-color has-text-color has-background text-white bg-blue-700\">This is the second post in the Ask the Bartender series.  Have a question of your own? <a href=\"https://wptavern.com/contact-me/ask-the-bartender\">Shoot it over</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Dec 2020 20:50:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:74:\"WPTavern: State of the Word 2020: WordPress Moves Toward 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=109009\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/state-of-the-word-2020-wordpress-moves-toward-full-site-editing?utm_source=rss&utm_medium=rss&utm_campaign=state-of-the-word-2020-wordpress-moves-toward-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:6819:\"<p>WordPress enthusiasts around the world tuned into Matt Mullenweg&rsquo;s annual State of the Word address this week, delivered virtually for the first time. Mullenweg recognized the community&rsquo;s efforts in working together during a global pandemic, without the benefit of periodic in-person events that have traditionally re-energized collaboration on the project.</p>\n\n\n\n<p>During a most unusual year that has warped the passage of time and slowed it to the speed of molasses, WordPress&rsquo; release schedule kept a steady, reassuring pace in contrast. The first part of the State of the Word highlighted the three major releases shipped in 2020, which introduced improvements to the block editor, a new default theme, application passwords for the REST API, and new, game-changing features like block patterns, to name just a few. </p>\n\n\n\n<p>WordPress continues to grow its dominant market share and is currently sitting at 39.3% of the&nbsp;<a href=\"https://www.alexa.com/\">Alexa</a>&nbsp;top 10 million sites. Mullenweg attributed&nbsp;that growth to three major contributing factors: the lockdown, e-commerce, and economic uncertainty. The lockdowns put in place to mitigate the virus&rsquo; spread had the effect of giving people the space and time to connect online. It also drove an uptick in entrepreneurship and e-commerce. Mullenweg reported that WooCommerce facilitated more than $20 billion in sales. </p>\n\n\n\n<h3>Site Editor Beta Demo Shows Progress on Full Site Editing Project</h3>\n\n\n\n<p>Gutenberg design contributor Joen Asmussen joined by video to unveil a sneak peek of the progress on the Full Site Editing (FSE) project with a <a href=\"https://youtu.be/QI3qCoiuG3w?t=1293\">demo of the Site Editor beta</a>. The Site Editor allows users to edit a theme&rsquo;s template outside of the post&rsquo;s content. It introduces new blocks for things like the query loop, navigation, site title, tagline, and other aspects of editing templates.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>The block list view shows all the different areas of the page, such as the header, footer, columns, and site title, so the user can jump to the section for quick access. Block patterns can also be used within template designs to speed up page layout or match a demo design. Given the current complexity of creating a template design from a blank canvas, block patterns have the potential to become even more indispensable when WordPress users finally get the reins for editing theme templates.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>&ldquo;This is the culmination of several ongoing projects to expand upon and improve the customization possibilities in WordPress,&rdquo; Asmussen said. The demo offers a quick overview of how the FSE project is coming together. The reality of &ldquo;everything becoming a block&rdquo; is finally materializing. Gutenberg will soon be capable of providing a consistent editing experience across all aspects of site customization. </p>\n\n\n\n<p>&ldquo;By creating this common framework that every theme and plugin can build on, we&rsquo;re reducing the balkanization within WordPress from people who are solving these problems lots of different ways, and providing what I believe is the basis for the next decade of WordPress&rsquo; growth,&rdquo; Mullenweg said.</p>\n\n\n\n<h3>WordPress&rsquo; Global Community Reiterates the Demand for Multilingual Capabilities</h3>\n\n\n\n<p>The number of questions during the Q&amp;A related to multilingual capabilities underscores the fact that WordPress is undeniably a global community. More than 50% of WordPress sites are not using English. Better multilingual support could be key to the next era of WordPress&rsquo; growth. Nevertheless, multilingual features are at the tail end of the four-phase roadmap for the project&rsquo;s immediate future. </p>\n\n\n\n<p>Mullenweg said WordPress is about &ldquo;two years into a 10-year project,&rdquo; with good chunks of phase 1 and phase 2 done. Phase 1 includes editing inside the post/page content, creating the fundamental building blocks and also bringing them to the mobile apps. Phase 2 is centered around editing outside the content, using blocks to create the site&rsquo;s templates.</p>\n\n\n\n<p>Phase 3 will introduce new collaboration features and workflow for real-time co-editing. Phase 4, which Mullenweg said is &ldquo;just in the imagination stage right now,&rdquo; covers multilingual features. He said he expects this phase to likely &ldquo;be taken underway pretty vigorously in 2022.&rdquo;</p>\n\n\n\n<p>Mat&iacute;as Ventura answered a question about a phase 4 roadmap, confirming that there is no specific plan for its multilingual implementation right now. He said there have been some initial conversations regarding the implications of localization, specifically around patterns and block themes, and how those can be built. Nothing substantial has emerged yet but the team will be creating a more detailed overview of what is needed. Fallback languages is one feature that several community members brought up in the Q&amp;A time.</p>\n\n\n\n<p>When asked whether some existing multilingual solutions could be reused for core, Mullenweg was hesitant to prescribe a specific approach at this time. He said he is anxious to get better multilingual support in Gutenberg and offered what I believe is the most candid explanation thus far for why multilingual capabilities fall further down the the list of priorities:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Whether we do it as part of core or as part of an official plugin is to be decided. Part of the reason we made it phase 4 is that we can only do so many things well at a time. It is supremely important that we execute super well on these first phases of Gutenberg blocks. If we don&rsquo;t get phase 1 and phase 2 to be the best experiences in the world for editing bar none, of any open source or proprietary competitors or builders, phase 3 and 4 just won&rsquo;t matter because&nbsp;WordPress won&rsquo;t be relevant a decade from now. I do believe that is the most important problem we&rsquo;re facing. I don&rsquo;t want to dilute the core contributors&rsquo; focus away from the initial phases of Gutenberg because that&rsquo;s how important I think they are.</p></blockquote>\n\n\n\n<p>Mullenweg said there is nothing stopping the community from investing more in multilingual plugins and exploring different approaches to see what will get core most of the way there. The next official step would be figuring out a framework that will work well with plugins and themes.</p>\n\n\n\n<p>Depending on your interest and involvement in the community, there is a lot more to explore in the Q&amp;A. Check out the whole presentation in the video below.</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:\"Fri, 18 Dec 2020 09:21:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: Contact Form 7 Version 5.3.2 Patches Critical Vulnerability, Immediate  Update Recommended\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109081\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:241:\"https://wptavern.com/contact-form-7-version-5-3-2-patches-critical-vulnerability-immediate-update-recommended?utm_source=rss&utm_medium=rss&utm_campaign=contact-form-7-version-5-3-2-patches-critical-vulnerability-immediate-update-recommended\";s: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:1899:\"<p><a href=\"https://wordpress.org/plugins/contact-form-7/\">Contact Form 7</a> has <a href=\"https://contactform7.com/2020/12/17/contact-form-7-532/\">patched</a> a critical file upload vulnerability in version 5.3.2, released today by plugin author Takayuki Miyoshi. The plugin is installed on more than five million WordPress sites. </p>\n\n\n\n<p>&ldquo;An unrestricted file upload vulnerability has been found in Contact Form 7 5.3.1 and older versions,&rdquo; Miyoshi said. &ldquo;Utilizing this vulnerability, a form submitter can bypass Contact Form 7&rsquo;s filename sanitization, and upload a file which can be executed as a script file on the host server.&rdquo;</p>\n\n\n\n<p>The vulnerability was discovered by&nbsp;<a href=\"https://www.jinsonvarghese.com/\">Jinson Varghese Behanan</a>&nbsp;from&nbsp;<a href=\"https://www.getastra.com/\">Astra Security</a> on December 16, 2020, and Miyoshi released a fix less than 24 hours later. Behanan highlighted a few ways this vulnerability might be exploited:</p>\n\n\n\n<ol><li>Possible to upload a web shell and inject malicious scripts</li><li>Complete takeover of the website and server if there is no containerization between websites on the same server</li><li>Defacing the website</li></ol>\n\n\n\n<p>Astra Security plans to publish more details on the vulnerability in two weeks after the plugin&rsquo;s user base has had more time to update to the patched version.</p>\n\n\n\n<p>Version 5.3.2 removes control, separator, and other types of special characters from the filename to fix the unrestricted file upload vulnerability. At the time of publishing, more than a million Contact Form 7 updates have been downloaded today. Approximately 20% of the plugin&rsquo;s user base is protected from the vulnerability. Now that it has been patched and published, Contact Form 7 users who do not update will be more at risk of having the vulnerability exploited.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Dec 2020 22:32:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:73:\"WPTavern: Help Steer the Future of WordPress via the FSE Outreach Program\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=109083\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/help-steer-the-future-of-wordpress-via-the-fse-outreach-program?utm_source=rss&utm_medium=rss&utm_campaign=help-steer-the-future-of-wordpress-via-the-fse-outreach-program\";s: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:4280:\"<p>All hands on deck. 2021 will be the year of the Site Editor.</p>\n\n\n\n<p>Anne McCarthy announced the official <a href=\"https://make.wordpress.org/core/2020/12/11/the-fse-outreach-program-is-officially-starting/\">start of the Full-Site Editing (FSE) Outreach Program</a> last Friday on the Make Core blog. The program is primarily geared toward end-users. With few channels for average users to communicate with the development team, this offers an opportunity for them to provide direct feedback.</p>\n\n\n\n<p>This announcement comes on the heels of Matias Ventura&rsquo;s full <a href=\"https://make.wordpress.org/core/2020/12/10/status-check-site-editing-and-customization/\">overview of the FSE project</a>. In the post, he laid out where specific FSE features currently stand and what needs to happen to bring the project to fruition.</p>\n\n\n\n<p>The FSE Outreach Program was <a href=\"https://make.wordpress.org/core/2020/05/01/an-experimental-outreach-project-for-full-site-editing/\">expected to begin earlier</a> in the year. Josepha Haden announced it on May 1. However, there was no movement for most of 2020. An early version of FSE was also expected to land in WordPress 5.6, but that was too lofty of a goal for a feature that will essentially change everything about front-end development on the platform.</p>\n\n\n\n<p>The official launch of the program should coincide with the release of Gutenberg 9.6, which is expected to ship within the next week. The program will focus on specific features and flows related to full-site editing. According to the <a href=\"https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/faq-for-fse-outreach-experiment/\">program FAQs</a>, participants could be asked to volunteer for up to three hours per week. However, it will also be flexible enough for anyone to participate, regardless of their available hours.</p>\n\n\n\n<p>The program is also starting small, limiting feedback to more common user experiences. It is still experimental at this stage. Easing participants into such a testing program seems like a smart approach.</p>\n\n\n\n<p>Right now, the Site Editor can sometimes be a painful user experience. While it is already possible to put together some interesting layouts, at least as a labor of love, there are many missing pieces. Workflows are odd. Expected features for a design tool are nowhere to be found.  Someone might look at it today and think there is no way it could be a viable core feature next year, but the development team continues to polish the experience with each Gutenberg update. The Site Editor is not production-ready yet, but it is time to get serious about testing and feedback.</p>\n\n\n\n<p>Those interested in volunteering for the program should have a WordPress Slack account and join the <a href=\"https://wordpress.slack.com/archives/C015GUFFC00\">#fse-outreach-experiment</a> channel. McCarthy said she will also post an update on the <a href=\"https://make.wordpress.org/test/\">Make Test</a> blog with further details for participants once Gutenberg 9.6 is released.</p>\n\n\n\n<h2>The First Focus Area</h2>\n\n\n\n<p class=\"has-drop-cap\">The first feature up for discussion is a new <a href=\"https://github.com/WordPress/gutenberg/pull/26355\">template editing mode inside the post editor</a>. It adds a new &ldquo;Template&rdquo; option in the post-editing sidebar that will allow users to jump between editing their post and editing the template that outputs that post. It is a marriage of the post and site editors. Underneath, both are run by the block system, so there is little difference in the experiences.</p>\n\n\n\n<img />Potential template editing option in the post editor.\n\n\n\n<p>Long-term, it makes sense that users should be able to switch seamlessly between both editors. I worry that we may be jumping the gun a bit on this feature since the Site Editor is still at a rough beta stage. However, it does not hurt to get some early feedback on what the workflow should look like.</p>\n\n\n\n<p>&ldquo;Please keep in mind that this is the program&rsquo;s first iteration,&rdquo; wrote McCarthy in the post. &ldquo;We&rsquo;re starting with this first item and expecting the outcome to be a comprehensive list of issues that the Gutenberg team can work on as capacity allows.&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, 17 Dec 2020 22:09:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"BuddyPress: How BuddyX made its way to the official WordPress.org 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:32:\"https://buddypress.org/?p=316229\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://buddypress.org/2020/12/how-buddyx-made-its-way-to-the-official-wordpress-org-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:14561:\"<p>We use to feature BuddyPress usage case studies. These are great ways to share with you how BuddyPress can help you achieve your community site projects reading how other buddies did it. The case study you are about to read now is a bit different. It’s about the steps the lovely <a href=\"https://wordpress.org/themes/buddyx/\">BuddyX</a> BuddyPress theme had to take to be widely and freely available from the official WordPress.org theme directory. I’m very happy <a href=\"https://profiles.wordpress.org/vapvarun/\">Varun Dubey</a> took the time to write this guest post to share his experience with all of us. My secret hope is that it will inspire as many BuddyPress Theme authors as possible to do the same <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f607.png\" alt=\"?\" class=\"wp-smiley\" />.</p>\n\n\n\n<p>Varun Dubey is a full-stack WordPress &amp; BuddyPress developer. He’s the co-founder of <a rel=\"noreferrer noopener\" href=\"https://wbcomdesigns.com/about-us/\" target=\"_blank\">Wbcom Designs</a>, a WordPress themes and plugins development agency in India. He’s also a regular BuddyPress contributor, we often talk with him about the BuddyPress project during our development meetings (every other Wednesday at 19:00 UTC on Slack), he contributes to our development tasks (testing, reporting issues, patching, documenting, etc..) and he still manage to find time to help you regularly <a href=\"https://buddypress.org/members/vapvarun/forums/replies/\">replying to your support topics</a> (661 replies so far!). So, once again, many thanks to him for <a href=\"https://codex.buddypress.org/participate-and-contribute/\">getting involved with BuddyPress</a> <img src=\"https://s.w.org/images/core/emoji/13.0.1/72x72/1f60d.png\" alt=\"?\" class=\"wp-smiley\" />.</p>\n\n\n\n<p><em>So let’s learn more from his experience, here’s what he wanted to share with you about it!</em></p>\n\n\n\n<span id=\"more-316229\"></span>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I submitted my first theme at WordPress.org, and now it’s live.</p><cite><a class=\"bp-suggestions-mention\" href=\"https://buddypress.org/members/vapvarun/\" rel=\"nofollow\">@vapvarun</a></cite></blockquote>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"wp-embedded-content\"><a href=\"https://wordpress.org/themes/buddyx/\">Buddyx</a></blockquote>\n</div>\n\n\n\n<p>We, at Wbcom Designs, are excited about our achievement to present a full-fledged community theme powered by BuddyPress and WordPress. It took almost a year to work on BuddyX and make it stable enough to submit at WordPress.org.&nbsp;</p>\n\n\n\n<p>The approval process was surprisingly short, approx 6-7 weeks to get it approved after initial submission. We usually had heard that it might take 6-9 months to get the theme live.</p>\n\n\n\n<p>Submitting the theme at WordPress.org will increase your reach to all sites which are using WordPress. The WordPress theme directory is used by millions of WordPress users all over the world. The directory themes are available for download from WordPress.org, and WordPress users can also install them directly from their administration screens.</p>\n\n\n\n<p>By hosting your theme on WordPress.org, you’ll get:</p>\n\n\n\n<ul><li>Stats on how many times your theme has been downloaded</li><li>User feedback in the forums</li><li>Ratings, to see what users think of your theme.</li></ul>\n\n\n\n<p>We have learned a lot about code reviews, code quality, and theme lifecycle during the approval process. I will give a quick glimpse of how it was for BuddyX; it might help others get the theme approved quickly.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>How to start with a theme skeleton?</h2>\n\n\n\n<p>Lots of developers begin the development of a theme from scratch. There are articles and tutorials available on how to start theme development from scratch, and the <a href=\"https://developer.wordpress.org/themes/\">WordPress Themes development handbook</a> also has a detailed step guide on this topic.&nbsp;</p>\n\n\n\n<p>After comparing <a href=\"https://underscores.me/\" target=\"_blank\" rel=\"noreferrer noopener\">_s</a>, <a href=\"https://roots.io/\" target=\"_blank\" rel=\"noreferrer noopener\">roots</a>, and other starter themes, we decided to start with <a href=\"https://wprig.io/\" target=\"_blank\" rel=\"noreferrer noopener\">the WP rig</a>. WP rig helped get a basic skeleton of the BuddyX using the latest tools, best practices, and coding standards. It helped integrate lazy-loading, async/defer JavaScript enqueueing, component-level pre-loaded CSS, optimized Web Font loading, modular extensions, and a full-featured list of optional template hierarchy files at day one.&nbsp;</p>\n\n\n\n<p>Along with WordPress Code Quality Testing, <a href=\"https://make.wordpress.org/core/handbook/best-practices/coding-standards/\">WordPress Coding Standards</a> integration was also part of it. After getting initial help for the WP rig, we only have to focus on design improvement for BuddyPress Community features.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>Early prep of the Theme submission</h2>\n\n\n\n<p>After the design part gets ready, we have released our theme on our website and make it available for free download to get initial feedback as a soft launch. It received a good response from the community, and we have got some feature requests and feedback on initial versions. It helped us to gain the confidence to submit BuddyX at WordPress.org.</p>\n\n\n\n<p>You can follow these steps to check your theme against WordPress requirements before submitting it for review.&nbsp;</p>\n\n\n\n<p>1- Code Quality Check- To make sure your theme code is secure ( using proper escaping functions ), it meets <a href=\"https://github.com/WordPress/WordPress-Coding-Standards\">WordPress Coding Standards</a>.&nbsp;</p>\n\n\n\n<p>2- Theme Check by plugin- The WordPress Theme review team checks your theme using the <a href=\"https://wordpress.org/plugins/theme-check/\">Theme Check</a> plugin. It will be useful to double-check your theme against it first before uploading it.</p>\n\n\n\n<div class=\"wp-block-image\"><a href=\"https://buddypress.org/wp-content/uploads/1/2020/12/buddyx-theme-check.jpg\"><img width=\"1999\" height=\"1738\" src=\"https://buddypress.org/wp-content/uploads/1/2020/12/buddyx-theme-check.jpg\" alt=\"Illustration of the screen generated by the Theme Check plugin\" class=\"wp-image-316230\" /></a></div>\n\n\n\n<p>3- Theme Requirement Checklist- WordPress Theme review team has published <a href=\"https://make.wordpress.org/themes/handbook/review/required/\">Theme Requirements</a>. You also have to make sure you have gone through all items one by one.</p>\n\n\n\n<p>Essential points you have to double-check with Theme requirements are</p>\n\n\n\n<ul><li>Debug log should be clean; it should not have any PHP or JavaScript errors.</li><li>All strings should be ready for translation.&nbsp;</li><li>Add unminified source files along with minified JavaScript and CSS files.&nbsp;</li><li>All functions and Classes should have a theme-specific unique prefix.</li><li>All js or CSS should enqueue properly inside theme functions instead of hard-coded in the header or footer.&nbsp;</li></ul>\n\n\n\n<p>5- Theme Unit Test XML &#8211; You will also have to check with <a href=\"https://github.com/WPTT/theme-unit-test\">Unit Testing XML</a> data. It will help get proper labels and layout testing on various templates like 404, comments on pages, comments on the post, post format testing, layout, and alignment testing.&nbsp;</p>\n\n\n\n<p>6- Screenshot- It should not contain any branded logo or visible human face.</p>\n\n\n\n<p>7- Keyboard Navigation- Keyboard-dependent navigators are also mandatory features now. You can find details at the <a href=\"https://make.wordpress.org/themes/handbook/review/accessibility/required/#keyboard-navigation\">Keyboard Navigation section of the theme development handbook</a>.</p>\n\n\n\n<p>Consider the following non-coding points before submission:</p>\n\n\n\n<ol><li>Your website terms and conditions page must indicate that your <strong>company has all products under GPL</strong>.</li><li>All images inside the theme must have GPL.</li><li>Make sure you have not disabled any default WordPress features.&nbsp;</li><li>The readme file must have all credit info for used images, libraries, and references.</li><li>Theme does not represent anything illegal, dishonest, or morally offensive behavior.</li></ol>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2>Upload at WordPress.org&nbsp;</h2>\n\n\n\n<p>You can upload the theme using <a href=\"https://wordpress.org/themes/upload/\">https://wordpress.org/themes/upload/</a>, any new revision, and the theme updates.&nbsp;</p>\n\n\n\n<p>After uploading the theme files, it will create a ticket, and you will have to wait for a couple of days before any developer requests to review your theme. All reviewers are volunteers. You can also get an idea of the current theme review <a href=\"https://make.wordpress.org/themes/handbook/about/members/\">team member </a>from the codex page.</p>\n\n\n\n<p>You can also check current themes waiting in the queue at <a href=\"https://themes.trac.wordpress.org/query?status=reopened&status=reviewing&col=id&col=summary&col=owner&col=priority&col=resolution&col=time&col=changetime&col=reporter&report=8&desc=1&order=changetime\">https://themes.trac.wordpress.org</a>. It will also be useful to join the <a href=\"https://wordpress.slack.com/messages/themereview/\">Slack theme review channel</a> to discuss review issues in the open channel.</p>\n\n\n\n<div class=\"wp-block-image\"><a href=\"https://buddypress.org/wp-content/uploads/1/2020/12/buddyx-ticket.jpg\"><img width=\"1660\" height=\"1354\" src=\"https://buddypress.org/wp-content/uploads/1/2020/12/buddyx-ticket.jpg\" alt=\"Screen capture of the Themes Trac environment\" class=\"wp-image-316233\" /></a><a href=\"https://themes.trac.wordpress.org/ticket/89135\">View the full ticket</a></div>\n\n\n\n<p>Try to be proactive for any comments and points made related to your theme and submit fixes actively to keep your ticket reviewer.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h2><strong>About BuddyX features</strong></h2>\n\n\n\n<div class=\"wp-block-image\"><a href=\"https://buddypress.org/wp-content/uploads/1/2020/12/buddyx-screenshot-v.png\"><img width=\"1024\" height=\"768\" src=\"https://buddypress.org/wp-content/uploads/1/2020/12/buddyx-screenshot-v-1024x768.png\" alt=\"\" class=\"wp-image-316234\" /></a></div>\n\n\n\n<p>BuddyX is a community membership theme with BuddyPress support. It is a lightweight, fully responsive, SEO optimized, RTL &amp; Translation ready theme. It is a multipurpose theme perfect for all niches, be it membership, social community, corporate, e-commerce, LMS, etc.</p>\n\n\n\n<p>The theme also provides support for WooCommerce, WC Vendor, LearnDash, LearnPress, and GamiPress plugins. It is highly customizable and works perfectly with page builders such as Elementor and Gutenberg. BuddyX is perfect for creating social learning, marketplace, and blogging websites using BuddyPress integrations.</p>\n\n\n\n<p>BuddyX has the latest best practices for progressive web content and optimization. We have tested it with the latest BuddyPress version and popular BuddyPress addons. BuddyX is developed, maintained, and supported by Wbcom Designs.</p>\n\n\n\n<p>We have worked on the following features</p>\n\n\n\n<ul><li>User menu for logged in members</li><li>Improved UI for Activity, members, groups directory pages</li><li>Improved UI for Member and Group single unique layout</li><li>Both sidebar options for BuddyPress pages</li><li>Improve sidebar widgets style</li><li>rtMedia supports to display of single and multiple photos in the activity.</li><li>Better widgets layout</li><li>Color scheme options</li><li>Extensible with plugins</li></ul>\n\n\n\n<p>Within the theme, we have overridden several template files to make the above changes.</p>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3><strong>Activity Compotent &#8211;&nbsp;</strong></h3>\n\n\n\n<pre class=\"wp-block-verse\">buddypress/activity/entry.php\nbuddypress/activity/single/home.php</pre>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3><strong>Members Component &#8211;</strong></h3>\n\n\n\n<pre class=\"wp-block-verse\">buddypress/members/members-loop.php\nbuddypress/members/single/cover-image-header.php\nbuddypress/members/single/home.php\nbuddypress/members/single/friends/requests-loop.php\nbuddypress/members/single/groups/invites.php</pre>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3><strong>Groups Component &#8211;&nbsp;</strong></h3>\n\n\n\n<pre class=\"wp-block-verse\">buddypress/groups/groups-loop.php\nbuddypress/groups/single/cover-image-header.php\nbuddypress/groups/single/home.php\nbuddypress/groups/single/members-loop.php</pre>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<h3><strong>rtMedia plugin &#8211;</strong></h3>\n\n\n\n<pre class=\"wp-block-verse\">rtmedia/main.php&nbsp;</pre>\n\n\n\n<div class=\"wp-block-spacer\"></div>\n\n\n\n<p>We have picked the Nouveau template for BuddyX for various reasons as following.</p>\n\n\n\n<ul><li>Nouveau delivers modern markup with fresh JavaScript-powered templates.</li><li>Nouveau provides vertical and horizontal layout options for BuddyPress navigation.</li><li>Provide a grid layout and a classic flat list.</li><li>Minimal styling for better theme compatibility.</li><li>Consistent and flexible PHP template functions.</li><li>Customizer compatibility.</li><li>Better differentiation of content types.</li><li>A rethought Messages component.</li></ul>\n\n\n\n<p>Summarizing features for BuddyX, you can check a detailed overview at <a href=\"https://buddyxthe